Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Example: Configuring Inline Video Monitoring Using Media Delivery Index Metrics

 

This example shows how to configure monitoring of video streaming efficiency using Media Delivery Index (MDI) metrics.

Requirements

This example uses the following hardware and software components:

  • MX Series 3D Universal Edge Router

  • One of the following MPC interface cards:

    • MPC1E

    • MPC2E

    • MPC-16XGE

    • MPC7E

    • MPC8E

    • MPC9E

  • Junos OS Release 14.1 or later

Overview

Junos OS Release 14.1 introduces support for video monitoring using MDI criteria. MDI information enables you to quickly identify devices causing excessive jitter or packet loss in streaming video applications.

Topology

The topology for inline video monitoring is shown in Figure 1

Figure 1: Inline Video Monitoring
Inline Video Monitoring

Configuration

CLI Quick Configuration

To quickly configure this example, copy the following commands, paste them into a text file, remove any line breaks, change any details necessary to match your network configuration, copy and paste the commands into the CLI at the [edit] hierarchy level, and then enter commit from configuration mode.

Configuring Interfaces

Step-by-Step Procedure

To configure the interfaces for input flows, output flows, or both:

  1. Define an interface for input media flow traffic.
    [edit]
    user@host# set interfaces xe-2/2/1 unit 0 family inet address 20.0.0.1/24
  2. Define an interface for output media flow traffic.
    [edit]
    user@host# set interfaces ge-2/0/6 unit 0 family inet address 60.0.0.1/24

Configuring Selection of Flows for Monitoring

Step-by-Step Procedure

To configure input media flows, output media flows, or both for video monitoring:

  1. Specify an interface subject to input flow monitoring, including the interface name, xe-2/2/1.0, the name of the flow definition, f1, the type of flows measured, input flows, and the name of the template used for defining the flows, t1.
    [edit]
    user@host# set services video-monitoring interfaces xe-2/2/1.0 family inet input-flows f1 template t1

  2. For the same interface, specify any selection criteria to limit the number of flows selected for monitoring.

    You can select based on any combination of source IP, source port, destination IP, and destination port. If you do not specify selection criteria, all flows containing media packets are monitored. In this example, we are limiting monitoring to flows with source IP 20.0.2.0/32, source port 1024, and destination IP 60.0.0.2

    [edit]
    user@host# set services video-monitoring interfaces xe-2/2/1.0 family inet input-flows f1 source-address 20.0.2.0/32 source-port 1024 destination-address 60.0.0.2

  3. Specify an interface subject to output flow monitoring, including the interface name, ge-2/0/6.0, the name of the flow definition, f2, the type of flows measured, output flows, and the name of the template used for defining the flows, t2.
    [edit]
    user@host# set services video-monitoring interfaces ge-2/0/6.0 family inet output-flows f2 template t2

  4. For the same interface, specify any selection criteria to limit the number of flows selected for monitoring.

    In this example, no output flow selection criteria are specified, meaning that all output media flows are selected for monitoring.

Results

From configuration mode, confirm your configuration by entering the show services video-monitoring interfaces command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Configuring Monitoring Templates for Input and Output Flows

Step-by-Step Procedure

You can configure monitoring templates specifying monitoring criteria to apply to selected flows. The monitoring templates specify expected flow rates and the number of media packets expected in an IP packet. The templates can also be used to specify threshold values for delay factor, media rate variation, and media loss rate. Log messages are created when the threshold values are exceeded.

To configure monitoring templates for input and output flows:

  1. Configure measurement parameters for flows, including expected rate and packet size information, name the template t1, and include the duration of measuring intervals (in seconds).

    This template is used for input flows and includes the following information:

    template name

    t1

    duration of measurement interval (seconds)

    1

    timeout (seconds of inactivity before concluding measurement of a flow)

    30

    expected media rate in bits per second

    2972400

    number of media packets in Layer 3 IP packet

    7

    size of a media packet in bytes

    100

    [edit]
    user@host# set services video-monitoring templates t1 interval-duration 1
    user@host# set services video-monitoring templates t1 timeout 30
    user@host# set services video-monitoring templates t1 rate media 2972400
    user@host# set services video-monitoring templates t1 media-packets-count-in-layer3 7
    user@host# set services video-monitoring templates t1 media-packet-size 188

  2. Configure threshold levels for generating SYSLOG messages.

    For each of the following optional thresholds, you specify the level of the SYSLOG message generated when the threshold is exceeded. The levels are critical, warning, and info; you can define 0 to 3 SYSLOG message thresholds for each measurement.

    delay-factor (milliseconds) threshold info

    100

    delay-factor threshold warning

    200

    delay-factor threshold critical

    500

    media-loss-rate (percentage) threshold info

    5

    media-loss-rate threshold warning

    10

    media-loss-rate threshold critical

    20

    media-rate-variation threshold info

    10

    media-rate-variation threshold warning

    15

    media-rate-variation threshold critical

    20

    [edit]
    user@host# set services video-monitoring templates t1 delay-factor threshold info 100
    user@host# set services video-monitoring templates t1 delay-factor threshold warning 200
    user@host# set services video-monitoring templates t1 delay-factor threshold critical 500
    user@host# set services video-monitoring templates t1 media-loss-rate threshold info percentage 5
    user@host# set services video-monitoring templates t1 media-loss-rate threshold warning percentage 10
    user@host# set services video-monitoring templates t1 media-loss-rate threshold critical percentage 20
    user@host# set services video-monitoring templates t1 media-rate-variation threshold info 10
    user@host# set services video-monitoring templates t1 media-rate-variation threshold warning 15
    user@host# set services video-monitoring templates t1 media-rate-variation threshold critical 20
  3. Configure a template containing measurement parameters for output flows.

    In this example, template t2 is used to configure monitoring criteria that are applied to the output interface definition. This template does not specify threshold levels for SYSLOG messages, indicating that the user is interested only in monitoring statistics, error information, and flow statistics that are available via show commands.

    [edit]
    user@host# set services video-monitoring templates t2 interval-duration 1
    user@host# set services video-monitoring templates t2 timeout 30
    user@host# set services video-monitoring templates t2 rate media 2972400
    user@host# set services video-monitoring templates t2 media-packets-count-in-layer3 7
    user@host# set services video-monitoring templates t2 media-packet-size 188

Results

From configuration mode, confirm your configuration by entering the show services video-monitoring templates command. If the output does not display the intended configuration, repeat the instructions in this example to correct the configuration.

Verification

Confirm that the configuration is working properly.

Verifying Statistics Reporting

Purpose

Verify that statistics are being reported.

Action

From operational mode, enter the show services video-monitoring mdi statistics command.

user@router> show services video-monitoring mdi statistics fpc-slot 2

Meaning

The output shows that inline video monitoring is operational.