Extreme Networks VCS Fabric Upgrade Multi-Version Upgrade Methodology
The VDX's has the ability to download its configuration from the Principal switch when that switch is replaced or has its configuration defaulted before being re-introduced into the fabric. The Multi-Version Upgrade methodology was developed around this specific capability.
More specifically, the Multi-Version Upgrade Methodology (MV) is where a temporary Principal switch is upgraded, one version at a time, from its initial version to its target version and the rest of the fabric is upgraded, from its initial version to its target version in one pass using the "firmware download default-config" command. The use of the default-config option triggers the VDXs to download their configurations from the Principal switch.
The temporary Principal switch can be an existing leaf switch or an additional switch which is temporarily added to the fabric.
Table C. Show the timing for a three version upgrade for the Figure A Fabric using the Multi-Version Methodology with the "Odd/Even" best practice.
|1||Temporary Principle Switch||0:30|
|2||Temporary Principle Switch||0:30|
|3||Temporary Principle Switch||0:30|
In this example the Multi-Version Upgrade Methodology reduces the upgrade time for the six-node fabric by two hours and 15 minutes. Table D shows the time savings per number of versions required for the upgrade.
The table indicates that there can be a significant savings can be realized when a large number of versions need to be applied during a maintenance window.Click on the following link for complete details. NOS Multi-Version White Paper