nas和sun cluster集成的重点须知！！

nimysun

去掉该贴的隐藏属性，向公众开放几天。
###################################
需要更改部分启动脚本，确认在cluster启动之前，nas已经准备好了。


举例：
I have configured a nas quorum device, following these documents:
Sun Cluster 3.1 With Network-Attached Storage Devices Manual for Solaris OS
Sun Cluster System Administration Guide for Solaris OS ---> How to Add a Network Appliance Network-Attached Storage (NAS) Quorum Device.
Server names are: alamo and tannenberg:
Netapp Filer name is cannonau.admin
Steps:
Setup a NAS device and a LUN
Install in both nodes ,Software to support NetApp filer with Sun Cluster.
#pkgadd NTAPclnas
Add the NAS device to the cluster:
#scnas -a -h cannonau.admin -t netapp -o userid=root
Add the NAS volume to the cluster (this volume contain the LUN):
#scnasdir -a -h cannonau.admin -d /vol/QUORUM_UKT (maybe this step is not necessary)
Add Network Appliance quorum devices:
#scconf -a -q name=ukt_canno,type=netapp_nas,filer=cannonau.admin,lun_id=1
Up to here it seems everything is ok:
[root@alamo:/>>scstat -q
-- Quorum Summary --
Quorum votes possible: 3
Quorum votes needed: 2
Quorum votes present: 2
-- Quorum Votes by Node --
Node Name Present Possible Status
--------- ------- -------- ------
Node votes: alamo 1 1 Online
Node votes: tannenberg 1 1 Online
-- Quorum Votes by Device --
Device Name Present Possible Status
----------- ------- -------- ------
Device votes: ukt_canno 1 1 Online
Problems:
After rebooting tannenberg, the server starts without problem, but with this warning:
NOTICE: CMM: Node tannenberg: joined cluster.
WARNING: CMM: Reading reservation keys from quorum device ukt_canno failed.
When reboot alamo, the server panic:
tannenberg console login: Sep 28 14:47:58 tannenberg cl_runtime: NOTICE: CMM: Node alamo (nodeid =
panic[cpu1]/thread=3000349f7e0: CMM: Cluster lost operational quorum; aborting.
When the servers starts, they show this logs and warning:
from tannenberg:
NOTICE: CMM: Node tannenberg: joined cluster.
NOTICE: CCR: Waiting for repository synchronization to finish.
WARNING: CMM: Reading reservation keys from quorum device ukt_canno failed.
From alamo:
NOTICE: clcomm: Path alamo:hme0 - tannenberg:hme0 being initiated
NOTICE: CMM: Node tannenberg (nodeid: 2, incarnation #: 1127911851) has become reachable.
NOTICE: clcomm: Path alamo:hme0 - tannenberg:hme0 online
WARNING: CMM: Reading reservation keys from quorum device ukt_canno failed.
Besides, when the server are up the quorum is Offline:
[root@tannenberg:/>>scstat -q
-- Quorum Summary --
Quorum votes possible: 3
Quorum votes needed: 2
Quorum votes present: 2
-- Quorum Votes by Node --
Node Name Present Possible Status
--------- ------- -------- ------
Node votes: alamo 1 1 Online
Node votes: tannenberg 1 1 Online
-- Quorum Votes by Device --
Device Name Present Possible Status
----------- ------- -------- ------
Device votes: ukt_canno 0 1 Offline



处理方法：
The problem doesn't seem to be about routing. As you said, our NAS device is on the same network the cluster is.
The cluster is starting in rcS.d, while the network interfaces are getting up in rc2.d. This causes the cluster not being able to reach the NAS device - and the quorum iSCSI itself -, because there are no interfaces plumbed.

We've finally solved the problem by moving the original /etc/rcS.d/S72bootcluster.sh to level 2 scripts, just after S72inetsvc, and before S72sc_update*


本文来自ChinaUnix博客，如果查看原文请点：http://blog.chinaunix.net/u/43/showart_338855.html