![]() Could you try doing this to make sure it works.Īlso, are you trying to get the slot MAC's from the BD slots or a summit stack slot? These OID's are for summit stacking slots. ![]() You can try to poll the switch for OUI's through the CLI. I downgraded a summit stack to 15.3.4.6 to make sure it was not a SW version issue, and these OID's did work when I was using ireasoning mib browser. Any suggestions I'm running out of ideas? I have posted screen shots below of a good and bad SNMP pull. I have about 50+ non-stacked summit switches that are able to pull snmp correctly. As mentioned earlier this is happening on all four of my blackdiamond switches and all stacked summit switches. The tool I am using to gather information is LANsweeper, I initially contacted them about the issue but they seem to think it is a firmware issue on the switch itself. This is causing an issue because I now have one asset for each IP I've assigned to my cores. It will pull other basic information and pull the macs associated with each port but not the mac of the switch itself. However when I scan the problematic switches SNMP does not return the mac address for the device and the port status is a consistent "testing" state. I am only trying to pull basic information such as device info (sysname, contact, MAC, etc) and port mappings. ![]() SNMPv2 is configured the same on all switches in our environment. My non-stacked Summit series switches are not experiencing this issue and are pulling all info as expected. I am currently having an issue pulling device info from my Blackdiamond cores and stacked Summit series switches via SNMP (Both v2 and V3 produce same results). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |