Conference decwet::networker

733.0. "Strange (to me) NSR behaviour in strange ASE setup" by COMICS::CORNEJ (What's an Architect?) Tue Jun 03 1997 09:12

    I don't know if what follows is a bug, a feature, or what.  I would be
    interested to know what caused the symptoms observed.  The system has
    been reconfigured since so I can't get any further information!
    
    zen and orac are the two nodes in as ASE.  A bunch of disks sit behind
    a sengle HSZ40 on a shared SCSI.
    
    Customer wants a /usr/local on each machine,  but due to lack of enough
    local disk space, they must be on the HSZ.  To ensure no mis-use of the
    disks I made a disk service for each /usr/local (one disk each).  ASE
    doesn't like two services with the same mount point (obviously:-) so
    zens' /usr/local was actually mounted as /usr/zlocal with a link to
    /usr/local.  Each service was set up such that it could never fail
    over to the "wrong" machine.   OK,  this is a hack,  but so far it seems
    to work.
    
    Now NSR V4.2A is set up (yes,  I know it is old - it is all that was
    available though and the customer does not want to upgrade (ie does not
    want to pay to upgrade) ).
    
    All works fine until the cluster service zenlocal is added as an NSR
    client.  NSR complains about oraclocal not being available (I had not
    got that far).
    
    NSR seems to recognise that zenlocal is mounted on /usr/local and then
    sees that oraclocal is also mounted on /usr/local - hence it talking
    about oraclocal when I request zenlocal.
    
    Is this behaviour to be expected?
    
    Jc