HP XC System Software Incorporating External NICs HowTo Version 3.
© Copyright 2007, 2008 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
Table of Contents Overview.............................................................................................................................7 1 Minimum Requirements......................................................................................................................7 2 Impact...................................................................................................................................................7 3 Before You Begin..........................................
List of Tables 1 2 3 4 Minimum Requirements.................................................................................................................7 Affect on Existing HP XC Systems..................................................................................................7 Modelmap Values..........................................................................................................................12 Data Worksheet...................................................................
Overview This document describes the procedures for incorporating more than one external networking interface card (NIC) in a node of an HP XC system. The cluster_config utility configures the first external physical Ethernet port. HP recommends that the ordering of NICs remain consistent for all nodes of the same model type.
To perform the necessary tasks for this HowTo, you need: • • • • • To gather node-specific information To determine NIC-specific information To specify networking information To understand the platform_vars.ini Configuration File To understand how to use the device_config Command 3.1 Gathering Node-Specific Information The following node-specific information is required to complete the tasks in this HowTo: • The node name. That is, how the node is known to the HP XC system.
NOTE: • • The PCI bus ID does not apply to the model type rx8620 server. the Ethernet device port the Ethernet device's MAC address On all model types except the rx8620, use the lshw command on the target node to return the data for the Ethernet interfaces: IMPORTANT: Do not use the lshw command to determine the Ethernet data for model type rx8620 nodes. This action could cause those nodes to crash.
description: Ethernet interface product: NetXtreme BCM5703 Gigabit Ethernet vendor: Broadcom Corporation physical id: 1 bus info: pci@05:01.0 logical name: eth2 version: 10 serial: 00:00:00:00:00:02 ... The dd variable was used in this example to denote the last portion of the MAC address. Record the information, as shown here: Ethernet Device PCI Bus ID MAC Address eth0 02:00.0 00:00:00:00:00:00 eth1 03:00.0 00:00:00:00:00:01 eth2 05:01.
3.3 Gathering Networking Information The following information is required to configure the NIC: • • • • • • The external host name for the node The external IP address Optionally, the external IPv6 address The netmask The gateway, that is, the system that acts as a gateway to external communications Optionally, the largest packet size (MTU). Complete the corresponding portions of Table 4 (page 14) with the information from this section. 3.4 Understanding the platform_vars.
used to determine the values for the Administration port, the Interconnect port, and the External port or ports, which are assigned to the modelmap variable. • Interconnect type. That is, does the system use Gigabit Ethernet for the Interconnect switch or not? • Ethernet device count.
1 2 The entries in the platform_vars.ini file for the model type rx8620 nodes must specify Ethernet devices, not PCI bus IDs. This value can be used reliably only when all nodes of that model type have zero or one NIC available after matching up the explicitly specified PCI bus ids to their corresponding logical networks (Admin/Interconnect/External), that is, when the choice of NIC for offboard is unambiguous.
NOTE: If you are using IPv6 or MTU, there are additional options that you should specify. Enter the following command for more information: # /opt/hptc/config/sbin/device_config --help 4 Applying the HowTo The following list summarizes the steps to incorporate one or more network interface card for an HP XC system node: 1. 2. 3. 4. 5. “Consolidating Data for the HowTo” (page 14) “Edit the platform_vars.ini Configuration File” (page 14). “Update the Database for the External Network Card” (page 16).
6. Determine which modelmap variable assignment line applies to your needs: The lines that begin with the string Ethernet are provided for systems that use Gigabit Ethernet for the Interconnect switch. The lines that begin with the string !Ethernet are provided for systems that use an interconnect other than Gigabit Ethernet. Determine the line that corresponds to the final number of Ethernet devices for the node. 7.
1. From the head node, copy the platform_vars.ini to the target node or nodes: # pdcp -w nodelist /opt/hptc/config/platform_vars.ini /opt/hptc/config/ TIP: It may desirable to copy this file to all the nodes. # pdcp -a /opt/hptc/config/platform_vars.ini /opt/hptc/config/ 2. 3. 4. Log in to the target node. Verify that the platform_vars.ini file on the target node contains the changes you made. Run the following perl command on the target node.
--extnetwork external1 \ --ip 192.0.2.2 \ --name station2.example.com \ --netmask 255.255.248.0 \ --gw 192.0.2.100 \ --iftype Ethernet \ 00:00:00:00:00:02 NOTE: The options and arguments are displayed on separate lines for clarity. The following variables were used in this example: nn dd 3. 4. Is the first octet of the IP address and gateway IP address. Is the last portion of the MAC address. Examine the command output.
5 This line opens virtual port 22 for TCP on the fourth additional physical external Ethernet port, External4. The subsequent line performs the same function for virtual port 443. You can modify these lines in the iptables.proto file to configure each logical network independently from the others across the HP XC system. When no Ethernet device serves in the position of a particular network, the line in the iptables.proto file is ignored. In effect, the line is dropped from the actual configuration.
. . . host_names: Admin: device: gateway: hwaddr: iftype: ifusage: interface_number: ipaddr: ipv6addr: mtu: name: netmask: port: switch: External: device: gateway: hwaddr: iftype: ifusage: interface_number: ipaddr: ipv6addr: mtu: name: netmask: External1: device: gateway: hwaddr: iftype: ifusage: interface_number: ipaddr: ipv6addr: mtu: name: netmask: Interconnect: device: gateway: hwaddr: iftype: ifusage: interface_number: ipaddr: ipv6addr: mtu: name: netmask: eth0 00:00:00:00:00:00 Ethernet Admin 172.20.
4.5 Reconfiguring the Nodes After editing the platform_vars.ini file and updating the database, you need to reconfigure the nodes with the new NICs. Use the following procedure: 1. 2. Log in as superuser (root) on the head node. Copy the following files, and any other files that you may have changed: # pdcp -a -x `hostname` /opt/hptc/config/platform_vars.ini /opt/hptc/config/platform_vars.ini # pdcp -a -x `hostname` /etc/sysconfig/iptables.proto /etc/sysconfig/iptables.
Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on Supports Wake-on: umbg Wake-on: g Current message level: 0x00000007 (7) Link detected: yes For information on the ethtool command, see ethtool(8). 6 Troubleshooting Use the standard Linux networking commands to troubleshoot your network connection.
