BSR64K-R5 3 1-CMTSGuide

BSR 64000 CMTS
Configuration and
Management Guide
Compass ID: 362291231 Version 2

Release 5.3.1
Notice
Copyright 2010
Motorola, Inc.
All rights reserved
No part of this publication my be reproduced in any form or by any means or used to make any derivative work (such
as translation, transformation or adaptation) without written permission from Motorola, Inc.
Motorola reserves the right to revise this publication and to make changes in content from time to time without
obligation on the part of Motorola to provide notification of such revision or change. Motorola provides this guide
without warranty of any kind, either implied or expressed, including, but not limited to, the implied warranties of
merchantability and fitness for a particular purpose. Motorola may make improvements or changes in the product(s)
described in this manual at any time.
Motorola and the stylized M logo are registered trademarks of Motorola, Inc. Broadband Services Router, BSR, BSR
64000, RiverDelta, and SmartFlow are trademarks of Motorola, Inc. All other trademarks and registered trademarks
are the property of their respective owners.

Release 5.3.1
Published: 9/10
Contents
Preface
Scope ........................................................................................................................................... xxi
Audience.....................................................................................................................................xxii
Documentation Set .....................................................................................................................xxii
Conventions................................................................................................................................ xxv
Notes, Cautions, Warnings ........................................................................................................xxvi
If You Need Help......................................................................................................................xxvii
1 Configuring the Cable Interface

Introduction .................................................................................................................................1-1
Setting the IP DHCP Relay Functions ........................................................................................1-2
Configuring the Cable Helper and IP Helper Addresses.............................................................1-5
Configuring Multiple ISPs ..........................................................................................................1-7
Enabling a VCI on a Cable Interface................................................................................1-7
DHCP Option 60................................................................................................1-8
Selecting a Specific ISP....................................................................................................1-9
Enabling Host Authorization for All Cable Modems................................................................1-12
Disabling Host Authorization for All Cable Modems....................................................1-12
Creating a Static Host Authorization Entry for a Specific Cable Modem ................................1-12
Deleting a Static Host Authorization Entry for a Specific Cable Modem .....................1-13
Enabling Host Authorization for an IP Range of CPEs ............................................................1-14
Removing Host Authorization for an IP Range of CPEs ...............................................1-14
Displaying Host Authorization Information .............................................................................1-15
Using DHCP Lease Query Function to Secure the Cable Network ..........................................1-16
Compass ID: 362291231 Version 2 iii

BSR 64000 CMTS Configuration and Management Guide Release 5.3.1
Setting ARP Parameters ............................................................................................................1-18

Defining MAC Domains on the 2:8 Primary CMTS Resource Module ...................................1-19
Default MAC Domain Definition...................................................................................1-20
Redefining a MAC Domain............................................................................................1-20
Configuring AntiVirus/AntiWorm Protection ...........................................................................1-23
Configuring the Cable Channel Utilization Interval .................................................................1-24
Bundling Cable Interfaces into a Single IP Subnet ...................................................................1-24
Creating a Cable Bundle on a Cable Interface ...............................................................1-25
Adding a Static ARP Entry to a Cable Bundle Interface .................................1-28
Creating a Cable Bundle on a Loopback Interface.........................................................1-28
Subneting DHCP Clients on the Cable Interface ......................................................................1-32
Forcing the Primary Cable Address for DHCP Requests...............................................1-33
Clearing Cable Interface Counters ............................................................................................1-33
Configuring Cable Intercepts ....................................................................................................1-34
Cable Intercept Security .................................................................................................1-34
Configuring the Cable Intercept Feature Through TACACS Authorization..................1-35
Group Configuration ........................................................................................1-35
TACACS Settings ............................................................................................1-35
Shell Command Authorization Settings...........................................................1-36
Logging in as securityuser..............................................................................................1-36
Changing the securityuser Password ..............................................................................1-37
Enabling a Cable Intercept .............................................................................................1-38
Enabling a Bridging Cable Intercept ..............................................................................1-40
Disabling a Cable Intercept ............................................................................................1-41
Disabling a Bridging Cable Intercept .............................................................................1-42
Displaying Cable Intercept Information .........................................................................1-42
Configuring Cable Security Authorized....................................................................................1-46
Enabling Cable Security Authorized ..............................................................................1-46
Configuring Cable Security Failure................................................................................1-46
Configuring User-defined Channel-IDs ....................................................................................1-47
Default Channel IDs .......................................................................................................1-47
Configuring User-defined Channel-IDs .........................................................................1-48
iv Compass ID: 362291231 Version 2

Release 5.3.1 Contents
2 Configuring a Downstream Channel

Introduction .................................................................................................................................2-1
Initial Downstream Configuration Tasks ....................................................................................2-1
Configuring the Downstream Frequency and Modulation Rate.......................................2-2
Enforcing the Downstream Rate Limit.............................................................................2-3
Enabling the Downstream Port.........................................................................................2-4
Entering a Description of the Downstream Port...............................................................2-4
Managing the Downstream Channel ...........................................................................................2-5
Configuring the Downstream Interleave Depth ...............................................................2-5
Adjusting the Downstream Power Level..........................................................................2-6
Resetting a Downstream Port ...........................................................................................2-7
Reserving Downstream Bandwidth..................................................................................2-7
Unreserving Downstream Bandwidth ..............................................................................2-8
Cable Modem Downstream Frequency Override During Ranging..................................2-8
Testing RF Carrier Modulation ........................................................................................2-9
Specifying Downstream Queue Thresholds .....................................................................2-9
Limiting Downstream Multicast Traffic.........................................................................2-10
Configuring Multicast Downstream Replication Control (MDRC)...............................2-11
Enabling MDRC on a MAC Domain...............................................................2-11
Configuring a Multicast Capable Downstream Channel .................................2-12
Displaying Cable Interface Parameters ..........................................................................2-13
Displaying Downstream Parameters ..............................................................................2-14
Viewing Downstream Port Information ...........................................................2-14
3 DOCSIS 3.0 Features

Partial Services............................................................................................................................3-1
Dynamic Bonding Change ..........................................................................................................3-2
Expanded Downstream Bonding Groups....................................................................................3-3
Upstream Fiber Node Configuration...........................................................................................3-3
MD-CM-SG Ambiguity Resolution............................................................................................3-4
Cable Modem Control (CM-CTRL) ...........................................................................................3-5
Cable Modem Status (CM-STATUS)..........................................................................................3-6
Channel Specific Events ....................................................................................3-6
Non-Channel Specific Events ............................................................................3-6
Compass ID: 362291231 Version 2 v

Service Flow Attribute Based Downstream Assignment............................................................3-7
4 Configuring Downstream Channel Bonding

Introduction .................................................................................................................................4-1
Configuring a Bonding Domain ..................................................................................................4-2
Configuring a Bonding Group.....................................................................................................4-2
Clearing Channel Bonding Statistics...........................................................................................4-4
Disabling Downstream Channel Bonding...................................................................................4-4
Configuring the DOCSIS 3.0 MAC Domain Descriptor Message Interval................................4-5
5 Configuring an Upstream Channel

Introduction .................................................................................................................................5-1
About Upstream Channel Commands ..............................................................................5-2
Initial Upstream Configuration Tasks .........................................................................................5-3
Setting the Upstream Frequency ......................................................................................5-4
Setting the Upstream Power Level ...................................................................................5-4
Setting the Upstream Power Level in Relative Mode........................................5-5
Setting the Upstream Power Level in Absolute Mode.......................................5-6
Enforcing the Upstream Cable Modem Rate Limit..........................................................5-7
Enabling an Upstream Port...............................................................................................5-8
Entering a Description of the Upstream Port ...................................................................5-9
Modulation Profiles.....................................................................................................................5-9
The Modulation Profile Numbering Scheme .................................................................5-11
Displaying Configured Modulation Profiles ..................................................................5-11
Determining the Modulation Profile Applied to an Upstream Port ...............................5-12
Modulation Profile Configuration Mode........................................................................5-14
Entering Modulation Profile Configuration Mode...........................................5-14
Configuring a Modulation Profile ..................................................................................5-15
Configuring a Modulation Profile with the iuc Command ..............................5-15
Configuring a Modulation Profile Through an IUC Submode ........................5-19
Applying a Modulation Profile.......................................................................................5-21
Copying a Modulation Profile ........................................................................................5-22
Restoring a Default Modulation Profile Configuration..................................................5-23
Deleting a Modulation Profile or IUC............................................................................5-24
vi Compass ID: 362291231 Version 2

Managing the Upstream Channel..............................................................................................5-24

Configuring Upstream Cable Modem Registration Parameters.....................................5-25
Moving a Cable Modem or MTA to a Different Upstream Channel..............................5-29
Adjusting for Physical Delay between the Cable Interface and Cable Modems............5-30
Enabling Pre-equalization ..............................................................................................5-32
Forcing the Fragmentation of Large Upstream Packets .................................................5-33
Disabling an Upstream Port............................................................................................5-33
Configuring the Upstream Channel Descriptor ..............................................................5-34
Limiting the Number of Voice Calls on an Upstream Channel......................................5-35
Enabling/Disabling CMTS Concatenation Capabilities.................................................5-36
Enabling/Disabling Concatenation for DOCSIS 1.0 Cable Modems.............................5-36
Displaying Upstream Parameters ..............................................................................................5-37
Viewing Upstream Port Information ..............................................................................5-37
6 Configuring a DOCSIS 2.0 Upstream Logical Channel

Introduction .................................................................................................................................6-1
About DOCSIS 2.0......................................................................................................................6-1
Logical Channels.........................................................................................................................6-2
Channel Types .............................................................................................................................6-2
DOCSIS 2.0 Only Channel Types ....................................................................................6-3
Other Channel Types ........................................................................................................6-3
Logical Channel Operation...............................................................................................6-3
Obtaining Detailed DOCSIS 2.0 Information ..................................................................6-4
DOCSIS 2.0 and the BSR 64000 ................................................................................................6-4
BSR 64000 Hardware Support for DOCSIS 2.0 ..............................................................6-5
BSR 64000 Software Support for DOCSIS 2.0................................................................6-6
DOCSIS 2.0 Logical Channel Configuration Task Summary.....................................................6-7
About Upstream Channel Commands ..............................................................................6-7
Determining the 2:8 CMTS Module Type ..................................................................................6-9
Determining the DOCSIS Version of a Slot..............................................................................6-10
Configuring the Channel Type ..................................................................................................6-11
Configuring Spectrum Power Density Maintenance for a Logical Channel.............................6-14
Additional S-CDMA Logical Channel Configurations.............................................................6-14
Configuring S-CDMA Active Codes .............................................................................6-15
Compass ID: 362291231 Version 2 vii

Configuring S-CDMA Codes Per Minislot ....................................................................6-16

Configuring the S-CDMA Hopping Seed ......................................................................6-16
Configuring the S-CDMA Spreading Interval ...............................................................6-16
Displaying the Upstream Logical Channel Configuration ........................................................6-17
7 Using RF Sentry on the 2:8 CMTS Resource Module

Introduction .................................................................................................................................7-1
Power Level Measurement..........................................................................................................7-2
Configuring FFT...............................................................................................................7-2
Configuring the FFT Processor ........................................................................................7-3
Displaying the FFT Processor Configuration...................................................................7-3
Starting FFT Power Level Measurement .........................................................................7-3
Storing FFT Power Level Measurement Data ...................................................7-4
Displaying FFT Power Level Measurement Data ............................................................7-4
Retrieving FFT Data from an Operational CMTS Module................................7-5
Retrieving FFT Data from a File System...........................................................7-5
Signal to Noise Ratio Measurement............................................................................................7-6
Configuring SNR Measurement .......................................................................................7-6
Configuring an Automatically Repeated SNR Test ...........................................7-8
Displaying the SNR Configuration ..................................................................................7-9
Starting SNR Measurement ..............................................................................................7-9
Storing SNR Measurement Data ....................................................................................7-10
Displaying SNR Measurement Data ..............................................................................7-10
Retrieving SNR Data from an Operational CMTS Module.............................7-11
Retrieving SNR Data from a File System ........................................................7-11
Configuring an SNR Offset ............................................................................................7-12
7 Managing Cable Modems

Introduction .................................................................................................................................7-1
Configuring Network Parameters for Cable Modems.................................................................7-2
Enabling the Cable Modem Aging Timer ........................................................................7-2
Removing Cable Modems from the Offline List..............................................................7-2
Setting the Insertion Interval for Cable Modems .............................................................7-3
Setting the Synchronization Interval ................................................................................7-4
viii Compass ID: 362291231 Version 2

Setting Cable Modem Authentication Parameters ...........................................................7-5

Restoring Previously Defined Authentication Parameters.................................7-7
Denying Access to a Cable Modem .................................................................................7-7
Setting the Maximum Number of Hosts...........................................................................7-7
Configuring Baseline Privacy .....................................................................................................7-9
Setting TEK Privacy.......................................................................................................7-10
Setting Authorization Key Values ..................................................................................7-12
Managing Multicast Traffic............................................................................................7-13
Configuring Cable Privacy Mandatory ..........................................................................7-14
Using Flap Lists ........................................................................................................................7-15
Setting Flap List Parameters...........................................................................................7-15
Using Flap Lists to Troubleshoot Cable Modem Problems ...........................................7-18
Viewing Flap List Statistics to Identify Network Health .................................7-18
Interpreting Flap List Statistics ........................................................................7-19
Tips for Administering Flap Lists ..................................................................................7-23
Pinging a Cable Modem at the MAC Layer..............................................................................7-24
Resetting the Cable Modem ......................................................................................................7-25
Clearing Cable Modem Counters..............................................................................................7-26
Viewing Cable Modem Information .........................................................................................7-26
Multiple IP Addresses Per MAC Address .......................................................7-31
Viewing the Timing Adjustments for Cable Modems .....................................7-32
Configuring Remote Query .......................................................................................................7-34
Enabling Remote Query .................................................................................................7-35
Configuring the SNMP Response Timeout ....................................................................7-36
Enabling SNMP Remote Query Traps ...........................................................................7-36
Displaying Remote Query Information ..........................................................................7-37
9 Configuring Service Classes

Introduction .................................................................................................................................9-1
Service Classes .................................................................................................................9-1
Maximum Assigned Bandwidth .......................................................................................9-2
Overbooking .....................................................................................................................9-2
Scheduling Priority...........................................................................................................9-2
Admission Control............................................................................................................9-3
Compass ID: 362291231 Version 2 ix

Downstream Flow Classifier Support ..............................................................................9-3

Service Class Name Expansion ........................................................................................9-3
Service Flow and Classifier Allocation............................................................................9-4
Default Service Classes ...............................................................................................................9-5
Default Parameter Settings ...............................................................................................9-5
Sharing Bandwidth Between Service Classes .............................................................................9-7
DQoS Emergency Call Service Classes ......................................................................................9-8
Configuring the DQoS Emergency Call Service Classes.................................................9-8
Displaying DQoS Emergency Call Information...............................................................9-9
High Priority Pre-emption for 911 Calls ...................................................................................9-10
Defining DQoS Voice Calls for Premption ....................................................................9-10
Enabling DQoS Emergency Pre-emption.......................................................................9-11
Creating Service Classes ...........................................................................................................9-12
Calculating Maximum Assigned Bandwidth Percentages .......................................................9-15
Maximum Assigned Bandwidth Override......................................................................9-16
Modifying Service Class Parameters ........................................................................................9-17
Viewing Service Class Information...........................................................................................9-25
Displaying Service Class Statistics ................................................................................9-25
Displaying Service Flow Parameters..............................................................................9-25
Displaying Service Class Information............................................................................9-26
Displaying Service Flow Statistics .................................................................................9-27
Displaying Service Class Statistics ................................................................................9-28
Voice Call Statistics...................................................................................................................9-29
Configuring a Voice Call Statistics Sample....................................................................9-29
Viewing Active Voice Call Statistics..............................................................................9-29
Clearing Active Voice Call Statistics..............................................................................9-31
Disabling Active Voice Call Statistics............................................................................9-31
10 Setting QoS Parameters

Introduction ...............................................................................................................................10-1
Creating or Modifying a QoS Profile........................................................................................10-2
Resetting the Default Values ..........................................................................................10-4
Deleting a QoS Profile ..............................................................................................................10-4
Viewing a QoS Profile...............................................................................................................10-5
x Compass ID: 362291231 Version 2

Initiating a DSA ........................................................................................................................10-6

Initiating a DSC.........................................................................................................................10-7
Initiating a DSD ........................................................................................................................10-9
Configuring an Active Timeout for Dynamic Service Flows .................................................10-10
Viewing QoS Information .......................................................................................................10-11
Displaying the Packet Classifier...................................................................................10-11
Displaying SFID and QoS Information........................................................................10-12
Displaying Service Flow Statistics ...............................................................................10-12
Displaying Upstream Service Flow Statistics ..............................................................10-13
Displaying Payload Header Suppression Entries .........................................................10-13
Displaying QoS Profiles ...............................................................................................10-14
Notes About Viewing Class of Service (Qos) Profiles ..................................10-14
Configuring the BSR 64000 for DOCSIS 1.0+ Interoperability.............................................10-16
Verifying that DOCSIS 1.0+ Devices Successfully Register .......................................10-18
Troubleshooting DOCSIS 1.0+ Interoperability ..........................................................10-19
11 Configuring Spectrum Management

Introduction ...............................................................................................................................11-1
Configuring a Spectrum Group .................................................................................................11-2
Creating a Spectrum Group ............................................................................................11-3
Scheduling the Availability of a Spectrum Group Band ................................................11-5
Deleting an Existing Availability Time for a Band..........................................11-6
Scheduling the Removal of a Spectrum Group Band.....................................................11-7
Deleting an Existing Removal Time for a Band ..............................................11-8
Configuring Spectrum Data Collection ..........................................................................11-9
Configuring Spectrum Hopping Rules .........................................................................11-10
Configuring the Spectrum Hopping Error Threshold...................................................11-14
Configuring the Spectrum Hopping Flap Threshold ....................................................11-14
Enabling and Disabling Spectrum Roll-back ...............................................................11-16
Configuring the Guard Band ........................................................................................11-16
Reviewing the New Spectrum Group Configuration ...................................................11-16
Viewing Your Spectrum Group Configuration.............................................................11-17
Applying a Spectrum Group to an Upstream Port ..................................................................11-18
Evaluating Spectrum Management Performance....................................................................11-20
Compass ID: 362291231 Version 2 xi

Displaying Spectrum Data............................................................................................11-20

Viewing Spectrum Management Configuration Changes ............................................11-21
Determining the Upstream Signal to Noise Ratio ........................................................11-22
Determining the MIB Index ID Number of an Upstream Port.....................................11-22
Viewing Spectrum Management Activity ....................................................................11-23
Viewing Spectrum Management Hopping Actions ......................................................11-24
Viewing the Spectrum Management Roll-back Function ............................................11-27
12 Configuring Advanced Spectrum Management

Introduction ...............................................................................................................................12-1
Terminology ..............................................................................................................................12-2
Frequency Agility...........................................................................................................12-3
Frequency Rollback........................................................................................................12-4
Modulation Profile Agility .............................................................................................12-4
Modulation Profile Rollback ..........................................................................................12-5
Prerequisites ..............................................................................................................................12-5
Advanced Spectrum Management Operational Rules ..............................................................12-6
Legacy Spectrum Management CLI Commands ......................................................................12-6
Advanced Spectrum Management CLI Commands..................................................................12-7
Configuring Frequency Agility .................................................................................................12-9
Specifying Hop Action Band Start and End Frequencies ..............................................12-9
Specifying a Hop Action Center Frequency.................................................................12-11
Specifying the Active Channel Hop Sampling Period .................................................12-12
Specifying the Spare Channel Hop Sampling Period...................................................12-12
Specifying SNR Hysteresis ..........................................................................................12-13
Applying a Spectrum Group to an Upstream Receiver ................................................12-14
Configuring Frequency Rollback ............................................................................................12-15
Enabling Frequency Rollback .................................................................................................12-16
Configuring Modulation Profile Agility .................................................................................12-16
Specifying a Modulation Profile ..................................................................................12-16
Configuring Modulation Type SNR Thresholds ..........................................................12-17
Specifying SNR Hysteresis ..........................................................................................12-19
Applying a Spectrum Group to an Upstream Receiver ................................................12-20
Enabling Modulation Profile Rollback ...................................................................................12-21
xii Compass ID: 362291231 Version 2

Excluding Reference Cable Modems......................................................................................12-22

Displaying the Reference Modem List....................................................................................12-22
13 Configuring Load Balancing

Introduction ...............................................................................................................................13-1
Configuring Static Upstream Load Balancing ..........................................................................13-2
Enabling Static Upstream Load Balancing.....................................................................13-2
Load Balancing Across All Upstream Channels ............................................................13-4
Moving a Cable Modem to a Specified Upstream Channel ...........................................13-5
Displaying Load Balancing Statistics for a Spectrum Group.........................................13-6
Displaying UCC Statistics ..............................................................................................13-7
Configuring Static Count-Based Load Balancing .....................................................................13-7
Configuring Dynamic Load Balancing .....................................................................................13-8
Load Balancing Groups..................................................................................................13-8
Configuring a Load Balancing Rule...............................................................................13-9
Configuring a Load Balancing Policy ..........................................................................13-12
Configuring the Load Balancing Group.........................................................13-12
Configuring a Restricted Load Balancing Group.........................................................13-13
Restricting an Entire Load Balancing Group .................................................13-13
Restricting Selected Cable Modems in a Load Balancing Group..................13-15
Assigning Downstream and Upstream Channels to a Load Balancing Group.............13-16
Enabling/Disabling Dynamic Load Balancing.............................................................13-17
Enabling/Disabling Dynamic Load Balancing on all CMTS Modules..........13-17
Enabling/Disabling Dynamic Load Balancing for a Load Balancing Group 13-18
Displaying Dynamic Load Balancing Information ......................................................13-18
Manually Moving a Cable Modem .........................................................................................13-20
Manually Moving a DOCSIS 1.0 or 1.1 Cable Modem with UCC..............................13-20
Manually Moving a DOCSIS 1.1 or 2.0 Cable Modem with DCC..............................13-21
Displaying UCC/DCC Statistics .............................................................................................13-22
Clearing UCC or DCC Statistics ..................................................................................13-22
Redistributing CMTS Traffic Among HSIMs.........................................................................13-23
Displaying CMTS to HSIM Bindings ..........................................................................13-24
Compass ID: 362291231 Version 2 xiii

14 Configuring PacketCable
Overview ...................................................................................................................................14-1
PacketCable and PacketCable Multimedia Components ...............................................14-1
Configuration Task Summary ...................................................................................................14-3
Common Network Configuration Tasks.........................................................................14-4
PacketCable and PacketCable Multimedia Configuration Tasks ...................................14-4
Related Tasks..................................................................................................................14-5
Entering PacketCable Configuration Mode ..............................................................................14-5
Configuring Common Parameters.............................................................................................14-6
Specifying the Protocol IP Address................................................................................14-6
Configuring COPS Parameters.......................................................................................14-6
Restricting COPS Connections ........................................................................14-7
Specifying the Policy Enforcement Point ........................................................14-7
Configuring the COPS Client Timer................................................................14-7
Configuring Access Control Lists for COPS Connections ..............................14-8
Displaying COPS Connections ........................................................................14-8
Verifying the COPS Configuration ..................................................................14-9
Configuring Event Messages..........................................................................................14-9
Enabling the Event Message System ...............................................................14-9
Configuring Event Message Parameters ........................................................14-10
Disabling Event Messages .............................................................................14-14
Displaying Event Message Statistics .............................................................14-14
Configuring IP Security................................................................................................14-15
Configuring a Security Policy Using IPSec and IKE ....................................14-15
Configuring IPSec and IKE Parameters.........................................................14-19
Enabling IPSec and IKE ................................................................................14-21
Deleting Security Policy Database Policy Entries .........................................14-22
Displaying the IPSec Configuration ..............................................................14-22
Configuring Electronic Surveillance ............................................................................14-23
Displaying Electronic Surveillance Information............................................14-24
Configuring PacketCable Specific Parameters .......................................................................14-25
Enabling DQoS.............................................................................................................14-25
Configuring DQoS Parameters.....................................................................................14-26
Configuring DQoS Gate T0 and T1 Timers...................................................14-26
xiv Compass ID: 362291231 Version 2

Displaying Gates ............................................................................................14-27

Displaying Gate Statistics ..............................................................................14-28
Configuring PacketCable Multimedia Specific Parameters....................................................14-29
Enabling PacketCable Multimedia ...............................................................................14-29
Configuring the Multimedia Gate Timer T1 ................................................................14-29
PacketCable DSCP..................................................................................................................14-30
Configuring Related PacketCableTasks ..................................................................................14-30
Clearing All COPS Connections ..................................................................................14-31
Enabling the COPS Status SNMP Trap........................................................................14-31
Enabling the Emergency Call SNMP Trap...................................................................14-31
Enabling the Resource Request SNMP Trap................................................................14-32
Clearing Gates ..............................................................................................................14-32
Clearing PacketCable Statistics ....................................................................................14-33
Clearing PacketCable Configuration ............................................................................14-34
15 Configuring DSG
Introduction ...............................................................................................................................15-1
Prerequisites ..............................................................................................................................15-3
DSG Configuration Tasks .........................................................................................................15-4
Entering DSG Configuration Mode ..........................................................................................15-4
Initial DSG Configurations .......................................................................................................15-5
Configuring a Channel List ............................................................................................15-5
Configuring a Classifier .................................................................................................15-6
Configuring a Timer .......................................................................................................15-7
Configuring a Vendor Parameter ....................................................................................15-8
Configuring a DSG Client.........................................................................................................15-8
Configuring a DSG Tunnel .....................................................................................................15-10
Specifying Tunnel Parameters......................................................................................15-10
Configuring a Tunnel Group ........................................................................................15-11
Configuring a DSG Downstream Channel..............................................................................15-11
DCD Messages .............................................................................................................15-12
Associating Tunnel Groups to a Downstream Channel................................................15-12
Additional Configuration..............................................................................................15-14
Displaying DSG Information ..................................................................................................15-15
Compass ID: 362291231 Version 2 xv

16 Configuring VLAN Tagging

Introduction ...............................................................................................................................16-1
VLAN Tagging Packet Formats ................................................................................................16-4
Enabling VLAN Tagging ..........................................................................................................16-5
Enabling VLAN Tagging on Multiple Ports ..................................................................16-6
Configuring VLAN Tagged Bridging .......................................................................................16-6
Specifying a Bridging Cable Modem through a Bridge Mode TLV ..............................16-7
Specifying a Bridging Cable Modem through the CLI ..................................................16-8
Configuring VLAN Stacking on a Bridging Cable Modem...........................................16-9
Enabling VLAN Stacking through an Enhanced Bridge Mode TLV.............16-10
Enabling VLAN Stacking through the CLI ...................................................16-10
Configuring VLAN Tagged Routing.......................................................................................16-11
Configuring the External L2/L3 Switch..................................................................................16-13
Configuring Cable Privacy Mandatory ...................................................................................16-13
Bridging Packet Sizes..............................................................................................................16-14
Displaying VLAN Tagging Statistics......................................................................................16-15
Clearing VLAN Tagging Statistics..........................................................................................16-16
17 Configuring Tagged Sub-Interfaces

Introduction ...............................................................................................................................17-1
TSI Feature Description ............................................................................................................17-2
Adding and Removing a Sub-Interface.....................................................................................17-2
Associating an IEEE 802.1q VLAN ID with a Sub-Interface...................................................17-3
Configuring the Physical Interface to Include Optional 802.1p and 802.1q Tags ....................17-4
Updated Commands ..................................................................................................................17-5
TSI-Related Syntax Enhancement to CLI Commands...................................................17-5
List of CLI-Configurable Commands for TSI................................................................17-6
18 Subscriber Management
Introduction ...............................................................................................................................18-1
Creating Filters to Manage Subscribers ....................................................................................18-1
Creating a Packet Filter Group .......................................................................................18-2
Configuring the Source IP Address and Mask.................................................18-2
Configuring the Destination IP Address and Mask .........................................18-3
xvi Compass ID: 362291231 Version 2

Configuring the Upper Level Protocol.............................................................18-3

Configure the TOS Value and Mask ................................................................18-4
Configure the Filter Match Action...................................................................18-4
Enabling a Packet Filter ...................................................................................18-4
Displaying the Packet Filter Configuration .....................................................18-5
Deleting a Packet Filter....................................................................................18-5
Configuring Filters for TCP or UDP Packet Headers ....................................................18-6
Configuring the TCP/UDP Source Port ...........................................................18-6
Configuring the TCP/UDP Destination Port....................................................18-6
Configuring the TCP Flag Value and Mask .....................................................18-7
Enabling the TCP/UDP Packet Filter...............................................................18-7
Displaying the TCP/UDP Packet Filter Configuration ....................................18-8
Deleting a TCP/UDP Packet Filter ..................................................................18-8
Configuring Default Packet Filter Group for CMs and CPEs........................................18-8
Configuring Default Filter Group for a CPE ...................................................18-9
Configuring Default Filter Group for a CM.....................................................18-9
Configuring the Default Maximum CPEs........................................................18-9
Configuring the Active Default for CPEs ......................................................18-10
Configuring the Learnable Default for CPEs.................................................18-10
Displaying the Default Filter Groups and CPE Control Defaults..................18-10
19 Configuring a Distributed MAC Domain

Introduction ...............................................................................................................................19-1
Downstream Configuration Commands .........................................................................19-4
MAC Domain Layer 3 Configuration .......................................................................................19-6
Creating a Cable Bundle on a Loopback Interface.........................................................19-6
Fiber Node Configuration .........................................................................................................19-9
Entering Fiber Node Configuration Mode .....................................................................19-9
Entering a Description of the Fiber Node.....................................................................19-10
MAC Domain Configuration ..................................................................................................19-11
Initial Configuration .....................................................................................................19-11
Entering Cable Interface Configuration Mode for the CMTS 2:8 Module....19-11
Entering a Description of the Distributed MAC Domain ..............................19-11
Associating the Cable Bundle ........................................................................19-12
Compass ID: 362291231 Version 2 xvii

Binding the Downstream Channels................................................................19-12

Configuring a Bonding Group......................................................................................19-13
CMTS 2:8 Downstream Channel Configuration..........................................................19-15
Entering a Description of the Downstream Channel .....................................19-16
Enabling the Downstream Rate Limit............................................................19-16
Configuring the Downstream Modulation Rate.............................................19-17
Adjusting the Downstream Power Level .......................................................19-17
Configuring the Downstream Frequency .......................................................19-18
Associating the Fiber Nodes to the Downstream Channel ............................19-18
Enabling the Downstream Channel................................................................19-18
CMTS 2:8 Upstream Port Configuration .....................................................................19-19
Binding the Upstream Ports ...........................................................................19-19
Entering a Description of the Upstream Port .................................................19-20
Setting the Upstream Frequency ....................................................................19-21
Enabling the Upstream Port ...........................................................................19-21
TX32 Downstream Port Configuration ...................................................................................19-22
Entering TX32 Downstream Port Configuration Mode ...............................................19-22
Entering a Description of the TX32 Downstream Port ................................................19-23
Configuring the TX32 Channel Mode..........................................................................19-23
Adjusting the TX32 Downstream Port Power Level....................................................19-24
Configuring the TX32 Downstream Channel Frequency.............................................19-25
Associating the Fiber Nodes to the TX32 Downstream Port .......................................19-25
Entering a Description of the TX32 Downstream Channel..........................................19-26
Enabling a TX32 Downstream Channel.......................................................................19-26
Enabling a TX32 Downstream Port .............................................................................19-27
Verifying the TX32 Downstream Port Configuration ..................................................19-27
Additional TX32 Downstream Port Configurations.....................................................19-27
Additional TX32 Downstream Channel Configurations..............................................19-28
20 Cable Traffic Management

Theory of Operations ................................................................................................................20-2
Cable Traffic Policies .....................................................................................................20-4
Traffic Token Bucket ......................................................................................................20-5
Traffic Token Bucket Monitoring Algorithms .................................................20-6
xviii Compass ID: 362291231 Version 2

Traffic Enforcement Algorithms......................................................................20-7

Cable Sample Interval ....................................................................................................20-7
Offline Cable Modems ...................................................................................................20-8
Other Cable Traffic Management Operational Features ...........................................................20-9
Configuring a Cable Traffic Policy ...........................................................................................20-9
Applying Cable Traffic Policies to Subscriber Service Tiers.........................................20-9
Cable Traffic Policy Configuration Tasks ....................................................................20-10
Entering Cable Traffic Policy Configuration Mode.......................................20-11
Configuring Maximum Rate Matching..........................................................20-12
Configuring the Credit Maximum..................................................................20-13
Configuring the Enforce Rate ........................................................................20-13
Configuring the Peak Time ............................................................................20-14
Configuring the Penalty Period......................................................................20-15
Configuring Bidirectional Enforcement.........................................................20-16
Enabling a Cable Traffic Policy .....................................................................20-16
Configuring the Cable Sample Interval........................................................................20-17
Displaying Cable Traffic Management Information ....................................................20-18
show cable subscriber-usage ..........................................................................20-18
show cable subscriber-usage summary ..........................................................20-19
show cable traffic policy ................................................................................20-19
Clearing Cable Traffic Management Statistics ..................................................... 20-20
clear cable traffic enforcement.......................................................................20-20
clear cable traffic history................................................................................20-20
A Pre-Defined Modulation Profiles

Introduction ................................................................................................................................A-1
B Understanding and Modifying Modulation Profiles

Introduction ................................................................................................................................ B-1
TDMA, A-TDMA and MTDMA ............................................................................................... B-2
Modulation (Modulation Type) ....................................................................................... B-2
FEC (FEC ERR CRC, FEC CW Len) ............................................................................. B-3
Preamble (Preamble Len) ................................................................................................ B-4
Post-Equalization .............................................................................................. B-5
Compass ID: 362291231 Version 2 xix

Pre-Equalization................................................................................................ B-5
Mix of DOCSIS 1.0, 1.1, and 2.0 Cable Modems ............................................ B-6
Interleaving (Intlv Depth)................................................................................................ B-8
S-CDMA .................................................................................................................................... B-8
Modulation (Modulation Type) ....................................................................................... B-8
FEC (FEC ERR CRC, FEC CW Len) ........................................................................... B-10
Preamble (Preamble Len) .............................................................................................. B-10
Interleaving (Intlv Stp Sz) ............................................................................................. B-10
Index
xx Compass ID: 362291231 Version 2

Preface
Scope
This document describes how to configure and manage the cable network modem
termination system (CMTS) component of the Motorola Broadband Services
Router 64000 (BSR 64000). The following tasks and procedures are described in this
document:
Configuring the Cable Interface
Configuring a Downstream Channel
DOCSIS 3.0 Features
Configuring Downstream Channel Bonding
Configuring an Upstream Channel
Configuring a DOCSIS 2.0 Upstream Logical Channel
Using RF Sentry on the 2:8 CMTS Resource Module
Managing Cable Modems
Configuring Service Classes
Setting QoS Parameters
Configuring Spectrum Management
Configuring Advanced Spectrum Management
Configuring Load Balancing
Configuring PacketCable
Configuring DSG
Configuring VLAN Tagging
Configuring Tagged Sub-Interfaces
Compass ID: 362291231 Version 2 xxi

Subscriber Management
Configuring a Distributed MAC Domain
Cable Traffic Management
The following additional information is also provided:
Pre-Defined Modulation Profiles
Understanding and Modifying Modulation Profiles
Audience
This document is for use by those persons who will install and configure the
BSR 64000 product. Only trained service personnel should install, maintain, or
replace the BSR 64000.
Documentation Set
The following documents comprise the BSR 64000 documentation set:
BSR 64000 Quick Start Guide

The quick start guide provides a "roadmap" to the tasks involved in physically
installing the BSR 64000 product, physically connecting it to your network/HFC
infrastructure, and performing configuration tasks to enable the BSR 64000 to
operate in your networking environment.
BSR 64000 Installation Guide
This guide provides detailed instructions for physically installing the BSR 64000
product including: procedures for rack mounting, making physical network cable
connections, connecting DC power, and for determining the status of the BSR
64000 after applying power to it. This document also provides a description of the
BSR 64000 chassis, its hardware components and modules.
BSR 64000 Resource and I/O Module Installation Guide
This guide contains procedures for installing additional and replacement
Resource and I/O Modules in a BSR 64000 chassis and for making physical cable
connections to the modules.
BSR 64000 Command Line Interface Users Guide
ixxii Compass ID: 362291231 Version 2

Release 5.3.1 Preface
For users, this guide describes the structure of the BSR 64000 Command Line
Interface (CLI) and its various command modes. It also provides rules and
guidelines for navigating through the CLI.
Compass ID: 362291231 Version 2 ixxiii

BSR 64000 Command Reference Guide

This guide contains individual descriptions of the entire set of commands that
comprise the BSR 64000 Command Line Interface (CLI). These commands are
used to interface with, configure, manage, and maintain the BSR 64000.
BSR 64000 System Administration Guide
For system administrators, this guide provides detailed procedures for performing
initial configuration tasks including setting up: user accounts and passwords;
telnet and console access; system logging; and associated servers such as DHCP,
DNS, etc.
BSR 64000 CMTS Configuration and Management Guide
This guide provides the instructions and procedures for configuring and
managing BSR 64000 CMTS operation.
BSR 64000 Routing Configuration and Management Guide
This guide contains the instructions and procedures for configuring and managing
BSR 64000 routing operation, including RIP, OSPF, and BGP.
BSR 64000 SNMP Configuration and Management Guide
managing BSR 64000 Simple Network Management Protocol (SNMP) operation.
It also describes SNMP MIBs; provides information that describes standard and
proprietary MIB support; describes how to walk MIBs; and how to compile and
load SNMP MIBs.
BSR 64000 BGP/MPLS VPN Configuration Guide
managing the BSR 64000 to support and implement Border Gateway Protocol/
MultiProtocol Label Switching Virtual Private Networks (BGP/MPLS VPNs).
BSR 64000 Troubleshooting Guide
This guide contains instructions and procedures for troubleshooting typical
configuration problems that might be encountered using the BSR 64000. It also
offers suggestions for information to record, and have available should the need
arise to call Motorola support for assistance with BSR 64000 operational
problems.
ixxiv Compass ID: 362291231 Version 2

BSR 64000 Release Notes

These documents are specific to each release of the BSR 64000 product (software
and hardware). Release notes provide information about features not documented
or incorrectly documented in the main documentation set; known problems and
anomalies; product limitations; and problem resolutions.
Conventions
This document uses the conventions in the following table:
Convention Example Explanation

angle brackets < > ping <ip-address> Arguments in italic and enclosed by angle
ping 54.89.145.71 brackets must be replaced by the text the
argument represents. In the example,
54.89.145.71 replaces <ip-address>. When
entering the argument, do not type the angle
brackets.
bar brackets [ ] disable [level] Bar brackets enclose optional arguments. The
example indicates you can use the disable
command with or without specifying a level.
Some commands accept more than one
optional argument. When entering the
argument, do not type the bar brackets.
bold text cable relay-agent-option Boldface text must be typed exactly as it
appears.
brace brackets {} page {on | off} Brace brackets enclose required text. The
example indicates you must enter either on or
off after page. The system accepts the
command with only one of the parameters.
When entering the text, do not type the brace
brackets.
italic text boot system <filename> Italic type indicates variables for which you
supply values in command syntax descriptions.
It also indicates file names, directory names,
document titles, or emphasized text.
Compass ID: 362291231 Version 2 ixxv

Convention Example Explanation

screen display Wed May 6 17:01:03 This font indicates system output.
2000
vertical bar | page {on | off} A vertical bar separates the choices when a
parameter is required. The example indicates
you can enter either command:
page on or page off
When entering the parameter, do not type the
vertical bar or the brace brackets.
Notes, Cautions, Warnings

The following icons and associated text may appear in this document.
Note: A note contains tips, suggestions, and other helpful information, such
as references to material not contained in the document, that can help you
complete a task or understand the subject matter.
Caution: The exclamation point, within an equilateral triangle, is intended to

alert the user to the presence of important installation, servicing, and
operating instructions in the documents accompanying the equipment.
Warning: This symbol indicates that dangerous voltage levels are present
within the equipment. These voltages are not insulated and may be of
sufficient strength to cause serious bodily injury when touched. The symbol
may also appear on schematics.
ixxvi Compass ID: 362291231 Version 2

If You Need Help

If you need assistance while working with the BSR 64000 HD or BSR 64000, contact
the Motorola Technical Response Center (TRC):
Inside the U.S. 1-888-944-HELP

1-888-944-4357
Outside the U.S. +1-215-323-0044
Motorola Online http://businessonline.motorola.com
The TRC is on call 24 hours a day, 7 days a week. In addition, Motorola Online offers
a searchable solutions database, technical documentation, and low-priority issue
creation and tracking.
Compass ID: 362291231 Version 2 ixxvii

ixxviii Compass ID: 362291231 Version 2

1
Configuring the Cable
Interface
Introduction
This chapter discusses required configuration tasks that must be performed to make
the cable interface on the CMTS module operational. It also discusses additonal
optional cable interface configuration tasks.
You must perform the following mandatory intial cable interface configuration tasks:
Setting the IP DHCP Relay Functions
Configuring the Cable Helper and IP Helper Addresses
Configuring Multiple ISPs
Enabling Host Authorization for All Cable Modems
Creating a Static Host Authorization Entry for a Specific Cable Modem
Enabling Host Authorization for an IP Range of CPEs
Using DHCP Lease Query Function to Secure the Cable Network
Setting ARP Parameters
Compass ID: 362291231 Version 2 1-1

Additonally, you can also perform the following optional cable interface
configuration tasks:
Defining MAC Domains on the 2:8 Primary CMTS Resource Module
Configuring AntiVirus/AntiWorm Protection
Configuring the Cable Channel Utilization Interval
Bundling Cable Interfaces into a Single IP Subnet
Subneting DHCP Clients on the Cable Interface
Clearing Cable Interface Counters
Configuring Cable Intercepts
Configuring Cable Security Authorized
Configuring User-defined Channel-IDs
Note: Ensure that an IP address and subnetwork mask has been configured
for the cable interface before performing any of the tasks described in this
chapter.
Setting the IP DHCP Relay Functions

The IP DHCP relay function is used to forward DHCP messages between clients and
servers. The IP DHCP relay agent function gathers broadcast DHCP discovery
packets from a Multimedia Terminal Adapter (MTA) device, cable modem, or
Customer Premises Equipment (CPE), and forwards the packets to their
corresponding DHCP server. The DHCP relay function enables an MTA, cable
modem, or CPE to obtain an IP address from a DHCP server through the DHCP relay
agent, which is the router (SRM) between the cable interface and the DHCP server.
1-2 Compass ID: 362291231 Version 2

Release 5.3.1 Configuring the Cable Interface
The ip dhcp relay information command enables the BSR's DHCP relay agent to
insert the Spectrum Group Name that DHCP client belongs to and/or inserts the MAC
address of the DHCP client and the DOCSIS Device Class Identifier into outbound
requests to the DHCP server. The DOCSIS Device Class Indenter is only supported
for 1.1 cable modems. Support for DHCP Option 82, sub-option 2 (Agent Remote ID)
and sub-option 4 (DOCSIS Device Class Identifier) is enabled by the ip dhcp relay
information option command. Support for DHCP Option 82, sub-option 85
(Spectrum Group Name) is enabled by the ip dhcp relay information
spectrum-group-name. The no ip dhcp relay agent information command disables
the insertion of DHCP Option 82, sub-options.
The following steps outline the IP DHCP relay process:
1. An MTA device, cable modem, or CPE sends broadcast DHCP discover packets
to the DHCP relay agent containing a request for an IP address.
2. The DHCP relay agent inserts the MTA, cable modem, or CPE option into the
DHCP discover packets. This option contains either the spectrum group name and
associated MAC address or a MAC address.
3. The DHCP relay agent inserts any configured options into the DHCP discover
packets. This can be a spectrum group name, a MAC address and a DOCSIS
Device Class Identifier or both the spectrum group name and the MAC address
and DOCSIS Device Class Identifier.
4. The DHCP server assigns an IP address to each MTA, cable modem, or CPE that
requested an IP address by placing the IP address in the (Your IP Address) yiaddr
field in the DHCP packet header. The yiaddr is the IP address to be used by the
MTA, cable modem, or CPE.
5. The DHCP relay agent removes the MTA, cable modem, or CPE option and
forwards the DHCP server reply, containing the IP address to the MTA, cable
modem, or CPE.
Follow these steps to configure the DHCP relay option on the BSR:
1. Use the show running-config command in Privileged EXEC mode determine the
DHCP relay function is enabled for the desired cable interface:
MOT:7A#show running-config
2. If you need to change or enable the DHCP relay function for a cable interface,
enter the desired cable interface from Global Configuration mode.

3. Use the ip dhcp relay information option command in Interface Configuration

mode to enable the DHCP relay agent to insert a MAC address (Agent Remote
ID) only into a clients DHCP packet:
Note: The ip dhcp relay information option command must be entered to

enable the DHCP relay information option function. If the DHCP relay
information option function is not enabled, cable modems cannot register and
go on-line.
If you are configuring two MAC domains on the 2x8 CMTS module, the ip
dhcp relay information option command must be entered for each MAC
domain. If this command is not entered in for each domain, cable modems
cannot register in that domain.
MOT:7A(config-if)#ip dhcp relay information option

4. Optionally use the ip dhcp relay information spectrum-group-name command
in Interface Configuration mode to enable the DHCP relay agent to insert the
spectrum group name (Circuit ID) into all of the DHCP packets:
Note: If a DHCP client on a particular subnet is using an upstream frequency

that is not configured as a member of a spectrum group, the spectrum group
name is not inserted by the DHCP relay agent into the DHCP discover
packet.
MOT:7A(config-if)#ip dhcp information spectrum-group-name

Configuring the Cable Helper and IP Helper

Addresses
The cable helper IP address function disassembles a cable modem DHCP broadcast
packet, and reassembles it into a unicast packet so that the packet can traverse the
router and communicate with the DHCP server.
The cable helper address function is used in conjunction with the DHCP relay
function. If the ip dhcp relay information option command is not set, all requests
are sent to the IP address defined by the ip helper-address command. When ip dhcp
relay information option is enabled, the BSR can distinguish between requests from
cable modems, secondary hosts and secondary MTAs, and forwards the DHCP
requests to the cable helper IP address specifically defined for the requesting device.
Note: Multiple cable-helper addresses can be configured for cable modems,

hosts, and MTAs. If you want both cable modem and host DHCP requests to
be sent to the same DHCP server, configure the same cable helper IP
address for hosts and cable modems.
Follow the steps in this section to configure the cable helper and IP helper address:
1. Use the cable helper-address command in Interface Configuration mode to
configure the helper IP address for the cable interface to forward only DHCP
broadcasts:
MOT:7A(config-if)#cable helper-address <A.B.C.D> cable-modem
where:
A.B.C.D is the IP address of the destination DHCP server.
2. Optionally use the cable helper-address command in Interface Configuration
mode to configure a secondary helper IP address for the CPE to forward only
UDP broadcasts:
MOT:7A(config-if)#cable helper-address <A.B.C.D> host
where:
A.B.C.D is the IP address of the destination DHCP server.
3. Optionally use the cable helper-address command in Interface Configuration
mode to configure a secondary helper IP address for the Multimedia Terminal
Adapter (MTA) device to forward only UDP broadcasts:

MOT:7A(config-if)#cable helper-address <A.B.C.D> mta

where:
A.B.C.D is the destination DHCP server IP address.
4. The IP helper address necessary for the BSR to forward packets to the DHCP
server. Use the ip helper-address command in Interface Configuration mode to
forward default UDP broadcasts including IP configuration requests to the DHCP
server:
Note: The IP helper address must be entered for the DHCP Lease Query
function to work regardless of whether the relay agent option is used.
MOT:7A(config-if)#ip helper-address <A.B.C.D>

where:
A.B.C.D is the destination DHCP server IP address.
5. Use the show ip dhcp stats command in Interface Configuration mode to display
information about DHCP upstream and downstream port statistics:
MOT:7A(config-if)#show ip dhcp stats [<0-15>]
where:
0-15 is the module slot number.

Configuring Multiple ISPs

The DHCP-relay agent, which is the router (SRM) between the cable interface and
DHCP server, monitors DHCP CPE host requests for the presence of the Vendor Class
Identifier (VCI) also known as DHCP Relay Option 60. Vendors define a VCI to
optionally identify the DHCP client vendor type and configuration information. For
example, if a VCI identifies a DHCP client as a Multimedia Terminal Adapter (MTA)
device, the DHCP server can put all MTA devices that are on a cable interface into the
same subnet.
The host and mta VCI options are used to configure a CPE host or MTA gateway IP
address (giaddr) for the cable interface. During the DHCP process, the DHCP relay
agent requests an IP address in a particular subnet by inserting the cable interface
giaddr into the DHCP requests from cable modems, hosts, and MTAs. The primary IP
address is always inserted in cable modem DHCP requests. The ip dhcp relay
information option command must be enabled to allow the BSR to determine what
type of device originated the DHCP request. The primary IP address for the cable
interface is inserted into DHCP requests by default.
Enabling a VCI on a Cable Interface

Follow these steps to enable a VCI on the cable interface:
1. Use the ip address command in Interface Configuration mode for the cable
interface to define the Gateway IP address (giaddr) for CPE host DHCP requests
or MTA DHCP requests that creates individual subnets for host CPEs, and MTAs:
Note: The ip dhcp relay information option command must be enabled to

allow the BSR to determine what type of device originated the DHCP request.
The primary IP address for the cable interface is inserted into DHCP requests
by default.
MOT:7A(config-if)# ip address {<A.B.C.D> <A.B.C.D>} secondary [host |

mta]
where:
A.B.C.D is the IP address.
A.B.C.D is the subnetwork IP address mask.
secondary specifies that the secondary IP address is a secondary IP address
for cable modem DHCP requests.

host optionally defines this secondary IP CPE host address as the giaddr to
be inserted into CPE host DHCP requests.
mta optionally defines this secondary IP MTA address as the giaddr to be

inserted into MTA DHCP requests.
Note: The BSR supports 256 secondary IP subnets per CMTS module.The
maximum number of secondary IP subnets that can be configured on the
entire BSR chassis is 1024.
If you are running a BCM 3140-based DOCSIS 2.0 2:8 CMTS module as two
1:4 configurations, the limit is still 256 secondary IP subnets for the entire 2:8
CMTS module. The total number of secondary IP subnets between MAC
Domain 0 and MAC Domain 1 can only equal 256. Also, if you apply the
same cable bundle to each MAC domain even though the secondary IP
subnets are the same they must be counted twice.
For example, if you have 256 secondary IP subnets in a cable bundle and
you apply that cable bundle to two MAC domains, the total number of
secondary IP subnets would be 512 which exceeds the limit for the DOCSIS
2.0 CMTS module. In this example, there can be no more than 128
secondary IP subnets on the cable bundle.
DHCP Option 60
The DHCP Vendor Class Identifier Relaying feature enhancement allows the BSR to
relay DHCP traffic based on the contents of the vendor class identifier (VCI) field.
This allows DHCP traffic sourced from specific devices, such as set-top boxes, to be
relayed to specific DHCP servers based on the contents of the VCI field (option 60).
There are no requirements for devices to include the VCI field, however, the intention
of this feature enhancement is to allow the VCI field to be used as a way to identify
certain devices. Set-top boxes, for example, can be designed to include a specific VCI
string that allows the BSR 64000 to relay their DHCP traffic to specific DHCP servers
with this feature enhancement.
The following commands are used for this feature:
cable helper-address host vendor-class-identifiers
vendor-class-identifier

Selecting a Specific ISP

The multiple ISP feature requires significant coordination between the operator's
provisioning system and the BSR. The following is a high level walkthrough of the
use of this feature:
1. The operator configures the BSR and their provisioning system correctly.
2. The customer powers up the cable modem.
3. The cable modem sends a DHCP request to the cable helper-address defined for
cable-modems. The giaddr value is set to that of the primary interface on the
cable interface.
4. The DHCP server assigns an IP address to the cable modem using the giaddr
value.
5. The customer's CPE sends a DHCP discover to cable helper-address defined for
hosts. The giaddr value is set to that of the first secondary ip address defined for
the interface.
6. The DHCP server assigns an IP address for the CPE using the giaddr value.
7. The CPE traffic is now directed to a configuration server which allows the
customer to select the ISP provider.
8. The configuration server saves the information related to the customer's ISP
selection.
9. The cable modem and CPE must now be power cycled to force both devices to
initiate the DHCP process again.
10. The cable modem sends a DHCP request to the cable helper-address defined for
cable-modems. The giaddr value is set to that of the primary interface on the
cable interface. Since the provisioning server now knows the ISP that the
customer selected, it assigns the cable modem an IP address on a sub network that
is associated with the ISP provider.
11. The CPE sends a DHCP request to the cable helper-address that has been defined
for all CPEs that are connected to a cable modem with IP address assignment in
the isp-bind sub network. The giaddr is set to the giaddr of the secondary IP
address that has been defined for all CPEs that are connected to a cable modem
with an IP address in the isp-bind network.
12. The DHCP server now responds with an IP address in a subnet that is owned by
the ISP provider.

13. All subsequent CPEs that perform DHCP that are connected to the same cable
modem will be automatically assumed to have selected the same ISP.
The BSR supports an "isp-bind" option for the CLI commands ip address and cable
helper-address.
The isp-bind option for the ip address command allows the BSR to bind a
secondary IP address subnet, to another secondary IP address subnet.
The isp-bind option for the cable helper-address command allows the BSR to
bind the cable helper address with a secondary IP address subnet.
A CPE that is connected to a cable modem that has an IP address in the A.B.C.D
subnet of the isp-bind <A.B.C.D> option will have the giaddr field of its DHCP
requests set to the ip address A.B.C.D value and will have its DHCP requests
forwarded to the cable helper-address defined for isp-bind A.B.C.D.
An operator can bind a secondary IP address range that was defined for CPEs with the
giaddr of the secondary IP address range that was defined for cable modems of a
particular ISP provider using the ip address and cable helper address commands.
The operator creates an internal mapping of a cable modem subnet, giaddr value and
cable helper address. There can be up to 128 subnets configured on each CMTS
module. Since binding a secondary IP subnet to another secondary IP subnet requires
the use of two subnets and one subnet for the primary, up to 64 ISPs can be configured
for each CMTS.
After a CPE has selected an ISP, all subsequent DHCP requests will have the IP
address of the cable modem inserted by the CMTS module before forwarding the
request to the relay agent on the SRM. The SRM sets the giaddr field and the IP
address of the DHCP server using the cable modems IP address to determine what
the value should be.
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D> [ secondary [ host |

mta ] [isp-bind <A.B.C.D>]]]
where:
secondary specifies that the secondary IP address is a secondary IP address for
cable modem DHCP requests.

isp-bind A.B.C.D specifies the secondary IP subnet that this

secondary IP address is bound to.
MOT:7A(config-if)#cable helper-address <A.B.C.D> {cable-modem | host
[isp-bind <A.B.C.D>] | mta [isp-bind <A.B.C.D>]}
where:
A.B.C.D indicates the IP address of the destination DHCP server.
cable-modem specifies that only cable modem UDP broadcasts are forwarded.
host specifies that only CPE UDP broadcasts are forwarded.
mta specifies that only CPE MTA broadcasts are forwarded
isp-bind A.B.C.D specifies the secondary IP subnet to which the
secondary IP address is bound.
Note: The isp-bind option is only available after selecting the host or mta
options. It is not available for the cable modem option.
Note: The cable helper-address command allows operators to support

multiple cable modem subnets bound to a single cable helper-address. Any
DHCP requests from clients that are attached to cable modems that are part
of the Multiple ISP configuration will have their requests relayed to any
defined ip helper-addresses.

Enabling Host Authorization for All Cable Modems

The host authorization feature is used for security purposes on the cable network.
When enabled, host authorization denies access to any hacker who tries to take or
spoof an IP address from any legitimate user on the same cable network. A hacker
takes the IP address from this user to steal their data service. The hacker accomplishes
this by changing the IP address on their PC to the IP address that the DHCP server
assigned to a legitimate users CPE.
Note: The host authorization feature is turned off by default.
Follow these steps to enable the host authorization feature:

1. Enter the cable interface on which host authorization is enabled.
2. Use the host authorization on command in Interface Configuration mode to
enforce the bind of the cable modem and CPE MAC addresses to the IP address
assigned to them (statically or through DHCP):
MOT:7A(config-if)#host authorization on
Disabling Host Authorization for All Cable Modems

Use the no host authorization on command to disable host authorization on the cable
interface.
Creating a Static Host Authorization Entry for a

Specific Cable Modem
Cable operators can create static entries to deny hackers from stealing service from
users. Through static entries, cable operators can manually bind the Customer
Premises Equipment (CPE) MAC (hardware) and IP address or Customer Premises
Router (CPR) MAC (hardware) and IP address to a particular cable modem. This
command may be used in circumstances when DHCP is not used to assign the CPE IP
addresses.
Follow these steps to configure and verify a static host authorization:

1. Use the cable interface command in Global Configuration mode to enter the
desired cable interface.
2. Use the host authorization command in Interface Configuration mode to create a
static entry for a specific cable modem and CPE, as follows:
MOT:7A(config-if)#host authorization <mac> cpe <mac> <prefix>
where:
mac is the MAC address of the cable modem.
mac is the MAC address of the CPE.
prefix is the IP address of the CPE.
3. Use the host authorization command in Interface Configuration mode to create a
static entry for a specific cable modem and CPR, as follows:
MOT:7A(config-if)#host authorization <mac> cpr <mac> <prefix>
where:
mac is the MAC address of the CPR.
prefix is the IP address of the CPR.
4. Use the show host authorization cpe static command to display the static entries
and DHCP lease query information for CPEs only:
MOT:7A#show host authorization cpe static
Deleting a Static Host Authorization Entry for a Specific

Cable Modem
Use the no host authorization command in Interface Configuration mode to delete a
host authorization entry, as follows:
MOT:7A#no host authorization <mac> cpe <mac> <prefix>
where:
mac is the MAC address of the customer premises equipment (CPE).
prefix is the IP address of the CPE.

Enabling Host Authorization for an IP Range of

CPEs
Instead of adding individual static CPEs on a specific cable interface using the cable
host authorization cpe command, CPEs can be added automatically to the network
by specifying a start and end range of IP addresses. This function allows you to
specify a partial subnet by allowing CPEs on different cable interfaces to
automatically connect to a network.
Use the cable host authorization range command in Global Configuration mode to
define a range of CPE IP addresses that are allowed to be added to the host
authorization table (static IP table). Any CPE IP address within the specified start and
end IP address range is added to the host authorization table when a CPE joins the
network.
Note: Up to 32 CPE IP address ranges can be defined for the BSR.
MOT:7A(config)#cable host authorization range {<prefix> <prefix>}

where:
prefix is the start of the IP address range.
prefix is the end of the IP address range.
For example:
MOT:7A(config-if)#cable host authorization range 150.42.19.100
150.42.19.109
Removing Host Authorization for an IP Range of CPEs

Use the no cable host authorization range command to remove the start and end IP
range of CPE addresses so that new CPEs trying to join the network (having an IP
address within the specified range) cannot be added to the host authorization table:
MOT:7A(config)#no cable host authorization range {<prefix> <prefix>}

A CPE with an IP address that is within the start and end range defined by the host
authorization range command that is currently connected remains in the host
authorization table until it is individually removed by the no host authorization
command, or if the BSR is reset.
Displaying Host Authorization Information

Use the following show command options to view host authorization information in
all modes except UserEXEC mode:
If you want to view a summary of ARP authorization table information, issue the
show host authorization cpe leased command:
MOT:7A#show host authorization summary
If you want to view the type, host IP address and host MAC address of dynamic
entries in the ARP authorization table, issue the show host authorization cpe
leased command:
MOT:7A#show host authorization cpe leased
If you want to view the type, host IP address and host MAC address of static
entries and DHCP lease query information for CPEs only, issue the show host
authorization cpe static command:
MOT:7A#show host authorization cpe static
If you want to view all entries or the entries for a specified CMTS module in the
ARP authorization table on the BSR, issue the show host authorization
command:
MOT:7A#show host authorization [<0-15>]
where:
0-15 is the BSR module slot number.
Refer to the BSR 64000 Command Reference Guide to see typical screen output and
field descriptions for the show host authorization and show host authorization
summary commands.

Using DHCP Lease Query Function to Secure the

Cable Network
The DHCP lease query feature provides additional security on the cable network by
preventing hackers from stealing service from customers. Hackers steal service from
other subscribers by spoofing their connection information contained in ARP
broadcasts. Preventing hackers from spoofing the cable network also prevents
undesirable ARP broadcasts from disrupting service on the cable network.
The DHCP lease query feature is used in conjunction with the host authorization
feature on the BSR to query the location of a hackers cable modem and its connected
Customer Premises Equipment (CPE) when a packet either arrives from or is destined
to a subscribers cable modem and its CPE, and has no location information in the
DHCP Lease table.
If the DHCP lease query attempt fails, packets associated with the cable modem and
its CPE are discarded. The BSR sends DHCPLEASEQUERY messages to the
specified DHCP server and accepts DHCPACTIVE, DHCPKNOWN and
DHCPUNKNOWN replies from the DHCP server.
The DHCP lease query function requires that the DHCP Server is configured with the
following values for the different DHCP message types:
DHCPDISCOVER (1)
DHCPOFFER (2)
DHCPREQUEST (3)
DHCPDECLINE (4)
DHCPACK (5)
DHCPNAK (6)
DHCPRELEASE (7)
DHCPINFORM (8)
DHCPLEASEQUERY (10)
DHCPLEASEUNASSIGNED (11)
DHCPLEASEUNKNOWN (12)
DHCPLEASEACTIVE (13)
The following steps demonstrate how the BSR uses the DHCP lease query feature:
1. Cable Subscriber requests and gets an IP address from DHCP server.

2. Cable Subscriber starts to pass traffic through the cable interface.

3. The BSR inspects the cable network traffic to ensure source IP addresses are valid
by doing the following:
Verify DHCP server acknowledgement messages to learn if IP packets are
forwarded only once for an IP address.
Query the DHCP server to verify if an IP address was legally assigned by
verifying DHCP lease information table. If it is confirmed that static IP
address was assigned by a hacker for a cable modem, packets are not
forwarded beyond the cable interface.
Disallow ARP broadcasts
Query the DHCP server to verify that one IP address to MAC address
binding appears for a cable modem. If there is more than one IP address to
MAC address combination, one IP was assigned by DHCP and the other IP
address is statically (manually) set by a hacker. In this instance, only packets
sent from the legal source learned through DHCP are forwarded.
The DHCP lease query feature can also determine:
If the BSR is replaced or inadvertently rebooted.
When a cable modem re-registers and acquires a new lease.
When a cable modem or CPE maintains its lease because it has not expired.
When the cable interface learns about the DHCP lease through a
DHCPLEASEQUERY exchange.
When the cable modem or CPE can continue passing data.

Follow these steps to enable the DHCP lease query feature:

1. Use the interface cable command in Global Configuration mode to enter the
desired cable interface:
MOT:7A(config)#interface cable <X/Y>
where:
X/Y is the slot and MAC Domain number of the CMTS module.
2. Use the dhcpleasequery authorization on command in Interface Configuration
mode to enable DHCP lease query messages to be exchanged between the cable
interface and DHCP server:
Note: The IP helper address must be entered for the DHCP Lease Query
function to function properly. Refer to Configuring the Cable Helper and IP
Helper Addresses for more information on setting the IP helper address on
the cable interface.
For the DHCP Lease Query feature to function properly, host authorization
must also be enabled with the host authorization command. Host
authorization is used for security purposes on a cable network. Refer to
Enabling Host Authorization for All Cable Modems.
MOT:7A(config-if)#dhcpleasequery authorization on
3. Use the show ip traffic command to monitor DHCP lease query statistics, which
include the number of active, known, unknown, and unimplemented DHCP
packet transmissions.
Setting ARP Parameters

The Address Resolution Protocol (ARP) is used to build a correlation between the
cable network and the connected cable modems and customer premises equipment
(CPE) by translating the cable modem and CPEs MAC address to a logical IP
address. The collected information is dynamically stored in a table called the ARP
cache.
Follow these steps to set ARP parameters on a cable interface.
1. Enter the cable interface on which ARP is enabled.

2. Use the arp command in Interface configuration mode to specify the type of ARP
packet that is used on the BSR 64000:
MOT:7A(config-if)#arp [arpa | snap]
where:
arpa is entered for the standard ARP protocol.
snap is entered for the IEEE 802.3 usage of ARP.
The ARP timeout feature is used to prevent unnecessary flooding of traffic over the
cable network. ARP resolution requests are terminated after a defined interval when
attempts to resolve addressing information, for a device entry in the ARP cache table.
3. The ARP cache table expiration value is disabled by default. Use the arp timeout
command in Interface Configuration mode to set the ARP cache table expiration
value:
MOT:7A(config-if)#arp timeout <1-6000>
where:
1-6000 is the expiration value in minutes.
If you want to return to the default ARP timeout condition, use the no arp timeout
command in Interface Configuration mode:
MOT:7A(config-if)#no arp timeout
Defining MAC Domains on the 2:8 Primary CMTS

Resource Module
A 2:8 Primary CMTS Resource Module supports up to two MAC Domains. A MAC
Domain must have at least one downstream and one upstream channel associated with
it (i.e, bound to it). In effect, a MAC Domain is somewhat analogous to the concept
of an interface.
When the 2:8 CMTS Resource Module is installed into an operating chassis, it sets up
MAC Domains based on the default MAC Domain definition in the startup
configuration file. After the module boots you can modify the MAC Domain
definition through the BSR Command Line Interface (CLI).

Each MAC Domain must have at least one downstream and one upstream channel
associated (bound) to it. A user associates (binds) either one or both of the two
downstream channels and a specific group of the eight upstream channels on the
module to either of the two MAC Domains available on the module. When installed in
an operating BSR chassis, the 2:8 Primary CMTS Resource Module sets up MAC
Domains based on the default definition in the startup configuration file.
Default MAC Domain Definition

A MAC Domain definition is defined for each resource module slot in which a 2:8
Primary CMTS Module can be installed (slots 0-5, 9-15) in the BSR startup
configuration file. Slot 6 is reserved for the Standby CMTS, slot 7 is reserved for the
SRM, and slot 8 is reserved for the Standby SRM. When a 2:8 Primary CMTS
Resource Module is installed into an operating BSR chassis, the module, after
booting, has one MAC Domain (0). MAC Domain 0 comprises downstream port 0
and upstream ports 0, 1, 2, 3, 4, 5, 6, and 7.
Redefining a MAC Domain

The 2:8 Primary CMTS Resource Modules supports two MAC Domains that can be
configured through the BSR CLI. Configuration flexibility allows operators to
associate (bind) one of the modules two downstream ports with any combination of
upstream ports to define a MAC Domain. Follow this procedure to redefine the MAC
Domains on a single 2:8 Primary CMTS Module. As an example, this procedure
describes rebinding upstream and downstream ports from MAC Domain 1 to MAC
Domain 0.

1. On the installed 2:8 Primary CMTS Module, navigate to Interface Configuration

mode for MAC Domain 1, as follows:
where:
X is the chassis slot number of an installed 2:8 Primary CMTS Module
Y is the number of the MAC Domain (e.g. MAC Domain 1)
2. Use the cable downstream shutdown and cable upstream shutdown command
to disable the upstream and downstream ports on MAC Domain 1 that you want
to bind to MAC Domain 0, as follows:
MOT:7A(config-if)cable downstream <NUM> shutdown
where
NUM is the number of the downstream port.
MOT:7A(config-if)cable upstream {<NUM> | <X/Y>} shutdown
where:
NUM is the number of the upstream port (channel).
X/Y is the upstream port number and logical channel number (0-3)
Note: When using the cable upstream shutdown command, only the NUM
option displays for a BCM 3138-based 2:8 CMTS modules. Both the NUM
and X/Y arguments display for BCM 3140-based DOCSIS 2.0 2:8 CMTS. The
cable upstream shutdown command is applicable to both an upstream port
or upstream port and logical channel.
To determine which 2:8 CMTS module is installed in the BSR 64000, use the
show chassis status command. For BCM 3138-based 2:8 CMTS modules,
the command display reads 2:8 CMTS, and for the BCM 3140-based
DOCSIS 2.0 2:8 CMTS, the display reads, 2:8 CMTS (DOCSIS 2.0)
3. Use the show cable modem registered and show cable modem unregistered
commands to view the deregistration of all cable modems associated with the
channels you disabled in Step 2. Wait until all modems associated with the port
deregister before proceeding to Step 4.
4. Shutdown the cable interface associated with the MAC Domain 1, as follows:

MOT:7A(config-if)shutdown
5. Navigate to Interface Configuration mode for MAC Domain 0, as follows:
where:
6. Use the cable bind downstream command to bind a downstream port to MAC
Domain 0, as follows:
MOT:7A(config-if)cable bind downstream <NUM>
where:
NUM is the number of a single downstream port or both downstream port
numbers on the module separated by a comma (0,1).
7. Use the cable bind upstream command to bind an upstream port to MAC
MOT:7A(config-if)cable bind upstream <NUM>
where:
NUM specifies a single upstream port number, a subset of upstream port
numbers (separated by commas), or all upstream port numbers on the module
separated by commas (0,1,2,3,4,5,6,7).
8. Use the no cable downstream shutdown and no cable upstream shutdown
commands to enable the individual ports now associated (rebound) to MAC
MOT:7A(config-if)no cable downstream <NUM> shutdown
MOT:7A(config-if)no cable upstream <NUM> shutdown
where:
NUM is the number of the downstream or upstream channel
9. Use the show cable modem registered and show cable unregistered commands
to view the reregistration of all cable modems associated with the channels you
enabled in Step 8.
10. Navigate to Interface Configuration mode for MAC Domain 1, as follows:


where:
11. Enable the cable interface associated with the MAC Domain 1, as follows:
MOT:7A(config-if)no shutdown
12. Use the copy running-config startup-config command in Privileged EXEC
mode to copy (save) the running configuration to the startup configuration, as
follows:
MOT:7A#copy running-config startup-config
Note: Repeat the above procedure, as required, to redefine MAC Domains

on additional 2:8 Primary CMTS Resource Modules.
Configuring AntiVirus/AntiWorm Protection

The BSR supports a configurable antivirus/antiworm feature that enables operators to
filter (drop) worm/virus packets on both the upstream and downstream cable
interfaces.
Using the cable deny ip CLI command, operators specify the IP protocol used by the
virus or worm and its packet length (in bytes) to enable a filter for a particular threat.
For example, to handle the Nachi worm the CMTS must be able to filter 92-byte
ICMP packets both upstream and downstream.
This feature is disabled by default and must be explicitly enabled by the operator. The
ACCPKT event system keeps track of the number of dropped packets in the upstream
and downstream directions using the ACCPKT.33 and ACCPKT.68 events.
Use the cable deny ip command to create and implement a filter that will filter (drop)
the virus or worm from the cable network.
Before creating a filter you must know the following:
Number of the IP protocol used by the threat (virus or worm)
The size (in bytes) of the virus or worm

Use the cable deny ip command from Cable Interface Configuration Mode to create a
filter for a specific threat, as follows:
MOT:7A(config-if)# cable deny ip <0-255> <20-65535>
where:
0-255 is a numeric value indicating which IP protocol number to drop.
20-65535 is the length in bytes indicating the size of the IP packet to drop.
Use the no form of this command, no cable deny ip, to delete a filter you created, as
follows:
MOT:7A(config-if)# no cable deny ip <0-255> <20-65535>
Configuring the Cable Channel Utilization Interval

The cable utilization-interval command is used to estimate the amount of bandwidth
used on each BSR CMTS module for their downstream and upstream channels for a
specified interval. Use the cable utilization-interval command in Global
Configuration mode to specify the upstream and downstream channel utilization
calculation interval. The no cable utilization-interval returns the channel utilization
calculation interval to the default value of "0" (disabled).
MOT:7A(config)#cable utilization-interval <0-86400>
where:
0-86400 is the channel utilization interval in seconds, 0 is disabled.
Bundling Cable Interfaces into a Single IP Subnet

Cable bundling allows you to group multiple cable interfaces into a single IP subnet.
Cable bundling simplifies network management and conserves IP addresses.
Each BSR 64000 DOCSIS module provides one cable interface. A cable bundle
comprises two or more cable interfaces: one cable interface is configured as the
master, while the remaining interfaces are configured as slaves to the master. If one
DOCSIS module is configured as the master, the other DOCSIS modules can become
slaves. The master cable interface is assigned IP addresses and the slaves share the
same IP addresses with the master. Therefore, the bundling feature eliminates the
need for an IP subnet for each cable interface.

The cable bundle feature provides the following benefits:

You can add new DOCSIS modules without having to assign an IP address to
each new DOCSIS module or to cable modems on each interface.
You can move a cable modem that has a static IP address to any cable interface on
the same bundle without assigning the cable modem a new IP address.
You can bundle all cable interfaces into a single bundle to share a single IP
subnet.
The cable bundling feature requires that the following conditions are observed:
Cable interface bundling is only supported on cable interfaces.
One cable interface must be configured as the master interface for the bundle. The
other cable interfaces are configured as slave interfaces.
An IP address is only assigned to master cable interface.
DHCP relay is only enabled on the master cable interface.
ARP authorization is enabled on both the master cable interface and the slave
cable interfaces.
Cable upstream and downstream parameters remain unique for each individual
cable interface.
Cable interface bundles are configured using CLI commands only.
Creating a Cable Bundle on a Cable Interface

Follow these steps to configure a cable bundle on the BSR 64000:
cable interface that you want to designate as the master cable interface:
where:
For example:
MOT:7A(config)#interface cable 4/0
2. Use the show running-config command in Privileged EXEC mode to make sure
that DHCP relay is enabled on the master cable interface. Check the command
output to see if the IP helper address or cable helper address is assigned to the
master cable interface.

3. If the IP helper address or cable helper address is not assigned to the master cable
interface, use the ip helper-address or cable helper-address command in
Interface configuration mode to enable DHCP relay. The ip helper-address or
cable helper address specifies the DHCP server.
4. Use the show interfaces cable command in Global Configuration mode to
determine if an ip address is assigned to the master cable interface:
MOT:7A(config)#show interfaces cable <X/Y>
where:
5. If the master cable interface does not have IP address, use the ip address
command in Interface Configuration mode to specify the master cable interface
IP address.
6. Use the cable bundle master command in Interface Configuration mode to
assign the cable interface as the master cable interface and assign the bundle a
number:
MOT:7A(config-if)#cable bundle <0-255> [master]
where:
0-255 is the number of the cable bundle identifier.
For example:
MOT:7A(config-if)#cable bundle 1 master
7. Use the end command in Interface Configuration mode to exit the master cable
interface.
8. Use the show interfaces cable command in Global Configuration mode to make
sure that the slave cable interface does not have an IP address assigned to it:
where:
9. Use the interface cable command in Global Configuration mode to assign
another cable interface as the slave interface:

where:
For example:
10. Use the cable bundle command in Interface Configuration mode to assign this
cable interface as the slave cable interface and assign the bundle the same number
as the master cable interface:
MOT:7A(config-if)#cable bundle <0-255>
where:
For example:
MOT:7A(config-if)#cable bundle 1
11. Use the show running-config command in Privileged EXEC mode to verify your
cable bundle configuration for each cable interface.
The examples in this section show that the DOCSIS module master cable interface is
in slot 4 and the DOCSIS module slave cable interface is in slot 5. Both modules are
in the same IP subnet that is described as cable bundle 1.
Here is the entire example configuration discussed in this section:
MOT:7A(config-if)#end
MOT:7A(config-if)#end
Note: In the case of virtual cable bundling, the BSR will support the
association of CMs in a single IP subnet with sub-interfaces across the MAC
domains (as slaves) of the same CMTS 2:8 module. This will also be
supported across the MAC domains of two different CMTS 2:8 modules.

Adding a Static ARP Entry to a Cable Bundle Interface

Use the arp cablebundle cable command in Global Configuration mode to optionally
add a static arp entry to the cable bundle interface:
MOT:7A(config)#arp <A.B.C.D> <H.H.H> [arpa | snap] cablebundle cable <X/
Y>
where:
A.B.C.D is the IP address of the ARP entry.
H.H.H is the 48-bit MAC address of the ARP entry.
The following example shows how to add a static arp entry that has an IP address of
10.1.1.10 and MAC address of 0000.0000.0010 MAC in arpa format on cable bundle
interface cable 3/0:
MOT:7A(config)#arp 10.1.1.10 0000.0000.0010 arpa cablebundle cable 3/0
Creating a Cable Bundle on a Loopback Interface

Configuring a loopback interface as a cable bundle master provides a mechanism for
configuring the IP parameters of a cable bundle in a virtual interface which is
independent of physical cable interfaces. The advantage of configuring a virtual
interface as the cable bundle master is that IP configuration information will be
always available regardless of the state of the CMTS hardware. The slave cable
interfaces of a bundle whose master is a virtual interface will not lose their IP
information when the hardware module for one of the cable interfaces has either
failed or been removed.
Follow these steps to configure a cable bundle on a loopback interface on the BSR
64000:
1. Use the interface loopback command in Global Configuration mode to enter the
loopback interface that you want to designate as the master cable bundle:
MOT:7A(config)#interface loopback <1-255>
where:
1-255 is the loopback interface number for the master cable bundle.
For example:
MOT:7A(config)#interface loopback 4
2. Use the ip address command in Interface Configuration mode to define an IP
address for the loopback interface:

MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D>

where:
A.B.C.D is the IP address of the BSR interface designated for the loopback
interface.
A.B.C.D is the subnetwork mask of the IP network, on which the interface is
associated.
Note: A 32-bit mask (255.255.255.255) is permitted for a loopback IP

address.
3. Use the ip address secondary command in Interface Configuration mode to

optionally configure a secondary IP address for the loopback interface:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D> secondary
where:
A.B.C.D is the secondary IP address of the BSR interface.
associated.

secondary optionally designates the IP address as a secondary IP address.

Include the keyword secondary after the IP address and subnet mask to
specify additional secondary IP addresses.
If you are running a BCM 3140-based DOCSIS 2.0 2:8 CMTS module as two
1:4 configurations, the limit is still 256 secondary IP subnets for the entire 2:8
CMTS module. The total number of secondary IP subnets between MAC
Domain 0 and MAC Domain 1 can only equal 256. Also, if you apply the
4. Use the show running-config command in Privileged EXEC mode to make sure
that DHCP relay is enabled on the master cable loopback interface. Check the
command output to see if the IP helper address or cable helper address is assigned
to the master cable loopback interface.
5. If the IP helper address or cable helper address is not assigned to the master cable
loopback address, use the ip helper-address or cable helper-address command
in Interface configuration mode to enable DHCP relay. The ip helper-address or
cable helper address specifies the DHCP server.
6. Use the show interfaces loopback command in Interface Configuration mode to
determine if an IP address is assigned to the master cable loopback interface:
MOT:7A(config-if)#show interfaces loopback <1-255>
where:
1-255 is the loopback interface number.

7. If the master cable loopback interface does not have IP address, use the ip
address command in Interface Configuration mode to specify the master cable
loopback interface IP address.
8. Use the cable bundle master command in Interface Configuration mode to
assign the loopback interface as the master cable interface and assign the bundle a
number:
where:
For example:
9. Use the end command in Interface Configuration mode to exit the master cable
interface.
10. Use the show interfaces cable command in Global Configuration mode to make
sure that the slave cable interface does not have an IP address assigned to it:
where:
11. Use the show running-config command in Privileged EXEC mode to verify your
cable bundle configuration for each loopback interface.

Subneting DHCP Clients on the Cable Interface

The DHCP-relay agent, which is the router (SRM) between the cable interface and
DHCP server, monitors DHCP CPE host requests for the presence of the Vendor Class
Identifier (VCI) also known as DHCP Relay Option 60. Vendors define a VCI to
optionally identify the DHCP client vendor type and configuration information. For
example, if a VCI identifies a DHCP client as a Multimedia Terminal Adapter (MTA)
device, the DHCP server can put all MTA devices that are on a cable interface into the
same subnet.
The host and mta VCI options are used to configure a CPE host or MTA gateway IP
address (giaddr) for the cable interface. During the DHCP process, the DHCP relay
agent requests an IP address in a particular subnet by inserting the cable interface
giaddr into the DHCP requests from CMs, hosts, and MTAs. The primary IP address
is always inserted in CM DHCP requests. The ip dhcp relay information option
command must be enabled to allow the BSR to determine what type of device
originated the DHCP request if one or more secondary giaddr IP addresses are defined
for a secondary CM host or MTA device. The primary IP address for the cable
interface is inserted into DHCP requests by default.
Follow these steps to enable a VCI on the cable interface:
1. Enter the desired cable interface.
2. Use the ip address secondary command to define the Gateway IP address
(giaddr) for CPE host DHCP requests or MTA DHCP requests that creates
individual subnets for host CPEs, and MTAs:
Note: The primary IP address for the cable interface is used for CM DHCP
requests.
MOT:7A(config-if)# ip address {<A.B.C.D> <A.B.C.D>} secondary [host |

mta]
where:
secondary specifies that the secondary IP address is a secondary IP address
for CM DHCP requests.

host optionally defines this secondary IP CPE host address as the giaddr to
be inserted into CPE host DHCP requests.
mta optionally defines this secondary IP MTA address as the giaddr to be
inserted into MTA DHCP requests.
Forcing the Primary Cable Address for DHCP Requests

If you need to force the BSR to always set the gateway IP address (giaddr) to use the
primary IP address only for DHCP requests, which is the IP address of the cable
interface, optionally issue the cable dhcp-giaddr primary command in Interface
Configuration mode:
MOT:7A(config-if)#cable dhcp-giaddr primary
Clearing Cable Interface Counters

Use the clear counters cable command in any mode to clear the counters for a cable
interface:
MOT:7A#clear counters cable <X/Y>
where:

Configuring Cable Intercepts

Cable intercept provides a means of monitoring and intercepting data originating from
a cable network. The Cable Intercept feature provides MSOs with Lawful Intercept
capabilities required by the Communications Assistance for Law Enforcement Act
(CALEA) for electronic surveillance. Lawful Intercept capabilities are used by law
enforcement agencies to conduct electronic surveillance of circuit and data
communications.
Warning: Lawful Intercept capabilities to intercept customer traffic are

authorized by either a judicial means to support local laws or through an
administrative order governed by service level agreements (SLAs). The
proper legal or administrative persons must be contacted first before
customer traffic is intercepted and examined.
When a cable intercept is initiated, copies of the data transmissions from and to a
specified Customer Premises Equipment (CPE) MAC address (such as a PC) are sent
to an intercept collector, which is a server at a specified IP address and UDP port
number.
On the 2:8 CMTS module, each MAC domain supports a maximum of 16 cable
intercept entries in the startup configuration and running configuration files for a total
of 32 cable intercept entries for a 2:8 CMTS module. Only one MAC address per CPE
device, such as a PC can be intercepted and only packets from these CPEs are
intercepted.
Cable Intercept Security

Only authorized personnel should be able to configure and monitor current intercepts.
Access to cable intercept functionality is password protected. A user with the
appropriate privilege level is able to enable, disable, and view cable intercepts. Users
without the appropriate privilege level cannot access any cable intercept CLI
commands for configuring or viewing cable intercepts.
A new CLI user group called security, which is similar to the existing sysadmin user
group, is now supported by the BSR. There is a single username, called securityuser,
within this user group which effectively has superuser privileges and is the only
username with access to all cable intercept related commands. All other users will be
excluded from any CLI commands relating to cable intercepts.

For auditing and traceability purposes, it is necessary to log securityuser logins,

logouts, and all cable intercept related commands. This logging information is
available to a user logged in as securityuser with the show log security command.
The following commands are only available to a user logged in as securityuser:
cable intercept
no cable intercept
bridge cable intercept
no bridge cable intercept
clear packet-cable statistics es identifier
clear packet-cable statistics em
show interfaces cable intercept
show log security
show packet-cable statistics es identifier
show packet-cable statistics em
show packet-cable gate identifier
show running-config security
show startup-config security
Configuring the Cable Intercept Feature Through TACACS

Authorization
The following TACACS server configuration is needed to successfully login and
configure the cable intercept feature through TACACS authorization:
Group Configuration
Enable Options -> Max Privilege for any AAA Client
Set to Level 14
TACACS Settings
Check - Shell (Exec)
Check - Privilege Level then input 14 into the box

Shell Command Authorization Settings

Per Group Command Authorization -> Unmatched Cisco IOS Commands
Check - Permit
Note: When the cable intercept feature is enabled, the TACACS

authorization servers must be configured to include a securityuser user with a
privilege level set to 14.
Logging in as securityuser
To login as securityuser, do the following:
1. Use the login command, in User EXEC mode, as follows:
MOT:7A> login securityuser
2. Press the Enter key.
The Password: prompt displays.
3. Enter the default password of securityuser.
4. Press the Enter key to login as securityuser and access Privileged EXEC mode.
The MOT:7A# prompt displays.
Note: Motorola recommends changing the securityuser password from the

default password of securityuser as described in the following section.

Changing the securityuser Password

The securityuser password is encrypted by default. Use one of the forms of the
username password command, in Global Configuration mode, to define a new
encrypted password for the securityuser user account, as shown below.
Note: Although three forms of the username password command are

available, Motorola recommends using forms 1 and 2 from the description
below for specifying a password for securityuser.
1. MOT:7A(config)#username securityuser password <WORD>

2. MOT:7A(config)#username securityuser password 0 <WORD>
3. MOT:7A(config)#username securityuser password 7 <WORD>
(ENCRYPTED)
where:
0 specifies that a plain text password follows.
7 specifies that an encrypted password follows.
WORD defines the password for the securityuser login account and is entered in
plain text.
WORD (ENCRYPTED) defines the encrypted password for the securityuser login
account and is entered as an encrypted password.
The password is always displayed in the encrypted form in any show command
output. For example, the following is an example of typical username output from the
show running-config command:
MOT:7A#show running-config | inc username
username securityuser user-group security

username securityuser password 7 79676a222571d69cd5496dc5c019046d946fe259

Enabling a Cable Intercept

Follow these steps to intercept data for a particular CPE:
1. Use the interface command, in Global Configuration mode, to enter the cable
interface on which you want to enable a cable intercept:
where:
X/Y is the slot and MAC Domain number of the 2:8 CMTS module:
2. Use the cable intercept command, in Cable Interface Configuration mode, to
create a cable intercept to respond to CALEA requests from law enforcement for
traffic regarding a specific user:
MOT:7A(config-if)#cable intercept <mac> <prefix> <0-65535>
where:
mac is the intercept source, which is the MAC address from which traffic is
intercepted. Packets with a source or destination MAC address that matches
this address are copied and forwarded to the data collection server. Most
often, this MAC address is the user's CPE device, and not the MAC address
of the user's CM.
prefix specifies the destination IP address for the data collection server that
receives copies of the forwarded traffic.
0-65535 is the destination User Datagram Port (UDP) port number, which is
used exclusively by the data collection server. A default UDP port number is
not provided.
3. Use the show running-config security command to display configured cable
intercept entries in the running configuration file. Refer to Displaying Cable
Intercept Information for an example of typical configured cable intercept entries
from the show running-config security command screen output.
4. Use the copy running-config startup-configuration command to save the
configuration changes made in the running configuration to the startup
configuration so that these changes are guaranteed to persist across a reboot of the
BSR:

MOT:7A(config-if)#copy running-config startup-configuration
Note: When the BSR is rebooted without a startup configuration file, all
configured cable intercepts will be automatically removed. If the BSR is
rebooted without a startup configuration file, the securityuser password is
reset to the default of securityuser. A non-authorized individual will potentially
be able to login as securityuser and identify any ongoing intercepts. This
scenario should be avoided.
5. Use the show interfaces cable intercept command to view intercept information
for each intercepted CPE MAC address. Each destination IP address and UDP
port for the data collection server are displayed and the total number of packets
and bytes that are intercepted from this CPE are also displayed:
MOT:7A(config-if)#show interfaces cable <X/Y> intercept
where:
X/Y is the slot and MAC Domain number of the 2:8 CMTS module.

Enabling a Bridging Cable Intercept

The bridge cable intercept command creates a cable intercept on a specified bridging
cable modem as a response to a CALEA request from law enforcement for traffic
regarding a specific user. Follow these steps to intercept data for a particular bridging
cable modem:
1. Use the bridge cable intercept command, in Global Configuration mode, to
create a bridging cable modem intercept to respond to CALEA requests from law
enforcement for traffic regarding a specific user:
MOT:7A(config)#bridge cable intercept <mac> modem <mac> <A.B.C.D>
<0-65535>
where:
of the user's CM.
A.B.C.D specifies the destination IP address for the data collection server that
modem mac is the MAC address of the user's cable modem.
not provided.
2. Use the show running-config security command to display configured cable
intercept entries in the running configuration file. Refer to Displaying Cable
Intercept Information for an example of typical configured cable intercept entries
from the show running-config security command screen output.
3. Use the copy running-config startup-configuration command to save the
configuration changes made in the running configuration to the startup
configuration so that these changes are guaranteed to persist across a reboot of the
BSR.

Disabling a Cable Intercept

Follow these steps to disable a cable intercept for a particular CPE:
1. Use the interface cable command, in Global Configuration mode, to enter the
cable interface on which cable intercepts are configured:
where:
2. Use the no cable intercept command, in Cable Interface Configuration mode, to
delete a cable intercept on the cable interface:
MOT:7A(config-if)#no cable intercept <mac> <prefix> <0-65535>
where:
of the user's CM.
prefix specifies the destination IP address for the data collection server that
not provided.

Disabling a Bridging Cable Intercept

Follow these steps to disable a bridging cable modem intercept for a particular
bridging cable modem:
Use the no bridge cable intercept command, in Cable Interface Configuration mode,
to delete a cable intercept on the cable interface:
MOT:7A(config)#no bridge cable intercept <mac> modem <mac> <A.B.C.D>
<0-65535>
where:
intercepted. Packets with a source or destination MAC address that matches this
address are copied and forwarded to the data collection server. Most often, this
MAC address is the user's CPE device, and not the MAC address of the user's
CM.
A.B.C.D specifies the destination IP address for the data collection server that
modem mac is the MAC address of the user's cable modem.
0-65535 is the destination User Datagram Port (UDP) port number, which is used
exclusively by the data collection server. A default UDP port number is not
provided.
Displaying Cable Intercept Information

Use the show running-config security or show startup-config security
commands to display configured cable intercept or bridging cable intercept
entries in the respective running configuration or startup configuration files. The
following displays an example of typical configured cable intercept entries from
the show running-config security or show startup-config security command
screen output.

cable intercept 0000.0001.0201 10.14.38.52 1900

cable intercept 0000.0001.0301 10.14.38.52 1900
cable intercept 0000.0001.0401 10.14.38.52 1900
CPE MAC Data Collection UDP

Address Server IP Port
Address
bridge cable intercept 0000.0000.0004 modem 0017.ee85.b148 150.31.159.77 99
CPE MAC Cable Modem Cable Modem UDP

Address MAC Address IP Address Port
Use the show users command to display the group access level for the
securityuser user account. The following displays an example of typical screen
output from the show users command.
Active connections
user group/privilege origin session
------------------------------------------------------------------
console sysadmin/rw console 0
securityuser security/rw 10.14.37.103 1*

For auditing and traceability purposes, it is necessary to log login, logout, and all
cable intercept related commands. This logging information is available to a user
logged in as securityuser with the show log security command. Use the show log
security command to display logged cable intercept information. The following
displays an example of typical screen output from the show log security
command. The newest logged entries appear first in the output.
[12/13-13:45:20.43- 07:tRDNts0004]-N-session 01 disconnected

[12/13-13:45:20.43- 07:tRDNts0004]-N-user securityuser logged out.
[12/13-13:17:46.58- 02:tNetTask]arptnew failed on 961f9f08
[12/13-13:04:10.09- 07:telnet01]-N-user securityuser authenticated
[12/13-13:03:49.68- 07:telnet01]-N-connection made from 10.14.37.103 on session
01
[12/13-13:03:19.24- 07:telnet01]-N-user enabled-user authenticated
01
[12/13-13:01:36.48- 07:telnet01]-N-user enabled-user authenticated
01
[12/13-13:01:11.11- 07:tRDNts0001]-N-user securityuser logged out.
[12/13-12:59:17.84- 07:telnet01]-repeat 2:-E-Invalid GateID: 0
[12/13-12:59:17.84- 07:telnet01]-E-Invalid GateID: 0
[12/13-12:57:11.81- 07:telnet01]-N-user securityuser authenticated

Use the show interfaces cable intercept command to view statistical information
for each intercepted Customer Premises Equipment (CPE) MAC address.
MOT:7A#show interfaces cable <X/Y> intercept
where:
X/Y is the slot and MAC Domain number of the 2:8 CMTS module:
The show interfaces cable intercept command displays the following CPE
information:
MAC Address MAC (hardware) address of a CPE, such as a

customers PC or VoIP phone.
Destination IP Address IP address of the data collection server.
Destination UDP Port UDP Port number that is used exclusively by the data
collection server.
Packets The total number of packets that have been
intercepted from each specified CPE on this CMTS
interface.
Bytes The total number of bytes that have been intercepted
from each specified CPE on this CMTS interface.
The following is an example of typical screen output from the show interfaces
cable intercept command:
Type: R - Layer 3 Intercept, B - Layer 2 (Bridged) Intercept

Destination Destination
MAC Address IP Address UDP Port Type Packets Bytes
00c0.4f5e.e476 150.31.98.100 10000 R 0 0

Configuring Cable Security Authorized

The Cable Security Authorized feature prevents theft of service by hacked cable
modems. Hacked cable modems will request configuration files unauthorized for their
MAC address or playback an earlier Registration Request transmitted to a different
CM to gain unauthorized service. The Cable Security Authorized feature significantly
reduces the number of unauthorized registrations from hacked cable modems.
Enabling Cable Security Authorized

Use the cable security authorized command, in Cable Interface Configuration mode,
to enable cable security authorization for a MAC domain, as follows:
MOT:7A(config-if)#cable security authorized
Configuring Cable Security Failure

When an initializing CM fails a cable security option check, it is said to have a cable
security failure. In order to account for present and future initializing CMs that may
change their behavior between initialization attempts, the BSR permits an initializing
CM to have one cable security failure before it applies a configured cable security
failure action after the second failure.
Use the cable security failure command, in Cable Interface Configuration mode,
configure how the BSR handles an initializing cable modem after the CMs second
consecutive security failure, as follows:
MOT:7A(config-if)#cable security failure {mark | reject}

where:
mark allows the CM to register, but the CM is marked as having failed a
security option.
reject means that the BSR continues to reject the CMs registration and resets the
consecutive failure count to zero.


A user can specifiy downstream or upstream Channel-IDs instead of using the default
pre-defined Channel IDs that are automatically assigned to the upstream and
downstream ports by the BSR CMTS.
User-defined Channel-IDs can simplify the configuration of features such as Dynamic
Load Balancing (DLB) because user-defined Channel-IDs can be more meaningful to
an user than the default Channel-IDs.
The BSR 64000 now supports the following CableLabs Channel ID ECNs:
OSSI V 2.0-N-04.0201-3
RFI V 2.0-R-04.0200-1
Default Channel IDs

The BSR maintains the default downstream and upstream channel ID tables for each
CMTS module in the BSR chassis. The BSR reads each table to determine if any new
channel ID that has been configured by a user conflicts with a channel ID from the
table that is already in use. If an attempt is made to configure a channel ID that is
equal to the default channel ID value of any other downstream or upstream port on the
BSR, an error message will be generated.
The default upstream channel IDs are determined based on the upstream port number
and the upstream port number and optional logical channel number and are unique
within a CMTS module.
The BSR will save and retain an user-defined channel ID during a reboot/reload of the
BSR chassis if the running configuration file has been copied to the startup
configuration file.

Note: A downstream or upstream channel ID may not be assigned a value

that is equal to the default channel ID value of any other downstream or
upstream port on the BSR.
If an attempt is made to configure a channel ID that is equal to the default

channel ID value of any other downstream or upstream port on the BSR, the
following error message(s) will be generated:
DS channel ID - <X> (a default value) is restricted from

slot <X>, port <Y>
US channel ID - <X> (a default value) is restricted from

slot <X>, port <Y>
Follow these steps to configure a new downstream or upstream Channel ID on a

CMTS module:
desired cable interface:
where:
2. Use the cable downstream channel-id command to specify a Channel ID
number for a downstream port.
MOT:7A(config-if)#cable downstream <NUM> channel-id <0-255>
where:
NUM the downstream port number (0-1).
0-255 is the downstream Channel ID number.
3. Optionally, repeat Step 2 if a Channel ID number for another downstream port
needs to be specified.

4. Use the show controllers cable downstream command to verify the configured
downstream Channel ID.
MOT:7A(config-if)#show controllers cable <X/Y> downstream <NUM>
where:
NUM is the downstream port number.
5. Use the cable upstream channel-id command to specify a Channel ID number
for an upstream port and optional logical channel.
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} channel-id
<1-255>
where:
NUM is the upstream port number
X/Y the upstream port number and optional logical channel number (0-3).
1-255 is the upstream Channel ID number.
Note: When using this command, only the NUM option displays for BCM
3138-based 2:8 CMTS modules. Both the NUM and X/Y arguments display
for BCM 3140-based DOCSIS 2.0 2:8 CMTS.
To determine which 2:8 CMTS module is installed in the BSR 64000, use the
show chassis status command. For BCM 3138-based 2:8 CMTS modules,
the command display reads 2:8 CMTS, and for the BCM 3140-based
DOCSIS 2.0 2:8 CMTS, the display reads, 2:8 CMTS (DOCSIS 2.0).
6. Optionally, repeat Step 5, if a Channel ID number for another upstream port needs
to be specified.
Note: For a user-defined downstream or upstream channel ID to be retained

after a reboot/reload of the of the BSR chassis, use the copy running-config
startup-config command to save the running configuration file as the new
startup configuration file.

7. Use the show controller cable upstream command to verify the configured
upstream Channel ID.
MOT:7A(config-if)#show controller cable <X/Y> upstream <NUM>
where:
NUM is the upstream port number.

2
Configuring a Downstream
Channel
Introduction
A downstream channel is configured to control the data flow from the cable interface
to the users cable modem. This section is divided into two parts. The downstream
parameters that must be configured for the minimal operation of the downstream port
are discussed in the Initial Downstream Configuration Tasks section. The downstream
parameters that are configured to manage the downstream channel operation are
discussed in the Managing the Downstream Channel section.
Initial Downstream Configuration Tasks

This section discusses the following intial downstream configuration tasks:
Configuring the Downstream Frequency and Modulation Rate
Enforcing the Downstream Rate Limit
Enabling the Downstream Port
Entering a Description of the Downstream Port

Configuring the Downstream Frequency and Modulation

Rate
Follow the steps in this section to configure the downstream center frequency and
modulation rate:
1. Use the cable downstream frequency command in Interface Configuration
mode to enter the fixed center frequency for the downstream channel:
MOT:7A(config-if)#cable downstream <NUM> frequency {<91000000
- 857000000>}
Note: The digital carrier frequency cannot be the same as the video carrier
frequency.
where:
91000000 - 857000000 is the downstream frequency in Hertz.
2. Use the cable downstream modulation command in Interface Configuration
mode to set the downstream digital to analog signal modulation rate:
MOT:7A(config-if)#cable downstream <NUM> modulation [64 | 256]
where:
64 is 6 bits per downstream symbol Quadrature Amplitude Modulation
(QAM). This is the default downstream digital to analog signal modulation
rate.
256 is 8 bits per downstream symbol Quadrature Amplitude Modulation
(QAM).
Use the no cable downstream modulation command in Interface Configuration
mode to restore the default (64 QAM):
MOT:7A(config-if)#no cable downstream <NUM> modulation [64 | 256]

Release 5.3.1 Configuring a Downstream Channel
Enforcing the Downstream Rate Limit

Use the cable downstream rate-limit command to enable the downstream data
transmission rate-limit to cable modems on the HFC network. Once the downstream
data transmission rate-limit function is enabled, data sent from the cable interface to
the cable modems is rate-limited according to each cable modem configuration.
Packets are buffered by the CMTS, when the data exceeds the permitted bandwidth of
the cable modem, and queued for transmission once downstream bandwidth for the
cable modem becomes available.
Follow the steps in this section to enable the downstream rate-limit for cable modems:
1. Edit the cable modem configuration file to set the downstream data rate limit.
2. Use the cable downstream rate-limit command in Interface Configuration mode
to enable the rate-limiting function:
MOT:7A(config-if)#cable downstream <NUM> rate-limit
where:
Use the no cable downstream rate-limit command to disable the downstream
rate-limiting function.
3. Use the show running-config command in Privileged EXEC mode to verify that
downstream rate-limiting is enabled or disabled on the cable interface:
4. Use the show cable qos svc-flow statistics command to display the service flow
statistics for all service flow ID (SFID), a specific cable interface, or a specific
service flow:
MOT:7A#show cable qos svc-flow statistics [<X/Y>] [<1-4292967295>]
where:
1-4292967295 is the SFID number.

Enabling the Downstream Port

The downstream port is in an administrative shut-down state by default and must be
enabled to function.
Follow these steps to enable the downstream port:
1. Use the no cable downstream shutdown command in Interface Configuration
mode to enable the downstream port:
MOT:7A(config-if)#no cable downstream shutdown
2. Use the show interfaces cable command in Interface Configuration mode to
verify that the downstream port is enabled:
MOT:7A(config-if)#show interfaces cable <X/Y>
where:
Entering a Description of the Downstream Port

Optionally use the cable downstream description command in Interface
Configuration mode to specify descriptive information for a downstream port. This
information is limited to 80 characters and spaces cannot be used.
Note: The entered description can be seen in the running configuration file,
and in the display output of various show commands such as the show ip
interface command.
MOT:7A(config-if)#cable downstream <NUM> description <LINE>

where:
LINE is the text that describes the downstream port.
For example:
MOT:7A(config-if)#cable downstream 0 description charlestown_1D

Managing the Downstream Channel

The tasks in this section involve some parameters that you may choose to change. If a
parameter default is satisfactory, you can ignore its associated task.
The tasks in this section are used to manage the operation of the downstream channel:
Configuring the Downstream Interleave Depth
Adjusting the Downstream Power Level
Resetting a Downstream Port
Reserving Downstream Bandwidth
Unreserving Downstream Bandwidth
Cable Modem Downstream Frequency Override During Ranging
Testing RF Carrier Modulation
Specifying Downstream Queue Thresholds
Limiting Downstream Multicast Traffic
Configuring the Downstream Interleave Depth

The cable operator can protect the downstream path from excess noise or decrease
latency on the downstream path by setting the interleave depth. A higher interleave
depth provides more protection from noise on the HFC network, but increases
downstream latency. A lower interleave depth decreases downstream latency, but
provides less protection from noise on the HFC network.
1. Review Table Table to determine the appropriate interleave-depth.
Table Interleave Depth Criteria
Depth # of Taps Increments

8 8 16
16 16 8
32 32 4
64 64 2
128 128 1

Note: The Euro DOCSIS standard requires an interleave depth of 12, 12

Taps, and 17 increments.
2. Use the cable downstream interleave-depth command, in Interface

Configuration mode, to set the downstream port interleave depth:
Note: A higher interleave depth provides more protection from bursts of noise
on the HFC network; however, it increases downstream latency.
MOT:7A(config-if)#cable downstream <NUM> interleave-depth [8 | 16 |

32 | 64 | 128]
where:
Use the no cable downstream interleave-depth command in Interface
Configuration mode to restore the default (8 for the North American standard):
MOT:7A(config-if)#no cable downstream <NUM> interleave-depth [8 |
16 | 32 | 64 | 128]

The default downstream power level is 55 decibels per millivolt (550 dBmV). If you
need to adjust the downstream power level, use the cable downstream power-level
command, in Interface Configuration mode, as follows:
MOT:7A(config-if)#cable downstream <NUM> power-level <450-630>
where:
450-630 is the downstream power level expressed in one tenth of a dB.
Use the no cable downstream power-level command in Interface Configuration
mode to restore the default power-level setting (550 dBmV):
MOT:7A(config-if)#no cable downstream <NUM> power-level <450-630>

Resetting a Downstream Port

Follow these steps to optionally reset a downstream port:
1. Use the cable downstream shutdown command, in Interface Configuration
mode, to optionally disable a downstream port if it must be reset:
MOT:7A(config-if)#cable downstream <NUM> shutdown
where:
2. Use the no cable downstream shutdown command, in Interface Configuration
mode, to enable the downstream port again:
MOT:7A(config-if)#no cable downstream <NUM> shutdown
3. Use the show interfaces cable command to verify that the downstream port is
activated:
MOT:7A#show interfaces cable <X/Y> downstream <NUM>
where:
Reserving Downstream Bandwidth

Use the cable downstream reserve-bandwidth command, in Interface Configuration
mode, to reserve a specified amount of downstream bandwidth for cable modems:
MOT:7A(config-if)#cable downstream <NUM> reserve-bandwidth
<1-38469736>
where:
1-38469736 is the amount of downstream bandwidth in bits per second.

Unreserving Downstream Bandwidth

Use the cable downstream unreserve-bandwidth command to unreserve a specified
amount of downstream bandwidth for cable modems, in Interface Configuration
mode:
MOT:7A(config-if)#cable downstream <NUM> unreserve-bandwidth
<1-38469736>
where:
1-38469736 is the amount of downstream bandwidth in bits per second.
Cable Modem Downstream Frequency Override During

Ranging
The Cable Modem Downstream Frequency Override helps the BSR to accelerate
ranging in an RF environment where all downstream signals are seen by all cable
modems but upstream signals are wired discretely. This is accomplished by sending
an RNG-RSP message with a downstream frequency override that tells a specific
cable modem to move to a specific downstream channel. By default, this feature is
disabled.
The Cable Modem Downstream Frequency Override feature is useful if the network is
configured as follows:
there are multiple downstream channels tied together on the same RF pipe
all upstream channels must be physically separated
the same upstream parameters (frequency, modulation, etc.) must be set for all
physical upstream channels
Use the following commands, in Global Configuration Mode, to enable or disable the
Cable Modem Downstream Frequency Override feature:
MOT:7A(config)#cable multi-ds-override
MOT:7A(config)#no cable multi-ds-override
Note: Depending on cable modem software and hardware revisions, this

feature will not be effective if a cable modem does not support the
downstream frequency override in the RNG-RSP message.

Testing RF Carrier Modulation

The downstream carrier-only function is disabled by default and is used for testing
purposes only to control downstream output. Use the cable downstream carrier-only
command in Interface Configuration mode to optionally enable this test function.
MOT:7A(config-if)#cable downstream <NUM> carrier-only
where:
Use the no cable downstream carrier-only command to disable the downstream
carrier-only function.
Specifying Downstream Queue Thresholds

If the BSR is running both a time critical application (such as Voice Over IP) and best
effort service, the cable downstream threshold command guarantees that the
downstream scheduler can only release bandwidth within a certain specified range to
the downstream channel. When a higher priority VOIP packet arrives, the VOIP
packet will move ahead of the previously queued downstream non-VOIP data. This
command allows an operator to configure "back pressure" parameters for various
applications. Use the cable downstream threshold command, in Interface
Configuration mode, to specify downstream channel upper and lower queue
thresholds, as follows:
MOT:7A(config-if)#cable downstream <NUM> threshold {bytes
<500-65535> [<500-65535> ] | pdu <16-256> <16-256>}
where:
bytes uses the byte count as a threshold unit.
500-65535 specifies the upper byte threshold.
500-65535 specifies the optional lower byte threshold.
pdu uses the PDU count as a threshold unit.
16-256 specifies the upper PDU threshold.
16-256 specifies the lower PDU threshold.

The command defaults are listed below.

upper byte threshold = 1000 bytes
lower byte threshold = 500 bytes
upper pdu threshold = 32 PDUs
lower pdu threshold = 16 PDUs
Note: When using the byte count parameter as the threshold unit, you must
specify a value for the lower byte threshold. If the lower byte threshold is not
specified, the BSR will automatically use one half of the upper byte threshold
value as the lower byte threshold value.
Limiting Downstream Multicast Traffic

The BSR can be configured to limit the amount of multicast traffic (including
DVMRP or PIM) on a downstream channel. Limiting the amount of multicast traffic
allows an MSO to balance the bandwidth requirements of IP-based video streaming
services with other bandwidth critical services such as voice traffic or high-priority
business traffic. Multicast traffic rate limiting is achieved by creating a static
multicast downstream service flow and assigning the service flow to a service class.
Use the cable multicast command, in Global Configuration mode, to create a static
multicast downstream service flow and assign the service flow to a service class, as
follows:
MOT:7A(config)#cable multicast <A.B.C.D> <A.B.C.D> [<WORD>]
where:
A.B.C.D is the destination IP multicast address.
A.B.C.D is the destination IP multicast address mask.
WORD is the optional service class name. If the service class is not specified, the
downstream service flow defaults to the DefMCDown service class.
Note: The BSR supports the configuration of 256 downstream multicast

service flows specified by unique combinations of a destination IP multicast
address and destination IP multicast address mask {ipAddr, ipMask}. The
BSR supports the mapping of different downstream multicast service flows to
a specific user defined service class for a maximum of 256 mappings.

For specific information on service classes and service class configuration, refer to
Chapter 9, Configuring Service Classes.
Configuring Multicast Downstream Replication Control

(MDRC)
The Multicast Downstream Replication Control (MDRC) feature controls the
replication of multicast packets on downstream channels. The MDRC feature allows a
user/operator to specify whether replicated multicast traffic, belonging to any
multicast session, should be transmitted on a specific downstream channel. This
functionality is available per downstream channel (not per downstream port) of the
TX32 module and per downstream port of the CMTS 2:8 module. During replication,
the downstream IXP will only replicate a multicast packet on a downstream channel/
port that has been enabled to forward multicast traffic. This will not affect local-scope
multicast, routed broadcast or bridging traffic. This functionality will only affect
routed non-local-scope multicast traffic. If the MDRC feature is enabled on a MAC
domain but no downstream channels are configured as "multicast capable", IGMP
messages will not be reflected on any of the downstream channels of that MAC
domain.
Note: IGMP joins will still be listened for devices using a multicast disabled
downstream. If a device requests a join to a multicast session, the associated
cable modem will be moved to a multicast enabled downstream.
This chapter describes the following MDRC tasks and related commands:
Enabling MDRC on a MAC Domain
Configuring a Multicast Capable Downstream Channel
Enabling MDRC on a MAC Domain

Use the mdrc enable command, in Cable Interface Configuration mode, to enable
Multicast Downstream Replication Control on a MAC Domain, as shown below:
MOT:7A(config-if)#mdrc enable

Configuring a Multicast Capable Downstream Channel

The cable downstream multicast enable command allows a user to configure a
downstream channel as multicast capable. This enables the replication of
downstream multicast packets on the specified channel/port.
Use the cable downstream multicast enable command, in TX32 Downstream Port
Configuration mode, to configure a TX32 downstream channel as multicast
capable, as show below:
MOT:7A(config-ds)#cable downstream <0-3> multicast enable
where:
0-3 is the TX32 downstream channel number.
Use the cable downstream multicast enable command, in Cable Interface
Configuration mode, to configure a CMTS 2:8 downstream channel as multicast
capable, as shown below:
MOT:7A(config-if)#cable downstream <NUM> multicast enable
where:
NUM is the CMTS 2:8 downstream port number.

Displaying Cable Interface Parameters

Select from the following options to display downstream cable interface parameters:
Use the show interfaces cable configuration command in all modes except User
EXEC mode to view the downstream and updtream configuration for the
specified interface:
MOT:7A#show interfaces cable <X/Y> configuration
where:
Use the show interfaces cable downstream command in all modes except User
EXEC mode to view a specified downstream ports statistics for a cable interface.
This command describes whether the downstream port is up or down, the number
of packets and bytes transmitted on the downstream port, how many packets are
discarded, the number of active cable modems, and the associated upstream
Spectrum Group names.
MOT:7A#show interfaces <X/Y> cable downstream <NUM>
where:
Use the show stats cmts command in all modes except User EXEC mode to view
cable interface statistics, which includes both downstream and upstream port
statistics and QOS service flow dynamic statistics:
MOT:7A#show stats <NUM> cmts
where:
NUM is the CMTS slot number.
Refer to the BSR 64000 Command Reference Guide to see typical screen output for
the show interfaces cable configuration, show interfaces cable downstream, and
show stats cmts commands.

Displaying Downstream Parameters

Use the show cable downstream command in Interface Configuration mode to show
the configured parameters for the downstream port:
MOT:7A(config-if)#show cable downstream <NUM>
where:
the show cable downstream command.
Viewing Downstream Port Information

Use the show interfaces cable downstream command in all modes except User
EXEC mode to view downstream port statistics:
MOT:7A#show interfaces cable <X/Y> downstream <NUM>
where:
the show interfaces cable downstream command.

3
DOCSIS 3.0 Features
This chapter provides brief descriptions of the new or enhanced features that are
included in the Motorola Broadband Services Router 64000 (BSR 64000) Release
5.3.0 software. The following new or enhanced features are described:
Partial Services
Dynamic Bonding Change
Expanded Downstream Bonding Groups
Upstream Fiber Node Configuration
MD-CM-SG Ambiguity Resolution
Cable Modem Control (CM-CTRL)
Cable Modem Status (CM-STATUS)
Service Flow Attribute Based Downstream Assignment
Partial Services
Partial Services is a DOCSIS 3.0 concept that was introduced to maintain services
upon the loss of one or more channels in a transmit or receive channel set. Cable
modems operating with a reduced channel set is said to be operating in partial
service mode.

A channel can be declared unusable when the cable modem is unable to acquire it
during registration and/or a Dynamic Bonding Change (DBC) transaction or the cable
modem loses an upstream and/or downstream channel during normal operation.
Partial Service is a temporary mode of operation where service is not be operating
optimally and the loss can be resolved. The cable modem signals that it is operating in
a partial service mode and the CMTS will try and resolve a cable modems partial
service state.
By definition a cable modem is in a partial service mode of operation any time the
cable modem is operating with a subset of the channels in the receive channel set and/
or transmit channel set because a channel has become unusable either due to an
inability to acquire a channel during registration, a DBC transaction taking place, or
because communication on a channel was lost during normal operation. Partial
service mode is intended to be a temporary mode of operation where services may not
operate normally and which can be resolved.
The BSR Partial Service feature protects services that may be interrupted by an
impaired downstream channel(s) in a DBG by allowing cable modems to continue to
operate in partial service mode and by automatically restoring full downstream
operation once the impaired channel(s) are restored. This is achieved through the
implementation of additional registration confirmation codes, the DOCSIS 3.0
specified CM-STATUS message, and the Dynamic Bonding Change (DBC) protocol.
With the introduction of the DBC protocol to move DOCSIS 3.0 bonded cable
modems between channels and around receive channels sets, the DCC protocol has
been re-defined. DCC can now only move DOCSIS 3.0 cable modems across MAC
domains leaving channel movement within MAC Domains to be performed with
DBC. The functionality enforces DBC for DOCSIS 3.0 cable modems operating in a
DOCSIS 3.0 mode and DCC for non-DOCSIS 3.0 cable modems.
The following commands are provided with the Partial Services feature:
cable partial-service
clear cable modem downstream partial-service reset
show cable modem downstream partial-service
Dynamic Bonding Change

Dynamic Bonding Change (DBC) is a DOCSIS 3.0 mechanism that allows a CMTS
and a cable modem to communicate in order to change bonding parameters. At any
time after registration, the CMTS uses DBC to change the receive channel set,
DSID(s) or DSID association attributes

Release 5.3.1 DOCSIS 3.0 Features
The DBC change can only occur within a MAC domain. The CMTS uses a DCC
message to move cable modems between MAC domains. The CMTS can add
channels, delete channels, or change channels within the receive and transmit channel
set(s) of a cable modem by sending a new receive channel and/or transmit channel
through a DBC-REQ message. The CMTS can also add channels, delete channels, or
change channels within the downstream re-sequencing channel list by replacing a
cable modems downstream re-sequencing channel list with a new list.
When communicating a new transmit channel configuration to the cable modem, the
CMTS also includes an updated assignment of SID(s) or SID cluster.
Note: During a DCC, the CMTS modifies the SID, SFID and SAID assignments for
the primary channel. During a DBC, the SID will be changed but SFID and SAID
assignments remain the same.
Expanded Downstream Bonding Groups

Release 5.3.0 increases the maximum number of DOCSIS 3.0 Downstream Bonding
Groups per MAC Domain from 4 to 8 and the maximum number of downstream
channels that can be assigned to a Downstream Bonding Group from 4 to 8.
Upstream Fiber Node Configuration

Upstream fiber node configuration is the ability for the BSR to associate upstream
ports to fiber nodes. Upstream fiber node configuration is an addition to the previous
implementation, introduced in Release 5.2.0, which only supported downstream fiber
node associations. This feature allows the BSR to be configured with a more complete
picture of a cable plants physical topology. An operator configures the list of fiber
nodes in the plant and configures which fiber nodes are reached by each downstream
and upstream channel. Based on this information, along with channel binding and
administrative state, the BSR can automatically determine channel groups reachable
by cable modems on the plant. These channel groups are called
MD-DS-SG-ID (MacDomain-DownStream-ServingGroup)
MD-US-SG-ID (MacDomain-UpStream-ServingGroup)
MD-CM-SG-ID (MacDomain-CableModem-ServingGroup)

As the BSR processes the configuration of channel binding to a MAC Domain and
their associations to fiber nodes, the channels are grouped into respective MD-DS-SG,
MD-US-SG and MD-CM-SGs. They are formed on a per MAC Domain based on the
set of active channels reaching a particular fiber node. The MD-DS-SG, MD-US-SG
and MD-CM-SGs are unique to each MAC Domain. A cable modem is expected to
have access to particular channel groups based on the MAC domain and fiber node
the cable modem is reached by. If multiple fiber nodes reach the same exact set of
channels (upstream, downstream or both), they will share an MD-DS-SG, MD-US-SG
and MD-CM-SG.
The following commands are provided with the upstream fiber node configuration
feature:
cable upstream fiber-node
show cable fiber-node
show cable md-cm-sg
show cable md-us-sg
show interfaces cable downstream
show interfaces cable upstream
MD-CM-SG Ambiguity Resolution

With the introduction of channel bonding in the DOCSIS 3.0 specification, upstream
and downstream channels can be shared across HFC fiber nodes.The BSR must be
aware of the cable modems serving group (MD-CM-SG) for the purpose of channel
set assignment, load balancing, partial service resolution, and other applications.
Determining the cable modems serving group allows the BSR to assign and move
cable modems between reachable upstream and downstream channels.
The BSR may be able to associate a cable modem with a unique MD-CM-SG based
solely upon receiving a ranging message. This can be achieved if the Downstream
Channel ID (DCID), the Upstream Channel ID (UCID) and the MAC Domain
Downstream Service Group ID (MD-DS-SG-ID) are associated with one and only
one MD-CM-SG.

Release 5.3.1 DOCSIS 3.0 Features
If the UCID, DCID and MD-DS-SG-ID found in the ranging message, do not point to
a uniquely defined MD-CM-SG, the BSR performs a sequence of steps to resolve the
cable modems MD-CM-SG. Once the MD-DS-SG is identified, the BSR determines
if the MD-US-SG is unique based on the upstream channel from which the ranging
message was received. If the upstream channel is not associated with a unique
MD-CM-SG, the BSR will send a RNG-RSP with an Upstream Channel Adjustment
TLV containing another upstream channel that can reduce the set of possible
MD-CM-SGs.
The following command is provided with the MD-CM-SG Ambiguity Resolution
feature:
cable cm-sg-resolution
Cable Modem Control (CM-CTRL)

The BSR now supports the CM-CTRL-REQ management message as defined in the
DOCSIS 3.0 MULPI specification. CM-CTRL-REQ is sent to a specified cable
modem to enforce a specific action. It is a replacement for the DOCSIS 2.0 UP-DIS
management message. The CM-CTRL-REQ management message will only be sent
to DOCSIS 3.0 capable cable modems and is used to perform the following actions:
Mute or un-mute an upstream channel. A mute interval must be specified for
mute action, i.e. an amount of time to mute the upstream channel (in
milliseconds).
Reinitialize a cable modem MAC.
Enable or disable the forwarding of PDUs in the upstream and downstream
direction for a specified cable modem.
Override a downstream status event enable bitmask.
Override upstream status event enable bitmask.
Override non-channel specific CM-STATUS event enable bitmask.
CM-CTRL_RSP is a new MAC message specified by DOCSIS 3.0 that is sent from a
cable modem to a CMTS indicating how a recently sent CM-CTRL-REQ message
was handled. The following command is provided with the cable mode control
feature:
cable modem control

Cable Modem Status (CM-STATUS)

CM-STATUS messages are used by a cable modem to report an event condition such
as an MDD timeout or QAM/FEC lock failure. The event condition can be for a
particular downstream channel, a particular upstream channel, or non-channel
specific. Event reporting is enabled by the presence of the appropriate Event Control
TLV 11 and the appropriate bit in the CM-STATUS Event Enable Bit Mask TLV 1.5,
7.2, or 15 in the MDD message.
Channel Specific Events

If an override for the CM-STATUS event enable bitmask for a channel is
specified via a unicast CM-CTRL-REQ message, then the cable modem enables
or disables event reporting for the event type on the channel according to the
bitmask specified in the CM-CTRL-REQ message.
If an override for the CM-STATUS event enable bitmaskis not specified via a
unicast CM-CTRL-REQ message, then the cable modem enables or disables
event reporting for the event type on the channel according to the upstream or
downstream CM-STATUS event enable bitmask provided in the MDD message.
Non-Channel Specific Events

If an override for the CM-STATUS event enable bitmask for a non-channel
specific event is specified via a unicast CM-CTRL-REQ message, then the cable
modem enables or disables the event reporting for the event type according to the
bitmask specified in the CM-CTRL-REQ message.
If an override for the CM-STATUS event enable bitmask for a non-channel
specific event is not specified via a unicast CM-CTRL-REQ message, then the
cable modem enables or disables event reporting for the event type according to
the CM-STATUS event enable bitmask for a non-channel specific event provided
in the MDD message.
The following commands are provided with the cable modem status feature:
cable cm-status-event
cable non-chan-specific cm-status-eventt
cable downstream cm-status-event
cable upstream cm-status-event

Release 5.3.1
Service Flow Attribute Based Downstream

Assignment
DOCSIS 3.0 adds the concept of assigning service flows to channels or bonding
groups based on binary attributes. The BSR will allow for Provisioned Service Flow
Attributes to be configured for downstream channels and downstream bonding
groups. Within the cable modem configuration file and within the TLVs of a cable
modems registration request, service flow encodings now include both required and
forbidden attributes. The BSR attempts to assign channels or bonding groups whose
attributes match the requirements of the service flow (i.e. making a downstream
assignment that has provisioned attributes including all of the cable modems service
flows required attributes and none of the forbidden attributes).
In order to support the service flow attribute feature, the BSR has moved away from a
per cable modem downstream assignment and towards a per service flow downstream
assignment. This allows that multiple downstream assignments to be made in order to
satisfy multiple service flows, each with a unique set of requested attributes.
The following commands are provided with the service flow attribute based
downstream assigment feature:
cable downstream service-flow-attribute
cable downstream bonding-group service-flow-attribute
show cable downstream bonding-groups
show cable qos svc-flow param-set

4
Configuring Downstream
Channel Bonding
Introduction
The Downstream Channel Bonding feature allows the combination of multiple
downstream channels on the BSR 64000 to provide up to 100 Mbps of downstream
throughput for a single cable modem.
In a Downstream Channel Bonding configuration, packets received by the BSR 64000
Network Interface Module (NIM) are forwarded to a 2:8 CMTS module. The CMTS
distributes the packets over multiple downstream channels (referred to as a bonding
group) to a cable modem. The cable modem collects packets received on the
downstream channels, resequences them to the order in which they were transmitted,
and then forwards them to the subscribers Customer Premises Equipment (CPE).
This chapter describes the functionality supported for DOCSIS 3.0 standard
downstream channel bonding. Configuring Downstream Channel Bonding involves
the following procedures:
Configuring a Bonding Domain
Configuring a Bonding Group
Clearing Channel Bonding Statistics
Disabling Downstream Channel Bonding

Configuring a Bonding Domain

The cable downstream bonding-domain command configures a bonding domain
that will be used for binding more than one MAC Domain to a bonding group. The no
cable downstream bonding-domain removes a bonding domain from the BSRs
configuration.
All bonding groups configured in a bonding domain must be deleted before removing
that bonding domain from the BSRs configuration. The BSR will not allow the
configuration of bonding domains whose slots are currently configured in an existing
bonding domain.
For example, if a bonding domain is currently configured to include slots 1 and 2 and
the user wants to remove slot 2 from that bonding domain, the bonding domain
consisting of slots 1 and 2 must first be removed and then a new bonding domain must
be created that only includes slot 1.
Use the cable downstream bonding-domain command, in Global Configuration
mode, to configure a bonding domain.
MOT:7A(config)#cable downstream bonding-domain <NUM> [<NUM>]
where:
NUM is the 2:8 CMTS module slot number.

A bonding group is a set of two or more downstream channels that offer multiple
channel through-put to individual bonding cable modems. The channels comprising a
bonding group must be within the same bonding domain. For release 4.4 a bonding
group is limited to two, three, or four downstream channels. Bonding groups are
defined within the context of a MAC domain. However, the downstream channels
comprising a bonding group may span multiple MAC domains. Hence, the
relationship between a bonding group and a MAC domain is fairly loose. This is a
known violation of the Media Access Control and Upper Layer Protocols Interface
Specification (MULPI) definition for a bonding group, where a bonding group is
associated with a single MAC Domain.

Release 5.3.1 Configuring Downstream Channel Bonding
Bonding modems ranging and registering on a downstream and upstream channel pair
will be considered to be registered in the MAC domain that contains that downstream
and upstream channel pair. Those modems will also belong to the bonding group
configured in that MAC domain. From a forwarding perspective downstream packets
sent to a bonding modem will be forwarded to the MAC domain/interface that the
bonding modem is registered in despite the fact that some of the packets may transit
downstream channels belonging to other MAC domains.
To configure a downstream channel bonding group, do the following:
where:
X is the 2:8 CMTS module slot number.
Y is the MAC domain.
2. Use the cable downstream bonding-group command to configure a downstream
channel bonding group.
MOT:7A(config-if)#cable downstream bonding-group <NUM> <X/Y>
<X/Y> [...<X/Y>]
where:
NUM is the downstream channel bonding group number, which must be 1.
X/Y is a downstream channel associated with this channel bonding group: X
is the 2:8 CMTS module slot number and Y is the MAC domain.
Note: For information on the additonal parameters provided with this

command, refer to cable downstream bonding-group in the BSR 64000
Command Reference Guide.
3. Use the show cable downstream bonding-groups command to verify that the
channel bonding group and its downstream channels are enabled and configured
correctly.
MOT:7A(config-if)#show cable downstream bonding-groups

Clearing Channel Bonding Statistics

Use the clear cable downstream bonding-group statistics command, in any mode
except User EXEC, to clear the channel bonding statistical counters for a cable
interface:
MOT:7A#clear counters cable <X/Y>
where:
Disabling Downstream Channel Bonding

To disable channel bonding for a downstream channel, do the following:
where:
Y is the MAC domain
2. Use the cable downstream bonding disable command to disable downstream
channel bonding.
MOT:7A(config-if)#cable downstream bonding disable
Note: Channel Bonding is enabled by default.
Disabling downstream channel bonding during run-time will result in the

deregistration of all bonding cable modems associated with this MAC
domain.

Release 5.3.1 Configuring Downstream Channel Bonding
Configuring the DOCSIS 3.0 MAC Domain

Descriptor Message Interval
In order to communicate topology and IP layer service initialization parameters to a
DOCSIS 3.0 Cable Modem, the BSR transmits an MAC Domain Descriptor (MDD)
message periodically on every downstream channel in the MAC Domain. The MDD
message is configured with the cable mdd-interval command. A separate MDD
message is sent for each downstream channel associated with the bonding domain
where a DOCSIS 3.0 bonding group is configured. This message is used by the cable
modem during initialization. The information provided to the cable modem in the
MDD message allows the cable modem to identify the downstream fiber node it is
connected to and which downstream channels reach it. The downstream fiber node is
identified by the MAC Domain Downstream Service Group (MD-DS-SG). MDD
messages will coexist on the same downstream channel with Motorola Proprietary
BDM messages if a Motorola Proprietary bonding group and a DOCSIS 3.0 bonding
group share the same channel.
To configure the MAC Domain Descriptor message transmission interval, do the
following:
where:
2. Use the cable mdd-interval command to configure the bonding descriptor
message transmission interval.
MOT:7A(config-if)#cable mdd-interval <0-2000>
where:
0-2000 is the MAC Domain Descriptor message interval in milliseconds.
Entries will be rounded to nearest 50 milliseconds. For example, an entry of
151 milliseconds would be rounded to 200 milliseconds. The default bonding
descriptor message transmission interval is 2000 milliseconds (2 seconds). A
value of "0" disables sending MDD messages on this MAC Domain.

5
Configuring an Upstream
Channel
Introduction
An upstream channel is configured to control the data flow from a cable modem to the
cable interface. This section is divided into two parts. The initial upstream parameters
that must be configured for the minimal operation of the upstream port are discussed
in the Initial Upstream Configuration Tasks section. Modulation profiles are discussed
in the Modulation Profiles section. The upstream parameters that are configured to
manage the upstream channel operation and performance are discussed in the
Managing the Upstream Channel section. In addition, refer to the section About
Upstream Channel Commands before configuring an upstream channe.
Note: The cable interface will not operate until a fixed upstream frequency is
set.

About Upstream Channel Commands

When using the following cable upstream and related show commands, only the
NUM option displays for BCM 3138-based 2:8 CMTS modules. Both the NUM and
X/Y arguments display for BCM 3140-based DOCSIS 2.0 2:8 CMTS modules. These
commands are applicable to both an upstream port or upstream port and logical
channel.
channel-type modulation-profile
data-backoff range-backoff
force-frag show cable upstream
map-interval show interfaces cable upstream
max-calls trap-enable-cmts
minislot-size trap-enable-if
shutdown trap-enable-rdn
When using the following cable upstream commands, both the NUM and X/Y
arguments display for a BCM 3140-based DOCSIS 2.0 2:8 CMTS module. These
commands are only applicable for an upstream port and logical channel and will only
be available through the X/Y argument.
active-codes iuc11-grant-size
codes-minislot maintain-power-density
hopping-seed spread-interval
When using the following cable upstream commands, only the NUM option displays
for BCM 3138-based 2:8 CMTS modules. Both the NUM and X/Y arguments display
for a BCM 3140-based DOCSIS 2.0 2:8 CMTS modules. These commands are only
applicable for an upstream port will only be available through the NUM argument.

Release 5.3.1 Configuring an Upstream Channel
channel-width physical-delay
concatenation power-level
description pre-equalization
frequency range-forced-continue
ingress-canceller range-power-override
invited-range-interval rate-limit
loadbalance-group snr-offset
modem-ranging-delay spectrum-group
Note: To determine which 2:8 CMTS module is installed in the BSR 64000,
refer to Determining the 2:8 CMTS Module Type.
For additional information on any of the above commands, refer to Chapter

13 of the BSR 64000 Command Reference Guide.
Initial Upstream Configuration Tasks

Follow these tasks for the initial configuration of the upstream channel:
Setting the Upstream Frequency
Setting the Upstream Power Level
Enforcing the Upstream Cable Modem Rate Limit
Enabling an Upstream Port
Entering a Description of the Upstream Port


The cable interface does not operate until a fixed upstream frequency is set. The RF
upstream frequency must comply with the expected cable modem output frequency.
Note: Make sure that the upstream frequency selected does not interfere
with the frequencies used for any other upstream applications running in the
cable plant.
1. Use the cable upstream frequency command in Interface Configuration mode to

set the upstream frequency for an upstream port:
MOT:7A(config-if)#cable upstream <NUM> frequency
<5000000-42000000>
where:
5000000-42000000 is the upstream frequency value in Hertz (Hz) for
DOCSIS.
Note: Upstream frequency ranges are different depending on your regional

implementation of DOCSIS or Euro-DOCSIS. The frequency ranges that
appear in the CLI help are related to your implementation of DOCSIS. The
upstream frequency value for Euro-DOCSIS is 5000000 to 65000000 Hz.
Setting the Upstream Power Level

The cable interface controls cable modem output power levels to meet the desired
upstream port input power level. Input power level adjustments to an upstream port
compensate for cable interface signal degradation between the optical receiver and the
upstream RF port. You can configure the upstream input power level in either
absolute or relative mode.
If the upstream input power level is set to the absolute mode, the input power
level does not change when the upstream channel width is changed. Defining the
input power level in absolute mode could possibly cause upstream return lasers to
clip on a completely populated upstream channel.

If the upstream input power level is set in relative mode, the input power level
changes when the upstream channel width is changed. For example, if the input
power level is +11 dBmV for a DOCSIS 3.2 MHz upstream channel bandwidth
setting in relative mode and is changed to 1.6 MHz, the default receive power is
+8 dBmV. The default power levels for the 3.2 MHz and 1.6 MHz channels are
equal relative to their respective channel bandwidth settings.
Caution: If the power level is not explicitly set on the upstream interfaces,
they default to 0 dBmV in absolute mode with a 3.2 MHz, 2560 kilosymbols
per second rate. Ensure that the correct power level is set on each upstream
channel.
Table Table describes how the upstream channel bandwidth corresponds to the input
power-level range and default power-level range for a specific upstream channel.
Table Upstream Input Power Level Range Parameters
Upstream Channel Default Power-level Power-level

Bandwidth Range Range
200 KHz -1 dBmV -16 to +14 dBmV
400 KHz +2 dBmV -13 to +17 dBmV
800 KHz +5 dBmV -10 to +20 dBmV
1.6 MHz +8 dBmV -7 to +23 dBmV
3.2 MHz +11 dBmV -4 to +26 dBmV
Setting the Upstream Power Level in Relative Mode

Use the cable upstream power-level default command in Interface Configuration
mode to set the upstream input power level in relative mode:
MOT:7A(config-if)#cable upstream <NUM> power-level default <offset>
where:
offset is the number expressed in dB above or below the default input power level.

Example 1:
mode to set the input power level for a 3.2 MHz channel in relative mode from +11
dBmV to +5 dBmV:
MOT:7A(config-if)#cable upstream 0 power-level default -60
The default input power level is reduced by 6 dBmV. The power level is now
+5 dBmV.
Example 2:
mode to set the input power level for a 3.2 MHz channel in relative mode from +11
dBmV to 0 dBmV:
MOT:7A(config-if)#cable upstream 0 power-level default -110
The default input power level is reduced by 11 dBmV.
Setting the Upstream Power Level in Absolute Mode

Use the cable upstream power-level command in Interface Configuration mode to
set the upstream input power level in absolute mode:
Caution: Use caution when increasing the input power level in absolute
mode. The cable modems on the HFC network increase their transmit power
level by 3 dB for every incremental upstream channel bandwidth change,
causing an increase in the total power on the upstream channel. This may
violate the upstream return laser design parameters
MOT:7A(config-if)#cable upstream <NUM> power-level <power>

where:
power is the input power level, expressed in dB.
Example
Use the cable upstream power-level command in Interface Configuration mode to
set the upstream input power level to +5 dBmV in absolute mode, which keeps the
input power level at +5 dBmV regardless of the upstream channel bandwidth setting:
MOT:7A(config-if)#cable upstream 0 power-level 50

Enforcing the Upstream Cable Modem Rate Limit

Use the cable upstream rate-limit command to enable the upstream data
transmission rate-limit. This limits the traffic rate for data sent from the cable modems
to the cable interface. Packets are buffered by the CMTS, when the data exceeds the
permitted bandwidth of the cable modem, and queued for transmission once upstream
bandwidth for the cable modem becomes available.
Follow these steps to enable the upstream rate-limit for cable modems.
1. Edit the cable modem configuration file to set the upstream data rate limit.
2. Use the cable upstream rate-limit command in Interface Configuration mode to
enable the rate-limiting function:
MOT:7A(config-if)#cable upstream <NUM> rate-limit
where:
If you need to disable the upstream rate-limiting function, use the no cable
upstream rate-limit command.
3. Use the show running-config command in Privileged EXEC mode to verify that
upstream rate-limiting is enabled or disabled on the cable interface:
4. Use the show cable qos svc-flow statistics command in Privileged EXEC mode
to determine the number of packets dropped due to upstream rate-limiting for a
particular service flow:
MOT:7A#show cable qos svc-flow statistics <X/Y> [<1-4292967295>]
where:
1-4292967295 is the Service Flow Identifier (SFID).

Enabling an Upstream Port

The upstream ports are in an administrative shut down state by default.
Follow these steps to enable the upstream ports:
1. Use the show interfaces cable command to determine if an upstream port is
activated or deactivated:
MOT:7A(config)#show interfaces cable <X/Y> upstream {<NUM> |
<X/Y>}
where:
upstream NUM is the upstream port number.
upstream X/Y is the upstream port and logical channel number (0-3).
2. Navigate to Cable Interface Configuration mode, as follows:
MOT:7A(config)#interfaces cable <X/Y>
where:
3. The upstream ports are in a shutdown state by default. Use the no cable
upstream shutdown command in Interface Configuration mode to enable the
upstream ports:
MOT:7A(config-if)#no cable upstream {<NUM> | <X/Y>} shutdown
where:
X/Y is the upstream port and logical channel number (0-3).


Optionally issue the cable upstream description command in Interface
Configuration mode to specify descriptive information for the upstream port that you
are configuring. This information is limited to 80 characters and spaces cannot be
used.
Note: The entered description can be seen in the running configuration, and
in the command output of show commands such as the show ip interface
command.
MOT:7A(config-if)#cable upstream <NUM> description <LINE>

where:
LINE is the text that describes the upstream port.
For example:
MOT:7A(config-if)#cable upstream 3 description charlestown_1U3
Modulation Profiles
A modulation profile is a collection of up to eight burst profiles that are sent out in an
Upstream Channel Descriptor (UCD) message to configure cable modem
transmission parameters for upstream traffic. Each upstream transmission burst type
is given a number called the Interval Usage Code (IUC). IUC codes are used to
allocate upstream time slots. The following IUC codes are supported:
IUC 1 Request Burst - opportunity for cable modems to transmit bandwidth
requests
IUC 3 Initial Maintenance - opportunity for cable modems to join the network by
sending an initial ranging request
IUC 4 Station Maintenance -cable modem periodic ranging
IUC 5 Short Grant Burst - short data burst
IUC 6 Long Grant Burst - long data burst
IUC 9 Advanced PHY Short Data Grant - advanced short data burst
IUC 10 Advanced PHY Long Data Grant - advanced long data burst

IUC 11 Unsolicited Grant Service - advanced unsolicited grant service

DOCSIS 1.0 and 1.1 cable modems use IUCs 5 and 6 for data transmission while
DOCSIS 2.0 cable modems use IUCs 9, 10, and 11 for data transmission. IUCs 9, 10,
and 11 may use higher modulation orders not supported by DOCSIS 1.0 and 1.1. IUC
11 was added for unsolicited grant service (UGS) flows.
Warning: Motorola does not recommend modification of modulation profile

parameters without a thorough understanding of modulation changes and
DOCSIS interface specifications. Modulation profile parameters will affect the
physical layer and may cause disruption or degradation of services.

The Modulation Profile Numbering Scheme

With Release 4.1.0, the number of modulation profiles supported by the BSR has been
increased from 16 to 600. The number of pre-defined modulation profiles supported
has also been increased and a user is allowed to modify a pre-defined modulation
profile. There are 35 default modulation profiles assigned to the TDMA (1-4),
MTDMA (101-116), A-TDMA (201-205), and S-CDMA (301-310) channel types.
The numbering ranges for pre-defined modulation profiles for each channel type are
as follows:
1-100 = TDMA
101-200 = MTDMA
201-300 = A-TDMA
301-400 = S-CDMA
The total number of defined modulation profiles can be determined with the show
cable modulation-profile brief command.
Note: For a complete list and configuration of all 35 pre-defined modulation

profiles, refer to Appendix A.
For guidelines on modifying modulation profile parameters, refer to

Appendix B.
Displaying Configured Modulation Profiles

1. Use the show cable modulation-profile command to view all existing
modulation profiles, as shown below:
MOT:7A#show cable modulation-profile
2. Use the show cable modulation-profile command to view a specific modulation
profile, as shown below:
MOT:7A#show cable modulation-profile <1-600>
where:
1-600 is the modulation profile number.
3. Use the show cable modulation-profile brief command to view cursory
information about all configured modulation profiles, as shown below:
MOT:7A#show cable modulation-profile brief

The show cable modulation-profile brief command displays which modulation

profiles are pre-defined, pre-defined but modified by the user, or user configured
as shown in the sample command output below:
Profile Chan-type Config-status In-use

1 tdma pre-defined yes
2 to 4 tdma pre-defined
5 tdma user-configured
6 tdma user-configured
101 mtdma pre-defined, changed
102 to 116 mtdma pre-defined
201 to 205 A-TDMA pre-defined
301 to 310 S-CDMA pre-defined
Determining the Modulation Profile Applied to an Upstream

Port
Follow these steps to determine which modulation profile is applied to a specific
upstream channel:
where:
2. Use the show cable upstream command, in Cable Interface Configuration mode,
to determine which modulation profile is applied to an upstream port, as shown
below:
MOT:7A(config-if)#show cable upstream {<NUM> | <X/Y>}
where:
X/Y is the updtream port number and logical channel number (0-3).

ifIndex: 46989444
description:
centerFreq: 13200000
rng_back_st: 0
rng_back_en: 4
data_back_st: 2
data_back_en: 8
channelWidth: 3200000
powerLevel: 0 (10th of dB)
slotSize: 0
force-frag: 0
map-interval: 4000 (usec)
pre-equalization: 0
invited-range-interval: 10000 (msec)
range-forced-continue: 0
range-power-override: false
concatenation: true
physical-delay: Mode 0, Min 400, Max 1600
rate-limit: 0
modulation-profile: 301 Modulation Profile
max-calls: 0 Number
Spectrum Group:
Channel type: S-CDMA
S-CDMA active codes: 126
S-CDMA codes per slot: 2
S-CDMA spreading intrvl: 16
S-CDMA hopping seed: 0
Ingress canceller state: enabled
Ingress canceller idle interval: 320 (symbols)
Ingress canceller idle frequency: 5
Maintain power spectrum density: off
Modem ranging delay: 250 (usec)
IUC 11 grant size: 0

Modulation Profile Configuration Mode

Modulation Profile Configuration Mode allows you to configure or modify a
modulation profile. DOCSIS 1.0, 1.1, and 2.0 modulation profiles can be configured
through this mode.
Entering Modulation Profile Configuration Mode

To enter Modulation Profile Configuration Mode, use the cable modulation-profile
command, as shown below:
MOT:7A(config)#cable modulation-profile <1-600>
where:
Note: Modulation profiles 1-4, 101-116, 201-205, and 301-310 are

pre-configured modulation profiles.
Motorola recommends that user-created modulation profiles use the

numbering range of 401-600 to ensure better future portability.
The prompt changes to config-modprof followed by the specified modulation

profile number and IUC submode (Figure Figure ).
MOT:7A(config-modprof:5:request)#
Modulation IUC
Profile Submode
Number
Figure The Modulation Profile Configuration Mode Prompt
There are 8 IUC submodes (a-long, a-short, a-ugs, initial, long, request, short, and
station). The default IUC submode is request. There are two ways to enter a different
IUC submode:

A different IUC submode can be specified when entering Modulation Profile

Configuration Mode. For example:
MOT:7A(config)#cable modulation-profile 5 a-long
A different IUC submode can be specified when in Modulation Profile
Configuration Mode with the iuc command. For example:
MOT:7A(config-modprof:5:request)#iuc a-long
Configuring a Modulation Profile

There are two methods of configuring a modulation profile in Modulation Profile
Configuration Mode:
The iuc command can be used to completely configure a modulation profile
without having to enter individual IUC submodes.
A modulation profile can be configured on an IUC submode by submode basis..
Note: The modulation profile parameters that need to be configured are

dependant on the DOCSIS channel type.


For a complete list and configuration of all 35 pre-defined modulation profiles,

refer to Appendix A.
Configuring a Modulation Profile with the iuc Command

Follow these steps to configure a modulation profile using the iuc command:
1. Use the cable modulation-profile command in Global Configuration mode to
enter Modulation Profile Configuration Mode for the modulation profile that you
want to configure or modify, as shown below:

where:
1-600 is a modulation profile number.
2. Use the iuc command in Modulation Profile Configuration Mode to configure a
new modulation profile, as shown below:
MOT:7A(config-modprof:<modulation profile number>:<IUC Submode>)#
iuc {a-long | a-short | a-ugs | initial | long | request | short | station} [A-TDMA
| mtdma | S-CDMA | tdma] {128qam | 16qam | 256qam | 32qam | 64qam |
8qam | qpsk} {<0-16>} {<16-253>} {fixed | short} {<0-255>} {off | on}
{<0x0-0x7fff>} {off | on} {none | qpsk0 | qpsk1} {<0-1536>} {<0-2048>}
{<0-2048>} {<0-32>} {off | on} {<0-128>} {off | on}
Table Table provides a description of each parameter listed in the iuc command
syntax above.

Table iuc Command Modulation Profile Parameters and Descriptions
Parameter Description
The Interval Usage Code:
a-long Advanced PHY long data grant

a-short Advanced PHY short data grant
a-ugs Unsolicited Grant Service
initial Initial Ranging Burst
long Long Grant Burst
request Request Burst
short Short Grant Burst
station Station Ranging Burst
128qam The modulation type:
16qam
256qam 128qam is used for DOCSIS 2.0 A-TDMA or S-CDMA channel
32qam types only - creates a default 128 -QAM modulation type where
64qam all bursts are sent using 128-QAM.
8qam
qpsk 256qam is used for DOCSIS 2.0 A-TDMA or S-CDMA channel
types only - creates a default 256 -QAM modulation type where
all bursts are sent using 256-QAM.
16qam creates a default 16-QAM modulation type where all

bursts are sent using 16-QAM.
32qam is used for DOCSIS 2.0 A-TDMA or S-CDMA channel

types only - creates a default 32-QAM modulation type where all
64qam used for DOCSIS 2.0 A-TDMA or S-CDMA channel

8qam is used for DOCSIS 2.0 A-TDMA or S-CDMA channel

qpsk creates a default QPSK modulation type where all bursts

are sent using QPSK.

Parameter Description
0-16 the number of bytes that can be corrected per FEC code word
16-253 the FEC code word length
fixed fixed handling of FEC for last code word
short shortened handling of FEC for last code word
0-255 the maximum burst length in minislots
off | on disable/enable scrambler
0x0-0x7fff the scrambler seed in hexadecimal format
off | on disable/enable differential encoding
Note: If a modulation profile is in use, differential encoding
cannot be enabled or disabled for any of the burst types. To
enable or disable differential encoding for a burst type, an
operator must copy the modulation profile to a new modulation
profile number, enable or disable differential encoding for the
new modulation profile, and assign the new modulation profile to
the desired upstream channel. Attempting to enable or disable
differential encoding for a modulation profile that is in use will
generate the following error message:
[10/07-10:26:06.59- 07:CRMTASK]-E-mod profile

in use, cannot change diff encoding
none the preamble type
qpsk0 low power QPSK preamble
qpsk1 high power QPSK preamble
0-1536 the preamble length in bits
0-2048 the interleaver depth value
0-2048 the interleaver block size value
0-32 the interleaver step size
off | on turn spreader off/on (S-CDMA only)
0-128 the codes subframe value (S-CDMA only)
off | on turn TCM encoding off/on - indicates whether trellis code
modulation (TCM) is enabled for (S-CDMA only)
3. Use the show cable modulation-profile command in Privileged EXEC mode to

view the modulation profile parameters and verify the configuration, as shown
below:


where:



Configuring a Modulation Profile Through an IUC Submode

Follow these steps to configure modulation profile on an IUC submode by submode
basis:
1. Use the cable modulation-profile command in Global Configuration mode to
enter Modulation Profile Configuration Mode for the modulation profile that you
want to configure or modify, as shown below:
where:
2. Use the commands shown below to configure a modulation profile on an IUC
submode by submode basis.




IUC Submode Commands
Command Description
channel-type Specifies the channel type for a modulation profile.

codes-subframe Specifies the sub-frame size. (S-CDMA only)
differential-encoding on Disables or enables differential encoding.
Note: If a modulation profile is in use, differential encoding
cannot be enabled or disabled for any of the burst types. To
enable or disable differential encoding for a burst type, an
operator must copy the modulation profile to a new modulation
profile number, enable or disable differential encoding for the
new modulation profile, and assign the new modulation profile
to the desired upstream channel. Attempting to enable or
disable differential encoding for a modulation profile that is in
use will generate the following error message:
[10/07-10:26:06.59- 07:CRMTASK]-E-mod profile

in use, cannot change diff encoding
fec-codeword Specifies the Forward Error Correction (FEC) code word
length.
fec-correction Specifies the number of bytes that can be corrected per FEC
code word.
interleaver-block-size Specifies the interleaver block size value.
interleaver-depth Specifies the interleaver depth value.
interleaver-step-size Specifies the interleaver step size value.
last-codeword-length Specifies the handling of FEC for the last code word.
max-burst Specifies the maximum burst length in minislots.
modulation-type Specifies the modulation profile modulation type.
preamble-length Specifies the preamble length in bits.
preamble-type Specifies the preamble type.
scrambler-mode Disables or enables the scrambler.
scrambler-seed Specifies the scrambler seed in hexadecimal format.
spreader on Disables or enables the spreader. (S-CDMA only)
tcm-encoding on Disables or enables the TCM Encoding. (S-CDMA only)
3. Use the show cable modulation-profile command in Privileged EXEC mode to

view the modulation profile parameters and verify the configuration, as shown
below:
where:



Applying a Modulation Profile

Modulation profiles 1-4 or user configured modulation profiles 5-16 can be applied to
an upstream channel for a cable interface. Follow these steps to apply a modulation
profile to an upstream channel:
1. Use the show cable modulation-profile command to view a specific modulation
profile, as shown below:
where:
2. Use the cable upstream modulation-profile command in Interface
Configuration mode to apply an upstream modulation profile to an upstream port,
as shown below:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>}
modulation-profile <1-600>
where:
X/Y is the upstream portnumber and logical channel number (0-3).

Use the no cable upstream modulation profile command to restore the default,
as shown below:
MOT:7A(config-if)#no cable upstream {<NUM> | <X/Y>}
modulation-profile <1-600>
where:
X/Y is the updtream portnumber and logical channel number (0-3).
Note: When a modulation profile is assigned to an upstream channel, the

assignment will be rejected if any of the following rules are violated:
Differential encoding can only be enabled for TDMA, MTDMA, and

A-TDMA channel types not the S-CDMA channel type.
Differential encoding can only be enabled for bursts using the QPSK and
16QAM modulation types.
For the TDMA and MTDMA channel types, the differential encoding
setting (enabled or disabled) must be the same for IUC's 1, 3, 4, 5, and 6.
For the A-TDMA channel type, the differential encoding setting (enabled
or disabled) must be the same for IUC's 1, 3, and 4.
For the MTDMA and A-TDMA channel types, the differential encoding
setting (enabled or disabled) must be the same for IUC's 9, 10, and (if
defined) IUC 11.
Copying a Modulation Profile

Use the cable modulation-profile copy command, in Global Configurtion mode, to
copy an existing modulation profile from a source modulation profile number to a
destination modulation profile number, as show below. The destination modulation
profile number is overwritten by the source modulation profile number.
MOT:7A(config)#cable modulation-profile copy {<1-600>} {<1-600>}
where:
1-600 is the source modulation profile number.
1-600 is the destination modulation profile number.

Restoring a Default Modulation Profile Configuration

Use the cable modulation-profile reset command to reset a modified, pre-defined
modulation profile back to the system default. There are 35 default modulation
profiles assigned to the TDMA (1-4), MTDMA (101-116), A-TDMA (201-205), and
S-CDMA (301-310) channel types.
MOT:7A(config)#cable modulation-profile reset {<1-4> | <101-116> |
<201-205> | <301-310>}
where:
1-4, 101-116, 201-205, 301-310 is the pre-defined modulation profile number.

Deleting a Modulation Profile or IUC

Follow these steps to delete a modulation profile or an IUC from a modulation profile:
1. Use the no cable modulation-profile command, in Global Configuration mode,
to delete a configured modulation profile, as shown below:
MOT:7A(config)#no cable modulation-profile <1-600>
where:
1-600 is a modulation profile number to be deleted.
2. Use the no cable modulation-profile command, in Global Configuration mode,
to delete an IUC from a configured modulation profile, as shown below:
MOT:7A(config)#no cable modulation-profile <1-600> [a-long | a-short |
a-ugs | initial | long | request | short | station]
where:
a-long deletes the Advanced PHY long data grant IUC.
a-short deletes the Advanced PHY short data grant IUC.
a-ugs deletes the Unsolicited Grant Service IUC.
initial deletes the Initial Ranging Burst IUC.
long deletes the Long Grant Burst IUC.
request deletes the Request Burst IUC.
short deletes the Short Grant Burst IUC.
station deletes the Station Ranging Burst IUC.
Managing the Upstream Channel

The following upstream tasks in this sections are used to manage or improve the
performance of the upstream channel:
Configuring Upstream Cable Modem Registration Parameters
Moving a Cable Modem or MTA to a Different Upstream Channel
Adjusting for Physical Delay between the Cable Interface and Cable Modems
Enabling Pre-equalization

Forcing the Fragmentation of Large Upstream Packets

Disabling an Upstream Port
Configuring the Upstream Channel Descriptor
Limiting the Number of Voice Calls on an Upstream Channel
Enabling/Disabling CMTS Concatenation Capabilities
Enabling/Disabling Concatenation for DOCSIS 1.0 Cable Modems
Configuring Upstream Cable Modem Registration

Parameters
Configuring upstream cable modem registration parameters includes the following
options:
Setting the Upstream Minislot Size
Setting the Upstream Channel Width
Setting the Upstream Range-backoff
Forcing a Range-response
Forcing a Range Power Override
Setting the Upstream Data-backoff
Configuring the Invited Ranging Interval
Configuring the Map Interval
Note: For any cable modem TFTP configuration files using the Upstream
Channel ID configuration Setting (TLV type 2), you must edit the configuration
file to update the channel ID TLV. Taking this action ensures that cable
modems implementing upstream channel override will interoperate properly
with the upstream channel numbering convention. If your modems implement
upstream channel override, failure to update the cable modems TFTP
configuration file to accommodate the BSR upstream channel numbering
convention will result in the cable modems being unable to complete
registration.
Follow these options to configure upstream cable modem registration parameters:

Use the cable upstream minislot-size command in Interface Configuration mode
to set the upstream minislot size:

MOT:7A(config-if)#cable upstream <NUM> minislot-size [2 | 4 | 8 | 16 |

32 | 64 | 128]
where:
Use the no cable upstream minislot-size command in Interface Configuration
mode to reset the upstream minislot size:
MOT:7A(config-if)#no cable upstream <NUM> minislot-size [2 | 4 | 8 |
16 | 32 | 64 | 128]
where:
Use the cable upstream channel-width command in Interface Configuration
mode to set the upstream channel width in Hertz (Hz):
MOT:7A(config-if)#cable upstream <NUM> channel-width [200000 |
400000 | 800000 | 1600000 | 3200000]
where:
Use the no cable upstream channel-width command in Interface Configuration
mode to reset the default:
MOT:7A(config-if)#no cable upstream <NUM> channel-width [200000 |
400000 | 800000 | 1600000 | 3200000]
where:
Use the cable upstream range-power-override command in Interface
Configuration mode to enable cable modem power adjustment:
MOT:7A(config-if)#cable upstream <NUM> range-power-override
where:

Use the no cable upstream range-power-override command in Interface

Configuration mode to disable the power adjustment:
MOT:7A(config-if)#no cable upstream <NUM> range-power-override
where:
Use the cable upstream data-backoff command in Interface Configuration
mode to set the upstream data-backoff start and end values. If you choose
automatic, the system selects the upstream data-backoff start and end values.
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} data-backoff
[automatic | <0-15> | <0-15>]
where:
0-15 is the start value.
0-15 is the end value.
Use the no cable upstream data-backoff command in Interface Configuration
mode to restore the upstream data-backoff default:
MOT:7A(config-if)#no cable upstream {<NUM> | <X/Y>} data-backoff
[automatic | <0-15> | <0-15>]
where:
X/Y is the upstream port and logical channel number (0-3)
0-15 is the start value.
0-15 is the end value.
The default time value allowed by the cable interface between ranging requests
transmitted by the cable modem is 10000 milliseconds. If you need to adjust the
time value allowed between ranging requests, use the cable upstream
invited-range-interval command in Interface Configuration mode:
MOT:7A(config-if)#cable upstream <NUM> invited-range-interval
<0-30000>

where:
0-30000 is the number of milliseconds allowed between ranging requests.
Use the cable upstream map-interval command in Interface Configuration
mode to determine the time interval in microseconds for bandwidth maps
messages (MAP) to be used by the cable modem to allocate upstream time slots,
as shown in the following command example:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} map-interval
<2000-16000>
where:
2000-16000 is the time interval in microseconds. The default is 4000
microseconds.
The initial ranging start and end backoff values are a part of the Upstream
Bandwidth Allocation Map (MAP) that cable modems use to register with the
CMTS. If a cable modem initial ranging request collides with requests from other
cable modems during the initial ranging process, the cable modem initial ranging
request is lost. The CMTS does not directly detect the collision. The cable
modem determines that a collision (or other reception failure) occurred when the
next MAP fails to include acknowledgement of the request. The cable modem
must then perform a back-off algorithm and retry its initial ranging request
causing prolonged cable modem downtime.
The initial ranging backoff start and end number of backoffs (wait times) can be
adjusted to randomize when initial ranging is initiated by cable modems that are
colliding during initial ranging. This adjustment lowers the odds for cable
modems colliding again, reducing the amount of time that a cable modem is
down.
Use the cable upstream range-backoff command in Interface Configuration
mode to set the initial ranging backoff start and end time. If the automatic
argument is used, the CMTS automatically sets the upstream data-backoff start
and end values:

MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} range-backoff

[automatic | <0-15> | <0-15>]
where:
automatic prompts the ranging backoff to start and end automatically.
0-15 is the start ranging backoff number of requests.
0-15 is the end ranging backoff number of requests.
Use the no cable upstream range-backoff command in Interface Configuration
mode to return the range-backoff function to the default:
MOT:7A(config-if)#no cable upstream {<NUM> | <X/Y>} range-backoff
[automatic | <0-15> | <0-15>]
where:
automatic prompts the ranging backoff to start and end automatically.
0-15 is the start ranging backoff number of requests.
0-15 is the end ranging backoff number of requests.
Moving a Cable Modem or MTA to a Different Upstream

Channel
Use the cable modem ucc command in Privileged EXEC mode to move a cable
modem or MTA to a different upstream channel
A cable modem or MTA can be moved to a different upstream channel within the
same spectrum group and the same MAC domain after registration to balance the
number of cable modem or MTAs evenly among the receivers of the CMTS module to
utilize the entire upstream bandwidths more efficiently.
MOT:7A#cable modem {<mac> | <prefix>} ucc <0-7>
where:
mac is the cable modem MAC address in the form of xxxx.xxxx.xxxx.
prefix is the cable modem IP address.

0-7 is the channel number.
Adjusting for Physical Delay between the Cable Interface

and Cable Modems
The physical delay function is used to adjust the upstream propagation delay
threshold between the cable interface and cable modems. The cable interface adjusts
the physical delay function automatically by default.
You can use the following options to adjust the physical delay function:
A single fixed time can be set for physical delay.
Physical delay parameters can be configured so that they are adjusted
automatically by the BSR when you use the automatic option with a specified
minimum and maximum range in microseconds.
If you do not want to specify a range for the automatic option, select the
automatic option only.
Use the cable upstream physical-delay automatic command in Interface
Configuration mode to set the automatic physical delay value for an upstream
channel:
MOT:7A(config-if)#cable upstream <NUM> physical-delay automatic
[<10-1600> | <10-1600>]
where:
10-1600 is the minimum upstream physical delay in microseconds. The default
value is 200 microseconds.
10-1600 is the maximum upstream physical delay in microseconds. The default
value is 1600 microseconds.
-or-
Use the cable upstream physical-delay command in Interface Configuration mode to
set the fixed value for an upstream channel:
MOT:7A(config-if)#cable upstream <NUM> physical-delay <10-1600>
where:

10-1600 is the fixed upstream physical delay value in microseconds. The default
is 800 microseconds.
The 800 microsecond default setting is an optimal setting for HFC networks with a
radius of not more than 50 miles (i.e., distance to the farthest cable modem).
However, when the default setting of 800 microseconds is in force on HFC plants
with a radius larger than 50 miles, cable modems may not be able to register or pass
data reliably since the round-trip propagation delay exceeds the configured value for
the physical delay (i.e, cable modems are not given enough time to register).
Note: Setting a physical delay value larger than required is allowed, although
data passing performance will not be optimized. However, do not set a
physical delay value smaller than required since this might cause some cable
modems to become inoperable.
Should you need to change the default value for the physical delay, refer to the
guidelines in the table that follows or calculate a setting value using the formulas that
follow the table.
BSR
Physical
Delay One-way One-Way Round trip Round trip
Transit Delay Setting distance Distance distance distance
(microsecs) (microsecs) (miles) (kilometers) (miles) (kilometers)
800 1,600 100.0 160.9 200.0 321.9
700 1,400 87.5 140.8 175.0 281.6
600 1,200 75.0 120.7 150.0 241.4
500 1,000 62.5 100.6 125.0 201.2
400 800 50.0 80.5 100.0 160.9
300 600 37.5 60.4 75.0 120.7
200 400 25.0 40.2 50.0 80.5
100 200 12.5 20.1 25.0 40.2
To calculate a setting value for your HFC plant, follow these steps using one of the
formulas provided in Step 2:

1. Determine the distance from the BSR 64000 (i.e, CMTS) to the most distant cable
modem measured in miles (or kilometers) of HFC (i.e, physical cable length).
2. Calculate the value for the physical delay using one of the following formulas:
For HFC measured in miles:
16 x L = PD
where
L is the value determined in Step 1.
PD is the value to specify for the command cable upstream physical-delay
For HFC measured in kilometers:
9.95 x L = PD
where
L is the value determined in Step 1.
PD is the value to specify for the command cable upstream physical-delay
Note: The physical delay cannot be configured to a value less than 10

microseconds.
Enabling Pre-equalization
Use the cable upstream pre-equalization command to enable the pre-equalization
adjustment function on the upstream port, which includes sending pre-equalization
coefficients in a ranging response to a cable modem to compensate for impairment
over the transmission line in Interface Configuration mode:
Note: Not all cable modems support the pre-equalization adjustment. If you
enable the pre-equalization adjustment for an upstream port and the cable
modem does not support this adjustment, the cable interface may not receive
valid upstream data from the cable modem.
MOT:7A(config-if)#cable upstream <NUM> pre-equalization

where:


If you need to disable the pre-equalization adjustment, use the no cable upstream
pre-equalization command.
Forcing the Fragmentation of Large Upstream Packets

The cable upstream force-frag command is used as a traffic shaping tool. When a
cable modem sends a request to the cable interface for a large data grant that exceeds
the configured minislot threshold, the cable interface grants the cable modem the
configured minislot threshold, which forces the cable modem to make another data
grant request for the remaining data, thereby causing the data packets to be
fragmented by the cable modem.
Use the cable upstream force-frag command to force cable modems to fragment
large upstream packets in Interface Configuration mode:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} force-frag <0-255>
where:
0-255 is the threshold number of minislots without fragmentation for large data
grants.
Disabling an Upstream Port

Follow these steps to administratively shut down an upstream port:
1. Use the show interfaces cable command in Privileged EXEC mode to determine
if an upstream port is activated or deactivated:
MOT:7A#show interfaces cable <X/Y> upstream {<NUM> |
<X/Y>}
where:
upstream NUM is the upstream port number.
upstream X/Y is the upstream port and logical channel number (0-3).
MOT:7A(config)#interfaces cable <X/Y>

where:
3. Use the cable upstream shutdown command in Interface Configuration mode to
disable an upstream port:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} shutdown
where:
Configuring the Upstream Channel Descriptor

Follow the steps in this section to configure the upstream channel descriptor (UCD).
1. Use the cable upstream shutdown command in Interface Configuration mode to
disable the upstream channel:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} shutdown
where:
2. The default UCD message transmission interval is 1000 milliseconds. If you want
to adjust this parameter, use the cable ucd-interval command in Interface
Configuration mode to set the UCD message transmission interval:
MOT:7A(config-if)#cable ucd-interval <0-2000>
where:
0-2000 is the UCD message transmission interval in milliseconds.
3. Use the show cable ucd-interval command in Interface Configuration mode to
display the configured ucd interval value:
MOT:7A(config-if)#show cable ucd-interval
4. Use the no cable upstream shutdown command in Interface Configuration
mode to re-enable the upstream channel:
MOT:7A(config-if)#no cable upstream {<NUM> | <X/Y>}shutdown
where:


Limiting the Number of Voice Calls on an Upstream Channel

The Maximum Assigned Bandwidth (MAB) feature is used on the cable interface to
regulate the number of Voice-over-IP (VOIP) calls that are available on a particular
upstream channel for Unsolicited Grant Service (UGS) and Unsolicited Grant Service
with Activity Detection UGS-AD constant bit rate (CBR) data flows. A definitive
limit on the number of voice calls ensures that bandwidth resources are not overused
on an upstream channel.
The maximum number of calls is set to zero by default, which means that the
BSR accepts an unlimited number of voice calls. Use the cable upstream
max-calls command in Interface Configuration mode to configure the maximum
number of voice calls for an upstream channel:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} max-calls
<0-255>
where:
0-255 is the number of voice calls permitted on the upstream channel.
Use the no cable upstream max-calls command in Interface Configuration mode
to return the maximum number of voice calls to the default value, which is zero.
MOT:7A(config-if)#no cable upstream {<NUM> | <X/Y>} max-calls
<0-255>
where:
0-255 is the number of voice calls permitted on the upstream channel.

Enabling/Disabling CMTS Concatenation Capabilities

The CMTS concatenation feature on the BSR allows an MSO to globally enable or
disable concatenation for DOCSIS 1.0, 1.1, and 2.0 cable modems. Enabling the
concatenation feature allows the CMTS to do concatenation with participating cable
modems. This increases per-cable modem upstream throughput by combining
multiple MAC frames into one packet request. Cable modems request only one
DOCSIS timeslot on the upstream channel for multiple small packets, as opposed to
having to request an individual timeslot for each MAC frame.
CMTS concatenation also allows an MSO to disable CMTS concatenation. Disabling
CMTS concatenation would be useful in preventing potential concatenation-related
problems from occurring.
Use the cable upstream concatenation command, in Cable Interface Configuration
mode, to globally enable or disable CMTS concatenation capabilities, as follows:
MOT:7A(config-if)#cable upstream <NUM> concatenation
MOT:7A(config-if)#no cable upstream <NUM> concatenation
where:
Enabling/Disabling Concatenation for DOCSIS 1.0 Cable

Modems
Concatenation can be enabled or disabled specifically for DOCSIS 1.0 cable modems.
Use the cable concatenation command, in Cable Interface Configuration mode, to
enable or disable concatenation for DOCSIS 1.0 cable modems, as follows:
MOT:7A(config-if)#cable concatenation { docsis-1.0 }

MOT:7A(config-if)#no cable cable concatenation { docsis-1.0 }
where:
docsis-1.0 enables/disables concatenation for DOCSIS 1.0 cable modems only.

Note: Concatenation must be enabled globally with the cable upstream

concatenation command before any setting specified with the cable
concatenation command is valid. Once concatenation is enabled globally,
the cable concatenation command will enable or disable concatentation for
DOCSIS 1.0 cable modems only and concatenation will always be enabled
for DOCSIS 1.1 and DOCSIS 2.0 cable modems regardless of any setting
specified with this command.
Displaying Upstream Parameters

Use the show cable upstream command in Interface Configuration mode to show the
configured upstream parameters:
where:
X/Y is the upstream port and logical channel number (0-3)
the show cable upstream command.
Viewing Upstream Port Information

Use the show interfaces cable upstream command in all modes except User EXEC
mode to view upstream port statistics:
MOT:7A#show interfaces cable <X/Y> upstream [stats | signal-quality | spectrum
<5000000-42000000> <5000000-42000000>]
where:
upstream <NUM> is the upstream port number.
upstream <X/Y> is the upstream port and logical channel number (0-3).
stats provides upstream information in a statistical format.
signal-quality displays upstream port RF signal quality information.

spectrum displays upstream port spectrum information for power levels

comparing the upstream frequency to the number of microvolts and dBmV.
5000000-42000000 is the upstream start of the frequency range in Hertz (Hz).
5000000-42000000 is the upstream end of the frequency range in Hertz (Hz).
the show interfaces cable upstream command.

6
Configuring a DOCSIS 2.0
Upstream Logical Channel
Introduction
DOCSIS 2.0 increases physical upstream channel performance. It increases upstream
channel capacity and increases overall system tolerance to noise. The benefit of this is
improved spectral efficiency for the HFC network.
About DOCSIS 2.0

DOCSIS 2.0 capabilities include:
Advanced-Time Division Multiple Access (A-TDMA) encoding
Synchronous Code Division Multiple Access (S-CDMA) encoding
Higher symbol rates (5.12 MSym/sec - 6.4 MHz wide channel)
Higher order modulations
In addition to the QPSK and 16 QAM modulations available in DOCSIS 1.0 and
1.1, DOCSIS 2.0 adds: 8QAM, 32Qam and 64QAM.
Additional Forward Error Correction (FEC) (16 correctable bytes per codeword)
Additional burst protection through byte interleaving

Additional multipath protection (24 tap equalizer)
Logical Channels
For DOCSIS 1.0 and 1.1, a single channel was associated with each single physical
port on a BSR 64000 CMTS module. DOCSIS 2.0 introduces the ability to have
logical upstream channels on each single physical port. Logical channels allow
accommodation of DOCSIS 1.0 and 1.1 (legacy) cable modems in a DOCSIS 2.0
environment.
Channel Types
DOCSIS 2.0 allows operators to assign a channel type to each logical channel
associated with a physical port. A channel type allows (or restricts) the kind of cable
modem (DOCSIS 2.0, 1.1, or 1.0 compliant) that can operate over the logical channel
to which the channel type is assigned. Available channel types are listed in
Table Table :
Table Channel Types Supported by DOCSIS 2.0
Channel Type DOCSIS Specification Type Comment

TDMA (Time Division Multiple Type 1 DOCSIS 1.0 and 1.1 only channel
Access) type
MTDMA (Mixed TDMA and Type 2 DOCSIS 2.0, DOCSIS 1.1 and 1.0
A-TDMA) channel type
A-TDMA (Advanced TDMA) Type 3A DOCSIS 2.0 only channel type
S-CDMA (Synchronous Code Type 3S DOCSIS 2.0 only channel type
Division Multiple Access)

Release 5.3.1 Configuring a DOCSIS 2.0 Upstream Logical Channel
DOCSIS 2.0 Only Channel Types

The DOCSIS 2.0 only channel types, A-TDMA and S-CDMA, greatly enhance
upstream channel capacity, as shown in Table Table :
Table Features of DOCSIS 2.0 Logical Channel Types
DOCSIS 2.0 Channel Type Features

A-TDMA A-TDMA features include:
Increased pre-equalization and equalization from 8 to 24 taps
Increased Forward Error Correction capabilities from 10 to 16
bytes.
Increased channel width from 3.2 to 6.4 MHz
Expanded upstream channel bandwidth capacity from 10Mb to
30Mb
Increased modulation orders (QPSK, 8,16,32,64 QAM)
Byte interleaving
S-CDMA S-CDMA supports all the features of A-TDMA with the addition of:
CDMA spreading
Trellis Coded Modulation (TCM)
128 QAM with TCM
128 codes
Other Channel Types

To accommodate DOCSIS 1.0 and 1.1 cable modems in a DOCSIS 2.0 environment,
DOCSIS 2.0 also supports, in addition to A-TDMA and S-CDMA, two other logical
channel types:
TDMA (Time Division Multiple Access)
MTDMA (Mixed TDMA and A-TDMA)
Logical Channel Operation

For more than one logical channel to co-exist on the same physical CMTS port and
use the single frequency configured for that port, each logical channel type is
assigned a unique set of non-overlapping timeslots in which to communicate.

For example, the bandwidth scheduler that resides in the CMTS module allocates
S-CDMA bursts to S-CDMA timeslots, while allocating DOCSIS 1.x or A-TDMA
bursts to TDMA timeslots.
The allocation of timeslots to each logical channel is interleaved and assigned based
on usage. TDMA-based cable modems transmit data during TDMA assigned
timeslots while S-CDMA based cable modems transmit data during their own
timeslots. In addition, multiple S-CDMA cable modems may transmit on the same
upstream channel at the same time, up to the total capacity of the channel. TDMA
requires that each cable modem on a particular upstream channel be allocated
different intervals of transmission time.
Obtaining Detailed DOCSIS 2.0 Information

For detailed information, refer to the CableLabs DOCSIS 2.0 specification. This
specification is available at the CableLabs website: http://www.cablemodem.com/
downloads/specs/CM-SP-RFIv2.0-I07-041210.pdf
DOCSIS 2.0 and the BSR 64000

The ability to configure the BSR 64000 successfully for operation in a DOCSIS 2.0
environment is dependent upon the BSR 64000 hardware configuration, your
awareness of limitations imposed by the DOCSIS 2.0 specification itself, and the
software characteristics of the Motorola implementation of DOCSIS 2.0.
Refer to the following sections for more information:
BSR 64000 Hardware Support for DOCSIS 2.0
BSR 64000 Software Support for DOCSIS 2.0

BSR 64000 Hardware Support for DOCSIS 2.0

BSR 64000 CMTS module support for DOCSIS 2.0 is described in following table:
Table BSR 64000 CMTS Module Support for DOCSIS 2.0
DOCSIS 2.0 Logical Channel Channel Type

Module Support Support Support
2:8 Primary CMTS Yes Yes S-CDMA, A-TDMA,
(DOCSIS 2.0 2:8) MTDMA, TDMA
(DOCSIS 2.0, Euro-DOCSIS 2.0)
(Broadcom 3140)
2:8 Primary CMTS Yes No A-TDMA, MTDMA,
(DOCSIS 2:8) TDMA
(DOCSIS and Euro-DOCSIS)
(Broadcom 3138)
2:8 Standby CMTS Yes Yes S-CDMA, A-TDMA,
(DOCSIS 2.0 2:8 Standby) MTDMA, TDMA
(DOCSIS 2.0 and Euro-DOCSIS
2.0)
2:8 Standby CMTS Yes No A-TDMA, MTDMA,
(DOCSIS 2:8 Standby) TDMA
(DOCSIS and Euro-DOCSIS)
(Broadcom 3138)
For a DOCSIS 2.0 2:8 CMTS Module, four logical channels are available on each
physical upstream port. The kinds of channel types that can be assigned to each
logical channel on a single upstream physical port of a 2:8 DOCSIS 2.0 CMTS
Module are listed in Table Table .

Table Channel Types that can be Assigned to Logical Channels
Logical Channel Number Supported Channel Types

0 S-CDMA, A-TDMA, MTDMA,
TDMA
Physical
Upstream 1 S-CDMA, A-TDMA, MTDMA,
Port TDMA
2 A-TDMA, MTDMA, TDMA
3 A-TDMA, MTDMA, TDMA
BSR 64000 Software Support for DOCSIS 2.0

DOCSIS 2.0 is supported by BSR 64000 Release 4.1.0 and later as follows:
The default channel type for all Primary (or Standby) DOCSIS 2.0 2:8 CMTS
Module logical channels is TDMA.
The default channel type for all CMTS modules other than the Primary and
Standby DOCSIS 2.0 2:8 CMTS Module is TDMA.
The S-CDMA DOCSIS 2.0 channel type can be assigned only to logical channels
0 and 1.
TDMA and S-CDMA channel types can co-exist in the same MAC domain on a
2:8 DOCSIS 2.0 CMTS Module.
A 6.4 Mhz channel width can only be used with A-TDMA and S-CDMA channel
types.
The Motorola implementation of DOCSIS 2.0 offers 128QAM and 256QAM in
addition to those specified in the CableLabs DOCSIS 1.0, 1.1, and 2.0
specifications.
Note: Only the Primary (and Standby) 2:8 DOCSIS 2.0 CMTS Module
supports the configuration of logical channels.

DOCSIS 2.0 Logical Channel Configuration Task

Summary
A summary of tasks for configuring DOCSIS 2.0 is listed in below:
Table DOCSIS 2.0 Configuration Task Summary
Task Refer to...

1. Confirm that your BSR 64000 hardware Determining the 2:8 CMTS Module
configuration supports DOCSIS 2.0 Type
Determining the DOCSIS Version
of a Slot
2. Enable Spectrum Power Density Configuring Spectrum Power
Maintenance Density Maintenance for a Logical
Channel
3. Assign a channel type to a logical channel Configuring the Channel Type
4. For logical channels assigned an Additional S-CDMA Logical
S-CDMA channel type, configure Channel Configurations
additional S-CDMA related parameters
5. Review the configuration Displaying the Upstream Logical
Channel Configuration
About Upstream Channel Commands

When using the following cable upstream and related show commands, only the
NUM option displays for BCM 3138-based 2:8 CMTS modules. Both the NUM and
X/Y arguments display for BCM 3140-based DOCSIS 2.0 2:8 CMTS modules. These
commands are applicable to both an upstream port or upstream port and logical
channel.
channel-type modulation-profile
data-backoff range-backoff
force-frag show cable upstream
map-interval show interfaces cable upstream
max-calls trap-enable-cmts

minislot-size trap-enable-if
shutdown trap-enable-rdn
When using the following cable upstream commands, both the NUM and X/Y
arguments display for a BCM 3140-based DOCSIS 2.0 2:8 CMTS modules. These
commands are only applicable for an upstream port and logical channel and will only
be available through the X/Y argument.
active-codes iuc11-grant-size
codes-minislot maintain-power-density
hopping-seed spread-interval
When using the following cable upstream commands, only the NUM option displays
for BCM 3138-based 2:8 CMTS modules. Both the NUM and X/Y arguments display
for a BCM 3140-based DOCSIS 2.0 2:8 CMTS modules. These commands are only
applicable for an upstream port will only be available through the NUM argument.
channel-width physical-delay
concatenation power-level
description pre-equalization
frequency range-forced-continue
ingress-canceller range-power-override
invited-range-interval rate-limit
loadbalance-group snr-offset
modem-ranging-delay spectrum-group

Note: To determine which 2:8 CMTS module is installed in the BSR 64000,
refer to Determining the 2:8 CMTS Module Type.
For additional information on any of the above commands, refer to Chapter

13 of the BSR 64000 Command Reference Guide.
Determining the 2:8 CMTS Module Type

Use the show chassis status command, in all modes except User EXEC, to determine
the type of 2:8 CMTS module that is installed in the BSR 64000 chassis. An installed
2:8 DOCSIS CMTS module will return a type and subtype of 2x8 and an installed
2:8 DOCSIS 2.0 CMTS module will return a type and subtype of 2x8 (2.0). The
following is typical screen output from the show chassis status command displaying
the two 2:8 CMTS module type:

Slot Type Sub Red State RM IO UpTime LastUpTime Success Failure

0 CMTS 2X8 - RUN x x 19:38:20 1 1
1 - - - - 0 0
2 - - - x 0 0
3 CMTS 2x8(2.0) 6 RUN x x 19:38:27 1 1
4 - - - - 0 0
5 - - - - 0 0
6 CMTS 2x8(2.0) - stby x x 19:38:28 0 1
7 SRM 8 RUN x x 19:49:11 0 0
8 SRM - stby x - 19:46:50 1 1
9 - - - - 0 0
10 CMTS 2x8 - RUN x - 19:39:58 1 1
11 - - - - 0 0
12 - - - - 0 0
13 - - - - 0 0
14 CMTS 2X8 - RUN x - 19:37:56 1 1
15 HSIM ETH8 - RUN x x 19:47:03 1 1
2:8 DOCSIS CMTS module 2:8 DOCSIS 2.0 CMTS module
Determining the DOCSIS Version of a Slot

Use the show docsis-version command, in all modes except User EXEC, to
determine the supported DOCSIS version of a slot in the BSR 64000 chassis, as show
below:
MOT:7A#show docsis-version <0-15>
where:
0-15 is the chassis slot number.
Returned values are DOCSIS 1.X (DOCSIS 1.0 or DOCSIS 1.1) and DOCSIS 2.0.
The DOCSIS version information allows you to determine the channel type that a
BSR chassis slot supports and the subsequent configuration procedures.

Configuring the Channel Type

The cable upstream channel-type command allows you to specify the channel type
for the default upstream channel (0) or specify the channel type for up to four logical
channels (0-3).
Follow this procedure to configure the channel type for an upstream channel:
where:
2. Use the cable upstream channel-type command in Cable Interface
Configuration mode to configure an upstream channel type, as shown below:
MOT:7A(config-if)#cable upstream {<NUM> | <X/Y>} channel-type
{tdma | A-TDMA | mtdma | S-CDMA}
where:
NUM is the upstream port number and default channel number 0.
X/Y the upstream port number and logical channel number (0-3).
tdma is a DOCSIS 1.1 channel type.
A-TDMA is a DOCSIS 2.0 channel type.
mtdma is a DOCSIS 1.1 or DOCSIS 2.0 TDMA channel type.
S-CDMA is a DOCSIS 2.0 channel type only used for logical channel
configurations.

Note: The channel-type command is applicable to the 2:8 and 2:8

(2.0)CMTS modules only. To determine which CMTS modules are installed in
the BSR 64000, use the show chassis status command.
It is unnecessary to configure and enable multiple logical channels with the

same channel types. The total capacity of the physical channel will not be
enhanced by enabling multiple logical channels. However, it is reasonable to
assign unique modulation profile to multiple logical channels of the same type
for RF impairment investigation.
Note: If you are configuring an S-CDMA logical channel, refer to Additional

S-CDMA Logical Channel Configurations.
3. Use the show interfaces cable configuration command, in all modes except
User EXEC, or show cable upstream command, in Cable Interface
Configuration mode, to view the channel type configuration, as shown below:
MOT:7A(config-if)#show interfaces cable <X/Y> configuration
where:
\MOT:7A(config-if)#show cable upstream {<NUM> | <X/Y>}
where:
The following is screen output from the show interfaces cable configuration
command which displays the channel type configuration. In this example, four
logical channels with an MTDMA channel type have been configured on
upstream port 4.

Invited Ranging Attempts: 16

--US PORT 4-- Upstream Port Number
Max Tx Timing Offset: 0
Forced Continue Ranging: 0
Ranging Interval: 10000(ms)
Power Offset Threshold: 24
Power Desired: 16384(linear)
--CHAN 0--
Channel Type: mtdma
Rx Pwr Lvl Config: 0(10th of dB)
Max Power Adj: 8
AdjCtrlFlag: 8
--CHAN 1--
Channel Type: mtdma
Max Power Adj: 8 Upstream Logical
AdjCtrlFlag: 8 Channel Number
--CHAN 2-- and Channel Type
Channel Type: mtdma
Max Power Adj: 8
AdjCtrlFlag: 8
--CHAN 3--
Channel Type: mtdma
Max Power Adj: 8
AdjCtrlFlag: 8

Configuring Spectrum Power Density Maintenance

for a Logical Channel
The Maintain Power Spectral Density feature can be enabled for each logical channel.
If Maintain Power Spectral Density is enabled and the modulation rate is different
from the previous UCD, the cable modem must change its transmit power level to
keep the power spectral density as close as possible to what it was prior to the
modulation rate change. If Maintain Power Spectral Density is disabled, the cable
modem maintains the same power level that it was using prior to the modulation rate
change.
Use the cable upstream maintain-power-density on command, in Cable Interface
Configuration mode, to enable the Maintain Power Spectral Density feature, as shown
below:
MOT:7A(config-if)#cable upstream <X/Y> maintain-power-density on
where:
Additional S-CDMA Logical Channel

Configurations
The S-CDMA logical channel type introduces additional complexities in the timing
and synchronization of upstream scheduling. The upstream channel is still scheduled
using intervals described in terms of minislots.
In S-CDMA channel types, determining the minislot size in time ticks is no longer
used. S-CDMA groups data and codes into S-CDMA frames. A minislot in S-CMDA
is defined as an interval of time and a code (or combination of codes). Mini-slots are
mapped to frames. S-CDMA uses the concepts of spreading intervals, the number of
allowed active codes, and the number of active codes per mini-slot to determine
scheduling intervals per S-CDMA frame. A spreading interval is the time it takes to
send one symbol per code across all 128 possible codes in an S-CDMA frame. The
time duration of an S-CDMA frame is determined by a configurable number of
spreading intervals and the signaling rate. The number of codes per mini-slot is also
configurable as is the number of codes used.

The S-CDMA channel type allows multiple modems to transmit on the same
upstream channel at the same time. S-CDMA spreads the signals transmitted based on
the particular code used so that messages will not interfere with each other. The
coding has the effect of creating channels within the same spectrum. With S-CDMA,
more than one mini-slot can occupy the same place in time in the upstream bandwidth
allocation. Mini-slots are separated by the code(s) used.
The existing time stamp mechanism is not sufficient for synchronizing these new
frames so an additional level of synchronization is added called a timestamp snapshot.
This information contains the frame number, mini-slot number, and time stamp.
Timestamp snapshot information is conveyed in the SYNC and UCD messages.
The following additional configuration procedures are required for an S-CDMA
logical channel:
Configuring S-CDMA Active Codes
Configuring S-CDMA Codes Per Minislot
Configuring the S-CDMA Hopping Seed
Configuring the S-CDMA Spreading Interval
Configuring S-CDMA Active Codes

S-CDMA channels support the configuration of the number of active codes allowed
for an S-CDMA channel type. The active codes value must be a non prime number.
Increasing the number of allowed active codes provides more transmission channel
capacity. Reducing the number of active codes takes advantage of the S-CDMA
spreader processing gain at the expense of channel capacity.
Use the cable upstream active codes command, in Cable Interface Configuration
mode, to specify the number of active codes allowed for an S-CDMA channel type, as
shown below:
MOT:7A(config-if)#cable upstream <X/Y> active codes <64-128>
where:
64-128 the total number of allowed active codes.

Configuring S-CDMA Codes Per Minislot

S-CDMA channels support the configuration of the number of active codes allowed
for each minislot. The number active codes allowed for each minislot determines the
minislot capacity and sets the granularity of the upstream grants.
Use the cable upstream codes-minislot command, in Cable Interface Configuration
mode for the S-CDMA channel, to specify the number of active codes per minislot, as
shown below:
MOT:7A(config-if)#cable upstream <X/Y> codes-minislot <2-32>
where:
2-32 is the number of codes allowed per minislot.
Configuring the S-CDMA Hopping Seed

Use the cable upstream hopping-seed command, in Cable Interface Configuration
mode, to specify the 15 bit S-CDMA hopping seed value used for the code hopping
sequence initialization, as shown below:
MOT:7A(config-if)#cable upstream <X/Y> hopping-seed <0-32767>
where:
0-32767 is the hopping seed value (0 disables code hopping)
Note: The logical channel must be disabled to specify a new hopping seed
value.
Configuring the S-CDMA Spreading Interval

S-CDMA channels support the configuration of spreading interval. A spreading
interval is the time that it takes to transmit one symbol per code across all 128 codes
in an S-CDMA frame. The time duration of an S-CDMA frame is determined by a
configurable number of spreading intervals and the signaling rate.
Use the cable upstream spread-interval command, in Cable Interface Configuration
mode, to specify the spreading interval for an S-CDMA frame, as shown below:

MOT:7A(config-if)#cable upstream <X/Y> spread-interval <1-32>

where:
1-32 is the spreading interval value.
Displaying the Upstream Logical Channel

Configuration
Use the show cable upstream command, in Cable Interface Configuration mode, to
display the complete configuration of an upstream logical channel, as shown below:
where:
The following is screen output from the show cable upstream command which
displays a complete channel configuration. Configuration parameters introduced with
DOCSIS 2.0 highlighted.

ifIndex: 118161
description:
rng_back_st: 0
rng_back_en: 4
data_back_st: 2
data_back_en: 8
powerLevel: 0 (10th of dB)
slotSize: 4
force-frag: 0
map-interval: 4000 (usec)
pre-equalization: 0
invited-range-interval: 10000 (msec)
range-power-override: false
concatenation: true
rate-limit: 0
modulation-profile: 1
max-calls: 0
Spectrum Group:
Channel type: tdma
S-CDMA active codes: 0
S-CDMA codes per slot: 0
S-CDMA spreading intrvl: 0
S-CDMA hopping seed: 0
Ingress canceller state: disabled
Ingress canceller idle interval: 320 (symbols)
Ingress canceller idle frequency: 5
Maintain power spectrum density: off
Modem ranging delay: 250 (usec)
IUC 11 grant size: 0

7
Using RF Sentry on the 2:8
CMTS Resource Module
Introduction
The BSR 64000 2:8 CMTS module provides an RF Sentry upstream Spectrum
analysis tool. The RF Sentry tool is used to measure either power levels or signal to
noise ratios of each of the eight upstream ports. The RF Sentry works by means of the
Fast Fourier Transform (FFT) algorithm for power level measurement or Signal to
Noise Ratio (SNR) measurement.
Power level measurement is done by means of the Fast Fourier Transform (FFT)
algorithm. FFT transforms a discrete signal in a time domain to a power level in a
frequency domain. Power level measurement is done through a built-in FFT
processor.
SNR measurement is done by exchanging data between a reference modem and
the CMTS. A reference modem is a registered cable modem that is selected to
send an upstream traffic/burst used to measure the SNR on that upstream.

The RF Sentry has its own RF path which can be switched between the RF paths of
the eight upstream ports. The RF Sentry uses a tap-in mode to access the RF path.
Both power level and Signal to Noise Ratio measurement is done within the
Broadcom chip set (BCM3138/BCM3140) on the 2x8 CMTS module.
Note: In a DOCSIS 2.0 environment, RF Sentry power level or SNR

measurement is only supported on logical channel 0. S-CDMA mode is also
not supported.
Power Level Measurement

The FFT processor measures the power levels of a signal in one of the upstream
receiver ports that spans a range of frequencies. Power level measurement provides an
informational big picture of the signal in a particular upstream port. The power
level measurement data can then be displayed to determine power level estimates at
different frequencies across the Spectrum over time. This information can then be
used for upstream Spectrum trend analysis.
Note: Running any FFT commands can impact voice performance.
This section describes the following tasks:

Configuring FFT
Configuring the FFT Processor
Displaying the FFT Processor Configuration
Starting FFT Power Level Measurement
Storing FFT Power Level Measurement Data
Displaying FFT Power Level Measurement Data
Configuring FFT
The fft setup command can be used to configure the FFT processor on the BCM3138/
BCM3140 chip set or to display the current FFT processor configuration.

Release 5.3.1 Using RF Sentry on the 2:8 CMTS Resource Module
Configuring the FFT Processor

Use the fft setup command, in Privileged EXEC mode, to configure the FFT
processor, as follows:
MOT:7A#fft setup <Slot/Port> [sample {<256-2048>} mode {Tap-in} window
{blackman | blackman-harris | hamming | hanning | rectangular}]
where:
Slot/Port is the operational 2x8 CMTS slot number and a valid upstream port
number.
sample 256-2048 is the number of samples of the power level measurement. The
default is 2048.
mode Tap-in is the RF Sentrys operational mode
window is the window coefficient to shape the output of the power level
measurement (rectangular, hamming, hanning, blackman, or
blackman-harris). The default is rectangular.
Displaying the FFT Processor Configuration

Use the fft setup <Slot/Port> command, without any additional arguments, to display
the current FFT processor configuration for a particular port on a particular CMTS
module, as follows:.
MOT:7A#fft setup <Slot/Port>
where:
Slot/Port is the operational CMTS slot number and a valid upstream port number.
Starting FFT Power Level Measurement

Use the fft start command to initiate power level measurement using the FFT
algorithm via the RF Sentry.
MOT:7A#fft start <Slot/Port> [sample {<256-2048>}] [mode {Tap-in}] [window
{rectangular | hamming | hanning | blackman | blackman-harris}]
where:
Slot/Port is the operational 2x8 CMTS slot number and a valid upstream port
number.

sample 256-2048 is the number of samples of the power level measurement. The
default is 2048,
mode Tap-in is the RF Sentrys operational mode
window is the window coefficient to shape the output of the power level
measurement (rectangular, hamming, hanning, blackman, or
blackman-harris). The default is rectangular.
Note: The sample, mode, and window arguments are optional with the fft
start command but can be used to override the current FFT processor
configuration specified with the fft setup command and initiate power level
measurement with a new FFT processor configuration.
Storing FFT Power Level Measurement Data

The fft store command saves the latest FFT power level measurement data for a
CMTS module to a file system. The user specifies a particular slot and port, the file
system (NVRAM or Flash), and a file name without any extension to be used to store
the FFT power level measurement data. An extension of ".fft" will be automatically
added to the file name.
Use the fft store command to save the FFT power level measurement data, as follows:
MOT:7A#fft store <Slot/Port> {nvram: <WORD> | flash: <WORD>}
where:
Slot/Port is the operational 2x8 CMTS slot number and valid upstream port
number.
nvram: stores the power level measurement data to the NVRAM file system.
flash: stores the power level measurement data to the flash file system
WORD is the power level measurement data filename with a limit of 20
characters excluding the ".fft" filename extension.
Displaying FFT Power Level Measurement Data

The fft display command is used to display FFT power level measurement data. The
command provides the following FFT data retrieval options:
Retrieving FFT Data from an Operational CMTS Module
Retrieving FFT Data from a File System

The FFT data can be processed into a table or graph format and then displayed to a
console or telnet session.
Retrieving FFT Data from an Operational CMTS Module

Power level measurement data can be directly retrieved from an operational CMTS
module. Use the fft display command, in Privileged EXEC mode, to retrieve FFT
data from a CMTS module, as follows:
MOT:7A#fft display {<Slot/Port>} startfreq {<0-81920000>} endfreq
{<0-81920000>} {table | graph}
where:
Slot/Port is the operational 2x8 CMTS slot number and valid upstream port
number.
startfreq 0-81920000 is the start of the frequency range (0 Hz - 81.92 MHz).
endfreq 0-81920000 is the end of the frequency range (0 Hz - 81.92 MHz).
table | graph specifies a table or graph display format.
Retrieving FFT Data from a File System

Power level measurement data can be retrieved from a file system if a user has saved
the latest FFT power level measurement data to a file system with the fft store
command. See Storing FFT Power Level Measurement Data.
Use the fft display command, in Privileged EXEC mode, to retrieve FFT power level
measurement data from a file system, as follows:
MOT:7A# fft display {nvram: <WORD> | flash: <WORD>} startfreq
{<0-81920000>} endfreq {<0-81920000>} {table | graph}
where:
nvram: retrieves the power level measurement data from the NVRAM file
system.
flash: retrieves the power level measurement data from the Flash file system.
WORD is the power level measurement data filename - limit of 20 characters
excluding the ".fft" filename extension.
startfreq 0-81920000 is the start of the frequency range (0 Hz - 81.92 MHz).
endfreq 0-81920000 is the end of the frequency range (0 Hz - 81.92 MHz).
table | graph specifies a table or graph display format.

Signal to Noise Ratio Measurement

Signal to Noise Ratio (SNR) measurements using the RF Sentry are performed on a
specified idle Spectrum. The acquired SNR data can be displayed or stored in a file
for on demand diagnostic purposes.
Configuring SNR Measurement
Displaying the SNR Configuration
Starting SNR Measurement
Storing SNR Measurement Data
Displaying SNR Measurement Data
Configuring an SNR Offset
Configuring SNR Measurement

The snr setup command can be used to configure the SNR measurement on the
BCM3138/BCM3140 chip set. Use the snr setup command, in Privileged EXEC
mode, to configure SNR measurement, as follows:
MOT:7A#snr setup {<NUM>{<NUM>}} {<5000000-42000000> |
<5000000-65000000> | <5000000-55000000>} {<5000000-42000000> |
<5000000-65000000> | <5000000-55000000>} {1600000 | 200000 | 3200000 |
400000 | 6400000 | 800000} [equalization {auto | off | on}| ingress-cancel {auto |
off | on} | modulation-type {16qam | auto | qpsk}]
where:
NUM is the operational 2x8 CMTS slot number.
NUM is a valid upstream port number.
5000000-42000000 is the North America standard start frequency in Hz.
5000000-42000000 is the North America standard end frequency in Hz.
5000000-65000000 is the EURODOCSIS standard start frequency in Hz.
5000000-65000000 is the EURODOCSIS standard start frequency in Hz.
5000000-55000000 is the J-DOCSIS standard start frequency in Hz.
5000000-55000000 is the J-DOCSIS standard end frequency in Hz.

Note: Depending on the configuration of the installed 2:8 CMTS Resource

Module, the start and end frequencies will reflect the North American
DOCSIS, EURODOCSIS, or J-DOCSIS standards
1600000 is the channel width 1600 kHz.

200000 is the channel width in 200 kHz.
equalization auto evaluates the SNR with and without equalization.
equalization off evaluates the SNR without equalization.
equalization on evaluates the SNR with equalization.
Note: Equalization settings on the snr setup command is for POST

equalization.
ingress-cancel auto evaluates the SNR with and without ingress cancellation.
ingress-cancel off evaluates the SNR without ingress cancellation.
ingress-cancel on evaluates the SNR with ingress cancellation.
modulation-type 16qam evaluates the SNR for 16qam mode.
modulation-type auto evaluates the SNR for both QPSK and 16QAM modes.
modulation-type qpsk evaluates the SNR for QPSK mode.

Configuring an Automatically Repeated SNR Test

SNR measurement tests to perform SNR measurements for a specified number of
times on one particular frequency. Configuring a automatically repeated SNR
measurement test involves specifying a loop count and a center frequency. This type
of SNR measurement test is used for diagnostic purposes.
Use the snr loop command to configure an automatically repeated SNR measurement
test, as shown below:
MOT:7A#snr loop {<NUM>} {<NUM>}{<NUM>}{<NUM>}{<frequency>}
{1600000 | 200000 | 3200000 | 400000 | 6400000 | 800000} [<mac> | equalization
{off | on} | ingress-cancel {off | on} | modulation-type {16qam | qpsk}]
where:
NUM is the slot number of an operational 2:8 CMTS module (0-5, 9-15).
NUM is a valid upstream port number (0-7).
NUM is the number SNR measurement repetitions (1-100).
NUM is a ranging pattern number used to look up a certain pattern to be used for
SNR measurement.
frequency is the particular frequency to perform SNR measurements on.
mac is he MAC address, in the form of xxxx.xxxx.xxxx, of a device to perform
SNR measurements on.
equalization auto evaluates the SNR with and without equalization.
equalization off evaluates the SNR without equalization.

equalization on evaluates the SNR with equalization.
Note: Equalization settings on the snr loop command is for POST

equalization.
ingress-cancel auto evaluates the SNR with and without ingress cancellation.
ingress-cancel off evaluates the SNR without ingress cancellation.
ingress-cancel on evaluates the SNR with ingress cancellation.
modulation-type 16qam evaluates the SNR for 16qam mode.
modulation-type auto evaluates the SNR for both QPSK and 16QAM modes.
modulation-type qpsk evaluates the SNR for QPSK mode.
Displaying the SNR Configuration

Use the snr setup-get command, without any additional arguments, to display the
current SNR measurement configuration for a particular port or all ports on a
particular CMTS module, as follows:.
MOT:7A#snr setup-get [<NUM> [<NUM>]]
where:
NUM is the slot number of the 2x8 CMTS module.
Starting SNR Measurement

Use the snr start command to initiate SNR via the RF Sentry.
MOT:7A#snr start {<NUM>{<NUM>}} [<mac>]
where:
mac the MAC address of the reference modem in the form of
xxxx.xxxx.xxxx

Storing SNR Measurement Data

The snr store command saves the latest SNR measurement data for a CMTS module
to a file system. The user specifies a particular slot and port, the file system (NVRAM
or Flash), and a file name without any extension to be used to store the SNR
measurement data. An extension of ".snr" will be automatically added to the file
name.
Note: The snr start command must first be used to initiate SNR
measurement before the snr store command can be used to store SNR
measurement data.
Use the snr store command to save the SNR measurement data, as follows:
MOT:7A#snr store {<NUM>{<NUM>}} {flash:<filename> <WORD>|
nvram:<filename> <WORD>}
where:
flash:<filename> stores the SNR measurement data to the Flash file system.
nvram:<filename> stores the SNR measurement data to the NVRAM file
system.
WORD is the SNR measurement data filename with a limit of 20 characters
excluding the ".snr" filename extension.
Displaying SNR Measurement Data

The snr display command is used to display SNR measurement data. The command
provides the following SNR data retrieval options:
Retrieving SNR Data from an Operational CMTS Module
Retrieving SNR Data from a File System
The SNR data can be displayed to a console or telnet session.

Retrieving SNR Data from an Operational CMTS Module

SNR measurement data can be directly retrieved from an operational CMTS module.
Use the snr display command, in Privileged EXEC mode, to retrieve SNR data from
a CMTS module, as follows:
MOT:7A#snr display {<NUM>{<NUM>}
where:
NUM is the slot number of the 2:8 CMTS module.
Retrieving SNR Data from a File System

SNR measurement data can be retrieved from a file system if a user has saved the
latest SNR measurement data to a file system with the snr store command. See
Storing SNR Measurement Data.
Use the snr display command, in Privileged EXEC mode, to retrieve SNR
measurement data from a file system, as follows:
MOT:7A#snr display {flash:<filename> <WORD> | nvram:<filename>
<WORD>}
where:
nvram:<filename> retrieves the SNR measurement data from the NVRAM file
system.
flash:<filename> retrieves the SNR measurement data from the Flash file
system.
WORD is the SNR measurement data filename - limit of 20 characters excluding
the ".snr" filename extension.

Configuring an SNR Offset

The cable upstream snr-offset command configures the display of an SNR value
with an offset. The offset can be configured for each upstream port up to a value of
100 (10 dB) in 10 (1 dB) increments. The offset value will be added to the SNR value
when it is displayed with the show controllers and show interfaces cable upstream
signal-quality CLI commands and through SNMP. The offset value will not be added
to the actual SNR reading that is used by critical tasks such as Spectrum Management.
Use the cable upstream snr-offset command, in Interface Configuration mode, to
configure an SNR offset, as follows:
MOT:7A(config-if)#cable upstream <NUM> snr-offset [10 | 20 | 30 | 40 | 50 |
60 | 70 | 80 | 90 | 100]
where:
10 | 20 | 30 | 40 | 50 | 60 | 70 | 80 | 90 | 100 is the offset value in increments of 10
(1 dB).

7
Managing Cable Modems
Introduction
This chapter describes managing cable modems and includes the following
procedures and tasks:
Configuring Network Parameters for Cable Modems
Configuring Baseline Privacy
Using Flap Lists
Pinging a Cable Modem at the MAC Layer
Resetting the Cable Modem
Clearing Cable Modem Counters
Viewing Cable Modem Information
Release 5.3.1 7-1

Configuring Network Parameters for Cable

Modems
Configuring cable modem network parameters involves the following tasks:
Enabling the Cable Modem Aging Timer
Removing Cable Modems from the Offline List
Setting the Insertion Interval for Cable Modems
Setting the Synchronization Interval
Setting Cable Modem Authentication Parameters
Denying Access to a Cable Modem
Setting the Maximum Number of Hosts
Enabling the Cable Modem Aging Timer

The cable modem aging timer feature is used to automatically remove off-line cable
modems from the network after a configured time period. The cable modem aging
timer is disabled by default.
Use the cable modem-aging-timer command in Global Configuration mode to set
and enable the cable modem aging timer:
MOT:7A(config)#cable modem-aging-timer <10-30240>
where:
10-30240 is the cable modem Aging Timer number in minutes (10 minutes to 21
days).
Use the cable modem-aging-timer off command to disable the aging timer.
Removing Cable Modems from the Offline List

The cable modem aging timer function causes cable modems to be removed after a
configurable timeout period. However, the clear cable modem offline command is
useful for removing cable modem(s) before its configured aging timeout period or if
the cable modem aging timer function is not used. Refer to Enabling the Cable
Modem Aging Timer for more information on enabling the cable modem aging timer
feature.
Use the following options to remove cable modems from the offline list:

Release 5.3.1 Managing Cable Modems
Use the clear cable modem offline command to remove all offline cable modems
from the offline list:
MOT:7A:7A#clear cable modem offline
Use the clear cable modem offline command to remove a specific offline cable
modem from the offline list or all cable modems from a specific CMTS slot and
port:
MOT:7A:7A#clear cable modem offline {<mac> | <X/Y>}
where:
Use the clear cable modem offline slot command to remove all offline cable
modems in a single CMTS from the offline list:
MOT:7A:7A#clear cable modem offline slot <NUM>]
where:
NUM is the slot number of a CMTS module from 0-5 and 9-14.
Setting the Insertion Interval for Cable Modems

The insertion interval is the fixed time period available for cable modem initial
channel request. The default insertion interval is 20.
1. Use the cable insert-interval command in Interface Configuration mode to set
the insertion interval for cable modem initial channel request:
Note: Ensure that the upstream port is down before setting the insertion
interval.
MOT:7A(config-if)#cable insert-interval {<0-200>}
where:
0-200 is the insertion interval in hundredths of a second.

2. Use the no cable insertion-interval command in Interface Configuration mode

to return the default insertion interval:
MOT:7A(config-if)#no cable insert-interval {<0-200>}
where:
0-200 is the insertion interval in hundredths of a second.
3. Use the show cable insert-interval command in Interface Configuration mode to
view the insertion interval:
MOT:7A(config-if)#show cable insert-interval
Setting the Synchronization Interval

The synchronization message interval is the interval between successive
synchronization message transmissions from the cable interface to the cable modems.
Follow the steps in this section to set and verify the synchronization interval:
1. Use the cable sync-interval command in Interface Configuration mode to set the
synchronization message interval value:
Note: Ensure that the interface is down before setting the synchronization
message interval.
MOT:7A(config-if)#cable sync-interval {0-200}

where:
0-200 is the synchronization interval set in milliseconds (msecs).
2. Use the show running-config command to verify the synchronization message
interval setting. Until an interval is set, the no sync interval entry appears in the
display.
Use the no cable sync-interval command in Interface Configuration mode if you
need to reset the default synchronization message interval:
MOT:7A(config-if)#no cable sync-interval
3. Use the show cable sync-interval command in Interface Configuration mode to
display the synchronization message interval:

MOT:7A(config-if)#show cable sync-interval

Use the no cable sync-interval command in Interface Configuration mode to
reset the default synchronization message interval:
MOT:7A(config-if)#no cable sync-interval <1-200>
Setting Cable Modem Authentication Parameters

The default authentication parameters are enabled, but have a null value by default.
Use the information in the following sections to set authentication parameters on the
cable interface and the cable modems to ensure security on the HFC network.
Note: The unencrypted "authentication string" on the BSR can be up to 246

characters. The encrypted "authentication string" on the BSR can be up to
508 characters.
1. Use one the following two options to configure cable modem authentication
parameters so that all cable modems return a known text string to register with the
cable interface for network access:
Caution: Ensure that the authentication string or hexadecimal key in the

cable modem configuration file matches the authentication string or
hexadecimal key configured on the cable interface. Cable modems cannot
register with the cable interface if the authentication parameters do not
match.
If you want to activate cable modem authentication so that all cable modems
return an unencrypted text string to register with the cable interface for
network access, issue the cable shared-secret 0 command in Global
Configuration mode:
MOT:7A(config)#cable shared-secret 0 < string>
where:
0 specifies that an unencrypted authentication text string follows.
string is an alphanumeric text authentication string. The authentication string
must enclosed with double quotes if the string contains spaces. The "%" and
"!" characters must not be used.

Automatic encryption on the BSR is disabled by default. If you want to

activate cable modem authentication so that all cable modems return an
encrypted key and register with the cable interface for network access, the
service password-encryption command must be configured.
2. Use the show running-config command in Global Configuration mode to
determine if the automatic encryption function is enabled on the BSR and if cable
modem authentication is activated or deactivated on a cable interface:
Note: The show running-config command output identifies the system

password with the number 0 if it is unencrypted. If the system password is
encrypted, it is identified with the number 7. If cable modem authentication is
active, cable modem authentication information does not appear in the
display
MOT:7A(config)#show running-config interface cable <X/Y>

where:
interface displays running configuration information on all interfaces or a
specific interface.
cable X/Y is the slot and MAC Domain number of the CMTS module.
The configuration parameters that you have set should appear in the show
running-config command output.

Restoring Previously Defined Authentication Parameters

Use the no cable shared-secret command in Interface Configuration mode to restore
the previously defined authentication parameters:
MOT:7A(config)#no cable shared-secret [< string> | <key>]
where:
string is an alphanumeric text string.
key is the shared secret key, expressed in hexadecimal notation, for example,
0x434F5453.
Denying Access to a Cable Modem

Use the cable modem deny command, in Global Configuration mode, to remove a
specified cable modem from the network and deny it future entry:
MOT:7A(config)#cable modem deny <mac>
where:
Use the no cable modem deny command to remove the restriction from the specified
cable modem:
MOT:7A(config)#no cable modem deny <mac>
where:
Setting the Maximum Number of Hosts

Use the cable modem max-hosts command to set the number of CPE hosts that can
connect to a cable modem on the HFC subnetwork.
1. Use the cable modem max-hosts command. in Privileged EXEC Mode. to
specify the maximum number of CPE hosts that can attach to a particular cable
modem:
MOT:7A#cable modem [<mac> | <prefix>] max-hosts <0-32>
where:
mac is the cable modem MAC address.

0-32 is the maximum number of hosts.

2. Use the cable modem max-hosts-all command, in Global Configuration Mod.e
to specify the maximum number of CPE hosts that can attach to a all cable
modems:
MOT:7A(config)#cable modem max-hosts-all <0-32>
where:
0-32 is the maximum number of hosts.
3. Use the show cable modem hosts command to verify the maximum number of
hosts setting:
MOT:7A#show cable modem {<mac> | <prefix>} hosts
where:
The screen displays the current number of hosts connected to the cable modem,
the maximum number of hosts allowed for the cable modem, and the host CPE IP
addresses behind the cable modem.

Configuring Baseline Privacy

This section contains the tasks to configure Baseline Privacy (BPI). You must
configure BPI to encrypt upstream and downstream data on an HFC network. BPI is
activated by default and, in most cases, the BPI parameter default values are
satisfactory. The optional tasks described in this section involve some parameters you
may choose to change. If a parameter default is satisfactory, you can ignore its
associated task.
You can set the Traffic Encryption Key (TEK) and Authorization Key (AK) for BPI.
The encryption is based on 40-bit or 56-bit Data Encryption Standard (DES)
algorithms.
You can set the TEK to expire based on a grace-time value or a lifetime value. A
grace-time key assigns a temporary key to a cable modem to access the network. A
lifetime key assigns a more permanent key to a cable modem. Each cable modem that
has an assigned lifetime key requests a new lifetime key from the cable interface
before the current key expires.
Note: The configuration and activation of BPI depend on the cable operator
physical plant.
Configuring BPI involves the following tasks:

Setting TEK Privacy
Setting Authorization Key Values
Using Flap Lists
The following table describes the BPI parameters.
Table BPI Parameters
Parameter Identification Default Value

AK grace-time Temporary AK assigned to the 600 seconds 300 to 1,800
cable modem seconds
AK lifetime More permanent AK assigned to 604,800 1 to 6,048,000
the cable modem after grace-time seconds seconds
AK expires

Table BPI Parameters
Parameter Identification Default Value

TEK grace-time Temporary traffic key assigned to 600 seconds 300 to 1,800
cable modem seconds
TEK lifetime More permanent TEK assigned to 43,200 seconds 1,800 to
cable modem after grace-time 6,048,000
TEK expires seconds
Setting TEK Privacy

The TEK is assigned to a cable modem when its Key Encryption Key is established
during the cable modem registration process. The TEK encrypts data traffic between
the cable modem and the cable interface. The cable interface assigns a temporary
grace-time TEK to a cable modem so the cable modem can access the network. When
the grace-time TEK expires, the cable modem must renew its grace-time TEK with a
lifetime TEK. The cable interface assigns a more permanent lifetime TEK to a cable
modem when the grace-time TEK expires.
1. Use the interface cable command to enter Cable Interface Configuration mode
from Global Configuration mode to configure the cable interface:
where:
2. Use the cable privacy tek life-time command in Cable Interface Configuration
mode to configure the global TEK lifetime value:
MOT:7A(config-if)#cable privacy tek life-time <30-604800>
where:
30-604800 is the TEK life-time value in seconds (the maximum value is 7
days).
Use the no cable privacy tek life-time command, in Cable Interface
Configuration mode, if you need to restore the default:
MOT:7A(config-if)#no cable privacy tek life-time <30-604800>

Use the cable privacy cm-tek grace-time command in Cable Interface

Configuration mode to set an individual cable modem grace-time TEK value for
Baseline Privacy.
MOT:7A(config-if)#cable privacy cm-tek grace-time <1-8192>
<300-302399>
where:
1-8192 is the Service Identifier (SID).
300-302399 is the grace-time value, expressed in seconds (5 minutes to 3.5
days).
Use the no cable privacy cm-tek grace-time command if you need to reset the
default.
3. If a new grace-time value is set for one or more cable modems, use the cable
privacy cm-tek reset command, in Cable Interface Configuration mode, to reset
the grace-time cable modem TEK value:
MOT:7A(config-if)#cable privacy cm-tek reset [<1-16383>]
where:
1-16383 is the primary Service Identifier (SID) of the cable modem.
4. The default lifetime TEK is 43,200 seconds. Use the cable privacy cm-tek
life-time command, in Cable Interface Configuration mode, to set a lifetime TEK
for an individual cable modem:
MOT:7A(config-if)#cable privacy cm-tek life-time <0-16383>
<1800-604800>
where:
0-16383 is the cable modems primary SID.
1800-604800 is the TEK lifetime value, expressed in seconds.
5. Use the show cable privacy tek command to display current TEK lifetime and
grace-time information:
MOT:7A#show cable privacy tek
6. Use the show cable privacy cm-tek command to display TEK information for
an individual cable modem using its MAC address:
MOT:7A(config)#show cable privacy cm-tek [<1-8192>]

where:
Setting Authorization Key Values

An Authorization Key (AK) has a limited lifetime and must be periodically refreshed.
A cable modem refreshes its AK by re-issuing an Authorization Request to the cable
interface. Follow the steps in this section to configure the AK values.
1. Use the cable privacy cm-auth life-time command, in Cable Interface
Configuration mode, to set the AK lifetime value:
MOT:7A(config-if)#cable privacy cm-auth life-time {<mac>}
[<300-6048000> ]
where:
300-6048000 is the AK lifetime value, expressed in seconds.
2. Use the cable privacy cm-auth grace-time command, in Cable Interface
Configuration mode, to set an individual grace-time AK value:
MOT:7A(config-if)#cable privacy cm-auth grace-time <mac>
<300-3024000>
where:
300-3024000 is the individual grace-time AK, expressed in seconds (5
minutes to 35 days).
3. Use the cable privacy cm-auth reset command, in Cable Interface Configuration
mode, to reset the individual cable modem life-time or grace-time value once a
new AK life-time or grace-time value is configured:
MOT:7A(config-if)#cable privacy cm-auth reset <mac>
where:

Managing Multicast Traffic

Follow this procedure to manage multicast traffic on the BSR:
Use the cable privacy mcast command, in Cable Interface Configuration mode.
to enable the encryption of multicast traffic, as follows:
MOT:7A(config-if)#cable privacy mcast <A.B.C.D> <A.B.C.D>
[<8192-16381>]
where:
A.B.C.D is the multicast IP address.
A.B.C.D is the multicast subnet mask.
8192-16381 is the multicast SAID number.
Use the cable privacy mcast access command, in Cable Interface Configuration
mode, to configure a multicast address access list:
MOT:7A(config-if)#cable privacy mcast access <H.H.H> <A.B.C.D>
[<8192-16381>]
where:
H.H.H is the cable modem MAC address.
A.B.C.D is the multicast IP address.
8192-16381 is the multicast SAID number.

Configuring Cable Privacy Mandatory

The cable privacy mandatory feature allows a cable operator to enable the encryption
of all routed broadcasts and routed unmapped multicast traffic. Cable privacy
mandatory encrypts otherwise unencrypted downstream routed non-unicasts and only
gives the key to decrypt these messages to routing cable modems. Bridging cable
modems will discard all downstream routed broadcasts or routed multicasts.
Note: The cable privacy mandatory feature requires that all cable modems
have BPI enabled in order to register. If a cable modem does not have BPI
enabled and cable privacy mandatory is turned on, the cable modem will not
be able to register.
With cable privacy mandatory enabled, routed broadcasts are not received by
VLAN Tagging CM's. Therefore, VLAN tagging cable modems will not be able
to respond to broadcast pings.
Use the cable privacy mandatory command, in Global Configuration or Cable

Interface Configuration Mode, to allow the encryption of all routed broadcasts and
routed unmapped multicast traffic, as follows:
MOT(config)#cable privacy mandatory
Warning: After enabling the cable privacy mandatory feature, the cable
operator must issue the clear cable modem all reset command to
re-register all cable modems and allow non-unicast traffic (including ARPs) to
function correctly.
The cable privacy enforce-bpi-plus command mandates that a cable modem

provisioned in DOCSIS 1.1 or higher must register with DOCSIS Baseline Privacy
Interface Plus (BPI+) and not use the earlier version of DOCSIS BPI.
MOT(config)#cable privacy enforce-bpi-plus
Note: CMs provisioned with DOCSIS 1.0 are permitted to register without
BPI+.

Using Flap Lists

Flap lists are used to collect statistics for determining cable modem problems on the
network. The cable modem flap list keeps track of the cable modem MAC address, up
and down transitions, registration events, missed periodic ranging packets, upstream
power adjustments on the BSR.
The following sections describe how Flap lists are used:
Setting Flap List Parameters
Using Flap Lists to Troubleshoot Cable Modem Problems
Tips for Administering Flap Lists
Setting Flap List Parameters

Flap list parameters are configured to define a criteria for the proper functioning of
your cable network.
When a cable modem makes an insertion request more frequently than the defined
insertion time (the time allowed for cable modems to complete registration), the cable
modem is placed in the flap list for recording. When the cable modem power
adjustment meets or exceeds its predefined threshold, the cable modem is placed in
the flap list. You can specify the power adjustment threshold to a value that will cause
a flap-list event to be recorded. A miss rate is the number of times a cable modem
does not acknowledge a MAC layer keepalive message from a CMTS. You can
specify the number of seconds to record and retain flapping activity for the cable
modems connected to the CMTS. The number of cable modems that can be recorded
in the flap list is 8192 cable modems.
Use the following options to set flap list parameters:
1. Use the cable flap-list aging command, in Global Configuration mode, to specify
flap list aging, the number of minutes a cable modem is kept in the flap list.
MOT:7A(config)#cable flap-list aging <1-860400>
where:
1-860400 is the flap list aging value, expressed in minutes. The default flap
list aging value is 1440.
2. Use the cable flap-list insertion-time command, in Global Configuration mode,
to specify the flap list insertion time:
MOT:7A(config)#cable flap-list insertion-time <1-86400>

where:
1-86400 is the flap list insertion time, expressed in seconds. The default flap
list insertion time is 60.
3. Use the cable flap-list percentage-threshold command, in Cable Interface
Configuration mode, to specify the cable modem miss percentage:
MOT(config-if)#cable flap-list percentage-threshold <1-100>
where:
1-100 is the cable modem miss percentage.
Use the cable flap-list trap-enable command to control whether a flapListTrap
will be sent to the CMTS by the SNMP agent if the cable modem miss percentage
exceeds the flapListPercentageThreshold specified with the cable flap-list
percentage threshold command.
4. Use the cable flap-list power-adjust threshold command, in Global
Configuration mode, to specify the power adjustment threshold value between 0
to 2 dBmV. The power adjustment threshold causes a flap-list event to be
recorded when the threshold is exceeded:
Note: Motorola recommends that you do not change the power adjustment
threshold from the default value, which is 2 dbmV. Ensure that you evaluate
the need to enable this function before applying it to your network. A power
adjustment threshold of less than 1 dBmV may cause excessive flap list
event recording.
MOT:7A(config)#cable flap-list power-adjust threshold <1-10>

where:
1-10 is the power adjustment threshold value, expressed in dB.

5. The default miss threshold for MAC-layer keepalive messages is 6. If you want to
change the threshold number of MAC-layer keepalive message misses that will
result in the cable modems being recorded in the flap list, use the cable flap-list
miss-threshold command, in Global Configuration mode, as follows:
Note: A high miss rate can indicate intermittent upstream problems, fiber
laser clipping, or common-path distortion.
MOT:7A(config)#cable flap-list miss-threshold <1-12>

where:
1-12 is the keepalive misses threshold value.
6. Use the cable flap-list size command, in Global Configuration mode, to specify
the maximum number of cable modems that can be recorded in the flap list:
MOT:7A(config)#cable flap-list size <1-8191>
where:
1-8191 is a number that defines the maximum number of cable modems.
7. Use the clear cable flap-list command, in Global Configuration mod,e to remove
a cable modem from the flap list.
MOT:7A(config)#clear cable flap-list [<mac>] | all
where:
8. Use the show cable flap-list command to display the cable modem flap lists and
verify cable flap list information. Refer to Using Flap Lists to Troubleshoot Cable
Modem Problems for using the various show cable flap-list command options.
MOT:7A#show cable flap-list
You can also use the show running-configuration command to display the cable
modem flap lists and verify flap list information:

MOT:7A#show running-configuration | include flap
Note: If a value is set to the default, the default value does not display after a
show running-configuration command.
Using Flap Lists to Troubleshoot Cable Modem Problems

The BSR maintains a database of flapping cable modems to assist in locating cable
plant problems. The flap list feature tracks the upstream and downstream performance
of all cable modems on the network, without impacting throughput and performance
between the cable modem and BSR, or creating additional packet overhead on the
HFC network.
The following tasks are used to troubleshoot cable modem Problems:
Viewing Flap List Statistics to Identify Network Health
Interpreting Flap List Statistics
Viewing Flap List Statistics to Identify Network Health

This section describes the different show cable flap list sorting options and describes
the command output fields. Cable modems appear in the flap list when any of the
following conditions are detected:
The cable modem re-registers more frequently than the configured insertion time.
Intermittent keepalive messages are detected between the BSR and the cable
modem.
The cable modem upstream transmit power changes beyond the configured power
adjust threshold.
Follow these steps to view flap list statistics by using different sorting options:
1. Use the show cable flap list command to view all flap list statistics for cable
modems:
MOT:7A#show cable flap-list
2. Use the show cable flap-list sort-flap command to sort the flap list statistics by
the cable modem flap:
MOT:7A#show cable flap-list sort-flap

3. Use the show cable flap-list sort-time command to sort the flap list statistics by
the time at which the cable modem flap occurred:
MOT:7A#show cable flap-list sort-time
4. Use the show cable flap-list sort-interface comman to sort the flap list statistics
by the cable upstream interface on which the cable modem flap occurred:
MOT:7A#show cable flap-list sort-interface
field descriptions for the show cable flap-list command.
Interpreting Flap List Statistics

This section describes how to interpret flap list statistics in order to troubleshoot the
cable network
Cable modem activity follows the sequence below.
Power-on
Initial maintenance
Station maintenance
Power-off
The initial link insertion is followed by a keepalive loop between the BSR and cable
modem and is called station maintenance. When the link is broken, initial
maintenance is repeated to re-establish the link.
Initial maintenance @ Time T1
Station maintenance
Init maintenance @ Time T2
The Ins and Flap counters in the flap list are incremented whenever T2 T1 < N
where N is the insertion-time parameter configured using the cable flap-list
insertion-time command. The default value for this parameter is TBD seconds.
Use the following cause or symptom observations (Table Table ) to interpret flap list
activity and solve cable modem problems:
Note: Cable modems go offline faster than the frequency hop period and can
cause the frequency to stay fixed while cable modems go offline. Reduce the
hop period to 10 seconds to adjust to the hop frequency period.

Table Troubleshooting Cable Modem Problems
Cause or Symptom Problem

Subscriber cable modem shows a lot of Cable modem is having communication
flap list activity problems with the BSR.
Subscriber cable modem shows little or The cable modem is communicating with the
no flap list activity. BSR effectively, however there is still a
problem. The problem can be isolated to the
subscribers CPE computer equipment or the
cable modem connection.
Ten percent of the cable modems in the These cable modems are most likely having
flap list show a lot of activity. difficulties communicating with the BSR.
Cable modems have a lot of power Cable modems have problems with their
adjustment (P-Adj) errors. physical upstream paths or in-home wiring
problems.
Use corresponding cable modems on the
same physical upstream port interface with
similar flap list statistics to quickly resolve
problems outside the cable plant to a
particular node or geographic location.
All cable modems are incrementing the There is a provisioning server failure.
insertion at the same time.
A cable modem has more than 50 power The cable modem has a suspect upstream
adjustments per day. path.
Corresponding cable modems on the same
physical upstream port interface with similar
flap list statistics can be used to quickly
resolve problems outside the cable plant to a
particular node or geographic location.
A cable modem has roughly the same There is a problematic downstream path. For
number of hits and misses and contain a example, the downstream power level to the
lot of insertions. cable modem may have a power level that is
too low.
A high flap list insertion (Ins) time Intermittent downstream synchronization loss.
number. DHCP or cable modem registration problems.
Low miss/hit ratio, low insertion, low Indicates an optimal network situation.
P-adj, low flap counter and old
timestamp.

Table Troubleshooting Cable Modem Problems
Cause or Symptom Problem

High ratio of misses over hits (> 10%) Hit/miss analysis should be done after the
"Ins" count stops incrementing. In general, if
the hit and miss counts are about the same
order of magnitude, then the upstream may
be experiencing noise. If the miss count is
greater, then the cable modem is probably
dropping out frequently and not completing
registration. The upstream or downstream is
perhaps not stable enough for reliable link
establishment. Very low hits and miss
counters and high insertion counters indicate
provisioning problems.
High power adjustment counter. Indicates the power adjustment threshold is
probably set at default value of 2 dB
adjustment. The cable modem transmitter
step size is 1.5 dB, whereas the headend may
command 0.25 dB step sizes. Tuning the
power threshold to 6 dB is recommended to
decrease irrelevant entries in the flap list. The
power adjustment threshold may be set using
<cable flap power threshold <0-10 dB> from
Global Configuration mode. A properly
operating HFC network with short amplifier
cascades can use a 2-3 dB threshold.
High P-Adj (power adjustment) This condition can indicate that the fiber node
is clipping the upstream return laser. Evaluate
the cable modems with the highest number of
correcteds and uncorrecteds first. If the cable
modems are not going offline (Ins = 0), this
will not be noticed by the subscriber.
However, they could receive slower service
due to dropped IP packets in the upstream.
This condition will also result in input errors on
the cable interface.
High insertion rate. If link re-establishment happens too
frequently, then the cable modem is usually
having a registration problem.This is indicated
by a high Ins counter which tracks the Flap
counter.

Table Table describes how to interpret flap list statistics:
Table Flap List Statistic Interpretations
Field Description
Hit and Miss The HIT and MISS columns are keepalive polling statistics between the
BSR and the cable modem. The station maintenance process occurs for
every cable modem approximately every 10 seconds. When the BSR
receives a response from the cable modem, the event is counted as a Hit.
If the BSR does not receive a response from the cable modem, the event
is counted as a Miss. A cable modem will fail to respond either because of
noise or if it is down. Cable modems which only log Misses and zero Hits
are assumed to be powered off.
Misses are not desirable since this is usually an indication of a return path
problem; however, having a small number of misses is normal. The flap
count is incremented if there are M consecutive misses where M is
configured in the cable flap miss-threshold parameter. The parameter
value ranges from 1-12 with a default of 6.
Ideally, the HIT count should be much greater than the Miss counts. If a
cable modem has a HIT count much less than its MISS count, then
registration is failing. Noisy links cause the MISS/HIT ratio to deviate from
a nominal 1% or less. High Miss counts can indicate:
Intermittent upstream possibly due to noise
Laser clipping
Common-path distortion
Ingress or interference
Too much or too little upstream attenuation
P-Adj The station maintenance poll in the BSR constantly adjusts the cable
modem transmit power, frequency, and timing. The Power Adjustments
(P-Adj) column indicates the number of times the cable modems power
adjustment exceeded the threshold value. The power adjustment
threshold may be set using the <cable flap power threshold > parameter
with a value range of 0-10 dB and a default value of 2 dB. Tuning this
threshold is recommended to decrease irrelevant entries in the flap list.
Power Adjustment values of 2 dB and below will continuously increment
the P-Adj counter. The cable modem transmitter step size is 1.5 dB,
whereas the cable interface may command 0.25 dB step sizes. Power
adjustment flap strongly suggests upstream plant problems such as:
Amplifier degradation
Poor connections
Thermal sensitivity
Attenuation problem

Table Flap List Statistic Interpretations
Field Description
Flap The Flap counter indicates the number of times the cable modem has
flapped. This counter is incremented when one of the following events is
detected:
Unusual cable modem insertion or re-registration attempts. The Flap and
the Ins counters are incremented when the cable modem tries to
re-establish the RF link with the BSR within a period of time that is less
than the user-configured insertion interval value.
Abnormal Miss/Hit ratio The Flap counter is incremented when N
consecutive Misses are detected after a Hit where N can be
user-configured with a default value of 6.
Unusual power adjustment The Flap and P-adj counters are incremented
when the cable modems upstream power is adjusted beyond a
user-configured power level.
Time Time is the timestamp indicating the last time the cable modem flapped.
The value is based on the clock configured on the local BSR. If no time is
configured, this value is based on the current uptime of the BSR. When a
cable modem meets one of the three flap list criteria, the Flap counter is
incremented and Time is set to the current time.
Tips for Administering Flap Lists

Follow these suggestions for administrating flap lists:
Write script(s) to periodically poll the flap list.
Analyze and identify cable modem trends from the flap list data.
Query the billing and administrative database for cable modem MAC
address-to-street address translation and generate reports. These reports can then
be given to the Customer Service Department or the cable plants Operations and
Maintenance Department. Maintenance personnel use the reports to see patterns
of flapping cable modems, street addresses, and flap statistics that indicate which
amplifier or feeder lines are faulty. The reports also help troubleshoot problems in
the downstream and/or upstream path, and determine if a problem is related to
ingress noise or equipment.

Save the flap list statistics to a database server at least once a day to keep a record
of flap list statistics which includes upstream performance and quality control
data. These statistics can be used again at a later time to evaluate trends and solve
intermittent problems on the HFC networks. Once the flap list statistics are
backed up daily on the database server, the flap list statistics can be cleared.
Pinging a Cable Modem at the MAC Layer

The ping docsis command is used to ping or find a cable modem on the network at
the MAC layer by entering the cable modems MAC or IP address.
When a DOCSIS ping is initiated, the BSR sends a test packet downstream towards
the cable modem to test its connection. In most instances, this command is used to
determine if a particular cable modem is able to communicate at the MAC address
layer when a cable modem has connectivity problems at the network layer. For
example, if a cable modem is unable to register and obtain an IP address, the ping
DOCSIS command can help you determine if there are provisioning problems
associated with the cable modem.
Follow these steps to use the ping DOCSIS function:
Cable Interface Configuration
where:
2. Use the ping docsis command, in Cable Interface Configuration mode, to
determine if a cable modem is online:
MOT:7A(config-if)#ping docsis {<mac> | <prefix>} <1-100>
where:
prefix is the IP address of the cable modem.
1-100 is the number of ping test packets to be sent to the cable modem.

Resetting the Cable Modem

Use the following options to reset cable modems on the network:
Use the clear cable modem reset command, in Privileged EXEC mode, to reset a
single cable modem by using its MAC address:
MOT:7A#clear cable modem <mac> reset
where:
Use the clear cable modem reset command, in Privileged EXEC mode, to reset
specific group of cable modems:
MOT:7A#clear cable modem <mac> [<mac>] reset
where:
mac a MAC address mask that specifies a group of cable modems.
Use the clear cable modem reset command, in Privileged EXEC mode, to reset a
single cable modem by using its IP address:
MOT:7A#clear cable modem <prefix> reset
where:
Use the clear cable modem all reset command, in Privileged EXEC mode, to
reset all cable modems:
MOT:7A#clear cable modem all reset

Clearing Cable Modem Counters

Use one of the following options to clear cable modem counters:
Use the clear cable modem counters command, in Privileged EXEC mode, to
clear and reset a specific cable modems traffic counters from the station
maintenance list by using its MAC address:
MOT:7A#clear cable modem <mac> [<mac>] counters
where:
mac resets counters for a specified cable modems MAC address.
mac optionally specifies a set of cable modem MAC addresses to reset
counters by masking a portion of the MAC address.
Use the clear cable modem counters command, in Privileged EXEC mode, to
clear and reset a specific cable modems traffic counters from the station
maintenance list by using its IP address:
MOT:7A#clear cable modem <prefix> counters
where:
prefix resets counters for a specified cable modems IP address.
Use the clear cable modem all counters command, in Privileged EXEC mode,
to clear and reset all cable modems traffic counters on the BSR:
MOT:7A#clear cable modem all counters
Viewing Cable Modem Information

The show cable modem command allows you to view statistical information about
cable modems connected to the BSR. The information helps you to evaluate network
performance, troubleshoot registration problems, and determine registration status
and learn ranging information.
Use the following options to view cable modem information:
Use the show cable modem command to display information for all cable
modems on connected to the BSR:
MOT:7A#show cable modem
Use the show cable modem command to display information for a specific cable
modem connected to the BSR:

MOT:7A#show cable modem [<mac> | <prefix>]

where:
Use the following options to view Customer Premises Equipment (CPE)
information:
If you want to display CPE information for all cable interfaces, use the show
cable modem cpe command as shown bellow:
MOT:7A#show cable modem cpe
If you want to display information for a CPE IP or MAC address, use the
show cable modem cpe command:
MOT:7A#show cable modem cpe [<mac> | <prefix>]
where:
mac is the CPE MAC address.
prefix is the CPE IP address.
If you want to display CPE information for a particular upstream port, use the
show cable modem cpe upstream command:
MOT:7A#show cable modem cpe <X/Y> upstream <NUM>
where:
Use the show cable modem detail command in Privileged Exec mode to
display information for a SID assigned to a cable modem on a specific
DOCSIS interface:
MOT:7A#show cable modem detail <X/Y> <NUM>
where:
NUM is the Service Identifier assigned to a cable modems.
Use the show cable modem detail command in Privileged Exec mode to
display information for a specific modem connected to a specific interface:

MOT:7A#show cable modem detail <MAC>

where:
MAC is the cable modem MAC address.
The show cable modem summary command displays information for the total
number of cable modems, registered cable modems, and unregistered cable
modems:
Registered modems are modems which have reached the Online(d), Online
(pk), Online(pt) or Online(un) states.
Active modems are those modems in any Init, DHCP or Reject state or
substate. All other modems are assumed to be powered off.
Unregistered modems are those modems in any Init, DHCP or Reject state or
substate. Offline modems are any cable modems which have no state, are not
communicating, but are remembered because they previously were
provisioned. These modems are assumed to be powered off.
Use the following options to view cable modem summary information:
Use the show cable modem summary command to display the total number
of registered, unregistered and offline cable modems for cable interfaces on
the BSR 64000:
MOT:7A#show cable modem summary
Use the show cable modem summary total command to display the total
number of registered, unregistered and offline cable modems for a specific
cable module:
MOT:7A#show cable modem summary [<X/Y> | total]
where:
Use the show cable modem svc-flow-id command in Privileged Exec mode to
view the service flow ID for a cable modem connected to a slot and cable
interface on the BSR:
MOT:7A#show cable modem <mac> svc-flow-id
where:

Use the show cable modem hosts command in Privileged EXEC mode to display
the number of Customer Premises Equipment (CPE) hosts connected to a specific
cable modem:
MOT:7A#show cable modem {<mac> | <prefix>} hosts
where:
Use the show cable modem offline command to display offline cable modems
only:
Note: The show cable modem offline command output is updated if the
aging timer interval expires for an offline cable modem. Also, the cable
modem offline table can contain 6100 entries. If this total number is reached
and a new cable modem goes offline, the oldest entry in the table is deleted.
MOT:7A#show cable modem offline [<mac> | <0-15>]

where:
mac is the MAC hardware address of the cable modem.
0-15 is the slot number of the CMTS module to which cable modems are
associated.
Use the show cable modem registered command to display registered cable
modems only:
MOT:7A#show cable modem registered
Use the show cable modem unregistered command to display unregistered
cable modems only by filtering online and reject states:
MOT:7A#show cable modem registered
where:
The following online and reject states are filtered:
init(o),init(t), init(r1), init(r2), init(rc), dhcp(d), dhcp(req), dhcp(ack), offline
Use the show cable modem time-registered command to display the Spectrum
Group for the cable modem and how long the cable modem has been registered:

MOT:7A#show cable modem time-registered [<mac> | <slot> |

spectrum-group <WORD>]
where:
mac is the MAC hardware address of the cable modem.
slot is the slot number of the cable module to which cable modems are
associated.
spectrum-group is used to identify a spectrum group.
WORD is the spectrum group name to which the cable modem belongs.
The show cable modem mac command displays MAC layer (layer 2)
information for cable modems.
Use the following options to view cable modem MAC layer information:
Use the show cable modem mac command to view MAC layer information
for cable modems on a specific cable module:
MOT:7A#show cable modem mac <X/Y>
where:
Use the show cable modem mac command to view MAC layer information
for a specific cable modem:
MOT:7A#show cable modem <mac> mac
where:
The show cable modem phy command displays physical hardware information
for cable modems.
Use the following options to view cable modem physical layer information:
Use the show cable modem phy command to view physical layer
information for cable modems on a specific CMTS module:
MOT:7A#show cable modem phy <X/Y>
where:
X/Y is the slot and MAC Domain number of the CMTS module

Use the show cable modem phy command to view physical layer
information for a specific cable modem:
MOT:7A#show cable modem <mac> phy
where:
The show cable modem maintenance command is used to view station
maintenance statistics, which includes station maintenance retries, station
maintenance failures, and recent event timestamps.
Cable modem station maintenance ranging, which occurs during the cable
modem registration process, uses periodic time intervals to send a unicast
message containing a registered SID between the cable modem and the CMTS.
Use the following options to display station maintenance statistics:
Use the show cable modem maintenance command to view all station
maintenance statistics:
MOT:7A#show cable modem maintenance
Use the show cable modem maintenance command to view station
maintenance statistics for cable modems on a particular cable interface:
MOT:7A#show cable modem <X/Y> maintenance
where:
Use the show cable modem maintenance command to view station
maintenance statistics for a particular cable modem:
MOT:7A#show cable modem <mac> maintenance
Refer to the BSR 64000 Command Reference Guide to see typical screen output, field
descriptions, and an explanation of connectivity states for the show cable modem
commands.
Multiple IP Addresses Per MAC Address

The BSR supports host authorization for multiple IP addresses using the same MAC
address. The maximum number of static IP addresses that can be configured behind a
single MAC address is 252. The output of several CLI commands has been modified
to accommodate the existence of multiple IP addresses per MAC address. The
commands affected are as follows:

show cable modem <mac> hosts

show cable modem <mac> cpe
show cable modem cpe
show cable host <mac>
The following is an example of typical screen output displaying multiple IP addresses
per MAC address:
Interface Prim Connect Timing Rec Ip Address Mac Address

Sid State Offset Power
Cable 5/0/U1 7 online 1230 3 7.1.1.22 0090.8336.cdf1
Number of Hosts = 0
Cable 5/0/U1 6 online 1226 -2 7.1.1.23 0090.8336.d2fd
Number of Hosts = 0
Cable 5/0/U2 4 online 1239 0 7.1.1.24 0090.833d.8f82
Number of Hosts = 0
Cable 5/0/U2 3 online 1233 0 7.1.1.17 0090.833d.8f88
7.1.1.18
7.1.1.19
7.1.1.20
7.1.1.21
Number of Hosts = 0
Viewing the Timing Adjustments for Cable Modems

Each cable modem manufacturer uses a different initial timing offset value. The BSR
stores the initial timing values based on the cable modem manufacturer. The true
timing offset that each cable modem uses is read by the cable modem using SNMP.
The cable modem with the highest recorded timing offset is the furthest cable modem
away from the BSR that is functioning correctly.

The timing offset stored in the cable modem is the collection of all the timing
adjustments sent to the cable modem. The BSR cannot determine the timing offset at
which a particular cable modem starts. The cable modem starts at an initial timing
offset based on its internal delays. The values stored and displayed by the BSR are the
summary of the cable modem initial timing offset adjustments.
The show cable modem timing-offset command allows the user to select which
cable modems are displayed based on their timing offset value.
Use the show cable modem timing-offset below command in Privileged EXEC
mode to identify all cable modems with a timing offset below the entered number:
MOT:7A#show cable modem timing-offset below <0-500000> [<X/Y>]
where:
0-500000 is the timing offset value that displays all cable modems below this
timing offset value.
Use the show cable modem timing-offset above command in Privileged EXEC
mode to identify all cable modems with a timing offset above the entered number:
MOT:7A#show cable modem timing-offset above <0-500000> [<X/Y>]
where:
0-500000 is the timing offset value that displays all cable modems above this
timing offset value.
Refer to the BSR 64000 Command Reference Guide to see typical screen output, field
descriptions, and an explanation of connectivity states for the show cable modem
commands.

Configuring Remote Query

The Remote Query feature allows the BSR to act as an SNMP Manager and query its
registered cable modems via SNMP to obtain particular RF parameters. Providing the
BSR with the ability to remotely query cable modems results in a significant
performance improvement over a central SNMP manager querying each individual
modem.
The Remote Query feature enables an SNMP Remote Query task to the SRM that
periodically polls every registered cable modem on the BSR to obtain five particular
RF parameters critical for the management of an MSOs HFC plant. The cable modem
RF parameters are:
downstream signal to noise ratio (docsIfSigQSignalNoise)
upstream transmit power level (docsIfCmStatusTxPower)
received downstream power level (docsIfDownChannelPower)
current round trip time obtained from the ranging offset
(docsIfUpChannelTxTimingOffset)
the total microreflections including in-channel responses perceived on the
downstream interface (docsIfSigQMicroreflections)
The Remote Query feature executes the following operational sequence:
1. An SNMPv1 Get-Request is sent to each cable modem attached to the BSR. The
Remote Query task is implemented on the SRM, and it sends only one SNMP
request at a time.
2. The results of these SNMP requests are stored in an "Rquery CM Table" with an
entry for each cable modem.
3. The MSOs Network Operation Center (NOC) reads the Rquery CM Table by
performing an SNMPv2 "GetBulk" operation. Each GetBulk response from the
BSR to the NOC will contain the data for up to eight CMs.
Remotely polling cable modems at each CMTS and having a central SNMP
application perform SNMPv2 GetBulk walks to obtain the RFstatistics for all cable
modems attached to the CMTS provides a distinct technical advantage. A central
polling application typically polls one cable modem at a time while an SNMPv2
GetBulk packet can obtain the RF parameters for eight cable modems at a time.

Configuring the Remote Query feature involves the following tasks:

Enabling Remote Query
Configuring the SNMP Response Timeout
Enabling SNMP Remote Query Traps
Enabling Remote Query

Use the cable modem remote-query command, in Global Configuration mode, to
enable the Remote Query polling operation, configure the polling interval to use when
querying each cable modem, and specify the SNMP community name to use when to
reading a cable modems RF parameters, as follows:
MOT:7A(config)#cable modem remote-query <1-86400>
<snmp-community-name>
where:
1-86400 configures the interval, in seconds, that the Remote Query task waits
after completing one full polling cycle of all cable modems and then starting the
next polling cycle.
snmp-community-name is the SNMPv1 community name that the Remote Query
task uses to read a cable modems RF parameters.
Note: The Remote Query feature polls cable modems using SNMPv1 only.
The MSO must configure CMs to accept the SNMPv1 community string
specified with the cable modem remote-query command.
An operator can force the immediate execution of a Remote Query polling

cycle by entering the following sequence of commands:
1) cable modem remote-query <1-86400> <snmp-community-name>

2) no cable modem remote-query
3) show cable modem remote-query (check the status of the polling cycle)
The frequency of Remote Query polling should be selected with care so as

not to introduce excessive overhead that would degrade performance.
The cable modem remote-query command is the only command required to

enable the Remote Query feature. No additional SNMP commands are
required.

Configuring the SNMP Response Timeout

Use the snmp-server manager response-timeout command to specify the number of
milliseconds that the SNMP manager running on the BSR waits for an SNMP
response from a cable modem polled by the Remote Query feature, as follows:
MOT:7A(config)#snmp-server manager response-timeout <10-60000>
where:
10-60000 is the number of milliseconds
Note: Increasing the response-timeout value increases the probability of

receiving a cable modem remote query response under high upstream load
conditions, but also increases the overall polling cycle time when cable
modems completely fail to respond.
Enabling SNMP Remote Query Traps

The BSR acts as an SNMP management station to query its registered cable modems
when the Remote Query feature is enabled. For the BSR to send remote query traps,
the following must also be configured:
At least one SNMP trap destination host must be configured with the
snmp-server host command.
Remote query traps must be enabled with the snmp-server enable traps
remote-query command.
The snmp-server enable traps remote-query command enables a new SNMP trap
group named "remote-query" to control sending of traps defined for the Remote
Query feature. This allows the BSR to send an unsolicited notification to one or more
pre-configured management stations that are identified to receive traps with the
snmp-server host command.
To enable the BSR to send SNMP Remote Query traps, do the following:
1. Use the snmp-server host command, in Global Configuration mode, to specify a
destination SNMP trap host to receive SNMP trap information, as shown below.
MOT:7A(config)#snmp-server host <A.B.C.D> traps <WORD>
remote-query

where:
A.B.C.D is the IP address of the host machine to receive remote query SNMP
trap information
WORD is the SNMPv1/v2c community string or SNMPv3 user name
2. Use the snmp-server enable traps command, in Global Configuration mode, to
enable SNMP traps, as shown below. This command configures the BSR to send
SNMP traps to the host(s) specified with the snmp-server host command.
MOT:7A(config)#snmp-server enable traps remote-query
Displaying Remote Query Information

The show cable modem remote-query command displays the polled RF parameters
for each cable modem that has registered on the BSR.
MOT:7A# show cable modem remote-query
field descriptions for the show cable modem remote-querycommand.

9
Configuring Service Classes
Introduction
The Service Levels Classes with Maximum Assigned Bandwidth (MAB) feature
allows customers to configure service classes and control the amount of bandwidth
allocated to each class. This permits customers to provide support for communication
applications with varying Quality of Service (QoS) requirements such as voice, video,
and data and to effectively manage the bandwidth allocated to these applications.
Additionally, this feature allows customers to provide differentiated levels of service
to their end users.
Service Classes
The concept of service classes implies assigning service flows to a service class and
providing all flows belonging to that class with a defined quality of service. DOCSIS
has defined a set of QoS parameters, including maximum sustained and minimum
reserved traffic rates, and a way for associating specific QoS parameter values to
service flows. DOCSIS has further incorporated the concept of a service class name
so that service flows, when being created, may be assigned their QoS parameters by
referencing a service class name. The Service Level Classes with Maximum Assigned
Bandwidth feature has extended the DOCSIS definition of a service class by
introducing additional service class parameters for maximum assigned bandwidth,
over-booking, and class-based scheduling priority. Service classes are supported for
both downstream and upstream directions.

Maximum Assigned Bandwidth

Maximum Assigned Bandwidth (MAB) specifies the amount of bandwidth a service
class is permitted to consume on an interface. It is expressed as a percent of the total
interface bandwidth capacity. The MAB of a service class is applied during admission
control to determine whether to admit a new service flow and again by the scheduling
algorithms to provide a class-based weighting to the scheduler. Any unused portion of
a class bandwidth may be used on demand by other classes which have a traffic
load in excess of their own MAB.
Overbooking
Since not all service flows are active simultaneously the service level classes feature
permits customers to overbook service classes. Overbooking means admitting service
flows to a service class such that the sum of their guaranteed minimum reserved rates
are in excess of the configured MAB for the service class. A configurable
overbooking factor is provided by the service levels classes feature to control the
amount of overbooking. This parameter is called the Configured Active Percent
(CAP). The CAP is an estimate of how many service flows, expressed in percent, are
likely to be active simultaneously. For example, if the CAP for a service class is set to
20 percent then it is estimated that only 20 percent of the service flows belonging to
that class will be active simultaneously. Therefore, 5x (1 / 0.2) overbooking would be
allowed. A CAP of 100 percent means that no overbooking will be allowed. A CAP of
zero percent means that unlimited overbooking is allowed.
Scheduling Priority
The scheduling priority of a service class determines the order in which service flows
are serviced by the packet scheduling algorithm. All service flows belonging to a
service class with a higher scheduling priority will be serviced before service flows
belonging to service classes with a lower scheduling priority. Class scheduling
priority is distinct from the DOCSIS QoS parameter, traffic priority, which is
specified to differentiate priority for service flows with other-wise identical QoS
parameter sets.

Release 5.3.1 Configuring Service Classes
Admission Control
Admission control is a process wherein the bandwidth requirements of a service flow
are checked to verify that admission of the service flow to a service class does not
exceed the class MAB after accounting for the allowed level of overbooking. Service
flows are created during modem registration or through dynamic service messaging.
A CM registering with primary service flows will be permitted to register regardless
of whether the admission of its service flows would exceed its service class MAB. In
this case the service flow will be admitted in a Restricted state meaning that the
service flow will not be provided any guaranteed minimum reserved rate. Service
flows created via dynamic service messaging will be rejected if admission of the
service flow would cause its service class to exceed its MAB.
Downstream Flow Classifier Support

The BSR 64000 supports classification of downstream VLAN traffic into service
flows with guaranteed bandwidth, minimum rate settings, and priority settings. This
enhancement adds full support for L2VPN QoS classification for downstream traffic.
Service Class Name Expansion

The Service Class Name (SCN) Expansion enhancement is implemented with the
introduction of the Template Service Class feature for the BSR 64000. The Template
Service Class (TSC) feature increases the number of available service class names
from 64 to 1023, and each Template Service Class name has a QoS parameter set
assigned to it that defines a subscriber service tier. The TSC feature also significantly
increases the number of subscriber service tiers that can be identified in IPDR records
from 64 to 1023.
Each service class name is configured as either a Scheduling Service Class or a
Template Service Class. A Scheduling Service Class configures Motorola-specific
parameters that control admission control and packet scheduling, and corresponds to
service class names defined before the introduction of the Template Service Class
feature. The maximum number of Scheduling Service Classes remains at 32 in each
direction.
All remaining service class names must be a Template Service Class. A Template
Service Class is configured to "schedule-with" a Scheduling Service Class. Multiple
Template Service Classes may be configured to schedule with the same Scheduling
Service Class. The group of all service flows assigned to the Scheduling Service Class
and the Template Service Classes scheduling with it are treated as a single aggregate
group for admission control and scheduling purposes.

Service Flow and Classifier Allocation

This release increases the total number of supported service flows and classifiers per
modem to 32 in each direction, to support a T1 Primary Rate Interface (PRI) over
DOCSIS solution. For example, a cable modem that supports 24 Unsolicited Grant
Service (UGS) flows will be capable of providing up to 24 lines of voice over a single
modem. The total number of service flows and classifiers per module has not
changed; the allocation of these resources is now dynamic rather than static.
With the large amount of grant servicing being done on a single modem, the Packet
Cable Multimedia (PCMM) provisioning configuration must be set to optimally
guarantee a quality of service for all service flows for the modem. Specifically, there
must be an acceptable packet latency that will not translate to voice jitter.
A recommended configuration is shown in the table below. The recommended
PCMM configuration for a packetization interval of 20 milliseconds mandates an
Unsolicited Grant Size of 240 bytes.
Recommended PCMM Configuration

Assumed packetization interval 20ms
Unsolicited Grant Size 240 bytes
Grants Per Interval 1
Nominal Grant Interval (microseconds) 9000
Tolerated Grant Jitter (microseconds) 2000
Recommended BSR 64000 Configuration

Upstream map-interval (microseconds) 4000
To keep up with the rate of grants being offered, the upstream map-interval
configured on the BSR 64000 should not be set higher than 5000 microseconds. The
recommended value is 4000, which is the default.
The Nominal Grant Interval should not be set to align with the packetization interval
of 20 milliseconds (20000 microseconds). If a modem were to miss a grant in such a
configuration, it would have to wait for an entire grant interval before being able to
send out a packet. This would result in close to a 20000 microsecond latency, which
would translate to voice jitter and possible backlog of subsequent packets. Set the
Nominal Grant Interval to a value that lets packets utilize a subsequent grant in time if
the original grant was missed. The recommended value for this configuration is 9000
microseconds.

Default Service Classes

All service flows must be assigned to a service class. If a service class name is not
present in a Registration Request message generated by a CM, then the CM service
flows are assigned to a default service class based on the direction, scheduling service
type, and the specified minimum reserved rate for the service flows.
The table describes the eight default service classes on the BSR:
Note: The parameters of the default service classes may be modified but the
default service classes cannot be deleted. Refer to Modifying Service Class
Parameters for more information on changing service class parameters.
Default Service
Class Description
DefBE-Down Default downstream service class, no minimum rate.
DefRRDown Default downstream service class, non-zero minimum rate.
DefBEUp Default upstream best-effort service class, no minimum rate.
DefRRUp Default upstream best-effort service class, non-zero minimum rate.
DefUGS Default upstream UGS service class.
DefUGSAD Default upstream UGS-AD service class.
DefRTPS Default upstream real-time polling service class.
DefNRTPS Default upstream non-real-time polling service class.
DefEMUp Default upstream emergency call service class.
DefEMDown Default downstream emergency call service class.
DefMCDown Default downstream mulitcast service class.
Default Parameter Settings

The default settings for all parameters are based solely on the schedule type of the
service class.

The following table describes all of the default service class parameters on the BSR:
Parameter Downstream Best-effort UGS UGS-AD RTPS Non-RTPS

MAB 10 10 25 5 5 5
CAP 0 0 100 80 5 5
Scheduling Priority 1 1 1 1 1 1
Admitted BW Threshold 0 0 0 0 0 0
Traffic Priority 0 0 N/A N/A N/A 0
Maximum Sustained Traffic 0 0 N/A N/A 0 0
Rate
Maximum Traffic Burst 3044 3044 N/A N/A 3044 3044
Minimum Reserved Traffic 0 0 N/A N/A 0 0
Rate
Assumed Minimum Rate 128 128 128 128 128 128
Packet Size
Maximum Concatenated N/A 1522 N/A N/A 1522 1522
Burst
Nominal Polling Interval N/A N/A N/A 10000 50000 50000
Tolerated Poll Jitter N/A N/A N/A 5000 25000 N/A
Unsolicited Grant Size N/A N/A 152 152 N/A N/A
Nominal Grant Interval N/A N/A 10000 10000 N/A N/A
Tolerated Grant Jitter N/A N/A 2000 2000 N/A N/A
Grants Per Interval N/A N/A 1 1 N/A N/A
Maximum Latency 0 N/A N/A N/A N/A N/A
Activity Timeout 0 0 0 0 0 0
Admitted Parameter 200 200 200 200 200 200
Timeout
Tos And Mask N/A 0xff 0xff 0xff 0xff 0xff
Tos Or Mask N/A 0x00 0x00 0x00 0x00 0x00
Request/transmission N/A 0x000 0x07f 0x07f 0x01f 0x000
Policy

Note: For scheduling purposes, each service class gets its bandwidth based
on its MAB fraction relative to other classes, not based on the absolute value
of the MAB. For example, if there are only two active service classes and
both have the same MAB, each service class would get 50% of the
bandwidth. The absolute value of the MAB is only used for admission control
not scheduling.
Sharing Bandwidth Between Service Classes

The BSRs CMTS provides two service class admission control policies; one for
normal voice communications and one for emergency communications. These two
policies have configurable parameters that specify:
a maximum amount of bandwidth that may be allocated non-exclusively to
normal voice and emergency communications sessions. This may be 100% of the
bandwidth capacity.
the amount of bandwidth that may be allocated exclusively to normal voice and
emergency communications sessions. This may be 0% of the capacity.
The BSR provides the ability to share bandwidth between different service level
classes. Enabling bandwidth sharing, allows the bandwidth of a service level class to
be used as a bandwidth pool that can be shared by multiple service level classes.
Use the allow-share command, in Service Class Configuration mode, to enable
bandwidth sharing:
MOT:7A(config-srvclass)#allow-share <WORD> <0-1>
where:
WORD is the name of the service class.
0 disables bandwidth sharing.
1 enables bandwidth sharing.

DQoS Emergency Call Service Classes

The DQoS Emergency Call feature supports differentiated resource reservation for
high priority calls. High priority calls refer to emergency voice calls such as "911".
Since HFC upstream/downstream bandwidth is limited, an emergency call may be
blocked during high traffic hours due to insufficient bandwidth. In order to guarantee
the bandwidth for the emergency calls, the DQoS Emergency Call feature introduces
two new emergency service level classes whose bandwidth is reserved for emergency
voice calls only.
All other normal voice calls will not be allowed to use the bandwidth reserved for the
emergency class. However, emergency calls are allowed to use the bandwidth for
other service classes if the bandwidth of the emergency service class is full. Also,
bandwidth reserved for the emergency service class can be used for other applications
if the bandwidth is not already being used for emergency voice calls. If there is no
bandwidth available in the DefUGS, DefUGSAD, DefEMUp, or DefEMDown
service classes, the emergency call will be dropped.
Note: For emergency calls to use the bandwidth for other service classes,
bandwidth sharing must be enabled for those service classes. Refer to
Sharing Bandwidth Between Service Classes and the allow-share
command.
Configuring the DQoS Emergency Call Service Classes

Configuring the DQoS Emergency Call feature involves setting the maximum
assigned bandwidth (mab) for the default emergency call service classes and enabling
the emergency call trap. The default emergency call service classes are:
DefEMUp - the upstream emergency call service class
DefEMDown - the downstream emergency call service class
Use the mab command in Service Class Configuration mode to configure the
maximum assigned bandwidth for each emergency call service class:
MOT:7A(config-srvclass)#mab DefEMUp <1-100>
MOT:7A(config-srvclass)#mab DefEMDown <1-100>
where:

1-100 the percentage of bandwidth the service class is permitted to use on an

interface.
Note: The configure active percent (cap) for both the DefEMUp and
DefEMDown service classes is always 100 percent and cannot be changed.
The default maximum assigned bandwidth (mab) for both the DefEMUp and
DefEMDown service classes is 1 percent.
Use the dqos emergency-trap-enable command in Packet Cable Configuration mode

to enable the trap for Emergency Calls:
MOT:7A(config-pktcable)#dqos emergency-trap-enable
Note: The emergency call trap can also be enabled with the
rdnPktDQoSEmergencyTrapEnable MIB object (rdn-pktcable-mib).
Displaying DQoS Emergency Call Information

Use the show packet-cable gate command to view the gate ID in hexadecimal
notation, CM MAC address, subscriber IP address, CMTS slot number, upstream and
downstream SFID, status and committed time gate summary information for the
emergency service classes:
MOT:7A#show packet-cable gate

High Priority Pre-emption for 911 Calls

The High Priority (e.g. 911 Emergency Call) Pre-emption feature, which is disabled
by default, can be configured so that additional normal voice bandwidth is admitted
for high-priority 911 calls. For example, when 911 calls occur and exceed their
bandwidth, they can then use normal voice bandwidth, regardless of the normal calls
in progress.
Defining DQoS Voice Calls for Premption

The operator must enable certain upstream and downstream service class flags so that
DQoS calls can either share additional bandwidth or be pre-empted when high
priority calls occur. The applicable upstream and downstream service class flags are
disabled (0) by default.
Note: PacketCable Multimedia calls are not considered DQoS calls.
Follow these steps to configure DQoS Calls for the High Priority Pre-emption feature:
1. Use the cable service-class command in Global Configuration mode to enter
Service Class Configuration mode.
2. Choose the sharing option that best corresponds to the DQoS call type that is
being used:
a. Use the allow-share DefUGS 1 command in Service Class Configuration
mode to allow the Upstream Emergency Call Service Class (DefEMUp)
to share bandwidth with the Default Upstream Unsolicited Grant Services
(UGS) Service Class (DefUGS).
MOT:7A(config-srvclass)#allow-share DefUGS 1
b. Use the allow-share DefUGSAD 1 command in Service Class
Configuration mode to allow the Upstream Emergency Call Service Class
(DefEMUp) to share bandwidth with the Default Upstream Unsolicited
Grant Services with Activity Detection Service Class (DefUGS-AD).
MOT:7A(config-srvclass)#allow-share DefUGSAD 1

3. Use the allow-share DefRRDown 1 command in Service Class Configuration

mode to allow the Downstream Emergency Call Service Class (DefEMDown) to
share bandwidth with the Default Downstream Service Class, non-zero minimum
rate (DefRRDown).
MOT:7A(config-srvclass)#allow-share DefRRDown 1
4. Use the show cable service-class command in Global Configuration mode to
view the allowShared output field to determine if the upstream and downstream
service class flags are configured for DQoS calls.
Enabling DQoS Emergency Pre-emption

Follow these steps to configure additional bandwidth for 911 calls:
1. Use the packet-cable command in Global Configuration mode to enter
PacketCable Configuration mode:
MOT:7A(config)#packetcable
2. Use the dqos emergency-preempt command in PacketCable Configuration
mode to select all or one of three DQoS emergency pre-emption options:
MOT:7A(config-pktcable)#dqos emergency-preempt [most-recent |
oldest | random]
where:
most-recent admits bandwidth from the most recent active normal voice
calls.
oldest admits bandwidth from the oldest active normal voice calls.
random admits bandwidth from random normal voice calls.
3. Use the show packet-cable configuration dqos command to verify that the 911
emergency pre-emption option is enabled.

Creating Service Classes

In order to define and use service classes, a service class must first be created. The
service class name must then be added to the cable modem configuration file. The
service class name TLV is part of the service flow encoding, Type [24/25].4. CM
service flows are then added to the service class name referenced in the CM request
message. If no other QoS parameters are included in the Registration Request
message, then the parameters configured for the service class in the CMTS are applied
to the service flows. Please refer to Modifying Service Class Parameters for more
information on how to set service class parameters for the service class that you
create. If you do not set the service class parameters, then the default parameters are
used based on the scheduling type that you selected for your service class. QoS
parameters included in the CM Registration Request message override those
configured in the CMTS.
Follow these steps to define a new service class:
Cable Service Class mode and define a new service class or modify a default
service class:
Note: A total of 32 service classes, including the 11 default service classes,

are supported.
MOT:7A(config)#cable service-class <WORD>

where:
WORD is the service class name.
Note: Default service classes can be changed, but cannot be deleted.

2. Use the name schedule-type command in Cable Service Class mode to create a
service class that specifies the scheduling service type on an upstream service
flow:
Note: The upstream or downstream direction is inferred from the scheduling

service type.
MOT:7A(config-srvclass)#name <WORD> schedule-type [BE-DOWN |

BE-UP | UGS | UGS-AD | RTPS | NON-RTPS]
where:
WORD is the service class name, which can be between 1 and 15 characters.
BE-DOWN is for best effort service on the downstream port.
BE-UP is for best effort service on the upstream ports.
NON-RTPS is for non-real-time polling.
RTPS is for real-time polling.
UGS is for unsolicited grant service.
UGS-AD is for unsolicited grant service with activity detection.
3. Use the mab command in Cable Service Class mode to specify the bandwidth
that a service class is permitted to consume on an interface.
Note: The default MAB for any user-defined service class is set to 1
regardless of the scheduling type.

The service class MAB is applied during admission control to determine whether
to admit a new service flow and again by the packet schedulers to provide a
class-based weighting to the scheduler.
Note: When configuring the Maximum Assigned Bandwidth (MAB) for service
classes, it is not permitted to configure MABs such that the sum of the MABs
for all service classes for each direction (upstream and downstream) exceeds
100 percent. Refer to Calculating Maximum Assigned Bandwidth
Percentages.
MOT:7A(config-srvclass)#mab <WORD> <1-100>

where:
1-100 is the percent of the total interface bandwidth capacity.
Note: For scheduling purposes, each service class gets its bandwidth based
on its MAB fraction relative to other classes, not based on the absolute value
of the MAB. For example, if there are only two active service classes and
both have the same MAB, each service class would get 50% of the
bandwidth. The absolute value of the MAB is only used for admission control
not scheduling.

Calculating Maximum Assigned Bandwidth

Percentages
The total percentage of combined MABs for all upstream or all downstream service
classes can not exceed 100%. If a user attempts to exceed this threshold, the BSR will
adjust the desired MAB percentage accordingly so it does not exceed 100%. For
example, the total combined upstream MABs is 70% as displayed in the following
output from the show cable service-class command.
Upstream Service Classes
Service Class mab cap priority

-------------------------------------------------
DefBEUp 10 0 1
DefRRUp 10 0 1
DefUGS 10 100 1
DefUGSAD 10 80 1
DefRTPS 10 5 1
DefNRTPS 10 5 1
DefEMUp 10 100 1
Total assigned bandwidth (mab sum): 70%

The remaining MAB available is 30%. The DefEMUp service class has a MAB of
10%. If a user attempts to change the MAB percentage for the DefEMUp service class
to 50%, the following output would be displayed with the show cable service-class
command reflecting that the additional 10% MAB requested for the DefEMUp
service class was not allowed by the BSR and the MAB for the DefEMUp service
class was adjusted downward to 40%.
Upstream Service Classes
Service Class mab cap priority

-------------------------------------------------
DefBEUp 10 0 1
DefRRUp 10 0 1
DefUGS 10 100 1
DefUGSAD 10 80 1
DefRTPS 10 5 1
DefNRTPS 10 5 1
DefEMUp 40 100 1
Total assigned bandwidth (mab sum): 100%
Maximum Assigned Bandwidth Override

The cable upstream max-calls command now overrides the service class Maximum
Assigned Bandwidth (MAB) parameter for Voice-over-IP (VOIP) admission.
Prior to this release, the Default Unsolicited Grant Service (DefUGS) service class
Maximum Assigned Bandwidth (MAB) parameter had to always be assigned to
reserve sufficient bandwidth to admit Voice-over-IP (VOIP) flows. Because you can
only configure service class MAB parameters globally, installations with different
capacity upstream channels were forced to set the DefUGS MAB to a percentage
based on the lowest-capacity channel. This reserved an unnecessarily high DefUGS
MAB percentage on the high-capacity channels, permitting inappropriate
over-admission of VOIP and preventing sufficient granularity of MAB assignment to
other service classes. If the cable interface mode configuration command cable
upstream <port> max-calls <n> was configured, both the DefUGS MAB and the
cable upstream max-calls conditions must have been satisfied in order to admit the
VOIP call.
With this release, if cable upstream max-calls is configured, it overrides the VoIP
admission control check for the DefUGS (or DefUGSAD) MAB on that channel.
Installations which configure cable upstream max-calls on all upstream channels

should set the DefUGS (and DefUGSAD) MAB to its minimum value of one percent,
since the MAB setting for those service classes will be ignored for purposes of
admission control.
Note: Once admitted, UGS and UGSAD scheduling type upstream flows are
always granted bandwidth with higher priority than best-effort scheduling type
flows .
Modifying Service Class Parameters

Follow these options to make adjustments to service class parameters for either a
default service class or a created service class:
Configured Active Percent (CAP) is used to estimate the percent of service flows
which are likely to be simultaneously active since all service flows are not active
simultaneously. Use the cap command in Cable Service Class mode to specify the
amount of over-booking for a service class:
Note: CAP can be specified for a service class that has a minimum reserved
traffic rate. Overbooking for UGS classes is not permitted. The CAP
parameter is fixed at 100 percent. The CAP parameter for UGS-AD classes
may not be set to less than 80 percent (25 percent overbooking).
MOT:7A(config-srvclass)#cap <WORD> <0-100>

where:
0-100 is the percent of service flows belonging to this service class that can
be simultaneously active on an interface.
For example, if the CAP for a service class is set to 20 percent then 5 X (1 / 0.2)
overbooking would be allowed. If set to 100 percent then no overbooking would
be permitted. If set to 0 then unlimited overbooking would be permitted.

Scheduling priority determines the order in which service classes are serviced.
All service flows belonging to a service class with a higher scheduling priority
are serviced before service flows belonging to service classes with a lower
scheduling priority. Use the schedpriority command in Cable Service Class
mode to assign a scheduling priority to the service class that you are configuring:
Note: The scheduling priority is different from the traffic priority DOCSIS QoS
parameter that is specified to characterize a priority for service flows that
have identical QoS parameter sets.
MOT:7A(config-srvclass)#schedpriority <WORD> <1-32>

where:
1-32 is the priority of this service class.
Note: The larger the priority number is, the higher the priority it has.
The admitted bandwidth threshold is used to generate an event trap for a service
class on a per-interface basis when the admitted bandwidth falls below the
threshold. Use the admitted-bw-threshold command in Cable Service Class
mode to configure the admitted bandwidth threshold value for this service class:
MOT:7A(config-srvclass)#admitted-bw-threshold <WORD> <0-100>
where:
0-100 is the threshold expressed as percent of the admitted bandwidth.
Use the trafpriority command in Cable Service Class mode to specify the
relative priority of service flows with identical QoS parameters:
MOT:7A(config-srvclass)#trafpriority <WORD> <1-7>

where:
1-7 is the traffic priority of the service flows used by this service class.
Use the max-rate command in Cable Service Class mode to control the
maximum sustained traffic rate of a service flows in a service class:
MOT:7A(config-srvclass)#max-rate <WORD> <0-4294967295>
where:
0-4294967295 is the maximum rate number in bits per second.
Use the max-burst command in Cable Service Class mode to control the
maximum traffic burst size at the transmission line rate of a service flows in a
service class:
MOT:7A(config-srvclass)#max-burst <WORD> <1522-65535>
where:
1522-65535 is the maximum burst size at the transmission line rate of a
service flow in bytes or the value of the maximum concatenated burst size
QoS parameter.
Use the min-rate command in Cable Service Class mode to specify the
guaranteed or reserved traffic rate of a service flows in a service class:
MOT:7A(config-srvclass)#min-rate <WORD> <0-4294967295>
where:
0-4294967295 is the guaranteed or reserved minimum number of bits per
second.

Use the min-pkt-size command in Cable Service Class mode to specify the
minimum packet size for a service flows in a service class with a reserved traffic
rate:
Note: Packets sent on the service flow which are smaller than the assumed
minimum packet size are considered to be the assumed minimum packet
size.
MOT:7A(config-srvclass)#min-pkt-size <WORD> <64-1522>

where:
64-1522 is the assumed minimum packet size in bytes.
Use the max-concat-burst command in Service Class configuration mode to
specify the maximum size, in bytes, of a concatenated upstream burst from CMs:
MOT:7A(config-srvclass)#max-concat-burst <WORD> <0-65535>
where:
0-65535 is the maximum upstream burst size.
Use the activity-timeout command in Cable Service Class mode to specify the
amount of time that an active service flow can be unused if there is no activity on
the service flow within the time-out interval:
MOT:7A(config-srvclass)#activity-timeout <WORD> <0-65535>
where:
0-65535 is the timeout in seconds.
Use the admission-timeout command in Cable Service Class mode to specify the
amount of time that reserved resources are allowed to exceed the active time-out
of the service flow. Reserved service flow resources are released when a Dynamic
Service Change (DSC) message is received by the CMTS from a CM after the
admission time-out interval expires.
MOT:7A(config-srvclass)#admission-timeout <WORD> <0-65535>

where:
0-65535 is the time-out in seconds.
Use the req-trans-policy command in Cable Service Class mode to specify
which Interval Usage Code (IUC) opportunities a CM may use for upstream
requests and packet transmissions, whether requests for bandwidth can be
piggy-backed with packet transmissions, and if data transmissions are
concatenated, fragmented or payload header suppression (PHS) is allowed:
MOT:7A(config-srvclass)#req-trans-policy <WORD> <0x0-0x7fff>
where:
0x0-0x7fff is the policy bit mask.
Use the poll-interval command in Cable Service Class mode to specify the
nominal interval between unicast request opportunities. The nominal polling
interval is relevant for service flows using UGS-AD scheduling, real-time, and
non-real time polling scheduling.
MOT:7A(config-srvclass)#poll-interval <WORD> <0-4294967295>
where:
0-4294967295 is the polling interval in micro-seconds.
Use the poll-jitter command in Cable Service Class mode to specify the interval
in which unicast requests may be delayed from nominal polling, as shown below:
Note: The tolerated poll jitter feature is relevant only for service flows using
UGS-AD and real-time polling scheduling.
MOT:7A(config-srvclass)#poll-jitter <WORD> <0-4294967295>

where:
0-4294967295 is the interval in micro-seconds.

Use the grant-size command in Cable Service Class mode to specify the size of
the unsolicited grant
Note: The unsolicited grant size function is relevant only for service flows
using UGS or UGS-AD scheduling.
MOT:7A(config-srvclass)#grant-size <WORD> <0-65535>

where:
0-65535 is the number of bytes.
Use the grant-interval command in Cable Service Class mode to specify the
apparent or nominal time between grants:
Note: The nominal grant interval function is relevant only for service flows
MOT:7A(config-srvclass)#grant-interval <WORD> <0-4294967295>

where:
0-4294967295 is the number of microseconds permitted between grants.
Use the grant-jitter command in Cable Service Class mode to specify the
amount of time that a grant may be delayed past the nominal grant interval:
Note: The grant-jitter command is relevant only for service flows using UGS
or UGS-AD scheduling.
MOT:7A(config-srvclass)#grant-jitter <WORD> <0-4294967295>

where:


0-4294967295 is the number of microseconds permitted past the nominal
grant interval.
Use the grants-per-interval command in Cable Service Class mode to specify
the number of data grants per grant interval:
Note: The grants-per-interval command is relevant only for service flows

MOT:7A(config-srvclass)#grants-per-interval <WORD> <0-127>

where:
0-127 is the number of grants permitted past the nominal grant interval.
Use the tos-overwrite command in Cable Service Class mode to provide an
AND and OR mask that the CMTS uses to overwrite the type of service (TOS)
field on all upstream IP packets on a service flow
Note: If the TOS and mask is omitted, then the TOS field on upstream IP
packets are not modified by the CMTS.
MOT:7A(config-srvclass)#tos-overwrite <WORD> <0x0-0xff>

<0x0-0xff>
where:
0x0-0xff is the TOS defined in hexadecimal format.
0x0-0xff is the optional numerical mask in hexadecimal format for the TOS.

Use the max-latency command in Cable Service Class mode to specify a

maximum delay between when a packet is received on a network interface and
transmitted on a cable downstream interface:
Note: This max-latency applies only to downstream service flows.
MOT:7A(config-srvclass)#max-latency <WORD> <0-4294967295>

where:
0-4294967295 is the delay in microseconds.
Use the over-max-rate command in Cable Service Class mode to increase the
maximum sustained rate for voice calls on a cable downstream interface:
Note: The over-max-rate command only applies to downstream service

flows.
A setting of 100% (the default) will have the effect of disabling rate limting for
voice calls.
MOT:7A(config-srvclass)#over-max-rate <0-100>
where:
0-100 is the amount of increase, specified as a percent of the configured max
rate. The default is 100%.

Viewing Service Class Information

Use the following sections to display service flow and service class information:
Displaying Service Class Statistics

If you want to view statistics for a service class on the BSR, issue the show cable
srvclass-stats command in Service Class Configuration mode:
MOT:7A(config-srvclass)#show cable srvclass-stats [<X/Y> <WORD>]
where:
Displaying Service Flow Parameters

Use the show cable qos svc-flow param-set command to display the service flow
parameter set for all service flows, a specific cable interface, or a specific service
flow:
MOT:7A#show cable qos svc-flow param-set [<X/Y>] [<1-4292967295>]
where:

Displaying Service Class Information

Use the show cable service-class command, in all modes except User EXEC, to
display a configuration summary for all service classes, including all default service
classes, that are active on the BSR:
Note: The complete configuration of an individual service class can also be

displayed.
MOT:7A#show cable service-class [<WORD>]

where:
WORD is a user-defined service class created with the name command or one of
the default service classes.
Use the show interfaces cable service-class command, in all modes except User
EXEC, to display interface level service class information for all downstream and
upstream service classes, downstream service classes, or upstream service classes that
are active on the BSR:
MOT:7A#show interfaces cable <X/Y> service-class [all | downstream | upstream]
where:
all displays both upstream and downstream service class information
downstream displays downstream service class information only
upstream display upstream service class information only

Displaying Service Flow Statistics

Follow these steps to find an SFID and display service flow statistics for the desired
SFID:
1. Use the show cable modem svc-flow-id command in Privileged EXEC mode to
display the Service Flow ID (SFID) of all the service flows used by a specific
CM, which includes the upstream or downstream channel direction and the
maximum sustained flow rate for the SFID in bits-per second:
Note: "no restriction" indicates that there is no traffic rate limit for this service.
MOT:7A#show cable modem {<mac> | <prefix>} svc-flow-id

where:
mac is the CM MAC address.
prefix is the CM IP address.
Figure Figure displays typical show cable modem svc-flow-id command output for
a specific CM:
Service flow id Interface Flow Direction Flow Max Rate

51 cable 5/0 Upstream no restriction
52 cable 5/0 Downstream no restriction
Figure show cable modem svc-flow-id Command Output

2. Use the show cable qos svc-flow statistics command to display the service flow
statistics for all service flows, a specific cable interface, or a specific service
flow:
MOT:7A#show cable qos svc-flow statistics [<X/Y>] [<1-4292967295>]
where:
Displaying Service Class Statistics

If you want to view statistics for a service class on the BSR, issue the show cable
srvclass-stats command in Service Class Configuration mode:
MOT:7A(config-srvclass)#show cable srvclass-stats {<X/Y>} {<NUM>}
{<WORD>}
where:
X is the slot number.
Y is the MAC Domain number.
NUM is the port number on the specified MAC Domain.

Voice Call Statistics

The following sections provide information for configuring, viewing, clearing and
disabling voice calls:
Configuring a Voice Call Statistics Sample
Viewing Active Voice Call Statistics
Clearing Active Voice Call Statistics
Disabling Active Voice Call Statistics
Configuring a Voice Call Statistics Sample

The default voice call statistics sample is 60 minutes. Follow these steps to configure
a voice call statistics sample:
Service Class Configuration mode:
MOT:7A(config)#cable service-class
2. Use the ugs-stats-window command in Service Class Configuration mode to
configure the UGS Flow Voice Call statistics sample period.
MOT:7A(config-srvclass)#ugs-stats-window {<0> | <5-120>}
where:
0 disables UGS Flow Statistics sampling
5-120 is UGS Flow Statistics sampling time interval in minutes
Viewing Active Voice Call Statistics

Use the show cable ugs-stats command in all modes except User EXEC mode to
determine how many calls are active on a given BSR upstream port at a specific time.
MOT:7A#show cable ugs-stats <0-15> <0-7>
where:
0-15 is the DOCSIS module number.
0-7 is the upstream port number

Figure Figure displays the active voice calls on a specified upstream port after 1
minute.
US Interface slot/port: 4/1

Current flow count: 3
Flow count Max (last 5 min window): <Valid in 5 minute(s)>
Flow count Min (last 5 min window): <Valid in 5 minute(s)>
Flow count Ave (last 5 min window): <Valid in 5 minute(s)>
Flow count Max (last 10 min window): <Valid in 10 minute(s)>
Flow count Min (last 10 min window): <Valid in 10 minute(s)>
Flow count Ave (last 10 min window): <Valid in 10 minute(s)>
Figure Active Voice Calls on a Specified Upstream Port
Figure Figure displays the active voice calls on a specified upstream port after 10
minutes.
US Interface slot/port: 4/1

Current flow count: 3
Flow count Max (last 5 min window): 3
Flow count Min (last 5 min window): 3
Flow count Ave (last 5 min window): 3
Flow count Max (last 10 min window): 3
Flow count Min (last 10 min window): 3
Flow count Ave (last 10 min window): 3
Figure Active Voice Calls on a Specified Upstream Port
The Current Flow Count output field is updated every time statistics are displayed.
The Maximum, Minimum and Average UGS flow counts for voice calls are updated
once every minute to display their status within the configured sample period. Once
enough samples are collected, these statistics become valid.

Clearing Active Voice Call Statistics

Use the clear cable ugs-stats command in all modes except User EXEC mode to
clear active voice call statistics for all CMTS modules, a specified CMTS module, or
a specified upstream port on a CMTS module.
MOT:7A#clear cable ugs-stats [<0-15> [<0-7>]]
where:
0-15 is the DOCSIS (CMTS) module slot number.
0-7 is the upstream port number.
Disabling Active Voice Call Statistics

Follow these steps to disable active voice call statistics:
Service Class Configuration mode.
MOT:7A(config)#cable service-class
2. Use the ugs-stats-window 0 command in Service Class mode to disable active
voice call (UGS Flow) statistics.
MOT:7A(config-srvclass)#ugs-stats-window 0

10
Setting QoS Parameters
Introduction
This chapter describes how to configure Quality of Service (QoS) using service flows.
Use the commands in this section to create, change, or delete service flows with
Dynamic Service Addition (DSA), Dynamic Service Change (DSC), and Dynamic
Service Deletion (DSD) MAC management messages. Configuring QoS involves the
following tasks:
Creating or Modifying a QoS Profile
Deleting a QoS Profile
Viewing a QoS Profile
Initiating a DSA
Initiating a DSC
Initiating a DSD
Configuring an Active Timeout for Dynamic Service Flows
Viewing QoS Information

Creating or Modifying a QoS Profile

A QoS Profile is used for authentication and bandwidth management of DOCSIS1.0
and DOCSIS1.0+ cable modems. QoS Profiles are either learned from the cable
modem during registration or a new QoS Profile can be created through the Command
Line Interface (CLI). The parameters of a QoS Profile can also be modified through
the CLI.
To create a new QoS Profile or modify an existing QoS profile, do the following:
1. Use the cable qos-profile command to enter QoS Profile Configuration mode, as
follows:
MOT:7A(config)#cable qos-profile <prof-num>
where:
prof-num is the QoS Profile identifying number.
Note: Only QoS Profile numbers 1-16 are user configurable.
The command line prompt changes to the following:

MOT:7A(config-qosprof:<prof-num>)#
2. Use the following commands to create or modify the QoS Profile.
baseline-privacy
guaran-us-bandwidth
max-ds-bandwidth
max-us-bandwidth
max-us-burst
priority
tos-mask
tos-value
grant-interval
grant-size
name

Release 5.3.1 Setting QoS Parameters
For example:
To configure the grant-interval and grant-size, you would do the following:
MOT:7A(config-qosprof:prof-num>)# grant-interval 20
MOT:7A(config-qosprof:prof-num>)# grant-size 229
The QoS Profile parameters are described in detail in Table Table . To verify a QoS
Profile configuration refer to Viewing a QoS Profile.
Table QoS Profile Parameters
QoS Profile Description Default

baseline-privacy <0-1> "0" indicates that Baseline Privacy is not 0
enabled for this QoS profile
"1" indicates that Baseline Privacy is enabled
for this QoS profile -
guaran-us-bandwidth The guaranteed minimum upstream rate in 0
<0-10000000> bits per second. "0" indicates no minimum
upstream rate.
max-ds-bandwidth The maximum downstream data rate in bits 0
<0-10000000> per second that a modem using this QoS
profile will receive. "0" indicates no
downstream rate limit.
max-us-bandwidth The maximum upstream data rate in bits per 0
<0-10000000> second that a modem using this QoS profile
will receive. 0" indicates no upstream rate
limit.
max-us-burst The maximum upstream transmit burst size in 0
<0-10000000> bits per second that the modem can send for
any single transmit burst. "0" indicates no
burst size limit.
priority <1-7> The relative priority number assigned to 1
upstream traffic by this QoS profile with 7
being the highest priority.
tos-mask <0-255> Overwrites the Type of Service (TOS) field in 0
IP datagrams received on the upstream
before forwarding them downstream if the
value is not "0". This parameter sets the
hexadecimal mask bits to a hexadecimal
value to help the CMTS identify QoS
datagrams for QoS on the IP backbone.

Table QoS Profile Parameters
QoS Profile Description Default

tos-value <0-255> The overwrite value substituted for the 0
received TOS value.
grant-interval <0-65535> The grant interval in milliseconds. The grant 0
interval specifies the nominal time between
grants.
grant-size <0-65535> The grant size in bytes.The grant size 0
specifies the unsolicited grant size. Grant size
includes the entire MAC frame data PDU from
the Frame Control byte to end of the MAC
frame.
name WORD The ASCII string identifier for the QoS Profile NULL string
to a maximum of 30 characters.
Resetting the Default Values

Use the no qualifier for each of the QoS Profile parameters described in Table Table
to reset the parameters default value.
For example:
The following would reset the maximum downstream rate limit to "0" (no
downstream rate limit):
MOT:7A(config-qosprof:<prof-num>)#no max-ds-bandwidth
Deleting a QoS Profile

Use the no cable qos-profile command, in Global Configuration mode, to delete a
QoS Profile as follows:
MOT:7A(config)#no cable qos-profile <prof-num>
where:
prof-num is the QoS Profile identifying number from 1-16.
Note: Only QoS Profile numbers 1-16 can be deleted with the no cable
qos-profile command.

Viewing a QoS Profile

The show running-config and show cable qos profile commands can be used to
view QoS Profile configurations.
Use the show running-config command to view all QoS Profiles, as follows:
MOT:7A#show running-config | begin cable qos
Use the show running-config command to view a specific QoS Profile, as
follows:
MOT:7A#show running-config | begin cable qos profile<<prof-num>
Use the show cable qos profile command, to view all QoS Profiles, as follows:
MOT:7A#show cable qos profile
Note: The show cable qos profile command without any argumanets
displays all user-configured QoS profiles on the BSR regardless of whether
they are in use. The show cable qos profile command without arguments
does not display any QoS profiles that have been learned via modem
registration.
The show cable qos profile command with the <NUM> argument displays
all active Qos Profiles either user-configured or learned via modem
registration for the specified CMTS slot.
Use the show cable qos profile NUM command, to view learned and configured
(in use) QoS Profiles for a particular CMTS, as follows:
MOT:7A#show cable qos profile NUM
where:
NUM is a CMTS slot number on the BSR.
Use the show cable qos profile [NUM [<1-32>]] command, to view a specific
QoS Profile for the specified Profile Index of the specified CMTS, as follows:
MOT:7A#show cable qos profile [NUM [<1-32>]]
where:
NUM is a CMTS slot number on the BSR 64000.
1-32 is the Qos Profile index (identifying number).

Use the show cable qos profile mac command, to add the MAC addresses of
cable modems to the display output for the specified profile (with active flows) of
the specified CMTS, as follows:
MOT:7A#show cable qos profile [<NUM> [<1-32> [mac]]]
where:
NUM is a CMTS slot number on the BSR 64000.
1-32 is the Qos Profile identifying number.
mac causes the MAC Address for each modem
the show cable qos profile commands.
Note: The "Prof Idx" field in the show cable qos profile command output
indicates a user configured QoS Profiles unique identifying number in the
range of 1-16. All QoS Profile identifying numbers in the range of 17-32
indicate a QoS Profile that was learned from cable modem registrations.
Initiating a DSA
The cable modem qos dsa command triggers the CMTS to send a Dynamic Service
Change (DSC) message to create a new service flow for a specified cable modem
(CM). The Dynamic Service Addition (DSA) is defined in the CM configuration file.
The current implementation has only the change of service based on service-flow (not
the flow classifier, nor the payload-header-suppression).
Note: Before you begin, ensure that the correct DSA definition is entered in
the CM configuration file, which is saved in the TFTP "boot" directory on a
TFTP server with a known IP address.
Follow these steps to cause the CMTS to initiate DSA messages on an existing service
flow for a CM:

1. Use the cable modem qos dsa command in Privileged EXEC mode to create a
new service flow:
Warning: This command should be used with extreme caution as the

dynamic service definition in the CM configuration file is overwritten.
MOT:7A#cable modem {<mac> | <prefix>} qos dsa {<prefix> <string>}

where:
prefix is the TFTP server IP address.
string is the CM configuration file name.
2. Use the show cable qos svc-flow dynamic-stat command to display statistics for
dynamic service additions, deletions, and changes for both upstream and
downstream service flows:
MOT:7A#show cable qos svc-flow dynamic-stat
Refer to the BSR 64000 Command Reference Guide to see typical screen output
for the show cable qos svc-flow dynamic-stat command.
Initiating a DSC
Follow these steps to cause the CMTS to initiate DSC messages on an existing service
flow for a CM.
Note: Before you begin, ensure that the correct DSA definition is entered in
the CM configuration file. Also ensure that the DSC definition applies to each
SFID. The CM configuration file must contain the correct SFID for the service
flow you change.

display the Service Flow ID (SFID) of all the service flows used by a specific
CM, which includes the upstream or downstream channel direction and the
maximum sustained flow rate for the SFID in bits-per second:
Note: "no restriction" indicates that there is no traffic rate limit for this service.
MOT:7A#show cable modem {<mac> | <prefix>} svc-flow-id

where:
for the show cable modem svc-flow-id command.
2. Use the cable modem qos dsc command in Privileged EXEC mode to change an
existing service flow:
MOT:7A#cable modem {<mac> | <prefix>} qos dsc {<prefix> <string>}
where:
prefix is the TFTP server IP address.
string is the CM configuration file name.

3. Use the show cable qos svc-flow statistics command in Privileged EXEC mode
to display service flow statistics:
MOT:7A#show cable qos svc-flow statistics [<X/Y> [<1-4292967295>]]
where:
1-4292967295 is the Service Flow Identifier (SFID) number.
4. Use the show cable qos svc-flow dynamic stat command in Privileged EXEC
mode to display statistics for both upstream and downstream DSC messages:
MOT:7A#show cable qos svc-flow dynamic stat
the show cable qos svc-flow commands.
Initiating a DSD
Follow these steps to cause the CMTS to initiate DSD messages to delete an existing
service flow for a CM:
Note: Before you begin, ensure that the correct CM SFID is selected.
display the SFID of all the service flows used by a specific CM:
MOT:7A#show cable modem [<mac> | <prefix>] svc-flow-id
where:
2. Use the cable modem qos dsd command in Privileged EXEC mode to initiate the
DSD of a specific SFID:
MOT:7A#cable modem qos dsd {<X/Y> <1-262143>}

where:
3. Use the show cable qos svc-flow log command in Privileged EXEC mode to
display the deleted service flow log:
MOT:7A#show cable qos svc-flow log
4. Use the show cable qos svc-flow dynamic stat command in Privileged EXEC
mode to display statistics for both upstream and downstream DSD messages:
MOT:7A#show cable qos svc-flow dynamic stat
the show cable qos svc-flow commands.
Configuring an Active Timeout for Dynamic

Service Flows
CMs dynamically request resources to CMTS such as service flow identifiers (SFIDs)
and bandwidth by using a Dynamic Service Addition (DSA) transaction. If the CM
fails to issue a Dynamic Service Deletion Request (DSD-REQ) to the CMTS or the
DSD-REQ is being dropped for any reasons (e.g. due to noise), these resources could
be held by the CMTS indefinitely. For this reason, an active timeout interval could be
configured on the cable interface so that the CMTS can remove the dynamic service
flows by issuing the DSD-REQs to the CM when the timer expires. The default for the
active timeout interval is zero, which is disabled.
Follow these steps to set the active timeout for dynamic service flows:
appropriate cable interface:
where:
2. Use the cable dynamic-service active-timeout command in Interface
Configuration mode to set the active timeout for CMs to release unused dynamic
service flow resources:

MOT:7A(config-if)#cable dynamic-service active-timeout <0-65535>

where:
0-65535 is the active timeout value in seconds - "0" disables the active timer.
Note: If the CM requests an active timeout for that dynamic service flow in
the Dynamic Service Addition Request (DSA-REQ), this active timer starts
using the timeout value specified in the DSA-REQ.
Viewing QoS Information

Use the following sections to obtain QoS information:
Displaying the Packet Classifier
Displaying SFID and QoS Information
Displaying Upstream Service Flow Statistics
Displaying Payload Header Suppression Entries
Displaying QoS Profiles
Displaying the Packet Classifier

A service flow classifier matches a packet to a service flow using a service flow
reference. The service flow reference associates a packet classifier encoding with a
service flow encoding to establish a SFID. Classifiers have the following features:
Classifiers are loosely ordered by priority.
Several classifiers can refer to the same service flow.
More than one classifier may have the same priority.
The cable interface uses a downstream classifier to assign packets to downstream
service flows.
The CM uses an upstream classifier to assign packets to upstream service flows.
Use the show cable qos svc-flow classifier command to display the packet classifiers
of a service flow configured on the cable interface:
MOT:7A#show cable qos svc-flow classifier [<X/Y> [<1-4292967295>]
[<1-65535>]]]

where:
1-65535 is the classifier identifier..
Note: If the Classifier ID is not given, all the classifiers with the given SFID
are listed.
the show cable qos svc-flow classifier command.
Displaying SFID and QoS Information

Use the show cable qos svc-flow summary command to display service flow
identifier (SFID) and QoS parameter information:
MOT:7A#show cable qos svc-flow summary [<X/Y> [<1-4292967295>]]
where:
the show cable qos svc-flow summary command.

Use the show cable qos svc-flow statistics command to display service flow
statistics:
MOT:7A#show cable qos svc-flow statistics [<X/Y> [<1-4292967295>]]
where:
the show cable qos svc-flow statistics command.

Displaying Upstream Service Flow Statistics

Use the show cable qos svc-flow upstream-stat command to view upstream service
flow statistics, which includes the number of fragmented packets, incomplete
fragmented packets, and the number of concatenated bursts:
MOT:7A#show cable qos svc-flow upstream-stat [<X/Y> [<1-65535>]]
where:
the show cable qos svc-flow upstream-stat command.
Displaying Payload Header Suppression Entries

Use the show cable qos svc-flow phs command to display the Payload Header
Suppression (PHS) entries for a service flow:
MOT:7A#show cable qos svc-flow phs [<X/Y> [<1-4292967295> [<1-65535>]]]
where:
1-65535 is the classifier identifier.
Note: If the Classifier ID is not given, all the classifiers with the given SFID
are listed.

Displaying QoS Profiles

Use the show cable qos profile command to display the priority, bandwidth
allocation, and baseline privacy information for all QoS profiles or a selected QoS
profile which applies to DOCSIS 1.0, DOCSIS 1.0+, and Euro-DOCSIS 1.0 cable
modems, as follows:
MOT:7A#show cable qos profile [<NUM> [<1-32> [mac]]]
where:
NUM is the CMTS slot number.
1-32 is the Qos Profile index (identifying number).
Note: The "Prof Idx" field output indicates a user configured QoS Profiles
unique identifying number in the range of 1-16. All QoS Profile identifying
numbers in the range of 17-32 indicate a QoS Profile that was learned from
cable modem registrations.
mac adds the MAC addresses of the cable modems to the display.
Note: The show cable qos profile command without any argumanets
displays all user-configured QoS profiles on the BSR regardless of whether
they are in use. The show cable qos profile command without arguments
does not display any QoS profiles that have been learned via modem
registration.
The show cable qos profile command with the <NUM> argument displays
all active Qos Profiles either user-configured or learned via modem
registration for the specified CMTS slot.
and output descriptions for the show cable qos profile commands
Notes About Viewing Class of Service (Qos) Profiles

When using the show cable qos profile command to view the class of service
configuration for DOCSIS 1.0 and Euro-DOCSIS 1.0 modems, you will obtain
inconsistent results under the following conditions.

When you have not given each class of service (QoS Profile) a unique classID (in
the range 1 through 16) in the CM configuration file.
When you modify a CMs configuration file and specify parameter values that are
already in use by other registered modems and fail to change the class of service
ID to a unique value.
However, all registered CMs are using the class of service (QoS) parameters as
defined in their respective configuration files, only the displayed output of the show
cable qos profile command that is inconsistent.
Once all DOCSIS 1.0, DOCSIS 1.0+, and Euro-DOCSIS 1.0 classes of service have
unique classIDs, the display of the show cable qos profile command is accurate.

Configuring the BSR 64000 for DOCSIS 1.0+

Interoperability
In order for the BSR 64000 to register DOCSIS 1.0+ cable modems successfully, the
BSR 64000 must be configured to accept and process DSA-REQs from DOCSIS 1.0+
devices.
Follow these steps to configure the BSR 64000 for interoperability with DOCSIS 1.0+
cable modems.
1. Use the configure command to enter Global Configuration mode.
MOT:7A#configure
The prompt changes to MOT:7A(config)# indicating that the CLI is accepting
commands in Global Configuration mode.
2. Use the interface cable command to select the cable interface from Global
Configuration mode.
where:
3. Use the cable dynamic-service authorization-mode unauthorize command
from Interface Configuration mode to allow the cable interface to accept
DSA-REQs from DOCSIS 1.0+ cable modems.
MOT:7A(config-if)#cable dynamic-service authorization-mode unauthorize
After issuing the command, a message similar to the following is displayed on the
console.
MOT:7A(config-if)#[05/14-15:22:31.31-
07:console]-N-configuration change by [console]: cable
dynamic-service authorization-mode unauthorize
4. Use the show running configuration command with the following parameters to
verify that the cable dynamic-service authorization-mode unauthorize
command was accepted by the BSR.
MOT:7A#show run | begin interface cable <X/Y>
where:

The command will display output similar to the following. Find the line cable
dynamic-service authorization-mode unauthorize to confirm that the command
issued in Step 3 was accepted by the BSR.
interface cable 11/0

cable bundle 1
no ip address
no shutdown
cable bind downstream 0
cable downstream 0 modulation 64
cable downstream 0 power-level 630
no cable downstream 0 shutdown
cable bind upstream 0,1,2,3,4,5,6,7
cable upstream 0 modulation-profile 2
cable upstream 0 shutdown
cable upstream 1 frequency 10000000
cable upstream 1 channel-width 1600000
cable upstream 1 modulation-profile 2
cable upstream 1 spectrum-group srv-grp1
no cable upstream 1 shutdown
cable upstream 2 frequency 30000000
cable upstream 2 spectrum-group srv-grp1
cable dynamic-service authorization-mode unauthorize
ip dhcp relay information option
5. Define the following five QoS Profiles in the BSR 64000 running configuration
file. Refer to the section, Creating or Modifying a QoS Profile, earler in this
chapter.
cable qos profile 12 guaranteed-upstream 221
cable qos profile 12 max-upstream 221
cable qos profile 12 grant-size 149
cable qos profile 12 grant-interval 5
cable qos profile 12 name CALLS_4_AT_10MSEC


cable qos profile 15 name CALLS_2_AT_10MSEC_2FLOWS
6. Save your current running configuration as your startup configuration using the
copy running-config startup-config command in Privileged EXEC mode:
MOT:7A#copy running-config startup-config
Caution: If you do not save your current running configuration to your startup
configuration, your running configuration will be lost when the BSR is
rebooted.
Verifying that DOCSIS 1.0+ Devices Successfully Register

There are two ways to verify that DOCSIS 1.0+ devices successfully register and that
the BSR 64000 recognizes them.

Review the EVT messages displayed on the console. The following information
EVT should be displayed on the console if a cable modem has successfully
registered as DOCSIS 1.0+:
[05/14-15:28:58.09- 11:REG]-I- REG.15 DOCSIS 1.0+ enabled
for CM, for MAC add r: 0008.0e16.fafe
Use the show cable modem mac command. The output of the command
indicates DOCSIS version for each cable modem as shown below.
MAC Address MAC Prim DOC Qos Frag Con PHS Priv DCC DS US Dev
State SID Ver Prov Saids Sids
0011.805f.fd30 online 2 2.0 1.1 yes yes yes BPI+ yes 15 16 eCM
0011.8061.3f0e online 1 2.0 1.1 yes yes yes BPI+ yes 15 16 eCM
000b.0643.33fc online 195 1.0+ 1.0 no yes no BPI no 0 0 CM
000b.0643.3718 online 203 1.0+ 1.0 no yes no BPI no 0 0 CM
0020.409a.24c8 online 194 1.1 1.0 no no no BPI no 0 0 CM
00e0.0c60.2854 online 213 1.0 1.0 no no no BPI no 0 0 CM
0011.1ac9.2094 offline 0 1.0 1.0 no no no BPI no 0 0 CM
0011.1aca.1394 online 1 2.0 1.1 yes yes yes BPI+ yes 15 16 eCM
0011.1aca.13a6 online 2 2.0 1.1 yes yes yes BPI+ yes 15 16 eC
Troubleshooting DOCSIS 1.0+ Interoperability

If a phone call cannot be established enable the following EVT from Global
Configuration mode:
MOT:7A(config)#logging evt set c 11:RESSF 1-10
Verify that there are no indications that the grant-interval and grant-size are not
being matched.
If EVT "RESSF.1" is reported, verify that the running configuration file has a QOS
profile configured with the grant-interval and grant-size specified in this EVT.


11
Configuring Spectrum
Management
Introduction
The spectrum management system monitors the upstream signal integrity, and collects
upstream spectrum information. When signal integrity degrades due to noise, the
spectrum management system automatically configures the upstream channel
parameters to maintain low packet loss by changing the upstream frequency,
modulation profile, channel-width and/or power level to ensure that upstream
performance stays at acceptable levels.
The following tasks are used to implement frequency agility on the BSR:
Configuring a Spectrum Group
Applying a Spectrum Group to an Upstream Port
Evaluating Spectrum Management Performance

Configuring a Spectrum Group

Each spectrum group contains spectrum data, a spectrum map, and channel
assignment:
The spectrum data is where the collected spectrum noise information is kept. It
contains the starting frequency, resolution, number of data points, time of the last
measurement, and a pointer to an array where the noise level is kept.
The spectrum map describes the way the upstream spectrum is used for a
particular band. It contains the start and stop frequency, and the current status.
The channel assignment defines the frequency allocation of the upstream channel.
Note: The term "upstream channel" is synonymous to the term "upstream

port".
Each spectrum group also contains the following management information:

Spectrum signal quality information is collected through the spectrum monitoring
process. This information contains the periodic error rate that is computed and
compared with the Forward Error Correction (FEC) error threshold to determine
if spectrum hopping is necessary, and the periodic combination of in-band power
and spectrum data collection to compute signal-to-noise ratio (SNR) for the
upstream channel.
The spectrum schedule contains information on the availability of a certain
frequency band. The band can be made available statically, or available only at
certain time period(s). The actual available spectrum is the super set of all the
bands that are available at the time.
Spectrum hopping rules determine the action taken when the spectrum manager
decides to change the parameters of an upstream channel to combat noise.
Operators can improve upstream channel conditions to combat ingress noise by
specifying hopping rules for upstream frequency changes, upstream frequency
band changes, modulation profile changes, channel-width reduction (until
channel conditions improve), and power adjustments (if it is necessary).

Release 5.3.1 Configuring Spectrum Management
Defining a spectrum group requires performing the following tasks:

Creating a Spectrum Group
Scheduling the Availability of a Spectrum Group Band
Scheduling the Removal of a Spectrum Group Band
Configuring Spectrum Data Collection
Configuring Spectrum Hopping Rules
Configuring the Spectrum Hopping Error Threshold
Configuring the Spectrum Hopping Flap Threshold
Enabling and Disabling Spectrum Roll-back
Configuring the Guard Band
Reviewing the New Spectrum Group Configuration
Creating a Spectrum Group

Follow these steps to create a cable spectrum group:
1. Use the cable spectrum command, in Global Configuration mode, to create a
cable spectrum group and enter Cable Spectrum Group mode in which to
configure your new cable spectrum group:
MOT:7A(config)#cable spectrum <WORD>
where:
WORD is the spectrum group name.
Note: No spaces are allowed for the spectrum group name.
The Cable Spectrum Group mode prompt displays. From this new prompt, all
cable spectrum parameters are configured. For example, if you defined your
group name as spectrum1 the prompt would display as shown below:
MOT:7A(config-spcgrp:spectrum1)#
If you need to delete a spectrum group, use the no cable spectrum
command, in Global Configuration or Cable Spectrum Group mode as shown
below:

MOT:7A(config)#no cable spectrum <WORD>

MOT:7A(config-spcgrp:<WORD>)#no cable spectrum <WORD>
If you need to change to another spectrum group or want to create a new
spectrum group, use the cable spectrum command in Cable Spectrum Group
mode as shown below:
MOT:7A(config-spcgrp:spectrum1)#cable spectrum <WORD>
where:
WORD is the name of a new spectrum group or another spectrum group.
For example:
MOT:7A(config-spcgrp:spectrum1)#cable spectrum2
MOT:7A(config-spcgrp:spectrum2)#
2. Use the band command, in Cable Spectrum Group mode, to define the start and
end frequency band for the spectrum group:
MOT:7A(config-spcgrp:<WORD>)#band {<5000000-42000000>
<5000000-42000000>}
where:
WORD is the spectrum group name that you defined.
5000000-42000000 is the start upstream frequency in Hertz.
5000000-42000000 is the end upstream frequency in Hertz.
For example, if you defined your spectrum1 group to have a start frequency of 8
MHz and an end frequency of 12 MHz your command syntax would look as
shown below:
MOT:7A(config-spcgrp:spectrum1)#band 8000000 12000000
If you need to add another start and end frequency band to the spectrum
group, repeat this step.
If you need to delete a start and end frequency band from a spectrum group,
use the no band command as shown below:
MOT:7A(config-spcgrp:<WORD>)#no band {<5000000-42000000>
<5000000-42000000>}

Scheduling the Availability of a Spectrum Group Band

The time band command is used to schedule when a spectrum group band is
available. The spectrum group band can be made available on either a daily or weekly
schedule.
Follow these steps to schedule the availability of a spectrum group band:
1. Use the cable spectrum command, in Global Configuration mode, to enter Cable
Spectrum Group mode:
Note: If a new availability time for a band is entered for a spectrum group, the
existing availability time for a band must be deleted first.
MOT:7A(config)#cable spectrum <WORD>

where:
The Cable Spectrum Group mode displays for the spectrum group.
2. If you want to schedule the time for when the spectrum group band becomes
available on a daily basis, use the time band command in Cable Spectrum Group
mode:
MOT:7A(config-spcgrp:<WORD>)#time <hh:mm:ss> band
{<5000000-42000000> <5000000-42000000>}
where:
hh:mm:ss is the time of the day, which includes the hour, minute, and second
when the band becomes available.
For example:
The following example defines the 25 MHz to 35 MHz upstream frequency band
as being available daily at 4:00 PM for spectrum group spectrum1:

MOT:7A(config-spcgrp:spectrum1)#time 16:00:00 band 25000000

35000000
3. To schedule the time for when the spectrum group band becomes available on a
weekly basis, use the time band command in Cable Spectrum Group mode:
MOT:7A(config-spcgrp:<WORD>)#time {<day> <hh:mm:ss>} band
{<5000000-42000000> <5000000-42000000>}
where:
day is the three letter abbreviation for day of the week.
hh:mm:ss is the time during the day when the band becomes available.
The following example defines the 21 MHz to 29 MHz upstream frequency band
as being available every Thursday morning at 10:00 AM for spectrum group
spectrum1:
MOT:7A(config-spcgrp:spectrum1)#time Thu 10:00:00 band
21000000 29000000
Deleting an Existing Availability Time for a Band

To delete the existing availability time for a band, use the no time band command in
Cable Spectrum Group mode:
MOT:7A(config-spcgrp:<WORD>)#no time {<day> | <hh:mm:ss>} band
{<5000000-42000000> <5000000-42000000>}
Note: When deleting the time for a band, ensure that the exact day,
hh:mm:ss, and start and end upstream frequencies are used.
where:
day is the three letter abbreviation for day of the week
hh:mm:ss is the time during the day when the band is removed.

5000000-42000000 is the start upstream in Hertz.

Scheduling the Removal of a Spectrum Group Band

Follow these steps to schedule the removal of a spectrum group band:
1. To schedule the time when the spectrum group band is removed on a daily basis,
use the time delete band command in Cable Spectrum Group mode:
Note: If a new removal time for a band is entered for a spectrum group, the
existing removal time for a band must be deleted first.
MOT:7A(config-spcgrp:<WORD>)#time <hh:mm:ss> delete band

{<5000000-42000000> <5000000-42000000>}
where:
The following example determines that the band from 25 MHz to 35 MHz,
belonging to spectrum group spectrum1, is removed every day at 20:00 PM:
MOT:7A(config-spcgrp:spectrum1)#time 20:00:00 delete band
25000000 35000000
The following example determines that the band from 21 MHz to 29 MHz,
belonging to spectrum group spectrum1, is removed every Thursday morning at
11:00 AM:
MOT:7A(config-spcgrp:spectrum1)#time Thu 11:00:00 delete band
21000000 29000000
2. To schedule the time when the spectrum group band is removed on a weekly
basis, use the time delete band command in Cable Spectrum Group mode:
MOT:7A(config-spcgrp:<WORD>)#time {<day> <hh:mm:ss>} delete
band {<5000000-42000000> <5000000-42000000>}

where:
day is the three letter abbreviation for day of the week
For example, the following syntax is used to express that the band from 21 MHz
to 29 MHz, belonging to spectrum group spectrum1, is removed every Thursday
morning at 11:00 AM:
MOT:7A(config-spcgrp:spectrum1)#time Thursday 11:00:00 delete
band 21000000 29000000
Deleting an Existing Removal Time for a Band

To delete the existing removal time for a band, use the no time delete band command
in Cable Spectrum Group mode:
MOT:7A(config-spcgrp:<WORD>)#no time {<day> <hh:mm:ss>} delete
band {<5000000-42000000> <5000000-42000000>}
Note: Ensure that the exact parameters for the removal of a time band are
entered in order for the change to occur.
where:
day is the three letter abbreviation for day of the week.

Configuring Spectrum Data Collection

The spectrum data collection feature can be used to take a 'snapshot' or view of all or
a portion of the upstream spectrum between 5 and 42 MHz to help determine the best
places on the upstream spectrum to configure the hop action frequency and band
values. The spectrum data collection feature is also used to analyze and troubleshoot
the upstream channel when a user does not have access to a spectrum analyzer to view
noise level and signal information. The spectrum data collection feature is disabled by
default and does not need to be enabled in order for spectrum management to work.
The spectrum data collection task is split between the spectrum manager and the
spectrum agent. The spectrum manager schedules the data collection with the
spectrum agent, and provides data storage for the collected data, while the spectrum
agent performs the actual data collection and sends the collected data to the spectrum
manager.
Note: Spectrum data is not collected for an upstream channel until the correct
collection interval is configured for the spectrum group, and the spectrum
group is applied to the upstream port.
Follow these options to change the default spectrum data collection parameters used
by the spectrum manager:
The default resolution is 200000 Hertz (Hz). Use the collect resolution command
in Cable Spectrum Group mode to change the frequency resolution rate that the
spectrum manager performs:
MOT:7A(config-spcgrp:<WORD>)#collect resolution
<200000-4000000>
where:
200000-4000000 is the resolution in Hz.
The default collection interval is 0, which indicates that no collection interval is
defined. Use the collect interval command in Cable Spectrum Group mode to
configure the interval rate at which data collection is performed by the spectrum
manager while it scans the entire spectrum map from 5 MHz to 42 MHz:
MOT:7A(config-spcgrp:<WORD>)#collect interval <60-65535>

where:
60-65535 is the time interval expressed in seconds.
For example, the following syntax shows that the spectrum managers data
collection interval rate for scanning the spectrum map occurs once every hour:
MOT:7A(config-spcgrp:spectrum1)#collect interval 3600
Since the spectrum collection feature uses resources on the upstream channel that
may affect throughput for CMs associated with the upstream port, the spectrum
data collection feature should be turned off when it is no longer in use to conserve
network resources.
Use the no collect interval command to disable the collection interval.
Use the no collect resolution command to disable the frequency resolution.
Configuring Spectrum Hopping Rules

Rules for spectrum hopping must be defined before the spectrum hopping function is
used. Spectrum hopping rules are searched before spectrum hopping occurs on an
upstream port when the spectrum group is triggered. Spectrum hopping rules are used
by the spectrum manager to find the best way to defeat noise problems on an upstream
port.
The following spectrum hopping rules apply:
No actions are taken if spectrum hopping rules are not defined. The rules include
the preferred frequency, modulation profile, channel-width parameters, and
power adjustment.
Multiple hopping rules with same type of action are allowed.
Each hopping rule can be assigned with different priorities.
Hopping rules are applied by priority and hopping rules with same priority are
applied in the order in which they are entered.
If each individual rule fails to apply, the spectrum manager attempts to apply
different combinations of the individual rules.
Follow these steps to configure spectrum hopping rules:
1. The default hop period is 300 seconds. Use the hop period command in Cable
Spectrum Group mode to prevent excessive frequency hops on an upstream port:
MOT:7A(config-spcgrp:<WORD>)#hop period <30-3600>

where:
30-3600 is the rate at which the frequency hop takes place, expressed in
seconds.
2. Use the hop action frequency command in Cable Spectrum Group mode to
determine the frequency hop for discrete center frequencies during the frequency
hop action:
MOT:7A(config-spcgrp:<WORD>)#hop action frequency
<5000000-42000000> [priority <1-255>]
where:
5000000-42000000 is the upstream frequency from 5000000 to 42000000 Hz
1-255 is the priority number of the upstream frequency hop action. When no
priority is assigned, the default priority is 128. The lower number takes
precedence.
For example, the following syntax determines that 28 MHz replaces the existing
upstream frequency when a hop action is triggered and defines the priority level
of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action frequency 28000000
priority 30
3. Use the hop action modulation-profile command in Cable Spectrum Group
mode to change the modulation profile setting for a hop action:
MOT:7A(config-spcgrp:<WORD>)#hop action modulation-profile
<1-16> [priority {<1-255>}]
where:
1-16 is the modulation profile number. The default modulation profiles are 1
and 2.
1-255 is the priority number of the upstream modulation profile hop action.
When no priority is assigned, the default priority is 128.

For example, the following syntax determines that modulation profile 2 replaces
the existing modulation profile when the hop action is triggered and defines the
priority level of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action modulation-profile 2
priority 50
4. Use the hop action channel-width command in Cable Spectrum Group mode to
change the upstream channel-width setting in Hertz (Hz) for a hop action:
Note: Refer to Configuring Upstream Cable Modem Registration Parameters

for more information on setting the upstream channel width.
MOT:7A(config-spcgrp:<WORD>)#hop action channel-width [1600000 |

200000 | 3200000 | 400000 | 800000] [priority <1-255>]
where:
1-255 is the priority number of the upstream channel width setting. When no
priority is assigned, the default priority is 128.
For example, the following syntax determines that the upstream channel width of
1.6 MHz replaces the existing upstream channel width when the hop action is
triggered and defines the priority level of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action channel-width 1600000
priority 100
5. Use the hop action band command in Cable Spectrum Group mode to determine
the hop for each frequency band during the frequency hop action:
MOT:7A(config-spcgrp:<WORD>)#hop action band
{<5000000-42000000> <5000000-42000000>} [priority <1-255>]
where:
5000000-42000000 is the start upstream frequency band in Hz.
5000000-42000000 is the end upstream frequency band in Hz.

1-255 is the priority number of the upstream band hop action. When no
priority is assigned, the default priority is 128.
For example, the following syntax determines that the upstream frequency band
of 20 MHz to 30 MHz replaces the existing upstream frequency band when the
hop action is triggered and defines the priority level of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action band 20000000
30000000 priority 110
6. Use the hop action power-level command in Cable Spectrum Group mode to
change the power-level setting for a hop action:
Note: Refer to the Setting the Upstream Power Level for more information on
setting the upstream power level parameters for relative and absolute mode.
MOT:7A(config-spcgrp:<WORD>)#hop action power-level {<200-3200>

| default < -150 - +150>} [priority <1-255>]
where:
200-3200 is the input power level, expressed in dB.
default -150 - +150> is the number of dB above or below the default input
power level.
1-255 is the priority number of the upstream power level hop action. When
no priority is assigned, the default priority is 128.
The following table describes the input power level parameters expressed in dB:
Power Range Upstream Channel Width

-160 to +140 dB 200 kHz
-130 to +170 dB 400 kHz
-100 to +200 dB 800 kHz
-70 to +230 dB 1600 kHz
-40 to +260 dB 3200 kHz

Configuring the Spectrum Hopping Error Threshold

A frequency hopping error threshold is configured as a criteria to apply the hopping
rules in instances when an unacceptable error rate occurs, which is caused possibly by
the poor signal quality of channel.
The hopping threshold error rate is determined by the Forward Error Correction
(FEC) error-rate threshold value. If the error-rate threshold is configured, the
spectrum manager periodically polls the signal quality table of the member channels
to compute the error rate during the polling interval. If the error rate exceeds the
threshold, it triggers spectrum hopping for the affected channel. The error rate is a
fraction of 1000.
The default hopping threshold error rate is 10 or 1 percent. Use the hop threshold
error command in Cable Spectrum Group mode to adjust the acceptable hopping
threshold error rate:
MOT:7A(config-spcgrp:<WORD>)#hop threshold error {<1-1000>}
where:
1-1000 is the error rate as a fraction of 1000.
For example, an error rate of 1 implies 0.1 percent or an error rate of 1000 implies 100
percent.
Configuring the Spectrum Hopping Flap Threshold

A frequency hopping flap threshold is configured as a criteria to apply the hopping
rules in instances when one or a minimal number of cable modems (CMs) lose their
connection with the BSR (Flap).
The frequency hopping flap threshold is determined by the percentage of CMs that
lose their connectivity. If the flap threshold is configured, the spectrum manager
periodically scans the flap-list table of the member channels to compute the flap rate
during the scan interval. If the flap rate exceeds the threshold, it triggers spectrum
hopping for the affected channel.
This frequency hopping threshold is activated with a value of 0 percent by default to
prevent the unnecessary triggering of a hopping action. For example, if the
downstream cable is disconnected or the downstream frequency is changed, these
actions would cause all CMs on the network to flap.
Use the hop threshold flap command in Cable Spectrum Group mode to set a value
that triggers when a greater than a set percentage of CMs lose their connectivity:

MOT:7A(config-spcgrp:<WORD>)#hop threshold flap {<1-100>}

where:
1-100 is the percentage of CMs from 1 to 100 that lose connectivity on the
network.
If an existing percentage other than zero is set, and you need to take some action that
causes CMs to flap (such as changing the downstream frequency), issue the no hop
threshold flap command in Cable Spectrum Group mode to deactivate the frequency
hopping threshold before taking the action:
MOT:7A(config-spcgrp:<WORD>)#no hop threshold flap <1-100>
where:
1-100 is the set percentage of CMs that lose their connectivity on the network.

Enabling and Disabling Spectrum Roll-back

The spectrum roll-back function is disabled by default and is used to return the
upstream channel width or modulation profile setting, that was adjusted during a hop
action, to the original configuration when upstream channel conditions improve.
Use the hop action rollback command in Cable Spectrum Group mode to enable the
spectrum roll-back function:
MOT:7A(config-spcgrp:<WORD>)#hop action rollback
where:
Use the no hop action rollback command to disable the spectrum roll-back function.
Configuring the Guard Band

Use the guard-band command in Cable Spectrum Group mode to set the minimum
spectrum separation or spacing between upstream channels in the same spectrum
group.
MOT:7A(config-spcgrp:<WORD>)#guard-band {<0-37000000> |
<0-60000000>}
where:
0-37000000 is the guard band separation size expressed in Hertz (Hz) for
DOCSIS. The default guard band is 0 Hz.
0-60000000 is the guard band separation size expressed in Hertz (Hz) for
Euro-DOCSIS. The default guard band is 0 Hz.
Reviewing the New Spectrum Group Configuration

Use the show cable spectrum-group command to review the configuration of the
newly created spectrum group:
MOT:7A(config)#show cable spectrum-group [<WORD>]
where:
Use the show cable spectrum-group map command to view the spectrum allocation
map for the spectrum group that you created:

MOT:7A(config)#show cable spectrum-group <WORD> map

where:
Note: In the show cable spectrum-group map command output, the

SPEC_OCCUPIED message that appears in the Map status column
indicates that this section of the upstream spectrum is occupied by the
upstream channel of the spectrum group. The SPEC_AVAILABLE message
indicates that the section of the upstream spectrum is free to use, and no
upstream channel is currently using this section of the upstream spectrum.
Use the show cable spectrum-group schedule command in Global Configuration

mode to view the spectrum schedule for the spectrum group that you created:
MOT:7A(config)#show cable spectrum-group <WORD> schedule
where:
the show cable spectrum-group commands.
Viewing Your Spectrum Group Configuration

The show running config command does not show the configured parameters if the
spectrum manager makes changes the upstream frequency, channel width, modulation
or power level by hopping action. However, you can issue the show running-config
command in Privileged EXEC mode to view the configuration of a spectrum group
that you created:
For example, the following show running-config command output shows the
configured spectrum group information:
cable spectrum-group spectrum1
time 16:00:00 band 25000000 35000000
time 20:00:00 delete band 25000000 35000000
time Thus 10:00:00 band 21000000 29000000
time Thus 11:00:00 delete band 21000000 29000000
band 17000000 22000000
band 26000000 30000000
collect interval 3600
hop action frequency 28000000 priority 30

hop action modulation-profile 2 priority 50

hop action channel-width 1600000 priority 100
hop action band 20000000 30000000 priority 110
hop action roll-back
Applying a Spectrum Group to an Upstream Port

When a spectrum group is applied to an upstream port, the upstream port belongs to
the spectrum group.
Note: The spectrum manager is unaware of the physical topology of your

cable plant, and it is only aware of the spectrum group. Ensure that you apply
the same spectrum group to all upstream ports that share the same upstream
frequency assignment on the same physical cable plant. Also ensure that the
frequency configurations of different spectrum groups do not overlap if they
share the same physical plant.
Follow these steps to assign a spectrum group to an upstream port on a cable

interface:
Cable Interface Configuration Mode:
where:
2. Use the cable upstream spectrum-group command, in Cable Interface
Configuration mode, to apply a spectrum group to an upstream port:
Note: All upstream ports sharing the same return path must be configured to
the same spectrum group.
MOT:7A(config-if)#cable upstream <NUM> spectrum-group <WORD>

where:
WORD is the exact spectrum group name applied to the upstream port.

3. Use the show cable spectrum-group command to verify if the spectrum group
that you assigned is activated for the upstream port:
MOT:7A(config-if)#show cable spectrum-group [<WORD>]
where:
WORD is the exact group name applied to the upstream port.
4. If you want to see what spectrum group is applied to each upstream port, issue the
show running config command in Privileged EXEC mode:

Evaluating Spectrum Management Performance

Use the information and examples contained in the following sections to evaluate
your spectrum management configuration and performance:
Displaying Spectrum Data
Viewing Spectrum Management Configuration Changes
Determining the Upstream Signal to Noise Ratio
Determining the MIB Index ID Number of an Upstream Port
Viewing Spectrum Management Activity
Viewing Spectrum Management Hopping Actions
Viewing the Spectrum Management Roll-back Function
Displaying Spectrum Data

Use the show interfaces cable upstream spectrum command to view the noise
power level for the whole spectrum:
MOT:7A#show interfaces cable <X/Y> upstream <NUM> spectrum
where:
NUM is the upstream port number
the show interfaces cable upstream spectrum command.

Viewing Spectrum Management Configuration Changes

Follow these steps to view upstream information when the spectrum manager makes
changes to an upstream port:
1. Use the interface cable command to enter Cable Interface Configuration mode:
where:
2. Use the show cable upstream command in Cable Interface Configuration mode
to display the current frequency, channel width, modulation or power level for the
upstream port:
MOT:7A(config-if)#show cable upstream <NUM>
where:
field descriptions for the show cable upstream command.

Determining the Upstream Signal to Noise Ratio

Use the show interfaces cable upstream signal-quality command in Privileged
EXEC mode to determine the signal power to noise ratio, and error signal quality
information as shown below:
MOT:7A#show interfaces cable <X/Y> upstream <NUM> signal-quality
where:
the show interfaces cable upstream signal-quality command.
Determining the MIB Index ID Number of an Upstream Port

It is important to learn the MIB Index ID number that is associated to a specific
upstream port on a DOCSIS module because the debug specmgr and logging console
notifications command log output only displays the MIB Index ID number.
Follow these steps to determine the MIB Index ID number of an upstream port:
1. Use the interface cable command to enter Cable Interface Configuration mode:
where:
2. Use the show cable upstream command to discover what MIB Index ID number
is associated with a upstream port on a particular module as shown below:
MOT:7A(config-if)#show cable upstream <NUM>
where:

The following example shows that upstream port 1 on module 0 has a MIB Index ID
number (ifIndex) of 5. This number is used to determine the slot and upstream port
number that is displayed in the debug specmgr and console logging output.
MOT:7A(config-if)#show cable upstream 1
ifIndex: 5
rng_back_st: 0
rng_back_en: 4
data_back_st: 2
data_back_en: 8
powerLevel: 100
slotSize: 4
force-frag: 0
map-interval: 4000
pre-equalization: 0
invited-range-interval: 10000
range-power-override: 0
rate-limit: 0
modulation-profile: 2
Spectrum Group: spectrum_1
Viewing Spectrum Management Activity

The logging console notifications command can be used to monitor spectrum
management activity whenever the frequency, channel width, modulation profile,
power level changed manually or changed by the Spectrum Manager, the notification
message is displayed.
Use the logging console notifications command in Global Configuration mode to
turn on console logging and view manual changes or changes made by the spectrum
manager:
MOT:7A(config)#logging console notifications
For example, if the upstream frequency was changed to 20000000 Hertz, the
following notification output appears:
[07/23-10:57:17:SPECMGR]-N-Set to new frequency 20000000 for
channel ifIndex = 4 .
[07/23-10:57:17:console]-N-configuration change by
[enabled-user]: cable upstream 0 frequency 20000000

Viewing Spectrum Management Hopping Actions

The debug specmgr command is used to monitor all active upstream ports. The
debug specmgr command output in this section describes what can happen when
spectrum management hopping actions occur.
Note: Ensure that the logging console notifications command is activated so

that you can view spectrum management changes.
The following debug specmgr command output example displays no ingress noise
problems on the active upstream port. The command output displays a time stamp, the
error rate, the number of word errors, total word count, and the upstream noise power
level in one-tenth of a dBmV.
Note: Ensure that you review the criteria for the hop action rules that you
have configured when reviewing the debug specmgr and console logging
output to clearly understand what is happening in the debug specmgr
command output and console logging output.
Use the debug specmgr command in Privileged EXEC mode to monitor one or more
active upstream ports:
MOT:7A#debug specmgr
Note: In the following example, the IfIndex = 7 entry in the debug output
represents a single upstream port on a DOCSIS module.
MOT:7A#[07/23-11:00:08:SPECMGR]-D-Monitor Channel IfIndex = 7 :

[07/23-11:00:08:SPECMGR]-D-Error Rate: 0.0000 %, ErrorWord : 0,
TotalWord : 2901
[07/23-11:00:08:SPECMGR]-D-Channel Noise Power (1/10 dbmv):
-197.

The following command output example displays what happens when the ingress
noise power increases causing the error rate to exceed the error threshold on an
upstream port:
Note: Notice that the noise power level increases.

TotalWord : 3723
[07/23-11:01:58:SPECMGR]-D-Channel Noise Power (1/10 dbmv) :
-152.
[07/23-11:02:08:SPECMGR]-D-Monitor Channel IfIndex = 7 :
[07/23-11:02:18:SPECMGR]-D-Error Rate: 25.8228 %, ErrorWord :
816, TotalWord : 3160
-84.
[07/23-11:02:20:SPECMGR]-D-Updating specTimers
The following command output example displays what happens when the spectrum
manager initiates the first hop action (the hop action rule is 1 with a priority of 30):
TotalWord : 3054
-68.
The following command output example shows that the first hop action succeeded to
set a new frequency, and the desired noise power level is restored.
[07/23-11:03:07:SPECMGR]-N-Set to new frequency 28000000 for
TotalWord : 3781
-198.
If the noise power increases at the new frequency, the next hop action rule is to change
modulation profile (in this example, the hop action rule is 2 with a priority of 50).
Notice that the noise power level continues to increase:


TotalWord : 3054
-172.
TotalWord : 4044
-102.
TotalWord : 3754
-102.
Ingress noise causes the error rate to exceed the threshold and the second hop action
occurs:
TotalWord : 3197
-76.
The following output shows that the second hop action to change modulation profile 2
is successful. The noise power level does not change, however, since the modulation
type is different in modulation profile 2, than in modulation profile 1, the acceptable
noise power threshold is different.
[07/23-11:05:58:SPECMGR]-N-Set to new mode profile 2 for channel
ifIndex = 7 .
TotalWord : 2842
-76.
TotalWord : 3805
-32.
In the following output example, ingress noise causes the error rate to exceed the error
threshold, and the next hop action changes the upstream channel width:
[07/23-11:08:58:SPECMGR]-D-Error Rate: 4.5083 %, ErrorWord :
182, TotalWord : 4037
[07/23-11:08:58:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : 16.

The following output displays that the hop action succeeded and that a new channel
width has been assigned to the upstream port by the spectrum manager:
[07/23-11:08:59:SPECMGR]-N-Set to new width 1600000, miniSlot 8
for channel ifIndex = 7 .
TotalWord : 2947
[07/23-11:09:08:SPECMGR]-D-Channel Noise Power (1/10 dbmv) : 16.
The following output displays that the noise power level is restored:
TotalWord : 3040
-183.
Viewing the Spectrum Management Roll-back Function

When the spectrum roll-back function is enabled, the spectrum manager returns the
upstream channel width or modulation profile setting, that was adjusted during a hop
action, to the original configuration when upstream channel conditions improve.
In the following output example, the roll-back function starts when the ingress noise
is removed:
TotalWord : 2809
-184.
TotalWord : 2143
-185.
The following output shows the existing upstream channel width reverting to its
original upstream channel width setting:
[07/23-11:09:39:SPECMGR]-N-Revert to width 3200000, miniSlot 4
succeed for channel ifIndex = 7 .
TotalWord : 1927
-182.


TotalWord : 2108
-197.
TotalWord : 1926
-196.
TotalWord : 2434
-197.
The following output shows the existing upstream modulation profile reverting to its
original upstream modulation profile setting:
[07/23-11:10:19:SPECMGR]-N-Revert to mode profile 1 succeed for
TotalWord : 1322
-197.
TotalWord : 395
-197.

12
Configuring Advanced
Spectrum Management
Introduction
This chapter discusses the functionality and configuration procedures for the
Advanced Spectrum Management features on the BSR. Advanced Spectrum
Management includes Frequency Agility, Frequency Rollback, Modulation Profile
Agility and Modulation Profile Rollback.
The purpose of the Frequency Agility, Frequency Rollback, Modulation Profile
Agility and Modulation Profile Rollback features is to monitor the upstream signal
quality and automatically change the frequency and modulation profile (per operators
configuration), to operate the receiver at the optimum throughput by adapting to the
quality of the upstream spectrum. When the signal quality on the primary channel
improves, the upstream port is reverted back to the original configuration. The signal
quality is measured using MER (Mean Error Ratio). RF Sentry on the 2:8 CMTS
modules is used to assess the quality of the spare channels without affecting the data
or voice passing on the active channel.

Configuring Advanced Spectrum Management on the BSR could involve the

following tasks:
Configuring Frequency Agility
Specifying Hop Action Band Start and End Frequencies
Specifying a Hop Action Center Frequency
Specifying the Active Channel Hop Sampling Period
Specifying the Spare Channel Hop Sampling Period
Specifying SNR Hysteresis
Applying a Spectrum Group to an Upstream Receiver
Configuring Frequency Rollback
Configuring Modulation Profile Agility
Specifying a Modulation Profile
Configuring Modulation Type SNR Thresholds
Enabling Modulation Profile Rollback
Excluding Reference Cable Modems
Terminology
RFSentry and 9th Receiver are synonymous.
MER (Mean Error Ratio) and SNR(Signal-To-Noise Ratio) are synonymous and
both represent coherent channel signal quality measurements across the spectrum.
Active Channel indicates the configured channel or the spare channel whichever is
active at the time.
NON-OPTIMAL the channel is not operating at the highest configured modulation
profile mode.

Release 5.3.1 Configuring Advanced Spectrum Management
Channel State indicates the operational state of the channel tuned to a receiver (as per
signal quality) and can be one of the following:
NORMAL is the operational status of the channel tuned to the receiver. If there
are registered modems on the receiver, continue to operate in this state or set the
channel quality to IMPAIRED based on the SNR measurements. If there are no
registered cable modems on the receiver, the channel quality state is changed to
PENDING.
IMPAIRED is the operational status of a channel that is operating below the
signal quality threshold. If there are registered cable modems on the receiver, the
channel can continue to operate in this state or the channel quality can be reset to
NORMAL based on the improved SNR measurements. If no registered cable
modems are on the receiver, the channel quality is changed to PENDING. If the
receiver is retuned to a different center frequency, the channel state is changed to
PENDING until SNR measurements can be performed.
PENDING is the operational status of the channel pending SNR signal quality
assessment. If there are registered modems on the receiver, set the channel
quality to either NORMAL or IMPAIRED based on the SNR measurements
Frequency Agility
Frequency Agility provides the capability of periodically monitoring the quality of the
active upstream channel. If the plant conditions degrade, i.e. noise detected on the
tuned center frequency, the spare spectrum that is configured for the Spectrum Group
is assessed using the RF Sentry 9th receiver. If a spare channel of acceptable quality is
available in that Spectrum Group, the receiver with the degrading channel is retuned
to the channel of acceptable quality.

The quality assessment for a spare channel is performed whenever the active channel
of a receiver in the Spectrum Group is in the "IMPAIRED" state provided a spare
channel for the Spectrum Group is available. If all spare channels are searched and no
acceptable replacement channel is found, a configurable hold down delay will elapse
before the retesting of the spare channels is resumed. When impairment is detected for
an active channel, before retuning the receiver with a spare channel, the spare
channels are assessed for suitable channel quality. The impaired channel is swapped
only if the spare channel meets the quality threshold. In the event that an impaired
channel could not be swapped with another channel due to poor quality of the spare
channels, the receiver with the impaired channel continues to operate on the
"IMPAIRED" channel. However, the spare channels are periodically assessed using
the RF Sentry 9th receiver until the receiver is operating on a channel that is not
impaired.
Frequency Rollback
Frequency Rollback provides the ability to switch the active channel which is running
on a spare frequency back to the primary channel. If the primary channel becomes
noise free, the receiver is switched back (rolled back) to its primary channel and the
spare channel becomes available for use by any of the receivers in the Spectrum
Group, in the event that there is impairment on their respective configured channels.
Note: The ASPM Frequency Rollback feature is only supported where the
configured frequencies are configured specifically for each upstream port and
the spare channel is used to replace the configured channel when there is
noise on the configured channel.
Modulation Profile Agility

Modulation Profile Agility provides the capability of periodically monitoring the
quality of the upstream channel that is in use and to provide dynamic selection of a
configured modulation profile based on the signal quality. When an impairment on the
active channel exceeds the SNR threshold for the modulation profile currently in use,
the channel is reconfigured to use another modulation profile provided for the
Spectrum Group.

Modulation Profile Rollback

Modulation Profile Rollback provides the ability for a receiver to use a secondary
modulation profile until the receiver can again operate effectively using another
modulation profile. When there is impairment on the primary or spare channel, the
modulation profile for the channel is changed to use another lower modulation profile.
When the signal quality of the channel improves and if Modulation Profile Rollback
is configured, the channel will use another higher modulation profile.
Prerequisites
Frequency agility is used first in the Advanced Spectrum Management feature if
the quality of the active upstream channel degrades. If a spare channel of
acceptable quality is not available, Modulation Profile Agility will then be used to
improve signal quality.
The Advanced Spectrum Management features described in this chapter are only
supported by the BCM 3138-based and BCM 3140-based 2:8 CMTS modules
that provide valid SNR channel quality measurements for upstream ports. These
modules provide a 9th receiver in order to provide channel quality measurements
on unused upstream channels.
The BCM 3137-based 1:4 and 1:8 CMTS modules will continue to support the
existing Spectrum Management features that are based on RSSI and packet error
metrics. SNR based Spectrum Management functionality is not supported on the
1:4 and 1:8 CMTS modules.
BCM 3140-based 2:8 CMTS modules for the BSR 64000 Release 4.2 or higher
only support the Modulation Profile Agility and Modulation Rollback features on
logical channel 0. This applies to both ASPM for Release 4.4 and the existing
Spectrum Management feature.
No Advanced Spectrum Management features will be supported for S-CDMA
channel types.
A minimum a five (5) registered cable modems are required for the ASPM
feature to work.

Advanced Spectrum Management Operational

Rules
If a another (secondary) modulation profile or profiles are configured for an
active channel, then in the event that the active channel becomes impaired and
can not be swapped with a spare channel, the modulation profile of the active
channel is changed to another modulation profile while the spare channels are
being assessed as replacements using the modulation profile used by the active
channel before it became impaired. If noise persists after the modulation profile
of the active channel is changed to another modulation profile, the active channel
will be operating in an "IMPAIRED" or "NON-OPTIMAL" state while the spare
channels are being assessed.
If rollback is configured and the receiver is operating on a spare channel, the
originally configured channel for the receiver is periodically measured with RF
Sentry. Once the SNR on the originally configured channel is greater than the
threshold, the receiver is switched back to the originally configured channel.
If rollback is configured, and the receiver is operating on a another modulation
profile, the modulation profile will be rolled back to a previously used
modulation profile before the active channel became impaired as that channels
quality improves.
If no hopping rules are configured for a Spectrum Group or if a receiver is not a
member of any Spectrum Group, in the event of channel degradation the receiver
will continue to operate on the configured channel using the configured
modulation profile in an "IMPAIRED" or "NON-OPTIMAL" state.
Legacy Spectrum Management CLI Commands

This section identifies the existing Spectrum Group commands that are not applicable
to the Advanced Spectrum Management feature for 2:8 CMTS modules. These
commands will continue to be applicable for 1:4 and 1:8 CMTS modules and their
associated Spectrum Groups.
Note: The CLI help text will indicate which Spectrum Management
commands are only valid for Spectrum Groups associated with a 2:8 CMTS
modules upstream ports. The BSR will ignore the legacy CLI commands
listed below for a Spectrum Group associated with a 2:8 CMTS module.

The following legacy Spectrum Management CLI commands commands are not
supported by the Advanced Spectrum Management feature:
band configures the start and end frequency band for a

Spectrum Group
guard band configures the guard band
hop action channel-width configures the hopping rule for channel width
hop action power-level configures the hopping rule for power-level
hop period prevents excessive frequency hops on an upstream
port
hop threshold error configures the spectrum hopping error threshold
hop threshold flap configures the spectrum hopping flap threshold
time band schedules the availability of the spectrum group
band
time delete band schedules the removal of the spectrum group band
Advanced Spectrum Management CLI Commands

The following legacy Spectrum Management CLI commands commands are
supported by the Advanced Spectrum Management feature:
cable upstream spectrum-group
hop action frequency
hop action band
hop action modulation-profile
hop action roll-back

The following new Advanced Spectrum Management CLI commands have been
intoduced with the Advanced Spectrum Management feature to allow the operator to
have more control over ASPM:
clear interfaces cable upstream channel-agility-stats
hop snr hysteresis
hop sampling-period active-channel
hop sampling-period rollback-channel
hop sampling-period spare-channel
hop threshold snr modulation-type
reference-modem-exclusion
show cable spectrum-group modem-exclusion-list
show cable spectrum-group reference-modem
show cable spectrum-group snr-thresholds
show interfaces cable upstream channel-agility-stats

Configuring Frequency Agility

Configuring the BSR for Frequency Agility may require the following procedures:
Note: The Active Channel Sampling Period, Spare Channel Sampling Period,
and SNR Hysteresis features have enabled default values that do not need to
be re-configured.
Note: If cable operators have nothing but bonded cable modems in a

Spectrum Group, then ASPM will not work for frequency agility.


Use the hop action band command in Cable Spectrum Group mode to determine the
hop for each frequency band during the frequency hop action:
MOT:7A(config-spcgrp:<WORD>)#hop action band {<5000000-42000000>
<5000000-42000000>} [priority <1-255>]
where:
WORD is the Spectrum Group name.
5000000-42000000 is the start upstream frequency band in Hz.
5000000-42000000 is the end upstream frequency band in Hz.
1-255 is the priority number of the upstream band hop action. When no priority is
assigned, the default priority is 128.

For example, the following syntax determines that the upstream frequency band of 20
MHz to 30 MHz replaces the existing upstream frequency band when the hop action
is triggered and defines the priority level of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action band 20000000
30000000 priority 110


Use the hop action frequency command in Cable Spectrum Group mode to
determine the frequency hop for discrete center frequencies during the frequency hop
action:
MOT:7A(config-spcgrp:<WORD>)#hop action frequency
{<5000000-42000000> | <5000000-65000000> | <1000000-55000000>}
[priority <1-255>]
where:
5000000-42000000 is the North America standard frequency in Hz.
5000000-65000000 is the EURODOCSIS standard frequency in Hz.
1000000-55000000 is the J-DOCSIS standard start frequency in Hz.
1-255 is the priority number of the upstream frequency hop action. When no
priority is assigned, the default priority is 128. The lower number takes
precedence.
For example, the following syntax determines that 28 MHz replaces the existing
upstream frequency when a hop action is triggered and defines the priority level
of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action frequency 28000000
priority 30
Note: Depending on the configuration of the installed 2:8 CMTS Resource

Module, the start and end frequencies will reflect the North American
DOCSIS, EURODOCSIS, or J-DOCSIS standards


The hop sampling-period active-channel command configures the active channel
sampling period which is how often the active channel quality is measured.
The signal quality of the active channel is periodically measured for SNR. The active
channel sampling period is the time between two consecutive signal quality
measurements of the active channel.
Use the hop sampling-period active-channel command to configure the active
channel sampling period, as follows:
1. Navigate to Cable Spectrum Group mode from Global Configuration mode.
MOT:7A(config)#cable spectrum-group <WORD>
where:
2. Specify the active channel sampling period. The default is 3 seconds.
MOT:7A(config-spcgrp:Spectrum Group name)#hop
sampling-period active-channel <0-15>
where:
0-15 is the rate, measured in seconds, at which the signal quality of the active
channel is assessed. "0" disables active channel measurement per Spectrum
Group.

The hop sampling-period spare-channel command configures the spare channel
sampling period which is how often the spare channels Spectrum quality is measured
when an active channel is "IMPAIRED" or "NON-OPTIMAL".
If an "IMPAIRED" or "NON-OPTIMAL" active channel could not be swapped with a
spare channel due to the poor signal quality of the spare channels, the spare channels
are periodically assessed on the RF Sentry 9th receiver. The spare channel sampling
period is the time between two consecutive signal quality measurements of all the
spare channels. In each spare channel quality sampling cycle, the first good spare
channel is used.
Use the hop sampling-period spare-channel command to configure the spare
channel sampling period, as follows:


where:
2. Specify the spare channel sampling period. The default is 10 seconds.
sampling-period spare-channel <10-600>
where:
10-600 is the rate, measured in seconds, at which the signal quality of the
spare channel is assessed.

The hop snr hysteresis command specifies the amount of dB degradation in a
downward direction before a channel will be marked as "IMPAIRED". For example.
if a channel is operating in a "NORMAL" state of 20 dB and SNR hysteresis is set to
2 dB, if the channel degrades in a downward direction until it reaches 18 dB, then the
channel will be considered to be in the "IMPAIRED" state. If the channel again
improves to 20 dB, the channel is no longer considerd to be "IMPAIRED".
The user must be aware of the effects of lowering or increasing the SNR hysteresis. A
higher SNR hysteresis value will delay switching to a channel that is not impaired. A
smaller SNR hysteresis value could result in too many channel transitions.
Use the hop snr hysteresis command to specify the amount of dB degradation in a
downward direction before a channel will be marked as "IMPAIRED", as follows:
where:
2. Specify a new SNR hysteresis value. The default is 2 dB.
MOT:7A(config-spcgrp:Spectrum Group name)#hop snr hysteresis
<2-3>
where:
2-3 specifies the amount of dB degradation in a downward direction before a
channel will be marked as "IMPAIRED".


When a Spectrum Group is applied to an upstream receiver, that upstream receiver
belongs to the Spectrum Group.
Follow these steps to assign a Spectrum Group to an upstream port and associated
receiver:
where:
X/Y is the slot and MAC Domain number of the 2:8 CMTS module. The 2:8
and 2:8 (2.0) CMTS modules will have a MAC Domain number of "0" or
"1".
Configuration mode, to apply a Spectrum Group to an upstream port:
Note: All upstream ports sharing the same return path should be configured
to the same Spectrum Group.

where:
WORD is the exact Spectrum Group name to be applied to the upstream port.
3. Use the show cable spectrum-group command to verify if the Spectrum Group
is assigned to the upstream port:
where:
WORD is the exact Spectrum Group name applied to the upstream port.
4. Use the show controllers cable upstream to display which Spectrum Group is
applied to each upstream.
MOT:7A(config-if)#show controllers cable <X/Y> upstream <NUM>

where:
X/Y displays cable interface controller information for the specified BSR
chassis slot and MAC Domain including RF signal information, the type of
hardware installed, FEC information for both corrected and uncorrected
packets, the spectrum group and the status of the cable interface.
NUM displays information for an upstream port including the upstream
modulation type, channel width, frequency, modulation profile information
(i.e minislots, interleave, preamble, etc.), and upstream Channel ID number.
or
Use the show running config command to see which Spectrum Group is applied
to each upstream.
Configuring Frequency Rollback

The hop sampling-period rollback-channel command configures the channel
rollback sampling period which is how often the configured channel quality is
measured with RF Sentry.
When a primary channel is swapped with the spare channel, if the rollback is
configured, the primary channel is periodically measured for signal quality in the
background using RF Sentry. The primary rollback channel sampling period is the
time between two consecutive signal quality measurements of the primary channel.
To enable Spectrum rollback and specify the rollback sampling period, do the
following:

where:
2. Use the hop sampling-period rollback-channel command to configure the
rollback channel sampling period. The default is 60 seconds.
sampling-period rollback-channel <10-300>

where:
10-300 is the rate, measured in seconds, at which the signal quality of the
primary channel is measured when an upstream is operating on a spare
channel.
Enabling Frequency Rollback

Use the hop action roll-back command to enable the Spectrum rollback function.
The default is disabled.
MOT:7A(config-spcgrp:Spectrum Group name)#hop action roll-back
Configuring Modulation Profile Agility

Configuring the BSR for Modulation Profile Agility may require the following
procedures:
Note: The Configuring Modulation Type SNR Thresholds and the SNR
Hysteresis features have enabled default values that do not need to be
re-configured.


Use the hop action modulation-profile command in Cable Spectrum Group mode to
change the modulation profile setting for a hop action:
Note: The modulation type for the hopping profile has to be the same as the
configured channel profile type (i.e.TDMA to TDMA or A-TDMA to A-TDMA,
etc.)

MOT:7A(config-spcgrp:<WORD>)#hop action modulation-profile <1-600>

[priority {<1-255>}]
where:
1-255 is the priority number of the upstream modulation profile hop action. When
no priority is assigned, the default priority is 128.
For example, the following command syntax determines that modulation profile 200
replaces the existing modulation profile when the hop action is triggered and defines
the priority level of the hop:
MOT:7A(config-spcgrp:spectrum1)#hop action modulation-profile 200
priority 50

The hop threshold snr modulation-type command configures the SNR thresholds
for each modulation type.
SNR threshold is used to determine if a channel is capable of operating error free in
the modulation mode that is specified for Long Data or Advanced Long Data IUCs in
the configured modulation profile for the upstream receiver. A default SNR threshold
is used for each modulation type. The operator can override this by configuring a
different SNR threshold for a specific modulation type that is used in the active
channel. This threshold is used to transition channel states. SNR thresholds are
configurable with a resolution of 1dB.
The following table lists the recommended SNR thresholds for different modulation
types without FEC.
Note: The SNR threshold values for the different modulation types must
always be in a low to high order with QPSK being the lowest and 256QAM
being the highest.

Modulation Type Default SNR Threshold
QPSK 14dB
8QAM 17dB
16QAM 20dB
32QAM 23dB
64QAM 27dB
128QAM 30dB
256QAM 33dB
Use the hop threshold snr modulation-type command to configure SNR thresholds
for each modulation type, as follows:

where:
2. Specify a new SNR threshold for a modulation type.
MOT:7A(config-spcgrp:Spectrum Group name)#hop threshold snr
modulation-type {128qam | 16qam | 256qam | 32qam | 64qam | 8qam | qpsk}
<13-34>
where:
13-34 is the SNR threshold, in dB, at which a specified modulation type
should operate. This setting is also used to transition channel states.
3. Use the show cable spectrum-group snr-thresholds command to display the
configured SNR thresholds for each modulation type.
MOT:7A(config)#show cable spectrum-group <WORD> snr-thresholds

where:

The hop snr hysteresis command specifies the amount of dB degradation in a
downward direction before a channel will be marked as "IMPAIRED". For example,
if the SNR threshold is configured to 20dB and the default hop SNR hysteresis of 2dB
is used, then in the event of channel noise, a channel switch from the active channel to
the spare channel will take effect when the SNR value drops to 18dB on the active
channel (provided the spare channels SNR is at least 20dB). When the previously
active channels SNR goes back up to 20dB, the channel will be rolled back.
If a spare channel is not available or the spare channels SNR is below 20dB, and if a
another modulation profile is configured, then the modulation profile of the impaired
active channel will be changed.
The user must be aware of the effects of lowering or increasing the SNR hysteresis. A
higher SNR hysteresis value will delay switching to a channel that is not impaired. A
smaller SNR hysteresis value could result in too many channel transitions.
Use the hop snr hysteresis command to specify the amount of dB degradation in a
downward direction before a channel will be marked as "IMPAIRED", as follows:
where:
2. Specify a new SNR hysteresis value. The default is 2 dB.
MOT:7A(config-spcgrp:Spectrum Group name)#hop snr hysteresis
<2-3>
where:
2-3 specifies the amount of dB degradation in a downward direction before a
channel will be marked as "IMPAIRED".


When a Spectrum Group is applied to an upstream receiver, that upstream receiver
belongs to the Spectrum Group.
Follow these steps to assign a Spectrum Group to an upstream port and associated
receiver:
where:
X/Y is the slot and MAC Domain number of the 2:8 CMTS module. The 2:8
and 2:8 (2.0) CMTS modules will have a MAC Domain number of "0" or
"1".
Configuration mode, to apply a Spectrum Group to an upstream port:
Note: All upstream ports sharing the same return path should be configured
to the same Spectrum Group.

where:
WORD is the exact Spectrum Group name to be applied to the upstream port.
3. Use the show cable spectrum-group command to verify if the Spectrum Group
is assigned to the upstream port:
where:
WORD is the exact group name applied to the upstream port.
4. Use the show controllers cable upstream to display which Spectrum Group is
applied to each upstream.
MOT:7A(config-if)#show controllers cable <X/Y> upstream <NUM>

where:
X/Y displays cable interface controller information for the specified BSR
chassis slot and MAC Domain including RF signal information, the type of
hardware installed, FEC information for both corrected and uncorrected
packets, the spectrum group and the status of the cable interface.
NUM displays information for an upstream port including the upstream
modulation type, channel width, frequency, modulation profile information
(i.e minislots, interleave, preamble, etc.), and upstream Channel ID number.
or
Use the show running config command to see which Spectrum Group is applied
to each upstream.
Enabling Modulation Profile Rollback

Modulation Profile Rollback provides the ability for a receiver to use a secondary
modulation profile until the receiver can again operate effectively using another
modulation profile. When there is impairment on the primary or spare channel, the
modulation profile for the channel is changed to use lower mode modulation profile.
When the signal quality of the channel improves and if Modulation Profile Rollback
is configured, the channel will use another higher modulation profile.
To enable Modulation Profile Rollback, do the following:

where:
2. Use the hop action roll-back command to enable the Spectrum roll-back
function. The default is disabled.
MOT:7A(config-spcgrp:Spectrum Group name)#hop action roll-back

Excluding Reference Cable Modems

The reference-modem-exclusion command specifies the number of low SNR cable
modem(s) on each upstream channel in a Spectrum Group that are not allowed to be
used for channel assessment.
This value is used to exclude bad or errored cable modems from being selected as the
reference modem. These excluded reference cable modems are those with the lowest
SNR values within the reference cable modem list.
Use the reference-modem-exclusion command to specify the number of low SNR
cable modem(s) on each upstream channel, as follows:
where:
2. Specify the number of low SNR cable modem(s) on each upstream channel. The
default is 0.
MOT:7A(config-spcgrp:Spectrum Group name)#
reference-modem-exclusion <0-15>
where:
0-15 is the number of low SNR cable modem(s) on each upstream in the
Spectrum Group that are not allowed to be used for channel assessment. This
parameter has no effect when the number of registered cable modems on a
specific upstream are less than double this value. A value of "0" indicates that
no cable modem is excluded from the reference cable modem list.
3. Use the show cable spectrum-group modem-exclusion-list command to
display the list of low SNR cable modem(s) that are not allowed to be used for
channel assessment.
Displaying the Reference Modem List

Use the show cable spectrum-group reference-modem command to display a
list of reference cable modem(s) being used for channel assessment. The
reference cable modem list is built every 5 minutes. Only two cable modems, an
active reference cable modem and a rollback reference cable modem, are
displayed.

13
Configuring Load Balancing
Introduction
This chapter provides information on configuring various types of load balancing on
the BSR. The following load blancing procedures are described:
Configuring Static Upstream Load Balancing
Configuring Static Count-Based Load Balancing
Configuring Dynamic Load Balancing
Manually Moving a Cable Modem
Redistributing CMTS Traffic Among HSIMs

Configuring Static Upstream Load Balancing

Static upstream load balancing evenly distributes cable modems across multiple
upstream channels serving the same geographical community or Spectrum Group.
The term "static" means that the BSR will only attempt to move a cable modem to
another upstream channel after the registration process is complete. When enabled,
static upstream load balancing occurs automatically to move a newly registered cable
modem to the least loaded upstream channel.
Static upstream load balancing can be enabled or disabled per user-defined Spectrum
Group. By default, when a Spectrum Group is first created, the static upstream load
balancing feature will be disabled.
Static upstream load balancing is only based on the cable modem count on each
upstream channel. Cable modem types (DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0, or
PacketCable Embedded MTA), upstream channel physical parameters (channel type,
channel width, modulation profile, minislot size), reserved bandwidth for each service
flow, channel quality, or channel traffic utilization are not taken into account.
Load-balancing can also be achieved manually through the Command Line
Interfaces cable modem ucc command which uses the DOCSIS Upstream Channel
Change (UCC) mechanism for moving cable modems to a different upstream channel.
Note: Using the static load balancing feature requires a thorough knowledge
of creating and using Spectrum Groups. Refer to the BSR 64000
Configuration and Management Guide and the BSR 64000 Command
Reference Guide for detailed instruction on creating and using Spectrum
Groups.
Enabling Static Upstream Load Balancing

Use the load-balancing static command in Spectrum Group mode to enable static
upstream load balancing for a Spectrum Group, as follows:
MOT:7A(config-spcgrp:<Spectrum Group name>)# load-balancing

static

Release 5.3.1 Configuring Load Balancing
There are two ways to determine if static load balancing has been enabled:
A "load-balancing static" entry appears in the running-configuration

file.
A "load-balancing static" entry appears in the show cable
spectrum-group <WORD> command output, as follows:
MOT:7A# show cable spectrum-group [<WORD>]
where:
WORD is the Spectrum Group name
Note: Before a new upstream channel that is added to a Spectrum Group is

considered for load balancing, the new upstream channel must have at least
one cable modem registered on it. To do this, a user must use the cable
modem ucc command to manually force a cable modem onto the new
upstream channel. After one cable modem is registered on the new upstream
channel, any subsequently registering cable modems will be eligible for load
balancing. Refer to the Moving a Cable Modem to a Specified Upstream
Channel section for more information.
Use the no load-balancing static command in Spectrum Group mode to disable static
upstream load balancing for a Spectrum Group, as follows:
MOT:7A(config-spcgrp:<Spectrum Group name>)# no load-balancing

static
Note: If load balancing is disabled for a Spectrum Group, that specific

Spectrum Group can still be load balanced by including the Spectrum Group
name with the cable load-balance spectrum-group command. If the cable
load-balance spectrum-group command is used without a specific
Spectrum Group name, any Spectrum Groups that have load balancing
disabled will not be load balanced.

If static upstream load balancing is enabled for a Spectrum Group, cable modems are
balanced across the upstream channels within the same Spectrum Group based only
on count. If the cable modem count on the current upstream channel on which the
cable modem is trying to register is greater than the count on the least loaded
upstream channel by a difference of 5, the cable modem is automatically moved to the
least loaded upstream channel.
Note: If a user invokes the load-balance feature through the CLI with the
cable load-balance spectrum-group command (see Load Balancing
Across All Upstream Channels), the difference of 5 will not apply and the
number of modems is divided, almost equally, between the available
receivers within the Spectrum Group.
Note: Cable modems will not be moved with the load-balancing static
command if any of the following conditions apply:
a cable modem has TLV type 2, upstream channel ID, assigned in the
configuration file. To move cable modems registered with a TLV type 2,
you must use the cable modem ucc command to move them
manually.
a cable modem de-registers after a UCC failure and attempts to
re-register within 30 seconds of de-registration.
Load Balancing Across All Upstream Channels

The cable load-balance spectrum-group command balances cable modems across
all upstream channels within the same Spectrum Group. This command can be used
for one specific Spectrum Group or for all Spectrum Groups. If a Spectrum Group
spans multiple CMTS MAC Domains, load balancing will be done on each CMTS
MAC Domain independently.
To balance cable modems across all upstream channels within the same Spectrum
Group, use the cable load-balance spectrum-group command as follows:
MOT:7A# cable load-balance spectrum-group [<WORD>]
where:

WORD indicates balancing only a specified Spectrum Group
Note: Entering the cable load-balance spectrum-group command without

specifying a Spectrum Group will load-balance only the Spectrum Groups
that have the static load-balancing feature enabled.
Note: Before a new upstream channel that is added to a Spectrum Group is

considered for load balancing, the new upstream channel must have at least
one cable modem registered on it. To do this, a user must use the cable
modem ucc command to manually force a cable modem onto the new
upstream channel. After one cable modem is registered on the new upstream
channel, any subsequently registering cable modems will be eligible for load
balancing. Refer to the Moving a Cable Modem to a Specified Upstream
Channel section for more information.
Moving a Cable Modem to a Specified Upstream Channel

The cable modem ucc command allows an operator to manually move a CM or
embedded MTA to a different upstream channel within the same Spectrum Group and
the same MAC domain. The CM/MTA can be moved after registration to balance the
number of CM/MTAs evenly among the receivers of the CMTS module so that the
entire upstream bandwidth can be used more efficiently.
The cable modem ucc command is the only command that can move a cable modem
registered with a TLV type 2. (Cable modems registered with a TLV type 2 cannot be
moved using the static load balancing feature.)
Use the cable modem ucc command in Privileged EXEC mode to move a CM or
MTA to a different upstream channel, as follows:
MOT:7A# cable modem {<mac> | <prefix> } ucc <0-7>
where:
mac is the cable modems MAC address in the form xxxx.xxxx.xxxx
prefix is the cable modems IP address
0-7 is the upstream port number

Upon receipt of the UCC request from the CMTS, the cable modem will perform
ranging on the new upstream channel. The cable modem remains registered over the
channel change.
Note: Cable modems will not be moved with the cable modem ucc
command if any of the following conditions apply:
cable modem is not registered or having pending transaction (UCC or

DSX).
the new upstream channel is not in the same Spectrum group or MAC
Domain.
Displaying Load Balancing Statistics for a Spectrum Group

The show cable spectrum-group load-balance summary command displays a
summary of cable modem distribution and load balancing statistics for a Spectrum
Group.
The show cable modem summary and show cable modem summary total
commands display a summary of cable modem information, including the Spectrum
Group name for each upstream channel, for each cable interface on the BSR.
MOT:7A# show cable spectrum-group <WORD> load-balance summary
where:
WORD is the Spectrum Group name
Refer to the BSR 64000 Command Reference Guide to see typical screen output from
the show spectrum-group load-balance summary command.
MOT:7A# show cable modem summary
MOT:7A# show cable modem summary total
the show cable modem summary and show cable modem summary total
commands.

Displaying UCC Statistics

The show cable ucc-stats command displays DOCSIS Upstream Channel Change
(UCC) statistics for a MAC Domain.
MOT:7A# show cable ucc-stats [<X/Y>]
where:
the show cable ucc-stats command.
Configuring Static Count-Based Load Balancing

Static count-based static load balancing evenly distributes cable modems across
multiple downstream/upstream channels serving the same geographical community or
Spectrum Group. The term "static" means that the BSR will only attempt to move a
cable modem to another channel after the registration process is complete. When
enabled, static count-based load balancing occurs automatically to move a newly
registered cable modem to the least loaded channel.
Static count-based load balancing is based on the cable modem count on each
downstream/upstream channel. All cable modem types (DOCSIS 1.0, DOCSIS 1.1,
DOCSIS 2.0, or PacketCable Embedded MTA) are supported by this feature. In
Release 4.4.0.2, the BSR supports static count-based load balancing at registration
time. This is a form of registration-based load balancing that is done at the time that a
cable modem registers. When a cable modem sends its registration request
(REG-REQ) and ranging request (RNG-REQ) messages, the CMTS responds with a
ranging response (RNG-RSP) message that includes a Downstream Frequency
Override field that instructs the a DOCSIS 1.0 cable modem which downstream
channels it should use. All other cable modems use DCC for downstream load
balancing.
The cable load-balance command executes downstream or upstream static
count-based load balancing (based on ds-reg or us-reg rules) for all registered cable
modems in the affected load balancing groups. Downstream or upstream static
count-based load balancing evenly distributes cable modems across multiple channels
serving the same geographical community or Spectrum Group. The term "static"
means that the BSR will only attempt to move a cable modem to another channel after
the registration process is complete. Static downstream or upstream load balancing
occurs automatically moves a newly registered cable modem to the least loaded
channel.

MOT:7A# cable load-balance [downstream| upstream] [loadbalance-group

<WORD>]
where:
downstream enables downstream cable modem count load balancing.
upstream enables upstream cable modem count load balancing.
loadbalance-group WORD load balances the specified load balancing group.
Configuring Dynamic Load Balancing

Dynamic Load Balancing evenly distributes voice/data traffic across upstream and
downstream channels within a load balancing group. A load balancing group is a
cluster of downstream and associated physical upstream channels among which cable
modems can be autonomously load balanced. The BSR assigns a cable modem to a
load balancing group upon successful registration, if the cable modems channel is
associated with that load balancing group. The operator must define load balancing
groups to be consistent with the physical plant topology. Load balancing groups can
also be defined in order to support a specific class of service.
When the BSR is configured for Dynamic Load Balancing, cable modems are moved
from a channel with highest utilization to a channel with lowest utilization based on
the actual bandwidth utilization and the utilization thresholds.The algorithm takes into
account the actual bandwidth utilization of each channel that is configured for the
load balance group, the actual bandwidth utilized by each modem on the highest
utilized channel and the utilization thresholds.
Load Balancing Groups

This section describes configuring load balancing groups. There are two types of load
balancing groups:
General Load Balancing Groups
Restricted Load Balancing Groups
A Restricted Load Balancing Group is associated with a specific, provisioned set of
cable modems. Restricted Load Balancing Groups are used to accommodate a
topology specific or provisioning specific restriction such as a set of channels
reserved exclusively for business customers.
General Load Balancing Groups are open for cable modems which are not
provisioned into a Restricted Load Balancing Group.

The CMTS assigns cable modems to a General Load Balancing Group based on the
upstream channel on which they register. The CMTS will assign a modem to a
Restricted Load Balancing Group only if it is explicitly provisioned (via SNMP or
a configuration file TLV) to be a member of that group. The CMTS will not assign
a cable modem to more than one Load Balancing Group.
Configuring General Load Balancing Groups involves the following tasks:

1. Configuring a Load Balancing Rule
2. Configuring a Load Balancing Policy
3. Configuring the Load Balancing Group
4. Assigning Downstream and Upstream Channels to a Load Balancing Group
Configuring Restricted Load Balancing Groups is described in the Configuring a
Restricted Load Balancing Group section.
Note: Before configuring a load balancing group, you must configure a load
balancing policy and associated policy rules.
Configuring a Load Balancing Rule

Load balancing policies provide control over the autonomous load balancing process
on a per-CM basis. A load balancing policy is described by a set of conditions (rules)
that govern the autonomous load balancing process for the cable modem. When a load
balancing policy is defined by multiple rules, all of the rules apply in combination.
This section describes configuring load balancing rules. Adding rules to a load
balancing policy is discussed in the Configuring a Load Balancing Policy section.
The following rules can be configured:
dis-period - disables load balancing for a specified time period.
disable - disables the load balancing rule.
ds-util - the threshold percentage of downstream utilization before
load-balancing starts.
enable - enables the load balancing rule.
interval - the periodic interval for load balancing in minutes.

us-reg modem-count-thresh - the maximum allowed difference in the cable

modem count between the cable modem's initial upstream channel and the least
loaded upstream channel in the load balance group.
us-util - the threshold percentage of upstream utilization before load-balancing
starts.
Follow this procedure to configure a policy rule:
Use the cable loadbalance-rule command in Global Configuration mode to create a
new load balancing rule or modify an existing load balancing policy rule, as shown
below:
MOT:7A(config)#cable loadbalance-rule <WORD> {dis-period <0-86400>
<0-86400> | disable | ds-util {min <0-100> delta <0-100> stop <0-100} | enable |
interval <0-480> | rem-dsx | us-reg modem-count-thresh <1-50> | us-util {min
<0-100> delta <0-100> stop <0-100}} [snmp-index <0-4294967295>]
where:
WORD is the policy rule name.
dis-period disables load balancing for a specified time period.
0-86400 is the dis-period start time in seconds after 12:00 AM.
0-86400 is the dis-period length in seconds.
Note: The load balancing disable time period that is entered in a load
balancing rule cannot span AM to PM (i.e. 4 PM through 9 AM).
For example, to disable load balancing for this time period, you would need to
enter two separate command strings, 4 PM to 11:59:59 PM and 00:00:01 AM
to 9 AM, as follows:
cable loadbalance-rule <WORD> dis-period 57600 28799
cable loadbalance-rule <WORD> dis-period 1 32400
disable disables the load balancing rule.

ds-util min 0-100 is the mininum threshold percentage of downstream utilization

before load-balancing starts.
Note: Only the maximum utilized channel must meet the minimum threshold
value before load balancing starts within a load balancing group.
ds-util delta 0-100 is the delta percentage of downstream utilization between

load-balancing channels to start load balancing.
ds-util stop 0-100 is the delta percentage of downstream utilization between
load-balancing channels to stop load balancing.
enable enables the load balancing rule.
interval 0-480 is the periodic interval for load balancing in minutes.
rem-dsx enables remote DSX resource failure load-balancing
us-reg modem-count-thresh 1-50 is the maximum allowed difference in the
cable modem count between the cable modem's initial upstream channel and the
least loaded upstream channel in the load balance group.
us-util min 0-100 is the mininum threshold percentage of upstream utilization
before load-balancing starts.
Note: Only the maximum utilized channel must meet the minimum threshold
value before load balancing starts within a load balancing group.
us-util delta 0-100 is the delta percentage of upstream utilization between

load-balancing channels to start load balancing.
us-util stop 0-100 is the delta percentage of upstream utilization between
load-balancing channels to stop load balancing.

Configuring a Load Balancing Policy

Load balancing policies provide control over the autonomous load balancing process
on a per-CM basis. A load balancing policy is described by a set of conditions (rules)
that govern the autonomous load balancing process for the CM. This section describes
configuring load balancing policies.
You configure load balancing policies through Load Balancing Policy Configuration
mode. Load Balancing Policy Configuration mode allows you to create a new load
balancing policy or modify an existing load balancing policy.
Follow these steps to configure a load balancing policy:
1. Use the cable loadbalance-policy command in Global Configuration mode to
enter Load Balancing Policy Configuration mode, as shown below:
MOT:7A(config)#cable loadbalance-policy <WORD>
where:
WORD is load balancing policy name.
2. Use the policy rule command to add an existing policy rule to the load balancing
policy, as shown below:
MOT:7A(config-lbPolicy:<load balance policy
name>)#policy rule <WORD> [snmp-index <0-4294967295>]
where:
WORD is the policy rule name.
snmp-index 0-4294967295 is the SNMP index value.
Refer to Configuring a Load Balancing Rule for instructions on creating policy rules.
Configuring the Load Balancing Group

This section describes configuring a General Load Balancing Group. General Load
Balancing Groups are open for CMs which are not provisioned into a Restricted Load
Balancing Group.
You configure load balancing group through Load Balancing Group Configuration
mode. Load Balancing Group Configuration mode allows you to create a new load
balancing group or modify an existing load balancing group.
Follow these steps to configure a load balancing group:
1. Use the cable loadbalance-group command in Global Configuration mode to
enter Load Balancing Group Configuration mode, as shown below:

MOT:7A(config)#cable loadbalance-group <WORD> [snmp-index

<0-4294967295>]
where:
WORD is the name of the load balancing group to be created or modified.
2. Use the load-balancing command in Load Balancing Group Configuration mode
to configure the load balancing group, as shown below:
MOT:7A(config-lbgrp:<load balance group
name>)#load-balancing {init-tech <1-31> | policy <WORD> | restricted
{false | true}}
where:
init-tech 1-31 configures a default initialization technique bitmap for a load
balancing group.
policy WORD is the load balancing group's policy name.
restricted is the load balancing groups restricted status; false or true.
Configuring a Restricted Load Balancing Group

This section describes configuring a Restricted Load Balancing Group. A Restricted
Load Balancing Group is associated with a specific, provisioned set of cable modems.
Restricting an Entire Load Balancing Group

Follow these steps to designate an entire load balancing group as restricted:
1. Use the cable loadbalance-group command in Global Configuration mode to
enter Load Balancing Group Configuration mode, as shown below:
MOT:7A(config)#cable loadbalance-group <WORD> [snmp-index
<0-4294967295>]
where:
WORD is the load balancing group name.
2. Use the load-balancing restricted command to designate an entire load
balancing group as restricted, as shown below:


name>)#load-balancing restricted true
To remove the restricted designation from an entire load balancing group, use
the load-balancing restricted command, as shown below
name>)#load-balancing restricted false

Restricting Selected Cable Modems in a Load Balancing Group

To designate a particular CM or a range of CMs as restricted, use the cable
load-balance restricted command, as shown below:
MOT:7A(config)#cable loadbalance-restricted [<1-256> | <WORD> [
snmp-index <0-4294967295>]] no-move [<1-100> [<mac> [<mac>]]]
where:
1-256 the load balancing group ID.
no-move is a restricted cable modem that cannot be moved to another channel.
1-100 the cable modem index of the restricted cable modem that cannot be moved
to another channel..
Note: The cable modem index refers to an index of the Restricted List not the
index of the CM record.
mac the MAC address of the CM to be restricted from load balancing in the form
of xxxx.xxxx.xxxx.
mac the mask to specify a particular CM or a range of CMs in the form of
xxxx.xxxx.xxxx.

Assigning Downstream and Upstream Channels to a Load

Balancing Group
This section describes assigning a downstream and upstream channel to a load
balancing group.
Use the cable downstream loadbalance-group command to assign a downstream
channel to a load balancing group, as shown below:
MOT:7A(config-if)#cable downstream <NUM> loadbalance-group
<WORD>
Note: The same downstream channel may be assigned to multiple load

balancing groups.
Use the cable upstream loadbalance-group command to assign an upstream channel

to a load balancing group, as shown below:
MOT:7A(config-if)#cable upstream <NUM> loadbalance-group <WORD>
where:
NUM the upstream port (default channel number = 0)
WORD the load balancing group name
Note: The upstream channel can not be assigned to multiple load balancing
groups unless the load balancing groups are defined as restricted.

Enabling/Disabling Dynamic Load Balancing

This section describes enabling or disabling Dynamic Load Balancing on the BSR.
The Dynamic Load Balancing can be enabled or disabled for all CMTS modules in
the BSR chassis or for specific Load Balancing Groups.
Enabling/Disabling Dynamic Load Balancing on all CMTS

Modules
The BSR supports a global Dynamic Load Balancing enable/disable feature that
enables or disables Dynamic Load Balancing on all CMTS modules in the BSR
chassis. This feature can be enabled or disabled through SNMP or the CLI. If
disabled on the BSR, Dynamic Load Balancing operations are only allowed from an
external management station.
Through SNMP:
Dynamic Load Balancing can be enabled or disabled on all BSR CMTS modules
through the docsLoadBalEnabled MIB object. This object takes precedence
over any enable or disable objects that apply to a Load Balancing Group.
Through the CLI:

Dynamic Load Balancing can be enabled or disabled on all BSR CMTS modules
through the CLI. Enabling or disabling Dynamic Load Balancing through the CLI
takes precedence over any commands that enable or disable Dynamic Load
Balancing within a Load Balancing Group.
Use the cable modem disable loadbalancing command, in Global Configuration
mode, to disable Dynamic Load Balancing on all CMTS modules, as shown
below:
MOT:7A(config)#cable modem disable loadbalancing
Use the no cable modem disable loadbalancing command, in Global
Configuration mode, to enable Dynamic Load Balancing on all CMTS modules,
as shown below:
MOT:7A(config)#no cable modem disable loadbalancing

Enabling/Disabling Dynamic Load Balancing for a Load

Balancing Group
Dynamic Load Balancing can be enabled or disabled for each Load Balancing Group.
If enabled, Dynamic Load Balancing operations will occur autonomously (based on
policy rules) between channels that are assigned to this Load Balancing Group.
Use the loadbalancing mode enabled command, in Load Balancing Group
Configuration mode, to enable Dynamic Load Balancing for a Load Balancing Group,
as shown below:
MOT:7A(config-lbgrp:<load balance group name>)#loadbalancing
mode enabled
Use the loadbalancing mode disabled command, in Load Balancing Group
Configuration mode, to disable Dynamic Load Balancing for a Load Balancing
Group, as shown below:
MOT:7A(config-lbgrp:<load balance group name>)#loadbalancing
mode disabled
Displaying Dynamic Load Balancing Information

The show cable loadbalance-group command configuration information for all load
balancing groups or a specific load balancing group.
MOT:7A# show cable loadbalance-group [<WORD>]
where:
the show cable loadbalance-group command.
The show cable modem loadbalance-group command displays cable modem load
balancing group assignments.
MOT:7A# show cable modem loadbalance-group
the show cable modem loadbalance-group command.
The show cable loadbalance-policy command displays configuration information for

all load balancing policies or a specific load balancing policy.

MOT:7A# show cable loadbalance-policy [<WORD>]

where:
WORD is the load balancing policy name.
the show cable loadbalance-policy command.
The show cable loadbalance-restricted command lists all cable modems associated
with a particular restricted load balancing group or all restricted load balancing
groups.
MOT:7A# show cable loadbalance-restricted [<1-256> | <WORD>] [snmp-index
<0-4294967295>] [ungrouped]
where:
1-256 is the load balancing group ID.
ungrouped displays the ungrouped restricted list.
the show cable loadbalance-restricted command.
The show cable loadbalance-rule command configuration information for all load
balancing rules or a specific load balancing rule.
MOT:7A# show cable loadbalance-rule [<WORD>]
where:
WORD is the load balancing rule name.
the show cable loadbalance-policy command.

Manually Moving a Cable Modem

DOCSIS Upstream Channel Change (UCC) and DOCSIS Dynamic Channel Change
(DCC) are software mechanisms that allow an operator to manually move a cable
modem to a different downstream or upstream channels. Cable modems can be moved
after registration to balance the number of cable modems evenly among the receivers
of the CMTS module so that the entire bandwidth can be used more efficiently.
The cable modem ucc command allows an operator to manually move a
DOCSIS 1.0 cable modem to a different upstream channel.
The cable modem dcc command allows an operator to manually move DOCSIS
1.1 and 2.0 cable modems to a specified downstream or upstream channel.
Manually Moving a DOCSIS 1.0 or 1.1 Cable Modem with

UCC
Use the cable modem ucc command, in Privileged EXEC mode, to move a DOCSIS
1.0 or 1.1 CM or MTA to a different upstream channel, as follows:
MOT:7A# cable modem {<mac> | <prefix>} ucc [init-tech <0-4> | logical <0-3>]>
where:
mac is the cable modems MAC address in the form xxxx.xxxx.xxxx
prefix is the cable modems IP address
init-tech 0-4 is the ranging technique used for DCC:
0 = re-initialize the MAC
1 = perform broadcast intitial ranging on the new channel before normal
operation
2 = perform unicast ranging on the new channel before normal operation
3 = perform either broadcast or unicast ranging on the new channel before
normal operation
4 = use the new channel directly without re-intializing or ranging
logical 0-3 is the upstream logical channel

Manually Moving a DOCSIS 1.1 or 2.0 Cable Modem with

DCC
Use the cable modem dcc command, in Privileged EXEC mode, to move a DOCSIS
1.1 or 2.0 CM or MTA to a different downstream or upstream channel within the same
MAC domain, as shown below:
MOT:7A(config)#cable modem {<mac> | <prefix>} dcc [downstream <0-1>
[init-tech <0-4>] | init-tech <0-4>| upstream <0-7>/<0-3> [init-tech <0-4>|
[downstream [init-tech <0-4>]]]
where:
mac is cable modem MAC address in the form of xxxx.xxxx.xxxx.
downstream 0-1 is the downstream port number
init-tech 0-4 is the ranging technique used for DCC:
0 = re-initialize the MAC
1 = perform broadcast intitial ranging on the new channel before normal
operation
2 = perform unicast ranging on the new channel before normal operation
3 = perform either broadcast or unicast ranging on the new channel before
normal operation
4 = use the new channel directly without re-intializing or ranging
upstream 0-7/0-3 is the upstream port/logical channel
Note: The upstream channel must be physically connected for DOCSIS 1.1
and 2.0 cable modems to be manually moved.
When moving a CM or MTA to a different downstream or upstream channel,

the upstream channel must be specified first followed by the downstream
channel.
The same init-tech must be specified for both the upstream and downstream
channels.

Displaying UCC/DCC Statistics

Use the show cable ucc-stats and show cable dcc-stats command to display UCC or
DCC statistics for a MAC Domain, as shown below:"
MOT:7A# show cable ucc-stats [<X/Y>]
where:
the show cable ucc-stats command.
MOT:7A# show cable dcc-stats [<X/Y>]

where:
the show cable dcc-stats command.
Clearing UCC or DCC Statistics

Use the following commands to clear statistics displayed with show cable ucc-stats
and show cable dcc-stats commands:
MOT:7A#clear cable ucc-stats [X/Y]
MOT:7A#clear cable dcc-stats [X/Y]
where:

Redistributing CMTS Traffic Among HSIMs

The BSR automatically binds a CMTS module to an HSIM (NIM) by default. An
operator may use the bind cmts command to manually bind a CMTS module to
another HSIM module if a problem is suspected on this HSIM, or to optimize network
efficiency so that CMTS traffic can be appropriately mapped or bound to other
HSIMs. For example, if an HSIM is having hardware or software problems, the
operator can use the bind cmts command to map a CMTS modules traffic to another
HSIM in order to exempt the problem HSIM from passing CMTS traffic so it can be
properly debugged without interrupting network operation.
The balance command automatically redistributes all unbound CMTS module traffic
across the available HSIM modules in the BSR chassis. For example; if there are 7
CMTS modules in the BSR, and 3 have been manually bound using the bind cmts
command, issuing the balance command redistributes the remaining 4 CMTS
modules traffic while leaving the manually bound CMTS modules traffic unaffected.
Follow these steps to redistribute CMTS traffic among HSIMs:
1. Use the slot command in Global Configuration mode to enter a populated CMTS
module slot:
MOT:7A(config)#slot <NUM>
where:
NUM is the number of the CMTS module slot.
For example:
MOT:7A(config)#slot 2
The following prompt displays:
MOT:7A(config-slot02)#
2. Use the bind hsim command in Slot Configuration mode to re-distribute the
CMTS modules traffic to a specified HSIM:
Note: The no bind hsim command manually unbinds the specified CMTS
module from an HSIM module returning it to its default state.
MOT:7A(config-slot02)#bind hsim <NUM>

where:
NUM is the number of the HSIM slot to which the CMTS module is bound
3. Use the balance command in Global Configuration mode, to automatically
redistribute the CMTS modules traffic across the available HSIM modules in the
BSR chassis:
Note: The balance command can be accessed in all modes except User
EXEC mode.
MOT:7A(config-slot02)#balance
Displaying CMTS to HSIM Bindings

Use the show bindings command to display bindings, or mapping, between CMTS
and HSIM modules:
MOT:7A(config-if)7A#show bindings
the show bindings command.

14
Configuring PacketCable
Overview
The BSR fully supports the Cablelabs PacketCable 1.x and PacketCable
Multimedia (PCMM) specifications. PacketCable Multimedia, building on the VoIP
capabilities of PacketCable 1.x, provides an IP-based platform for delivering
Quality-of-Service (QoS)-enhanced multimedia services over DOCSIS 1.1 and 2.0
HFC networks. Using PacketCable Multimedia, cable operators can offer subscribers,
in addition to the VoIP telephony services available through PacketCable 1.x,
additional services that include interactive gaming, streaming media, video telephony,
and video conferencing.
PacketCable and PacketCable Multimedia Components

Both PacketCable and PacketCable Multimedia share many of the same architectural
components. The basic difference is that PacketCable provides Quality-of-Service
(QoS) that is independent of applications, while PacketCable Multimedia provides
QoS to applications.

Table Table describes the PacketCable and PacketCable Multimedia functional

components.
Table Required PacketCable and PacketCable Multimedia Functional Components
Functional
Component Description PC PCMM
Application Controls application sessions and communicates with the Customer No Yes
Manager (AM) Premises Equipment (CPE) Client to enable an application or service
and the Policy Server to pass Quality-of-Service information.
Call Management Maintains and manages PacketCable Network Call Signaling (NCS) Yes No
Server (CMS). based Voice over IP (VoIP) calls.
Policy Server Also referred to as the Policy Decision Point (PDP). The Policy Server No Yes
(PS) applies a policy and manages the relationships between AM(s) and
Cable Modem Termination System(s).
Multimedia A device that provides an interface for a subscribers telephone Yes Yes
Terminal Adapter service. A Terminal Adapter (TA) that is embedded into a cable
(MTA) modem becomes an EMTA.
Client A Client can be a Multimedia Terminal Adapter or other CPE device No Yes
that communicates directly with the Application Manager, such as a
gaming console or PC.
Common Open Protocol used to communicate a Quality-of-Service-related decision Yes Yes
Policy Service message to and from a Policy Decision Point (Policy Server and Call
(COPS) Management Server) and Policy Enforcement Point (BSR).
Cable Modem In a PacketCable or PacketCable Multimedia environment, the CMTS Yes Yes
Termination enforces and manages Quality-of-Service policies through DOCSIS
System (CMTS) service flows (i.e. the BSR). The CMTS is referred to as the cable
interface in this document.
Event Message All Quality-of-Service activities on the BSR are collected and sent Yes Yes
System through event messages to a Record Keeping Server for further
processing.
Record Keeping Stores event messages which are used by applications for billing, Yes Yes
Server (RKS) settlements, network usage monitoring, and fraud detection purposes.
Media Server Plays announcements based on the state of the phone call, which is Yes No
(MS) determined by the Call Management Server. For example, "The
number you have reached has been disconnected."
Media Gateway Provides an interface to the Public Switched Telephone Network Yes No
(MG) (PSTN).
Signaling Handles the signaling and call control functions to "bridge the gap" Yes No
Gateway (SG) between the PSTN and IP networks.

Release 5.3.1 Configuring PacketCable
Table Required PacketCable and PacketCable Multimedia Functional Components
Functional
Component Description PC PCMM
Media Gateway Manages the connection with the PSTN by controlling the Media Yes No
Controller (MGC) Gateway and Signaling Gateway and maintains the call state for calls
requiring PSTN interconnection.
IP Security Encrypts data flowing between a gateway and a host, a pair of Yes Yes
(IPSec) gateways, or between a pair of hosts.
Internet Key Authenticates IPSec peers, negotiates IPSec security associations for Yes Yes
Exchange (IKE) the data flow, and negotiates and extracts keys for IPSec. IKE is
Management asynchronous to call signaling messages and does not contribute to
any delays during communications setup.
Electronic Requirement for the Communications Assistance for Law Yes No
Surveillance Enforcement Act (CALEA). Cable operators must satisfy CALEA
requirements if they are a PacketCable Telecommunications Service
Provider (PC/TSP) because this BSR feature provides any Law
Enforcement Agency (LEA) with Call Data Content (CDC) and Call
Content Connection (CCC) information.
Note: For detailed PacketCable and PacketCable Multimedia information,

refer to the CableLabs PacketCable specifications. These specifications are
available at the CableLabs website: http://www.packetcable.com/
specifications/
Configuration Task Summary

PacketCable and PacketCable Multimedia share many configuration procedures, but
also have specific configuration procedures. Configure the common configuration
tasks first, then complete those configuration tasks that are specific to the network you
intend to configure (PacketCable 1.x or PacketCable Multimedia).
The following sections contain common network configuration tasks, PacketCable
specific tasks, PacketCable Multimedia specific tasks, and Related Tasks:
Common Network Configuration Tasks
PacketCable and PacketCable Multimedia Configuration Tasks
Related Tasks

Common Network Configuration Tasks

Table Table provides a common configuration task summary:
Table Common Configuration Task Summary
Task Refer to:

1. Specify the network or loopback interface IP Specifying the Protocol IP Address on page 14-6
address used for the PacketCable protocols.
2. Restrict COPS Connections to a specified Restricting COPS Connections on page 14-7
Policy Decision Point (PDP) (optional).
3. Specify the Policy Enforcement Point to Specifying the Policy Enforcement Point on page 14-7
uniquely identify the BSR(s) that are within
the PacketCable/PacketCable Multimedia
domain (optional).
4. Enable event messages. Enabling the Event Message System on page 14-9
5. Configure the security policy. Configuring a Security Policy Using IPSec and IKE on
page 14-15
6. Enable IP Security (IPSec) and Internet Key Enabling IPSec and IKE on page 14-21
Exchange (IKE) protocols.
PacketCable and PacketCable Multimedia Configuration

Tasks
Table Table provides a summary of tasks specific to PacketCable 1.x and
PacketCable Multimedia:
Table PacketCable and PacketCable MultimediaConfiguration Task Summary
Task Refer to:

1. Enable Dynamic Quality-of-Service (DQoS). Enabling DQoS on page 14-25
2. Configure each cable interface to accept
Dynamic Service.
1. Enable PacketCable Multimedia. Enabling PacketCable Multimedia on page 14-29

Related Tasks
Table Table provides a summary of tasks related to both PacketCable and
PacketCable Multimedia:
Table Related Task Summary
Task Refer to:

Enable the COPS status SNMP Trap to view the Enabling the COPS Status SNMP Trap on page 14-31
status of COPS connections.
Enable the Emergency Call SNMP Trap for Enabling the Emergency Call SNMP Trap on page 14-31
emergency calls.
Enable the Resource Request SNMP Trap to Enabling the Resource Request SNMP Trap on page
view resource problems. 14-32
Tear down a gate. Clearing Gates on page 14-32
Clear PacketCable statistics. Clearing PacketCable Statistics on page 14-33
Clear PacketCable configuration. Clearing PacketCable Configuration on page 14-34
Entering PacketCable Configuration Mode

Before you can configure PacketCable 1.x and PacketCable Multimedia, you must
enter Packetcable Configuration mode from the BSR command line interface.
Through PacketCable Configuration mode, you can access PacketCable 1.x and
PacketCable Multimedia configuration parameters.
Use the packet-cable command, in Global Configuration mode, to enter PacketCable
Configuration mode:
MOT:7A(config)#packet-cable
The prompt changes to the following:
MOT:7A(config-pktcable)#

Configuring Common Parameters

Follow the procedures in these sections to configure parameters common to both
PacketCable 1.x and PacketCable Multimedia:
Specifying the Protocol IP Address
Configuring COPS Parameters
Configuring Event Messages
Configuring IP Security
Configuring Electronic Surveillance
Note: If PacketCable or PacketCable Multimedia is implemented on a BSR

with BGP/MPLS VPNs, the configuration must be implemented on the
"global" VPN network.
Specifying the Protocol IP Address

Use the cmts-ip command in PacketCable Configuration mode to specify the network
or loopback interface IP address used for the PacketCable protocols.
MOT:7A(config-pktcable)#cmts-ip <A.B.C.D>
where:
A.B.C.D is the network or loopback interface IP address.
Configuring COPS Parameters

Follow the procedures in these sections to configure the Common Open Policy
Service (COPS) protocol parameters for the Policy Decision Point (PDP) and Policy
Enforcement Point (PEP):
Restricting COPS Connections
Specifying the Policy Enforcement Point
Configuring the COPS Client Timer
Configuring Access Control Lists for COPS Connections
Displaying COPS Connections
Verifying the COPS Configuration

Restricting COPS Connections

The BSR accepts COPS connections from any Policy Decision Point (PDP)
IP address through a TCP connection by default. A PDP is either the Call
Management Server in the PacketCable architecture or the Policy Server in the
PacketCable Multimedia architecture where a Client/MTA policy request is either
serviced or rejected.
Use the cops pdp-ip command in PacketCable Configuration mode to restrict COPS
connections to a specific PDP:
MOT:7A(config-pktcable)#cops pdp-ip <A.B.C.D>
where:
A.B.C.D is the PDP IP address.
Repeat this step to restrict additional COPS connections to another PDP.
Note: If one or more PDP IP addresses are configured, only connections

from these PDP IP addresses are accepted. Up to 100 trusted PDP
IP addresses can be configured.
Specifying the Policy Enforcement Point

Use the cops pep-id command in PacketCable Configuration mode to specify the
default Policy Enforcement Point (PEP) text string, that is used in COPS messaging,
to uniquely identify the BSR(s) that are within the PacketCable/PacketCable
Multimedia domain:
MOT:7A(config-pktcable)#cops pep-id <WORD>
where:
WORD is a text string that is between 1 and 32 characters. The default is
Motorola CMTS
Configuring the COPS Client Timer

Follow these steps to configure the COPS Client timer:
1. Use the show packet-cable statistics gate command in PacketCable
Configuration mode.

2. If the show packet-cable statistics gate command output for the Client-Open
Sent field in the COPS Statistics section is incrementing, the network and the
PDP server need to be examined to determine the reason for the COPS Client
timeouts. The COPS Client Timer (which is the response timer for sending the
COPS Client-Open message) can be specified if COPS connections timeout
before receiving a Client-Accept message.
3. Use the cops client-timer command in PacketCable Configuration mode to
configure the amount of time permitted for the BSR to receive the Client-Accept
message from the PDP before terminating the COPS connection:
MOT:7A(config-pktcable)#cops client-timer <1-3600000>
where:
1-3600000 is the COPS Client timer value in milliseconds. The default is
3000.
Configuring Access Control Lists for COPS Connections

Configuration of an access control list (ACL) restricts COPS connections to a trusted
range of IP addresses.
MOT:7A(config-pktcable)#cops listener access-list <1-99>
where:
1-99 specifies the number of the access list.
Displaying COPS Connections

Use the show packet-cable cops command in all modes except User EXEC mode to
display COPS connections, which includes the COPS Client handle, PDP IP address,
port number, keep-alive timeout, and duration time:
MOT:7A#show packet-cable cops [inactive]
where:
inactive optionally specifies displaying all inactive COPS Client handles.
field descriptions for the show packet-cable cops command.

Verifying the COPS Configuration

Use the show packet-cable configuration cops command in all modes except User
EXEC mode to display the COPS configuration and status information for the PEP
ID, Client Timer, and verify if the Status SNMP trap is enabled.
field descriptions for the show packet-cable configuration cops command.
Configuring Event Messages

Follow the procedures in these sections to configure event messages:
Enabling the Event Message System
Configuring Event Message Parameters
Disabling Event Messages
Displaying Event Message Statistics
Enabling the Event Message System

Follow these steps to enable the event message system and specify an event message
Element ID for each BSR:
1. Use the no em shutdown command in PacketCable Configuration mode to
enable event messaging for the BSR.
2. Use the em element-number command to specify a unique event message
Element ID for the BSR:
MOT:7A(config-pktcable)#em element-number <0-99999>
where:
0-99999 is the Element ID number. The default is 0.
3. Use the show packet-cable configuration em command to verify that event
messages are enabled and the event message Element ID number is configured
properly.
and field descriptions for the show packet-cable configuration cops command.

Configuring Event Message Parameters

Follow the procedures in these sections to configure event message parameters:
Configuring the Priority for Event Messages
Configuring the UDP Port for Event Messages
Configuring the Retry Interval
Configuring the Retry Message Count
Configuring the Hold-time for Batched Event Messages
Configuring the Number of Batched Event Messages
Configuring a Mask for Disabling Event Messages
Overriding the Event Message Flag Function
Disabling the Event Message QoS Descriptor
Configuring the Priority for Event Messages

Based on the overall PacketCable network, the Record Keeping Server can prioritize
event messages from the BSR. The higher the number, the lower the priority.
Use the em event-priority command in PacketCable Configuration mode to
configure the priority value of event messages generated from the BSR relative to
other events:
MOT:7A(config-pktcable)#em event-priority <0-255>
where:
0-255 is the event priority ranking. The default is 128.
Configuring the UDP Port for Event Messages

If the default UDP port is already in use, another UDP port can be configured for
PacketCable event messages. A different UDP port can also be configured for event
messages to enhance security.
Use the em udp-port command, in PacketCable Configuration mode, to configure a
UDP port number for event messages:
MOT:7A(config-pktcable)#em udp-port <1-65535>
where:
1-65535 is the UDP port number. The default is 1813.

Configuring the Retry Interval

When a Record Keeping Server receives and records an Accounting-Request event
message from the BSR, it sends an Accounting-Response message to the BSR. If the
BSR does not receive an Accounting-Response message within the configured retry
interval, it sends another Accounting-Request message to the Record Keeping Server.
The event message retry interval can be configured depending on the amount of
network congestion and the distance between the BSR and the Record Keeping
Server. For example, if the distance caused a time delay, the event message retry
interval can be extended from the default value to allow more time for the BSR to
receive an Accounting-Response message. The network and the Record Keeping
Server should be examined to determine the reason for these timeouts. In most cases
the em retry-count command parameter should be increased before the em
retry-interval command parameter is modified.
Use the em retry-interval command, in PacketCable Configuration, mode to
configure the event message retry interval for receiving an Accounting Response.
MOT:7A(config-pktcable)#em retry-interval <1-3600>
where:
1-3600 is the retry interval in seconds. The default is 2.
Configuring the Retry Message Count

If an Accounting-Response event message is not received by the BSR from the
Record Keeping Server, the BSR sends the event message again. Once all retries are
exhausted, the BSR tries an alternate Record Keeping Server (if one is available).
The network and the Record Keeping Server should be examined to determine the
reason for these timeouts. The event message retry count can be specified depending
on the amount of network congestion and the distance between the BSR and the
Record Keeping Server.
Follow these steps to configure the event message retry count:
1. Use the show packet-cable statistics command to determine if the event
message retry count needs to be changed.
2. If network congestion causes reported timeouts in the Account Request Failure
field in the show packet-cable statistics command output, Use the em
retry-count command in PacketCable Configuration mode to change the number
of event message retries:
MOT:7A(config-pktcable)#em retry-count <1-16>

where:
1-16 is the retry count. The default is 3.
Configuring the Hold-time for Batched Event Messages

The hold-time for batched event messages can be configured to allow more time so
that multiple event messages can be combined into one packet to reduce network
traffic.
Use the em max-batch-time command, in PacketCable Configuration mode, to
configure the interval that the batched event messages are held before they are sent to
the Record Keeping Server:
MOT:7A(config-pktcable)#em max-batch-time <1-60>
where:
1-60 is the time in seconds for batched event messages to be withheld. The
default is 10.
Configuring the Number of Batched Event Messages

The number of batched event messages can be configured so that multiple event
messages can be combined into one packet to reduce network traffic.
Event messages are batched together before being sent to the Record Keeping Server.
Use the em max-batch-events command, in PacketCable Configuration mode, to
configure the amount of event messages that are batched. The collected messages are
sent when the em max-batch-time parameter expires.
MOT:7A(config-pktcable)#em max-batch-events <2-32>
where:
2-32 is the maximum batched event messages. The default is 6.
Configuring a Mask for Disabling Event Messages

An MSO can disable unwanted event messages to reduce network traffic.
Use the em event-disable-mask command, in PacketCable Configuration mode, to
configure a hexidecimal mask to disable event messages:
MOT:7A(config-pktcable)#em event-disable-mask <0x00000000-0xffffffff>
where:
0x00000000-0xffffffff sets the bits that correspond to event message IDs that are
disabled. The default is 0x0 (no mask).

Table Table describes the QoS event message bit definitions:
Table Event Message Bit Definitions
Event Message Bit Definition 1 Based Hexidecimal value

QoS_Reserve 7 0x00000040
QoS_Release 8 0x00000080
Time_Change 17 0x00010000
QoS_Commit 19 0x00040000
For example, if the QoS_Reserve event message is disabled, the following command
is entered:
MOT:7A(config-pktcable)#em event-disable-mask 0x00000040
Note: Hexidecimal values can also be combined. For example,

QoS_Release and QoS_Commit event messages can be disabled by
entering the hexidecimal number: 0x00040080.
Overriding the Event Message Flag Function

The Call Management Server handles the logging of event messages to the Record
Keeping Server. This is done in either batch mode (putting event messages together in
a packet) or in real-time mode (sending event messages in packets as they come). The
event flag, which tells the BSR to send event messages to the Record Keeping Server,
can be overridden.
Use the em flag-override command, in PacketCable Configuration mode, to force the
BSR to use real-time mode or batch mode regardless of what the Call Manager Server
directs the BSR to do:
MOT:7A(config-pktcable)#em flag-override {realtime | batch}
where:
realtime sends the event message in real-time mode.

batch sends the event message in batch mode.
Note: PacketCable Multimedia supports real-time mode only.
Disabling the Event Message QoS Descriptor

The QoS Descriptor attribute can be disabled if an MSO decides it does not need it
because it wants to reduce the size of the event messages for network traffic
management purposes.
The QoS Descriptor attribute contains the Service Class profile name and QoS
parameters. Use the em qos-descriptor-disable command, in PacketCable
Configuration mode, to disable the QoS Descriptor attribute.
Disabling Event Messages

Use the em shutdown command, in PacketCable Configuration mode, to disable
event messages generated from the BSR if they are not needed.
Note: Event messages are enabled by default.
Displaying Event Message Statistics

Use the show packet-cable statistics em command to display event messages or Gate
statistical information.
the show packet-cable statistics em command.

Configuring IP Security
Both voice and signaling data that is transmitted over the PacketCable/PacketCable
Multimedia network must be protected. The BSR uses the Internet Protocol Security
(IPSec) and Internet Key Exchange (IKE) protocols for security and key management.
The security between the CMTS and CM is established through DOCSIS Baseline
Privacy Plus (BPI+).
Follow the procedures in these sections to configure IPSec and IKE:
Configuring a Security Policy Using IPSec and IKE
Configuring IPSec and IKE Parameters
Enabling IPSec and IKE
Deleting Security Policy Database Policy Entries
Displaying the IPSec Configuration
Configuring a Security Policy Using IPSec and IKE

A security policy that contains the following attributes must be configured to protect
the network traffic between two IPSec peers:
source and destination address
source and destination port
protocol type to identify the traffic
encryption algorithm
authentication method
key lifetime for the traffic
The IPSec Security Policy Database (SPD) specifies what security services are
offered to the IP traffic depending on source and destination IP address and port
number and protocol type.
Specifying Security Policy Database Pre-shared Keys

Follow these steps to specify the Pre-shared Keys for the SPD:
Note: The pre-shared key configured in this section must match the
pre-shared key that is configured on the Call Management Server/Gate
Controller or Policy Server and Record Keeping Servers.

1. Use the ipsec command from Global Configuration mode to enter IPSec
Configuration mode.
2. Use the spd preshared-key command to configure the Pre-shared Key IP address
to allow a Pre-shared secret key to be passed between parties in a communication
flow to authenticate their mutual identities:
MOT:7A(config-ipsec)#spd preshared-key <A.B.C.D> <string>
where:
A.B.C.D is the IP address of the cable interface.
string is the name of the Pre-shared Key which is between 1 to 128
characters.
3. Repeat Step 2 if more Pre-shared Key IP addresses must be configured or go to
the next step.
4. Use the show ipsec spd preshared-key to verify the SPD pre-shared key
configuration.
In the following example, the IP address of the Call Management Server/Gate
Controller or Call Management Server/Policy Server is 10.1.40.63 with the
Pre-shared Key PACKETCABLE and the IP address of the Record Keeping
Server is 10.1.40.70 with the Pre-shared Key PACKETCABLE:
MOT:7A(config-ipsec)#spd preshared-key 10.1.40.63 PACKETCABLE
MOT:7A(config-ipsec)#spd preshared-key 10.1.40.70 PACKETCABLE
MOT:7A(config-ipsec)#show ipsec spd preshared-key
Index Dest IP Address Key Len Key
1 10.1.40.63 11 PACKETCABLE
2 10.1.40.70 11 PACKETCABLE
Specifying the Security Policy Database

The Security Policy Database (SPD) policy is priority based. The lower number index
has a higher priority. The data packets are compared against rules in the SPD policy,
starting with the first index. When a match is found, that rule is applied and no further
comparisons are made against the SPD policy for that data packet.
The SPD adds two rules to the policy during initialization. The first rule forces data
that is specific to the IKE protocol to bypass. The second rule, which is the lowest
priority, discards any packet which has not matched a higher priority rule.
Follow these steps to specify the SPD policy:

1. Use the ipsec command in Global Configuration mode to enter IPSec

Configuration mode.
2. Use the spd policy command to specify a security policy for the given peers for
the IPSec SPD:
MOT:7A(config-ipsec)#spd policy <ipAddr{-ipAddr2|:ipMask}>
<ipAddr{-ipAddr2|:ipMask}> <num> <0-65535> <0-65535> {apply transport |
bypass | discard} [after <num>]
where:
ipAddr{-ipAddr2|:ipMask} is the source network IP address followed by a
colon and subnetwork mask. If a hyphen is used between ipAddr and
ipAddr2, this specifies a range of source network IP addresses.
ipAddr{-ipAddr2|:ipMask} is the destination network IP address followed by
a colon and subnetwork mask. If a hyphen is used between ipAddr and
ipAddr2, this specifies a range of destination network IP addresses.
num is the transport protocol number which is the IP protocol from the IP
protocol header. The format is a decimal number. A value of 0 represents
any protocol. For example, the Call Management Server/Gate Controller or
Call Management Server/Policy Server can use TCP Port 6 and the Record
Keeping Server can use UDP Port 17.
0-65535 is the source TCP/UDP port number. 0 represents any port.
0-65535 is the destination TCP/UDP port number. 0 represents any port.
apply transport is used if the packet matches the rule for this policy (i.e.,
ipAddr, ipAddr2, num, source port, or destination port matches the packet
being processed), then apply transport mode IPSEC to the IP Packet.
bypass is used if the packet matches the rule for this policy (i.e., ipAddr,
ipAddr2, num, source port, or the destination port matches the packet being
processed), then the IPSEC processing is bypassed and the IP packet is
processed.
discard is used if the packet matches the rule for this policy (i.e., ipAddr, ip
Addr2, num, source port, or dest port matches the packet being processed),
then discard this IP packet.
after optionally allows a rule to be inserted after an existing rule in the SPD.
If the after is not present, the new rule is added to the first index.

num is the policy security entry number. The index numbering begins at 1.
3. Use the spd policy bypass command to specify the default bypass policy to allow
a non-protected date to pass:
MOT:7A(config-ipsec)#spd policy 0.0.0.0-255.255.255.255 0.0.0.0-
255.255.255.255 0 0 0 bypass
4. Use the show ipsec spd policy command to verify if SPD policy is configured
correctly.
for the show ipsec spd policy command.
Overriding SPD Configurations

Use the spd override command in IPSec Configuration mode to override IP
addresses, ports, or protocols that are configured in the IPSec Security Policy
Database (SPD).
MOT:7A(config-ipsec)#spd override [addr-selector | port-selector |
protocol-selector]
where:
addr-selector sets the SPD to override a specific IP address within a range of IP
addresses set in the SPD or a wild card IP address set in the SPD.
port-selector sets the SPD to override a specific port with a range of port(s) or
wild card set in the SPD.
protocol-selector sets the SPD to override a specific protocol with a range of
protocol or wild card of protocol set in the SPD.
Note: By default, no SPD override address selector is configured. However,

the SPD override port selector and SPD override protocol selector are
configured by default.

Allowing a Peer to Negotiate a Connection with the SPD

Use the spd allow-dynamic-rsp command in IPSec Configuration mode to allow a
dynamic response from a peer to negotiate Internet Key Exchange (IKE) even though
the IPSec Security Policy Database (SPD) policy setting is other than the "APPLY"
policy setting.
Note: By default, the BSR strictly follows the configured SPD.
Displaying the Security Associations Database Configuration

The Security Associations Database (SADB) specifies cryptographic keys and
algorithms, which are used to secure data transfer for IPsec and IKE. Use the
show ipsec sadb command to display its configuration.
the show ipsec sadb command.
Configuring IPSec and IKE Parameters

Follow the procedures in these sections to configure IPSec and IKE network
parameters:
Configuring IKE Retransmissions
Configuring the IKE Retransmission Timeout Interval
Configuring the IKE Phase 1 Lifetime Interval and Lifesize Value
Configuring IKE Retransmissions

Follow these steps to configure the number of IKE retries for network problems:
Configuration mode.
2. Use the show ipsec ike command in IPSec Configuration mode.
3. Observe the number of IKE retries in the show ipsec ike command output. If the
number of IKE retries is increasing, then the network and server should be
examined to determine the reason for the excessive number of IKE retries.
4. Use the ike retries command to configure the number of IKE retries:

MOT:7A(config-ipsec)#ike retries <1-10>

where:
1-10 is the retries permitted. The default is 3.
Configuring the IKE Retransmission Timeout Interval

Follow these steps to configure the IKE retransmission timeout interval for network
problems.
Configuration mode.
2. Use the show ipsec ike command in IPSec Configuration mode.
3. Observe the number of IKE timeouts in the show ipsec ike command output. If
the number of IKE timeouts is increasing, then the network and server should be
examined to determine the reason for the excessive number of IKE timeouts.
4. Use the ike timeout command to configure the IKE retransmission timeout
interval:
MOT:7A(config-ipsec)#ike timeout <1-20>
where:
1-20 is the timeout interval in seconds. The default is 10.

The IKE Phase 1 Lifetime interval and IKE Phase 1 Lifesize can be configured to
enhance security. These settings determine how long the key is exposed. For example,
an MSO administrator can decide to update this key on a regular basis to prevent
successful hacking.
Follow these steps to configure the IKE Phase 1 Lifetime interval and Lifesize value:
Configuration mode.
2. Use the ike phase1 lifetime command in IPSec Configuration mode to configure
the IKE phase 1 lifetime value and the lifesize value that can either trigger or
prevent the expiration of the IKE security association:
MOT:7A(config-ipsec)#ike phase1 lifetime <0, 300-2592000> [lifesize <0,
10240-4190000>]

where:
0, 300-2592000 is the lifetime interval value in seconds. The default is
28800. Zero indicates an unlimited lifetime.
0, 10240-4190000 is the lifesize value in kilobytes. The default is 0, which
indicates an unlimited value in kilobytes.

The IKE Phase 2 Lifetime Interval and IKE Phase 2 Lifesize can be configured to
enhance security. These settings determine how long the key is exposed. For example,
an MSO administrator can decide to update this key on a regular basis to prevent
successful hacking.
Follow these steps to configure the IKE Phase 2 Lifetime interval and Lifesize value:
Configuration mode.
2. Use the ike phase2 lifetime command in IPSec Configuration mode to configure
the IKE phase 2 lifetime value, and optionally configure the lifesize value for the
lifetime:
MOT:7A(config-ipsec)#ike phase2 lifetime <0, 300-2592000> [lifesize
<0, 10240-4190000>]
where:
0, 300-2592000 is the lifetime interval value in seconds. The default is
28800. Zero indicates an unlimited time.
0, 10240-4190000 is the lifesize value in kilobytes. The default is 0, which
indicates an unlimited size.
Enabling IPSec and IKE

Follow these steps to enable PacketCable IPSec and IKE:
Configuration mode.
2. Use the ike client-addr command in IPSec Configuration mode to specify the IP
address used by the BSR for its source address during IKE protocol exchanges.
MOT:7A(config-ipsec)#ike client-addr <A.B.C.D>
where:

A.B.C.D is the host IP address used for IKE.

3. Use the no ipsec shutdown command to enable IPSEC and IKE.
Caution: Improperly configured policies could prevent all IP traffic going in

and/or out of the BSR.
Deleting Security Policy Database Policy Entries

Follow these steps to delete Security Policy Database (SPD) policy entries:
1. Use the no spd policy command in IPSec Configuration mode to delete SPD
entries when they are no longer needed. A single rule or all the rules in the table
can be deleted at once:
MOT:7A(config-ipsec)#no spd policy {all | <num>}
where:
all deletes all entries in the SPD.
num deletes a specific rule from the SPD specified by the index number.
Note: Use caution when deleting more than one SPD entry, because the
SPD index numbers change whenever an index is deleted.
2. Use the show ipsec spd policy command to verify if the appropriate SPD policy
was deleted.
Displaying the IPSec Configuration

Use the following commands in all modes except User EXEC mode to display the
IPSec configuration.
Use the show ipsec ike command to display the IKE configuration.
for the show ipsec ike command.
Use the show ipsec ipsec command to display the IPSec configuration.

for the show ipsec ipsec command.
Configuring Electronic Surveillance

Use the following command option,s in PacketCable Configuration mode, to
configure electronic surveillance:
Electronic surveillance is disabled by default. Use the no es shutdown command
to enable electronic surveillance.
Use the es shutdown command to disable the electronic surveillance.
Use the es trap-enable command to enable or disable the electronic surveillance
SNMP trap:
MOT:7A(config-pktcable)#es trap-enable {disable | enable}
where:
disable disables the electronic surveillance SNMP trap.
enable enables the electronic surveillance SNMP trap. The default is
disabled.
Note: Electronic surveillance conforms to Communications Assistance for

Law Enforcement Act (CALEA) requirements.
Use the following commands to clear electronic surveillance information:

Use the clear packet-cable statistics es identifier command, in Privileged
EXEC mode, to clear duplicated packet and byte counts:
MOT:7A#clear packet-cable statistics es identifier <0x00000000-0xffffffff>
where:
0x00000000-0xffffffff clears a specific ES identifier.
Use the clear configuration es command in PacketCable Configuration mode to
clear electronic surveillance SNMP traps and reset es trap-enable to "disabled".

Displaying Electronic Surveillance Information

Use the following show commands to display electronic surveillance information.
Use the show packet-cable configuration es command to display electronic
surveillance configuration information.
for the show packet-cable configuration es command.
Use the show packet-cable statistics em command to display event message
statistical information including the electronic surveillance generated
QoS-Reserve, QoS-Commit and QoS-Release event counts.
for the show packet-cable configuration em command.
Use the show packet-cable statistics es identifier command to display
duplicated byte and packet counts along with the gates IP address and UDP
port.
MOT:7A#show packet-cable statistics es identifier <0x00000000-0xffffffff>
where:
0x00000000-0xffffffff is the gate identifier in hexadecimal notation.
for the show packet-cable statistics es identifier command.
Note: The statistics for an inactive gate are not displayed.

Configuring PacketCable Specific Parameters

If you intend to configure a PacketCable 1.x network and have already completed the
common configuration tasks as described in Table Table on page 14-4, then complete
the procedures in this section. These procedures are specific to PacketCable 1.x.
PacketCable is configured in the following sections by enabling Dynamic
Quality-of-Service (DQoS), configuring each PacketCable cable interface to accept
DQoS gates, and optionally configuring DQoS Gate Timers:
Enabling DQoS
Configuring DQoS Parameters
Enabling DQoS
Follow these steps to enable Dynamic Quality-of-Service (DQoS) and configure each
PacketCable cable interface to accept DQoS gates:
1. Use the no dqos shutdown command in PacketCable Configuration mode to
enable DQoS.
2. Use the end command to go back to Global Configuration mode.
3. Use the interface cable command to enter a cable interface:
where:
4. \Use the cable dynamic-service authorization-mode command in Interface
Configuration mode to allow each PacketCable cable interface to accept dynamic
service:
MOT:7A(config-if)#cable dynamic-service authorization-mode
{auth_no_ecn02064 | authorize | unauthorize}
where:
auth_no_ecn02064 authorizes Dynamic Service based on DQoS gates
without PacketCable ECN 2064 support.
authorize authorizes CM initiated Dynamic Service based on DQoS gates.
This argument is required when DQoS is enabled.
unauthorize accepts all Dynamic Service.

5. Use the end command to exit the cable interface and return to Global
Configuration mode.
6. Repeat Step 3 through Step 5 if more cable interfaces need to accept dynamic
service.
7. Use the show cable dynamic-service command to verify the dynamic service
configuration status for the configured cable interfaces.
for the show cable dynamic-service command.
8. Use the show packet-cable configuration dqos command to verify the DQoS
configuration.
for the show packet-cable configuration dqos command.
Configuring DQoS Parameters

Follow the procedures in these sections to configure DQoS parameters:
Configuring DQoS Gate T0 and T1 Timers
Displaying Gates
Displaying Gate Statistics
Configuring DQoS Gate T0 and T1 Timers

The DQoS Gate Timers have default parameter settings associated with them and they
do not have to be configured. If T0 and T1 timeouts are being counted in the show
packet-cable statistics gate command output, the network and the PDP server need
to be examined. T0 and T1 timers may need to be increased from their default values
to avoid T0 and T1 timeouts.
The BSR considers the assigned gate ID to be invalid when the DQoS Gate Timer
T0 timer expires.
Use the dqos t0-timer command in PacketCable Configuration mode to limit the
period of time that a gate can be allocated without the gate parameters being
configured:
MOT:7A(config-pktcable)#dqos t0-timer <1-3600>
where:
1-3600 is the timer value in seconds. The default is 30.

The BSR clears all resources reserved for a gate (depending on the state of the
gate) when the DQoS gate Timer T1 expires, which causes the MTA or Client to
delete the gate.
Use the dqos t1-timer command in PacketCable Configuration mode to
configure the T1 timer:
MOT:7A(config-pktcable)#dqos t1-timer <1-3600>
where:
Displaying Gates
Use the following show commands to display gate information.
Use the show packet-cable gate command to display the gate ID in hexidecimal
notation, CM MAC address, CPE (subscriber) IP address, cable interface slot
number, upstream and downstream Service Flow Identifier (SFID) number, status
and committed time gate summary information.
Use the show packet-cable gate identifier command to display detailed gate
information for a specified gate ID:
MOT:7A#show packet-cable gate identifier <0x0-0xffffffff>
where:
0x0-0xffffffff is the specified hexidecimal number for the gate ID.
Use the show packet-cable gate cops command to display gate summary
information for the specified COPS Client handle:
MOT:7A#show packet-cable gate cops <0-99>
where:
0-99 is the specified COPS Client handle.

Use the show packet-cable gate slot command to display gate summary
information for the specified cable interface slot:
MOT:7A#show packet-cable gate slot <NUM>
where:
NUM is the cable interface slot number.
Use the show packet-cable gate modem command to display gate summary
information for a specified CM:
MOT:7A#show packet-cable gate modem <mac>
where:
mac is the MAC address of the CM.
Use the show packet-cable gate subscriber command to display gate summary
information for the specified MTA or Client subscriber using their IP address:
MOT:7A#show packet-cable gate subscriber <A.B.C.D>
where:
A.B.C.D is the IP address of the MTA or Client subscriber.
the show packet-cable gate commands.
Displaying Gate Statistics

Use the show packet-cable statistics gate command in all modes except User EXEC
mode to display detailed statistics for all DQoS gates.
the show packet-cable statistics gate command.

Configuring PacketCable Multimedia Specific

Parameters
If you intend to configure a PacketCable Multimedia network and have already
completed the common configuration tasks as described in the Table on Page 13-4,
then complete the procedures in this section. These procedures are specific to
PacketCable Multimedia.
PacketCable Multimedia is configured in the following sections by enabling
PacketCable Multimedia and optionally configuring the Multimedia Gate Timer T1:
Enabling PacketCable Multimedia
Configuring the Multimedia Gate Timer T1
Enabling PacketCable Multimedia

Follow these steps to enable PacketCable Multimedia:
1. Use the no mm shutdown command in PacketCable Configuration mode to
enable PacketCable Multimedia and COPS operation on the BSR.
2. Use the show packet-cable configuration mm command to verify if
PacketCable Multimedia operation is enabled.
for the show packet-cable configuration mm command.
Configuring the Multimedia Gate Timer T1

The Multimedia Gate Timer T1 has a default setting for the interval that elapses
between authorizing and reserving a PacketCable Multimedia gate.
The multimedia T1 timer starts when a gate is authorized. The Multimedia T1 timer is
stopped when an operation is performed (e.g. The gate state is switched to Reserved).
On expiration of this timer, the BSR deletes the gate.
Follow these steps to configure the multimedia T1 timer:
1. Use the mm t1-timer command in PacketCable Configuration mode to configure
the multimedia T1 timer:
MOT:7A(config-pktcable)#mm t1-timer <1-3600>
where:

2. Use the show packet-cable configuration mm command to verify the

Multimedia T1 Timer setting.
PacketCable DSCP
The PacketCable Differentiated Services Code Point (DSCP) feature allows an
operator to configure the DSCP field on IP packet headers for PacketCable traffic
generated by the BSR. The DSCP field can be configured for DQoS, MM, EM and
ES.
Differentiated services enhancements enable scalable service discrimination in a
network without the need for per-flow state and signaling at every hop. Differentiated
services can be constructed by a combination of:
1. setting bits in an IP header field at network boundaries
2. using those bits to determine how packets are forwarded by the nodes inside the
network and
3. conditioning the marked packets at network boundaries in accordance with the
requirements or rules of each service
The following commands are used to configure the PacketCable DSCP feature:
dqos dscp
em dscp
es ccc-dscp
mm dscp
Refer to the BSR 64000 Command Reference Guide for information on these
commands.
Configuring Related PacketCableTasks

Follow the procedures in these sections to configure related PacketCable tasks:
Clearing All COPS Connections
Enabling the COPS Status SNMP Trap
Clearing Gates
Clearing PacketCable Statistics
Clearing PacketCable Configuration

Clearing All COPS Connections

Use the clear cops pdp-ip all command in PacketCable Configuration mode to
remove all Policy Decision Point (PDP) IP addresses, which causes all COPS
connections to be cleared.
Enabling the COPS Status SNMP Trap

Use the cops status-trap enable command, in PacketCable Configuration mode, to
optionally enable the COPS status SNMP trap through the DQoSCopsTrap SNMP
MIB object.
MOT:7A(config-pktcable)#cops status-trap-enable [enable | disable]
where:
enable enables COPS status SNMP trap. The default is disabled.
disable disables COPS status SNMP trap.
If the COPS status SNMP trap is enabled, the BSR generates an SNMP trap when one
or more of the following conditions occur:
a keep alive timeout
the COPS connection is disconnected
a failure to establish a TCP connection
a COPS connection is established
an unauthorized PDP attempt to establish a COPS connection
Enabling the Emergency Call SNMP Trap

Use the dqos emergency-trap command, in PacketCable Configuration mode, to
optionally enable an SNMP trap for Emergency Calls through the
rdnPktDQoSEmergencyTrapEnable SNMP MIB object:
MOT:7A(config-pktcable)#dqos emergency-trap-enable [enable | disable]
where:
enable enables Emergency Call SNMP trap. The default is disabled.
disable disables Emergency Call SNMP trap.
If the Emergency Call SNMP trap is enabled, the BSR generates an SNMP trap if an
Emergency Call is initiated.

Enabling the Resource Request SNMP Trap

Use the dqos res-req-trap command, in PacketCable Configuration mode, to
optionally enable the Resource Request SNMP trap through the DQoSResReq SNMP
MIB object.
MOT:7A(config-pktcable)#dqos res-req-trap-enable [enable | disable]
where:
enable enables Resource Request SNMP trap. The default is disabled.
disable disables Resource Request SNMP trap.
If the Resource Request SNMP trap is enabled, the BSR generates an SNMP trap if a
Resource Request from an MTA is invalid. This would include one or more of the
following conditions:
an invalid gate ID (DSA-REQ contains an unknown gate ID)
a missing gate ID (DSA-REQ is missing gate ID)
requested resources are exceeded
Clearing Gates
PacketCable gate information can be displayed using the show packet-cable gate
command, which provides the information necessary to clear them.
the show packet-cable gate command.
Use the following commands, in Privileged EXEC mode, to clear PacketCable gate
information:
Use the clear packet-cable gate identifier command to clear the specified Gate
ID:
MOT:7A#clear packet-cable gate identifier <0x0 - 0xffffffff>
where:
0x0-0xffffffff is the specified hexidecimal number for the Gate ID.
For example:
MOT:7A#clear packet-cable gate identifier 0x6bde0001
Use the clear packet-cable gate all command to clear all gates:

Use the clear packet-cable gate cops command to clear all gates for a COPS
Client handle:
MOT:7A#clear packet-cable gate cops <0-99>
where:
0-99 specifies the specific COPS Client handle.
Use the clear packet-cable gate slot command to clear all gates associated with a
specified BSR slot number:
MOT:7A#clear packet-cable gate slot <NUM>
where:
NUM specifies the specific BSR slot number.
Use the clear packet-cable gate subscriber command to clear a gate associated
with a specified subscriber (MTA or Client) IP address:
MOT:7A#clear packet-cable gate subscriber <A.B.C.D>
where:
A.B.C.D specifies the subscriber IP address.
Use the clear packet-cable gate dqos command to clear all DQoS gates.
Use the clear packet-cable gate mm command to clear all Multimedia gates.
Clearing PacketCable Statistics

PacketCable statistics can be displayed using the show packet-cable gate command,
which provides the information necessary to clear them.
Use the following commands in Privileged EXEC mode to clear PacketCable
statistics:
Use the clear packet-cable statistics em command to clear event message
statistics.
Use the clear packet-cable statistics gate command to clear gate statistics for all
COPS connections.

Use the clear counters ipsec command to clear the statistic counters displayed in
the output of the show ipsec commands.
Note: Refer to Configuring Electronic Surveillance on page 14-23, for more

information on clearing PacketCable statistics for electronic surveillance.
Clearing PacketCable Configuration

Use the following command options in PacketCable Configuration mode to clear
PacketCable configuration(s):
Use the clear configuration cops command to set all COPS configuration
parameters to default values.
Use the clear configuration dqos command to set all DQoS configuration
Use the clear configuration em command to set all event message configuration
Use the clear configuration mm command to set all PacketCable Multimedia
configuration parameters to default values.

15
Configuring DSG
Introduction
This chapter describes the tasks required to configure Out-Of-Band (OOB) messaging
between a Set-top Controller and customer premises equipment (CPEs) using the
DOCSIS Digital Set-top Gateway (DSG) protocol. Typical out-of-band cable services
include conditional access (CA), electronic program guide (EPG), emergency alert
services (EAS).
DSG allows the BSR CMTS to provide OOB cable services over a DOCSIS network.
DSG merges both set-top box and DOCSIS operations into a single, open network
without having to re-configure their existing network or cable modems. DSG uses the
concept of DSG tunnels which are logical interfaces that are used to encapsulate
various packet types and send them over a created link between two devices at remote
points on the network.
DSG provides a distinct advantage over traditional OOB cable services which use
proprietary protocols over a dedicated channel to provide network management of
customer CPEs (Set Top Boxes (STBs) or Set Top Devices (STDs) The traditional
OOB model hinders MSO flexibility through the use of proprietary application
servers and STDs which limit both upstream bandwidth and scalability for future
interactive services.

A DSG network consists of:

DSG Clients - the DSG client operates within the STD, is the termination point
of the DSG Tunnel, and receives OOB content from the DSG Server. There may
be more than one DSG Client within a Set-top Device.
DSG Server - the DSG server is the source of the OOB data and refers to any
server (such as an Application Server or other network attached device) that
provides data that is transported through the DSG tunnel data to the DSG client.
DSG Agent - the DSG agent is the implementation of the DSG protocol within
the CMTS. The DSG agent creates the DSG Tunnel, places data from the DSG
server into the DSG tunnel, and transmits the DSG tunnel to the DSG client.
The BSR 64000 implements the DSG Agent. The DSG agent performs two main
functions:
Provisioning of DSG tunnels to service specific DSG clients on the downstream
channels.
Forwarding the received OOB transmissions into the appropriate DSG tunnel and
delivering it to the DSG clients in the STDs.
DSG configuration consists of classifying the expected service (e.g. EAS -
Emergency Alert Services; EPG - Electronic Program Guide) traffic and configuring
the appropriate parameters to create a DSG tunnel for that service's DSG client. The
BSR CMTS signals groups of DSG tunnels on the downstream channel through a
DOCSIS MAC message or Downstream Channel Descriptor (DCD) at a repeated
interval. STDs parse the DCD to determine if their services (e.g. EAS, EPG, CA) have
a DSG tunnel present on the downstream and how they should receive its content.The
BSR CMTS forwards DSG traffic received from the DSG server into DSG tunnels on
the cable downstream interface(s). DSG has two modes of operation:
DSG Basic Mode operates without the DCD message in that clients do not listen
to DCD messages. Address assignment is static. The DSG Tunnel Address is
determined by the DSG Client and set by the DSG Agent through
configuration. This mode provides backwards compatibility with earlier
versions of the DSG specification.
DSG Advanced Mode operates with the DCD message in that clients listen to
DCD messages. Address assignment is dynamic. The DSG Tunnel Address is
determined by the DSG Agent and learned by the DSG Client in the DCD
message.

Release 5.3.1 Configuring DSG
Note: On the BSR, the configuration of Basic or Advanced mode is identical.
Prerequisites
The following prerequisite configurations must be completed before configuring any
DSG components:
IP multicast routing must be enabled.
The PIM routing protocol must be configured, as follows:
PIM must be enabled.
A PIM network must be designated.
Candidate BSRs must be configured.
Candidate RPs must be configured.
All HSIM interfaces for PIM operation and all the DSG enabled cable
downstream interfaces must be configured for PIM operation.
Note: PIM is a multicast routing protocol that runs over an existing Unicast
(legacy) infrastructure. The DSG specification requires support for legacy
DSG services and support for IP networks that may not support IP multicast.

DSG Configuration Tasks

Table provides a DSG configuration task summary:
Table DSG Configuration Task Summary
Task Refer to:

Entering DSG Configuration Mode Entering DSG Configuration Mode
Configuring a Channel List Configuring a Channel List
Configuring a Classifier Configuring a Classifier
Configuring a Timer Configuring a Timer
Configuring a Vendor Parameter Configuring a Vendor Parameter
Configuring a DSG Client Configuring a DSG Client
Configuring a DSG Tunnel Configuring a DSG Tunnel
Configuring a DSG Downstream Channel Configuring a DSG Downstream Channel
Displaying DSG Information Displaying DSG Information
Entering DSG Configuration Mode

DOCSIS Set-top Gateway Configuration Mode allows you to configure or modify
various DSG configurations including channel lists, classifiers, client lists, tunnel
group to channel maps, timers, vendor parameters, and DSG tunnels.
To enter DOCSIS Set-top Gateway Configuration Mode, use the cable dsg command,
from Global Configuration mode, as shown below:
MOT:7A(config)#cable dsg
The prompt changes as follows:
MOT:7A(config-dsg:)#

Initial DSG Configurations

This section provides procedural information on initial DSG configurations
procedures.
The following tasks are described:
Configuring a Channel List
Configuring a Classifier
Configuring a Timer
Configuring a Vendor Parameter
Configuring a Channel List

This section describes configuring a DSG channel list. A channel list is a list of one or
multiple downstream frequencies that are carrying configured DSG tunnels. The
appropriate DSG channel list will be included in the DCD messages on the associated
downstream channel. The DSG Client uses the channel list to determine which
downstream frequencies have DSG Tunnels present.
Note: Configuring a DSG channel list is optional. A DSG channel list provides
a faster means of searching for DSG Tunnels but is not a mandatory
configuration.
Use the channel-list command, in DOCSIS Set-top Gateway Configuration mode, to

create a new channel list or modify an existing channel list, as shown below:
MOT:7A(config-dsg:)#channel-list <1-4294967295> channel
<1-4294967295> ds-freq <91000000-857000000>
where:
1-4294967295 specifies a channel list index.
channel 1-4294967295 specifies a channel index.
ds-freq 91000000-857000000 specifies the downstream channel frequency in
Hz.
Use the no channel-list delete command to delete a channel list.

Configuring a Classifier
This section describes configuring a DSG classifier. A classifier specifies layer 3 and
layer 4 filtering which will be applied to DSG tunnel traffic. DSG Classifiers may be
specified in the DSG Agent and can be sent as a component of the DSG Address
Table in the DCD Message.
Use the classifier command, in DOCSIS Set-top Gateway Configuration mode, to
create a new classifier or modify an existing classifier, as shown below:
MOT:7A(config-dsg:)#classifier <1-65535> {destination <A.B.C.D> |
destination-port <0-65535> <0-65535> | include-in-dcd | priority <0-255> | source
<A.B.C.D> <A.B.C.D>}
where:
1-65535 is the classifier number.
destination A.B.C.D is the destination IP address to be matched for this classifier.
Note: Specifying a destination IP address is required for the operation of this

DSG classifier.
destination-port 0-65535 0-65535 is the low and high end destination port range
to be matched for this classifier.
include-in-dcd specifies the inclusion of this DSG classifier in DCD messages.
priority 0-255 is the priority of this classifier. The default value of 0 indicates the
lowest priority.
source A.B.C.D A.B.C.D is the IP address and network mask of the DSG server.
Use the no classifier command to delete a classifier.

Configuring a Timer
This section describes configuring a DSG timer. Four specific DSG timeout timers
can be sent to DSG clients through a DCD message. Each downstream channel is
mapped to only one set of timers.
Note: Configuring a DSG timer is optional.
Use the timer command, in DOCSIS Set-top Gateway Configuration mode, to create
a new timer or modify an existing timer, as shown below:
MOT:7A(config-dsg:)#timer <1-4294967295> {dsg1 <1-65535> | dsg2
<1-65535> | dsg3 <1-65535> | dsg4 <1-65535>}
where:
1-4294967295 is the timer group number.
dsg1 is the initialization timeout. This is the timeout period for DSG packets
during the initialization of the DSG client.
dsg2 is the operational timeout. This is the timeout period for DSG packets
during the normal operation of the DSG client.
dsg3 is the two-way retry timer. This is the retry timer that determines when the
DSG client attempts to reconnect with the DSG Agent and establish two-way
connectivity. A value of 0 indicates that the DSG client will continuously retry
two-way operation.
dsg4 is the one-way retry timer. The retry timer that determines when the DSG
client attempts to rescan for a DOCSIS downstream channel that contains DSG
packets after a dsg1 or dsg2 timeout. A value of 0 indicates that the DSG client
will immediately begin scanning upon a dsg1 or dsg2 timeout.
1-65535 is the timer value in seconds.
Use the timer delete command to delete a timer group.

Configuring a Vendor Parameter

This section describes configuring a DSG vendor parameter. A vendor parameter
allows a vendor to send vendor specific parameters.
Use the vendor-param command, in DOCSIS Set-top Gateway Configuration mode,
to create a new vendor parameter or modify an existing vendor parameter, as shown
below:
MOT:7A(config-dsg:)#vendor-param <1-4294967295> vendor
<1-4294967295> oui <line> value <octet string>
where:
1-4294967295 specifies a vendor parameter index.
vendor 1-4294967295 specifies a vendor index.
oui line specifies a vendor assigned Organization Unique Id (OUI) which is three
bytes of an octet string (e.g. aa056b).
value octet-string specifies a vendor value string of up to 50 characters.
Use the no vendor-param delete command to delete a vendor parameter.
Configuring a DSG Client

A DSG client terminates the DSG tunnel and receives transmission from the CMTS.
There may be more than one DSG Client within a Set-top Device. Configuring a DSG
client involves specifying the matching parameters for the DSG clients for which the
DSG rules applies.
A DSG client ID uniquely identifies each DSG client. The DSG client ID is unique
per DSG client but is not unique per Set-top Device as the same DSG client which
provides the same function may exist in multiple Set-top Devices.
In DSG Advanced Mode, the DSG client ID can be a 6 byte MAC address or may
additionally be a 2 byte Application ID, a 2 byte CA_system_ID, or a broadcast ID.
The Set-top Device has a fixed MAC address that must be matched by the DSG
tunnel.
Use the client-list command, in DOCSIS Set-top Gateway Configuration mode, to
create a new DSG client list or modify an existing DSG client list, as shown below:
MOT:7A(config-dsg:)#client-list <1-4294967295> client-id <1-4294967295>
{application-id <line> | broadcast [<1-4>] | ca-id <line> | mac-address <mac> |
vendor-param <1-4294967295>}

where:
1-4294967295 is the client list number.
client-id 1-4294967295 is the client identifier.
application-id line specifies an application ID in 2-byte hex string (e.g. 12ab).
This indicates a numeric ID for an application running on the Set-top Device.
broadcast 1-4 specifies the broadcast ID which identifies what types of data
streams are provided through the Broadcast Tunnel.
where:
1 = contains SCTE-65 [SCTE-65] delivery as defined in Annex D
2 = contains SCTE-18 [SCTE-18]delivery as defined in Annex D
3 = contains OCAP Object Carousel [OC-SP-OCAP1.0
4 = contains OpenCable Common Download Carousel
ca-id line specifies a CA ID in 2-byte hex string (e.g. 12ab). This indicates the
type of CA system applicable for the associated embedded Cable Modem
(ECM) streams.
mac-address mac specifies a DSG client MAC address in the form of
xxxx.xxxx.xxxx.This refers to the MAC address of the DSG Client within
the Set-top Device.
vendor-param 1-4294967295 is the index of the vendor parameter list specifying
the vendor specific DSG parameters.
Use the no client-list command to delete a DSG client.

Configuring a DSG Tunnel

A DSG Tunnel is a dedicated channel for transmitting DSG data from the CMTS to
the Set-top Devices. In DSG Basic Mode, a DSG tunnel is only identified by its DSG
tunnel address. In DSG Advanced Mode, a DSG tunnel can be identified by its DSG
Tunnel Address or a combination of the DSG tunnel address and other DSG Rule
parameters such as UCID range, Classifier IP addresses, and TCP port numbers.
Specifying Tunnel Parameters
Configuring a Tunnel Group
Specifying Tunnel Parameters

Use the tunnel command, in DOCSIS Set-top Gateway Configuration mode, to create
a new DSG tunnel or modify an existing DSG tunnel, as shown below:
MOT:7A(config-dsg:)#tunnel <1-4294967295> {classifier <1-65535> |
client-list <1-4294967295> | mac-address <mac> | service-class <WORD>}
where:
1-4294967295 specifies the DSG tunnel number.
classifier 1-65535 specifies a classifier number for this DSG tunnel.
client-list 1-4294967295 specifies a client list number for this DSG tunnel.
mac-address mac specifies a DSG tunnel MAC address in the form of
xxxx.xxxx.xxxx.
service-class WORD specifies a Service Class name.
Note: A DSG tunnel with a minimum specification of classifier, client-list,

and mac-address must be configured before the configuration of a DSG
tunnel group.
Use the no tunnel command to delete a DSG tunnel.

Configuring a Tunnel Group

Pre-configured DSG tunnels must be configured as a group of tunnels. This tunnel
group can then be associated to one or more downstream channels.
Use the tunnel tunnel-group command, in DOCSIS Set-top Gateway Configuration
mode, to create a tunnel group or modify an existing tunnel group, as shown below:
MOT:7A(config-dsg:)#tunnel <1-4294967295> tunnel-group
<1-4294967295>
where:
1-4294967295 specifies the DSG tunnel number.
1-4294967295 specifies the DSG tunnel group number.
Configuring a DSG Downstream Channel

Configuring a downstream channel for DSG operation involves the following
procedures:
Enabling/disabling DSG DCD messages on a downstream cable interface.
Mapping/un-mapping a group of DSG tunnels to a downstream cable interface.
Associating/disassociating a channel list with a downstream cable interface.
Associating/disassociating DSG timers with a downstream cable interface.
Associating/disassociating DSG vendor parameters with a downstream cable
interface.
This section describes the following:
DCD Messages
Associating Tunnel Groups to a Downstream Channel
Additional Configuration

DCD Messages
DSG Downstream Channel Descriptor (DCD) messages contain a group of DSG
Rules and DSG Classifiers. This collection of DSG Rules and DSG Classifiers in the
DCD message is known as the DSG Address Table.
A DSG Rule within the DSG Address Table assigns a DSG client ID to a DSG tunnel
address. A DSG classifier specifies layer 3 and layer 4 filtering which will be applied
to DSG tunnel traffic.
Note: DCD messages are enabled by default.
Use the cable downstream dsg enable command, in Cable Interface Configuration
mode, to disable or enable DCD messages on a downstream channel, as shown below:
MOT:7A(config-if)#cable downstream <NUM> dsg enable
MOT:7A(config-if)#no cable downstream <NUM> dsg enable
where:
NUM is the downsteam port number.
Associating Tunnel Groups to a Downstream Channel

Tunnel groups can be associated to one or more downstream channels by creating a
DSG group map. A DSG group map contains the downstream port number, DSG rule
priority, UCID range, tunnel group, and vendor parameter identifications. At least one
tunnel has to be configured before a tunnel group can be mapped to a downstream
channel through a group map.
Use the group-map tunnel-group command, in DOCSIS Set-top Gateway
Configuration mode, to associate a tunnel group to one or more downstream channels,
as shown below:
MOT:7A(config-dsg:)#group-map <1-4294967295> tunnel-group
<1-4294967295> {interface cable <X/Y> downstream <NUM> | priority <0-255> |
ucid <1-255> [<1-255>...] | vendor-param <1-4294967295>}
where:
1-4294967295 specifies a group map number.
tunnel-group 1-4294967295 specifies the tunnel group number.

interface cable X/Y downstream

where:
priority 0-255 specifies a DSG rule priority level. DSG rule priority determines
the order of which the channel and its associated UCIDs should be applied by the
DSG client.
ucid 1-255 is the upstream channel ID (UCID) for which the DSG rule applies.
vendor-param 1-4294967295 is the index of the vendor parameter list specifying
the vendor specific DSG parameters.
Use the no group-map command to delete a DSG group map.

Additional Configuration
Channel lists, timers, and vendor parameters can also be associated with a
downstream channel.
Use the cable downstream dsg channel-list command, in Cable Interface
Configuration mode, to associate a channel list to a downstream cable channel, as
shown below:
MOT:7A(config-if)#cable downstream <NUM> dsg channel-list
<1-4294967295>
where:
1-4294967295 is the channel list index.
Use the cable downstream dsg timer command, in Cable Interface
Configuration mode, to associate a timer group to a downstream cable channel, as
shown below:
MOT:7A(config-if)#cable downstream <NUM> dsg timer
<1-4294967295>
where:
1-4294967295 is the timer index.
Use the cable downstream dsg vendor-param command, in Cable Interface
Configuration mode, to associate a vendor parameter list to a downstream cable
channel, as shown below:
MOT:7A(config-if)#cable downstream <NUM> dsg vendor-param
<1-4294967295>
where:
NUM is the downstream port number (default=0).
1-4294967295 is the vendor parameter index.

Displaying DSG Information

The show cable dsg command displays all DSG configuration information provided
with the following show commands:
show cable dsg channel-list
show cable dsg classifier
show cable dsg client-list
show cable dsg downstream
show cable dsg group-map
show cable dsg timer
show cable dsg tunnel
show cable dsg tunnel-group
show cable dsg vendor-param
Additionally, the show cable dsg command displays tunnel group associations to one
or more downstream channels.
MOT:7A# show cable dsg
the show cable dsg command and tunnel group associations to one or more
downstream channels.
The show cable dsg channel-list command displays DSG channel list configuration
information.
MOT:7A# show cable dsg channel-list [<1-4294967295> {channel
<1-4294967295>}]
where:
1-4294967295 specifies a channel list index.
channel 1-4294967295 specifies a channel index.
the show cable dsg channel-list command.
The show cable dsg classifier command displays DSG classifier configuration
information.

MOT:7A# show cable dsg classifier [<1-65535>]

where:
1-65535 specifies a classifier number.
the show cable dsg classifier command.
The show cable dsg client-list command displays DSG client list information.
MOT:7A# show cable dsg client-list [<1-4294967295> {client-id
<1-4294967295>}]
where:
1-4294967295 specifies a client list number.
client-id 1-4294967295 specifies a client identifying number.
the show cable dsg client-list command.
The show cable dsg downstream command displays DSG downstream channel
configuration information.
MOT:7A# show cable dsg downstream
the show cable dsg downstream command.
MOT:7A# show cable dsg group-map [<1-4294967295>]

where:
1-4294967295 specifies a group map number.
the show cable dsg group-map command.
The show cable dsg timer command displays DSG timer configuration information.
MOT:7A# show cable dsg timer [<1-4294967295>]
where:
1-4294967295 specifies a timer index.

the show cable dsg timer command.
The show cable dsg tunnel command displays DSG tunnel configuration
information.
MOT:7A# show cable dsg tunnel [<1-4294967295>]
where:
1-4294967295 specifies a tunnel number.
the show cable dsg tunnel command.
The show cable dsg tunnel-group command displays DSG tunnel group information.
MOT:7A# show cable dsg tunnel-group [<1-4294967295>]
where:
1-4294967295 specifies a tunnel group number.
the show cable dsg tunnel-group command.
The show cable dsg vendor-param command displays DSG vendor parameter
configuration information.
MOT:7A# show cable dsg vendor-param [<1-4294967295>]
where:
1-4294967295 specifies a vendor parameter group number
the show cable dsg vendor-param command.

16
Configuring VLAN Tagging
Introduction
The BSR 64000 normally acts as an IP router, forwarding only IP packets at ISO
layer 3 between Customer Premises Equipment (CPEs) attached to DOCSIS cable
modems and a network port of the BSR 64000. The VLAN Tagging feature of the
BSR introduces the concept of bridging CPE Ethernet packets at ISO layer 2 onto a
particular Virtual Local Area Network (VLAN) appearing on a BSR Gigabit Ethernet
interface. The VLAN Tagging feature allows cable operators to offer "Transparent
LAN Service (TLS)" or "Layer 2 Virtual Private Network" to their business enterprise
customers while at the same time continuing to offer Internet access via IP routing to
their household subscribers.
The VLAN Tagging feature bridges packets in a point-to-point manner from one cable
modem to one IEEE 802.1Q VLAN. VLAN Tagging allows the BSR to forward
traffic received from CPEs to a uniquely numbered VLAN using 802.1Q
industry-standard trunking encapsulation. A layer 2 switch is required to bridge layer
2 traffic between the cable modem bridged VLANs. The BSR Gigabit Ethernet port
used to forward traffic is called a "trunk port". Trunk ports carry the traffic of multiple
VLANs over a single link and can extend a VLAN across an entire network. The BSR
64000 supports VLAN-tagged bridging and routing IP traffic on the same trunk port.
The routed IP traffic may configured to be tagged or untagged.

VLAN Tagging represents a major business opportunity for cable operators. Many
businesses with multiple branches in the cable operators region interconnect their
branches to their main office using technologies such as Frame Relay connections.
These Frame Relay connections typically provide Layer 2 bridged Ethernet
connectivity between the branch office and the main office. MSOs can offer VLAN
Tagging over cable modems as a cost-effective alternative to more expensive
connections such as Frame Relay.
Frame Relay connections typically cost in the hundreds of US dollars per month while
consumer broadband service typically costs a few tens of US dollars per month.
Accordingly, cable operators can provide the same layer 2 connectivity as Frame
Relay with a layer 2 TLS service offering to businesses that has significantly higher
revenue per month than consumer service but is still much cheaper to the
multi-branch enterprise customer themselves.
The diagram in Figure 1-1 depicts a typical TLS deployment:

Release 5.3.1 Configuring VLAN Tagging
Internet Router
Layer 2/3 Backbone

Internet
L2/L3 Switch L2/L3 Switch
BSR 1 BSR 2
CM
CM
CM
Home
CM Subscribers CM
Customer A Customer A
Branch Main Office
Figure Transparent LAN Service
The home subscribers of the cable operator continue to have all packets routed
through an Internet router to the Internet. A business enterprise customer A, however,
has all packets connected to a CM on BSR1 bridged through the operators backbone
to the customers main office via a CM connected to BSR 2. The customer's Main
Office may also be directly connected to the Layer 2/3 Backbone of the cable
operator. This is Transparent LAN Service provided to customer A.

With the VLAN tagging feature, each enterprise requires a "per-Enterprise" VLAN
implemented on the L2/L3 backbone. In addition, each cable modem configured for
bridging requires a unique "per-CM" VLAN on the connection between the L2/L3
switch and the BSR. The L2/L3 switch performs inter-VLAN bridging of the per-CM
VLANs together into the per-Enterprise VLAN. The Gigabit Ethernet connection
between the L2/L3 switch and the BSR is configured as an IEEE 802.1Q "trunk"
mode port, which tags all Ethernet packets with a particular VLAN number.
When the BSR forwards bridged packets to the L2/L3 switch, it always indicates a
particular VLAN for the bridged packet using 802.1Q tags. When the BSR forwards
an IP routed packet, however, it may or may not be tagged, depending on BSR
configuration.
VLAN Tagging Packet Formats

On the BSR Gigabit Ethernet interface, separate VLANs are identified with a tag as
defined by the IEEE 802.1Q standard.
The IEEE 802.1Q standard defines a format for adding 4 additional bytes to Ethernet
packets to identify the packet as belonging to a particular VLAN. The original
two-byte Ethernet Type field is replaced by the special type code 0x8100, followed
by a 16-bit VLAN ID tag. The VLAN ID Tag field contains 12 bits that define the
VLAN ID number for the packet. The three 802.1Q priority bits in the VLAN ID Tag
field are ignored on reception and set to the DOCSIS Service Flow Traffic Priority
Value on transmission out of a trunk port. The original Ethertype field then follows
the VLAN ID field. The operation of 802.1Q Tagging is depicted In Figure 1-2.
Original CPE Ethernet Packet
DA(6) SA(6) Original Data (1500

Type (2) bytes maximum)
IEEE 802.1Q VLAN Tagged Ethernet Packet
DA(6) SA(6) 0x8100 VLAN ID Original Data (1500

Tag (2) Type (2) bytes maximum)
Figure IEEE 802.1Q VLAN Tagging

This chapter describes the following:

Enabling VLAN Tagging
Configuring VLAN Tagged Bridging
Configuring VLAN Tagged Routing
Configuring the External L2/L3 Switch
Bridging Packet Sizes
Displaying VLAN Tagging Statistics
Clearing VLAN Tagging Statistics
Enabling VLAN Tagging

Follow these steps to designate a network interface as a bridge trunk port and enable
VLAN tagging:
1. Use the interface gigaether command, in Global Configuration mode, to enter
Interface Configuration Mode for the Gigabit Ethernet interface, for example:
MOT(config)#interface gigaether <X/Y>
where:
X/Y is the Gigabit Ethernet slot and port number.
2. Use the bridge mode trunk command to enable VLAN tagging for the network
port.
MOT(config-if)#bridge mode trunk
This configures the port to tag all layer 2 forwarded traffic and as a possible trunk
port. By default, all IP layer 3 routed traffic on the trunk is transmitted and
received untagged.
Note: VLAN Tagging is only supported on Gigabit Ethernet HSIM modules.

Enabling VLAN Tagging on Multiple Ports

The BSR 64000 also supports the configuration of VLAN Tagging on multiple
network ports with the bridge mode trunk command. If VLAN Tagging is enabled
on more than one port, the BSR selects exactly one port to forward VLAN Tagged
data. If the selected bridge trunk port fails, the BSR automatically switches VLAN
Tagged traffic to another enabled "bridge mode trunk" port.
In order to control the priority with which the BSR selects a bridge trunk port, an
optional priority argument may be configured.
Use the bridge mode trunk command, in Interface Configuration Mode for the
Gigabit Ethernet interface, to enable the optional priority argument, as follows:
MOT(config-if)#bridge mode trunk <0-255>
where:
0-255 is the priority value of the port.
The BSR will always select the highest numbered available port for VLAN Tagged
traffic forwarding. If a priority value is not specified for a "bridge mode trunk" port,
the default priority value is 128.
Configuring VLAN Tagged Bridging

With the introduction of the VLAN Tagging features, cable modems may now be
configured to operate with the BSR as "bridging" CMs, so that the BSR will bridge
their CPE traffic. Any modem not configured as a "bridging" CM will be considered
to be a normal "routing" CM, where the BSR routes the IP traffic from its CPE.
There are two methods of designating a bridging CM:
Through a CM configuration file TLV parameter.
Through the BSR Command Line Interface.
With the VLAN Tagging feature, only one bridging CM can be configured for each
VLAN. All downstream packets received on the "trunk mode" Gigabit Ethernet port
of the BSR are examined for VLAN tags. If a VLAN tag is present, the packet may be
bridged or routed depending on the tag value. If a VLAN tag is not present, the packet
will always be routed.

The BSR 64000 supports bridging of traffic received from CPEs behind a
PacketCable Embedded Multimedia Terminal Adapter (E-MTA) which is registered
as a bridging modem. Network traffic originating from the E-MTA will be routed
while traffic from the CPE will be bridged from the same E-MTA device. The BSR
identifies the traffic originating from an E-MTA device based on the source MAC
address of Ethernet frames received from it. The MAC address is extracted from the
E-MTAs DHCP packets. To distinguish DHCP packets recevied from an E-MTA
device, Option 60 must be enabled with the Vendor Class ID set to "pktc1.0".
Note: Baseline Privacy Interface (BPI) should be configured for all CMs
enabled for bridging. Otherwise, downstream bridged multicasts and
broadcasts will be received by all subscriber CMs, not just the bridging CM.
See Configuring Cable Privacy Mandatory for more information.
Specifying a Bridging Cable Modem through a Bridge Mode

TLV
Motorola supports a Bridge Mode TLV, in a cable modems configuration file, that
associates the cable modems traffic to a specified VLAN by specifying the cable
modem as the Bridging CM. The format of the Bridge Mode TLV is as follows:
Motorola vendor-specific TLV

Type = 43
Length = 15
Subtype=8
Length=3
Value=0x08003E
Subtype = 3
Length = 9
Value = vlan:<VLAN identifying number>
ASCI string with "vlan:"

followed by the decimal (2-4094)
number of the VLAN to which
the CM is bridged.

The Bridge Mode TLV is received by the BSR when the cable modem makes a
registration request.
Note: Any VLAN association specified in the Bridge Mode TLV can be
overridden with the bridge cable modem command. See Specifying a
Bridging Cable Modem through the CLI.
The Motorola Bridge Mode TLV is supported by all DOCSIS standard cable
modems. A bridging cable modem need not be manufactured by Motorola.
An MSO must change the total length and subtype 3 length values specified
in the TLV file based on the number of characters in the files VLAN Value
field. The VLAN Value field can be from 6-9 characters.
Using the TLV to define the VLAN ID will require that every cable modem
have a unique TLV file. The BSR disallows registration of a modem bridging
to a VLAN when another modem on the same CMTS is already registered as
bridging to that VLAN. The BSR disallows registration of a cable modem
bridging to a VLAN when that VLAN is already configured on the a tagged
routing interface. Although the BSR does not disallow registration of CMs on
different CMTSs with the same bridging VLAN, operation is unspecified. This
is considered a misconfiguration and is indicated in the output of the show
bridge vlan command.
VLAN ID 1 is reserved for use by the attached Layer 2 switch/router for

management purposes and as the default "native" VLAN for that equipment.
VLAN ID 1 may not be configured on the BSR for cable modem Layer 2
bridging.
The same VLAN ID value cannot be configured for both a bridging CM and a
tagged router interface
Specifying a Bridging Cable Modem through the CLI

The Command Line Interface (CLI) can be used to associate a cable modems traffic
to a specified VLAN by specifying the cable modem as the Bridging CM. Follow
these steps to specify a cable modem as the Bridging CM:
1. Use the bridge cable modem command to associate a particular cable modems
traffic to a specified VLAN, as follows:

MOT(config)#bridge cable modem <mac> <2-4094>
where:
mac is the cable modems MAC Address in the form xxxx.xxxx.xxxx.
2-4094 is the VLAN ID number.
2. Use the no bridge cable modem command to remove a particular cable modem
from a specified VLAN, as follows:
MOT(config)#no bridge cable modem <mac> <2-4094>
Note: The BSR ignores a VLAN TLV received in the registration request from
a cable modem, if VLAN mapping is already established for that cable
modem with the bridge cable modem command.
VLAN Tagging requires that each bridging cable modem be assigned to a

different VLAN number. An external L2 switch is required to bridge layer 2
traffic between the cable modem bridged VLANs.
VLAN ID 1 is reserved for use by the attached Layer 2 switch/router for

bridging.
The same VLAN ID value cannot be configured for both a bridging CM and a
tagged router interface
Configuring VLAN Stacking on a Bridging Cable Modem

VLAN stacking enables the transport of traffic from multiple VLANs by
encapsulating one VLANs traffic within another VLAN. VLAN stacking allows the
BSR to receive and forward stacked VLAN traffic. VLAN stacking is enabled or
disabled on a per cable modem basis to control whether CPE traffic may be tagged
with an inner or stacked VLAN tag by a particular bridging CM. The "outer" or MSO
Vlan tag is added by the BSR. CPE and MSO VLAN tags can co-exist in a single
packet. The BSR does not look at the CPE VLAN tag for any information. Without
VLAN stacking enabled, the BSR does not forward stacked VLAN traffic.

Enabling VLAN Stacking through an Enhanced Bridge Mode

TLV
Motorola provides a proprietary enhanced Bridge Mode TLV, in a cable modems
configuration file, that enables VLAN stacking for the corresponding cable modem.
The format of the enhanced Bridge Mode TLV is as follows:
Motorola vendor-specific TLV

Type = 43
Length = 26
Subtype=8
Length=3
Value=0x08003E
Subtype = 3
Length = 19
Value = vlan:<VLAN identifying number> stackable"
Indicates that
VLAN stacking is enabled.
Note: An MSO must change the total length and subtype 3 length values
specified in the TLV file based on the number of characters in the files VLAN
Value field. The VLAN Value field can be from 16-19 characters.
Enabling VLAN Stacking through the CLI

The Command Line Interface (CLI) can be used to enable or disable VLAN stacking.
1. Use the bridge cable modem command, in Global Configuration Mode, to
enable VLAN stacking for a particular cable modem, as follows:
MOT(config)#bridge cable modem <mac> <2-4094> stackable
where:
mac is the cable modems MAC Address in the form xxxx.xxxx.xxxx.

2-4094 is the VLAN ID number.

stackable enables VLAN stacking.
2. Use the no bridge cable modem command to disable VLAN stacking for a
particular cable modem, as follows:
MOT(config)#no bridge cable modem <mac> <2-4094> stackable
Note: VLAN ID 1 is reserved for use by the attached Layer 2 switch/router for
bridging.
Configuring VLAN Tagged Routing

When VLAN Tagging is enabled on a network interface with the bridge mode trunk
command, the port still performs layer 3 routing of untagged packets. Some layer 2
switches do not support the concept of a "native" or untagged VLAN for such layer 3
IP packet forwarding to the BSR. For this reason, the BSR allows one of the 802.1Q
VLANs to be configured as the (single) VLAN on which the BSR performs layer 3
routing on a "bridge mode trunk" port. This feature is called "Tagged Routing".
Note: The same VLAN ID value cannot be configured for both a bridging CM
and a tagged router interface
To configure tagged routing on the BSR, do the following:

1. Use the interface gigaether command to navigate to the BSRs Gigabit Ethernet
interface, as follows:
MOT(config)# interface gigaether <X/Y>
where:
X/Y is the Gigabit Ethernet slot and port number.
2. If not already configured, use the ip address command to define a router
interface on the port:

MOT(config-if)# ip address <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP host address of the interface.
A.B.C.D is the network mask.
3. Use the encapsulation dot1q command to configure a routed VLAN on the
BSRs Gigabit Ethernet interface, as follows:
MOT(config-if)#encapsulation dot1q <1-4094>
where:
1-4094 specifies the VLAN ID for routed traffic.

Configuring the External L2/L3 Switch

The VLAN Tagging feature of the BSR performs point-to-point forwarding from one
CM to one IEEE 802.1Q VLAN. When CPE traffic from multiple cable modems
belonging to the same enterprise customer must be bridged together, an L2 switch
external to the BSR must perform "inter-VLAN" bridging of the different "per-CM"
VLANs into a single "per-Customer" VLAN.
One way to perform inter-VLAN bridging is to configure a sub-interface in the
external L2 switch for each per-CM VLAN, and then bridge each of the sub-interfaces
to the same bridge group. An example of this is depicted below.
In this example, the external Cisco router is configured to connect to the BSR with the
following configuration:
interface Ethernet 0/0.1
encapsulation dot1q 17
bridge group 100
interface Ethernet 0/0.2
encapsulation dot1q 18
bridge group 100

The cable privacy mandatory feature allows a cable operator to enable the encryption
of all routed broadcasts and routed unmapped multicast traffic. Cable privacy
mandatory encrypts otherwise unencrypted downstream routed non-unicasts and only
gives the key to decrypt these messages to routing cable modems. Bridging cable
modems will discard all downstream routed broadcasts or routed multicasts.
Note: The cable privacy mandatory feature requires that all cable modems
have BPI enabled in order to register. If a cable modem does not have BPI
enabled and cable privacy mandatory is turned on, the cable modem will not
be able to register.
With cable privacy mandatory enabled, routed broadcasts are not received by
VLAN Tagging CM's. Therefore, VLAN tagging cable modems will not be able
to respond to broadcast pings.

Use the cable privacy mandatory command, in Global Configuration or Cable

Interface Configuration Mode, to allow the encryption of all routed broadcasts and
routed unmapped multicast traffic, as follows:
MOT(config)#cable privacy mandatory
Warning: After enabling the cable privacy mandatory feature, the cable
operator must issue the clear cable modem all reset command to
re-register all cable modems and allow non-unicast traffic (including ARPs) to
function correctly.
Bridging Packet Sizes

The VLAN Tagging feature will accept upstream Ethernet packets from CPEs up to a
maximum size of 1522 bytes from start of the Destination Address to the end of FCS.
A maximum size Ethernet packet with a single "inner" 802.1Q tag added by the
customer CPE is supported. When such packets are bridged onto the trunk mode
network port, the BSR adds an "outer" 802.1Q tag with the configured VLAN for the
CM, increasing the maximum packet size to 1526 bytes. VLAN stacking must be
enabled for this feature to work.
Likewise, in the downstream direction, the BSR accepts a maximum packet size of
1526 bytes, and will forward a maximum size packet of 1522 bytes to the bridging
CM.
Note: Some CMs may not forward 1522 byte packets with a customer
provided "inner" 802.1Q tag, and instead only forward a maximum size
packet of 1518 bytes. VLAN stacking of maximum size Ethernet packets is
not supported on such cable modems.

Displaying VLAN Tagging Statistics

Use the show bridge vlan command to display the bridging cable modem MAC
addresses for all VLANS or a specific VLAN, as follows:
MOT#show bridge vlan [<2-4094>]
where:
2-4094 is the VLAN ID of the bridging CM. If omitted, all VLANs are displayed.
The following is typical screen output from the show bridge vlan command:
Selected Network Bridge Port: gigaether 15/2

Vlan CM Stackable
---- -------------- ---------
400 0008.0e10.39be disabled
900 000b.0643.33fc disabled
910 0020.409a.24c8 disabled
The show bridge vlan counters command displays statistical counters for all VLANs
or a specific VLAN.
MOT#show bridge vlan [counters [<2-4094>]]

where:
2-4094 is the VLAN ID of the bridging CM to display statistics.
The following is typical screen output from the show bridge vlan counters
command:
VLAN Upstream Upstream Downstream Downstream

ID Packets Discards Packets Discards
---- -------- ------------- ---------- ----------
2 1234 45 1890 56
3 714 23 922 34
4 50 0 45 0

Clearing VLAN Tagging Statistics

Use the clear bridge vlan counters command, in Privileged EXEC mode, to clear all
upstream and downstream statistics for all VLANs associated with a VLAN cable
modem. These are the same statistics displayed with the show bridge vlan counters
command.
MOT#clear bridge vlan counters [<2-4094>]
where:
2-4094 is the VLAN ID of the bridging CM to display statistics. If omitted, all
VLANs counters are cleared.

17
Configuring
Tagged Sub-Interfaces
Introduction
This chapter provides information on configuring Tagged Sub-Interfaces (TSIs). The
following topics are discussed:
TSI Feature Description
Adding and Removing a Sub-Interface
Associating an IEEE 802.1q VLAN ID with a Sub-Interface
Configuring the Physical Interface to Include Optional 802.1p and 802.1q Tags
Updated Commands

TSI Feature Description

TSIs (Tagged Sub-Interfaces) can be used to logically divide traffic among various
classes of traffic. For example, if an L2 switch is connected to an HSIM, a single
physical interface can be subdivided to segment different ISPs traffic into different
VLANs. The 802.1q (and optionally 802.1p) tagged packets coming from the HSIM
can be used by upstream router/switches to provide different forwarding treatment
and optional Layer 2 QoS.
TSIs can also be used to make an HSIM physical interface part of multiple VPNs. By
accepting VLAN tagged packets for some interfaces, and untagged packets for other
interfaces (based on user configuration), TSIs can be combined with VLAN tagging
to allow a single physical link to transport logically separated routing and bridging
traffic.
The BSR performs 802.1p marking of egress (outgoing) packets using route-maps and
QoS queues for upstream traffic from a cable modem going out a TSI. This is
achieved by configuring a route-map with the QoS queue to be used and the next hop
of the outbound interface, in this case, the TSI. The physical interface (the top-level
interface) corresponding to the TSI configures mapping of the QoS queue, described
in the route-map, to the 802.1p priority bits. Packets from the CMTS are sent to the
TSI via the configured route-map. The VLAN tag and the 802.1p priority bits are
applied to each packet as it is transmitted upstream out of the GIG-E port.
Adding and Removing a Sub-Interface

Up to 31 sub-interfaces are supported, in the range 1-31. To add a sub-interface, do
the following:
1. Use the interface gigaether X/Y.N command from Global Configuration mode.
2. Specify the sub-interface number, using numbers in the range 1 - 31 for the value
of N.
Example: MOT:7A#(config) interface gigaether 15/0.1
To remove a sub-interface, do the following:

1. Use the no interface gigaether X/Y.N command from Global Configuration
mode.
Example: MOT:7A#(config) no interface gigaether 15/0.1

Release 5.3.1 Configuring Tagged Sub-Interfaces
Associating an IEEE 802.1q VLAN ID with a

Sub-Interface
Each sub-interface is associated with a unique 802.1q tag, which must be configured
in the sub-interface shell. Perform the following steps to associate an 802.1q VLAN
ID with a sub-interface:
1. Use the interface gigaether <X/Y.N> command in Global Configuration mode to
specify the slot, port and sub-interface. The sub-interface must be in the range
1-31.
Example: MOT:7A#(config) interface gigaether 15/0.1
2. Use the ip address <A.B.C.D> <A.B.C.D> command to specify the IP address
and the subnet mask.
Example: MOT:7A#(config-if) ip address 1.1.1.1
255.255.255.0
3. Use the encapsulation dot1q <vlan-id> command to specify the VLAN ID. The
VLAN ID must be in the range 1-4094.
Example: MOT:7A#(config-if) encapsulation dot1q 100
4. Enable the interface with the no shutdown command.
Example: MOT:7A(config-if)# no shutdown
Note: The IEEE 802.1q VLAN ID cannot be used for TSIs if it is already in
use for the VLAN Tagging feature (bridging) through "bridge cable modem" or
cable modem TLV.

Configuring the Physical Interface to Include

Optional 802.1p and 802.1q Tags
A physical interface (the top-level interface, for example 15/0) may be configured as
either a "Tagged Router Interface", an "Untagged Router Interface", or neither (i.e., a
tagged sub-interface only).
To configure the physical interface, perform the following steps:
1. Use the interface gigaether <X/Y> command from Global Configuration mode.
Example: MOT:7A(config)#interface gigaether <X/Y>
where:
X is the module slot number with an available Gigabit Ethernet interface.
Y is 0.
2. Optionally, to configure either a Tagged Router Interface or an Untagged Router
Interface, you may use the ip address <A.B.C.D> <A.B.C.D> command to
specify the IP address and the subnet mask.
Example: MOT:7A#(config-if) ip address 2.2.2.2
255.255.255.0
3. Optionally, to configure a Tagged Router Interface, you may use the
encapsulation dot1q <vlan-id> command to specify the VLAN ID. The VLAN
ID must be in the range 1-4094.
Example: MOT:7A#(config-if) encapsulation dot1q 100
4. Optionally, to configure 802.1p priority bits in Tagged Router Interface and/or
Tagged Sub-Interface outgoing packets, you may use the qos queue <0-7> dot1p
<1-7> command.
Example: MOT:7A#(config-if) qos queue 0 dot1p 0
5. Enable the interface and the configuration change with the no shutdown
command.

Example: MOT:7A(config-if)# no shutdown
Note: If TRIs and TSIs are configured for the same physical interface,
untagged traffic will be dropped.
Updated Commands
As a result of the new TSI functionality implemented in Release 4.2.3, the syntax of
many CLI commands has been modified and enhanced. The following sections
provide a list of the commands that have been affected, a description of the
enhancements to the CLI commands, as well as command examples and sample
command output.
The following sections provide more detailed information.
TSI-Related Syntax Enhancement to CLI Commands
List of CLI-Configurable Commands for TSI
TSI-Related Syntax Enhancement to CLI Commands

Up to 31 TSIs are supported, for many CLI commands, on Gigabit interfaces. A
syntax enhancement, necessary to specify the TSIs has been implemented on these
CLI commands. Note that in addition to specifying the slot and port number in the
standard X/Y format, the sub-interface number (represented as N ) must also be
specified immediately after the port number, using a period as a delimiter.
For example,
interface gigaether X/Y.N
where:
X is the slot number of the Gigabit Interface module.
Y is the port number.
N is the sub-interface number, in the range 1-31.
Refer to the BSR Command Reference Guide for release 4.2.3 for full command
descriptions of the interface and show interfaces commands. All CLI commands that
support TSIs have been enhanced similarly. A list of all of the TSI-affected CLI
commands is provided in the next section, List of CLI-Configurable Commands for
TSI.

List of CLI-Configurable Commands for TSI

The following is a list of the CLI-configurable commands for TSI:
arp timeout
cable intercept
description
encapsulation dot1q
ike client-addr
interface gigaether
ip access-group
ip address
ip broadcast-address
ip igmp access-group
ip igmp query-interval
ip igmp query-max-response-time
ip igmp querier-timeout
ip igmp static-group
ip igmp version
ip igmp version1-querier
ip mask-reply
ip ospf authentication key
ip ospf cost
ip ospf database-filter all out
ip ospf dead-interval
ip ospf hello-interval
ip ospf message-digest-key md5
ip ospf priority
ip ospf retransmit-interval
ip ospf transmit-delay
ip network
ip pim border
ip pim bsr-candidate

ip pim bsr-candidate ip-address

ip pim dr-priority
ip pim message-interval
ip pim query-interval
ip pim rp-candidate
ip pim rp-candidate group-list
ip pim rp-candidate interval
ip pim rp-candidate ip address
ip pim rp-candidate priority
ip policy route-map
ip rarp-server
ip redirects
ip rip authentication key
ip rip receive version
ip rip send version
ip rip host-routes
ip split-horizon
ip unreachables
offset-list offset gigaether
message-digest-key md5
passive-interface gigaether
qos queue dot1p
radius-server host
show interfaces gigaether
show ip arp gigaether
show ip igmp interface
show ip interface gigaether
show ip interface brief gigaether
show ip ospf interface gigaether
show ip pim interface gigaether
show ip pim neighbor gigaether

show l2-cam ip
show running-config
show stats 7 xfabric
trap-enable-if
trap-enable-rdn

18
Subscriber Management
Introduction
This chapter provides support, configuration, and command information for the
subscriber management feature:
The BSR supports the CableLabs DOCSIS Subscriber Management MIB (ECN
OSSIv2-05.0215), which extends CMTS filtering capabilities to include embedded
Multimedia Terminal Adapters (eMTAs), embedded Set-top Boxes (eSTBs), and
CableHome portal servers in order to support the DOCSIS Set-top Gateway (DSG)
feature.
In Release 4.2, filter groups were configured on the BSR through the MIB to manage
subscribers. Release 4.2.3 extends this capability so that filter groups can be
configured through the BSR Command Line Interface (CLI).
Creating Filters to Manage Subscribers

Packet Filters and TCP/UDP Filters are used to further identify the multiple Customer
Premises Equipment (CPE) and differentiate the services associated with the cable
modem (CM) to manage subscribers effectively. For example, a cable operator applies
one set of filters so that the CMTS can correctly identify the type of CPE device
behind a CM.

Creating a Packet Filter Group

Packet filters are applied on the BSR to ensure that packets from CMs and their
respective CPEs go to and from their specified locations. A variety of packet filters
can be applied to a packet filter group. Select from the following packet filter options
in this section:
Configuring the Source IP Address and Mask
Configuring the Destination IP Address and Mask
Configuring the Upper Level Protocol
Configure the TOS Value and Mask
Configure the Filter Match Action
Enabling a Packet Filter
Displaying the Packet Filter Configuration
Deleting a Packet Filter
Configuring the Source IP Address and Mask

Use the cable filter group index src-ip command in Global Configuration mode to
configure the source IP address and bit mask, which must match the classified
packets source IP address and bit mask.
MOT:7A(config)#cable filter group <1-32> index <1-64> src-ip <A.B.C.D>
<A.B.C.D>
where:
1-32 is the subscriber management filter group number.
1-64 is the submanagement packet filter number (index).
A.B.C.D is the source IP address.
A.B.C.D is the source IP bit mask.

Release 5.3.1 Subscriber Management
Configuring the Destination IP Address and Mask

Use the cable filter group index dst-ip command in Global Configuration mode to
configure the destination IP address and bit mask, which must match the classified
packets destination IP address and bit mask.
MOT:7A(config)#cable filter group <1-32> index <1-64> dst-ip <A.B.C.D>
<A.B.C.D>
where:
A.B.C.D is the destination IP address.
A.B.C.D is the destination IP bit mask.
Configuring the Upper Level Protocol

Each Layer 4 upper level protocol (ULP) has an assigned IP protocol number. ULP IP
protocol numbers are assigned by the Internet Assigned Numbers Authority. Click on
the following URL for more information:
http://www.iana.org/assignments/protocol-numbers
Use the cable filter group index ulp command in Global Configuration mode to
configure the ULP, which is to be matched in the classified packet.
MOT:7A(config)#cable filter group <1-32> index <1-64> ulp <0-256>
<A.B.C.D>
where:
0-256 is the ULP number.
Note: If the ULP number is 256, it matches all ULP values.

Configure the TOS Value and Mask

Use the cable filter group index tos command in Global Configuration mode to
configure the Type of Service (TOS) value and mask, which is to be matched in the
classified packet.
MOT:7A(config)#cable filter group <1-32> index <1-64> tos <0x0-0xff>
<0x0-0xff>
where:
0x0-0xff is the hexidecimal TOS number.
0x0-0xff is the hexidecimal TOS mask.
Configure the Filter Match Action

Use the cable filter group index action command in Global Configuration mode to
configure the action to take when the filter matches.
MOT:7A(config)#cable filter group <1-32> index <1-64> action {accept | drop}
where:
accept accepts the packet for further processing.
drop discards the packet.
Enabling a Packet Filter

Use the cable filter group index enable command in Global Configuration mode to
enable the configured packet filter.
MOT:7A(config)#cable filter group <1-32> index <1-64> enable
where:

Displaying the Packet Filter Configuration

Use the show cable filter command to display the packet filter configuration.
MOT:7A(config)#show cable filter [group <1-32> [index <1-64>]]
where:
group <1-32> displays the subscriber management filter group number.
index <1-64> displays the submanagement packet filter number (index).
Deleting a Packet Filter

Use the no cable filter group index command in Global Configuration mode to
delete a packet filter.
MOT:7A(config)#no cable filter group <1-32> index <1-64>
where:

Configuring Filters for TCP or UDP Packet Headers

TCP or UDP packet filters can be applied to a packet filter group. Select from the
following packet filter options in this section:
Configuring the TCP/UDP Source Port
Configuring the TCP/UDP Destination Port
Configuring the TCP Flag Value and Mask
Enabling the TCP/UDP Packet Filter
Displaying the TCP/UDP Packet Filter Configuration
Deleting a TCP/UDP Packet Filter
Configuring the TCP/UDP Source Port

Use the cable tcpudp-filter group index src-port command in Global Configuration
mode to configure the TCP/UDP source port that should be matched in the classified
packet.
MOT:7A(config)#cable tcpudp-filter group <1-32> index <1-64> src-port
<0-65536>
where:
1-32 selects the TCP/UDP packet filter group number.
1-64 selects a packet filter.
0-65536 is the source port to match in the classified packet.
Note: The default source port 65536 matches any value in the TCP or UDP
source field.
Configuring the TCP/UDP Destination Port

Use the cable tcpudp-filter group index dst-port command in Global Configuration
mode to configure the TCP/UDP destination port that should be matched in the
classified packet.
MOT:7A(config)#cable tcpudp-filter group <1-32> index <1-64> dst-port
<0-65536>
where:


0-65536 is the destination port to match in the classified packet.
Note: The default destination port 65536 matches any value in the TCP or
UDP destination field.
Configuring the TCP Flag Value and Mask

Use the cable tcpudp-filter group index tcp-flag command in Global Configuration
mode to configure the desired TCP packet header flag value and mask to match in the
classified packet.
MOT:7A(config)#cable tcpudp-filter group <1-32> index <1-64> tcp-flag
<0x0-0x3f> <0x0-0x3f>
where:
0x0-0x3f specifies the TCP flag value
0x0-0x3f specifies the TCP flag mask.
Note: The TCP flag value must always be a subset (proper or otherwise) of
the mask field.
Enabling the TCP/UDP Packet Filter

Use the cable tcpudp-filter group index enable command in Global Configuration
mode to enable the configured TCP/UDP packet filter.
MOT:7A(config)#cable tcpudp-filter group <1-32> index <1-64> enable
where:
1-32 is the TCP/UDP packet filter group number.
1-64 is the packet filter.

Displaying the TCP/UDP Packet Filter Configuration

Use the show cable tcpudp-filter command to display the TCP/UDP packet filter
configuration.
MOT:7A(config)#show cable tcpudp-filter [group <1-32> [index <1-64>]]
where:
group <1-32> displays a specified TCP/UDP packet filter group.
index <1-64> displays the packet filter.
Deleting a TCP/UDP Packet Filter

Use the no cable tcpudp-filter group index command in Global Configuration
mode to delete a TCP/UDP packet filter.
MOT:7A(config)#no cable tcpudp-filter group <1-32> index <1-64>
where:
Configuring Default Packet Filter Group for CMs and CPEs

A default filter group is used when the cable modems (CM) Configuration File is sent
upstream from the CM to CMTS and does not specify a particular packet filter group
to use.
Select from the following default packet filter group configurations for CMs and
CPEs:
Configuring Default Filter Group for a CPE
Configuring Default Filter Group for a CM
Configuring the Default Maximum CPEs
Configuring the Active Default for CPEs
Configuring the Learnable Default for CPEs
Displaying the Default Filter Groups and CPE Control Defaults

Configuring Default Filter Group for a CPE

Use the cable submgmt default filter-group command in Global Configuration
mode to configure the default filter group for traffic applied to or from CPEs
connected to a CM.
MOT:7A(config)#cable submgmt default filter-group {downstream |
upstream} <1-32>
where:
downstream configure the default filter group for a CPE, for traffic going to the
CPE through its connected CM on the downstream from the CMTS.
upstream configure the default filter group for a CPE, for traffic going from the
CPE through its connected CM on the upstream to the CMTS.
1-32 selects the default packet filter group number.
Configuring Default Filter Group for a CM

Use the cable submgmt default filter-group cm command in Global Configuration
mode to configure the default filter group for traffic applied to or from the CM itself.
MOT:7A(config)#cable submgmt default filter-group cm {downstream |
upstream} <1-32>
where:
downstream configure the default filter group for a CM, for traffic going to the
CM on the downstream from the CMTS.
upstream configure the default filter group for a CPE, for traffic going from the
CM on the upstream to the CMTS.
Configuring the Default Maximum CPEs

Use the cable submgmt default cpe-control max-cpe command in Global
Configuration mode to configure a packet filter for controlling the number of CPEs, if
it is not signaled in the DOCSIS registration request.
MOT:7A(config)#cable submgmt default cpe-control max-cpe <0-1024>
where:

Configuring the Active Default for CPEs

Use the cable submgmt default cpe-control active command in Global
Configuration mode to configure the CPE active default if it is not signaled in the
DOCSIS Registration request.
MOT:7A(config)#cable submgmt default cpe-control active {true | false}
where:
true indicates that the CPE is active.
false indicates that the CPE is not active.
Configuring the Learnable Default for CPEs

Sometimes the CMTS does not learn a CPE IP address from the DOCSIS
provisioning entries in a CMs configuration file that is signaled in a DOCSIS
registration request.
Use the cable submgmt default cpe-control learnable command in Global
Configuration mode to configure the default for controlling whether or not a CPE IP
address can be learned.
MOT:7A(config)#cable submgmt default cpe-control learnable {true | false}
where:
true indicates that the CPE IP address can be learned.
false indicates that the CPE IP address cannot be learned.
Displaying the Default Filter Groups and CPE Control Defaults

Use the show cable submgmt cpe-control default command in all modes except
User EXEC mode to display default filter groups and CPE control defaults.
MOT:7A(config)#show cable submgmt cpe-control default

19
Configuring a Distributed
MAC Domain
Introduction
A Distributed MAC Domain logically binds together upstream channels and
downstream channels from different modules installed in a BSR chassis. A
Distributed MAC Domain is defined on a module containing one or more upstream
channels that binds downstream channels from the same or a different module.
Release 5.2.1 supports up to 10 downstream channels per 2:8 CMTS module in a
distributed MAC Domain. A distributed MAC Domain consists of downstream
channels from a local 2:8 (DOCSIS or EuroDOCSIS) module and remote downstream
channels on a TX32 module. Support for 10 downstream channels per 2:8 CMTS
module allows up to 80 downstream and 64 upstream channels for each BSR 64000
chassis. Distributed MAC Domains are defined with decoupled CLI configuration
syntax. The Distributed MAC Domain command syntax will now support binding the
downstream channels of a CMTS 2:8 module and a TX32 module into a single logical
MAC Domain.
This chapter provides an example of configuring a Distributed MAC Domain between
a CMTS 2:8 module and a TX32 module. Refer to Appendix A for additional
configuration information based on the example depicted in Figure 19-1 on page
19-2.

In the example topology, the CMTS 2:8 downstream channels are connected through
one port to four fiber nodes, and is called 1:4 splitting. The TX32s RF ports are
also connected through one port to four fiber nodes. In the upstream, two ports are
connected to one fiber node, denoted as 2:1 splitting. This sample configuration and
topology allows one TX32 to support 32 fiber nodes.
D0
CMTS D1
2x8
U0
U1
Fiber Node A
U2
U3
Fiber Node B
U4
U5
Fiber Node C
U6
U7
Fiber Node D
1/8th D0/C0 D0/C1

D0/C2 D0/C3
TX32
HSIM4
2x1
HSIM4
Figure 19-1 Distributed MAC Domain Configuration Example

Release 5.3.1 Configuring a Distributed MAC Domain
The BSR chassis configuration used in the Distributed MAC Domain configuration
example depicted in Figure 19-1 is shown in the following table:
Slot Module
0 CMTS 2:8
1 CMTS 2:8
2 CMTS 2:8
3 CMTS 2:8
4 CMTS 2:8
5 CMTS 2:8
6 Spare 2:8
7 SRM3/4
8 SRM3/4
9 CMTS 2:8
10 CMTS 2:8
11 <empty>
12 <empty>
13 Primary TX32
14 GigE/Ether-Flex
15 GigE/Ether-Flex
This chapter discusses the following required procedures needed to configure the
Distributed MAC Domain example:
MAC Domain Layer 3 Configuration
Fiber Node Configuration
MAC Domain Configuration
TX32 Downstream Port Configuration

Downstream Configuration Commands

This section lists the BSR 64000 downstream configuration commands. These
commands allow a user to configure the downstream RF port or channel on the TX32
module and configure the downstream channel on the 2:8 CMTS module. The
following table lists which commands are available for each configuration scenario.
TX32 Downstream TX32 Downstream 2:8 CMTS Downstream

RF Port Channel Channel
cable downstream channel-mode cable downstream carrier-only cable downstream carrier-only
cable downstream description cable downstream channel-id cable downstream channel-id
cable downstream fiber-node cable downstream description cable downstream description
cable downstream cable downstream frequency cable downstream fiber-node

interleave-depth
cable downstream cable downstream frequency

cable downstream modulation loadbalance-group
cable downstream cable downstream
cable downstream power-level primary-capable interleave-depth
cable downstream
cable downstream scrambler on cable downstream rate-limit loadbalance-group
cable downstream shutdown cable downstream shutdown cable downstream modulation
cable downstream
cable downstream sync-interval trap-enable-if cable downstream power-level
cable downstream cable downstream

trap-enable-rdn primary-capable
cable downstream rate-limit
cable downstream scrambler on

cable downstream shutdown
cable downstream
trap-enable-if
cable downstream
trap-enable-rdn
commands.

MAC Domain Layer 3 Configuration

Cable bundling allows you to group multiple cable interfaces into a single IP subnet.
This simplifies network management and conserves IP addresses. A cable bundle
comprises two or more cable interfaces: one cable interface is configured as the
master, while the remaining interfaces are configured as slaves to the master. If one
CMTS module is configured as the master, the other CMTS modules can become
slaves. The master cable interface is assigned IP addresses and the slaves share the
same IP addresses with the master. Therefore, the bundling feature eliminates the
need for an IP subnet for each cable interface.
Configuring a loopback interface as a cable bundle master provides a mechanism for
configuring the IP parameters of a cable bundle in a virtual interface which is
independent of physical cable interfaces. The advantage of configuring a virtual
interface as the cable bundle master is that IP configuration information will be
always available regardless of the state of the CMTS hardware. The slave cable
interfaces of a bundle whose master is a virtual interface will not lose their IP
information when the hardware module for one of the cable interfaces has either
failed or been removed.
Creating a Cable Bundle on a Loopback Interface

Follow these steps to configure a cable bundle on a loopback interface:
1. Use the interface loopback command in Global Configuration mode to enter the
loopback interface that you want to designate as the master cable bundle:
MOT:7A(config)#interface loopback <1-255>
where:
1-255 is the loopback interface number for the master cable bundle.
For example:
MOT:7A(config)#interface loopback 2
2. Use the ip address command in Interface Configuration mode to define an IP
address for the loopback interface:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D>
where:
A.B.C.D is the IP address of the BSR interface designated for the loopback
interface and is the primary address used by the cable modem.


associated.
3. Use the ip address secondary command in Interface Configuration mode to
optionally configure a secondary IP address for the loopback interface:
MOT:7A(config-if)#ip address <A.B.C.D> <A.B.C.D> secondary
where:
A.B.C.D is the secondary IP address of the BSR interface.
associated.
secondary optionally designates the IP address as a secondary IP address.
Include the keyword secondary after the IP address and subnet mask to
specify additional secondary IP addresses.
If you are running a BCM 3140-based DOCSIS 2.0 2:8 CMTS module
configured as two 1:4s, the limit is still 256 secondary IP subnets for the
entire 2:8 CMTS module. The total number of secondary IP subnets between
MAC Domain 0 and MAC Domain 1 can only equal 256. Also, if you apply the
4. Use the show running-config command to make sure that DHCP relay is
enabled. Check the command output to see if the IP helper address or cable helper
address is assigned to the master cable loopback interface.

5. If the IP helper address or cable helper address is not configured for the bundle
master cable interface, use the ip helper-address or cable helper-address
command, in Interface Configuration mode. The ip helper-address or cable
helper address specifies the DHCP server.
6. Use the show interfaces loopback command to determine if an IP address is
assigned to the master cable loopback interface:
MOT:7A(config-if)#show interfaces loopback <1-255>
where:
1-255 is the loopback interface number.
7. If the master cable loopback interface does not have IP address, use the ip
address command in Interface Configuration mode to specify the master cable
loopback interface IP address.
8. Use the cable bundle master command, in Cable Interface Configuration mode,
to assign the loopback interface as the master cable interface and assign the
bundle a number:
where:
For example:
9. Use the show interfaces cable command to make sure that the slave cable
interface does not have an IP address assigned to it:
10. Use the show running-config command to verify the cable bundle configuration
for each loopback interface.

Fiber Node Configuration

In an HFC network, a fiber node represents the point of interface between a fiber
termination and the coaxial distribution. In the BSR configuration, a Fiber Node
reflects the physical connectivity of the cable plant into service areas, in order to
enable channel bonding operation. It is required to assign a name to each fiber node. It
is not required, but recommended to add a description to each fiber node name
configured. The following procedures are described in this section:
Entering Fiber Node Configuration Mode
Entering a Description of the Fiber Node
Note: It is required to assign a name to each Fiber Node. It is not required,

but recommended to add a description to each Fiber Node name configured.
Entering Fiber Node Configuration Mode

Fiber Node Configuration mode allows a user to name and describe a Fiber Node. To
enter Fiber Node Configuration mode, do the following:
1. Use the cable fiber-node command, in Global Configuration mode, to enter Fiber
Node configuration mode:
MOT:7A(config)# cable fiber-node <WORD>
where:
WORD is the Fiber Node name up to a length of 15 characters.
The command line prompt changes to:
MOT:7A(config-fiber-node:<Fiber Node name>)#
2. Use the end or exit commands to return to Global Configuration mode:

Entering a Description of the Fiber Node

Use the description command, in Fiber Node Configuration mode, to enter a
description of the Fiber Node:
MOT:7A(config-fiber-node:<Fiber Node name>)description <string>
where:
string is the Fiber Node description. A maximum of 255 characters can be
entered. The description must be enclosed within double quotes if the description
contains spaces. The description can include any printable ASCII character ( # , \
! ; ? . & etc).
For example:
MOT:7A(config-fiber-node:FN-A)description North & East
Downtown

MAC Domain Configuration

The following procedures are required to configure the MAC Domain in the
Distributed MAC Domain configuration example:
Initial Configuration
CMTS 2:8 Downstream Channel Configuration
CMTS 2:8 Upstream Port Configuration
Initial Configuration
The following procedures are required for the initial configuration of the Distributed
MAC Domain in the configuration example:
Entering a Description of the Distributed MAC Domain
Associating the Cable Bundle
Binding the Downstream Channels
Entering Cable Interface Configuration Mode for the CMTS 2:8

Module
From Global Configuration mode, navigate to Cable Interface Configuration mode for
MAC Domain 0 on the CMTS 2:8 module, as follows:
where:
Entering a Description of the Distributed MAC Domain

Use the description command, in Cable Interface Configuration mode, to specify
descriptive information for each downstream port. This information is limited to 80
characters. Spaces can be used and are counted as a part of the 80 character limit.
interface command.

MOT:7A(config-if)#description <WORD>
where:
WORD is the text that describes the Distributed MAC Domain.
For example:
MOT:7A(config-if)#description Distributed MAC Domain to FN-A,
FN-B, FN-C, and FN-D
Associating the Cable Bundle

Use the cable bundle command, in Interface Configuration mode, to assign this cable
interface as the slave cable interface and assign the bundle the same number as the
bundle master loopback interface configured previously:
Binding the Downstream Channels

Use the cable bind downstream command to bind the downstream channels for the
Distributed MAC Domain, as follows:
MOT:7A(config-if)cable bind downstream <NUM>
where:
NUM is a list of local and/or remote downstream channels separated by commas.
Local channels are represented as a single digit channel number. Remote channels
are in the form slot/downstream port number/downstream channel number. No
spaces are allowed in the channel list.
For example:
MOT:7A(config-if)cable bind downstream 0,1,13/0/0,13/0/1
Use the show cable binding command to display the bind configuration.


A bonding group is a set of two or more downstream channels that offer multiple
channel through-put to individual bonding cable modems. A bonding group is limited
to two, three, or four downstream channels. Bonding groups are defined within the
context of a MAC domain. However, the downstream channels comprising a bonding
group may span two MAC domains if a bonding domain is configured.
Bonding cable modems ranging and registering on a downstream and upstream
channel pair will be considered to be registered in the MAC domain that contains that
downstream and upstream channel pair. Those cable modems will also belong to the
bonding group configured in that MAC domain. From a forwarding perspective,
downstream packets sent to a bonding modem will be forwarded to the MAC domain/
interface that the bonding modem is registered despite the fact that some of the
packets may transit downstream channels belonging to other MAC domains.
To configure a downstream channel bonding group, do the following:
where:
For example:
2. Use the cable downstream bonding-group command to configure a downstream
DOCSIS 3.0 channel bonding group.
MOT:7A(config-if)#cable downstream bonding-group <1-65535>
<NUM>
where:
1-65535 is the DOCSIS 3.0 downstream channel bonding group number.
NUM is a list of local and/or remote downstream channels separated by
spaces. Local channels are represented as a single digit channel number.
Remote channels are in the form slot/downstream port number/downstream
channel number. A remote TX32 downstream channel must be bound before
it can be bonded.

4/[0-7]/[0-3] 9/[0-1] 11/[0-1]
TX32 Module Slot Number/ 2:8 CMTS Module Slot Number/

TX32 Downstream Port Number/ Downstream Port Number
TX32 Downstream Channel Number
3. Use the cable downstream mot-bonding-group command to configure a

Motorola Proprietary downstream channel bonding group.
MOT:7A(config-if)#cable downstream mot-bonding-group <1-65535>
<NUM>
where:
1-65535 is the downstream Motorola proprietary channel bonding group
number.
NUM is a list of local and/or remote downstream channels separated by
spaces. Local channels are represented as a single digit channel number.
Remote channels are in the form slot/downstream port number/downstream
channel number. A remote TX32 downstream channel must be bound before
it can be bonded.

4/[0-7]/[0-3] 9/[0-1] 11/[0-1]
TX32 Module Slot Number/ 2:8 CMTS Module Slot Number/

TX32 Downstream Port Number/ Downstream Port Number
TX32 Downstream Channel Number
4. Use the show cable downstream bonding-groups command to verify that the
channel bonding groups and their downstream channels are enabled and
configured correctly.
MOT:7A(config-if)#show cable downstream bonding-groups
CMTS 2:8 Downstream Channel Configuration

A CMTS downstream channel is configured to control the data flow from the cable
interface to the users cable modem. The following procedures are used to configure
the CMTS 2:8 downstream channel:
Entering a Description of the Downstream Channel
Enabling the Downstream Rate Limit
Configuring the Downstream Modulation Rate
Configuring the Downstream Frequency
Associating the Fiber Nodes to the Downstream Channel
Enabling the Downstream Channel
Refer to Chapter 4 for a complete listing of available commands.

Entering a Description of the Downstream Channel

Use the cable downstream description command, in Cable Interface Configuration
mode, to specify descriptive information for each downstream port.
and in the display output of various show commands such as the show
cable downstream command.

where:
NUM is the downstream channel number.
LINE is the text that describes the downstream port. This information is limited to
80 characters. Spaces can be used and are counted as a part of the 80 character
limit.
MOT:7A(config-if)#cable downstream 0 description local dsport 0
Enabling the Downstream Rate Limit

Use the cable downstream rate-limit command to enable the downstream data
transmission rate-limit for cable modems on the HFC network. Once the downstream
data transmission rate-limit function is enabled, data sent from the cable interface to
the cable modems is rate-limited according to each cable modems configuration file.
Packets are buffered by the CMTS if the data exceeds the permitted bandwidth of the
cable modem and then queued for transmission once downstream bandwidth for the
cable modem becomes available.
Follow the steps in this section to enable the downstream rate-limit:
1. Use the cable downstream rate-limit command in Cable Interface Configuration
mode to enable the rate-limiting function:
MOT:7A(config-if)#cable downstream <NUM> rate-limit
where:
Use the no cable downstream rate-limit command to disable the downstream
rate-limiting function.

2. Use the show running-config command to verify that downstream rate-limiting

is enabled on the cable interface:
MOT:7A#show running-config | inc rate-limit
The following line should be returned for downstream port 0:
cable downstream 0 rate-limit
Configuring the Downstream Modulation Rate

Use the cable downstream modulation command, in Cable Interface Configuration
mode, to set the downstream digital to analog signal modulation rate:
MOT:7A(config-if)#cable downstream <NUM> modulation [64 | 256]
where:
64 is 6 bits per downstream symbol Quadrature Amplitude Modulation (QAM).
This is the default downstream digital to analog signal modulation rate.
256 is 8 bits per downstream symbol Quadrature Amplitude Modulation (QAM).
Use the no cable downstream modulation command to restore the default (64
QAM):
MOT:7A(config-if)#no cable downstream <NUM> modulation [64 | 256]

The default downstream power level is 55 decibels per millivolt (55 dBmV). If you
need to adjust the downstream power level, use the cable downstream power-level
command, in Cable Interface Configuration mode, as follows:
MOT:7A(config-if)#cable downstream <NUM> power-level <450-630>
where:
Use the no cable downstream power-level command to restore the default
power-level setting (55 dBmV):
MOT:7A(config-if)#no cable downstream <NUM> power-level <450-630>

Configuring the Downstream Frequency

Follow the steps in this section to configure the downstream center frequency:
Use the cable downstream frequency command, in Cable Interface Configuration
mode, to enter the fixed center frequency for the downstream channel:
MOT:7A(config-if)#cable downstream <NUM> frequency {<91000000 -
857000000>}
where:
Note: Downstream frequency ranges are different depending on your

regional implementation of DOCSIS, Euro-DOCSIS, or J-DOCSIS. The
frequency ranges that appear in the CLI help are related to your
implementation of DOCSIS.
Associating the Fiber Nodes to the Downstream Channel

Use the cable downstream fiber-node command, in Cable Interface Configuration
mode, to associate a CMTS 2:8 downstream port to one or more configured Fiber
Nodes.
MOT:7A(config-if)#cable downstream <NUM> fiber-node <WORD>
where:
WORD is the list of Fiber Node names separated by commas with no spaces
allowed.
Enabling the Downstream Channel

The downstream port is in an administrative shutdown state by default and must be
enabled to function.
Follow these steps to enable the downstream channel:
1. Use the no cable downstream shutdown command, in Cable Interface
Configuration mode, to enable the downstream channel:
MOT:7A(config-if)#no cable downstream <NUM> shutdown
where:


2. Use the show interfaces cable command in Interface Configuration mode to
verify that the downstream port is enabled:
MOT:7A(config-if)#show interfaces cable <X/Y>
where:
The following line should be returned for downstream port 0:
cable 3/0 is up, line protocol is up
CMTS 2:8 Upstream Port Configuration

An upstream channel is configured to control the data flow passing data traffic from a
cable modem to the cable interface. The following procedures are used to configure
the CMTS 2:8 upstream ports:
Binding the Upstream Ports
Enabling the Upstream Port
Binding the Upstream Ports

1. Use the cable bind upstream command to bind an upstream port a to MAC
Domain, as follows:
MOT:7A(config-if)cable bind upstream <NUM>
where:
NUM specifies a single upstream port number, a subset of upstream port
numbers (separated by commas), or all upstream port numbers on the module
separated by commas (0,1,2,3,4,5,6,7).
For example:
MOT:7A(config-if)cable bind upstream 0,1,2,3,4,5,6,7

2. Use the show cable binding cable command to verify the binding configuration:
MOT:7A(config-if)#show cable binding cable <X/Y>
where:
Note: The following procedures must be repeated for each upstream port in
the configuration example.


Use the cable upstream description command, in Cable Interface Configuration
mode, to specify descriptive information for the upstream port that you are
configuring..
Note: The entered description can be seen in the running configuration, and
in the command output of show commands such as the show cable
upstream command.
MOT:7A(config-if)#cable upstream <NUM> description <LINE>

where:
LINE is the text that describes the upstream port. This information is limited to 80
characters.
For example:
MOT:7A(config-if)#cable upstream 0 description 2:8 usport 0


A fixed upstream frequency needs to be set and must comply with the upstream
frequency plan..
Note: Make sure that the upstream frequency selected does not interfere
with the frequencies used for any other upstream applications running in the
cable plant.
1. Use the cable upstream frequency command, in Cable Interface Configuration

mode, to set the upstream frequency for an upstream port:
MOT:7A(config-if)#cable upstream <NUM> frequency
<5000000-42000000>
where:
5000000-42000000 is the upstream frequency value in Hertz (Hz) for
DOCSIS.
Note: Upstream frequency ranges are different depending on your regional

implementation of DOCSIS, Euro-DOCSIS, or J-DOCSIS. The frequency
ranges that appear in the CLI help are related to your implementation of
DOCSIS.

The upstream port is in an administrative shutdown state by default. Follow these
steps to enable the upstream channel:
Use the no cable upstream shutdown command, in Cable Interface Configuration
mode, to enable the upstream channel. You must perform both procedures.
MOT:7A(config-if)#no cable upstream <NUM> shutdown
MOT:7A(config-if)#no cable upstream <X/Y> shutdown
where:

TX32 Downstream Port Configuration

The following procedures are used to configure the TX32 downstream port:
Entering TX32 Downstream Port Configuration Mode
Entering a Description of the TX32 Downstream Port
Configuring the TX32 Channel Mode
Adjusting the TX32 Downstream Port Power Level
Configuring the TX32 Downstream Channel Frequency
Associating the Fiber Nodes to the TX32 Downstream Port
Entering a Description of the TX32 Downstream Channel
Enabling a TX32 Downstream Channel
Enabling a TX32 Downstream Port
Verifying the TX32 Downstream Port Configuration
Additional TX32 Downstream Port Configurations
Additional TX32 Downstream Channel Configurations
Entering TX32 Downstream Port Configuration Mode

TX32 Downstream Port Configuration mode allows a user to configure the TX32
downstream port as described in the above list of procedures.
To enter TX32 Downstream Port Configuration mode, do the following:
1. Use the cable downstream port command, in Global Configuration mode, to
enter TX32 Downstream Port Configuration configuration mode:
MOT:7A(config)# cable downstream port <X/Y>
where:
X/Y is the slot and downstream port number of the TX32 module.
MOT:7A(config)# cable downstream port 13/0
The command line prompt changes to:
MOT:7A(config-ds)#
2. Use the end or exit commands to return to Global Configuration mode:
MOT:7A(config-ds) end

MOT:7A(config-ds) exit
Entering a Description of the TX32 Downstream Port

Use the cable downstream description command, in TX32 Downstream
Configuration mode, to specify descriptive information for the downstream port.
and in the display output of various show commands such as the show
cable downstream command.
MOT:7A(config-ds)#cable downstream description <LINE>

where:
LINE is the text that describes the downstream port. This information is limited to
80 characters. Spaces can be used and are counted as a part of the 80 character
limit.
For example:
MOT:7A(config-ds)#cable downstream 0 description TX32 dsport 0
Configuring the TX32 Channel Mode

Use the cable downstream channel-mode command, in TX32 Downstream
Configuration mode, to configure the channel mode (1 channel, 2 channel, or 4
channel) of a TX32 downstream RF port. When configured to the default value of
4, the configuration is not displayed in the show running-config downstream port
command output.
Note: The TX32 downstream RF port must be shutdown before changing the
channel mode of the port. Also, the user must first unbind the already bound
affected channels of the TX32 downstream RF port before changing the
channel mode of the port.

MOT:7A(config-ds)#cable downstream channel-mode {1 | 2 | 4}

where:
1 allocates 1 channel on this port.
2 allocates 2 channels on this port.
4 allocates 4 channels on this port.
Adjusting the TX32 Downstream Port Power Level

The default downstream port power level is 55 decibels per millivolt (55 dBmV). If
you need to adjust the downstream port power level, use the cable downstream
power-level command, in TX32 Downstream Port Configuration mode, as follows:
MOT:7A(config-ds)#cable downstream power-level <440-600>
where:
Note: The allowed power levels that can be specified with the cable
downstream power-level command for theTX32 will vary depending on the
channel mode that the TX32 is set to with the cable downstream
channel-mode command (1, 2, or 4 channel mode).
Power-level ranges valid for a TX32 port are as follows:
Channel Mode 1 Power Level <520-600>

If a power level is configured beyond the range allowed, an error will be

displayed and the configuration will be rejected.
Use the no cable downstream power-level command in TX32 Downstream Port

Configuration mode to restore the default power-level setting (55 dBmV):
MOT:7A(config-ds)#no cable downstream power-level <440-600>

Configuring the TX32 Downstream Channel Frequency

Use the cable downstream frequency command, in TX32 Downstream Port
Configuration mode, to enter the fixed center frequency for the downstream channel:
MOT:7A(config-ds)#cable downstream <NUM> frequency <91000000 -
857000000>
where:
Note: The four downstream frequencies of a TX32 downstream port are

configured by setting downstream channel 0s center frequency. Explicit
configuration of the downstream frequency for channels 1-3 is not allowed.
The downstream frequencies of channels 1-3 are derived internally as the
next three contiguous frequencies in the spectrum (based on a channel-width
of 6 or 8 MHz) from the downstream frequency defined for channel 0.
Configuring the frequency for downstream channel 0 automatically

configures the frequency (in 6 MHz or 8 MHz increments) of the remaining
downstream channels for that TX32 port depending on the channel-mode
setting.
Associating the Fiber Nodes to the TX32 Downstream Port

Use the cable downstream fiber-node command, in TX32 Downstream Port
Configuration mode, to associate a TX32 RF Port to one or more configured Fiber
Nodes.
MOT:7A(config-ds)#cable downstream fiber-node <WORD>
where:
WORD is the list of Fiber Node names separated by commas with no spaces
allowed.
For example:
MOT:7A(config-ds)#cable downstream fiber-node
FN-A,FN-B,FN-C,FN-D

Entering a Description of the TX32 Downstream Channel

Optionally use the cable downstream description command, in Interface
Configuration mode, to specify descriptive information for a downstream port.
interface command.

where:
LINE is the text that describes the downstream channel. This information is
limited to 80 characters and spaces cannot be used.
For example:
MOT:7A(config-if)#cable downstream 0 description ds-channel0
Enabling a TX32 Downstream Channel

The downstream channel is in an administrative shut-down state by default and must
be enabled to function.
Follow these steps to enable the downstream port:
1. Use the no cable downstream shutdown command, in TX32 Downstream Port
Configuration mode, to enable the downstream channel:
MOT:7A(config-ds)#no cable downstream <0-3> shutdown
where:
0-3 is the downstream channel number.
2. Use the show running-config cable downstream port command to verify that
the downstream channel is enabled:
MOT:7A(config-ds)#show running-config cable downstream port <X/Y>
where:

Enabling a TX32 Downstream Port

The TX32 downstream port is in an administrative shut-down state by default and
must be enabled to function.
Follow these steps to enable the TX32 downstream port:
1. Use the no cable downstream shutdown command, in TX32 Downstream Port
Configuration mode, to enable the downstream port:
MOT:7A(config-ds)#no cable downstream shutdown
2. Use the show running-config cable downstream port command to verify that
the downstream channel is enabled:
where:
Verifying the TX32 Downstream Port Configuration

Use the show running-config cable downstream port command to verify the
downstream port configuration:
where:
X/Y is the slot and port number of the TX32 module.
Additional TX32 Downstream Port Configurations

The following additional TX32 downstream port configurations are available through
the following commands:
cable downstream interleave-depth
cable downstream modulation
cable downstream scrambler on
cable downstream sync-interval
commands.

Additional TX32 Downstream Channel Configurations

The following additional TX32 downstream channel configurations are available
through the following commands:
cable downstream carrier-only
cable downstream loadbalance-group
cable downstream primary-capable
cable downstream rate-limit
commands.

20
Cable Traffic Management
A DOCSIS system shares both downstream and upstream RF channels among

hundreds of subscribers. This sharing of bandwidth is feasible because few residential
users are concurrently active and transmitting at their configured maximum rate limit.
Unfortunately, a small minority of highly active modems (HAMs) are significantly
more active than the average, and these HAMs account for the vast majority of traffic.
In one traffic study by Motorola, the top 5 cable modems by traffic out of 340 cable
modems registered (1.4%) accounted for over 50% of downstream traffic during
heavy network utilization periods. Because cable operators base their long-term
capacity planning decisions on channel utilization, the HAMs can cause an operator to
unnecessarily expand downstream or upstream capacity. Another problem with HAM
traffic is that by increasing the number of backlogged cable modems at any instant,
HAM activity will lower the downstream TCP throughput rate of all of the normally
active residential cable modems.

Theory of Operations
Cable Traffic Management allows an operator to temporarily lower the maximum rate
limit for highly active modems so that they will lessen their impact on peak time
utilization and their impact on normally active modems.
The Cable Traffic Management feature provides three important new concepts within
a BSR64000:
A Cable Traffic Policy (CTP) is a configuration object that controls the creation
and operation of Traffic Token Buckets. Refer to Cable Traffic Policies.
A Traffic Token Bucket (TTB) is a run-time object that controls the rate limiter of
a single service flow by monitoring the traffic actually scheduled from the service
flow and reducing the rate limiter to a lower enforced rate when the traffic is
excessive. Refer to Traffic Token Bucket.
A cable sample interval is the configured number of minutes for calculating
tokens in a Traffic Token Bucket (TTB). Although every TTB is updated once per
cable sample interval, updating of different TTBs is staggered throughout the
cable sample interval. Refer to Traffic Token Bucket.
The following figure conceptually depicts how the Cable Traffic Management feature
controls traffic for downstream and upstream service flows.

Release 5.3.1 Cable Traffic Management
Service Flow
Packet (Request) Queue
RF
Rate Limit (L) Channel(s)
Packet
Scheduler
Sets to M
or E
Other SFs
Traffic
Token Bytes Transferred
Bucket
(TTB)
creates
Applies To
Cable Traffic Policy
In the downstream direction, the BSR maintains a queue per service flow of packets
awaiting transmission. The BSR implements a scheduler Rate Limit (denoted by L)
that limits the rate at which packets can be scheduled on a downstream channel (or set
of channels, with channel bonding). When a downstream packet at the head of the
packet queue has waited sufficiently long to not exceed its rate limit, the packet is
scheduled along with the head-of-line packets from other service flows and eventually
transferred downstream on a downstream channel.

Operation is similar in the upstream direction, except that the BSR enqueues a single
request for an upstream burst of bandwidth rather than individual packets. Even in the
upstream direction, however, the BSR implements the concept of a scheduler rate
limit L that limits the rate of upstream bandwidth grants. The BSR signals a cable
modem wih a Dynamic Service Change DOCSIS MAC management message to
change its service flow rate when it is enforced with the Cable Traffic Management
feature. For the upstream direction, this instructs the CM to not request traffic that
exceeds the enforce rate.
When a service flow is created, its initial maximum rate limit is called its
configured Maximum Sustained Traffic Rate (denoted by L). The configured
maximum rate M of a primary service flow is provided in the cable modems
configuration file.
Cable Traffic Policies

A cable traffic policy is said to apply to a service flow. A TTB for a service flow is
created for each cable traffic policy that applies to it. A cable traffic policy can apply
only to the primary downstream service flow and primary upstream service flow.
Each primary service flow can only have one cable traffic policy that applies to it.
Cable traffic policies only apply in a single direction. An operator can define
downstream policies or upstream policies. With the exception of policies that specify
bidirectional enforcement, the upstream and downstream policies operate
independently.
A cable traffic policy also applies to the bonded service flows of DOCSIS 3.0 cable
modems as well as the non-bonded service flows of pre-DOCSIS 3.0 cable modems.
Note: In order to enforce a cable traffic policy for a direction, it is necessary

that all channels in that direction have rate limiting enabled with the cable
downstream rate-limiting or cable upstream rate-limiting commands.
Rate limiting is enabled for downstream or upstream channels by default. In
order to use the Cable Traffic Management feature effectively, a user must
make sure that rate limiting is enabled for all channels on the BSR. The BSR
warns the user when enabling the Cable Traffic Management feature for a
direction if any channel in that direction does not have rate limiting enabled.

Traffic Token Bucket

The Traffic Token Bucket operates in the background control plane of the
BSR64000, rather than in the high-speed data plane of per-packet processing. The
operator configures a global cable sample interval at which the TTB operates. At
least once every cable sample interval, the TTB updates a token count based on the
traffic actually transmitted for the service flow. If the token count goes negative, the
TTB then adjusts the flows maximum rate limiter to an enforce rate. A flow which is
limited to the lower enforce rate is said to be penalized".
The operation of a Traffic Token Bucket is depicted in the following figure:
Enforce Rate (E)
Credit (C)
Tokens (T)
Bytes Transferred (B)
A Traffic Token Bucket implements a variation of a leaky bucket algorithm. The

TTB maintains a single signed 32-bit counter of tokens (denoted by T) which can
be visualized as the level of water in a leaky bucket. Each token represents the right to
send one unpenalized byte of traffic at the configured maximum rate. The maximum
number of tokens that can be held in the TTB is called its maximum Credit (denoted
by C), which represents the maximum number of bytes that the flow can transmit
before becoming penalized. A TTB is always initialized to its Credit Maximum value.
As the service flow transfers bytes, the TTB subtracts one token per byte transferred.
A TTB token count only includes subscriber Ethernet payload bytes, from the first
byte of the Ethernet Destination Address to the last byte of the CRC. It does not
include DOCSIS physical or MAC layer overhead bytes. This is the same convention
used for counting service flow byte statistics.

The difference between the TTBs initial credit maximum C and its current token
level T (or C-T) is called the traffic count statistic of the TTB and is displayed
through the show commands of the CTM feature.
Token buckets are implemented as signed 32-bit integers storing units of 1000-byte
kilobytes. They are updated in the background processing of the BSR based on the
number of bytes transferred in a cable sample interval.
The Traffic Token Bucket is analogous to a bank account with a credit balance and
direct deposit of a regular paycheck. As long as the balance is positive, the entire
initial credit can be spent, but once the credit is gone, only the regularly earned
paychecks can be spent.
Traffic Token Bucket Monitoring Algorithms

The TTBs token count is controlled via a configured monitoring algorithm. The two
monitoring algorithms are:
Continuous monitoring
Peak-time monitoring.
If a cable traffic policy is configured with the peak-time command, the TTBs created
for it use the peak-time monitoring algorithm. If no peak-time interval is defined, all
TTBs created for the cable traffic policy use the continuous monitoring algorithm.
With peak-time monitoring, a TTB only monitors service flow traffic during a
configured peak-time interval during a day. With this algorithm, the TTB resets itself
to the credit maximum C at the start of the peak-time, and only subtracts tokens for
traffic transferred during the peak-time itself. The TTB does not add tokens with
peak-time monitoring. After the peak time ends, the TTB remains frozen at its final
value until the start of the next peak-time interval.
With continuous monitoring, a TTB monitors service flow traffic at all times in the
traditional manner of a token bucket. On every sample interval boundary, the TTB
both subtracts tokens for bytes transferred and adds tokens earned at the enforce
rate for the passage of time, or E * S. In this manner, as long as the flow transfers at or
below the long-term enforce rate, the token level will remain constant. As the flow
transfers over the enforce rate, the token level will drop. When the token level drops
below zero, the flow is enforced to transfer at only the enforce rate itself. Over any
long-term interval T much longer than the sample interval S, the flow can transmit a
total of only C+E*T bytes.

At the boundary between cable sample intervals, a TTB removes tokens for the
number of bytes transferred for the service flow (denoted by B), i.e. transmitted
downstream or received upstream. Because tokens are updated only on cable sample
interval boundaries, rather than with every packet, the token count of a TTB is
permitted to go negative.
Traffic Enforcement Algorithms

A TTB enforces the traffic rate of a service flow with one of two different
enforcement algorithms:
A token-based algorithm whereby enforcement is applied whenever a
monitored flow has no positive tokens.
A penalty-period algorithm, whereby enforcement is applied for a fixed
duration penalty-period.
A TTB uses the penalty-period algorithm when its cable traffic policy is configured
with the penalty-period command. If no penalty-period attribute is configured, the
TTB uses the token-based algorithm.
With either algorithm, when the token level of a TTB drops below zero, the TTB
changes the packet scheduler rate limiter L to the enforce rate E for that service flow
based on the TTBs cable traffic policy enforce configuration. The packet rate
limiter L remains at the lower enforce rate E for the entirety of the next cable sample
interval.
Cable Sample Interval

Cable Traffic Management operates in the background of data forwarding,
periodically updating a Traffic Token Bucket based on background sampling of the
bytes transferred for a service flow. The configured cable sample interval controls the
maximum interval between updates of a TTB for a single service flow. Because
thousands of TTBs must be updated during a sample interval (one for each primary
service flow), the BSR staggers the updates for different flows at different times
during the sample interval. The cable sample interval defines the staggering rate of
traffic token bucket updates assuming that the maximum of 14000 service flows must
be updated during the interval. For example, with the default cable sample interval of
300 seconds, the pacing rate is approximately 46 TTB updates per second.

Because a TTB is only updated on a time-staggered cable sample interval boundary,

the time at which a TTB recognizes the start or end of a peak-time monitoring
interval may differ from the actual peak-time start by up to one full cable sample
interval. The earliest that a TTB can enforce a flow monitored during a peak-time is
the second cable sample boundary after the peak-time start, so it may take up to two
cable sample intervals after the actual peak-time start time of day for a TTB to enforce
a service flow.
Note: During a CMTS switchover, the staggered cable sample interval

boundary for each TTB is recalculated so that the duration of a penalty period
in progress may be up to one cable sample interval shorter or longer than the
penalty period would have been had the CMTS switchover not occurred.
Offline Cable Modems

When a cable modem deregisters, the BSR maintains the current state of primary
service flow TTBs in memory as offline TTBs. Offline TTBs continue to be
updated on cable sample interval boundaries, although no bytes are transferred for the
TTB. When and if the cable modem re-registers, the TTBs for its primary service
flows are updated to reflect the passage of time while the CM was offline rather than
being reset to their initial values. This prevents subscribers from bypassing
enforcement of cable traffic policies by periodically resetting their CM.
The BSR destroys an offline TTB when it updates it back to its initial condition. For
peak-time monitored TTBs, this occurs at the start of the next peak-time interval. For
continuously-monitored TTBs, this occurs when the token count is increased to its
credit maximum and any penalty-period has expired.
The BSR supports a maximum of two TTBs, including both online and offline TTBs,
on a CMTS module for the maximum number of service flows supported by that
module. In Release 5.0.1, the CMTS 2:8 module supports a maximum of 7168 CMs
and a maximum of 14436 TTBs.

Other Cable Traffic Management Operational

Features
Cable Traffic Management operates independently of the Dynamic Load Balancing
feature; a service flows traffic token bucket is updated regardless of the particular
channel (or channels) of a MAC domain on which the service flow is assigned.
Cable Traffic Management inter-operates with cable interfaces that are configured
with the Dual 2x8 Channel Bonding feature, i.e. the feature manages bonded service
flow traffic that includes traffic transferred on remote CMTS 2x8 modules. The
Cable Traffic Management feature operates with the distributed MAC domain
feature of the TX32 feature, i.e. it manages bonded and non-bonded service flow
traffic transferred on a remote DTX module.
SRM and CMTS Redundancy is supported by the Cable Traffic Management feature.
Configuring a Cable Traffic Policy

This section discusses the functionality and configuration procedures for the Cable
Traffic Management feature on the BSR. The following topics and procedures are
described:
Applying Cable Traffic Policies to Subscriber Service Tiers
Cable Traffic Policy Configuration Tasks
Configuring the Cable Sample Interval
Displaying Cable Traffic Management Information
Clearing Cable Traffic Management Statistics
Applying Cable Traffic Policies to Subscriber Service Tiers

A subscriber service tier is a combination of QOS parameters for the service flows
provided to a single subscriber and is often expressed as the combination of the
configured maximum rate in both the downstream and upstream directions. For
example, a 2/128 tier refers to a configured maximum rate of 2 Mbps in the
downstream direction and 128 kbps in the upstream direction.
A cable traffic policy can be configured to apply to a single subscriber tier or multiple
subscriber tiers. An operator should select only one of these two configuration
strategies for applying cable traffic policies to subscriber tiers.
The following table summarizes how the attributes of a cable traffic policy should be
configured for each configuration strategy:

Single Tier Multiple Tiers

per Policy per Policy Refer to:
max-rate max-rate all Configuring Maximum Rate Matching

credit credit Configuring the Credit Maximum
enforce enforce Configuring the Enforce Rate
With the single-tier configuration strategy, the cable traffic policy matches a single
configured maximum rate value. The token bucket credit maximum and enforce rate
and are both specified in absolute terms.
With a multiple-tier strategy, the policy applies to all primary service flows in the
policys direction regardless of their configured maximum rate. In the multiple-tier
case, the credit maximum and enforce rate of the TTBs controlled by the policy are
specified relative to the configured maximum rate of the flow.
Cable Traffic Policy Configuration Tasks

The following list summarizes the tasks required for the configuration of a cable
traffic policy:
Entering Cable Traffic Policy Configuration Mode
Configuring Maximum Rate Matching
Configuring the Credit Maximum
Configuring the Enforce Rate
Configuring the Peak Time
Configuring the Penalty Period
Configuring Bidirectional Enforcement
Enabling a Cable Traffic Policy

For more detailed descriptions of the commands used for the tasks described in this
section, refer to the BSR 64000 Command Reference Guide.
bidirectional
cable traffic sample-interval
cable traffic policy
clear cable traffic enforcement
clear cable traffic history
credit
enabled
enforce
max-rate
peak-time
penalty-period
show cable subscriber-usage
show cable subscriber-usage summary
show cable traffic policy
Entering Cable Traffic Policy Configuration Mode

Cable Traffic Policy configuration mode allows a user to configure a Cable Traffic
Policy. A user can either create a new named cable traffic policy in a specified
direction and enters Cable Traffic Policy configuration mode for the new policy or
enters Cable Traffic Policy configuration mode for an existing cable traffic policy.
Use the command the cable traffic policy command to configure a cable traffic
policy, as follows:
MOT(config)#cable traffic policy <ctp-name> {upstream | downstream}
where:
ctp-name is the cable traffic policy name. The name can be from one to 12
case-sensitive alphanumeric characters including underscores and must start with
a letter.
upstream indicates that this cable traffic policy applies in the upstream direction.
downstream indicates that this cable traffic policy applies in the downstream
direction.

The following prompt displays indicating that the user is in Cable Traffic Policy
configuration mode (config-traffic:<ctp-name>#)
Configuring Maximum Rate Matching

The max-rate command specifies whether a cable traffic policy only applies to
primary service flows with a particular configured maximum rate. The max-rate
configuration is in kilobits per second (kbps). When a cable traffic policy is created,
the default setting is max-rate all which means that the policy applies to all
configured maximum rate values (i.e. all service flows in the direction of the cable
traffic policy). When a cable modem registers, the BSR selects a cable traffic policy
for its primary downstream and primary upstream service flows based on the
configured maximum rate of the service flow. The BSR prioritizes matching to a cable
traffic policy with a specific match for the max-rate <kbps> configuration over a
policy with a max-rate all configuration. The BSR does not permit more than one
cable traffic policy in the same direction to be configured with the same max-rate
configuration.
If max-rate 0-4294967 is configured, the policy will apply to a service flow only if
that service flows configured maximum rate value equals the value specified in the
0-4294967 argument of the command.
Use the max-rate command to specify whether a cable traffic policy only applies to
primary service flows with a particular configured maximum rate, as follows:
MOT(config-traffic:<ctp-name>)#max-rate {<0-4294967> | all}
where:
0-4294967 indicates that the cable traffic policy will apply to a service flow only
if that service flows configured maximum rate value equals the value specified in
the 0-4294967 argument. Entering a max-rate of "0" will specify that the cable
traffic policy applies to all service flows of cable modems without configured
max rates.
all indicates that the cable traffic policy applies to all configured maximum rate
values - all service flows in the direction of the cable traffic policy.

Configuring the Credit Maximum

The credit command configures how a TTB controlled by a cable traffic policy
determines its credit maximum.
Use the credit command to configure how a TTB controlled by a cable traffic policy
determines its credit maximum, as follows:
MOT(config-traffic:<ctp-name>)#credit {mbytes <1-2147483> | seconds
<1-43200> }
where:
mbytes 1-2147483 indicates that the credit maximum is the absolute number of
megabytes specified.
seconds 1-43200 indicates that the credit maximum is calculated relative to the
configured maximum rate (max-rate) as the number of megabytes (rounded up)
transferred in a specified number of seconds at the rate of bits per second.
Note: Motorola recommends that the credit mbytes option for TTBs be
configured to be at least 10 megabytes.
Configuring the Enforce Rate

The enforce configures how a TTB controlled by the cable traffic policy determines
its enforce rate for a service flow to which the policy applies. The enforce rate can be
configured to an absolute number with enforce rate command or as a relative
percentage of the configured maximum rate (max-rate) with the enforce percent
command.
Use the enforce command to specify the enforce rate for service flow, as follows:
MOT(config-traffic:<ctp-name>)#enforce { percent <0-100> | rate
<8-200000> }
where:
percent <0-100> configures the enforce rate relative to the percentage of the
service flow's maximum rate (max-rate).
rate <8-200000> configures the enforce rate to a absolute number in kbps.

Configuring the Peak Time

The peak-time command configures a cable traffic policy for peak-time monitoring
mode. In peak-time monitoring mode, a service flow is permitted to send a traffic
count up to a credit limit during a configured peak-interval in the day before being
penalized to an enforced rate. A policy can be configured with up to four
non-overlapping peak-time attributes, each with a different index value.
Use the peak-time command to configure a cable traffic policy for peak-time
monitoring mode, as follows:
MOT(config-traffic:<ctp-name>)#peak-time <1-4> {daily | weekday |
weekend} start {<hh:mm> | <0-23>} duration <1-1440>
where:
1-4 indicates a required index argument that uniquely identifies the peak-time
interval within the cable traffic policy.
daily specifies a peak-time that is defined all seven days of the week.
weekday specifies a peak-time interval that is defined only Monday through
Friday.
weekend specifies the peak-time interval as only on Saturday or Sunday.
start {<hh[:mm]> | <hh>} / start 0-23 specifies the starting hour (and optionally,
minute) of the peak time during the day. hh = 0-23 mm = 0-59
duration 1-1440 specifies the number of minutes that the peak-time interval
lasts. The duration may not extend past 24 hours.
Note: Peak-time monitoring mode is disabled by default. Not configuring the

peak-time command causes the CTM to use Continuous Mode.

Configuring the Penalty Period

The penalty-period command configures a cable traffic policy to penalize a service
flow exceeding its traffic count credit for a fixed duration penalty period. The penalty
is also enforced for that primary service flow in the opposite direction, provided a
policy is applied in that direction.
Note: The penalty-period mode of traffic enforcement is intended for

compatibility with other vendors subscriber traffic management feature.
Motorola recommends NOT using the penalty-period configuration and using
token-based enforcement instead. Token-based enforcement restores
subscribers to their configured maximum rate limit as soon as they have
earned the tokens to do so minimizing the enforcement duration for the
subscriber.
Use the penalty-period command to configure a cable traffic policy penalty period,
as follows:
MOT(config-traffic:<ctp-name>)#penalty-period <0-1440>
[expires-end-peak]
where:
0-1440 specifies the penalty period duration in minutes (24 hour maximum). The
minimum penalty-period may be specified as "0" minutes in order to monitor
subscriber traffic without enforcing it.
expires-end-peak stops enforcement of a service flow at the end of the policy
peak time. If the expires-end-peak option is specified, then any penalty-period
being enforced at the end of the peak-time expires. If the expires-end-peak
option is omitted, a penalty period can extend beyond the end of the current
peak-time. Any such late penalty-period expires automatically at the start of the
next peak-time interval. The expires-end-peak option is ignored with continuous
traffic monitoring, i.e. when no peak-time is configured.

Configuring Bidirectional Enforcement

The bidirectional command specifies that when a primary service flow controlled by
a cable traffic policy is enforced in one direction, the penalty is also enforced for that
primary service flow in the opposite direction. If the opposite directions primary
service flow does not have a cable traffic policy applied and the policy is not enabled
when the bidirectional attribute is configured, the BSR logs an event. Each cable
traffic policy can have bidirectional configured as an option.
Note: The bidirectional configuration is intended to match the behavior of

other vendors Subscriber Traffic Management enforce-rule options which
penalize both the upstream and downstream primary service flows when a
downstream service flow or upstream service flow's traffic count exceeds its
policy credit maximum. Motorola recommends omitting the bidirectional
configuration so that only the service flow direction which is being abused is
penalized.
Use the bidirectional command to configure the bidirectional parameter for a service
flow, as follows:
MOT(config-traffic:<ctp-name>)#bidirectional
Enabling a Cable Traffic Policy

The enabled command enables a configured cable traffic policy. When a cable traffic
policy is first created, it is disabled by default. Cable traffic policies are configured
with working defaults and may be enabled immediately after creation without any
additional configuration. The default values are:
Command Command Default
max-rate max-rate all

credit The default cable sample interval in seconds.
The default cable sample interval is 5
minutes, so the default credit maximum is
300 seconds.
enforce enforce percent = 50
bidirectional Disabled

penalty-period Disabled
peak-time Disabled
Note: No attribute of an existing cable traffic policy can be changed while it is

enabled. For example, you must disable a cable traffic policy in order to
change the max-rate attribute. When a cable traffic policy is disabled, all
TTBs configured by the policy are deleted and all service flows controlled by
those TTBs are restored to their configured maximum rate.
Use the enabled command to enable a configured cable traffic policy, as follows:
MOT(config-traffic:<ctp-name>)#enabled
Configuring the Cable Sample Interval

The cable traffic sample-interval command configures the cable sample interval at
which Traffic Token Buckets (TTBs) are updated and enforcement applied. The
configured cable sample interval controls the interval between updates of a TTB for a
single service flow.
Note: When any cable traffic policies are enabled, setting the cable traffic
sample-interval will disable and re-enable these policies after the interval is
changed. This will reset any current enforcement. A user will receive the
following warning message:
Changing sample-interval will reset any enabled cable

traffic policies. Continue? [yes/no]:
Use the cable traffic sample-interval command, in Global Configuration mode, to

configure the cable sample interval, as follows:
MOT(config)#cable traffic sample-interval <5-60>
where:
5-60 indicates the cable sample interval in minutes.

Displaying Cable Traffic Management Information

show cable subscriber-usage
The show cable subscriber-usage command displays the cable traffic policy
enforcement state for downstream and upstream primary service flows of online cable
modems for which a cable traffic policy is applied.
MOT:7A# show cable subscriber-usage [ <mac> | <X/Y> ] [ downstream |
upstream] [<ctp-name> | over-consume | sort-byte-count ]
where:
mac displays the cable traffic policy enforcement state for downstream and
upstream primary service flows, for which a cable traffic policy is applied, of the
indicated cable modems MAC address.
X/Y restricts the command output to a single cable interface and MAC domain,
otherwise, all interfaces are shown in order of slot and MAC domain number.
downstream displays all the downstream service flows of the cable traffic policy.
upstream displays all the upstream service flows of the cable traffic policy.
ctp-name indicates the name of a cable traffic policy. Only the configuration for
the this named policy is displayed.
over-consume restricts the command output to service flows that have been
penalized (or were being penalized at that time) since the last clear cable traffic
history command was issued. These are service flows that report a Last
Enforced timestamp in the command output.
sort-byte-count displays the service flows on a given cable traffic policy are
shown in decreasing order of Traffic Count, otherwise, the service flows are
shown in increasing order of the service flow ID.
the show cable subscriber-usage command.

show cable subscriber-usage summary

The show cable subscriber-usage summary command displays the sum of the traffic
transferred for all service flows controlled by a particular cable traffic policy on a
particular cable interface.
MOT:7A# show cable subscriber-usage summary [ downstream | upstream ]
[<X/Y>]
where:
downstream displays all the downstream service flows of the cable traffic policy.
upstream displays all the upstream service flows of the cable traffic policy.
X/Y restricts the command output to a single cable interface and MAC domain,
otherwise, all interfaces are shown in order of slot and MAC domain number.
the show cable subscriber-usage summary command.
show cable traffic policy

The show cable traffic policy command displays the configuration of all existing
cable traffic policies.
MOT:7A# show cable traffic policy [<ctp-name>]
where
ctp-name indicates the name of a cable traffic policy. Only the configuration for
this policy is displayed.
the show cable traffic policy command.

Clearing Cable Traffic Management Statistics

clear cable traffic enforcement
The clear cable traffic enforcement command clears the Traffic Count fields
displayed with the show cable subscriber-usage command and, depending on the
parameter specified with the clear cable traffic enforcement command, will effect
the summary counts in the show cable subscriber-usage summary output.
MOT:7A# clear cable traffic enforcement {<cmMac> | <ctp-name> | <X/Y> | all}
where:
cmMac indicates a cable modem MAC address. The command clears the TTBs
for the downstream and upstream primary service flows of the indicated cable
modem.
ctp-name indicates a cable traffic policy name. The command clears all TTBs
created by that policy on all cable interface.
X/Y clears the TTBs for all online cable modems registered in the indicated cable
interface and MAC domain.
all clears the TTBs for all online cable modems on all cable interfaces.
clear cable traffic history

The clear cable traffic history command starts a newEnforced Since history
period for the show cable subscriber-usage command. The clear cable traffic
history command clears the Last Enforced timestamp for all TTBs and the Last
Enforced field of the show cable subscriber-usage command for all service flows.
Subsequent show cable subscriber-usage commands will display as Last Enforced
only those service flows that had started enforcement since the clear cable traffic
history command was issued.
MOT:7A# clear cable traffic history

A
Pre-Defined Modulation
Profiles
Introduction
This appendix lists the pre-defined modulation profiles supported in Release 4.1.0 of
the BSR software. There are 23 default modulation profiles assigned to the TDMA
(1-4), MTDMA (101-116), A-TDMA (201-205), and S-CDMA (301-310) channel
types.

Compass ID: 362291231 Version 2 A-1

TDMA A-TDMA
Modulation Profile 1 Modulation Profile 201
Modulation Profile 205
MTDMA
Modulation Profile 101 S-CDMA
A-2 Compass ID: 362291231 Version 2

Release 5.3.1 Pre-Defined Modulation Profiles
Cable Modulation Profile 1

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
| IUC | Req | Init | Per | Short| Long | Adv | Adv | Adv |
| | | Maint| Maint| Data | Data | Short| Long | UGS |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk 16qam 16qam
Diff Encoding OFF OFF OFF OFF OFF
Preamble Len 64 128 128 144 160
FEC Err CRC 0 5 5 5 10
FEC CW Len 16 34 34 78 235
Scrambler Seed 338 338 338 338 338
Max Burst 2 0 0 8 0
Guard Time 8 48 48 8 8
Last Codeword FIXED FIXED FIXED SHORT SHORT
Scrambler ON ON ON ON ON
Intlv Depth 1 1 1 1 1
Intlv Blk Sz 0 0 0 0 0
Preamble Type NONE NONE NONE NONE NONE
S-CDMA Spreader OFF OFF OFF OFF OFF
Codes Subfrm 0 0 0 0 0
Intlv Stp Sz 0 0 0 0 0
TCM Encoding OFF OFF OFF OFF OFF
Channel Type tdma tdma tdma tdma tdma


+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk qpsk qpsk
Preamble Len 64 128 128 72 80
FEC CW Len 16 34 34 78 220
Scrambler Seed 338 338 338 338 338
Max Burst 2 0 0 12 0


+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk 16qam 16qam
Preamble Len 64 128 128 144 160
FEC CW Len 16 34 34 78 220
Scrambler Seed 338 338 338 338 338


+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk qpsk qpsk
Preamble Len 64 128 128 72 80
FEC CW Len 16 34 34 78 220
Scrambler Seed 338 338 338 338 338

TDMA and A-TDMA support

16-QAM with heavy Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
64-QAM with Medium Post-Equalization for DOCSIS 2.0 cable modems
Medium to heavy FEC for all burst types
Limited Pre-Equalization support
Note: Pre-Equalization must be enabled on the BSR.
Cable Modulation Profile 101 needs a fairly clean plant with an SNR of at least 27 dB. Profile will tolerate
some impulse noise.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk 16qam 16qam 64qam 64qam XXXX
Diff Encoding OFF OFF OFF OFF OFF OFF OFF XXXX
Preamble Len 64 128 128 384 384 120 120 XXXX
FEC Err CRC 0 5 5 5 10 12 16 XXXX
FEC CW Len 16 34 34 78 235 75 220 XXXX
Scrambler Seed 338 338 338 338 338 338 338 XXXX
Max Burst 0 0 0 8 0 6 0 XXXX
Guard Time 8 48 48 8 8 8 8 XXXX
Last Codeword FIXED FIXED FIXED SHORT SHORT SHORT SHORT XXXX
Scrambler ON ON ON ON ON ON ON XXXX
Intlv Depth 1 1 1 1 1 1 1 XXXX
Intlv Blk Sz 0 0 0 0 0 1536 1536 XXXX
Preamble Type QPSK0 QPSK0 QPSK0 NONE NONE QPSK1 QPSK1 XXXX
S-CDMA Spreader OFF OFF OFF OFF OFF OFF OFF XXXX
Codes Subfrm 0 0 0 0 0 0 0 XXXX
Intlv Stp Sz 0 0 0 0 0 0 0 XXXX
TCM Encoding OFF OFF OFF OFF OFF OFF OFF XXXX
Channel Type mtdma mtdma mtdma mtdma mtdma mtdma mtdma XXXX


QPSK with no Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
16-QAM with no Post-Equalization for DOCSIS 2.0 cable modems
Medium to heavy FEC for all burst types
Limited Pre-Equalization support
Cable Modulation Profile 102 would commonly be used on a cable plant with a high noise floor. Profile
requires an SNR of at least 21 dB. Profile will tolerate some impulse noise. This profile does not deal well
with significant plant distortions such as micro-reflections or group delay.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk qpsk qpsk 16qam 16qam XXXX
FEC Err CRC 0 5 5 5 8 12 16 XXXX
FEC CW Len 16 34 34 78 220 99 220 XXXX
Intlv Blk Sz 0 0 0 0 0 1536 2048 XXXX
Preamble Type QPSK0 QPSK0 QPSK0 NONE NONE QPSK0 QPSK0 XXXX


16-QAM with no Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
Heavy FEC for all burst types
Excellent Pre-Equalization support
Cable Modulation Profile 103 requires an SNR of at least 27 dB. Profile will tolerate a moderate level of
impulse noise. For plants with predominantly DOCSIS 2.0 cable modems (which correctly support
Pre-Equalization), this profile will deal fairly well with significant plant distortions such as micro-reflections or
group delay.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC Err CRC 0 7 7 8 10 16 16 XXXX
FEC CW Len 16 34 34 75 219 75 219 XXXX
Intlv Blk Sz 0 0 0 0 0 0 2048 XXXX
Preamble Type QPSK0 QPSK0 QPSK0 QPSK0 QPSK0 QPSK1 QPSK1 XXXX


16-QAM with no Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
group delay. TDMA and A-TDMA 16-QAM and 64-QAM Profile for Mixed Impulse Channel
* MS = 32T (UCD field value of 5)

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk 16qam 16qam 64qam 64qam 64qam
Diff Encoding OFF OFF OFF OFF OFF OFF OFF OFF
Preamble Len 64 640 384 72 80 88 96 96
FEC Err CRC 0 10 10 10 10 16 16 16
FEC CW Len 16 34 34 75 219 75 219 219
Scrambler Seed 338 338 338 338 338 338 338 338
Max Burst 0 0 0 8 0 6 0 0
Guard Time 8 48 48 8 8 8 8 8
Last Codeword FIXED FIXED FIXED SHORT SHORT SHORT SHORT SHORT
Scrambler ON ON ON ON ON ON ON ON
Intlv Depth 1 1 1 1 1 1 0 0
Intlv Blk Sz 0 0 0 0 0 0 2048 2048
Preamble Type QPSK0 QPSK0 QPSK0 QPSK0 QPSK0 QPSK1 QPSK1 QPSK1
S-CDMA Spreader OFF OFF OFF OFF OFF OFF OFF OFF
Codes Subfrm 0 0 0 0 0 0 0 0
Intlv Stp Sz 2 2 2 0 0 2 2 2
TCM Encoding OFF OFF OFF OFF OFF OFF OFF OFF
Channel Type mtdma mtdma mtdma mtdma mtdma mtdma mtdma mtdma


16-QAM with very limited Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
256-QAM with moderate Post-Equalization for DOCSIS 2.0 cable modems
Minimal FEC for all burst types
Cable Modulation Profile 105 requires an SNR of at least 33 dB. Profile will tolerate a very limited level of
group delay. TDMA and A-TDMA 256-QAM and Transmit Pre-equalization.
Note: This profile does not conform to the DOCSIS standard as 256-QAM is not supported in TDMA mode
by DOCSIS 1.0, 1.1, or 2.0.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


16-QAM with heavy Post-Equalization for DOCSIS 1.0 and 1.1 cable modems
256-QAM with heavy Post-Equalization for DOCSIS 2.0 cable modems
impulse noise. With both Pre- and Post-Equalization, this profile will deal well with significant plant
distortions such as micro-reflections or group delay. TDMA and A-TDMA 256-QAM and Transmit
Post-Equalization.
by DOCSIS 1.0, 1.1, or 2.0.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


group delay. TDMA and A-TDMA 128-QAM and Transmit Pre-Equalization.
by DOCSIS 1.0, 1.1, or 2.0.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


Post-Equalization.
by DOCSIS 1.0, 1.1, or 2.0.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX



+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


Post-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


Minimal FEC for DOCSIS 1.0 and 1.1 cable modems, moderate to heavy FEC for DOCSIS 2.0 cable
modems
group delay. TDMA and A-TDMA 32-QAM and Transmit Pre-Eequalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


16-QAM with very heavy Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
Minimal FEC except for long data packets from DOCSIS 2.0 cable modems
Post-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


Pre-Equalization ), this profile will deal fairly well with significant plant distortions such as micro-reflections
or group delay. While this profile will operate, it is generally not recommended for field use as its preamble
settings affecting the equalizer performance between DOCSIS 1.x and 2.0 cable modems are not optimized.
TDMA and A-TDMA 16-QAM and Transmit Pre-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


Minimal FEC for DOCSIS 1.0 and 1.1 cable modems, heavy FEC for DOCSIS 2.0 cable modems
Cable Modulation Profile 114 requires an SNR of at least 21 dB. Profile will tolerate a limited level of impulse
noise. With both Pre- and Post-Equalization, this profile will deal well with significant plant distortions such
as micro-reflections or group delay. TDMA and A-TDMA 16-QAM and Transmit Post-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


QPSK with very limited Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
8-QAM with limited Post-Equalization for DOCSIS 2.0 cable modems
modems
Cable Modulation Profile 115 requires an SNR of at least 18 dB. Profile will tolerate a modeate level of

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX


QPSK with very limited Post-Equalizatiom for DOCSIS 1.0 and 1.1 cable modems
8-QAM with limited Post-Equalization for DOCSIS 2.0 cable modems
modems
Cable Modulation Profile 116 requires an SNR of at least 18 dB. Profile will tolerate a modeate level of
group delay. TDMA and A-TDMA 8-QAM.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
FEC CW Len 16 34 34 75 220 75 220 XXXX
Last Codeword FIXED FIXED FIXED FIXED FIXED FIXED FIXED XXXX
Intlv Blk Sz 1536 1536 1536 1536 1536 1536 1536 XXXX

A-TDMA support of 64-QAM only for DOCSIS 2.0 cable modems

Moderate Post-Equalizatiom for long date and UGS
No Post-Equalization for short data
Cable Modulation Profile 201 requires an SNR of at least 27 dB. Profile only supports plants with DOCSIS
2.0 cable modems, but in such cases, should provide excellent performance in dealing with impulse noise
and significant distortions such as micro-reflections or group delay. A-TDMA 64-QAM Transmit
Pre-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk XXXX XXXX 64qam 64qam 64qam
Diff Encoding OFF OFF OFF XXXX XXXX OFF OFF OFF
Preamble Len 64 640 384 XXXX XXXX 64 128 128
FEC Err CRC 4 10 10 XXXX XXXX 16 16 16
FEC CW Len 16 34 34 XXXX XXXX 75 219 219
Scrambler Seed 50 338 338 XXXX XXXX 6236 6378 6378
Max Burst 0 0 0 XXXX XXXX 3 0 0
Guard Time 8 48 48 XXXX XXXX 8 8 8
Last Codeword FIXED FIXED FIXED XXXX XXXX SHORT SHORT SHORT
Scrambler ON ON ON XXXX XXXX ON ON ON
Intlv Depth 1 1 1 XXXX XXXX 1 1 1
Intlv Blk Sz 1536 1536 1536 XXXX XXXX 1536 1536 1536
Preamble Type QPSK0 QPSK0 QPSK0 XXXX XXXX QPSK1 QPSK1 QPSK1
S-CDMA Spreader OFF OFF OFF XXXX XXXX OFF OFF OFF
Codes Subfrm 0 0 0 XXXX XXXX 0 0 0
Intlv Stp Sz 0 0 2 XXXX XXXX 0 0 0
TCM Encoding OFF OFF OFF XXXX XXXX OFF OFF OFF
Channel Type A-TDMA A-TDMA A-TDMA XXXX XXXX A-TDMA A-TDMA A

A-TDMA support of 64-QAM only for DOCSIS 2.0 cable modems (with 32-QAM for short data)
Moderate Post-Equalizatiom for all data bursts
Pre-Equalization and Post-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+



+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+


Cable Modulation Profile 204 requires an SNR of at 21 dB. Profile only supports plants with DOCSIS 2.0
cable modems, but in such cases, should provide excellent performance in dealing with impulse noise and
significant distortions such as micro-reflections or group delay. A-TDMA 16-QAM Transmit Pre-Equalization
and Post-Equalization.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+


Moderate Post-Equalizatiom for long date and UGS
No Post-Equalization for short data

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+

S-CDMA support of 64-QAM

Cable Modulation Profile 301 requires an SNR of at least 27 dB; This profile only supports plants with
DOCSIS 2.0 cable modems, but in such cases, should provide very good performance in dealing with
impulse noise and significant distortions such as micro-reflections or group delay.
Additional Recommended Configurations
cable upstream actives-codes = 112
cable upstream spread-interval = 32
cable upstream codes-minislot = 2


+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
S-CDMA Spreader ON OFF OFF XXXX XXXX ON ON ON
Channel Type S-CDMA S-CDMA S-CDMA XXXX XXXX S-CDMA S-CDMA S


Minimal Post-Equalizatiom for all data bursts
Moderate FEC for short data, heavy FEC for long data
cable upstream actives-codes = 126 (typical), 112 (AWGN)

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Modulation qpsk qpsk qpsk XXXX XXXX 64qam 64qam XXXX
Diff Encoding OFF OFF OFF XXXX XXXX OFF OFF XXXX
Preamble Len 64 640 384 XXXX XXXX 64 96 XXXX
FEC Err CRC 0 7 7 XXXX XXXX 10 16 XXXX
FEC CW Len 16 34 34 XXXX XXXX 75 219 XXXX
Scrambler Seed 50 338 338 XXXX XXXX 6236 6378 XXXX
Max Burst 0 0 0 XXXX XXXX 5 0 XXXX
Guard Time 0 0 0 XXXX XXXX 0 0 XXXX
Last Codeword FIXED FIXED FIXED XXXX XXXX SHORT SHORT XXXX
Scrambler ON ON ON XXXX XXXX ON ON XXXX
Intlv Depth 1 1 1 XXXX XXXX 1 1 XXXX
Intlv Blk Sz 0 0 0 XXXX XXXX 0 0 XXXX
Preamble Type QPSK0 QPSK0 QPSK0 XXXX XXXX QPSK1 QPSK1 XXXX
S-CDMA Spreader ON OFF OFF XXXX XXXX ON ON XXXX
Codes Subfrm 4 6 6 XXXX XXXX 7 20 XXXX
Intlv Stp Sz 1 1 1 XXXX XXXX 1 1 XXXX
TCM Encoding OFF OFF OFF XXXX XXXX OFF OFF XXXX
Channel Type S-CDMA S-CDMA S-CDMA XXXX XXXX S-CDMA S-CDMA


No Post-Equalizatiom
Moderate FEC for short data, heavy FEC for long data
impulse noise and significant distortions such as micro-reflections or group delay. This profile would be
more commonly used on plants where the AWGN floor is higher.

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+


Minimal Post-Equalizatiom for short data, moderate Post-Equalizatiom for long data
Heavy FEC for all data bursts

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
Channel Type S-CDMA S-CDMA S-CDMA XXXX XXXX S-CDMA S-CDMA X


Minimal Post-Equalizatiom for short data, moderate Post-Equalizatiom for long data
Heavy FEC for all data bursts

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+

S-CDMA support of 64-QAM for Impulse Channel

64-QAM with minimal Post-Equalizatiom for short data, moderate Post-Equalizatiom for long data
Heavy FEC with Interleaving for all data bursts
10us Impulse @5.12Mcps


+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+
- Scrambler ON ON ON XXXX XXXX ON ON XXXX
- Codes Subfrm 3 6 6 XXXX XXXX 4 10 XXXX


10us Impulse @5.12Mcps

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+



+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+

S-CDMA 64-QAM Profile

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+

S-CDMA 16-QAM Profile

+--------------+------+------+------+------+------+------+------+------+
| | 1 | 3 | 4 | 5 | 6 | 9 | 10 | 11 |
+--------------+------+------+------+------+------+------+------+------+

B
Understanding and Modifying
Modulation Profiles
Introduction
This appendix describes TDMA, A-TDMA, MTDMA, and S-CDMA modulation
profile parameters and guidelines for modifying these parameters.

Note: For both TDMA and S-CDMA, Ingress cancellation performance is not
impacted by parameters set within the modulation profiles. Ingress
cancellation is enabled and configured through other parameters with the
CLI.
Compass ID: 362291231 Version 2 B-1

TDMA, A-TDMA and MTDMA

This section summarizes, in order of significance, key modulation profile parameters
and their impact on achieving an operating TDMA, A-TDMA, or MTDMA DOCSIS
modulation profile on the upstream channel.
Modulation (Modulation Type)

The most critical parameter in defining the Modulation Profile is the Modulation
Type. The Modulation Type is most impacted by the quality of the channel, namely
SNR (MER). The following table lists the SNR performance requirements for a
TDMA channel to support each modulation type. A good rule of thumb - if you can
not measure an SNR of at least a value as the SNR values listed in Table Table below,
you probably should not run the associated modulation type.
Table SNR Requirements for DOCSIS TDMA Modulation Types
Channel SNR Required (dB) Modulation Type
15 QPSK
18 8QAM
21 16QAM
24 32QAM
27 64QAM
30 128QAM
33 256QAM
Note: 128QAM and 256QAM are not a part of the DOCSIS 2.0 specification.
Howerver, the BSR and associated Motorola DOCSIS 2.0 cable modems do
support these modulations.
B-2 Compass ID: 362291231 Version 2

Release 5.3.1 Understanding and Modifying Modulation Profiles
FEC (FEC ERR CRC, FEC CW Len)

FEC is the primary parameter used to mitigate the effect of impulse type noise on an
upstream channel. Impulse noise is burst noise (i.e., noise that is present for several
bits of bytes in a data transmission and is gone for 10s of bytes or longer). Impulse
noise is very difficult to monitor without sophisticated test equipment as it requires
triggering off very short bursts of noise. Effects of impulse noise are minimal on an
SNR (MER) measurement. In order to mitigate impulse noise, additional FEC error
correction should be added. FEC error correction may be added by adjusting two
parameters, as shown in Table Table below.
Table FEC Modification to Mitigate Impulse Noise
Impulse Noise Protection Parameter Adjustment
Increased Impulse Protection Increase FEC Err CRC

Increased Impulse Protection Decrease FEC CW Len
Decreased Impulse Protection Decrease FEC Err CRC
Decreased Impulse Protection Increase FEC CW Len
Note: As stated above, FEC is really intended to mitigate impulse noise;

however, it can have a minimal impact on the SNR required to run a given
modulation type. FEC may provide up to 3 dB of improvement in the SNR
required to run a given modulation type although 1 to 2 dB is more generally
the case. This means that when running FEC, the SNR numbers shown in
Table Table above may be decreased by as much as 3 dB. For example,
QPSK operating with a modulation profile of heavy FEC might achieve
reasonable operation with an SNR as low as 12 dB. Increased impulse
protection results in greater data overhead (and lower through-put) on a
channel.

Preamble (Preamble Len)

The preamble allows the BSR to receive the cable modems upstream burst.
Generally, the preamble must be long enough to allow the BSR to detect and
demodulate the burst for a given channel SNR. The Preamble Len parameter is highly
correlated to the performance of the equalizer on an upstream DOCSIS channel and,
as a result, is the primary means of mitigating distortion effects on a DOCSIS
channel. Distortion effects include: micro-reflections, group delay and amplitude
roll-off and are unique to each cable modem. These distortion effects can be difficult
and time consuming to characterize on a plant as they will vary by frequency and
cable modem location; however, one general distortion characteristic can be
leveraged. DOCSIS channel frequencies near the band edge (42 MHz for US plants,
and 65 MHz for European plants) will experience greater amplitude roll-off and group
delay as a result of the diplex filters present in the plant amplifiers. The greater the
number of amplifiers separating the cable modem from the BSR, the greater the
amplitude roll-off and group delay encountered by the cable modem signal. Three
factors will impact the value that a user will want to set for the Preamble Len
parameter of the various IUC types:
1. Post-Equalization
2. Pre-Equalization
3. Mix of DOCSIS 1.0, 1.1, and 2.0 Cable Modems

Post-Equalization
Post-equalization is equalization performed only at the head-end (BSR), i.e., it does
not require any cable modem interaction and performs the same for DOCSIS 1.0, 1.1,
and 2.0 modems. Post-equalization can not be disabled by the user; however, the
performance of the post-equalization is related to the length of the preamble used
during a burst transmission. Thus, the user can increase the post-equalization
performance of the BSR by increasing the preamble length of each IUC burst type.
The key point here is that post-equalization is dependent upon the preamble length of
EACH IUC. For example, the BSR is better able to receive a Short Data (IUC 5) burst
if the preamble length of IUC 5 is increased, but this has no impact on the BSRs
ability to receive a Periodic Maintenance (IUC 4) or Long Data (IUC 6) burst or any
other IUC. Hence, to increase the distortion mitigation capabilities of the BSR using
post-equalization, the preamble length of each IUC must be increased.
Note: Increasing the preamble length also increases the overhead of the
channel and thus lowers the effective through-put of the channel. The BSR
utilizes a 24-Tap internal equalizer.
Pre-Equalization
Pre-equalization is equalization performed at the cable modem transmitter prior to
actually sending an upstream burst. Pre-equalization performs better than
post-equalization as it does not require the BSR to retrain for each new burst and
further allows finer adjustments to be made. Pre-equalization works as follows:
1. the BSR trains its internal equalizer based upon a given cable modem Init Maint
(IUC 3) or Periodic Maint (IUC 4) burst.
2. the BSR sends these equalizer coefficients to the cable modem which it will then
use for all bursts transmissions sent to the BSR.
3. the BSR continues to monitor the upstream bursts sent by the cable modem
during Station Maint (IUC 4), and if significant deviations in the coefficients are
detected, then an updated set of coefficients are sent to the cable modem.

Pre-equalization does not perform the same for DOCSIS 1.0, 1.1, and 2.0 cable
modems. In particular, DOCSIS 1.0 and 1.1 cable modems provide for only an 8-Tap
equalizer while DOCSIS 2.0 cable modems provide for a 24-Tap equalizer. (A 24-Tap
equalizer can mitigate a micro-reflection up to 3 times longer than that achieved with
an 8-Tap.) Further, earlier on in the DOCSIS certification process, equalization was
not well tested and as a result, a number of modems exist within the field that do not
implement equalization correctly. (Some of these modems were produced by vendors
who are no longer in business and therefore, software updates are not available.) As a
result when pre-equalization is enabled, operators may see performance by certain
classes of cable modems that is extremely poor and in some cases, these modems may
deregister.
In addition to the dependence on the type of cable modem (DOCSIS 1.0, 1.1, and 2.0),
the performance of pre-equalization is related to the length of the preamble used
during Init Maint (IUC 3) and Periodic Maint (IUC 4) bursts. The user can increase
the pre-equalization performance of the system by increasing the preamble length of
IUCs 4 and 5. Regardless of the preamble lengths, pre-equalization may be enabled
and disabled by the user which results in the termination of coefficient updates being
sent to the cable modem.
Mix of DOCSIS 1.0, 1.1, and 2.0 Cable Modems

The mix of DOCSIS 1.0, 1.1, and 2.0 cable modems present in combination with
whaevert distortions are present on the plant and what modulation type the user
configures will impact what values the user might choose for preamble lengths.
Table Table provides a set of guidelines for choosing preamble lengths for the various
IUCs depending upon cable modem mix within a cable plant.
Table Guidelines for Setting Preamble Length
Cable Modems Plant Distortion Preamble Length Selection Guidelines
Any None or Minimal Since minimal distortion is present on the channel, the
operator can utilize shorter preambles. Since minor
distortion has a greater impact on higher modulation
types, the user will want to utilize slightly longer
preambles for higher modulation types to allow the
BSRs post-equalizatoin to mitigate any minor impacts.
General values for the DATA IUCs would range from
68 for a QPSK burst to 96 for a 64QAM burst. IM and
SM IUCs would likely use slightly longer preambles.

Table Guidelines for Setting Preamble Length
Cable Modems Plant Distortion Preamble Length Selection Guidelines
1.0 & 1.1 Typical to Heavy Requires post-equalization which means preamble
length for each IUC burst type will be impacted.
General values would range as follows:
IUC Preamble Length
3 - Init Maint 640

4 - Per Maint 384
5 - Short Data 96-384
6 - Long Data 96-384
1.0, 1.1, & 2.0 Typical to Heavy Requires post-equalization for DOCSIS 1.0 and 1.1
cable modems which means preamble length for IUCs
5 and 6 will be impacted. Conversly, DOCSIS 2.0 cable
modems may use pre-equalization (as obtained by the
BSR using IUC 3 and 4) or post-equalization. General
values would range as follows:
IUC Preamble Length
3 - Init Maint 640

4 - Per Maint 384
5 - Short Data 96-384
6 - Long Data 96-384
9 - Adv Short Pre- 68-96
Post- 96-384
10 - Adv Long Pre- 68-96
Post- 96-384
2.0 Typical to Heavy DOCSIS 2.0 cable modems may use pre-equalization
(as obtained by the BSR using IUC 3 and 4) or
post-equalization. General values would range as
follows:
IUC Preamble Length
3 - Init Maint 640

4 - Per Maint 384
9 - Adv Short Pre- 68-96
Post- 96-384
10 - Adv Long Pre- 68-96
Post- 96-384

Interleaving (Intlv Depth)

IUC 9 and 10 on A-TDMA and MTDMA channels only. The Intlv Depth parameter
heightens the performance of the FEC by supporting the correction of longer impulse
noise. This parameter is only supported by DOCSIS 2.0 modems operating in TDMA
mode (i.e., IUCs 9 and 10). Increasing the Intlv Depth parameter will increase the
FEC correction capability to handle longer impulse noise. Similarly decreasing this
value will decrease the correction capability.
Note: An Interleaving Depth value of 1 means interleaving is disabled and an

Interleaving Depth value of 0 means dynamic interleaving is enabled.
Dynamic interleaving utilizes the Intlv Blk Sz parameter to bound the
interleaving block sizes rather than the Intlv Depth parameter.
S-CDMA
This section summarizes, in order of significance, key modulation profile parameters
and their impact on achieving an operating S-CDMA DOCSIS modulation profile on
the upstream channel.
Modulation (Modulation Type)

The most critical parameter in defining the Modulation Profile is the Modulation
Type. This is because the Modulation Type is most impacted by the quality of the
channel, namely SNR. The following table lists the SNR performance requirements
for a channel to support each modulation type on a S-CDMA channel. A good rule of
thumb, if you cant measure an SNR (MER) of at least that listed in Table Table
below, you probably shouldnt run the associated modulation type.

Table SNR Requirements for a DOCSIS S-CDMA Modulation Type
15 QPSK
18 8QAM
21 16QAM
24 32QAM
27 64QAM
30 128QAM
33 256QAM
Table Table only summarizes SNR performance assuming that all S-CDMA codes
are active. If a reduced set of codes are active, then a coding gain is achieved and the
Channel SNR required will be reduced. The amount by which the SNR can be
reduced may be calculated as:
SNR improvement = 10*log10(128/(# active codes))
Therefore, if only 64 codes are active, then an SNR improvement of 3 dB is realized
and Table Table may be rewritten with the values displayed in Table Table

Table SNR Requirements for a DOCSIS S-CDMA Modulation Type with 64 Active Codes
12 QPSK
15 8QAM
18 16QAM
21 32QAM
24 64QAM
27 128QAM
30 256QAM
Note: DOCSIS 2.0 requires Trellis Coded Modulation (TCM) in 128QAM

mode.
256QAM is not a part of the DOCSIS 2.0 specification. However, the Motorola
BSR and associated Motorola 2.0 cable modems do support this modulation.
By reducing the number of active codes from 128 to 64, you are actually reducing the
effective throughput of the channel by . The same effect is achieved in a TDMA
channel by reducing the Modulation Type and at the same expense, a reduction of 3
dB in the required SNR. The net effect is that S-CDMA and TDMA perform roughly
the same when comparing through-put with channel-width and SNR. This is no real
surprise as Shannons limit applies to both S-CDMA and TDMA channels.
FEC (FEC ERR CRC, FEC CW Len)

The relationship provided in the TDMA section also applies to S-CDMA.
Preamble (Preamble Len)

The relationship provided in the TDMA section also applies to S-CDMA.
Interleaving (Intlv Stp Sz)

IUC 9 and 10 on S-CDMA Channels only - TBD.

Index
Numbers
parameters, 7-9
911 Emergency Calls, 9-10
Bridge Mode TLV, 16-7, 16-10
A
C
Accounting Request message, 14-11
cable bundling, 1-24
Accounting-Response message, 14-11
cable headend path loss, 5-4
adding a sub-interface, 17-2
cable modem (CM), 14-2
Address Resolution Protocol (ARP), 1-18
Cable Modem Termination System (CMTS), 14-2
admission control, 9-3
cable network security, 1-16
AK
BPI, 7-9 Cable Spectrum Group, 11-3
grace-time, 7-9 Call Content Connection (CCC), 14-3
permanent, 7-9 Call Data Content (CDC), 14-3
temporary, 7-9
Call Management Server (CMS)
Application Manager (AM) description, 14-2
description, 14-2
channel list
applying configuring for DSG, 15-5
a modulation profile, 5-21
channel type
ARP configuring, 6-11
see host authorization, 1-12
Channel-IDs, 1-47
Authorization Key
classifier
setting, 7-9
configuring for DSG, 15-6
B clearing
dcc statistics, 13-22
Baseline Privacy ucc statistics, 13-22
configuring, 7-9 Client
BGP/MPLS VPNs, 14-6 description, 14-2
billing, settlements, 14-2 Client-Accept message, 14-8
BPI CM authentication information
configuring, 7-9 obtaining, 7-6
Compass ID: 362291231 Version 2 Index-1

CM information clearing, 13-22

displaying, 7-26 displaying, 13-22
timing adjustments, 7-32 DCD messages
Common Open Policy Service (COPS), 14-6 for DSG, 15-12
description, 14-2 default power-level
Communications Assistance for Law Enforcement Act range, 5-5
(CALEA), 14-3, 14-23 default synchronization message interval
configuration mode resettingl, 7-4, 7-5
DSG, 15-4 deleted service flow log
Configured Active Percent (CAP), 9-2 displaying, 10-10
configuring deleting
a DOCSIS 2.0 upstream logical channel, 6-18 a modulation profile, 5-24
a DSG client, 15-8 an IUC from a modulation profile, 5-24
a DSG downstream channel, 15-11 service flow, 10-9
a DSG tunnel, 15-10 deleting a QoS profile, 10-4
a DSG tunnel group, 15-11
deleting a sub-interface, 17-2
a load balancing policy, 13-12
a load balancing rule, 13-9 DES, 7-9
a restricted load balancing group, 13-13 determining
additional S-CDMA logical channel parameters, number of dropped packets, 5-7
6-14 determining the 2:8 CMTS module type, 6-9
an SNR offset, 7-12
automatically repeated SNR tests, 7-8 determining the DOCSIS version of a slot, 6-10
Baseline Privacy, 7-9 DHCP lease query, 1-16
dynamic load balancing, 13-8 DHCP relay information option, 1-2
modulation interface profile, 5-15
disabling
SNR measurement, 7-6
downstream port, 2-7
the BSR for DOCSIS 1.0+ interoperability, 10-16
power adjustment, 5-27
Configuring Spectrum Management, 11-1
disabling dynamic load balancing on CMTS modules
configuring spectrum power density maintenance for a through SNMP, 13-17
logical channel, 6-14 through the CLI, 13-17
configuring the channel type, 6-11 displaying
controlling configured modulation profiles, 5-11
upstream input power level, 5-4 dcc statistics, 13-22
copying deleted service flow log, 10-10
a modulation profile, 5-22 DSA message
statistics, 10-7
creating or modifying a QoS profile, 10-2 DSC message
Customer Premises Equipment (CPE), 14-2 statistics, 10-9
DSD message statistics, 10-10
D DSG information, 15-15
FFT power level measurement data, 7-4
Data Encryption Standard, 7-9 load balancing information, 13-18
dcc statistics service flow
Index-2 Compass ID: 362291231 Version 2

Release 5.3.1 Index
packet classifiers, 10-11 DSD message statistics

QoS information, 10-12 displaying, 10-10
service flow SID information, 10-12 DSG
service flow statistics, 10-9 associating channel lists to a downstream channel,
SFID, 10-9 15-14
SNR measurement data, 7-10 associating timers to a downstream channel, 15-14
the FFT processor configuration, 7-3 associating tunnel groups to a downstream channel,
the SNR configuration, 7-9 15-12
ucc statistics, 13-22 associating vendor parameters to a downstream
displaying CM information, 7-26 channel, 15-14
displaying the upstream logical channel configuration, configuration tasks, 15-4
6-17 configuring a channel list, 15-5
configuring a classifier, 15-6
DOCSIS 1.0+ interoperability
configuring a timer, 15-7
configuring, 10-16
configuring a vendor parameter, 15-8
DOCSIS 2.0 DCD messages, 15-12
and the BSR 64000, 6-4 displaying information for, 15-15
BSR 64000 hardware support for, 6-5 entering configuration mode, 15-4
BSR 64000 software support for, 6-6 initial confgurations, 15-5
capabilities, 6-1 specifying tunnel parameters, 15-10
channels types, 6-2
DSG client
configuring upstream logical channels, 6-18
configuring, 15-8
logical channel configuration task summary, 6-7
logical channels, 6-2 DSG downstream channel
configuring, 15-11
downstream data
encrypting, 7-9 DSG tunnel
configuring, 15-10
downstream data transmission rate-limit
enabling, 2-3 DSG tunnel group
configuring, 15-11
downstream port
disabling, 2-7 dynamic load balancing
configuring, 13-8
downstream power level
disabling, 13-17
setting, 2-6
enabling, 13-17
downstream rate-limiting status load balancing groups, 13-8
verifying, 2-3
Dynamic Load Balancing (DLB), 1-47
DSA, 10-1
Dynamic Quality of Service (DQoS), 14-25
DSA message
Dynamic Service Addition, 10-1
statistics
displaying, 10-7 Dynamic Service Change, 10-1
DSC, 10-1 Dynamic Service Deletion, 10-1
DSC message
statistics
E
displaying, 10-9 ECN OSSIv2-05.0215, 18-1
DSD, 10-1 Electronic Surveillance, 14-23

Element ID, 14-9 H

embedded Multimedia Terminal Adapters (eMTAs),
host authorization
18-1
dynamic, 1-12
embedded Set-top Boxes (eSTBs), 18-1 static, 1-12
enabling verifying, 1-15
downstream data transmission rate-limit, 2-3
power adjustment, 5-26 I
rate-limiting function, 2-3
upstream data transmission rate-limit, 5-7 IEEE 8021q VLAN ID
enabling dynamic load balancing on CMTS modules associating with a sub-interface, 17-3
through SNMP, 13-17 individual CM grace-time TEK
through the CLI, 13-17 setting, 7-11
encrypting initial configurations
downstream data, 7-9 for DSG, 15-5
upstream data, 7-9 initiating
encryption, 7-9 DSD
Event Message (EM) System, 14-2 of SFID, 10-9
input power-level range, 5-5
F insertion interval
setting, 7-3
FFT
interleave depth
power level measurement, 7-2
setting, 2-6
power level measurement data, 7-4
retrieving data from a file system, 7-5 Internet Key Exchange (IKE), 14-19
retrieving data from an operational CMTS module, Internet Protocol Security (IPSec), 14-15
7-5 IP Security (IPSec)
FFT power level measurement description, 14-3
starting, 7-3
IUC
FFT processor deleting from a modulation profile, 5-24
displaying the configuration of, 7-3
flap lists, 7-15 K
troubleshooting, 7-18
KEK
forcing
setting, 7-9
packet fragmentation, 5-33
Key Encryption Key, 7-9
fraud detection, 14-2
frequency band, 11-4 L
G Law Enforcement Agency (LEA), 14-3
life-time, 7-9
gaming console, 14-2
load balancing group
Gate ID, 14-26
assigning downstream and upstream channels to,
grace-time, 7-9 13-16

Release 5.3.1 Index
enabling/disabling dynamic load balancing for, with UCC, 13-20

13-18 Multimedia Terminal Adapter (MTA)
load balancing groups, 13-8 description, 14-2
load balancing information
displaying, 13-18 N
load balancing policy network
configuring, 13-12 cable network security, 1-16
load balancing rule network usage, 14-2
configuring, 13-9
number of dropped packets
Loopback interface, 14-6 determining, 5-7
M O
MAC management messages, 10-1 obtaining
manually moving a cable modem, 13-20 CM authentication information, 7-6
Maximum Assigned Bandwidth (MAB), 9-1 OSSI V 2.0-N-04.0201-3, 1-47
maximum CPE host number output power level, 5-4
specifying, 7-7, 7-8
verifying, 7-8, 7-29 P
Media Gateway (MG)
Gateway description, 14-2 packet fragmentation
forcing, 5-33
Media Gateway Controller (MGC)
Gateway description, 14-3 PacketCable
description, 14-1
Media Server (MS)
description, 14-2 PacketCable Multimedia
description, 14-1
modualtion profile configuration
restoring default, 5-23 PacketCable Telecommunications Service Provider
(PC/TSP), 14-3
modulation
interface profile parameters
configuring, 5-15 BPI, 7-9
modulation profile payload header suppression entries, 10-13
applied to an upstream port, 5-12 PC, 14-2
applying, 5-21 permanent AK, 7-9
configuration mode, 5-14
permanent TEK, 7-10
configuring though an IUC submode, 5-19
copying, 5-22 PHS entries
deleting, 5-24 displaying, 10-13
displaying, 5-11 ping docsis, 7-24
numbering scheme, 5-11 Policy Decision Point (PDP), 14-2
modulation profiles, 5-9 Policy Enforcement Point (PEP), 14-7
moving a cable modem manually, 13-20 Policy Server (PS)
with DCC, 13-21 description, 14-2

power adjustment RF Sentry

disabling, 5-27 using on the 2:8 CMTS resource module, 7-1
enabling, 5-26 using to measure SNR, 7-6
pre-defined modulation profiles, A-1 RFI V 2.0-R-04.0200-1, 1-47
prerequisites
for configuring DSG, 15-3 S
Pre-shared Key, 14-15 S-CDMA active codes, 6-15
Public Switched Telephone Network (PSTN), 14-2 S-CDMA codes per minislot, 6-16
S-CDMA hopping seed, 6-16
Q
S-CDMA logical channels
QoS profile configuring, 6-14
creating, 10-2 S-CDMA spreading interval, 6-16
deleting, 10-4
scheduling, 9-2
modifying, 10-2
viewing, 10-5 scheduling priority, 9-2
Quality of Service (QoS), 9-1, 14-1 Security Policy Database (SPD), 14-15
MAB, 9-1 to 9-2 Service, 9-1
setting, 10-1 to 10-11 service class
default, 9-5
R
service classes, 9-1
rate-limiting function service flow
enabling, 2-3 changing, 10-8
Record Keeping Server (RKS), 14-2 deleting, 10-9
packet classifiers
resetting
displaying, 10-11
default synchronization message interval, 7-4, 7-5
SID information
upstream channel width default, 5-26
displaying, 10-12
upstream minislot size, 5-26
statistics
upstream range-backoff default, 5-29
displaying, 10-12
restoring
service flow QoS information
default modulation profile configuration, 5-23
displaying, 10-12
restricted load balancing group
service flow statistics
configuring, 13-13
displaying, 10-9
retreiving FFT data
setting
from an operational CMTS module, 7-5
Authorization Key, 7-9
retrieving FFT data downstream modulation rate, 2-2
from a file system, 7-5 downstream power level, 2-6
retrieving SNR data individual CM grace-time TEK, 7-11
from a file system, 7-11 insertion interval, 7-3
from an operational CMTS module, 7-11 interleave depth, 2-6
RF output upstream frequency, 5-4, 19-21 KEK, 7-9
setting, 5-4, 19-21 RF output upstream frequency, 5-4, 19-21

Release 5.3.1 Index
synchronization message interval, 7-4 sub-interfaces

TEK, 7-9 adding, 17-2
UCD message transmission interval, 5-34 associating with an IEEE 802.1q VLAN ID, 17-3
upstream channel width, 5-26 deleting, 17-2
upstream data-backoff, 5-27 synchronization message interval
upstream frequency, 5-4 setting, 7-4
upstream minislot size, 5-25 verifying, 7-4
upstream range-backoff, 5-28
SFID T
displaying, 9-27, 10-8, 10-9
SFID DSD TCP, 14-7
initiating, 10-9 TEK
signal to noise measurement, 7-6 grace-time, 7-10
life-time, 7-10
Signaling Gateway (SG) permanent, 7-10
Gateway description, 14-2 setting, 7-9
SNR configuration temporary AK, 7-9
displaying, 7-9
temporary traffic key, 7-10
SNR data
retrieving from a file system, 7-11 timer
retrieving from an operational CMTS module, 7-11 configuring for DSG, 15-7
traffic key
SNR measurement
configuring, 7-6 temporary, 7-10
starting, 7-9 trunk, 16-1
SNR measurement data tunnel parameters
displaying, 7-10 specifying for DSG, 15-10
storing, 7-10
SNR measurements, 7-6 U
SNR offset ucc statistics
configuring, 7-12 clearing, 13-22
SNR test displaying, 13-22
configuring automatically repeated, 7-8 UCD message transmission interval
specifying setting, 5-34
maximum CPE host number, 7-7, 7-8 upstream, 5-30
spectrum data collection, 11-9 upstream cable interface port, 5-8, 5-33
spectrum power density maintenance upstream channel bandwidth, 5-5
configuring for a logical channel, 6-14
upstream channel width
starting setting, 5-26
the FFT power level measurement, 7-3
upstream channel width default
starting SNR measurement, 7-9 resetting, 5-26
storing FFT power level measurement data, 7-4 upstream data
storing SNR measurement data, 7-10 encrypting, 7-9

upstream data transmission rate-limit

enabling, 5-7
upstream data-backoff
setting, 5-27
upstream input power level
controlling, 5-4
upstream logical channel configuration
displaying, 6-17
upstream minislot size
resetting, 5-26
setting, 5-25
upstream propagation delay, 5-30
upstream range-backoff
setting, 5-28
upstream range-backoff default
resetting, 5-29
V
vendor parameter
configuring for DSG, 15-8
verifying
downstream rate-limiting status, 2-3
host authorization, 1-15
maximum CPE host number, 7-8, 7-29
synchronization message interval, 7-4
viewing
QoS profiles, 10-5
VLAN Tagging, 16-1
Voice over IP (VoIP), 14-2

Visit our website at:
www.motorola.com

9/10
MGBI

BSR64K-R5 3 1-CMTSGuide

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

BSR64K-R5 3 1-CMTSGuide

Caricato da

Copyright:

Formati disponibili

BSR 64000 CMTS

Compass ID: 362291231 Version 2

Compass ID: 362291231 Version 2

1 Configuring the Cable Interface

Compass ID: 362291231 Version 2 iii

Setting ARP Parameters ............................................................................................................1-18

iv Compass ID: 362291231 Version 2

2 Configuring a Downstream Channel

3 DOCSIS 3.0 Features

Compass ID: 362291231 Version 2 v

Service Flow Attribute Based Downstream Assignment............................................................3-7

4 Configuring Downstream Channel Bonding

5 Configuring an Upstream Channel

vi Compass ID: 362291231 Version 2

Managing the Upstream Channel..............................................................................................5-24

6 Configuring a DOCSIS 2.0 Upstream Logical Channel

Compass ID: 362291231 Version 2 vii

Configuring S-CDMA Codes Per Minislot ....................................................................6-16

7 Using RF Sentry on the 2:8 CMTS Resource Module

7 Managing Cable Modems

viii Compass ID: 362291231 Version 2

Setting Cable Modem Authentication Parameters ...........................................................7-5

9 Configuring Service Classes

Compass ID: 362291231 Version 2 ix

Downstream Flow Classifier Support ..............................................................................9-3

10 Setting QoS Parameters

x Compass ID: 362291231 Version 2

Initiating a DSA ........................................................................................................................10-6

11 Configuring Spectrum Management

Compass ID: 362291231 Version 2 xi

Displaying Spectrum Data............................................................................................11-20

12 Configuring Advanced Spectrum Management

xii Compass ID: 362291231 Version 2

Excluding Reference Cable Modems......................................................................................12-22

13 Configuring Load Balancing

Compass ID: 362291231 Version 2 xiii

xiv Compass ID: 362291231 Version 2

Displaying Gates ............................................................................................14-27

Compass ID: 362291231 Version 2 xv

16 Configuring VLAN Tagging

17 Configuring Tagged Sub-Interfaces

xvi Compass ID: 362291231 Version 2

Configuring the Upper Level Protocol.............................................................18-3

19 Configuring a Distributed MAC Domain

Compass ID: 362291231 Version 2 xvii

Binding the Downstream Channels................................................................19-12

20 Cable Traffic Management

xviii Compass ID: 362291231 Version 2

Traffic Enforcement Algorithms......................................................................20-7

A Pre-Defined Modulation Profiles

B Understanding and Modifying Modulation Profiles

Compass ID: 362291231 Version 2 xix

xx Compass ID: 362291231 Version 2

Compass ID: 362291231 Version 2 xxi

BSR 64000 Quick Start Guide

ixxii Compass ID: 362291231 Version 2

Compass ID: 362291231 Version 2 ixxiii

BSR 64000 Command Reference Guide

ixxiv Compass ID: 362291231 Version 2

BSR 64000 Release Notes

Convention Example Explanation

Compass ID: 362291231 Version 2 ixxv

Convention Example Explanation