<?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 XIQ Supplemental CLI for EXOS Sharing Group Uplink Config in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/xiq-supplemental-cli-for-exos-sharing-group-uplink-config/m-p/72167#M18948</link>
    <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have a few X450 G2 switches already in production as IDF switches with sharing groups configured for the up-links back to the core MLAG pair. Now I need to get these IDF switches on-boarded for management in XIQ. It does not appear there is any ability read my existing config into XIQ, so I will need to recreate them in the XIQ GUI. The problem I am running into is that there does not appear to be a way to configure sharing groups in XIQ, so when I try to push the config it errors out because XIQ is trying to configure sharing group members instead of the master port. I am wondering about using the Supplemental CLI feature in XIQ to get around this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is what I have in mind:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The IDF switches presently each have ports 50 and 51 configured as a sharing group connecting back to the MLAG core.&lt;/P&gt;&lt;P&gt;Step-1: Remove port 51 from the sharing group on the production IDF switch and disable port 51 to avoid any chance of a loop via the CLI. This should allow XIQ GUI config to push to both of these ports without a fatal exception.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step-2a: Configure my XIQ switch template to configure port 50 as a trunk port with the same vlans etc just as it is configured currently. XIQ will also insist on pushing something to port 51, so I will let it configure it as a generic access port and leave it disabled. This will just get wiped out when I add the port back to the sharing group later.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step-2b: Include Supplemental CLI commands in the template to configure the sharing group uplink as it was before Step-1 by adding port 51 back to the sharing group and enabling it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step-3: Cross fingers and push the config?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Does this seem worth a shot?&lt;/LI&gt;	&lt;LI&gt;Anyone know how XIQ handles existing config on a switch that it does not have hooks for in the GUI? When I played around pushing config to some lab switches it didn’t seem to totally wipe out the existing config.. my default route, sshd, sntp etc all stayed iirc. In this case I am curious if port 50 will still be a configured as the master of a 1-member sharing group after I push config.&lt;/LI&gt;	&lt;LI&gt;Will I be able to recover with a scheduled reboot if this goes sideways? Has anyone tried scheduling a reboot then pushing config from XIQ. I am guessing it saves right away, but it would be nice if there was a window where a simple reboot would revert changes.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry this got to be a bit long!&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
    <pubDate>Thu, 14 Jan 2021 13:43:51 GMT</pubDate>
    <dc:creator>David_Nelson</dc:creator>
    <dc:date>2021-01-14T13:43:51Z</dc:date>
    <item>
      <title>XIQ Supplemental CLI for EXOS Sharing Group Uplink Config</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/xiq-supplemental-cli-for-exos-sharing-group-uplink-config/m-p/72167#M18948</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;I have a few X450 G2 switches already in production as IDF switches with sharing groups configured for the up-links back to the core MLAG pair. Now I need to get these IDF switches on-boarded for management in XIQ. It does not appear there is any ability read my existing config into XIQ, so I will need to recreate them in the XIQ GUI. The problem I am running into is that there does not appear to be a way to configure sharing groups in XIQ, so when I try to push the config it errors out because XIQ is trying to configure sharing group members instead of the master port. I am wondering about using the Supplemental CLI feature in XIQ to get around this.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This is what I have in mind:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The IDF switches presently each have ports 50 and 51 configured as a sharing group connecting back to the MLAG core.&lt;/P&gt;&lt;P&gt;Step-1: Remove port 51 from the sharing group on the production IDF switch and disable port 51 to avoid any chance of a loop via the CLI. This should allow XIQ GUI config to push to both of these ports without a fatal exception.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step-2a: Configure my XIQ switch template to configure port 50 as a trunk port with the same vlans etc just as it is configured currently. XIQ will also insist on pushing something to port 51, so I will let it configure it as a generic access port and leave it disabled. This will just get wiped out when I add the port back to the sharing group later.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step-2b: Include Supplemental CLI commands in the template to configure the sharing group uplink as it was before Step-1 by adding port 51 back to the sharing group and enabling it.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Step-3: Cross fingers and push the config?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Questions:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Does this seem worth a shot?&lt;/LI&gt;	&lt;LI&gt;Anyone know how XIQ handles existing config on a switch that it does not have hooks for in the GUI? When I played around pushing config to some lab switches it didn’t seem to totally wipe out the existing config.. my default route, sshd, sntp etc all stayed iirc. In this case I am curious if port 50 will still be a configured as the master of a 1-member sharing group after I push config.&lt;/LI&gt;	&lt;LI&gt;Will I be able to recover with a scheduled reboot if this goes sideways? Has anyone tried scheduling a reboot then pushing config from XIQ. I am guessing it saves right away, but it would be nice if there was a window where a simple reboot would revert changes.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Sorry this got to be a bit long!&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 14 Jan 2021 13:43:51 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/xiq-supplemental-cli-for-exos-sharing-group-uplink-config/m-p/72167#M18948</guid>
      <dc:creator>David_Nelson</dc:creator>
      <dc:date>2021-01-14T13:43:51Z</dc:date>
    </item>
  </channel>
</rss>

