iso/org/dod/internet/private/enterprises/.6876/.120/vmwNSXsysMIB/vmwNsxTDataCenterNotifications/vmwNsxTFederationFeaturePrefix/vmwNsxTFederationFeature/vmwNsxTFederationRtepConnectivityLost
vmwNsxTFederationRtepConnectivityLost
NOTIFICATION-TYPE
1.3.6.1.4.1.6876.120.1.0.32.0.7
Description
Edge node vmwNsxTDataCenterTransportNodeName lost RTEP (Remote Tunnel Endpoint) connectivity with remote location vmwNsxTDataCenterRemoteSiteName. Action required: 1. Invoke the NSX CLI command `get logical-routers` on the affected edge node vmwNsxTDataCenterTransportNodeName. 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 and the RTEP IP addresses on the remote location vmwNsxTDataCenterRemoteSiteName. 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 vmwNsxTDataCenterTransportNodeName.