T.R | Title | User | Personal Name | Date | Lines |
---|
2635.1 | Pretty straightforward ... | YAHEY::BOSE | | Thu Mar 26 1992 15:02 | 34 |
|
Renato,
Here's a simple explanation of how each object gets its
object identifier.
Each object's object id is obtained by appending its sub-id
to its parent's object id.
Example :
chipcom OBJECT IDENTIFIER ::= { enterprises 49 }
chipmib01 OBJECT IDENTIFIER ::= { chipcom 1 }
chipGen OBJECT IDENTIFIER ::= { chipmib01 1 }
chipGenAddress OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-write
STATUS mandatory
DESCRIPTION
"An integer that can be used by the Management
Station for whatever purpose it chooses
(e.g., the name of the management station)."
::= { chipGen 5 }
We know that the object identifier for enterprises is 1.3.6.1.4.1.
Thus the object identifier for chipGenAddress is
1.3.6.1.4.1.49.1.1.5.
Hope this helps. (You might also want to look at RFC-1065 and RFC-1212
for further information).
Rahul.
|
2635.2 | SNMP/MIBs : RFC-1065 and RFC-1212 pointers... | ZTOIS1::VISTA | Renato VISTA, SIS Strasbourg, France | Mon Mar 30 1992 08:08 | 10 |
|
Hello Rahul,
And thank you for your explanations !
Have you got any EASYnet pointers about RFC-1065 and RFC-1212 ? I'm
very interested by SNMP/MIBs standard descriptions.
Renato
|
2635.3 | | YAHEY::BOSE | | Mon Mar 30 1992 11:30 | 6 |
|
Renato,
The RFCs can be found on NETRIX in the ~rfc directory.
From VMS do a $ dir netrix::"~rfc" to get a list of all the RFCs.
Rahul.
|