Sun Storage 3510 FC Array
 
Sun Storage 3511 SATA Array
 

GCS>Sun Microsystems>Storage - Disk>Modular Disk - 3xxx Arrays
 

New LUN mapping on the Sun StorageTek[TM] 351x (SE3510 and SE3511) does not show up in format.

This is an example of a SE3510 operating in loop mode on the host channels.
Both controllers have target ID's assigned on channels 0,1,4 and 5.

All LUN mappings are assigned to the primary controller. Secondary controller has no mapped LUN's. Even the mandatory LUN 0 is missing. In this case the Secondary controller presents a SES device as LUN 0 to be in compliance with the SCSI standard.

luxadm_-e_dump_map_-devices-pci@9,600000-SUNW,qlc@1-fp@0,0:devctl.out

Pos AL_PA ID Hard_Addr Port WWN Node WWN Type

0 1 7d 0 210000e08b0ff5ec 200000e08b0ff5ec 0x1f (Unknown Type)
1 a7 28 a7 216000c0ff8051c7 206000c0ff0051c7 0x0 (Disk device)
2 2 7c 0 210000e08b107111 200000e08b107111 0x1f (Unknown Type,Host Bus Adapter)
3 a6 29 a6 216000c0ff9051c7 206000c0ff0051c7 0xd (SES device) <== SES device presented as LUN 0

luxadm_-e_dump_map_-devices-pci@9,600000-SUNW,qlc@2-fp@0,0:devctl.out

Pos AL_PA ID Hard_Addr Port WWN Node WWN Type

0 1 7d 0 210000e08b0f5ab0 200000e08b0f5ab0 0x1f (Unknown Type,Host Bus Adapter)
1 9f 2c 9f 256000c0ffc051c7 206000c0ff0051c7 0x0 (Disk device)
2 2 7c 0 210000e08b104d11 200000e08b104d11 0x1f (Unknown Type)
3 9e 2d 9e 256000c0ffd051c7 206000c0ff0051c7 0xd (SES device) <== SES device presented as LUN 0

The luxadm -e dump_map can be used to show the availability of all targets on FC-loop.

Then a new ld is created and assigned to the secondary controller. A new LUN mapping is added for the secondary controller.

show_channels.out

sccli: selected device /dev/rdsk/c2t40d0s2 [SUN StorEdge 3510 SN#0051C7]

Ch Type Media Speed Width PID / SID
--------------------------------------------

0 Host FC(L) 2G Serial 40 / 41
1 Host FC(L) 2G Serial 42 / 43
2 DRV+RCC FC(L) 2G Serial 14 / 15
3 DRV+RCC FC(L) 2G Serial 14 / 15
4 Host FC(L) 2G Serial 44 / 45
5 Host FC(L) 2G Serial 46 / 47
6 Host LAN N/A Serial N/A / N/A

show_lun-maps.out

sccli: selected device /dev/rdsk/c2t40d0s2 [SUN StorEdge 3510 SN#0051C7]

Ch Tgt LUN ld/lv ID-Partition Assigned Filter Map
---------------------------------------------------------------------

0 40 0 ld0 197989FA-00 Primary
0 40 1 ld0 197989FA-01 Primary
0 41 0 ld4 0F749DCC-01 Secondary <== new mapping
1 42 0 ld0 197989FA-00 Primary
1 42 1 ld0 197989FA-01 Primary

:::::

4 45 0 ld4 0F749DCC-01 Secondary <== new mapping
5 46 0 ld0 197989FA-00 Primary
5 46 1 ld0 197989FA-01 Primary

:::::

This newly mapped LUN does not show up in format. The luxadm -e dump_map command can be used to show the availability of all targets on the FC-loop. The secondary controller is seen on the loop.

luxadm_-e_dump_map_-devices-pci@9,600000-SUNW,qlc@1-fp@0,0:devctl.out

Pos AL_PA ID Hard_Addr Port WWN Node WWN Type

0 1 7d 0 210000e08b0ff5ec 200000e08b0ff5ec 0x1f (Unknown Type)
1 a7 28 a7 216000c0ff8051c7 206000c0ff0051c7 0x0 (Disk device)
2 2 7c 0 210000e08b107111 200000e08b107111 0x1f (Unknown Type,Host Bus Adapter)
3 a6 29 a6 216000c0ff9051c7 206000c0ff0051c7 0xd (SES device) <== secondary still presenting a SES device

luxadm_-e_dump_map_-devices-pci@9,600000-SUNW,qlc@2-fp@0,0:devctl.out

Pos AL_PA ID Hard_Addr Port WWN Node WWN Type

0 1 7d 0 210000e08b0f5ab0 200000e08b0f5ab0 0x1f (Unknown Type,Host Bus Adapter)
1 9f 2c 9f 256000c0ffc051c7 206000c0ff0051c7 0x0 (Disk device)
2 2 7c 0 210000e08b104d11 200000e08b104d11 0x1f (Unknown Type)
3 9e 2d 9e 256000c0ffd051c7 206000c0ff0051c7 0xd (SES device) <== secondary still presenting SES device

While luxadm -e dump_map can be used to show the availability of all targets on the FC-loop, cfgadm can be used to show all available LUN mappings (see command options used in steps below).

Ap_Id Type Receptacle Occupant Condition

::::

c2 fc-private connected configured unknown
c2::210000e08b0ff5ec unknown connected unconfigured unknown
c2::216000c0ff8051c7,0 disk connected configured unknown
c2::216000c0ff8051c7,1 disk connected configured unknown

::::

c2::216000c0ff9051c7,0 disk connected configured unknown <== secondary new LUN 0

c3 fc-private connected configured unknown
c3::210000e08b104d11 unknown connected unconfigured unknown
c3::256000c0ffc051c7,0 disk connected configured unknown
c3::256000c0ffc051c7,1 disk connected configured unknown

::::

c3::256000c0ffd051c7,0 disk connected configured unknown <== secondary new LUN 0

To make the new LUN visible in format the ssd driver needs to rescan the LUN mapping. The ssd driver has to issue a "REPORT LUNS" SCSI command to the secondary controller which can be forced with a LIP. The LIP can be forced with:

# luxadm -e forcelip /dev/cfg/c2
# luxadm -e forcelip /dev/cfg/c3

General steps after mapping new LUNs

1. Check for the new LUN using the commands listed below:

- luxadm -e dump_map /dev/cfg/cx use the controller number listed in cfgadm

(this command lists all targets available on the FC-loop)

- cfgadm -al -o show_SCSI_LUN or show _FCP_dev in older releases

(this command shows all LUN's available)

- format

2. Check syslog file for additional information

3. use luxadm -e forcelip /dev/cfg/cx to force a LIP and a rescan of the mapped LUNs

4. Recheck for the new LUN using

- cfgadm -al -o show_SCSI_LUN or show _FCP_dev in older releases

- format

If You can see the disk in format you are finished.

5. Check syslog file for additional information

6. Run devfsadm manually. devfsadm maintains the /dev and /devices namespaces.

7. Recheck for the new LUN using:

- cfgadm -al -o show_SCSI_LUN or show _FCP_dev in older releases

- format

If You can see the disk in format you are finished.

8. Check syslog file for additional information

9. Unplug/plug the FC connections to force a rescan of the mapped LUNs

This operation is disruptive and requires a scheduled downtime for single path configurations.

10. Recheck for the new LUN using:

- cfgadm -al -o show_SCSI_LUN or show _FCP_dev in older releases

- format

If You can see the disk in format you are finished.

11. Check syslog file for additional information.

12. At this point a reconfiguration boot may be considered.

This solution has no attachment