Enclosures > About blocking issues during migration |  | next

# About blocking issues during migration

The following partial list of Virtual Connect features are considered blocking issues because they are not supported in HPE OneView. Blocking issues can also result when settings conflict between the Virtual Connect domain and the HPE OneView logical interconnect group into which the domain is being migrated. HPE OneView checks for these features and blocks the migration when these issues are found. Resolving an issue might require disabling a feature within Virtual Connect, changing a configuration in Virtual Connect, or in some cases, changing the HPE OneView logical interconnect group.

If a feature is required in your environment and your enclosure contains ProLiant G6 or later server blades, you might want to consider monitoring your enclosure. See About monitored c7000 enclosures.

| NOTE: VCEM-managed enclosures can be migrated to HPE OneView. See About migrating c7000 enclosures managed by other management systems for more information.

Blocking issues
Advanced SR-IOV[a] Auto-deployment c3000 enclosures, ProLiant G1 through G6 server blades, Integrity blades and Storage server blades Ethernet, iSCSI, and FCoE connection speed type disabled Federal Information Processing Standard (FIPS 140–2) | IGMP multicast filters and filter sets More than 1000 networks defined within the VC domain Multiple enclosure stacked domains Partially stacked domains[b] Server VLANs mapped to alternate network VLANs | SNMP v3 Storage management credentials Unassigned Ethernet, iSCSI, or FCoE network connections[b] Unsupported Fibre Channel speeds[b] VCEM multiple FC initiators
[a] Blocking issue for mixing automatic and non-automatic settings for in-service migration. However, for offline migration, settings are set to default (virtual functions are evenly spread across all physical functions). [b] Blocking issue for in-service migration only.

| NOTE: In general, for functions that are not required in your environment, disabling the function in VCM enables you to migrate the enclosure.

## About unassigned VCM server profile connections during migration

An unassigned VCM server profile connection is a connection without a specified network or fabric. There are five types of connections within VCM.

- Ethernet — One or more Ethernet networks assigned to the same server profile connection.

- FCoE — An FCoE network associated with an uplink set. Ethernet and FCoE networks may share the same uplink set.

- FCoE FC SAN — An FCoE connection assigned to a SAN fabric. These connections have one or more native Fibre Channel connections to the uplink ports which are part of the SAN fabric. They utilize FlexFabric physical function 2 of the adapter.

- Native Fibre Channel — A native Fibre Channel adapter connection to a Fibre Channel interconnect.

- iSCSI — An iSCSI, Ethernet network or unshared iSCSI network that is associated with an uplink set. Ethernet and iSCSI networks may share the same uplink set.

HPE OneView does not support unassigned server profile connections, so the connections are not migrated and cannot be recreated for the migrated server profile. For native Fibre Channel connections, a warning issue appears on the compatibility report. For all other connections, a blocking issue appears on the compatibility report for in-service migrations.

To determine how to resolve unassigned server profile connections depends on the reason for the unassigned connection and the ramifications to the OS configuration if the connection is not migrated.

#### More information

About blocking issues during migration
Migrate a c7000 enclosure currently managed by VCM

prev | up | next
Before migrating c7000 enclosures | home | About migration acknowledgments

Copyright © 2013, 2016 Hewlett Packard Enterprise Development LP