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
- Siblings
- 27
Syntax
No syntax metadata recorded.
Values & Constraints
No enumerated values or constraints recorded.
Related Objects
Sibling Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| vmwNsxTRoutingBGPDown In Router vmwNsxTDataCenterLrId, BGP neighbor vmwNsxTDataCenterEntityId (vmwNsxTDataCenterBGPNeighborIP) is down.
Reason: vmwNsxTDataCenterFailureReason.
Action require… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.1 |
| vmwNsxTRoutingRoutingDownClear At least one BGP/BFD session up.
Action required:
None, receipt of this notification indicates event cleared. | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.10 |
| vmwNsxTRoutingOSPFNeighborWentDownClear OSPF neighbor vmwNsxTDataCenterPeerAddress moved to full state.
Action required:
None, receipt of this notification indicates event cleared. | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.12 |
| vmwNsxTRoutingProxyARPNotConfiguredForServiceIP Proxy ARP for Service IP vmwNsxTDataCenterServiceIP and Service entity vmwNsxTDataCenterEntityId
is not configured as the number of ARP proxy entries generated due to overlap of
t… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.13 |
| vmwNsxTRoutingProxyARPNotConfiguredForServiceIPClear Proxy ARP for Service entity vmwNsxTDataCenterEntityId is generated successfully as the
overlap of service IP with subnet of lrport vmwNsxTDataCenterLrportId on Router vmwNsxTData… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.14 |
| vmwNsxTRoutingBGPDownClear In Router vmwNsxTDataCenterLrId, BGP neighbor vmwNsxTDataCenterEntityId (vmwNsxTDataCenterBGPNeighborIP) is up.
Action required:
None, receipt of this notification indi… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.2 |
| vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborApproaching Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP reaches vmwNsxTDataCenterPrefixesCountThreshold. Limit defined for th… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.39 |
| vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborApproachingClear Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountThreshold.
… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.40 |
| vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborExceeded Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP exceeded the limit defined for this peer of vmwNsxTDataCenterPrefixes… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.41 |
| vmwNsxTRoutingMaximumIPv4PrefixesFromBGPNeighborExceededClear Number of IPv4 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountMax.
Act… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.42 |
| vmwNsxTRoutingMaximumIPv4RouteLimitApproaching IPv4 routes limit has reached vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
1. Check… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.43 |
| vmwNsxTRoutingMaximumIPv4RouteLimitApproachingClear IPv4 routes are within the limit of vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
No… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.44 |
| vmwNsxTRoutingMaximumIPv4RouteLimitExceeded IPv4 routes has exceeded limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
1. Che… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.45 |
| vmwNsxTRoutingMaximumIPv4RouteLimitExceededClear IPv4 routes are within the limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
None… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.46 |
| vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborApproaching Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP reaches vmwNsxTDataCenterPrefixesCountThreshold. Limit defined for th… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.47 |
| vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborApproachingClear Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountThreshold.
… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.48 |
| vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborExceeded Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP exceeded the limit defined for this peer of vmwNsxTDataCenterPrefixes… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.49 |
| vmwNsxTRoutingStaticRoutingRemoved In router vmwNsxTDataCenterLrId, static route vmwNsxTDataCenterEntityId (vmwNsxTDataCenterStaticAddress) was removed because
BFD was down.
Action required:
The static r… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.5 |
| vmwNsxTRoutingMaximumIPv6PrefixesFromBGPNeighborExceededClear Number of IPv6 vmwNsxTDataCenterSubsequentAddressFamily prefixes received from vmwNsxTDataCenterBGPNeighborIP is within the limit vmwNsxTDataCenterPrefixesCountMax.
Act… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.50 |
| vmwNsxTRoutingMaximumIPv6RouteLimitApproaching IPv6 routes limit has reached vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
1. Check… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.51 |
| vmwNsxTRoutingMaximumIPv6RouteLimitApproachingClear IPv6 routes are within the limit of vmwNsxTDataCenterRouteLimitThreshold on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
No… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.52 |
| vmwNsxTRoutingMaximumIPv6RouteLimitExceeded IPv6 routes has exceeded limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
1. Che… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.53 |
| vmwNsxTRoutingMaximumIPv6RouteLimitExceededClear IPv6 routes are within the limit of vmwNsxTDataCenterRouteLimitMaximum on Tier0 Gateway and all Tier0 VRFs on Edge node vmwNsxTDataCenterEdgeNode.
Action required:
None… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.54 |
| vmwNsxTRoutingStaticRoutingRemovedClear In router vmwNsxTDataCenterLrId, static route vmwNsxTDataCenterEntityId (vmwNsxTDataCenterStaticAddress) was re-added as BFD
recovered.
Action required:
None, receipt o… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.6 |
| vmwNsxTRoutingBFDDownOnExternalInterface In router vmwNsxTDataCenterLrId, BFD session for peer vmwNsxTDataCenterPeerAddress is down.
Action required:
1. Invoke the NSX CLI command `get logical-routers`.
2. Swi… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.7 |
| vmwNsxTRoutingBFDDownOnExternalInterfaceClear In router vmwNsxTDataCenterLrId, BFD session for peer vmwNsxTDataCenterPeerAddress is up.
Action required:
None, receipt of this notification indicates event cleared. | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.8 |
| vmwNsxTRoutingRoutingDown All BGP/BFD sessions are down.
Action required:
Invoke the NSX CLI command `get logical-routers` to get the tier0 service router
and switch to this vrf, then invoke the… | notification | - | .1.3.6.1.4.1.6876.120.1.0.28.0.9 |
Notification Objects
| Object | Type | Syntax | OID |
|---|---|---|---|
| vmwNsxTDataCenterTimestamp The timestamp when the NSX Data Center event occurred. | scalar | SNMPv2-TCDateAndTime | .1.3.6.1.4.1.6876.120.1.1.1 |
| vmwNsxTDataCenterFeatureName The NSX Data Center feature ID associated with the event. | scalar | VmwNsxTDataCenterFeatureIdType | .1.3.6.1.4.1.6876.120.1.1.2 |
| vmwNsxTDataCenterEventType The name of the NSX Data Center event. | scalar | VmwNsxTDataCenterEventTypeType | .1.3.6.1.4.1.6876.120.1.1.3 |
| vmwNsxTDataCenterEventSeverity The severity of the NSX Data Center event. | scalar | VmwNsxTDataCenterSeverityType | .1.3.6.1.4.1.6876.120.1.1.4 |
| vmwNsxTDataCenterNodeId The node ID from where a NSX Data Center event was emitted. | scalar | VmwNsxTDataCenterNodeIdType | .1.3.6.1.4.1.6876.120.1.1.5 |
| vmwNsxTDataCenterNodeType The type of node from where a NSX Data Center event was emitted. | scalar | VmwNsxTDataCenterNodeTypeType | .1.3.6.1.4.1.6876.120.1.1.6 |
| vmwNsxTDataCenterEntityId The ID of a NSX Data Center entity an event pertains to. The event
description field provides additional details of the entity. For
example the ID can be for a specific Load Balan… | scalar | VmwNsxTDataCenterEntityIdType | .1.3.6.1.4.1.6876.120.1.1.21 |
| vmwNsxTDataCenterPeerAddress IP address of BFD peer. | scalar | VmwNsxTDataCenterPeerAddressType | .1.3.6.1.4.1.6876.120.1.1.54 |