cmcheckconf fail: Failed to probe network

[Benjamin Weng]

When I using the following command to check the cluster configuration,it happens:
# cmcheckconf -C cmcluster.asc

Begin cluster verification...

Error: nodeA lan2 did not receive DLPI probe from itself.
Error: nodeA lan2 should not be included in configuration.
Failed to probe network
cmcheckconf : Unable to reconcile configuration file cmcluster.asc
with discovered configuration information.

Have anyone met this problem before?
Thanks in advance.

[Steven E. Protter]

Shalom,

Yes,

I fixed it by carefully reviewing network configuration, making sure all references in /etc/hosts to the two nodes of the cluster were consistent.

I openned up .rhosts for root, but eventually went to the /etc/cmcluster/cmnodelist for network functionality.

This is for SG 11.16 HP-UX

SEP

[Uday_S_Ankolekar]

Try cmscancl , this will produce extensive report of your cluster configuration including network issues.


-USA..

[Benjamin Weng]

Thanks for the reply
But I check the /etc/hosts and the scancl.out, everything seems normal,no warning,no error...

[melvyn burnard]

Ok, so check this lan using netstat -in and ifconfig lan2
Post th eoutput, and if necessary post the scancl.out file, indicating the node name that has the error
Also, is this a standby or primary lan?

I suspect this is a standby lan that has had something configured on it

[Benjamin Weng]

Yes,the lan2 is the standby lan.
And the main lan0 is working normaly.

[rariasn]

Hi Benjamin,

In node 1,

# cmscancl
# more /tmp/scancl.out

In node 2,

# cmscancl
# more /tmp/scancl.out

- Verify "Checking LOCAL network connections"

Ran

[Benjamin Weng]

I tried to run "cmscancl -n nodeA -n nodeB".
The output is attached.
lan0 is main, lan2 is standby and lan1 is heartbeat.

[melvyn burnard · Accepted solution]

Well from the cmscancl output Lan2 CANNOT talk to any other card out there, everything s NO CONNECTION.
You apear to have a hardware/cabling network problem which must be fixed

[Benjamin Weng]

But I have tried to use lan3 instead of lan2 to work as the standby, but when cmcheckconf,it happened the same.
I think is not possible both the lan3 and lan2 have hardware problem.
Should it be the network cable problem or the lanswitch problem?
Thanks all for the replies.

[melvyn burnard]

well it could be any of these, including a switch configurationm issue.
You will need to investigate and trouble shoot, for example move the cables to a known working switch port etc.

[Benjamin Weng]

The problem has been fixed.
Root cause is the lan2 network adapter. The "lan2" I was using in fact is the lan3...
When I plug the cable into the real "lan2", all trouble had gone...
Sorry for my naive midtake and thank you all. I really learn much from the discussion.

ps:Anyone knows how to match the lan0/lan1/lan2/lan3/lan4 with the physical ports behind the machine? Every time I need to test a lot of times to know who is who...