Table of ContentsView in Frames

How volumes and LIFs are placed on the destination SVM

You must understand how aggregates are selected to place the volumes and ports to place the LIFs on the destination SVM in case you want to move the volumes or migrate the LIFs on the destination SVM.

Criteria for placing volumes on the destination SVM

When replicating volumes from the source SVM to the destination SVM, aggregates are selected based on the the following criteria:

  1. Volumes are always placed on non-root aggregates.
  2. If a volume on the source SVM is located on a Flash Pool aggregate, then the volume is placed on a Flash Pool aggregate on the destination SVM, if such an aggregate exists and has enough free space.
  3. Non-root aggregates are selected based on the available free space and the number of volumes already hosted on the aggregate.

    Aggregates with more free space and less number of volumes are given priority. The aggregate with the highest priority is selected.

  4. If the -space-guarantee option of the volume that is replicated is set to volume, only aggregates with free space greater than the volume size are considered.
  5. The volume size grows automatically on the destination SVM during replication, based on the source volume size.

    If you want to pre-reserve the size on the destination SVM, you must resize the volume. The volume size does not shrink automatically on the destination SVM based on the source SVM.

If you want to move a volume from one aggregate to another, you can use the volume move command on the destination SVM.

Criteria for placing LIFs on the destination SVM

When replicating network configuration LIFs from the source SVM to the destination SVM, ports are selected based on the the following criteria:

  1. Ports belonging to the same IPspace as that of the destination SVM are tested for connectivity to the subnet of the LIF that is replicated.
  2. The connectivity of such ports is verified by sending ARP probes (RFC5227).

    Ports that receive a response are considered as candidates for placing LIFs.

    If no port receives any response and if a subnet object exists that is configured same as the subnet of the LIF to be placed, then all ports belonging to that subnet are considered as candidates for the port list.

    If no port receives any response and there is no subnet object for all the LIF subnets, then all ports belonging to the IPspace are considered as candidates for the port list.

  3. From the candidate list of ports, a single port is selected based on the following criteria:
    • If the LIF is placed on a VLAN port on the source SVM and a port with the same VLAN tag in the candidate port list exists, then that port is chosen for placing the LIF.
    • If the LIF was placed on an interface group and an interface group with same name exists in the candidate port list, then that interface group is selected for placing the LIF.
    • If the LIF was placed on a physical port on the source SVM, then a physical port with the same speed as that of the source SVM is preferred from the candidate port list.
    • If same-speed ports are not available in the candidate port list, then the LIFs are distributed across candidate ports based on a weighted random algorithm.

      Ports with higher speed have more preference, and therefore LIFs are placed on the higher speed ports.

If you want to move the LIFs from one port to another, you can use the network interface migrate or network interface modify -home-node -home-port command.