C H A P T E R  5

Network Planning

This chapter contains information about the cabling connections for the Cluster Platform 15K/9960 system. It also includes system setup tables that you must complete before you attempt to install the system.


Network Connections

The Cluster Platform 15K/9960 system requires 10/100BASE-TX Ethernet connections on the customer network for each Sun Fire 15K server.

Each cluster node uses a Sun Quad FastEthernettrademark interface (qfe0) to connect to the public network. Port qfe4 is reserved as the network adapter failover (NAFO) interface for qfe0 on both cluster domain nodes. A qualified service technician must configure network failover (NAFO) interfaces using the pnmset(1M) command.



Note - Interfaces qfe2, qfe3, qfe5, qfe6, and qfe7 are available to expand network services. The qfe1 interface is reserved for the internal administration network.



Public Networks

The public network uses a 10/100BASE-T network hub to provide access to the domains. The hub is customer supplied. FIGURE 5-1 shows the layout of the public network.



Note - In the following diagram, the external public hub can be a switch or a hub.



 FIGURE 5-1 Public Network

Line art showing the cabling layout for the public network.

Administration Networks

The administration networks use a 10/100BASE-T network hub to provide access to the system controllers, domains (nodes), the shared storage, and the customer Intranet. FIGURE 5-2 shows the layout of the administration networks.



Note - In the following diagram, the external public hub can be a switch or a hub.



 FIGURE 5-2 Administration Networks

Line art showing the cabling layout for the administration networks.

Storage Connections

The storage connections enable the domains to have access to the shared storage and to the boot disks in the expansion cabinet. FIGURE 5-3 shows the layout of the storage connections.

 FIGURE 5-3 Storage Connections

Line art showing the cabling layout of the storage connections.

Serial Connections

The serial connections enable the terminal concentrator to have access to the system controllers. FIGURE 5-4 shows the layout of the serial connections.

 

FIGURE 5-4 Serial Connections

Line art showing the cabling layout of the serial connections.


System Setup Tables

Host names, networks, internet protocol (IP) addresses, and subnet masks for the Cluster Platform 15K/9960 system are required.

Sun Fire 15K System Controller Setup

Configuration of the system controllers and the installation of the operating system on the domains will also require host names, IP addresses, and subnet masks. Multiple user communities may also be involved. The tables that follow are designed to help organize this information before the installation.

Platform Name

The Sun Fire 15K server requires a platform name. The platform name, globally unique within the network, is a logical name given to an entire system and does not correspond to any host on the network. These names get set when you configure the system controllers. Use TABLE 5-1 to record the platform name for your records.

TABLE 5-1 Cluster Platform 15K/9960 System Platform Names

Sun Fire 15K Server

Platform Name

Server 1

 

Server 2

 


Domains

Host names and IP addresses are also required for the domain connections to a user community. Use TABLE 5-2 to record the domain settings. These values are set when you configure the system controllers.

TABLE 5-2 Domain Community, Host Name, and IP Addresses

Interface

User Community

Host Name

IP Address

Domain A (server 1)

domainA

 

 

Domain A (server 2)

domainA

 

 


Internal Networks

The subnets for the internal networks are fixed. Because I1, which is the domain to system controller management network (that is, MAN), and I2, which is the system controller to system controller management network, are not routed, the IP networks can be taken from the IP private pool. These networks should be set up using automatic assignment of host names and IP addresses. The networks should be unique within the customer network.

TABLE 5-3 IP Networks Subnet Masks for Internal Networks

Network

IP Network

Subnet Mask

Server 1, I1

 

255.255.255.224

Server 1, I2

 

255.255.255.252

Server 2, I1

 

255.255.255.224

Server 2, I2

 

255.255.255.252


External Networks

Enter the IP network address and subnet mask in TABLE 5-4. The subnet mask must be unique within the network. The system controller can connect only to one user community. These addresses are set when you configure the system controllers.

TABLE 5-4 IP Networks Subnet Masks for External Networks

User Community Network

IP Network

Subnet Mask

Community A (server 1 and server 2)

 

 


System Controller

IP addresses are required for every interface on the system controller (SC) that is cabled to a user community. Both SCs have one built-in Ethernet port (labeled "Ethernet") cabled, and the other port ("Ext Ethernet") is not used in this configuration.

The following table contains the user community and IP address for the SCs. These settings are set when you configure the system controllers.

TABLE 5-5 Community Host Name IP Addresses for the System Controllers

Cx Network

Interface

User Community

IP Address

Server 1, system controller 0, Ethernet

 

 

Server 2, system controller 0, Ethernet

 

 

Server 1, system controller 1, Ethernet

 

 

Server 2, system controller 1, Ethernet

 

 


Additionally, a logical interface is required for the SCs for each user community. Logical interfaces are only present on the main SC. SC pathgroup-specific IP addresses are also required when using an HA configuration (refer to the Sun Fire 15K Site Planning Guide for more information). Use the following table contains to record the logical interfaces. These interfaces are set when you configure the SCs.

TABLE 5-6 Host Name IP Addresses for the SC Logical Interface

User Community

Logical Host Name

Logical IP Address

SC0 Pathgroup IP Address

SC1 Pathgroup IP Address

Server 1, User Community A

 

 

 

 

Server 2, User Community A

 

 

 

 




Note - The logical and pathgroup-specific IP address for a community must use the same IP network and subnet as the physical NIC(s) in that community.



Terminal Concentrator Setup

You will need to provide the name, IP address, subnet mask, and broadcast address for the terminal concentrator. Use the following table to record the values.

TABLE 5-7 Terminal Concentrator Settings

Setting

Value

Name

 

IP address

 

Subnet mask

 

Broadcast address

 

Gateway default router

 


Management Server Setup

You will need to provide the following values during the management server configuration. Use the following table to record the values.

TABLE 5-8 Management Server Settings

Setting

Value

IP address

 

Cluster name

 

Internal administration network IP address

 

Internal administration network netmask

 

External administration network IP address

 


Node 1 Settings

You will need to provide the following values for node 1 during the management server configuration. Use the following table to record the values.

TABLE 5-9 Node 1 Settings

Setting

Value

Domain name

 

IP address

 

Administration network IP address

 

Ethernet address

 

Netmask address for the public network

 

Default router IP address for the public network

 

SC0 name

 

SC0 IP address

 

SC1 name

 

SC1 IP address

 


Node 2 Settings

You will need to provide the following values for node 2 during the management server configuration. Use the following table to record the values.

TABLE 5-10 Node 2 Settings

Setting

Value

Domain name

 

IP address

 

Administration network IP address

 

Ethernet address

 

SC0 name

 

SC0 IP address

 

SC1 name

 

SC1 IP address

 


Cluster Interconnect

You will need to provide the following values for the cluster interconnect during the management server configuration. Use the following table to record the values.

TABLE 5-11 Cluster Interconnect Settings

Setting

Value

IP address

 

Ethernet address