<?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 Re: 5508 WLC Service Port address update/change in Wireless</title>
    <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998764#M4691</link>
    <description>Sometimes you can get away from downtime by making the change, manually issue a force failover on the primary. When the secondary comes back up, you can then make the changes on that. Then issues another force failover. &lt;BR /&gt;</description>
    <pubDate>Sat, 14 Dec 2019 00:14:08 GMT</pubDate>
    <dc:creator>Scott Fella</dc:creator>
    <dc:date>2019-12-14T00:14:08Z</dc:date>
    <item>
      <title>5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998583#M4685</link>
      <description>&lt;P&gt;Hi all,&lt;/P&gt;&lt;P&gt;It is my guess that one can the Service Port IP address..&amp;nbsp; when ever, without causing/needing a reboot..&amp;nbsp; Yes or No?&lt;/P&gt;&lt;P&gt;I have a standalone LAB unit that I changed the SP ip on and the GUI (on mgnt ip) dropped out..&amp;nbsp; unit still pinged..&lt;/P&gt;&lt;P&gt;When I arrived on-site, the wlc was online.&amp;nbsp; I could find no log entries to validate a restart occurred.&lt;/P&gt;&lt;P&gt;I have 2 HA pairs to tweak and I was going to CLI in and issue config interface address service-port&amp;nbsp; update to each device but if they need to reboot, I will leave them disconnected&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;tia&lt;/P&gt;</description>
      <pubDate>Mon, 05 Jul 2021 18:25:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998583#M4685</guid>
      <dc:creator>David Ritter</dc:creator>
      <dc:date>2021-07-05T18:25:57Z</dc:date>
    </item>
    <item>
      <title>Re: 5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998588#M4686</link>
      <description>oh, I have changed the IP 3 times alredy without loosing GUI link. So maybe first event was a fluke..</description>
      <pubDate>Fri, 13 Dec 2019 17:19:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998588#M4686</guid>
      <dc:creator>David Ritter</dc:creator>
      <dc:date>2019-12-13T17:19:22Z</dc:date>
    </item>
    <item>
      <title>Re: 5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998639#M4687</link>
      <description>Changing that should not affect anything.  The only way it would affect anything is if that was connected to the network and was routable to the management interface. &lt;BR /&gt;</description>
      <pubDate>Fri, 13 Dec 2019 18:49:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998639#M4687</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2019-12-13T18:49:08Z</dc:date>
    </item>
    <item>
      <title>Re: 5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998650#M4688</link>
      <description>Thank you Scott,&lt;BR /&gt;But I wonder what affect the ability for the 2 segments to talk to each&lt;BR /&gt;other has on life.&lt;BR /&gt;I would think the systems would have no inherent reason to talk to it's&lt;BR /&gt;service port..&lt;BR /&gt;&lt;BR /&gt;Ok, what do you think you about making the cli adjustment to SP&lt;BR /&gt;address in an active HA pair..&lt;BR /&gt;can I do it or do I have to disable HA/sso first.&lt;BR /&gt;</description>
      <pubDate>Fri, 13 Dec 2019 19:03:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998650#M4688</guid>
      <dc:creator>David Ritter</dc:creator>
      <dc:date>2019-12-13T19:03:08Z</dc:date>
    </item>
    <item>
      <title>Re: 5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998684#M4689</link>
      <description>You can make changes with no issues. The documentation in regard to the service port will state to not have it routable with the management. This is only for OOB and should be on a segregated network if connected. &lt;BR /&gt;</description>
      <pubDate>Fri, 13 Dec 2019 20:10:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998684#M4689</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2019-12-13T20:10:08Z</dc:date>
    </item>
    <item>
      <title>Re: 5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998708#M4690</link>
      <description>&lt;P&gt;That was easy..&amp;nbsp; The HA Programmers&amp;nbsp;accounted for this need.&amp;nbsp; They forgot the occasional need to change NAT address's and we have to disable sso with a reboot...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;thank you again..&lt;/P&gt;</description>
      <pubDate>Fri, 13 Dec 2019 20:50:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998708#M4690</guid>
      <dc:creator>David Ritter</dc:creator>
      <dc:date>2019-12-13T20:50:55Z</dc:date>
    </item>
    <item>
      <title>Re: 5508 WLC Service Port address update/change</title>
      <link>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998764#M4691</link>
      <description>Sometimes you can get away from downtime by making the change, manually issue a force failover on the primary. When the secondary comes back up, you can then make the changes on that. Then issues another force failover. &lt;BR /&gt;</description>
      <pubDate>Sat, 14 Dec 2019 00:14:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/wireless/5508-wlc-service-port-address-update-change/m-p/3998764#M4691</guid>
      <dc:creator>Scott Fella</dc:creator>
      <dc:date>2019-12-14T00:14:08Z</dc:date>
    </item>
  </channel>
</rss>

