Summary: issues with cluster 3.2

Thanks to Murat BALKAS, and "aams listastecnicas", for confirming my 
suspecion. The problem with with cluster interconnect being on the same 
vlan. I have used cross cable and the errors are gone. 

Regarding the second error which i hv posted

May 25 19:24:40 orarac01 Cluster.SMF.DR: Unable to open door descriptor 
/var/run
/rgmd_receptionist_door
May 25 19:24:40 orarac01 Cluster.SMF.DR:
May 25 19:24:40 orarac01  Error in scha_cluster_get

its a bug and can be ignored, see CR 6490541

thanks


Ayaz Anjum 




Ayaz Anjum/IT/QGPC 
05/25/2007 07:27 PM

To

cc

Subject
issues with cluster 3.2





HI ! 

I am evaluating sun cluster 3.2 and facing following wierd issues  ( 
solaris 10 11/06 ) 

1. While installing i have specified a non default private interconnect ip 
addresses ( 10.20.0.0) 
Cluster nodes boots up fine but then i get following messages 

first node - orarac01 
May 25 16:32:29 orarac01 ip: [ID 903730 kern.warning] WARNING: IP: 
Hardware address '00:00:00:00:00:01' trying to be our address 
010.020.004.001! 

second node =- orarac02 
May 25 17:12:28 orarac02 ip: [ID 903730 kern.warning] WARNING: IP: 
Hardware address '00:00:00:00:00:02' trying to be our address 
010.020.004.002! 


I am using ce3 and ce7 for cluster interconect and i see following on both 
nodes 

orarac01: 
ce3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 
index 5 
        inet 10.20.0.129 netmask ffffff80 broadcast 10.20.0.255 
        ether 0:3:ba:db:9d:a3 
ce7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 
index 4 
        inet 10.20.1.1 netmask ffffff80 broadcast 10.20.1.127 
        ether 0:3:ba:3:7b:2e 
clprivnet0: 
flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 
1500 index 6 
        inet 10.20.4.1 netmask fffffe00 broadcast 10.20.5.255 
        ether 0:0:0:0:0:1 

orarac02: 
ce3: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 
index 4 
        inet 10.20.0.130 netmask ffffff80 broadcast 10.20.0.255 
        ether 0:3:ba:db:6c:af 
ce7: flags=1008843<UP,BROADCAST,RUNNING,MULTICAST,PRIVATE,IPv4> mtu 1500 
index 3 
        inet 10.20.1.2 netmask ffffff80 broadcast 10.20.1.127 
        ether 0:3:ba:3:bb:52 
clprivnet0: 
flags=1009843<UP,BROADCAST,RUNNING,MULTICAST,MULTI_BCAST,PRIVATE,IPv4> mtu 
1500 index 5 
        inet 10.20.4.2 netmask fffffe00 broadcast 10.20.5.255 
        ether 0:0:0:0:0:2 

i dont see and address conflict in above ifconfig output, but from the 
messages the nodes are complaining about the other member. 

Using the new feature of cluster 3.2, i booted in non cluster mode, and 
did clsetup to change the private ip address to default range but it gave 
me errors 
"remote access attempt to one or more of the other nodes failed" and i am 
not able to change the ip address 

Other error which i am gettting on reboots

May 25 19:24:40 orarac01 Cluster.SMF.DR: Unable to open door descriptor 
/var/run
/rgmd_receptionist_door
May 25 19:24:40 orarac01 Cluster.SMF.DR:
May 25 19:24:40 orarac01  Error in scha_cluster_get

I hv just installed cluster one node at a time, and reset the install 
mode, no configurations done


any suggestions 

thanks 




Ayaz Anjum 
Ayaz Anjum 
Systems Engineer , ITT/E6
Information Technology Department 
Qatar Petroleum 
P.O. Box 47   Doha, Qatar 
Tel +974 4405280 Cell +974 5729770
anjum@qp.com.qa  www.qp.com.qa 







-------------------------------------------------------------------------------------------------- 

Confidentiality Notice : This e-mail  and  any attachments  are 
confidential  to  the addressee and may also be privileged.  If  you are 
not  the addressee of  this e-mail, you may not copy, forward, disclose or 
otherwise use it in any way whatsoever.  If you have received this e-mail 
by mistake,  please  e-mail  the sender by replying to this message, and 
delete the original and any print out thereof. 








-------------------------------------------------------------------------------------------------- 

Confidentiality Notice : This e-mail  and  any attachments  are 
confidential  to  the addressee and may also be privileged.  If  you are 
not  the addressee of  this e-mail, you may not copy, forward, disclose or 
otherwise use it in any way whatsoever.  If you have received this e-mail 
by mistake,  please  e-mail  the sender by replying to this message, and 
delete the original and any print out thereof. 
_______________________________________________
sunmanagers mailing list
sunmanagers@sunmanagers.org
http://www.sunmanagers.org/mailman/listinfo/sunmanagers