As you plan your installation, you must consider TCP/IP address requirements and service access for the system.
| 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 | 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. The system 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; 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.
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 can use a fixed IP address per Ethernet port, or you can configure the system to use a DHCP-allocated address.
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.