Integrate > Integrate with NNMi with Intelligent Management Center

Integrate with NNMi with Intelligent Management Center

Network Node Manager i Software (NNMi) enables you to quickly detect, isolate, and troubleshoot abnormal network behavior. Using NNMi, you can also record what has been done to date to troubleshoot or resolve a problem.

Use NNMi and the NNMi - HPE IMC integration to leverage the features of NNMi and HPE IMC together. Together, NNMi and HPE IMC provide better tools to manage networks with heterogeneous elements that require highly scalable and fully integrated network management tools.

This topic contains the following sections:

Components of Integration

  • NNMi.
  • HPE IMC 7.1, 7.2

Prerequisite Tasks

  1. Install NNMi.
  2. Install HPE IMC.

 

Enable the NNMi - HPE IMC integration Integration

Task 1:    Load the MIBs Supported by HPE IMC (Optional)

Although not mandatory, manually loading the MIBs supported by HPE IMC extends NNMi’s monitoring capabilities. For example, having this additional information enables you to create custom collections using NNMi. See Managing MIBs in the NNMi Help for more information.

During the NNMi 10.30 installation, the MIBs supported by HPE IMC are installed on the NNMi management server. Complete the following steps to manually load these installed MIBs into NNMi using the nnmloadmib.ovpl script:

  1. All of the NNMi processes must be running before you attempt to load any additional MIBs.

  2. Look in the following directories and locate the additional MIBs that you want to load to support the NNMi - HPE IMC integration:

    Windows:

    • %NNM_SNMP_MIBS%\Vendor\H3C
    • %NNM_SNMP_MIBS%\IMC

    Linux:

    • $NNM_SNMP_MIBS/Vendor/H3C
    • $NNM_SNMP_MIBS/IMC

  3. To load the additional MIBs for devices supported by HPE IMC that exist in your network, see the directories shown in All of the NNMi processes must be running before you attempt to load any additional MIBs.. Run the following commands to load any of the MIBs for devices supported by HPE IMC. Make sure to verify that the displayed results include the MIBs you load:

    Windows:

    • nnmloadmib.ovpl -load %NNM_SNMP_MIBS%\Vendor\H3C\<mib name> -u <username> -p <password>
    • nnmloadmib.ovpl -load %NNM_SNMP_MIBS%\IMC\<mib name> -u <username> -p <password>

    Linux:

    • nnmloadmib.ovpl -load $NNM_SNMP_MIBS/Vendor/H3C/<mib name> -u <username> -p <password>
    • nnmloadmib.ovpl -load $NNM_SNMP_MIBS/IMC/<mib name> -u <username> -p <password>
    TIP:  Check for prerequisite MIBs before using the nnmloadmib.ovpl script to load these MIBs. The commands shown in this step will not load the MIBs if the prerequisite MIBs are not loaded.

    Instead of using the nnmloadmib.ovpl script to load these MIBs, use the Tools > Load/Unload MIB menu in the NNMi console, as it lists any prerequisite MIBs.

  4. Verify that the MIBs loaded correctly, by doing one of the following:

Task 2:    Load the Trap Definitions

For NNMi to retain (not drop) HPE IMC traps, you must manually load the HPE IMC trap definitions that are important for your network. If you do not load any HPE IMC trap definitions, NNMi drops the HPE IMC traps forwarded to NNMi by HPE IMC.

For most network environments, you will not want to load all of the HPE IMC trap definitions into NNMi. It is important that you determine the traps that are important for your network, then load only those traps into NNMi.

To load the trap definitions for HPE IMC-managed devices, do the following:

 a.    Change to the following directory:

  • Windows: %NnmInstallDir%\newconfig\HPOvNmsEvent
  • Linux: $NnmInstallDir/newconfig/HPOvNmsEvent

 b.    For NNMi to retain (not drop) HPE IMC traps, you must manually load the HPE IMC trap definitions that are important for your network. If you do not load any HPE IMC trap definitions, NNMi drops the HPE IMC traps forwarded to NNMi by HPE IMC.

NNMi provides the nnm-imc-incidentConfig.xml file that contains thousands of the HPE IMC trap definitions. In most network environments, you do not want to load all of these trap definitions into NNMi. To stop from loading unnecessary trap definitions, create a subset of the nnm-imc-incidentConfig.xml file, removing any of the trap definitions you do not need.

To help determine which incidents to retain from the nnm-imc-incidentConfig.xml file, you might do the following:

 a.    Access your HPE IMC product.

 b.    Browse the alarms that you are receiving, and determine which IMC alarms you want to forward to NNMi.

 c.    Look for and save the incident definitions that contain the OIDs for those alarms in a file, such as myincidents.xml.

 d.    Use the myincidents.xml file in the nnmconfigimport.ovpl command as shown below.

In rare circumstances, you might need to load a large number of trap definitions and could experience Configuration Import Errors.

Depending on whether you decide to use the nnm-imc-incidentConfig.xml file or the myincidents.xml file, use one of the following commands to load the HPE IMC trap definitions:

  • nnmconfigimport.ovpl -f myincidents.xml -u <username> -p <password>
  • nnmconfigimport.ovpl -f nnm-imc-incidentConfig.xml -u <username> -p <password>

Task 3:    Enable NNMi to Collect IMC Data

After completing the steps in this section, NNMi gathers data from the IMC servers you configured for the integration. During this discovery process, NNMi adds seeds for devices found in the set of IMC servers and links the devices to their IMC source.

NNMi discovers the devices contained in the IMC inventory and obtains information from IMC about these devices if they meet the following criteria:

  • NNMi has not already discovered the device.
  • The device is not already entered as a seed device in NNMi.

To enable NNMi to start collecting IMC data:

  1. From the NNMi console, click Integration Module Configuration > IMC. NNMi shows the NNMi - HPE IMC Integration Configuration screen.

  2. Select Enable IMC Integration.

  3. Select IMC SSL if you configured IMC to accept SSL connections.

  4. Add the following NNMi integration information:

    • NNMi host: This field contains the fully qualified domain name of the NNMi management server.
    • NNMi User: Enter an NNMi username that is mapped to an NNMi Administrators user group. This can also be an NNMi username mapped to an NNMi Web Service Clients user group.
    • NNMi Password: Enter the NNMi username password.

  5. Add the following HPE IMC integration information:

    • IMC host: This field contains the fully qualified domain name of the IMC server.
    • IMC Port: This field contains the port number used for accessing the IMC server.
    • IMC User: Enter the IMC username.
    • IMC Password: Enter the IMC username password.

  6. Optional. You can configure the NNMi - HPE IMC integration module for multiple IMC servers. These IMC servers function as element managers for a set of devices. These devices would then be seeded into NNMi so that NNMi is aware of the full set of devices. To add another IM server, click Add another IMC server.

    You need not configure the same username and password on each IMC host. NNMi supports using a separate IMC host username and password for each IMC host.

  7. Click Submit to finish enabling the NNMi - HPE IMC integration. After you click Submit, HPE IMC and NNMi begin sharing device information.

    NNMi periodically reads the set of management IP addresses from each configured IMC server. For each device that NNMi has not already discovered, and that does not already have a NNMi seed entry, NNM adds the new device or devices to its inventory. NNMi also saves the device ID as a custom attribute on the NNMi node.

NOTE:  If a node is removed from HPE IMC or NNMi, you must manually remove the node from the other application. There is no automatic discovery synchronization for removing a node from HPE IMC or NNMi.

Task 4:    Configure SSL Access for the NNMi - HPE IMC Integration

After completing this task, single sign-on works between the NNMi console and the HPE IMC console. Completing this task permits you to open the HPE IMC console from the NNMi console to view the device details residing in IMC.

If you selected IMC SSL in step 3, complete the following steps to configure an SSL connection between NNMi and HPE IMC.

The instructions in this section include how to import the IMC trust certificate into the NNMi trust store. Before you import the IMC trust certificate into the NNMi trust store, you must replace the IMC keystore with one that you create (as shown in step a through step b), so that the hostname verification succeeds when NNMi connects to HPE IMC.

SSL authentication relies on certificate path validation. For example, if VeriSign guarantees NNMi, and NNMi guarantees HPE IMC, then the certificate path will be HPE IMC <- NNMi <- VeriSign and authentication works correctly. These instructions assume that most systems trust VeriSign, and that you only need to import the NNMi and HPE IMC certificates.

Important: If the HPE IMC <- NNMi <- VeriSign chain is broken due to the NNMi certificate not being imported into HPE IMC, or the HPE IMC certificate not being imported into NNMi, the SSL authentication will not work properly.

 a.    Generate a replacement IMCkeystore file using the following command.

Replace <IMC_FQDN> with the fully qualified domain name of the IMC server.

Windows: <IMC_Installation_Directory>\deploy\jdk\jre\bin\keytool.exe -genkey -v -alias iMC -validity 3650 -keyalg RSA -dname "CN=<IMC_FQDN>, OU=your_workgroup, O=Unknown, L=Unknown, S=Unknown, C=Unknown" -keypass iMCV300R002 -storepass iMCV300R002 -keystore keystore

Linux: <IMC_Installation_Directory>/deploy/jdk/jre/bin/keytool -genkey -v -alias iMC -validity 3650 -keyalg RSA -dname "CN=<IMC_FQDN>, OU=your_workgroup, O=Unknown, L=Unknown, S=Unknown, C=Unknown" -keypass iMCV300R002 -storepass iMCV300R002 -keystore keystore

 b.    Replace the keystore file in the <IMC_Installation_Directory>\client\security\ directory with the keystore file you generated in  a.    Generate a replacement IMCkeystore file using the following command. .

 c.    Export the IMC certificates from the keystore file using the following command:

Windows:
<IMC_Installation_Directory>\deploy\jdk\jre\bin\keytool.exe -export -alias imc -file C:\temp\IMC.cer -keystore <IMC_Installation_Directory>\client\security\keystore -storepass iMCV300R002

Linux:
<IMC_Installation_Directory>/deploy/jdk/jre/bin/keytool -export -alias imc -file /tmp/IMC.cer -keystore <IMC_Installation_Directory>/client/security/keystore -storepass iMCV300R002

 d.    Verify that you see the Certificate stored in file <directory>:\IMC.cer message.

 e.    Copy the certificate from the IMC.cer file you created in step c to the NNMi management server.

 f.    Open a command window on the NNMi management server.

 g.    To import the IMC certificate into the NNMinnm.truststore file, run the following command:

Windows:
“%NnmInstallDir%\nonOV\jdk\hpsw\bin\keytool.exe” -import -alias sentinel -file <directory>\IMC.cer -keystore “%NnmDataDir%\shared\nnm\certificates\nnm.truststore” -storepass ovpass

Linux:
$NnmInstallDir/nonOV/jdk/hpsw/bin/keytool -import -alias sentinel -file <directory>/IMC.cer -keystore $NnmDataDir/shared/nnm/certificates/nnm.truststore -storepass ovpass

Make sure you answer yes when asked whether to Trust this certificate?. The following program listing is an example of what happens after you run this command:

Owner: CN=iMC Development Team, OU=R&D Beijing, O="Hangzhou H3C Technologies Co,. Ltd.", L=Shang-Di Information Industry Base, ST=Beijing, C=CN
Issuer: CN=iMC Development Team, OU=R&D Beijing, O="Hangzhou H3C Technologies Co,. Ltd.", L=Shang-Di Information Industry Base, ST=Beijing, C=CN
Serial number: 4609e6be
Valid from: Tue Mar 27 21:53:34 MDT 2007 until: Sun Mar 27 21:53:34 MDT 2022
Certificate fingerprints:
      MD5: A6:3D:D9:F2:15:13:09:4A:22:00:D9:C1:35:CD:53:02
      SHA1: 3D:40:80:73:C8:32:FA:23:F5:24:02:2D:6B:D9:12:C2:DA:94:66:85
      Signature algorithm name: MD5withRSA
      Version: 1
Trust this certificate? [no]: yes
Certificate was added to keystore

 h.    Obtain the NNMi certificate alias name using the following command. Write down the alias value obtained during this step, as you will need that value for the <alias> variable used during the next step.

Windows:

“%NnmInstallDir%\nonOV\jdk\hpsw\bin\keytool.exe” -v -list -keystore %NnmDataDir%\shared\nnm\certificates\nnm.keystore" -storepass nnmkeypass

Linux:

<NnmInstallDir>/nonOV/jdk/hpsw/bin/keytool -v -list -keystore <NnmDataDir>/OV/shared/nnm/certificates/nnm.keystore -storepass nnmkeypass

 i.    Export the NNMi certificate to a file using the following command.

Windows:

“%NnmInstallDir%\nonOV\jdk\hpsw\bin\keytool.exe” -export -alias <alias> -file <directory>\nnm.cer -keystore %NNMDataDir%\shared\nnm\certificates\nnm.keystore -storepass nnmkeypass

Linux:

<NnmInstallDir>/nonOV/jdk/hpsw/bin/keytool -export -alias <alias> -file <Directory>/nnm.cer -keystore <NnmDataDir>/shared/nnm/certificates/nnm.keystore -storepass nnmkeypass

 j.    Copy the NNMi certificate file to a directory on the IMC server.

For multiple IMC servers, complete step j through step l for each IMC server you plan to use in the NNMi - HPE IMC integration.

 k.    Import the NNMi certificate to the IMCtruststore file using the following command.

Windows:

<IMC_Installation_Directory>\deploy\jdk\jre\bin\keytool.exe -import -alias <alias> -file <Directory>\nnm.cer -keystore <IMC_Installation_Directory>\iMC\client\security\truststore -storepass iMCV300R002

Linux:

<IMC_Installation_Directory>/deploy/jdk/jre/bin/keytool -import -alias <alias> -file <Directory>/nnm.cer -keystore <IMC_Installation_Directory>/iMC/client/security/truststore -storepass iMCV300R002

Make sure you answer yes when asked whether to Trust this certificate?. The following program listing is an example of what happens after you run this command:

Owner: CN=<fully qualified system name>
Issuer: CN=<fully qualified system name>
Serial number: 50789c62
Valid from: Fri Oct 12 16:40:34 MDT 2012 until: Sun Sep 18 16:40:34 MDT 2112
Certificate fingerprints:
     MD5: CA:10:C4:8E:88:D5:21:04:DC:F2:95:74:47:65:B5:82
     SHA1: 0B:8D:1D:3F:F0:AA:87:87:D9:E9:1C:CD:DA:4F:C1:62:BF:62:E1:03
     Signature algorithm name: SHA1withRSA
     Version: 3
Trust this certificate? [no]: yes
Certificate was added to keystore

 l.    Restart the IMC server using the Intelligent Deployment Monitoring Agent.

 m.   Run the following command sequence on the NNMi management server:

  • ovstop
  • ovstart

 n.    Optional: Run the following commands on both the NNMi management server and the IMC server. Compare the outputs to make sure the keystore certificates reside on both servers’ truststore files:

NNMi management server (Windows):
keytool.exe -v -list -keystore %NnmDataDir%\shared\nnm\certificates\nnm.truststore -storepass ovpass

NNMi management server (Linux):
keytool -v -list -keystore $NnmDataDir/shared/nnm/certificates/nnm.truststore -storepass ovpass

IMC server (Windows):
<IMC_Installation_Directory>\deploy\jdk\jre\bin\keytool.exe -v -list -keystore <IMC_Installation_Directory>/iMC/client/security/truststore -storepass iMCV300R002

IMC server (Linux):
<IMC_Installation_Directory>/deploy/jdk/jre/bin/keytool -v -list -keystore <IMC_Installation_Directory>/iMC/client/security/truststore -storepass iMCV300R002 

Use the Integration

If you select any node in NNMi that was seeded from an IMC server, you can use the HPE IMC->View node in IMC menu from the NNMi console to open the IMC console. From the IMC console, you can log on to view information about the selected node. If you configured SSL access for the NNMi - HPE IMC Integration, the HPE IMC->View node in IMC menu in the NNMi console takes you directly to the device view in the corresponding IMC console.

The HPE IMC->View node in IMC menu item is enabled only if the selected node is SNMP enabled.

To open an IMC console view from the NNMi console (of any node that was seeded from an IMC server):

  1. Use the Action > HPE IMC > View Node in IMC menu to open a view of the node in the HPE IMC console.

  2. You can also use nodes located in Topology Maps in the NNMi console to access theHPE IMC console: for example, select a node from a Layer 3 Neighbor view; then right-click the node and use the HPE IMC > View Node in IMC to open a view of the node in the HPE IMC console.

Discover Information from IMC

During discovery, NNMi gathers data from the IMC servers you configured for the integration. During this discovery process, NNMi adds seeds for all the devices found in the set of IMC servers and links the devices to their IMC source. NNMi also saves the device ID as a custom attribute on the NNMi node.

During discovery, if there are devices that have been discovered by multiple IMC servers, NNMi links the first IMC server reporting these devices as the IMC source. If multiple IMC servers discover a device, then NNMi only discovers the device from the first IMC server reporting the device to NNMi.

Devices contained in the IMC inventory share information with NNMi if they meet the following criteria:

  • NNMi has not already discovered the device.
  • The device is not already listed as a seed address in NNMi.

If NNMi has already discovered nodes that also reside in the IMC database, NNMi does not automatically update customAttributes for these devices.

Use the Analysis Pane

When using the NNMi - HPE IMC integration, the NNMi console includes two additional analysis panels. These panels show device information when a selected node originates from an IMC server. These two panels are labeled Asset Details and Hardware/Firmware. Select Asset Details to view a table of HPE IMC-monitored device components. Select Hardware/Firmware to view additional hardware and firmware details discovered by HPE IMC.

The menu option is disabled for non-IMC nodes OR for non-SNMP nodes (even if they came from IMC).

Load Trap Definitions

Although discourages loading all of the IMC incident definitions discussed in Load the Trap Definition, there might be rare situations that require you to load many of the IMC incident definitions. If you must load a large number of trap definitions, split the nnm-imc-incidentConfig.xml file into two or more separate files, each containing a subset of the trap definitions, then load each file separately.

Make Configuration Changes

Required Configuration Changes: NNMi will not automatically update customAttributes for devices found in IMC if these devices already reside in the NNMi database. To configure the NNMi - HPE IMC integration to automatically update customAttributes for devices found in IMC, do the following:

  1. Remove the seeds for the devices from NNMi. To do this use the Configuration > Discovery > Seeds menu.

  2. Delete the node from NNMi:

    1. Use the Inventory > Nodes menu.
    2. Select the nodes you want to delete.
    3. Use the Action > Delete menu to delete the nodes.
  3. NNMi now receives information about the deleted devices, including customAttributes, from IMC.

  4. NNMi rediscovers the device using information forwarded by IMC.

If you delete any nodes that NNMi assigned to tenants other than the Default Tenant, then NNMi will rediscover those nodes and assign them to the Default Tenant. This Default Tenant assignment could disrupt an NNMi tenant model configuration.

Disable the Integration

To disable the NNMi - HPE IMC integration, do the following:

  1. From the NNMi console, click Integration Module Configuration > IMC. NNMi shows the NNMi - HPE IMC Integration Configuration screen.

  2. Deselect Enable IMC Integration.

  3. Click Submit to finish disabling the NNMi - HPE IMC integration.

    If you disable the NNMi - HPE IMC integration, then enable the integration at a later time, the discovery process starts again (re-synchronizes) to ensure that NNMi has the latest device information from the IMC servers.

After you disable the NNMi - HPE IMC integration, log out of the NNMi console, then log back in, you will no longer see the IMC-related menu items in the NNMi console. There are no other user actions required after completing these steps.

Send Help Center feedback