<?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: autoexec.xsf in ExtremeSwitching (EXOS/Switch Engine)</title>
    <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65259#M18231</link>
    <description>Hi Arjumand,&lt;BR /&gt;
&lt;BR /&gt;
I think you'd rather like 'Autoconfigure' script instead.&lt;BR /&gt;
Put that above to default.xsf and you're good to go.&lt;BR /&gt;
Please check EXOS User Guide on page 1600:&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;Autoconfigure:&lt;BR /&gt;
Configuration commands placed in the default.xsf file are executed by the switch as it comes up and is&lt;BR /&gt;
unable to find its usual configuration file or if the switch is unconfigured or if the configuration file&lt;BR /&gt;
cannot be determined due to a corrupt NVRAM.&lt;BR /&gt;
This returns the switch to some basic configuration. When default.xsf is executed, the show switch&lt;BR /&gt;
command shows default.xsf as the booted configuration file.&lt;BR /&gt;
The default.xsf file can have any CLI commands as long as they are all executed within 500 seconds.&lt;BR /&gt;
The script is aborted when the commands are not executed within that time. When the file is loaded,&lt;BR /&gt;
the results can be seen by executing the show script output default command.&lt;BR /&gt;
Autoexecute:&lt;BR /&gt;
Configuration commands placed in the autoexec.xsf file are executed after a switch loads its&lt;BR /&gt;
configuration.&lt;BR /&gt;
The file is not executed when a default.xsf file has been executed. Use the file to execute commands&lt;BR /&gt;
after a switch is up and running and also to revert changes made to the configuration by UPM scripts&lt;BR /&gt;
that run persistent commands. The commands must be executed within 500 seconds or the script&lt;BR /&gt;
execution is aborted.&lt;BR /&gt;
When an autoexec.xsf file is executed. the results can be seen by executing the show script&lt;BR /&gt;
output autoexec command.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps,&lt;BR /&gt;
Tomasz</description>
    <pubDate>Mon, 03 Dec 2018 07:41:24 GMT</pubDate>
    <dc:creator>Tomasz</dc:creator>
    <dc:date>2018-12-03T07:41:24Z</dc:date>
    <item>
      <title>autoexec.xsf</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65258#M18230</link>
      <description>Hello, what parameters should i put in the .xsf auto execution script so that the initial configuration can be retrieved. &lt;BR /&gt;
for instance i have all the basic connectivity already in place and someone accidentally uses &lt;BR /&gt;
unconfig switch all, and reboots the switch..&lt;BR /&gt;
&lt;BR /&gt;
can there be a autoexec.xsf file script that will at least install basic config like assign IP address to default vlan add and delete ports etc, and will not go to initial setup wizard?&lt;BR /&gt;
&lt;BR /&gt;
i tried to add basic commands in the .xsf file but after doing unconfig switch all and reboot, that xsf will not load the configuration mentioned in the xsf file rather the switch will start initial configuration wizard.&lt;BR /&gt;
&lt;BR /&gt;
kindly if someone can shed light on what needs to be added in order for my xsf start kicking in on the reboot.&lt;BR /&gt;
&lt;BR /&gt;
 xsf config contains&lt;BR /&gt;
&lt;BR /&gt;
conf vlan default ipaddress 10.10.10.200/24&lt;BR /&gt;
conf vlan default add ports 1 tagged&lt;BR /&gt;
conf vlan default add ports 23 tagged&lt;BR /&gt;
conf vlan default del ports 2-22&lt;BR /&gt;
create vlan data 100&lt;BR /&gt;
conf vlan data ipaddress 10.20.1.200/24&lt;BR /&gt;
conf vlan data add ports 1,23 tagged&lt;BR /&gt;
conf vlan data add ports 2-22&lt;BR /&gt;
ena ip-forwarding&lt;BR /&gt;
&lt;BR /&gt;
i need above config to be maintained if someone accidentally erases all the config and reboots</description>
      <pubDate>Sun, 02 Dec 2018 20:05:44 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65258#M18230</guid>
      <dc:creator>Arjumand</dc:creator>
      <dc:date>2018-12-02T20:05:44Z</dc:date>
    </item>
    <item>
      <title>Re: autoexec.xsf</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65259#M18231</link>
      <description>Hi Arjumand,&lt;BR /&gt;
&lt;BR /&gt;
I think you'd rather like 'Autoconfigure' script instead.&lt;BR /&gt;
Put that above to default.xsf and you're good to go.&lt;BR /&gt;
Please check EXOS User Guide on page 1600:&lt;BR /&gt;
&lt;BLOCKQUOTE&gt;Autoconfigure:&lt;BR /&gt;
Configuration commands placed in the default.xsf file are executed by the switch as it comes up and is&lt;BR /&gt;
unable to find its usual configuration file or if the switch is unconfigured or if the configuration file&lt;BR /&gt;
cannot be determined due to a corrupt NVRAM.&lt;BR /&gt;
This returns the switch to some basic configuration. When default.xsf is executed, the show switch&lt;BR /&gt;
command shows default.xsf as the booted configuration file.&lt;BR /&gt;
The default.xsf file can have any CLI commands as long as they are all executed within 500 seconds.&lt;BR /&gt;
The script is aborted when the commands are not executed within that time. When the file is loaded,&lt;BR /&gt;
the results can be seen by executing the show script output default command.&lt;BR /&gt;
Autoexecute:&lt;BR /&gt;
Configuration commands placed in the autoexec.xsf file are executed after a switch loads its&lt;BR /&gt;
configuration.&lt;BR /&gt;
The file is not executed when a default.xsf file has been executed. Use the file to execute commands&lt;BR /&gt;
after a switch is up and running and also to revert changes made to the configuration by UPM scripts&lt;BR /&gt;
that run persistent commands. The commands must be executed within 500 seconds or the script&lt;BR /&gt;
execution is aborted.&lt;BR /&gt;
When an autoexec.xsf file is executed. the results can be seen by executing the show script&lt;BR /&gt;
output autoexec command.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;
&lt;BR /&gt;
Hope that helps,&lt;BR /&gt;
Tomasz</description>
      <pubDate>Mon, 03 Dec 2018 07:41:24 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65259#M18231</guid>
      <dc:creator>Tomasz</dc:creator>
      <dc:date>2018-12-03T07:41:24Z</dc:date>
    </item>
    <item>
      <title>Re: autoexec.xsf</title>
      <link>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65260#M18232</link>
      <description>If the plan is to recover from an accidental unconfig switch all, use the default.xsf: it will be executed only after a reboot in default config. Inside that file, put all the relevant commands you need.</description>
      <pubDate>Mon, 03 Dec 2018 08:08:33 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/extremeswitching-exos-switch/autoexec-xsf/m-p/65260#M18232</guid>
      <dc:creator>Stephane_Grosj1</dc:creator>
      <dc:date>2018-12-03T08:08:33Z</dc:date>
    </item>
  </channel>
</rss>

