- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Re: Lun Lock status is unknown
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 03:58 AM
тАО04-24-2006 03:58 AM
Lun Lock status is unknown
Currently I compile the cluster script file ,and i manage bring up the cluter .
But , during i run command cmviewcl -v , i found out both server cluster lun lock status is unknown .
Please help
Thanks
Leongko
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 05:25 AM
тАО04-24-2006 05:25 AM
Re: Lun Lock status is unknown
Please post the commands you are using and the results of said commands.
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-24-2006 12:08 PM
тАО04-24-2006 12:08 PM
Re: Lun Lock status is unknown
Distro & kernel (uname -a works)
Serviceguard version
Shared storage type
Multipath SW if any
If there is anything in the system log (/var/log/messages) related to the lock lun during cluster fomration, that portionof the log is also helpful.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2006 05:02 PM
тАО04-25-2006 05:02 PM
Re: Lun Lock status is unknown
I compile the command is cmcheckconf -v -C /usr/local/cmcluster/conf/cmclconf.ascii -n Muatra005 -n Muatra004 and later is cmapplyconf -v -C /usr/local/cmcluster/conf/cmclconf.ascii .
And the output is successfull apply .
Current OS version is RHEL 3 with update3 .
I also checking the /var/log/message , i found out lun lock holding by node1( Muatra005) .At the same time , i also try to unplug all network cable on the node1( Muatra005) .The result is node2 (Muatra004) TOC (reboot) ,later node 1(Muatra005) following TOC .The package fail over to node 2 (Muatra004) .
Any idea ?
Thanks
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2006 05:09 PM
тАО04-25-2006 05:09 PM
Re: Lun Lock status is unknown
The SG cluster is version 11.16 , storage MS1000 and used qlogic failover driver kit provide from HP software and driver website .
Thanks
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2006 06:46 PM
тАО04-25-2006 06:46 PM
Re: Lun Lock status is unknown
On the cmapplyconf, I believe you are missing info in your post here. There should be a "-L" with the lock lun designator (for example /dev/sdc1). I'm guessing that you did the command correctly but didn't list all of the information here.
Can you caputure the output of the cmviewcl -v command and post it. That will show the LockLUN information as well as some other detail.
On the logs, I was not complete in my request. Can you attach just that portion of the log that has information about the lockLun and around the time you did the test you described.
Thanks
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-25-2006 09:00 PM
тАО04-25-2006 09:00 PM
Re: Lun Lock status is unknown
May I know what the command to apply the cluster file .
cmapply -v -C /usr/local/cmcluster/conf/cmclconf.ascii -n Muatra005 -L /dev/sdc2 -n Muatra004 -L /dev/sda2
This command isn't right ?
Thanks
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2006 01:16 AM
тАО04-26-2006 01:16 AM
Re: Lun Lock status is unknown
cmapply -v -C /usr/local/cmcluster/conf/cmclconf.ascii -n Muatra005 -L /dev/sdc2 -n Muatra004 -L /dev/sda2
it should be:
cmapplyconf -v -C /usr/local/cmcluster/conf/cmclconf.ascii -n Muatra005 -L /dev/sdc2 -n Muatra004 -L /dev/sda2
Again, this is likely a typo.
Also, it is unusual to have different disk identifiers for the two different nodes. Please check very carefully that /dev/sdc2 on Muatra005 and /dev/sda2 on Muatra004 are the same LUN.
Are you giving the exact command you used or are you typing an example? /dev/sda is almost ALWAYS and internal disk and could not be used as LockLUN.
Again, if you cut & paste the result of cmviewcl -v, as well as the log information requested, it would help.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2006 04:53 PM
тАО04-26-2006 04:53 PM
Re: Lun Lock status is unknown
The /dev/sda2 and /dev/sdc2 is a same lun .The device path is belong share disk so that configure as Lun Lock .
Posibble that i used the devlabel -u (device_id) -s /dev/lun on the both server .
Later on the cluster script Lun Lock change to /dev/lun ,isn't work ?
Thanks for advice
LeongKO
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-26-2006 06:13 PM
тАО04-26-2006 06:13 PM
Re: Lun Lock status is unknown
Hope this helps your understanding.
At this stage, it might be faster if you put in a call to HP support. They can help get all of the information, such as the log information, necessary fromt eh system to help with your problems.