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

Conference smurf::ase

Title:ase
Moderator:SMURF::GROSSO
Created:Thu Jul 29 1993
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2114
Total number of notes:7347

1907.0. "direcotor exit during net partition" by NETRIX::"[email protected]" (decatl::johnson) Fri Feb 28 1997 17:17

3.2g 

system A 
	has the disk service
system B
	has the director

a network partition occured, and is noted by both daemon.log's.

QUESTION:   the Directory on system B did not exit, should it have
            exited?

ASE admin setion B2 and B1 identifies sequences in which the
director exits,  and I have seen other calls where the direcotry
exited, but in this case the customer was able to continue to
use ASEMGR on the system without the service.  the logs indicated
a network partition condition.  no-reboot was attempted.


sid johnson
customer support center/atlanta
[Posted by WWW Notes gateway]
T.RTitleUserPersonal
Name		DateLines
1907.1Normal behaviour...BACHUS::DEVOSManu Devos DEC/SI Brussels 856-7539Sun Mar 02 1997 07:2414
    Sid,
    
    your question has been answered in both this notefiles and in the ASE
    admin guide a lot of time. If you have a NET partition, the asedirector
    is killed to prevent any relocation. To be more precise, you cannot
    start/stop any services, you cannot even use asemgr.
    
    This is documented in the ASE admin guide and is also the expected
    behaviour of ASE. Indeed, if the networrk is sut between the two
    members, does it implied that the client of the services are not able
    to access the server? 
    
    Regards, Manu.
1907.2I apologize ...BACHUS::DEVOSManu Devos DEC/SI Brussels 856-7539Sun Mar 02 1997 11:2115
    Hi again,
    
    Thanks to Dave Ascher who sent me a mail, I should correct my answer:
    
    It appears that, with the lastest version(s) (?), the asedirector is
    NOT exiting in case of NETWORK partition, and you can still use asemgr,
    but the relocations of services are still prevented.
    
    The advantage seams that ASE recovers automatically when the NET is UP
    again.
    
    Regards, and sorry to have read your too fast.
    
    Manu.
1907.2Yes, but what if it doesntNETRIX::"[email protected]"decatl::johnsonThu Mar 06 1997 08:2324

But, the customer says that both nodes did indicate a network partition, 
and that the directory did not exit (running the node without the 
service). and that he was able to run asemgr (not expected) but 
not able to do anything in asemgr.

He was looking for a explaination and I didnt have a explaination 
for this.  (but condition did not exist at the time he was
reporting the incident).
 
.0

>  but in this case the customer was able to continue to use ASEMGR 
>  on the system without the service.  the logs indicated
>  a network partition condition.  no-reboot was attempted.

re 'no-reboot was attempted', that is,  ASE did not attempt to 
reboot.



   
[Posted by WWW Notes gateway]
1907.3different look & feel, same behaviour...BRSDVP::DEVOSManu Devos DEC/SI Brussels 856-7539Sun Mar 09 1997 12:1611
    Hi,
    
    I am not from the engineering team, but maybe the last version of ASE
    has changed, and now the asedirector is no longer killed when ther is a
    net partition. If the asedirector is not killed, then asemgr can be
    called. But, the expected behaviour still exist: you  can not move,
    start or stop any service as far as the net partition exists.
    
    Any comments, Greg ?
    
    Manu.
1907.4SMURF::MYRDALMon Mar 10 1997 10:0910
    
    As far as I am aware nothing should have changed with the reaction
    of the director to a network partition.  I need to do some research 
    on this before I make a confident comment.  Unfortunately I will
    be out for a week so I will not be able to respond quickly.  Maybe
    another engineer will respond before I get back.
    
    regards,
    
    -- Greg