SMARTS NPM: Why isn't the OSPFNeighborRelationship Down event generated?
Article ID: 331779
Updated On:
Products
VMware Smart Assurance
Environment
VMware Smart Assurance - SMARTS
Resolution
For the OSPF to generate an OSPFNeighborRelationship down event, either the NeighborState1 or NeighborState2 have to be in a non-established state. If the NeighborState1 and/or NeighborState2 are UNKNOWN , the OSPF domain will not generate a down alarm because UNKNOWN state is a default state which sometimes can be caused by SNMP failures, error cases or device not reachable cases.
When two ends of a relationship (EndPoints / NeighborState) is UNKNOWN, the OSPF domain manager cannot generate an alarm. This behavior cannot be changed.
Please consider the following as reason of why the EndPoints/NeighborState can be UNKNOWN:
SNMP might be unresponsive resulting in the endpoint state being UNKNOWN.
OSPF Traffic has not started can result in endpoint state being UNKNOWN
UNKNOWN is a startup state thus we do not generate events on.
Device being unreachable can result endpoint state being UNKNOWN
When two ends of a relationship (EndPoints / NeighborState) is UNKNOWN, the OSPF domain manager cannot generate an alarm. This behavior cannot be changed.
Please consider the following as reason of why the EndPoints/NeighborState can be UNKNOWN:
SNMP might be unresponsive resulting in the endpoint state being UNKNOWN.
OSPF Traffic has not started can result in endpoint state being UNKNOWN
UNKNOWN is a startup state thus we do not generate events on.
Device being unreachable can result endpoint state being UNKNOWN
Additional Information
This is different from generating false OSPFNeighborRelationship Down events when one end of the neighbor is no longer valid and when the topology has duplicate IP in the neighbor relationship.
Feedback
Yes
No
Powered by
