Planning management connections
The cable-connection tables provide an easy to read method of recording the locations of current and planned cable connections for each control enclosure in the system.
Management Ethernet connections
Each node canister in a control enclosure connects over an Ethernet cable from Ethernet port 1 of the canister to an enabled port on your Ethernet switch or router. Ethernet port 1 is for accessing the management GUI, the service assistant GUI for the node canister, and iSCSI host attachment.
IP address allocation and usage
As you plan your installation, you must consider 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 |
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 |
| 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-based RDMA replication/high availability | Inbound and Outbound | TCP | 4791, 21451, 21452, 21455, and 21456 | Optional |
| IP-based RDMA replication/high availability | Inbound and Outbound | UDP | 4791, 21451, 21452, and 21455 | Optional |
| IP Partnership management IP communication | Inbound and Outbound | TCP | 3260 | Optional |
| IP Partnership data path connections1 | Inbound and Outbound | TCP | 3265 | Optional |
| REST API access and replication management | Inbound | TCP | 6443 and 7443 | Optional |
| NVMe over RDMA | Inbound and Outbound | UDP over RoCEv2 | 4420 | Optional |
| NVMe over TCP | Inbound and Outbound | TCP | 4420 | Optional |
| IP quorum application | Inbound and Outbound | TCP | 1260 | Optional |
| 1Ports must be open for IP addresses that are configured for replication and not the system IP address. | ||||
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.
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.