What the SNMP Connector Solves
Many organizations face a common problem: their ServiceNow CMDB contains outdated, incomplete, or manually maintained network device records. Our solution keeps switches, routers, access points and firewalls configuration data (CI) current typically means custom scripting, spreadsheet imports, or expensive tooling. The SNMP Connector provides automated, scheduled discovery that keeps your CMDB accurate simply and without operational overhead.
Adding your SNMP network devices to your ServiceNow Instance improves your key ITSM processes (incident, problem, change) thanks to accurate and complete CMDB. Try it for free for 30 days on non-prod instances.
Device Coverage
The connector automatically maps each device discovered to the correct CMDB CI class using an OID classification engine. This covers almost 30 CI classes including:
- Switches, routers, and wireless access points
- Firewalls - Fortinet, Cisco, Juniper, and Palo Alto
- Load balancers - F5 BIG-IP, A10, Citrix NetScaler, Cisco ACE, and Radware
- Servers - Linux, storage, and specialized appliances
- UPS, PDUs, and out-of-band management devices
- Printers and other SNMP-enabled hardware
Target Audience
Ideal for IT Operations teams, Network Administrators, Infrastructure Engineers, and CMDB Administrators who manage SNMP enabled network infrastructure and need automated, scheduled CMDB population with full job visibility and audit trails. Particularly suited to organizations that have invested in ServiceNow ITSM standard edition or ITSM foundation and want to extend CMDB accuracy for their network devices.
Broad and expendable discovery
Beyond the device CI itself, the connector also populates switch ports and network interfaces (interface number, name, MAC address, and operational status), network adapters (name, IP address, netmask, and MAC address), and network neighbor details discovered via CDP and LLDP, giving your CMDB a complete picture of each device, not just its existence. Devices with no OID match are reported in the job completion summary with their system OIDs, so new entries can be added to the classification table at any time without an application upgrade.
Performance Considerations
The SNMP Connector is optimized for scalable network discovery. Discovery jobs execute sequentially per IP address via MID Server ECC queue communication, with a 45 second per-device timeout and early exit for fast-responding devices, minimizing total job duration for large IP sets. A single schedule supports up to 510 IP addresses (one /23 subnet) in this release. Staging records are processed by the Robust Transformer and out-of-the box ETL pipeline, which handles large device volumes efficiently without impacting operational CMDB performance. Every job produces a completion summary with discovered IP counts, failed IP counts, and ETL error counts, making it straightforward to debug network or credential issues from data quality issues.
Limitations
Each discovery schedule supports one MID Server. SNMP v1 is not supported; SNMP v2c and v3 only. Discovery targets must be reachable from the designated MID Server on UDP port 161. Neighbor discovery requires CDP or LLDP to be enabled on target devices. The connector is focused on SNMP enabled network infrastructure devices. This solution can be complemented by ASP Intune Connector Premium for end point discovery and by Azure CMDB connector for Azure resource discovery
Installation Instructions
Install the SNMP CMDB Connector Application from the ServiceNow Store. Use the Guided Setup module to configure the connection with network devices.
- Create the SNMP credentials used to authenticate to devices.
- Enable secure credential resolution by creating the integration user and configuring the MID Server credentials.
- Verify the OID classification table that maps devices to their CMDB classes.
- Create a discovery schedule and activate the discovery scheduler.
Prerequisites
- Requires only ITSM standard Edition Subscription or ITSM Foundation Subscription
- A MID Server that is Up and Validated in ServiceNow, with network access to the target devices over SNMP (UDP 161).
- Python 3.12 installed on the MID Server host and available on the System PATH.
- SNMP credentials for the target devices: a v2c community string, and/or a v3 user with authentication and privacy keys.
- File access to edit the MID Server config.xml on the host and restart the MID Server service
Contact and Support
- Support Hours of Operation: 5 am to 6 pm CET
- Support Days of Operation: Monday – Friday (except Belgian public holidays)
- Promised Call Response Time: Within 8 hours of receiving support request
- Promised Call Resolution Time: Within 5 business days of response
- Contact Method: email, customer support portal
- Contact Details:
- Phone: +32 2 895 46 00
- Email: supportdesk@asp.be
- Web: https://www.asp.be
Agentless SNMP network discovery: Discover switches, routers, firewalls, printers, UPS devices and more across IP lists, ranges, and subnets using a standard MID Server. Nothing to install on target devices, SNMP does the work.
Scheduled and on-demand discovery: Run discovery on recurring schedules or trigger it on demand, with SNMP v2c and v3 credential support and secure per-schedule credential binding.
Automatic CI classification across 29 CMDB classes: Each device's sysObjectID is matched against a curated OID reference table to assign the precise CI class, manufacturer, and model. Unmatched devices are held in staging and reported for review, your CMDB stays free of unclassified records.
Clean CMDB population through the CI identification engine (IRE): Devices, switch ports, and network adapters are created and updated via IntegrationHub ETL and the standard identification and reconciliation engine, following ServiceNow CMDB best practices for deduplicated, well-formed CI data.
Network topology insight: LLDP/CDP neighbor relationships are captured in a dedicated table, giving visibility into device-to-device adjacency across your network.
Full job lifecycle visibility: Every run tracks discovered, failed, and ETL-error counts per job, making coverage verification and troubleshooting straightforward.
Extensible without upgrades: Add new device models to the OID classification table at any time, no application update or code change needed.
Zero-touch MID Server maintenance: Discovery engine components are delivered and updated automatically through platform script file synchronization; no direct access to MID Server hosts is required.
Guided Setup included: A gated, step-by-step guided setup takes administrators from installation to your first discovery run in minutes.
Built entirely on standard platform capabilities: Runs on the ServiceNow platform you already own (MID Server, IntegrationHub ETL, IRE, and Flow Designer) making trustworthy network inventory fast to adopt and easy to govern.
SNMP CMDB Connector V1.0.0
Initial production release.
The SNMP CMDB Connector delivers agentless, MID Server based SNMP discovery of network devices into the ServiceNow CMDB.
New Features
- Scheduled and on-demand SNMP discovery across IP lists, ranges, and subnets
- SNMP v2c and v3 support with secure per-schedule credential binding
- Automatic CI classification across 29 CMDB CI classes via a curated sysObjectID reference table (8,300+ OIDs included), covering CI class, manufacturer, and model
- Native CMDB population through IntegrationHub ETL and the CI identification engine (IRE): devices, switch ports, and network adapters
- LLDP/CDP neighbor relationships captured in a dedicated application table
- Full job lifecycle tracking with per-run discovered, failed, and ETL-error counts; unmatched system OIDs reported on the job for easy onboarding of new device types
- OID classification table extensible at any time without an application upgrade
- Automatic MID Server component delivery via platform script file synchronization; no MID Server host access needed for upgrades
- Guided Setup covering installation through first discovery run
Limitations
- Each discovery schedule supports up to 510 IP addresses (one /23 subnet, or an equivalent list or range); larger targets should be split across multiple schedules
- Discovery is dispatched sequentially per IP; very large IP sets increase total run time
- Each device is allotted 45 seconds of discovery time, with a 15-second timeout per SNMP operation; if an individual operation times out, partial results for the device are still processed. Unreachable devices are skipped and counted as failed
- Devices whose sysObjectID has no match in the OID reference table remain in staging and are not promoted to the CMDB until a matching OID entry is added, after which the next run promotes them automatically
See the System Requirements and Other Requirements sections for prerequisites.
ServiceNow Instance
- ServiceNow release: Australia
- Admin role required for installation and Guided Setup
Plugin Dependencies
- Configuration Management (CMDB) - com.snc.cmdb: 1.1 or later
- System Import Sets - com.glide.system_import_set: 1.0.0 or later
- Integration Commons for CMDB - sn_cmdb_int_util: 2.22.0 or later
- CMDB CI Class Models - sn_cmdb_ci_class: 1.81.2 or later
- IntegrationHub ETL (sn_int_studio): 3.3.6 or later - optional (required only to view/ edit the ETL mappings; the connector runs without it)
Plugins Required for Guided Setup
- Guided Setup (sn_ads_setup)
- Guided Setup – Legacy (sn_guided_setup)
- Playbook Experience (sn_playbook_exp)
- Playbook Experience Components (now_playbook_exp)
- Process Automation Content (sn_pad_content)
MID Server
- One MID Server, status Up and Validated
- Windows Server host (64-bit)
- Python 3.12 installed on the MID Server host and available on the System PATH
- Standard MID Server hardware sizing per ServiceNow's MID Server system requirements; no additional capacity needed
Network Connectivity
- MID Server → target devices: UDP port 161 (SNMP) open
- MID Server → ServiceNow instance: standard outbound HTTPS (TCP 443)
- No inbound connections to the MID Server host are required
- SNMP v2c or v3 enabled on target network devices
- SNMP credentials (v2c community string, or v3 username with authentication/privacy passphrases) available for the devices to be discovered
- Network devices must be reachable from the MID Server on UDP port 161