<?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 you can try adding a static in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937920#M5801</link>
    <description>&lt;P&gt;you can try adding a static ARP entry on the gateway tot this CIMC subnet, to attach an ip-address to the MAC address of the CIMC.&lt;BR /&gt;Maybe this allows you to access the CIMC for configuration, then remove the static arp.&lt;/P&gt;</description>
    <pubDate>Thu, 23 Feb 2017 12:46:54 GMT</pubDate>
    <dc:creator>pieterh</dc:creator>
    <dc:date>2017-02-23T12:46:54Z</dc:date>
    <item>
      <title>CIMC configuration and access on standby WLC 5520</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937915#M5796</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have configured two 5520 WLC one as primary and one has SSO HA which is working fine.&lt;/P&gt;
&lt;P&gt;However I want to configure the CIMC on both units but the controller command line doesnt let me define the standby CIMC IP Address, infact the single command is syned to the standby WLC.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I applied the&amp;nbsp;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;B class="cCN_CmdName"&gt;imm address&lt;/B&gt;&lt;SPAN&gt; &lt;/SPAN&gt;&lt;EM class="cArgument"&gt;ip-addr net-mask gateway-ip-addr&lt;/EM&gt;&lt;SPAN&gt;.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;commands this works I can web to that IP address but how do I get to the standby WLC's CIMC??&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;I am remote to the units so right now my only option is controller commandline.&amp;nbsp;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have been using these resources&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/5500/5520/installation/guide/wlc-ig-5520/overview.html#pgfId-1281012" target="_blank"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/5500/5520/installation/guide/wlc-ig-5520/overview.html#pgfId-1281012&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/5520-WLC-DG/b_Cisco-5520-WLC-deployment-guide.html" target="_blank"&gt;http://www.cisco.com/c/en/us/td/docs/wireless/controller/technotes/8-1/5520-WLC-DG/b_Cisco-5520-WLC-deployment-guide.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for your help.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 12:27:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937915#M5796</guid>
      <dc:creator>c-davies</dc:creator>
      <dc:date>2021-07-05T12:27:19Z</dc:date>
    </item>
    <item>
      <title>I would simply leave CIMC to</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937916#M5797</link>
      <description>&lt;P&gt;I would simply leave CIMC to be DHCP and reserve IP address in DHCP server for that MAC address.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Wed, 20 Jul 2016 20:46:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937916#M5797</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2016-07-20T20:46:35Z</dc:date>
    </item>
    <item>
      <title>Thanks, its an option but my</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937917#M5798</link>
      <description>&lt;P&gt;Thanks, its an option but my customer would prefer statically fixing the IP Address, they don't want to have to create a DHCP pool for just 2 devices. Mind you if that's how everyone else does it... I guess a dhcp server could be configured on the switch..&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2016 09:07:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937917#M5798</guid>
      <dc:creator>c-davies</dc:creator>
      <dc:date>2016-07-21T09:07:27Z</dc:date>
    </item>
    <item>
      <title>Otherwise you can do this</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937918#M5799</link>
      <description>&lt;P&gt;Otherwise you can do this when these devices initially configured (CIMC setup menu). Since now this is in production with HA, not sure whether you can do it without breaking HA.&lt;/P&gt;
&lt;P&gt;DHCP option should be the simple fix.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;
&lt;P&gt;Rasika&lt;/P&gt;
&lt;P&gt;*** Pls rate all useful responses ***&lt;/P&gt;</description>
      <pubDate>Thu, 21 Jul 2016 22:26:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937918#M5799</guid>
      <dc:creator>Rasika Nayanajith</dc:creator>
      <dc:date>2016-07-21T22:26:50Z</dc:date>
    </item>
    <item>
      <title>I don't know if this is</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937919#M5800</link>
      <description>&lt;P&gt;I don't know if this is supported, but you can always boot the WLC with an attached serial console. During boot - before the WLC booting process, a prompt will come up to press F8 in order to configure the CIMC (as for all UCS based servers).&lt;/P&gt;
&lt;P&gt;In the following text based UI, you can edit the IP address parameters.&lt;/P&gt;
&lt;P&gt;CAUTION:&lt;/P&gt;
&lt;DIV&gt;
&lt;UL&gt;
&lt;LI class="pBu1_Bullet1"&gt;Do not change the NIC mode to shared. It should be in dedicated mode&lt;/LI&gt;
&lt;LI class="pBu1_Bullet1"&gt;Do not change the FlexFlash Mode&lt;/LI&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;A name="pgfId-1303426"&gt;&lt;/A&gt;Do not change the SSD/Virtual disk settings&lt;/LI&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;A name="pgfId-1303427"&gt;&lt;/A&gt;BIOS parameters should not be changed&lt;/LI&gt;
&lt;/UL&gt;
&lt;/DIV&gt;
&lt;DIV&gt;
&lt;H3 class="p_H_Head2"&gt;&lt;A name="pgfId-1303478"&gt;&lt;/A&gt;&lt;A name="Expectations_when_logged_in_via_CIMC"&gt;&lt;/A&gt;Expectations when logged in via CIMC&lt;/H3&gt;
&lt;UL&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;A name="pgfId-1309329"&gt;&lt;/A&gt;FlexFlash is configured for RAID but only one flash is populated this causes CIMC to show the FlexFlash as degraded.We can safely dis-regard the FlexFlash degradation warning in our case.&lt;/LI&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;A name="pgfId-1303518"&gt;&lt;/A&gt;Expect to see only one CPU populated&lt;/LI&gt;
&lt;LI class="pBu1_Bullet1"&gt;&lt;A name="pgfId-1303510"&gt;&lt;/A&gt;Do not configure Software Raid on SSD&lt;/LI&gt;
&lt;/UL&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Just a side note - I would like to configure just SNMP (poll and trap) to the CIMC.&lt;/P&gt;
&lt;P&gt;I think/hope/guess this is a more reliable way to monitor the health status of the secondary WLC as with WLC integrated traps (like HDD failure, memory failure etc.). Hopefully, there will be a statement of Cisco at some time, that this is "officially" supported, without breaking the WLC.&lt;/P&gt;
&lt;/DIV&gt;</description>
      <pubDate>Wed, 15 Feb 2017 17:07:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937919#M5800</guid>
      <dc:creator>Johannes Luther</dc:creator>
      <dc:date>2017-02-15T17:07:25Z</dc:date>
    </item>
    <item>
      <title>you can try adding a static</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937920#M5801</link>
      <description>&lt;P&gt;you can try adding a static ARP entry on the gateway tot this CIMC subnet, to attach an ip-address to the MAC address of the CIMC.&lt;BR /&gt;Maybe this allows you to access the CIMC for configuration, then remove the static arp.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Feb 2017 12:46:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/2937920#M5801</guid>
      <dc:creator>pieterh</dc:creator>
      <dc:date>2017-02-23T12:46:54Z</dc:date>
    </item>
    <item>
      <title>Re: CIMC configuration and access on standby WLC 5520</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3175088#M5802</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;i just had exactly the same issue. Two WLC 5520 in HA at a remote site. And i'm off the opinion that this behavior of syncing the CIMC ip address to both machines when HA is enabled is some kind of design flaw. The command should not sync to both machines and there should be some kind of "imm peer address" command to be able to set the IP address of the secondary machine as well.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But still I was able to solve this issue without any interruption:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;Login to WLC CLI using SSH to Management IP Address.&lt;/LI&gt;&lt;LI&gt;Issue "show inventory" and take a note of the serial number.&lt;/LI&gt;&lt;LI&gt;Issue "show redundancy summary" and make sure the state is "STANBY HOT" and BulkSync Status is "Complete" and your connected to Primary Unit.&lt;/LI&gt;&lt;LI&gt;Issue "imm address&amp;nbsp;&amp;lt;ipaddr&lt;STRONG&gt;1&lt;/STRONG&gt;&amp;gt;&amp;nbsp;&amp;lt;netmask&amp;gt;&amp;nbsp;&amp;lt;gateway&amp;gt;" and "imm dhcp disable" as advised. IP Address will be synced to both WLC-CIMC, as far as i experienced (duplicate IP address...).&lt;/LI&gt;&lt;LI&gt;Issue "redundancy force-switchover". The primary unit will reboot and secondary unit will take its place immediately.&lt;/LI&gt;&lt;LI&gt;You will probably lose SSH connection. If so, reconnect to WLC CLI&amp;nbsp;&lt;SPAN&gt;using SSH to Management IP Address.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Issue "show inventory" and take a note of the serial number.&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Issue "show redundancy summary" and you will notice, that the state is unknown and you are connected to the secondary unit, which is currently active.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;Issue "imm address&amp;nbsp;&amp;lt;ipaddr&lt;STRONG&gt;2&lt;/STRONG&gt;&amp;gt;&amp;nbsp;&amp;lt;netmask&amp;gt;&amp;nbsp;&amp;lt;gateway&amp;gt;" and "imm dhcp disable" as advised. This time the IP address will only be synced to the secondary unit, since the primary unit is still rebooting.&lt;/LI&gt;&lt;LI&gt;Now connect to both CIMC IP addresses using HTTPS in a browser and compare before noted serial numbers as verification. You now should have both CIMC interfaces configured correctly. Yay! &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;Back to WLC CLI. We have to cleanup now:&amp;nbsp;&lt;SPAN&gt;Issue "&lt;/SPAN&gt;&lt;SPAN&gt;show redundancy summary" and make sure the primary unit is back up and state is "STANDBY HOT" again and&amp;nbsp;BulkSync Status is "Complete". Notice the current active uni is still the secondary unit.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;Issue "redundancy force-switchover" again for the primary unit to become the active unit again.&lt;/SPAN&gt;&lt;/LI&gt;&lt;LI&gt;&lt;SPAN&gt;After a couple of minutes issue "show redundancy summary"to make sure the secondary unit is back up again (State is "STANBY HOT" and&amp;nbsp;BulkSync Status is "Complete").&lt;/SPAN&gt;&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;&lt;SPAN&gt;I hope this will work for you. I had no problems and experienced no outtages or any disruptive behaviors at all.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Disclaimer: I still don't take any responsibilities in case anything goes wrong and i don't guarantee the 100% correctness of this guide. When in productive environment, always do this kind of work in maintenance windows.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Best Regards!&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 24 Aug 2017 08:44:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3175088#M5802</guid>
      <dc:creator>KAF</dc:creator>
      <dc:date>2017-08-24T08:44:59Z</dc:date>
    </item>
    <item>
      <title>Re: CIMC configuration and access on standby WLC 5520</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3767971#M5803</link>
      <description>&lt;P&gt;This method isn't working on my current setup. I have two 5520 wlc with HA, and I have configured static IP on Primary CIMC port, and I reloaded the primary wlc, then I logged into secondary wlc (running as primary), surprisedly IMM also replicated to secondary wlc (which means I saw static IP on current wlc, which I configured on primary wlc).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;is there any other process available except shutting down one wlc and configure the second wlc CIMC port ?&lt;/P&gt;</description>
      <pubDate>Fri, 21 Dec 2018 16:55:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3767971#M5803</guid>
      <dc:creator>kumarpadala</dc:creator>
      <dc:date>2018-12-21T16:55:28Z</dc:date>
    </item>
    <item>
      <title>Re: CIMC configuration and access on standby WLC 5520</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3769486#M5804</link>
      <description>&lt;P&gt;I recently encountered this issue and this is the process TAC suggested on my 8540 HA pair:&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;So to proceed with CIMC configuration on the standby you need to break HA first.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;When the Controller is in HA pair, you can try to go for CIMC configuration by doing failovers but that does not guarantee that disruption won’t be caused.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;I prefer to disable HA on secondary so that your primary is up and running and once CIMC configuration is done, you can enable HA again on standby so that means you will only end up rebooting secondary controller.&lt;/P&gt;</description>
      <pubDate>Thu, 27 Dec 2018 13:58:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3769486#M5804</guid>
      <dc:creator>Joel Frye</dc:creator>
      <dc:date>2018-12-27T13:58:55Z</dc:date>
    </item>
    <item>
      <title>Re: CIMC configuration and access on standby WLC 5520</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3923632#M5805</link>
      <description>&lt;P&gt;It is a known bug&amp;nbsp;&lt;SPAN&gt;CSCvf57867:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf57867" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvf57867&lt;/A&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt;&lt;BR /&gt;have two controllers in HA (AP-SSO) try to configure IMM for active and standby. However, only a single IP gets synced to both active and standby.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 12 Sep 2019 23:38:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/3923632#M5805</guid>
      <dc:creator>tadnan001</dc:creator>
      <dc:date>2019-09-12T23:38:49Z</dc:date>
    </item>
    <item>
      <title>Re: CIMC configuration and access on standby WLC 5520</title>
      <link>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/4109248#M5806</link>
      <description>&lt;P&gt;It's very easy to do so!&amp;nbsp;I've got 5520 8.2 HA pair and configuration of CIMC by default (DHCP+0.0.0.0+default login/password) and have the same problem.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So before - you need access to router when the IP interface to CIMC will be used, and a switch where physically connected M ports to network or you can ask person responsible for this devices to help you.&lt;/P&gt;&lt;P&gt;1. Shutdown port on switch to standby WLC CIMC M port;&lt;/P&gt;&lt;P&gt;2. Configure CIMC by imm commands (&lt;A href="https://www.cisco.com/c/en/us/support/docs/wireless/5520-wireless-controller/212170-Console-access-to-5520-8540-WLC-via-CIMC.html" target="_blank" rel="noopener"&gt;https://www.cisco.com/c/en/us/support/docs/wireless/5520-wireless-controller/212170-Console-access-to-5520-8540-WLC-via-CIMC.html&lt;/A&gt;);&lt;/P&gt;&lt;P&gt;3. Access CIMC from HTTP, note serial or simple write the server Description;&lt;/P&gt;&lt;P&gt;4. Shutdown port on switch to active WLC CIMC M port, clear arp to configured IP on router and up the standby CIMC M port back;&lt;/P&gt;&lt;P&gt;5. Access standby CIMC from HTTP from same IP address and change it to whatever you want.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;So this method is better because you don't need to force-switchover anything and no risk at all on interruption to production traffic.&lt;/P&gt;</description>
      <pubDate>Thu, 25 Jun 2020 12:01:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/cimc-configuration-and-access-on-standby-wlc-5520/m-p/4109248#M5806</guid>
      <dc:creator>CfYz</dc:creator>
      <dc:date>2020-06-25T12:01:49Z</dc:date>
    </item>
  </channel>
</rss>

