UNSOLVED

drake2

updated

15 years ago

D

drake2

44 Posts

0

1234

April 20th, 2012 11:00

Linux - max luns

Hello, had a slight issue with Linux (RH5.5) not seeing LUN IDs over the default 256 on a Qlogic card.  I now understand that this HBA parameter can be changed to allow IDs above 256.  MAX LUNs parameter setting.

The question I have I have is if anyone is aware of any caveats or issues adjusting an HBA above this default value?

  • KD8EWE

    2 Intern

    •

    155 Posts

    618

    0

    Posted April 20th, 2012 12:00

    You do not have to change Qlogic Card settings,(you can if you want to)  You can map devices manually give Lun id as 001, 002, and try to map and mask. it works.

  • drake2

    44 Posts

    618

    0

    Posted April 20th, 2012 13:00

    Dymox thanks.  From being new to symmetrix and what little reading I have done on dynamic lun masking just now, it does seem like a resonable solution.  I was discussing this issues and your idea with the linux admin and he mentions the ease of groupings and device mangement as they relate to veritas/bcvs/clones etc, for one as they are now and then device tracking going forward.  So short of adding this additional layer this is why the questions revolving around the max lun setttings.  I thank you for your advice, but simply am curious to bumping the max luns above the recommended 256.  Again simply what if any trouble might result.  We assume this would be fine and will most likely test. I was just seeing if the commuity had any experience with this.

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    618

    1

    Posted April 20th, 2012 13:00

    how about using dynamic lun masking ? Lun number will start at 0 regardless of what the physical address is on the FA

  • drake2

    44 Posts

    618

    0

    Posted April 20th, 2012 13:00

    Hopefully I am explaining this correctly.  Chances of a host actually having over 256 devices would be rare if at all for us however with several hundred devices sharing a particular FA port on the Symmetrix the IDs can and in our case did hexidecimally represent themselves with a value above 256.  It is evident that the value of the ID in decimal is the issue not the necessarily only the number of actual devices.

    Example.  Device 0D2D with SYMID of 101 (decimal =257) not seen by my Linux host.  Same device with SYMID reset to 0A2 (decimal=162) all ok.

    I think we are in basic agreement I just want to change the HBA parameter to a higher value give myself further options to avoid the issue in the future and wondered if adjusting the MAX LUNS parameter on the HBA to do so would set me up for any adverse effects.

    Thanks for any advice.

  • dynamox

    11 Legend

    •

    20419 Posts

    •

    87439 Points

    618

    0

    Posted April 20th, 2012 19:00

    drake wrote:

      I was discussing this issues and your idea with the linux admin and he mentions the ease of groupings and device mangement as they relate to veritas/bcvs/clones etc, for one as they are now and then device tracking going forward.

    not sure this is a big issue, look at this output ..this will provide a matching table between the physical address (SYMM)  and the logical one (HOST).

    symmaskdb -sid 1234 list devs -wwn 21000024ff2e1e44

    Sym Dev




    L UN
    Name Dir:P Physical Device Name VBUS TID SYMM HOST Attr Cap(MB)
    ------ ----- --------------- -------- ---- --- ---- ---- ---- -------
    75 3B:0 Not Visible
    0 0 1c 0 (M) 517894
    00F3 3B:0 Not Visible
    0 0 1d 1 (M) 517894
    09B1 3B:0 Not Visible
    0 0 1e 2 (M) 517894
    09ED 3B:0 Not Visible
    0 0 1f 3 (M) 517894
    0A29 3B:0 Not Visible
    0 0 20 4 (M) 517894
    0A65 3B:0 Not Visible
    0 0 21 5 (M) 517894
    0C68 3B:0 Not Visible
    0 0 2c 6 (M) 517894