12-27-2007 01:24 PM
Does anyone know the OID/MIB needed to retrieve the system serial numbers of member stack switches?
Solved! Go to Solution.
12-27-2007 05:42 PM
Have a look at the following OIDs:
chassisId
(.1.3.6.1.4.1.9.3.6.3)
chassisSerialNumberString (.1.3.6.1.4.1.9.5.1.2.19)
If ths is a stack like 3750's I would look at:
entPhysicalSerialNum (.1.3.6.1.2.1.47.1.1.1.1.11)
http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=
ENTITY-MIB
My polling result:
% snmpget -c public 10.1.1.1
1.3.6.1.2.1.47.1.1.1.1.11.1001
SNMPv2-SMI::mib-2.47.1.1.1.1.11.1001 = STRING: "CAT0806N1X3"
% snmpget -c public 10.1.1.1
1.3.6.1.2.1.47.1.1.1.1.11.2001
SNMPv2-SMI::mib-2.47.1.1.1.1.11.2001 = STRING: "CAT0806N1X4"
12-27-2007 05:42 PM
Have a look at the following OIDs:
chassisId
(.1.3.6.1.4.1.9.3.6.3)
chassisSerialNumberString (.1.3.6.1.4.1.9.5.1.2.19)
If ths is a stack like 3750's I would look at:
entPhysicalSerialNum (.1.3.6.1.2.1.47.1.1.1.1.11)
http://tools.cisco.com/Support/SNMP/do/BrowseMIB.do?local=en&step=2&mibName=
ENTITY-MIB
My polling result:
% snmpget -c public 10.1.1.1
1.3.6.1.2.1.47.1.1.1.1.11.1001
SNMPv2-SMI::mib-2.47.1.1.1.1.11.1001 = STRING: "CAT0806N1X3"
% snmpget -c public 10.1.1.1
1.3.6.1.2.1.47.1.1.1.1.11.2001
SNMPv2-SMI::mib-2.47.1.1.1.1.11.2001 = STRING: "CAT0806N1X4"
12-28-2007 05:30 AM
entPhysicalSerialNum (.1.3.6.1.2.1.47.1.1.1.1.11) is the OID I was looking for. I actually found this last night after the post. Needless to say, the manner by which I found this was a bit crude, eg. searching through multiple MIBs for the word "serial," for serial number.
02-22-2019 04:41 AM - edited 02-22-2019 04:46 AM
Hi
I ended up on this page while attempting to find the serial numbers of all the switches in a stack. Thanks for sharing the OID, this helped me getting closer to what I was trying to achieve. Although the thread is marked solved but unfortunately snmp get didn't work and there are other limitations.
snmpget -v2c -c testcommunity 192.168.13.1 .1.3.6.1.4.1.9.3.6.3
iso.3.6.1.4.1.9.3.6.3 = No Such Instance currently exists at this OID
This may be because of my environment.
snmpget -v2c -c testcommunity 192.168.13.1 .1.3.6.1.4.1.9.5.1.2.19
iso.3.6.1.4.1.9.5.1.2.19 = No Such Instance currently exists at this OID
snmpget -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11
iso.3.6.1.2.1.47.1.1.1.1.11 = No Such Instance currently exists at this OID
if snmpwalk is used, serial numbers are shown of the first switch only (from the stack of two)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.4.1.9.3.6.3
iso.3.6.1.4.1.9.3.6.3.0 = STRING: "FDO152....A"
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.4.1.9.5.1.2.19
iso.3.6.1.4.1.9.5.1.2.19.0 = STRING: "FDO152....A"
command below does show both serial numbers of two switch stack against oid
but the issue is, it also show some other serial numbers which are not system serial numbers and doesn't correspond to any thing in the output of show version
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11
iso.3.6.1.2.1.47.1.1.1.1.11.1 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1001 = STRING: "FDO152....A"
iso.3.6.1.2.1.47.1.1.1.1.11.1002 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1003 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1004 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1005 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1006 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1007 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1008 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1009 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1010 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1011 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1012 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1013 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1014 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1015 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1016 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1017 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1018 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1019 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1020 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1021 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1022 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1023 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1024 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1025 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1026 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1027 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1028 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1029 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1030 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1031 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1032 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1033 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1034 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1035 = STRING: "LIT150....S"
iso.3.6.1.2.1.47.1.1.1.1.11.1036 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1037 = STRING: "FDO151....X"
iso.3.6.1.2.1.47.1.1.1.1.11.1038 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1039 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1040 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1041 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1042 = STRING: "LIT150....U"
iso.3.6.1.2.1.47.1.1.1.1.11.1043 = STRING: "FNS133....B "
iso.3.6.1.2.1.47.1.1.1.1.11.1049 = STRING: "FNS081....3 "
iso.3.6.1.2.1.47.1.1.1.1.11.1056 = STRING: "F78...2 "
iso.3.6.1.2.1.47.1.1.1.1.11.1065 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1066 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1067 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1068 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.1069 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2001 = STRING: "FDO152....4"
iso.3.6.1.2.1.47.1.1.1.1.11.2002 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2003 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2004 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2005 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2006 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2007 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2008 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2009 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2010 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2011 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2012 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2013 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2014 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2015 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2016 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2017 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2018 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2019 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2020 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2021 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2022 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2023 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2024 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2025 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2026 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2027 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2028 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2029 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2030 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2031 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2032 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2033 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2034 = STRING: "LIT150....B"
iso.3.6.1.2.1.47.1.1.1.1.11.2035 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2036 = ""
iso.3.6.1.2.1.47.1.1.1.1.11.2037 = ""
OID
iso.3.6.1.2.1.47.1.1.1.1.11.1001
iso.3.6.1.2.1.47.1.1.1.1.11.2001
results shows serial numbers of both switches int he stack.
The problem I have is, we have stacks with different numbers of switches in them. For the purpose of writing a generic script and querying different sized stacks I am unable to use OID provided above to give me serial numbers of all the switches in the stacks.
The example above queried only two switches probably because of prior knowledge that the stack contain two switches.
Hopefully someone can provide a OID else I have add more checks in the script for snmpwalk or query the possible non existing switches in the stack
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.1001 (for 1st switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.2001 (for 2nd switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.3001 (for 3rd switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.4001 (for 4th switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.5001 (for 5th switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.6001 (for 6th switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.7001 (for 7th switches serial number in the stack)
snmpwalk -v2c -c testcommunity 192.168.13.1 .1.3.6.1.2.1.47.1.1.1.1.11.8001 (for 8th switches serial number in the stack)
Thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide