Monitor Cisco 2811 DHCP Pool

Hello Andy,
we appreciate your contact.

Was SNMP already enabled on the 2811? Do other SNMP-based sensors work?

While there's no built-in sensor for this it may be possible using a custom SNMP sensor. First of all we need to have a look at the SNMP results provided by your device, for this we'll need you to download our latest SNMP Tester, run it on the PRTG Host (or host of the Remote Probe), and perform an "Walk" test against the target device providing the "1.3.6.1.4.1.9.10.102" OID (without quotes) as parameter. Kindly configure the Device's IP/Port and SNMP Credentials accordingly.

The test could take several minutes to run and will become unresponsive during the query, this is normal. Please share us the resulting logfile from the Tester.

Best Regards,
Luciano Lingnau [Paessler Support]

I ran the test as you instructed, but wanted to add that currently I have the 2811 configured and displaying information just fine. The test results are as followed:

----------------------- New Test -----------------------
Paessler SNMP Tester 5.2.3 Computername: AD Interface: 192.168.3.201
11/9/2017 10:12:59 AM (3 ms) : Device: 192.168.3.1
11/9/2017 10:12:59 AM (4 ms) : SNMP V2c
11/9/2017 10:12:59 AM (6 ms) : Custom OID 1.3.6.1.4.1.9.10.102
11/9/2017 10:12:59 AM (25 ms) : SNMP Datatype: SNMP_EXCEPTION_NOSUCHOBJECT
11/9/2017 10:12:59 AM (31 ms) : -------
11/9/2017 10:12:59 AM (33 ms) : Value: No such object (SNMP error # 222)
11/9/2017 10:12:59 AM (36 ms) : Done

Hello Andy,
thank you for your reply.

It appears as if you ran a "Custom OID" test, please switch to the "Walk" option, enter the 1.3.6.1.4.1.9.10.102 OID and try again. Please let me know how it goes.

Best Regards,
Luciano Lingnau [Paessler Support]

Paessler SNMP Tester 5.2.3 Computername: AD Interface: 192.168.3.201
11/10/2017 11:27:19 AM (7 ms) : Device: 192.168.3.1
11/10/2017 11:27:19 AM (11 ms) : SNMP V2c
11/10/2017 11:27:19 AM (17 ms) : Walk 1.3.6.1.4.1.9.10.102

Hello there,
thank you for your reply.

If there was no reply your device doesn't implement the CISCO-IETF-DHCP-SERVER-MIB. In that case you won't be able to monitor the DHCP usage unless you locate an alternative MIB that is compatible with your device and reports this information.

You could also contact Cisco's support and inquiry about the SNMP MIB/OID's that can be polled for the DHCP Counters/Usage.

Best Regards,
Luciano Lingnau [Paessler Support]

I realize that this thread is 5 years old. But I am looking for information on how to do similar monitoring of DHCP on my Cisco switches. I ran the "walk" test against my switch and received results.

----------------------- New Test -----------------------
Paessler SNMP Tester - 20.2.4 Computername: ACCPRTG Interface: (xxx.xxx.xxx.xxx)
9/13/2022 1:47:04 PM (1 ms) : Device: xxx.xxx.xxx.xxx
9/13/2022 1:47:04 PM (3 ms) : SNMP v2c
9/13/2022 1:47:04 PM (5 ms) : Walk 1.3.6.1.4.1.9.10.102
9/13/2022 1:47:04 PM (15 ms) : 1.3.6.1.4.1.9.10.102.1.1.1.0 = "16.12.3a" [ASN_OCTET_STR]
9/13/2022 1:47:04 PM (21 ms) : 1.3.6.1.4.1.9.10.102.1.1.2.0 = "1.3.6.1.4.1.9.10.102.1.1" [ASN_OBJECT_ID]
9/13/2022 1:47:04 PM (26 ms) : 1.3.6.1.4.1.9.10.102.1.4.2.1.2.10.1.91.0 = "24" [ASN_UNSIGNED]
9/13/2022 1:47:04 PM (31 ms) : 1.3.6.1.4.1.9.10.102.1.4.2.1.3.10.1.91.0 = "Wireless" [ASN_OCTET_STR]
9/13/2022 1:47:04 PM (38 ms) : 1.3.6.1.4.1.9.10.102.1.4.2.1.4.10.1.91.0 = "254" [ASN_UNSIGNED]
9/13/2022 1:47:04 PM (43 ms) : 1.3.6.1.4.1.9.10.102.1.4.2.1.5.10.1.91.0 = "0" [ASN_UNSIGNED]
9/13/2022 1:47:04 PM (49 ms) : 1.3.6.1.4.1.9.10.102.1.4.2.1.6.10.1.91.0 = "244" [ASN_UNSIGNED]
9/13/2022 1:47:04 PM (55 ms) : 1.3.6.1.4.1.9.10.102.1.8.1.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (61 ms) : 1.3.6.1.4.1.9.10.102.1.8.2.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (67 ms) : 1.3.6.1.4.1.9.10.102.1.8.3.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (73 ms) : 1.3.6.1.4.1.9.10.102.1.8.4.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (80 ms) : 1.3.6.1.4.1.9.10.102.1.8.5.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (86 ms) : 1.3.6.1.4.1.9.10.102.1.9.1.0 = "2614" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (91 ms) : 1.3.6.1.4.1.9.10.102.1.9.2.0 = "2558" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (97 ms) : 1.3.6.1.4.1.9.10.102.1.9.3.0 = "76293" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (103 ms) : 1.3.6.1.4.1.9.10.102.1.9.4.0 = "3" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (108 ms) : 1.3.6.1.4.1.9.10.102.1.9.5.0 = "74899" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (113 ms) : 1.3.6.1.4.1.9.10.102.1.9.6.0 = "3" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (119 ms) : 1.3.6.1.4.1.9.10.102.1.9.7.0 = "1124" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (125 ms) : 1.3.6.1.4.1.9.10.102.1.9.8.0 = "175" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (131 ms) : 1.3.6.1.4.1.9.10.102.1.9.9.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (137 ms) : 1.3.6.1.4.1.9.10.102.1.9.10.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (144 ms) : 1.3.6.1.4.1.9.10.102.1.9.11.0 = "0" [ASN_COUNTER64]
9/13/2022 1:47:04 PM (150 ms) : 1.3.6.1.4.1.9.10.102.1.9.12.0 = "0" [ASN_COUNTER64]

Hi Tom,

Thank you for your message.

Your device provides data for the OID "" related to DHCP and BOOTP information, that's a good thing. Now, I invite you to have a look at the following documentation (OID) which contains children OIDs that could provide the information you would like to monitor:

cDhcpv4HCCounters:https://oidref.com/1.3.6.1.4.1.9.10.102.1.9

For example, to monitor the number of DHCP Discovers and offers you need to use the OIDs below (visible in the SNMP result you provided):

- Discovers: 1.3.6.1.4.1.9.10.102.1.9.1.0
- Offers: 1.3.6.1.4.1.9.10.102.1.9.2.0

When you have find the information you are looking for, I invite you to add a SNMP Custom Advanced sensor and create a channel (up to 10) for each of them.

If you have questions, do not hesitate.

Regards.