How do I find the FC ID (WWN) of a scsi device/LUN on Red Hat Enterprise Linux?

最新推荐文章于 2021-05-13 20:28:15 发布
最新推荐文章于 2021-05-13 20:28:15 发布
阅读量1.2k 收藏
点赞数
分类专栏： RHEL7 文章标签： WWN fc id

https://access.redhat.com/articles/17054

Updated 2018年十一月14日00:20 - 

English 

Release Found: Red Hat Enterprise Linux 5, 6, 7

Problem

Resolution

Although no supported tool exists to create a full storage topology view on SAN configurations, simple programs or scripts can be written that integrates the information available within the kernel into different useful forms and reports.

The following describes commands that can be used to retrieve various wwn and identifiers associated with storage and how to combine them in useful ways.

The command route description from host to a san storage disk, or other type of scsi device, that an io command takes consists of the following information:

  1. kernel assigned scsi address plus sdN and sgN names
  2. HBA wwnn and wwpn (if fabric: port identifier)
  3. switch port wwn that the hba is attached to (if fabric)
  4. Storage wwnn and wwpn (if fabric: port identifier)
  5. Disk (or other scsi device) WWID

Raw

Kernel Device IDs[1]           HBA WWNs/IDs[2]         Switch WWN[3]           Storage WWNs/IDs[4]     Device WWN[5]
----------------------------   ---------------------   ---------------------   ---------------------   -------------------------
scsi addr  : h:b:t:l           node name  : wwn/wwnn   fabric name: wwn/wwpn   node name  : wwn/wwnn   lun number: wwn/wwid
device name: /dev/sdN          port name  : wwn/wwpn                           port name  : wwn/wwpn   lun id    : wwn/wwid
sg name    : /dev/sgN          san port id: xx.xx.xx                           san port id: xx.xx.xx

 

On Red Hat Enterprise Linux 5, 6, and 7 almost all the kernel to storage route information is stored in /sys and can be found independently of the Fibre Channel driver in use. The only exception is the disk wwid itself - that isn't stored in /sys but can be found within the output of multipath -ll output.

For example here's some information put together from sysfs and multipath command output information.

Raw

#SCSI[1]            HBA[2]                                          Fabric[3]           Storage[4]
#Addr          Luns wwnn               wwpn               portid    wwn                 wwnn               wwpn                portid
#------------- ---- ------------------:------------------:--------  ------------------  ------------------:------------------:--------
8:0:1:-           9 0x20000024ff2254bf 0x21000024ff2254bf 0x030b00  0x100000053367f20d  0x50014380113622b0 0x50014380113622b9 0x020c00

#Addr         Paths WWID[5]                               DevName    SG Name       Serial Number
#------------ ----- ------------------------------------- ---------- ------------- -------------------------
8:0:1:1           4  60014380125989a10000400000270000      /dev/sdj   /dev/sg12     PAXPVG79S0D06V
8:0:1:2           4  60014380125989a100004000007f0000      /dev/sdk   /dev/sg13     PAXPVG79S0D06V 
8:0:1:3           4  60014380125989a10000400000830000      /dev/sdl   /dev/sg14     PAXPVG79S0D06V 
8:0:1:4           4  60014380125989a100004000013a0000      /dev/sdm   /dev/sg15     PAXPVG79S0D06V 
8:0:1:5           4  60014380125989a10000400001280000      /dev/sdn   /dev/sg16     PAXPVG79S0D06V 
8:0:1:6           4  60014380125989a100004000012c0000      /dev/sdo   /dev/sg17     PAXPVG79S0D06V 
8:0:1:7           4  60014380125989a10000400001300000      /dev/sdp   /dev/sg18     PAXPVG79S0D06V 
8:0:1:8           4  60014380125989a100004000013e0000      /dev/sdq   /dev/sg19     PAXPVG79S0D06V 
8:0:1:9           4  60014380125989a10000400001600000      /dev/sdr   /dev/sg20     PAXPVG79S0D06V

 

 

 

 

The following information has been provided by Red Hat, but is outside the scope of coverage of the posted Service Level Agreements and support procedures. The information is provided as-is and any configuration settings or installed applications made from the information in this article could make the Operating System unsupported by Red Hat Global Support Services. The intent of this article is to provide information to accomplish the system's needs. Use of the information in this article at the user's own risk.

Source for the program that generated the above output is available at 'mapdevs' source but is for illustrative purposes only and, per the above, is provided as-is and is unsupported. The output is from ./mapdevs -wpx.

 

 

 

 

For the above data this is a partial map of scsi host8 (the 8:0:1 is h:c:t:* scsi address with the 'h' being the scsi host number, aka host8 in this case). Its partial because there is also a 8:0:0:* route to devices for this host. In ascii art the route to a storage device is:

Raw



  +--------------------------------+ [1]
  | Devices                        |   
  |    /dev/sdj /dev/sdg12 8:0:1:1 | 
  |    /dev/sdk /dev/sdg13 8:0:1:2 | 
  |    :                           |
  |                                |
  +--------------------------------+
                  |
                  v
   +------------------------------+  [2]
   | HBA (host 8)                 |
   |     wwnn: 0x20000024ff2254bf |
   |     wwpn: 0x21000024ff2254bf |
   |  port id: 0x030b00           |
   |                              |
   +------------------------------+
                  |
                  |        +----------------------------------+  [3]
                  +------> | Switch                           |
                           |     port wwn: 0x100000053367f20d |
                           |                                  |
                           +----------------------------------+
                                    |                    |                      [4]
                                    |                    |        +--------------------------------------+
                                    |                    +------> | Storage (target 1)                   |
                                    |                             |    wwnn: 0x50014380113622b0          | ------+
                                    |                             |    wwpn: 0x50014380113622b9          |       |        [5]
                                    |                             | port id: 0x020c00                    |       |     +------------------------------------------+
                                    |                             +--------------------------------------+       +---> | Disk (lun 1)                             |
                                    +---------------------------->| Storage (target 0)                   |       |     |  wwid: 60014380125989a10000400000270000  |
                                                                  |    wwnn: 0x50014380113622b0          |       |     +------------------------------------------+
                                                                  |    wwpn: 0x50014380113622bd          | ------+
                                                                  | port id: 0x030c00                    |
                                                                  +--------------------------------------+

So where can we find all the above information?

[1] kernel assigned scsi address plus sdN and sgN names

With the following command, we can determine the mapping between SCSI HBTL addresses and the disks:

NOTE: sg_map is part of sg3_utils package. Plus running sg_map, it is necessary to have the sg module loaded on the system.

Raw

    # sg_map -x
    
    (output trimmed for clarity)

    /dev/sg12  8 0 1 1  0  /dev/sdj   (this gives us scsi address (H:B:T:L) of 8:0:1:1, sdN and sgN names of sg12 and sdj)
    /dev/sg13  8 0 1 2  0  /dev/sdk
    /dev/sg14  8 0 1 3  0  /dev/sdl
    /dev/sg15  8 0 1 4  0  /dev/sdm
    /dev/sg16  8 0 1 5  0  /dev/sdn
    /dev/sg17  8 0 1 6  0  /dev/sdo
    /dev/sg18  8 0 1 7  0  /dev/sdp
    /dev/sg19  8 0 1 8  0  /dev/sdq
    /dev/sg20  8 0 1 9  0  /dev/sdr
    :
    /dev/sg23  9 0 0 2  0  /dev/sdt
    /dev/sg24  9 0 0 3  0  /dev/sdu
    /dev/sg25  9 0 0 4  0  /dev/sdv
    /dev/sg26  9 0 0 5  0  /dev/sdw
    /dev/sg27  9 0 0 6  0  /dev/sdx
    /dev/sg28  9 0 0 7  0  /dev/sdy
    /dev/sg29  9 0 0 8  0  /dev/sdz
    /dev/sg30  9 0 0 9  0  /dev/sdaa
    :

An alternative command to provide the same information is the lsscsi -g command from the lsscsi package.

[2] HBA wwnn and wwpn (if fabric: port identifier)

To find the Fibre Channel addresses of the HBAs on the machine, run the following:

Raw

    # systool -c fc_host -v
    
    (output trimmed for clarity)
    
      Class Device path = "/sys/class/fc_host/host8"  (kernel assigned host name/number)
        node_name           = "0x20000024ff2254bf"    (hba wwnn       )
        port_name           = "0x21000024ff2254bf"    (hba wwpn       )
        port_id             = "0x030b00"              (fabric port id assigned by the san to this HBA)

      Class Device path = "/sys/class/fc_host/host9"
        node_name           = "0x20000024ff2254be"
        port_name           = "0x21000024ff2254be"
        port_id             = "0x010c00"

Alternatively, the information can be found directly within the sysfs tree. For example:

Raw


    # ls -1c /sys/class/fc_host/host*/*_name 2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort
    /sys/class/fc_host/host8/fabric_name:0x100000053367f20d
    /sys/class/fc_host/host8/node_name:0x20000024ff2254bf
    /sys/class/fc_host/host8/port_name:0x21000024ff2254bf
    /sys/class/fc_host/host8/symbolic_name:QLE2562 FW:v5.06.02 DVR:v8.04.00.04.06.3-k
    /sys/class/fc_host/host9/fabric_name:0x100000606951c582
    /sys/class/fc_host/host9/node_name:0x20000024ff2254be
    /sys/class/fc_host/host9/port_name:0x21000024ff2254be
    /sys/class/fc_host/host9/symbolic_name:QLE2562 FW:v5.06.02 DVR:v8.04.00.04.06.3-k


    # ls -1c /sys/class/fc_host/host*/port_id 2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort 
    /sys/class/fc_host/host8/port_id:0x030b00
    /sys/class/fc_host/host9/port_id:0x010c00

On the system the above data is from we see that this particular machine has two HBAs currently listed as host8 and host9.

NOTE: these host numbers can change. They can change every time the fibre channel driver is unloaded, reloaded, and can change across reboots. The kernel assigns host numbers in order, but which HBA gets which number depends upon discovery order and when a particular host gets registered with the kernel. The host number is the H-value on H:B:T:L SCSI addressing.

[3] (if fabric: switch port wwn that the hba is attached to)

If the san is a fabric with a switch, then there will be a switch port wwn listed under fabric name within the sysfs tree. To find the Fibre Channel addresses of the switch ports HBAs are connected to, run the following:

Raw

    # systool -c fc_host -v

    (output trimmed for clarity)
    
      Class Device path = "/sys/class/fc_host/host8"  
        fabric_name         = "0x100000053367f20d"    (switch port wwn)

      Class Device path = "/sys/class/fc_host/host9"
        fabric_name         = "0x100000606951c582"

Alternatively, the information can be found directly within the sysfs tree. For example:

Raw


    # ls -1c /sys/class/fc_host/host*/*_name 2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort
    /sys/class/fc_host/host8/fabric_name:0x100000053367f20d
    /sys/class/fc_host/host8/node_name:0x20000024ff2254bf
    /sys/class/fc_host/host8/port_name:0x21000024ff2254bf
    /sys/class/fc_host/host8/symbolic_name:QLE2562 FW:v5.06.02 DVR:v8.04.00.04.06.3-k
    /sys/class/fc_host/host9/fabric_name:0x100000606951c582
    /sys/class/fc_host/host9/node_name:0x20000024ff2254be
    /sys/class/fc_host/host9/port_name:0x21000024ff2254be
    /sys/class/fc_host/host9/symbolic_name:QLE2562 FW:v5.06.02 DVR:v8.04.00.04.06.3-k

[4] Storage wwnn and wwpn (if fabric: port identifier)

With the following command we can determine the Fibre Channel storage target WWNs for the triplet H:B:T from H:B:T:L SCSI addressing.

Raw

    # systool -c fc_transport -v
    
    (output trimmed for clarity)
    
      Class Device path = "/sys/class/fc_transport/target8:0:0"  (H:B:T scsi address assigned by kernel)
        node_name           = "0x50014380113622b0"               (storage target wwnn)
        port_name           = "0x50014380113622bd"               (storage target wwpn)
        port_id             = "0x030c00"                         (fabric port id assigned by the san to this storage port)

      Class Device path = "/sys/class/fc_transport/target9:0:0"
        node_name           = "0x50014380113622b0"
        port_name           = "0x50014380113622bc"
        port_id             = "0x010400"

     Class Device path = "/sys/class/fc_transport/target8:0:1"
        node_name           = "0x50014380113622b0"
        port_name           = "0x50014380113622b9"
        port_id             = "0x020c00"

     Class Device path = "/sys/class/fc_transport/target9:0:1"
        node_name           = "0x50014380113622b0"
        port_name           = "0x50014380113622b8"
        port_id             = "0x010d00"

Just note that there are two H:B:T combinations for each HBA, namely 8:0:0 plus 8:0:1 for host8 and 9:0:0 plus 9:0:1 for host9. This simply means each HBA is connected to a switch and that switch is connected to 2 or more storage ports of which 2 are zoned to be visible to each HBA.

In addition, all available remote ports can be listed via systool -c fc_report_ports -v, whereas fc_transport class only lists storage ports which have luns behind them, fc_report_ports will list all the ports that have been logged into. For example, this can include FCP Initiators (other HBAs) in our zone or storage ports that don't have any luns exported to the host.

Alternatively, the information can be gathered directly from the sysfs tree:

Raw

 RHEL5:
    # ls -1c /sys/class/fc_transport/target*/*_name  2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort
    # ls -1c /sys/class/fc_transport/target*/port_id 2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort

 RHEL6,7:
    # ls -1c /sys/bus/scsi/devices/target*/fc_transport/target*/*_name  2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort
    # ls -1c /sys/bus/scsi/devices/target*/fc_transport/target*/port_id 2> /dev/null | xargs -I {} grep -H -v "ZzZz" {} | sort

It is common, but not necessarily universal, that the storage port wwnn is common across all storage ports associated with a give storage system. For example, this output shows the system has two HBAs, with each connected to two storage ports per the H:B:T combinations present within the output:

Raw

/sys/class/fc_transport/target8:0:0/node_name:0x50014380113622b0
/sys/class/fc_transport/target8:0:1/node_name:0x50014380113622b0
/sys/class/fc_transport/target9:0:0/node_name:0x50014380113622b0
/sys/class/fc_transport/target9:0:1/node_name:0x50014380113622b0

We can see that the storage wwnn of each storage target is the same (0x50014380113622b0), indicating that all storage ports are in the same storage system. Other ways of telling if the storage system is the same or different include looking at scsi inquiry page 0x80 from the different luns. The returned serial number is often common, reflecting the serial number of the storage system. There may be other methods, including vendor specific, of determining which sets of storage ports (scsi targets) are associated with the same or different storage systems.

The companion storage target wwpn data for the above system shows there are four different storage ports per the different and unique identifiers listed:

Raw

/sys/class/fc_transport/target8:0:0/port_name:0x50014380113622bd
/sys/class/fc_transport/target8:0:1/port_name:0x50014380113622b9
/sys/class/fc_transport/target9:0:0/port_name:0x50014380113622bc
/sys/class/fc_transport/target9:0:1/port_name:0x50014380113622b8

 

So on this system, host8 is connected to two storage ports (0x50014380113622bd and 0x50014380113622b9) and host9 is connected to two different storage ports (0x50014380113622bc and 0x50014380113622b8, but all four storage ports are on the same storage system (wwnn:0x50014380113622b0).

[5] Disk (or other scsi device) WWID

The device WWIDs are not stored within the sysfs tree within RHEL5 or 6. A device WWID can be found using:

  • disks only: multipath command (device-mapper-multipath package),
  • all scsi devices: sg_inq command (sg3_utils package),
  • scsi_id command (RHEL 5,6 only: udev package),
  • lsscsi --scsi_id command (RHEL 7 only: lsscsi package),
  • or by examing links in /dev/<device-type>/by-id
    • <device-type> is "disk", "tape", etc.
    • link names are derived fronm the scsi_id command.

The typical place to quickly find these fro disks is within the output of the multipath -ll command.

Raw

    disc01 (360014380125989a100004000013a0000) dm-0 HP,HSV300
    size=10G features='1 queue_if_no_path' hwhandler='0' wp=rw
    |-+- policy='round-robin 0' prio=50 status=active
    | |- 8:0:1:4 sdm  8:192  active ready  running
    | `- 9:0:1:4 sdae 65:224 active ready  running
    `-+- policy='round-robin 0' prio=10 status=enabled
      |- 9:0:0:4 sdv  65:80  active ready  running
      `- 8:0:0:4 sdd  8:48   active ready  running

 

The highlighted portion is the disk WWID as returned by storage.

Alternatively the device WWID can be found via the sg_inq -p 0x83 /dev/sdN command:

Raw

    # sg_inq -p 0x83 /dev/sdm
    VPD INQUIRY: Device Identification page
      Designation descriptor number 1, descriptor length: 20
        designator_type: NAA,  code_set: Binary
        associated with the addressed logical unit
          NAA 6, IEEE Company_id: 0x1438
          Vendor Specific Identifier: 0x125989a1
          Vendor Specific Identifier Extension: 0x4000013a0000
          [0x60014380125989a100004000013a0000]
    :

    # sg_inq -p 0x83 /dev/sdd
    VPD INQUIRY: Device Identification page
      Designation descriptor number 1, descriptor length: 20
        designator_type: NAA,  code_set: Binary
        associated with the addressed logical unit
          NAA 6, IEEE Company_id: 0x1438
          Vendor Specific Identifier: 0x125989a1
          Vendor Specific Identifier Extension: 0x4000013a0000
          [0x60014380125989a100004000013a0000]
    :

Or using the scsi_id -g -u -s /block/sdN command:

RHEL5:

Raw

    # scsi_id -g -u -s /block/sdm
    360014380125989a100004000013a0000
    # scsi_id -g -u -s /block/sdd
    360014380125989a100004000013a0000
    # scsi_id -g -u -s /class/scsi_tape/st0
    360014380125989a100004000013b0000

RHEL6:

Raw

    # scsi_id --replace-whitespace --whitelisted --device /dev/sdm
    360014380125989a100004000013a0000
    # scsi_id --replace-whitespace --whitelisted --device /dev/sdd
    360014380125989a100004000013a0000
    # scsi_id --replace-whitespace --whitelisted --device /dev/st0
    360014380125989a100004000013b0000

RHEL7:
On RHEL 7, the scsi_id command does not exist. A partial replacement is lsscsi --scsi_id, but that will only work for disk devices.

Raw

  # lsscsi --scsi_id -g 
[4:0:0:0]    disk    HP       LOGICAL VOLUME   5.70  /dev/sda   3600508b1001c072a93d8825b16500fea  /dev/sg1 
[4:0:0:1]    disk    HP       LOGICAL VOLUME   5.70  /dev/sdb   3600508b1001c4c98d3b101921097c450  /dev/sg2 
[4:0:0:2]    disk    HP       LOGICAL VOLUME   5.70  /dev/sdc   3600508b1001c5096699d2d9dc6993ef2  /dev/sg3 
[4:3:0:0]    storage HP       P410i            5.70  -          -  /dev/sg0 
[8:0:0:5]    tape    IBM      ULT3580-TD4      0104  /dev/st0   -

As will using udevadm info --name, at least for disks:

Raw

# udevadm info --name sda
P: /devices/pci0000:00/0000:00:01.0/0000:04:00.0/host4/target4:0:0/4:0:0:0/block/sda
N: sda
:
E: ID_SCSI_SERIAL=50014380212E90E0
E: ID_SERIAL=3600508b1001c072a93d8825b16500fea
E: ID_SERIAL_SHORT=600508b1001c072a93d8825b16500fea
:

But still for non-disk devices, no scsi_id nor VPD identifier is available directly, only very limited information is captured:

Raw

# udevadm info --name sg0
P: /devices/pci0000:00/0000:00:01.0/0000:04:00.0/host4/target4:3:0/4:3:0:0/scsi_generic/sg0
N: sg0
E: DEVNAME=/dev/sg0
E: DEVPATH=/devices/pci0000:00/0000:00:01.0/0000:04:00.0/host4/target4:3:0/4:3:0:0/scsi_generic/sg0
E: MAJOR=21
E: MINOR=0
E: SUBSYSTEM=scsi_generic

In those cases using th sg_inq command from the sg3_utils package can be used:

Raw

# # sg_inq -p 0x83 /dev/sg0
VPD INQUIRY: Device Identification page
  Designation descriptor number 1, descriptor length: 20
    designator_type: vendor specific [0x0],  code_set: ASCII
    associated with the addressed logical unit
      vendor specific: 50014380212E90E0
  Designation descriptor number 2, descriptor length: 8
    designator_type: vendor specific [0x0],  code_set: Binary
    associated with the addressed logical unit
      vendor specific:
        00 00 00 00

Note that in the above case, the identifier is a vendor specific ascii string. By its very nature, vendor specific strings are not guaranteed to be world wide unique and therefore are no WWIDs as the term is commonly used. Whereas in the following example for a scsi tape device, the identifier conforms to NAA format which includes an IEEE OUI (Organizationally Unique Identifier) making this identifier world wide unique:

Raw

# sg_inq -p 0x83 /dev/st0
VPD INQUIRY: Device Identification page
  Designation descriptor number 1, descriptor length: 38
    designator_type: T10 vendor identification,  code_set: ASCII
    associated with the addressed logical unit
      vendor id: IBM     
      vendor specific: ULT3580-TD4     XYZZY_A5  
  Designation descriptor number 2, descriptor length: 12
    designator_type: NAA,  code_set: Binary
    associated with the addressed logical unit
      NAA 5, IEEE Company_id: 0x22334
      Vendor Specific Identifier: 0x4ab000500
      [0x50223344ab000500]

Another method available on all RHEL versions is the use or examination of links in /dev//by-id:

Raw

$ ls -l /dev/disk/by-id | grep sdm
lrwxrwxrwx 1 root root  9 Jul 24 15:52 scsi-360014380125989a100004000013a0000 -> ../../sdm
$ ls -l /dev/tape/by-id | grep st0
lrwxrwxrwx 1 root root  9 Jul 24 15:52 scsi-360014380125989a100004000013b0000 -> ../../st0

All the above methods depend on the output from the scsi INQUIRY command (page 0x83, Device identification page). You can specify scsi_id options "-p 0x83" on RHEL5 and --page 0x83" on RHEL6 to specify the INQUIRY page to use, although the command will use the best available option by default.

See "How are SCSI ID generated?" for information on how scsi_id forms a scsi unique identifier within the linux host.

Putting it all together

Using the commands and information from (1)-(5) a mapping from disk H:B:T:L SCSI addresses thru device WWID can be generated.

Lets pick /dev/sdd as an example:

Raw

 1. (kernel ) /dev/sg5  8 0 0 4  0  /dev/sdd
 2. (hba    ) port_name           = "0x21000024ff2254bf"
 3. (switch ) skipping this for now...
 4. (storage) port_name           = "0x50014380113622bd"
 5. (device ) multipath wwid      = 60014380125989a100004000013a0000

 Resulting in:

 scsi-addr      devn  hba/wwpn                storage target/wwpn     disk/wwid
 -------------- ----- ----------------------- ----------------------- ---------------------------------------
 8:0:0:4        sdd      8:0x21000024ff2254bf    0:0x50014380113622bd    4:60014380125989a100004000013a0000
 |   | |                 ^                       ^                       ^
 +--- - -----------------+                       |                       |
     | |                                         |                       |
     | +-----------------------------------------+                       |
     |                                                                   |
     +-------------------------------------------------------------------+

Doing the above for all disks associated with

Raw

 scsi-addr      devn  hba/wwpn                storage target/wwpn     disk/wwid
 -------------- ----- ----------------------- ----------------------- ---------------------------------------
 8:0:1:4        sdm      8:0x21000024ff2254bf    1:0x50014380113622b9    4:60014380125989a100004000013a0000 
 9:0:1:4        sdae     9:0x21000024ff2254be    1:0x50014380113622b8    4:60014380125989a100004000013a0000     
 9:0:0:4        sdv      9:0x21000024ff2254be    0:0x50014380113622bc    4:60014380125989a100004000013a0000 
 8:0:0:4        sdd      8:0x21000024ff2254bf    0:0x50014380113622bd    4:60014380125989a100004000013a0000
NOTE: the above is part of the output from ./mapdevs -wt.

 

Additional information is available just about the HBA itself, such as the pci address of the hba that was assigned scsi hostN, driver version (if available), hba firmware level (if available), and state information as follows (in the following example we're interested in just scsi8, pci address 0e:00.0).

Raw


#scsi_addr   name                   version                f/w                       device
#----------- ---------------------- ---------------------- ------------------------- ----------------------------------------------
:
 8:*:*:*     lpfc                   0:11.2.0.6             2.82A4 (Z3F2.82A4), sli-3 /sys/devices/pci0000:00/0000:00:07.0/0000:0e:00.0/host8
 9:*:*:*     lpfc                   0:11.2.0.6             2.82A4 (Z3F2.82A4), sli-3 /sys/devices/pci0000:00/0000:00:07.0/0000:0e:00.1/host9


#            --------- PCI -------------
#                          subsystem      model        model
#scsi_addr   vendor device vendor device  name         description
#----------- ------ ------ ------ ------  ------------ --------------------------------------------------
:
 8:*:*:*     0x10df 0xfe00 0x10df 0xfe00  LPe11002-M4  Emulex LPe11002-M4 4Gb 2port FC: PCIe SFF HBA
 9:*:*:*     0x10df 0xfe00 0x10df 0xfe00  LPe11002-M4  Emulex LPe11002-M4 4Gb 2port FC: PCIe SFF HBA


#scsi_addr   name               speed    state    symbolic_name                                  port_type
#----------- ------------------ -------- -------- ---------------------------------------------- -----------------------------------------------
:
 8:*:*:*     lpfc               4 Gbit   Online   Emulex LPe11002-M4 FV2.82A4 DV11.2.0.6 HN:hostname OS:Linux NPort (fabric via point-to-point)
 9:*:*:*     lpfc               4 Gbit   Online   Emulex LPe11002-M4 FV2.82A4 DV11.2.0.6 HN:hostname OS:Linux NPort (fabric via point-to-point)

:
.
#SCSI               HBA                                             Fabric              Storage                                        Port
#Addr          Luns wwnn               wwpn               portid    wwn                 wwnn               wwpn                portid  info
#------------- ---- ------------------/------------------/--------  ------------------  ------------------/------------------/--------/---------
8:0:0:-          58 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x20000024ff278fae 0x21000024ff278fae 0x010000 FCP Target
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x100000051e9036e4 0x200b00051e9036e4 0xfffffe Fabric Port
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x100000051e9036e4 0x21fc00051e9036e4 0xfffffc Directory Server
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x2001001b323b1015 0x2101001b323b1015 0x010800 FCP Initiator
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x2000001b321b1015 0x2100001b321b1015 0x010c00 FCP Initiator
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x200000e08b87de9a 0x210000e08b87de9a 0x010200 FCP Initiator
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x2000001b321b6814 0x2100001b321b6814 0x010a00 FCP Initiator
8:0:x:-           - 0x20000090fa16f41e 0x10000090fa16f41e 0x010b00  0x100000051e9036e4  0x2001001b323b6814 0x2101001b323b6814 0x010900 FCP Initiator
9:0:0:-          58 0x20000090fa16f41f 0x10000090fa16f41f 0x050b00  0x100000051e902974  0x20000024ff278faf 0x21000024ff278faf 0x050000 FCP Target
9:0:x:-           - 0x20000090fa16f41f 0x10000090fa16f41f 0x050b00  0x100000051e902974  0x100000051e902974 0x200b00051e902974 0xfffffe Fabric Port
9:0:x:-           - 0x20000090fa16f41f 0x10000090fa16f41f 0x050b00  0x100000051e902974  0x100000051e902974 0x21fc00051e902974 0xfffffc Directory Server
9:0:x:-           - 0x20000090fa16f41f 0x10000090fa16f41f 0x050b00  0x100000051e902974  0x200100e08ba7de9a 0x210100e08ba7de9a 0x050200 FCP Initiator
NOTE: the above is part of the output from ./mapdevs -pH.

 

Additional Resources

msdnchina
关注
  • 0
    点赞
  • 踩
  • 0
    收藏
    觉得还不错? 一键收藏
  • 0
    评论
专栏目录
查看FC HBA卡WWN信息的方法
06-03
在 RedHat Linux AS4 中，可以查看 /proc/scsi/qla2xxx/3 文件的内容，以查看 FC HBA 卡的 WWN 信息。例如： `# grep scsi /proc/scsi/qla2xxx/3` Number of reqs in pending_q= 0, retry_q= 0, done_q= 0, scsi_...
SCSI系列五：设备名称和地址
最新发布
探索未知，成就非凡
08-01 767
传统上，在Linux 中，SCSI 设备是通过其主设备号和次设备号而不是其SCSI 总线地址（例如SCSI 目标ID 和LUN）来标识的。设备伪文件系统 (devfs) 放弃了主设备号和次设备号方案，并且 SCSI 子系统使用基于 SCSI 总线地址的设备名称 ，或者，有一个名为scsidev的实用程序 ，它可以在 Linux SCSI 子系统范围内解决此问题，因此不会产生与 devfs 相同的系统范围影响。因此，可以有多个设备名称，其中一些可能提供略有不同的特性，所有这些名称都映射到同一实际设备。
linux 查询wwid命令,wwid、uuid、lun、multipath、hba、udev总结
weixin_39907157的博客
04-30 946
wwid:scsi_id命令执行后，只有磁盘、存储盘才可以显示wwid，多路径的存储盘显示的wwid一样本地磁盘分区、存储盘分区都没有wwid存储盘分区后，存储盘本身的wwid不变存储盘分区且格式化后，存储盘本身的wwid不变[root@mesdg ~]# scsi_id -g -u /dev/sdi3600a098038303867635d4a48624e5465uuid:sudo blkid命...
linux里hba状态_Linux下查看FC HBA信息
weixin_42500374的博客
01-17 6799
HBA卡是存储和主机之间连接的媒介。在后端存储配置前后，需要通进查看一些HBA卡信息，如HBA卡型号、HBA卡是否online、HBA卡WWN号等。这里汇总几种查看HBA卡的方法。一、lspci 指令查看HBA卡信息现在的HBA卡为了速度的保证，一般都是插在pci插槽上的FC HBA卡，这里以常用的FC接口HBA为例，通过lspci 查看：[boco4a@361way.com ~]$ lspci|...
HBA的WWN号以及存储区域网络
LINUX1273549598的博客
11-19 9663
古驰古驰巴拉巴拉，今天讲一下存储区域网络和wwn号以及查看wwn号的方法 存储区域网络（Storage Area Network，简称SAN）采用网状通道（Fibre Channel ，简称FC，区别与Fiber Channel光纤通道）技术，通过FC交换机连接存储阵列和服务器主机，建立专用于数据存储的区域网络 WWN: world wide number 是硬件的全球唯一标示 WWPN: ...
Windows主机端查看FC-HBA卡WWN号的方法
07-22
在IT领域，尤其是在存储网络环境中，WWN（World Wide Name）是FC（Fibre Channel）接口设备的全球唯一标识符，用于区分不同的光纤通道硬件。本文将详细解释如何在Windows主机上查看FC-HBA（Fibre Channel Host Bus ...
Linux下查看wwn号
12-16
### Linux及多平台下HBA卡WWN号的查看方法 #### 一、WWN号简介 WWN（World Wide Name）是用于唯一标识网络设备（如光纤通道卡FC卡）的一个固定序列号，通常由16进制数字组成。在存储区域网络(SAN)环境中，WWN用于...
如何在LinuxUnix平台查看HBA卡的WWN号
04-25
"如何在Linux/Unix平台查看HBA卡的WWN号" 在 Linux/Unix 平台上查看 HBA 卡的 WWN 号是非常重要的，因为 WWN 号是唯一标识每个光纤卡的标识符。在本文中，我们将介绍如何在 AIX 和 HP-Unix 平台上查看 HBA 卡的 WWN...
WWN,WWNN,WWPN区别
Warrior 技术大杂论
05-27 5279
WWN: world wide number 是硬件的全球唯一标示 WWPN: world wide port number 是指端口号 WWNN: world wide node number 是指节点号   如果是光纤交换机的话wwn和wwnn是一样的,而wwpn是指每个光纤端口. 如果是HBA卡的话,若是只有一个端口则三者可能一样,若是有多个端口则和交换机差不多
在rhel7中使用lsscsi --scsi_id 命令返回所有scsi设备的scsi identifier
msdnchina的专栏@JiNan,ShanDong
10-25 8997
RHEL 7: The lsscsi --scsi_id -g utility from the lssci package can be used to return the scsi identifier associated with all scsi disks within the system (but only scsi disk, not all devices). [root@...
linux下获取scsi上的磁盘设备的序列号
热门推荐
wwyyxx26的专栏
07-12 2万+
最简单的方法是直接到/dev/disk/by-id目录下查看，如下是一台机器上的结果 linux-b572:/dev/disk/by-id # ls ata-ST31000525SV_6VP17SN7                      scsi-SATA_ST31000525SV_6VP17SN7                  wwn-0x5000c5001863e582 ata
linux无法识别存储盘的wwid,HP-UX 识别存储盘符不一致解决办法（转）
weixin_42462474的博客
05-13 391
在HP-UX上安装RAC或者配置双机时经常会遇到盘符不一致的情况，下面是从网上搜到的帖子，根据其修改可以修改盘符及instance number。1.可以在2台主机上通过scsimgr -p get_attr all_lun -a hw_path -a device_file -a wwid来查看wwn，wwn一致的为同一个盘，也可以通过它与存储划得每个lun对应起来2.通过ioinit来修改，具...
查看unix和linux的HBA卡的WWN地址
qq_40907977的博客
03-10 1071
转载来源 ： 怎样查看unix和linux的HBA卡的WWN地址 ： https://blog.51cto.com/liuqun/1981222 AIX: 1,获得AIX主机连接的光纤设备: root@test:/# lsdev -Cc adapter -S a |grep fcs fcs0 Available 05-00 4Gb FC PCI Express Adapter (df1000...
WWN与SAS地址详解（10款SAS硬盘横评之三）
weixin_34050005的博客
02-01 910
SATA的点对点连接不存在寻址的问题，但加入扩展器（Expander）后形成交换架构的SAS却必须考虑如何寻址。为此，SAS引入了WWN（World Wide Name，全局名）的机制。WWN是一个符合NAA IEEE注册格式的8字节16进制数，以NAA（16进制的5，第0字节的高四位）开头，跟着3个字节（第0字节低四位至第3字节的高四位）的IEEE公司ID和4.5个字节...
shell scripts
ciyangliln703681的专栏
07-13 265
[sfdba@cnsz22pl0028:/dba/oracle/diag/rdbms/ecpdbsit/ecpdbsit/trace]$cat /usr/bin/sysauto_SF #!/bin/bash ########...
How to Dynamically Add and Remove SCSI Devices on Linux (文档 ID 603868.1)
weixin_34130269的博客
10-29 467
In this Document Goal Solution 1. SCSI Device Addressing 2. SCSI Device Naming 3. Scanning, Adding and Removing Devices 3.1 System reboot 3.2 Reload host...
linux查看wwn号
06-28
在Linux中查看WWN号，可以使用以下命令： 1. 查看所有的WWN号： # ls /sys/class/fc_host/ 2. 查看指定的WWN号： # cat /sys/class/fc_host/hostX/port_name 其中，hostX表示主机的FC HBA编号，port_name表示...
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值