Avaya Media Gateway
Plugin: go.d.plugin Module: snmp
Overview
Monitor Avaya Media Gateway (media gateway) 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 avaya-media-gateway.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 Avaya Media Gateway 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:
| Method | Best for | How to |
|---|---|---|
| UI | Fast setup without editing files | Go to Nodes → Configure this node → Collectors → Jobs, search for snmp, then click + to add a job. |
| File | If you prefer configuring via file, or need to automate deployments (e.g., with Ansible) | Edit go.d/snmp.conf and add a job. |
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:
- Go to Nodes.
- 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.
- The Collectors → Jobs view opens by default.
- In the Search box, type snmp (or scroll the list) to locate the snmp collector.
- Click the + next to the snmp collector to add a new job.
- 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 Avaya Media Gateway 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.
39 metrics in 9 groups; each row is a chart context usable in alerts.
| Group | Metrics |
|---|---|
| Hardware / FRU | 2 |
| Hardware / Sensor | 2 |
| Network / Interface | 4 |
| Network / Routing | 10 |
| System / CPU | 1 |
| System / Memory | 5 |
| System / Uptime | 1 |
| Voice / H248 | 3 |
| Voice / VoIPEngine | 11 |
Hardware / FRU
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_avaya_avEntPhyChFruFault | {status} | per avaya_ent_physical_index | Description of FRU fault |
snmp.device_prof_avaya_avEntPhyChFruOperStat | {status} | per avaya_ent_physical_index | Operational status of the chassis FRU unit |
Hardware / Sensor
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_entPhySensorOperStatus | {status} | per sensor_index, rm:sensor_type, rm:sensor_scale, rm:sensor_precision | Operational status of the sensor |
snmp.device_prof_entPhySensorValue | 1 | per sensor_index, rm:sensor_type, rm:sensor_scale, rm:sensor_precision | Most recent measurement obtained by the agent for this sensor |
Network / Interface
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_ifAdminStatus | {status} | per interface, interface | Current administrative state of the interface |
snmp.device_prof_ifHighSpeed | bit/s | per interface, interface | Estimate of the interface's current bandwidth |
snmp.device_prof_ifNumber | {interface} | device | Number of network interfaces regardless of their current state present on this system |
snmp.device_prof_ifOperStatus | {status} | per interface, interface | Current operational state of the interface |
Network / Routing
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_ospfIfLsaCount | {advertisement}/s | per ospf_ip_addr, neighbor_id | The total number of link-local link state advertisements in this interface's link-local link state database |
snmp.device_prof_ospfIfState | {status} | per ospf_ip_addr, neighbor_id | The OSPF Interface State |
snmp.device_prof_ospfNbrEvents | {event}/s | per neighbor_id, neighbor_ip | The number of times this neighbor relationship has changed state or an error has occurred |
snmp.device_prof_ospfNbrLsRetransQLen | {message} | per neighbor_id, neighbor_ip | The current length of the retransmission queue |
snmp.device_prof_ospfNbrState | {status} | per neighbor_id, neighbor_ip | The state of the relationship with this neighbor |
snmp.device_prof_ospfVirtIfLsaCount | {advertisement}/s | per neighbor_id | The total number of link-local link state advertisements in this virtual interface's link-local link state database |
snmp.device_prof_ospfVirtIfState | {status} | per neighbor_id | OSPF virtual interface states |
snmp.device_prof_ospfVirtNbrEvents | {change}/s | per neighbor_id, neighbor_ip | The number of times this virtual link has changed its state or an error has occurred |
snmp.device_prof_ospfVirtNbrLsRetransQLen | {message} | per neighbor_id, neighbor_ip | The current length of the retransmission queue |
snmp.device_prof_ospfVirtNbrState | {status} | per neighbor_id, neighbor_ip | The state of the virtual neighbor relationship |
System / CPU
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_cpu_usage | % | per cpu_index | The current CPU utilization |
System / Memory
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_genMemUtilizationDynAllocMemAvailable | By | device | The available dynamically allocated memory |
snmp.device_prof_genMemUtilizationDynAllocMemUsed | By | device | The dynamically allocated memory has been used |
snmp.device_prof_genMemUtilizationPercentUsed | % | per mem_module_index | The percentage of memory used |
snmp.device_prof_genMemUtilizationPhyRam | By | per mem_module_index | The total size of the physical RAM |
snmp.device_prof_genMemUtilizationTotalRAM | By | device | The total size of the RAM |
System / Uptime
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_systemUptime | s | device | Time since the system was last rebooted or powered on. |
Voice / H248
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_avaya_cmgH248LinkErrorCode | {status} | device | Most recently received H.248 error code affecting the link between media gateway and controller |
snmp.device_prof_avaya_cmgLocalSig802Priority | 1 | device | 802.1 priority for signaling traffic on the H.248 link locally administered |
snmp.device_prof_avaya_cmgRemoteSig802Priority | 1 | device | 802.1 priority for signaling traffic on the H.248 link received from the controller |
Voice / VoIPEngine
| Metric (chart context) | Unit | Scope | Description |
|---|---|---|---|
snmp.device_prof_avaya_cmgDSPCoreAdminState | {status} | per avaya_cmg_dsp_core_id | Maintenance busy-out state |
snmp.device_prof_avaya_cmgDSPCoreChannelsInUse | {channel} | per avaya_cmg_dsp_core_id | Number of channels currently in use at the DSP core |
snmp.device_prof_avaya_cmgDSPCoreDemandTestResult | {status} | per avaya_cmg_dsp_core_id | Result of demand test |
snmp.device_prof_avaya_cmgDSPCoreStatus | {status} | per avaya_cmg_dsp_core_id | Status of the DSP core |
snmp.device_prof_avaya_cmgDSPCoreTotalChannels | {channel} | per avaya_cmg_dsp_core_id | Total number of channels available to the DSP core |
snmp.device_prof_avaya_cmgVoipAdminState | {status} | per avaya_cmg_voip_current_ip_address | Maintenance busy-out state |
snmp.device_prof_avaya_cmgVoipAverageOccupancy | % | per avaya_cmg_voip_current_ip_address | Five-minute average occupancy of the VoIP engine |
snmp.device_prof_avaya_cmgVoipChannelsInUse | {channel} | per avaya_cmg_voip_current_ip_address | Number of channels currently in use at the VoIP engine |
snmp.device_prof_avaya_cmgVoipDspStatus | {status} | per avaya_cmg_voip_current_ip_address | Status of the DSP complex |
snmp.device_prof_avaya_cmgVoipHyperactivity | {status} | per avaya_cmg_voip_current_ip_address | Indicates whether hyperactivity has been detected |
snmp.device_prof_avaya_cmgVoipTotalChannels | {channel} | per avaya_cmg_voip_current_ip_address | Total number of channels available to the VoIP engine |
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.