Considerations for TCP/IP Address Standards at Mt Xia

These TCP/IP address standards are:

• used with disaster recovery procedures to coordinate fail-over resources
• used with disaster recovery procedures to eliminate resource conflicts
• used with high availability procedures to coordinate fail-over resources
• used with high availability procedures to eliminate resource conflicts
• used with manual fail-over procedures to coordinate fail-over resources
• used with manual fail-over procedures to eliminate resource conflicts
• consistent and repeatable procedures
• compatible with standalone, high availability, disaster recovery, business continuity, and virtualized environments

TCP/IP Address Standards

Standalone System, Single Ethernet Interface

Table 1:Example TCP/IP Addressing for a standalone system with a single ethernet interface

Host Name	Purpose	Binding	Example Address	Adapter	Routing	Subnet	NetMask	Access Type
easapora01-bt01	Boot	Bound to Adapter	192.168.201.28	en0	Non-routed	192.168.201.0	255.255.255.0	IPL
easapora01-pr01	Persistent	Bound to Node	10.110.201.28	en0	Routed	10.110.201.0	255.255.255.0	SysAdmin
easapora01	Node	Bound to Node	10.110.201.30	en0	Routed	10.110.201.0	255.255.255.0	Utility
easapora01-rg01	Service	Floater	10.110.201.31	en0	Routed	10.110.201.0	255.255.255.0	CNAME
orapdmx1	Alias	CNAME	easapora01-rg01					User/Appl

TCP/IP Address Standards

Standalone system, two ethernet interfaces servicing two resource groups

Table 2:Example TCP/IP Addressing for a standalone system with a two ethernet interfaces

Host Name	Purpose	Binding	Example Address	Adapter	Routing	Subnet	NetMask	Access Type
easapora01-bt01	Boot	Bound to Adapter	192.168.201.28	en0	Non-routed	192.168.201.0	255.255.255.0	IPL
easapora01-pr01	Persistent	Bound to Node	10.110.201.28	en0	Routed	10.110.201.0	255.255.255.0	SysAdmin
easapora01	Node	Bound to Node	10.110.201.30	en0	Routed	10.110.201.0	255.255.255.0	Utility
easapora01-rg01	Service	Floater	10.110.201.31	en0	Routed	10.110.201.0	255.255.255.0	CNAME
orapdmx1	Alias	CNAME	easapora01-rg01					User/Appl
Host Name	Purpose	Binding	Example Address	Adapter	Routing	Subnet	NetMask	Access Type
easapora01-bt02	Boot	Bound to Adapter	192.168.201.29	en1	Non-routed	192.168.201.0	255.255.255.0	IPL
easapora01-pr02	Persistent	Bound to Node	10.110.201.29	en1	Routed	10.110.201.0	255.255.255.0	SysAdmin
easapora01-rg02	Service	Floater	10.110.201.32	en1	Routed	10.110.201.0	255.255.255.0	CNAME
orapdmx2	Alias	CNAME	easapora01-rg02					User/Appl

TCP/IP Address Standards

Table 2:Example TCP/IP Addressing

Host Name	Purpose	Binding	Example Address	Routing	Subnet	NetMask	Access Type
easapora01-bt01	Boot	Bound to Adapter	192.168.201.29	Non-routed	192.168.201.0	255.255.255.0	IPL
easapora01-bt02	Boot	Bound to Adapter	192.168.201.30	Non-routed	192.168.201.0	255.255.255.0	IPL
easapora01-hb01	HeartBeat	Bound to Adapter	192.168.220.1	Non-routed	192.168.220.0	255.255.255.0	HACMP internal
easapora01-hb02	HeartBeat	Bound to Adapter	192.168.221.1	Non-routed	192.168.221.0	255.255.255.0	HACMP internal
easapora01-pr01	Persistent	Bound to Node	10.110.201.28	Routed	10.110.201.0	255.255.255.0	SysAdmin
easapora01-pr02	Persistent	Bound to Node	10.110.201.29	Routed	10.110.201.0	255.255.255.0	SysAdmin
easapora01	Node	Bound to Node	10.110.201.30	Routed	10.110.201.0	255.255.255.0	Utility
easapora01-rg01	Service	Floater	10.110.201.31	Routed	10.110.201.0	255.255.255.0	User/Appl
easapora01-rg02	Service	Floater	10.110.201.32	Routed	10.110.201.0	255.255.255.0	User/Appl
easapora01-sb01	Standby	Bound to Node	192.168.201.30	Non-routed	192.168.201.0	255.255.255.0	HACMP internal
easapora01-sb02	Standby	Bound to Node	192.168.201.31	Non-routed	192.168.201.0	255.255.255.0	HACMP internal

The policies, guidelines, standards, and procedures set forth in this document for your consideration are as follows:

Policies:

• All partition names, node names, and host names shall be enterprise wide unique values.
• Partition and Node names shall use alpha-numeric characters only
• The last character of all partition, node, and host names shall be a digit between 0 and 9.
• An even/odd numbering sequence shall be used with VIO Server host names to help the system administrator better identify VIO components.
• Do not use the underscore (_) character in host names, use the dash (-) instead.

Guidelines:

• VIO Server LPAR's should be created using a script to ensure consistency and adherence to standards.
• When defining LPAR's on the HMC, use the same name for the partition, profile, node, and host name.
• When defining nodes of an HACMP cluster, the host name which matches the node name of a system in the cluster should NOT fail over to any other node in the cluster.

Standards:

• This document defined a naming standard for logical partitions, nodes, hosts, and network adapters.

Procedures:

• When defining client LPAR's on multiple frames, do not place all LPAR's with even numbered node names on one frame and odd numbered on another, place both even and odd on each frame.