<?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 Upgrading DFE to v6.01.01.0020+ Deletes Part of Routing Configuration in FAQs</title>
    <link>https://community.extremenetworks.com/t5/faqs/upgrading-dfe-to-v6-01-01-0020-deletes-part-of-routing/m-p/40566#M1</link>
    <description>Article ID: 9964 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
DFE, firmware 6.x and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured one or more router instances using firmware through 5.x.&lt;BR /&gt;
Upgraded to firmware 6.x or higher. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Lost some router configurations. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
Using firmware prior to 6.01.01.0020, for local router redundancy within the DFE system it is necessary to configure two local router instances, with each instance corresponding to a unique slot number. For instance, a defined 'router 1' operates out of the slot 1 blade (master of the slot 1 routing task), minimally requiring that blade to be operational in order for the router instance to be "up". &lt;BR /&gt;
&lt;BR /&gt;
Firmware 6.01.01.0020 and higher automatically provides router redundancy without having to configure a second router instance. As a result it does not support the configuration of two routers; so if a router is upgraded from a prior firmware that has multiple routers configured, only the lowest router instance will be maintained unchanged after the upgrade. This means that all interfaces and other router configuration on higher router instances will be deleted. &lt;BR /&gt;
&lt;BR /&gt;
Non-symmertical router configurations are at high risk for failure as half the interfaces will be eliminated if not reconfigured properly as part of the upgrade process. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD) &lt;BR /&gt;
&lt;BR /&gt;
Workaround:&lt;BR /&gt;
Prior to such an upgrade, the configuration should be adjusted (VRRP configurations removed, etc) so that it only defines one router with the desired characteristics. If there is only one instance, no pre-configuration is needed. &lt;BR /&gt;
&lt;BR /&gt;
It is always prudent practice to perform a 'show config outfile slotx/config.cfg' to backup the configuration to flash. This allows one to review the older configuration via the 'show file' command, or to re-launch via the 'configure slotx/config.cfg' command (&lt;A href="http://bit.ly/1h7Itjx" target="_blank" rel="nofollow noreferrer noopener"&gt;5035&lt;/A&gt;). A saved 5.x configuration should only be re-launched using 5.x firmware, and a saved 6.x configuration should only be re-launched using 6.x firmware.</description>
    <pubDate>Sat, 23 Nov 2013 04:52:00 GMT</pubDate>
    <dc:creator>FAQ_User</dc:creator>
    <dc:date>2013-11-23T04:52:00Z</dc:date>
    <item>
      <title>Upgrading DFE to v6.01.01.0020+ Deletes Part of Routing Configuration</title>
      <link>https://community.extremenetworks.com/t5/faqs/upgrading-dfe-to-v6-01-01-0020-deletes-part-of-routing/m-p/40566#M1</link>
      <description>Article ID: 9964 &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Products&lt;/B&gt;&lt;BR /&gt;
DFE, firmware 6.x and higher &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Changes&lt;/B&gt;&lt;BR /&gt;
Configured one or more router instances using firmware through 5.x.&lt;BR /&gt;
Upgraded to firmware 6.x or higher. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Symptoms&lt;/B&gt;&lt;BR /&gt;
Lost some router configurations. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Cause&lt;/B&gt;&lt;BR /&gt;
Using firmware prior to 6.01.01.0020, for local router redundancy within the DFE system it is necessary to configure two local router instances, with each instance corresponding to a unique slot number. For instance, a defined 'router 1' operates out of the slot 1 blade (master of the slot 1 routing task), minimally requiring that blade to be operational in order for the router instance to be "up". &lt;BR /&gt;
&lt;BR /&gt;
Firmware 6.01.01.0020 and higher automatically provides router redundancy without having to configure a second router instance. As a result it does not support the configuration of two routers; so if a router is upgraded from a prior firmware that has multiple routers configured, only the lowest router instance will be maintained unchanged after the upgrade. This means that all interfaces and other router configuration on higher router instances will be deleted. &lt;BR /&gt;
&lt;BR /&gt;
Non-symmertical router configurations are at high risk for failure as half the interfaces will be eliminated if not reconfigured properly as part of the upgrade process. &lt;BR /&gt;
&lt;BR /&gt;
&lt;B&gt;Solution/Workaround&lt;/B&gt;&lt;BR /&gt;
Functions as Designed (FAD) &lt;BR /&gt;
&lt;BR /&gt;
Workaround:&lt;BR /&gt;
Prior to such an upgrade, the configuration should be adjusted (VRRP configurations removed, etc) so that it only defines one router with the desired characteristics. If there is only one instance, no pre-configuration is needed. &lt;BR /&gt;
&lt;BR /&gt;
It is always prudent practice to perform a 'show config outfile slotx/config.cfg' to backup the configuration to flash. This allows one to review the older configuration via the 'show file' command, or to re-launch via the 'configure slotx/config.cfg' command (&lt;A href="http://bit.ly/1h7Itjx" target="_blank" rel="nofollow noreferrer noopener"&gt;5035&lt;/A&gt;). A saved 5.x configuration should only be re-launched using 5.x firmware, and a saved 6.x configuration should only be re-launched using 6.x firmware.</description>
      <pubDate>Sat, 23 Nov 2013 04:52:00 GMT</pubDate>
      <guid>https://community.extremenetworks.com/t5/faqs/upgrading-dfe-to-v6-01-01-0020-deletes-part-of-routing/m-p/40566#M1</guid>
      <dc:creator>FAQ_User</dc:creator>
      <dc:date>2013-11-23T04:52:00Z</dc:date>
    </item>
  </channel>
</rss>

