Advanced DOCSIS Set-Top Gateway Application Guide

Transcription

1 Rev B Advanced DOCSIS Set-Top Gateway Application Guide For System Releases 3.7 and 4.2

2

3 Please Read Important Please read this entire guide. If this guide provides installation or operation instructions, give particular attention to all safety statements included in this guide.

4 Notices Trademark Acknowledgments Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at DOCSIS is a registered trademark of of Cable Television Laboratories, Inc. Other third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1009R) Publication Disclaimer Copyright Cisco Systems, Inc. assumes no responsibility for errors or omissions that may appear in this publication. We reserve the right to change this publication at any time without notice. This document is not to be construed as conferring by implication, estoppel, or otherwise any license or right under any copyright or patent, whether or not the use of any information in this document employs an invention claimed in any existing or later issued patent. 2007, 2012 Cisco and/or its affiliates. All rights reserved. Printed in the United States of America. Information in this publication is subject to change without notice. No part of this publication may be reproduced or transmitted in any form, by photocopy, microfilm, xerography, or any other means, or incorporated into any information retrieval system, electronic or mechanical, for any purpose, without the express permission of Cisco Systems, Inc.

5 Contents About This Guide v Chapter 1 Assumptions About Your System 1 Assumptions... 2 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 3 DNCS Configuration for SFM... 4 DNCS Configuration for MFM CMTS Configuration Overview ADSG DHCT Initialization Server Configurations Chapter 3 Customer Information Rev B iii

6

7 About This Guide About This Guide Introduction This application guide is specific to the operation of the Digital Broadband Delivery System (DBDS) network in an Advanced DOCSIS * Set-top Gateway (ADSG) environment. This application guide provides the guidelines for configuring the DBDS for ADSG when single-flow multicast (SFM) or multiflow multicast (MFM) is enabled on the Digital Network Control System (DNCS). * Data-Over-Cable Service Interface Specification Purpose This guide provides guidelines and sample configurations for setting up your overall system and for configuring the DNCS for SFM or MFM in an ADSG environment. This document includes instructions for enabling ADSG within a given cable system. Scope The contents of this document apply to sites that are using DNCS System Releases (SRs) 3.7 and 4.2. This document provides high-level information that applies to the configuration of the DBDS network, including the cable modem termination system (CMTS), for ADSG. This guide provides sample configurations; however, it does not include installation or troubleshooting procedures for ADSG. Audience This guide is written for the following personnel involved in setting up and operating a DBDS in an ADSG environment: DBDS and DNCS system administrators and operators IT system administrators Cisco Services engineers Call-center personnel Rev B v

8 About This Guide Related Publications You may find the following publications useful as resources when you implement the procedures in this document. Check the copyright date on your resources to assure that you have the most current version. The publish dates for the following documents are valid as of this printing. However, some of these documents may have since been revised: DNCS On-line Help (PC) (part number , published December 2006) DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems, RFC 2669 (Available at DOCSIS Set-top Gateway (DSG) Interface Specification, CM-SP-DSG-I , (Available at Dynamic Host Control Protocol, RFC 2131, (Available at Enhanced Channel Maps User's Guide (part number , published December 2006) Host Extensions for IP Multicasting, RFC 1112 (Available at RCS Network Configuration Guide (part number , published August 2005) Note: SR 3.7 and SR 4.2 include online Help that you can access from the DNCS. Document Version This is the second release of this document. vi Rev B

9 1 Chapter 1 Assumptions About Your System Introduction This chapter includes assumptions that Cisco has made concerning your overall system. Use these assumptions only as a guideline when configuring your DBDS network for ADSG. Important! The IP addresses used in this document are only examples. Cable service providers should determine their own IP addressing scheme. In This Chapter Assumptions Rev B 1

10 Chapter 1 Assumptions About Your System Assumptions Cisco makes the following assumptions in respect to your overall system: All servers, including the DNCS, are connected to the headend router through Ethernet. In a private network scenario, DBDS network elements use the 172 network ( ) and the 192 network ( ). In a private network, the "entire 10 network" ( ) is dedicated to end-user devices. The service provider will not use any subnets from the "private 10" network IP addresses that are currently used by existing DHCTs and DBDS network elements. This will eliminate any IP address conflicts. The network supports multicasting. The CMTS software supports ADSG. The DNCS release supports multicast and is streaming multicast traffic to the CMTS while it continues to unicast traffic to the existing quadrature phase shift key (QPSK) modulators, provided that each CMTS and QPSK modulator is defined as an out-of-band (OOB) bridge. Only a CMTS is interested in the multicast traffic streamed by the DNCS. The DHCP servers must implement the specifications as provided in Dynamic Host Control Protocol, RFC 2131, March The term DHCT CPE (customer premise equipment) is equivalent to estb (embedded set-top box). All current and planned ADSG-capable software images for Cisco based platforms (estb) will only operate in ADSG mode; therefore, ADSG-capable software images will not fall back to DAVIC (Digital Audio Visual Counsel) Rev B

11 2 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Introduction This chapter provides guidelines to help you configure the DBDS network to support DSG in an environment where the DNCS is streaming out-of-band data when enabled for SFM or MFM. In this environment, the CMTS is configured for Advanced DSG (ADSG) mode. In This Chapter DNCS Configuration for SFM... 4 DNCS Configuration for MFM CMTS Configuration Overview ADSG DHCT Initialization Server Configurations Rev B 3

12 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode DNCS Configuration for SFM DNCS Overview This section provides guidelines for configuring SFM on the DNCS. Prior to configuring SFM, please note the following definitions within this document concerning a logical CMTS bridge and a physical CMTS device: A logical CMTS bridge refers to the "logical" model of the CMTS bridge as configured and maintained on the DNCS GUI. A physical CMTS device refers to the physical CMTS hardware that resides in the headend or hub of a given cable system. The relationship between the DNCS GUI-configured logical CMTS bridge and the actual physical CMTS device is such that the logical CMTS bridge may represent one or many physical CMTS devices. The SFM IP address is used by the DNCS to send out-of-band data to all DHCTs. A single multicast address (referred to as single-flow multicast) is entered for each set of out-of-band data that is sent to a logical CMTS bridge. Many physical CMTS devices may be configured to join a given set of out-of-band data. A set of out-of-band data in an SFM environment comprises all out-of-band data using the same multicast Internet protocol (IP) address. The out-of-band data consists of the following message types: Out-of-band BFS data carousels UNConfigIndication (UNCI) messages UNPassThru (PT) messages System information (SI) Conditional access (CA) information Note: These types of out-of-band data are distinguished by destination UDP ports Rev B

13 DNCS Configuration for SFM Configure SFM on the DNCS When configuring SFM on the DNCS, a single multicast address is entered for each CMTS bridge. When organizing and defining CMTS bridges, consider the following relationships: CMTS Bridge and FIPS Code Area: Typically, only one CMTS bridge is required for each hub. However, the system operator should ensure that a given CMTS does not include more than one Federal Information Processing Standards (FIPS) code area. This means that the system operator should maintain a relationship of one CMTS bridge per FIPS code area. This could result in more than one CMTS bridge defined per hub. Hubs, CMTS Bridges, and Channel Lineups: The DBDS associates channel lineups with hubs. The DBDS also associates at least one CMTS bridge per hub; therefore, there is at least one bridge per hub. It is important that the system operator determine the relationship between CMTS bridges and the hubs they belong to in order to properly configure SFM on the DNCS. As a final configuration task, the system operator should identify each physical CMTS device that is associated with the logical CMTS bridge modeled on the DNCS. Note: For the remainder of this section, only one logical CMTS bridge is assumed. This means that one multicast IP address is provisioned for each defined hub. The following diagram illustrates how the DNCS transmits out-of-band data to each multicast address Rev B 5

14 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Using the Existing DNCS Interface for SFM Introduction Using the DNCS GUI, a system operator will setup a CMTS and a CMTS bridge to provision a SFM IP address for a set of out-of-band data that is destined to a specific bridge. The system operator must provide the following information on the GUI interface: A hub to associate with the bridge A bridge name An IP flow scheme defined as SFM The name and IP address of the CMTS hosting the bridge (the presence of this field is dependent upon the DNCS software version) A multicast IP address A DHCT Communication Mode (DCM) defined as DOCSIS for set-tops that are using DSG; a DCM setting of DAVIC for set-tops that are not using DSG After the DNCS is configured, it starts sending out each out-of-band message type using a multicast destination IP address that was provided by the system operator. If a group of CMTSs share the same out-of-band traffic, the system operator must only provision one multicast IP address on the DNCS GUI. Configuring SFM on the DNCS 1 From the DNCS Administrative Console, click Network Element Provisioning and then click QPSK/CMTS. The QPSK/CMTS List window opens Rev B

15 DNCS Configuration for SFM 2 From the File menu, click New and select CMTS. The Set Up CMTS window opens. 3 From the Hub Name field, click the arrow to select the hub to which the CMTS bridge is connected. Note: If needed, you can assign a different hub to each CMTS bridge 4 From the Bridge Name field, type a name for the bridge. 5 For IP flow, select SFM. 6 From the IP Address field, type an IP address for this bridge that is unique and is within the range of IP addresses reserved for multicasting. Note: Although the IPV4 multicast IP address range is to , Cisco recommends that you use one of the following ranges depending on whether you are using SSM (source-specific multicast). Not using SSM (IPV4 local range): to Using SSM (IANA reserved SSM [local host allocation]): to Click the DCM option and select DOCSIS. Note: Select DOCSIS because the set-top is using DSG. 8 From the SRM IP field, enter the IP address of your Session Resource Manager (SRM). Note: Refer to your network map to obtain the IP address of the SRM Rev B 7

16 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 9 If a vendor other than Cisco provides your conditional access system, click the Disable EMM Generation option to disable Cisco s PowerKEY EMMs. Note: When disabling PowerKEY EMMs, all DHCTs that have signed on and reported the ID for the CMTS bridge will not receive PowerKEY EMMs. In addition, new EMMs will not be generated for any DHCTs associated with the CMTS bridge 10 Click Save. The Set Up CMTS Bridge window closes and the CMTS bridge is listed in the QPSK/CMTS List window. Important! When configuring SFM on the DNCS, a single multicast address is entered for each logical CMTS bridge. Only one logical CMTS bridge is typically required for each hub; however, the system operator should carefully take into consideration the Federal Information Processing Standards (FIPS) code area when defining bridges. This may result in more than one logical bridge per hub. The system operator must identify the physical CMTSs that are associated with each logical bridge. 11 Do you need to set up another CMTS bridge? If yes, for each new bridge that you want to add to the DNCS, repeat steps 2 through 10. If no, you have successfully set up all the CMTS bridges for this CMTS chassis. Select the File menu and click Close to close the QPSK/CMTS List window. CMTS Configuration Overview Note: Cisco has tested ADSG with a Cisco CMTS; therefore, a Cisco CMTS is assumed throughout this document. After the DNCS is configured with SFM, you will also need to configure ADSG on the CMTS. Each CMTS in the system includes a single DSG agent. The DSG agent is configured to map all appropriate Cisco out-of-band IP flows onto the appropriate DOCSIS downstream channels based on the source and destination IP address in the defined classifiers. The DSG agent is configured to send this data to any MAC address that the operator deems appropriate. Note: The MAC address can be unicast or multicast (Host Extensions for IP Multicasting, RFC 1112, August 1999). The CMTS is configured so that the downstream channel descriptor (DCD) message sent on each DSG channel that is carrying Cisco out-of-band flows contains necessary rules and classifiers. These rules and classifiers identify the availability and location (within that DSG channel) of the out-of-band flows for the Cisco DSG clients Rev B

17 DNCS Configuration for SFM The DHCT does not have prior knowledge of the DSG tunnel address when it is searching for the appropriate DOCSIS downstream. Instead, the DHCT parses the DCD message and determines which, if any, Cisco DSG clients (client IDs) are listed in the DCD message. If the required client IDs are listed in the DCD message, the DHCT will remain on the DSG channel to receive the out-of-band data. If the required client IDs are not listed in the DCD message, the DHCT will continue searching for out-of-band data. CMTS Global Configuration in a Non-Straddle Environment A "non-straddle environment" is defined as a single DOCSIS RF downstream that covers the DHCT populations that are served by the same hub. The system operator should configure the following criteria in a non-straddle environment: DSG tunnels with their respective MAC address DSG classifiers that allow the CMTS to route traffic to the appropriate DSG tunnel Client lists that are used by the DHCT to pick rules that apply to it CMTS Interface Configuration Each interface on the CMTS device that receives multicast traffic must have several customized configurations. These configurations must specifically address the following two scenarios for configuring the CMTS: Non-Hub Straddling (on page 10) Hub Straddling (Regionalization) (on page 14) The general IP multicast CMTS configurations include the following scenarios: Each interface that receives multicast traffic must be enabled with Protocol Independent Multicast (PIM). RF Interfaces that forward multicast traffic must be statically configured using the CMTS to join the Cisco out-of-band multicast groups defined on the DNCS. Note: Some Internetwork Operating Systems (IOS), for example, Cisco, automatically include the "ip igmp static" command when the "cable downstream DSG Rule" is configured. If this occurs for your CMTS, configuring the "ip igmp static" command will not be necessary. DSG Rules should be configured on the downstreams to which they apply. This will result in a different DCD message sent from each downstream. The configuration of a DSG "Classifier" is required. The DSG Classifier enables the DSG agent to map the IP multicast address to the DSG tunnel. If ports are not included in the DSG classifier or if the DSG classifier is not included in the DCD message, the set-top will filter the Cisco DSG data based on existing, well-known port numbers Rev B 9

18 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Non-Hub Straddling Non-hub straddling includes the configuration of the CMTS when the CMTS' downstream message traffic is entirely contained within a single hub. When the CMTS message traffic is isolated in this manner, the resulting message traffic is defined as "non-hub straddling" (from a client set-top perspective). When the set-top tunes to receive downstream message traffic, it receives messages that were generated only for the given hub in which the set-top resides. The scenarios in Example: Non-Hub Straddling (on page 11) address a CMTS in which message traffic is categorized as non-hub straddling. Notes: In the following examples, the first usable IP address is configured as the gateway IP address. It is strongly recommended that the service provider prevent DBDS multicast traffic from flowing to the home network by applying MIB filters to stand-alone cable modems. These filters are defined in the DOCSIS Cable Device MIB Cable Device Management Information Base for DOCSIS compliant Cable Modems and Cable Modem Termination Systems, RFC 2669, August The following scenarios are only examples. To acquire a more up-to-date sample, refer to your current CMTS configuration. The line numbers to the left of the example CMTS configuration scenarios are for illustrative and explanatory purposes only. They are not indicative of actual CMTS device listings Rev B

19 DNCS Configuration for SFM Example: Non-Hub Straddling The following list describes various command lines within the example: Lines 2-3 define the client list. Lines 4-5 define the DSG tunnels. Lines 6-7 define the destination IP address and port (classifiers). Line 9 defines the interface name. Line 10 defines the interface IP address. Lines 11, 18, 27, and 52 enable the Protocol Independent Multicast (PIM). Lines 30 and 55 statically configure IGMP on the RF interface that forwards IP multicast traffic. Lines 31 and 56 enable DCD. Lines 32 and 57 specify Rule 1 priority, clients, and tunnel for this downstream interface. Line 33 and 58 specify Rule 1 classifiers for this downstream interface. 1 ip multicast-routing 2 cable dsg client-list 1 id-index 1 mac-addr 0001.a6d0.0b1e 3 cable dsg client-list 1 id-index 2 ca-system-id E00 4 cable dsg tunnel 1 mac-addr e cable dsg tunnel 2 mac-addr e cable dsg cfr 1 dest-ip tunnel 1 dest-port priority 0 srcip cable dsg cfr 2 dest-ip tunnel 2 dest-port priority 0 srcip ! 9 interface FastEthernet0/0 10 ip address ip pim sparse-dense-mode 12 ip mroute-cache 13 duplex full 14 no keepalive 15! 16 interface FastEthernet1/0 17 ip address ip pim sparse-dense-mode Rev B 11

20 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 19 ip mroute-cache 20 duplex full 21 no keepalive 22! 23 interface Cable3/0 24 ip address secondary 25 ip address ip helper-address ip pim sparse-dense-mode 28 cable dhcp-giaddr policy 29 ip dhcp relay information option 30 ip igmp static-group cable downstream dsg dcd-enable 32 cable downstream dsg rule 1 priority 1 clients 1 tunnel 1 33 cable downstream dsg rule 1 classifiers 1 34 ip mroute-cache 35 cable insertion-interval cable downstream annex B 37 cable downstream modulation 64qam 38 cable downstream interleave-depth cable downstream frequency cable downstream channel-id 0 41 cable upstream 0 frequency cable upstream 0 power-level 2 43 cable upstream 0 channel-width cable upstream 0 minislot-size cable upstream 0 modulation-profile 6 46 no cable upstream 0 shutdown 47! 48 interface Cable4/0 49 ip address secondary 50 ip address ip helper-address ip pim sparse-dense-mode 53 cable dhcp-giaddr policy Rev B

21 DNCS Configuration for SFM 54 ip dhcp relay information option 55 ip igmp static-group cable downstream dsg dcd-enable 57 cable downstream dsg rule 1 priority 1 clients 1 tunnel 2 58 cable downstream dsg rule 1 classifiers 2 59 ip mroute-cache 60 cable insertion-interval cable insertion-interval cable downstream annex B 63 cable downstream modulation 64qam 64 cable downstream interleave-depth cable downstream frequency cable downstream channel-id 0 67 cable upstream 0 frequency Rev B 13

22 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Hub Straddling (Regionalization) This section describes the second CMTS configuration option in which the downstream message traffic from the CMTS is not entirely contained within a single hub. When CMTS message traffic is not isolated to a single hub, the resulting message traffic is defined as "hub straddling" (from a client set-top perspective). When the set-top tunes to receive downstream message traffic, it can potentially receive messages that were generated for more than the single given hub in which the set-top box resides. Go to Example: Hub Straddling (on page 15) to see an example that addresses a CMTS in which message traffic is categorized as hub straddling. In this case, the DCD rules define the hub data in which the set-top will use. The DCD data is described as follows. As mentioned in the DNCS Overview (on page 4), a set of DSG data in an SFM environment comprises all out-of-band data (BFS, CA, PT, SI, and UNCI message types). This out-of-band data utilizes the same multicast IP address. Each set of DSG data on a given DSG channel is associated with a unique upstream channel ID or a set of upstream channel IDs. The CMTS device is configured such that the DCD rules associated with a set of DSG data is marked with the UCIDs of the associated upstream channels. When a DOCSIS twoway connection is achieved, the set-top selects the correct DCD rules to use and, consequently, receives the correct set of DSG data. To help clarify this concept, see Example: Hub Straddling (on page 15). Notes: Set-tops that reside in a hub must have their upstream channels connected to the same upstream ports. The UCID range always starts with one (1) even though the labeling of the physical upstream cable interface on some CMTS vendors starts with zero (0). In other words, for set-tops connected to "US0," their corresponding UCID is one (1) Rev B

23 DNCS Configuration for SFM Example: Hub Straddling The following list describes various command lines within the example: Lines 2-3 define the client list. Lines 5-7 define the DSG tunnels. Lines 9-11 define the destination IP address and port (classifiers). Lines 15, 22, 31, and 61 enable the Protocol Independent Multicast (PIM). Lines 34, 35, 64, and 65 statically configure IGMP on the RF interface that forwards IP multicast traffic. Lines 36 and 65 enable DCD. Lines 37 to 39 define the DSG rule with priority, clients, tunnel, UCID, and classifiers for hub #1. Lines 40 to 42 define the DSG rule with priority, clients, tunnel, UCID, and classifiers for hub #2. Lines 66 and 67 define the DSG rule with priority, clients, tunnel, UCID, and classifiers for hub #3. 1 ip multicast-routing 2 cable dsg client-list 1 id-index 1 mac-addr 0001.a6d0.0b1e 3 cable dsg client-list 1 id-index 2 ca-system-id E00 4! 5 cable dsg tunnel 1 mac-addr e cable dsg tunnel 2 mac-addr e cable dsg tunnel 3 mac-addr e ! 9 cable dsg cfr 1 dest-ip tunnel 1 dest-port priority 0 src-ip cable dsg cfr 2 dest-ip tunnel 2 dest-port priority 0 src-ip cable dsg cfr 3 dest-ip tunnel 3 dest-port priority 0 src-ip ! 13 interface FastEthernet0/0 14 ip address ip pim sparse-dense-mode 16 ip mroute-cache 17 duplex full Rev B 15

24 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 18 no keepalive 19! 20 interface FastEthernet1/0 21 ip address ip pim sparse-dense-mode 23 ip mroute-cache 24 duplex full 25 no keepalive 26! 27 interface Cable3/0 (STRADDLE CONFIGURED ON THIS DOWNSTREAM) 28 ip address secondary 29 ip address ip helper-address ip pim sparse-dense-mode 32 cable dhcp-giaddr policy 33 ip dhcp relay information option 34 ip igmp static-group ip igmp static-group cable downstream dsg dcd-enable 37 cable downstream dsg rule 1 priority 1 clients 1 tunnel 1 38 cable downstream dsg rule 1 ucid 2 39 cable downstream dsg rule 1 classifiers 1 40 cable downstream dsg rule 2 priority 1 clients 1 tunnel 2 41 cable downstream dsg rule 2 ucid 4 42 cable downstream dsg rule 2 classifiers 2 43 ip mroute-cache 44 cable insertion-interval cable downstream annex B 46 cable downstream modulation 64qam 47 cable downstream interleave-depth cable downstream frequency cable downstream channel-id 0 50 cable upstream 0 frequency cable upstream 0 power-level Rev B

25 DNCS Configuration for SFM 52 cable upstream 0 channel-width cable upstream 0 minislot-size cable upstream 0 modulation-profile 6 55 no cable upstream 0 shutdown 56! 57 interface Cable4/0 (NO STRADDLE CONFIGURED ON THIS DOWNSTREAM) 58 ip address secondary 59 ip address ip helper-address ip pim sparse-dense-mode 62 cable dhcp-giaddr policy 63 ip dhcp relay information option 64 ip igmp static-group cable downstream dsg dcd-enable 66 cable downstream dsg rule 1 priority 1 clients 1 tunnel 3 67 cable downstream dsg rule 1 classifiers 3 68 ip mroute-cache 69 cable insertion-interval cable insertion-interval cable downstream annex B 72 cable downstream modulation 64qam 73 cable downstream interleave-depth cable downstream frequency cable downstream channel-id Rev B 17

26 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode DNCS Configuration for MFM DNCS Overview This section provides guidelines for configuring MFM on the DNCS. Prior to configuring MFM, please note the following definitions within this document concerning a logical CMTS bridge and a physical CMTS device: A logical CMTS bridge refers to the "logical" model of the CMTS bridge as configured and maintained on the DNCS GUI. A physical CMTS device refers to the physical CMTS hardware that resides in the headend or hub of a given cable system. The relationship between the DNCS GUI-configured logical CMTS bridge and the actual physical CMTS device is such that the logical CMTS bridge may represent one or many physical CMTS devices or one physical CMTS can represent more than one bridge. When configuring MFM on the DNCS, a multicast IP address is entered for each flow. When MFM is enabled, the DNCS divides the out-of-band traffic into the following "flow" types: System-wide flow Site-specific flow (if applicable) Hub-specific flow Bridge-specific flow Rev B

27 DNCS Configuration for MFM Configuring MFM on the DNCS Important! The MFM feature must be enabled on the DNCS. If you do not see the MFMC feature, please contact Cisco Services. 1 From the DNCS Administrative Console, click Network Element Provisioning, and then click MFMC. The Multiflow Multicast: System Wide OOB IP Flow window opens. 2 From the IP Recommended Range section, click the IPV4 Org. Local Scope box. Notes: It is recommended that the operator use IP addresses from the Local Scope range. If Source Specific Multicast (SSM) is enabled on the network, select the IANA Reserved SSM option. If you do not select an option, you can use any IP address within the to range that is not reserved by the IANA Rev B 19

28 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 3 From the left frame, click OOB IP Address Restriction List to provision IP address ranges that are prohibited from being used on the network. 4 From the left frame, click System-Wide Out-of-Band IP Flow (on page 22), Site- Specific Out-of-Band IP Flow (on page 22), Hub-Specific Out-of-Band IP Flow (on page 24), or Bridge-Specific Out-of-Band IP Flow (on page 24) to configure or view details about specific IP flow types. 5 Input appropriate values into the IP flow-specific screen and then click Save. 6 Click Exit to close the Multiflow Multicast window. 7 To provision Bridge-Specific Flow, go to the DNCS Administrative Console, click Element Provisioning, and then click QPSK/CMTS. The QPSK/CMTS List window opens Rev B

29 DNCS Configuration for MFM 8 From the File menu, select New and then select CMTS. The Set Up CMTS Bridge window opens. 9 From the Hub Name field, select the hub to which this bridge is connected. 10 From the Bridge Name box, type a name for the bridge. 11 From the IP Flow Scheme options, select MFM. Note: When enabled, the appearance of this button is yellow. 12 From the IP Address box, type an IP address that is unique and is within the range of IP addresses chosen in steps 2 and 3 of this procedure. 13 From the DCM menu, select DOCSIS. Note: Select DOCSIS for set-tops that are going to use DSG; otherwise, select DAVIC. 14 If a vendor other than Cisco provides your conditional access system, click the Disable EMM Generation option to disable Cisco s PowerKEY EMMs. Note: When disabling PowerKEY EMMs, all DHCTs that have signed on and reported the ID for the CMTS bridge will not receive PowerKEY EMMs. In addition, new EMMs will not be generated for any DHCTs associated with the CMTS bridge. 15 From the SRM IP field, type the IP address of your Session Resource Manager (SRM). 16 Click Multiflow Multicast to view or edit the configuration data for any multicast IP flows on the system Rev B 21

30 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 17 If you modify any fields within the Multiflow Multicast GUIs, click Save. 18 Close the the Multiflow Multicast GUI by clicking Exit. 19 From the Set Up CMTS Bridge window, click Save. System-Wide Out-of-Band IP Flow This System-Wide Flow GUI allows the system operator to provision a system-wide IP flow on the DNCS. This IP flow refers to traffic that is intended for all DHCTs on a specific system. For example, the DNCS at the headend would use the system-wide OOB IP address to send PowerKEY conditional access (CA) data to all DHCTs on the DBDS network (for example, a site). Note: For systems using a Remote Network Control Server (RNCS), the operator should configure both system-wide out-of-band IP addresses and site-wide out-ofband IP addresses. This configuration allows distributed applications to use the site address, and applications that are not yet site-aware to use the system-wide address Rev B

31 DNCS Configuration for MFM Site-Specific Out-of-Band IP Flow The Site Wide OOB IP Flow GUI allows the system operator to provision a sitespecific IP flow on the DNCS. This IP flow refers to traffic that is intended for all DHCTs at a site. For example, a Lights Out Network Node (LIONN) would send BFS data to sites using the site-wide OOB IP address. Important! This GUI interface is only available if the Regional Control System (RCS) feature is enabled (multiple site headends). Refer to the RCS Network Configuration Guide for more details. Note: For systems using a Remote Network Control Server (RNCS), the operator must configure both site-wide out-of-band IP addresses and system-wide out-of-band IP addresses. This allows distributed applications to use the site address and applications that are not yet site-aware to use the system-wide address Rev B 23

32 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Hub-Specific Out-of-Band IP Flow The DNCS supports the following Hub-Specific Flow GUI interface. This interface allows the operator to provision a hub-specific flow. For example, system information (SI) would be sent to hubs using the hub-wide OOB IP address. Bridge-Specific Out-of-Band IP Flow The system operator uses the Set Up CMTS Bridge GUI on the DNCS to provision the bridge-specific flow. For example, UNPassThru messages can be sent to each CMTS bridge that is using the CMTS bridge IP Address. For more details, see steps 1 through 14 in Configuring MFM on the DNCS (on page 19). Note: The operator should carefully take into consideration the Federal Information Processing Standard (FIPS) code area when defining a bridge Rev B

33 CMTS Configuration Overview CMTS Configuration Overview This section provides guidelines for configuring ADSG on the CMTS when the DNCS is configured with MFM. Note: The global and interface configurations of the CMTS are the same as in the SFM case. For details, refer to CMTS Global Configuration in a Non-Straddle Environment (on page 9). Partial Configuration Example of a CMTS (No Straddle or Regionalization) The following examples show a partial configuration of a CMTS when there is no hub or bridge straddling in the DBDS network Rev B 25

34 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Example: No Straddle or Regionalization The following list describes various command lines within the example: Lines 2-3 define the client list. Lines 4-8 define the DSG tunnels. Lines 9-18 define the destination IP address and port (classifiers). Lines and statically configure IGMP on the RF interface that forwards IP multicast traffic. Lines 39 and 70 enable DCD. Lines 40 and 71 specify Rule 1 priority, clients, and tunnel. Lines 41 and 72 specify Rule 1 classifiers. Lines 42 and 73 specify Rule 2 priority, clients, and tunnel. Lines 43 and 74 specify Rule 2 classifiers. Lines 44 and 75 specify Rule 3 priority, clients, and tunnel. Lines 45 and 76 specify Rule 3 classifiers. 1 ip multicast-routing 2 cable dsg client-list 1 id-index 1 mac-addr 0001.a6d0.0b1e 3 cable dsg client-list 1 id-index 2 ca-system-id E00 4 cable dsg tunnel 1 mac-addr e cable dsg tunnel 2 mac-addr e40.010a 6 cable dsg tunnel 3 mac-addr e cable dsg tunnel 4 mac-addr e40.020a 8 cable dsg tunnel 5 mac-addr e cable dsg cfr 1 dest-ip tunnel 1 dest-port priority 0 src-ip cable dsg cfr 2 dest-ip tunnel 2 dest-port priority 0 src-ip cable dsg cfr 3 dest-ip tunnel 3 dest-port priority 0 src-ip cable dsg cfr 4 dest-ip tunnel 4 dest-port priority 0 src-ip cable dsg cfr 5 dest-ip tunnel 5 dest-port priority 0 src-ip ! 15 interface FastEthernet0/ Rev B

35 CMTS Configuration Overview 16 ip address ip pim sparse-dense-mode 18 ip mroute-cache 19 duplex full 20 no keepalive 21! 22 interface FastEthernet1/0 23 ip address ip pim sparse-dense-mode 25 ip mroute-cache 26 duplex full 27 no keepalive 28! 29 interface Cable3/0 30 ip address secondary 31 ip address ip helper-address ip pim sparse-dense-mode 34 cable dhcp-giaddr policy 35 ip dhcp relay information option 36 ip igmp static-group ip igmp static-group ip igmp static-group cable downstream dsg dcd-enable 40 cable downstream dsg rule 1 priority 1 clients 1 tunnel 1 41 cable downstream dsg rule 1 classifier 1 42 cable downstream dsg rule 2 priority 1 clients 1 tunnel 2 43 cable downstream dsg rule 2 classifiers 2 44 cable downstream dsg rule 3 priority 1 clients 1 tunnel 3 45 cable downstream dsg rule 3 classifiers 3 46 ip mroute-cache 47 cable insertion-interval cable downstream annex B 49 cable downstream modulation 64qam 50 cable downstream interleave-depth Rev B 27

36 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 51 cable downstream frequency cable downstream channel-id 0 53 cable upstream 0 frequency cable upstream 0 power-level 2 55 cable upstream 0 channel-width cable upstream 0 minislot-size 57 cable upstream 0 modulation-profile 6 58 no cable upstream 0 shutdown 59! 60 interface Cable4/0 61 ip address secondary 62 ip address ip helper-address ip pim sparse-dense-mode 65 cable dhcp-giaddr policy 66 ip dhcp relay information option 67 ip igmp static-group ip igmp static-group ip igmp static-group cable downstream dsg dcd-enable 71 cable downstream dsg rule 1 priority 1 clients 1 tunnel 1 72 cable downstream dsg rule 1 classifier 1 73 cable downstream dsg rule 2 priority 1 clients 1 tunnel 4 74 cable downstream dsg rule 2 classifiers 4 75 cable downstream dsg rule 3 priority 1 clients 1 tunnel 5 76 cable downstream dsg rule 3 classifiers 5 77 ip mroute-cache 78 cable insertion-interval cable insertion-interval cable downstream annex B 81 cable downstream modulation 64qam 82 cable downstream interleave-depth cable downstream frequency cable downstream channel-id 0 85 cable upstream 0 frequency Rev B

37 CMTS Configuration Overview Partial Configuration Example of a CMTS (Hub Straddle) The system-wide flow is sent to all DHCTs in a given system. Hub straddle occurs when a DHCT is able to see more than one set of hubs and bridge-specific traffic on a downstream. The CMTS is configured so that the DCD rules associated with the hub and bridgespecific flows are marked with the UCIDs from the associated upstream channels. When a DOCSIS two-way connection is achieved, the DHCT selects the correct rules to employ and consequently receives the correct hubs and bridge-specific flows. Note: Set-tops that reside in a hub must have their upstream channels connected to the same upstream ports. Example: Hub Straddle The following list describes various command lines within the example: Lines 2-3 define the client list. Lines 5-11 define the DSG tunnels. Lines define the destination IP address and port. Lines statically configure IGMP on the RF interface that forwards IP multicast traffic. Line 49 enables DCD. Lines define the DSG rule with priority, clients, tunnel, UCID, and classifiers for system-wide flow (hub #1 and Hub #2). Lines define the DSG rule with priority, clients, tunnel, UCID, and classifiers for bridge #1, hub # Rev B 29

38 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Lines define the DSG rule with priority, clients, tunnel, UCID, and classifiers for hub-specific, hub #1. Lines define the DSG rule with priority, clients, tunnel, UCID, and classifiers for bridge #2, hub #2. Lines define the DSG rule with priority, clients, tunnel, UCID, and classifiers for hub-specific, hub #2. 1 ip multicast-routing 2 cable dsg client-list 1 id-index 1 mac-addr 0001.a6d0.0b1e 3 cable dsg client-list 1 id-index 2 ca-system-id E00 4! 5 cable dsg tunnel 1 mac-addr e cable dsg tunnel 2 mac-addr e40.010a 7 cable dsg tunnel 3 mac-addr e cable dsg tunnel 4 mac-addr e40.020a 9 cable dsg tunnel 5 mac-addr e cable dsg tunnel 6 mac-addr e40.030a 11 cable dsg tunnel 7 mac-addr e ! 13 cable dsg cfr 1 dest-ip tunnel 1 dest-port priority 0 src-ip cable dsg cfr 2 dest-ip tunnel 2 dest-port priority 0 src-ip cable dsg cfr 3 dest-ip tunnel 3 dest-port priority 0 src-ip cable dsg cfr 4 dest-ip tunnel 4 dest-port priority 0 src-ip cable dsg cfr 5 dest-ip tunnel 5 dest-port priority 0 src-ip cable dsg cfr 6 dest-ip tunnel 6 dest-port priority 0 src-ip cable dsg cfr 7 dest-ip tunnel 7 dest-port priority 0 src-ip ! 21 interface FastEthernet0/0 22 ip address ip pim sparse-dense-mode 24 ip mroute-cache Rev B

39 CMTS Configuration Overview 25 duplex full 26 no keepalive 27! 28 interface FastEthernet1/0 29 ip address ip pim sparse-dense-mode 31 ip mroute-cache 32 duplex full 33 no keepalive 34! 35 interface Cable3/0 36 ip address secondary 37 ip address ip helper-address ip pim sparse-dense-mode 40 cable dhcp-giaddr policy 41 ip dhcp relay information option 42 ip igmp static-group ip igmp static-group ip igmp static-group ip igmp static-group ip igmp static-group cable downstream dsg dcd-enable 48 cable downstream dsg rule 1 priority 1 clients 1 tunnel 1 (RULE FOR SYSTEM WIDE FLOW) 49 cable downstream dsg rule 1 classifier 1 50 cable downstream dsg rule 2 priority 1 clients 1 tunnel 2 (RULE FOR BRIDGE-1 FLOW) 51 cable downstream dsg rule 2 ucid 1 52 cable downstream dsg rule 2 classifier 2 53 cable downstream dsg rule 3 priority 1 clients 1 tunnel 3 (RULE FOR HUB-1 FLOW) 54 cable downstream dsg rule 3 ucid 1 55 cable downstream dsg rule 3 classifier 3 56 cable downstream dsg rule 4 priority 1 clients 1 tunnel 4 (RULE FOR BRIDGE-2 FLOW) Rev B 31

40 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode 57 cable downstream dsg rule 4 priority 1 clients 1 tunnel 4 (RULE FOR BRIDGE-2 FLOW) 58 cable downstream dsg rule 4 ucid 4 59 cable downstream dsg rule 4 classifier 4 60 cable downstream dsg rule 5 priority 1 clients 1 tunnel 5 (RULE FOR HUB-2 FLOW) 61 cable downstream dsg rule 5 ucid 4 62 cable downstream dsg rule 5 classifier 5 63 ip mroute-cache 64 cable insertion-interval cable downstream annex B 66 cable downstream modulation 64qam 67 cable downstream interleave-depth cable downstream frequency cable downstream channel-id 0 70 cable upstream 0 frequency cable upstream 0 power-level 2 72 cable upstream 0 channel-width cable upstream 0 minislot-size cable upstream 0 modulation-profile 6 75 no cable upstream 0 shutdown 76! 77 interface Cable4/0 78 ip address secondary 79 ip address ip helper-address ip pim sparse-dense-mode 82 cable dhcp-giaddr policy 83 ip dhcp relay information option 84 ip igmp static-group ip igmp static-group ip igmp static-group cable downstream dsg dcd-enable 88 cable downstream dsg rule 1 priority 1 clients 1 tunnel 1 (RULE FOR SYSTEM WIDE FLOW) 89 cable downstream dsg rule 1 classifier Rev B

41 CMTS Configuration Overview 90 cable downstream dsg rule 1 priority 1 clients 1 tunnel 6 91 cable downstream dsg rule 1 classifier 6 92 cable downstream dsg rule 2 priority 1 clients 1 tunnel 7 93 cable downstream dsg rule 2 classifier 7 94 ip mroute-cache 95 cable insertion-interval cable insertion-interval cable downstream annex B 98 cable downstream modulation 64qam Rev B 33

42 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode ADSG DHCT Initialization Introduction The DHCT does not have prior knowledge of the DSG tunnel address as it searches for the appropriate DOCSIS downstream channel. For this reason, the DCD message is used to retrieve parameters that can identify the location of the DSG tunnels. DHCTs can also receive DSG data without establishing an interactive communications path with the CMTS. This allows the DBDS to support ADSG DHCTs in a one-way operating environment. Out-of-Band Flow and the DOCSIS Downstream As part of its initialization, the DHCT searches the DOCSIS spectrum until it locates a downstream channel that is carrying a DCD message. The DHCT parses the DCD message and determines which, if any, client IDs are listed in the DCD message. The DHCT requires that the Cisco client ID (for example, mac-addr 0001.a6d0.0b1e) be listed in the DCD for it to remain on the DSG channel and discover the DSG tunnel addresses for receiving out-of-band data. If the required Cisco client ID is not listed in the DCD, the DHCT will continue its out-of-band data search. Once the DHCT locates a valid DSG channel, it remains on that channel and continuously receives out-of-band data (for example, DSG data). The DHCT then attempts to register with the CMTS. If the DHCT supports PowerKEY conditional access (CA), it uses the CA ID to receive CA data (for example, ca-system-id E00). In order to ensure proper orientation of the Cisco DHCTs that support PowerKEY CA, rules contain both clients IDs (for example, mac-addr a6d0.0b1e and ca-system-id E00), which must be configured on the CMTS. If a straddle area exists (for example, UCID-based rules), the DHCT accomplishes the following tasks: Parses the DCD message Achieves a DOCSIS two-way connection Selects the correct rules to use based on its assigned UCID during DOCSIS registration Rev B

43 ADSG DHCT Initialization Loss of the DSG Data on a DSG Channel When a DHCT is operating in ADSG mode, the initialization sequence differs from the sequence used with a standard DOCSIS cable modem. In the ADSG mode, the DHCT responds differently to the following values and conditions: Timeouts Error conditions In ADSG, the DHCT uses the configurable timer values as specified in the DCD message. When the out-of-band data is no longer present on the downstream channel, the DHCT monitors the current downstream DOCSIS frequency until the combined value of Tdsg2 and Tdsg4 is reached. The DHCT then scans the entire DOCSIS spectrum until it finds a DOCSIS signal that is carrying DSG data. Loss of the DOCSIS Upstream Channel When a DHCT is operating in ADSG mode and loses its DOCSIS upstream channel, the DHCT starts the Tdsg3 timer and remains tuned to the DOCSIS downstream channel that contains out-of-band data. The DHCT continues to receive DSG data on the downstream channel regardless of two-way capabilities. When the Tdsg3 timer expires, the DHCT tries to reacquire the upstream channel and establish two-way connectivity. If the DBDS broadcast data becomes unavailable on the DOCSIS downstream channel, the DHCT resumes downstream scan after a Tdsg2 +Tdsg4 timeout Rev B 35

44 Chapter 2 Guidelines for Configuring the DBDS for Multicast and Advanced DSG Mode Server Configurations Introduction This section provides guidelines for configuring the server components for a DBDS network using DOCSIS: Mandatory DOCSIS 1.0 servers - Dynamic host configuration protocol (DHCP) server - Trivial file transfer protocol (TFTP) server Optional servers - Time of day (TOD) server - Domain naming system (DNS) server Mandatory DOCSIS 1.0 Servers This section describes the DHCP and TFTP server configurations are required to operate DOCSIS on the DBDS. To configure a DBDS network in a DSG environment, you must configure the following servers: DHCP server TFTP server TOD server, if used DNS server, if used For the purpose of this example, Cisco assumes that the service providers have already deployed the servers identified in this section for their high-speed data service. The service providers are responsible for deploying and configuring their servers Rev B

45 Server Configurations DHCP Server Unique scope must be configured on the DHCP server for the ecm and the estb. During manufacturing, DHCTs are configured with both an RF MAC address and an Ethernet MAC address. The DOCSIS cable modem uses the Ethernet MAC address and the DHCT CPE uses the RF MAC address. System administrators should be aware of these MAC addresses if they will be provisioned on the DHCP server. The DHCT server is a required server that provides IP addresses for the embedded cable modem (ecm) and the embedded set-top box (estb). The following table allows the operator to appropriately configure their DHCP servers to recognize DHCP messages that originate from the ecm and the estb. Note: You can use the same DHCP server that is used for your existing stand-alone cable modems. Opt. # Subopt Description Data Source for ecm 0 Pad option data X X 43 Vendor specific information in suboptions 1 Client requested server sub-options list (n=0) X Hardcode d:null string 2 STB or ECM Hardcode d:"ecm" 3 Colon delimited list of embedded esafe devices (e.g., ECM:ESTB) 4 Device serial number also in MIB object docsdevserialnumber (e.g.,sabhrchrn) 5 Hardware version number from <Hardware version> field also in MIB object sysdescr (e.g., A) 6 Software version number from <Software version> field also in MIB object sysdescr (e.g., ) Hardcode d:"ecm ESTB" NVM:kNv m_device SerialNum ber NVM:kNv m_hwco nfignumb er Hardcode d Data Source for estb X Hardcoded:null string Hardcoded:"ECM" Hardcoded:"ECM:ESTB" NVM:kNvm_DeviceSerialNumber NVM:kNvm_HWConfigNumber Unified image version number (component 0) Rev B 37