======================================================================
Halcyon PrimeAlert (R) PlusPack
Version 2.2.0a
Release Notes
======================================================================
Copyright (c) 1998-2008 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: 2.2.0a, 2.2.0, 2.1.0c, 2.1.0b, 2.1.0a,
2.1.0, 2.0.0b, 2.0.0a, 2.0.0, & 1.2.0
======================================================================
VERSION/DATE: 2.2.0a/2011-01-26
BUG FIXES
----------------------------------------------------------------------
- Fixed PrimeAlert SystemMonitor agent exit issue when used with
Solaris Patch Cluster 6/29/2010 and newer (and expected with
future full releases of Solaris 10).
- When the number of CPUs in a system or zone are changed, the
CPU Usage values in Solaris SystemMonitor will be accurate and
not show occasional errors. Resovles occasional errors with
the CPU Idle Time, CPU Busy Time, CPU System Time, and
CPU User Time fields.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This release obsoletes the Patch_4185 patch series. Do not apply
any version of Patch_4185 if you use this release.
If you have v2.2.0 plus Patch_4185_C on SPARC Solaris, you do
not need to upgrade to this version. This version is equivalent.
- This release is compatible with the previous 2.2.0 version.
- Refer to prior upgrade strategies in sequence for upgrades
from versions prior to 2.2.0.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Same as v2.2.0
- The ReleaseNotes and README file within the product packages
were not updated.
======================================================================
VERSION/DATE: 2.2.0/2008-10-28
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for SunMC agent on Solaris x86
- Added support for SunMC Linux agent
- Added support for Solaris zoned environment.
- Added monitoring ability for zfs filesystem in PrimeAlert SystemMonitor
for Solaris.
BUG FIXES
----------------------------------------------------------------------
- LogFileMonitor will now run alarm actions on subsequent "re-alarm every"
match (where new alarms are created for every Nth match above and
beyond the alarm threshold). Please refer to the Upgrade Strategy,
if you have LogFileAlert_Patch_3692 installed.
- Fixed the problem where in some cases PrimeAlert SystemMonitor for
Solaris module failed to collect data for certain file systems.
Please refer to the Upgrade Strategy if you have Patch_3971_SolarisSystemMonitor
installed.
- Added System Monitor / CPU - Percent Average Usage (for Solaris)
to the preconfigured list for PrimeAlert Reporter, so that it is now
visible in PrimeAlert Reporter Row Add/Delete window if you click on
"Add/Delete Rows..." inside PrimeAlert Reporter. Please refer to
Upgrade Strategy, if you have already added a row of "PrimeAlert
SystemMonitor / Average CPU Usage (%)" to PrimeAlert Reporter.
- Corrected the default units from "%sec" to "%/hour" for the following
objects inside PrimeAlert SystemMonitor for Solaris module, which
appears in PrimeAlert WebPortal web interface:
- UFS Filesystem Usage Table -> Rate (%/hour)
- Veritas Filesystem Usage Table -> Rate (%/hour)
Please refer to the Upgrade Strategy, if you have already added a row
of "PrimeAlert SystemMonitor / Rate (%/hour)" to PrimeAlert Reporter
and the units for the row inside PrimeAlert Reporter is not "%/hour".
- Fixed the problem where PrimeAlert Reporter did not collect the right
data for the object PrimeAlert SystemMonitor for Solaris -> Runnable
Processes, and/or could not graph for either of the following two
objects:
- PrimeAlert SystemMonitor -> Runnable Processes
- PrimeAlert SystemMonitor -> Idle Processes
Please refer to the Upgrade Strategy, if you have already added
one/both of the above two objects to PrimeAlert Reporter.
KNOWN PROBLEMS
----------------------------------------------------------------------
- The PrimeAlert FileBrowser module is not availible for the SunMC
Linux agent.
- Any probe commands in the PlusPack modules do not work on the
SunMC Linux agent.
- PrimeAlert PlusPack modules appear in the 'Available Modules'
section of the 'Module Manager' if the PrimeAlert PlusPack module
server and/or console layers are installed on a Sun MC server host.
In the above situation, the agent layer packages do not need to be
installed for the Sun MC agent to detect the PrimeAlert PlusPack
modules to be installed. Attempting to load these modules fails
because the required files (distributed with the agent layer
packages) were never installed.
- Cannot add rows in PrimeAlert Top10 using Group Operations.
- The PrimeAlert SystemMonitor module could not collect IPC Facilities
statistics on a Solaris 10 system.
UPGRADE STRATEGY
----------------------------------------------------------------------
- If you have LogFileAlert_Patch_3692 installed, uninstall it prior to
the upgrade:
# rm /var/opt/SUNWsymon/cfg/HALToolkit-counter-d.rul
# rm /var/opt/SUNWsymon/cfg/LogFileAlert_Patch_3692.readme.txt
If you have other patches or customization (provided by Halcyon)
installed, please contact Halcyon Support at:
Email: support@halcyoninc.com
Tel: 416-932-4666
Fax: 416-932-4711
- If you have Patch_3971_SolarisSystemMonitor installed, please take
the following steps.
Prior to upgrading, uninstall the patch as per the instructions
in the Patch_3971_SolarisSystemMonitor.tar.gz.readme.txt file.
This readme can be found within the patch, and may be found in the
/var/opt/SUNWsymon/cfg directory.
After upgrading:
- If you have added any zfs filesystem objects to PrimeAlert
Reporter, they must be re-added to Reporter as they now appear
seperately in their own table. The old objects in Reporter
will subsequently say "Object Not Found", but will continue
to contain the historical data prior to the upgrade.
- If you have any filters in PrimeAlert EventAction that are
related to a zfs filesystem monitored by PrimeAlert SystemMonitor
for Solaris, you need to adjust those filters in EventAction.
- If you have added a row of PrimeAlert SystemMonitor for Solaris /
Average CPU Usage (%) to PrimeAlert Reporter before installing this
version of PrimeAlert PlusPack, you need to execute the following
steps after the installation:
- In PrimeAlert WebPortal web interface, drill inside the agent
host where you have the row added and go inside PrimeAlert
Reporter module.
- Move your mouse over the triangle to the left of any of the
column titles and click on "Add/Delete Rows...". Notice that
there are two rows for the same object (PrimeAlert SystemMonitor
-> CPU Usage -> Average CPU Usage (%)): a new row under the CPU
category, and another under the category that you defined when
you added the row.
- In the PrimeAlert Row Add/Delete window:
- uncheck the row of PrimeAlert SystemMonitor / Average CPU
Usage (%) that you added previously (under the category that
you defined when you added the row), and
- check the row of System Monitor / CPU - Percent Average Usage
(under the CPU category), then click Apply.
- Now this row will be placed under the CPU category. Wait for 2
minutes before trying to graph the row. Historical data will be
preserved for this row.
- The previous category that you used for adding the row might
disappear from PrimeAlert Reporter after following the above
upgrade instructions, if PrimeAlert SystemMonitor / Average CPU
Usage (%) was the only row in that category. As a result, all
reports in that category will be invisible. If you want to keep
all your reports in the previous category, just edit the new row
in the CPU category and change its category to the previous one.
- If you have added a row of "PrimeAlert SystemMonitor for Solaris / Rate
(%/hour)" to PrimeAlert Reporter for the following objects inside the
PrimeAlert SystemMonitor module before installing this version of PrimeAlert
PlusPack:
- UFS Filesystem Usage Table -> Rate (%/hour)
- Veritas Filesystem Usage Table -> Rate (%/hour)
and if the units for the row inside PrimeAlert Reporter is not "%/hour",
then you need to edit the row in PrimeAlert Reporter and change the
units to "%/hour". This can be done as follows after the installation:
- In PrimeAlert WebPortal web interface, drill inside the agent
host where you have the row added and go inside PrimeAlert
Reporter module.
- Move your mouse over the triangle to the left of the row that
you have added and click on "Edit Row...".
- In the Row Editor window, change the Units value to "%/hour",
then click Apply.
Nothing needs to be done if there is no row inside PrimeAlert Reporter
that corresponds to the above Filesystem objects of PrimeAlert SystemMonitor
module, or if the units for the row inside PrimeAlert Reporter is "%/hour".
(The units appears in the Value column inside PrimeAlert Reporter module,
and it appears in the graph.)
- If you have already added rows for one/both of the following two objects
to PrimeAlert Reporter before installing this version of PrimeAlert
PlusPack:
- PrimeAlert SystemMonitor for Solaris -> Runnable Processes
- PrimeAlert SystemMonitor for Solaris -> Idle Processes
then you need to delete those rows and add the rows back from inside
PrimeAlert Reporter. This can be done as follows after the installation:
- In PrimeAlert WebPortal web interface, drill inside the agent
host where you have the rows added and go inside PrimeAlert
Reporter module.
- Delete all rows that are related to the above two objects, by
moving your mouse over the triangle to the left of the row and
clicking on "Delete Row...". These rows could be placed under
the "Processes" category, or any category that you defined.
- Then add back these two rows by moving your mouse over the
triangle to the left of any column title and clicking on
"Add/Delete Rows...".
- In the PrimeAlert Row Add/Delete window:
- check the following two rows under the Processes category:
- System Monitor / Idle Processes
- System Monitor / Runnable Processes
- Wait for 2 minutes before trying to graph the rows.
Note there may or may not be historical data available for
the "Runnable Processes" object.
- If you have any report that contains any of the above mentioned
two objects, you need to delete those objects from the report
and add them back to the report again.
======================================================================
VERSION/DATE: 2.1.0c/2008-04-15
ENHANCEMENTS
----------------------------------------------------------------------
- None.
BUG FIXES
----------------------------------------------------------------------
- Fixed a bug preventing the module from being installed/deployed via
AgentUpdate.
KNOWN PROBLEMS
----------------------------------------------------------------------
- The ReleaseNotes have not been updated within the installed
html help documentation. Only in the product distribution
tarball root and the post install archive location (typically
/var/opt/SUNWsymon/install/)
======================================================================
VERSION/DATE: 2.1.0b/2008-02-28
ENHANCEMENTS
----------------------------------------------------------------------
- Enabled the ability to install against Sun MC 4.0 (sparc and x86/x64
for Sun MC Server Layer, sparc only for Sun MC Agent).
BUG FIXES
----------------------------------------------------------------------
- Fixed Solaris SystemAlert bug "Filesystem Usage table irrational/empty"
(identical to Patch_3971_SolarisSystemMonitor)
KNOWN PROBLEMS
----------------------------------------------------------------------
- PrimeAlert PlusPack modules appear in the 'Available Modules'
section of the 'Module Manager' if the PrimeAlert PlusPack module
server and/or console layers are installed on a Sun MC server host.
In the above situation, the agent layer packages do not need to be
installed for the Sun MC agent to detect the PrimeAlert PlusPack
modules to be installed. Attempting to load these modules fails
because the required files (distributed with the agent layer
packages were never installed).
======================================================================
VERSION/DATE: 2.1.0a/2005-01-26
BUG FIXES
----------------------------------------------------------------------
- Fixed Solaris SystemAlert bug - swap usage may be incorrect
- Fixed Solaris SystemAlert bug - network statistics may be incorrect
UPGRADE STRATEGY
----------------------------------------------------------------------
- This release is compatible with the previous 2.1.0 version.
- Refer to prior upgrade strategies in sequence for upgrades
from versions prior to 2.1.0.
- If you were ever given manual over-ride patches for Solaris
SystemAlert, remove any/all of the following files from your
environment before applying this release:
/var/opt/SUNWsymon/cfg/HALSolarisSystemAlert-d.flt
/var/opt/SUNWsymon/cfg/HALSolarisSystemAlert-d.x
/var/opt/SUNWsymon/bin/HALSolarisSystemAlert-interface-d.sh
KNOWN PROBLEMS
----------------------------------------------------------------------
- This ReleaseNotes have not been updated within the installed
html help documentation. Only in the product distribution
tarball root and the post install archive location (typically
/var/opt/SUNWsymon/install/)
======================================================================
VERSION/DATE: 2.1.0/2004-08-17
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Sun MC 3.5 Update 1
- Added support for several versions of Linux 2.4 kernel (see README)
- Added support for 64-bit platforms on Linux 2.4 kernel
- Increased the number of characters of process arguments available
for matching on Solaris. See the 'Working With The Process Table'
page of the ProcessMonitor HTML Help for details.
- Added support for Sun Management Center's Agent Update feature.
- [LogFileMonitor] Allow customization of status message length,
and increased the default length from 512 characters to 1024.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This release is not backward compatible on Linux and HPUX. Please
contact Halcyon before upgradging on these platforms.
- This release is backward compatible on Solaris and no upgrade
strategy needs to be followed.
======================================================================
VERSION/DATE: 2.0.0b/2003-06-09
ENHANCEMENTS
----------------------------------------------------------------------
- Sun MC 3.5 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous versions 2.0.x
======================================================================
VERSION/DATE: 2.0.0a/2003-04-02
BUG FIXES
----------------------------------------------------------------------
- CPU Usage section did not update on some systems.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version 2.0.0
======================================================================
VERSION/DATE: 2.0.0/2003-01-23
ENHANCEMENTS
----------------------------------------------------------------------
- Solaris 9 support.
- Performance Reporting Manager and Group Operations support.
- Reduced disk footprint.
- Added PrimeAlert SystemMonitor for Solaris module.
- Documentation upgrades.
- Enhanced PrimeAlert FileSizeMonitor so that users can be alerted
on file modifications.
- Added support for Solaris zoned environment.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Cannot add rows in PrimeAlert Top10 using Group Operations.
NOTES:
----------------------------------------------------------------------
- Removal of Solaris 2.5.1 support
- Removal of Sun Management Center 2.x support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This version of PlusPack contains a ProcessMonitor Module that is not
backwards compatible with previous versions. After installation of
PlusPack the configuration files for any ProcessMonitor instances that
are already loaded will have to be upgraded by using the included
HALPlusPack-upgrade.sh script.
======================================================================
VERSION/DATE: 1.2.0/2001-09-24
ENHANCEMENTS:
----------------------------------------------------------------------
- [LogFileMonitor] Allow customization of status messages by specification
or formatting.
- [LogFileMonitor] Added ability to filter out duplicate alarms within a
user-defined time interval
- [ProcessMonitor] Allow filtering by PID and PPID
- [ProcessMonitor] / [LogFileMonitor] New common submodule
and data handling routines , allowing better intergration with
other Halcyon Modules such as PrimeAlert for Oracle and
PrimeAlert for Sybase
UPGRADE STRATEGY:
----------------------------------------------------------------------
This version of PlusPack contains a ProcessMonitor Module that is not
backwards compatible with previous versions. After installation of
PlusPack the configuration files for any ProcessMonitor instances that
are already loaded will have to be upgraded by using the included
HALPlusPack-upgrade.sh script.
If you do not currently have any ProcessMonitor modules loaded you
can safely skip running the upgrade script. Running it will not
modify your configuration if no modules are detected.
---//---