Forge Home


SNMP agent management


3,455 latest version

5.0 quality score

We run a couple of automated
scans to help you access a
module's quality. Each module is
given a score based on how well
the author has formatted their
code and documentation and
modules are also checked for
malware using VirusTotal.

Please note, the information below
is for guidance only and neither of
these methods should be considered
an endorsement by Puppet.

Version information

  • 0.2.6 (latest)
released Apr 2nd 2020
This version is compatible with:
  • Puppet Enterprise 2023.7.x, 2023.6.x, 2023.5.x, 2023.4.x, 2023.3.x, 2023.2.x, 2023.1.x, 2023.0.x, 2021.7.x, 2021.6.x, 2021.5.x, 2021.4.x, 2021.3.x, 2021.2.x, 2021.1.x, 2021.0.x, 2019.8.x, 2019.7.x, 2019.5.x, 2019.4.x, 2019.3.x, 2019.2.x, 2019.1.x, 2019.0.x, 2018.1.x, 2017.3.x, 2017.2.x, 2017.1.x, 2016.5.x, 2016.4.x
  • Puppet >= 3.8.0
  • , , , , ,

Start using this module

  • r10k or Code Manager
  • Bolt
  • Manual installation
  • Direct download

Add this module to your Puppetfile:

mod 'eyp-snmpd', '0.2.6'
Learn more about managing modules with a Puppetfile

Add this module to your Bolt project:

bolt module add eyp-snmpd
Learn more about using this module with an existing project

Manually install this module globally with Puppet module tool:

puppet module install eyp-snmpd --version 0.2.6

Direct download is not typically how you would use a Puppet module to manage your infrastructure, but you may want to download the module in order to inspect the code.



eyp/snmpd — version 0.2.6 Apr 2nd 2020


Table of Contents

  1. Overview
  2. Module Description
  3. Setup
  4. Usage
  5. Reference
  6. Limitations
  7. Development


SNMP agent management

Module Description

snmpd management: SNMP v1 and v2c ACL management and SNMPv3 user creation.

Support for:

  • disk monitoring
  • load average monitoring


What snmpd affects

  • snmpd package
  • snmpd service

Setup Requirements

Beginning with snmpd

Install snmpd:

class { 'snmpd': }


disable snmpd

class { 'snmpd':
  service_ensure => 'stopped',
  service_enable => false,

purge snmpd

class { 'snmpd':
  package_ensure => 'purged',
  manage_service => false,

SNMP v1 and v2c ACL

class { 'snmpd':
  add_default_acls => false,

snmpd::acl { 'demo':
  community => '1234567890',

SNMPv3 user creation

class { 'snmpd':
  add_default_acls => false,

snmpd::v3user { 'v3testuser':
  authpass => '1234567890',
  encpass  => '1234567890',

This setup can be tested vis snmpwalk:

# snmpwalk -v3  -l authPriv -u v3testuser -a SHA -A "1234567890"  -x AES -X "1234567890" system



  • basic operations:
    • manage_package = true,
    • package_ensure = 'installed',
    • manage_service = true,
    • manage_docker_service = true,
    • service_ensure = 'running',
    • service_enable = true,



Relies on fact ::eyp_snmpd_mountpoints for autoconfiguring disk monitoring if snmpd::add_disk_monit is set to true (default is true)


It is asumed that /usr/bin/net-snmp-create-v3-user is a bash script that this module modifies for it's own purposes. The modified script is stored on /usr/local/bin/puppet_net-snmp-create-v3-user


Mostly tested on CentOS 7 and Ubuntu 16.04


We are pushing to have acceptance testing in place, so any new feature should have some test to check both presence and absence of any feature


TODO list


  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Added some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request