heart beat lan pblm

[simon p j]

Here we have implemented two two node clusters.in this we are using four fibre channel gigabit lan cards for network configuration.two card is being used for stationary lan(one is configured and other one is standby) through swith and two is being used for heartbeat lan which is dircetly connected between servers not through switch.My pblm is whenever i querying through cmquerycl command the standby lan for heartbeat is not picking up.This is happening with bth the clusters and i have tried with interchanging the lan's still the sam pblm is coming.
Please help.

[RAC_1]

What version of SG? What is the message that you get? Can you post cmquerycl?

[Steven E. Protter]

Shalom,

Check the network cable.

If it is straight through, it will not work.

You need a reverse pair to network without a switch.

SEP

[Sยภเl Kย๓คг]

Hi,

Isolate HB cross cable and try cmquerycl, is this cross cable a proper one.

POST o/P of cmquerycl with all FC LAN and without cross cable HB.

Regards,
Sunil

[melvyn burnard]

This will not work!
You need to be able to physically connect between the primary and standby lan for your heartbeat for it to be able to act as a standby.
If you have the lans directly connected, this cannot happen.

You need to put a switch or network hub between the primary and standby heartbeat lans, just as you have done for the other two.

[Stephen Doud]

A standby LAN NIC can only operate as a standby if it is
- attached to the same physical network as the primary NIC,
- 'plumb'ed with and IP and a subnet mask of '0' (inet 0.0.0.0 netmask 0)
- the same type of NIC (ethernet)
- not defective

If you cannot do a linkloop -i , then the NICs cannot communicate with one another - so to SG, they are not on the same physical network.