HP Virtual Connect 4Gb Fibre Channel Module for c-Class BladeSystem - Manual (Page 295)

Appendix C: Using IPv6 with Virtual Connect 295
Migrations
Migration from IPv4 to a dual configuration
VC version OA version <4.00 OA version 4.00 or higher
VC version <4.10 • Upgrade VC to 4.10 or higher.
• Upgrade OA to 4.00 or higher.
• Enable IPv6 on all OAs starting
with the local enclosure.
• Enable DCPv6 or RA-SLAAC or
both to enable global addressing.
• Upgrade VC to 4.10 or higher.
• Enable IPv6 on all OAs starting with
the local enclosure, if not already
done.
• Enable DHCPv6 or RA-SLAAC or
both to enable global addressing.
VC version 4.10 or higher • Upgrade OA to 4.00 or higher.
• Enable IPv6 on all OAs starting
with the local enclosure.
• Enable DHCPv6 or RA-SLAAC or
both to enable global addressing.
• Enable IPv6 on all OAs starting with
the local enclosure.
• Enable DHCPv6 or RA-SLAAC or
both to enable global addressing.
Migration from a dual configuration to IPv6-only configuration:
1. Ensure the new configuration is not IPv6-only until the availability of IPv6-only support for iLO.
2. Validate if accessing VCM via IPv6 addresses is possible by either ssh or via the web GUI.
3. Disable DHCPv4 server, if any, in the environment.
4. Remove IPv4 addresses from the interconnect EBIPA configuration tabs.
5. Remove IPv4 configurations in the various utilities if they are not wanted in the future.
IPv4 configuration continue to exist and do not interfere with the operations. These configurations
include RSYSLOG entries, SNMP trap receiver entries, VCM Domain static IPv4 address, LDAP and
RADIUS/TACACS IPv4 entries.
6. Wait for the IPv4 addresses to be cleared from OA and VC. A reboot is recommended if the lease
period of a DHCPv4 address is high to ensure faster IP mode change.
To migrate from an IPv4 to IPv6-only configuration, HP recommends migrating to a dual configuration, and
then migrating to an IPv6-only configuration.
Disabling IPv6 support
The enclosure-wide IPv6 support can be disabled by unselecting the Enable IPv6 check box in the OA GUI or
by using the disable IPv6 command in the OA CLI. This functionality is implemented in OA version 4.00
and higher.
To prevent NO-COMM states, enclosure-wide IPv6 support should be disabled only after IPv4 addresses are
configured and reachable.
Any IPv6 configurations existing already are retained in the domain even after disabling IPv6 support, but the
configurations are not functional.
After IPv6 is disabled, all configuration pages on the GUI and CLI display the warning "The VC Domain is not
in IPv6 mode. Hence domain is not capable of functioning IPv6 addresses" but configurations are still
allowed.
The IPv6 functionality in VC is disabled by default when VC firmware is downgraded to a version below 4.10
or the OA firmware is downgraded to a version below 4.00.