Conference bulean::decnetvax

5886.0. "MAIL + FAL fail REMACP OK Phase 4" by SIOG::DOOLEY () Tue May 27 1997 05:56

    
    OpenVms 6.1, 4 Node Homo 7000-XXX, Cluster Alias,
    Decnet Phase 4, Fal and Vmsmail.
    
    Hi all,
    		I wonder if you might be able to help me. I have a customer
    that is experiencing the following problem.
    
    	Fal and Mail hang and timeout after 30-40 seconds whan mailing or
    copying to another cluster. I cannot see a FAL being created on the 
    destination node and likewise with Mail$server. I have set security
    ACL's on fal object and mail. I have set Acl's also on the proxy
    database. None of these files seem to be accessed as I am not receiving
    any messages.
    
    BTW Set host Remacp is working fine. The failing node is an endnode.
    Another node in this clustser is a routing node.  
    
    	"-SYSTEM-F-UNREACHABLE, remote node is not currently reachable".
    
    
    Could someone tell me the sequence of events that takes place when
    a DIR Remotenode:: takes place. Could I use some undocumented logicals
    to get deeper info, for example FAL$LOG. How do you use it/them.
    
    
    		Much obliged for all the help,
    							John Dooley
    
    
    The following objects are defines as follows:
    
    Object = FAL
    
    Number                   = 17
    File id                  = FAL
    User id                  = FAL$SERVER
    Password                 = ywyhxbhbsuwow
    Proxy access             = incoming and outgoing
    Alias outgoing           = Enabled
    Alias incoming           = Enabled
    
    
    
    Executor node = 12.10 (NODENAME) (modified by writer)
    
    Identification           = DECnet for OpenVMS VAX V6.1
    Management version       = V4.0.0
    Incoming timer           = 45
    Outgoing timer           = 60
    Incoming Proxy           = Enabled
    Outgoing Proxy           = Enabled
    NSP version              = V4.1.0
    Maximum links            = 500
    Delay factor             = 80
    Delay weight             = 5
    Inactivity timer         = 60
    Retransmit factor        = 10
    Routing version          = V2.0.0
    Type                     = nonrouting IV
    Routing timer            = 600
    Broadcast routing timer  = 180
    Maximum address          = 1023
    Maximum circuits         = 16
    Maximum cost             = 1022
    Maximum hops             = 30
    Maximum visits           = 63
    Maximum area             = 63
    Max broadcast nonrouters = 64
    Max broadcast routers    = 32
    Maximum path splits      = 1
    Area maximum cost        = 1022
    Area maximum hops        = 30
    Maximum buffers          = 100
    Buffer size              = 576
    Access                   = incoming and outgoing
    Default access           = incoming and outgoing
    Pipeline quota           = 4032
    Alias incoming           = Enabled
    Alias maximum links      = 200
    Alias node               = 12.82 (NODEALIAS)
    Path split policy        = Normal
    Maximum Declared Objects = 96
    
    
    Circuit = MFA-0
    
    State                    = on
    Service                  = disabled
    Designated router        = 16.1018
    Cost                     = 10
    Maximum routers allowed  = 33
    Router priority          = 64
    Hello timer              = 15
    Type                     = FDDI
    Adjacent node            = 16.1018
    Listen timer             = 45
                                                
    

    
     Thanks to John Weir in UK.
    
    Hi all,
    		the problem is the Cluster Alias seems to have gotten
    itself screwed up. When we disable ALIAS OUTGOING on the Fal and
    mail objects on the local node (failing node) then the problem goes
    away. 
    
    					Thanks,
    						John