[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference chefs::mdf

Title:Business Recovery Server
Notice:
Moderator:CHEFS::MCCAUGHAN_S
Created:Tue Nov 19 1991
Last Modified:Fri May 09 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:254
Total number of notes:980

249.0. "Quorum adjustment not reliable on BRS V1.4(-1)." by GIDDAY::MARSHALL (PaulG.Marshall, Systems Consultant, SPR_CSC) Wed Feb 05 1997 04:37

We are having intermittent quorum adjustment problems on BRS site locally
running the BRS kit V1.4-1.

Intermittently both OMS stations seem to go through the process of 
quorum adjustment but we get no opcom messages on either system in the
BRS cluster stating that the quorum adjustment has been proposed.

The OMS stations have a node name of HV60 and HV61, the cluster nodes
(only two) have node names of AV15 and AV16.

HV60/61 AMDS$CONSOLE_ACCESS.DAT files entries are:

HV60  *\1DECAMDS\R
      *\60ACCESS\W

HV61  *\1DECAMDS\R
      *\61ACCESS\W

AV15/16 AMDS$DRIVER_ACCESS.DAT file entries are:

AV15  *\1DECAMDS\R
      HV60LAN_ADD\60ACCESS\W
      HV61LAN_ADD\61ACCESS\W

AV16  *\1DECAMDS\R
      HV60LAN_ADD\60ACCESS\W
      HV61LAN_ADD\61ACCESS\W
    
Running a seperate AMDS console on a standalone workstation seems to work
fine (adding its entries in AMDS$DRIVER_ACCESS.DAT).

Anyone running BRS V1.4-1 experianced the same issue here?

Regards
Paul

T.RTitleUserPersonal
Name
DateLines
249.1Does this help?CHEFS::PADDICKMichael Paddick - BRS Bristol, UKThu Mar 06 1997 13:2737
    Paul,
    
    Quorum adjust from the BRS stations works by:-
    
    At BRS configuration time, the MAC address of the interface on each
    Cluster node that's running AMDS is hard coded into the BRS database.
    It uses whichever interface happens to be running AMDS at that time, so
    if customer changes AMDS$DEVICE logical at some time, or if any
    specific filtering is applied to network device which prevents 
    the AMDS protocol reaching the Cluster nodes (I have seen this) 
    and doesn't re-run BRS$CONFIG, then it will stop working.
    
    You can find out which address the QA frame will be sent to by running
    BRS$CONFIG.EXE and taking the 'database maintenance' option and writing
    a configuration report to a text file. Check the MAC addresses assigned
    to each system in that file, then use $ ANAL/SYS and SHOW LAN/FULL to
    check that the AMDS protocol (08-00-2b-80-48?) is runnign on the
    interface that BRS thinks it it's on.
    
    BRS will have, at config time, added an entry for each OMS in the
    DRIVER_ACCESS file specifying teh actual MAC address and a password,
    which is also input and configured at BRS config time. This password is
    also coded into the rport mentioned above.
    
    The point is that the BRS system seems to use only a very small part of
    AMDS, and when you use the Availability system fully, it is capable of
    listening to AMDS multi-cast frames from teh Cluster systems and
    identifying which MAC address is *CURRENTLY* in use and not (like BRS)
    the one that *WAS* in use when the BRS config took place.
    
    I have had several probelsm like this.
    
    Hope this help,
    
    Michael Paddick - BRS European delivery team, Bristol UK.
    
    
249.2BRS reconfig dangerous?SNOFS1::CHURCHILLJTue Mar 11 1997 04:118
        On the subject of BRS re-configuration, I've got one customer who
    persistently modifies the Console Manager and Watchdog databases via
    their respective GUI interfaces. I seem to recall though each time you
    use BRS$CONFIG, these databases no longer apply. New ones are created
    based on what BRS$CONFIG knows. I always thought using BRS$CONFIG as
    just a quick way to get things initially working. Later, the user
    modifies things using the appropriate POLYCENTER application. Please
    correct me if I'm wrong on this, or is there a way around all this?
249.3ALEPPO::BOWKERJoe Bowker, KB1GPTue Mar 11 1997 16:2511
    BRS$CONFIG will regenerate portions of the PCM config database.
    Specifically it changes anything related to any of the BRS systems, it
    does not change any scan profile stuff. If you have a non-BRS system in
    the database it will leave it alone.
    
    Watchdog works similarly.
    
    There is no way around it.
    
    
    Joe