Friday, March 21, 2014

Ephraim Iverson: How do I locate an IBM FC hba and driver from an EMC GRAB or AIX console

To find the IBM part number and driver level used to identify what HBA you are using and driver loaded, do the following:

1. run lscfg-vp at the AIX console or locate the lscfg -vp file in the EMC grab
2. In the output locate the fcs you wish to identify.
3. locate the customer card ID number, for the HBA type and the (Z9) for the driver number.

fcs6             U5796.001.1028194-P1-C4-T1                                      FC Adapter

        Part Number.................10N8620
        Serial Number...............1B84XXXXXX
        Manufacturer................001B
        EC Level....................D76625
        Customer Card ID Number.....5759
        FRU Number.................. 10N8620
        Device Specific.(ZM)........3
        Network Address.............10000000CXXXXXXX
        ROS Level and ID............02C8277A
        Device Specific.(Z0)........1036406D
        Device Specific.(Z1)........00000000
        Device Specific.(Z2)........00000000
        Device Specific.(Z3)........03000909
        Device Specific.(Z4)........FFC01231
        Device Specific.(Z5)........02C8277A
        Device Specific.(Z6)........06C12715
        Device Specific.(Z7)........07C1277A
        Device Specific.(Z8)........20000000C9XXXXXXX
        Device Specific.(Z9)........BS2.71X10
        Device Specific.(ZA)........B1F2.70A5
        Device Specific.(ZB)........B2F2.71X10
        Device Specific.(ZC)........00000000
        Hardware Location Code......U5796.001.1028194-P1-C4-T1





By: Ephraim Iverson, Storage Architect
Posted by at No comments:
Labels:
Location: Bristol, Bristol

Wednesday, March 12, 2014

How to connect (2) XIV storage systems to a Dual Fabric SAN


By: Ephraim Iverson





Storage Hostname PORT CONFIG SAN Switch Switch Slot







XIV_02 1:FC_Port:4:1 Target F1-CORE 1:4

XIV_02 1:FC_Port:4:2 Target


XIV_02 1:FC_Port:4:3 Target F2-CORE 1:4

XIV_02 1:FC_Port:4:4 Initiator


XIV_02 1:FC_Port:5:1 Target F1-CORE 1:24

XIV_02 1:FC_Port:5:2 Target


XIV_02 1:FC_Port:5:3 Target F2-CORE 1:24

XIV_02 1:FC_Port:5:4 Initiator


XIV_02 1:FC_Port:6:1 Target F1-CORE 2:4

XIV_02 1:FC_Port:6:2 Target


XIV_02 1:FC_Port:6:3 Target F2-CORE 2:7

XIV_02 1:FC_Port:6:4 Initiator


XIV_02 1:FC_Port:7:1 Target F1-CORE 2:7

XIV_02 1:FC_Port:7:2 Target


XIV_02 1:FC_Port:7:3 Target F2-CORE 2:4

XIV_02 1:FC_Port:7:4 Initiator


XIV_02 1:FC_Port:8:1 Target F1-CORE 3:13

XIV_02 1:FC_Port:8:2 Target


XIV_02 1:FC_Port:8:3 Target F2-CORE 3:13

XIV_02 1:FC_Port:8:4 Initiator


XIV_02 1:FC_Port:9:1 Target F1-CORE 3:4

XIV_02 1:FC_Port:9:2 Target


XIV_02 1:FC_Port:9:3 Target F2-CORE 3:4

XIV_02 1:FC_Port:9:4 Initiator








XIV_01 1:FC_Port:4:1 Target F1-CORE 1:11

XIV_01 1:FC_Port:4:2 Target


XIV_01 1:FC_Port:4:3 Target F2-CORE 1:11

XIV_01 1:FC_Port:4:4 Initiator


XIV_01 1:FC_Port:5:1 Target F1-CORE 1:28

XIV_01 1:FC_Port:5:2 Target


XIV_01 1:FC_Port:5:3 Target F2-CORE 1:28

XIV_01 1:FC_Port:5:4 Initiator


XIV_01 1:FC_Port:6:1 Target F1-CORE 1:22

XIV_01 1:FC_Port:6:2 Target


XIV_01 1:FC_Port:6:3 Target F2-CORE 1:22

XIV_01 1:FC_Port:6:4 Initiator


XIV_01 1:FC_Port:7:1 Target F1-CORE 2:22

XIV_01 1:FC_Port:7:2 Target


XIV_01 1:FC_Port:7:3 Target F2-CORE 2:22

XIV_01 1:FC_Port:7:4 Initiator


XIV_01 1:FC_Port:8:1 Target F1-CORE 3:31

XIV_01 1:FC_Port:8:2 Target


XIV_01 1:FC_Port:8:3 Target F2-CORE 3:6

XIV_01 1:FC_Port:8:4 Initiator


XIV_01 1:FC_Port:9:1 Target F1-CORE 3:28

XIV_01 1:FC_Port:9:2 Target


XIV_01 1:FC_Port:9:3 Target F2-CORE 3:28

XIV_01 1:FC_Port:9:4 Initiator







Posted by at No comments:
Labels:
Location: Bristol, Bristol

Tuesday, February 25, 2014

Ephraim Iverson : Migrate EMC Data to Virtualized Storage on an IBM SVC

Command Execution Script by Ephraim Iverson, Storage Architect

***        EMC Storage frame targeted HOST device side work

 1.) Verify cabling request with facilities, and request cables to be moved
 
2.) Confirm HBA WWPN online in SAN port per design and activate pre-staged SAN zoning of HOST to SVC

 3.) Mask targeted Device to SVC port. = = => Use command line( Symcli ) for masking.
 
 symmask -sid "Frame_ID" –wwn xxxx add dev xxxx –dir 8b –p 1   ===> See

Host LUN mapping for all detail
  
symmask -sid "Frame_ID" –wwn xxxx add dev xxxx –dir 9B –p 1   ===> See Host

LUN mapping for all detail
  
symmask -sid "Frame_ID" refresh

  Notes Yes, mask all 16 WWPN per each fabric to every devices, See tab EMC_Symcli for detail

 SPECIAL UNMASKING NEED for VSCSI Client since we are only moving client buy client.
    * * * * *   = = = > See tab Specail UNMasK for the detail
 1.) Unmask SAN LUN from Current/OLD HBA WWPN

***        SVC targeted HOST LUN side work
 1.) start putty session in to SVC
 a.) List mdisk already on this svc ===> svcinfo lsmdisk -filtervalue name=mdisk*
 b.) note down all existing mdisk name
 c.) discover the new mdisk ===> svctask discovermdisk
 d.) Document the unmanage Mdisk name into the Host_LUN Mapping tab

 NOTES PLEASE MAKE SURE YOU UPDATE HOST/SERVER's CLI_SCRIPT ACCORDINGLY

 2.) Execute Host/Server's SVC CLI Script ===> See tab " EMC_CLI_Script " for detail
 Here is a sample only of the SVC CLI script.

 #Create host entry with dummy WWPN
 #
 svctask mkhost -name server01 -force -hbawwpn 2000000000000000 -mask 1111
 #Create Image Mode MDG
 #
 svctask mkmdiskgrp -name IMGGRP -ext 512
 #Create FC Consistency Group
 #
 svctask mkfcconsistgrp -name SRV01_FCG -autodelete

 #Create Image Mode VDISK from unmanaged MDISK, FC Targets, FCunmap, and VDISK-host unmap
 #
 svctask mkvdisk -mdiskgrp IMGGRP -iogrp 1 -vtype image -mdisk mdisk23 -name SRV01_IMG_004
 
svctask addvdiskcopy -mdiskgrp T02G004DS8VA100 SRV01_IMG_004
 
svctask splitvdiskcopy -copy 1 -iogrp 0 -name server01_004 -force SRV01_IMG_004

 svctask mkfcmap -source SRV01_IMG_004 -target server01_004 -name SRV01_FMP_004 -consistgrp SRV01_FCG -copyrate 75 -autodelete
 
svctask mkvdiskhostmap -host server01 server01_004

 #Prep and Start FC
 #
 svctask startfcconsistgrp -prep SRV01_FCG

 #Add actual WWPNs and remove dummy to effectively unmap all 30 luns in single step.
 
svctask addhostport -force -hbawwpn <WWPN> server01
 
svctask rmhostport -hbawwpn 2000000000000000 server01

 NOTES ONCE DONE, LET SA COMPLETE THEIR WORK AND SCAN FOR THE SAN LUN

***        BACKOUT PLAN!
 1.) Disable server access to SAN on SVC
 2.) Remask SAN LUN to Current/OLD HBA

***        VERFICATION

 1) To check to see if host was created run
  svcinfo lshost [hostname]

 2) To check to see if mdiskgroup was created
  svcinfo lsmdiskgrp

 3) To check to see if image vdisks were created
  svcinfo lsvdisk -filtervalue type=image

 4) To check to see if target vdisks were created
  svcinfo lsvdisk -filtervalue name=[targetvdisk]*

 5) To check to see if flashcopy mappings were created/check status
  svcinfo lsfcmap

 6) To check to see if flashcopy consistency group was created
  svcinfo lsfcconsistgrp

 7) To check discovery status of detectmdisk
  svcinfo lsdiscoverystatus

Posted by at No comments:
Labels:
Location: Bristol, Bristol

Sunday, February 23, 2014

Ephraim Iverson : Connecting an 8 node SVC to a Dual Fabric Environment


When connecting an SVC with 8 nodes to a dual fabric environment. This is how each port should be connected to the fabric. F1-Core= A Fabric and F2-Core=B Fabric



fc_io_port_id node_id node_name status Switch \ Fabric
1 18 node1 active F1-CORE
2 18 node1 active F2-CORE
3 18 node1 active F1-CORE
4 18 node1 active F2-CORE
5 18 node1 inactive_unconfigured
6 18 node1 inactive_unconfigured
7 18 node1 inactive_unconfigured
8 18 node1 inactive_unconfigured
1 7 node2 active F1-CORE
2 7 node2 active F2-CORE
3 7 node2 active F1-CORE
4 7 node2 active F2-CORE
5 7 node2 inactive_unconfigured
6 7 node2 inactive_unconfigured
7 7 node2 inactive_unconfigured
8 7 node2 inactive_unconfigured
1 11 node3 active F1-CORE
2 11 node3 active F2-CORE
3 11 node3 active F1-CORE
4 11 node3 active F2-CORE
5 11 node3 inactive_unconfigured
6 11 node3 inactive_unconfigured
7 11 node3 inactive_unconfigured
8 11 node3 inactive_unconfigured
1 12 node4 active F1-CORE
2 12 node4 active F2-CORE
3 12 node4 active F1-CORE
4 12 node4 active F2-CORE
5 12 node4 inactive_unconfigured
6 12 node4 inactive_unconfigured
7 12 node4 inactive_unconfigured
8 12 node4 inactive_unconfigured
1 13 node5 active F1-CORE
2 13 node5 active F2-CORE
3 13 node5 active F1-CORE
4 13 node5 active F2-CORE
5 13 node5 inactive_unconfigured
6 13 node5 inactive_unconfigured
7 13 node5 inactive_unconfigured
8 13 node5 inactive_unconfigured
1 14 node6 active F1-CORE
2 14 node6 active F2-CORE
3 14 node6 active F1-CORE
4 14 node6 active F2-CORE
5 14 node6 inactive_unconfigured
6 14 node6 inactive_unconfigured
7 14 node6 inactive_unconfigured
8 14 node6 inactive_unconfigured
1 15 node7 active F1-CORE
2 15 node7 active F2-CORE
3 15 node7 active F1-CORE
4 15 node7 active F2-CORE
5 15 node7 inactive_unconfigured
6 15 node7 inactive_unconfigured
7 15 node7 inactive_unconfigured
8 15 node7 inactive_unconfigured
1 19 node8 active F1-CORE
2 19 node8 active F2-CORE
3 19 node8 active F1-CORE
4 19 node8 active F2-CORE
5 19 node8 inactive_unconfigured
6 19 node8 inactive_unconfigured
7 19 node8 inactive_unconfigured
8 19 node8 inactive_unconfigured


By: Ephraim Iverson, Storage Architect



Posted by at No comments:
Labels: , ,
Location: Bristol, Bristol

Ephraim Iverson : Mapping an XIV device to the SVC mdisks


By: Ephraim Iverson

XIV device name is vol_# with a lun mapping of the number in the serial number column. When discovered  by the SVC the mdisk is created the serial number appears in the mdisk UID number



Lun Name Capacity Serial Number Serial convert to HEX Target Hosts Target mdisk Number ( if Applicable ) SVC assigned UID
vol_001 2185 7 7 SVC02 mdisk16 17380051040007000000000000000000000000000000000000000000000000
vol_002 2185 8 8 SVC02 mdisk17 17380051040008000000000000000000000000000000000000000000000000
vol_003 2185 9 9 SVC02 mdisk18 17380051040009000000000000000000000000000000000000000000000000
vol_004 2185 10 A SVC02 mdisk41 1738005104000a000000000000000000000000000000000000000000000000
vol_005 2185 11 B SVC02 mdisk42 1738005104000b000000000000000000000000000000000000000000000000
vol_006 2185 12 C SVC02 mdisk44 1738005104000c000000000000000000000000000000000000000000000000
vol_007 2185 13 D SVC02 mdisk28 1738005104000d000000000000000000000000000000000000000000000000
Posted by at No comments:
Labels: ,
Location: Bristol, Bristol
Subscribe to: Posts (Atom)