Wism2 SNMP Authentication Failure

[mages_mark]

I cannot seem to communicate with my new Wism2 via SNMP.

The configuration is the same as on my Wism 1, same version of code, same SNMP settings and strings and subnets.

Slot  Controller  Service IP       Management IP    SW Version    Controller Type    Status

----+-----------+----------------+----------------+------------+------------------+---------------

1     1           192.168.10.2     10.XX.XX.10      7.0.116.0    WS-SVC-WISM-1-K9   Oper-Up

1     2           192.168.10.3     10.XX.XX.15      7.0.116.0    WS-SVC-WISM-1-K9   Oper-Up

3     1           192.168.10.4     10.XX.XX.20      7.0.116.0    WS-SVC-WISM-2-K9   Oper-Up

SNMPWalk of the Wism1 controllers is fine.  SNMPWalk of the Wism2 just gets me a timeout.

The snmplog does occasionally register an Authentication failure

Trying V1 and V2c with the same results.

Any advice?

[mages_mark]

So - I can snmpwalk, just not to the untagged management interface.  The tagged controller interface in the same VLAN as my host computer seems to work.

Any ideas why this is?  Not all of my SNMP widgets are going to be able to work around this.

[Stephen Rodriguez · Accepted solution]

on thew new WiSM2 did you issue the command config network-mgmt-via-dyamic interface enable?

by default the WLC has issues with responding to requests from the wire, for a subnet that it is configured to use.  The above is the workaround to this situation.

Per the best practices guide, "It is important to avoid configuring a dynamic  interface in the same sub network as a server that has to be reachable  by the controller CPU, for example a RADIUS server, as it might cause  asymmetric routing issues."

HTH,

Steve

[mages_mark]

>by default the WLC has issues with responding to requests from the wire, for a subnet that it is configured to use.

OK - that could be it.

I tried it via a machine on a subnet not served up as a dynamic interface, and it worked fine.

Thanks!