HP Virtual Connect 8Gb 20-port Fibre Channel Module for c-Class BladeSystem - Manual (Page 301)

Appendix C: Using IPv6 with Virtual Connect 301
Appendix C: Using IPv6 with Virtual Connect
Minimum requirements to support IPv6
To support IPv6 with Virtual Connect, the following requirements must be met:
• Install SPP 2013.09.0 (B) or later
• VC 4.10 or later
• OA 4.01 or later
IPv6 addresses in VC
Beginning with VC 4.10, Virtual Connect interconnect modules can be configured to use IPv6 addresses for
communication over an IPv6 management network.
IPv6 address configuration is controlled by the OA. To enable IPv6 addressing in the VC, select the IPv6
enable check box in the OA web GUI page or execute the appropriate OA command in the OA CLI. This is
an enclosure wide configuration and all VC modules in the enclosure enable IPv6 address configuration if
this option is selected through the OA.
Four types of IPv6 addresses can be acquired by VC when IPv6 is enabled:
1. Link local address
2. DHCPv6 based dynamic address
3. EBIPAv6 address
4. SLAAC-based router advertisement address
Link Local Address
The LLA is an automatically configured, SLAAC address based on the MAC address of the interface. This
address starts with the prefix 0xfe80 and has link-local scope.
An LLA is always configured when IPv6 is enabled. The only way to disable the LLA for VC is to disable IPv6
in the OA.
The LLA is usable for communicating with nodes within the same network. Packets sent with the LLA as the
source address cannot be routed.
The LLA is displayed on the OA web GUI as one of the addresses available for communication with the VC.
To access the VCM GUI page, the appropriate interface ID must be appended to the web address while
directing the browser to a particular VCM. For example, in Linux, if eth0 is the interface, it could be of the
form:
https://[fe80::2e27:d7ff:febe:60a2%eth0]
On Windows, if the interface ID is a number, for example 11, the web address becomes:
https://[fe80::2e27:d7ff:febe:60a2%11]