When I query a box for the 'at' table,
I get answers like:

r...@localhost mibs]# snmpgetnext -v1 -cpublic localhost
RFC1213-MIB::atPhysAddress
RFC1213-MIB::atPhysAddress.2.1.10.23.0.1 = Hex-STRING: 00 13 C3 9A 0E E0

Decoding the response I see 3 (?) elements of indexing:

atPhysAddress.2.1.10.23.0.1
                  ^^^^^^^^^  This is the IP address seen on this interface
(correct!)

                ^   What does this designate/imply ?????

              ^   This address is on interface # 2  (correct!)

a) I don't understand why the 'extra' element is in the indexing, and what
   is in the MIB definition for this index variable that tells me to expect
it?
b) Are there any other situations where this occurs?  (I suppose if I
understand
   why this happens, I'll be able to answer that question myself.)

For example... what makes that different than something else like:

TCP-MIB::tcpConnState.10.23.16.1.34736.74.125.43.18.443 = INTEGER:
established(5)

address               ^^^^^^^^^^
port                             ^^^^^
address                                ^^^^^^^^^^^^
port                                                ^^^

where the index is composed of the 4 elements I'd expect?

TIA
Fulko
------------------------------------------------------------------------------
This SF.net email is sponsored by:
High Quality Requirements in a Collaborative Environment.
Download a free trial of Rational Requirements Composer Now!
http://p.sf.net/sfu/www-ibm-com
_______________________________________________
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to