[Firstly, can you please send plain unencoded text.
The base64 encoding with an "unusual" charset makes it
harder to read the contents of your message. Thanks.]
> One question regarding the OBJECT IDENTIFIER in your NET-SNMP-MIB.tx file.
> Do you always have to begin the OBJECT from {xxx 1} or you can skip the
> {xxx 1} and start from {xxx 2}?
No - you can order the internal OID numbering however you like.
For example, see NET-SNMP-MONITOR-MIB.txt which starts:
nsProcess OBJECT IDENTIFIER ::= {netSnmpObjects 21}
nsDisk OBJECT IDENTIFIER ::= {netSnmpObjects 22}
nsFile OBJECT IDENTIFIER ::= {netSnmpObjects 23}
nsLog OBJECT IDENTIFIER ::= {netSnmpObjects 24}
or NET-SNMP-SYSTEM-MIB.txt, which starts:
nsMemory OBJECT IDENTIFIER ::= {netSnmpObjects 31}
nsSwap OBJECT IDENTIFIER ::= {netSnmpObjects 32}
nsCPU OBJECT IDENTIFIER ::= {netSnmpObjects 33}
nsLoad OBJECT IDENTIFIER ::= {netSnmpObjects 34}
nsDiskIO OBJECT IDENTIFIER ::= {netSnmpObjects 35}
or the new NET-SNMP-EXTEND-MIB.txt, which starts:
nsExtendObjects OBJECT IDENTIFIER ::= { nsExtensions 2}
nsExtendGroups OBJECT IDENTIFIER ::= { nsExtensions 3}
> For example,
> netSnmpObjects OBJECT IDENTIFIER ::= {netSnmp 1}
> Can you change the above line and change the number
> netSnmpObjects OBJECT IDENTIFIER ::= {netSnmp 2}
> whatever the rest of {netSnmp n} ==> {netSnmp n+1} respectively ?
Note that once a MIB has been "published", then you can *NOT* change
the numbers afterwards. You can drop a particular object, and
define a new alternative, but it needs to have a new name and a new
number. Once you've made a decision as to how to organise the MIB,
that's fixed.
> And of course what ever the descending module/object should be
> adjusted accordingly.
> Will there any problem of loading the module? Thanks for your advise.
No - there shouldn't be any problems in loading such modules.
The MIB parsing library doesn't care what numbers you use.
It's just convenient to number MIB objects sequentially.
Dave
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Net-snmp-coders mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
