Managing Network Datalinks in Oracle® Solaris 11.2

Exit Print View

Updated: September 2014
 
 

Migrating a VLAN to Another Underlying Link

You can migrate a VLAN from one underlying datalink to another underlying datalink without deleting and reconfiguring the VLAN. The underlying link can be a physical link, a link aggregation, or an etherstub. For more information about etherstubs, see Components of a Virtual Network in Managing Network Virtualization and Network Resources in Oracle Solaris 11.2 .

To successfully migrate a VLAN, the underlying datalink to which the VLAN is moved must be able to accommodate the datalink properties of the VLAN. If those properties are not supported, then migration fails and the user is notified. After a successful migration, all the applications that use the VLAN continue to operate normally provided that the VLAN remains connected to the network.

Certain hardware-dependent properties might change after a VLAN migration. For example, a VLAN always shares the same MAC address as its underlying datalink. Therefore, when you migrate a VLAN, the VLAN's MAC address changes to the primary MAC address of the target datalink. Other properties that might be affected are the datalink state, link speed, and MTU size. However, applications continue to operate without interruption.


Note - A migrated VLAN does not retain any of its hardware lane statistics from the original datalink. Available hardware lanes for the VLAN on the target datalink become the new source of statistics information. However, software statistics that are displayed by default by the dlstat command are preserved.

You can perform a VLAN migration either globally or selectively.

Global Migration

Global migration is used to migrate all of the VLANs that are configured over one datalink to another datalink. To perform a global migration, you need to specify only the source and target datalinks. The following example shows how to move all of the VLANs on ether0 to net1.

# dladm modify-vlan -l net1 -L ether0
–l

Refers to the target datalink to which the VLANs are migrated.

–L

Refers to the original datalink over which the VLANs are configured.


Note - You must specify the target datalink before the source datalink.

Selective Migration

Selective migration is used to migrate only selected VLANs. To perform selective VLAN migration, you specify the VLANs that you want to move. In the following example, which is based on Figure 3–3, VLANs are moved from net0 to net3.

# dladm modify-vlan -l net3 web1,auth1,app1

Note -  When migrating VLANs selectively, do not include the –L option, which applies only to global migration.

You can change the VLAN IDs of VLANs while performing a migration. Using Figure 3–3 as the basis, the following example shows how you would migrate multiple VLANs and change their VLAN IDs at the same time.

# dladm show-vlan
LINK    VID      OVER     FLAGS
web1    111      net0     -----
auth1   112      net0     -----
app1    113      net0     -----

# dladm modify-vlan -l net3 -v 123 web1
# dladm modify-vlan -l net3 -v 456 auth1
# dladm modify-vlan -l net3 -v 789 app1
# dladm show-vlan
LINK    VID      OVER     FLAGS
web1    123      net3     -----
auth1   456      net3     -----
app1    789      net3     -----

Note -  A parallel command, dladm modify-vnic, migrates VNICs that are configured as VLANs. You must use the correct subcommand depending on whether you are migrating VLANs or VNICs that are configured as VLANs. Use the modify-vlan subcommand on VLANs that are displayed by the dladm show-vlan command. Use the modify-vnic subcommand on VNICs, including those with VLAN IDs, that are displayed in the output of the dladm show-vnic command. For information about how to modify VNICs, see Modifying the VLAN IDs of VNICs in Managing Network Virtualization and Network Resources in Oracle Solaris 11.2 .