If your device is not showing up as expected in 3manager, it can often be due to a few common reasons. This guide will help you troubleshoot the most frequent scenarios and get your printer monitoring up and running.
1. Device Already Discovered but Not Monitored
In many cases, the device is discovered, but currently set as unmonitored.
What to do:
From the equipment dashboard click filter in upper right corner, add the filter "Monitored" and choose "No". Then click "Filter". This will return a list of devices which are marked as unmonitored.
If you have the serial number of the device of interest, this will be optimal to use as filter. In some cases IP might have changed since unmonitoring so its not recommended to use that as unique search criteria.
Or...
Go to: Account Settings → Device Monitoring If you see the device on the right side (unmonitored), click “Monitor”.
This will move the device to the monitored list, and the next time the data collector updates, it will fetch counters, supply levels, etc.
2. IP Address Not in the Configured IP Range
If the device is not appearing at all, the IP range configuration might be missing or incorrect.
What to do:
Check your IP range settings in the data collector configuration. If no ranges are added, only the local subnet is scanned. Many printers are located in other subnets, so be sure to include the full network range you want scanned.
3. Incorrect SNMP Community String
Your device might be using a different SNMP community string.
What to do:
Default SNMP string is usually “public”. If this has been changed, you must add the correct SNMP string(s) in the data collector settings.
You can add multiple SNMP strings, separated by commas. E.g. public,printer123,snmpv1
4. SNMP Disabled on the Device
If SNMP is turned off on the printer, it will be invisible to the data collector.
What to do:
Log in to the printer’s web interface. Make sure SNMP is enabled (preferably SNMP v1 or v2 for easiest compatibility).
5. Device Uses SNMP v3
If the printer uses SNMP v3, specific credentials are needed.
What to do:
Go to the data collector configuration. Add the SNMP v3 credentials under the SNMP v3 section.
6. Port 161 Blocked
SNMP communication uses port 161. If this port is closed, the printer can’t be reached.
What to do:
Ensure port 161 is open between the data collector and the printer. You may need to involve your network/IT team.
Quick Summary:
| Issue | Likely Symptom | Solution |
|---|---|---|
| Device not monitored | Appears in device list, but no data | Filter with Monitored = No and click Monitor |
| IP range misconfigured | Device not found at all | Add correct IP range to data collector settings |
| SNMP string incorrect | Device not discovered or shown as offline | Add correct SNMP strings to configuration |
| SNMP disabled on device | Device not found | Enable SNMP on the printer |
| Using SNMP v3 | Device not found | Add SNMP v3 credentials to data collector |
| Port 161 closed | Device not found | Ensure port 161 is open |
Comments
0 comments
Article is closed for comments.