<?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 V400 RMA'd: Any replacement procedure? in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/v400-rma-d-any-replacement-procedure/m-p/69691#M18691</link>
    <description>&lt;P&gt;Hi guys,&lt;/P&gt;  &lt;P&gt;I have a customer running a pair of X690 as CBs&amp;nbsp;(MLAG) to 4 V400 (slots 100 to 103) (exos 22.7.1.2-patch-1-24)&lt;/P&gt;  &lt;P&gt;Unfortunately one of these V400 simply died (no power on anymore) and it was RMA'd to Extreme.&lt;/P&gt;  &lt;P&gt;Is there any procedure to replace the faulty slot 102&amp;nbsp;V400 by the new one? I don't want to connect it and create a "new slot 104", but simply replace it as "slot 103" just like we usually do with stacked switches.&lt;/P&gt;  &lt;P&gt;By the way, the V400s are connected to partitioned ports on both X690, and were deployed using the partial automation method and I haven't issued the&amp;nbsp;"disable vpex auto-configuration" (so it's on since the deployment).&lt;/P&gt;  &lt;P&gt;Any considerations???&lt;/P&gt;  &lt;P&gt;Thanks!&lt;/P&gt;</description>
    <pubDate>Thu, 18 Jun 2020 01:26:06 GMT</pubDate>
    <dc:creator>LeoP1</dc:creator>
    <dc:date>2020-06-18T01:26:06Z</dc:date>
    <item>
      <title>V400 RMA'd: Any replacement procedure?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/v400-rma-d-any-replacement-procedure/m-p/69691#M18691</link>
      <description>&lt;P&gt;Hi guys,&lt;/P&gt;  &lt;P&gt;I have a customer running a pair of X690 as CBs&amp;nbsp;(MLAG) to 4 V400 (slots 100 to 103) (exos 22.7.1.2-patch-1-24)&lt;/P&gt;  &lt;P&gt;Unfortunately one of these V400 simply died (no power on anymore) and it was RMA'd to Extreme.&lt;/P&gt;  &lt;P&gt;Is there any procedure to replace the faulty slot 102&amp;nbsp;V400 by the new one? I don't want to connect it and create a "new slot 104", but simply replace it as "slot 103" just like we usually do with stacked switches.&lt;/P&gt;  &lt;P&gt;By the way, the V400s are connected to partitioned ports on both X690, and were deployed using the partial automation method and I haven't issued the&amp;nbsp;"disable vpex auto-configuration" (so it's on since the deployment).&lt;/P&gt;  &lt;P&gt;Any considerations???&lt;/P&gt;  &lt;P&gt;Thanks!&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2020 01:26:06 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/v400-rma-d-any-replacement-procedure/m-p/69691#M18691</guid>
      <dc:creator>LeoP1</dc:creator>
      <dc:date>2020-06-18T01:26:06Z</dc:date>
    </item>
    <item>
      <title>Re: V400 RMA'd: Any replacement procedure?</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/v400-rma-d-any-replacement-procedure/m-p/69692#M18692</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;  &lt;P&gt;on the CB the following thing should be configured:&lt;BR /&gt; configure vpex ports port_list slot slot_num&lt;/P&gt;  &lt;P&gt;If this is the case I would assume that a simple replacement of the broken V400 should do the trick and the new V400 receives the slot-number that is configured.&lt;/P&gt;</description>
      <pubDate>Thu, 18 Jun 2020 14:48:18 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/v400-rma-d-any-replacement-procedure/m-p/69692#M18692</guid>
      <dc:creator>Stefan_K_</dc:creator>
      <dc:date>2020-06-18T14:48:18Z</dc:date>
    </item>
  </channel>
</rss>

