Here are some mibs that can be used for that. I have a script that builds the logic. I will share it when I have time.
Inside MIB ID 1.3.6.1.4.1.9.9.498 you will find a lot of measurements to monitor the cluster.
Use these MIBs with this result:
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.1 = STRING: "Rack0"
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.2 = STRING: "Rack1"
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.2 = INTEGER: 1
if SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.1 returns 1 , then the node is ok.if SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.1 does not result anything, then node is down.
Example both are ok:
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.1 = STRING: "Rack0"
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.2 = STRING: "Rack1"
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.2 = INTEGER: 1
Example Rack0 is down:
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.1 = STRING: "Rack1"
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.2 = failed result
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.2 = failed result
Example Rack1 is down:
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.1 = STRING: "Rack0"
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.2.1.2 = failed result
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.1 = INTEGER: 1
SNMPv2-SMI::enterprises.9.9.498.1.1.6.1.10.1.2 = failed result
Example rack0 and rack1 are down:
guess what ... not reply :)
No comments:
Post a Comment