Migration to Segmented Management Instance

Important

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 VOSS Release Notes.

Ensure you understand the Management Instance interface types before you begin the upgrade and migration. For more information, see Interface Types.

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

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:

• Out-of-Band management interfaces
  • All IPv4 routes in the VRF 512 / mgmtrouter context are moved to the Segmented Management Instance.
  • All IPv6 routes in GRT with a nexthop IP address that exists in the same subnet as the IPv6 address are moved to the Segmented Management Instance.
• In-Band VLAN management
  • All IPv4 routes from the VRF bound to the migrated VLAN and that have a nexthop IP address in the same subnet as the IPv4 address being migrated are moved to the Segmented Management Instance.
  • All IPv6 routes from the VRF bound to the migrated VLAN and that have a nexthop IP address in the same subnet as the IPv6 address being migrated are moved to the Segmented Management Instance.
  

  Important

  The IP interface and all routing protocols attached to the original VLAN are deleted post migration.

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

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

As a best practice, use the convert command.

With the convert command, you can dynamically change the attributes of a Management Instance while you actively manage the switch over that same Management Instance without requiring the switch to reboot. This option also has rollback functionality to recover from unwanted changes.

For more information, see the following sections:

• Dynamic Change Options for Segmented Management Instance Attributes

• Change Management Instance Attributes

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. However, if you use this option, you must reboot your switch after you save the configuration changes.

The following is an outline of the steps required for management migration using the migrate-to-mgmt command:

1. 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.
   

   Important

   The IP interface and all routing protocols attached to the original VLAN are deleted post migration.

2. Add required routes to reach management services and subnets from the new interface.
3. Test connectivity to the new interface using ping and traceroute, and from the switch to management stations and servers.
4. Use the migrate-to-mgmt command from the new interface CLI mode.
5. Save the configuration and reboot.
   

   Note

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

For more information see, Migrate a VLAN or CLIP IP address to the Segmented Management Instance (using CLI) or Migrate an IP Address to a Segmented Management Instance (using EDM).

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 an XA1400 Series with the Fabric Extend (FE) tunnel Source IP using Segmented Management Instance:

Before upgrading to VOSS Release 8.1.60 or later:

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

2. Save configuration and reboot.

After upgrading to VOSS Release 8.1.60 or later:

1. Manage the XA1400 Series using the CLIP Management Instance.

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

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

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