Cisco cBR Converged Broadband Routers Video Features
First Published: March 17, 2016
Americas Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408 526-4000
800 553-NETS (6387)
Fax: 408 527-0883
© 2016
Cisco Systems, Inc. All rights reserved.
CONTENTS
CHAPTER 1
PowerKEY VOD 1
Information About PowerKEY VOD 1
Overview of PowerKEY VOD 1
How to Configure PowerKEY VOD 2
Configuring the Encryption Type on the Line Card 2
Configuring the Encrypted Virtual Carrier Groups 2
Verifying the Encrypted Virtual Carrier Groups Configuration 3
Configuring the Service Distribution Groups and Binding 3
Configuring the Logical Edge Device and GQI Protocol 3
Verifying the PowerKEY VOD Configuration 4
Troubleshooting Tips 6
Configuration Examples 7
Example: Configuring Encryption Type on the Line Card 7
Example: Configuring Encrypted Virtual Carrier Groups 8
Example: Configuring Service Distribution Groups and Binding 8
Feature Information for PowerKEY VOD 8
CHAPTER 2
Table-Based Video and VPME Encryption 11
Overview of VPME 11
Prerequisites for VPME 11
Restrictions for VPME 12
How to Configure Table-Based Video Session 12
Configuring Table-Based Video 12
Configuring Table-Based Session : VEI Input Port-Based 12
Configuring Table-Based Session :VEI Bundle-Based 13
Virtual Edge Input Bundling 14
Verifying Table-Based Video Configuration 14
Troubleshooting Video and VPME Encryption 15
Cisco cBR Converged Broadband Routers Video Features
iii
Contents
Output State is OFF 15
Output Status is Idle or Pending 17
Input State is Active and not Active PSI 18
Abnormalities on the Output 19
Configuring CEM Connectivity for PME Encryption 20
Configuring VODS-ID 20
Configuring CEM IP and Port 20
Configuring Management IP 20
Verifying CEM Connectivity 21
Troubleshooting Tips 21
Connectivity with CEM is Lost 21
How to Configure VPME Encryption 22
Enforcing Data Stream Encryption Type 22
Configuring Virtual Carrier Group 22
Verifying VPME Encryption Configuration 23
Troubleshooting Tips 24
No PMT at the Output 24
Configuration Examples For VPME Encryption 25
Use Cases or Deployment Scenarios 25
Topology 25
Feature Information for Table-Based Video and VPME Encryption 26
CHAPTER 3
Video QAM Replication 27
QAM Replication 27
Information About Replication 27
Overview of QAM Replication 27
Benefits of QAM Replication 28
Prerequisites for Replication 28
Restrictions for QAM Replication 29
Configuring Replication for Table-Based or Session-Based Video 29
Verifying Replication of Table Based Video Sessions 30
Configuration Examples 31
Feature Information for Replication 31
CHAPTER 4
D6 Discovery Protocol 33
Cisco cBR Converged Broadband Routers Video Features
iv
Contents
Information About D6 Discovery Protocol 33
Overview of the D6 Discovery Protocol 33
Prerequisites for D6 Discovery Protocol 34
How to Configure the D6 Discovery Protocol 35
Configuring the Mandatory D6 Discovery Protocol Parameters 35
Verifying the D6 Discovery Protocol Configurations 37
Troubleshooting the D6 Mandatory Parameters Configuration 37
Configuring the D6 Discovery Protocol Optional Parameters 38
Verifying the Hold Time and Timeout Settings 39
Troubleshooting the D6 Optional Parameters Configuration 39
Example: D6 Discovery Protocol Configuration 39
Deployment Scenario for the D6 Discovery Protocol 40
Feature Information for D6 Discovery Protocol 41
CHAPTER 5
Switched Digital Video 43
Switched Digital Video Services 43
Session Cloning 43
Redundant Multicast Sources 43
Benefits of Switched Digital Video 45
Prerequisites for Switched Digital Video 45
Restrictions for Switched Digital Video 45
Information About Switched Digital Video 45
QAM Sharing 45
QAM Replication 45
MPTS Pass-through Session 46
How to Configure the Switched Digital Video Services 46
Configuring Multicast Routing 46
Configuring Multicast Label 46
Configuring Multicast Table-based Sessions 47
Configuring Source Switching 47
Verifying Switched Digital Video Configuration 48
Troubleshooting Switched Digital Video Configuration 49
Configuration Examples for Switched Digital Video 49
CHAPTER 6
Video MIBs 53
Cisco cBR Converged Broadband Routers Video Features
v
Contents
SCTE-HMS-MPEG-MIB 53
SCTE-HMS-QAM-MIB 55
Cisco cBR Converged Broadband Routers Video Features
vi
CHAPTER
1
PowerKEY VOD
PowerKEY Video On Demand refers to video content that is chosen by the subscriber and streamed specifically
to the subscriber. The content is encrypted using PowerKEY conditional access through a video session that
is created on the Cisco cBR-8 specifically for each request.
Contents
• Information About PowerKEY VOD, page 1
• How to Configure PowerKEY VOD, page 2
• Configuration Examples, page 7
• Feature Information for PowerKEY VOD, page 8
Information About PowerKEY VOD
PowerKEY Video On Demand is used in a Cisco cable environment to provide edge-encrypted video-on-demand
movies and other content to subscribers. The subscriber selects the content via an on-screen selection and the
set-top box (STB) notifies the head-end of the request. The head-end equipment receives the request from the
STB and triggers the Session Resource Manager (SRM) to create an encrypted video session on the
Cisco cBR-8. At the same time, the video streamer is triggered to begin streaming the content in a UDP stream
to the Cisco cBR-8. The Cisco cBR-8 receives an unscrambled video content, encrypts it using PowerKEY,
combines the scrambled stream with other content destined for the RF carrier, and transmits the RF signal
from the RF port.
PowerKEY VOD allows the operator to provide secure, encrypted video streams to a particular subscriber
over the RF plant.
Overview of PowerKEY VOD
PowerKEY VOD allows the operator to provide secure, encrypted video streams to a particular subscriber
over the RF plant.
Cisco cBR Converged Broadband Routers Video Features
1
PowerKEY VOD
How to Configure PowerKEY VOD
How to Configure PowerKEY VOD
• Configuring the Encryption Type on the Line Card
• Configuring the Encrypted Virtual Carrier Groups
• Configuring the Service Distribution Groups and Binding
• Configuring the Logical Edge Device and GQI Protocol
• Verifying the PowerKEY VOD Configuration
Configuring the Encryption Type on the Line Card
The Cisco IOS-XE Release 3.18.0S supports PowerKey and PME encryption CA systems, but allows only
one encryption type to be installed on the line card. There are two levels in the CA system. The lower level
scrambler, which encrypts the actual data streams and the upper level conditional access system, which handles
how the control words are transferred from the encrypting device to the decrypting device.
To specify the type of encryption used to scramble the data streams, complete the following procedure:
configure terminal
cable video
encryption
linecard slot/bay ca-system [pme | powerkey] scrambler scrambler-type
exit
PowerKey currently supports DES and Privacy Mode Encryption (PME) supports DVS-042 type of encryption,
as given in the following table:
Table 1: Supported Encryption Types and Scrambler Modes
Encryption Type
Scrambler Mode
PME
DVS-042
PKEY
DES, 3DES
Verifying the Encryption Configuration
To verify the encryption type of a line card, use the show cable video encryption linecard command as
shown in the example below:
show cable video encryption linecard 7/0
Line card: 7/0
CA System
Scrambler
================================
powerkey
des
Configuring the Encrypted Virtual Carrier Groups
For the sessions to be encrypted on the Cisco cBR-8, the Virtual Carrier Groups (VCGs) must be specified
as encrypt and the line card must be configured as encrypted. In this way, the operator can choose the carriers
Cisco cBR Converged Broadband Routers Video Features
2
PowerKEY VOD
Configuring the Service Distribution Groups and Binding
on the line card that support encryption and other carriers that support only clear or pre-encrypted sessions.
Each encrypted carrier consumes an encrypted carrier license.
For the VCG to be used in a Logical Edge Device (LED) that is configured with the GQI protocol, each RF
carrier must be assigned with an output port number. The LED must be configured with the Generic QAM
Interface (GQI) protocol in order to support session-based operation.
Note
For PowerKEY VOD, you have to specify the session-based operation.
To configure the VCG, complete the following procedure:
configure terminal
cable video
virtual-carrier-group vcg-name
rf-channel channel range tsid tsid range output-port-number port num range
virtual-edge-input ip-address [vrf] vrf name input-port-number number
encrypt
exit
Verifying the Encrypted Virtual Carrier Groups Configuration
To verify the encrypted VCGs configuration, use the show cable video virtual-carrier-group name command
as shown in the example below:
show cable video virtual-carrier-group name vod-grp
Configuring the Service Distribution Groups and Binding
The Service Distribution Group (SDG) is a collection of one or more RF ports and defines the physical
slot/bay/port to be used in a video service. After you configure an SDG, you can bind a VCG to an SDG. The
binding connects the carriers defined in the VCG to the physical port listed in the SDG. After binding, a path
from the Virtual Edge Input (VEI) is mapped to the RF ports.
To configure the SDGs and binding, complete the following procedure:
configure terminal
cable video
service-distribution-group sdg name id sdg number
onid onid for port
rf-port integrated-cable slot/bay/port
exit
bind-vcg
vcg vcg-name sdg sdg-name
end
Configuring the Logical Edge Device and GQI Protocol
The PowerKEY VOD feature on the Cisco cBR-8 is directed by an external Session Resource Manager (SRM)
that creates video sessions in response to a subscriber selecting VOD content to watch on the set top box. You
Cisco cBR Converged Broadband Routers Video Features
3
PowerKEY VOD
Verifying the PowerKEY VOD Configuration
must configure a Logical Edge Device (LED) supporting the GQI protocol on the Cisco cBR-8 to support the
PowerKEY VOD.
The LED is configured with the GQI protocol as the LED communicates with an external SRM using the GQI
protocol. The GQI protocol supports the creation and deletion of sessions on the carriers owned by this LED.
Tip
Use the following command to get the chassis MAC address:
Router#show diag all eeprom detail | include
Chassis MAC Address : 54a2.740e.2000
MAC Address block size : 1024
MAC
Using the Chassis MAC as a basis, increment the least significant number to give a unique identifier
(mac-address) for each LED. This number needs to be unique with respect to the GQI server and does not
really relate to a true MAC address. Thus, the number is irrelevant, but needs to be unique.
To configure the Logical Edge Device and GQI Protocol, complete the following procedure:
configure terminal
cable video
logical-edge-device led name id led number
protocol gqi
mgmt-ip management ip address
mac-address mac address from this chassis range
server ip address of srm
virtual-edge-input-ip ip addr for content [vrf] vrf name input-port-number num
vcg virtual edge qam name (may be multiple vcgs in an LED)
active n
end
Verifying the PowerKEY VOD Configuration
The PowerKEY encrypted VOD LED is active and communicates with the external SRM device after
configuring the encryption type on the line card, VCGs, binding of SDGs, and LED with GQI protocol are
completed.
To verify the Logical Edge Device configuration, use the show cable video logical-edge-device name led
name command (or) show cable video logical-edge-device id led number command as shown in the example
below:
show cable video logical-edge-device name pkvodled
Logical Edge Device: pkvodled
Id: 1
Protocol: GQI
Service State: Active
Discovery State: Disable
Management IP: 1.23.2.10
MAC Address: 54a2.740d.dc99
Number of Servers: 1
Server 1: 1.200.3.75
Reset Interval: 8
Keepalive Interval: 10
Retry Count:3
Number of Virtual Carrier Groups: 1
Number of Share Virtual Edge Input: 1
Number of Physical Qams: 20
Number of Sessions: 0
No Reserve PID Range
Cisco cBR Converged Broadband Routers Video Features
4
PowerKEY VOD
Verifying the PowerKEY VOD Configuration
Virtual Edge Input:
Input Port
VEI
Slot/Bay
Bundle
Gateway
ID
IP
ID
IP
----------------------------------------------------------------1
174.10.2.1
7/0
-
Verify the following:
• The service state of the LED should be active and the other fields must be same as the configured values.
• The connection to the remote SRM should be displayed to ensure that there is a valid network connection
to the SRM.
• Execute the show cable video gqi connections command. The following is the sample output when
the connection is not established to the SRM :
LED Management Server
Connection
Version Event
Reset
Encryption
ID IP
IP
Status
Pending Indication Discovery
--------------------------------------------------------------------------------1
1.23.2.10 1.200.3.75 Not Connected 0
0
Not Sent
Not Sent
The following is the sample output when the connection is established to the SRM:
LED Management Server
Connection
Version Event
Reset
Encryption
ID IP
IP
Status
Pending Indication Discovery
--------------------------------------------------------------------------------1
1.23.2.10 1.200.3.75 Not Connected 2
0
ACKED
ACKED
Once the connection is established, the SRM may create encrypted sessions on the carriers of the LED.
• To view the encrypted sessions, use the show cable video session logical-edge-device id led name
summary command as shown in the example below:
show cable video session logical-edge-device id 1summary
Video Session Summary:
Active
: 1
Off
: 0
UDP
: 1
Remap
: 1
Total Sessions: 1
Init
Blocked
ASM
Data
:
:
:
:
0
0
0
0
Idle
PSI-Ready
SSM
Passthru
:
:
:
:
0
1
0
0
• The individual session information can be displayed for the entire LED, for a particular port or line card.
The details of a single session may be displayed by specifying a session-id or session-name. To display
all the sessions on the LED, use the show cable video session logical-edge-device name led name
command as shown in the example below:
show cable video session logical-edge-device name pkvodled
Total Sessions = 1
Session Output Streaming Session Destination UDP
Output Input
Output Input
Id
Port
Type
Type
Port Program State
State Bitrate
------------------------------------------------------------------------------------1048576 1
Remap
UDP
174.101.1.1 4915 1
ACTIVE-PSI ON
732788
Output Encrypt Encrypt
Session
Bitrate Type
Status
Name
----------------------------------1715446 PowerKey Encrypted 0x0000000000001
If the session is encrypted and transmitted properly, the session is displayed as shown in the above
example. The input state is "ACTIVE-PSI". The output state is "ON". For PowerKEY encrypted sessions,
the Encrypt Type will be "PowerKey" and the Encrypt Status will be "Encrypted".
Cisco cBR Converged Broadband Routers Video Features
5
PowerKEY VOD
Verifying the PowerKEY VOD Configuration
If the session is created as a clear session, then the Encrypt Type will be "CLEAR" and the Encrypt
Status will be "-".
If the GQI connection is not in connected state or if the sessions are not in the proper states then,
troubleshoot the connection. For more information, see Troubleshooting Tips, on page 6.
Troubleshooting Tips
GQI Connection
GQI connection problems can be the result of a problem in the network, such as a problem in the external
SRM device, or in the Cisco cBR-8 configuration. The first problem is beyond the scope of this document,
however to verify the Cisco cBR-8 configuration, the management interface port must be configured properly
and be active (not shutdown).
Session Input State
• If a session's input state is "OFF" or another state that is not "ACTIVE_PSI" then the problem is related
to content receiving on the Cisco cBR-8. This could be a problem elsewhere in the head-end network
or with the video streaming device. The Virtual Edge Input address specified in the LED should match
the destination IP address used by the streaming device.
To display the LED, use the following command:
show cable video logical-edge-device id led number
• The Virtual Edge Inputs are listed in the output. Check the streaming device to ensure the destination
IP address matches the appropriate VEI. Additionally, verify whether the UDP port of the video content
from the streamer matches the UDP port shown in the session display on the Cisco cBR-8, using the
following command:
show cable video session logical-edge-device id led number
• The TenGigabitEthernet port where the VEI address is routed must not be in the shutdown state. To
check the appropriate interface, use the following command:
show interface TenGigabitEthernet slot/bay/port
Session Output State
• If a session's input state is "Active-PSI" and the output state is not "OFF", then the problem is related
to the physical port channel configuration. The output of the show logical edge device command also
shows all the carriers and their Admin and Operation state.
To display the carriers and their state, use the following command:
show cable video scg logical-edge-device id number
show cable video logical-edge-device id number
Integrated Physical Admin Operational TSID ONID Output VCG
SDG Encryption
Cable
QAM ID
State State
Port
ID
ID
Capable
----------------------------------------------------------------------------8/0/0:0
0
ON
UP
1
100
1
1
1
powerkey
8/0/0:1
1
ON
UP
2
100
2
1
1
powerkey
8/0/0:2
2
ON
UP
3
100
3
1
1
powerkey
8/0/0:3
3
ON
UP
4
100
4
1
1
powerkey
Cisco cBR Converged Broadband Routers Video Features
6
PowerKEY VOD
Configuration Examples
• If the output port corresponding to the session does not show "ON" for Admin State and an Operational
State as "UP", then there is a problem with the configuration.To display the output port details, use the
following command:
show cable video output-port output port number
Session Encrypt Status
• If an encrypted GQI session has an Output State or Encrypt Status of "Pending", it means there is a
problem with the PowerKEY encryption of the session, or it is possible the encryption on the session is
just getting ready to start. First the session command should be executed over a few seconds to ensure
that the session was not transitioning from Pending to Active. If the state is Pending, then there is a
problem with the encryption.
To troubleshoot this problem the operator can check the Scrambling Control Group (SCG) that corresponds
to this session. Using the session id from the session display, the SCG ID can be found using the following
command:
show cable video scg logical-edge-device idled number
LED 1 has 8137 SCGs on 128 carriers
SCG ID
Session ID LED
TSID ONID
-----------------------------------------68157683
1048819
1
1
100
68157684
1048820
1
1
100
To verify the SCG ID of the session, use the following command:
show cable video scg logical-edge-device id led number | inc session id
68157684
1048820
1
1
100
To verfiy the SCG session information, use the following command:
show cable video scg id SCG id
SCGid: 68157684
Status: SUCCESS
TSID:
1
ONID: 100
Nominal CP: 550
If the Status does not show SUCCESS, then there must be a problem with the Encrypted Key exchange
between the Cisco cBR-8 and SRM.
Configuration Examples
This section provides configuration examples for the PowerKEY VOD feature:
Example: Configuring Encryption Type on the Line Card
The following example shows how to create a management IP interface:
configure terminal
cable video
encryption
Cisco cBR Converged Broadband Routers Video Features
7
PowerKEY VOD
Example: Configuring Encrypted Virtual Carrier Groups
linecard 7/0 ca-system powerkey scrambler des
exit
Example: Configuring Encrypted Virtual Carrier Groups
The following example shows how to configure the QAM channels from 64 to 158. These channels are
encryption capable once the VCG is successfully bound to a Service Distribution Group. The sessions created
on these QAM carriers are encrypted using the scrambler installed on the line card.
configure terminal
cable video
virtual-carrier-group vod-group
rf-channel 64-158 tsid 64-158 output-port-number 64-158
virtual-edge-input-ip14.1.1.1 input-port-number 1
virtual-edge-input-ip14.2.1.1 vrf Video-VOD-Vrfinput-port-number 2
encrypt
exit
Example: Configuring Service Distribution Groups and Binding
The following example shows how to configure the service distribution groups and binding:
configure terminal
cable video
logical-edge-device pkvodled id 1
protocol gqi
mgmt-ip 1.20.2.10
mac-address 54ab.6409.dc99
server 1.200.3.75
virtual-edge-input-ip 174.10.2.1 input-port-number 1
virtual-edge-input-ip 174.11.2.1 vrf Video-VOD-Vrfinput-port-number 2
vcg vod-grp
active n
end
Feature Information for PowerKEY VOD
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software release,
feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An
account on http://www.cisco.com/ is not required.
Note
The below table lists only the software release that introduced support for a given feature in a given
software release train. Unless noted otherwise, subsequent releases of that software release train also
support that feature.
Cisco cBR Converged Broadband Routers Video Features
8
PowerKEY VOD
Feature Information for PowerKEY VOD
Table 2: Feature Information for PowerKEY VOD
Feature Name
Releases
Feature Information
PowerKEY VOD
Cisco IOS-XE Release 3.18.0S
This feature was introduced on the
Cisco cBR Series Converged
Broadband Routers.
Cisco cBR Converged Broadband Routers Video Features
9
PowerKEY VOD
Feature Information for PowerKEY VOD
Cisco cBR Converged Broadband Routers Video Features
10
CHAPTER
2
Table-Based Video and VPME Encryption
Table-based video is a configuration mode for video sessions. This feature statically maps UDP flows into
appropriate RF QAM channels. Each UDP flow is identified by the destination IP address of the MPEG
traffic and UDP port number. The configuration contains the input port number, which is resolved into a
unique destination IP address, the UDP port, and an output program number.
The Video on Demand (VOD) Privacy Mode Encryption (PME) enables the Cisco Edge QAM Manager
(CEM) to encrypt the VOD content streamed through Motorola/Arris VOD systems. PME encryption is
applicable for table-based sessions.
Contents
• Overview of VPME, page 11
• How to Configure Table-Based Video Session, page 12
• How to Configure VPME Encryption, page 22
• Configuration Examples For VPME Encryption, page 25
• Feature Information for Table-Based Video and VPME Encryption , page 26
Overview of VPME
The PME Video On Demand system integrates the encrypted VOD content within an Arris digital cable
headend. A VOD system provides the clear content while the Cisco cBR-8 and CEM are added to provide
encryption. The details on the usage of the CEM are described in this chapter. Every MSO site should have
the CEM application, which is the single entity connecting to the Arris Encryption Renewal System (ERS).
All the Cisco cBR-8s on this MSO site should connect to this CEM.
Prerequisites for VPME
To enable VPME encryption, the connection to the CEM should be configured. VPME is a licensed feature
and requires appropriate license on the chassis. The following connection should be configured:
• The video traffic flow on the Ten Gigabit interface.
• Table-based video sessions.
Cisco cBR Converged Broadband Routers Video Features
11
Table-Based Video and VPME Encryption
Restrictions for VPME
• QAM PHY parameters for the physical QAM channel.
Restrictions for VPME
You can configure the line card in only one mode as the table-based session configuration and dynamic
GQI-based sessions are mutually exclusive. Hence, PME and PowerKey encryption are also mutually exclusive
modes at the line card level. For more details, see Configuring the Encryption Type on the Line Card section.
How to Configure Table-Based Video Session
• Configuring Table-Based Video
• Verifying Table-Based Video Configuration
• Configuring CEM Connectivity for PME Encryption
• Verifying CEM Connectivity
Configuring Table-Based Video
Before You Begin
Before configuring table-based sessions, you must configure the physical and virtual constructs for Cisco
cBR-8. You must also configure the Logical Edge Device (LED), Service Distribution Group (SDG), binding
and Virtual Carrier Group (VCG).
The following is an example for LED configuration. In this example, assumes that the video traffic is routed
via the input ports of Virtual Edge Input (VEI).
logical-edge-device pme_tbv id 1
protocol table-based
virtual-edge-input-ip 172.16.0.1 input-port-number 1
vcg pme_tbv
active
In the above example, protocol table-based indicates that this LED supports table-based sessions.
For more information, see the How to Configure the Logical Edge Devices section. For details related to D6
protocol, see the How to Configure the D6 Discovery Protocol section.
Configuring Table-Based Session : VEI Input Port-Based
To configure the table-based session based on Virtual Edge Input (VEI), complete the following procedure:
configure terminal
cable video
table-based
vcg vcg-name
rf-channel n-m
session name {input-port number | bundle-id number} start-udp-port number num-sessions-per-qam
number processing-type {program | data } start-program number [repeat] jitter ms [cbr | vbr ]
exit
Cisco cBR Converged Broadband Routers Video Features
12
Table-Based Video and VPME Encryption
Configuring Table-Based Video
The table-based keyword is the root keyword. The entire table-based configuration should be under this
keyword. Within this, the configuration is separated based on the VCG. Within each VCG, the configuration
can be created for each QAM channel.
• Processing-type
◦Remap—Configures VoD sessions as remap.
◦Data—Configure video streams that are not dejittered, and remapped. For example, Beacons,
carousel, and so on.
• Repeat—Repeats the program number across QAM channels.
Example:
The following is an example in which two sessions are created on all QAM channels from 20 to 22.
configure terminal
cable video
table-based
vcg pme_tbv
rf-channel 20-22
session bago_tbv input-port 1 start-udp-port 49152 num-sessions-per-qam 2 processing-type
remap start-program 32 jitter 150 cbr
exit
The following is an example in which one session is created on each QAM channel.
configure terminal
cable video
table-based
vcg pme_tbv2
rf-channel 23
session pme_tbv input-port 1
remap start-program 5 jitter
rf-channel 24
session pme_tbv input-port 1
remap start-program 5 jitter
exit
start-udp-port 50152 num-sessions-per-qam 1 processing-type
150 cbr
start-udp-port 50153 num-sessions-per-qam 1 processing-type
150 cbr
Configuring Table-Based Session :VEI Bundle-Based
Before You Begin
• Create two or more VEIs.
• Bundle the VEIs.
For more details, see Virtual Edge Input Bundling section.
To configure the VEI bundled table-based session, complete the following procedure:
configure terminal
cable video
table-based
vcg vcg-name
rf-channel n-m
session name bundle-id number start-udp-port number num-sessions-per-qam number processing-type
{program | passthru | data } start-program number [repeat] jitter ms [cbr | vbr ]
exit
Example:
Cisco cBR Converged Broadband Routers Video Features
13
Table-Based Video and VPME Encryption
Verifying Table-Based Video Configuration
The following is an example in which a session is created for VEI bundle (10) .
configure terminal
cable video
table-based
vcg pme_vcg
rf-channel 20-21
session tbv bundle-id 10 start-udp-port 49152 num-sessions-per-qam 2 processing-type remap
start-program 1 repeat jitter 100 vbr
exit
Virtual Edge Input Bundling
To create and bundle the VEIs, complete the following procedure:
configure terminal
cable video
logical-edge-device name
protocol table-based
virtual-edge-input-ip ip address input-port-number number
vcgvcg-name
vei-bundle id input-port-number number
active
exit
Example:
The following is an example in which a bundle (10) is created with two input ports (1 and 2) each with distinct
IP address.
configure terminal
cable video
logical-edge-device pme_led id 1
protocol table-based
virtual-edge-input-ip 172.16.0.1 input-port-number 1
virtual-edge-input-ip 172.16.0.1 input-port-number 2
vcg pme_vcg
vei-bundle 10 input-port-number 1,2
active
exit
Verifying Table-Based Video Configuration
• To verify all the sessions configured on a particular LED, use the show cable video session
logical-edge-device id number command as shown in the example below:
show cable video session logical-edge-device id 1
Total Sessions = 6
Session Output Streaming Session Destination UDP
Output Input
Output Input
Output Encrypt Encrypt Session
Id
Port
Type
Type
Port Program State
State Bitrate
Bitrate Type
Status Name
----------------------------------------------------------------------------------------------------------------------------------1048576 1
Remap
UDP
174.21.1.1 49152 32
ACTIVE-PSI ON
1718234
1702594 CLEAR
bago_tbv.1.0.1.20.49152
1048577 1
Remap
UDP
174.21.1.1 49153 33
ACTIVE-PSI ON
1718631
1702594 CLEAR
bago_tbv.1.0.1.20.49153
1048578 2
Remap
UDP
174.21.1.1 49154 34
ACTIVE-PSI ON
1717832
1702977 CLEAR
bago_tbv.1.0.1.21.49154
1048579 2
Remap
UDP
174.21.1.1 49155 35
ACTIVE-PSI ON
1717322
1702977 CLEAR
bago_tbv.1.0.1.21.49155
1048580 3
Remap
UDP
174.21.1.1 49156 36
ACTIVE-PSI ON
1718697
1702959 CLEAR
bago_tbv.1.0.1.22.49156
1048581 3
Remap
UDP
174.21.1.1 49157 37
ACTIVE-PSI ON
1717542
1702959 CLEAR
bago_tbv.1.0.1.22.49157
Cisco cBR Converged Broadband Routers Video Features
14
Table-Based Video and VPME Encryption
Verifying Table-Based Video Configuration
• To verify the summary of the session details at a LED level, use the show cable video session
logical-edge-device id number summary command as shown in the example below:
show cable video session logical-edge-device id 1 summary
Video Session Summary:
Active
: 6
Off
: 0
UDP
: 6
Remap
: 6
Total Sessions: 6
Init
Blocked
ASM
Data
:
:
:
:
0
0
0
0
Idle
PSI-Ready
SSM
Passthru
:
:
:
:
0
6
0
0
• To verify the QAM PHY parameters of RF-channel that are configured on the RF port, which is controller
Integrated-Cable 7/0/0, use the show controllers integrated-Cable slot/bay/portrf-channel n-m
command as shown in the example below:
show controllers integrated-Cable 7/0/0 rf-channel 0-95
Chan State Admin Frequency Type
Annex Mod srate Interleaver
0
UP
UP
93000000
VIDEO
B
256
5361 I32-J4
1
UP
UP
99000000
VIDEO
B
256
5361 I32-J4
2
UP
UP
105000000 VIDEO
B
256
5361 I32-J4
3
UP
UP
111000000 VIDEO
B
256
5361 I32-J4
4
UP
UP
117000000 VIDEO
B
256
5361 I32-J4
5
UP
UP
123000000 VIDEO
B
256
5361 I32-J4
6
UP
UP
129000000 VIDEO
B
256
5361 I32-J4
7
UP
UP
135000000 VIDEO
B
256
5361 I32-J4
8
UP
UP
141000000 VIDEO
B
256
5361 I32-J4
9
UP
UP
147000000 VIDEO
B
256
5361 I32-J4
10
UP
UP
153000000 VIDEO
B
256
5361 I32-J4
dcid
-
power
34
34
34
34
34
34
34
34
34
34
34
output
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
NORMAL
Troubleshooting Video and VPME Encryption
Output State is OFF
Step 1
Verify the video traffic using the show cable video session logical-edge-device id 1 command. In the below example,
the output state is OFF. This value confirm that there is no output traffic.
Session Output Streaming Session Destination UDP
Output Input Output Input
Output Encrypt
Encrypt Session
Id
Port
Type
Type
Port Program State State Bitrate Bitrate Type
Status Name
-----------------------------------------------------------------------------------------------------------------------------1048582
1
Remap
UDP
172.16.0.1 49152 32
OFF
OFF
0
0
PME
Pending bago_tbv.1.0.1.20.49152
1048583
1
Remap
UDP
172.16.0.1 49153 33
OFF
OFF
0
0
PME
Pending bago_tbv.1.0.1.20.49153
1048584
2
Remap
UDP
172.16.0.1 49154 34
OFF
OFF
0
0
PME
Pending bago_tbv.1.0.1.21.49154
1048585
2
Remap
UDP
172.16.0.1 49155 35
OFF
OFF
0
0
PME
Pending bago_tbv.1.0.1.21.49155
1048586
3
Remap
UDP
172.16.0.1 49156 36
OFF
OFF
0
0
PME
Pending bago_tbv.1.0.1.22.49156
1048587
3
Remap
UDP
172.16.0.1 49157 37
OFF
OFF
0
0
PME
Pending bago_tbv.1.0.1.22.49157
Cisco cBR Converged Broadband Routers Video Features
15
Table-Based Video and VPME Encryption
Verifying Table-Based Video Configuration
Step 2
Verify if the RF output of the controller is shut using the show cable video integrated-cable command.
Router#show cable video integrated-cable 8/0/0
Integrated TSID ONID Output Physical
Admin Operational Virtual-Carrier Service-Distribution
Logical-Edge Encryption Total
Cable
Port
QAM ID
State State
-Group Name
-Group Name
-Device
Name Capable
Sessions
------------------------------------------------------------------------------------------------------------------------------8/0/0:20
1
0
1
unavailable OFF
DOWN
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:21
2
0
2
unavailable OFF
DOWN
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:22
3
0
3
unavailable OFF
DOWN
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:23
4
0
4
unavailable OFF
DOWN
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:24
5
0
5
unavailable OFF
DOWN
pme_tbv
pme_tbv
pme_tbv
pme
0
a) If the RF output of the controller is shut, you must unshut the port. This action changes the status as ON for the
corresponding QAMs. You can verify the state using the show cable video integrated-cable command.
Router#show cable video integrated-cable 8/0/0
Integrated TSID ONID Output Physical Admin Operational Virtual-Carrier Service-Distribution
Logical-Edge Encryption Total
Cable
Port
QAM ID
State State
-Group Name
-Group Name
-Device
Name Capable
Sessions
---------------------------------------------------------------------------------------------------------------------------8/0/0:20
1
0
1
48
ON
UP
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:21
2
0
2
49
ON
UP
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:22
3
0
3
50
ON
UP
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:23
4
0
4
51
ON
UP
pme_tbv
pme_tbv
pme_tbv
pme
2
8/0/0:24
5
0
5
24
ON
UP
pme_tbv
pme_tbv
pme_tbv
pme
2
Step 3
Verify the JIB channel number for a specific QAM channel using the show cable video integrated-cable command.
Router#show controllers integrated-Cable 7/0/0 rf-channel 21 verbose
Chan State Admin Frequency Type
Annex Mod
21
UP
UP
219000000 VIDEO
B
256
Qam profile: 1
Spectrum Inversion: Off
Frequency Lane: 1 Block: 3 index: 6
Resource status:
OK
License: granted <01:07:01 EDT Feb 19 2016>
QAM Replication:
Group ID: 57344 (Pilot)
Slot group ID: 0
Members: 7/0/0:21 (P) 7/0/1:21 7/0/2:21
Cisco cBR Converged Broadband Routers Video Features
16
srate Interleaver
5361 I32-J4
7/0/3:21
dcid
-
power
34
output
NORMAL
Table-Based Video and VPME Encryption
Verifying Table-Based Video Configuration
Channel Replication Status: Up
JIB channel number: 21
Chan Pr EnqQ Pipe RAF
SyncTmr Vid Mac
Video Primary DqQ TM Mpts Sniff
21 -21
0 6880
0
1 0000.0000.0000
1
0
21 0
5 NO 86
Grp Prio P Prate Phy0-ctl Phy1-ctl Enable Tun-Id L2TPv3_Ses_id
2
0 0
1
1
0
TRUE
0
2
Chan
Qos-Hi
Qos-Lo
Med-Hi
Med-Lo
Low-Hi
Low-Lo
21
32774
16384
32768
16384
65536
32768
Chan Med Low TB-neg Qos_Exc Med_Xof Low_Xof
Qdrops(H-M-L) Pos Qlen(Hi-Med-lo) Fl
21
0
0
0
0
0
0
0
0
0 N 23808
0 11656 0
DSPHY Register Local Copy: QPRHI = c0005564, QPRLO = 216ab0
DSPHY Register Local Copy Vaddr = 800002e4, qam2max_mapping = 80000015
DSPHY Register Local Copy: SPR ID = 15, SPR Mapping= c200000b
Last read from HW: Fri Feb 19 01:07:57 2016
QPRHI = c0005564, QPRLO = 216ab0, SPR = c200000b SPRMAPING c0000205 Q2Max 80000015
Last time read spr rate info from HW: Fri Feb 19 03:06:43 2016
SPR ID 21, rate value in kbps 3463, overflow count 0, underflow count 0
Output Status is Idle or Pending
Step 1
Verify the video traffic. In the below example, the input bitrate is zero, and the input state is IDLE / OFF. These values
confirm that there is no input traffic.
Router#sh cable video session logical-edge-device id 1
Total Sessions = 6
Session Output Streaming Session Destination UDP
Output Input Output Input
Output Encrypt
Encrypt Session
Id
Port
Type
Type
Port Program State State Bitrate Bitrate Type
Status Name
-----------------------------------------------------------------------------------------------------------------------------1048588
1
Remap
UDP
172.16.0.1 49152 32
IDLE PENDING 0
0
PME
Pending bago_tbv.1.0.1.20.49152
1048589
1
Remap
UDP
172.16.0.1 49153 33
IDLE PENDING 0
0
PME
Pending bago_tbv.1.0.1.20.49153
1048590
2
Remap
UDP
172.16.0.1 49154 34
IDLE PENDING 0
0
PME
Pending bago_tbv.1.0.1.21.49154
1048591
2
Remap
UDP
172.16.0.1 49155 35
IDLE PENDING 0
0
PME
Pending bago_tbv.1.0.1.21.49155
1048592
3
Remap
UDP
172.16.0.1 49156 36
IDLE PENDING 0
0
PME
Pending bago_tbv.1.0.1.22.49156
1048593
3
Remap
UDP
172.16.0.1 49157 37
IDLE PENDING 0
0
PME
Pending bago_tbv.1.0.1.22.49157
Cisco cBR Converged Broadband Routers Video Features
17
Table-Based Video and VPME Encryption
Verifying Table-Based Video Configuration
Step 2
Verify details of the video traffic over the mid plane interface through which traffic is routed to the video data plane on
the line card. The mid plane is specific to the line-card slot. On subsequent trials, the output packet count should keep
increasing. You can verify the output packet count using the show interfaces video command.
Router#show interfaces video 7/0/0 accounting
Video7/0/0
Protocol
IP
DEC MOP
ARP
Pkts In
0
0
0
Chars In
0
0
0
Pkts Out
Chars Out
2211315936 2653579123200
12
756
4
112
Protocol
IP
DEC MOP
ARP
Pkts In
0
0
0
Chars In
0
0
0
Pkts Out
Chars Out
2220252160 2664302592000
12
756
4
112
Video7/0/0
Step 3
If the packet count is not increasing, verify the 10 GigE physical interface through which the video traffic is fed to the
chassis using the show interfaces command. In the below example, the video traffic is fed through the 10GigE interface
4/1/0 and the counter for packets keeps incrementing.
Router#show interfaces tenGigabitEthernet 4/1/0 accounting
TenGigabitEthernet4/1/0
Protocol
Pkts In
Chars In
Pkts Out Chars Out
Other
15
1155
1814
109078
IP 8038262210 9404766785700
0
0
DEC MOP
15
1155
14
1078
ARP
0
0
1
60
Router#show interfaces tenGigabitEthernet 4/1/0 accounting
TenGigabitEthernet4/1/0
Protocol
Pkts In
Chars In
Pkts Out Chars Out
Other
15
1155
1816
109198
IP 8047199112 9415222959870
0
0
DEC MOP
15
1155
14
1078
ARP
0
0
1
60
Input State is Active and not Active PSI
If the input state is Active and the input PSI information is not detected, verify the input PMT information
section for this particular session.
Verify the details of a particular video session, using the show cable video session logical-edge-device id
led-id session-id id command.
Router#show cable video session logical-edge-device id 1 session-id 1048599
Session Name
: bago_tbv.1.0.1.22.49157
Session Id:
: 1048599
Creation Time:
: Thu Feb 18 18:21:25 2016
Output Port
TSID
: 3
: 3
Cisco cBR Converged Broadband Routers Video Features
18
Table-Based Video and VPME Encryption
Verifying Table-Based Video Configuration
ONID
Number of Sources
Destination IP
UDP Port
Config Bitrate
Jitter
Processing Type
Stream Rate
Program Number
Idle Timeout
Init Timeout
Off Timeout
Encryption Type
Encryption Status
:
:
:
:
:
:
:
:
:
:
:
:
:
:
0
1
172.16.0.1
49157
2000000
150 ms
Remap
CBR
37
250 msec
1000 msec
60 sec
PME
Encrypted
Input Session Stats:
====================
State: ACTIVE-PSI, Uptime: 0 days 00:01:01
IP Packets: In 12202, RTP 0, Drop 0
TP Packets: In 69979, PCR 2447, PSI 1323, Null 3233, Unreference 153
Errors: Discontinuity 8, Sync loss 0, CC error 0, PCR Jump 17,
Underflow 0, Overflow 0, Block 0
Bitrate: Measured 1716626 bps, PCR 1800140 bps
Output Session Stats:
=====================
State: ON, Uptime: 0 days 00:01:01
TP Packets: In 70535, PCR 2440, PSI 1320,
Drop 910, Forward 68305, Insert 1752
Errors: Info Overrun 0, Info Error 0, Block 0, Overdue 0,
Invalid Rate 0, Underflow 0, Overflow 0
Bitrate: Measured 1723591 bps
PAT Info:
=========
Version 0, TSID 1, len 20, section 0/0
Program 0: NIT 16
Program 1: PMT 8020
Input PMT Info:
===============
Program 1, Version 0, PCR 8000, Info len 0
PID 8000: Type 2, Info len 5, (desc 2 len 3)
PID 8001: Type 129, Info len 17, (lang eng), (desc 5 len 4), (desc 129 len 3)
Output PMT Info:
================
Program 37, Version 1, PCR 273, Info len 6, (CA SYS-ID 18249, PID 303)
PID 273: Type 2, Info len 5, (desc 2 len 3)
PID 274: Type 129, Info len 17, (lang eng), (desc 5 len 4), (desc 129 len 3)
Output PID Map:
===============
PID 8000 -> 273
PID 8001 -> 274
PID 8020 -> 272
Abnormalities on the Output
If there are any abnormalities in the output such as macro blocks, ans so on, verify if there are any issues such
as CC errors or PCR errors in the MPEG packet.
Verify the session details, using the show cable video session logical-edge-device id led-id session-id id
command. This command displays errors for both input session stats and output session stats.
Cisco cBR Converged Broadband Routers Video Features
19
Table-Based Video and VPME Encryption
Configuring CEM Connectivity for PME Encryption
Configuring CEM Connectivity for PME Encryption
This section explains how to configure the connectivity to the external CEM and enforce PME encryption on
the line card.
Only one device from the MSO site can communicate with the Encryption Renewal System (ERS) and obtain
the latest ECM templates. The CEM communicates with the ERS and sends the ECM templates to the Cisco
Edge QAM devices in the MSO site.
You can configure the following:
• VODS-ID—IDs assigned by CCAD/ARRIS to the MSO site. The configured VODS-ID on the Cisco
cBR-8 and the CEM must be same.
• CEM IP—Interface IP of the Windows/Linux system through which the CEM can be reached by Cisco
cBR-8.
• CEM Port—Port number on which the CEM listens for connections from the Cisco cBR-8.
• Management Interface—Source IP address of the cBR-8 virtual interface through which the connection
must be established with the CEM server.
Note
There can be only one entry for VODS-ID, CEM IP, CEM Port, and Management Interface IP. If you
configure any new values for these parameters, the previous configuration is cleared. You can clear the
configurations using the 'no' form of the command.
Configuring VODS-ID
To configure the VODS-ID of the CEM, perform the following steps:
enable
configure terminal
cable video
encryption
pme vodsid id
exit
Configuring CEM IP and Port
To configure the CEM IP and port of the CEM, perform the following steps:
enable
configure terminal
cable video
encryption
pme cem ip-address tcp_port
exit
Configuring Management IP
To configure the PME management IP address to establish CEM connection, perform the following steps:
Cisco cBR Converged Broadband Routers Video Features
20
Table-Based Video and VPME Encryption
Verifying CEM Connectivity
Before You Begin
The virtual port group must be configured before configuring the management IP. For more information, see
the Configuring the VirtualPortGroup Interface section.
enable
configure terminal
cable video
encryption
pme mgmt-ip ip-address
exit
Verifying CEM Connectivity
To verify the connection status of PME, use the show cable video encryption pme status command as
shown in the following example:
Router#show cable video encryption
PME Connection Status:
VODS-ID : 111
CEM IP : 1.200.1.163
CEM Port : 5000
Local Mgmt IP : 1.24.2.6
Local Port : 50394
CEM Connection State : Connected
Count of ECMs recd : 2
pme status
Troubleshooting Tips
Connectivity with CEM is Lost
Step 1
If the CEM connection status is Not Connected, verify the VODS-ID, CEM IP, CEM port and local Mgmt IP address
parameters using the show cable video encryption pme status command.
Router#show cable video encryption pme status
PME Connection Status:
======================
VODS-ID
: 111
CEM IP
: 1.200.1.163
CEM Port
: 5000
Local Mgmt IP
: 1.35.2.5
Local Port
: 0
CEM Connection State : Not Connected
Step 2
If the PME connection parameters are valid, ensure there is route from the Cisco cBR-8's Virtual management iinterface
to the CEM by using the ping command. Ping the CEM IP address from the virtualPortGroup 0 on which the management
IP is created.
Router#ping 1.200.1.163 source virtualPortGroup 0
Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 1.200.1.163, timeout is 2 seconds:
Cisco cBR Converged Broadband Routers Video Features
21
Table-Based Video and VPME Encryption
How to Configure VPME Encryption
Packet sent with a source address of 1.35.2.1
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Step 3
Verify the alarms in the logs for any connectivity loss.
Feb 18 18:28:12.053 IST: %VEMAN-3-CEM_CONNECTION_LOST: CLC4: sup_veman:
Lost: Connection closed by peer-1.200.1.163:5000
Alarm Set: CEM Connection
How to Configure VPME Encryption
• Enforcing Data Stream Encryption Type
• Configuring Virtual Carrier Group
Enforcing Data Stream Encryption Type
Before You Begin
Configure the Virtual Carrier Group (VCG) to setup an encrypted session. For more details, see Configuring
Virtual Carrier Group section.
To configure the encryption type for a VOD session, perform the following steps:
enable
configure terminal
cable video
encryption
linecard slot/bay ca-system [dvb | pme | powerkey] scrambler scrambler-type [des | dvs042]
exit
Configuring Virtual Carrier Group
To configure the Virtual Carrier Group (VCG) for setting up an encrypted session, perform the following
steps:
enable
configure terminal
cable video
encryption
virtual-carrier-group name[idnumber]
rf-channel start-channel number-end-channel number tsid start-tsid-end-tsid output-port-number
start-num-end-num
virtual-edge-input ipaddr input-port-number port-number
encrypt
exit
Cisco cBR Converged Broadband Routers Video Features
22
Table-Based Video and VPME Encryption
Verifying VPME Encryption Configuration
Verifying VPME Encryption Configuration
• To verify the encryption configurations, use the show cable video encryption linecard [all | slot number]
command as shown in the following example:
Router#show cable video encryption linecard 7/0
Line card: 7/0
CA System Scrambler
====================================
PME dvs-042
• To verify the encryption status of all sessions on an LED, use the show cable video session
logical-edge-device id id command as shown in the following example:
Router#show cable video session logical-edge-device id 1
Total Sessions = 6
Session Output Streaming Session Destination UDP
Output Input
Output Input
Output Encrypt Encrypt
Session
Id
Port
Type
Type
Port Program State
State Bitrate
Bitrate Type
Status
Name
-------------------------------------------------------------------------------------------------------------------------------------1048582 1
Remap
UDP
172.16.0.1 49152 32
ACTIVE-PSI ON
996413
981109 PME
Encrypted bago_tbv.1.0.1.20.49152
1048583 1
Remap
UDP
172.16.0.1 49153 33
ACTIVE-PSI ON
1004787
981246 PME
Encrypted bago_tbv.1.0.1.20.49153
1048584 2
Remap
UDP
172.16.0.1 49154 34
ACTIVE-PSI ON
995088
984011 PME
Encrypted bago_tbv.1.0.1.21.49154
1048585 2
Remap
UDP
172.16.0.1 49155 35
ACTIVE-PSI ON
993061
984051 PME
Encrypted bago_tbv.1.0.1.21.49155
1048586 3
Remap
UDP
172.16.0.1 49156 36
ACTIVE-PSI ON
994238
988617 PME
Encrypted bago_tbv.1.0.1.22.49156
1048587 3
Remap
UDP
172.16.0.1 49157 37
ACTIVE-PSI ON
1004658
988602 PME
Encrypted bago_tbv.1.0.1.22.49157
• To verify the various sessions, which use the PME modules that are loaded on a specific line-card, use
the show cable video encryption pme linecard slot/bay session 1-65535 | all | summary command
as shown in the example below:
Router#show cable video encryption pme linecard 7/0 session all
Count of ECMG Streams: 4
==================== ECMG Stream DATA ========================
Stream
ID num EcmId CP# CwE CPDur NomCPD EcmRqst EcmRsp
---------- ---------- ---- --- ----- ------ ---------- ---------0020(0032) 0020(0032) 0002 0 0 40000 7 2
0021(0033) 0021(0033) 0002 0 0 40000 7 2
0040(0064) 0040(0064) 0002 0 0 40000 7 2
0041(0065) 0041(0065) 0002 0 0 40000 7 2
Router#show cable video encryption pme linecard 7/0 session 32
Stream 32, session 7681 is active
Stream number = 32 Session number = 7681
ECM requests = 8 ECM replies = 2
ECM ID = 32 CryptoPeriod num = 2
CP duration = 0 Nominal duration = 40000
CA transfer mode = 1 Stream status = No
Error Blob details
Router#show cable video encryption pme linecard 7/0 session summary
Currently active streams:
Active = 4
ECM req/resp mismatch = 4
Cisco cBR Converged Broadband Routers Video Features
23
Table-Based Video and VPME Encryption
Verifying VPME Encryption Configuration
ECM req, all streams = 32
ECM resp, all streams = 8
Since last reset:
Sessions created = 4
Sessions deleted = 0
ECMs received =2
ECMs discarded = 0
Troubleshooting Tips
No PMT at the Output
Step 1
Verify the encryption status using the show cable video session logical-edge-device id command. If the encrypt status
is shown as ca-waiting, then PMT is withheld.
Router#show cable video session logical-edge-device id 1
Total Sessions = 6
Session Output Streaming Session Destination UDP
Output Input
Output Input
Output Encrypt
Encrypt
Session
Id
Port
Type
Type
Port Program State
State Bitrate Bitrate Type
Status
Name
-------------------------------------------------------------------------------------------------------------------------------------1048582 1
Remap
UDP
172.16.0.1 49152 32
ACTIVE-PSI PENDING 996413 981109 PME
ca-waiting bago_tbv.1.0.1.20.49152
Step 2
Verify if the ECM count is zero using the show cable video encryption pme status command.
Router#show cable video encryption pme status
PME Connection Status:
VODS-ID : 111
CEM IP : 1.200.1.163
CEM Port : 5000
Local Mgmt IP : 1.24.2.6
Local Port : 50394
CEM Connection State : Connected
Count of ECMs recd : 0
Step 3
Verify if the ECM request or response count is 0 using the show cable video encryption pme linecard slot/bay session
summary command.
Router#show cable video encryption pme linecard 7/0 session summary
Currently active streams:
Active = 4
ECM req/resp mismatch = 4
ECM req, all streams = 32
ECM resp, all streams = 8
Since last reset:
Sessions created = 4
Sessions deleted = 0
Cisco cBR Converged Broadband Routers Video Features
24
Table-Based Video and VPME Encryption
Configuration Examples For VPME Encryption
ECMs received =2
ECMs discarded = 0
Configuration Examples For VPME Encryption
The following example shows running output for a PME configuration:
cable video
mgmt-intf virtualPortGroup 0
virtual-carrier-group pme_tbv
encrypt
service-type narrowcast
rf-channel 20-24 tsid 1-5 out 1-5
service-distribution-group pme_tbv
rf-port integrated-cable 7/0/0
bind-vcg
vcg pme_tbv sdg pme_tbv
encryption
linecard 7/0 ca-system pme scrambler dvs
pme vodsid 111
pme cem 1.200.1.163 5000
pme mgmt-ip 1.25.2.6
logical-edge-device pme_tbv
protocol table-based
virtual-edge-input-ip 174.101.1.1 input 1
vcg pme_tbv
active
table-based
vcg vcg_replication
rf-channel 21-31
session pme_tbv1 in 1 start-udp-port 49152 num-sessions-per-qam 2 processing-type remap
start-program 32 jitter 150 cbr
session pme_tbv2 in 1 start-udp-port 50001 num-sessions-per-qam 2 processing-type remap
start-program 64 jitter 150 cbr
Use Cases or Deployment Scenarios
Topology
A typical topology for CEM connectivity is shown below:
Cisco cBR Converged Broadband Routers Video Features
25
Table-Based Video and VPME Encryption
Feature Information for Table-Based Video and VPME Encryption
Feature Information for Table-Based Video and VPME Encryption
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software release,
feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An
account on http://www.cisco.com/ is not required.
Note
The below table lists only the software release that introduced support for a given feature in a given
software release train. Unless noted otherwise, subsequent releases of that software release train also
support that feature.
Table 3: Feature Information for Table-Based Video and VPME Encryption
Feature Name
Releases
Feature Information
Table-Based Video and VPME
Encryption
Cisco IOS-XE Release 3.18.0S
This feature was introduced on the
Cisco cBR Series Converged
Broadband Routers.
Cisco cBR Converged Broadband Routers Video Features
26
CHAPTER
3
Video QAM Replication
The Video QAM replication feature allows video carriers to be replicated to support service group alignment
between DOCSIS and Video service groups.
Contents
• QAM Replication, page 27
• Information About Replication, page 27
• Configuring Replication for Table-Based or Session-Based Video, page 29
• Configuration Examples, page 31
• Feature Information for Replication, page 31
QAM Replication
The QAM replication feature allows duplication of content on multiple QAM carriers. This feature is internal
to the cBR-8 and replaces the need for external splitters, allowing content to be replicated across multiple
ports on a line card.
Information About Replication
• Multiple Ports: Multiple ports in a Service Distribution Group (SDG) replicate all QAMs from the
Virtual Carrier Group (VCG) to output port listed in the same SDG.
• Unicast: Unicast (Video on Demand) services cannot be replicated across line cards.
Overview of QAM Replication
Video on Demand (VoD) or unicast services cannot be replicated across line cards. You can accomplish
replication by adding more than one RF port to an SDG. This feature works for the SDG regardless of whether
the video sessions are table-based or session-based.
Cisco cBR Converged Broadband Routers Video Features
27
Video QAM Replication
Benefits of QAM Replication
Replication also applies to the QAM PHY parameters. Hence, the QAM PHY parameters like frequency,
annex, and symbol rate of the replicated QAM carrier are the same as the QAM PHY parameters on the pilot
QAM carrier.
QAM replication is achieved in two ways: software and hardware. The line card performs the hardware QAM
replication. Each line card has the capability to replicate an output QAM (Pilot QAM) from one port to another
output QAM (Replicate QAM) on another port.
Note
QAM replication in the same port is not supported.
The service-distribution-group construct is used to perform replication. Hardware replication is supported
when the replication of individual QAM Carriers is limited to the same line card.
The bind-vcg construct, which is used to determine the physical QAMs to be replicated, is analogous to
combiner and splitter combination. The RF ports combine all the QAMs routed to them. Then, one or more
inputs are split to one or more RF output ports.
Benefits of QAM Replication
QAM replication reduces the need for external HFC components like splitters and combiners in the RF plant.
The figure below illustrates the bind operation that replaces a combiner and a splitter and performs replication
on multiple ports that are assigned to an SDG.
Prerequisites for Replication
The controller type for the slot/bay/port used for the SDG should be set as 'VIDEO'. The errors corresponding
to the incorrect controller type used in the SDG appear during the bind operation.
Cisco cBR Converged Broadband Routers Video Features
28
Video QAM Replication
Restrictions for QAM Replication
Perform the following steps to set the controller type:
configure terminal
controller Integrated-Cable slot/bay/port
rf-channel start-channel – end-channel
type VIDEO
start-frequency frequency
rf-output normal
power-adjust number
qam-profile qam-profile number
Restrictions for QAM Replication
• Hardware can support QAM replication only within the same line card.
• The output of a source QAM in any port can be replicated to only one QAM in another port. Replication
within the same port is not supported.
• The current line card has a maximum of eight ports. Hence, for each line card a pilot QAM can have up
to seven replicates (one on each port).
• Standard routing protocols prohibit routing of unicast traffic (VOD) to multiple destinations (across line
cards).
Configuring Replication for Table-Based or Session-Based
Video
Replication is configured within the SDG by adding a set of RF ports to the same SDG. To configure replication
you must choose the Pilot QAM carriers, a set of QAM carriers belonging to a RF port. The Pilot QAM carriers
are denoted by the first RF port added under SDG. The rest of RF ports, which carry the replicated content,
are specified within this SDG.
Choose the QAM carriers, which carry the content to be replicated, by configuring Virtual Carrier Group
(VCG) and specifying the number of QAM channels that are replicated in each RF port. When the pilot QAM
carrier is removed, one of the remaining replicated QAM carriers is automatically chosen as pilot QAM carrier.
To configure the replication, complete the following procedure:
configure terminal
cable video
service-distribution-group service distribution group name
rf-port integrated-cable slot/bay/port
rf-port integrated-cable slot/bay/port
virtual-carrier-group vcg_replication id number
virtual-edge-input-ip ip-address vrf vrf-name input-port-number number
rf-channel n-m tsid n-m output-port-number n-m
bind-vcg
vcg vcg_replication sdg sdg_replication
Cisco cBR Converged Broadband Routers Video Features
29
Video QAM Replication
Verifying Replication of Table Based Video Sessions
Verifying Replication of Table Based Video Sessions
To verify the replication information including the replication group ID, pilot or replicant, and the associated
status, use the show cable card slot/bayqam-repl group command as shown in the example below:
Router#show cable card 7/0 qam-repl group
----------------------------------------------------------------Grp Slot Chan QAM Grp
Chan
ID Grp cnt type State List
ID [port:chan state role]
U:Up
P:Pilot
D:Down R:Replicant
----------------------------------------------------------------57344 0
4 VID
U
0:21 UP
1:21 UR
2:21 UR
3:21 UR
57345 1
4
VID
U
0:22
UP
1:22
UR
2:22
UR
3:22
UR
57346 2
4
VID
U
0:23
UP
1:23
UR
2:23
UR
3:23
UR
57347 3
4
VID
U
0:24
UP
1:24
UR
2:24
UR
3:24
UR
57348 4
4
VID
U
0:25
UP
1:25
UR
2:25
UR
3:25
UR
57349 5
4
VID
U
0:26
UP
1:26
UR
2:26
UR
3:26
UR
57350 6
4
VID
U
0:27
UP
1:27
UR
2:27
UR
3:27
UR
57351 7
4
VID
U
0:28
UP
1:28
UR
2:28
UR
3:28
UR
57352 8
4
VID
U
0:29
UP
1:29
UR
2:29
UR
3:29
UR
57353 9
4
VID
U
0:30
UP
1:30
UR
2:30
UR
3:30
UR
57354 10
4
VID
U
0:31
UP
1:31
UR
2:31
UR
3:31
UR
----------------------------------------------------------------Total number of Replication groups on slot 7/0: 11
To verify the sessions on the pilot QAM carrier, use the show cable video session logical-edge-device id
number command as shown in the example below:
Router#show cable video session logical-edge-device id 1
Total Sessions = 22
Session
Output
Streaming
Session Destination
UDP
Output
Input
Output
Input
Output
Encrypt Encrypt
Session
Id
Port
Type
Type
Port
Program
State
State
Bitrate
Bitrate Type
Status
Name
-----------------------------------------------------------------------------------------------------------------------------------------------------1048598
21
Remap
UDP
172.16.0.1
49152 32
ACTIVE-PSI ON
1104548 1088424
CLEAR
bago_tbv.1.21.49152
1048599
21
Remap
UDP
172.16.0.1
49153 33
ACTIVE-PSI ON
1104482 1088424
CLEAR
bago_tbv.1.21.49153
1048600
22
Remap
UDP
172.16.0.1
49154 34
ACTIVE-PSI ON
1104922 1090656
CLEAR
bago_tbv.1.22.49154
1048601
22
Remap
UDP
172.16.0.1
49155 35
ACTIVE-PSI ON
1105033 1090534
CLEAR
bago_tbv.1.22.49155
1048602
23
Remap
UDP
172.16.0.1
49156 36
ACTIVE-PSI ON
1114332 1092488
CLEAR
bago_tbv.1.23.49156
1048603
23
Remap
UDP
172.16.0.1
49157 37
ACTIVE-PSI ON
1104353 1092488
CLEAR
-
Cisco cBR Converged Broadband Routers Video Features
30
Video QAM Replication
Configuration Examples
Configuration Examples
The following example configures replication across four RF ports on line card 7/0:
configure terminal
cable video
service-distribution-group sdg replication id 1
rf-port integrated-cable 7/0/0
rf-port integrated-cable 7/0/1
rf-port integrated-cable 7/0/2
rf-port integrated-cable 7/0/3
virtual-carrier-group vcg_replication id 1
virtual-edge-input-ip 172.31.1.1 vrf vrf-name input-port-number 1
rf-channel 21-31 tsid 21-31 output-port-number 21-31
bind-vcg
vcg vcg_replication sdg sdg_replication
Feature Information for Replication
Use Cisco Feature Navigator to find information about platform support and software image support.
Cisco Feature Navigator enables you to determine which software images support a specific software release,
feature set, or platform. To access Cisco Feature Navigator, go to http://tools.cisco.com/ITDIT/CFN/. An
account on http://www.cisco.com/ is not required.
Note
The below table lists only the software release that introduced support for a given feature in a given
software release train. Unless noted otherwise, subsequent releases of that software release train also
support that feature.
Table 4: Feature Information for Replication
Feature Name
Releases
Feature Information
Replication
Cisco IOS-XE Release3.18.0S
This feature was introduced on the
Cisco cBR Series Converged
Broadband Routers.
Cisco cBR Converged Broadband Routers Video Features
31
Video QAM Replication
Feature Information for Replication
Cisco cBR Converged Broadband Routers Video Features
32
CHAPTER
4
D6 Discovery Protocol
The D6 discovery protocol is part of the Comcast Next Generation on Demand (NGOD) specification. This
protocol helps in advertising the video QAM carrier information like frequency, modulation mode, annex,
and edge input for the video traffic such as IP address, group name, maximum bandwidth, and so on, to an
Edge Resource Manager (ERM). The D6 discovery protocol also sends unique structured names (topological
location information) for each edge input or carrier output. From these structured names, and input and RF
port numbers, the ERM can infer the topological network location of both the QAM streaming input port
(IP) and RF output port (MPEG).
Contents
• Information About D6 Discovery Protocol, page 33
• How to Configure the D6 Discovery Protocol, page 35
• Example: D6 Discovery Protocol Configuration, page 39
• Deployment Scenario for the D6 Discovery Protocol, page 40
• Feature Information for D6 Discovery Protocol, page 41
Information About D6 Discovery Protocol
The following sections provide more information about the D6 discovery protocol.
Overview of the D6 Discovery Protocol
You should configure the D6 discovery protocol for each Logical Edge Device (LED). When the LED is set
to active, the D6 discovery protocol establishes a connection with the ERM and sends out the below information
to the ERM:
• Streaming Zone—The streaming zone within which the LED operates. You must configure a streaming
zone.
• Component Name—The name of the LED for the ERM to associate the subsequent update messages.
You must configure a component name.
Cisco cBR Converged Broadband Routers Video Features
33
D6 Discovery Protocol
Prerequisites for D6 Discovery Protocol
• Vendor Specific String—Contains the vendor and mode names. When using PME encryption, the D6
vendor-string must be changed to something other than “Cisco”, for example, vendor-string “CBR8”.
For PowerKEY encryption, the vendor-string is an optional configuration and the default value is “Cisco
CBR8k”.
Edge inputs are configured under the LED or the Virtual Carrier Groups (VCG) associated to the LEDs. For
each edge input, the following information is sent to the ERM:
• IP Address—As configured under LED or VCG associated to the LED.
• Port—As configured for each input port.
• Max Bandwidth—As configured under the input group of D6 configuration. The defaults value is 20
Gbps.
• Group name—As configured under the input group of D6 configuration. The default value is the LED
name if the input port is configured under LED or the VCG name if the input port is configured under
VCG
For every QAM (RF channel) configured under the LED through VCG, the following information is sent to
the ERM:
• Route—Route state as Reachable, if a QAM is added, Withdrawn, if a QAM is removed.
• QAM Group Name—As configured for the VCG name.
• QAM Name—Streaming zone.tsid (for example, 1234.100). Streaming zone is configured under D6
and TSID is configured under VCG for every QAM.
• Total Bandwidth— Total bandwidth of the QAM.
• QAM Parameters:
• Frequency—Center frequency of this carrier
• Interleaver
• Modulation Mode
• TSID
• Annex—A/B
• Channel Width - 6 MHz/8 MHz
• UDP Map—This is sent only for the table-based session configurations. A table of the UDP port for
each MPEG program number is sent out through this.
• Output Port—The configured VCG ID is sent out as the Output Port ID.
The configuration updates are sent to the ERM through different update messages. D6 also exchanges the
keep alive messages periodically to retain the TCP connection with the ERM.
Prerequisites for D6 Discovery Protocol
• As the D6 configuration is placed under the LED protocol configuration, you must complete the following
configurations before configuring the D6 discovery protocol:
Cisco cBR Converged Broadband Routers Video Features
34
D6 Discovery Protocol
How to Configure the D6 Discovery Protocol
◦Service Distribution Group (SDG)
◦Virtual Carrier Group (VCG)
◦Bind VCG to SDG
◦Logical Edge Device (LED)
◦Associate VCG to LED
• Since the D6 discovery protocol requires a management IP for communicating with the external server,
ensure that the virtual port group interface is configured and the same is set for the management interface
under cable video. Follow the procedure below to configure a virtual port group:
configure terminal
cable video
mgmt-intf VirtualPortGroup virtual port group id
• If you must configure a Fully Qualified Domain Name (FQDN) for the D6 server configuration instead
of the IP address, then ensure that you configure the name server before configuring the D6 discovery
protocol. Use the show ip dns view command to see if the DNS name server is configured. Follow the
procedure below to configure the name server:
ip name-server ip address
ip domain name domain name
ip domain lookup
How to Configure the D6 Discovery Protocol
You can perform the D6 configuration only when the LED protocol is either table-based or GQI.
Note
To know more about the commands referenced in this section, see theCisco IOS Master Command List.
Configuring the Mandatory D6 Discovery Protocol Parameters
The mandatory D6 configuration parameters are:
• Management IP—The source IP address used to establish connection with the external D6 server (ERM).
The IP address must be in the same subnet as configured in a virtual port group. For GQI LED, this
configuration is not needed under the D6 discovery protocol as it is automatically fetched from the GQI
LED configuration.
• D6 discovery protocol server IP address and port—This is to identify the remote D6 server (ERM) IP
address and listening port used by the D6 client in LED to setup connection with the peer. You can
configure only one server address and port per LED. There are two ways to setup the IP address, either
by directly providing the IP address or by configuring the FQDN. Either one is sufficient for establishing
a connection with the server. If you configure both, then the IP address is preferred over the FQDN.
Both IP address and FQDN configurations must point to the same server and port.
• Streaming zone—Streaming zone as configured in the D6 server (ERM). The name should match with
the one configured in the ERM for the connection to be established.
Cisco cBR Converged Broadband Routers Video Features
35
D6 Discovery Protocol
Configuring the Mandatory D6 Discovery Protocol Parameters
• Component name—The name of the Edge QAM device. Each LED is considered by the D6 server as a
separate Edge QAM component. This name is used by the D6 server to represent the LED.
Before You Begin
Ensure the following:
• Virtual port group interface is configured and a management IP for the D6 discovery protocol is identified
(in case of table-based LED).
• Management interface is set to this virtual port group interface under the cable video configuration.
• You have the D6 server IP address or the FQDN, the port value, and the streaming zone name readily
available.
• If FQDN is to be used, ensure that the name server is configured and the FQDN is resolving to the IP
address by verifying using the ping <fqdn> command.
• The LED is configured with either table-based or GQI protocol.
• The LED turns to active without any issue. If errors occur, resolve them first.
• The LED is set to “no active” state.
To configure the D6 discovery protocol for table-based LEDs, complete the following procedure:
configure terminal
cable video
logical-edge-device device name [id number]
protocol table-based
no active
discovery-protocol d6
mgmt-ip ip address
streaming-zone name
component-name name
d6-server ip address [port]
d6-server fqdn domain-name [port]
exit
active
To configure the D6 discovery protocol for GQI LEDs, complete the following procedure:
configure terminal
cable video
logical-edge-device device name [id number]
protocol gqi
no active
discovery-protocol d6
streaming-zone name
component-name name
d6-server ip address [port]
d6-server fqdn domain-name [port]
exit
active
Cisco cBR Converged Broadband Routers Video Features
36
D6 Discovery Protocol
Configuring the Mandatory D6 Discovery Protocol Parameters
Verifying the D6 Discovery Protocol Configurations
To verify the D6 discovery protocol configuration, use the show cable video logical-edge-device command
as shown in the example below.
This CLI command shows the status and statistics of the D6 client associated to the LED. You can view all
the configuration and operation status of the D6 client. In the example below, it shows the duration and the
number of open, updated, keepalive and notification messages exchanged between the D6 client and the server,
in that duration. It also indicates how many unknown or unrecognized messages are received from the server.
When the open message count is more than 1, it indicates that the connection is terminated and reconnected.
show cable video logical-edge-device id 1 d6
Logical Edge Device: LED_PME
Id: 1
Protocol: Table-based
D6 Summary:
------------------------------------------------Enabled
: Yes
VREP Version
: 2
D6 State
: Established
Management IP
: 1.21.2.250
Source Port
: 6069
D6 server FQDN
: New_host1.test1
D6 Server IP
: 1.200.1.86
D6 Server Port
: 6069
Hold Time(negotiated): 240
Timeout
: 20
Keep Alive Interval : 80
Streaming Zone
: 3409
Failure Reason
: No Failure
------------------------------------------------D6 Statistics:
-------------------------------------------------------------Duration Dir Open
Update
KeepAlive Notification Unknown
-------------------------------------------------------------0
RX
1
0
19
0
0
0
TX
1
17
2
0
0
--------------------------------------------------------------
In the above example, the D6 State as “Established” and the Failure Reason as “No Failure” indicates that the
D6 configurations are adequate and it is able to establish the connection with the D6 server or the ERM.
The D6 Statistics section of the output describes various messages exchanged between the D6 client and the
D6 server in both the directions (Rx means received and Tx means transmitted). There is no update message
from the D6 server to the D6 client, so the Update message count in the RX row should always be 0. The
notification message is sent in case of error. When the notification is received, the connection is reset. Unknown
message count should be 0, any number greater than 0 indicates a packet corruption. Update message is sent
for every update. All the edge input IPs are sent in one update message, but there is a separate update message
for every QAM in the LED. So, the update message count increases based on the number of QAMs in the
LED. KeepAlive messages are exchanged periodically with the interval defined by the "Keep Alive Interval".
This Keep Alive Interval is a function of the Hold time configuration, which is one third of the hold time
Troubleshooting the D6 Mandatory Parameters Configuration
• Troubleshooting tips for possible configuration errors:
Cisco cBR Converged Broadband Routers Video Features
37
D6 Discovery Protocol
Configuring the D6 Discovery Protocol Optional Parameters
• The management IP should be unique and should be in the subnet of the virtual port group.
• If both, D6 server IP address and FQDN are configured, ensure that the same port value is used
for both.
• Ensure that the proper D6 server IP address or FQDN name is used.
• If FQDN is used, verify that the name server is configured and the FQDN gets resolved to the
correct IP address by issuing the ping <fqdn> command.
• Troubleshooting tips when the D6 state remains Idle:
• The failure reason indicates the type of failure. For most of the failures, the D6 client retries the
connection periodically. Check if it recovers after some time.
• Verify if the streaming zone configuration is matching with the D6 server setting.
• Verify if the TCP port number configured for the D6 server in Cisco cBR-8 is matching with the
listening port of the D6 server or the ERM.
• Check if you can ping the D6 server IP address from both the sides, that is, from the Cisco cBR-8
to the D6 server and from the D6 server to the Cisco cBR-8. Try to ping the virtual port group IP
and the management IP assigned to the LED from the D6 server. If the ping fails, check the routing
between the Cisco cBR-8 and the D6 server.
• Verify if the D6 server is up and running and ready to accept the connection.
• Verify if the virtual port group interface is up.
• Verify if the 10 Gb interface through which the management traffic is passing in to the Cisco
cBR-8, is up.
Configuring the D6 Discovery Protocol Optional Parameters
The optional D6 discovery protocol configuration parameters are:
• Vendor string—Vendor specific string for the ERM to identify the vendor. Contains the vendor and the
model name. The default value is "Cisco CBR8k"
• Timeout value—Time to wait for the connection in socket call. The default value is 10 seconds.
• Hold time value —This value decides the interval of the keepalive message exchange between the client
and the server. The default value is 30 seconds.
• Input group—Each virtual edge input (VEI) IP address under the LED can be assigned an input group
name and the maximum bandwidth that is used to send traffic to it. Also, each VCG associated to LED
can have a group name and bandwidth. D6 protocol uses this name for all the VEI IP addresses under
the VCG. This information is used in the D6 messages when advertising the edge inputs to the D6 server.
If these parameters are not configured for the group name, then the LED name for VEI IP addresses
under the LED or the VCG name for the VEI IP addresses under the VCG is used. For bandwidth, the
default value is 20 Gbps.
Repeat this command for each VEI IP address and VCG under the LED.
Before You Begin
Cisco cBR Converged Broadband Routers Video Features
38
D6 Discovery Protocol
Example: D6 Discovery Protocol Configuration
• Ensure that the VEI IP addresses are configured under the LED.
• Ensure that the VCGs are associated to the LED.
To configure the D6 discovery protocol optional parameters, complete the following procedure:
configure terminal
cable video
logical-edge-device device name [id number]
protocol table-based
no active
discovery-protocol d6
vendor-string <string>
timeout seconds
holdtime seconds
input-group vcg id <id> group-name <name>[ bandwidth <mbps>]
input-group led vei-ip <ip> group-name <name>[ bandwidth <mbps>]
exit
active
Verifying the Hold Time and Timeout Settings
To verify the hold time and timeout settings, use the show cable video logical-edge-device command. The
output is the same as shown in the Verifying the D6 Discovery Protocol Configurations, on page 37 section.
The hold time affects the keepalive interval, so the new value for the keepalive interval should be one third
of the hold time. Also, in the D6 statistics section, the keepalive count increases (in the TX row) based on the
keepalive interval.
Troubleshooting the D6 Optional Parameters Configuration
These are optional parameters and do not affect the basic functionalities of D6 discovery protocol. Any change
in the D6 discovery protocol configuration will result in a reset of the D6 connection and a reconnection with
the new values. So, the D6 state will momentarily move to Idle and then back to Established state.
Example: D6 Discovery Protocol Configuration
The following example shows a complete D6 configuration:
cable video
mgmt-intf VirtualPortGroup 0
encryption
linecard 7/0 ca-system pme scrambler dvs042
pme vodsid 111
pme cem 1.200.1.163 5000
pme mgmt-ip 1.25.2.6
service-distribution-group sdg-pme id 1
rf-port integrated-cable 7/0/7
virtual-carrier-group vcg-pme id 1
encrypt
service-type narrowcast
rf-channel 18 tsid 18 output-port-number 23
bind-vcg
vcg vcg-pme sdg sdg-pme
logical-edge-device led-pme id 1
protocol table-based
virtual-edge-input-ip 174.101.1.1 vrf Video-VOD-Vrf input-port-number 1
vcg vcg-pme
Cisco cBR Converged Broadband Routers Video Features
39
D6 Discovery Protocol
Deployment Scenario for the D6 Discovery Protocol
discovery-protocol d6
mgmt-ip 1.25.2.7
vendor-string cBR8
streaming-zone 3509
component-name led56100
d6-server 1.200.1.99 17654
timeout 20
holdtime 60
active
table-based
vcg vcg-pme
rf-channel 18
session sess1 input-port 1 start-udp-port 49152 num-sessions-per-qam 2 processing-type
remap start-program 1 jitter 100 cbr
Deployment Scenario for the D6 Discovery Protocol
The diagram below depicts a typical topology for the D6 feature:
Figure 1: D6 Deployment
• The advertised edge input IPs over D6 protocol to ERM makes the ERM aware of the edge input options
for the QAMs. When multiple VEI IP features are used, the D6 advertises all of the available VEI IPs
to the ERM. This enables the ERM to identify the most feasible edge input IP for sending the video
traffic to the QAMs, based on the physical topology.
• As D6 advertises the QAMs available in the LED, and updates the ERM whenever new QAMs are added
or the existing QAMs are removed, the ERM is always updated about the resources that it owns.
Cisco cBR Converged Broadband Routers Video Features
40
D6 Discovery Protocol
Feature Information for D6 Discovery Protocol
• D6 advertises the UDP port used for each MPEG program number of the table-based sessions. This
enables the ERM to identify the proper use of UDP ranges for each TSIDs or QAMs.
Feature Information for D6 Discovery Protocol
The following table provides release information about the feature or features described in this module. This
table lists only the software release that introduced support for a given feature in a given software release
train. Unless noted otherwise, subsequent releases of that software release train also support that feature.
Use Cisco Feature Navigator to find information about platform support and Cisco software image support.
To access Cisco Feature Navigator, go to www.cisco.com/go/cfn. An account on Cisco.com is not required.
Table 5: Feature Information for D6 Discovery Protocol
Feature Name
Releases
Feature Information
D6 Discovery Protocol
Cisco IOS-XE Release 3.18.0S
This feature was introduced on the
Cisco cBR Series Converged
Broadband Routers.
Cisco cBR Converged Broadband Routers Video Features
41
D6 Discovery Protocol
Feature Information for D6 Discovery Protocol
Cisco cBR Converged Broadband Routers Video Features
42
CHAPTER
5
Switched Digital Video
• Switched Digital Video Services, page 43
• Information About Switched Digital Video, page 45
• How to Configure the Switched Digital Video Services, page 46
• Configuration Examples for Switched Digital Video, page 49
Switched Digital Video Services
The Switched Digital Video (SDV) services are supported for the MPEG video subsystem on the Cisco cBR-8
router. It consists of Multicast IP Packet based video streams that are managed as "Video Sessions".The Cisco
cBR-8 router supports both Any Source Multicast (ASM) and Source Specific Multicast (SSM) sessions.
• For ASM, the input is identified by the group IP address.
• For SSM, the input is identified by the source and group IP address pair.
In both cases, the UDP ports are ignored. Both ASM and SSM can co-exist but cannot overlap in a group IP
address. Hence, for a group IP address, either a single ASM, or one or more SSM can be used.
Session Cloning
Session cloning refers to the ability of forwarding an input to multiple output QAM channels. Only multicast
sessions can be cloned. The output QAM channels are located on the same or different line cards. However,
an input cannot be cloned on the same QAM channel. Cloning is available on session-based GQIv2 or
Table-based sessions. It is applicable to re-mapped, pass-through, and data piping sessions. All cloned sessions
must have the same processing type, bitrate and jitter value. For re-mapped sessions, each output copy will
have a different output program number.
Redundant Multicast Sources
The redundant multicast sources feature supports up to four SSM/ASM multicast address pairs per video
session. However, only multicast traffic from one source is forwarded to the output QAMs. When the active
Cisco cBR Converged Broadband Routers Video Features
43
Switched Digital Video
Redundant Multicast Sources
source fails, another source is chosen automatically. Multicast sources must be unique within a redundant
group and cannot overlap across redundant groups.
The order of the sources is critical when multicast sessions are configured via GQI or VSRM. For a given
group IP address, the source IP addresses must be specified in the same order.
For example: The group IP address 232.1.2.3 used with two sessions must have the source IP addresses
specified in the same order.
Session A configured with group IP 232.1.2.3 source 174.2.3.4 source2 174.4.5.6 source3 174.7.8.9 and
session B or any session created after session A configured using group IP 232.1.2.3, must have the source
IP addresses in this same order as specified for session A. That is, source 174.2.3.4 source2 174.4.5.6 source3
174.7.8.9.
This ensures that all sessions switch to the same source IP address when a source switch occurs. Additionally,
sessions configured via GQI have up to three sources available for redundancy, whereas multicast labels
configured for table-based sessions have up to four sources available for redundancy.
Multicast labels must use unique groups and S/G pairs. These pairs cannot be used by other multicast labels
or by multicast sessions that use S/G pairs. For example, when one multicast session uses {[S1, G], [S2, G]
and [S3, G]}, another session cannot use {[S1, G], [S4, G]}.
Multicast source change is based on the session state; INIT, IDLE, ACTIVE or OFF. A session configured
for the first time is in INIT state and stays in this state for a brief time. If traffic starts before the INIT timer
expires, it moves to the ACTIVE state, otherwise to the IDLE state.
When traffic starts, the session remains in ACTIVE state as long as traffic continues to flow. When traffic
stops for a time longer than the IDLE timer, the session moves to IDLE state. During IDLE state, PAT and
PMT of the session is retained as the output. If traffic resumes in this state, the session moves to ACTIVE
state again with all its previous PSI and remapping information unaltered.
In IDLE state, if traffic does not start or resume before the OFF timer expires, the session transitions to OFF
state. When traffic resumes for a session in OFF state, it is treated as a new session.
Sessions that transition from ACTIVE to IDLE have higher priority and will be moved to the backup source
than those that were newly created and have changed from INIT to IDLE.
Cisco cBR Converged Broadband Routers Video Features
44
Switched Digital Video
Benefits of Switched Digital Video
Benefits of Switched Digital Video
Switched Digital Video provides the following benefits:
• Saves space, maintenance and cost.
• Allows customers to oversubscribe bandwidth.
Prerequisites for Switched Digital Video
• To access multicast capability, configure multicast routing.
• To switch sources for table-based sessions, configure at least two sources for a multicast label and then
associate with the desired session.
Restrictions for Switched Digital Video
• While creating a multicast label, up to four sources can be associated with one group IP address.
• Labels are used with table-based video sessions only.
• Sessions created with GQI Tools do not use labels. However, they can have up to three sources associated
with one group IP address.
Information About Switched Digital Video
QAM Sharing
Unicast and multicast video sessions can co-exist on the same QAM channel for VOD, SDV or Gaming
sessions. QAM sharing requires a common Edge Resource Manager to avoid oversubscription of QAM
resources between services.
Note
QAM sharing with MPTS pass-thru sessions is not supported.
QAM Replication
Multicast sessions can be replicated from one port to other ports on the same line card and/or across line cards.
The difference between a cloned session and replicated sessions is:
• Cloned sessions are initiated by a user on session creation. Each session has a unique session id and may
have different output configuration.
Cisco cBR Converged Broadband Routers Video Features
45
Switched Digital Video
MPTS Pass-through Session
• Replicated sessions have the same output configuration attributes. For sessions that are replicated across
line cards, session on each line card will have its own unique session id.
MPTS Pass-through Session
Switched digital video (SDV) sessions are typically multicast SPTS remap type. The Cisco cBR-8 router also
supports multicast MPTS pass-through and data-piping session types.
The MPTS session is assumed to have no collision in the PID space and program number space with other
sessions that already exist within a QAM. Hence, SPTS remap and MPTS pass-through sessions cannot
co-exist on the same QAM. Otherwise, there might be conflict when the PID and program numbers in the
MPTS and SPTS remuxing are not unique on the output QAM channel.
For a pass-through session:
• The PAT is snooped and regenerated with the correct TSID.
• The PMT and other program data are not changed.
• PID remapping is not performed.
• Input NULL packets are dropped.
• Oversubscription results in random TP dropping, and all ghost PIDs are preserved in the output.
How to Configure the Switched Digital Video Services
Configuring Multicast Routing
You can enable IP Multicast Distributed Switching (MDS) to provide distributed switching of multicast
packets received at the line cards.
enable
configure terminal
ip multicast-routing distributed
ip pim ssm range all-multicasts
ip pim rp-address ip-address
interface type number
ip pim sparse-dense-mode
ip igmp version 3
cable video
multicast-uplink interface-name access-list access-list-name
Configuring Multicast Label
The Cisco cBR-8 router supports up to four multicast address pairs per multicast session for backup purpose.
To specify additional sources for a multicast session for table-based, a label needs to be configured and attached
to the session configuration. A maximum of 2000 multicast labels can be created but only 2048 multicast
addresses can be active at a time.
Cisco cBR Converged Broadband Routers Video Features
46
Switched Digital Video
Configuring Multicast Table-based Sessions
Multicast label is used for table-based session configuration when more than one multicast source [S, G] is
used as backup for the sessions. A mullticast label can only be created or deleted; it cannot be modified. The
multicast label cannot be deleted before the sessions using it are removed.
Groups used by multicast labels must be unique like the multicast S/G pairs. However, sources may be used
by more than one label as long as the group is unique. A maximum of 4 multicast sources is allowed in one
label. If the label is used in multiple sessions, the sessions are considered as cloned sessions.
enable
configure terminal
cable video
table-based
multicast-label label group group-ip source source-ip source2 source-ip source3 source-ip source4
source-ip
Configuring Multicast Table-based Sessions
Similar to table-based unicast session configuration, sessions can be configured as individual sessions under
each QAM carrier that is assigned to a table-based LED.
A multicast session can be configured with a single input multicast input source or multiple input sources for
backup purpose. For multiple backup sources, a label is required to be associated with the session configuration.
Same label can be applied to multiple sessions on different QAM channel. These sessions are considered as
cloned sessions.
For session cloning on multiple QAMs within the same line card, only one copy of the traffic is forwarded to
the line card. The line card replicates the input packets and forwards them to multiple QAMs. Each cloned
copy of a remapped session will have the same or different output program number.
enable
configure terminal
cable video
table-based
vcg vcg-name
rf-channel channel
session session-name group group-ip source source-ip processing-type {remap | passthru |
data} start-program program-num [bit-rate bit-rate-number] [jitter jitter-number] [cbr | vbr]
Configuring Source Switching
Source switching happens automatically when the current source goes down. If more than one source IP is
configured, the software will automatically switch to the next valid source IP, if it is available. However, to
force switch from one valid source to another valid source, use the following commands:
Router(config)#
cable video source-switch from-group group-ip from-source source-ip
or
Router(config)#
cable video source-switch to-group group-ip to-source source-ip
Cisco cBR Converged Broadband Routers Video Features
47
Switched Digital Video
Verifying Switched Digital Video Configuration
Verifying Switched Digital Video Configuration
Router#show cable video session logical-edge-device id 2
Total Sessions = 4
Session
Output
Streaming
Session Session Source
UDP
Output
Input
Output Input
Output
Encrypt Encrypt
Session
Id
Port
Type
Type
Ucast Dest IP/Mcast IP (S,G)
Port Program
State
State Bitrate Bitrate Type
Status
Name
--------------------------------------------------------------------------------------------------------------------------------------------------------------------2097152
142
Remap
SSM
175.2.5.6,232.5.6.7
0
1
OFF
ON
0
0
CLEAR
SESS_PME2.1.7.338
2097153
163
Remap
SSM
175.6.1.13,232.2.1.6
0
2
INIT
ON
0
0
CLEAR
SESS_PME3.1.7.497
2097154
184
Passthru
SSM
175.2.6.7,232.5.6.15
0
OFF
ON
0
0
CLEAR
SESS_PME4.1.7.656
2097155
230
Data-Piping SSM
175.7.2.2,232.2.6.7
0
OFF
ON
0
0
CLEAR
SESS_PME6.1.7.978
Router#show cable video session logical-edge-device id 2 session-id 2097152
Session Name
: SESS_PME2.1.7.338
Session Id:
: 2097152
Creation Time:
: Fri Jun 24 16:30:45 2016
Output Port
TSID
ONID
Number of Sources
Source IP
Group IP
UDP Port
Config Bitrate
Jitter
Processing Type
Stream Rate
Program Number
Idle Timeout
Init Timeout
Off Timeout
Encryption Type
Encryption Status
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
142
142
0
1
175.2.5.6
232.5.6.7
0
not specified
100 ms
Remap
VBR
1
2000 msec
2000 msec
60 sec
CLEAR
-
Input Session Stats:
====================
State: OFF, Uptime: 0 days 00:26:35
IP Packets: In 0, RTP 0, Drop 0
TP Packets: In 0, PCR 0, PSI 0, Null 0
Unreference 0, Discontinuity 0
Errors: Sync loss 0, CC error 0, PCR Jump 0,
Underflow 0, Overflow 0, Block 0
Bitrate: Measured 0 bps, PCR 0 bps
Output Session Stats:
=====================
State: ON, Uptime: 0 days 00:26:35
TP Packets: In 0, PCR 0, PSI 0,
Drop 0, Forward 0, Insert 0
Errors: Info Overrun 0, Info Error 0, Block 0, Overdue 0,
Invalid Rate 0, Underflow 0, Overflow 0
Bitrate: Measured 0 bps
Cisco cBR Converged Broadband Routers Video Features
48
Switched Digital Video
Troubleshooting Switched Digital Video Configuration
Troubleshooting Switched Digital Video Configuration
Problem
Possible Causes
Recommended Solution
%ERROR: Duplicate multicast
source 175.2.5.6 group 232.5.6.7
not allowed for use in label
groupDuplicate.
Group and Source are already used Assign unique group and source
in an existing label.
IPs across multicast labels.
%ERROR: Duplicate multicast
Source has been repeated within a Assign unique source IP within a
source 178.3.3.3 group
label.
multicast label.
232.222.222.222 not allowed
within label DuplicateSourceHere.
%ERROR: Duplicate multicast
Session has been created with a
source 175.2.5.6 group 232.5.6.7 duplicate group IP. This group IP
not allowed for use in this session. has been used in an existing
multicast label.
Create the session with a unique
group IP.
%ERROR Only one multicast
Session has been created on a range RF channel range is not allowed.
session can be created per multicast of RF channels.
Create the session on an RF
session command; rf-channel range
channel.
values, such as rf-channel 20-30,
not allowed.
Configuration Examples for Switched Digital Video
Example 1: Table-based Multicast Session Configuration
enable
configure terminal
ip pim rp-address 9.1.1.1
ip pim ssm range all-multicasts
ip access-list standard all-multicasts
permit 233.0.0.0 0.255.255.255
permit 234.0.0.0 0.255.255.255
permit 235.0.0.0 0.255.255.255
permit 236.0.0.0 0.255.255.255
permit 237.0.0.0 0.255.255.255
permit 238.0.0.0 0.255.255.255
permit 232.0.0.0 0.255.255.255
permit 224.0.0.0 0.255.255.255
permit 239.0.0.0 0.255.255.255
interface TenGigabitEthernet4/1/2
ip address 2.33.1.1 255.255.255.252
ip pim sparse-mode
ip igmp version 3
ip ospf 64512 area 9
load-interval 30
cable video
multicast-uplink TenGigabitEthernet4/1/2 access-list all-multicasts
service-distribution-group sdg-1 id 1
Cisco cBR Converged Broadband Routers Video Features
49
Switched Digital Video
Configuration Examples for Switched Digital Video
rf-port integrated-cable 7/0/0
virtual-carrier-group vcg-1 id 1
service-type narrowcast
rf-channel 0-55 tsid 1-56 output-port-number 1-56
bind-vcg
vcg vcg-1 sdg sdg-1
logical-edge-device led_multicast id 1
protocol table-based
virtual-edge-input-ip 174.102.1.1 input-port-number 1
vcg vcg-1
active
table-based
multicast-label label1 group 232.2.1.1 source 175.2.2.2
vcg vcg-1
rf-channel 0
session mcast1 multicast-label label1 processing-type remap start-program 1 jitter
100 vbr
session mcast2 group 236.0.1.1 source 175.10.5.2 processing-type passthru jitter
100 cbr
Example 2: Table-based Configuration for Replicated Multicast Pass-through Sessions
Below is a table-based configuration for multicast pass-through sessions replicated to all QAM ports on the
same line card.
enable
configure terminal
cable video
multicast-uplink TenGigabitEthernet4/1/2 access-list all-multicasts
service-distribution-group sdg1 id 1
rf-port integrated-cable 7/0/0
rf-port integrated-cable 7/0/1
rf-port integrated-cable 7/0/2
rf-port integrated-cable 7/0/3
rf-port integrated-cable 7/0/4
rf-port integrated-cable 7/0/5
rf-port integrated-cable 7/0/6
rf-port integrated-cable 7/0/7
virtual-carrier-group vcg1 id 1
rf-channel 0-95 tsid 0-95 output-port-number 1-96
bind-vcg
vcg vcg1 sdg sdg1
logical-edge-device led1 id 1
protocol table-based
virtual-edge-input-ip 174.102.1.1 input-port-number 1
vcg vcg1
active
table-based
multicast-label mlabel1 group 236.0.1.1 source 175.10.5.2 source2 175.10.6.20 source3
175.10.7.2
vcg vcg1
rf-channel 0
session mcast1 multicast-label mlabel1 processing-type passthru vbr
rf-channel 5
session mcast2 group 237.0.1.1 source 175.10.6.2 processing-type passthru vbr
Example 3: QAM Sharing Configuration
Below is an example of how to create a PMT encrypted table-based session for both VOD and SDV on the
same QAM channel on 7/0/0 RF port.
cable video
multicast-uplink TenGigabitEthernet4/1/2 access-list all-multicasts
mgmt-intf VirtualPortGroup 0
encryption
Cisco cBR Converged Broadband Routers Video Features
50
Switched Digital Video
Configuration Examples for Switched Digital Video
linecard 7/0 ca-system pme scrambler dvs042
pme vodsid 111
pme cem 1.200.1.163 5000
pme mgmt-ip 1.33.2.6
service-distribution-group sdg1 id 1
rf-port integrated-cable 7/0/0
virtual-carrier-group vcg1 id 1
virtual-edge-input-ip 174.102.1.1 input-port-number 1
encrypt
service-type narrowcast
rf-channel 20-34 tsid 20-34 output-port-number 20-34
bind-vcg
vcg vcg1 sdg sdg1
logical-edge-device led1 id 1
protocol table-based
vcg vcg1
active
table-based
multicast-label mlabel1 group 236.0.1.1 source 175.10.5.2 source2 175.10.6.2 source3
175.10.7.2
vcg vcg1
rf-channel 20
session VOD input-port 1 start-udp-port 49152 processing-type remap start-program
1 jitter 100 vbr
session SDV multicast-label mlabel1 processing-type remap start-program 1000 jitter
100 vbr
!
Example 4: QAM Replication Configuration
Below is an example of how to configure multicast sessions with four backup sources and replicated on
multiple line cards and multiple RF ports within the same line card.
cable video
multicast-uplink TenGigabitEthernet4/1/2 access-list all-multicasts
service-distribution-group sdg-1 id 1
rf-port integrated-cable 7/0/0
rf-port integrated-cable 7/0/1
rf-port integrated-cable 8/0/0
rf-port integrated-cable 8/0/1
virtual-carrier-group vcg-1 id 1
service-type broadcast
rf-channel 0-55 tsid 1-56 output-port-number 1-56
bind-vcg
vcg vcg-1 sdg sdg-1
logical-edge-device led_multicast id 1
protocol table-based
virtual-edge-input-ip 174.102.1.1 input-port-number 1
vcg vcg-1
active
table-based
multicast-label label1 group 232.2.1.1 source 175.2.2.2 source2 175.2.3.2 source3
175.2.4.2 source4 175.5.1.12
vcg vcg-1
rf-channel 0
session mcast1 multicast-label label1 processing-type remap start-program 1 jitter
100 vbr
Example 5: SSM Session Configuration
The following examples show how to configure SSM sessions on a range of QAM channels with three multicast
sources.
table-based
multicast-label label110_1 group 232.2.1.35 source 175.2.2.2 source2 175.6.1.12 source3
175.2.9.2
multicast-label label103_1 group 232.2.1.30 source 175.2.2.2 source2 175.6.1.12 source3
Cisco cBR Converged Broadband Routers Video Features
51
Switched Digital Video
Configuration Examples for Switched Digital Video
175.2.9.2
vcg vcg-uni-multi0
rf-channel 0
session mcast multicast-label label110_1 processing-type remap start-program 1
jitter 100 cbr
rf-channel 6
session mcast multicast-label label103_1 processing-type remap start-program 1
jitter 100 cbr
Example 6: Multicast Session with Virtual Carrier Group as Service Type Broadcast Configuration
virtual-carrier-group VCG_PME0 id 1
service-type broadcast
rf-channel 20-35 tsid 100-115 output-port-number 100-115
table-based
multicast-label a2 group 232.5.6.7 source 175.2.5.6
multicast-label exampleLabel group 232.2.1.6 source 175.6.1.13 source2 175.6.1.12 source3
180.1.1.1 source4 175.6.1.14
vcg VCG_PME2
rf-channel 22
session SESS_PME2 multicast-label a2 processing-type remap start-program 1
vcg VCG_PME3
rf-channel 23
session SESS_PME3 multicast-label exampleLabel processing-type remap start-program
2
Example 7: Sessions with Passthru and Data Processing Type
table-based
multicast-label a2 group 232.5.6.7 source 175.2.5.6
multicast-label exampleLabel group 232.2.1.6 source 175.6.1.13 source2 175.6.1.12 source3
180.1.1.1 source4 175.6.1.14
vcg VCG_PME2
rf-channel 22
session SESS_PME2 multicast-label a2 processing-type remap start-program 1
vcg VCG_PME3
rf-channel 23
session SESS_PME3 multicast-label exampleLabel processing-type remap start-program
2
vcg VCG_PME4
rf-channel 24
session SESS_PME4 group 232.5.6.15 source 175.2.6.7 processing-type passthru
vcg VCG_PME6
rf-channel 30
session SESS_PME6 group 232.2.6.7 source 175.7.2.2 processing-type data
Cisco cBR Converged Broadband Routers Video Features
52
CHAPTER
6
Video MIBs
The SCTE-HMS-MPEG-MIB and SCTE-HMS-QAM-MIB are supported under the video management
framework of Cisco cBR-8 routers.
Note
For Cisco IOS-XE release 3.18.0S, only unicast traffic, that is VOD and SPTS, are supported.
• SCTE-HMS-MPEG-MIB, page 53
• SCTE-HMS-QAM-MIB, page 55
SCTE-HMS-MPEG-MIB
SCTE-HMS-MPEG-MIB MIB module represents the MPEG equipment in the headend. It defines both the
MPEG input and output MIB objects for managing MPEG input and output transport streams, programs and
elementary streams. It provides both input and output related statistics, as well as program mapping and video
session information. It includes the following tables:
mpegInputTSEntry
Provides the details of input transport stream to a video session.
mpegInputProgEntry
Describes the PSI of each incoming program.
mpegProgESEntry
Contains information about the elementary streams in a program.
mpegInputStatsEntry
Each entry in this table describes statistics for each input transport stream.
Cisco cBR Converged Broadband Routers Video Features
53
Video MIBs
SCTE-HMS-MPEG-MIB
mpegInputUdpOriginationEntry
Specifies the UDP unicast or multicast flows of an input transport stream. For unicast streams, it represents
the UDP port and optionally destination IP address of the input transport stream origination UDP IP flow.
For multicast streams, it represents the set of SSM multicast groups of the input transport stream origination
UDP IP flow.
mpegInsertPacketEntry
Describes packet insertion information. Typical packets that are inserted at the RF output of a device are PSI,
PSIP, and CVCT MPEG packets. These packets have their own PID. This table may be empty if the video
device does not support packet insertion or does not have any packet insertion configured.
mpegOutputStatsEntry
Specifies the diagnostic statistics objects for the output transport stream of an MPEG device.
mpegOutputTSEntry
Specifies the attributes of an outgoing transport stream SPTS or MPTS.
mpegOutputProgEntry
Describes the PSI of each outgoing program.
mpegOutputProgElemStatsEntry
Contains the statistical information associated with the elementary streams of an MPEG program.
mpegOutputUdpDestinationEntry
Specifies the UDP unicast or multicast of the output transport stream this entry references.
mpegProgramMappingEntry
Describes program mappings, i.e., ties the input destination to the output destination for every active program
in the device.
mpegVideoSessionEntry
Stores video session information. The session type is VOD, SDV or DB. It captures logical information about
a video stream, such as source and destination addresses, UDP port etc., and also ties this information with
direct mapping of input and output programs.
mpegVideoSessionPtrEntry
Provides a quick reference of the program mapping and input/output transport stream connection information
associated with a video session.
mpegInputTSOutputSessionEntry
Specifies the list of output session indexes that the input transport stream entry is feeding. For unicast sessions,
it typically points to just one output session. For multicast sessions, it points to all the output sessions using
this internally replicated input transport stream.
Cisco cBR Converged Broadband Routers Video Features
54
Video MIBs
SCTE-HMS-QAM-MIB
SCTE-HMS-QAM-MIB
SCTE-HMS-QAM-MIB represents edge QAM equipment present in the headend. It defines QAM channel
related configuration MIB objects associated with physical and logical characteristics of the QAM channel.
It includes the following tables:
qamChannelTable
Describes the configuration and attribution of each QAM channel designated by ifIndex.
qamChannelCommonTable
Describes QAM channel output bandwidth and utilization information designation by ifIndex.
qamConfigTable
Contains the following parameters for a range of QAM Channels:
• IP addresses configuration for the QAM channels (VEI IP Addresses)
• Program number range associated with QAM channels (constant in Cisco cBR-8 routers)
• UDP port range (constant in Cisco cBR-8 routers)
Cisco cBR Converged Broadband Routers Video Features
55
Video MIBs
SCTE-HMS-QAM-MIB
Cisco cBR Converged Broadband Routers Video Features
56