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. |
Syntaxe | Bits (0-raqmonPartRepDsrcName, 1-raqmonPartRepRecvName, 2-raqmonPartRepDsrcPort, 3-raqmonPartRepRecvPort, 4-raqmonPartRepSetupTime, 5-raqmonPartRepSetupDelay, 6-raqmonPartRepSessionDuration, 7-raqmonPartRepSetupStatus, 8-raqmonPartRepRTEnd2EndNetDelay, 9-raqmonPartRepOWEnd2EndNetDelay, 10-raqmonPartApplicationDelay, 11-raqmonPartRepIAJitter, 12-raqmonPartRepIPDV, 13-raqmonPartRepRcvdPackets, 14-raqmonPartRepRcvdOctets, 15-raqmonPartRepSentPackets, 16-raqmonPartRepSentOctets, 17-raqmonPartRepCumPacketsLoss, 18-raqmonPartRepFractionPacketsLoss, 19-raqmonPartRepCumDiscards, 20-raqmonPartRepFractionDiscards, 21-raqmonPartRepSrcPayloadType, 22-raqmonPartRepDestPayloadType, 23-raqmonPartRepSrcLayer2Priority, 24-raqmonPartRepSrcTosDscp, 25-raqmonPartRepDestLayer2Priority, 26-raqmonPartRepDestTosDscp, 27-raqmonPartRepCPU, 28-raqmonPartRepMemory, 29-raqmonPartRepAppName) |