Cluster disk lock error message in syslog

[Mahesh Alexander]

Dear friends,

I've been looking something about this message but couldn't find great stuff about it. Could anyone tell me what exactly this error means please? And how to get rid of it?

cmdisklockd[2507]: Still trying to inquire cluster lock disk /dev/dsk/c13t0d1

Thank you very much for your help.

[dipesh_2]

send the cmviewcl -v output from cluster node to verify

[Ganesan R]

Hi Mahesh,

It looks some issue with the lock disk. Either the lock disk may not be accessible or cluster lock information is missing on the system.
Are you able to access the lock disk c13t0d1 on the system where you are getting the message?

Have you replaced the lock disk recently and forget to update cluster structure on that disk?

[Steven E. Protter]

Shalom,

dmesg

grep lbolt /var/adm/syslog/syslog.log

See if the message matches this device.

Use cstm mstm or xstm to exercise the disk

dd if=/dev/dsk/c13t0d1 of=/dev/null count=10000
rc=$?
echo rc

SEP

[Prashanth Waugh · Accepted solution]

HI,

It seems the problem related to cluster lock disk but it will not create any problem to cluster . But This will crash the cluster if any thing failure happen in any nodes . so check it on high priorty is there any issue related to disk.
-------------------------

Check the cluster lock disk in cluster config file .then use the belwo steps
1) ioscan -fnC disk | grep "disk name"
2) diskinfo /dev/rdsk/cntndn which is mention in cluster config file.
3) check the /var/opt/resmon/event.log
4) check syslog
--------------------------

Regards
Prashnat

[Mahesh Alexander]

Hi all,

Thank you for your posts. Was a bit busy today so couldn't really check yet but will do and review it with your advises asap.

Thanks!!
Regards,

[Mahesh Alexander]

Hi again,

I found those messages in the event.log file:

============================================
>------------ Event Monitoring Service Event Notification ------------<

Notification Time: Sun Jun 28 16:43:24 2009

burbapp2 sent Event Monitor notification information:

/adapters/events/ql_adapter/0_0_14_1_0_4_0 is >= 1.
Its current value is CRITICAL(5).



Event data from monitor:

Event Time..........: Sun Jun 28 16:43:24 2009
Severity............: CRITICAL
Monitor.............: dm_ql_adapter
Event #.............: 58
System..............: burbapp2

Summary:
Adapter at hardware path 0/0/14/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: 585202005

The device id has disappeared from Name Server GPN_FT (FCP type) response
OR Port World-wide name for device id 0x60000 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.

===========================================
And just after 2:13 minutes the device is back:

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

What is the cause?
How could I get rid of this loss and reconnection? Maybe with STM?

Thanks!

[Prashanth Waugh]

Hi Mahesh,

It will not cause any problem. but better u can raise the call with HP .

[Mahesh Alexander]

Hi, thanks mate! I'll give a call to HP people.

Thank you.