System IP addresses

The system IP address provides access to the system management interfaces and access to remote services.

Requirements for storage portsets

The system supports a maximum of one portset of storage type, that is, portset 3. These requirements are specific to storage portsets:
  • The maximum number of IP addresses for a storage portset equals the number of Ethernet ports on the node.
  • A portset can either contain IPv4 or IPv6 IP or a mix of IPv4 and IPv6 addresses.
  • The storage type portset must be already created.

Requirements for System IP addresses

  • System IP requirements: The system IP address provides access to the system management interfaces, including the management GUI, CLI, and RestAPI. The system IP address is also used to access remote services like authentication servers, NTP, SNMP, SMTP, and syslog systems, if configured.
    • A system address (IPv4 or IPv6) must be configured on Ethernet port 1 (default) or any other Ethernet port.
    • Optionally, a second system address can be configured on any Ethernet port except the one where the first system address is configured.
    • A maximum of two system addresses, either IPv4, IPv6, or a mix of both, can be configured for system management.
    • To ensure system IP failover operations, the Ethernet ports where the system addresses are configured must be connected to the same subnet. The system IP address can fail over to any node in the system.
    • System addresses can be configured on any ports.
    • IP addresses configured for system management and service access must not be used for Ethernet-based host I/O.
    • A management portset (for a storage partition) can include one partition management IP address (IPv4 or IPv6). For more information, see Storage partitions.

To assign an IP address to any Ethernet interface I/O port, use the management GUI or the mkip command. To change the MTU parameter for specific Ethernet port, use the management GUI or chportethernet command.

If the node fails, the address becomes unavailable and the host loses communication with the system via that node. To allow hosts to maintain, access to data, the node-port IP addresses for the failed node are transferred to the partner node in the I/O group. The partner node handles requests for both its own node-port IP addresses and also for node-port IP addresses on the failed node. This process is known as node-port IP failover.