Managers,
We have 2 AS 4100s setup in a ASE. We are running DU V4.0D with
Patch Kit 6 & TruCluster 1.5.
The primary network path is through FDDI adapters. Back in February
we connected the Ethernet cards with a cable with a twist to be used
as the path for checking member status. The ASE network
configuration in the asecdb is as follows (with the names changed to
protect the innocent):
Member name: member1
Member IP address: 10.8.212.2
Daemon communicaiton use: Primary
Member aliveness ping use: Backup
Monitor interface setting: monitor
Member name: member1e
Member IP address: 16.8.17.1
Daemon communicaiton use: Backup
Member aliveness ping use: Primary
Monitor interface setting: ingore
Member name: member2
Member IP address: 10.8.211.2
Daemon communicaiton use: Primary
Member aliveness ping use: Backup
Monitor interface setting: monitor
Member name: member2e
Member IP address: 16.8.17.2
Daemon communicaiton use: Backup
Member aliveness ping use: Primary
Monitor interface setting: ignore
We recently experienced a problem with failover due to what appeared
to be a network failure. While investigating the problem I came
across entries in the mailing list archives that referenced the
documentation that stated that the following entries should be in the
/etc/routes file:
-host member1 member1
-host member1e member1e
-host member2 member2
-host member2e member2e
I missed this when setting this up.
My question is:
Can I use the "route" command to add these on the fly as well as
placing thme in the /etc/routes file or is a reboot required?
[=================================
[ Randy Rodgers
[ rrodgers_at_ci.ft-wayne.in.us
[ Senior Systems Programmer
[ Allen County/City of Fort Wayne
[ Information Systems
[ (219)427-5727
[=================================
Received on Thu Aug 03 2000 - 16:03:29 NZST