Integrate NNMi with Universal CMDB

By integrating Universal Configuration Management Database (UCMDB) with NNMi, you can store Layer 2 topology objects into UCMDB's database as CI types. These additional CI types enable you to enhance the change management and impact analysis tasks in UCMDB by including network resources.

This topic includes the following sections:

• Components of Integration
• Prerequisite Tasks
• Enable the Integration
• Use the Integration
• Disable the Integration

Components of Integration

The NNMi-UCMDB integration requires the following components:

• NNMi 10.30
• UCMDB 10.10, 10.11, 10.21, 10.22, 10.31, 10.32, 10.33

Prerequisite Tasks

1. Install NNMi.
2. Install UCMDB.

3. Create a new integration user in UCMDB.

   1. Open the UCMDB console.
   2. Select Security.
   3. Click Roles Manager.
   4. Create a New Role (for example, NNMi Integration)
   5. Go to the General Actions tab.
   6. Add Run Legacy API in System Access Actions and save it.
   7. Click Users and Groups.
   8. Add a new user and specify the credentials.
   9. Go to the Roles tab, and then click Edit.
   10. Select Discovery and Integration Admin and the newly created NNMi Integration roles.
   11. Save the new user.

4. Add an additional attribute to the InfrastructureElement CI Type.

   1. Open the UCMDB console.
   2. Select Modeling.
   3. Click CI Type Manager.
   4. Expand ConfigurationItem.
   5. Click IntrastructureElement.
   6. Go to the Attributes Tab

   7. Add a new attribute with the following specification:

      • Name: monitored_by
      • Display Name: Monitored By
      • Type: List of String
   8. Save the attribute.

5. If you want to use HTTPS communication, exchange certificates by following these steps:

   1. Log on to the NNMi management server as root or administrator.

   2. Check the certificate repository type.

      To check the type of certificate repository:

      1. Log on to the NNMi console.
      2. Click Help > System Information, and then go to the Server tab.

      3. Check the value of the javax.net.ssl.keyStore property.

         If the property points to the nnm-key.p12 file, your environment has a PKCS#12 repository.

         If the property points to the nnm.keystore file, your environment has a JKS repository.

      Alternatively, do the following:

      1. On the NNMi management server, as root or administer, run the following command:

         • On Windows: %nnminstalldir%\bin\nnmprops -l
         • On Linux: /opt/OV/bin/nnmprops -l

      2. From the command output, note the value of the javax.net.ssl.trustStoreType property.

         The value of this property indicates the type of certificate repository.

   3. Run the following command to export the NNMi certificate to a temporary file (for example, nnmi.ks).

      • For NNMi with a PKCS#12 repository:

        • On Windows:%nnminstalldir%\bin\nnmkeytool.ovpl -exportcert -alias<Cert alias>-keystore %nnmdatadir%\shared\nnm\certificates\nnm-key.p12 -storepass nnmkeypass -file C:\temp\nnmi.ks
        • On Linux:/opt/OV/bin/nnmkeytool.ovpl -exportcert -alias<Cert alias>-keystore /var/opt/OV/shared/nnm/certificates/nnm-key.p12 -storepass nnmkeypass -file /tmp/nnmi.ks

      • For NNMi with a JKS repository:

        When you use a JKS repository, you must use the keytool utility of the JDK that is configured to work with NNMi. The keytool utility is available in the bin directory under the home directory of the JDK.

        For easy access to the keytool utility:

        1. Determine the home directory of the JDK . The value of the com.hp.ov.nms.jdk.dir property in the nms-local.properties file indicates the directory path.

           The nms-local.properties file is available in the following directory on the NNMi management server:

           • On Windows: %nnmdatadir%\conf\nnm\props
           • On Linux: /var/opt/OV/conf/nnm/props

        2. Create an environment variable that points to the bin directory under the JDK home directory.

           For example, if the com.hp.ov.nms.jdk.dir property in above step shows /opt/OV/nonOV/jdk/zulu/zulu8.21.0.1-jdk8.0.131-linux_x64, set a new environment variable—for example, NNMi_JDK_BIN— that points to the /opt/OV/nonOV/jdk/zulu/zulu8.21.0.1-jdk8.0.131-linux_x64/bin directory.

        After setting the NNMi_JDK_BIN variable, run the following command:

        • On Windows:%NNMi_JDK_BIN%\keytool -exportcert -alias<Cert alias>-keystore %nnmdatadir%\shared\nnm\certificates\nnm.keystore -storepass nnmkeypass -file C:\temp\nnmi.ks
        • On Linux:$NNMi_JDK_BIN/keytool -exportcert -alias<Cert alias>-keystore /var/opt/OV/shared/nnm/certificates/nnm.keystore -storepass nnmkeypass -file /tmp/nnmi.ks

      In this instance, <Cert alias> is the alias of the NNMi certificate.

   4. Transfer the certificate to a temporary directory on the UCMDB server.
   5. Log on to the UCMDB server as root or administrator.

   6. Import the NNMi certificate to the UCMDB trust store.

   7. Export the UCMDB certificate to a temporary file (for example, ucmdb.ks):

   8. Transfer the UCMDB certificate to a temporary directory on the NNMi management server.

   9. On the NNMi management server, run the following command to import the UCMDB certificate to NNMi's trust store:

      • For NNMi with a PKCS#12 repository

        • On Windows:%nnminstalldir%\bin\nnmkeytool.ovpl -importcert -aliashpcert -keystore %nnmdatadir%\shared\nnm\certificates\nnm-trust.p12 -file C:\temp\ucmdb.ks
        • On Linux:/opt/OV/bin/nnmkeytool.ovpl -importcert -aliashpcert-keystore /var/opt/OV/shared/nnm/certificates/nnm-trust.p12 -file /tmp/ucmdb.ks

      • For NNMi with a JKS repository

        • On Windows:%jdkdir%\bin\keytool -importcert -aliashpcert-keystore %nnmdatadir%\shared\nnm\certificates\nnm.truststore -file C:\temp\ucmdb.ks
        • On Linux:$jdkdir/bin/keytool -importcert -aliashpcert-keystore /var/opt/OV/shared/nnm/certificates/nnm.truststore -file /tmp/ucmdb.ks
   10. Restart the UCMDB server.

Enable the Integration

To enable the NNMi-UCMDB integration:

1. Log on to the NNMi console as administrator.
2. Click Integration Module Configuration, and then click NNMi - BSM/UCMDB Topology. The NNMi - BSM/UCMDB Topology Integration Configuration page opens.

3. On the NNMi - BSM/UCMDB Topology Integration Configuration page, follow these steps:

   1. Select Enable Integration.
   2. If NNMi uses the HTTPS protocol for communication, select NNMi SSL Enabled.
   3. In the NNMi User box, type the name of an NNMi administrator.
   4. In the NNMi Password box, type the password of the above user.
   5. If UCMDB is configured to use HTTPS, select BSM SSL Enabled.
   6. In the BSM Host box, type the FQDN of the UCMDB server.
   7. In the BSM Port box, specify the communication port of UCMDB.
   8. In the BSM RTSM User box, type the name of the user that you created in step 3.
   9. In the BSM RTSM Password box, type of password of the above user.

   10. Optional. Select Only synchronize managed objects if you want to exclude unconnected interfaces from the integration.

   11. Optional. Click More Options for finer grain control over the types of CIs to be included in the topology synchronization. The Additional Object Filtering Options page opens. The page enables you to send the following objects to UCMDB:

       • Subnets
       • Interfaces
       • Addresses
       • Cards
       • Ports
       • Connections
       • VLANs

       Click Submit after making the selection.

   12. In the Topology Synchronization interval box, type the interval at which UCMDB will synchronize its database with the NNMi topology data.

   13. Type a Rule bundle name that defines the set of rules used to identify impacted UCMDB CIs.

       You can also type a Rule severity level, which determines the impact analysis trigger severity when applying the rules.

   14. Click Submit.

   15. Restart NNMi processes by running the following commands:

       1. ovstop -c
       2. ovstart -c

Use the Integration

The NNMi-UCMDB integration adds the Find BSM Impacted CIs item to the Actions menu for nodes in the NNMi console. To use this menu item, follow these steps:

1. Log on to the NNMi console.
2. Go to the Node view.

3. Click Actions > Find BSM Impacted CIs.

   A list of CIs returned from the UCMDB Impact Analysis Manager appears.

You can also see the following CI types in the UCMDB database:

• InfrastructureElement > Node: The nodes in the NNMi topology.

• InfrastructureElement > NodeElement> Interface: The interfaces associated with the Node CIs that the integration populates.

• InfrastructureElement > NetworkEntity > IpAddress: The IP addresses of the interfaces associated with the Node CIs that the integration populates.

• InfrastructureElement > NodeElement> HardwareBoard: The cards associated with the Node CIs that the integration populates.

• InfrastructureElement > NodeElement> PhysicalPort: The ports associated with the Node CIs that the integration populates.
• InfrastructureElement > NetworkEntity > IpSubnet: All subnets in the NNMi topology. Unless explicitly excluded, all subnets are provided to the database so that they are available for IP address relationships when node IP address CIs are created from the NNMi topology.
• InfrastructureElement > NetworkEntity > Layer2Connection: The NNMi Layer 2 connections with at least two connection ends that the integration populates as Node CIs.
• InfrastructureElement > NetworkEntity > Vlan: The NNMi VLANs with at one port that the integration populates as a Port CI.

Node Role Changes in NNMi

A device role might change from switch to a switch-router. Devices such as switches, routers, and servers are all defined as Node CI Types. The device type is identified by the Node CI’s NodeRole attribute. The NodeRole attribute is set to one or more of the following values:

• hub

• load_balancer

• printer

• router

• server

• lan_switch

• voice_gateway

• desktop
• firewall
• computer
• network_appliance

• wireless_access_point

The following table shows the mapping of NNMi Device Category to NodeRole attribute:

Device Category	NodeRole Attribute Value
Hub	hub
LoadBalancer	load_balancer
Printer	printer
Router	router
Server	server
Switch	lan_switch
Switch_Router	router, lan_switch
Voice Gateway	voice_gateway
Workstation	desktop
Firewall	firewall
Computer	computer
Network_Appliance	network_appliance
Wireless_Access_Point	wireless_access_point

 

Disable the Integration

1. In the NNMi console, click Integration Module Configuration, and then click NNMi - BSM/UCMDB Topology. The NNMi - BSM/UCMDB Topology Integration Configuration page opens.
2. Clear the Enable Integration check box.
3. Click Submit.