======================================================================
Halcyon PrimeAlert (R) ScriptRunner
Version 1.1.0
Release Notes
======================================================================
Copyright (c) 1998-2007 Halcyon Monitoring Solutions, Inc.
Note: For the latest information on this product, visit:
http://www.HalcyonInc.com
Refer to the README file(s) for all other information.
Versions Documented Below: 1.1.0c 1.1.0b 1.1.0a 1.1.0 1.0.5b
1.0.5a 1.0.5
======================================================================
VERSION/DATE 1.1.0c/2008-03-04
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Sun MC 4.0
BUG FIXES
----------------------------------------------------------------------
Note: Bugfixes integrated on Solaris and HPUX only. To receive
these same bugfixes on Linux or Windows, contact Halcyon.
- The 'Exit Status' field was hardcoded to zero in v1.1.0b. It will
now properly reflect the exit status of the script.
- Alarm Status Messages include text from the 'Last Line'
field in the 'Matches Table'. Certain characters in status
messages cause problems with the Sun MC Server layer and the
propagation of the alarm messages containing them, or
interfere with the proper display of the Sun MC Host Details.
The following characters are now replaced in status messages:
original replacement
{ '
} '
tab 4 spaces
| :
( '
) '
? removed
KNOWN PROBLEMS
----------------------------------------------------------------------
- The exit status field will be 1 (one) when the script exit
status is actually zero. (Recently discovered, affects all versions
of this product.)
- Please also see the Known Problems from v1.1.0b below.
UPGRADE STRATEGY
----------------------------------------------------------------------
- If you have custom patches installed for this product they should
be uninstalled first - except for ScriptRunner_Patch_20071213,
"execute scripts not owned by root". Please contact Halcyon Support
for an updated version of this patch.
- If any alarm filtering or searching is taking place at the NOC level
(for example in PrimeAlert EventAction, IBM Tivoli, etc) ensure that
all relevant filters are adjusted appropriately considering the
Alarm Status Message character substitutions described in the BUG FIXES
section above.
- Please also see the Upgrade Strategy from v1.1.0b below.
======================================================================
VERSION/DATE 1.1.0b/2007-08-30
ENHANCEMENTS
----------------------------------------------------------------------
- Added PRM support.
- Added Group Operations support.
BUG FIXES
----------------------------------------------------------------------
- Fix security exploit which allowed the execution of arbitrary
commands.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Due to a bug in Sun Management Center, the "Folder:" value in the
Attribute Editor will appear as "PrimeAlert ScriptRunner [{0}]". The
module instance name normally would appear rather than "{0}".
- If PrimeAlert ScriptRunner yields a message like "File: not found"
when trying to view the contents of a ScriptRunner script from the
console, try updating to the most current version of PrimeAlert
FileBrowser.
UPGRADE STRATEGY
----------------------------------------------------------------------
- The HPUX, Linux, and Solaris releases are compatible with the
previous version of the module.
- This release of the PrimeAlert ScriptRunner for Windows is not
forward compatible with the previous release for Windows. The
following steps must be taken to upgrade PrimeAlert ScriptRunner
for Windows:
1) Note all customizations (alarm threshold changes, alarm actions,
etc) that are configured to the ScriptRunner module.
2) Uninstall the ScriptRunner module (PrimeAlert ScriptRunner
version 1.1.0 or earlier) from the agent layer.
3) Install the ScriptRunner module (PrimeAlert ScriptRunner
version 1.1.0b) onto the agent layer.
4) Re-apply all customizations (alarm threshold changes, alarm actions,
etc) that were previously configured to the ScriptRunner module.
======================================================================
VERSION/DATE 1.1.0a/2007-06-11
ENHANCEMENTS
----------------------------------------------------------------------
- Added PRM support.
BUG FIXES
----------------------------------------------------------------------
- None.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Due to a bug in Sun Management Center, the "Folder:" value in the
Attribute Editor will appear as "PrimeAlert ScriptRunner [{0}]". The
module instance name normally would appear rather than "{0}".
- If PrimeAlert ScriptRunner yields a message like "File: not found"
when trying to view the contents of a ScriptRunner script from the
console, try updating to the most current version of PrimeAlert
FileBrowser.
UPGRADE STRATEGY
----------------------------------------------------------------------
- The HPUX, Linux, and Solaris releases are compatible with the
previous version of the module.
- PrimeAlert ScriptRunner for Windows has been redesigned. As a
result, this release for Windows is not compatible with the previous
release for Windows. The following steps must be taken to upgrade
PrimeAlert ScriptRunner for Windows:
1) Note all customizations (alarm threshold changes, alarm actions,
etc) that are configured to the ScriptRunner module.
2) Uninstall the ScriptRunner module (PrimeAlert ScriptRunner
version 1.1.0 or earlier) from the agent layer.
3) Install the ScriptRunner module (PrimeAlert ScriptRunner
version 1.1.0a) onto the agent layer.
4) Re-apply all customizations (alarm threshold changes, alarm actions,
etc) that were previously configured to the ScriptRunner module.
======================================================================
VERSION/DATE 1.1.0/2007-03-14
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun MC 3.6, 3.6.1 support.
- Added Solaris 10 support.
- Added support for Solaris 10 zones.
- Added support for x86/x64 Solaris.
- Added support for x86-64 Linux
- Added support for HP-UX
BUG FIXES
----------------------------------------------------------------------
- None.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Due to a bug in Sun Management Center, the "Folder:" value in the
Attribute Editor will appear as "PrimeAlert ScriptRunner [{0}]". The
module instance name normally would appear rather than "{0}".
- If PrimeAlert ScriptRunner yields a message like "File: not found"
when trying to view the contents of a ScriptRunner script from the
console, try updating to the most current version of PrimeAlert
FileBrowser.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.5b/2003-07-22
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun MC 3.5 support.
- Added Solaris 9 support.
BUG FIXES
----------------------------------------------------------------------
- None.
KNOWN PROBLEMS
----------------------------------------------------------------------
- See version 1.0.5.
UPGRADE STRATEGY:
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.5a/2002-05-03
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Linux 2.4 kernel
BUG FIXES
----------------------------------------------------------------------
- None.
KNOWN PROBLEMS
----------------------------------------------------------------------
- See version 1.0.5.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.5/2001-01-22
ENHANCEMENTS
----------------------------------------------------------------------
- PrimeAlert ScriptRunner is now interoperable with Sun Management
Center 3.0.
- PrimeAlert ScriptRunner is now compatible with Microsoft Windows
2000.
- 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.
BUG FIXES
----------------------------------------------------------------------
- For a Windows agent host, if a specified batch script contains a last
line such as "EXIT 0", "EXIT /B 0", or "EXIT", the agent will no
longer spin, but the "Last Execution" field always remains blank.
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.
- Some special characters may appear incorrectly in the Help Window for
some Window Managers, including Windows NT 4.
- Due to a bug in Sun Management Center, the "Folder:" value in the
Attribute Editor will appear as "PrimeAlert ScriptRunner [{0}]". The
module instance name normally would appear rather than "{0}".
- If PrimeAlert ScriptRunner yields a message like "File: not found"
when trying to view the contents of a ScriptRunner script from the
console, try updating to the most current version of PrimeAlert
FileBrowser.
- When using the SunMC console, the Alarms Tab is missing from the
Details window for an instance of ScriptRunner that has been pasted
into a topology group from a host.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This version of PrimeAlert ScriptRunner no longer supports Sun
Enterprise SyMON 2.0.x; only Sun Management Center 2.1 or higher is
supported.
- With regard to the Windows version of PrimeAlert ScriptRunner, this
version of ScriptRunner only works with version 5.1.1 or higher of the
PrimeAlert Agent for Windows. The INSTALL.txt file for version 5.1.1 of
the PrimeAlert Agent for Windows explains that upgrading to version
5.1.1 from 5.0 will cause all configuration information for the local
agent to be lost, unless certain files are manually copied to the new
agent directory tree after the upgrade; refer to the INSTALL.txt file
for the PrimeAlert Agent for Windows for details.
- In order to obtain the full benefit of the new features included in
this version of PrimeAlert ScriptRunner, PrimeAlert ScriptRunner
packages should be upgraded for all SunMC/PrimeAlert layers (server,
agent, and console).
- PrimeAlert ScriptRunner 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,
PrimeAlert ScriptRunner should continue to operate properly for all
agent hosts, regardless of the version of ScriptRunner 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 ScriptRunner 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.
---//---