---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure event collection from NNMi

# Configure event collection from NNMi {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

Configure the HP Network Node Manager i (NNMi) connector instance to receive events while monitoring your network resources.
{#configure-nnmi-connector__nnmi-connector}

## Before you begin

Supported version: NNMi 10.30 and later, including NNMi 25.5.  
Note:  
The connector supports NNMi versions 10.30.653 and 25.5. If you use another version and encounter issues, contact ServiceNow Support.

Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllEvent ManagementIntegrationsConnector Instances.
2. Click New.
3. On the form, fill in the fields.  
   {#configure-nnmi-connector__table_usg_pq2_sbb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Descriptive and unique name for the NNMi connector. |
   | Description | Description for the use of the NNMi event collection instance. |
   | Connector definition | Name of the required connector definition. Select NNMi. |
   | Host IP | IP address where NNMi is installed. |
   | Credential | Permission to connect to NNMi. Click the search icon in the Credential field. Either select the required credentials from the list or click New and create the required credentials on the Credentials form. If you create the credentials, save them using a unique and recognizable name, for example, NNMiCHCK. The selected credentials use basic authentication. |
   | Event collection last run time | Last run time value. Automatically updated. |
   | Last event collection status | Last run status. Automatically updated. |
   | Event collection schedule (seconds) | Frequency, in seconds, that the system checks for new events from NNMi. The default value is 120 seconds. |
   | Last error message | Last error message. Automatically updated. |
   [Table 1. Connector Instance form]

   {#configure-nnmi-connector__table_usg_pq2_sbb}
4. Right-click the form header and select Save.  
   The connector instance values are added to the form and the parameters that are relevant to the connector appear.
5. In the Connector Instance Values section, verify and where required, modify the default connector instance values.  
   {#configure-nnmi-connector__table_qjb_lzx_fdb__entry__2}

   | Field | Description |
   |-|-|
   | days_from | Number of days for which events must be collected at the first collection cycle. Default value: <kbd class="ph userinput">7</kbd> days. Note: The maximum number of past events that can be collected is 3,000. The first time that the connector runs, it collects all events (up to the 3,000 limit) that were created from the `days_from` date until the current date. |
   | debug | Display debug messages. Default value: <kbd class="ph userinput">false</kbd>. Specify <kbd class="ph userinput">true</kbd> to see debug messages. |
   | port | Number of the connector port. Default value: <kbd class="ph userinput">80</kbd>. |
   | protocol | Type of protocol. Default protocol type: <kbd class="ph userinput">http</kbd>. |
   [ ]

   {#configure-nnmi-connector__table_qjb_lzx_fdb}
6. **Optional:** In the MID Servers for Connectors section, specify a MID Server that is up and is valid.  
   If no MID Server is specified, an available MID Server that has a matching IP range is used.

   You can configure several MID Servers. If the first is down,
   the next MID Server is used. If that MID Server is not available, the next
   is selected, and so on. MID Servers are sorted according to the order that
   their details were entered into the MID Server for Connectors section.
7. Right-click the form header and select Save.
8. Test the connection between the MID Server and the NNMi connector.
   1. Click Test Connector.  
      If the test fails, follow the instructions that the error issues to correct the problem and then run another test.  
      Note:  
      Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to the external monitoring tool.

      If you encounter the error "TypeError: Cannot read property 'inc:getIncidentsResponse' from undefined, refer to the Known Error article [KB0262185](https://support.servicenow.com/kb?sys_kb_id=6fb0278147ab3a1027a3fac8736d4348&id=kb_article_view) for the updated script and instructions.
   2. After a successful test, select the Active check box.
   {#configure-nnmi-connector__substeps_jc5_ccy_fdb}
9. Click Update.
{#configure-nnmi-connector__steps_sz4_wz1_kz}

*[\>]: and then