#AFF-A250 NVMe/FC Question

1 messages · Page 1 of 1 (latest)

keen flower
#

I have just set up an AFF-A250, and connected 4 FC ports per node, but only 2 are showing as connected. Is this a best practice limitation or is there a way to get them all configured?

torn vine
#

Have you run through the basic FC / optics troubleshooting?

worn verge
#

Where do you see only 2 as connected?

dull brook
#

if you swap the cables with the "good" ports, you can rule out switch ports and cable.

gloomy lynx
#

So, NVMeFC only allows a limited target port per controller - from their published pdf:

To avoid any interface single points of failure, NetApp strongly recommends that you provision two paths per SVM, per node, per fabric. ONTAP will not allow storage administrators to create more than two LIFs per node/per SVM. This was a conscious choice by NetApp SAN target engineers to limit LIF creation to reduce the number of paths presented to an initiator. By creating this limit, NetApp can ensure sufficient redundancy to eliminate single points of failure while also reducing or eliminating the need for features such as Selective LUN Map (SLM), which is required in SCSI-based configurations to limit the number of paths presented to the initiator. If additional LIFs are needed for a given node, an additional SVM can be created where an additional two LIFs can be created per node to balance I/O to and from namespaces

#

so basically, create a 2nd SVM with the other ports and assign namespaces to it

median yew
#

I re-read the question 4 times now, I have no idea how you figured out OP was talking about NVMe/FC 😂 yeah, NVMe/FC can only do 2 LIFs per SVM, but I figured at least the ports would still show up as "connected"

frail path
median yew