I received a lot of help and some very appreciated guidance on this. I
really apprecaited all that responded.
Summary,
General info on Gated:
TruCluster v5 uses RIP for its cluster routing.
If you kill gated, you also (sort of) kill the cluster.
You can stop and start the gated by using these commandes:
/sbin/init.d/gateway stop
/sbin/init.d/gateway start
To fix my particular problem this was the answer.
alter the gated.conf file
locate and change
rip yes {
broadcast;
};
to
rip yes {
nobroadcast;
};
A very helpful email from Compaq was also forwarded to me that is displayed
in its entirety below:(This also could be a better solution)
As discussed on the phone the file /etc/gated.conf.memberx contains the
gated configuration for each cluster member.
The following section is from our test cluster /etc/gated.conf.member1
file.
rip yes {
broadcast;
interface alt0 ripin ripout;
interface mc0 ripin ripout metricout 10;
interface tu0 ripin ripout;
interface tu1 ripin ripout;
interface all noripin noripout;
};
Changing the tu0 line to:
interface tu0 noripin ripout;
Should prevent learning rip routes over the tu0 interface.
Unfortunately each time aliasd is restarted the /etc/gated.conf.memberx
files are rewritten.
So you will need to stop gated
/sbin/init.d/gateway stop
Modify the /etc/gated.conf.memberx files then restart gated.
You can add your own script in /sbin/init.d and point a soft link in
/sbin/rc3.d/S99xxxx to automate it on boot. But in a cluster fail over
these /etc/gated.conf.memberx could be rewritten.
The other possibility is using the filter feature via ifaccess.conf to
block all packets from that routers. But with ifaccess.conf there is no
way to stop just the router updates and not incoming traffic forwarded
through that router.
man ifaccess.conf for more info, but I highly recommend you test
filtering on a workstation and not a cluster.
Alan Anderson
UNIX Network Support CSC CS
Compaq Computer Corp.
Received on Wed Mar 27 2002 - 18:45:16 NZST