Get solaris to reconize new disk’s

Find the controler number that the HBA is using using.  The C$ is the controller number

cfgadm -al

please note, this is a lot more devices then most people would have

# cfgadm -al
Ap_Id                          Type         Receptacle   Occupant     Condition
c0                             scsi-bus     connected    configured   unknown
c0::dsk/c0t0d0                 CD-ROM       connected    configured   unknown
c1                             fc-private   connected    configured   unknown
c1::500000e010ad1f11           disk         connected    configured   unknown
c1::500000e010ad2011           disk         connected    configured   unknown
c2                             scsi-bus     connected    configured   unknown
c2::lus9                       unknown      connected    configured   unknown
c3                             scsi-bus     connected    configured   unknown
c3::lus10                      unknown      connected    configured   unknown
c4                             scsi-bus     connected    configured   unknown
c4::lus11                      unknown      connected    configured   unknown
c5                             scsi-bus     connected    configured   unknown
c5::lus12                      unknown      connected    configured   unknown
c6                             fc-fabric    connected    configured   unknown
c6::2101000d77bdf35a           disk         connected    unconfigured unknown
c6::500104f000600b7b           tape         connected    configured   unknown
c7                             fc-fabric    connected    configured   unknown
c7::2101000d77bdf15a           disk         connected    unconfigured unknown
c7::500104f000600b7e           tape         connected    configured   unknown
c7::500104f000600b84           tape         connected    configured   unknown
c7::5006016130601ac1           disk         connected    configured   unknown
c7::5006016830601ac1           disk         connected    configured   unknown
c8                             fc-fabric    connected    configured   unknown
c8::2103000d77fd8f5a           disk         connected    unconfigured unknown
c8::500104f000600b8d           tape         connected    configured   unknown
c8::500104f000600ba2           tape         connected    configured   unknown
c9                             fc-fabric    connected    configured   unknown
c9::2101000d77bd8f5a           disk         connected    unconfigured unknown
c9::500104f000600b81           tape         connected    configured   unknown
c9::500104f000600b87           tape         connected    configured   unknown
c9::5006016030601ac1           disk         connected    configured   unknown
c9::5006016930601ac1           disk         connected    configured   unknown
usb0/1                         unknown      empty        unconfigured ok
usb0/2                         unknown      empty        unconfigured ok
usb0/3                         unknown      empty        unconfigured ok
usb0/4                         unknown      empty        unconfigured ok

Rescan the HBA using cfgadm


cfgadm -c configure c$

Then run devfsadm -C to create the devicenodes for your newly discovered targets. 

Run format to verify that the new disks show up in the list – You should see four paths for each device as long as you have dual pathing on each of two controllers. 

Format output, snipet

–snip–

      26. c9t5006016930601AC1d5
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016930601ac1,5
27. c9t5006016030601AC1d5
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016030601ac1,5
28. c9t5006016030601AC1d6
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016030601ac1,6
29. c9t5006016930601AC1d6
/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w5006016930601ac1,6
30. emcpower0a
/pseudo/emcp@0
31. emcpower1a
/pseudo/emcp@1
32. emcpower2a
/pseudo/emcp@2
33. emcpower3a
/pseudo/emcp@3
34. emcpower4a
/pseudo/emcp@4
35. emcpower5a
/pseudo/emcp@5
If you can see the disks in format you could start using them right away.  You should always use power path and not the direct path because if you do you will not be taking advantage of the power pathing benfits of EMC powerpath.

Run the fowling command to clear out old and dead paths to devices

/etc/powercf -q and /etc/powermt check

To discover and new dievices
/etc/powermt config

- Run /etc/powermt display dev=all and verify that you now have a new emcpower device that points to the LUN ID you configured on the EMC.

run the fowling command to verify that you see all path’s.

/etc/powermt display dev=all

 # /etc/powermt display dev=all
Pseudo name=emcpower4a
CLARiiON ID=APM00050704294 [nepuinf020]
Logical device ID=600601606032140044F6BCBAB53DDB11 [LUN 322]
state=alive; policy=CLAROpt; priority=0; queued-IOs=0
Owner: default=SP A, current=SP A
==============================================================================
—————- Host —————   – Stor –   — I/O Path –  — Stats —
### HW Path                 I/O Paths    Interf.   Mode    State  Q-IOs Errors
==============================================================================
3074 pci@8/SUNW,qlc@3          c7t5006016130601AC1d2s0 SP A1     active  alive      0      1
3074 pci@8/SUNW,qlc@3          c7t5006016830601AC1d2s0 SP B0     active  alive      0      1
3076 pci@8/SUNW,qlc@2          c9t5006016030601AC1d2s0 SP A0     active  alive      0      1
3076 pci@8/SUNW,qlc@2          c9t5006016930601AC1d2s0 SP B1     active  alive      0      1

–Snip–

Now finish partitioning the disk using the format utility.