Video services

Video services are supported on:

• MS-ISA

• MS-ISA2

• MS-ISM (two MS-ISA2 on a single line card)

• ESA

These MS-ISA and ESA variants are referred to as ISAs in this section.

Both MS-ISA and MS-ISA2 support FCC and RET, VQM, and perfect stream functionality. The ESA currently only supports FCC and RET.

When configured in the router, ISAs are logically grouped into video groups for video services. A video group allows multiple ISAs/ESAs for an application. The system performs load balancing between the ISAs. Nokia recommends not mixing ISA, ISA2, and ESA in the same video group. All ISAs within a video group are always active, there are no standby ISAs.

Video groups provide a redundancy mechanism to guard against hardware failure within a group where the system automatically rebalances tasks to the group excluding the failed MS-ISA or ESA-VM. Video groups also pool the processing capacity of all the group members and increase the application throughput because of the increased packet processing capability of the group. The buffer usage is typically identical for all members of the video group, so increasing the number of members in a group does not increase the scaling numbers for parameters bounded by available buffering, but there is still the increase in performance gained from the pooled packet processor capacity. A video service must be enabled at the video group level before that service can be used.

A video application may restrict the number of ISAs supported in a video group to a smaller number. Please contact your local Nokia representative for more information about video application specifications.

The video group logically interfaces to a service instance with a video Service Access Point (SAP). Like a SAP for connectivity services, the video SAP allows the assignment of an ingress and egress filter policy and QoS policy.

Ingress and egress directions for the filter and QoS policy are named based on the perspective of the router which is the opposite perspective of the ISA. An ‟egress” policy is one that applies to traffic egressing the router and ingressing the ISA. An ‟ingress” policy is one that applies to traffic ingressing the router and egressing the video. Although potentially confusing, the labeling of ingress and egress for the ISA policies was chosen so that existing policies for connectivity services can be reused on the ISA unchanged.

If no filter or QoS policy is configured, the default policies are used.

One of the key attributes of a video SAP is a video group association. The video SAP’s video group assignment is what determines which video group services on that video SAP. The video groups configuration determines what video services are available.

The video interface acts as the following:

• FCC and RET server

• interface for multicast buffering

• interface for the perfect stream

A video interface supports up to 16 IP addresses and is supported on VPRN or IES services.

Multicast information policies on the 7750 SR and 7450 ESS serve multiple purposes. In the context of a service with video services, the multicast information policy assigned to the service provides configuration information for the multicast channels and defines video policy elements for a video interface.

This section describes the base elements of a multicast information policy in support of a video service. Specific video service features require additional configuration in the multicast information policy which are described in the sections dedicated to the video feature.

Multicast information policies are named hierarchically structured policies composed of channel bundles which contain channels which contain source-overrides.

• Bundles are assigned a name and contain a collection of channels. Attributes not defined for a named bundle are inherited from the special default bundle named ‟default”.

  *A:ALA-48configmcast-mgmtmcast-info-plcy# info
  ----------------------------------------------
              bundle "default" create
              exit
  ----------------------------------------------
  *A:ALA-48configmcast-mgmtmcast-info-plcy#
  

• Channels are ranges of IP multicast address identified by a start IP multicast address (GGstart) and optional end IP multicast address (Gend), so the channels encompasses (*,Gstart) through (*,Gend). A channel attribute is inherited from its bundle unless the attribute is explicitly assigned in which case the channel attribute takes precedence.

• A source-override within a channel are IP multicast addresses within the channel with a specific source IP address (Soverride), so the source-override encompass (Soverride,Gstart) through (Soverride,Gend). A source-override attribute is inherited from its channel unless the attribute is explicitly assigned in the source-override channel in which case the source-override channel attribute takes precedence.

For a IP multicast channel (*,G) or (S,G), the most specific policy element in the hierarchy that matches applies to that channel.

A multicast information policy is assigned to a service instance. For video services, the multicast information policy assigned to the service determines the video group for a given IP multicast channel. When a channel is assigned to a video group, the channel is sent to the video group for buffering or processing as appropriate depending on the video services enabled on the video group. If no video group is assigned to a channel, the channel is still distributed within the service instance, but no video services are available for that channel.

In addition to bundles, channels and source-overrides, multicast information policies also include video policies. Video policies define attributes for the video interfaces within the service instance.

Video policy attributes are specific to the video feature and are covered in detail in the applicable video feature section. Video policies are mentioned here because they are an element of the multicast information policy and provide the link to configuration for a video interface.

To protect against network interruption or reconvergence, it is often more efficient to protect the stream using an alternate transmission path. This can be a separate physical interface, transmission link, system, or even technology.

Perfect stream is also known as duplicate stream in some markets. Perfect stream protection allows an operator to split a single multicast stream (single S,G and common SSRC) into two different transmission paths that may have different transmission characteristics, such as latency or jitter. Instead of selecting one stream for retransmission to the client, the perfect stream protection feature evaluates each stream packet-by-packet, selecting the first, valid packet for retransmission.

A circular buffer is used for perfect stream protection which incorporates both packet-by-packet selection (based on RTP sequence number/timestamp and SSRC) and a re-ordering function whereby any out-of-sequence packets are placed into the buffer in order, therefore creating a corrected, in-order stream.

Playout rate is a function in ingest rate, however because the two streams may be delayed between one-another a few assumptions are made:

• The first arriving packet is always put into the buffer, allowing for the backup medium to wander in terms of latency and jitter.

• Because the source is the same, the rate at which a packet is put into the buffer (from either stream) can be assumed to be the normal bitrate.

The output RTP stream is always maintained in-sequence and the playout speed is always controlled. A moving window calculated against the time stamp smooths jitter that may occur between packets or the two contributing streams. The playout stream is described in Perfect stream selection.

This section describes perfect stream protection and provides details about packet selection on playout.

The following terminology is used in this section:

• TNC is an acronym for Technically Non-Conformant.

• QoS is an acronym for Quality of Service.

• POA is an acronym for Program Off Air.

• TNC event (also known as impaired event) refers to a trap/alarm that detects an impairment event and is therefore termed TNC.

  An impaired event is said to have occurred if:

  • A PAT/PMT syntax error occurs in that second.

  • Continuity counter errors were detected.

  • PAT /PMT/PCR PIDs were not present in the video stream for a time period equal to or greater than the configured TNC value in the respective alarm.

    The default value of the impaired threshold in terms of milliseconds is:

    • PAT (100 ms)

    • PCR (100 ms)

    • PMT (400 ms)

  • An unreferenced PID is seen in the video stream which has not been referred in the PMT.

• TNC seconds (also known as impaired seconds) refer to the number of seconds elapsed before an impaired event was detected and a TNC SNMP trap was sent. Although multiple TNC events may have occurred within a second, counters in the show>video>channel>analyzer command only increment once per second.

• QoS event (also known as degraded event) refers to a trap/alarm that detects a degraded event and is therefore termed QoS. A QoS event is said to have occurred if PAT/PMT/PCR PIDs are absent in the video stream for a time period equal to or greater than the configured QoS value in their respective alarms.

  The default value of the degraded threshold in terms of milliseconds is:

  • PAT (200 ms)

  • PCR (200 ms)

  • PMT (800 ms)

• QoS seconds (also known as degraded seconds) refer to the number of seconds elapsed before a degraded event was detected and a QoS SNMP trap was sent. Although multiple QoS events may have occurred within a second, counters in the show>video>channel>analyzer command only increment once per second.

• POA event (also known as error event) refers to a trap/alarm that detects an error event and is therefore termed POA.

  A POA event has occurred if:

  • A synchronization loss error has occurred for that particular second. A synchronization loss is said to have occurred if more than 1 consecutive synchronization byte error is seen in the stream.

  • PAT/PMT/PCR PIDs are absent from the video stream for a time period equal to or greater than the configured POA value.

    The default value of the degraded threshold in terms of milliseconds is:

    • PAT (500 ms)

    • PCR (500 ms)

    • PMT (2000 ms)

  • Traffic loss has occurred for that particular second.

  • A transport error indicator or TEI indicator is set in the transport stream packet header for that particular second in the video stream.

• POA seconds (also known as error seconds) refer to the number of seconds elapsed before an errored event was detected and a POA SNMP trap was sent. Although multiple POA events may have occurred within a second, counters in the show>video>channel>analyzer command only increment once per second.

• Good seconds refer to the number of seconds where there are no impaired, degraded, or error events.

PID stats are described in PID stats — description of fields

To address interval statistics, except for the PID statistics all other statistics described above have interval statistics. Information can be obtained about stream status for the last 1 minute, 5 minute, and 15 minute interval.

MDI - Media Delivery Index (RFC 4445, A Proposed Media Delivery Index (MDI))

• Delay Factor (RFC 4445)

  The delay factor is a value which indicates the minimum amount of time a STB buffers to resolve network jitter (that is, it is the minimum STB buffer depth in ms). RTP timestamp is used as the definitive time indicator (the notional drain rate).

• Loss Rate (RFC 4445)

  The Media Loss Rate is the number of media (Transport Stream) packets lost over a specific time interval. This is reported in TS/sec. Each RTP packet lost is assumed to have 7 TS packets lost.

In many instances IPTV operators are unable to identify the cause of visual impairments which are present in almost every video distribution network because the IPTV network has so many moving parts While head end transport-stream monitoring; full reference video analysis (comparing the source content to the encoded output), and; STB probes allow an operator to establish whether the contribution source, the encoder, or the network is the problem the network is a very complex thing.

Operators can use another measurement point in the network, just before the last mile such that network faults can be characterized as being between the head end and last mile (transport) or in the last-mile itself.

The multicast video quality monitoring solution provides an inspection point for the multicast video stream that is combined with other analysis methods to create a full view of video issues and help troubleshoot the part of the network causing the issue.

Video quality monitoring is one part of a video assurance program and is combined with:

• TS analysis on the encoder output (to detect encoder errors)

• Full-reference PSNR and PQR on the encoder output (to detect over-encoding, noise and other contribution or encoding artifacts)

• STB reporting (such as packet-loss, RET events, packet errors) from the entire STB population

• STB probes performing full-reference monitoring (against test streams)

• STB probes performing channel-change times, estimated PSNR, and so on

Multicast video monitoring within the network can be positioned as complementary to STB reporting and head end analysis, and but should not attempt to perform either of these functions. Because the network node is not capable of decrypting a MPEG transport stream is primarily used to identify correctable and uncorrectable network errors, correlate them with network events (such as routing re-convergence, interface failure, and so on) and provide summary reports and alarms.

For operators who do not have existing STB probes or reporting, a network-based VQM solution can provide insight into quality issues the network may be contributing to, possibly reducing the amount of STB probe investment that is needed. (that is, both probes and the 7750 SR VQM reports many of the same issues in terms of picture quality, fewer probes are needed to test channel change delay, and so on).

The metrics which VQM can report are based on the use of RTP streams which provide per-packet sequencing and an indication of picture type. These two parameters along with measured bitrate allow VQM to produce estimated MOSv scores for both stream ingress (uncorrected) and stream egress (corrected) outputs.

Reportable metrics include:

• Relevant SCTE-143 error counters

  • PAT

  • PMT

  • PCR

  • transport errors, and so on

• ETSI TR 101 290

  • PID

  • SI repetition

  • degraded blocks/intervals, and so on

• MDI (RFC 4445)

• forwarded and impaired I-/B-/P-frame counts

• GOP length

• video/audio/stream bitrate

These metrics are collected for each multicast group and have relevant parameters. Use the command show video channel analyzer address group-address detail to generate a numeric metrics summary report for a specific multicast group. Other information that is also captured by VQM but can only be expressed on a per-PID basis uses the command show video channel pid address group-address. The per-PID information captured by VQM includes:

• CC Err secs
• TEI Err secs
• Absent Err secs

The following is example output generated by the show video channel analyzer address group-address detail command:

*A:vmq-11# show video channel analyzer address 239.0.1.1 detail 

===============================================================================
Video channel analyzer detail
===============================================================================
  Channel number : 1
-------------------------------------------------------------------------------
Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
MDI Delay Factor : 4                    MDI Loss Rate    :        0
Good Secs        : 0                    
 

===============================================================================
GOP Stats
===============================================================================
                    Min                 Max                 Avg
-------------------------------------------------------------------------------
GOP Length          10                  31                  24
Frames/Sec          21                  28                  25

===============================================================================
Frame Stats
===============================================================================
                    I-Frame             P-Frame             B-Frame
-------------------------------------------------------------------------------
Good                42                  957                 0
Bad                 0                   0                   0

===============================================================================
Error Stats
===============================================================================
                    POA Events          QoS Events          TNC Events
-------------------------------------------------------------------------------
PAT Rep             0                   1215                0
PMT Rep             0                   0                   0
PCR Rep             0                   0                   1
PAT Syntax Err      -                   0                   -
PMT Syntax Err      -                   0                   -
Sync Byte Err       -                   0                   -
Sync Loss           0                   -                   -
Unref PID           -                   -                   34600
Traffic Loss        0                   -                   -
-------------------------------------------------------------------------------
Overall             30285               77                  4238
-------------------------------------------------------------------------------
Reoccurring events only increment counter once every second

-------------------------------------------------------------------------------
Number of channels : 1
===============================================================================


*A:vmq-11# show video channel pid address 239.0.1.1

===============================================================================
Video Channel PID
===============================================================================
Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
PID              : 0                    PID Type         : pat
MPEG Stream Type : 0                    Is PCR PID       : No
Cc Err Secs      : 0                    TEI Err Secs     : 0
Absent Err Secs  : 0                    PID Bitrate      : 0

Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
PID              : 100                  PID Type         : pmt
MPEG Stream Type : 0                    Is PCR PID       : No
Cc Err Secs      : 0                    TEI Err Secs     : 0
Absent Err Secs  : 0                    PID Bitrate      : 0

Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
PID              : 101                  PID Type         : video
MPEG Stream Type : 27                   Is PCR PID       : Yes
Cc Err Secs      : 0                    TEI Err Secs     : 0
Absent Err Secs  : 0                    PID Bitrate      : 5564800

Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
PID              : 201                  PID Type         : audio
MPEG Stream Type : 3                    Is PCR PID       : No
Cc Err Secs      : 0                    TEI Err Secs     : 0
Absent Err Secs  : 0                    PID Bitrate      : 204544

Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
PID              : 202                  PID Type         : audio
MPEG Stream Type : 3                    Is PCR PID       : No
Cc Err Secs      : 0                    TEI Err Secs     : 0
Absent Err Secs  : 0                    PID Bitrate      : 132352

Service Id       : 31905555             Interface Name   : vi-1
Group Address    : 239.0.1.1            Source Address   : 10.10.10.10
PID              : 401                  PID Type         : other
MPEG Stream Type : 6                    Is PCR PID       : No
Cc Err Secs      : 0                    TEI Err Secs     : 0
Absent Err Secs  : 30310                PID Bitrate      : 0

Number of pids for this channel: 6 
                                   
-------------------------------------------------------------------------------
Number of channels : 1
===============================================================================

Event alarms are reported by log, syslog, or SNMP. The following is an example of a trap:

1 2017/02/11 18:11:20.42 UTC WARNING: VIDEO #2009 Base Video[1/video-300]
Service Id - 300, Video interface - video-300, Group address - 192.0.2.6,  Source address - 10.20.13.2 Last 10 seconds of analyzer state is good good good  good good good good good good poa

A trap is only raised when a POA, QoS, or TNC event occurs within the last 10 seconds. The trap captures events within the last 10 seconds. In the example above, the first nine seconds were ‟good”, which indicates that no events occurred and that every single RTP packet was received. At the 10-second mark, a POA event occurred, which triggered the SNMP trap. This sampling continues every 10 seconds. If an event (POA, QoS, or TNC) continues to be detected, an SNMP trap is raised every 10 seconds.

When the analyzer detects 10 seconds of a ‟good” condition, another trap is raised to clear the alarm for the multicast (S,G). Subsequent alarms are raised and SNMP traps are triggered only when the analyzer detects another event (POA, QoS, or TNC).

61 2016/10/18 15:40:56.83 UTC WARNING: VIDEO #2010 Base Video[1/video-300]

Analyzer state is cleared for - Service Id - 300, Video interface - video-300, Group address - 192.0.2.6, Source address - 10.20.13.2

VQM is an optional module available on the input side, or output side of the video ISA. On input, it is applied before perfect stream protection. Conversely when on the output side it is applied only to multicast streams after perfect stream protection.

Because of the large number of channels and the nature of measuring input and output sides, VQM is highly reliant on the use of RTP extensions to provide relevant transmission metrics to the VQM analysis module. In a typical head end, a multicast stream is scrambled to encrypt its video or audio. When this encryption occurs, it is typical for the entire payload of the transport stream (for the nominated PID) to be completely scrambled. The consequence of such is that the video and audio PES headers, which reveal much about the picture and timing information, are unavailable to the VQM program.

VQM uses intelligent RTP re-wrapping. RTP re-wrapping is a prerequisite for ad insertion and Fast Channel Change (FCC) and involves marking packets before encryption based on the picture type (most importantly, the start of the I frame of IDR frame in H.264.

The VSA as currently defined, re-multiplexes each transport stream into a new RTP packet. By doing so it allows the separation of different picture types into their own respective RTP packets, and the separation of audio packets from video packets to allow different synchronization in events of FCC. In effect, it pulls the elementary streams back into their component forms while retaining the syntax and structure of the MPTS.

For information about VSAs, see the 7450 ESS, 7750 SR, 7950 XRS, and VSR System Management Guide.

Meanwhile, additional information can be made available, before scrambling, of the picture information for quality analysis. The quality analysis performed by the VQM module emphasizes impairments caused by network issues and transport stream syntax given the relative proximity of the router to the customer.

When the video ISA is deployed alongside the ALU VSA re-wrapper, a custom RTP header extension is sent with each RTP packet. The RTP header is shown in RTP header.

Where:

B (Frame Begin Flag): set if a frame starts in this packet
 E (Frame End Flag): set if a frame finishes in this packet
 ST (Stream Type)
 00 video
 01 audio
 10 data/padd/other
 11 Reserved
 S (Switch bit): set to 1 in all RTP packets from the moment
 the client should do the IGMP join (rewrap does not fill it)
 r: reserved (set to 1)
 PRI: Packet Priority (coarse)
 FPRI: Fine-grained priority
 PRI FPRI dec DSCP
 --- ---- --- ----
 3 7 31 AF41 Video IDR frame
 3 0 24 AF41 Audio
 2 0 16 AF41 Reference frame (P in MPEG2, I or P or some Bs in AVC)
 1 7 15 AF42 Non-reference frame (most Bs in MPEG2, some Bs in AVC)
 1 5 13 AF42 Trans-GOP frames, undecodable in some circumstances (some Bs in MPEG2)
 0 4 4 AF43 Rest of cases (data, secondary videos, etc)
 0 1 1 AF43 Padding packets
where AF41=100010, AF42=100100, AF43=100110 (DSCP bits in the IP header)

The following sections provide an overview of RET and FCC.

For each fast channel change, a new RTCP session is initialized, whereas for retransmission, the same RTCP session is always reused, with the same source and destination ports. The RTCP session duration is based on a timeout configuration, and a separate timeout parameter is available for FCC and RET under config>mcast-mgmt>mcast-info-policy>video-policy>video-interface, namely the fcc-session-timeout and ret-session-timeout parameters. As the FCC RTCP session timeout is generally shorter than the RET session timeout, the recommendation is to configure the FCC RTCP session timeout to a lower timeout value, accounting for the time required to complete a fast channel change and complete the multicast handoff. This strategy frees up RTCP sessions for other subscribers and improves efficiency.

The CLI command show isa video-group video-group-id displays the peak egress bandwidth and sessions per ISA. Each peak value is also marked with a timestamp.

There are configurable watermarks for bandwidth and session consumption. The watermarks generate SNMP traps or log events when the ISA has reached the bandwidth or session thresholds. The egress bandwidth and session watermarks are configurable for FCC and RET separately, and also for FCC and RET together. The SNMP trap or log event is generated as the configured watermark is exceeded and is cleared if it falls below 10% of the watermark. For example, if the maximum egress rate is 10 Gb/s and the watermark is set at 90%, the alarm is generated when the egress rate exceeds 9 Gb/s (90% of 10 Gb/s) and the alarm is cleared if the egress rate falls below 10% at 8.1 Gb/s (10% of 9 Gb/s = 0.9 Gb/s, and 9 Gb/s - 0.9 Gb/s = 8.1 Gb/s).

The following applies to video support for the ESA:

• The FCC and RET applications are supported.

• VQM and perfect stream are not supported at this time.

• SR-1/1s/2s/7/12/12e/7s/14s are currently supported.

• ISA and ESM must not be used in the same video group.

The FCC solution requires the STB to switch from unicast to multicast after the fast channel change completes. The STB uses IGMP to switch to multicast. In some cases, the multicast process is delayed. Delay may occur because of IGMP processing delay, authentication delay, or network delay. The extended-unicast command, which is used for IP Video for Live, delays the IGMP for up to 5 minutes. Nokia recommends enabling this command only in implementations where multicast delivery is delayed beyond 1.5 seconds. By default, extended unicast is disabled to ensure the optimal bandwidth for unicast to multicast handover.

The main entities of video configurations are:

• video group

• multicast information policy

  • a video policy to configure video interface properties

  • multicast bundles and channels to associate bundles/channels with video groups

• within a service, configuring video interfaces and their associations with video groups

Video services configuration elements shows various configuration elements and how they are associated by configuration.

A video interface within a service can have multiple IP address, and their association with the video interfaces within the video policy are based on IP addresses. Support for multiple video interface IP addresses for a specific video interface allows video characteristics (burst rate, retransmission format, and so on) for the channels associated with the video interface to be based on the IP address on which the request is received.

Both the bundle/channel configuration and the video interface configuration within the service are associated with a specific video group. If the request is received on a video interface for a channel not serviced by the video group associated with the video interface, the request is invalid and is dropped. Video services configuration elements displays an example of this is a request for mc-range2 received on IP1, IP2 or IP3. A request for mc-range2 would only be valid on IP4.

As with other multicast information policies, the bundle name default is a special bundle and is reserved for setting of default values. If a video parameter is not explicitly set in a bundle/channel, the value set in the default bundle is used.

The following output displays configurations of VQM with packet selection.

*A:SR-7/Dut-C>config>mcast-mgmt># info
----------------------------------------------
            multicast-info-policy "vqm" create
                bundle "ixia" create
                    channel "10.5.5.6" "10.5.5.7" create
                        admin-bw 20000
                        video
                            video-group 4
                            rt-buffer-size 1000
                            analyzer
                                alarms
                                    cc-error
                                    pat-repetition tnc 400 qos 600 poa 700
                                    pat-syntax
                                    pid-pmt-unref
                                    pmt-repetition tnc 2300 qos 2500 poa 2700
                                    pmt-syntax
                                    vid-pid-absent 5000
                                    non-vid-pid-absent 5000
                                    pcr-repetition tnc 400 qos 600 poa 700
                                    scte-35
                                    tei-set
                                    ts-sync-loss
                                exit
                            exit
                            stream-selection source1 192.168.2.1 intf1 "ineo-ingress1" 
source2 192.168.2.1 intf2 "ineo-ingress2"
                        exit
                        source-override "192.168.2.1" create
                        exit
                    exit
                exit
                bundle "default" create
                exit
            exit
----------------------------------------------
*A:SR-7/Dut-C>config>service# info
----------------------------------------------
        customer 1 create
            description "Default customer"
        exit
        ies 300 customer 1 vpn 300 create
            description "Default Ies description for service id 300"
            video-interface "video-300" create
                video-sap 4
                exit
                address 10.20.255.254/16
                channel 10.5.5.6 source 192.168.2.1 channel-name "Ineoquest-1"
                    zone-channel 10.5.5.6 source 10.20.0.1 adi-channel-name "Ineoquest-
1-1"
                exit
                adi
                exit
                no shutdown
            exit
            service-name "XYZ Ies 300"
            no shutdown
        exit
----------------------------------------------
*A:SR-7/Dut-C>config>service#

*A:SR-7/Dut-C>config>router# info
----------------------------------------------
#--------------------------------------------------
echo "IP Configuration"
#--------------------------------------------------
        interface "ineo-ingress1"
            address 10.200.16.1/24
            port 3/2/12
            ingress
                filter ip 100
            exit
        exit
        interface "ineo-ingress2"
            address 10.200.17.1/24
            port 5/1/1
            ingress
                filter ip 200
            exit
        exit
        interface "ixia-egress"
            address 10.200.15.1/24
            port 3/2/15
        exit
        interface "system"
            address 10.20.3.1/32
        exit
        ecmp 2
        multicast-info-policy "vqm"
        static-route 192.168.2.1/32
            next-hop 10.200.16.2
               no shutdown
            exit
            next-hop 10.200.17.2
               no shutdown
            exit
        exit
#--------------------------------------------------
echo "IGMP Configuration"
#--------------------------------------------------
        igmp
            interface "video-300-D"
                static
                    group 10.5.5.6
                        source 192.168.2.1
                    exit
                exit
            exit
            interface "video-300-D2"
                static
                    group 10.5.5.6
                        source 192.168.2.1
                    exit
                exit
            exit
            interface "ixia-egress"
                static
                    group 10.5.5.6
                        source 10.20.0.1
                    exit
                exit
            exit
        exit
#--------------------------------------------------
echo "PIM Configuration"
#--------------------------------------------------
        pim
            rpf-table rtable-m
            interface "video-300"
            exit
            interface "ineo-ingress1"
                multicast-senders always
            exit
            interface "ineo-ingress2"
                multicast-senders always
            exit
            rp
                static
                exit
                bsr-candidate
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
        exit
----------------------------------------------
*A:SR-7/Dut-C>config>router#
*A:SR-7/Dut-C>config>isa# info
----------------------------------------------
        video-group 4 create
            analyzer
            stream-selection
            primary 3/1
            no shutdown
        exit
----------------------------------------------
*A:SR-7/Dut-C>config>isa#

The following output displays configurations of VQM without packet selection.

----------------------------------------------
*A:SR-7/Dut-C>config>service# info
----------------------------------------------
        customer 1 create
            description "Default customer"
        exit
        ies 300 customer 1 vpn 300 create
            description "Default Ies description for service id 300"
            interface "linux-ingress"  create
                address 10.10.33.228/24
                sap 3/2/17 create
                    description "sap-300-10.10.33.228"
                exit
            exit
            interface "linux-egress"  create
                address 10.10.34.228/24
                sap 3/2/7 create
                    description "sap-300-10.10.34.228"
                exit
            exit
            video-interface "video-300" create
                video-sap 2
                exit
                address 10.20.13.1/24
                channel 10.5.5.6 source 192.168.2.1 channel-name "A2-SP3"
                    zone-channel 10.5.5.6 source 10.20.13.2 adi-channel-name "A2-SP3-1"
                exit
                adi
                exit
                no shutdown
            exit
            service-name "XYZ Ies 300"
            no shutdown
        exit
----------------------------------------------
*A:SR-7/Dut-C>config>service# /configure router
*A:SR-7/Dut-C>config>router# info
----------------------------------------------
#--------------------------------------------------
echo "IP Configuration"
#--------------------------------------------------
        interface "system"
            address 10.20.1.1/32
        exit
        multicast-info-policy "A-server"
#--------------------------------------------------
echo "Static Route Configuration"
#--------------------------------------------------
        static-route 128.251.33.0/24
            next-hop 10.10.33.229
               no shutdown
            exit
        static-route 192.168.2.0/24
            next-hop 10.10.33.229
               no shutdown
            exit
        exit
#--------------------------------------------------
echo "IGMP Configuration"
#--------------------------------------------------
        igmp
            interface "video-300-D"
                static
                    group 10.5.5.6
                        source 192.168.2.1
                    exit
                exit
            exit
            interface "linux-egress"
                static
                    group 10.5.5.6
                        source 10.20.13.2
                    exit
                exit
            exit
        exit
#--------------------------------------------------
echo "PIM Configuration"
#--------------------------------------------------
        pim
            interface "linux-ingress"
                hello-interval 0
                multicast-senders always
            exit
            interface "linux-egress"
                hello-interval 0
            exit
            apply-to all
            rp
                static
                exit
                bsr-candidate
                    shutdown
                exit
                rp-candidate
                    shutdown
                exit
            exit
        exit
----------------------------------------------
*A:SR-7/Dut-C>config>router# /configure isa
*A:SR-7/Dut-C>config>isa# info
----------------------------------------------
        video-group 2 create
            analyzer
            primary 2/1
            no shutdown
        exit
----------------------------------------------
*A:SR-7/Dut-C>config>isa# /configure mcast-management
*A:SR-7/Dut-C>config>mcast-mgmt># info
----------------------------------------------
            multicast-info-policy "A-server" create
                bundle "LiveTv" create
                    channel "10.5.6.243" "10.5.6.243" create
                        admin-bw 3000
                        video
                            video-group 2
                            rt-buffer-size 1000
                        exit
                    exit
                    channel "10.5.5.6" "10.5.5.6" create
                        admin-bw 5000
                        video
                            video-group 2
                            rt-buffer-size 1000
                            analyzer
                                alarms
                                    cc-error
                                    pat-repetition tnc 200 qos 400 poa 600
                                    pat-syntax
                                    pid-pmt-unref
                                    pmt-repetition
                                    pmt-syntax
                                    vid-pid-absent 1000
                                    non-vid-pid-absent 1000
                                    pcr-repetition tnc 200 qos 400 poa 600
                                    scte-35
                                    tei-set
                                    ts-sync-loss
                                    report-alarm severity tnc
                                exit
                            exit
                        exit
                        source-override "192.168.33.37" create
                        exit
                    exit
                exit
                bundle "default" create
                exit
                bundle "mp2ts-ads" create
                    channel "10.4.5.1" "10.4.5.254" create
                        admin-bw 5000
                        video
                            video-group 2
                            rt-buffer-size 1000
                        exit
                    exit
                exit
            exit
----------------------------------------------
*A:SR-7/Dut-C>config>mcast-mgmt>#

The following sections provide configuration examples for the RET client, RET server and FCC server.