现象:HN4Linux联盟
今天下午db报了几个EMS信息.内容如下:HN4Linux联盟
EMS [3183]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/TLHN4Linux联盟
_adapter/1_0_4_1_0" (Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -RHN4Linux联盟
208601093 -r /adapters/events/TL_adapter/1_0_4_1_0 -n 208601089 -a HN4Linux联盟
详细信息如下:HN4Linux联盟
ARCHIVED MONITOR DATA:
Event Time..........: Tue Nov 13 13:26:37 2007HN4Linux联盟
Severity............: CRITICALHN4Linux联盟
Monitor.............: dm_TL_adapterHN4Linux联盟
Event #.............: 37 HN4Linux联盟
System..............: bjeopd01
Summary:HN4Linux联盟
Adapter at hardware path 1/0/4/1/0 : Target WWN no longer acceptable
HN4Linux联盟
Description of Error:
HN4Linux联盟
lbolt value: 18270782
World wide name (unique identifier) for following device has HN4Linux联盟
changed HN4Linux联盟
nport Id = 0x13800 HN4Linux联盟
Probable Cause / Recommended Action:
Unlike paralled SCSI, Fibre Channel allows easy hot-swapping of disks HN4Linux联盟
Due to address conflicts it is possible for disks to swap loop IDs HN4Linux联盟
accidently when re-plugging them into a hub. HN4Linux联盟
In order to reduce the chance of user data corruption or file system HN4Linux联盟
panics, we normally require the world wide names for a particular device HN4Linux联盟
to stay the same. Requiring the fcmsutil replace_dsk command ensures HN4Linux联盟
that the replacement is intentional. HN4Linux联盟
The driver has detected a new "world-wide name" unique identifier HN4Linux联盟
at a loop position previously occupied by a device with a different HN4Linux联盟
identifier.HN4Linux联盟
If this is due to a deliberate replacement of the HN4Linux联盟
previous device, use the fcmsutil replace_dsk command HN4Linux联盟
to allow the new device to be used. If there has HN4Linux联盟
been no intentional replacing of any devices, check HN4Linux联盟
for conflicts in address assignments of devices on HN4Linux联盟
the loop.
HN4Linux联盟
Additional Event Data: HN4Linux联盟
System IP Address...: HN4Linux联盟
System IP Address...: System IP Address...:
Event Id............: 0x4739359000000000HN4Linux联盟
Monitor Version.....: B.01.00HN4Linux联盟
Event Class.........: I/OHN4Linux联盟
Client Configuration File...........:HN4Linux联盟
/var/stm/config/tools/monitor/default_dm_TL_adapter.clcfg HN4Linux联盟
Client Configuration File Version...: A.01.00 HN4Linux联盟
Qualification criteria met.HN4Linux联盟
Number of events..: 1 HN4Linux联盟
Associated OS error log entry id(s): HN4Linux联盟
0x4739358b00000000HN4Linux联盟
Additional System Data:HN4Linux联盟
System Model Number.............: 9000/800/rp7420 HN4Linux联盟
OS Version......................: B.11.11 HN4Linux联盟
EMS Version.....................: A.04.00 HN4Linux联盟
STM Version.....................: A.45.00 HN4Linux联盟
Latest information on this event:HN4Linux联盟
http://docs.hp.com/hpux/content/hardware/ems/dm_TL_adapter.htm#37
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: HN4Linux联盟
Physical Device Path....: 1/0/4/1/0HN4Linux联盟
Vendor Id...............: 0x0000103CHN4Linux联盟
Serial Number(WWN)......: 50060B000025DF58
I/O Log Event Data:
Driver Status Code..................: 0x00000025 HN4Linux联盟
Length of Logged Hardware Status....: 0 bytes. HN4Linux联盟
Offset to Logged Manager Information: 0 bytes. HN4Linux联盟
Length of Logged Manager Information: 68 bytes.
Manager-Specific Information:
Raw data from FCMS Adapter driver: HN4Linux联盟
00000001 0116CA3E 00000003 00000001 00013800 100000E0 00000000 2F75782F HN4Linux联盟
6B65726E 2F6B6973 752F544C 2F737263 2F636F6D 6D6F6E2F 7773696F 2F74645F HN4Linux联盟
66632E63
(其他EMS信息基本与该信息相同)
*********************************************HN4Linux联盟
=======================================HN4Linux联盟
***********************************************HN4Linux联盟
分析:
是光纤卡报告的问题,所以应该查看与光纤卡连接的设备
HN4Linux联盟
步骤:
1.使用ioscan查看光纤卡HN4Linux联盟
#ioscan -fnCfcHN4Linux联盟
Class I H/W Path Driver S/W State H/W Type DescriptionHN4Linux联盟
============================================HN4Linux联盟
fc 0 1/0/2/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage AdapterHN4Linux联盟
/dev/td0HN4Linux联盟
fc 1 1/0/4/1/0 td CLAIMED INTERFACE HP Tachyon XL2 Fibre Channel Mass Storage AdapterHN4Linux联盟
/dev/td1
2.为了避免是光纤卡的问题,检查每个光纤卡:
#fcmsutil /dev/td0
Vendor ID is = 0x00103cHN4Linux联盟
Device ID is = 0x001029HN4Linux联盟
XL2 Chip Revision No is = 2.3HN4Linux联盟
PCI Sub-system Vendor ID is = 0x00103cHN4Linux联盟
PCI Sub-system ID is = 0x00128cHN4Linux联盟
Topology = PTTOPT_FABRICHN4Linux联盟
Link Speed = 2GbHN4Linux联盟
Local N_Port_id is = 0x010200HN4Linux联盟
N_Port Node World Wide Name = 0x50060b000025df55HN4Linux联盟
N_Port Port World Wide Name = 0x50060b000025df54HN4Linux联盟
Driver state = ONLINEHN4Linux联盟
Hardware Path is = 1/0/2/1/0HN4Linux联盟
Number of Assisted IOs = 77665912HN4Linux联盟
Number of Active Login Sessions = 2HN4Linux联盟
Dino Present on Card = NOHN4Linux联盟
Maximum Frame Size = 2048HN4Linux联盟
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 (PHSS_31326) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Sep 5 2005, 10:14:40
fcmsutil /dev/td1
Vendor ID is = 0x00103cHN4Linux联盟
Device ID is = 0x001029HN4Linux联盟
XL2 Chip Revision No is = 2.3HN4Linux联盟
PCI Sub-system Vendor ID is = 0x00103cHN4Linux联盟
PCI Sub-system ID is = 0x00128cHN4Linux联盟
Topology = PTTOPT_FABRICHN4Linux联盟
Link Speed = 2GbHN4Linux联盟
Local N_Port_id is = 0x010200HN4Linux联盟
N_Port Node World Wide Name = 0x50060b000025df59HN4Linux联盟
N_Port Port World Wide Name = 0x50060b000025df58HN4Linux联盟
Driver state = ONLINEHN4Linux联盟
Hardware Path is = 1/0/4/1/0HN4Linux联盟
Number of Assisted IOs = 4775204HN4Linux联盟
Number of Active Login Sessions = 2HN4Linux联盟
Dino Present on Card = NOHN4Linux联盟
Maximum Frame Size = 2048HN4Linux联盟
Driver Version = @(#) libtd.a HP Fibre Channel Tachyon TL/TS/XL2 Driver B.11.11.12 PATCH_11.11 (PHSS_31326) /ux/kern/kisu/TL/src/common/wsio/td_glue.c: Sep 5 2005, 10:14:40
发现这两个光纤卡都是online状态.
3.检查光纤卡上连接的设备中到底是哪个有问题(主要担心外接存储有问题,因为这会影响应用),用ioscan查看disk和tape
#ioscan -funC diskHN4Linux联盟
发现所有外接硬盘均能认到,且,状态正常.
#ioscan -funC tapeHN4Linux联盟
发现有几个设备是NP_HW状态:HN4Linux联盟
tape 34 1/0/2/1/0.1.56.255.0.0.0 stape NO_HW DEVICE HP Ultrium 3-SCSIHN4Linux联盟
/dev/rmt/34m /dev/rmt/34mn HN4Linux联盟
/dev/rmt/c26t0d0BEST /dev/rmt/c26t0d0BESTn HN4Linux联盟
/dev/rmt/34mb /dev/rmt/34mnb HN4Linux联盟
/dev/rmt/c26t0d0BESTb /dev/rmt/c26t0d0BESTnbHN4Linux联盟
tape 37 1/0/2/1/0.1.56.255.0.0.1 stape NO_HW DEVICE HP Ultrium 3-SCSIHN4Linux联盟
/dev/rmt/37m /dev/rmt/37mn HN4Linux联盟
/dev/rmt/c26t0d1BEST /dev/rmt/c26t0d1BESTn HN4Linux联盟
/dev/rmt/37mb /dev/rmt/37mnb HN4Linux联盟
/dev/rmt/c26t0d1BESTb /dev/rmt/c26t0d1BESTnb
4.结论:HN4Linux联盟
确定是带机的问题.现在正有HP工程师在对带机做些操作.该EMS不是系统问题.而是td0和td1这两个光纤卡无法识别该带机.
****************************************
5.总结:HN4Linux联盟
也可以用一个相对简单的方法来检查.HN4Linux联盟
1)先看报错的设备的nportID为0x13800.HN4Linux联盟
2)其中,0x后面的1,对应的是设备地址中第一个小数点后面的1.HN4Linux联盟
3)再看nport中,1后面的38.该数值是16进制,转换成10进制,则为56.即可判断问题设备的硬件地址为1/0/4/1/0.1.56HN4Linux联盟
4)经ioscan查看,该设备为Ultrium 3的带库.HN4Linux联盟
Linux联盟收集整理 ,转贴请标明原始链接,如有任何疑问欢迎来本站Linux论坛讨论