HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations

Tammy Zitello

نسخه متنی -صفحه : 276/ 87
نمايش فراداده

12.3 THE OVO ADMINISTRATOR

OVO makes no assumptions about a managed enterprise. Because of this, the OVO managed enterprise must be configured. The default administrator account is

opc_adm and the password is

OpC_adm . The administrator account provides the capability to configure the managed environment. The OVO administrator tasks of OVO include:

  • Adding managed nodes Devices connected to the network are discovered by underlying NNM processes (see Chapter 3, "Create a Deployment Plan"). However, devices are not automatically managed by OVO. The administrator must define the devices that to be monitored.

  • Creating node groups Node groups provide a logical means of managing systems. Nodes can be grouped based on attributes such as platform, application or customer. Node groups can be used to assign templates. Node groups are assigned to an operator based on the operator's skill set.

  • Creating message groups Message groups provide a logical means of grouping events that arrive in the message browser. Message groups are assigned to an operator.

  • Creating and customizing templates Templates are assigned and distributed to the managed node to determine what the OVO agent will monitor.

  • Creating template groups Template groups provide a logical means of organizing template. Template groups are assigned and distributed to the managed node to determine what the OVO agent will monitor.

  • Creating operators The default OVO operator account is

    opc_op . A typical environment will have a separate operator account for each OVO user.

  • Configuring operators The configuration of an operator includes defining managed nodes, applications, message groups. Each OVO operator may have a specific set of managed nodes and message group in which to monitor.

  • Distribution of agents and templates to managed nodes When the managed environment has been defined, the administrator must assign and distribute templates and the OVO agent to the managed node. This installs a process with a small footprint (less than 2% of the CPU) on the managed node. The agent process performs application monitoring and the templates define which applications to monitor.