PROBLEM:        (QAR 44838)     (Patch ID: ASE130-004)
*******
This problem occurs when an asedirector exits or when it's node goes down,
which results in a broken connection between the submon daemon and the
asedirector.  In this case the submon goes into a set of several thousand
retry attempts, all of which fail.

This problem is typically recognized by the presence of very large numbers
of messages in daemon.log reporting "ASE_INQ_SERVICE failed".

In rarer circumstances this problem may be accompanied by a core dump from
the submon daemon found in the root directory.

Following is a typical daemon.log entry made when the described problem is
in evidence:

daemon.log:Feb 15 10:15:18 rzuds02 DECsafe: rzuds02 AseMgr Warning:
         blocking send of ASE_INQ_SERVICES failed or channel hung up

Note that variation of this error message may be seen, but in all cases
they repeat hundreds or thousands of times.  Often this problem can be
reproduced by killing the asedirector in a healthy system.

PROBLEM:        (QAR 43816)     (Patch ID: ASE130-011)
*******
Changes in the ASE environment are reported using an event report mechanism
implemented via a set of interconnected daemons (tractd), one per ASE member.
When two or more ASE members are simultaneously booted, their daemons may fail
to properly interconnect, resulting in missing or incomplete reports about
the ASE environment observed via the Cluster Monitor program (cmon).

In situations where interconnect delays occur, the submon enters messages
in the syslog user.log file stating that it's attempt to subscribe to
a TRACT event has failed, soon followed by another message saying that
a fatal error has been encountered and that the submon is exiting.
The submon exits cleanly without core.

PROBLEM:        (ISO100233)     (Patch ID: ASE130-012)
*******
Pulling all monitored network interface cables on the machine running
the asedirector and a service can result in another machine starting a new
director and starting the same service before it has been fully stopped on
the first machine.  This is especially noticeable when a service takes a
long time to stop.

PROBLEM:        (ISO100233)     (Patch ID: ASE130-013)
*******
Pulling a network cable on all ASE members results in the asedirector exiting.
Replacing the cable in any ASE member would not start a director.

The director restart logic in the agent was not starting a director in
some cases that it should have been.  All cases are now explicitly handled
in this code.  This fixed a number of director restart problems related to
network cable pulls.

PROBLEM:        (QAR 49356)     (Patch ID: ASE130-019)
*******
This patch corrects a problem whereby the ASE agent daemon (aseagent),
ASE director daemon (asedirector), the trigger-action server daemon (tractd),
or the submon process fails and exits without a core file if a SIGPIPE
or other stray signal occurs.

PROBLEM:        (QAR 55680)     (Patch ID: ASE130-021)
********
This patch is part of the set of Digital UNIX patches required to support
the HSZ70 UltraSCSI Raid Array controller on the KZPSA adapter under ASE 1.3.

PROBLEM:    (HPAQ615S1,BRO101095,BRO101096,QAR 55182)   (Patch ID: ASE130-022)
********
This patch fixes a problem that may occur in an ASE (either DECsafe ASE
Version 1.3, TruCluster Available Server, or TruCluster Production Server)
when the ASE encounters connection attempts from hosts whose IP addresses
cannot be resolved to hostnames.  Instead of printing a warning about a
possible security breach, the ASE daemons will core dump with a segmentation
violation.  One cause of this problem may be unknown hosts on the network
using public domain internet security software which scans all TCP ports
on remote hosts.

PROBLEM:        (MCGM21LWR)     (Patch ID: ASE130-023)
********
This patch fixes a problem in the message service routines used by the
daemons in TruCluster Available Server and Production Server software.

When the message queue fills, the following message is entered
in the daemon.log file, but the queue is not emptied:

        msgSvc: message queue overflow, LOST MESSAGE!

From this point on, no further messages will be received.

PROBLEM:  (BRO101102 & STLQ45901)    (Patch ID: ASE130-026)
********
This patch fixes a problem where the Host Status Monitor (asehsm) incorrectly 
reports a network down (HSM_NI_STATUS DOWN) if the counters for the network 
interface get zeroed.

PROBLEM:  (DEKB31190)    (Patch ID: ASE130-027)
********
This patch fixes a problem that caused the asedirector to core dump if asemgr 
processes were modifying services from more than one node in the cluster at 
the same time.

PROBLEM:  (QAR 69272)    (Patch ID: ASE130-031)
********
This patch corrects a problem in which the asemgr can core dump when adding
a member back into an ASE.