Dynamic Change Options for Segmented Management Instance Attributes

You can now 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. For example, if your switch onboards using VLAN 4048, you can change that Management Instance VLAN to a new VLAN.

You can change the following attributes for the Management Instance:

• Management Instance VLAN:

  • VLAN ID

  • IPv4 address

  • default gateway

  • I-SID (on a DvR Leaf)

  • ports-tagged

  • ports-untagged

• Management Instance CLIP

  • IPv4 address

  • vrf

• Management Instance Out-of-Band (OOB)

  • IPv4 address

  • default gateway

Operational Considerations

The following are operational considerations when you change Management Instance attributes using the convert command:

• IPv6 is not supported and is removed during conversion, if an IPv6 address exists.

• You cannot change parameters for more than one Management Instance operation at a time. You must issue the mgmt convert-commit command before you use the convert command for either the same or a different Management Instance.

• If you attempt to change attributes for an existing Management Instance VLAN, you cannot configure ports-tagged, ports-untagged, and I-SID parameters. Make configuration changes to the existing Management InstanceVLAN first before you use the convert command. If you change your switch to a DvR leaf node, you can change the I-SID parameter.

• If you attempt to change attributes for a Management Instance VLAN and the VLAN does not exist, a VLAN is automatically created in the background. You can specify ports-tagged, ports-untagged, and I-SID parameters to be associated with this new VLAN. The new VLAN is assigned to the default Spanning Tree Group, which is 0.

• If you attempt to change attributes for a Management Instance VLAN and the VLAN does not exist, and you do not specify ports-tagged, ports-untagged, or I-SID parameters, then this is a special case. If any untagged ports in the old VLAN have dynamic Address Resolution Protocol (ARP) entries then these ports automatically move from the old VLAN to the new VLAN. For example, VLAN 200 has port members 1/1, 1/2, and 1/3. ARP entries are configured on ports 1/1 and 1/2. VLAN 300 is created in the background and only ports 1/1 and 1/2 automatically move to this new VLAN.

  If an MLT ID is associated with the old VLAN, the association is removed and re-added to the new Management Instance VLAN ID.

• If you attempt to change the vrf attribute for a Management Instance CLIP but the vrf does not exist, a vrf is automatically created in the background. In order for this vrf to function properly, you must configure either SPBM Layer 3 VSN or IP interfaces and routing protocols.

  The best practice is to configure and test vrf connectivity before you use the convert command.

• The following applies when you change static routes attributes on a Management Instance VLAN or Management Instance OOB interface:

  • If you provide the static route next-hop gateway, all next-hop gateway direct to the new gateway.

  • If you do not provide the static route next-hop gateway and the new subnet is the same as the old subnet, all routes are re-added as is.

  • If you do not provide a gateway and the new subnet is different, routes are discarded.

• Dynamic routes added by DHCP convert to static routes.