RE: OID for MIBs

"Robson, Alan" <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <2228BF4A620F664B97F85AF2B5E7507C027009A135@wdc1exchmbxp02.hq.corp.viasat.com>
I see a lot of examples where one company buys another and retains the old MIBS and PENs for the products they have acquired.

I don’t think there are any hard rules about what has to be put into sysdescr. I see guidelines…

            "A textual description of the entity.  This value should
            include the full name and version identification of the
            system's hardware type, software operating-system, and
            networking software."

But the actual content of sysdescr is up to you.

Alan

From: Pushpa Thimmaiah [mailto:[email protected]]
Sent: Thursday, July 13, 2017 7:57 AM
To: Robson, Alan
Cc: [email protected]
Subject: Re: OID for MIBs

Hi Alan,
Thank you for the clarification.
I am working in enterprise-1 and hence defined private mib for their products with iso.3.6.1.4.1.PEN1.1
and now the enterprise-1 has been acquired by enterprise-2.
Is it okay to retain mib-oid for already existing products and change only SNMPv2-MIB::sysDescr
i.e private mib  oid of enterprise-1 already existing product-1 =.1.3.6.1.4.1.PEN1.1
However its SNMPv2-MIB::sysDescr = Enterprise-2 name


Thank you,
Pushpa.T

On Thu, Jul 13, 2017 at 2:30 PM, Robson, Alan <[email protected]<mailto:[email protected]>> wrote:
iso.3.6.1.4.1 signifies an enterprise. The next number is the Private Enterprise Number (PEN), anything after that is up to the enterprise to define the meaning of.

So yes and no (but mostly no !). If the first enterprise number (PEN) belongs to your organization (ie. you work for enterprise_1), you can put whatever you like after it and it will take your meaning – call the next number a second enterprise identifier if you like, but it’s just part of enterprise_1’s MIB and has no special meaning other than what you wish it to mean and no-one would know it is intended to refer to an IANA registered PEN unless you told them.

Whereas anyone familiar with snmp would know that enterprise1_oid was an IANA enterprise number because of the iso.3.6.1.4.1 prefix regardless of whether they had read your documentation.

This may be helpful: http://www.dpstele.com/snmp/what-does-oid-network-elements.php<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.dpstele.com_snmp_what-2Ddoes-2Doid-2Dnetwork-2Delements.php&d=DwMFaQ&c=jcv3orpCsv7C4ly8-ubDob57ycZ4jvhoYZNDBA06fPk&r=xN9AnMDZvO_QvUZQZcoply6WFqSJuNcpv-dDu2fA4Ac&m=Fn4SO2dKV-o9JW9JbOxMRJxxz_InmSSMHHjp5paqQic&s=jC43IYW2X1J5nvZwFzCtU7Nv_op7eftspf2Lb554dr4&e=>

Alan

From: Pushpa Thimmaiah [mailto:[email protected]<mailto:[email protected]>]
Sent: Wednesday, July 12, 2017 11:37 PM
To: [email protected]<mailto:[email protected]>
Subject: OID for MIBs

Hi All,
Can we use two enterprise OID for mibs?
Eg:  iso.3.6.1.4.1.enterprise1_oid.enterprise2_oid.1
Kindly guide
Thank you,
Pushpa.T

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.