topic Re: Syslog error in Operating System - HP-UX

Syslog error

Gurumanickam — Thu, 11 Jan 2007 00:06:20 GMT

hi all,

Yesterday my sanswitch got hang, i restarted the san switch after that i'm getting the following error in syslog on 3 machines. i checked the fcmsutil /dev/fcd0 stat -s and fcmsutil it's online. it there any issue in this. please suggest.

Jan 9 10:42:49 sr5 EMS [2491]: ------ EMS Event Notification ------ Value: "C
RITICAL (5)" for Resource: "/adapters/events/ql_adapter/2_0_8_1_0_4_0" (Thre
shold: >= " 3") Execute the following command to obtain event details: /op
t/resmon/bin/resdata -R 163250178 -r /adapters/events/ql_adapter/2_0_8_1_0_4_0 -
n 163250178 -a
CURRENT MONITOR DATA:

Event Time..........: Tue Jan 9 10:42:48 2007
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 59
System..............: sr5

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

Description of Error:

lbolt value: 194289467

Target with device id 0x20000 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.1.1.68
Event Id............: 0x45a3245000000000
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):
0x45a3245000000000
Additional System Data:
System Model Number.............: 9000/800/rp8420
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.51.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....: 2/0/8/1/0/4/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 0B949F3B 00000001 00000001 00020000 2F75782F 636F7265 2F697375
2F464344 2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F646D
2E63

Re: Syslog error

Steven E. Protter — Thu, 11 Jan 2007 01:18:05 GMT

Shalom,

For more info:
opt/resmon/bin/resdata -R 163250178 -r /adapters/events/ql_adapter/2_0_8_1_0_4_0 -
n 163250178 -a

Its not a big deal. When a system loses track of a disk, provided through the SAN for longer than its time out value, EMS figures it out and the syslog has an lbolt.

It will stop happening the next time the system is booted.

SEP

Re: Syslog error

Andrew Merritt_2 — Thu, 11 Jan 2007 04:40:49 GMT

If you just got the one message (on each system) after the SAN switch was restarted, then I think that is normal behaviour; a problem has been recovered from, and this is being reported. I agree it is a little alarming that it is reported as a Critical event; I think this is so it is logged in the same places as the matching Event 58 which would normally precede it. The text of the message pretty much describes the situation.

If you are continuing to get Event 59 logged every day, and maybe event 58 as well, that can indicate an ongoing problem with the SAN. Sometimes a reset or reboot can clear it, otherwise I'd suggest contacting HP support.

To clarify SEP's response; you've already run the 'resdata' command. You can also see the events in the /var/opt/resmon/log/event.log file. The EMS HW monitor, dm_ql_adapter, is reporting the event detected by the device driver. An lbolt is simply a indication of elapsed time, it's not an error in itself; SCSI error reports include the lbolt as an extra piece of information to help diagnosis of the problem.

Andrew