MSA2000 and LUN 0

[Michael Grech]

Not sure if this is the correct forum, but I have an MSA 2000 divided into 3 logical drives. VMWare ESXi4 see's all three logical drives and says they are all in LUN 0. I need to configure a different LUN ID's for each drive. Any idea's? The hardware is a GL360 G5 with a p800 controller attached to the MSA2000 (25 - 146GB drives). Thanks.

[Uwe Zessin]

Can you provide a screenshot
(simple .JPG - if multiple in a .ZIP archive -- no .doc[x], please)?
Or run a "vicfg-mpath -l > mpath.txt" and load the file up as an attachmed?

[Bert Zefat]

LUN 0 is a control LUN. This is the LUN any system "sees" if it has connection (direct of via a SAN switch) to a SCSI (SAN) deivice. You should change the access and LUN ID on the Volumes you want to present to your hosts. Make sure all your ESX hosts see the same Volume with the same LUN ID (starting with LUN ID 1). You should set the ESX multipathing to fixed for an MSA2000.

[Bill Costigan]

You probably have Selective Storage Presentation enabled on the MSA which prevents hosts from seeing the actual LUNs unless you specifically configure the MSA to allow them to see the LUNs.

In SSP you should see the WWNs of the ESX HBAs. Select the correct OS for ESX on each WWN and check the LUNs it should see. After saving the config on the MSA go back and rescan the HBAs on the ESX hosts.