I was recently in a situation at work when I needed to stop work on a NetApp AFF redeploy and mount the SAN so some of its original data could be recovered. Now the SAN used Fiber Channel in its old location and its new location was Ethernet.
At this point I have re-IPed the Service Processors and was about to factory reset the unit. But now I needed present the LUNs to VMware. To do this I needed to remove the FC ports and mount the LUNs using iSCSI over Ethernet.
After allot of fruitless searching I remembered my college Mick did the same thing with this SANs DR target. He even blogged about it.
Micks Blog post is here.
https://www.jordansphere.co.uk/convert-netapp-ports-from-fc-to-cna/
I needed to convert ports e0e – e0h from Fiber Channel to CNA (Ethernet)
So, once I am SSHed to the cluster I enter the following to display the FC ports. Note I am in standard admin mode.
First I need to see the ports I want to convert.
ucadmin show
And I get the following
Current Current Pending Pending Admin
Node Adapter Mode Type Mode Type Status
———— ——- ——- ——— ——- ——— ———–
san01-01
0e fc target – – online
san01-01
0f fc target – – online
san01-01
0g fc target – – online
san01-01
0h fc target – – online
san01-02
0e fc target – – online
san01-02
0f fc target – – online
san01-02
0g fc target – – online
san01-02
0h fc target – – online
8 entries were displayed.
Next I need to disable these ports.
network fcp adapter modify -node san01-01 -adapter 0e -status-admin down
network fcp adapter modify -node san01-01 -adapter 0f -status-admin down
network fcp adapter modify -node san01-01 -adapter 0g -status-admin down
network fcp adapter modify -node san01-01 -adapter 0h -status-admin down
network fcp adapter modify -node san01-02 -adapter 0e -status-admin down
network fcp adapter modify -node san01-02 -adapter 0f -status-admin down
network fcp adapter modify -node san01-02 -adapter 0g -status-admin down
network fcp adapter modify -node san01-02 -adapter 0h -status-admin down
Now the ports are disabled I can change them to cna mode.
system node hardware unified-connect modify -node san01-01 -adapter 0e -mode cna
system node hardware unified-connect modify -node san01-01 -adapter 0f -mode cna
system node hardware unified-connect modify -node san01-01 -adapter 0g -mode cna
system node hardware unified-connect modify -node san01-01 -adapter 0h -mode cna
system node hardware unified-connect modify -node san01-02 -adapter 0e -mode cna
system node hardware unified-connect modify -node san01-02 -adapter 0f -mode cna
system node hardware unified-connect modify -node san01-02 -adapter 0g -mode cna
system node hardware unified-connect modify -node san01-02 -adapter 0h -mode cna
When converting adapters 0e and 0g you will be asked for confirmation
Warning: Mode on adapter 0e and also adapter 0f will be changed to cna.
Do you want to continue? {y|n}: y
Any changes will take effect after rebooting the system. Use the "system node reboot" command to reboot.
Just enter “y” and carry on.
Once done you will have to reboot each controller.
system node reboot -node san01-01
One at a time
system node reboot -node san01-02
Once both controllers are back up, SSH back on to the cluster and enable the now Ethernet ports.
network fcp adapter modify -node san01-01 -adapter 0e -status-admin up
network fcp adapter modify -node san01-01 -adapter 0f -status-admin up
network fcp adapter modify -node san01-01 -adapter 0g -status-admin up
network fcp adapter modify -node san01-01 -adapter 0h -status-admin up
network fcp adapter modify -node san01-02 -adapter 0e -status-admin up
network fcp adapter modify -node san01-02 -adapter 0f -status-admin up
network fcp adapter modify -node san01-02 -adapter 0g -status-admin up
network fcp adapter modify -node san01-02 -adapter 0h -status-admin up
There you go.
Thank you Mick for the initial pain of finding this info.