<?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 Renumbering a VCS Logical Chassis Cluster in Data Center (SLX)</title>
    <link>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62321#M207</link>
    <description>I have an 8-switch VCS cluster (6740x2, 6710x6, NOS 4.1, Logical Chassis, no vcs virtual ip set) which needs renumbering onto a new management network (resulting from merger and reorganization).&lt;BR /&gt;
&lt;BR /&gt;
What are the implications for doing this while the devices are in production? Can it be done at all without flattening and rebuilding the configuration?</description>
    <pubDate>Tue, 04 Jun 2019 08:33:55 GMT</pubDate>
    <dc:creator>dvc</dc:creator>
    <dc:date>2019-06-04T08:33:55Z</dc:date>
    <item>
      <title>Renumbering a VCS Logical Chassis Cluster</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62321#M207</link>
      <description>I have an 8-switch VCS cluster (6740x2, 6710x6, NOS 4.1, Logical Chassis, no vcs virtual ip set) which needs renumbering onto a new management network (resulting from merger and reorganization).&lt;BR /&gt;
&lt;BR /&gt;
What are the implications for doing this while the devices are in production? Can it be done at all without flattening and rebuilding the configuration?</description>
      <pubDate>Tue, 04 Jun 2019 08:33:55 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62321#M207</guid>
      <dc:creator>dvc</dc:creator>
      <dc:date>2019-06-04T08:33:55Z</dc:date>
    </item>
    <item>
      <title>Re: Renumbering a VCS Logical Chassis Cluster</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62322#M208</link>
      <description>No, this can not be done without impacting traffic.&lt;BR /&gt;
&lt;BR /&gt;
Changing the RB ID will default the configuration of the switch. As a result, the configuration will be lost which will cause traffic disruption and the switch will be added as a new switch on the VCS.</description>
      <pubDate>Tue, 04 Jun 2019 09:24:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62322#M208</guid>
      <dc:creator>Truyen_Phan</dc:creator>
      <dc:date>2019-06-04T09:24:00Z</dc:date>
    </item>
    <item>
      <title>Re: Renumbering a VCS Logical Chassis Cluster</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62323#M209</link>
      <description>Don't want to change any of the rbridge configuration other than ip address and default gateways. No topology or rbridge-id changes.</description>
      <pubDate>Tue, 04 Jun 2019 09:33:09 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62323#M209</guid>
      <dc:creator>dvc</dc:creator>
      <dc:date>2019-06-04T09:33:09Z</dc:date>
    </item>
    <item>
      <title>Re: Renumbering a VCS Logical Chassis Cluster</title>
      <link>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62324#M210</link>
      <description>If it''s just IP address and gateway (control plane) of each switch, then there will not be any impact to the data traffic (data plane).</description>
      <pubDate>Tue, 04 Jun 2019 09:38:12 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/data-center-slx/renumbering-a-vcs-logical-chassis-cluster/m-p/62324#M210</guid>
      <dc:creator>Truyen_Phan</dc:creator>
      <dc:date>2019-06-04T09:38:12Z</dc:date>
    </item>
  </channel>
</rss>

