vmwNsxTFederationRtepBGPDown

RTEP (Remote Tunnel Endpoint) BGP session from source IP vmwNsxTDataCenterBGPSourceIP
to remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP is down.
Reason: vmwNsxTDataCenterFailureReason.
          
Action required:
1. Invoke the NSX CLI command `get logical-routers` on the affected edge node.
2. Switch to REMOTE_TUNNEL_VRF context.
3. Invoke the NSX CLI command `get bgp neighbor summary` to check the BGP neighbor status.
4. Alternatively, invoke the NSX API GET /api/v1/transport-nodes/<transport-node-id>/inter-site/bgp/summary
   to get the BGP neighbor status.
5. Invoke the NSX CLI command `get interfaces` and check if the correct RTEP IP address is assigned
   to the interface with name remote-tunnel-endpoint.
6. Check if the ping is working successfully between assigned RTEP IP address (vmwNsxTDataCenterBGPSourceIP) and the
   remote location vmwNsxTDataCenterRemoteSiteName neighbor IP vmwNsxTDataCenterBGPNeighborIP.
7. Check /var/log/syslog for any errors related to BGP.
8. Invoke the NSX API GET or PUT /api/v1/transport-nodes/<transport-node-id> to get/update remote_tunnel_endpoint
   configuration on the edge node.
   This will update the RTEP IP assigned to the affected edge node.
          
If the reason indicates `Edge is not ready`, check why the Edge node is not in good state.
1. Invoke the NSX CLI command `get edge-cluster status` to check reason why Edge node might be down.
2. Invoke the NSX CLI commands `get bfd-config` and `get bfd-sessions` to check if BFD is running well.
3. Check any Edge health related alarms to get more information.

MIB

VMWARE-NSX-MIB

OID

.1.3.6.1.4.1.6876.120.1.0.32.0.1

Type

notification

Status

current

Parent

vmwNsxTFederationFeature

Siblings

25