MSA2012i LUNs not visible

[jdudmesh]

I've got an MSA2012i which has had 6 disks and 3 LUNs running quite happily got the last 3 months.

Last week I hot added an additional 6 disks and 3 LUNs and although everything appears to be configured correctly, the LUNs are not visible to any of the iSCSI initiators I point at it. The original 3 LUNs are still visible and working correctly.

# show volumes
Vdisk Volume Name Size WR Policy Class
Volume Serial Number Cache Opt Type
-------------------------------------------------------------------------
vdisk1 vdisk1_V1 1000.1GB writeback standard
00c0ffd5bbe100007bdd4f4901000000 standard standard
vdisk1 vdisk1_V2 1000.1GB writeback standard
00c0ffd5bbe100007cdd4f4901000000 standard standard
vdisk1 vdisk1_V3 1000.1GB writeback standard
00c0ffd5bbe100007cdd4f4902000000 standard standard
vdisk2 vdisk2_V1 1000.1GB writeback standard
00c0ffd5bbe10000267dcb4901000000 standard standard
vdisk2 vdisk2_V2 1000.1GB writeback standard
00c0ffd5bbe10000277dcb4901000000 standard standard
vdisk2 vdisk2_V3 1000.1GB writeback standard
00c0ffd5bbe10000277dcb4902000000 standard standard
-------------------------------------------------------------------------

# show volume-map
Volume [SN 00c0ffd5bbe100007bdd4f4901000000, Name (vdisk1_V1)] mapping view:
CH ID LUN Access Host-Port-Identifier Nickname
-------------------------------------------------------------------------------
0,1 0 0 rw all other hosts

Volume [SN 00c0ffd5bbe100007cdd4f4901000000, Name (vdisk1_V2)] mapping view:
CH ID LUN Access Host-Port-Identifier Nickname
-------------------------------------------------------------------------------
0,1 0 1 rw all other hosts

Volume [SN 00c0ffd5bbe100007cdd4f4902000000, Name (vdisk1_V3)] mapping view:
CH ID LUN Access Host-Port-Identifier Nickname
-------------------------------------------------------------------------------
0,1 0 2 rw all other hosts

Volume [SN 00c0ffd5bbe10000267dcb4901000000, Name (vdisk2_V1)] mapping view:
CH ID LUN Access Host-Port-Identifier Nickname
-------------------------------------------------------------------------------
0,1 0 3 rw all other hosts

Volume [SN 00c0ffd5bbe10000277dcb4901000000, Name (vdisk2_V2)] mapping view:
CH ID LUN Access Host-Port-Identifier Nickname
-------------------------------------------------------------------------------
0,1 0 4 rw all other hosts

Volume [SN 00c0ffd5bbe10000277dcb4902000000, Name (vdisk2_V3)] mapping view:
CH ID LUN Access Host-Port-Identifier Nickname
-------------------------------------------------------------------------------
0,1 0 5 rw all other hosts



# show host-map
Host [IQN iqn.1998-01.com.vmware:mer-chassis1-blade1-esx-46b89acc, Name (mer-blade1)] Mapping View:
Volume Name Volume SN ID LUN Access Channels
----------------------------------------------------------------------------
vdisk1_V1 00c0ffd5bbe100007bdd4f4901000000 0 0 rw 0,1
vdisk1_V2 00c0ffd5bbe100007cdd4f4901000000 0 1 rw 0,1
vdisk1_V3 00c0ffd5bbe100007cdd4f4902000000 0 2 rw 0,1
vdisk2_V1 00c0ffd5bbe10000267dcb4901000000 0 3 rw 0,1
vdisk2_V2 00c0ffd5bbe10000277dcb4901000000 0 4 rw 0,1
vdisk2_V3 00c0ffd5bbe10000277dcb4902000000 0 5 rw 0,1

[Sivakumar MJ._1]

Check the HP Advisory.. if something helps you out..

[Sivakumar MJ._1]

Check the HP Advisory.. if something helps you out..

http://h20000.www2.hp.com/bizsupport/TechSupport/Document.jsp?lang=en&cc=us&taskId=110&prodSeriesId=3687128&prodTypeId=12169&objectID=c01470001

[jdudmesh]

I knew it had to be something simple!

That's fixed it - thanks very much.

[jdudmesh]

I should add that it was necessary to remap the volumes as all the mappings get deleted when the vdisk owner changes.

[Sivakumar MJ._1]

Hi Jdudmesh,

If you have found your solution.. Pls. close the thread...

[jdudmesh]

All sorted