About migrating partially stacked domains

In Virtual Connect Manager, three types of Ethernet stacking configurations are supported and can be migrated into HPE OneView:

Full

Every Ethernet interconnect has a path to all other Ethernet interconnects. Full stacking is the default mode.

This configuration is migrated into HPE OneView with all Ethernet and Fibre Channel interconnects in one logical interconnect group. This configuration can be migrated in-service or offline.

Primary-slice

Stacking occurs only between the primary and standby Ethernet interconnects within the domain.

This configuration is migrated into HPE OneView with the primary and secondary interconnects configured within one logical interconnect group. All other Ethernet interconnects are configured in their own logical interconnect group with one Ethernet interconnect per logical interconnect group. Fibre Channel interconnects are configured together in a separate logical interconnect group. This configuration must be migrated offline.

Horizontal

Stacking occurs between each horizontal Ethernet interconnect pair.

This configuration is migrated into HPE OneView with all horizontally-adjacent interconnects configured into one logical interconnect group. If there is no horizontally-adjacent interconnect present, when migrated, the corresponding logical interconnect group contains only a single Ethernet interconnect. This configuration must be migrated offline. Fibre Channel interconnects are configured together in a separate logical interconnect group.

Full stacking migration from Virtual Connect Manager to HPE OneView
Primary-slice stacking migration from Virtual Connect Manager to HPE OneView
Horizontal stacking migration from Virtual Connect Manager to HPE OneView
You migrate a VCM-managed enclosure into a new or existing enclosure group.
  • New enclosure group — the logical interconnect groups are created based on the Virtual Connect stacking configuration. The networks and uplink sets are copied to the newly created logical interconnect group(s).

    For horizontal or primary-slice:

    • Ethernet networks are copied to all logical interconnect groups containing Ethernet interconnects. Uplink sets are copied to all logical interconnect groups. Uplink set ports are copied only to the created uplink set within the logical interconnect groups containing those ports.

      All Ethernet settings such as QoS are migrated to the newly configured Ethernet logical interconnect groups.

    • FCoE networks are added to the uplink set created in the logical interconnect group containing the associated uplink set ports.

    • Virtual Connect fabrics are copied as Fibre Channel uplink sets within the logical interconnect group containing the fabric uplink ports. An associated Fibre Channel network is also created.

    • SNMP configurations are migrated to all the logical interconnect groups, including the Fibre Channel logical interconnect group.

  • Existing enclosure group — the existing HPE OneView logical interconnect group(s) must match the exact bay and interconnect type of the Virtual Connect configuration. Otherwise, a compatibility error occurs and the migration is blocked.

    For example, if a VCM-managed enclosure is Primary-slice and bays 1, 2, 3, and 4 are populated with HPE Virtual Connect FlexFabric 10Gb/24–Port Modules, an error occurs if HPE OneView does not have a matching enclosure group with the logical interconnect groups defined with the same interconnect type (HPE Virtual Connect FlexFabric 10Gb/24–Port Module) for all four bays. In addition, bays 1 and 2 must be configured together in one logical interconnect group and bays 3 and 4 must be configured into two separate logical interconnect groups.

    The attributes applied to the logical interconnect groups such as uplink sets, Ethernet settings, and SNMP configurations must also match or errors can occur.