======================================================================
Halcyon PrimeAlert (R) for Sun Messaging Server
Version 2.1.0
Release Notes
======================================================================
Copyright (c) 1998-2006 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: 2.1.0b 2.1.0a 2.1.0 2.0.0 1.0.1b 1.0.1a
1.0.1 1.0.0
======================================================================
VERSION/DATE: 2.1.0b/2008-04-11
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Sun MC 4.0.
BUG FIXES
----------------------------------------------------------------------
- The Error Logs folder will not turn irrational when an alarm is
detected in one of the logs.
- Illegal characters from table row instances will be removed. As a
result, this product can be used with PrimeAlert Reporter.
UPGRADE STRATEGY
----------------------------------------------------------------------
- If custom alarm limits or alarm actions have been set for any of
the tables under the folders 'Connections' or 'Messages Statistics',
then those changes will have to be re-applied. Also, if any data
from these tables is being graphed using PrimeAlert Reporter, then
the rows will have to removed from PrimeAlert Reporter and then
added back in.
KNOWN PROBLEMS
----------------------------------------------------------------------
- SunMC fails to interpret question marks ('?') which results in
abnormal behaviour when included in load parameters and customized
alarm messages.
- Sun Manager Center 3.6 is experiencing problems serving help files
from the server layer. Please refer to Troubleshooting for a
workaround to this problem.
- Some folders are empty or cannot be opened when selecting data
properties for use with Sun Management Center Performance Reporting
Manager or Group Operations
See the FAQ for details on how to work around this issue.
- Deployment of Module Configuration Parcels using Group Operations
fails without any errors
Workaround:
Load module manually on each agent.
- Only one installation of Sun ONE Messaging Server per host can be
fully monitored with PrimeAlert for Sun ONE Messaging Server. This
is a limitation of the Sun ONE Messaging Server SNMP sub-agent,
which does not correctly multiplex when more than one installation is
present on a host. Only the modules instance that was loaded last
would report the correct values.
Workaround:
None.
- When the location of any of the error logfiles is changed
for a Messaging Server instance, the PrimeAlert for Sun ONE
Messaging Server module will not automatically begin monitoring
the new error logfile.
To work around this issue, whenever the error logfile location
is changed, edit the PrimeAlert for Sun ONE Messaging Server module,
and the new error log location will be detected.
- Changes to some of the initial load parameters do not take affect.
The workaround for this problem is to unload the module and load
it again with the desired parameters.
======================================================================
VERSION/DATE: 2.1.0a/2006-12-10
ENHANCEMENTS
----------------------------------------------------------------------
- None.
BUG FIXES
----------------------------------------------------------------------
- The Error Logs folder will not turn irrational when an alarm is
detected in one of the logs.
- Illegal characters from table row instances will be removed. As a
result, this product can be used with PrimeAlert Reporter.
UPGRADE STRATEGY
----------------------------------------------------------------------
- If custom alarm limits or alarm actions have been set for any of
the tables under the folders 'Connections' or 'Messages Statistics',
then those changes will have to be re-applied. Also, if any data
from these tables is being graphed using PrimeAlert Reporter, then
the rows will have to removed from PrimeAlert Reporter and then
added back in.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Sun MC fails to interpret question marks ('?') which results in
abnormal behaviour when included in load parameters and customized
alarm messages.
- Sun Manager Center 3.6 is experiencing problems serving help files
from the server layer. Please refer to Troubleshooting for a
workaround to this problem.
- Some folders are empty or cannot be opened when selecting data
properties for use with Sun Management Center Performance Reporting
Manager or Group Operations
See the FAQ for details on how to work around this issue.
- Deployment of Module Configuration Parcels using Group Operations
fails without any errors
Workaround:
Load module manually on each agent.
- Only one installation of Sun ONE Messaging Server per host can be
fully monitored with PrimeAlert for Sun ONE Messaging Server. This
is a limitation of the Sun ONE Messaging Server SNMP sub-agent,
which does not correctly multiplex when more than one installation is
present on a host. Only the modules instance that was loaded last
would report the correct values.
Workaround:
None.
- When the location of any of the error logfiles is changed
for a Messaging Server instance, the PrimeAlert for Sun ONE
Messaging Server module will not automatically begin monitoring
the new error logfile.
To work around this issue, whenever the error logfile location
is changed, edit the PrimeAlert for Sun ONE Messaging Server module,
and the new error log location will be detected.
- Changes to some of the initial load parameters do not take affect.
The workaround for this problem is to unload the module and load
it again with the desired parameters.
======================================================================
VERSION/DATE: 2.1.0/2006-07-07
ENHANCEMENTS
----------------------------------------------------------------------
- Added x86 support.
- Added Neuron support.
- Help files are now served from the Halcyon website.
- Added Sun Messaging Server 6.2 support.
- Added Sun Manager Center 3.6 support.
- Added Solaris 10 support.
- Help documentation update.
- Added whole root zone and sparse root zone support.
BUG FIXES
----------------------------------------------------------------------
- None.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Sun MC fails to interpret question marks ('?') which results in
abnormal behaviour when included in load parameters and customized
alarm messages.
- Sun Manager Center 3.6 is experiencing problems serving help files
from the server layer. Please refer to Troubleshooting for a
workaround to this problem.
======================================================================
VERSION/DATE: 2.0.0/2004-08-16
ENHANCEMENTS
----------------------------------------------------------------------
- Support for Sun Messaging Server 6.1.
- Added monitoring of watcher, LMTP processes.
- Support for Sun Management Center 3.5.1.
- Support for Agent Update installation.
- Added process count alarm limits.
- Improved Response Times alarm messages.
- Clarified Module Load parameters.
BUG FIXES
----------------------------------------------------------------------
- Corrected data acquisition errors that occured for some tables when
the table index contained a fully qualified domain name.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version 1.0.1b.
======================================================================
VERSION/DATE: 1.0.1b/2003-07-04
ENHANCEMENTS
----------------------------------------------------------------------
- Add Sun MC 3.5 Support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version 1.0.1a.
======================================================================
VERSION/DATE: 1.0.1a/2003-04-02
BUG FIXES
----------------------------------------------------------------------
- Module installs on Solaris 9
- Documentation upgrades.
- Improved CPU Utilization.
- Default alarms limits are set in the log file monitoring section.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version 1.0.1.
======================================================================
VERSION/DATE: 1.0.1/2002-09-10
ENHANCEMENTS
----------------------------------------------------------------------
- Solaris 2.9 support.
- Support for Sun Management Center Performance Reporting Manager.
- Support for Sun Management Center Group Operations.
- Support for Sun ONE Messaging Server 5.x.
- Module objects are available in the PrimeAlert Reporter Add/Delete
Rows picklist.
BUG FIXES
----------------------------------------------------------------------
- Module is available in the Module Specification picklist in the
Filters tab of PrimeAlert EventAction.
- Documentation upgrades.
- Alarms messages in some of the tables were not formatted properly.
NOTES
----------------------------------------------------------------------
- Remove Solaris 2.5.1 support.
- Remove Sun Management Center 2.x support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version 1.0.0.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Some folders are empty or cannot be opened when selecting data
properties for use with Sun Management Center Performance Reporting
Manager or Group Operations
See the FAQ for details on how to work around this issue.
- Deployment of Module Configuration Parcels using Group Operations
fails without any errors
Workaround:
Load module manually on each agent.
- Only one installation of Sun ONE Messaging Server per host can be
fully monitored with PrimeAlert for Sun ONE Messaging Server. This
is a limitation of the Sun ONE Messaging Server SNMP sub-agent,
which does not correctly multiplex when more than one installation is
present on a host. Only the modules instance that was loaded last
would report the correct values.
Workaround:
None.
- When the location of any of the error logfiles is changed
for a Messaging Server instance, the PrimeAlert for Sun ONE
Messaging Server module will not automatically begin monitoring
the new error logfile.
To work around this issue, whenever the error logfile location
is changed, edit the PrimeAlert for Sun ONE Messaging Server module,
and the new error log location will be detected.
- Changes to some of the initial load parameters do not take affect.
The workaround for this problem is to unload the module and load
it again with the desired parameters.
======================================================================
VERSION/DATE: 1.0.0/2002-05-30
ENHANCEMENTS
----------------------------------------------------------------------
- None. This is the FCS release.
BUG FIXES
----------------------------------------------------------------------
- None. This is the FCS release.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Only one installation of iPlanet Messaging Server per host can be
fully monitored with PrimeAlert for iPlanet Messaging Server. This
is a limitation of the iPlanet Messaging Server SNMP sub-agent,
which does not correctly multiplex when more than one installation is
present on a host. Only the modules instance that was loaded last
would report the correct values.
Workaround:
None.
- When the location of any of the error logfiles is changed
for a Messaging Server instance, the PrimeAlert for iPlanet
Messaging Server module will not automatically begin monitoring
the new error logfile.
To work around this issue, whenever the error logfile location
is changed, edit the PrimeAlert for iPlanet Messaging Server module,
and the new error log location will be detected.
- Changes to some of the initial load parameters do not take affect.
The workaround for this problem is to unload the module and load
it again with the desired parameters.
---//---