Skip to main content

Adva AG Optical Networking SNMP Traps

Plugin: go.d.plugin Module: snmp_traps

Overview

Receive, decode, and store SNMP traps and INFORMs from Adva AG Optical Networking devices with Netdata. The bundled Adva AG Optical Networking trap profile decodes 1510 trap definitions across 24 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 Adva AG Optical Networking enterprise OID space, and decodes the varbinds using the bundled Adva AG Optical Networking 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 Adva AG Optical Networking 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 1510 trap definitions from Adva AG Optical Networking across 24 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: emerg 1 · alert 57 · crit 355 · err 23 · warning 724 · notice 317 · info 33

By category: state_change 320 · config_change 95 · security 46 · auth 11 · license 8 · diagnostic 1029 · unknown 1

Coverage by MIB

MIBTrap definitions
ADVA-FSPR7-MIB564
FspR7-MIB551
ADVA-FSP3000ALM-MIB111
METRO1500-MIB80
FSP150-MIB44
FspR7-LAYER2-MIB40
CM-PERFORMANCE-MIB24
FspR7-SPEQ-MIB21
F3-PTP-MIB14
ADVA-FSPR7-CFM-EXTENSION-MIB11
F3-L3-MIB11
CM-SYSTEM-MIB7
F3-FPM-MIB7
F3-SYNCJACK-MIB6
CM-ALARM-MIB4
F3-CONNECTGUARD-MIB4
CM-SA-MIB3
CM-SECURITY-MIB2
AOS-CORE-ALARM-MIB1
F3-EOMPLS-MIB1
F3-NTP-MIB1
F3-PWE3-MIB1
F3-TWAMP-MIB1
OSA-TWAMP-MIB1

Sample decoded traps

  • METRO1500-MIB::metro1500HardwareAdded
  • METRO1500-MIB::metro1500HardwareDeleted
  • METRO1500-MIB::metro1500PSNotFail
  • METRO1500-MIB::metro1500PSFail
  • METRO1500-MIB::metro1500FanNotFail

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