Distributed Systems Administration Utilities V1.1 Release Notes for HP-UX 11i v2 March 2006

1 System Administration Release Notes
These Release Notes describe known issues when using the Distributed Systems Administration Utilities for
the HP-UX 11.23 March 2006 release.
Consolidated Logging
New Features
▲ When running System Management Homepage's (HPSMH) System Log Viewer on a log consolidator,
the viewer can view the consolidated logs in addition to the system's local syslog files. The administrator
accesses the viewer using a browser and navigating to http://hostname:2301. In a Serviceguard
cluster, the log consolidation service is highly available and runs as a package. In order to view the
consolidated logs, the administrator had first to determine where the package was currently running
(for example, using cmviewcl -p clog) and then navigate to the URL for that particular cluster member:
http://<hosting_member>:2301/
System Management Homepage has added a new feature to support virtual IP addresses such as those
used by Serviceguard packages. This allows the administrator to navigate to
http://<virtual_IP_address>:2301. This lets the administrator access the log consolidator immediately
using the package's DNS name or IP address.
This feature is enabled by:
1. Setting the monitor-ip-changes tag to 1 in the /opt/hpsmh/conf.common/smhpd.xml file;
monitor-ip-changes is enabled by default.
2. HPSMH's autostart feature must be enabled. See the smhstartconfig(1M) man page for
details. By default, autostart is enabled.
With the two attributes enabled, when HPSMH processes a new connection request, it scans the available
IP addresses for the system and makes sure to accept requests for any new addresses that are present
on the system. For example, if a package fails over from member A to member B, new connections to
http://<package_IP_address>:2301 will correctly start HPSMH on memberB.
Problems that Have Been Fixed
▲ When consolidating package log files in a Serviceguard cluster, it was possible that the first message
written to a new package log file was not captured in the consolidated log. This has been fixed.
Known Problems and Workarounds
• When using the System Log Viewer, which is part of the System Management Home page, the user
can use the Filter tab to specify the number of lines to read from the end of the file. This can improve
performance when the log file is very large. If the user enters a number larger than the number of lines
in the log file, an incorrect number of lines will be displayed. The same is also true when using the
"clog -t lines” command.
• When using the Consolidated Logging Wizard in a Serviceguard cluster and choosing to have the
cluster be a log consolidation server, the wizard creates a Serviceguard package named "clog.” If you
then run the wizard and choose to re-configure the cluster to be a log forwarding client, the package
is not removed. To work around this, before re-configuring the cluster, manually delete the package
using the following commands:
# cmhaltpkg clog
# cmdeleteconf -p clog
Consolidated Logging 5