======================================================================
Halcyon PrimeAlert (R) for Sun Directory Server
Version 2.0.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: 2.0.0a 2.0.0 1.0.0d 1.0.0c 1.0.0b 1.0.0a
1.0.0
======================================================================
VERSION/DATE: 2.0.0a/2007-05-01
ENHANCEMENTS
----------------------------------------------------------------------
- Added a new column "Hostname" in Monitored Instance Control Table,
whose value is set by default to the environment variable
HOST/HOSTNAME.
- Help documentation was updated.
- Improved logging of error messages.
BUG FIXES
----------------------------------------------------------------------
- Agent Update fails on SunMC 3.6.1.
- Incorrect module file permissions.
- For some installations of PrimeAlert Neuron agent, module does not
start correctly.
- Access log filename is now set dynamically through an LDAP query.
Previously, access log filename was set statically to a default value.
- When a directory server instance is no longer being monitored,
the associated sub-modules are unloaded. Previously, the
associated sub-modules remain loaded.
- Module no longer reads or writes temporary files to /tmp.
Predictable /tmp files are a security risk.
- ProcessAlert submodule now monitors only the correct Directory Server
instance. Previously, ProcessAlert submodule was monitoring all
processes which matched Arguments Pattern as a substring.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Sun Manager Center 3.6 and up is experiencing problems serving help
files from the server layer. Please refer to Troubleshooting for a
workaround to this problem.
- Only one installation of Sun Directory Server per host can be
fully monitored with PrimeAlert for Sun Directory Server. This
is a limitation of the Sun Directory Server SNMP sub-agent,
which does not correctly multiplex when more than one installation is
present on a host.
When more than one instance is configured for monitoring in the
PrimeAlert module for Sun Directory Server, all but one of
the Monitored Instances will be missing a few fields of data
(they will appear as -1 or 0), and informational alarms will
be raised in the Monitored Instances Control table for those
instances, the alarm will be "SUBAGENT MASKED".
- When the location(s) of the Directory Server error logfile and/or
access logfile are changed for a Directory Server instance,
the PrimeAlert for Sun Directory Server module will not
automatically begin monitoring the new logfile(s).
To work around this issue, whenever the error logfile and/or
access logfile location(s) are changed, edit the PrimeAlert for
Sun Directory Server module's load parameter, e.g. "Description"
field, to force a reloading of the module. Then, the new logfile
location(s) will be detected.
- When certain derived rates have a small statistical basis,
nuisance alarms may be opened. For example, if you get one
hit and it was a cache miss, the cache hit ratio will appear
as zero, this violating any "lesser than" alarm threshold.
======================================================================
VERSION/DATE: 2.0.0/2006-02-20
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun Manager Center 3.6 support.
- Added x86 Solaris support.
- Added Solaris 10 support.
- Added PrimeAlert Neuron support.
- Help documentation update.
- Help files now served from the Sun Management Center server
layer.
- Module renamed to "PrimeAlert for Sun Directory Server".
BUG FIXES
----------------------------------------------------------------------
- Log File Monitor down state on module load.
- Empty Current Connections table.
- Incorrect default error pattern for Log File Monitor.
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
KNOWN PROBLEMS
----------------------------------------------------------------------
- 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.0d/2004-06-28
ENHANCEMENTS
----------------------------------------------------------------------
- None.
BUG FIXES
----------------------------------------------------------------------
- Module will function properly with any user that has sufficient
privileges to read performance data from Directory Server.
Previously it only supported "Directory Manager".
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.0c/2004-05-17
ENHANCEMENTS
----------------------------------------------------------------------
- None.
BUG FIXES
----------------------------------------------------------------------
- Update the error row in the Error Log File section of the module to
use the proper scan pattern.
- Specify default alarm limit for the error row in the Error Log File
section.
UPGRADE STRATEGY
----------------------------------------------------------------------
- This release is not compatible with the previous version. The
following steps should be taken to properly upgrade the module:
1) After installation of this release, stop the agent
# /opt/SUNWsymon/sbin/es-stop -a
2) Remove the configuration files related to the log file scanning
section
# rm /var/opt/SUNWsymon/cfg/HALiDS5+iDSM_*logs.dat
3) Restart the agent
======================================================================
VERSION/DATE: 1.0.0b/2004-05-03
ENHANCEMENTS
----------------------------------------------------------------------
- Added Sun Java System Directory Server 5.2 support.
BUG FIXES
----------------------------------------------------------------------
- None
UPGRADE STRATEGY
----------------------------------------------------------------------
- None. This release is compatible with the previous version.
======================================================================
VERSION/DATE: 1.0.0a/2003-07-07
ENHANCEMENTS
----------------------------------------------------------------------
- Sun MC 3.5 support.
UPGRADE STRATEGY
----------------------------------------------------------------------
- The agent component of this version of the module is not backwards
compatible. After installation, the following steps must be taken:
1) Note the instance name of each PrimeAlert for Sun Directory
Server module that is loaded in the agent.
2) Unload the module(s) from step 1.
3) Stop the agent
# /opt/SUNWsymon/sbin/es-stop -a
4) For Sun MC 3.5, remove the agent oids files
# rm /var/opt/SUNWsymon/cfg/agent-*oid*
For Sun MC 3.0, remove the user oids file
# rm /var/opt/SUNWsymon/cfg/user-oids-d.dat
5) Restart the agent
# /opt/SUNWsymon/sbin/es-start -a
6) Reload each PrimeAlert for Sun Directory Server module that
was noted in step 1 using the same instance name.
======================================================================
VERSION/DATE: 1.0.0/2002-10-12
ENHANCEMENTS
----------------------------------------------------------------------
- None. This is the FCS release.
BUG FIXES
----------------------------------------------------------------------
- None. This is the FCS release.
KNOWN PROBLEMS
----------------------------------------------------------------------
- Only one installation of Sun Directory Server per host can be
fully monitored with PrimeAlert for Sun Directory Server. This
is a limitation of the Sun Directory Server SNMP sub-agent,
which does not correctly multiplex when more than one installation is
present on a host.
When more than one instance is configured for monitoring in the
PrimeAlert module for Sun Directory Server, all but one of
the Monitored Instances will be missing a few fields of data
(they will appear as -1 or 0), and informational alarms will
be raised in the Monitored Instances Control table for those
instances, the alarm will be "SUBAGENT MASKED".
- When the location of the Directory Server error logfile is changed
for a Directory Server instance, the PrimeAlert for Sun
Directory Server module will not automatically begin monitoring
the new logfile.
To work around this issue, whenever the error logfile location
is changed, edit the PrimeAlert for Sun Directory Server module,
and the new error log location will be detected.
- When certain derived rates have a small statistical basis,
nuisance alarms may be opened. For example, if you get one
hit and it was a cache miss, the cache hit ratio will appear
as zero, this violating any "lesser than" alarm threshold.
- When circumstances arise such that the module is in the down
state (through misconfiguration or unavailability of the Sun
Directory Server), the Error Log section of the module may continue
to have a down alarm in the hierarchical view even after the
general down state has been cleared.
The actual logfile monitoring may or may not continue normally.
To work around this issue, try editing the module. If that fails,
stop and restart the agent. If that fails, reload the module.
---//---