======================================================================
Halcyon PrimeAlert for Veritas Cluster Server
Version 2.1.0
Release Notes
======================================================================
Copyright (c) 1998-2008 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.0a 2.1.0 2.0.0b 2.0.0a 2.0.0 1.0.0c
1.0.0b 1.0.0a 1.0.0
======================================================================
VERSION/DATE: 2.1.0a/2008-12-01
Enhancements
----------------------------------------------------------------------
Modified the following alarm thresholds to add consistency with
Veritas recommendations:
- Cluster State
- System State
- Group State
- Resource State
- Resource probed
Bug Fixes
----------------------------------------------------------------------
N/A
UPGRADE STRATEGY
----------------------------------------------------------------------
If you have changed any alarm threshold settings and/or alarm actions
for the Network Details table, your changes will not be preserved
after upgrading to version 2.1.0a.
To perform an upgrade from version 2.0.0 to version 2.1.0a,
we recommend the following steps:
1) Make a note of any customizations (alarm threshold changes,
alarm actions, etc) for the Network Details table (under the
Heartbeats folder).
2) Upgrade PrimeAlert for VCS from version 2.0.0 to version 2.1.0a.
3) Re-apply the customizations (alarm threshold changes, alarm
actions, etc) noted in step 1 to the Network Details table.
Note: since the 'VCS Notifier' (previously known as 'Notifier Status')
node has been redesigned to raise custom alarm message(s),
you can no longer set any alarm threshold(s) for this node.
Consequently, all previous customizations for this node are not
retained after upgrading.
Note: after upgrading to version 2.1.0a, the module loader window
may not report a correct module version number. Reloading
PrimeAlert for VCS will set the module version number correctly.
Known Problems
----------------------------------------------------------------------
- Sun Management Center (Sun MC) 3.6 and up is experiencing problems
serving help files from the server layer. Please refer to
Troubleshooting for a workaround to this problem.
Notes
----------------------------------------------------------------------
- It is recommended that the VCS SNMP notifier be configured
to send SNMP traps to PrimeAlert for VCS module. However,
PrimeAlert for VCS can monitor VCS without having VCS SNMP event
notification enabled.
- To configure VCS for SNMP event notification, please refer to the VCS
User's Guide. For example, Veritas Cluster Server 4.1 User's Guide
on page 206 outlines a step by step procedure on how to set up VCS
event notification using the VCS Notifier Wizard.
- It is strongly recommended that the VCS SNMP notifier be configured
to run under the Cluster Service Group. Having the notifier under
the Cluster Service Group provides failover when necessary.
Running the notifier process via the command line utility does not
provide any failover.
- After PrimeAlert for VCS has been loaded/unloaded repeatedly,
benign warning and/or error messages may appear in the agent.log
file. Restarting the agent will eliminate these extraneous messages.
======================================================================
VERSION/DATE: 2.1.0/2007-11-30
Enhancements
----------------------------------------------------------------------
- Added PRM support.
- Added support for Veritas Cluster Server 5.0.
- Only SNMP traps with the correct community string(s) will be
injected into SUN MC and/or Neuron.
- Added MIB file support.
- Added support for Sun Management Center 4.0.
- Added support for Solaris zoned environment.
- Dropped support for Solaris 2.6 and 2.7.
Bug Fixes
----------------------------------------------------------------------
- Documentation upgrades.
UPGRADE STRATEGY
----------------------------------------------------------------------
If you have changed any alarm threshold settings and/or alarm actions
for the Network Details table, your changes will not be preserved
after upgrading to version 2.1.0.
To perform an upgrade from version 2.0.0 to version 2.1.0,
we recommend the following steps:
1) Make a note of any customizations (alarm threshold changes,
alarm actions, etc) for the Network Details table (under the
Heartbeats folder).
2) Upgrade PrimeAlert for VCS from version 2.0.0 to version 2.1.0.
3) Re-apply the customizations (alarm threshold changes, alarm
actions, etc) noted in step 1 to the Network Details table.
Note: since the 'VCS Notifier' (previously known as 'Notifier Status')
node has been redesigned to raise custom alarm message(s),
you can no longer set any alarm threshold(s) for this node.
Consequently, all previous customizations for this node are not
retained after upgrading.
Note: after upgrading to version 2.1.0, the module loader window
may not report a correct module version number. Reloading
PrimeAlert for VCS will set the module version number correctly.
Known Problems
----------------------------------------------------------------------
- Sun Management Center (Sun MC) 3.6 and up is experiencing problems
serving help files from the server layer. Please refer to
Troubleshooting for a workaround to this problem.
Notes
----------------------------------------------------------------------
- It is recommended that the VCS SNMP notifier be configured
to send SNMP traps to PrimeAlert for VCS module. However,
PrimeAlert for VCS can monitor VCS without having VCS SNMP event
notification enabled.
- To configure VCS for SNMP event notification, please refer to the VCS
User's Guide. For example, Veritas Cluster Server 4.1 User's Guide
on page 206 outlines a step by step procedure on how to set up VCS
event notification using the VCS Notifier Wizard.
- It is strongly recommended that the VCS SNMP notifier be configured
to run under the Cluster Service Group. Having the notifier under
the Cluster Service Group provides failover when necessary.
Running the notifier process via the command line utility does not
provide any failover.
- The 'Notifier Status' node has been renamed to 'VCS Notifier'.
- After PrimeAlert for VCS has been loaded/unloaded repeatedly,
benign warning and/or error messages may appear in the agent.log
file. Restarting the agent will eliminate these extraneous messages.
- The 'Module Activation Order' parameter has been renamed to
'Cluster Monitoring Order'.
======================================================================
VERSION/DATE: 2.0.0b/2006-04-25
Enhancements
----------------------------------------------------------------------
- If VCS is not configured for SNMP event notification, PrimeAlert for
VCS will simply report this without raising an alarm.
- If VCS is configured for SNMP event notification but is not sending
SNMP traps to the agent host, PrimeAlert for VCS will raise an alarm.
- Same as version 2.0.0a and 2.0.0 (please see below).
Bug Fixes
----------------------------------------------------------------------
- Module generated irrational alarms when VCS returned error messages
instead of data on its SNMP event notifier.
UPGRADE STRATEGY
----------------------------------------------------------------------
- If PrimeAlert for VCS version 1.x was previously installed, please
follow the Upgrade Strategy outlined below for version 2.0.0a.
- If PrimeAlert for VCS version 2.0.0a was previously installed,
please do the following:
1) Install PrimeAlert for VCS version 2.0.0b.
2) Stop and re-start the agent.
Known Problems
----------------------------------------------------------------------
- Same as version 2.0.0a and 2.0.0 (please see below).
Notes
----------------------------------------------------------------------
- PrimeAlert for VCS version 2.0.0b can monitor VCS without having
VCS SNMP event notification enabled.
- To configure VCS for SNMP event notification, please refer to the VCS
User's Guide. For example, Veritas Cluster Server 4.1 User's Guide
on page 206 outlines a step by step procedure on how to set up VCS
event notification using the VCS Notifier Wizard.
- It is strongly recommended that the VCS SNMP notifier be configured
to run under the Cluster Service Group. Having the notifier under
the Cluster Service Group provides failover when necessary.
Running the notifier process via the command line utility does not
provide any failover.
======================================================================
VERSION/DATE: 2.0.0a/2006-04-12
Enhancements
----------------------------------------------------------------------
- Same as version 2.0.0 (please see below).
Bug Fixes
----------------------------------------------------------------------
- Install script failed to update console layer packages properly.
- Also please see Bug Fixes for version 2.0.0 below.
UPGRADE STRATEGY
----------------------------------------------------------------------
- PrimeAlert for Veritas Cluster Server (PrimeAlert for VCS) has been
redesigned. As a result, please note the following important points:
- PrimeAlert for VCS version 2.x is literally a different module
than PrimeAlert for VCS version 1.x, and thus the two versions
of PrimeAlert for VCS can run side by side on both the agent and
server layers simultaneously. Thus, both version 2.x and version
1.x can co-exist simultaneously on both the agent and server
layers.
- To differentiate between the versions, please note that the module
name for PrimeAlert for VCS version 2.x is HALVeritasCS4, and that
the module name for PrimeAlert for VCS version 1.x is HALVeritasCS.
To perform an upgrade, we recommend the following steps:
1) Install the HALVeritasCS4 module (PrimeAlert for VCS version
2.0.0a) onto the server layer along side the HALVeritasCS module
(PrimeAlert for VCS version 1.x). After step 1, both versions
of the module should be present on the server layer.
2) Make a note of any customizations (alarm threshold changes,
alarm actions, etc) that were configured to the HALVeritasCS
module (PrimeAlert for VCS version 1.x) on the agent layer.
3) Unload and uninstall the HALVeritasCS module (PrimeAlert for VCS
version 1.x) from the agent layer.
4) Install and load the HALVeritasCS4 module (PrimeAlert for VCS
version 2.0.0a) onto the same agent layer.
5) Re-apply the customizations (alarm threshold changes, alarm actions,
etc) noted in step 4 to the HALVeritasCS4 module (PrimeAlert for
VCS version 2.0.0a) on the same agent layer. After step 5,
only the HALVeritasCS4 module (PrimeAlert for VCS version 2.0.0a)
should be present on the agent layer.
6) Repeat steps 2 through 5 for all other required agent layers.
7) Uninstall the HALVeritasCS module (PrimeAlert for VCS version
1.x) from the server layer. Do not uninstall the HALVeritasCS4
module (PrimeAlert for VCS version 2.0.0a). After step 7, only
the HALVeritasCS4 module (PrimeAlert for VCS version 2.0.0a)
should be present on the server layer.
Known Problems
----------------------------------------------------------------------
- Same as version 2.0.0 (please see below).
======================================================================
VERSION/DATE: 2.0.0/2006-03-20
Enhancements
----------------------------------------------------------------------
- Added Cluster Health section which eliminates duplicate alarms
from multiple agents.
- Added Notifications section which generates alarms based
upon SNMP V2c traps received from Veritas Cluster Server.
- Added Service Monitoring capability which enables/disables modules
within the agent based on the state of Veritas service groups
on the local host.
- Added support for monitoring remote clusters.
- Added support for Solaris 10.
- Added support for PrimeAlert Neuron Agent.
- Added support for Sun Management Center 3.6.
- Added support for Veritas Cluster Server 4.1.
Bug Fixes
----------------------------------------------------------------------
- Module now looks for VCS 4.0 logfile patterns instead of VCS 3.X patterns.
- Module now supports single node Veritas cluster.
UPGRADE STRATEGY
----------------------------------------------------------------------
- PrimeAlert for Veritas Cluster Server has been redesigned. As a
result, this release is not compatible with the previous version.
The following steps must be taken:
1) Uninstall the VeritasCS module (PrimeAlert for Veritas Cluster
Server version 1.0.0) from the console, agent, and server layers.
2) Install the VeritasCS4 module (PrimeAlert for Veritas Cluster
Server version 2.0.0) onto the server, and agent layers.
3) Re-apply any customizations (alarm threshold changes, alarm actions,
etc) that were previously configured to the VeritasCS4 module.
KNOWN PROBLEMS
----------------------------------------------------------------------
- When the module is initially loaded, warning message(s) may
appear in agent.log. These warning messages can be safely
ignored. See the TroubleShooting for details.
- 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: 1.0.0c/2005-07-07
Enhancements
----------------------------------------------------------------------
- Added support for Veritas Cluster versions 3.5 and 4.0.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
NOTE: The package version numbers for the module have not changed.
Only the documentation was changed to reflect support for the
new version of Veritas Cluster. As a result, an upgrade
is not required from version 1.0.0b of this module.
======================================================================
VERSION/DATE: 1.0.0b/2003-07-25
Enhancements
----------------------------------------------------------------------
- Added Solaris 9 support.
- Added Sun MC 3.5 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.0a/2002-04-12
- Minor Patch Release.
- Now supports alpha-numeric characters for clustered hostnames.
======================================================================
VERSION/DATE: 1.0.0/2002-03-01
Enhancements
----------------------------------------------------------------------
- None. This is the FCS release.
Bug Fixes
----------------------------------------------------------------------
- None. This is the FCS release.
Known Problems
----------------------------------------------------------------------
- None.
---//---