HP Serviceguard Version A.11.18 Release Notes, September 2008

• Openview integration is done via HP SIM.
• No file save – Serviceguard Manager A.05.01 had the ability to save a snapshot of
the current clusters monitored, and display it later. This feature is mainly used for
comparing configuration changes, which you can now do with DSAU.
Limitations
• Using Serviceguard Manager, you can create only legacy packages.
But you can monitor and administer both legacy and modular packages. See
“About Modular Packages” (page 26) for more information about modular and
legacy packages.
• You cannot use Serviceguard Manager to configure cross-subnet clusters or
packages (see “About Cross-Subnet Configurations” (page 40)).
— The Serviceguard Manager Configuration pull-down menu is disabled in
a cross-subnet configuration.
Although you can view the cluster, node, and package property pages, you
cannot create or modify a cluster, package, or package control script.
— You cannot configure DSAU log consolidation.
If you currently have DSAU configured to consolidate the logs locally, you will
need to set up a remote log consolidation server. See Chapter 3 of the Distributed
Systems Administration User's Guide for more information.
If you use messages that are sent to syslog.log to trigger warning and alert
alarms, you will need to configure the alarm server to point to the log server.
Help Subsystem
Use this section to help you become familiar with Serviceguard Manager. Once
Serviceguard Manager is running, use the tooltips by moving your mouse over a field
from the read-only property pages for a brief definition for each field. You can also
access the online help by clicking the button located in the upper-right hand corner
of the screen to view overview and procedure information. Start with the help topic
Understanding the HP Serviceguard Manager Main Page. You should read the help
topic About Security, as it explains HP Serviceguard Manager Access Control Policies,
as well as root privileges.
What’s in this Release 55