Segmented Management Instance Migration

Important

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. This section does not apply to VSP 8600 Series.

Note

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:

Note

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.

Automatic Migration

Out-of-Band management interface and DVR leaf configurations automatically migrate during the upgrade process. The management port interface, and all associated applications are moved to the Segmented Management Instance .

A DVR leaf has a single management interface that also automatically migrates during the upgrade process to the Segmented Management Instance.

Static Route Migration

When a VLAN designated as management interface or an Out-of-Band management interface migrates to the Segmented Management Instance, static routes might be required for IP reachability. Static routes are always required for Out-of-Band management interfaces but can also be used with in-band VLAN management.

Static route migration is completed by the upgrade process and no commands are necessary to prepare for the migration. The following logic is applied during the upgrade process to the static routes:

Consider the following example of In-Band VLAN management. The static route configuration listed below is in the GRT:
ip route 192.168.20.0 255.255.255.0 192.168.10.2 weight 1
ip route 192.168.30.0 255.255.0.0 192.168.10.50 weight 1
ip route 192.168.40.0 255.255.255.0 192.168.20.99 weight 1
ip route 192.168.50.0 255.255.255.0 192.168.10.2 weight 1
no ip route 192.168.50.0 255.255.255.0 192.168.10.2 enable

The GRT is associated with VLAN 10 with an IP address of 192.168.10.1. This is the VLAN to be migrated. After the upgrade, the 192.168.20.0, 192.168.30.0, and, 192.168.50.0 routes are migrated to the management instance because their nexthop IP address is associated with the 192.168.10.0/24 subnet.

Note

Note

All routes with a nexthop IP address associated with the subnet are migrated. This includes administratively disabled routes. Administratively disabled routes must be manually deleted after the upgrade if the route is not needed.

ECMP static route migration is not supported for the Segmented Management Instance. For an ECMP static route, only the first path in the configuration file migrates.

After upgrading to VOSS Release 8.1.60 or later, any administratively disabled static routes that migrated to the OOB or VLAN Segmented Management Instance subnet become active. Administratively disabled routes must be manually deleted after the upgrade if the route is not needed.

The static route configuration in the Management VLAN configuration block will be the following after the upgrade:
mgmt vlan 10
ip address 192.168.10.1/24
ip route 192.168.20.0/24 next-hop 192.168.10.2
ip route 192.168.30.0/16 next-hop 192.168.10.50
ip route 192.168.50.0/24 next-hop 192.168.10.2

Segmented Management Instance Migration

Beginning in VOSS 8.2, you can use the migrate-to-mgmt command to move a management VLAN to a different VLAN ID, or a management CLIP to a different VRF. After you complete the command and save the configuration, the migration to management of the selected interface occurs during the next switch reboot. The following is an outline of the steps required for management migration:

  • Configure a new or existing VLAN or CLIP management interface using Interface Configuration mode in the CLI (interface vlan <vlan_id> or interface loopback <clip_id>) or EDM.
  • Add required routes to reach management services and subnets from the new interface.
  • Test connectivity to the new interface using ping and traceroute, and from the switch to management stations and servers.
  • Use the migrate-to-mgmt command from the new interface CLI mode.
  • Save the configuration and reboot.
    Note

    Note

    During boot, the migrate-to-mgmt settings are parsed and override the existing management interface with the new interface.
  • Access and manage the switch from the new interface.

XA1400 Series Management Migration with a Fabric Extend Source IP VLAN

Before VOSS Release 8.1.60, a single IP address could be used for both routing or management, however Segmented Management Instance separates the routing and management networking stacks. Because migrate-to-mgmt can only move an IP from the routing stack to the management stack, see the following scenario for a before and after upgrade process required to manage a XA1400 Series with the Fabric Extend (FE) tunnel Source IP using Segmented Management Instance:

Before upgrading to VOSS Release 8.1.60 or later:

  • Configure a CLIP Management Instance or designate an existing loopback IP for migration.

  • Save configuration and reboot.

After upgrading to VOSS Release 8.1.60 or later:

  • Manage the XA1400 Series using the CLIP Management Instance.

  • Create the VLAN Management Instance with the same VLAN ID and IP address as the FE tunnel source VLAN.

  • Modify the default route or create static routes to the VLAN Management Instance.

  • Manage the XA1400 Series with the VLAN or CLIP Management Instance.

9036830-00 Rev AD