close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Flow Monitoring and Flow Collection Services
play_arrow Flow Capture Services
- play_arrow Dynamically Capturing Packet Flows Using Junos Capture Vision
- play_arrow Detecting Threats and Intercepting Flows Using Junos Flow-Tap and FlowTapLite Services
play_arrow Inline Monitoring Services and Inband Network Telemetry
- play_arrow Inline Monitoring Services
  - Inline Monitoring Services Configuration
- play_arrow Flow-Based Telemetry
  - Flow-Based Telemetry (EX4100, EX4100-F, and EX4400 Series)
  - Flow-Based Telemetry for VXLANs (QFX5120)
- play_arrow Inband Flow Analyzer 2.0
  - Inband Flow Analyzer (IFA) 2.0 Probe for Real-Time Flow Monitoring
- play_arrow Juniper Resiliency Interface
  - Juniper Resiliency Interface
play_arrow Sampling and Discard Accounting Services
play_arrow Real-Time Performance Monitoring and Video Monitoring Services
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Configuring Inline Video Monitoring on MX Series Routers

date_range 01-Dec-23

arrow_backward

arrow_forward

Configuring Media Delivery Indexing Criteria

To configure media delivery indexing criteria:

In edit mode, create a named template for video monitoring.

content_copy zoom_out_map
user@host# edit services video-monitoring templates template-name

For example,

content_copy zoom_out_map
user@host# edit services video-monitoring templates t1

Set the duration for sampling in seconds. Flow media delivery indexing statistics are updated at the end of this interval.
```
[edit services video-monitoring templates template-name]
user@host# set interval-duration interval-duration
```
For example,
```
[edit services video-monitoring templates t1]
user@host# set interval-duration 1
```
Best Practice:
If you change the interval duration when a template is being used, you cause a change in the calculated number of expected packets in an measurement interval for the template. We recommend that you do not change the interval duration for a template that is in use.

Set the inactivity timeout.

content_copy zoom_out_map
[edit services video-monitoring templates template-name]
user@host# set inactive-timeout inactive-timeout

For example,

content_copy zoom_out_map
[edit services video-monitoring templates t1]
user@host# set inactive-timeout 30

Configure either the media rate or layer 3 packet rate to establish expected flow rates used to compare to monitored flow rates.
Note:
The media rate is the configured media bit rate for the stream. The media rate is used to establish expected packets per second (pps).

The Layer 3 packet rate in packets per second (pps) is used to establish expected bits per second (bps).
```
[edit services video-monitoring templates template-name]
user@host# set rate media media-bits-per-second
```
For example,
```
[edit services video-monitoring templates t1]
user@host# set rate media 2972400
```

Set delay factor thresholds for syslog message levels.

content_copy zoom_out_map
[edit services video-monitoring templates template-name]
user@host# set delay-factor threshold info delay-factor-threshold 
user@host# set delay-factor threshold warning delay-factor-threshold 
user@host# set delay-factor threshold critical delay-factor-threshold 

For example,

content_copy zoom_out_map
[edit services video-monitoring templates t1]
user@host# set delay-factor threshold info 100 
user@host# set delay-factor threshold warning 200 
user@host# set delay-factor threshold critical 300 

Set media loss rate thresholds for syslog message levels. You can set the threshold based on number of packets lost, or percentage of packets lost.

content_copy zoom_out_map
[edit services video-monitoring templates template-name]
user@host# set media-loss-rate threshold info percentage mlr-percentage 
user@host# set media-loss-rate threshold warning percentage mlr-percentage 
user@host# set media-loss-rate threshold critical percentage mlr-percentage 

For example,

content_copy zoom_out_map
[edit services video-monitoring templates t1]
user@host# set media-loss-rate threshold info percentage 5 
user@host# set media-loss-rate threshold warning percentage 10 
user@host# set media-loss-rate threshold critical percentage 20 

Set the media rate variation thresholds for syslog message levels. The threshold is based on the ratio of the difference between the configured media rate and the monitored media rate to the configured media rate, expressed as a percentage.

content_copy zoom_out_map
[edit services video-monitoring templates template-name]
user@host# set media-rate-variation threshold info mrv-variation 
user@host# set media-rate-variation threshold warning mrv-variation 
user@host# set media-rate-variation threshold critical mrv-variation 

For example,

content_copy zoom_out_map
[edit services video-monitoring templates t1]
user@host# set media-rate-variation threshold info 10 
user@host# set media-rate-variation threshold warning 15 
user@host# set media-rate-variation threshold critical 20 

Configuring Interface Flow Criteria

You can identify the input and output flows that you want to monitor. If you do not specify any identifiers, all flows on the interface are monitored. Starting in Junos OS Release 17.2R1, you can identify IPv4-over-MPLS flows. Starting in Junos OS Release 17.4R1, you can identify IPv6 flows and IPv6-over MPLS flows. MPLS flows with more than three labels cannot be monitored.

Note:

You can configure a maximum of 256 flow definitions for an interface. If your flow definitions contain lists of addresses and ports, you can exceed the number of match conditions. When you exceed the limits for flows or match conditions, you receive the following constraint message when you commit:

content_copy zoom_out_map
'interfaces xe-0/2/2.0'
    Number of flows or Number of match condition under flows exceeded limit
error: configuration check-out failed

To configure monitoring of flows for interfaces:

In edit mode, identify an interface for monitoring.
```
user@host# edit services video-monitoring interfaces interface-name
```

Identify IPv4 input flows for monitoring.

Assign a name to the input flow.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set input-flows input-flow-name 

Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set input-flows input-flow-name source-address [ address ] 

Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set input-flows input-flow-name destination-address [ address ] 

Identify the source port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set input-flows input-flow-name source-port [ port ] 

Identify the destination port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set input-flows input-flow-name destination-port [ port ] 

Identify the template used to monitor the input flow on the interface.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set input-flows input-flow-name template template-name

Identify IPv4 output flows for monitoring.

Assign a name to the output flow.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set output-flows output-flow-name 

Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set output-flows output-flow-name source-address [ address ] 

Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set output-flows output-flow-name destination-address [ address ] 

Identify the source port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set output-flows output-flow-name source-port [ port ] 

Identify the destination port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set output-flows output-flow-name destination-port [ port ] 

Identify the template used to monitor the output flow on the interface.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet]
user@host# set output-flows output-flow-name template template-name

Identify IPv4-over-MPLS input flows for monitoring:
1. Assign a name to the input flow.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name
2. Identify the payload type as IPv4 over MPLS.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name payload-type ipv4
3. Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use up to 32 destination addresses and up to 32 source addresses.
  Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use up to 32 destination addresses and up to 32 source addresses.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name destination-address [address] user@host# set input-flows input-flow-name source-address [address]
  If you configure multiple addresses for both the destination and source, then either all the destination or all the source values must have the same prefix length. For example, the following is allowed, because all the destination addresses have the same prefix length.
  [edit services video-monitoring interfaces ge-0/2/2.0 family mpls] user@host# set input-flows input-flow-name destination-address [203.0.13.0/24 198.51.100.0/24] user@host# set input-flows input-flow-name source-address [172.16.0.0/12 192.0.2.11/32]
4. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name destination-port [ port ]
5. Identify the source port for the flow. You can use multiple port numbers and port ranges.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name source-port [ port ]
6. Identify the template used to monitor the input flow on the interface.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name template template-name

Identify IPv4-over-MPLS output flows for monitoring:

Assign a name to the output flow.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family mpls]
user@host# set output-flows output-flow-name 

Identify the payload type as IPv4 over MPLS.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family mpls]
user@host# set output-flows output-flow-name payload-type ipv4

Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use up to 32 destination addresses and up to 32 source addresses.
Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use up to 32 destination addresses and up to 32 source addresses.
```
[edit services video-monitoring interfaces interface-name family mpls]
user@host# set output-flows output-flow-name destination-address [address] 
user@host# set output-flows output-flow-name source-address [address]
```
If you configure multiple addresses for both the destination and source, then either all the destination or all the source values must have the same prefix length. For example, the following is allowed, because all the destination addresses have the same prefix length.
```
[edit services video-monitoring interfaces ge-0/2/2.0 family mpls]
user@host# set output-flows output-flow-name destination-address [203.0.13.0/24 198.51.100.0/24] 
user@host# set output-flows output-flow-name source-address [172.16.0.0/12 192.0.2.11/32]
```

Identify the source port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family mpls]
user@host# set output-flows output-flow-name source-port [port] 

Identify the destination port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family mpls]
user@host# set output-flows output-flow-name destination-port [ port ] 

Identify the template used to monitor the output flow on the interface.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family mpls]
user@host# set output-flows output-flow-name template template-name

Identify IPv6 input flows for monitoring.

Assign a name to the input flow.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set input-flows input-flow-name 

Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set input-flows input-flow-name source-address [ address ] 

Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set input-flows input-flow-name destination-address [ address ] 

Identify the source port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set input-flows input-flow-name source-port [ port ] 

Identify the destination port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set input-flows input-flow-name destination-port [ port ] 

Identify the template used to monitor the input flow on the interface.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set input-flows input-flow-name template template-name

Identify IPv6 output flows for monitoring.

Assign a name to the output flow.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set output-flows output-flow-name 

Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set output-flows output-flow-name source-address [ address ] 

Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set output-flows output-flow-name destination-address [ address ] 

Identify the source port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set output-flows output-flow-name source-port [ port ] 

Identify the destination port for the flow. You can use multiple port numbers and port ranges.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set output-flows output-flow-name destination-port [ port ] 

Identify the template used to monitor the output flow on the interface.

content_copy zoom_out_map
[edit services video-monitoring interfaces interface-name family inet6]
user@host# set output-flows output-flow-name template template-name

Identify IPv6-over-MPLS input flows for monitoring:
1. Assign a name to the input flow.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name
2. Identify the payload type as IPv6 over MPLS.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name payload-type ipv6
3. Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use multiple addresses (up to 32) for either the destination or the source IP address, but not for both.
  Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use multiple addresses (up to 32) for either the destination or the source IP address, but not for both.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name destination-address [address] user@host# set input-flows input-flow-name source-address [address]
4. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name destination-port [ port ]
5. Identify the source port for the flow. You can use multiple port numbers and port ranges.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name source-port [ port ]
6. Identify the template used to monitor the input flow on the interface.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set input-flows input-flow-name template template-name
Identify IPv6-over-MPLS output flows for monitoring:
1. Assign a name to the output flow.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set output-flows output-flow-name
2. Identify the payload type as IPv6 over MPLS.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set output-flows output-flow-name payload-type ipv6
3. Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use multiple addresses (up to 32) for either the destination or the source IP address, but not for both.
  Identify the destination IP address or prefix value, the source IP address or prefix value, or both for the flow. You can use multiple addresses (up to 32) for either the destination or the source IP address, but not for both.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set output-flows output-flow-name destination-address [address] user@host# set output-flows output-flow-name source-address [address]
4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set output-flows output-flow-name source-port [port]
5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set output-flows output-flow-name destination-port [ port ]
6. Identify the template used to monitor the output flow on the interface.
  [edit services video-monitoring interfaces interface-name family mpls] user@host# set output-flows output-flow-name template template-name

Configuring the Number of Flows That Can Be Measured

Starting in Junos OS Release 16.1R1, you can configure the number of flows that can be measured per Packet Forwarding Engine at a given time by an MPC. This value takes effect the next time the MPC is rebooted. If you do not configure this value, the default maximum value for an MPC is given in Understanding Inline Video Monitoring on MX Series Routers.

To configure the number of flows that can be measured per Packet Forwarding Engine by an MPC at a given time:

Configure the flow table size. The range is 16 through 8192.

content_copy zoom_out_map
[edit chassis fpc slot inline-video-monitoring]
user@host# set flow-table-size size

Change History Table

Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.

Release

Description

17.4R1

Starting in Junos OS Release 17.4R1, you can identify IPv6 flows and IPv6-over MPLS flows.

17.2R1

Starting in Junos OS Release 17.2R1, you can identify IPv4-over-MPLS flows.

16.1R1

Starting in Junos OS Release 16.1R1, you can configure the number of flows that can be measured per Packet Forwarding Engine at a given time by an MPC.

arrow_backward PREVIOUS Understanding Inline Video Monitoring on MX Series Routers

NEXT arrow_forward Inline Video Monitoring Syslog Messages on MX Series Routers

Monitoring, Sampling, and Collection Services Interfaces User Guide

ON THIS PAGE

Configuring Inline Video Monitoring on MX Series Routers

Configuring Media Delivery Indexing Criteria

Configuring Interface Flow Criteria

Configuring the Number of Flows That Can Be Measured

Change History Table

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Monitoring, Sampling, and Collection Services Interfaces User Guide

ON THIS PAGE

Configuring Inline Video Monitoring on MX Series Routers

Configuring Media Delivery Indexing Criteria

Configuring Interface Flow Criteria

Configuring the Number of Flows That Can Be Measured

Related Documentation

Change History Table

Stay in touch