Filter
Top Products
3.4.3 Configuring the Interconnect Network Over the Administration Network
In cases where an additional Gigabit Ethernet port or switch may not be available, the HP XC
System Software enables you to configure the interconnect on the administration network. When
the interconnect is configured on the administration network, only a single LAN is used.
To configure the interconnect on the administration network, you include the --ic=AdminNet
option on the discover command line, which is documented in “Task 4: Discover Switches”
(page 29).
Be aware that configuring the interconnect on the administration network may negatively impact
system performance.
3.5 Cabling for the External Network
Depending upon the roles you assign to nodes during the cluster configuration process, some
nodes might require connections to an external public network. Making these connections requires
one or more Ethernet ports in addition to the ports already in use. The ports you use depend
upon the hardware configuration and the number of available ports.
On non-blade server nodes, the appropriate port assignments for the external network are shown
in the HP XC Hardware Preparation Guide.
On a server blade, the number of available Ethernet ports is influenced by the type of interconnect
and the server blade height:
• Nodes in clusters that use an InfiniBand interconnect have only one NIC in use for the
administration network.
• Nodes in clusters that use a Gigabit Ethernet interconnect have two NICs in use; one for the
administration network, and one for the interconnect network.
• Half-height server blade models have two built-in NICs.
• Full-height server blade models have four built-in NICs.
You can use the built-in NICs on a server blade if any are available. If the node requires more
ports, you must add an Ethernet card to mezzanine bay 1 on the server blade. If you add an
Ethernet card to mezzanine bay 1, you must also add an Ethernet interconnect module (either a
switch or pass-thru module) to interconnect bay 3 or 4 of the enclosure.
On full-height server blades, you can avoid having to purchase an additional mezzanine card
and interconnect module by creating virtual local area networks (VLANs). On a full-height server
blade, NICs 1 and 3 are both connected to interconnect bay 1, and NICs 2 and 4 are both connected
to interconnect bay 2. Ifyou are using one of these NICs for the connection to the externalnetwork,
you might have to create a VLAN on the switch in that bay to separate the external network from
other network traffic.
For information about configuring VLANs, see “Creating VLANs” (page 22).
The ports and interconnect bays used for external network connections vary depending on the
hardware configuration, the ports that are already being used for the other networks, and the
server blade height. For more information about how to configure the external network in these
various configurations, see the illustrations in the following sections:
• “Configuring the External Network: Option 1” (page 19)
• “Configuring the External Network: Option 2” (page 20)
• “Configuring the External Network: Option 3 - Non Gigabit Ethernet Interconnect Clusters”
(page 21)
3.5.1 Configuring the External Network: Option 1
Figure 3-5 (page 20) assumes that NIC1 and NIC2 are already in use for the administration and
interconnect networks. This situation requires a third NIC for the external network. Half-height
3.5 Cabling for the External Network 19