Set the FC or UTA/UTA2 configuration on node3
If node3 has onboard FC ports, onboard unified target adapter (UTA/UTA2) ports, or a UTA/UTA2 card, you must configure the settings before completing the rest of the procedure.
You might need to complete Configure FC ports on node3 or Check and configure UTA/UTA2 ports on node3, or both sections.
|
|
NetApp marketing materials might use the term "UTA2" to refer to CNA adapters and ports. However, the CLI uses the term "CNA". |
If node3 does not have onboard FC ports, onboard UTA/UTA2 ports, or a UTA/UTA2 card (for example, AFF and FAS systems introduced beginning with ONTAP 9.15.1), and you are upgrading a system with storage disks, you can skip to the Map ports from node1 to node3.
Configure FC ports on node3
If node3 has FC ports, either onboard or on an add-on FC adapter, you must set port configurations on the node before you bring it into service because the ports are not preconfigured when the systems are shipped. If you don't configure the ports, you might experience a disruption in service.
You must have the values of the FC port settings from node1 that you saved in Prepare the nodes for upgrade.
You can skip this section if your system does not have FC configurations. If your system has onboard UTA/UTA2 ports or a UTA/UTA2 card, you configure them in Check and configure UTA/UTA2 ports on node3.
|
|
Enter the commands in this section at the cluster prompt. |
-
Display information about all FC and converged network adapters on the system.
system node hardware unified-connect show -
Compare the FC settings of node3 with the settings that you captured earlier from node1.
-
Take one of the following actions:
If the default FC settings on the new nodes are… Then… The same as the ones you that captured on node1
Go to Step 9.
Different from the ones that you captured on node1
Go to Step 4.
-
Modify the FC ports on node3 as needed by entering one of the following commands:
-
To program target ports:
system node hardware unified-connect modify -type \| -t target -adapter port_name -
To program initiator ports:
system node hardware unified-connect modify -type \| -t initiator -adapter port_name-tis the FC4 type: target or initiator.
-
-
Verify the new settings by entering the following command and examining the output:
system node hardware unified-connect show -
Exit Maintenance mode:
halt -
After you enter the command, wait until the system stops at the boot environment prompt.
-
Boot node3 at the boot environment prompt:
boot_ontap -
Take one of the following actions:
-
If node3 has a UTA/UTA2 card or UTA/UTA2 onboard ports, go to Check and configure UTA/UTA2 ports on node3.
-
If node3 does not have a UTA/UTA2 card or UTA/UTA2 onboard ports, skip Check and configure UTA/UTA2 ports on node3 and go to Map ports from node1 to node3.
-
Check and configure UTA/UTA2 ports on node3
If node3 has onboard UTA/UTA2 ports or a UTA/UTA2 card, you must check the configuration of the ports and possibly reconfigure them, depending on how you want to use the upgraded system.
You must have the correct SFP+ modules for the UTA/UTA2 ports.
If you want to use a Unified Target Adapter (UTA/UTA2) port for FC, you must first verify how the port is configured.
|
|
NetApp marketing materials might use the term UTA2 to refer to CNA adapters and ports. However, the CLI uses the term CNA. |
You can use the ucadmin show command to verify the current port configuration:
*> ucadmin show
Current Current Pending Pending Admin
Adapter Mode Type Mode Type Status
------- ------- --------- ------- --------- -----------
0e fc target - initiator offline
0f fc target - initiator offline
0g fc target - initiator offline
0h fc target - initiator offline
1a fc target - - online
1b fc target - - online
6 entries were displayed.
UTA/UTA2 ports can be configured into native FC mode or UTA/UTA2 mode. FC mode supports FC initiator and FC target; UTA/UTA2 mode enables concurrent NIC and FCoE traffic sharing the same 10GbE SFP+ interface and supports FC targets.
UTA/UTA2 ports might be found on an adapter or on the controller, and have the following configurations, but you should check the configuration of the UTA/UTA2 ports on the node3 and change it, if necessary:
-
UTA/UTA2 cards ordered when the controller is ordered are configured before shipment to have the personality you request.
-
UTA/UTA2 cards ordered separately from the controller are shipped with the default FC target personality.
-
Onboard UTA/UTA2 ports on new controllers are configured before shipment to have the personality you request.
Enter the commands in this section at the cluster prompt unless directed to enter Maintenance mode.
-
Check the current port configuration by entering the following command on node3:
system node hardware unified-connect showThe system displays output similar to the following example:
cluster1::> system node hardware unified-connect show Current Current Pending Pending Admin Node Adapter Mode Type Mode Type Status ---- ------- ------- --------- ------- ------- ------ f-a 0e fc initiator - - online f-a 0f fc initiator - - online f-a 0g cna target - - online f-a 0h cna target - - online f-b 0e fc initiator - - online f-b 0f fc initiator - - online f-b 0g cna target - - online f-b 0h cna target - - online 12 entries were displayed. -
If the current SFP+ module does not match the desired use, replace it with the correct SFP+ module.
Contact your NetApp representative to obtain the correct SFP+ module.
-
Examine the output of the
system node hardware unified-connect showorucadmin showcommand to determine whether the UTA/UTA2 ports have the personality you want. -
Take one of the following actions:
If the UTA/UTA2 ports… Then… Do not have the personality that you want
Go to Step 5.
Have the personality that you want
Skip Step 5 through Step 13 and go to Step 14.
-
If the system has storage disks and is running clustered Data ONTAP 8.3, boot node3 and enter maintenance mode:
boot_ontap maint -
Verify the settings:
ucadmin show -
Take one of the following actions:
If you are configuring… Then… Ports on a UTA/UTA2 card
Go to Step 8.
Onboard UTA/UTA2 ports
Skip Step 8 and go to Step 9.
-
If the adapter is in initiator mode, and if the UTA/UTA2 port is online, take the UTA/UTA2 port offline:
storage disable adapter adapter_nameAdapters in target mode are automatically offline in maintenance mode.
-
If the current configuration does not match the desired use, change the configuration as needed:
ucadmin modify -m fc|cna -t initiator|target adapter_name-
-mis the personality mode,fcorcna. -
-tis the FC4 type,targetorinitiator.You must use the FC initiator for tape drives and MetroCluster configurations. You must use the FC target for SAN clients.
-
-
Stop the system:
haltThe system stops at the boot environment prompt.
-
Enter the following command:
boot_ontap -
system node hardware unified-connect showThe output in the following examples show that the FC4 type of adapter "1b" is changing to
initiatorand that the mode of adapters "2a" and "2b" is changing tocna:cluster1::> system node hardware unified-connect show Current Current Pending Pending Admin Node Adapter Mode Type Mode Type Status ---- ------- ------- --------- ------- ----------- ------ f-a 1a fc initiator - - online f-a 1b fc target - initiator online f-a 2a fc target cna - online f-a 2b fc target cna - online 4 entries were displayed. -
Place any target ports online by entering the following command, once for each port:
network fcp adapter modify -node node_name -adapter adapter_name -state up