Skip to main content


NetApp Knowledgebase

What is the default IP behavior when configuring management ports on E-Series?

Last Updated:


Applies to



E-Series default management port IP behavior:

By default, E-Series controllers ship with DHCP enabled on both network ports. When the network port is in a 'link down' state, that is, disconnected from a LAN, the SANtricity Storage Manager will report its configuration as either static and display an IP address of (earlier releases) or DHCP enabled with no IP address reported (later releases). Once the network port is in a 'link up' state (that is, connected to a LAN), it will attempt to obtain an IP address through DHCP.
If the controller is unable to obtain a DHCP address on a given network port, it will revert 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 :
Controller 1 (port 2):  IP Address :*
Controller 2 (port 1):  IP Address :
Controller 2 (port 2):  IP Address :*

*Port 2 on the controllers should be reserved for Customer Support usage, so the default network settings of DHCP enabled should not be changed.

The default addresses are not persisted across link down events. When a network port on a controller is set to use DHCP, the controller will attempt 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 will be used. 

If the desire is to use DHCP to assign the IP address of the controller, connecting the controller to a network that can process DHCP requests is all that is needed to obtain a DHCP address for the controller. When using DHCP, the recommendation is to use a permanent DHCP lease.

If a static IP address is preferred, it is recommended to set a static IP using SANtricity. Once a static IP is configured, it will remain set through all link down/up events.

After changing the management IP address, the SANtricity management software might be unable to connect to the storage array. The fix is to remove the storage array from the Enterprise Management window and then add it again.