HP OpenView System Administration Handbook [Electronic resources] : Network Node Manager, Customer Views, Service Information Portal, HP OpenView Operations نسخه متنی

Figure 11-1. The Network tab of the Generic Net demo displays fictitious data consisting of

Network Device Health, Message Board, Topology, Bookmarks , and

Alarms .

[View full size image]

Figure 11-3. SIP may be configured to display NNM Topology. The NNM topology module must be configured and the map must be open to access the topology.

Chapter 9, "Scalability and Distribution") to create a separate map for each customer. A combination of map filters and CV configuration (covered in Chapter 10, "Customer Views") allows you to define exactly what a customer's map contains. After the map has been created, configure an SIP user to have access to the customized map. This prevents a customer from accessing the topology of another customer's network.

Network Health gauges may be displayed on the portal, as shown in Figure 11-4. The following fields defined from NNM and Customer Views can be displayed as gauges:

• Router Health
  Devices with the attributes

  isRouter and

  isConnector set to TRUE. Determined by NNM upon discovery.

• Server Health
  Devices with the attribute

  isServer set to TRUE. Defined by the ovcustomer utility.

• Key Device Health
  Devices with the attribute

  isKeyDevice set to TRUE. Defined by the ovcustomer utility.

• Customer Premises Equipment Health
  Devices with the attribute

  isCPE set to TRUE. Defined by the ovcustomer utility.

• Interface Health
  Devices with the attribute

  isInterface set to TRUE. Determined by NNM upon discovery.

Detailed information for a device gauge may be obtained by clicking the gauge.Chapter 8, "Data Collection and Event Configuration"). Create an SIP user that has access only to a specific Alarm category. This not only hides alarms generated by other customer equipment, but also allows you to limit the alarms displayed to the customer. For example, a customer may not want to know when an interface goes down if it comes back within a short period of time. The configuration of the Alarm category is the key to what you wish the customer to see.

The Message Board shown in Figure 11-6 provides a way for an SIP administrator to communicate with users via the portal. Any user created with SIP administration capability can send messages to the board. The Message Board can be used to

• Create messages that include problem status information

• Change context of existing messages

• Delete messages from the board that should no longer be displayed

Bookmark links, also shown in Figure 11-6, can be used for quick access to documents and web pages. For example, you may want to provide access to OpenView documentation, software downloads, or internal web pages.

OpenView Internet Services (OVIS) allows you to monitor a customer's Intranet and network services. OVIS measures the availability, response time, set up time, and throughput of specific network activity. It can generate alarms and make them available to NNM. Information gathered by OVIS can be displayed on the portal, as shown in Figure 11-7. For more information on OVIS, refer to the Internet Services documentation available at http://ovweb.external.hp.com:80/lpe/doc_serv.

OpenView Service Navigator, an add-on component of OpenView Operations, allows you to configure services. A service is a group of processes or relationships between processes and systems. SIP can display Service Navigator-defined Service Cards, Service Graphs, Service Browser, and Service Health, as shown in Figure 11-8. For more information on Service Navigator, refer to the OpenView Operations section of the document server for the document

Service Navigator Concepts and Configuration Guide available at http://ovweb.external.hp.com:80/lpe/doc_serv.

OpenView Operations (OVO) allows you to detect, solve, and prevent problems occurring in networks, systems, and applications. OVO agents are distributed to the managed systems. The OVO agents perform local monitoring of logfiles and processes. When the agent encounters a problem, it performs a local action and sends a message to the OVO manager. The message generated by the agent appears in the OVO message browser. The OVO messages may be integrated into SIP, as shown in Figure 11-9. For more information on OVO, refer to the document server http://ovweb.external.hp.com:80/lpe/doc_serv.

OpenView Service Desk (OVSD) provides an integrated set of support processes, including call management, incident management, and problem management. SIP can be configured to access OVSD data such as service calls, incidents, and so on, as shown in Figure 11-10. For more information on OVSD, refer to the document server http://ovweb.external.hp.com:80/lpe/doc_serv.

OpenView Service Reporter (OVSR) creates web-based reports from systems it discovers. A system running an OpenView Operations agent or an

OpenView Performance (OVP) can be discovered by OVSR. It collects message and operator information from OVO. Reports for performance metrics such as CPU and memory utilization may be generated using OVSR. Reports can be displayed on the portal, as shown in Figure 11-11. For more information on OVSR, refer to the document server http://ovweb.external.hp.com:80/lpe/doc_serv.