FC target port configuration recommendations
Suggest changes
PDFs
FC target ports can be configured and used for the FC-NVMe protocol in the exact same way they are configured and used for the FC protocol. Support for the FC-NVMe protocol varies based upon your platform and your ONTAP version. Use NetApp Hardware Universe to verify support.
For best performance and highest availability, you should use the recommended target port configuration listed in NetApp Hardware Universe for your specific platform.
Configuration for FC target ports with shared ASICs
The following platforms have port pairs with shared application-specific integrated circuits (ASICs). If you use an expansion adapter with these platforms, you should configure your FC ports so that they do not use the same ASIC for connectivity.
| Controller | Port pairs with shared ASIC | Number of target ports: Recommended ports |
|---|---|---|
|
0g+0h |
1: 0g 2: 0g, 0h |
|
0c+0d 0e+0f |
1: 0c 2: 0c, 0e 3: 0c, 0e, 0d 4: 0c, 0e, 0d, 0f |
FC target port supported speeds
FC target ports can be configured to run at different speeds. All target ports used by a given host should be set to the same speed. You should set the target port speed to match the speed of the device to which it connects. Do not use autonegotiation for your port speed. A port that is set to autonegotiation can take longer to reconnect after a takeover/giveback or other interruption.
You can configure onboard ports and expansion adapters to run at the following speeds. Each controller and expansion adapter port can be configured individually for different speeds as needed.
| 4 Gb ports | 8 Gb ports | 16 Gb ports | 32 Gb ports |
|---|---|---|---|
|
|
|
|
|
UTA2 ports can use an 8 Gb SFP+ adapter to support 8, 4, and 2 Gb speeds, if required. |