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

Conference lassie::ucx

Title:DEC TCP/IP Services for OpenVMS
Notice:Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System
Moderator:ucxaxp.ucx.lkg.dec.com::TIBBERT
Created:Thu Nov 17 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:5568
Total number of notes:21492

5333.0. "Forcing a Node to Be Impersonator" by VMSNET::P_NUNEZ () Wed Mar 12 1997 16:47

    
    I see how you setup the cluster impersonator and I can see how, by
    setting the cluster timer to 0, you force a node to always be
    the impersonator.  But does the node with the value of 0 have to
    become the impersonator thru normal means before it becomes the
    "permanent" impersonator?  I assume yes, in case the another node was
    acting as the impersonator (ie, the node with the timer set to 0 was
    down) and had active sessions.  
    
    What if the node that is currently the impersonator has no sessions to
    the impersonator address and now suddenly UCX is started on the node
    with the cluster timer set to 0 - does it immediately failover or must
    the cluster timer on the current impersonator expire first?
    
    Phew....
    
    Paul
T.RTitleUserPersonal
Name		DateLines
5333.1timer =0 ==> 1st booted gets it54958::ROELANDTSWa d'es ma da ve ne stuutThu Mar 13 1997 03:1214
    
    
    
    Paul,
    
    When using a timer of 0, the system that boots first will be the
    impersonator, there won't be a shift over mechanism even if there are 
    no connections to the cluster alias. That last mechanism is taking
    place only if the timer is different from 0.
    
    Rgds,
    
           Guy
5333.2yeah, but...VMSNET::P_NUNEZThu Mar 13 1997 09:4211
    Guy,
    
    But what if I want one specific node in the cluster to be the
    impersonator regardless of which boots first?  I'd have the timer set
    to 0 on that node and set to >0 on other members.  When can I expect
    the node with timer=0 to become the impersonator - immediately
    (assuming no connections to impersonator address on other node) or
    after timer expires on the other node?   It may be trivial, but a
    customer wants to know anyway...
    
    Paul
5333.3more infoBACHUS::ROELANDTSWa d'es ma da ve ne stuutThu Mar 13 1997 11:1614
    
    
    Paul,
    
    I think that if a node, with a timer = 0, boots that it will become the
    impersonator, if there are no connections to the cluster alias on
    another system. That system will remain the cluster impersonator as
    long as it will stay up ... for more info read notes 3263 - 2029 - 1638
    in this conference ... I think you'll find more info in those notes
    
    Rgds,
         
            Guy
5333.4Nevermind...VMSNET::P_NUNEZThu Mar 13 1997 14:1210
    
    Those help, but the one difference is we were looking at
    setting the timer to 0 on one node and >=1 on the other. 
    
    However, the customer has decided to use other methods 
    to meet his goal, so it's no longer an issue...
    
    Thanks,
    
    Paul