TCP/IP requirements for SAN Volume Controller

Plan your installation, considering TCP/IP address requirements and service access.

To plan your installation, use Table 1 and consider the TCP/IP address requirements of the SAN Volume Controller clustered system and the requirements for the SAN Volume Controller to access other services. You must also plan for the Ethernet address allocation, and for the configuration of the Ethernet router, gateway and firewall.

Figure 1 shows the TCP/IP ports and services that are used by SAN Volume Controller.

Figure 1. TCP/IP ports and services

Table 1. Summary of TCP/IP ports and services
Service	Traffic direction	Protocol	Port	Service type
Email (SMTP) notification and inventory reporting	Outbound	TCP	25	Optional
SNMP event notification	Outbound	UDP	162	Optional
Syslog event notification	Outbound	UDP	514	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
HTTPS for GUI access	Inbound	TCP	443	Mandatory
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
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

Both IPv4 and IPv6 addresses are supported. SAN Volume Controller can operate with either internet protocol or with both internet protocols concurrently.

For configuration and management, you must allocate an IP address to the system, which 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 both IPv4 and IPv6 are operating concurrently, an address is required for each protocol.

Note: When the 10 Gbps Ethernet feature is installed, each node has two 10 Gbps Ethernet ports, which are numbered ports 3 and 4. The 10 Gbps ports can only be used for iSCSI or Fibre Channel over Ethernet host attachment. They cannot be used for configuration or management.

In addition to the management IP addresses, the system is configured with one or more service IP addresses. Service IP addresses are used to gain access to the service assistant when a node is not operating correctly as part of the system. As with the management IP addresses, service IP addresses can be IPv4 addresses, IPv6 addresses, or both. You should choose a fixed IP address per Ethernet port, or you can configure SAN Volume Controller to use a DHCP-allocated address.

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 an error.

If the SAN Volume Controller 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 SAN Volume Controller for 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 SAN Volume Controller management addresses.

SAN Volume Controller does not use name servers 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 SAN Volume Controller 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 Control Enclosure) is supported
IPv6 for Management is not supported.