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

Tammy Zitello

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

11.1 GENERIC NET DEMO

SIP is typically accessed via a traditional web browser. Limited information can be configured and viewed via wireless devices such as PDAs and WML-based cell phones. When you access SIP as a guest, you can see a demo version of SIP. The demo provides an excellent illustration of what SIP could look like after configuration. The data included with the Generic Net demo is fictitious and does not represent your network. The figures in this section illustrate the type of information that can be configured in your portal.

When you install SIP, the Apache web server is installed and configured to run on port 80. If you already have a web server running on port 80, it is necessary to change the port before SIP functions. Perform the following tasks to modify the port number:

  • Edit the file /opt/OV/SIP/apache/conf/httpd.conf.

  • Search for Port and change it from 80 to the desired port.

  • Save and exit the file.

  • Restart the web server as the user root:

    • HP-UX:

      /sbin/init.d/ovsip stop /sbin/init.d/ovsip start

    • Solaris:

      /etc/init.d/ovsip stop /etc/init.d/ovsip start

    • Note

    The default port for secure communications (https) is 443.

    To access the SIP demo, enter the following URL in a browser, supplying the hostname of the SIP server and the port defined previously:

    http://

    hostname:port

    /ovportal

    At the SIP login page, provide the userid

    guest and click

    [Login] . The Generic Net demo portal shown Figure 11-1 should appear. The Network tab of the demo consists of the following five sections:

    • Network Device Health [1] This section provides gauges that indicate router health, server health, key device health, customer premises equipment, and interface health. The information is gathered from NNM and CV. Click any gauge to obtain a list of individual device information shown in Section 11.2, "Integrating SIP with NNM," for access to network device health, topology, and alarms.

      Figure 11-2. Click any device health gauge to display individual device information.

      [View full size image]

    • Message Board This provides a way to send messages to customers. It requires the administration function for the portal. The sipadmin user can send messages from the Message Board tab.

    • Topology The topology gathered from NNM is displayed from the IP Internet submap of the default submap. The map must be open for the topology to be displayed. Drill-down capability is supported.

    • Bookmarks Bookmarks to other web links can be configured by the Bookmarks tab of the sipadmin portal login account.

    • Alarms The alarms module of NNM may be displayed on the portal.

    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]

    The NNM topology maps may be displayed in the portal, as shown in Figure 11-3. The map must be opened in the native NNM GUI to be accessed via SIP. Drill-down functionality is available by double-clicking a symbol.

    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.

    Figure 11-4. Network Device Health may be configured to include

    Router Health, Server Health, Key Device Health, Customer Premises Equipment Health , and

    Interface Health . These gauges can be displayed on a user's portal.

    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.

    Figure 11-5. The Network tab may be configured to display Alarms received by NNM. The NNM alarms module must be configured to display alarms.

    [View full size image]

    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

    Figure 11-6. The Message Board and Bookmarks are displayed on a user's portal. The Message Board provides a mechanism for an SIP administrator to communicate status information to portal users. The Bookmarks provide hypertext links to commonly accesses sites.

    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.

    Figure 11-7. The Internet Tab of the demo is configured to display information regarding services such as

    web page response time, availability , and

    SLO compliance provided by OVIS.

    [View full size image]

    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.

    Figure 11-8. The Service tab of the demo is configured to display the

    Service Browser, Service Graph, Service Cards , and

    Service Health for services configured by OpenView Service Navigator.

    [View full size image]

    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.

    Figure 11-9. The Operations tab of the demo provides Messages generated by OVO.

    [View full size image]

    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.

    Figure 11-10. The Help Desk tab of the demo is configured to provide links to OVSD. SIP can provide access to

    Service Calls, Incidents, Problems, Changes , and

    Work Orders .

    [View full size image]

    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.

    Figure 11-11. The Reports tab of the demo is configured to provide performance data from OVR. Reporter provides data collected by OVO and OVP agents. This data includes performance metrics such as

    CPU, memory , and

    disk utilization .

    [View full size image]