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

11.2 INTEGRATING SIP WITH NNM

SIP may be installed on the NNM management station or installed and configured on a separate server. It can be configured to communicate with one or many NNM stations. Three NNM modules may be configured in SIP, including

• Alarms module
  Provides the alarm messages gathered from one or more alarm categories within NNM. You can filter the alarms so that only the alarms relevant to a particular user are displayed for an SIP portal view.

• Network Device Health module
  Provides custom gauges that track the health of network devices so that your customers can monitor network performance at-a-glance. Predefined gauges such as router and server health are included. You can also write your own gauge definitions to monitor what is important.

• Topology module
  Provides a collection of submaps from one or more NNM maps. Each map must be open on the management station before the associated submap can be accessed. Drill-down through the NNM submap hierarchy is available.

11.2.1 Configuring Users

Before using SIP with live data, you must first define SIP users and roles. Users and Roles are defined from the SIP Configuration Editor GUI shown in Figure 11-11. Roles are associated with users to differentiate what appears on a user's portal view. For example, you may have a technical user that is interested in always displaying the same data on the portal. You may have a number of NOC Operators that require the ability to customize their portal to view specific data. SIP supplies a technical user that cannot be customized from the portal and a NOC operator that allows the user to add modules from the portal. The SIP Configuration Editor is started by executing

UNIX: /opt/OV/SIP/bin/SIPConfig

Windows: Start

Programs: HP OpenView

Service Information Portal

Configuration Editor

All valid portal users must be associated with at least one role. A role defines what a user can see and do through the portal. If a user has been associated with multiple roles, he can switch between roles via a drop-down list on the portal.

SIP uses XML files to define users and roles. The configuration editor manipulates these files based on the information supplied in the GUI. Each user and each role consists of a separate set of XML files organized per user. Before defining a user, you should determine the responsibilities of the user. The basic roles of a user include

• A portal view
  Determines what information the user sees. It is a configured set of modules the user has access to and how these modules appear on the tabs. It also includes portal attributes, such as name, in the button bar, refresh rate, default tab, and portal header and footers.

• An editing permissions level
  Defines the interactive editing operations that a user can perform through the portal interface. There are three editing levels, including ReadOnly, UserPreferences, and ViewAdmin.

• A management data filter
  Refers to information about resources such as services, nodes, interfaces, servers that you want to display through the portal. There are three options in filtering data: AllData, NoData, and a customized data filter (providing nodes, interfaces, and services).

After determining the user roles, define a user. The following steps allow you to define a user with the existing role of a NOC Operator. The NOC Operator portal view contains a similar setup to the Generic Net view except that live data from your network is displayed. The NNM map must be open to access the Topology module.

1. Start the SIP Configuration Editor.

2. Right-click

   Users and select

   New… .

3. Provide the User Login Name
   operator and Display Name NOC
   operator on the
   General tab, as shown in Figure 11-13.

   Figure 11-13. Use the

   SIP Configuration Editor to add users. Supply a

   User Login Name and a

   Display Name from the General tab.

   
   

   height="393" SRC="/image/library/english/10090_11fig14.gif" >

4. Select the

   Roles tab. Click the drop-down list for the

   Initial Role: and select

   NOC

   Operator as shown in Figure 11-14.

   Figure 11-14. Select the Roles tab to define the

   Initial Role and

   Other Roles for a user. Select the Initial Role from the drop-down list as shown.

   
   

   [View full size image]

   height="393" SRC="/image/library/english/10090_11fig15.gif" >

5. Click the

   [Add] button and select

   NOC

   Operator and

   Technical and click

   [OK] (see Figure 11-15).

   Figure 11-15. Select the

   [Add] button from the Roles tab to provide additional roles for the user. Select as many roles as required for the user.

   
   

   height="406" SRC="/image/library/english/10090_11fig16.jpg" >

6. Select

   FileSave from the main menu of the SIP Configuration Editor.

7. Open the default NNM map by executing

   ovw&

8. Login as the newly created user operator from the URL http://hostname/ovportal, specifying the SIP server hostname.

The NOC Operator role has the ability to add and remove modules as required for his job. Any user associated with the NOC Operator role has this capability. Figure 11-16 shows the drop down list of modules that may be added to the user's portal.

11.2.2 Configuring Roles

A role defines what the user sees in the portal view. Filters may be defined at the role level to hide data. This involves explicitly associating a filter definition with each role. The filter defines what data should be displayed when a user is acting in the given role. Three management data filters are available when defining roles:

1. Show All Data
   Use this option if you do not want to segment data by customer organization.

2. Show No Data
   Use this option if you do not want to display any real data through the portal, such as the Generic Net demo.

3. Show Data for the Following Organizations
   Use this option if you want to configure a specific customer model that contains the organizations that you want to filter on.

Users and roles are configured in XML files. While these files may be manually edited, it is recommended that you use the SIP Configuration Editor to make changes. Certain advanced features are not available in the Configuration Editor and require the editing of the XML files. Roles can be modified using the following steps:

1. Start the SIP Configuration Editor.

2. Right click

   Roles and select

   New… .

3. Provide the

   Role Name and

   Display Name fields.

4. Select the Edit Permissions

   ViewAdmin as shown in Figure 11-17.

   Figure 11-17. Supply the name of the XML file for the portal view relative to the views directory. Use the

   [Browse] button to search for the XML files. Sample XML files are provided in the

   samples directory.

   
   

   [View full size image]

   height="344" SRC="/image/library/english/10090_11fig18.gif" >

5. Click the

   [Browse] button and browse to the file samples/technical.xml.

6. Provide the Modified View File

   myTech.xml .

7. Select the

   Data Management tab shown in Figure 11-18.

   Figure 11-18. Select

   Use specific management data on the

   Management Data tab. Select

   All Data from the data drop-down list to give a user access to all customers.

   
   

   height="344" SRC="/image/library/english/10090_11fig19.gif" >

8. Select

   Use specific management data: AllData .

9. Click

   [OK] .

10. Select

    FileSave from the main menu of the SIP Configuration Editor.

11.2.3 User Role Packages

In addition to providing the capability of defining users and roles, the SIP Configuration Editor may be used to group users and roles by organization. This type of grouping is called a user role package. Each user role package contains a set of users, roles, and management data. You can define all users and roles in a single package or partition them into multiple packages. For example, you may want to create a separate package for each customer. This package would contain the customer's role definitions, users, and management data. To create a package, follow these steps:

1. Start the SIP Configuration Editor.

2. Right-click

   User Role Packages and select

   New…

3. Provide the

   Package Name: Customer1

4. Provide the

   Package Title: Customer1

5. Select

   Assign Default Management Data .

6. Select

   AllData from the

   Default Management Data drop-down list.

7. Add Roles and Users to the newly created user role package, as previously defined.

11.2.4 Adding an NNM Station to SIP

Before accessing live data via your portal, you must establish connectivity between SIP and NNM. One or more NNM stations can be added to SIP. NNM does not need reside on the same system as NNM. NNM stations are configured with the SIP Configuration Editor.

1. Start the SIP Configuration Editor.

2. Right-click the

   Management Stations folder and select

   [New…] .

3. Provide the fully qualified hostname of the management station and click

   [OK] .

4. Select the

   NNM tab, as shown in Figure 11-19.

   Figure 11-19. To add an NNM server, start the SIP Configuration Editor, right-click

   Management Server , and click

   New . From the NNM tab, select

   NNM Is Installed On This System as shown.

   
   

   height="404" SRC="/image/library/english/10090_11fig20.gif" >

5. Select

   NNM

   Is Installed On This System .

6. Select the Version of NNM you are running.

7. Select the operating system (Windows or UNIX).

8. The port numbers do not need to be modified. They are populated when you save the configuration.

9. Select

   Use As

   SNMP

   Data Source to enable access to data for the Network Device Health Gauge module.

10. Select

    Use As Alarms Data Source to enable access to data for the Alarms module.

11. Select

    Use As OVw Symbol Source to enable access to symbol images for the Topology module and click

    [OK] .

11.2.5 Integrating CV Organizations

The SIP program

getcvdata.exe generates an XML file of the data from the CV database. Each XML file generated is an SIP customer model mapping conforming to the standard SimpleCustomerModel.dtd supplied with SIP. Configure CV as defined in Chapter 8 before this integration begins. The following steps allow integration of Customer Views defined data to be integrated into SIP:

1. Execute the command

   getcvdata.exe .

   UNIX :
   

   /opt/

   OV /www/cgi-bin/getcvdata.exe > /tmp/cvdata.xml

   Windows :
   

   \OpenView\www\cgi-bin\getcvdata.exe > c:\temp\cvdata.xml

2. Copy the

   cvdata.xml file to the organizations directory.

   UNIX:

   cp /tmp/cvdata.xml /opt/

   OV /

   SIP /conf/share/organizations

   Windows:

   copy \temp\cvdata.xml %SIP_HOME%\conf\share\organizations

3. Log into the portal as

   sipadmin .

4. Select the

   Customer Model tab and scroll down to

   Customer Model Sources .

5. Type

   cvdata.xml in the New customer Model Source URL field.

6. Click

   [Add] to integrate all customers from the

   cvdata.xml file.

7. Create a new package called BellSouth (assuming that you defined BellSouth as a customer in CV).

8. Add new management data specifying to

   Show Data for the Following Organizations . The drop-down list should now contain all customers previously defined in CV. Select bellsouth.net and click

   [OK] twice.

9. Create a new role named Bell South Tech. Specify the Edit Permissions as

   ViewAdmin . Browse to the

   samples/technical.xml as the Portal View File. Select

   Use Specific management Data and select

   Bell South .

10. Define a new user named BellSouth using the BellSouth Tech Role. When you login as the newly defined user, you see a filtered view of the network. Based on this filter, the view is limited to BellSouth alarms, network device health and topology.