07-10-2015 07:35 AM
I'm running PI 2.2 as a really inexperienced admin (both in PI, and Cisco in general), and I am unable to get a Configuration Archive from a WLC Series 5508 running software version 7.6.130.0. I've finally figured out how to reproduce the problem by attempting to run the Upload configuration command within PI. When I do this, I eventually get a dialog box which tells me that the SNMP query timed out. By logging into PI as root, I have confirmed that I can successfully query the device with the RW community string, and I am getting responses. But when I run a tcpdump on PI, it appears the SNMP query for this particular OID is timing out:
.1.3.6.1.4.1.9.9.618.1.1.8.1.1.3.2.2
I also discovered I can reproduce this problem by querying that OID on a standard linux server. By using the Cisco SNMP Object Navigator tool, it seems that object translates to an InetAddressType=2, or IPv6. It doesn't appear that the WLC has any IPv6 addresses assigned, so I guess it makes sense why the query would time out. However what I can't seem to figure out is why PI is asking for an IPv6 address type? And I'm only having this problem on about 4/~80 WLCs, so I'm not sure if this is a difference in the PI device, or in the WLC config.
Anyone see this before?
07-10-2015 09:48 AM
Answered my own question. I discovered Global IPv6 Config was enabled on the WLC. When it was disabled, that changed the nature of the problem. I will submit a separate post about that.
07-10-2015 12:02 PM
Well, I spoke too soon. We did disable Global IPv6 Config on the WLC. And from the PI, I can now successfully /query/ that OID. But a network trace shows PI is sending a SetRequest to that OID and it's timing out. I have confirmed the SetRequest is using the correct RW community string.
I have deleted and re-added the device in PI.
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