Pelco IMES19 cameras cannot be classified during SNMP Discovery because they return a generic OIDIssue .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Pelco IMES19 mini-dome cameras respond to SNMP queries, but Discovery cannot reliably classify them as Pelco IMES19 devices. Symptoms .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } The camera responds during SNMP Discovery but is not classified as the intended device type.The camera returns 1.3.6.1.4.1.8072.3.2.10 as its sysObjectID.An attempt to add the returned OID to an SNMP OID Classification record is blocked by the out-of-box Prevent Generic OID business rule.A custom SNMP Classification cannot reliably identify the device as a Pelco IMES19 camera. Facts .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } Pelco's Private Enterprise Number base OID is 1.3.6.1.4.1.25066.The camera reports 1.3.6.1.4.1.8072.3.2.10, which is a generic Net-SNMP Linux agent OID.The reported OID does not uniquely identify the manufacturer, model, or device type.Multiple unrelated devices can return the same generic OID.The failure occurs during SNMP classification and device identification, before a Discovery Pattern can process the device as the intended class. Release All Releases Cause .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul, .kb-wrapper ol { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 6px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } The Pelco IMES19 firmware reports the generic Net-SNMP Linux agent sysObjectID instead of a Pelco-specific enterprise OID. The out-of-box Prevent Generic OID business rule prevents this shared OID from being assigned to a specific manufacturer, model, or CI class. Assigning it to the Pelco IMES19 could cause unrelated Net-SNMP devices to be classified incorrectly. Resolution .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 10px 0; } .kb-wrapper code { background: #e6f0f5; color: #032D42; border: 1px solid #b8cfd8; padding: 1px 4px; border-radius: 3px; font-family: Consolas, monospace; } .kb-wrapper .kb-warning { border-left: 4px solid #e6a817; background: #fff4e0; padding: 10px 12px; margin: 0 0 12px 0; } Contact Pelco: Ask Pelco whether updated firmware or an SNMP configuration option can return a Pelco-specific sysObjectID.SNMP Discovery limitation: If the device can return only the generic OID 1.3.6.1.4.1.8072.3.2.10, the device cannot be supported with SNMP Discovery.Consider a custom IntegrationHub ETL integration: You may be able to connect directly to the Pelco VideoXpert REST API or a central video management system (VMS) controller and use IntegrationHub ETL (IH-ETL) to map the source payload into the CMDB through the Identification and Reconciliation Engine (IRE). Contact Pelco for information about its API and supported VMS controllers.Consider Service Graph Connector for Cisco Cyber Vision: Other customers have successfully populated camera and other Internet of Things (IoT) device data by using Service Graph Connector for Cisco Cyber Vision, available from the ServiceNow Store. Warning: Do not disable or bypass the Prevent Generic OID business rule to map 1.3.6.1.4.1.8072.3.2.10 to the Pelco IMES19 model. Doing so can cause unrelated Net-SNMP devices to be classified incorrectly. Related Links .kb-wrapper { max-width: 100%; font-family: Lato, sans-serif; font-size: 12pt; line-height: 1.7; color: #000000; } .kb-wrapper p { margin: 0 0 12px 0; } .kb-wrapper ul { margin: 0 0 12px 24px; padding: 0; } .kb-wrapper li { margin: 0 0 8px 0; } .kb-wrapper a { color: #032D42; text-decoration: underline; } .kb-wrapper .kb-disclaimer { font-size: 10pt; font-style: italic; margin: 2px 0 12px 0; } Create a Discovery CI classificationIntegrationHub ETLGetting started with Service Graph ConnectorsService Graph Connector for Cisco Cyber VisionIoT device Discovery This link points to a ServiceNow Community article. Community content is not official ServiceNow documentation and may be updated or removed without notice.