Thanks to a schedule power down in one of our computer rooms over the
weekend, this problem is now fixed. It seems that ASE can't handle NICs
being added/configured after ASE is started. Once the system was rebooted I
was able to add the new interface in without a hitch.
Dave.
-----Original Message-----
I am trying to add a third network interface in a two node ASE V1.5 cluster
running V4.0E PK1, and it is failing with an obscure message. I already have
two networks defined on different subnets - one for the cluster heartbeat
and the other for the first interface to the main LAN. I have just added a
third interface on another subnet and when I try and add it to ASE as a
monitored backup network it barfs with:
ASE: xxx02 Director Bug: invalid message result: 38... exiting
ASE: xxx01 AseMgr Error: blocking send to director failed
ASE: xxx01 AseMgr Error: Member change failed
ASE: xxx01 AseMgr Error: new director hasn't started up yet...
My current ASE network setup is:
ASE Network Configuration
Member Name Interface Name Member Net Monitor
___________ ______________ __________ _______
xxx01 xxx01 Backup Yes
xxx01 tcxxx01 Primary No
xxx02 xxx02 Backup Yes
xxx02 tcxxx02 Primary No
I cannot see why it will not let me add this interface. Can anyone help?!
Thanks in advance,
Dave Campbell
(dave.campbell_at_vf.vodafone.co.uk)
Received on Mon Sep 27 1999 - 08:16:45 NZST