Monitoring Multiple Systems

I l @ ve RuBoard

If you have a set of systems that needs to be managed in similar ways, being able to perform operations on groups of systems, rather than individual systems, can cut down on your having to do repeated tasks . Several tools allow you to cluster or group systems together, which can help you to apply management policies or monitor configurations in a single operation.

IT/O

IT/O managed nodes can be grouped into node groups . When configuring monitoring for IT/O managed nodes, you can assign templates to an entire node group. Then, when you update the managed nodes, templates are distributed to all of the systems that are defined in the node group. This makes it easier to configure multiple systems in a consistent way and there is less room for error. If you assign templates to node groups, however, it becomes difficult to customize monitoring for each system. Customization requires separate templates that get applied individually to each node as needed.

ClusterView

Some companies group critical systems together into a high availability configuration referred to as a cluster . ClusterView has special monitoring capabilities for HP-UX and Windows NT high availability clusters. It can report on the overall status of a cluster. In some cases, a cluster is considered to be available when at least one system in the cluster is up.

ClusterView also allows you to define management clusters as a group of HP-UX systems. Then, from IT/O, you can apply management operations, such as applying templates or graphing metrics in PerfView, on a group of systems in a single step.

In a single-system environment, you know where your application is running. When running applications in an MC/ServiceGuard environment, you may not always know where your applications are running. ClusterView shows where your applications are running or where they last attempted to run and their status.

I l @ ve RuBoard