vmwNsxTRoutingOSPFNeighborWentDown

VMWARE-NSX-MIB · .1.3.6.1.4.1.6876.120.1.0.28.0.11

Object

notification

OSPF neighbor vmwNsxTDataCenterPeerAddress moved from full to another state.
          
Action required:
1. Invoke the NSX CLI command `get logical-routers` to get the vrf id and
   switch to TIER0 service router.
2. Run `get ospf neighbor` to check the current state of this neighbor. If the
   neighbor is not listed in the output, the neighbor has gone down or out of
   the network.
3. Invoke the NSX CLI command `ping <OSPF neighbor IP address>` to verify the
   connectivity.
4. Also, verify the configuration for both NSX and peer router to ensure that
   timers and area-id match.
5. Check /var/log/syslog to see if there are any errors related to connectivity.

Context

MIB: VMWARE-NSX-MIB
OID: .1.3.6.1.4.1.6876.120.1.0.28.0.11
Type: notification
Status: current
Parent: vmwNsxTRoutingFeature
Groups: 1

Net-SNMP examples

How SNMP and these commands work

Notifications are emitted by an agent; they cannot be read with snmpget or walked.

Inspect the notification definition

/usr/bin/snmptranslate -Pud -Ir -Td -m 'VMWARE-NSX-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-NSX-MIB::vmwNsxTRoutingOSPFNeighborWentDown'

More examples

Translate to a numeric OID

/usr/bin/snmptranslate -Pud -Ir -On -m 'VMWARE-NSX-MIB' -M '/opt/observium/mibs/vmware:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'VMWARE-NSX-MIB::vmwNsxTRoutingOSPFNeighborWentDown'

Syntax

No syntax metadata recorded.

Values & Constraints

No enumerated values or constraints recorded.