HP XC System Software Release Notes for Version 3.1

1.6 Support for IPv6 Addresses
Support for IPv6 addresses has been added in this release. When you invoke the cluster_prep
command, you can specify an IPv6 address for the head node's Ethernet connection to the external
network. Specifying this address is optional and is intended for sites that use IPv6 addresses for
the rest of the network.
Similarly, when you use the cluster_config utility to add an external Ethernet connection
to any node, you have the option to specify an IPv6 address.
1.7 Support for Jumbo Frames
Support for jumbo frames has been added in this release. When you invoke the cluster_prep
command, you can enable jumbo frames on Ethernet.
Similarly, when you use the cluster_config utility to add an external Ethernet connection
to any node, you have the option to enable jumbo frames.
1.8 Changes to Node Roles and Services
The following changes and enhancements have been made to roles and services:
• The console_services role has been replaced by the console_network role.
• The following roles have been added:
— The avail_node_mangement role provides improved availability for services typically
supplied by the head node.
— The console_network role enables you to designate nodes with physical connectivity
to the console network that are used by HP XC management functions. By default, all
nodes are assumed to have physical connectivity to the console network.
1.9 Enhancements to the discover Command
Supporting the HP server blade platform in HP XC hardware configurations introduces the
concept of enclosure-based systems. Server blades are housed in cabinets called enclosures.
Enclosures have a device known as the Onboard Administrator (OA), which manages the
enclosure and gathers all data necessary for the discover command to populate the HP XC
configuration and management database.
The discover command has been enhanced to discover the switch topology as well as the OAs
to discover all server blades in the hardware configuration.
In addition, to extend the enclosure concept to a hardware configuration that does not contain
server blades, the discover command has been enhanced to recognize the concept of a real
and virtual enclosure. A real enclosure is defined as an enclosure with one of more Onboard
Administrators. A virtual enclosure is defined as a ProCurve switch that has at least one console
port from a non-server blade node plugged into it.
In this release, the maximum number of server blade nodes in a real enclosure is 16. The maximum
number of non-server blade nodes in a virtual enclosure is 38.
1.10 Changes to Internal Node Naming Conventions
Internal node naming is affected when the hardware configuration contains enclosures and HP
server blades.
When the hardware configuration does not contain enclosures and HP server blades, internal
node names are assigned in a dense fashion in which there are no missing numbers in the node
numbering scheme except for a possible missing number between the branch nodes and those
nodes that are connected to the Root Administration switch.
1.6 Support for IPv6 Addresses 21