Skip to main content

Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd SNMP Traps

Plugin: go.d.plugin Module: snmp_traps

Overview​

Receive, decode, and store SNMP traps and INFORMs from Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd devices with Netdata. The bundled Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd trap profile decodes 440 trap definitions across 74 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 Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd enterprise OID space, and decodes the varbinds using the bundled Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd 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 Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd 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 440 trap definitions from Ruijie Networks Co Ltd Formerly Start Network Technology Co Ltd across 74 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 36 · crit 12 · err 9 · warning 171 · notice 205 · info 7

By category: state_change 181 · config_change 16 · security 50 · auth 10 · mobility 28 · diagnostic 154 · unknown 1

Coverage by MIB​

74 MIBs decoded — show per-MIB trap counts
MIBTrap definitions
RUIJIE-SYSTEM-MIB50
RUIJIE-WLAN-FIT-AP-CF-MIB48
RUIJIE-WLAN-FAT-AP-CF-MIB35
RAISECOM-RS485-CLASS-MIB20
RAISECOM-AC-MGMT-MIB19
RAISECOM-RRM-MIB19
RAISECOM-V1-TRAP17
RAISECOM-3G-MIB14
RUIJIE-INTERFACE-MIB14
RAISECOM-MPLSOAM-MIB12
RUIJIE-ENTITY-MIB11
RUIJIE-BGP4-MIB10
RUIJIE-MLAG-MIB10
RAISECOM-CM-WAPI-MIB9
RAISECOM-DOT11-WIDS-MIB9
RUIJIE-CAPWAP-APP-MIB8
RUIJIE-FIBER-MIB8
RAISECOM-4G-MIB6
RAISECOM-AAA-MIB6
RAISECOM-AUTH-GATEWAY-MIB6
RAISECOM-WLAN-WLOG-MIB5
RUIJIE-ROUTE-MIB5
RAISECOM-CLUSTER-MIB4
RAISECOM-EGHA-MIB4
RAISECOM-LTE-MIB4
RAISECOM-VSU-MIB4
RUIJIE-RS485-CLASS-MIB4
RUIJIE-VXLAN-MIB4
MY-SYSTEM-MIB3
RAISECOM-CAPWAP-DHCP-MIB3
RAISECOM-TEMP-FAN-MIB3
RAISECOM-WLAN-FIT-AP-IN-MIB3
RUIJIE-POE-MIB3
MY-ENTITY-MIB2
MY-SMP-MIB2
RAISECOM-BFD-MIB2
RAISECOM-CM-PORTAL-MIB2
RAISECOM-IPSEC2-MIB2
RAISECOM-L2TP-MIB2
RAISECOM-L2TPV2-MIB2
RAISECOM-MIB-MIB2
RAISECOM-SMM-MIB2
RAISECOM-VPLS-GENERIC-MIB2
RUIJIE-CPP-MIB2
RUIJIE-IPSEC-MIB2
RUIJIE-MSTP-MIB2
RUIJIE-NTP-MIB2
RUIJIE-RLDP-MIB2
RUIJIE-UPGRADE-MIB2
RUIJIE-VSU-MIB2
RUIJIE-VXU-MIB2
RUIJIE-WAN-FPM-MIB2
MY-ADDRESS-MIB1
MY-INTERFACE-MIB1
MY-SECURITY-MIB1
RAISECOM-CAPWAP-MOBILITY-MIB1
RAISECOM-DHCP-SNOOPING-MIB1
RAISECOM-FILE-MIB1
RAISECOM-IGMP-MIB1
RAISECOM-IP-PRIVATE-MIB1
RAISECOM-PIM-MIB1
RAISECOM-SECZONE-MIB1
RAISECOM-TRAFFIC-CTRL-MIB1
RAISECOM-URPF-MIB1
RAISECOM-VM-MIB1
RAISECOM-WLAN-FAT-AP-IN-MIB1
RAISECOM-WLAN-HOTBACKUP-MIB1
RAISECOM-WLAN-SECURITY-MIB1
RUIJIE-CAPWAP-DHCP-MIB1
RUIJIE-DVMRPINTEROPERABILITY-MIB1
RUIJIE-IP-PRIVATE-MIB1
RUIJIE-LINK-SLA-MIB1
RUIJIE-NFPP-MIB1
RUIJIE-RNS-MIB1

Sample decoded traps​

  • RAISECOM-V1-TRAP::sysHardChangeDetected
  • RAISECOM-V1-TRAP::portSecurityViolate
  • RAISECOM-V1-TRAP::stormViolationAlarm
  • RAISECOM-V1-TRAP::macNotification
  • RAISECOM-V1-TRAP::powerStateChange
Last updated on

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