Ad Widget

Collapse

How to manage OID dynamically present in the SNMP tree when items go "Not supported"

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • asindona
    Junior Member
    • Dec 2009
    • 2

    #1

    How to manage OID dynamically present in the SNMP tree when items go "Not supported"

    Hi all
    I want to monitor a link status from the routing status point of view. In particular I want to monitor the OSPF adjacency on a link. I have found in the SNMP tree that there is the following path available:

    MIB-2::OSPF:spfNbrTable:spfNbrEntry:spfNbrState (.1.3.6.1.2.1.14.10.1.6)

    The OID must be completed with the physical address of the ospf neighbor and .0 and it returns a number which represents from 1 (down) to 8 (full) the ospf state of the neighborship. As an example the full OID is .1.3.6.1.2.1.14.10.1.6.10.0.255.4.0 for the neighbor 10.0.255.4

    Unfortunately if the adjacency is not present then the OID doesn't exist (and the entire ospfNbrTable do not exist if no neighbors are present) so if I create an item for the adjacency it becomes "Not supported" when the neighbor disappears and the trigger I created do not works.

    The problem is the following: I want to manage the fact that the OID is not present as an information and the trigger should become a problem if the OID is not existent OR if the retrieved value is below 8 (FULL adjacency). The .nodata() function doesn't work as well as the .count(). How can I manage this situation?

    Thanks
  • grmnrvs
    Member
    • Jun 2018
    • 35

    #2
    Originally posted by asindona
    Hi all
    I want to monitor a link status from the routing status point of view. In particular I want to monitor the OSPF adjacency on a link. I have found in the SNMP tree that there is the following path available:

    MIB-2::OSPF:spfNbrTable:spfNbrEntry:spfNbrState (.1.3.6.1.2.1.14.10.1.6)

    The OID must be completed with the physical address of the ospf neighbor and .0 and it returns a number which represents from 1 (down) to 8 (full) the ospf state of the neighborship. As an example the full OID is .1.3.6.1.2.1.14.10.1.6.10.0.255.4.0 for the neighbor 10.0.255.4

    Unfortunately if the adjacency is not present then the OID doesn't exist (and the entire ospfNbrTable do not exist if no neighbors are present) so if I create an item for the adjacency it becomes "Not supported" when the neighbor disappears and the trigger I created do not works.

    The problem is the following: I want to manage the fact that the OID is not present as an information and the trigger should become a problem if the OID is not existent OR if the retrieved value is below 8 (FULL adjacency). The .nodata() function doesn't work as well as the .count(). How can I manage this situation?

    Thanks
    Hello, can you resolve it?

    Comment

    Working...