Graphing DHCP pools

project722 project722 at gmail.com
Thu Dec 21 18:50:51 UTC 2017


@David Rampage - I am still wrestling with that error when poling
externally. Here is my dhcpd-snmp.conf file structure, as you requested.

# Configuration file for dhcpd-snmp

# Path to the dhcpd.leases file.
#
# leases: /var/lib/dhcp3/dhcpd.leases

leases: /var/lib/dhcpd/dhcpd.leases

# Definition of the pools
#
# pool: number, description, from-to, from-to, from-to...

pool: 1, "Market 1", 192.168.100.100 192.168.100.254 192.168.101.100
192.168.101.254

pool: 2, "Market 2", 192.168.200.100 192.168.200.254 192.168.201.100
192.168.201.254

pool: 3, "Market 3", 192.168.202.100 192.168.202.254 192.168.203.100
192.168.203.254


Just to recap, I can run the dhcpd-snmp script locally, and it works. But
if I try an smnpwalk from a remote device, I get the following error:

#snmpwalk -v 2c <host> -c public .1.3.6.1.4.1.21695.1.2
SNMPv2-SMI::enterprises.21695.1.2 = No more variables left in this MIB View
(It is past the end of the MIB tree)

Do I need to place some dhcpd-snmp specific MIB's somewhere on the server?


On Thu, Dec 7, 2017 at 3:34 PM, Simon Hobson <dhcp1 at thehobsons.co.uk> wrote:

> project722 <project722 at gmail.com> wrote:
>
> > I'm going to look into Cacti, as we will probably not deem this high
> enough on the priority list to purchase Solarwinds. But, for the moment, I
> have setup dhcpd-snmp on my DHCP server.
>
> Just a thought ...
> Cacti doesn't HAVE to use SNMP, you can supply your own data externally.
> So you could use any means of extracting the pool status and insert that
> into RRD files, and let Cacti handle the graphing. Obviously it starts
> getting more complicated if the DHCP and Cacti servers are on different
> hosts.
>
> _______________________________________________
> dhcp-users mailing list
> dhcp-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/dhcp-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/dhcp-users/attachments/20171221/51500f01/attachment.html>


More information about the dhcp-users mailing list