I saw a message in syslog to check for an EMS Event Notification.
root@hp-ux:/ # cat /var/adm/syslog/syslog.log
Jul 23 11:33:07 hp-ux EMS [2596]: —— EMS Event Notification —— Value: “SERIOUS (4)” for Resource: “/adapters/events/TL_adapter/0_2_1_0″ (Threshold: >= ” 3″) Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 170131458 -r /adapters/events/TL_adapter/0_2_1_0 -n 170131457 -a
root@hp-ux:/ # /opt/resmon/bin/resdata -R 170131458 -r /adapters/events/TL_adapter/0_2_1_0 -n 170131457 -a
CURRENT MONITOR DATA:
Event Time……….: Thu Jul 23 11:33:07 2009
Severity…………: SERIOUS
Monitor………….: dm_TL_adapter
Event #………….: 23
System…………..: hp-ux
Summary:
Adapter at hardware path 0/2/1/0 : Fibre Channel driver has gone into
non-participating mode
Description of Error:
lbolt value: 3207
The Fibre Channel Driver has gone into non-participating mode
Frame Manager Status Register = 0x200002ff
Probable Cause / Recommended Action:
A cable or hardware problem exists. This can also be caused due
to the Tachyon TL adapter changing its AL_PA across a LIP.
Do the following:
1. Verify that the fiber optic cable is functional and securely
attached to the Fibre Channel Mass Storage Adapter.
2. After checking the cabling, execute a loopback test using
fcmsutil.
Command syntax is as follows:
/opt/fcms/bin/fcmsutil <device_file> lb plm
If the problem persists after verifying fiber optic cabling,
replace the adapter
Additional Event Data:
System IP Address…: 10.122.100.24
Event Id…………: 0x4a6874a300000000
Monitor Version…..: B.01.00
Event Class………: I/O
Client Configuration File………..:
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg
Client Configuration File Version…: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x4a68739100000000
Additional System Data:
System Model Number………….: 9000/800/rp4440
OS Version………………….: B.11.11
EMS Version…………………: A.04.20
STM Version…………………: A.49.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#23
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/2/1/0
Vendor Id……………: 0x0000103C
Serial Number(WWN)……: 50060B00005FCE46
I/O Log Event Data:
Driver Status Code………………: 0x00000017
Length of Logged Hardware Status….: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 61 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver:
00000003 00000C87 00000001 00000001 200002FF 2F75782F 6B65726E 2F6B6973
752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F 6973722E 63
Checking the device file.
root@hp-ux:/ # ioscan -fnC fc
Class I H/W Path Driver S/W State H/W Type Description
=================================================================
fc 0 0/2/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td0
fc 1 0/6/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage Adapter
/dev/td1
I tried to pass td1 as argument but it needed the full path.
root@hp-ux:/ # /opt/fcms/bin/fcmsutil td1 lb plm
Error: FCP driver not loaded.
I passed the entire path and the fcmsutil worked:
root@hp-ux:/ # /opt/fcms/bin/fcmsutil /dev/td0 lb plm
WARNING: This is a DESTRUCTIVE test.
This might result in failure of current I/O requests.
Do you want to continue? (y/n) [n]…
setaOffice 
You must be logged in to post a comment.