Skip to main content

Polycom HDX SNMP


The Polycom HDX Room system is an endpoint device that provides voice and video connectivity across collaboration networks.

This Monitoring Connector checks basic system health indicators and video/audio related protocols performances during a call.

Monitoring Connector assets​

Monitored objects​

  • HDX Room systems

Collected metrics​

Metric nameDescriptionUnit
cpu.user.utilization.percentageCPU User utilization%
cpu.nice.utilization.percentageCPU Nice utilization%
cpu.system.utilization.percentageCPU System utilization%
cpu.idle.utilization.percentageCPU Idle utilization%
cpu.wait.utilization.percentageCPU Wait utilization%
cpu.kernel.utilization.percentageCPU Kernel utilization%
cpu.interrupt.utilization.percentageCPU Interrupt utilization%
cpu.softirq.utilization.percentageCPU SoftIrq utilization%
cpu.steal.utilization.percentageCPU Steal utilization%
cpu.guest.utilization.percentageCPU Guest utilization%
cpu.guestnice.utilization.percentageCPU Guest Nice utilization%


Device Configuration​

On the Polycom device, enable and configure the SNMP agent:

- Connect to the HDX Admin Web UI
- Go to 'System > Manage > Credentials'
- Create new SNMP credentials specifying community and version

Network flows​

The Centreon Poller must be able to reach the UDP/161 SNMP port of the Polycom HDX device.


  1. Install the Centreon package on every Centreon Poller expected to monitor Polycom HDX devices:
yum install centreon-plugin-Hardware-Devices-Polycom-Hdx-Snmp
  1. On the Centreon Web interface, install the Polycom HDX SNMP Monitoring Connector through Configuration > Monitoring Connector Manager page.

Host configuration​

  • Add a new Host and apply the HW-Device-Polycom-Hdx-SNMP-Custom Host Template
  • Fill SNMP Version and Community fields according to the device's configuration

When using SNMP v3, use the SNMPEXTRAOPTIONS Macro to add specific authentication parameters More information in the Troubleshooting SNMP section.

SNMPEXTRAOPTIONSConfigure your own SNMPv3 credentials combo


How to test the Plugin and what are the main options for?​

Once the plugin installed, log into your Centreon Poller CLI using the centreon-engine user account and test the Plugin by running the following command:

/usr/lib/centreon/plugins/ \
--plugin=hardware::devices::polycom::hdx::snmp::plugin \
--mode=viewstation-stats \
--hostname= \
--snmp-version='2c' \
--snmp-community='mysnmpcommunity' \
--warning-h323-packet-loss='5' \
--critical-h323-packet-loss='10' \

Expected command output is shown below:

OK: View Station Phone Number: '0123456789' Stats: H323 Packet Loss 1.00 %, H323 (audio/video) Jitter 30.00 ms, H323 (audio/video) Latency 4.00 |
'h323-packet-loss'=1.00%;;;0;100 'h323-jitter'=30.00ms;;;0;100 'vs_latency'=4.00;;;0;100

The command above monitors the sessions statistics of a Polycom HDX ViewStation device (--plugin=hardware::devices::polycom::hdx::snmp::plugin --mode=viewstation-stats) identified by the IP address (--hostname= As the Plugin is using the SNMP protocol to request the device, the related community and version are specified (--snmp-version='2c' --snmp-community='mysnmpcommunity').

This command would trigger a WARNING alarm if the packet loss rate of the active calls raises over 5% (--warning-h323-packet-loss='5') and a CRITICAL alarm over 10% (--critical-h323-packet-loss='10').

All the options as well as all the available thresholds can be displayed by adding the --help parameter to the command:

/usr/lib/centreon/plugins/ --plugin=hardware::devices::polycom::hdx::snmp::plugin --mode=viewstation-stats --help

UNKNOWN: SNMP GET Request : Timeout​

If you get this message, you're probably facing one of theses issues:

  • The SNMP agent of the device isn't started or is misconfigured
  • An external device is blocking the request (firewall, ...)

What does the '(skipped: no values)' message mean?​

When using ViewStation-Statistics service, you will get this message when there is no audio and/or video call in progress on the HDX Room system. This is the expected behavior. As soon as a call starts, metrics will get populated.