ERROR in re-configuration cluster

[Marcelo De Florio_1]

i have a followgin messagge error in re-configuration of cluster:

Error: Non-uniform connections detected,
a2500 lan0 successfully received from a2500 lan2
but a2500 lan2 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
s2500d lan5 successfully received from a2500 lan0
but a2500 lan0 did not receive from s2500d lan5.
This is probably due to heavy network traffic or heavy load on s2500d.
Error: Non-uniform connections detected,
a2500 lan2 successfully received from a2500 lan0
but a2500 lan0 did not receive from a2500 lan2.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
s2500c lan5 successfully received from a2500 lan0
but a2500 lan0 did not receive from s2500c lan5.
This is probably due to heavy network traffic or heavy load on s2500c.
Error: Non-uniform connections detected,
s2500b lan5 successfully received from a2500 lan0
but a2500 lan0 did not receive from s2500b lan5.
This is probably due to heavy network traffic or heavy load on s2500b.
Error: Non-uniform connections detected,
s2500b lan4 successfully received from a2500 lan0
but a2500 lan0 did not receive from s2500b lan4.
This is probably due to heavy network traffic or heavy load on s2500b.
Error: Non-uniform connections detected,
s2500a lan5 successfully received from a2500 lan0
but a2500 lan0 did not receive from s2500a lan5.
This is probably due to heavy network traffic or heavy load on s2500a.
Error: Non-uniform connections detected,
s2500a lan4 successfully received from a2500 lan0
but a2500 lan0 did not receive from s2500a lan4.
This is probably due to heavy network traffic or heavy load on s2500a.
Error: Non-uniform connections detected,
a2500 lan0 successfully received from s2500a lan5
but s2500a lan5 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
a2500 lan0 successfully received from s2500a lan4
but s2500a lan4 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
a2500 lan0 successfully received from s2500b lan5
but s2500b lan5 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
a2500 lan0 successfully received from s2500b lan4
but s2500b lan4 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
a2500 lan0 successfully received from s2500c lan5
but s2500c lan5 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: Non-uniform connections detected,
a2500 lan0 successfully received from s2500d lan5
but s2500d lan5 did not receive from a2500 lan0.
This is probably due to heavy network traffic or heavy load on a2500.
Error: lan0 on node a2500 cannot be configured in the cluster
because it does not have an IP address, and it is not a standby lan for any oth
er lan.
Failed to evaluate network
cmapplyconf : Unable to reconcile configuration file S2500.config.20020703
with discovered configuration information.

any ideas.

MDF

[melvyn burnard]

Your network configuration is bust!
start verifying that the cards can linkloop to each other in the way you expect.
This is normally caused by:
a) faulty or incorrectly connected cables
b) faulty hub/switch ports
c) faulty hardware

[Carsten Krege]

The SG 11.09 patch PHSS_21425 and the SG 10.12 patch PHSS_21995 fix the following problem:

2. ServiceGuard config commands(cmcheckconf, cmapplyconf) consistently fail to configure a cluster with error "Non-uniform connections detected". The problem is more likely to occur on large cluster configurations.

The fix is already implemented in later versions of SG (SG 11.12 and up), but the problem exists in all earlier versions of SG (SG 11.09 and earlier on HPUX 11.x and on SG 10.12 and earlier on HPUX 10.x).

Other problems of this sort involved the usage of NIS, when nodename resolution took a long time (SG waits up to 3 sec for a reply to the network probing). Make sure you use the /etc/cmcluster/cmclnodelist file for access between nodes.

Carsten