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

Appendix C: Using IPv6 with Virtual Connect 294
• VCSU version 1.9.0 can be used to update VC to 4.10 using IPv4 as target addresses.
Observe the following additional requirements for enabling IPv6 support in VC:
• The ability to enable or disable IPv6 as a stack is an enclosure-wide configuration, and can be done
using the OA CLI or the OA Web GUI.
• Although IPv6 is supported on OA versions prior to 4.00, IPv6 support for VC requires OA 4.00 or
later.
• On versions earlier than OA 4.00, IPv6 capability was enabled by default, while it is disabled by
default from OA 4.00 onward.
IMPORTANT: Avoid deploying an IPv6-only configuration until the availability of IPv6-only
support for the iLOs.
• To disable IPv4 configurations on the system, do the following:
o Ensure the new configuration is not IPv6-only until the availability of IPv6-only support for iLO.
o Ensure there are no DHCPv4 servers in the environment.
o Ensure EBIPAv4 pages corresponding to the iLOs and interconnects are not populated.
o Ensure the OA does not have an IPv4 address configured.
• Enabling IPv6 on the OA enables the IPv6 stack and ensures the availability of Link-Local SLAAC-based
addresses on all the modules. You must explicitly enable DHCPv6 or RA-SLAAC to enable the other
addresses on VC and the OA.
New installation
For a new deployment of OA 4.00 and VC 4.10, observe the following guidelines:
• iLO must have the same network configuration as the OA and VC.
• Dual IP mode configuration
o A configuration where all VC modules and OAs have been configured with both IPv4 addresses
and IPv6 addresses is a dual IP mode configuration. This configuration enables users and
administrators to access VC and the OA by using either the IPv6 address or the IPv4 address using
either ssh or the web GUI.
o Select both IPv4 and IPv6 check boxes on the OA for the primary and all the remote enclosures.
o Verify that all VC modules have both IPv4 addresses and IPv6 addresses.
o Import the local enclosure by providing the OA credentials.
o Remote enclosures can be imported using the IPv4 addresses or the IPv6 addresses of their
respective OAs.
• IPv6-only configuration
IMPORTANT: Avoid deploying an IPv6-only configuration until the availability of IPv6-only
support for the iLOs.
o Import remote enclosures using IPv6 addresses because IPv4 addresses would not exist in an
IPv6-only environment.
o Importing an enclosure with dual configuration fails because it is mandatory to have a uniform IP
configuration on all enclosures of the domain.