--- Digital Program Insertion resource management ---
All DCMD9900/D9901 products equipped with one or more Co-Processor cards configured for DPI functionality.
This application note provides instructions on how to manage the available Digital Program Insertion (DPI) resources so to avoid splice performance issues.
This application note is written for:
Cisco Advanced Services personnel
The Co-Processor Card of the DCM is able to perform many different video manipulation processes like DPI, transrating, and delaying service components. Each process consumes a portion of the total available Co-Processor Card processing power. The primary factors that determine the processing power requirements are the process itself (DPI or transrating), the bit rate of the video stream, and the number of audio streams in the service.
Note: Transrating requires continuous processing power from a Co-Processor Card while DPI only requires additional processing power at the moment of execution.
When ordering a DCM, the limitations are outlined through the sales configurator but in operational environments the customer may deviate from these limitations and as a result, experience performance drops that affect the available resources for splicing. This is especially true when splices are scheduled simultaneously.
Limiting factors are:
The number of HD video streams processed and bitrates
The number of SD video streams processed and bitrates
The number of audio components within the services and the audio bitrates
The number of streams being transrated
The number of streams provisioned for DPI
The video quality optimization settings
The installed software and firmware version
If the installed version of DCM code is 8.00.81, SD video bandwidth is up to 3.75Mbps, HD video bandwidth is up to 16 Mbps, and the video optimization setting is set to “quality”, then here is the resulting capacity per co-processor:
# of service / co-processor
Cisco has a tool available (“DPI Capacity Check – Configurator Vxx.yy.zz.xls”) that simulates the required processing power based on above factors. Contact your SPVTG service organization to get a copy.
Software Features in 8.02.xx:
From SW version 8.2 onwards, a load management algorithm is added to the GUI.
The web browser user interface of the DCM will hereby display the following theoretical calculated processing load figures:
Current processing load: the current processing load of the Co-Processor Card
Maximum processing load: the maximum processing load of the Co-Processor Card since reset
Worst Case processing load: the processing load of the Co-Processor Card as if all configured DPI channels for this card are splicing simultaneously.
Furthermore, it is possible to block splices if all DPI capacity has been consumed.
Hi, I config sbfd for SR-TE policy，but the bfd couldn't up with version 7.3.1. Configuration as follows: SBFD Reflector: interface Loopback0 ipv4 address 22.214.171.124 255.255.255.255 ! sbfd local-discriminato...
Hi, Guys, When i reload a NSO package it shows following error: >>> System upgrade is starting.>>> Sessions in configure mode must exist to operational mode.>>> No configuration changes can be performed until upgrade h...
Hi, I'm running a lab with some XRv9000 (v7.3.1) and an Opendaylight controller (v13.1 (Aluminium)). The goal is to push a Segment Routing LSP from the PCE over the IOS XRv, which is working. However when querying my controller for the...