BFS In Band Distribution via

DCM 9900

WAN/LAN LAB (4.2.500) DNCS Systems Integration

Subscriber Networks

Revision 1.1

September 19, 2006

Revision HistoryRevision Date Description Author1.0 8/11/2006 First Revision David Turrie1.1 9/19/2006 Updated DCM configuration (No Transrate group) David Turrie

Table of Contents

TABLE OF CONTENTS................................................................................................3

INTRODUCTION...........................................................................................................4

Purpose........................................................................................................................................4

Audience......................................................................................................................................4

References....................................................................................................................................4

LAB NETWORK CONFIGURATION............................................................................5

Physical Connectivity.................................................................................................................5

Equipment Information.............................................................................................................6

BFS In Band Configuration.......................................................................................................7

Architectural Considerations....................................................................................................9

Configuration Steps (Basic Outline).......................................................................................10DCM 9900 (Gbe with Co-Processor Card)............................................................................10DNCS......................................................................................................................................10Network..................................................................................................................................10

Test Procedure Steps (Basic Outline).........................................................................................11

Introduction

Purpose

This document provides detailed configuration information for distributing BFS In Band (IB) data via the Scientific-Atlanta (S-A) digital content manager (DCM 9900). The DCM9900 is a new product that is gaining traction due to its support for Switched Digital Video (SDV) and Ad Insertion. Operators may also want to take advantage of this device to distribute BFS IB via their Gigabit Ethernet networks allowing them to remove all remnants of their ASI distribution networks.

Audience

This document is intended for Scientific-Atlanta personnel who are experienced with the Digital Video System and basic networking principles.

References

[1] Install Direct ASI.doc, dtd 1/21/2005 (K. Perry)[2] DCM Configuration Guide.pdf

Lab Network Configuration

Physical Connectivity

Figure 1 shows the physical connectivity of the components pertinent to this document.

Figure 1 – Physical Connectivity

Equipment Information

Table 1 – Equipment List

ItemDescription Vendor Hardware Software

ReleaseComments

1 DNCS Scientific-Atlanta (Subscriber)

SUN E450 SR 4.2.0.20

2 HMUX Card Video Propulsion DVP-2764/MT SAIasi package 1.0.0.6

Installed in DNCS

3 CF QAM Scientific-Atlanta (Subscriber)

D9476 2.5.0 BFS QAM

4 Digital Content Manager Scientific Atlanta (Transmissions)

DCM9900 2.00.18 ASI I/O module;Gbe I/O module with co-processor

5 GQAM Scientific-Atlanta (Subscriber)

D9479-1 4.0.3

6 Settops Scientific-Atlanta 8300HD8000HD2000 Rev 5.0 3250HD

1.89.10.11.89.10.11.60.2.11.60.15

7 Aggregation Router Cisco 7606 (Sup7203B) 12.2(18)SXD5 650X 48 port 10/100/1000BT and 650X 24 port Gbe (SFP) modules

8 Remote Switch Router Cisco 4948-L33750-L3

12.2(20)EWA12.2(25)SEB2

BFS In Band Configuration

Table 2 lists the BFS In band sessions used for the test that are automatically setup by the DNCS on the BFS QAM.

Table 2 – Default BFS sessions

#In Band Service

Session IDData Rate

(Mbps)Program # PMT PID

Elementary Stream PID

1 In-Band 00:00:00:00:00:00 02 (0x 02) 1.0 128 (0x80) 112 (0x70) 113 (0x71)2 CAM IB 00:00:00:00:00:00 04 (0x 04) 1.0 129 (0x81) 128 (0x80) 129 (0x81) 3 IPG IB 00:00:00:00:00:00 06 (0x 06) 1.0 130 (0x82) 144 (0x90) 145 (0x91)4 PPV IB 00:00:00:00:00:00 08 (0x 08) 1.0 131 (0x83) 160 (0xA0) 161 (0xA1)5 IPG2 IB 00:00:00:00:00:00 10 (0x 0A) 1.0 132 (0x84) 176 (0xB0) 177 (0xB1)6 IPG3 IB 00:00:00:00:00:00 12 (0x 0C) 1.0 133 (0x85) 192 (0xC0) 193 (0xC1)7 IPG4 IB 00:00:00:00:00:00 14 (0x 0E) 1.0 134 (0x86) 208 (0xD0) 209 (0xD1)8 IPG5 IB 00:00:00:00:00:00 16 (0x 10) 1.0 135 (0x87) 224 (0xE0) 225 (0xE1)9 IPG6 IB 00:00:00:00:00:00 18 (0x 12) 1.0 136 (0x88) 240 (0xF0) 241 (0xF1)

10 IPG7 IB 00:00:00:00:00:00 20 (0x 14) 1.0 137 (0x89) 256 (0x100) 257 (0x101)11 PPV IB2 00:00:00:00:00:00 22 (0x 16) 0.8 138 (0x8a) 272 (0x110) 273 (0x111)12 SDV IB 00:00:00:00:00:00 24 (0x 18) 1.0 139 (0x8b) 288 (0x120) 289 (0x121)13 OSM 00:00:00:00:00:00 199 (0x C7) 3.0 167 (0xa7) 736 (0x2E0) 737 (0x2E1)14 SAIXOD 00:00:00:00:00:00 7000 (0x1B58) 2.0 168 (0xa8) 752 (0x2F0) 753 (0x2F1)

Total 16.80

As is the case with all remote headend installations, a QAM must be directly connected to the DNCS regardless if this QAM is connected to the HFC plan (aka “dummy QAM”) and the operator must configure a separate source definition and session per remote headend for each source. In this case, the session type is a GQAM multicast session. Table 3 shows these sessions for remote 1 GQAM. The multicast sessions for the remote 2 GQAM are identical except for the session MAC ending with 0x11.

Table 3 – Manual GQAM Multicast Sessions

# In Band Service

Session IDData Rate

(Mbps)Program # Multicast IP

1 In-Band 00:00:00:00:00:10 02 1.0 128 (0x80) 232.255.1.1282 CAM IB 00:00:00:00:00:10 04 1.0 129 (0x81) 232.255.1.1293 IPG IB 00:00:00:00:00:10 06 1.0 130 (0x82) 232.255.1.1304 PPV IB 00:00:00:00:00:10 08 1.0 131 (0x83) 232.255.1.1315 IPG2 IB 00:00:00:00:00:10 10 1.0 132 (0x84) 232.255.1.1326 IPG3 IB 00:00:00:00:00:10 12 1.0 133 (0x85) 232.255.1.1337 IPG4 IB 00:00:00:00:00:10 14 1.0 134 (0x86) 232.255.1.1348 IPG5 IB 00:00:00:00:00:10 16 1.0 135 (0x87) 232.255.1.1359 IPG6 IB 00:00:00:00:00:10 18 1.0 136 (0x88) 232.255.1.136

10 IPG7 IB 00:00:00:00:00:10 20 1.0 137 (0x89) 232.255.1.13711 PPV IB2 00:00:00:00:00:10 22 0.8 138 (0x8a) 232.255.1.13812 SDV IB 00:00:00:00:00:10 24 1.0 139 (0x8b) 232.255.1.13913 OSM 00:00:00:00:00:10 199 3.0 167 (0xa7) 232.255.1.16714 SAIXOD 00:00:00:00:00:10 7000 2.0 168 (0xa8) 232.255.1.168

Total 16.80

Architectural Considerations

1. Multicast versus unicast: Since each remote headend distributes the same BFS IB content to the settops, distributing BFS IB on the network using multicast is the obvious choice.

2. MPTS versus SPTS: The operator can either configure the DCM9900 to transmit the BFS IB sources in a single MPTS or each source as a SPTS. I chose SPTS for two reasons:

a. Redundancy: If the operator configured redundant BFS IB sources, then it makes sense for each BFS source to be a SPTS in order for the GQAM (and subsequently the network) to selectively choose an alternate DCM 9900 in the case of a failed individual BFS source. If MPTS, the GQAM will receive all sources when it joins the alternate group/source pair.

b. Troubleshooting: Using SPTS allows the operator to see each BFS source in the multicast routing table and may assist them when a particular BFS source is not functional at the settop.

The one deficiency of using SPTS is that a unique IP address per BFS source is required. Since the number of BFS IB sources is typically limited (Forty is a high number), this should not be a factor for most installations.

3. Source Specific Multicast versus Anycast: Use of SSM is only required if the customer is interested in configuring redundant BFS sources or if they desire to limit the BFS multicast to be received only from a “qualified” video source (i.e. DCM9900). Otherwise, anycast can be used (i.e. IGMPv2/PIM-SM). In this lab system, SSM is configured on the routers; and therefore, the standard IANA IP address range 232/8 is used. The last octet matches the program number for easier identification.

4. Transrating: Transrating is not required since the DNCS transmits BFS via ASI at a constant rate and the settop requires that the multiplexer not alter the data. The BFS programs on the ASI input were dragged to the Gigabit Ethernet output port and assigned a rate per the DNCS GUI settings with a small overhead to avoid continuity errors.

5. Bootloader: Ideally, the same frequency should be allotted for all QAM Carriers forwarding BFS to avoid requiring OSM_Automux. If this is not possible, the operator must enable OSM_Automux, but currently there is a bug (CR 60956) that breaks OSM_Automux in this configuration. Until the bug is fixed and in the release used by the system, the operator must have the same frequency available per remote site for BFS.

Configuration Steps (Basic Outline)

DCM 9900 (Gbe with Co-Processor Card)

1. Assign BFS sources from the programs listed under the DCM ASI input to a Gigabit Ethernet port.

2. Set the multicast IP address for each BFS source per Table 3. (Note: The UDP port is arbitrary – I assigned the same port to all BFS sources for easier troubleshooting).

3. Set the data rate for each output program, matching the BFS Admin setting plus a small overhead.

DNCS

1. For each BFS source, create a source definition with a unique session ID (see Table 3). 2. Choose Multicast Session via GQAM and configure the following:

a. Bandwidth (per BFS Admin Source Configuration)b. QAM Namec. Output Carrier (Ideally, choose the same carrier for all BFS sessions)d. Program Number: Enter the program number per Table 3

Note: The program number is not required for the GQAM to activate the session if SPTS is used. However, specifying the program number is required for the bootloader carousel session; otherwise, CVT will not work . In addition, it may be useful to include the program number for all sessions for future reference when displaying the session on the DNCS GUI.

e. Source Address 1: (Enter DCM 9900’s Gbe IP address)f. Source Address 2 and 3: If using redundant sources, enter the secondary and

tertiary IP addresses. Otherwise, leave blank.g. Input Destination Multicast IP Address: See Table 3h. UDP Port: Leave Blank

Network

1. Configure IP multicast routing on each router2. Enable a multicast routing protocol on the DCM 9900 and GQAM interfaces. For this

test, PIM-SSM was used. 3. Enable IGMPv3 on the GQAM interface (if SSM is used).

Test Procedure Steps (Basic Outline)

For all steps, compare performance with local settops (same models) that receive BFS IB directly from the BFS QAM.

1. IPG Verification

a. Reboot settop.b. Verify the settop boots “Ready QAM” for IPGc. Check the guide for seven days of IPGd. Verify that the mini-carousel discovery file is successfully downloaded.

Results: SUCCESS

2. PPV Verification

a. Tune to a PPV channelb. Ensure the PPV barker shows the latest eventc. Buy a PPV event.

Results: SUCCESS

3. Other In Band Application Verification

a. Tune to a xOD channelb. Verify the client successfully loads. c. Purchase a movie.

Results: SUCCESS

4. Image Download Verification

a. Download an image to a settop via CVT.

Results:

OK if not using OSM Automux. Failed if using OSMAutomux configuration due to a defect on how OSM Kludge Manager obtains the TSID for the remote GQAMs. CR 60956

Note: OSM Automux is required if each GQAM carrier forwarding BFS IB does not match the BFS QAM frequency.