1754355 Members
5026 Online
108813 Solutions
New Discussion юеВ

warning logs Server

 
SOLVED
Go to solution
Eli Daniel
Super Advisor

warning logs Server

Hi,
i have warning in the syslog:

ARCHIVED MONITOR DATA:

Event Time..........: Tue Apr 13 17:46:46 2010
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 62
System..............: sback900

Summary:
Adapter at hardware path 0/0/14/1/0/4/0 : Fabric Name Server rejected
GPN_FT query



Description of Error:


lbolt value: 1262180648

Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request.
Explanation: FC-4 Type not registered.


Probable Cause / Recommended Action:

The HBA port may not be part of a zone.
Please check zone configuration on your switch.


Additional Event Data:
System IP Address...: 10.1.0.162
Event Id............: 0x4bc4ed4e00000000
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):
0x4bc4ed4e00000000
Additional System Data:
System Model Number.............: ia64 hp server rx7640
OS Version......................: B.11.23
EMS Version.....................: A.04.20
STM Version.....................: C.60.00
Latest information on this event:
http://docs.hp.com/hpux/content/hardware/ems/dm_ql_adapter.htm#62

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/0/14/1/0/4/0

I/O Log Event Data:

Driver Status Code..................: 0x0000003E
Length of Logged Hardware Status....: 0 bytes.
Offset to Logged Manager Information: 0 bytes.
Length of Logged Manager Information: 65 bytes.

Manager-Specific Information:

Raw data from FCMS Adapter driver:
00000001 4B3B5928 00000000 00000001 2F75782F 636F7265 2F697375 2F464344
2F6B6572 6E2F7372 632F636F 6D6D6F6E 2F777369 6F2F6663 645F7072 6F62652E
63
10 REPLIES 10
Steven E. Protter
Exalted Contributor
Solution

Re: warning logs Server

Shalom,

This looks to me like a disk array is being detected on LUN0. The disk array is not a disk and throws errors.

The solution is to have storage present a disk in LUN0 and that will prevent this from happening.

Or ignore it.

SEP
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
Tim Nelson
Honored Contributor

Re: warning logs Server

I would have to say it means just what it says.

"Description of Error:


lbolt value: 1262180648

Fabric Name Server rejected GPN_FT query.
Reason code: unable to perform request.
Explanation: FC-4 Type not registered.


Probable Cause / Recommended Action:

The HBA port may not be part of a zone.
Please check zone configuration on your switch."



Is this port zoned on the switch ? Any SAN config changes recently ?
Eli Daniel
Super Advisor

Re: warning logs Server

the administracion SAN is by for other group in the organizacion.
these problem is switch or the server (hardware)
Eli Daniel
Super Advisor

Re: warning logs Server

please,
these problem is switch or the server (hardware)??
Eli Daniel
Super Advisor

Re: warning logs Server

anex the images.
cnb
Honored Contributor

Re: warning logs Server

Eli,

Need to look at the other paired message in EMS per the link:

http://docs.hp.com/en/diag/ems/dm_ql_adapter.htm


"Event 62

Severity: CRITICAL
Description: Port World-wide name for device id 0x! has changed OR the device id has disappeared from Name Server GPN_FT (FCP type) response.

device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices.

Cause: This is a paired message with "Target device is lost in the Name Server GPN_FT response". No action is needed. 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.

Action: Driver will be able to communicate with the device. "

You would need to see if there are lots of these occuring, if only one time, monitor it.

Otherwise you will need to check to see if your patches are up to date, analyze the fabric with tools like fcmsutil, etc...

Also see this thread:

http://forums11.itrc.hp.com/service/forums/questionanswer.do?threadId=994641&admit=109447626+1272059014449+28353475



Rgds,
Eli Daniel
Super Advisor

Re: warning logs Server

Do not really understand the failure. this fault is software or hardware?
S.N.S
Valued Contributor

Re: warning logs Server

Eli,
Just to help you out-->
As per experts advice', it is not a Hardware problem; but merely an issue due to wrong configuration...

Read thru the messages posted + the link that had been provided

HTH
SNS
"Genius is 1% inspiration, 99% Perspiration" - Edison
Eli Daniel
Super Advisor

Re: warning logs Server

thansk, this wrong configuration is fibra channel? or switch??