4 Step ServiceNow Discovery for Axis IP Cameras Using SNMP
Out of the box, ServiceNow Discovery may not correctly identify or fully populate details for network cameras such as Axis IP cameras.
With a few adjustments, you can build a custom classifier and custom pattern that leverage SNMP to detect these devices and populate attributes like model, manufacturer, serial number, and device name.
This guide walks you through the process in three phases:
-
Prerequisites
-
Classifier creation
-
Pattern creation
1. Prerequisites
Before creating a classifier or pattern:
-
Ensure SNMP is functional
Run an snmpwalk from the MID Server host to the camera on port 161 to verify access. -
Collect required OIDs
Identify the exact SNMP OIDs for:-
Model → (already confirmed working)
-
Manufacturer → (already confirmed working)
-
Serial Number → Often 1.3.6.1.2.1.47.1.1.1.1.11 or Axis-specific enterprise OID
-
Device Name → Often sysName → 1.3.6.1.2.1.1.5.0
-
-
Optional: Download and import the Axis MIB files into the MID Server’s \agent\mibs directory. This can help with human-readable names in SNMP queries.
2. Create the Custom Classifier
Purpose: Tell Discovery “when this signature appears, it’s an Axis IP camera.”
-
Go to:
Discovery Definition → Classifiers -
Click New and fill in:
-
Name: Axis IP Camera
-
Type: SNMP
-
CI Type: cmdb_ci_ip_camer
-
Priority: 10 (lower number = higher priority)
-
-
Add Signature Conditions:
-
Condition 1: sysDescr contains "AXIS"
-
OR Condition 2: SNMP OID <modelOID> exists and value contains "AXIS"
-
-
Save the classifier.
3. Create the Custom Pattern
Purpose: Once classified, this pattern queries the correct OIDs and maps them to CMDB fields.
-
Go to:
Discovery Definition → Patterns -
Click New and fill in:
-
Name: Axis IP Camera Pattern
-
Type: SNMP
-
Applies to Class: cmdb_ci_ip_camera
-
-
In Pattern Designer:
-
Add a SNMP Query step:
-
Query OID: <serialNumberOID> → Map to serial_number
-
-
Add another SNMP Query step:
-
Query OID: <deviceNameOID> → Map to name
-
-
(Optional) Query OID: <modelOID> → Map to model_id.name
-
-
Click Test Pattern with an Axis camera IP to verify.
-
Save and publish.
4. Link Classifier to Pattern
-
In the Axis IP Camera Classifier, under Pattern, select Axis IP Camera Pattern so it triggers automatically during Discovery.
5. Example OID Mapping for Axis Cameras
| Attribute | Common OID |
|---|---|
| sysName | 1.3.6.1.2.1.1.5.0 |
| sysDescr | 1.3.6.1.2.1.1.1.0 |
| Model Name | 1.3.6.1.4.1.368.4.1.1.1.1.0 |
| Serial Number | 1.3.6.1.2.1.47.1.1.1.1.11.1 |
| Manufacturer | 1.3.6.1.2.1.1.1.0 or Axis enterprise OID |
6. Troubleshooting When Serial Number and Name OIDs Are Missing
Thanks to analysis of a sample SNMP payload from an Axis camera, here’s why you may not find serial number or device name OIDs:
From the sample payload:
-
sysName (1.3.6.1.2.1.1.5) exists but is empty.
-
sysDescr contains the model (AXIS M3046-V) and firmware info, but no serial number.
-
No ENTITY-MIB section is returned (which normally contains entPhysicalSerialNum).
-
The SNMP walk stops early, showing only the system group.
Why this happens
Axis cameras often require:
-
SNMP enabled in the web GUI (done by default in some models).
-
Extended SNMP access or Axis Enterprise MIB loaded — otherwise, only sysDescr, sysName, and sysObjectID are available.
-
SNMPv3 instead of v2c to retrieve hardware details like serial number.
How to find missing OIDs
From your MID Server or another SNMP client:
snmpwalk -v2c -c public <camera-ip> .1
or
snmpwalk -v3 -u <user> -l authNoPriv -a MD5 -A <pass> <camera-ip> .1
Look for:
-
entPhysicalSerialNum → .1.3.6.1.2.1.47.1.1.1.1.11
-
Axis-specific OIDs under .1.3.6.1.4.1.368
If still missing, download the Axis MIB from
https://www.axis.com/developer-community/mib-files, (CONTACT VENDOR FOR MIB)
place it in your MID Server’s /agent/mibs directory, restart the MID Server, and retry.
7. Workaround When SNMP Won’t Return Serial Number
If SNMP can’t provide the serial number:
-
Still create a custom classifier matching sysDescr containing "AXIS".
-
In your pattern, parse the sysDescr string to extract model.
-
Leave serial_number blank or fill it using an HTTP probe to the camera’s admin API.
Example HTTP GET request:
GET /axis-cgi/admin/param.cgi?action=list&group=Properties.System.SerialNumber
Sample response:
root.Properties.System.SerialNumber=ACCC8E123456
You can combine SNMP classifier + HTTP probe in one ServiceNow Discovery pattern to ensure serial_number and name are always populated.
If you find the article to be useful or effective for your knowledge Kindly Consider Marking the article HELPFUL and BOOKMARK if for your future use...
<<< Top Articles >>>
- ServiceNow Integration with Splunk
- LDAP Integration with ServiceNow
- ServiceNow Integration with Veeam
- Handling ServiceNow flow errors with a flow
- Show parent child incident relationships - display in field message
- ServiceNow SSO Logout Error (redirects to logout page) – Reason, Fixes and Cause.
- Multi Row Variable set ServiceNow MRVS - Creating - Scripting - Example - Limits
- ServiceNow Integration with MAC vendor - Get Mac vendor for the given MAC Address.
- How to find Log4j vulnerable severs in ServiceNow Using CMDB Query Builder (SecOps)
- How to Cancel a Long-Running Transaction ServiceNow
- Hidden Features for System Administrators
- Servicenow RPA - Understanding Attended / Unattended / Skilled Automation Bots
MF Sohail Khilji | ServiceNow Developer / Consultant.
Connect On LinkedIn > https://www.linkedin.com/in/mf-sohail-khilji/
2 Comments
