Topic
8 replies Latest Post - ‏2012-10-19T15:03:18Z by PopeyeSailor
PopeyeSailor
PopeyeSailor
9 Posts
ACCEPTED ANSWER

Pinned topic detecting SAN storage

‏2012-10-04T23:33:51Z |
Hi , i am just a beginner SA , and as with most SA's challenging task is to get the storage configured with so many forms of virtualization on IBM hardware .

position is like this , how to find the correct LUN assigned to the VIO client ??

I am looking for a principal property that is shared between System admin and SAN admin like serial number which is unique and does not change on any virtualization level , please advise is there any such property which i can get from the AIX (VIO Client) to confirm that the storage is a new Logical Unit Number (LUN) assigned by Storage Admin to this VIO Client a.k.a AIX server.

please advise.
Updated on 2012-10-19T15:03:18Z at 2012-10-19T15:03:18Z by PopeyeSailor
  • The_Doctor
    The_Doctor
    92 Posts
    ACCEPTED ANSWER

    Re: detecting SAN storage

    ‏2012-10-04T23:40:47Z  in response to PopeyeSailor
    try this on your VIO Server
    
    /home/padmin > $ chkdev -dev hdiskNNN -verbose   OR   /home/padmin > $ lsdev -dev hdiskNNN -attr
    
    • The_Doctor
      The_Doctor
      92 Posts
      ACCEPTED ANSWER

      Re: detecting SAN storage

      ‏2012-10-04T23:46:12Z  in response to The_Doctor
      BTW, that really only works for VSCSI LUNs.

      If you're using NPIV, then the VIO Server won't see the LUNs (unless you zone them).

      NPIV LUNs are generally only zoned to the Client LPAR.
      • dv8
        dv8
        1 Post
        ACCEPTED ANSWER

        Re: detecting SAN storage

        ‏2012-10-05T13:22:53Z  in response to The_Doctor
        Depending on the storage vendor, they may provide utilities that help identify the LUN information you're looking for. For example, in my case, we use EMC storage. They provide an inq utility to scan the storage LUNs. See sample output below. The first column is the hdisk device that the AIX team would reference while the serial number column (second to last) includes the LUN ID that storage team uses as a reference.

        Inquiry utility, Version V7.3-1214 (Rev 0.1) (SIL Version V7.3.0.1 (Edit Level 1214)
        Copyright (C) by EMC Corporation, all rights reserved.
        For help type inq -h.

        .................


        DEVICE :VEND :PROD :REV :SER NUM :CAP(kb)
        /dev/rhdiskpower0 :DGC :VRAID :0430 :044D5172 : 251658240
        /dev/rhdiskpower1 :DGC :VRAID :0430 :034D5172 : 429916160
        /dev/rhdiskpower2 :DGC :VRAID :0430 :104DFA2B : 262144000
  • kamdard
    kamdard
    1 Post
    ACCEPTED ANSWER

    Re: detecting SAN storage

    ‏2012-10-10T03:42:11Z  in response to PopeyeSailor
    You can also do "lsattr -El hdisk<X>" and search for "unique_id".

    Hope this helps.

    Regards,
    DK.
    • PopeyeSailor
      PopeyeSailor
      9 Posts
      ACCEPTED ANSWER

      Re: detecting SAN storage

      ‏2012-10-19T14:17:48Z  in response to kamdard
      Thanks for the information , but the UUID and World Wide LUN Name are different.

      Storage gave this :

      LUN ID:39
      World Wide LUN Name: 6001-4380-05de-f943-0000-7000-0bc2-0000

      UUID is different from this.

      how to find ? its HP EVA.

      thanks.
      • PopeyeSailor
        PopeyeSailor
        9 Posts
        ACCEPTED ANSWER

        Re: detecting SAN storage

        ‏2012-10-19T15:01:52Z  in response to PopeyeSailor
        found my answer in

        lsattr -El hdisk#

        find the unique_id and extract the World Wide Lun Number from that to confirm which lun storage has added.
    • PopeyeSailor
      PopeyeSailor
      9 Posts
      ACCEPTED ANSWER

      Re: detecting SAN storage

      ‏2012-10-19T15:03:18Z  in response to kamdard
      Thanks Kamdard , it worked.
  • PopeyeSailor
    PopeyeSailor
    9 Posts
    ACCEPTED ANSWER

    Re: detecting SAN storage

    ‏2012-10-19T15:02:35Z  in response to PopeyeSailor
    Storage LUN <> OS mapping on VIO client identified.