The "wrench" or management Ethernet port on the back of your system provides access to two internal interfaces 1. e0M: an interface you can use to manage your system via TCP/IP protocols (e.g. ssh, snmp, telnet, ONTAPI, etc.) 2. SP: an interface on your service processor - very handy for out-of-band management (remote access to your console port, power control, monitoring of your system) Since they're physically behind a common ethernet port, they need to be on the same IP subnet. In addition, as you saw from syslog, that subnet should be dedicated - not shared with your data-serving GigE interfaces.  Based on your IP subnet descriptions, it looks like you've done that.  Note: If all of your ethernet connections are going into single switch, you must use VLANs by assigning a VLAN per subnet (and placing the right switch ports for each subnet into the right VLAN). This is required to get true L2 Ethernet isolation between subnets. The #5 in the diagram port is called the "private management" port. The interface behind that port is e0P (P = private). This port is exclusively used for connecting the Alternate Control Path (ACP) Ethernet cables to external NetApp storage shelves (e.g. DS4243) for out-of-band recovery and management from the controller (via the e0P interface).  Do you have external shelves? Then we recommend that you set up the ACP ethernet cabling and enable ACP. See: Universal SAS and ACP Cabling Guide ... View more