HP-UX

log 분석 문의 드립니다.

 
김천기
조언자

log 분석 문의 드립니다.

안녕하세요.
log 분석 문의 드립니다.
Model : rx8640
OS Ver : 11.23
dmesg,event.log,ioscan값을 첨부 하였습니다. 무엇이 문제여서 어떤 조치를 취해야하는지 알고 싶습니다. ioscan값에서 보면 esl장비가 unknown으로 나오는데 원인과 해결 방법을 알고 싶습니다. 자세히 설명해주시면 감사하겠습니다.
고수님들 도움 부탁드립니다.
-------------------------------------------------
dmesg
-------------------------------------------------
0/0/8/1/0: Device at device id 0x11700 has disappeared from Name Server GPN_FT
(FCP type) response, or its 'Port World-Wide Name' has changed.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices
System won't be able to see LUNs behind this port.
--------------------------------------------------
ioscan
--------------------------------------------------
korea01# ioscan -fnH 0/0/8/1/0
Class I H/W Path Driver S/W State H/W Type Description
===========================================================================
fc 4 0/0/8/1/0 fcd CLAIMED INTERFACE HP AB379-60101 4Gb Dual Port PCI/PCI-X Fibre Channel Adapter (FC Port 1)
/dev/fcd4
fcp 4 0/0/8/1/0.1 fcd_fcp CLAIMED INTERFACE FCP Domain
ext_bus 12 0/0/8/1/0.1.20.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 22 0/0/8/1/0.1.20.255.0.0 tgt CLAIMED DEVICE
unknown -1 0/0/8/1/0.1.20.255.0.0.0 UNCLAIMED UNKNOWN HP ESL E-Series
tape 5 0/0/8/1/0.1.20.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/5m /dev/rmt/5mn /dev/rmt/c12t0d1BEST /dev/rmt/c12t0d1BESTn
/dev/rmt/5mb /dev/rmt/5mnb /dev/rmt/c12t0d1BESTb /dev/rmt/c12t0d1BESTnb
tape 1 0/0/8/1/0.1.20.255.0.0.2 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/c12t0d2BEST /dev/rmt/c12t0d2BESTb /dev/rmt/c12t0d2BESTn /dev/rmt/c12t0d2BESTnb
ext_bus 13 0/0/8/1/0.1.21.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 23 0/0/8/1/0.1.21.255.0.0 tgt CLAIMED DEVICE
tape 3 0/0/8/1/0.1.21.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/3m /dev/rmt/3mn /dev/rmt/c13t0d0BEST /dev/rmt/c13t0d0BESTn
/dev/rmt/3mb /dev/rmt/3mnb /dev/rmt/c13t0d0BESTb /dev/rmt/c13t0d0BESTnb
tape 7 0/0/8/1/0.1.21.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/7m /dev/rmt/7mn /dev/rmt/c13t0d1BEST /dev/rmt/c13t0d1BESTn
/dev/rmt/7mb /dev/rmt/7mnb /dev/rmt/c13t0d1BESTb /dev/rmt/c13t0d1BESTnb
ext_bus 14 0/0/8/1/0.1.22.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 25 0/0/8/1/0.1.22.255.0.0 tgt CLAIMED DEVICE
tape 2 0/0/8/1/0.1.22.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/2m /dev/rmt/2mn /dev/rmt/c14t0d0BEST /dev/rmt/c14t0d0BESTn
/dev/rmt/2mb /dev/rmt/2mnb /dev/rmt/c14t0d0BESTb /dev/rmt/c14t0d0BESTnb
tape 6 0/0/8/1/0.1.22.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/6m /dev/rmt/6mn /dev/rmt/c14t0d1BEST /dev/rmt/c14t0d1BESTn
/dev/rmt/6mb /dev/rmt/6mnb /dev/rmt/c14t0d1BESTb /dev/rmt/c14t0d1BESTnb
ext_bus 15 0/0/8/1/0.1.23.255.0 fcd_vbus CLAIMED INTERFACE FCP Device Interface
target 24 0/0/8/1/0.1.23.255.0.0 tgt CLAIMED DEVICE
tape 4 0/0/8/1/0.1.23.255.0.0.0 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/4m /dev/rmt/4mn /dev/rmt/c15t0d0BEST /dev/rmt/c15t0d0BESTn
/dev/rmt/4mb /dev/rmt/4mnb /dev/rmt/c15t0d0BESTb /dev/rmt/c15t0d0BESTnb
tape 8 0/0/8/1/0.1.23.255.0.0.1 stape CLAIMED DEVICE HP Ultrium 3-SCSI
/dev/rmt/8m /dev/rmt/8mn /dev/rmt/c15t0d1BEST /dev/rmt/c15t0d1BESTn
/dev/rmt/8mb /dev/rmt/8mnb /dev/rmt/c15t0d1BESTb /dev/rmt/c15t0d1BESTnb
--------------------------------------------------
event.log
--------------------------------------------------
>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Mon Jan 11 17:35:46 2010

korea01 sent Event Monitor notification information:

/adapters/events/ql_adapter/0_0_8_1_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Mon Jan 11 17:35:46 2010
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 59
System..............: korea01

Summary:
Adapter at hardware path 0/0/8/1/0 : Target device is back. Port
World-wide name remains the same as original.



Description of Error:


lbolt value: 259126257

Target with device id 0x11400 is back in the Name Server GPN_FT (FCP type)
response. And the 'Port World-wide name' remains the same as original.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices


Probable Cause / Recommended Action:

This is a paired message with "Target device is lost in the
Name Server GPN_FT response".
On receiving another RSCN, driver sent Name Server GPN_FT request
to obtain all the FC-4 type device information in the fabric.
Driver has detected that a previously lost device (Nport_id)
is back in the GPN_FT response, or it's corresponding World-Wide
Name remains the same.

Driver will be able to communicate with the device.
No action is needed.


Additional Event Data:
System IP Address...: 10.223.50.10
Event Id............: 0x4b4ae2e200000000
Monitor Version.....: B.02.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.04.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4b4ae2e200000000
Additional System Data:
System Model Number.............: ia64 hp server rx8640
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.60.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ql_adapter.htm#59

v-v-v-v-v-v-v-v-v-v-v-v-v D E T A I L S v-v-v-v-v-v-v-v-v-v-v-v-v



Component Data:
Physical Device Path....: 0/0/8/1/0

I/O Log Event Data:

Driver Status Code..................: 0x0000003B
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 66 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 0F71F3F1 00000001 00000001 00011400 2F75782F 636F7265 2F697375
2F464344 2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F646D
2E63





>---------- End Event Monitoring Service Event Notification ----------<
1 응답 1
monoworld_1
조언자

log 분석 문의 드립니다.

일단 결론 부터 말하면 몰려주신 자료만으로 보면
해당 서버가 백업 관리서버가 아니고 백업 드라이브 정상적으로 동작하면 신경 안쓰셔도 됩니다.

esl장비에서 unknown으로 나오는 부분은 autoch 라는 백업 장비의 테입을 관리하는 디바이스에 해당하며 해당 서버에 schgr driver 가 설치 안되어 있어서 OS에서 해당 디바이스를 인식 하지 못해 발생하는 증상입니다.
백업 마스터 서버가 아니라면 굳이 드라이버 설치할 필요는 없고 정상 상태입니다. 백업 마스터 서버라면 당연 드라이브 설치하고 OS에서 백업 장비 컨트롤 할 수 있는 환경 구축해 주시면 됩니다.
EMS 메시지도 unknown과는 상관 없고요. 백업 장비의 드라이브를 조정하거나 해서 드라이브 WWWN과 OS가 인식하고 있는 WWWN 이 상이해 나오는 메시지고 드라이브 정상 동작 한다면 무시해도 되는 메시지 입니다.