On 2 November 2011 01:09, Nguyen Dinh Phong <[email protected]> wrote:
> For example with the system mib:
> system.sysdescr.0 for the main node
> system.sysdescr.[index1] for node 1
> system.sysdescr.[index2] for node2,
No - SNMP doesn't work like that.
sysDescr (note the capitalisation) is defined as a scalar object.
That means the *only* valid instance is sysDescr.0
Anything else is Just Plain Wrong.
The way to handle multiple overlapping instances is to use
different contexts (SNMPv3 & AgentX), or different communities
(SNMPv1 & 2c) to distinguish which box you were interested in.
So
snmpget -c public .... sysDescr.0
might give you the information for the main node
while
snmpget -c comm1 .... sysDescr.0
might give you the information for node 1
It takes a little work to set this up, but such an arrangement is
certainly possible, But you can't unilaterally change a scalar
object into a table as you're proposing above.
Dave
------------------------------------------------------------------------------
RSA® Conference 2012
Save $700 by Nov 18
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev1
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
