Skip to main content

NEC Univerge

NEC Univerge

Plugin: go.d.plugin Module: snmp

Maintained by Netdata

Overview​

Monitor NEC Univerge (network device) with Netdata over SNMP. Netdata recognizes the device automatically by its sysObjectID (recognized across 2 device identifiers) and collects the metrics this profile declares — on top of the generic SNMP baseline — with no manual OID configuration.

Netdata's SNMP collector matches the device to the nec-univerge.yaml profile via sysObjectID/sysDescr, then polls the OIDs it declares.

This integration is supported on all platforms.

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

Default Behavior​

Auto-Detection​

Auto-detected as NEC Univerge via sysObjectID/sysDescr.

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 collector in two ways:

MethodBest forHow to
UIFast setup without editing filesGo to Nodes → Configure this node → Collectors → Jobs, search for snmp, 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 collector from the Netdata web interface:

  1. Go to Nodes.
  2. Select the node where you want the snmp 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 (or scroll the list) to locate the snmp collector.
  5. Click the + next to the snmp 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​

On top of the generic SNMP baseline (the Generic SNMP Device integration — interfaces, system, IP/TCP/UDP, host resources), this NEC Univerge profile adds the metrics below. Each is collected only where the device exposes the matching OID — inclusion means the profile requests it; availability depends on the device model and software.

47 metrics in 7 groups; each row is a chart context usable in alerts.

GroupMetrics
Hardware / Sensor1
Hardware / Temperature2
Network / Interface4
Network / VPN37
System / CPU1
System / Memory1
System / Uptime1

Hardware / Sensor​

Metric (chart context)UnitScopeDescription
snmp.device_prof_nec_picoVoltagemVdeviceIndicates the observed voltage

Hardware / Temperature​

Metric (chart context)UnitScopeDescription
snmp.device_prof_nec_picoCelsiusCeldeviceIndicates the temperature of the equipment inside
snmp.device_prof_nec_picoFahrenheitdegFdeviceIndicates the temperature of the equipment inside

Network / Interface​

Metric (chart context)UnitScopeDescription
snmp.device_prof_ifAdminStatus{status}per interface, interfaceCurrent administrative state of the interface
snmp.device_prof_ifHighSpeedbit/sper interface, interfaceEstimate of the interface's current bandwidth
snmp.device_prof_ifNumber{interface}deviceNumber of network interfaces regardless of their current state present on this system
snmp.device_prof_ifOperStatus{status}per interface, interfaceCurrent operational state of the interface

Network / VPN​

Metric (chart context)UnitScopeDescription
snmp.device_prof_nec_pikeGlobalActiveTunnels{tunnel}deviceCurrently active IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalAuthFails{failure}/sdeviceAuthentications which ended in failure by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalDecryptFails{failure}/sdeviceDecryptions which ended in failure by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalHashValidFails{failure}/sdeviceHash validations which ended in failure by IPsec Phase-1 Tunnels
snmp.device_prof_nec_pikeGlobalInNotifys{notification}/sdeviceNotifys received by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalInP1SaDelRequests{request}/sdeviceISAKMP security association delete requests received by IPsec Phase-1 Tunnels
snmp.device_prof_nec_pikeGlobalInP2ExchgInvalids{exchange}/sdeviceIPsec Phase-2 exchanges which were received and found to be contain references to unrecognized security parameters
snmp.device_prof_nec_pikeGlobalInP2ExchgRejects{exchange}/sdeviceIPsec Phase-2 exchanges which were received and validated but were rejected by the local policy
snmp.device_prof_nec_pikeGlobalInP2Exchgs{exchange}/sdeviceIPsec Phase-2 exchanges received by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalInP2SaDelRequests{request}/sdeviceIPsec Phase-2 security association delete requests received by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalInitTunnelFails{tunnel}/sdeviceIPsec Phase-1 IKE Tunnels which were locally initiated and failed to activate
snmp.device_prof_nec_pikeGlobalInitTunnels{tunnel}deviceIPSec Phase-1 IKE Tunnels which were locally initiated
snmp.device_prof_nec_pikeGlobalOutNotifys{notification}/sdeviceNotifys sent by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalOutP1SaDelRequests{request}/sdeviceISAKMP security association delete requests sent by IPsec Phase-1 Tunnels
snmp.device_prof_nec_pikeGlobalOutP2ExchgInvalids{exchange}/sdeviceIPsec Phase-2 exchanges which were sent and were flagged by the peer to contain references to unrecognized security parameters
snmp.device_prof_nec_pikeGlobalOutP2ExchgRejects{exchange}/sdeviceIPsec Phase-2 exchanges which were sent, validated by the peer but were rejected by the peers policy
snmp.device_prof_nec_pikeGlobalOutP2Exchgs{exchange}/sdeviceIPsec Phase-2 exchanges which were sent by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalOutP2SaDelRequests{request}/sdeviceIPsec Phase-2 SA delete requests sent by IPsec Phase-1 IKE Tunnels
snmp.device_prof_nec_pikeGlobalRespTunnelFails{tunnel}/sdeviceIPsec Phase-1 IKE Tunnels which were remotely initiated and failed to activate
snmp.device_prof_nec_pikeGlobalRespTunnels{tunnel}/sdeviceIPsec Phase-1 IKE Tunnels hich were remotely initiated
snmp.device_prof_nec_pipSecGlobalActiveTunnels{tunnel}deviceCurrently active IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInAuthFails{failure}/sdeviceInbound authentication which ended in failure by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInAuths{authentication}/sdeviceInbound authentications performed by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInDecryptFails{failure}/sdeviceInbound decryptions which ended in failure by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInDecrypts{decryption}/sdeviceInbound decryptions performed by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInDrops{packet}/sdevicePackets dropped during receive processing by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInOctetsBy/sdeviceData received by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInPkts{packet}/sdevicePackets received by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalInReplayDrops{packet}/sdevicePackets dropped during receive processing due to Anti-Replay processing by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalNoSaFails{failure}/sdeviceNon-existent SA in failures which occurred during processing by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutAuthFails{failure}/sdeviceOutbound authentication's which ended in failure by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutAuths{authentication}/sdeviceOutbound authentications performed by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutDrops{packet}/sdevicePackets dropped during send processing by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutEncryptFails{failure}/sdeviceOutbound encryptions which ended in failure by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutEncrypts{encryption}/sdeviceOutbound encryptions performed by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutOctetsBy/sdeviceData sent by IPsec Phase-2 Tunnels
snmp.device_prof_nec_pipSecGlobalOutPkts{packet}/sdevicePackets sent by IPsec Phase-2 Tunnels

System / CPU​

Metric (chart context)UnitScopeDescription
snmp.device_prof_cpu_usage%deviceThe current CPU utilization

System / Memory​

Metric (chart context)UnitScopeDescription
snmp.device_prof_memory_usage%deviceMemory usage percentage

System / Uptime​

Metric (chart context)UnitScopeDescription
snmp.device_prof_systemUptimesdeviceTime since the system was last rebooted or powered on.

Troubleshooting​

Other Problems​

Collect Diagnostics for Netdata Support​

For SNMP metrics, BGP, licensing, or topology issues, follow Collect SNMP troubleshooting data to include built-in diagnostics in a support bundle. SNMP evidence is unsanitized; share the bundle through a restricted Netdata Support ticket.


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