Thursday, September 13, 2012
3PAR inserv not showing WWNs on the FC switch
After the 3par installation was complete and we were working on creating zones for the hosts.
We noticed the fc coming from insev nodes doesn't show the wwns on the switch.
Here are some information learned while talking to 3PAR support
All the ports connected to cage/chassis should be set to initiator
All the ports in front of the host should be configured as target.
I believe by default all ports are configured as mode type initiators.
Step #0. showport
Result:
3par cli% showport
N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol
2:0:1 initiator ready 2FF70002AC001477 22010002AC001477 disk FC
2:0:2 initiator ready 2FF70002AC001477 22020002AC001477 disk FC
2:1:1 target loss_sync 2FF70002AC001477 22110002AC001477 free FC
2:1:2 target loss_sync 2FF70002AC001477 22120002AC001477 free FC
2:2:1 initiator ready 2FF70002AC001477 22210002AC001477 disk FC
2:2:2 initiator ready 2FF70002AC001477 22220002AC001477 disk FC
2:2:3 initiator ready 2FF70002AC001477 22230002AC001477 free FC <--- should be target
2:2:4 initiator ready 2FF70002AC001477 22240002AC001477 free FC <--- should be target
2:6:1 peer loss_sync - 0002AC69249B rcip IP
3:0:1 initiator ready 2FF70002AC001477 23010002AC001477 disk FC
3:0:2 initiator ready 2FF70002AC001477 23020002AC001477 disk FC
3:1:1 target loss_sync 2FF70002AC001477 23110002AC001477 free FC
3:1:2 target loss_sync 2FF70002AC001477 23120002AC001477 free FC
3:2:1 initiator ready 2FF70002AC001477 23210002AC001477 disk FC
3:2:2 initiator ready 2FF70002AC001477 23220002AC001477 disk FC
3:2:3 initiator ready 2FF70002AC001477 23230002AC001477 free FC <--- should be target
3:2:4 initiator ready 2FF70002AC001477 23240002AC001477 free FC <--- should be target
3:6:1 peer loss_sync - 0002AC6A2867 rcip IP
---------------------------------------------------------------------------
18
Step #1. Change all ports which would connect to hosts as targets
Assuming you have 4 connections to the fc switch
controlport rst -m target 2:2:3
controlport rst -m target 2:2:4
controlport rst -m target 3:2:3
controlport rst -m target 3:2:4
Results:
3par cli% controlport rst -m target 2:2:3
Are you sure you want to run controlport rst -m target on port 2:2:3?
select q=quit y=yes n=no: y
>>>>>repeat the same other ports
Step #2 showport -c
Result:
3par_F400_mcomNY01 cli% showport
N:S:P Mode State ----Node_WWN---- -Port_WWN/HW_Addr- Type Protocol
2:0:1 initiator ready 2FF70002AC001477 22010002AC001477 disk FC
2:0:2 initiator ready 2FF70002AC001477 22020002AC001477 disk FC
2:1:1 target loss_sync 2FF70002AC001477 22110002AC001477 free FC
2:1:2 target loss_sync 2FF70002AC001477 22120002AC001477 free FC
2:2:1 initiator ready 2FF70002AC001477 22210002AC001477 disk FC
2:2:2 initiator ready 2FF70002AC001477 22220002AC001477 disk FC
2:2:3 target ready 2FF70002AC001477 22230002AC001477 free FC <-- converted as target
2:2:4 target ready 2FF70002AC001477 22240002AC001477 free FC <-- converted as target
2:6:1 peer loss_sync - 0002AC69249B rcip IP
3:0:1 initiator ready 2FF70002AC001477 23010002AC001477 disk FC
3:0:2 initiator ready 2FF70002AC001477 23020002AC001477 disk FC
3:1:1 target loss_sync 2FF70002AC001477 23110002AC001477 free FC
3:1:2 target loss_sync 2FF70002AC001477 23120002AC001477 free FC
3:2:1 initiator ready 2FF70002AC001477 23210002AC001477 disk FC
3:2:2 initiator ready 2FF70002AC001477 23220002AC001477 disk FC
3:2:3 target ready 2FF70002AC001477 23230002AC001477 free FC <-- converted as target
3:2:4 target ready 2FF70002AC001477 23240002AC001477 free FC <-- converted as target
3:6:1 peer loss_sync - 0002AC6A2867 rcip IP
---------------------------------------------------------------------------
After converting to target also, the switch still doesn't show the WWNs
Step #3.showport -c
Result
3par cli% showport -c
N:S:P Mode Device Pos Config Topology Rate Cls Mode_change
2:0:1 initiator cage0 0 valid private_loop 4Gbps 3 prohibited
cage4 1 valid private_loop 4Gbps 3 prohibited
2:0:2 initiator cage1 0 valid private_loop 4Gbps 3 prohibited
cage5 1 valid private_loop 4Gbps 3 prohibited
2:1:1 target --- - --- n/a n/a n/a allowed
2:1:2 target --- - --- n/a n/a n/a allowed
2:2:1 initiator cage2 0 valid private_loop 4Gbps 3 prohibited
cage6 1 valid private_loop 4Gbps 3 prohibited
2:2:2 initiator cage3 0 valid private_loop 4Gbps 3 prohibited
cage7 1 valid private_loop 4Gbps 3 prohibited
2:2:3 target --- - --- private_loop 4Gbps 3 allowed <--Topology has to fabric instead of private_loop
2:2:4 target --- - --- private_loop 4Gbps 3 allowed <--Topology has to fabric instead of private_loop
3:0:1 initiator cage0 1 valid private_loop 4Gbps 3 prohibited
cage4 0 valid private_loop 4Gbps 3 prohibited
3:0:2 initiator cage1 1 valid private_loop 4Gbps 3 prohibited
cage5 0 valid private_loop 4Gbps 3 prohibited
3:1:1 target --- - --- n/a n/a n/a allowed
3:1:2 target --- - --- n/a n/a n/a allowed
3:2:1 initiator cage2 1 valid private_loop 4Gbps 3 prohibited
cage6 0 valid private_loop 4Gbps 3 prohibited
3:2:2 initiator cage3 1 valid private_loop 4Gbps 3 prohibited
cage7 0 valid private_loop 4Gbps 3 prohibited
3:2:3 target --- - --- private_loop 4Gbps 3 allowed <--Topology has to fabric instead of private_loop
3:2:4 target --- - --- private_loop 4Gbps 3 allowed <--Topology has to fabric instead of private_loop
--------------------------------------------------------------------
24
Step #4. Setup ports as fabric and instead of loop
Results:
To enable port on the switch:
3par cli% controlport offline 2:2:3
Are you sure you want to run controlport offline on port 2:2:3?
select q=quit y=yes n=no: y
3par cli% controlport config host -ct point 2:2:3
Are you sure you want to run controlport config host -ct point on port 2:2:3?
select q=quit y=yes n=no: y
3par cli% controlport rst 2:2:3
Are you sure you want to run controlport rst on port 2:2:3?
select q=quit y=yes n=no: y
>>>>>repeat the same other ports
Step #5. Finally it should look as below
3par cli% showport -c
N:S:P Mode Device Pos Config Topology Rate Cls Mode_change
2:0:1 initiator cage0 0 valid private_loop 4Gbps 3 prohibited
cage4 1 valid private_loop 4Gbps 3 prohibited
2:0:2 initiator cage1 0 valid private_loop 4Gbps 3 prohibited
cage5 1 valid private_loop 4Gbps 3 prohibited
2:1:1 target --- - --- n/a n/a n/a allowed
2:1:2 target --- - --- n/a n/a n/a allowed
2:2:1 initiator cage2 0 valid private_loop 4Gbps 3 prohibited
cage6 1 valid private_loop 4Gbps 3 prohibited
2:2:2 initiator cage3 0 valid private_loop 4Gbps 3 prohibited
cage7 1 valid private_loop 4Gbps 3 prohibited
2:2:3 target --- - --- fabric 4Gbps 3 allowed <-- Mode as target and Topology fabric
2:2:4 target --- - --- fabric 4Gbps 3 allowed <-- Mode as target and Topology fabric
3:0:1 initiator cage0 1 valid private_loop 4Gbps 3 prohibited
cage4 0 valid private_loop 4Gbps 3 prohibited
3:0:2 initiator cage1 1 valid private_loop 4Gbps 3 prohibited
cage5 0 valid private_loop 4Gbps 3 prohibited
3:1:1 target --- - --- n/a n/a n/a allowed
3:1:2 target --- - --- n/a n/a n/a allowed
3:2:1 initiator cage2 1 valid private_loop 4Gbps 3 prohibited
cage6 0 valid private_loop 4Gbps 3 prohibited
3:2:2 initiator cage3 1 valid private_loop 4Gbps 3 prohibited
cage7 0 valid private_loop 4Gbps 3 prohibited
3:2:3 target --- - --- fabric 4Gbps 3 allowed <-- Mode as target and Topology fabric
3:2:4 target --- - --- fabric 4Gbps 3 allowed <-- Mode as target and Topology fabric
--------------------------------------------------------------------
24
Subscribe to:
Post Comments (Atom)
2 comments:
Dear Pankaj,
THis post is awesome, very useful and it helped me sort out all my issues.
Since i was struggling to setup VSP and Smartstart. Even through smartstart 3PAR could not reach any hosts. But the L-Port issue and changing initiator to Target, i learnt and sorted only through your site. Even none of the HP 3PAR document did not talk about this. This is very handy.
Regards
Satheesh
Thanks Pankaj, your article really was great when I had this exact same issue on a brand new 3Par 7200. All FC ports came up as initiators and no matter what I did I could not get them to change to targets. All sorted now and saved me having to spend hours on the phone with HP whilst they diagnosed the issue.
Thanks for your time in putting this together.
Regards
Hugh
Post a Comment