All MIBs › RAQMON-MIB › raqmonParticipantReportCaps
raqmonParticipantReportCaps
Module: RAQMON-MIB
OID (symbolic): RAQMON-MIB::raqmonParticipantReportCaps
OID (numeric): 1.3.6.1.2.1.16.31.1.1.1.1.3
Node type: OBJECT-TYPE
Type: Bits
Access: read-only
Description: The Report capabilities of the participant, as perceived by the Collector.
If the participant can report the Data Source Name as defined in [RFC4710], Section 5.3, then the raqmonPartRepDsrcName bit will be set.
If the participant can report the Receiver Name as defined in [RFC4710], Section 5.4, then the raqmonPartRepRecvName bit will be set.
If the participant can report the Data Source Port as defined in [RFC4710], Section 5.5, then the raqmonPartRepDsrcPort bit will be set.
If the participant can report the Receiver Port as defined in [RFC4710], Section 5.6, then the raqmonPartRepRecvPort bit will be set.
If the participant can report the Session Setup Time as defined in [RFC4710], Section 5.7, then the raqmonPartRepSetupTime bit will be set.
If the participant can report the Session Setup Delay as defined in [RFC4710], Section 5.8, then the raqmonPartRepSetupDelay bit will be set.
If the participant can report the Session Duration as defined in [RFC4710], Section 5.9, then the raqmonPartRepSessionDuration bit will be set.
If the participant can report the Setup Status as defined in [RFC4710], Section 5.10, then the raqmonPartRepSetupStatus bit will be set.
If the participant can report the Round-Trip End-to-end Network Delay as defined in [RFC4710], Section 5.11, then the raqmonPartRepRTEnd2EndNetDelay bit will be set.
If the participant can report the One-way End-to-end Network Delay as defined in [RFC4710], Section 5.12, then the raqmonPartRepOWEnd2EndNetDelay bit will be set.
If the participant can report the Application Delay as defined in [RFC4710], Section 5.13, then the raqmonPartApplicationDelay bit will be set.
If the participant can report the Inter-Arrival Jitter as defined in [RFC4710], Section 5.14, then the raqmonPartRepIAJitter bit will be set.
If the participant can report the IP Packet Delay Variation as defined in [RFC4710], Section 5.15, then the raqmonPartRepIPDV bit will be set.
If the participant can report the number of application packets received as defined in [RFC4710], Section 5.16, then the raqmonPartRepRcvdPackets bit will be set.
If the participant can report the number of application octets received as defined in [RFC4710], Section 5.17, then the raqmonPartRepRcvdOctets bit will be set.
If the participant can report the number of application packets sent as defined in [RFC4710], Section 5.18, then the raqmonPartRepSentPackets bit will be set.
If the participant can report the number of application octets sent as defined in [RFC4710], Section 5.19, then the raqmonPartRepSentOctets bit will be set.
If the participant can report the number of cumulative packets lost as defined in [RFC4710], Section 5.20, then the raqmonPartRepCumPacketsLoss bit will be set.
If the participant can report the fraction of packet loss as defined in [RFC4710], Section 5.21, then the raqmonPartRepFractionPacketsLoss bit will be set.
If the participant can report the number of cumulative discards as defined in [RFC4710], Section 5.22, then the raqmonPartRepCumDiscards bit will be set.
If the participant can report the fraction of discards as defined in [RFC4710], Section 5.23, then the raqmonPartRepFractionDiscards bit will be set.
If the participant can report the Source Payload Type as defined in [RFC4710], Section 5.24, then the raqmonPartRepSrcPayloadType bit will be set.
If the participant can report the Destination Payload Type as defined in [RFC4710], Section 5.25, then the raqmonPartRepDestPayloadType bit will be set.
If the participant can report the Source Layer 2 Priority as defined in [RFC4710], Section 5.26, then the raqmonPartRepSrcLayer2Priority bit will be set.
If the participant can report the Source DSCP/ToS value as defined in [RFC4710], Section 5.27, then the raqmonPartRepSrcToSDscp bit will be set.
If the participant can report the Destination Layer 2 Priority as defined in [RFC4710], Section 5.28, then the raqmonPartRepDestLayer2Priority bit will be set.
If the participant can report the Destination DSCP/ToS Value as defined in [RFC4710], Section 5.29, then the raqmonPartRepDestToSDscp bit will be set.
If the participant can report the CPU utilization as defined in [RFC4710], Section 5.30, then the raqmonPartRepCPU bit will be set.
If the participant can report the memory utilization as defined in [RFC4710], Section 5.31, then the raqmonPartRepMemory bit will be set.
If the participant can report the Application Name as defined in [RFC4710], Section 5.32, then the raqmonPartRepAppName bit will be set.
The capability of reporting of a specific metric does not mandate that the metric must be reported permanently by the data source to the respective collector. Some data sources MAY be configured not to send a metric, or some metrics may not be relevant to the specific application.
What is raqmonParticipantReportCaps?
This read-only BITS value tells a collector which of the roughly 30 defined RAQMON metrics (CPU, memory, jitter, payload types, DSCP, packet/octet counts, etc.) a given participant is actually capable of reporting, as observed by the collector rather than self-declared. Before alerting on a missing metric for a participant, check this field first -- a zero value for that metric may just mean the device never reports it, not that something is broken.
Examples
Walk all instances (SNMPv2c):
snmpwalk -v2c -c public <target> 1.3.6.1.2.1.16.31.1.1.1.1.3 snmpwalk -v2c -c public <target> RAQMON-MIB::raqmonParticipantReportCaps
Get a specific instance (index 1):
snmpget -v2c -c public <target> 1.3.6.1.2.1.16.31.1.1.1.1.3.1 snmpget -v2c -c public <target> RAQMON-MIB::raqmonParticipantReportCaps.1
Start monitoring vendor-neutral, standards-based MIB (RFC 4711), implemented by RAQMON-capable VoIP/video endpoints with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the RAQMON-MIB::raqmonParticipantReportCaps OID value, configure state conditions and alerts, and monitor any vendor-neutral, standards-based MIB (RFC 4711), implemented by RAQMON-capable VoIP/video endpoints from a single console.
OID Breakdown
Upper-level ancestors (7 from the standard OID tree / other modules)
| Numeric OID | Name | Module |
|---|---|---|
| 1 | iso | LANART-AGENT |
| 1.3 | org | AirPair-MIB |
| 1.3.6 | dod | AirPair-MIB |
| 1.3.6.1 | internet | AirPair-MIB |
| 1.3.6.1.2 | mgmt | AXON-MIB |
| 1.3.6.1.2.1 | mib_2 | AXON-MIB |
| 1.3.6.1.2.1.16 | rmon | LBHUB-BOOM-MIB |
| Numeric OID | Name | Module |
|---|---|---|
| 1.3.6.1.2.1.16.31 | raqmonMIB | RAQMON-MIB |
| 1.3.6.1.2.1.16.31.1 | raqmonMIBObjects | RAQMON-MIB |
| 1.3.6.1.2.1.16.31.1.1 | raqmonSession | RAQMON-MIB |
| 1.3.6.1.2.1.16.31.1.1.1 | raqmonParticipantTable | RAQMON-MIB |
| 1.3.6.1.2.1.16.31.1.1.1.1 | raqmonParticipantEntry | RAQMON-MIB |
| 1.3.6.1.2.1.16.31.1.1.1.1.3 | raqmonParticipantReportCaps | RAQMON-MIB |