RHEL5 FCID 와 disk/LUN 정보 확인

어떻게
RHEL 5에서 FC ID (WWN) 와 disk/LUN 정보를 확인할 수 있나?

Article
ID: 19446 Created on: May 22, 2009 10:54 AM Last Modified: Sep 27, 2009 12:12
PM

http://kbase.redhat.com/faq/docs/DOC-19446

Release
Found:
Red Hat Enterprise
Linux 5

Problem

multiple
SAN들이 연결된 시스템에서는 , 어떤 디스크가 어떤 SAN인지, 어떤 포트 어떤 연결인지 확인하기 어렵니다.

Resolution

On
Red Hat Enterprise Linux 5 에서는 모든 데이타가 /sys
에 저장되어 있고, Fibre Channel 별로 찾을 수 있다.
.

1)
서버에서 HBA의 Fibre Channel 주소를 찾기위해서는 아래와 같이 실행해라:

# systool -c fc_host -v (output trimmed for clarity) Class Device path = "/sys/class/fc_host/host8" port_name = "0x10000000c9802436" node_name = "0x20000000c9802436" Class Device path = "/sys/class/fc_host/host9" port_name = "0x10000000c9802437" node_name = "0x20000000c9802437"


서버에서, 현재 두개를 가지는 HBA가 현재 host8 host9로
동작하는 것을 알 수 있다.
(please notice
that these numbers can change, they change every time the fibre channel driver
is unloaded, reloaded, and can change across reboots). 이 host숫자는 HBTL SCSI addressing 에서의 H-value 이다.

2)
아래의 명령으로 또한 우리는 triplet HBT ( HBTL SCSI addressing) 에 대한
fibre channel target WWN을 확인할 수 있다..

# systool -c fc_transport -v (output trimmed for clarity) Class = "fc_transport" Class Device path = "/sys/class/fc_transport/target8:0:0" node_name = "0x50060160ba601693" port_name = "0x500601683a601693" Class Device path = "/sys/class/fc_transport/target9:0:0" node_name = "0x50060160ba601693" port_name = "0x500601683a601693" Class Device path = "/sys/class/fc_transport/target8:0:1" node_name = "0x50060160ba601693" port_name = "0x500601603a601693" Class Device path = "/sys/class/fc_transport/target9:0:1" node_name = "0x50060160ba601693" port_name = "0x500601603a601693"

Where
node_name, is the FC WWN of the Storage System, and port_name is the FC WWID of
the Storage Processor Port.

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

(sg_map
is part of sg3_utils, and before running sg_map, it is necessary to have the sg
module loaded on the system)

# sg_map -x (output trimmed for clarity) /dev/sg4 8 0 0 0 0 /dev/sdd /dev/sg5 8 0 0 1 0 /dev/sde /dev/sg6 8 0 0 2 0 /dev/sdf /dev/sg7 8 0 1 0 0 /dev/sdg /dev/sg8 8 0 1 1 0 /dev/sdh /dev/sg9 8 0 1 2 0 /dev/sdi /dev/sg10 9 0 0 0 0 /dev/sdj /dev/sg11 9 0 0 1 0 /dev/sdk /dev/sg12 9 0 0 2 0 /dev/sdl /dev/sg13 9 0 1 0 0 /dev/sdm /dev/sg14 9 0 1 1 0 /dev/sdn /dev/sg15 9 0 1 2 0 /dev/sdo

4)
From commands on (1), (2) and (3) we have the mapping from disk to HBTL SCSI addresses, and the mapping of SCSI address to fibre
channel address. If, for instance, we want to see where the following multipath
device is hosted, we do:

disc01 (3600601608e661a01486cd3c7f53ede11) dm-1 DGC,RAID 5 [size=10G][features=0][hwhandler=1 emc][rw] \_ round-robin 0 [prio=2][active] \_ 8:0:1:0 sdg 8:96 [active][ready] \_ 9:0:1:0 sdm 8:192 [active][ready] \_ round-robin 0 [prio=0][enabled] \_ 8:0:0:0 sdd 8:48 [active][ready] \_ 9:0:0:0 sdj 8:144 [active][ready]

5)
We know already that it’s an EMC Clariion because the vendor is DGC,
but I could have LUNs from more than one Clariion on this system, so let’s pick
/dev/sdj as an example:

/dev/sg10 9 0 0 0 0 /dev/sdj /dev/sdj = H:B:T:L = 9:0:0:0

Therefore
for sdj we have, H=9 and HBT=9:0:0. From (1) and (2) we have:

Host HBA WWN: 0x20000000c9802437 Host HBA WWP: 0x10000000c9802437 Storage System WWN: 0x50060160ba601693 Storage Processor WWP: 0x500601683a601693

6)
Doing for all disks:

Local Port Remote port STORAGE 8:0:1:0 sdg 0x10000000c9802436 0x500601603a601693 0x50060160ba601693 9:0:1:0 sdm 0x10000000c9802437 0x500601603a601693 0x50060160ba601693 8:0:0:0 sdd 0x10000000c9802436 0x500601683a601693 0x50060160ba601693 9:0:0:0 sdj 0x10000000c9802437 0x500601683a601693 0x50060160ba601693

ATTENTION: look carefully at the ‘Remote port’ values,
they normally differ only in a few bits.

In
this particular case, we see that both sdd and sdj are on the same remote port,
and sdg and sdm are on the same ports as well.

7)
A storage system can have many ports. In most cases 2 or 4, but the Storage ID
should remain the same. In sysfs we have 0x50060160ba601693, which maps
perfectly to the storage WWN from the storage admin interface.

Current Storage System Name: AX150 Storage System World Wide Name: 50:06:01:60:BA:60:16:93

서진우

슈퍼컴퓨팅 전문 기업 클루닉스/ 상무(기술이사)/ 정보시스템감리사/ 시스존 블로그 운영자

You may also like...

29 Responses

  1. gate io türkiye 말해보세요:

    I am an investor of gate io, I have consulted a lot of information, I hope to upgrade my investment strategy with a new model. Your article creation ideas have given me a lot of inspiration, but I still have some doubts. I wonder if you can help me? Thanks.

  2. 20bet 말해보세요:

    Your article gave me a lot of inspiration, I hope you can explain your point of view in more detail, because I have some doubts, thank you.

  1. 2023년 6월 7일

    … [Trackback]

    […] Read More Info here on that Topic: nblog.syszone.co.kr/archives/4930 […]

  2. 2023년 6월 13일

    … [Trackback]

    […] Find More Info here to that Topic: nblog.syszone.co.kr/archives/4930 […]

  3. 2023년 6월 13일

    … [Trackback]

    […] Here you can find 25166 additional Information to that Topic: nblog.syszone.co.kr/archives/4930 […]

  4. 2023년 7월 11일

    … [Trackback]

    […] Find More to that Topic: nblog.syszone.co.kr/archives/4930 […]

  5. 2023년 7월 13일

    … [Trackback]

    […] Read More to that Topic: nblog.syszone.co.kr/archives/4930 […]

  6. 2023년 7월 19일

    … [Trackback]

    […] Read More Info here on that Topic: nblog.syszone.co.kr/archives/4930 […]

  7. 2023년 7월 21일

    … [Trackback]

    […] Find More on to that Topic: nblog.syszone.co.kr/archives/4930 […]

  8. 2023년 8월 2일

    … [Trackback]

    […] Read More on on that Topic: nblog.syszone.co.kr/archives/4930 […]

  9. 2023년 8월 6일

    … [Trackback]

    […] Information on that Topic: nblog.syszone.co.kr/archives/4930 […]

  10. 2023년 8월 25일

    … [Trackback]

    […] Find More to that Topic: nblog.syszone.co.kr/archives/4930 […]

  11. 2023년 10월 2일

    … [Trackback]

    […] Read More Info here to that Topic: nblog.syszone.co.kr/archives/4930 […]

  12. 2023년 10월 8일

    … [Trackback]

    […] Find More Information here on that Topic: nblog.syszone.co.kr/archives/4930 […]

  13. 2023년 10월 27일

    … [Trackback]

    […] Info on that Topic: nblog.syszone.co.kr/archives/4930 […]

  14. 2023년 11월 5일

    … [Trackback]

    […] Here you will find 57516 more Information to that Topic: nblog.syszone.co.kr/archives/4930 […]

  15. 2023년 11월 10일

    … [Trackback]

    […] Read More here to that Topic: nblog.syszone.co.kr/archives/4930 […]

  16. 2023년 11월 11일

    … [Trackback]

    […] Find More to that Topic: nblog.syszone.co.kr/archives/4930 […]

  17. 2023년 11월 12일

    … [Trackback]

    […] Read More Info here on that Topic: nblog.syszone.co.kr/archives/4930 […]

  18. 2023년 11월 18일

    … [Trackback]

    […] There you will find 62570 additional Info on that Topic: nblog.syszone.co.kr/archives/4930 […]

  19. 2023년 11월 23일

    … [Trackback]

    […] Read More on that Topic: nblog.syszone.co.kr/archives/4930 […]

  20. 2023년 11월 29일

    … [Trackback]

    […] Read More Information here on that Topic: nblog.syszone.co.kr/archives/4930 […]

  21. 2023년 12월 6일

    … [Trackback]

    […] Info on that Topic: nblog.syszone.co.kr/archives/4930 […]

  22. 2023년 12월 8일

    … [Trackback]

    […] Info to that Topic: nblog.syszone.co.kr/archives/4930 […]

  23. 2023년 12월 19일

    … [Trackback]

    […] Read More here on that Topic: nblog.syszone.co.kr/archives/4930 […]

  24. 2024년 2월 10일

    … [Trackback]

    […] Read More on to that Topic: nblog.syszone.co.kr/archives/4930 […]

  25. 2024년 2월 15일

    … [Trackback]

    […] Find More here to that Topic: nblog.syszone.co.kr/archives/4930 […]

  26. 2024년 3월 26일

    … [Trackback]

    […] Read More to that Topic: nblog.syszone.co.kr/archives/4930 […]

  27. 2024년 5월 26일

    … [Trackback]

    […] Read More Information here to that Topic: nblog.syszone.co.kr/archives/4930 […]

페이스북/트위트/구글 계정으로 댓글 가능합니다.