UNSOLVED

AdrianG2

updated

17 years ago

A

AdrianG2

4 Posts

0

1425

April 8th, 2010 22:00

Symmetrix Lun offset

Hi,

COuld you please help me how i'm going to apply the lun offset for this exsting masking. DIR to be used is 7aa which has the last LUN ID is 135(hex). I will add 3 more devices on this server. What is the offset and base? What is the exact command for using lun offset?

Sym Dev                                               LUN
Name    Dir:P  Physical Device Name     VBUS  TID  SYMM HOST  Attr  Cap(MB)
------  -----  -----------------------  ----  ---  ---- ----  ----  -------
0543     7A:0  Not Visible                 0    0    1  N/A   (M)     36866
0545     7A:0  Not Visible                 0    0    2  N/A   (M)     36866
0547     7A:0  Not Visible                 0    0    3  N/A   (M)     36866
0549     7A:0  Not Visible                 0    0    4  N/A   (M)     36866
054B     7A:0  Not Visible                 0    0    5  N/A   (M)     36866
054D     7A:0  Not Visible                 0    0    6  N/A   (M)     36866
054F     7A:0  Not Visible                 0    0    7  N/A   (M)     36866
0551     7A:0  Not Visible                 0    0    8  N/A   (M)     36866
0553     7A:0  Not Visible                 0    0    9  N/A   (M)     36866
0555     7A:0  Not Visible                 0    0    a  N/A   (M)     36866
0557     7A:0  Not Visible                 0    0    b  N/A   (M)     36866
0559     7A:0  Not Visible                 0    0    c  N/A   (M)     36866
055B     7A:0  Not Visible                 0    0    d  N/A   (M)     36866
055D     7A:0  Not Visible                 0    0    e  N/A   (M)     36866
055F     7A:0  Not Visible                 0    0    f  N/A   (M)     36866
0561     7A:0  Not Visible                 0    0   10  N/A   (M)     36866
088C     7A:0  Not Visible                 0    0   11  N/A             513
08FA     7A:0  Not Visible                 0    0   12  N/A   (M)     36866
08FC     7A:0  Not Visible                 0    0   13  N/A   (M)     36866
08FE     7A:0  Not Visible                 0    0   14  N/A   (M)     36866
0900     7A:0  Not Visible                 0    0   15  N/A   (M)     36866
0902     7A:0  Not Visible                 0    0   16  N/A   (M)     36866
0904     7A:0  Not Visible                 0    0   17  N/A   (M)     36866
0906     7A:0  Not Visible                 0    0   18  N/A   (M)     36866
0908     7A:0  Not Visible                 0    0   19  N/A   (M)     36866
090A     7A:0  Not Visible                 0    0   1a  N/A   (M)     36866
090C     7A:0  Not Visible                 0    0   1b  N/A   (M)     36866
090E     7A:0  Not Visible                 0    0   1c  N/A   (M)     36866
0910     7A:0  Not Visible                 0    0   1d  N/A   (M)     36866
0E93     7A:0  Not Visible                 0    0   4d  N/A   (M)     36866
0E95     7A:0  Not Visible                 0    0   4e  N/A   (M)     36866
0E97     7A:0  Not Visible                 0    0   4f  N/A   (M)     36866

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    460

    0

    Posted April 9th, 2010 04:00

    Adrian,

    what are trying to achieve/fix by using lun offset ? Does your host require that you have contiguous symdev and no holes in the middle ?

  • modaslam

    2 Intern

    •

    217 Posts

    460

    0

    Posted April 9th, 2010 04:00

    in this case you can use Dynamic LUN Addressing. I have  Tech document about DLA. Don't remember from where did I get it.  let me search for that.

  • modaslam

    2 Intern

    •

    217 Posts

    461

    0

    Posted April 9th, 2010 04:00

  • modaslam

    2 Intern

    •

    217 Posts

    342

    0

    Posted April 9th, 2010 04:00

    AdrianG,

    Welcome to the Forum !!!

  • AdrianG2

    4 Posts

    460

    0

    Posted April 9th, 2010 04:00

    HI Dynamox,

    This is a windows server and FA's being use by this host are all for windows OS. but the LUN SYMM ID is already beyond ff, 135 is the last LUN, which i believe will no be visible on the hostside. Don't have any FA's available as the have same scenario LUN's beyond FF. My option is todo a luns offset, and this is my first time to try.

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    461

    0

    Posted April 9th, 2010 07:00

    Adrian,

    in one of those threads i shared my experience enabling DLA on an existing host, i had disastrous results.  YMMV

    as far as enabling offset you can follow this article emc109921

  • AdrianG2

    4 Posts

    461

    0

    Posted April 9th, 2010 09:00

    Thanks Dynamox, given on the output below, i see there's a gap symm dev 0910 and 0E93. Can you tell me if the command below is correct. the available SYMM LUN ID on 7aa start with 135

    symmask -sid -wwn set lunoffset on 135 1E -dir 7a -p 0,  also if 3 devices will be added how can i put range?

    Name    Dir:P  Physical Device Name     VBUS  TID  SYMM HOST  Attr  Cap(MB)
    ------  -----  -----------------------  ----  ---  ---- ----  ----  -------
    0543     7A:0  Not Visible                 0    0    1  N/A   (M)     36866
    0545     7A:0  Not Visible                 0    0    2  N/A   (M)     36866
    0547     7A:0  Not Visible                 0    0    3  N/A   (M)     36866
    0549     7A:0  Not Visible                 0    0    4  N/A   (M)     36866
    054B     7A:0  Not Visible                 0    0    5  N/A   (M)     36866
    054D     7A:0  Not Visible                 0    0    6  N/A   (M)     36866
    054F     7A:0  Not Visible                 0    0    7  N/A   (M)     36866
    0551     7A:0  Not Visible                 0    0    8  N/A   (M)     36866
    0553     7A:0  Not Visible                 0    0    9  N/A   (M)     36866
    0555     7A:0  Not Visible                 0    0    a  N/A   (M)     36866
    0557     7A:0  Not Visible                 0    0    b  N/A   (M)     36866
    0559     7A:0  Not Visible                 0    0    c  N/A   (M)     36866
    055B     7A:0  Not Visible                 0    0    d  N/A   (M)     36866
    055D     7A:0  Not Visible                 0    0    e  N/A   (M)     36866
    055F     7A:0  Not Visible                 0    0    f  N/A   (M)     36866
    0561     7A:0  Not Visible                 0    0   10  N/A   (M)     36866
    088C     7A:0  Not Visible                 0    0   11  N/A             513
    08FA     7A:0  Not Visible                 0    0   12  N/A   (M)     36866
    08FC     7A:0  Not Visible                 0    0   13  N/A   (M)     36866
    08FE     7A:0  Not Visible                 0    0   14  N/A   (M)     36866
    0900     7A:0  Not Visible                 0    0   15  N/A   (M)     36866
    0902     7A:0  Not Visible                 0    0   16  N/A   (M)     36866
    0904     7A:0  Not Visible                 0    0   17  N/A   (M)     36866
    0906     7A:0  Not Visible                 0    0   18  N/A   (M)     36866
    0908     7A:0  Not Visible                 0    0   19  N/A   (M)     36866
    090A     7A:0  Not Visible                 0    0   1a  N/A   (M)     36866
    090C     7A:0  Not Visible                 0    0   1b  N/A   (M)     36866
    090E     7A:0  Not Visible                 0    0   1c  N/A   (M)     36866
    0910     7A:0  Not Visible                 0    0   1d  N/A   (M)     36866
    0E93     7A:0  Not Visible                 0    0   4d  N/A   (M)     36866
    0E95     7A:0  Not Visible                 0    0   4e  N/A   (M)     36866
    0E97     7A:0  Not Visible                 0    0   4f  N/A   (M)     36866

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    461

    0

    Posted April 9th, 2010 10:00

    the issue that i see is that you can only do one lun offset per HBA so in your case you will be able to skip 000-01D and add devices up to 04D. I am assuming that right now 7A:0 can only take devices above 0FF , so for this box you would need to skip another hole but you can't because you can only do it once. I would bite the bullet, schedule downtime for this box and implement dynamic Lun masking. According to this technote you should be able to implement dynamic lun masking on an existing host, it should not mess with existing mapping and should skip the address that's already assigned to the HBA via regular masking.  When i did that on a windows box that was online, it completly hosed the box. I had to reboot it and it was fine after that. I am sure if i had the box down and i presented new devices via DLA it would probably be fine.

    https://powerlink.emc.com/nsepn/webapps/btg548664833igtcuup4826/km/live1//en_US/Offering_Technical/Technical_Documentation/300-005-734.pdf

  • modaslam

    2 Intern

    •

    217 Posts

    360

    0

    Posted April 9th, 2010 13:00

    Dynamox,

    Is this only happens to windows box, Why do we need the host down to be down when we use –dynamic_lun option.?, is it only for the first time?

    we have Solaris 8 box in our environment and now we dont have LUN ID's less than FF. we are planing to use DLA. we already have storage allocated.(ie static Lun ids)

    I was just planing to use –dynamic_lun will the masking step to use DLA features.

  • modaslam

    2 Intern

    •

    217 Posts

    342

    0

    Posted April 9th, 2010 13:00

    dynamox wrote:

    Adrian,

    in one of those threads i shared my experience enabling DLA on an existing host, i had disastrous results.  YMMV

    as far as enabling offset you can follow this article emc109921

    dynamox,

    Can you post the url of the thread which you shared the experience. the thread which I have posted cycles to the same thread.