Cluster heartbeat

[Torfi Olafur Sverrisson_1]

Hi

I've created a two node cluster, each have 1 FDDI and 2 1Gb Ethernet NICs.

The cluster is up and running and now I trying to find out which of the NICs are responsable for the Cluster heartbeat if I remove the FDDI ring.

Can any one help me in this matter?

Regards, Torfi.

[Mobeen_1]

Torfi,
Could you give little more detail on the type of your cluster or your cluster setup/configuration.

Since its a 2-node cluster, i bet you have a quorum disk? Am i right in concluding this?

It should not be an issue for you to remove the FDDI loop, how ever i would need more details before i can confirm on this :-)

What is your intended use of the FDDI loop?

I am sorry, i am asking more questions rather than replying. I just wanted to get as many details as possible and throw this out to every one here, so that they can all have their perspective :-)

regards
Mobeen

[labadie_1]

If you want to see if the Lavc protocol (60-07) is running on all cards (Fddi, and the 2 Nic) the simplest way is
ana/sys
sh lan
and see if you have 60-07 and Lavc foor each card.

by default, the Cluster protocol runs on all interfaces.
You can stop it with the programs in sys$examples:lavc$start_bus and lavc$stop_bus.
if you have Vms 7.3 or later, you have a better way, play with priorities with
$ mc scacp
set lan_device ewa/prio=4
set lan-device ewb/prio=2

or just stop the protocol for certain cards
$ mc scacp
stop lan_device ewa

[Keith Parris]

It would be helpful to know what OpenVMS version you are running. There were a lot of changes to PEDRIVER at 7.3 and above. Given you have Gigabit Ethernet, I'll assume you're most likely at 7.3 or above.

(BTW, there is much more complex communication between OpenVMS Cluster nodes than a simple heartbeat as one might see in a simple fail-over cluster under Windows or UNIX, and this communication includes such things as distributed lock manager traffic.)

PEDRIVER is the portion of OpenVMS code which handles inter-node communications in a cluster over a LAN.

Based on packet loss history, capacity, and latency, PEDRIVER selects a set of optimal channels to a remote node, which is called the Equivalent Channel Set, and transmits round-robin across all of the channels in the ECS. (At the same time, it can receive on all channels, whether they're in the ECS for transmitting or not.) This is documented in Appendix G of the OpenVMS Cluster Systems Manual at http://h71000.www7.hp.com/doc/731FINAL/4477/4477pro_034.html#congestion_appendix

To easily see which path(s) PEDRIVER is using to transmit from each node to each of the other nodes at a given point in time, run the SHOW_PATHS_ECS.COM procedure from the [KP_CLUSTERTOOLS] directory on the V6 Freeware CD that shipped with 7.3-2 and is also available on the Web at http://h71000.www7.hp.com/openvms/freeware/

[Uwe Zessin]

Keith,
the additions to PEDRIVER (it now reports excessive packet loss) have been very useful during my last mission. We had attempted to migrate from 10MBit to 100MBit at a customer's site. After the message I used good old DECnet's DTSEND and 'MCR NCP SHOW KNOWN LINES COUNTERS' to diagnose everything - turned out to be a flow-control mismatch.

Please forward my thanks to whoever has made the improvement!

[Keith Parris]

Uwe,
I've forwarded your thanks to Verell Boaen, who leads the team handling PEDRIVER.