VMware Cloud Community
Jaune
Contributor
Contributor
Jump to solution

Can't mask a lun through Disk.MaskLUNs

I'm trying to mask luns from the ESX Host.

I tried with the following syntax:

vmhba1:0:0:1;

vmhba1:0:0;

vmhba1:0:0-1;

Is there any service to restart so the changes get effective?

Thanks

0 Kudos
1 Solution

Accepted Solutions
bertdb
Virtuoso
Virtuoso
Jump to solution

first of all, you're masking LUNs, and LUNs have three component names in ESX:

vmhbaA:B:C, where C is the LUN number.

Four component names are only there to identify a specific partition on a LUN, and that makes no sense in LUN masking.

But what's really breaking this for you, is that ESX doesn't support the masking of LUN 0. This was mentionned in the "known bugs" or "current issues" in ESX 2.1.something, but is still true as far as I know.

You can mask any other LUN number or range, but not 0.

View solution in original post

0 Kudos
4 Replies
bertdb
Virtuoso
Virtuoso
Jump to solution

first of all, you're masking LUNs, and LUNs have three component names in ESX:

vmhbaA:B:C, where C is the LUN number.

Four component names are only there to identify a specific partition on a LUN, and that makes no sense in LUN masking.

But what's really breaking this for you, is that ESX doesn't support the masking of LUN 0. This was mentionned in the "known bugs" or "current issues" in ESX 2.1.something, but is still true as far as I know.

You can mask any other LUN number or range, but not 0.

0 Kudos
biekee
Hot Shot
Hot Shot
Jump to solution

That might be true indeed. Just a question, why would you mask in ESX and not at the SAN itself by removing LUN0 from that specific server?

bk

Jaune
Contributor
Contributor
Jump to solution

Thanks guys, I'll look at that option instead, I'm just trying to do it from the esx since I'm not san admin... I'll send that to the san guy.

0 Kudos
Jaune
Contributor
Contributor
Jump to solution

Nevermind Its a 0...

Message was edited by:

Jaune

0 Kudos