interfaces (Video Monitoring)
Syntax
interfaces {
interface-name {
family {
inet {
input-flows {
input-flow-name {
destination-address [ address ];
destination-port [ port ];
source-address [ address ];
source-port [ port ];
template template-name;
}
}
output-flows {
output-flow-name {
destination-address [ address ];
destination-port [ port ];
source-address [ address ];
source-port [ port ];
template template-name;
}
}
}
inet6 {
input-flows {
input-flow-name {
destination-address [ address ];
destination-port [ port ];
source-address [ address ];
source-port [ port ];
template template-name;
}
}
output-flows {
output-flow-name {
destination-address [ address ];
destination-port [ port ];
source-address [ address ];
source-port [ port ];
template template-name;
}
}
}
mpls {
input-flows {
input-flow-name {
(destination-address [ address ] | source-address [ address ]);
destination-port [ port ];
payload-type (ipv4 | ipv6);
source-port [ port ];
template template-name;
}
}
output-flows {
output-flow-name {
(destination-address [ address ] | source-address [ address ]);
destination-port [ port ];
payload-type (ipv4 | ipv6);
source-port [ port ];
template template-name;
}
}
}
}
}
}
Hierarchy Level
[edit services video-monitoring]
Description
Define video monitoring for specified input or output flows on selected interfaces. You can configure a maximum of 256 flows for an interface.
Options
| destination-address address | Destination IPv4 or IPv6 address or prefix value of a flow that you want to monitor. You can use up to 32 addresses. For IPv4-over-MPLS flows, 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] For IPv6-over-MPLS flows, if you configure both the destination and source address, you can use multiple addresses for either the destination or the source IP address, but not for both. |
| destination-port port | Destination port number of a flow that you want to monitor. You can use multiple port numbers and port ranges.
|
| input-flows input-flow-name | Name of an input flow you are defining. |
| interface-name | Name of the interface to monitor. |
| output-flows output-flow-name | Name of an output flow you are defining. |
| payload-type ipv4 | Monitor video stream for IPv4-over-MPLS traffic. |
| payload-type ipv6 | Monitor video stream for IPv6-over-MPLS traffic. |
| source-address address | Source IPv4 or IPv6 address or prefix value of a flow that you want to monitor. You can use up to 32 addresses. For IPv4-over-MPLS flows, 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] For IPv6-over-MPLS flows, if you configure both the destination and source address, you can use multiple addresses for either the destination or the source IP address, but not for both. |
| source-port port | Source port number of a flow that you want to monitor. You can use multiple port numbers and port ranges.
|
template-name |
Name of the template used to monitor the
input flows or output flows on an interface. The template contains
the measurement parameters for video monitoring, and is configured
at the |
Required Privilege Level
interface—To view this statement in the configuration.
interface-control—To add this statement to the configuration.
Release Information
Statement introduced in Junos OS Release 14.1.
mpls option introduced in Junos OS Release 17.2.
payload-type ipv6 option introduced in Junos OS Release
17.4.