Important
VOSS 8.2 introduced changes to Segmented Management Instance that required migration of legacy management interfaces. Before you upgrade to VOSS 8.2 or later from an earlier release, you must consider your management interface configuration and migration scenario requirements. Backup and save your configuration files off the switch before upgrading to this release.
If the switch already runs VOSS 8.2 or later, you can ignore this section.
Management interface access to the switch can be lost if you do not perform the applicable migration scenarios before upgrading to this release. Loss of management access after an upgrade can result in an automatic roll-back to the previous software version.
You must perform a manual software commit after upgrading from VOSS Release 8.1.5.0 or earlier to VOSS 8.2 or later. Management interface access is required to input the software commit CLI command within 10 minutes after the upgrade. If the time expires the system initiates an automatic roll-back to the previous release.
You must ensure the switch runs VOSS 8.1.x before you upgrade to VOSS 8.2 or later to support the migrate-to-mgmt functionality.
Note
If the network environment must migrate static IPv6 routes, the switches must run VOSS Release 8.1.2.0 or later before you upgrade to VOSS 8.2 or later.
Not all upgrade paths are validated by Extreme Networks for each new software release. To understand the validated upgrade paths, see Validated Upgrade Paths.
You must consider the following legacy management interface migration scenarios before you upgrade to VOSS 8.2 or later:
|
Mgmt Interface |
Mgmt Scenario |
Migration Description |
|---|---|---|
|
DvR leaf |
Automatic migration during upgrade. |
DvR leaf settings migrate automatically during the software upgrade process. The DvR inband-mgmt-ip CLIP automatically becomes the new Segmented Management Instance CLIP. Note:
Leaf nodes only support the management CLIP as part of the Global Routing Table (GRT). |
|
OOB |
Automatic migration during upgrade. |
Out-of-Band management settings migrate automatically during the software upgrade process. |
|
CLIP |
Specify a Circuitless IP (CLIP) interface for migration to management interface before you upgrade. |
You can use this interface type for CLIP management network routing in a Fabric network or Layer 3 routing network. Use the migrate-to-mgmt command in the Loopback Interface Configuration mode of the CLI to specify the CLIP interface for management before starting the software upgrade process. You can designate the IP Shortcut CLIP to migrate to the Management Instance CLIP. After the upgrade, the IS-IS source IP address moves to the Management Instance CLIP. You must configure a new GRT CLIP using a different IP address and assign that as the new IS-IS source IP. Save the configuration before upgrading. Important:
Ensure that the management CLIP IP address does not fall into the range of a configured VLAN IP address range as this is not allowed. |
|
VLAN |
Specify a VLAN interface for migration to management interface before you upgrade. |
You can use this interface type for management of Layer 2 switches or for Zero-Touch onboarding of newly deployed devices. Use the CLIP Management Instance for routed management. Use the migrate-to-mgmt command in the VLAN Interface Configuration mode of the CLI to specify the VLAN interface for management before starting the software upgrade process. Important:
Choose a VLAN that does not have an IP interface on it. The upgrade process removes the IP configuration and network connectivity will be impacted. If the switch has more than one IP address on more than one VLAN before the upgrade, the switch is probably a Layer 3 BEB and should be managed using a CLIP Management Instance instead. Save the configuration before upgrading. The VLAN Management Instance does not route to or from the GRT. Bridged management traffic must ingress on the VLAN or I-SID. |
For more information about Segmented Management Instance migration, see VOSS User Guide.