#   File:    ReleaseNotes
#   Author:  Halcyon Monitoring Solutions, Inc.
#   Desc.:   Software Release Notes for Halcyon
#            PrimeAlert (R) for Sun Cluster 2.2
#
#   Copyright (c) 1993-2001 Halcyon Monitoring Solutions, Inc.
#

NOTE: 
    For the latest information on this product, go to the
    web site at http://www.HalcyonInc.com

    Refer to the README file(s) for all other information.

Versions Documented Below: 1.0.0

-----------------------------------------------------------------------
VERSION/DATE: 1.0.0/2001-05-16 (beta1)

BUG FIXES:

- None.

ENHANCEMENTS:

- None.

KNOWN PROBLEMS:

- If PrimeAlert for Sun Cluster 2.2 is loaded on a host that is not a
  Sun Cluster 2.2 node, the module will immediately become irrational.
  See the TroubleShooting file for more details.

- The Processes table in the 'Local Cluster Processes' folder may show
  the '% CPU' of a process to be 0 for a short time after the process
  is started or re-started.

- For the included module(s), certain tables with more than 50 rows of
  data may no longer display properly when using a SunMC 2.1.1 console.
  This problem does not occur when using a SunMC 2.1 or 3.x console. If
  you are still using the SunMC 2.1.1 console, and you are experiencing
  the table display problem, then please contact Halcyon for a patch
  (info@HalcyonInc.com).

- Assume that a user installs Sun Management Center in the /opt
  directory, and then decides to relocate some of the installed
  directories (located below /var/opt/SUNWsymon or below
  /opt/SUNWsymon) after SunMC is installed. For example, assume that
  the directory /opt/SUNWsymon/modules is moved to /export1/SUNWsymon,
  and then a symbolic link is created to link /opt/SUNWsymon/modules to
  /export1/SUNWsymon/modules. In this case, if the current distribution
  attempts to install any files in or below the directory
  /opt/SUNWsymon/modules, the symbolic link will be replaced by a real
  directory. This problem does not occur under Solaris 2.5.1.

UPGRADE STRATEGY:

- In order to obtain the full benefit of the new features included in
  this version of PrimeAlert for Sun Cluster 2.2, module packages for
  PrimeAlert for Sun Cluster 2.2 should be upgraded for all SunMC
  layers (server, agent and console).

- PrimeAlert for Sun Cluster 2.2 packages on the SunMC server host
  should be upgraded first. Then, agent hosts can be upgraded according
  to any user defined schedule. Note that after the server host is
  upgraded, the Sun Cluster 2.2 module should continue to operate
  properly for all agent hosts, regardless of the version of the module
  that is installed on an agent host. Finally, after all server and
  agent hosts have been upgraded, the console hosts should be upgraded
  to ensure that the module help documentation is up-to-date.

- CAVEAT: After the server host has been upgraded, agent hosts that
  contain older versions of PrimeAlert for Sun Cluster 2.2 may not 
  have all of the functionality of the newest module until the agent
  hosts have also been upgraded to the same level as the server host.

---//---