Each VUE Server within a VUE system can contain an Auxiliary Core Control Plane (ACCP). Each ACCP can be configured to transmit packet metrics collected from the RxD population it manages. A VUE Aux Core can manage up to 1000 RxDs. Upon an Aux Core being configured to transmit RxD metrics data to a Kafka endpoint in the Domain Manager Telemetry Pipeline, the ACCP will transmit messages containing channel metric data for the RxDs that the Aux Core manages (those assigned to it). Configuring a VUE server having an Aux Core to transmit RxD metrics data can be found in the VUE User Guide topic, Configuring the Telegraf agent on a VUE server to send metric data to Kafka message broker.
The ACCP transmits messages every 60 seconds by default; you can configure the interval in VTM. Refer to the VUE documentation to configure a VUE Aux Core to transmit RxD metric data.
The RxD metric data sent by the VUE
server(s) to the Kafka message broker in the Domain Manager Telemetry Pipeline is processed and
stored in a Time Series Database (TSDB). VTM makes use of this data for monitoring and
troubleshooting. VTM uses pre-configured queries into the TSDB that render graphs/charts
in the form of Grafana iFrames for the following types of information:
- L2TP DEPI session input metric
data (per DEPI session per device):
- Dropped Ingress Packets: For a given DEPI multicast session (transport stream), these are the number of DEPI frames that the VUE server transmitted to the RxDs that were subsequently dropped by the RxDs on the receiving end. The metric is calculated and represented as a percentage within a collected sampling interval by the VUE Aux Core (for example, 60 seconds): Dropped Ingress Packets = (vuePktsDelta - l2tpInDelta)/vuePksDelta * 100
- Discarded Packets: For a given DEPI multicast session (transport stream), these are the number DEPI frames that the VUE server transmitted to the RxDs and were subsequently discarded by the RxDs on the receiving end. This metric is calculated as a DEPI frame count within the collected sampling interval by the VUE Aux Core (for example, 60 seconds).
- Out of Sequence Packets: For a given DEPI multicast session (transport stream), these are the number DEPI frames that the VUE server transmitted to the RxDs and were subsequently received out of sequence by the RxDs. This metric is calculated as a DEPI frame count within the collected sampling interval by the VUE Aux Core (for example, 60 seconds).
- RxD RF Channel Output metric
data (per RF QAM channel per device):
- Dropped Egress Packets: The number of dropped MPEG packets for a given channel within anRxD. This metric is calculated and represented as a percentage within the collected sampling interval by the VUE Aux Core (for example, 60 seconds): Dropped Egress Packets = (outDiscardDelta +outErrorsDelta)/l2tpInDelta * 100
- Discarded Packets: The number of discarded MPEG packets for a given channel within an RxD. This metric is calculated and represented as an MPEG packet count within the collected sampling interval by the VUE Aux Core (for example, 60 seconds).
- Packets in Error: The number of MPEG packets found in error for a given channel within an RxD. This metric is calculated and represented as an MPEG packet count within the collected sampling interval by the VUE Aux Core (for example, 60 seconds).
NOTE: Channel packet counts are MPEG packets,
whereas session-based packet counts are DEPI frame counts. Typically, there are about 7
to 10 MPEG packets in a DEPI session frame.