Skip to main content
SANtricity 11.9

Considerations for assigning IP addresses

Contributors netapp-jolieg netapp-driley
PDFs

By default, controllers ship with DHCP enabled on both network ports. You can assign static IP addresses, use the default static IP addresses, or use DHCP-assigned IP addresses. You also can use IPv6 stateless auto-configuration.

Note

IPv6 is disabled by default on new controllers, but you can configure the management port IP addresses using an alternate method, and then enable IPv6 on the management ports using System Manager.

When the network port is in a "link down" state, that is, disconnected from a LAN, the system reports its configuration as either static, displaying an IP address of 0.0.0.0 (earlier releases), or DHCP enabled with no IP address reported (later releases). After the network port is in a "link up" state (that is, connected to a LAN), it attempts to obtain an IP address through DHCP.

If the controller is unable to obtain a DHCP address on a given network port, it reverts to a default IP address, which might take up to 3 minutes. The default IP addresses are as follows:

Controller 1 (port 1): IP Address: 192.168.128.101
Controller 1 (port 2): IP Address: 192.168.129.101
Controller 2 (port 1): IP Address: 192.168.128.102
Controller 2 (port 2): IP Address: 192.168.129.102

When assigning IP addresses:

  • Reserve Port 2 on the controllers for Customer Support usage. Do not change the default network settings (DHCP enabled).

  • To set static IP addresses for E4000, E2800, and E5700 controllers, use SANtricity System Manager. To set static IP addresses for E2700 and E5600 controllers, use SANtricity Storage Manager. After a static IP address is configured, it remains set through all link down/up events.

  • To use DHCP to assign the IP address of the controller, connect the controller to a network that can process DHCP requests. Use a permanent DHCP lease.

    Note

    The default addresses are not persisted across link down events. When a network port on a controller is set to use DHCP, the controller attempts to obtain a DHCP address on every link up event, including cable insertions, reboots, and power cycles. Any time a DHCP attempt fails, the default static IP address for that port is used.