NetApp port descriptions and what to do with e0M, SP and ACP

The current NetApp lineup has a variety of ports on the back which can be confusing to even the most experienced admin.

A FAS3240 (single-chassis HA) for example has two SAS, two GBIC slots, two GBICs with FCP modules, five RJ45 and a USB – and that’s without using the two PCI expansion slots or the chassis I/O expansion.

Here I’ll break down the ports you see on the back of a FAS3240 and describe the three “new” management methods e0M, SP and ACP.

The documentation that ships with the controller has a good legend to help decipher the icons printed by each connection:

And a picture of the chassis, just in case you are not standing next to it.

I’ll go left-to-right

7: SAS cables for your external SAS shelves. 0a, 0b. If you ordered your filer with SAS shelves it should have shipped with cables. Note that you can multi-path shelves with SAS just like FCP.

8: HA cables. c0a, c0b. If you buy a multi-chassis filer (ie you want a FAS3240 with the expansion module you’ll get two physical chassis) or want to do metro-cluster. Note also – these are 10G Ethernet ports but they have OS-set IP addresses and cannot be used for anything but HA.

6: FCP. 0c, 0d. Used for connecting to Fibre Channel switches, shelves or tape drives (for NDMP backups)

3: e0a and e0b. Two 1GB Ethernet adapters for network access and traditional management. iSCSI, CIFS, NFS, http will all use these ports.

4: Unlocked management. e0M / SP combo port. This is the successor to BMC/RLM out-of-band management port. It adds a twist in that port e0M on the filer shares this port (there is an internal hub). You can configure just the SP port (sp setup) and use it for out-of-band management, you can also configure e0M from the filer which will use this port for in-band management – Filerview, System Manager etc. Note that you are required to have e0M on a separate IP network than your other ethernet ports, and it is required to be on the same network as the Service Processor. It is possible data (iSCSI, NFS, CIFS) traffic will go out this port as a last resort – but it won’t have it’s own default gateway. This needs to be on a dedicated management-only network. Do not configure e0M unless you intend to use it – the filer will default management traffic to it if it is configured.

5: Locked management. e0P. Used for Alternate Control Path (ACP) Out-Of-Band (OOB) management of SAS shelves More and More

1/2: Serial port and RJ45-to-DB9 adapter. Used to manage the filer via console. Note you’ll need one of these if you have a modern system to connect the old-school serial cable up to your modern USB port. Don’t forget putty also.

Not labeled: USB. Currently described as “unused”

Always configure SP. Don’t configure e0M unless SP is connected to a dedicated management network. Always connect the ACP cables (hey, you paid for it!).
Always multipath SAS and FCP when you have the ports available.
Always take the lifeboat with the motor.

This entry was posted in Computing, NetApp, Storage and tagged , , , , , . Bookmark the permalink.

21 Responses to NetApp port descriptions and what to do with e0M, SP and ACP

          Leave a Reply

          This site uses Akismet to reduce spam. Learn how your comment data is processed.