[c-nsp] Nexus OIDs

[Mike Hammett]

I apparently don't have oid2name on my system, nor can I figure out how to get it into Ubuntu 16.04. However... 

I got iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.9.12.3.1.3.1508 

iso.3.6.1.4.1.9.12.3.1.3.1508 = No Such Object available on this agent at this OID 

I poked around in some MIBs, but yeah, all I could find was the basic reference to each of what I posted, but up one level. I mean I know what it is by looking at the data, but I'm trying to do the legwork for the OSS_SNMP guys to be able follow a sort of chain of command to get to those results. 

Then again, maybe Cisco doesn't support that. 



----- 
Mike Hammett 
Intelligent Computing Solutions 

Midwest Internet Exchange 

The Brothers WISP 

----- Original Message -----

From: "Lee" <ler762 at gmail.com> 
To: "Mike Hammett" <cisco-nsp at ics-il.net> 
Cc: cisco-nsp at puck.nether.net 
Sent: Monday, February 27, 2017 11:35:59 AM 
Subject: Re: [c-nsp] Nexus OIDs 

what does this get you 
snmpget <deviceName> .1.3.6.1.2.1.1.2.0 

$ oid2name .1.3.6.1.2.1.1.2.0 
RFC1213-MIB::sysObjectID.0 

from the mib: 
sysObjectID OBJECT-TYPE 
SYNTAX OBJECT IDENTIFIER 
ACCESS read-only 
STATUS mandatory 
DESCRIPTION 
"The vendor's authoritative identification of the 
network management subsystem contained in the 
entity. This value is allocated within the SMI 
enterprises subtree (1.3.6.1.4.1) and provides an 
easy and unambiguous means for determining `what 
kind of box' is being managed. For example, if 
vendor `Flintstones, Inc.' was assigned the 
subtree 1.3.6.1.4.1.4242, it could assign the 
identifier 1.3.6.1.4.1.4242.1.1 to its `Fred 
Router'." 
::= { system 2 } 


everything you listed is in the entity mib, which is a bit of a pain 
to figure out 

+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.2.149 
ENTITY-MIB::entPhysicalDescr.149 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.7.149 
ENTITY-MIB::entPhysicalName.149 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.13.10 
ENTITY-MIB::entPhysicalModelName.10 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.13.22 
ENTITY-MIB::entPhysicalModelName.22 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.13.149 
ENTITY-MIB::entPhysicalModelName.149 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.11.10 
ENTITY-MIB::entPhysicalSerialNum.10 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.11.22 
ENTITY-MIB::entPhysicalSerialNum.22 
+ snmptranslate iso.3.6.1.2.1.47.1.1.1.1.11.149 
ENTITY-MIB::entPhysicalSerialNum.149 

Regards, 
Lee 


On 2/27/17, Mike Hammett <cisco-nsp at ics-il.net> wrote: 
> I did an SNMPWalk of two of my Nexus switches looking for what has the model 
> and serial numbers. I found several, sometimes with slightly different 
> information. The MIBs on Cisco's site don't go down this far either. I was 
> wondering if someone could point me as to the differences among them and\or 
> which one would be "more standard" across product lines. 
> 
> iso.3.6.1.2.1.47.1.1.1.1.2.149 = STRING: "Nexus 3548 Chassis" 
> iso.3.6.1.2.1.47.1.1.1.1.7.149 = STRING: "Nexus 3548 Chassis" 
> iso.3.6.1.2.1.47.1.1.1.1.13.10 = STRING: "N3K-C3548P-10GX" 
> iso.3.6.1.2.1.47.1.1.1.1.13.22 = STRING: "N3K-C3548P-10GX" 
> iso.3.6.1.2.1.47.1.1.1.1.13.149 = STRING: "N3K-C3548P-10GX" 
> iso.3.6.1.2.1.47.1.1.1.1.11.10 = STRING: "[redacted]" 
> iso.3.6.1.2.1.47.1.1.1.1.11.149 = STRING: "[redacted]" 
> 
> 
> 
> iso.3.6.1.2.1.47.1.1.1.1.2.149 = STRING: "N9K-C9396PX" 
> iso.3.6.1.2.1.47.1.1.1.1.7.149 = STRING: "N9K-C9396PX" 
> iso.3.6.1.2.1.47.1.1.1.1.13.10 = STRING: "N9K-C9396PX" 
> iso.3.6.1.2.1.47.1.1.1.1.13.22 = STRING: "N9K-C9396PX" 
> iso.3.6.1.2.1.47.1.1.1.1.13.149 = STRING: "N9K-C9396PX" 
> iso.3.6.1.2.1.47.1.1.1.1.11.10 = STRING: "[redacted]" 
> iso.3.6.1.2.1.47.1.1.1.1.11.22 = STRING: "[redacted]" 
> iso.3.6.1.2.1.47.1.1.1.1.11.149 = STRING: "[redacted]" 
> 
> 
> 
> 
> 
> ----- 
> Mike Hammett 
> Intelligent Computing Solutions 
> 
> Midwest Internet Exchange 
> 
> The Brothers WISP 
> 
> _______________________________________________ 
> cisco-nsp mailing list cisco-nsp at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/cisco-nsp 
> archive at http://puck.nether.net/pipermail/cisco-nsp/ 
>