topic Re: Cluster interconnect and priorisation in Operating System - OpenVMS

Cluster interconnect and priorisation

Kirsten Knüttel — Thu, 13 Dec 2007 11:50:46 GMT

Hello,

I've got a cluster with 3 nodes (Alpha, OpenVMS 7.3-2) and I want to know, how I can see on what connection is the cluster interconnect (I want to have it on a special device). And if the cluster IC is on the wrong device, how can I change this or priorise this.

Regards,

Kirsten

Re: Cluster interconnect and priorisation

Fekko Stubbe — Thu, 13 Dec 2007 12:08:03 GMT

Hi Kirsten

You can use the SCACP program
$MCR SCACP
SHOW vc
SHOW circ
SHOW channel

You can also set priorities on the various interconnects via the
SET CHANNEL/PRIO

Fekko

Re: Cluster interconnect and priorisation

R. Verkerk — Thu, 13 Dec 2007 12:10:15 GMT

Kirsten,

you could do following:

HPS1:SYSTEM> mc scacp sho lan

SMHPS1 PEA0 Device Summary 13-DEC-2007 13:06:26.67:

Device Errors + Mgt Buffer MgtMax Line Total Current
Device Type Events Status Priority Size BufSiz Speed Pkts(S+R) LAN Address
------ ---- ------ ------ -------- ---- ------ ----- --------- -----------
LCL 0 Run Online Local Restart 0 1426 0 N/A 399498 00-00-00-00-00-00
EWC 0 Run Online Restart 0 1426 0 1000 2320236 00-1A-4B-AC-B1-40
EWD 0 Run Online Restart 0 1426 0 1000 2237576 00-1A-4B-AC-B1-41
EWA 0 Not in use by SCA 0 0 0 1000 0 00-00-00-00-00-00
EWB 0 Not in use by SCA 0 0 0 1000 0 00-00-00-00-00-00

It will show you interconnects used for Cluster.

In scacp you can set things for devices. in your systartup_vms.com add for instance:

$ IF F$GETDVI("EIC0","EXISTS") THEN MC SCACP SET LAN/PRIO=100 EIC
$ IF F$GETDVI("EID0","EXISTS") THEN MC SCACP SET LAN/PRIO=100 EID
$ IF F$GETDVI("EWA0","EXISTS") THEN MC SCACP STOP LAN EWA
$ IF F$GETDVI("EWB0","EXISTS") THEN MC SCACP STOP LAN EWB

This will disable two devices and give others higher priority.

gr,

Robert

Re: Cluster interconnect and priorisation

Volker Halle — Thu, 13 Dec 2007 12:11:39 GMT

Kirsten,

MC SCACP is your friend ;-)

MC SCACP SHOW CHANNEL (use SET TERM/WID=132) will show you the channels, i.e. all cluster communication pathes formed between all visible LAN interfaces of all nodes within the cluster. There can be multiple channels between any 2 nodes in the cluster, it depends on the HW and network configuration.

Between each pair of nodes in the cluster then exists the VC (Virtual Circuit), which carries the SCS traffic. This virtual circuit may be multiplexed over all available channels between that pair of nodes.

You can use various SCACP> SET {CHANNEL|CIRCUIT|PORT|LAN_DEVICE} /PRIO=n commands to manually try to distribute the load over the various communication pathes.

You could also stop SCS communication over individual LAN interfaces (MC SCACP STOP LAN EWA)

If you want to reduce SCS traffic on a specific LAN segment, you could use MC SCACP SET LAN_DEVICE EWA/PRIO=-10

Volker.

Re: Cluster interconnect and priorisation

Jan van den Ende — Thu, 13 Dec 2007 12:26:10 GMT

Kirsten,

Robert wrote:

>>>$
IF F$GETDVI("EWA0","EXISTS") THEN MC SCACP STOP LAN EWA
$ IF F$GETDVI("EWB0","EXISTS") THEN MC SCACP STOP LAN EWB

This will disable two devices and give others higher priority.
<<<

While this is true, you should VERY SERIOUSLY think whether this is what you want/need!

See Volker's answer about LOWERING priority. SHOULD anything unwelcome happen then, then the LOW priority interconnect will keep your cluster alive, but DISABLED does what it says: they will simply NOT function. And if there is NO (enabled) interconnect, there is NO cluster... It will hang, then crash.

Usually a low-performing cluster is WAY preferable, and upon return of the desired interconnect, full function is IMMEDIATELY, AUTOMATICALLY restored.

hth

Proost.

Have one on me.

jpe

Re: Cluster interconnect and priorisation

Jess Goodman — Thu, 13 Dec 2007 17:58:42 GMT

I believe that there will be some SCS packets (broadcasts/announcements) on any network interconnect that has SCA enabled, even if there is no currently active connection to another VMS node on that interconnect.

If so, IMO, it is reasonable to disable SCA on certain network interfaces, such as the interface you might use for TCP/IP external internet traffic for security reasons.

Re: Cluster interconnect and priorisation

Andy Bustamante — Thu, 13 Dec 2007 21:16:11 GMT

As Jess points out, if you're using a network interconnect (and based on your question, I'm making that assumption), VMS will use all interfaces for cluster traffic. The operating system will monitor performance and use the interconnect with the best response time by default.

>>> if the cluster IC is on the wrong device, how can I change this or priorise this.

There should be no "wrong device" as a cluster interconnect. To use multiple network interfaces as cluster interconnect, simply connect the cables and make sure speed/duplex are properly configured. If you have multiple interfaces, ideally you'd want to use redundant switching for a 3 node cluster, otherwise the loss of a switch can cause the cluster to fail.

The SCACP utility will allow you to set priorities and monitor traffic. Assuming two networks, if you configure one for users and the second for cluster traffic, if you ever have a failure of the cluster network segment, your cluster fails. If you accept the default behavior however, your cluster would continue.

Re: Cluster interconnect and priorisation

Kirsten Knüttel — Sat, 15 Dec 2007 12:02:18 GMT

Thank you to all for your good answers. I know now what to do (and better not to do).
Thank you very much.

Kirsten