<?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: SD-Access FIB loopback0 change IP in Software-Defined Access (SD-Access)</title>
    <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5579648#M4520</link>
    <description>&lt;P&gt;Loopback 0 acts as the device's anchor point for routing (RLOC), its management address for network orchestration, the control plane mapping database identifier, and the anchor for the embedded WLC (eWLC) wireless management interface (WMI)&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-switch/217434-configure-an-non-sda-ewc-switch-to-onboa.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-switch/217434-configure-an-non-sda-ewc-switch-to-onboa.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;i suggest the steps as below :&lt;/P&gt;
&lt;P&gt;De-provision Wireless (you can move to different WLC controller for time being) - any way switch go down, so AP also go offline, so downtime needed.&lt;/P&gt;
&lt;P&gt;Remove Fabric Roles&amp;nbsp; and make changes , and re-provision WLC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 01 Oct 2026 07:25:51 GMT</pubDate>
    <dc:creator>balaji.bandi</dc:creator>
    <dc:date>2026-10-01T07:25:51Z</dc:date>
    <item>
      <title>SD-Access FIB loopback0 change IP</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5225890#M3750</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;
&lt;P&gt;I have a working location with single 9300X working as FIB - i.e. it runs edge, contorl, border and also embedded WLC functionality.&lt;/P&gt;
&lt;P&gt;The fabric is working good. But now I need to change the Loopback0 IP address (due to global network renumbering).&lt;/P&gt;
&lt;P&gt;Is there a safe way to change it?&lt;/P&gt;
&lt;P&gt;I mean, I can shortly remove the EN|BN|CP functionality, if needed. I just want to avoid wiping out everything and starting the discovery/fabric configuration from scratch.&lt;/P&gt;
&lt;P&gt;Any suggestion appreciated!&lt;/P&gt;
&lt;P&gt;IGOR&lt;/P&gt;</description>
      <pubDate>Mon, 18 Nov 2024 13:04:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5225890#M3750</guid>
      <dc:creator>igor-k</dc:creator>
      <dc:date>2024-11-18T13:04:43Z</dc:date>
    </item>
    <item>
      <title>Re: SD-Access FIB loopback0 change IP</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5579484#M4519</link>
      <description>&lt;P&gt;Loopback0 is the fabric RLOC — it's what the device registers with the map server and what all the LISP overlay signaling keys off, so there isn't a supported way to just renumber it in place while the fabric roles are active. Since you're on Fabric-in-a-Box with all roles on the single 9300X, the supported path is the one you suspected: remove the EN/BN/CP roles from the device in Catalyst Center first (this cleanly withdraws the LISP registrations and underlay entries), then change the Loopback0 IP, and finally re-provision the fabric roles so the new RLOC gets registered with the map server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;No need to wipe the switch — removing and re-adding the roles is enough. Just plan a maintenance window, take a config backup, and make sure no other part of the global network config references the old RLOC before you change it. Also worth confirming the exact procedure against the SD-Access deployment guide for your Catalyst Center version.&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2026 12:50:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5579484#M4519</guid>
      <dc:creator>Jhonbruce</dc:creator>
      <dc:date>2026-09-30T12:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: SD-Access FIB loopback0 change IP</title>
      <link>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5579648#M4520</link>
      <description>&lt;P&gt;Loopback 0 acts as the device's anchor point for routing (RLOC), its management address for network orchestration, the control plane mapping database identifier, and the anchor for the embedded WLC (eWLC) wireless management interface (WMI)&lt;/P&gt;
&lt;P&gt;&lt;A href="https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-switch/217434-configure-an-non-sda-ewc-switch-to-onboa.html" target="_blank"&gt;https://www.cisco.com/c/en/us/support/docs/switches/catalyst-9300-switch/217434-configure-an-non-sda-ewc-switch-to-onboa.html&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;i suggest the steps as below :&lt;/P&gt;
&lt;P&gt;De-provision Wireless (you can move to different WLC controller for time being) - any way switch go down, so AP also go offline, so downtime needed.&lt;/P&gt;
&lt;P&gt;Remove Fabric Roles&amp;nbsp; and make changes , and re-provision WLC.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Oct 2026 07:25:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/software-defined-access-sd-access/sd-access-fib-loopback0-change-ip/m-p/5579648#M4520</guid>
      <dc:creator>balaji.bandi</dc:creator>
      <dc:date>2026-10-01T07:25:51Z</dc:date>
    </item>
  </channel>
</rss>

