Re: Mapping of the MODULE-IDENTITY value
David Spakes <[email protected]>
| Newsgroups | gmane.ietf.snmpv3 |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 29 Nov 2002, Harrie Hazewinkel wrote:
> The SNMPv2-MIB. That MIB module was already under mib-2 and
> did not have a MODULE-IDENTITY. After 'upgrading' it to
> SMIv2 the MODULE-IDENTITY was added, but the MODULE-IDENTITY
> could not become the top node of the snmp subtree.
Why couldn't the OBJECT IDENTIFIER for "snmp" have been reused in a
MODULE-IDENTITY macro?
What difference is there between invoking the MODULE-IDENTITY and defining
a non-leaf OBJECT IDENTIFIER?
Consider the mosy tool. When run with the argument "-1", mosy converts
an SMIv2 document to SMIv1. In the process, it maps MODULE-IDENTITY to
OBJECT IDENTIFIER (see example below). Why wouldn't it be okay to go
the other way around when one is republishing a MIB document in SMIv2?
Regards,
David
-------------------------------------------
Command line:
% mosy -1 -o vcr_smiv1.my vcr.my
Text from our original SMIv2 document (vcr.my):
vcr MODULE-IDENTITY
LAST-UPDATED "9603050000Z"
ORGANIZATION "SNMP Research"
CONTACT-INFO
" Technical Support
Postal: SNMP Research
3001 Kimberlin Heights Road
Knoxville, TN 37920-9716
Tel: +1 865 573 1434
Fax: +1 865 573 9197
E-mail: [email protected]
Europe: [email protected]"
DESCRIPTION
"An example MIB module to demonstrate the SNMP
Research method routines for row creation in
conceptual tables and MIB tool features for the
RowStatus textual convention."
::= { srTableRowCreation 1 }
Text produced by mosy with -1 argument (vcr_smiv1.my):
vcr OBJECT IDENTIFIER ::= { srTableRowCreation 1 }
-------------------------------------------------------------
David Spakes email: [email protected]
SNMP Research voice: +1 865 573 1434
3001 Kimberlin Heights Road fax: +1 865 573 9197
Knoxville, TN 37920-9716 USA http://www.snmp.com
-------------------------------------------------------------