Ehlers, Kolja schrieb:
> Hi all,
> 
> while reading michaels book i was wondering if there is a complete treeview
> abailable for the ha mib?

Thanks. I hope you also bought it ;-)

> I have looked that the file itself but it did not
> help. How do I get from LHALiveNodeCount to .1.2.0. I guess snmpwalk is used
> for that but sill it gives me
> LINUX-HA-MIB::LHALiveNodeCount.0 = Counter32: 2 - how is that .1.2.0

Read the MIBs! It is located in /usr/share/snmp/mibs/LINUX-HA-MIB-mib

If you search for LHALiveNodeCount you will find that it is defined as
LHAClusterInfo 2, which in turn is defined as LinuxHA 1, which in turn
is defined a enterprises 4682, which is .1.2.5.1.4.1. Putting all
together LHALiveNodeCount gives you
.1.3.6.1.4.1.4682.1.2.0

Instead of reading the MIB you also could do a:
snmpwalk -v1 -cpublic -mALL -On node1 LHALiveNodeCount
.1.3.6.1.4.1.4682.1.2.0 = Counter32: 2

The option -On displays the OIDs, not the transcriptions.

> Also can I figure out something more complex like is a resource active on xx
> node? Or do I need a nrpe plugin + cl_status for that?

NOOOOOOOOOOOO!
Use SNMP, it is really SIMPLE!

Rading the MIB you will find that there are OIDs for
LHAResourceName
LHAResourceName
LHAResourceNode
LHAResourceStatus
LHAResourceIsManaged
LHAResourceFailCount
LHAResourceParent

I the LHAResourceTable, which means this information is available for
ALL resources. I hope with this information it is possible to find out
the OIDs for the interesting information yourself. Otherwise mail me.

Hint: snmpwalk (other options) -mALL node .enterprises.4682

Anyway. If you installed the MIB on you network management server it not
nescessary to know the OIDs. Since it NMS relies on SNMP and SNMP knows
the transcriptions of the OIDs you also can use the human readable
transcriptions.

> 
> Thanks

You are welcome.

Michael.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems

Reply via email to