#   File:    ReleaseNotes
#   Author:  Halcyon Inc.
#   Desc.:   Software Release Notes for Halcyon
#            PrimeAlert (R) for Cisco Router 
#
#   Copyright (c) 1993-2003 Halcyon 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.


-----------------------------------------------------------------------
VERSION/DATE: 1.1.1b/2005-11-28

ENHANCEMENTS:

- Tested against Sun MC 3.6.

- Added Solaris 10 Support.


UPGRADE STRATEGY:

- None.  This release is compatible with the previous version.

  If you have any patches or manual procedures that you used with
  the 1.1.1a module, you should also install/undertake
  them with the 1.1.1b module.


NOTES:

- Note that the cisco router module has a built in limit of 30
  interfaces that it can monitor in "detailed" state.  The rest
  of the interfaces may be monitored via the "Status Only" state,
  which means it will be monitored in the "Interface Status" table.
 

-----------------------------------------------------------------------
VERSION/DATE: 1.1.1a/2003-07-14

ENHANCEMENTS:

- Added Sun MC 3.5 support.

- Added Solaris 9 Support.


UPGRADE STRATEGY:

- None.  This release is compatible with the previous version.


-----------------------------------------------------------------------
VERSION/DATE: 1.1.1/2001-01-22

BUG FIXES:

- Fixed a problem that was causing a memory leak in the Sun Management
  Center agent process.

- All interfaces are now properly monitored after the module is edited.

ENHANCEMENTS:

- PrimeAlert for Cisco Router is now interoperable with Sun Management
  Center 3.0.

- As documented in the README file for this distribution, all text
  documentation files for this distribution are now archived to a
  standard location on any installation host.

- This distribution includes a new UNIX uninstallation script; see
  the README.install file for details.

- The handling of dormant interfaces has been changed. See the HTML
  help documentation for more information.

KNOWN PROBLEMS:

- 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.

- Versions of Red Hat Linux prior to 6.1 may contain a problematic
  version of tar that cannot handle long pathnames. Although this will
  not affect the installation of the Linux packages, extraneous files may
  be created in the directory where the tarball is extracted; thus, the
  tarball should be extracted in a dedicated staging directory, such as
  /tmp/install. Note that if your version of Linux tar cannot handle
  long pathnames, then the extracted tarball should only be used for
  doing installations on the local Linux host.

- The router check script, HALRouterAlertCisco-check.sh, does not work
  through a firewall unless the firewall is configured to allow
  outbound packets to the router on UDP port 161, and inbound UDP
  packets from the router on all ports above 1024. Otherwise, the check
  script will report that it "cannot access the router".

- Some module configuration files are not removed after the module is
  unloaded.

- Currently it is not possible to graph data from an Interface Summary
  Statistics table.

- Loading multiple instances of PrimeAlert for Cisco Router on a single 
  SunMC/PrimeAlert agent may consume large amounts of resources if the
  total number of router interfaces monitored in the 'detailed' mode is
  greater than 30. In unusual cases, this could cause the agent to
  become unresponsive. Refer to the TroubleShooting file for details.

UPGRADE STRATEGY:

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

- Module 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 Cisco
  Router 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 Cisco Router 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.