{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30331,"path":"it-operations-management/event-management/configure-nnmi-connector.md","title":"Configure event collection from NNMi","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure event collection from NNMi\n\nConfigure the HP Network Node Manager i \\(NNMi\\) connector instance to receive events while monitoring your network resources.\n\n## Before you begin\n\nSupported version: NNMi 10.30 and later, including NNMi 25.5.\n\n**Note:** The connector supports NNMi versions 10.30.653 and 25.5. If you use another version and encounter issues, contact ServiceNow Support.\n\nRole required: evt\\_mgmt\\_admin\n\n## Procedure\n\n1.  Navigate to **All** &gt; **Event Management** &gt; **Integrations** &gt; **Connector Instances**.\n\n2.  Click **New**.\n\n3.  On the form, fill in the fields.\n\n<table id=\"table_usg_pq2_sbb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nDescriptive and unique name for the NNMi connector.\n\n</td></tr><tr><td>\n\nDescription\n\n</td><td>\n\nDescription for the use of the NNMi event collection instance.\n\n</td></tr><tr><td>\n\nConnector definition\n\n</td><td>\n\nName of the required connector definition. Select **NNMi**.\n\n</td></tr><tr><td>\n\nHost IP\n\n</td><td>\n\nIP address where NNMi is installed.\n\n</td></tr><tr><td>\n\nCredential\n\n</td><td>\n\nPermission 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.\n\n</td></tr><tr><td>\n\nEvent collection last run time\n\n</td><td>\n\nLast run time value. Automatically updated.\n\n</td></tr><tr><td>\n\nLast event collection status\n\n</td><td>\n\nLast run status. Automatically updated.\n\n</td></tr><tr><td>\n\nEvent collection schedule \\(seconds\\)\n\n</td><td>\n\nFrequency, in seconds, that the system checks for new events from NNMi. The default value is 120 seconds.\n\n</td></tr><tr><td>\n\nLast error message\n\n</td><td>\n\nLast error message. Automatically updated.\n\n</td></tr></tbody>\n</table>4.  Right-click the form header and select **Save**.\n\n    The connector instance values are added to the form and the parameters that are relevant to the connector appear. \\[Omitted image \"nnmi-connector-values.png\"\\] Alt text: NNMi Connector Instance Values\n\n5.  In the Connector Instance Values section, verify and where required, modify the default connector instance values.\n\n<table id=\"table_qjb_lzx_fdb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\ndays\\_from\n\n</td><td>\n\nNumber of days for which events must be collected at the first collection cycle. Default value: `7` 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.\n\n</td></tr><tr><td>\n\ndebug\n\n</td><td>\n\nDisplay debug messages. Default value: `false`. Specify `true` to see debug messages.\n\n</td></tr><tr><td>\n\nport\n\n</td><td>\n\nNumber of the connector port. Default value: `80`.\n\n</td></tr><tr><td>\n\nprotocol\n\n</td><td>\n\nType of protocol. Default protocol type: `http`.\n\n</td></tr></tbody>\n</table>6.  In the MID Servers for Connectors section, specify a MID Server that is up and is valid.\n\n    If no MID Server is specified, an available MID Server that has a matching IP range is used.\n\n    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.\n\n7.  Right-click the form header and select **Save**.\n\n8.  Test the connection between the MID Server and the NNMi connector.\n\n    1.  Click **Test Connector**.\n\n        If the test fails, follow the instructions that the error issues to correct the problem and then run another test.\n\n        **Note:** Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to the external monitoring tool.\n\n        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.\n\n    2.  After a successful test, select the **Active** check box.\n\n9.  Click **Update**.\n\n\n**Parent Topic:**[Configure a pull connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/t_EMConfigureConnectorInstance.md)\n\n"}}