 |
» |
|
|
|
|  | |
Serviceguard Manager version A.04.00 supports Serviceguard
A.11.16. In Serviceguard Manager A.04.00, you
can create or modify configuration of clusters and packages on nodes
with Serviceguard version A.11.16. Many of your configuration options are discovered by Serviceguard and
displayed in lists for you to select. The configuration file and control
script can be automatically created, then distributed to the nodes
by clicking a button. Serviceguard Manager uses the new Serviceguard non-root
access roles to administer Serviceguard Version A.11.16 clusters
and packages. The Properties have several new tabs, and now display
information about physical volumes, volume groups, EMS resources,
and access control policies (roles). The new Operations Log window shows messages for
administration and configuration actions. Messages from all operations
are integrated into the one screen. If you connect to a session server with Serviceguard
A.11.16, it can discover these Serviceguard Extension for RAC clusters: SGeRAC 11.14 clusters with Oracle
8i or Oracle 9i SGeRAC 11.15 clusters with Oracle 8i, Oracle 9i,
or Oracle 10g SGeRAC 11.16 with Oracle 9i or Oracle 10g
What
You See | |
The figure below shows an instance of Serviceguard Manager
with two sessions. (Up to 10 sessions are supported.) The icon by
the connection to Session Server fresno shows that the user’s
role has an Admin role for those clusters. In the second session,
the icon shows the user role is Monitor. The Alerts button tells you there is information about serious
alerts. We can see a red-bordered cluster is down. Also critical
are the clusters that have a package icon with a red X, showing
they have a package that is down. With Serviceguard Manager, you see Serviceguard objects three
ways. In the tree on the left pane, you
see cluster relationships listed hierarchically. You can navigate through the map by clicking an object in
the tree. The map pane will show information relevant to the object
you clicked. For example, if you click a node, you see that node,
its cluster, and the packages configured to run on it. In the map on the right pane, you can see configuration
relationships by the position of objects in the diagram. You can
see status from the colors and symbols. You can also get a small
text message about the status if you pause the mouse over a cluster
object. In Properties, you see more detailed information
about any session, cluster, node, or package on your map. To open
Properties, select an object, then go to the menu on top. Or right-click
an object and use the pop-up menu.
You can issue common administrative commands on your clusters through
Serviceguard Manager. WIth Serviceguard A.11.16 clusters, administrators
can be specified by configuring a non-root Admin Access Control
Policy. With Serviceguard A.04.00, you can configure clusters and
packages on nodes with Serviceguard A.11.16 installed. How
it Works | |
You install Serviceguard Manager on a management station.
This can be HP-UX, Linux, or Windows. From the management station, you connect to a Session Server
with Serviceguard installed (HP-UX or Linux). Each Session Server connection
is displayed on the tree with the clusters it discovered. The component
of Serviceguard that interfaces with Serviceguard Manager is called
the COM (Cluster Object Manager). The version of the Session Server’s
COM is shown in its properties. When you log in to a Session Server, it goes out on its subnets
to discover Serviceguard nodes configured for these types of clusters: Serviceguard, Version A.10.10 and
later Serviceguard Extension for RAC, Version A.11.14.01
or later ServiceGuard OPS Edition, Version A.11.13 and later Metrocluster, all versions Continentalclusters, all versions Serviceguard Extension for Faster Failover, all
versions.
You can do administrative commands if the Session Server and
the target Serviceguard node or cluster has version A.11.13 or later.
The rules for access are different in Serviceguard versions A.11.13
to A.11.15 than in version A.11.16. See Table 1-1 “Capabilities of Session Servers on Target clusters”Table 2-1 on page 18. The Session Server queries Serviceguard nodes on its subnet
for status and configuration information. If the discovered node
has allowed the Session Server to query, the information will appear
in your map, tree, Properties, and Alerts. (See “Before
Installing Serviceguard Manager,” below, for a description
of configuring node access permissions.) Note: Because Continental Clusters are always on more than
one subnet, Serviceguard Manager sees them as two clusters. To see
all the information about a Continental cluster, open two separate
sessions, one on each subnet. |
Printable version
