Segmented Management Instance Migration

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.

Note

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 one of the following VOSS releases before you upgrade to VOSS 8.2 or later to support the migrate-to-mgmt functionality:

VOSS 8.1.0.0 or later for switches running VOSS 8.1.x releases.
VOSS 8.0.1.0 or later for switches running VOSS 8.0.x releases.
VOSS 7.1.3.0 or later for switches running VOSS 7.1.x releases.

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. Always refer to Release Notes for VOSS to understand the validated upgrade paths.

You must consider the following legacy management interface migration scenarios before you upgrade to VOSS 8.2 or later:

Table 1. Management Interface Migration Scenarios
Mgmt Interface	Mgmt Scenario	Migration Description
DVR leaf	Automatic migration during upgrade.	DvR leaf settings migrate automatically during the software upgrade process. 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 upgrading.	Use the migrate-to-mgmt command in the Loopback interface configuration CLI to specify the CLIP interface for management before starting the software upgrade process. The loopback IP to migrate can include the configured ISIS IP shortcuts. Save the configuration before upgrading. A Fabric or legacy Layer 3 network typically uses the CLIP management interface. 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 upgrading.	Use the migrate-to-mgmt command in the VLAN interface configuration CLI mode to specify the VLAN interface for management before starting the software upgrade process. Save the configuration before upgrading. A Layer 2 network typically uses the VLAN management interface, or for restricting management access to a specific subnet or I-SID.

For more information about Segmented Management Instance migration, see VOSS User Guide.