TimothyXu
Contributor
Contributor

Geneve tunnel down between 1 host and 1 edge

Hi Guys,

I have 4 host transport nodes and 2 edge transport nodes, I use inter TEP to create geneve communication, each transport node has 2 uplink (2 TEP IP), NSX-T version is 3.2.

After I created T1 and T0, I start use VM to test, I found an edge (edge-1) node has 2 tunnel down, the 2 tunnels are failed to connect to one host (esxi-03) node. The 2 nodes can ping each other with large MTU 8000. Below is BFD session:

 

BFD Session
Dest_port : 3784
Diag : No Diagnostic
Encap : geneve
Forwarding : last false (current false)
Interface : c293074a-ce78-5a0c-aa52-9637498fb641
Keep-down : false
Last_cp_diag : No Diagnostic
Last_cp_rmt_diag : No Diagnostic
Last_cp_rmt_state : down
Last_cp_state : down
Last_fwd_state : NONE
Last_local_down_diag : No Diagnostic
Last_remote_down_diag : No Diagnostic
Local_address : 172.16.40.9
Local_discr : 3278883262
Min_rx_ttl : 255
Multiplier : 3
Received_remote_diag : No Diagnostic
Received_remote_state : down
Remote_address : 172.16.40.6
Remote_admin_down : false
Remote_diag : No Diagnostic
Remote_discr : 0
Remote_min_rx_interval : 0
Remote_min_tx_interval : 0
Remote_multiplier : 0
Remote_state : down
Router_down : false
Rx_cfg_min : 1000
Rx_interval : 1000
Session_type : TUNNEL
State : down
Tx_cfg_min : 100
Tx_interval : 1000

 

BFD Session
Dest_port : 3784
Diag : No Diagnostic
Encap : geneve
Forwarding : last false (current false)
Interface : f5855f5a-f13d-5169-8a6f-c8672191f690
Keep-down : false
Last_cp_diag : No Diagnostic
Last_cp_rmt_diag : No Diagnostic
Last_cp_rmt_state : down
Last_cp_state : down
Last_fwd_state : NONE
Last_local_down_diag : No Diagnostic
Last_remote_down_diag : No Diagnostic
Local_address : 172.16.40.10
Local_discr : 3927459420
Min_rx_ttl : 255
Multiplier : 3
Received_remote_diag : No Diagnostic
Received_remote_state : down
Remote_address : 172.16.40.6
Remote_admin_down : false
Remote_diag : No Diagnostic
Remote_discr : 0
Remote_min_rx_interval : 0
Remote_min_tx_interval : 0
Remote_multiplier : 0
Remote_state : down
Router_down : false
Rx_cfg_min : 1000
Rx_interval : 1000
Session_type : TUNNEL
State : down
Tx_cfg_min : 100
Tx_interval : 1000

 

0 Kudos
1 Reply
JaSo2
Enthusiast
Enthusiast

Went through something similar while deploying 3.2 in the exact same manner. Some connections were green and some were flagged as red (but none of them worked actually - I think the GUI was not showing it right).

Ended up that I had to restart all edges, before everything started to work.

0 Kudos