ON THIS PAGE
 

Move Virtual Network to Different Routing Zone

You can move one or more virtual networks from one routing zone to another (as of version 5.0.0). This is traffic-impacting for any endpoints that are part of the selected virtual networks (since the VNs need to be deleted from one RZ and recreated in the other one).

Move One Virtual Network to a Different Routing Zone

  1. From the blueprint, navigate to Staged > Virtual > Virtual Networks and click the Edit button in the Actions panel for the virtual network to move.
    User interface for managing virtual networks with tabs like Dashboard, Analytics, Staged, Uncommitted, Active, and Time Voyager. Virtual tab selected, showing options to create networks and a table listing network details including Name, Routing Zone, Type, VN ID, L3 MTU, and connectivity. Table includes actions for editing or deleting entries.
    The Edit Virtual Network dialog opens.
  2. From the Routing Zone drop-down list, select the routing zone that you want to move the virtual network to. (The virtual network subnet IP, gateway IP (if the VN is IP-enabled) and VLAN ID of the source virtual network will be preserved, so these need to "free of use" in the destination routing zone.)
    User interface for editing virtual network configuration with fields: Type set to VXLAN, Name set to blue_300_evpn_esi_001_le_v4, Routing Zone set to blue, optional Description, and an Update button to save changes.
  3. Click Update to stage the change and return to the Virtual Networks table view.

When you're ready to activate your changes, go to the Uncommitted tab to review and commit (or discard) your changes.

Move Multiple Virtual Networks to a Different Routing Zone

  1. From the blueprint, navigate to Staged > Virtual > Virtual Networks, select the check boxes for one or more virtual networks to move, then click the Migrate selected Virtual Networks... button that becomes available above the table.
    Network management interface with tabs for Dashboard, Analytics, Staged, Uncommitted, Active, and Time Voyager. Virtual category selected, showing subcategories like Virtual Networks and Routing Zones. Table lists virtual networks with details. Migration tooltip explains moving networks between Routing Zones. Create Virtual Networks button visible.
    The Migrate Selected Virtual Networks to another Routing Zone dialog opens.
  2. From the Routing Zone drop-down list, select a different routing zone. (The virtual network subnet IP, gateway IP (if the VN is IP-enabled) and VLAN ID of the source virtual networks will be preserved, so these need to "free of use" in the destination routing zone.)
    Migrate selected virtual networks to another routing zone interface with a warning about traffic impact, routing zone dropdown, table listing virtual network details, and a migrate button.
  3. Click Migrate to stage the change and return to the Virtual Networks table view.

When you're ready to activate your changes, go to the Uncommitted tab to review and commit (or discard) your changes.