Skip to main content

Configure FC adapters

Contributors netapp-aherbin netapp-aaron-holt netapp-dbagwell
PDFs

Onboard FC adapters and some FC expansion adapter cards can be individually configured as either initiators or targets ports. Other FC expansion adapters are configured as initiators or targets at the factory and cannot be changed. Additional FC ports are also available through supported UTA2 cards configured with FC SFP+ adapters.

Initiator ports can be used to connect directly to back-end disk shelves, and possibly foreign storage arrays. Target ports can be used to connect only to FC switches.

The number of onboard ports and CNA/UTA2 ports configured for FC varies depending on the model of the controller. The supported target expansion adapters also varies depending on controller model. See NetApp Hardware Universe for a complete list of onboard FC ports and supported target expansion adapters for your controller model.

Configure FC adapters for initiator mode

Initiator mode is used to connect the ports to tape drives, tape libraries, or third-party storage with Foreign LUN Import (FLI).

Before you begin

  • LIFs on the adapter must be removed from any port sets of which they are members.

  • All LIFs from every storage virtual machine (SVM) using the physical port to be modified must be migrated or destroyed before changing the personality of the physical port from target to initiator.

Note

NVMe/FC does not support initiator mode.
Steps

  1. Remove all LIFs from the adapter:

    network interface delete -vserver _SVM_name_ -lif _lif_name_,_lif_name_

  2. Take your adapter offline:

    network fcp adapter modify -node _node_name_ -adapter _adapter_port_ -status-admin down

    If the adapter does not go offline, you can also remove the cable from the appropriate adapter port on the system.

  3. Change the adapter from target to initiator:

    system hardware unified-connect modify -t initiator _adapter_port_

  4. Reboot the node hosting the adapter you changed.

  5. Verify that the FC ports are configured in the correct state for your configuration:

    system hardware unified-connect show

  6. Bring the adapter back online:

    node run -node _node_name_ storage enable adapter _adapter_port_

Configure FC adapters for target mode

Target mode is used to connect the ports to FC initiators.

The same steps are used to configure FC adapters for the FC protocol and the FC-NVMe protocol. However, only certain FC adapters support FC-NVMe. See the NetApp Hardware Universe for a list of adapters that support the FC-NVMe protocol.

Steps

  1. Take the adapter offline:

    node run -node _node_name_ storage disable adapter _adapter_name_

    If the adapter does not go offline, you can also remove the cable from the appropriate adapter port on the system.

  2. Change the adapter from initiator to target:

    system node hardware unified-connect modify -t target -node _node_name_ adapter _adapter_name_

  3. Reboot the node hosting the adapter you changed.

  4. Verify that the target port has the correct configuration:

    network fcp adapter show -node _node_name_

  5. Bring your adapter online:

    network fcp adapter modify -node _node_name_ -adapter _adapter_port_ -state up

Configure FC adapters for direct-attachment to FC and FC-NVMe hosts

Beginning with ONTAP 9.19.1, an FC switch is not required to establish connections between FC and FC-NVMe hosts and ONTAP storage. Hosts can be directly connected to FC adapter ports on AFF, ASA, ASA r2 and FAS systems. Direct-attachment capability can be especially valuable in remote sites and hybrid environments where simplicity is key. You must take the FC port offline and modify its topology before it can be directly attached to a host.

FC ports used in direct-attachment configurations have the following restrictions:

  • The port can be assigned to only one storage VM (SVM).

  • Only one network interface (LIF) can be assigned to the port after it is configured for direct attachment.

  • The port can support the FC protocol or the FC-NVMe protocol, but not both.

Before you begin

You must be a cluster administrator.

System Manager

  1. In System Manager, select Network > FC ports.

  2. Select selection icon next to the port you want to configure for direct attachment and then select Edit topology.

  3. Under Topology, select Direct and then select I want to change the topology and take the port offline.

  4. Select Save.

  5. Connect the cable for the target port directly to the host initiator.

  6. If you have an AFF, ASA or FAS system, follow these steps to create a LIF: If you have an ASA r2 system, follow this System Manager procedure to create a LIF.

    1. Select Network > Interfaces and then select add icon.

    2. Select the FC or NVMe/FC protocol.

    3. Name the LIF or accept the name generated by ONTAP.

    4. Select the home port.

    5. Select Save.

      The port is brought online automatically when the LIF is created.

What's next?

In System Manager, select Network > FC ports and then verify that the Topology is displayed as Direct.

CLI

  1. Verify that the port you want to use for direct attachment supports the direct topology:

    network fcp adapter show -fields topologies-supported

  2. View the administrative and operational status of the LIF used for the adapter port:

    network interface show -vserver <SVM_name>

  3. Take the LIF used for the adapter port offline:

    network interface modify -vserver <SVM_name> -lif * -home-port <adapter_port> -status-admin down

  4. Remove all LIFs from the adapter port:

    network interface delete -vserver <SVM_name> -lif * -home-port <adapter_port>

  5. Take the adapter offline:

    network fcp adapter modify -node <node_name> -adapter <adapter_port> -status-admin down

  6. Change the adapter port topology to direct:

    network fcp adapter modify -node <node_name> -adapter <adapter_port> -topology direct

  7. Connect the cable for the target port directly to the host initiator.

  8. Create a single LIF interface:

    network interface create -vserver <SVM_name> -lif <lif_name> -data protocol fcp|fcp-nvme -home-node <node_name> -home-port <port_name>

    The port is automatically enabled after LIF creation.

  9. Verify that the port is configured for direct attachment:

    network fcp interface show

    The topology should be displayed as direct.

Related information

Configure FC adapter speed

You should configure your adapter target port speed to match the speed of the device to which it connects, instead of using autonegotiation. A port that is set to autonegotiation can take longer time to reconnect after a takeover/giveback or other interruption.

About this task

Because this task encompasses all storage virtual machines (SVMs) and all LIFs in a cluster, you must use the -home-port and -home-lif parameters to limit the scope of this operation. If you do not use these parameters, the operation applies to all LIFs in the cluster, which might not be desirable.

Before you begin

All LIFs that use this adapter as their home port must be offline.

Steps

  1. Take all of the LIFs on this adapter offline:

    network interface modify -vserver * -lif * { -home-node node1 -home-port 0c } -status-admin down

  2. Take the adapter offline:

    network fcp adapter modify -node node1 -adapter 0c -state down

    If the adapter does not go offline, you can also remove the cable from the appropriate adapter port on the system.

  3. Determine the maximum speed for the port adapter:

    fcp adapter show -instance

    You cannot modify the adapter speed beyond the maximum speed.

  4. Change the adapter speed:

    network fcp adapter modify -node node1 -adapter 0c -speed 16

  5. Bring the adapter online:

    network fcp adapter modify -node node1 -adapter 0c -state up

  6. Bring all of the LIFs on the adapter online:

    network interface modify -vserver * -lif * { -home-node node1 -home-port 0c } -status-admin up
Related information