Skip to main content

Adtran SNMP Traps

Plugin: go.d.plugin Module: snmp_traps

Overview

Receive, decode, and store SNMP traps and INFORMs from Adtran devices with Netdata. The bundled Adtran trap profile decodes 1372 trap definitions across 87 MIBs into structured journal events with named, typed varbinds — searchable and filterable in the Logs tab.

Netdata's SNMP trap listener receives traps on UDP/162, matches them to the Adtran enterprise OID space, and decodes the varbinds using the bundled Adtran trap profile. No per-trap configuration.

This integration is supported on all platforms.

This integration supports multiple instances configured side-by-side.

Default Behavior

Auto-Detection

Traps from Adtran devices are decoded automatically once the device is pointed at the Agent's trap listener.

Limits

The default configuration for this integration does not impose any limits.

Performance Impact

The default configuration for this integration is not expected to impose a significant performance impact on the system.

Setup

You can configure the snmp_traps collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for snmp_traps, then click + to add a job.
FileIf you prefer configuring via file, or need to automate deployments (e.g., with Ansible)Edit go.d/snmp.conf and add a job.
important

UI configuration requires paid Netdata Cloud plan.

Prerequisites

SNMP access

SNMP must be enabled on the device and reachable from the Netdata Agent acting as the site's SNMP hub.

Configuration

Options

Configure the SNMP collector with the device hostname and SNMP credentials. See the SNMP collector reference for all options.

via UI

Configure the snmp_traps collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the snmp_traps data-collection job to run and click the (Configure this node). That node will run the data collection.
  3. The Collectors → Jobs view opens by default.
  4. In the Search box, type snmp_traps (or scroll the list) to locate the snmp_traps collector.
  5. Click the + next to the snmp_traps collector to add a new job.
  6. Fill in the job fields, then click Test to verify the configuration and Submit to save.
    • Test runs the job with the provided settings and shows whether data can be collected.
    • If it fails, an error message appears with details (for example, connection refused, timeout, or command execution errors), so you can adjust and retest.

via File

The configuration file name for this integration is go.d/snmp.conf.

The file format is YAML. Generally, the structure is:

update_every: 1
autodetection_retry: 0
jobs:
- name: some_name1
- name: some_name2

You can edit the configuration file using the edit-config script from the Netdata config directory.

cd /etc/netdata 2>/dev/null || cd /opt/netdata/etc/netdata
sudo ./edit-config go.d/snmp.conf
Examples

There are no configuration examples.

Alerts

There are no alerts configured by default for this integration.

Metrics

Netdata decodes 1372 trap definitions from Adtran across 87 MIBs into structured journal events. A trap is decoded only if the device actually sends it; inclusion here means the profile can decode it.

By severity: alert 43 · crit 85 · err 12 · warning 767 · notice 458 · info 7

By category: state_change 411 · config_change 14 · security 9 · auth 8 · diagnostic 930

Coverage by MIB

87 MIBs decoded — show per-MIB trap counts
MIBTrap definitions
ADTRAN-GENERIC-OTN-MIB110
ADTRAN-DSX1COMMON-TRAPS-MIB86
ADTRAN-SHDSL-MIB77
ADTRAN-GENTA8XX-MIB68
ADTRAN-ACTDAXL3-MIB66
ADTRAN-TACONTROLER-PRODUCT-MIB59
ADTRAN-GEN-ETH-IFC-MIB54
ADTRAN-GENGPON-MIB53
ADTRAN-EFMEXT-MIB52
ADTRAN-DSX1COMMON-MIB49
ADTRAN-TA5K-SM-MIB42
ADTRAN-EFM-MIB34
ADTRAN-GENERIC-IMA-MIB32
ADTRAN-ERPS-MIB31
ADTRAN-GENERIC-OPTICAL-ADD-DROP-MULTIPLEXER-MIB30
ADTRAN-GENVDSL2-LINE-MIB30
ADTRAN-ATLAS-T1-MIB28
ADTRAN-TA5K-DS3-PM-THRESHOLD-MIB28
ADTRAN-ATLAS-V35NX-MIB26
ADTRAN-GEN-OPTICAL-AMPLIFIER-MIB26
ADTRAN-HSU600-MIB26
ADTRAN-TA5K-SingleDS3-MIB20
ADTRAN-TAeSCUEXT1-MIB20
ADTRAN-TAMINIDSLAM3G-MIB16
ADTRAN-GENCHASSISTRAP-MIB15
ADTRAN-GENMEF-MIB14
ADTRAN-AOS-SFP-MIB13
ADTRAN-DSUDPP-MIB13
ADTRAN-TA5K-REDUNDANCY-MIB13
ADTRAN-PLUGGABLE-PORT-MIB12
ADTRAN-TA5K-TREE-NETWORKING-MIB12
ADTRAN-ATLAS-MODULE-MIB10
ADTRAN-GEN-ETHERNET-CFM-MIB10
ADTRAN-GENERIC-BRIDGE-MIB10
ADTRAN-GENERIC-PPP-MIB10
ADTRAN-GENMUXPONDER-MIB10
ADTRAN-5KSCM-MIB9
ADTRAN-AOS-3G8
ADTRAN-EFM-NTU-MIB8
ADTRAN-TA5K-POTS-MIB8
ADTRAN-TAESCUAUTOUPGRADE-MIB8
ADTRAN-GENERIC-PSEUDOWIRE-CEM-ALARM-MIB6
ADTRAN-GENPOLICER-MIB6
ADTRAN-GENSLOT-MIB6
ADTRAN-TA5000FAN-MIB6
ADTRAN-AOS-POWER5
ADTRAN-DSUIQ-MIB5
ADTRAN-GEN-SYSTEM-TIMING-MIB5
ADTRAN-GENPROCESSES-MIB5
ADTRAN-TSUIQ-MIB5
ADTRAN-ETHERNET-DSLAM-FLOW-MIB4
ADTRAN-GEN-FRAME-RELAY-MIB4
ADTRAN-GENUPGRADE-MIB4
ADTRAN-TA1100FSCM-MIB4
ADTRAN-TA5000-THERMAL-MGMT-MIB4
ADTRAN-TA5K-LINK-AGGREGATION-MIB4
ADTRAN-TAeSCU-MIB4
ADTRAN-AOS-NETWORK-SYNC-MIB3
ADTRAN-ACTDAX-MIB2
ADTRAN-AOS-NETWORKMONITOR2
ADTRAN-AOS-OVER-TEMP-PROTECTION-MIB2
ADTRAN-AOSCPU2
ADTRAN-ATLAS-550-MIB2
ADTRAN-ATLAS-HSSI-V35-MIB2
ADTRAN-ATLAS-UNIT-MIB2
ADTRAN-ATLASIQ-MIB2
ADTRAN-GEN-Y1731-MIB2
ADTRAN-GENAUTOCONFIG-MIB2
ADTRAN-GENERIC-LLDP-MIB2
ADTRAN-GENERIC-PACKET-TIMING-MIB2
ADTRAN-GENERIC-VECTORING-MIB2
ADTRAN-GENEZPROVISIONING-MIB2
ADTRAN-GENIF-MIB2
ADTRAN-GENMAC-MIB2
ADTRAN-GENMAX-ACCESSORY-MIB2
ADTRAN-AOS-DNS-MIB1
ADTRAN-AOS-DS1-EXT1
ADTRAN-AOS-DYING-GASP-MIB1
ADTRAN-AOS-FAN-MIB1
ADTRAN-AOS-PORT-SECURITY-MIB1
ADTRAN-AOS-SIP-PROXY-MIB1
ADTRAN-AOS-SIP-REGISTRATION1
ADTRAN-AOS-VQM1
ADTRAN-AOS-VRRP-MIB1
ADTRAN-GENSUBTENDEDHOST-MIB1
ADTRAN-TA5K-ATM-LM-MIB1
ADTRAN-TACONTROLER-PRODUCT2-MIB1

Sample decoded traps

  • ADTRAN-ACTDAX-MIB::ds1Alarm
  • ADTRAN-ACTDAX-MIB::ds1Alert
  • ADTRAN-DSUDPP-MIB::adDSUDPSelfTestPass
  • ADTRAN-DSUDPP-MIB::adDSUDPSelfTestFail
  • ADTRAN-DSUDPP-MIB::adDSUDPNetworkINS

Do you have any feedback for this page? If so, you can open a new issue on our netdata/learn repository.