This chapter describes the internal system management network addressing scheme for SGI UV 2000, SGI UV 1000, or SGI UV 100 systems.
It covers the following topics:
The SGI UV hostname assignment is based on the rack and u position of the blade or other component. The rack/u position must be uniform across all SGI UV systems that are attached to a system management node (SMN). In other words, a single SGI UV 1000 system or SGI UV 2000 system that encompasses multiple racks will have racks numbers 1 to N in increments of 1, and u positions (upos) within each rack will range from 1 to 42, with an increment of 3 (there is an exception where upos 2 is also present). In the case of multiple SGI UV 100 systems, each SGI UV 100 is assigned a unique rack/upos in the same manner, so all SGI UV 100 systems are identifiable in this way.
The system management node (SMN) has three dedicated Ethernet ports to connect to the SGI UV systems, specifically, for the system control network and the primary Base I/O of each partition. There is one Ethernet port on the SMN that is to be attached to the customer network. The connections described in this manual are very specific. Sites are not allowed to also attach other unrelated customer equipment to these dedicated networks because this would interfere with SGI UV system management network.
The SMN detects and then assigns hostnames, IP addresses, and name binding for the SGI UV systems and any additional systems that have a dedicated BMC port connection to the single system image (SSI) segment. For more information, see “eth1smn” and “Multiple SGI UV Partitions or Systems on a Single SMN”. Because the SGI UV rack/upos convention for identification is used and the network connections are very specific, guidelines must be adhered to carefully.
The SGI UV 2000 SMN is a SuperMicro SuperServer 6017R-N3RF4+ server. The SGI UV 1000 SMN is a SuperMicro SuperServer 6016T-URF 1U server.
The four ports on the SMN are designated eth0 through eth3. The eth0 port is attached to the customer network. Its address is not assigned by the SMN software stack. Customers assign the IP address of the eth0 port. The ports eth1 through eth3 are dedicated to the system management network. To distinguish the SMN Ethernet ports from other ports on Base I/O blades or CMCs, the port is suffixed with "smn", for example eth0smn.
You can get product specification information and other documentation for the SuperMicro servers at http://www.supermicro.com/ or at http://docs.sgi.com/. Search on the following:
SuperServer 6016T-URF User's Manual, part number 860-0498-001.
SuperServer 6017R-N3RF4+ User's Manual, part number 007-5849-001
eth1smn is the port for the private network known as the SSI network. This is a dedicated, known path between the SGI Management Center (SMC) application and each kernel instance, or single system image (SSI). If an SGI UV system is partitioned, each partition requires at least one Base I/O blade, and the primary Base I/O of each partition is connected to the SMN. The eth1smn network connects the Base I/O baseboard management controller (BMC) to the SMN. This network can also connect systems other than SGI UV systems to an SMN. For example, you can attach the BMC from an SGI Rackable series system to the SMN, thus enabling administration through the SMN for these systems.
The IP address range for eth1smn is 172.21.0.0/16 with starting address 172.21.1.1. Within this range, the convention is to designate 172.21.1-128.x for Base I/O Ethernet and 172.21.129-254.x for BMCs on systems other than SGI UV systems.
eth2smn is the port for the private network known as the primary CMC network. The SGI UV 100, SGI UV 1000, or SGI UV 2000 systems with multiple CMCs are very specifically configured into a small network, and the SMN is a peer on this network.
The range of IP addresses for devices attached to eth2smn is 172.19.0.0/16 with starting address 172.19.1.1.
You can configure the eth3smn interface to operate in one of three different modes. To configure different modes for eth3smn, open file /etc/sysconfig/smnconfig, and search for the ETH3_MODE parameter. The ETH3_MODE parameter accepts one of the following arguments:
| Argument | Effect | |
| sysco | Configures eth3smn to operate in the same way as eth2smn, except that this argument sets the IP address range from 172.20.1.0 through 172.20.255.254 for DHCP known clients. For unknown clients, an anonymous pool is available in the range 172.20.0.2 through 172.20.0.63. The range 172.20.0.64 through 172.20.0.255 is reserved for static IP addresses and is not managed by the SMN's DHCP server. | |
| dhclient | Configures eth2smn as a standard DHCP client, so no DHCP configuration is generated for the eth2 interface. The IP range of 172.20.0.0/16 segment should not be used. | |
| dhserver | The effect of the dhserver argument is similar to the effect of the sysco argument. IP addresses ranging from 172.20.0.2 through 170.20.0.63 and IP addresses ranging from 172.20.1.0 through 172.20.255.254 are available for unknown clients. Like the sysco argument, the range 172.20.0.64 through 172.20.0.255 is reserved for static IP addresses and is not managed by the SMN's DHCP server. |
The chassis management controllers (CMCs) are given IP addresses based on their location in the racks. The address is determined, as follows:
172.{19|20}.rh.rruuuuuu
|
'rh' is the lower 8 bits of the rack number.
'rr' is the upper two bits of the rack number, shifted down 2. Rarely used.
'uuuuuu' is the upos (6 bits)
eth0 is the WAN interface (see Figure A-6 and Figure A-6). By default, SGI UV systems are shipped with dynamic host configuration protocol (DHCP) .
eth2 is 172.19.0.1 on the SMN. 172.19.XX.YY is the IP address when the SMN assigns the IP address to the CMC.
eth3 is same as eth2 except it is 172.20.
eth1 is the same but 172.21.X.Y. This is the link to the single-system image (SSI) SGI UV Base I/O. The SGI UV SSI Base I/O will get IP address either from system management node (SMN) or the SGI Management Center (SMC), when installed. For this segment, the SMN do not use rack/upos since it is not relevant for SSI Base I/O.
A single SGI UV system may be partitioned and have multiple kernels running. The Base I/O blade from each partition must have its eth1 and BMC ports attached to the system management node (SMN). To accommodate the additional cabling, a GigE switch is needed.
In a similar way, a single SMN can be configured to manage multiple SGI UV 100, SGI UV 1000 or SGI UV 2000 systems. One GigE switch is used for the SSI network, another switch for the CMC network.
The smnconfig tool performs discovery and address assignment in both of these configurations, if the cabling is connected per the guideline and the multiple SGI UV 100, SGI UV 1000 or SGI UV 2000 systems have their CMCs uniquely designated with the rack/upos method.
In addition to managing SGI UV 100, 1000, or 2000 systems, the SMN can also provide system management for other systems, such as the SGI UV 10, SGI Rackable systems, and so on. For these classes of systems, the only connection to the SMN required is the BMC port from the motherboard to the SSI network. The SSI network 172.21.0.0/16 connects the SGI UV Base I/O eth0 ports and the Base I/O BMC ports. Systems other than SGI UV systems connect their BMC ports to this network and are assigned addresses from the 172.21.129-254.x range.
Because of system addressing requirements for the system management node (SMN), see “System Network Addressing Overview”, firewall capabilities should only be applied to the SMN wide area network (WAN) interface eth0smn. The interfaces eth1smn, eth2smn, and eth3smn (see “System Management Node Ethernet Ports”) should not be firewalled in any manner with one exception, as follows:
If you use a remote client (installing the client-only installation of SMC on a different server), then TCP ports 7620, 4672, and 7673 need to be opened up in the firewall. This is the only requirement for the WAN interface.