EMS로그 분석 요청

[홍진석]

안녕하세요.. 아래와 같은 로그가 나와 분석을 요청합니다. 경험하신 분이나 적용한 사례에 대한 답변 부탁드립니다. 현 상태는 이상없습니다.

-----------------------------------------------------------------

CURRENT MONITOR DATA:



Event Time..........: Mon Jan 3 09:30:15 2005

Severity............: MAJORWARNING

Monitor.............: disk_em

Event #.............: 100091

System..............: utlsdb01



Summary:

Disk at hardware path 2/0/1/0/0.2.0 : Software configuration error





Description of Error:



The device is in a condition where it requires action on the part of the

device driver or a human operator.



Probable Cause / Recommended Action:



The device has been reset by a Bus Device Reset message, a hard reset

condition, or a power-on reset.



If this is the case, no action is necessary.



Alternatively, a removable medium has been loaded or replaced.



If this is the case, no action is necessary.



Alternatively, the mode parameters, microcode, or inquiry data for the

device have been changed.



If this is the case, no action is necessary.



Alternatively, the installed version of the device driver does not match

that of the installed version of HP-UX. Install the correct version of the

driver.



Additional Event Data:

System IP Address...: 9.11.2.139

Event Id............: 0x41d8921700000000

Monitor Version.....: B.01.01

Event Class.........: I/O

Client Configuration File...........:

/var/stm/config/tools/monitor/default_disk_em.clcfg

Client Configuration File Version...: A.01.00

Qualification criteria met.

Number of events..: 1

Associated OS error log entry id(s):

0x41d8921700000000

Additional System Data:

System Model Number.............: 9000/800/SD32000

OS Version......................: B.11.11

STM Version.....................: A.38.00

EMS Version.....................: A.03.20

Latest information on this event:

http://docs.hp.com/hpux/content/hardware/ems/scsi.htm#100091



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...: 2/0/1/0/0.2.0

Device Class...........: Disk

Inquiry Vendor ID......: HP 36.4G

Inquiry Product ID.....: MAS3367NC

Firmware Version.......: HPC3

Serial Number..........: KT044693 0422



Product/Device Identification Information:



Logger ID.........: sdisk

Product Identifier: SCSI Disk

Product Qualifier.: HP36.4GMAS3367NC

SCSI Target ID....: 0x02

SCSI LUN..........: 0x00



I/O Log Event Data:



Driver Status Code..................: 0x0000000B

Length of Logged Hardware Status....: 36 bytes.

Offset to Logged Manager Information: 40 bytes.

Length of Logged Manager Information: 34 bytes.



Hardware Status:



Raw H/W Status:

0x0000: 00 00 00 02 70 00 06 00 00 00 00 28 00 00 00 00

0x0010: 29 02 00 00 00 00 02 2A 00 67 03 01 00 00 00 00

0x0020: 00 00 00 00



SCSI Status...: CHECK CONDITION (0x02)

Indicates that a contingent allegiance condition has occurred. Any

error, exception, or abnormal condition that causes sense data to be

set will produce the CHECK CONDITION status.



SCSI Sense Data:



Undecoded Sense Data:

0x0000: 70 00 06 00 00 00 00 28 00 00 00 00 29 02 00 00

0x0010: 00 00 02 2A 00 67 03 01 00 00 00 00 00 00 00 00



SCSI Sense Data Fields:

Error Code : 0x70

Segment Number : 0x00

Bit Fields:

Filemark : 0

End-of-Medium : 0

Incorrect Length Indicator : 0

Sense Key : 0x06

Information Field Valid : FALSE

Information Field : 0x00000000

Additional Sense Length : 40

Command Specific : 0x00000000

Additional Sense Code : 0x29

Additional Sense Qualifier : 0x02

Field Replaceable Unit : 0x00

Sense Key Specific Data Valid : FALSE

Sense Key Specific Data : 0x00 0x00 0x00



Sense Key 0x06, UNIT ATTENTION, indicates that the target has been

reset by a BUS DEVICE RESET message, a hard reset condition, or by a

power-on reset. If not a reset, then one of the following may have

occurred.

1. A removable medium may have been changed.

2. The mode parameters in effect for this initiator have been

changed by another initiator.

3. The version or level of microcode has been changed.

4. Tagged commands queued for this initiator were cleared by

another initiator.

5. INQUIRY data has been changed.

6. The mode parameters in effect for this initiator have been

restored from non-volatile memory.

7. A change in the condition of a synchronized spindle.

8. Any other event that requires the attention of the initiator.



SCSI Command Data Block:



Command Data Block Contents:

0x0000: 2A 00 00 00 13 20 00 00 04 00



Command Data Block Fields (10-byte fmt):

Command Operation Code...(0x2A)..: WRITE

Logical Unit Number..............: 0

DPO Bit..........................: 0

FUA Bit..........................: 0

Relative Address Bit.............: 0

Logical Block Address............: 4896 (0x00001320)

Transfer Length..................: 4 (0x0004)



Manager-Specific Data Fields:

Request ID.............: 0x00662F91

Data Residue...........: 0x00000800

CDB status.............: 0x00000002

Sense Status...........: 0x00000000

Bus ID.................: 0x00

Target ID..............: 0x02

LUN ID.................: 0x00

Sense Data Length......: 0x20

Q Tag..................: 0x76

Retry Count............: 1

[김병수]

scsi error가 발생된것으로 보여지는데요..



일단 사용하는데는 문제가 없어 보입니다만..혹시모르니



# demsg

error message를 확인하시고요...





backup을 받어 두시기 바랍니다.

[고광태]

위메세지는 조치 사항이 없습니다.



단순히 scsi 쪽에 에러가 발생했었다는 뜻입니다.



위와같은 메세지가 계속 발생하는지 모니터링을 하는것이 좋을듯하네요..