Thanks to: Hong, Mike Pardy, Brian I'll do some testings. thanks again! Here are both answers: 1- In older versions of Veritas Cluster Server such as 1.1.1, I believe the default behavior upon encountering certain events is to panic the server. If, for example, a new server shows up on the private cluster network with the same node number as a system currently in the cluster, the original box will panic and reboot. Depending on how many links to the private network you have, it may be possible that this server lost all of its private network links simultaneously and panic()'d in order to avoid disk concurrency violations. 2- Hi, It's been awhile since i last worked with VCS but you might want to check your heatbeat connections. If i recall, when i lost both heatbeats channels, then the system would panic. Good luck, Mike Hong -----Original Message----- From: Rodrigo G [mailto:rmg00@yahoo.com] Sent: Friday, June 21, 2002 11:55 AM To: sunmanagers@sunmanagers.org Subject: Panic Hi!!, Has anyone face this problem: Solaris 2.6 Veritas Cluster 1.1.1 VM, VxFS panic[cpu3]/thread=0x3025be80: GAB: Port h halting system due to network failure Yahoo! - Official partner of 2002 FIFA World Cup http://fifaworldcup.yahoo.com _______________________________________________ sunmanagers mailing list sunmanagers@sunmanagers.org http://www.sunmanagers.org/mailman/listinfo/sunmanagersReceived on Fri Jun 21 14:33:57 2002
This archive was generated by hypermail 2.1.8 : Thu Mar 03 2016 - 06:42:47 EST