Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Configuring Inline Video Monitoring on MX Series Routers

Configuring Media Delivery Indexing Criteria

To configure media delivery indexing criteria:

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

    For example,

  2. Set the duration for sampling in seconds. Flow media delivery indexing statistics are updated at the end of this interval.

    For example,

    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.

  3. Set the inactivity timeout.

    For example,

  4. 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).

    For example,

  5. Set delay factor thresholds for syslog message levels.

    For example,

  6. 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.

    For example,

  7. 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.

    For example,

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:

To configure monitoring of flows for interfaces:

  1. In edit mode, identify an interface for monitoring.
  2. Identify IPv4 input flows for monitoring.
    1. Assign a name to the input flow.
    2. Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.
    3. Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.
    4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the input flow on the interface.
  3. Identify IPv4 output flows for monitoring.
    1. Assign a name to the output flow.
    2. Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.
    3. Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.
    4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the output flow on the interface.
  4. Identify IPv4-over-MPLS input flows for monitoring:
    1. Assign a name to the input flow.
    2. Identify the payload type as IPv4 over MPLS.
    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.

      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.

    4. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the input flow on the interface.
  5. Identify IPv4-over-MPLS output flows for monitoring:
    1. Assign a name to the output flow.
    2. Identify the payload type as IPv4 over MPLS.
    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.

      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.

    4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the output flow on the interface.
  6. Identify IPv6 input flows for monitoring.
    1. Assign a name to the input flow.
    2. Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.
    3. Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.
    4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the input flow on the interface.
  7. Identify IPv6 output flows for monitoring.
    1. Assign a name to the output flow.
    2. Identify the source IP address or prefix value for the flow. You can use up to 32 addresses.
    3. Identify the destination IP address or prefix value for the flow. You can use up to 32 addresses.
    4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the output flow on the interface.
  8. Identify IPv6-over-MPLS input flows for monitoring:
    1. Assign a name to the input flow.
    2. Identify the payload type as IPv6 over MPLS.
    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.

    4. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the input flow on the interface.
  9. Identify IPv6-over-MPLS output flows for monitoring:
    1. Assign a name to the output flow.
    2. Identify the payload type as IPv6 over MPLS.
    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.

    4. Identify the source port for the flow. You can use multiple port numbers and port ranges.
    5. Identify the destination port for the flow. You can use multiple port numbers and port ranges.
    6. Identify the template used to monitor the output flow on the interface.

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.

Related Documentation

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.