HPE EVA Storage

log messages in /var/adm/syslog/syslog.log regarding FCMS

 
SOLVED
Go to solution
periyasamy
Advisor

log messages in /var/adm/syslog/syslog.log regarding FCMS

Hi
I have a problem with hp-ux servers log messages.In one of my hp-ux server's(11i v3) log message i had seen the following messages,If anybody knows why this message has generated and hoe to resolve it,Pls help me


output of /var/aadm/syslog/syslog.log
ct 10 01:40:32 ghiaadb2 vmunix: 0/3/1/0/4/0: Device at device id 0x11400 has disappeared from Name Server GPN_FT
Oct 10 01:40:32 ghiaadb2 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Oct 10 01:40:32 ghiaadb2 vmunix: device id = loop id, for private loop devices
Oct 10 01:40:08 ghiaadb2 ntalkd[12400]: Bad protocol version 214
Oct 10 01:40:32 ghiaadb2 above message repeats 2 times
Oct 10 01:40:32 ghiaadb2 vmunix: device id = nport ID, for fabric/public-loop devices
Oct 10 01:40:32 ghiaadb2 vmunix: System won't be able to see LUNs behind this port.
Oct 10 01:40:32 ghiaadb2 vmunix:
Oct 10 01:40:32 ghiaadb2 EMS [2249]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/ql_adapter/0_3_1_0_4_0"
(Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 147390466 -r /adapters/events/ql_adapter/0_3_1_
0_4_0 -n 147390517 -a
Oct 10 01:40:33 ghiaadb2 vmunix: 0/4/1/0/4/0: Device at device id 0x21400 has disappeared from Name Server GPN_FT
Oct 10 01:40:33 ghiaadb2 vmunix: (FCP type) response, or its 'Port World-Wide Name' has changed.
Oct 10 01:40:33 ghiaadb2 vmunix: device id = loop id, for private loop devices
Oct 10 01:40:33 ghiaadb2 vmunix: device id = nport ID, for fabric/public-loop devices
Oct 10 01:40:33 ghiaadb2 vmunix: System won't be able to see LUNs behind this port.
Oct 10 01:40:33 ghiaadb2 vmunix:
Oct 10 01:40:33 ghiaadb2 EMS [2249]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/ql_adapter/0_4_1_0_4_0"
(Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 147390471 -r /adapters/events/ql_adapter/0_4_1_
0_4_0 -n 147390518 -a
Oct 10 01:40:38 ghiaadb2 ntalkd[12400]: Bad protocol version 214
Oct 10 01:40:54 ghiaadb2 vmunix: 0/3/1/0/4/0: Device at device id 0x11400 is back in Name Server GPN_FT (FCP type)
Oct 10 01:40:54 ghiaadb2 vmunix: response, and its 'Port World-Wide Name' remains the same as
Oct 10 01:40:54 ghiaadb2 vmunix: original.
Oct 10 01:40:54 ghiaadb2 vmunix: device id = loop id, for private loop devices
Oct 10 01:40:54 ghiaadb2 vmunix: device id = nport ID, for fabric/public-loop devices
Oct 10 01:40:54 ghiaadb2 vmunix: System will be able to see LUNs behind this port
Oct 10 01:40:54 ghiaadb2 vmunix: (might need to run 'ioscan' first).
Oct 10 01:40:54 ghiaadb2 vmunix:
Oct 10 01:40:54 ghiaadb2 EMS [2249]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/ql_adapter/0_3_1_0_4_0"
(Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 147390466 -r /adapters/events/ql_adapter/0_3_1_
0_4_0 -n 147390519 -a
Oct 10 01:40:58 ghiaadb2 vmunix: 0/4/1/0/4/0: Device at device id 0x21400 is back in Name Server GPN_FT (FCP type)
Oct 10 01:40:58 ghiaadb2 vmunix: response, and its 'Port World-Wide Name' remains the same as
Oct 10 01:40:58 ghiaadb2 vmunix: original.
temp (50%)Oct 10 01:40:58 ghiaadb2 vmunix: device id = loop id, for private loop devices
Oct 10 01:40:58 ghiaadb2 vmunix: device id = nport ID, for fabric/public-loop devices
Oct 10 01:40:58 ghiaadb2 vmunix: System will be able to see LUNs behind this port
Oct 10 01:40:58 ghiaadb2 vmunix: (might need to run 'ioscan' first).
Oct 10 01:40:58 ghiaadb2 vmunix:
Oct 10 01:40:58 ghiaadb2 EMS [2249]: ------ EMS Event Notification ------ Value: "CRITICAL (5)" for Resource: "/adapters/events/ql_adapter/0_4_1_0_4_0"
(Threshold: >= " 3") Execute the following command to obtain event details: /opt/resmon/bin/resdata -R 147390471 -r /adapters/events/ql_adapter/0_4_1_
0_4_0 -n 147390520 -a
8 REPLIES 8
OFC_EDM
Respected Contributor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Looks like you're having a problem communicating with the switch. May be a card, or switch issue. Either way it can't see the LUNs accoring to the messages.

How do you zone your SAN?

Did you run
/opt/resmon/bin/resdata -R 147390466 -r /adapters/events/ql_adapter/0_3_1_
0_4_0 -n 147390517 -a
as suggested in the log. It may give you more information.

Please post output.


Cheers
The Devil is in the detail.
OFC_EDM
Respected Contributor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Looking at it closer the "device" is disappearing / reappearing from the Name Server....from the switch(?).

Have someone look at the switch and see if there's issues with the port. Look at the simple things first...is the cable plugged well at both ends?

As well running an ioscan and ensuring everything is Claimed would be a start.

Is this a production / dev / test system?
The Devil is in the detail.
Ninad_1
Honored Contributor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Hi,

Were these errors noted only once or they had occured earlier as well OR have repeated again ?
Since the disappearing and reappearing is in such a short time, it could also be as a result of say firmware upgrade activity done or switch or something like that.
Please check with your Storage admin on such possibility.

Regards,
Ninad
periyasamy
Advisor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Hi Kevin
I had added the following command with output
from server.If i want to check the physical connectivity(ststus) in san with the server
how i can check,anybody having idea in that,because i am new in hp-eva4000 san enviroment.

output of /opt/resmon/bin/resdata -R 147390466 -r /adapters/events/ql_adapter/0_3_1_
0_4_0 -n 147390517 -a


ARCHIVED MONITOR DATA:

Event Time..........: Fri Oct 10 01:40:33 2008
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 58
System..............: ghiaadb1

Summary:
Adapter at hardware path 0/4/1/0/4/0 : Device id has disappeared from
GPN_FT response or
Port World-wide name for device has changed.



Description of Error:


lbolt value: 385250399

The device id has disappeared from Name Server GPN_FT (FCP type) response
OR Port World-wide name for device id 0x11400 has changed.
device id = loop id, for private loop devices
device id = nport ID, for fabric/public-loop devices


Probable Cause / Recommended Action:

On receiving 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 discovered device
(Nport_id) is no longer in the GPN_FT response, or it's
corresponding World-Wide Name has changed.

Driver won't be able to communicate with the device any
more, please check that device.
If the problem persists, please contact your HP customer
representative.


Additional Event Data:
CowBoy
Regular Advisor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Dear All
I still have the same problem .
I have Changed the OS(HP-UX),Fiber Card,Fiber Cable and also the server(RP-8420)
but still the problem exists.
The Only thing that i have not changed were the SAN Switches.
Today I want to change the SAN but I dont know what should i do if the the problem will exist.
Dileep..
Trusted Contributor
Solution

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

hell0,

I assume this switch is a Brocade Switch.

Changing OS/FC card /switch/cable is not solution for this issue. this message just indicate that .

1) the WWN number of the device connected to 14th port of switch (both the switch Domain1 & 2) has changed

2)Device which was connected to 14th port of both the switch has been removed.

from the logs i could see that this server has 2 FC cards and is connected to both the san switches ( Domain ID 1 & 2) . I would suggest to focus on the device connected to port14 and findout what exaclty happened to that during the time of these events.


Dileep..
Trusted Contributor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Sorry the port number is not "14",it is "20".

The NPORT ID mentioned in the log is Hex format.
Piyush Trambadiya
Occasional Advisor

Re: log messages in /var/adm/syslog/syslog.log regarding FCMS

Hello There,

I am also getting the same errors in multiple servers ! And the common thing is the device id - 0x21400 among all servers.
I have checked and suspected some Tape drives are being shared by multiple servers. and suspecting the error from them...