cancel
Showing results for 
Search instead for 
Did you mean: 

MSA 2040 LUN 0

 
SOLVED
Go to solution
skyvo
Occasional Contributor

MSA 2040 LUN 0

Hi,
recently I've reconfigured all storage pools and I've started assigning volumes from LUN ID 1, leaving free LUN ID 0 , as suggested from some colleagues. Is this correct or not? I have this doubt because now, after a rescan, all hosts are still seeing a LUN 0 ID device for every other LUNs defined, but the reported device type is "enclosure", while other LUNs is rightly reported as "disk". What does it means?

2 REPLIES 2
StephenWagner7
Frequent Advisor
Solution

Re: MSA 2040 LUN 0


@skyvo wrote:

Hi,
recently I've reconfigured all storage pools and I've started assigning volumes from LUN ID 1, leaving free LUN ID 0 , as suggested from some colleagues. Is this correct or not? I have this doubt because now, after a rescan, all hosts are still seeing a LUN 0 ID device for every other LUNs defined, but the reported device type is "enclosure", while other LUNs is rightly reported as "disk". What does it means?


You did this correct. As per the "best practice configuration" document, you should not assign any volumes as LUN 0. What you are also observing is correct as the enclosure (controllers) will show up as LUN 0.

(The reason why you don't assign disks to LUN 0 is because the controller/enclosure is using LUN 0)

If you're running a VMware envioment, also make sure you change the "Missing LUN response" option from "Not Ready" to "Illegal Request".

Hope this helps!

Cheers!

skyvo
Occasional Contributor

Re: MSA 2040 LUN 0

Thank you very much