lbolt value: 22175434

[Asif Sharif]

Hi,
I have this error in the my one box rp3440
.It appers every two or three days. Do I have to do something??
The error is ,

++++++++++++++++++++++++++++++++++++++++++++++
tppovw02:/#/opt/resmon/bin/resdata -R 147128325 -r
/adapters/events/ql_adapter/0_3_1_1 -n 147128324 -a

CURRENT MONITOR DATA:

Event Time..........: Sat Jul 30 16:06:18 2005
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 59
System..............: tppovw02.asif.com.pk

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



Description of Error:


lbolt value: 22175434

Target with device id 0x40100 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...: 192.1.1.23
Event Id............: 0x42eb5f2a00000000
Monitor Version.....: B.01.00
Event Class.........: I/O
Client Configuration File...........:
/var/stm/config/tools/monitor/default_dm_ql_adapter.clcfg
Client Configuration File Version...: A.01.00
Qualification criteria met.
Number of events..: 1
Associated OS error log entry id(s):
0x42eb5f2a00000000
Additional System Data:
System Model Number.............: 9000/800/rp3440
OS Version......................: B.11.11
EMS Version.....................: A.04.00
STM Version.....................: A.45.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/3/1/1

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: 62 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 01525ECA 00000001 00000001 00040100 2F75782F 6B65726E 2F6B6973
752F4643 442F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F646D 2E63

[Mahesh Kumar Malik]

Hi Asif

Update the driver for FC card before you decise to replace it. A typical driver download is available at following link


http://h20000.www2.hp.com/bizsupport/TechSupport/DriverDownload.jsp?locale=en_US&pnameOID=331466&taskId=135&prodTypeId=329290&prodSeriesId=331464〈=en&cc=us&swEnvOID=7

Check the model of FC HBA and download the coreect driver

Regards
Mahesh