<?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 Controller SNMP management in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/controller-snmp-management/m-p/2256418#M37463</link>
    <description>&lt;P&gt;We faced one recent issue with WLC configuration behavior and explaining our observation and workaround we did. If there is an alternate better approach, please suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Requirement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Requirement is to manage the WLC (5508 with 7.4 code) using two SNMP managers in different locations. Also these two Servers should use the same community string to manage WLC.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Observation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We were able to configure the SNMP community string for one server IP (to allow access) through GUI&lt;/LI&gt;&lt;LI&gt;While trying to add another Server – IP with same community string – it didn’t allow &lt;/LI&gt;&lt;LI&gt;As per the configuration guide, Controller can use only one IP address range to manage SNMP community. &lt;/LI&gt;&lt;LI&gt;So we cannot configure the same community string to allow only two different server IP addresses&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: .25in;"&gt;Configuration reference&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: .25in;"&gt;&lt;A href="http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_0111.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_0111.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We currently configured the major subnet ( 10.x / 8 - two match both server addresses) and it works fine&lt;/LI&gt;&lt;LI&gt;Also when we tried&amp;nbsp; 0.0.0.0 / 0.0.0.0 , it didn’t work (SNMP was failing)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this creates a security issue wherein anybody can poll the WLC. Please suggest if something else can be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Guru&lt;/P&gt;</description>
    <pubDate>Sun, 04 Jul 2021 07:12:45 GMT</pubDate>
    <dc:creator>gururajan</dc:creator>
    <dc:date>2021-07-04T07:12:45Z</dc:date>
    <item>
      <title>Controller SNMP management</title>
      <link>https://community.cisco.com/t5/wireless/controller-snmp-management/m-p/2256418#M37463</link>
      <description>&lt;P&gt;We faced one recent issue with WLC configuration behavior and explaining our observation and workaround we did. If there is an alternate better approach, please suggest.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Requirement&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Requirement is to manage the WLC (5508 with 7.4 code) using two SNMP managers in different locations. Also these two Servers should use the same community string to manage WLC.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Observation&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We were able to configure the SNMP community string for one server IP (to allow access) through GUI&lt;/LI&gt;&lt;LI&gt;While trying to add another Server – IP with same community string – it didn’t allow &lt;/LI&gt;&lt;LI&gt;As per the configuration guide, Controller can use only one IP address range to manage SNMP community. &lt;/LI&gt;&lt;LI&gt;So we cannot configure the same community string to allow only two different server IP addresses&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: .25in;"&gt;Configuration reference&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P style="margin-left: .25in;"&gt;&lt;A href="http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_0111.html" target="_blank"&gt;http://www.cisco.com/en/US/docs/wireless/controller/7.4/configuration/guides/consolidated/b_cg74_CONSOLIDATED_chapter_0111.html&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;We currently configured the major subnet ( 10.x / 8 - two match both server addresses) and it works fine&lt;/LI&gt;&lt;LI&gt;Also when we tried&amp;nbsp; 0.0.0.0 / 0.0.0.0 , it didn’t work (SNMP was failing)&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;But this creates a security issue wherein anybody can poll the WLC. Please suggest if something else can be done.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Guru&lt;/P&gt;</description>
      <pubDate>Sun, 04 Jul 2021 07:12:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-snmp-management/m-p/2256418#M37463</guid>
      <dc:creator>gururajan</dc:creator>
      <dc:date>2021-07-04T07:12:45Z</dc:date>
    </item>
    <item>
      <title>Controller SNMP management</title>
      <link>https://community.cisco.com/t5/wireless/controller-snmp-management/m-p/2256419#M37464</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This is not paossible.&amp;nbsp; You would need to have two different community strings in order to not get an error.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks, &lt;BR /&gt; &lt;BR /&gt;Scott &lt;BR /&gt; &lt;BR /&gt;Help out other by using the rating system and marking answered questions as "Answered"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 11 Jun 2013 12:37:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/controller-snmp-management/m-p/2256419#M37464</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2013-06-11T12:37:32Z</dc:date>
    </item>
  </channel>
</rss>

