cmcheckconf fail: Failed to probe network

[Lana Klosterman]

Checking cluster file: S01_cluster.config

Checking nodes ... Done

Checking existing configuration ... Done

Gathering storage information

Found 110 devices on node ftlssaps1s01

Found 110 devices on node ftlssaps2s01

Analysis of 220 devices should take approximately 2 seconds

0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%

Found 5 volume groups on node ftlssaps1s01

Found 5 volume groups on node ftlssaps2s01

Analysis of 10 volume groups should take approximately 1 seconds

0%----10%----20%----30%----40%----50%----60%----70%----80%----90%----100%

Gathering network information

Beginning network probing (this may take a while)

Completed network probing

Detected a partition of IPv4 subnet 192.168.226.0.

Partition 1

ftlssaps1s01 lan1

Partition 2

ftlssaps2s01 lan1

Failed to evaluate network

cmcheckconf: Unable to reconcile configuration file S01_cluster.config

with discovered configuration information.

[freddy_21]

Hello Lana,

Please check network connectivity using linkloop command

linkloop -i < lan number> < station address>

note: station address, you can find with lanscan command.

please check beetwen primary lan and heart beat lan. it must no connection beetween heartbeat and primary lan.

example at ascii file:

CLUSTER_NAME cwg

NODE_NAME cwgmatrx
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.168.12.3
NETWORK_INTERFACE lan1
HEARTBEAT_IP 10.10.24.3
NETWORK_INTERFACE lan2


NODE_NAME cwgepath
NETWORK_INTERFACE lan0
HEARTBEAT_IP 192.168.12.2
NETWORK_INTERFACE lan1
HEARTBEAT_IP 10.10.24.2
NETWORK_INTERFACE lan2


lan0 and lan1 have not connection each other.

thanks
freddy

[melvyn burnard]

Detected a partition of IPv4 subnet 192.168.226.0
This is telling you there is a problem on this subnet, where the lans cannot talk to each other.
You need to investigate this and fix it.
Check cabling, configuration settings etc.

[Stephen Doud]

Serviceguard validates layer 2 DLPI protocol (data link level) between NICs. If there is no connectivity, or something blocks DLPI transmission between NICs expected to be on the same network, the message is generated.