This is a discussion on HACMP 5.3 3-nodes cluster, calls network_down 5 sec after node_up by itself within the AIX Operating System forums, part of the Unix Operating Systems category; --> Hi, We do have have problems with an 3-node HACMP cluster ver. 5.3 So the scenario is that we ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, We do have have problems with an 3-node HACMP cluster ver. 5.3 So the scenario is that we have 3 nodes and a concurent RG and all the 3 nodes are participating in it. Each node has private and public interface (the minimum scenario, no IP address or alias take over defined yet), the network connectivity is just fine, the configuration is double and tripple checked by 3 CEs and big number of references. The verification and synchronization is completing with 'Ok' with no errors and warnings. we have the application server start and stop scripts in place (blank - it's easier to debug that way) The HACMP service starts on all the 3 nodes - Ok But when we check the status of the cluster we have Node1 - up Pivate interface - up Public interface - DOWN Node2 - up Pivate interface - up Public interface - DOWN Node3 - up Pivate interface - up Public interface - UP _______________________ Node1 - ONLINE Node2 - ONLINE Node3 - ONLINE ___________________________________ Cluster - UP and STABLE ............. In the log file we can see that network_down is called by the cluster manager 5 seconds after cluster starts successfuly on nodes 1 and 2. The network configuration is as follows - we have ether channel consisted by 2 physical interfaces - over this ethercannel we have 2 interfaces in 2 different VLANs. the network is checked and it''s working more over we have that scenario working but in 2 node cluster even tried with almost mirrored configuration but with no success. Please any considerations are welcomed, will provide you with more info tomorrow. B. |