Unassigned server profile connections cannot be migrated

Symptom

The HPE OneView migration compatibility report shows a warning or blocking issue due to an unassigned server profile connection. To determine how to resolve an unassigned server profile connection depends on the reason for the unassigned connection and the ramifications to the OS configuration if the connection is not migrated. Review the following solutions to determine the cause of the issue and how to resolve it.

Solution 1
Cause

Resolve server profile connections associated with a specific adapter port

An unassigned server profile connection cannot be migrated. The connection was created in VCM to associate with a specific adapter port.

VCM associates Ethernet connections to server adapter ports with a round-robin algorithm. If a connection is needed to map to a mezzanine port instead of a LOM port, an unassigned connection is created in VCM to force the mapping. The first two connections are unassigned and the next two connections map to the mezzanine ports.

HPE OneView allows a server profile connection to be directly associated with a specific adapter port. During migration, HPE OneView maps the specific connections associated with the server in VCM to the specific adapter ports in HPE OneView. Because the unassigned connection is not migrated, the removal of the corresponding interface within the operating system might cause issues.

Action
In VCM, perform one of the following actions based on the type of connection.
  1. Fibre Channel — If an OS impact is not expected, proceed with the migration without the connection. If an OS impact is expected, resolve the issue after migration.
  2. FCoE — Assign a network with an uplink set containing an uplink port.
  3. FCoE FC SAN and native Fibre Channel — Assign a SAN fabric with an uplink port or proceed with the migration without the connection.
  4. iSCSI — Assign a network to the server profile connection or proceed with the migration without the connection.
  5. Ethernet — Do one or more of the following:

    If the downlink port status is irrelevant, assign an unused, private network to eliminate server-to-server traffic.

    If the downlink port must be disabled, associate a private network with an uplink set with an unused port. Enable Smart Link on the network.

    If the connection is not necessary, delete the connection.

Solution 2
Cause

Assign a network for pre-allocated virtual MAC/WWNs

An unassigned server profile connection cannot be migrated. The connection was created in VCM as a placeholder for pre-allocation. Pre-allocation of virtual MAC/WWNs requires a network or fabric association with a profile connection.

Action
In VCM, perform one of the following actions based on the type of connection.
  1. FCoE — Assign a network with an uplink set containing an uplink port.
  2. FCoE FC SAN and native Fibre Channel — Assign a SAN fabric with an uplink port or proceed with the migration without the connection.
  3. iSCSI — Assign a network to the server profile connection or proceed with the migration without the connection.
  4. Ethernet — Do one or more of the following:

    If the downlink port status is irrelevant, assign an unused, private network to eliminate server-to-server traffic.

    If the downlink port must be disabled, associate a private network with an uplink set with an unused port. Enable Smart Link on the network.

    If the connection is not necessary, delete the connection.

Solution 3
Cause

Plan for mitigation for place holders created for an absent interconnect

An unassigned server profile connection cannot be migrated. The connection was created in VCM as a redundant FC or FCoE connection between vertical interconnects.

If redundant FC or FCoE connections are created between vertical interconnects (for example, when using two adapters for redundancy) instead of horizontally-adjacent interconnects, VCM requires a connection placeholder for the adapter even though the adapter port is not associated with an interconnect. HPE OneView does not require a placeholder since connections can be directly associated with a specific adapter port. For FC connections, the detection of a placeholder connection to an absent interconnect is a warning issue on the HPE OneView compatibility report, regardless of the server power status because the interface associated with the placeholder connection is present for the adapter port, even after server reboot. For FCoE connections, if the server power is on, the detection is a blocking issue on the compatibility report because the removal of the connection might result in the removal of the OS interface when the server is rebooted.

Action
  1. FC SAN — Proceed with the migration.
  2. FCoE and offline migration — Determine if there will be OS impact and plan for mitigation after the migration.
  3. FCoE and in-service migration — Power off the server and determine if there will be OS impact and plan for mitigation after the migration.
Solution 4
Cause

Remove FCoE, iSCSI, and FC connections created automatically by default

An unassigned server profile connection cannot be migrated. The connection was created in VCM because the VCM GUI automatically associates connections with FCoE, iSCSI, and FC interconnects.

Action
If they are not needed, delete the FCoE, iSCSI, and FC connections from the server profile.