======================================================================
Halcyon PrimeAlert (R) High Availability
Version 1.2.0
Release Notes
======================================================================
Copyright (c) 1998-2005 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: 1.2.0a 1.2.0 1.1.0a 1.1.0 1.0.0a 1.0.0
======================================================================
VERSION/DATE: 1.2.0a/2008-04-30
ENHANCEMENTS
----------------------------------------------------------------------
- Added support for Sun MC 4.0.
BUG FIXES
----------------------------------------------------------------------
- None.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This release is compatible with the previous version.
- Any patches/workarounds provided by Halcyon prior to this release
should be removed. Specifically check ESDIR/bin and ESDIR/cfg
for files named HALHAClient-* (where ESDIR is often /var/opt/SUNWsymon/)
KNOWN PROBLEMS
----------------------------------------------------------------------
- If the HAClient module is edited while it is in the middle of
a failover, the client may not fail over properly. It may not fail
over properly in the future either. The symptom to look for is
the agent.log will be filled with entries stating that "a failover
is pending" however no failover will occur. The workaround is to
manually stop and re-start the agent.
======================================================================
VERSION/DATE: 1.2.0/2007-2-9
ENHANCEMENTS
----------------------------------------------------------------------
- The failover process now works with Solaris 10, with Service
Management Facility (SMF) enabled.
- Added Solaris whole root zone and sparse root zone support.
- Added x86/x64 Solaris support.
BUG FIXES
----------------------------------------------------------------------
- Minor fixes in the documentations.
- If the seed for a server is changed in the HAClient module the
agent will be re-seeded upon next failover to that server.
Prior to this, PrimeAlert High Availability used backups of
authentication records, thus necessitating that an agent
be manually re-seeded should a server layer's seed ever change.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This release is compatible with the previous version.
- Any patches/workarounds provided by Halcyon prior to this release
should be removed. Specifically check ESDIR/bin and ESDIR/cfg
for files named HALHAClient-* (where ESDIR is often /var/opt/SUNWsymon/)
KNOWN PROBLEMS
----------------------------------------------------------------------
- If the HAClient module is edited while it is in the middle of
a failover, the client may not fail over properly. It may not fail
over properly in the future either. The symptom to look for is
the agent.log will be filled with entries stating that "a failover
is pending" however no failover will occur. The workaround is to
manually stop and re-start the agent.
======================================================================
VERSION/DATE: 1.1.0a/2005-3-28
Bug FIXES
----------------------------------------------------------------------
- Workaround a failure for some agents to properly exit during failover
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Same as 1.1.0
======================================================================
VERSION/DATE: 1.1.0/2004-10-17
ENHANCEMENTS
----------------------------------------------------------------------
- Invalid high availability configurations will be reported by the
modules. Examples:
a) the primary and backup server have the same ip address
b) the ip addresses of the servers cannot be resolved
- Added support for Sun Management Center's Agent Update feature.
BUG FIXES
----------------------------------------------------------------------
- Determine agent's server context based on ip address rather than
hostname.
- Module will install properly if Sun Managment Center is not
installed in the default directory.
- Fixed miscellaneous docmentation mistakes.
- On some systems, the agent is known to fork a temporary process when
it exits. The failover script will stop any forked processes so
that the failover process is not hindered.
- Regular expression matching has been improved so that failover will
not be affected by the hostname or size of the process id.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Symptom:
The console reports the error message "Unable to obtain console info"
when opening the Host Details window for the agent.
Possible Causes:
- The server layer has not updated the agent with the security keys
used for communication. Wait and retry after five minutes.
- On a system with multiple agents (standard agent plus platform
agents), failover can result in an agent pointing to a server layer
with the incorrect security keys. This may occur if the agent is
restarted by the the user before the failover process has completed
but another agent has completed its failover steps.
- In rare occassions, if the user starts the agent just before the
failover process has completed, the agent will use the incorrect
keys.
Workaround:
1) Stop the agent
2) Remove the failover configuration
# rm -rf /var/opt/SUNWsymon/cfg/failovers
3) Reseed the agent
# /opt/SUNWsymon/sbin/es-run base-usm-seed.sh -s <secret_seed> -c <component>
where <secret_seed> is the seed used to initially configure
the agent and <component> is the name of agent being reseeded.
For example, the following command will reseed the default agent:
# /opt/SUNWsymon/sbin/es-run base-usm-seed.sh -s maplesyru -c agent
The following example will reseed the platform agent with the
instance name "platform1":
# /opt/SUNWsymon/sbin/es-run base-usm-seed.sh -s maplesyru -c platform1
4) Start the agent
======================================================================
VERSION/DATE: 1.0.0a/2003-07-29
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun MC 3.5 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.0/2003-05-12
ENHANCEMENTS
----------------------------------------------------------------------
- None. This is a FCS release.
BUG FIXES
----------------------------------------------------------------------
- None. This is a FCS release.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This is a FCS release.
KNOWN PROBLEMS
----------------------------------------------------------------------
- If a failover gets initiated while /tmp is full, the agent is not
able to restart.
Workaround:
Monitor the /tmp directory and ensure it never reaches capacity.
---//---