back to back cluster

[Edgar Ulloa]

Thanks for all your comments
I will the conection early

my doubth was because when I put
sda>sho port only I can see one port

866B7E30 pe PEA0 SYS$PEDRIVER
and I want have 2 ports betwen the nodes.

I think that will be necesary configure independiently each card or some thing.

Thanks again

[David Jones_21]

>>my doubth was because when I put
sda>sho port only I can see one port

866B7E30 pe PEA0 SYS$PEDRIVER
and I want have 2 ports betwen the nodes.

I think that will be necesary configure independiently each card or some thing<<

Clustering began using a special piece of 'CI' (Computer Interconnect) hardware. When clustering via a LAN, the PEDRIVER (Port Emulator) provides a pseudo-device that looks like a CI but communicates over other network interfaces. The code inside PEDRIVER handles selecting the path to use so you only need PEA0.

The DCL command "MCR LANCP show config/users" will show you which protocols are being used the available ethernet adapters. Cluster traffic is carried on NISCA.

[Edgar Ulloa]

Ian Miller

You asked me..?

Are the nodes connected to a network switch/hub/other and you plan to replace this with a simple cable?

the idea is have both, switch and simple cable..? its probably do it..?

David Jones

Thanks for your comements Can I select wich card I choice for my cluster trafic..?

Thanks

[David Jones_21]

>>Thanks for your comements Can I select which card I choice for my cluster trafic..?<<

The sys$examples directory has 2 programs, lavc$start_bus and lavc$stop_bus, that control which controllers run NISCS. See appendices D and E of the "Cluster Systems" manual.

I stop LAVC on my fastest server's gigabit card (keeping it on the 2 100 Mbit ethernets on the motherboard) because otherwise it tends to overwhelm the slower Alphas that have only 100 Mbit interfaces.

[Ian Miller. · Accepted solution]

on VMS V7.3 and later use SCACP to control which interface is used.
http://h71000.www7.hp.com/doc/82FINAL/6048/6048pro_contents_003.html#toc_chapter_18

[comarow]

You don't say if you have more than one cluster on your network. Make sure the cluster has a unique group number and group password.

This is during cluster config, but can also be performed using the sysman utility.
The defualt is group number of one and it can get you into a lot of trouble.

You can take a cluster_authorization.dat
from one node, sys$common:[sysexe] and copy it to the other nodes.

Bob

[Edgar Ulloa]

Thanks for all your comments

I will apply it