<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Wism2 SNMP Authentication Failure in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735825#M37507</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So - I can snmpwalk, just not to the untagged management interface.&amp;nbsp; The tagged controller interface in the same VLAN as my host computer seems to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas why this is?&amp;nbsp; Not all of my SNMP widgets are going to be able to work around this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 14 Sep 2011 21:17:58 GMT</pubDate>
    <dc:creator>mages_mark</dc:creator>
    <dc:date>2011-09-14T21:17:58Z</dc:date>
    <item>
      <title>Wism2 SNMP Authentication Failure</title>
      <link>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735824#M37506</link>
      <description>&lt;P&gt;I cannot seem to communicate with my new Wism2 via SNMP.&lt;/P&gt;&lt;P&gt;The configuration is the same as on my Wism 1, same version of code, same SNMP settings and strings and subnets.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Slot&amp;nbsp; Controller&amp;nbsp; Service IP&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Management IP&amp;nbsp;&amp;nbsp;&amp;nbsp; SW Version&amp;nbsp;&amp;nbsp;&amp;nbsp; Controller Type&amp;nbsp;&amp;nbsp;&amp;nbsp; Status&lt;/P&gt;&lt;P&gt;----+-----------+----------------+----------------+------------+------------------+---------------&lt;/P&gt;&lt;P&gt;1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.10.2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.XX.XX.10&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7.0.116.0&amp;nbsp;&amp;nbsp;&amp;nbsp; WS-SVC-WISM-1-K9&amp;nbsp;&amp;nbsp; Oper-Up&lt;/P&gt;&lt;P&gt;1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 2&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.10.3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.XX.XX.15&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7.0.116.0&amp;nbsp;&amp;nbsp;&amp;nbsp; WS-SVC-WISM-1-K9&amp;nbsp;&amp;nbsp; Oper-Up&lt;/P&gt;&lt;P&gt;3&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.10.4&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 10.XX.XX.20&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 7.0.116.0&amp;nbsp;&amp;nbsp;&amp;nbsp; WS-SVC-WISM-2-K9&amp;nbsp;&amp;nbsp; Oper-Up&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;SNMPWalk of the Wism1 controllers is fine.&amp;nbsp; SNMPWalk of the Wism2 just gets me a timeout.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The snmplog does occasionally register an Authentication failure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Trying V1 and V2c with the same results.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any advice?&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 03:46:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735824#M37506</guid>
      <dc:creator>mages_mark</dc:creator>
      <dc:date>2021-07-04T03:46:39Z</dc:date>
    </item>
    <item>
      <title>Wism2 SNMP Authentication Failure</title>
      <link>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735825#M37507</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;So - I can snmpwalk, just not to the untagged management interface.&amp;nbsp; The tagged controller interface in the same VLAN as my host computer seems to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas why this is?&amp;nbsp; Not all of my SNMP widgets are going to be able to work around this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2011 21:17:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735825#M37507</guid>
      <dc:creator>mages_mark</dc:creator>
      <dc:date>2011-09-14T21:17:58Z</dc:date>
    </item>
    <item>
      <title>Wism2 SNMP Authentication Failure</title>
      <link>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735826#M37508</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;on thew new WiSM2 did you issue the command config network-mgmt-via-dyamic interface enable? &lt;MIGHT need="" to="" check="" my="" syntax="" there=""&gt;&lt;/MIGHT&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;by default the WLC has issues with responding to requests from the wire, for a subnet that it is configured to use.&amp;nbsp; The above is the workaround to this situation. &lt;/P&gt;&lt;P&gt; Per the best practices guide, "It is important to avoid configuring a dynamic&amp;nbsp; interface in the same sub network as a server that has to be reachable&amp;nbsp; by the controller CPU, for example a RADIUS server, as it might cause&amp;nbsp; asymmetric routing issues."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH,&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2011 21:25:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735826#M37508</guid>
      <dc:creator>Stephen Rodriguez</dc:creator>
      <dc:date>2011-09-14T21:25:54Z</dc:date>
    </item>
    <item>
      <title>Wism2 SNMP Authentication Failure</title>
      <link>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735827#M37509</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;&amp;gt;by default the WLC has issues with responding to requests from the wire, for a subnet that it is configured to use. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OK - that could be it.&lt;/P&gt;&lt;P&gt;I tried it via a machine on a subnet not served up as a dynamic interface, and it worked fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Sep 2011 21:33:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/wism2-snmp-authentication-failure/m-p/1735827#M37509</guid>
      <dc:creator>mages_mark</dc:creator>
      <dc:date>2011-09-14T21:33:52Z</dc:date>
    </item>
  </channel>
</rss>

