How to create a boot lun in VMAX

Thanks for the reply.

We just need to create the luns in a normal way and then server team need to assign the lun to boot right.

There's no real distinction on the VMAX between a boot LUN and any other data LUN.  Create the symdev as you would any other device and mask it to the host.

The key difference is it becomes very important to know what your LUN # is.  You will need to point your host to the correct LUN ID in your HBA's BOOT BIOS in order to install your operating system on the right LUN.

We have some Host Connectivity guides on the support.emc.com site that cover this.  Depending on the OS and HBAs you're using the host-side instructions vary.

That's correct.  Create it and tell the storage team what you have for a LUN #.

If you're not sure of the LUN # you have set, run a 'symdev -sid show on the device and check the LUN IDs.

Here's an example of what it will look like, this is a partial symdev show output.  Under the LUN column you'll see SYMM and Host.

Use the Host LUN ID first unless it's N/A (not set), then use the SYMM LUN ID.  Also remember these values are in HEX.  In the example below, this device is LUN ID 03C on one path and 005 down the other.

Front Director Paths (2):

     {

     ----------------------------------------------------------------------

                              POWERPATH  DIRECTOR   PORT             LUN

                              --------- ----------  ---- -------- ---------

     PdevName                 Type      Type Num    Sts  VBUS TID SYMM Host

     ----------------------------------------------------------------------

     Not Visible              N/A       FA   11E:1  RW   000  00  03C N/A

     Not Visible              N/A       FA   06F:0  RW   000  00  005 N/A

     }

Thank you

I used this command

symaccess -sid -name -type storage add devs -lun

assigned it lun 0

Host field is never populated, i would use output from symaccess -sid 123 show view . There Host Lun # will actually match what the host can see, not what FA address that device is mapped to.

what server platform are you using ?

it does not matter what that id is, it's all about host id ...remember VMAX us doing dynamic lun masking by default. You can have device mapped to 0FF but as long as host id is 0, that's how the host is going to see it.

If you're going to be mapping/masking to multiple Directors which you should you need to mask with a consistent LUN ID. In the example provided by pete2c the Dev is masked to FAs 11E:1 & 6F:0 with the LUN IDs 03c and 005 respectively. Those LUN IDs are in HEX too, so you need to convert them to decimal (60 & 5).

Front Director Paths (2):

     {

     ----------------------------------------------------------------------

                              POWERPATH  DIRECTOR   PORT             LUN

                              --------- ----------  ---- -------- ---------

     PdevName                 Type      Type Num    Sts  VBUS TID SYMM Host

     ----------------------------------------------------------------------

     Not Visible              N/A       FA   11E:1  RW   000  00  03C N/A

     Not Visible              N/A       FA   06F:0  RW   000  00  005 N/A

I used the above command for Aix platform. But when i changed the lun id to 0, Server team are not able to see that.

Help me how to create a boot lun for Aix and windows platform

if i mapped device to 0FF, The device can be seen as boot lun

Hi kgoudus,

                 As dynamox said,host id is important.And you can not specify it .I generally allocate the boot lun as first lun to the host so that host id 0 would be reserved for that.You can get the host id by the command # symaccess -sid xxxx show view .Hope it helps.

Hi, we have some UCS Blades here, Server team has attached some ESX hosts to that blade ports. I have zoned them to VMAX. But i am not its logged into array. Can anyone help me to trouble shoot. Below is the output from vmax when i list logins

                            User-generated                      Logged On

Identifier       Type  Node Name        Port Name        FCID   In     Fabric

---------------- ----- --------------------------------- ------ ------ ------

20000025b511b10f Fibre xxxesx213       HBA2             9d0103 No     Yes

until OS is loaded it won't be logged-in

i want to create a boot lun as 2 way mirror. Do i need to create tdev's from pool or normal dev from diskgroup

Hi, we have some UCS Blades here, Server team has attached some ESX hosts to that blade ports. I have zoned them to VMAX. But i am not its logged into array. Can anyone help me to trouble shoot. Below is the output from vmax when i list logins

                            User-generated                      Logged On

Identifier       Type  Node Name        Port Name        FCID   In     Fabric

---------------- ----- --------------------------------- ------ ------ ------

20000025b511b10f Fibre xxxesx213       HBA2             9d0103 No     Yes