02-14-2013 06:13 AM
Hi,
I've a script that does the check of port status asking OIDs
after a firmware upgrade, all these OIDs are not available.
for example:
snmpwalk -v 2c -c public 192.168.1.197 .1.3.6.1.2.1.17.4.3.1.2
iso.3.6.1.2.1.17.4.3.1.2 = No Such Instance currently exists at this OID
I also tried to follows procedures like:
http://www.cisco.com/en/US/tech/tk648/tk362/technologies_tech_note09186a00801c9199.shtml
using the community string indexing (I don't think that it applies to small business switches) but for desperation...
Have you any suggestion?
Thank you very much in advance,
and sorry if it's an already asked question, I've tried the search button, but without finding a definitive answer.
Best Regards,
Franceco
02-14-2013 07:46 AM
Hi Srl, what firmware were you using previously?
1.3.6.1.2.1.17.4.3.1.1 - dot1dTpFdbAddress
1.3.6.1.2.1.17.4.3.1.2 - dot1dTpFdbPort
1.3.6.1.2.1.2.2.1.8 - ifOperStatus
When I put the OID provided in to an Object navigator the above output are the object names provided.
http://tools.cisco.com/Support/SNMP/do/BrowseOID.do?local=en
On this document, I have provided all of the object names the switch supports from a debug console. This document includes output from 1.2.7.76 and 1.1.2.0, in which on both firmwares I cannot find those object names.
https://supportforums.cisco.com/docs/DOC-29896
Can you provide a visual evidence those OIDs are working on a previous release and not working on the current release?
-Tom
Please mark answered for helpful posts
02-14-2013 08:09 AM
Hi Tom,
thanks for your answer,
on my first switch (firmware 1.0.0.27)
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 iso.3.6.1.4.1.9.6.1.101.53.4.1.5.1
iso.3.6.1.4.1.9.6.1.101.53.4.1.5.1 = STRING: "1.0.0.27"
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 iso.3.6.1.4.1.9.6.1.101.53.4.1.6.1
iso.3.6.1.4.1.9.6.1.101.53.4.1.6.1 = STRING: "SF 300-24P"
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.17.4.3.1.1
iso.3.6.1.2.1.17.4.3.1.1.0.1.108.10.28.67 = Hex-STRING: 00 01 6C xx xx xx
iso.3.6.1.2.1.17.4.3.1.1.0.5.51.63.126.18 = Hex-STRING: 00 05 33 xx xx xx
...
iso.3.6.1.2.1.17.4.3.1.1.228.31.19.196.116.24 = Hex-STRING: E4 1F 13 xx xx xx
iso.3.6.1.2.1.17.4.3.1.1.228.31.19.196.116.26 = Hex-STRING: E4 1F 13 xx xx xx
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.17.4.3.1.2
iso.3.6.1.2.1.17.4.3.1.2.0.1.108.10.28.67 = INTEGER: 1000
iso.3.6.1.2.1.17.4.3.1.2.0.5.51.63.126.18 = INTEGER: 1000
...
iso.3.6.1.2.1.17.4.3.1.2.228.31.19.196.116.24 = INTEGER: 1000
iso.3.6.1.2.1.17.4.3.1.2.228.31.19.196.116.26 = INTEGER: 1000
francesco@europa:~$ snmpwalk -v 2c -c public 192.168.1.195 1.3.6.1.2.1.2.2.1.8
iso.3.6.1.2.1.2.2.1.8.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.2 = INTEGER: 2
...
iso.3.6.1.2.1.2.2.1.8.100000 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.8.300000 = INTEGER: 1
On firmware 1.1.1.8 same output.
If you need somthing else, please let me know.
Best Regards,
Francesco
02-14-2013 04:51 PM
Hi SRL, I have confirmed this behavior in my lab. I will engage Cisco. Here is my ticket number for tracking
624830577
-Tom
Please mark answered for helpful posts
02-15-2013 12:06 AM
Hi Tom,
thank you very much for your help.
Francesco
02-27-2013 06:11 PM
Here is the bug id for this.
-Tom
Please mark answered for helpful posts
02-28-2013 07:47 AM
Hi Tom,
thank you again but I cant'access the link, i get:
Your Cisco Guest Login is not entitled to use Bug Toolkit.
maybe I need some kind of assistance contract to access it?
Best Regards,
Francesco
02-28-2013 07:50 AM
Hi Credires, this would need elevated permissions on your Cisco ID. I am not sure what service level your Cisco ID would require to access that feature.
Suffice to say, it is a documented issue and hopefully will be addressed
-Tom
Please mark answered for helpful posts
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