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

Conference csc32::consolemanager

Title:POLYCENTER Console Manager
Notice:Kits, Scans, Docs on CSC32:: as PCM$KITS:,PCM$DOCS:, PCM$SCANS:
Moderator:CSC32::BUTTERWORTH
Created:Thu Aug 06 1992
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:1541
Total number of notes:6564

1179.0. "failover and secondary CM" by 22603::DICKLIAO () Wed Jan 31 1996 21:57

    
    hi colleagues:
    
    can anyone help me ?
    i have some questions by the following for consolemanager .
    
    1. can the failover function be supported on which version of
       consolemanager of digital unix ?
    2  whether i can setup secondary platform for consolemanager or not if
       the failover function is not supported.
    3. continue 2. i means the secondary platform will boot after the
       primary consolemanager down and the same as  the consolemanager function
       of the primary
    4. why not if the item 3 is not functionality .
    
             thanks for you regards
    
                           dickliao
    
    
T.RTitleUserPersonal
Name
DateLines
1179.156525::RCOLLIERThu Feb 01 1996 10:2824
    PCM currently does not provide a server failover functionality.
    There are customers out there who have implemented some form of
    "failover" by putting other applications in place, such as
    shadowing.  We are currently in the process of defining and
    designing a failover functionality for the next release of PCM.
    If you have any suggestions/requirements, please send me mail.
    You can also post it here for general discussion.
    
    Customers who have implemented partial failover do the following:
    	- shadow or copy over the PCM datasets (config db, etc) to a
    	  secondary site also running a PCM server
    	- use the secondary server to monitor the primary PCM server.
    	- action routine set up so if failure is detected on the primary
    	  server, the secondary server looks at the configuration database
    	  (from the shadowing/copying) and re-establishes connections
    	  to those nodes.
    
    What's not covered in this scenario that we are still trying to
    address are:
    	- licensing: the secondary server now has to have the same
    	  set of licenses as the primary
    	- return of controls to the primary server when it comes back
          up.