IP address allocation and usage

As you plan your installation, you must consider IP address requirements and service access for the system.

Use Table 1 to consider the TCP/IP address requirements of the system and the requirements to access other services. You must also plan for the IP address allocation, and for the configuration of the Ethernet router, gateway and firewall.

Table 1. Summary of TCP/IP ports and services
Service	Traffic direction	Protocol	Port	Service type
Email (SMTP) notification and inventory reports	Outbound	TCP	25	Optional
SNMP event notification	Outbound	UDP	162	Optional
Syslog event notification	Outbound	TCP UDP	6514 (TCP) 514 (UDP)	Optional
IPv4 DHCP (Node service address)	Outbound	UDP	68	Optional
IPv6 DHCP (Node service address)	Outbound	UDP	547	Optional
Network time server (NTP)	Outbound	UDP	123	Optional
SSH for command line interface (CLI) access	Inbound	TCP	22	Mandatory
Remote support assistance	Outbound	TCP	22	Optional
HTTPS for GUI access	Inbound	TCP	443	Mandatory
Uploading support packages to IBM	Outbound	TCP	443	Optional
Remote support assistance for HTTPS GUI access	Outbound	TCP	443	Optional
CIMOM (HTTPS)	Inbound	TCP	5989	Optional
CIMOM SLPD	Inbound	UDP	427	Optional
Remote user authentication service - HTTP	Outbound	TCP	16310	Optional
Remote user authentication service - HTTPS	Outbound	TCP	16311	Optional
Remote user authentication service - Lightweight Directory Access Protocol (LDAP)	Outbound	TCP	389	Optional
iSCSI	Inbound	TCP	3260	Optional
iSCSI iSNS	Outbound	TCP	3260	Optional
iSER-RoCE host attach	Outbound	UDP	3260	Optional
iSER-iWARP host attach	Outbound	TCP	860	Optional
iSER-iWARP host attach	Outbound	UDP	860	Optional
IP-based RDMA clustering	Inbound/Outbound	TCP	4791, 21451, 21452, and 21455	Optional
IP-based RDMA clustering	Inbound/Outbound	UDP	4791, 21451, 21452, and 21455	Optional
IP Partnership management IP communication	Inbound	TCP	3260	Optional
IP Partnership management IP communication	Outbound	TCP	3260	Optional
IP Partnership data path connections	Inbound	TCP	3265	Optional
IP Partnership data path connections	Outbound	TCP	3265	Optional

Figure 1 shows the TCP/IP ports and services that are used by the system.

For configuration and management, you must allocate an IP address to the system; this IP address is referred to as the management IP address. For extra fault tolerance, you can also configure a second IP address for the second Ethernet port on the node. The addresses must be fixed addresses. If IPv4 and IPv6 are operating concurrently, you must provide an address for each protocol.

Attention: The address for a management IP cannot be the same address that is used for the service IP. Using the same IP address causes communication problems.

If the system console is used on a system other than the IBM® System Storage® Productivity Center , the system that it is run on must be able to access the system itself.

Any system that accesses the service IP address must be able to access a management IP address, or a dynamically allocated service address if DHCP is used.

You can configure event notification by SNMP, syslog, or email. To configure notification, you must ensure that the SNMP agent, syslog IP addresses, or SMTP email server IP addresses can be accessed from all system management addresses.

Name servers are not used to locate other devices. You must supply the numeric IP address of the device. To locate a device, the device must have a fixed IP address.

The nodes in a system can receive native IPv4 or IPv6 packets. The nodes cannot operate as an endpoint of a tunnel where an IPv4 packet contains an IPv6 payload or where an IPv6 packet contains an IPv4 payload.

To summarize then, with regards to IPv6 protocols supported:

IPv6 for iSCSI data traffic (to the node or control enclosure) is supported.
IPv6 for Management is not supported.