CMTS Software Config Guide 11-14-11 Release 6.1.1

CMTS Software Configuration Guide
Version: November 15, 2011

(For Casa Software Releases 5.2, 5.4.19, 5.4.21, 6.0.3, and 6.1.1)
Casa Systems, Inc.
100 Old River Road
Andover, MA 01810
Phone: 978-688-6706
Fax: 978-688-6584
info@casa-systems.com
www.casa-systems.com
CASA CMTS
Copyright 2011 Casa Systems, Inc. All rights reserved. Licensed software products are
owned by Casa Systems or its suppliers and are protected by United States copyright laws and
international treaty provisions.
The information regarding the product in this guide is subject to change without notice. All
statements, information, and recommendations in this guide are believed to be accurate but are
presented without warranty of any kind, express of implied. Users must take full responsibility for
their application of the product.
In no event shall Casa or its suppliers be liable for any indirect, special, consequential, or
incidental damages, including, without limitation, lost profits or loss or damage to data arising out
of the use or inability to use this guide, even if Casa or its suppliers have been advised of the
possibility of such damages.
Casa CMTS Software Configuration Guide
CASA CMTS
Table of Contents
VERSION: NOVEMBER 15, 2011 ........................................................................................................................ 1
(FOR CASA SOFTWARE RELEASES 5.2, 5.4.19, 5.4.21, 6.0.3, AND 6.1.1) ............................................................... 1
TABLE OF CONTENTS ............................................................................................................................. 3
PREFACE.............................................................................................................................................. 27
PURPOSE OF THE GUIDE .................................................................................................................................. 27
AUDIENCE .................................................................................................................................................... 27
REVISION INFORMATION ................................................................................................................................. 27
CONTENT ..................................................................................................................................................... 32
NOTATION CONVENTIONS ............................................................................................................................... 33
1 CASA CMTS CONFIGURATION OVERVIEW.......................................................................................... 34
SLOT AND PORT NUMBERING ........................................................................................................................... 34
C2200 slot and port numbering ............................................................................................................ 34
C3200 slot and port numbering ............................................................................................................ 36
C10200 and C10G slot and port numbering ......................................................................................... 36
C10G REDUNDANCY OPERATIONS..................................................................................................................... 37
Slot information and cabling on the network side ................................................................................ 37
Slot information on the RF I/O side....................................................................................................... 37
High availability (HA) redundancy commands...................................................................................... 38
Fan, power, and temperature status on the C10G ............................................................................... 41
C10G 8-channel QAM frequency configurations .................................................................................. 42
C10G router redundancy....................................................................................................................... 43
COMPLETING PRE-CONFIGURATION ................................................................................................................... 44
USING THE COMMAND LINE INTERFACE .............................................................................................................. 44
STARTING THE SYSTEM CONFIGURATION ............................................................................................................. 45
Connecting the console ......................................................................................................................... 45
Resetting the console............................................................................................................................ 45
Starting the system ............................................................................................................................... 46
Viewing the loaded software version ................................................................................................... 46
Viewing the system hardware configuration ........................................................................................ 47
Viewing the system running configuration ........................................................................................... 47
Entering and exiting configuration mode ............................................................................................. 47
CASA CMTS
Configuring CMTS device contact and location strings......................................................................... 48
Setting security access to the system console ...................................................................................... 48
Saving the current configuration .......................................................................................................... 49
Resetting the IP address ....................................................................................................................... 50
Restoring factory defaults .................................................................................................................... 50
SAMPLE CONFIGURATION FILES ......................................................................................................................... 51
Basic configuration ............................................................................................................................... 51
General configuration ........................................................................................................................... 52
2 CONFIGURING AND MANAGING THE CMTS FROM THE CLI ................................................................ 55
MANAGING THE SYSTEM ................................................................................................................................. 56
Entering privileged mode ...................................................................................................................... 57
Exiting privileged mode ........................................................................................................................ 57
Changing the privileged mode password ............................................................................................. 58
Resetting the privileged mode password to the default setting ........................................................... 58
Encrypting passwords ........................................................................................................................... 58
Changing the prompt for privileged mode ........................................................................................... 59
Setting up a command alias ................................................................................................................. 59
Showing the configured command alias............................................................................................... 60
MANAGING CONFIGURATIONS AND FILES............................................................................................................ 60
Saving a running configuration to the startup configuration ............................................................... 60
Copying the startup configuration to a file........................................................................................... 61
Restoring a startup configuration from a file in NVRAM ...................................................................... 61
Restoring the startup configuration to the running configuration ....................................................... 61
Copying the running configuration to an external location .................................................................. 62
Copying files over FTP/TFTP.................................................................................................................. 63
Copying files from fdsk2 to destinations over FTP/TFTP ....................................................................... 65
Displaying fdsk2 directory contents ...................................................................................................... 66
Displaying the running configuration ................................................................................................... 66
Displaying the system startup configuration ........................................................................................ 66
Displaying configuration settings within the current context............................................................... 66
MANAGING NVRAM FILES ............................................................................................................................. 67
Listing files in the directory ................................................................................................................... 67
Removing a file from the directory ....................................................................................................... 67
Copying a file to a remote host............................................................................................................. 68
UPDATING CASA CMTS SOFTWARE .................................................................................................................. 68
CASA CMTS
USER MANAGEMENT AND SECURITY CONTROL ..................................................................................................... 68
SSH support (Release 5.4 and later)...................................................................................................... 70
Enabling and disabling SSH................................................................................................................... 72
Adding Telnet and SSH users ................................................................................................................ 72
Displaying Telnet and SSH users ........................................................................................................... 73
Changing Telnet and SSH user passwords ............................................................................................ 73
Removing Telnet or SSH users .............................................................................................................. 74
Removing a logged-in user ................................................................................................................... 74
Configuring and displaying the Telnet port .......................................................................................... 75
Setting the maximum number of concurrent Telnet session ................................................................ 75
Configuring Telnet and SSH timeout periods ........................................................................................ 75
Rebooting the system ........................................................................................................................... 76
Enabling a save configuration reminder at reboot............................................................................ 77
Rebooting a downstream/upstream module ....................................................................................... 78
Displaying the system boot device........................................................................................................ 78
Displaying the system hardware version .............................................................................................. 79
Displaying the system software version ............................................................................................... 79
Setting and displaying the system clock ............................................................................................... 80
Setting and displaying the time zone.................................................................................................... 80
Synchronizing the system clock with an NTP server ............................................................................. 81
Configuring system rate limiting (Rel. 6.0) ........................................................................................... 82
Configuring an NTP loopback interface ................................................................................................ 82
Adding and removing IPv4 network route entries ................................................................................ 83
Adding and removing IPv4 host table entries ....................................................................................... 83
Adding and removing IPv6 network route entries ................................................................................ 84
Displaying the IPv4 and IPv6 routing tables ......................................................................................... 84
Displaying alarm states ........................................................................................................................ 85
Displaying system logs .......................................................................................................................... 85
Configuring a log message source IP address....................................................................................... 86
Configuring lawful intercept ................................................................................................................. 86
Displaying Rapid Spanning Tree Protocol status .................................................................................. 87
Displaying ARP entries .......................................................................................................................... 87
Configuring the ARP request interval ................................................................................................... 88
Configuring ARP packet filtering........................................................................................................... 88
Clearing an entry in the ARP cache ....................................................................................................... 89
CASA CMTS
Displaying the ARP request interval ..................................................................................................... 90
Enabling and disabling the ARP timeout reset ..................................................................................... 90
Displaying IPv6 information.................................................................................................................. 90
Displaying the ARP timeout reset configuration................................................................................... 91
Displaying CPU usage ........................................................................................................................... 91
Displaying memory usage..................................................................................................................... 93
Monitoring line card status .................................................................................................................. 94
Monitoring Gigabit Ethernet interfaces................................................................................................ 94
Displaying the current monitor settings (Rel. 6.0 and later)................................................................. 94
Enabling auto-reboot mode (5.2) ......................................................................................................... 95
Using the Ping and Ping6 commands ................................................................................................... 95
Testing connectivity with extended Ping .............................................................................................. 96
Using the traceroute command (Rel. 6.0)............................................................................................. 96
Configuring ICMP packet filtering....................................................................................................... 100
Configuring DHCP packet filtering ...................................................................................................... 100
Displaying all filtering settings in the running configuration ............................................................. 101
Setting channel utilization intervals ................................................................................................... 101
Displaying channel utilization ............................................................................................................. 101
Displaying upstream channel utilization............................................................................................. 103
Displaying downstream channel utilization........................................................................................ 104
Configuring the system monitor (Release 5.4 and later) .................................................................... 105
CONFIGURING THE MANAGEMENT PORT........................................................................................................... 106
Setting the Fast Ethernet port as the management port.................................................................... 106
Obtaining the IP address of the Fast Ethernet port from the DHCP server ......................................... 107
Configuring an IP access group on eth0 (C3200 and C10200 only) .................................................... 108
CONFIGURING GIGABIT ETHERNET (GIGE) PORTS............................................................................................... 108
Enabling/disabling auto-negotiation mode on a Gigabit Ethernet port ............................................. 109
Assigning or removing a Gigabit Ethernet port IP address ................................................................. 110
Assigning an IP access group to a Gigabit Ethernet port .................................................................... 111
Assigning an IPv6 address to a Gigabit Ethernet port ........................................................................ 111
Assigning a Gigabit Ethernet port to a VLAN ...................................................................................... 112
Enabling/disabling the IGMP client service on a Gigabit Ethernet port ............................................. 113
Configuring the MTU size on a Gigabit Ethernet interface (5.4)......................................................... 114
Displaying the Gigabit Ethernet interface configuration .................................................................... 114
Displaying the 10Gigabit Ethernet interface configuration ................................................................ 116
CASA CMTS
Displaying the Gigabit Ethernet interface statistics ........................................................................... 116
CONFIGURING LOOPBACK INTERFACES.............................................................................................................. 118
Enabling interface loopback mode ..................................................................................................... 118
Configuring an IPv6 address on a loopback interface ........................................................................ 118
Configuring an IPv4 address on a loopback interface ........................................................................ 119
Assigning an access group to a loopback interface ............................................................................ 120
Configuring a log message source IP address..................................................................................... 120
Configuring a loopback interface as source IP address on FTP/TFTP packets ................................... 120
Setting the source IP address of lawful intercept packets to the loopback IP interface ..................... 121
CONFIGURING TRUNK INTERFACES................................................................................................................... 121
Creating a trunk interface................................................................................................................... 122
Assigning an IP address to a trunk interface ...................................................................................... 122
Enabling/disabling a trunk interface .................................................................................................. 123
Adding a GigE port to a trunk interface .............................................................................................. 123
Enabling IGMP client services on a trunk interface ............................................................................ 124
Applying an IP access group to a trunk interface ............................................................................... 124
Displaying a trunk interface configuration ......................................................................................... 125
Displaying ARP entries from a trunk interface.................................................................................... 126
CONFIGURING LINK AGGREGATION CONTROL PROTOCOL (LACP) (5.4) ................................................................. 127
Enabling the LACP global configuration ............................................................................................. 127
Setting LACP port priority (5.4) ........................................................................................................... 128
Setting the LACP system port priority (5.4) ......................................................................................... 128
Displaying LACP group information .................................................................................................... 129
Configuring and displaying LACP port priority on GigE interfaces ...................................................... 129
Configuring and displaying LACP trunk interfaces .............................................................................. 131
Displaying the LACP system ID............................................................................................................ 132
CONFIGURING IS-IS ROUTING PROTOCOL (5.4 ONLY) ........................................................................................ 132
Configuring IPv4 IS-IS under a GigE Port............................................................................................. 132
Configuring IPv6 IS-IS under a GigE port............................................................................................. 132
Configuring an IS-IS circuit type on a GigE interface .......................................................................... 133
Configuring IS-IS point-to-point links .................................................................................................. 134
Configuring the complete sequence number PDU (CSNP) interval ..................................................... 134
Configuring the IS-IS Hello interval ..................................................................................................... 135
Configuring the IS-IS Multiplier for Hello holding time ....................................................................... 136
Enabling padding on IS-IS Hello packets ............................................................................................. 136
CASA CMTS
Configuring the IS-IS default metric .................................................................................................... 137
Configuring the authentication password for a GigE interface .......................................................... 138
Configuring the IS-IS priority ............................................................................................................... 138
Configuring the IS-IS retransmit-interval ............................................................................................ 139
Configuring IS-IS router area tag ........................................................................................................ 140
Displaying the IS-IS command list ....................................................................................................... 140
Specifying the IS-IS IPv6 address family paramters ............................................................................ 141
Configuring the IS-IS router area authentication password ............................................................... 143
Configuring the IS-IS router authentication key chain ........................................................................ 144
Configuring the IS-IS router authentication mode .............................................................................. 144
Configuring the IS-IS router authentication send-only option ............................................................ 145
Configuring the IS-IS router default route distribution ....................................................................... 146
Configuring the IS-IS router domain authentication password .......................................................... 146
Configuring the IS area types.............................................................................................................. 147
Configuring the IS-IS LSP generation interval ..................................................................................... 148
Configuring the IS-IS LSP lifetime ........................................................................................................ 148
Configuring the IS-IS route redistribution metric style........................................................................ 149
Configuring the network entity title (NET).......................................................................................... 149
Enabling the IS-IS dynamic hostname capability ................................................................................ 150
Configuring IS-IS passive interfaces .................................................................................................... 150
Configuring IS-IS to redistribute route advertisements from other protocols .................................... 151
Setting the IS-IS overload bit............................................................................................................... 152
Setting the IS-IS shortest path first (SPF) calculations ........................................................................ 153
Setting the IPv4 summary address prefix ........................................................................................... 154
Displaying the IS-IS area configuration............................................................................................... 155
Displaying the IS-IS counter statistics ................................................................................................. 156
Displaying the IS-IS link state database .............................................................................................. 156
Displaying the IS-IS interface statistics ............................................................................................... 157
Displaying the IS-IS neighbor routers.................................................................................................. 158
Displaying the IS-IS topology information .......................................................................................... 159
Displaying the IPv4 and IPv6 IS-IS routing table ................................................................................. 159
CONFIGURING PROTOCOL INDEPENDENT MULTICAST IN SPARSE MODE ................................................................. 159
Enabling PIM-SM on a GigE or loopback interface ............................................................................. 160
Displaying the current PIM-SM interface and neighbor configurations ............................................. 161
Configuring rendezvous point addresses ............................................................................................ 161
CASA CMTS
Configuring the rendezvous point candidate ...................................................................................... 162
Configuring the bootstrap router candidate....................................................................................... 164
Setting the Shortest Path Tree threshold ............................................................................................ 165
Configuring source-specific multicast ................................................................................................. 165
CONFIGURING THE OSPF ROUTING PROTOCOL ................................................................................................. 166
Entering OSPF configuration mode..................................................................................................... 167
Exiting OSPF configuration mode ....................................................................................................... 167
Enabling OSPF area authentication .................................................................................................... 167
Configuring the OSPF area default cost .............................................................................................. 168
Configuring the OSPF area filter list.................................................................................................... 169
Configuring the OSPF area export list ................................................................................................. 170
Configuring the OSPF area import list ................................................................................................ 170
Configuring the OSPF area NSSA ........................................................................................................ 171
Configuring the OSPF area range ....................................................................................................... 172
Configuring the OSPF area shortcut ................................................................................................... 173
Configuring the OSPF area stub .......................................................................................................... 173
Configuring the OSPF area virtual link ................................................................................................ 174
Configuring the OSPF interface auto cost ........................................................................................... 176
Configuring OSPF-compatible RFC1583 .............................................................................................. 176
Configuring OSPF control-distribution default information ................................................................ 177
Configuring the OSPF default metric .................................................................................................. 178
Configuring the OSPF administrative distance ................................................................................... 178
Displaying the OSPF command list ..................................................................................................... 179
Configuring the OSPF neighbor router ................................................................................................ 180
Configuring OSPF routing on an IP network ....................................................................................... 181
Configuring the OSPF ABR type .......................................................................................................... 181
Configuring the OSPF route ID ............................................................................................................ 182
Configuring the OSPF passive interface .............................................................................................. 182
Configuring the OSPF distribute list .................................................................................................... 183
Configuring OSPF redistribute information ........................................................................................ 184
Configuring the OSPF refresh parameters .......................................................................................... 184
Configuring the OSPF route ID ............................................................................................................ 185
Configuring the OSPF routing timers .................................................................................................. 185
Configuring IP OSPF authentication.................................................................................................... 186
Configuring the IP OSPF authentication-key ....................................................................................... 186
CASA CMTS
Configuring the IP OSPF cost .............................................................................................................. 187
Configuring the IP OSPF dead interval ................................................................................................ 188
Configuring the IP OSPF Hello interval................................................................................................ 189
Configuring the IP OSPF message digest key ...................................................................................... 189
Configuring the IP OSPF retransmit interval ....................................................................................... 190
Configuring the IP OSPF transmit delay .............................................................................................. 191
Displaying OSPF general information ................................................................................................. 191
Displaying the OSPF internal routing table entries ............................................................................. 192
Displaying the OSPF database for a specified router .......................................................................... 192
Displaying OSPF interface information ............................................................................................... 192
Displaying OSPF neighbor information ............................................................................................... 193
Displaying the OSPF routing table ...................................................................................................... 193
Displaying IPv4 route information ...................................................................................................... 193
Sample OSPF configurations ............................................................................................................... 194
CONFIGURING THE ROUTING INFORMATION PROTOCOL ...................................................................................... 195
Entering RIP configuration mode ........................................................................................................ 196
Exiting RIP configuration mode .......................................................................................................... 196
Configuring the RIP default route ....................................................................................................... 196
Configuring the RIP default metric ..................................................................................................... 197
Configuring the RIP administrative distance ...................................................................................... 198
Configuring the RIP filter list ............................................................................................................... 198
Displaying the RIP command list ........................................................................................................ 199
Configuring the RIP neighbor router ................................................................................................... 200
Configuring RIP routing on an IP network .......................................................................................... 200
Configuring the RIP offset list ............................................................................................................. 201
Configuring the RIP passive interface ................................................................................................. 202
Configuring RIP redistribute information............................................................................................ 202
Configuring RIP static routes .............................................................................................................. 203
Configuring the RIP router map .......................................................................................................... 203
Configuring the RIP routing timers ..................................................................................................... 204
Configuring the RIP version ................................................................................................................ 204
Configuring the IP RIP authentication key chain ................................................................................ 205
Configuring an IP RIP authentication string ....................................................................................... 205
Configuring the IP RIP authentication mode ...................................................................................... 206
10
CASA CMTS
Displaying RIP routing information..................................................................................................... 207
Displaying RIP status information ...................................................................................................... 207
Displaying IP route Information .......................................................................................................... 208
CONFIGURING THE BGP ROUTING PROTOCOL (RELEASE 5.4 ONLY) ....................................................................... 209
Enabling BGP routing.......................................................................................................................... 210
Setting the BGP distance .................................................................................................................... 211
BGP decision processing ..................................................................................................................... 212
Enabling BGP networks....................................................................................................................... 212
Defining BGP peers ............................................................................................................................. 214
Setting the BGP address family........................................................................................................... 224
Configuring autonomous systems ...................................................................................................... 224
Using the BGP communities attribute ................................................................................................ 225
Configuring BGP community lists ....................................................................................................... 226
Displaying BGP routes......................................................................................................................... 231
Clearing and reestablishing BGP routes ............................................................................................. 232
Enabling capability negotiation .......................................................................................................... 234
Configuring route reflectors................................................................................................................ 235
IP ACCESS CONTROL ..................................................................................................................................... 236
Creating and removing ACLs............................................................................................................... 236
Entering and exiting ACL editing mode............................................................................................... 237
Adding and removing control rules .................................................................................................... 237
Adding remark statements to the ACL ................................................................................................ 239
Displaying a control rule in an ACL ..................................................................................................... 239
Displaying ACL names ......................................................................................................................... 240
Numbering control rules in ACLs......................................................................................................... 240
Applying an ACL to an IP interface (C3200 and C10200 only) ............................................................ 241
Removing the ACL from an IP interface .............................................................................................. 243
Creating and deleting IP access classes .............................................................................................. 243
Displaying access class information (Release 5.4) .............................................................................. 244
CONFIGURING ROUTE MAPS ........................................................................................................................... 245
Creating a named and sequenced route-map .................................................................................... 245
Using the route-map match commands ............................................................................................. 246
Matching BGP autonomous system paths.......................................................................................... 246
Matching the BGP community list ...................................................................................................... 247
11
CASA CMTS
Matching IPv4 and IPv6 addresses ..................................................................................................... 247
Matching route metrics ...................................................................................................................... 248
Matching route origins ....................................................................................................................... 249
Matching peer routes ......................................................................................................................... 250
Matching route tags ........................................................................................................................... 250
Using the route-map set commands .................................................................................................. 251
Modifying BGP autonomous system paths ......................................................................................... 251
Setting the atomic aggregate ............................................................................................................. 251
Modifying the BGP community attribute............................................................................................ 252
Modifying next-hop IP addresses........................................................................................................ 253
Setting the BGP local-preference path attribute ................................................................................ 253
Setting the metric for destination routing .......................................................................................... 254
Modifying route origins ...................................................................................................................... 254
Setting the BGP originator-id attribute .............................................................................................. 255
Setting the BGP weight attribute ........................................................................................................ 256
Displaying route-map details .............................................................................................................. 256
CONFIGURING VIRTUAL LOCAL AREA NETWORKS (VLANS) ................................................................................. 256
Configuring a VLAN............................................................................................................................. 256
Configuring up to six VLANs concurrently (Release 5.4) ..................................................................... 257
Configuring VLANs in a range (Release 5.4) ....................................................................................... 257
Configuring the MAC address on each VLAN interface....................................................................... 258
Enabling/disabling VLAN Interfaces (5.4) ........................................................................................... 258
Assigning a Gigabit Ethernet port to a VLAN ...................................................................................... 258
Assigning a 10Gigabit Ethernet port to a VLAN.................................................................................. 259
Removing a Gigabit Ethernet port from a VLAN ................................................................................. 259
Removing a 10Gigabit Ethernet port from a VLAN ............................................................................ 260
Assigning an IPv4 address to a VLAN.................................................................................................. 260
Assigning an IPv6 address to a VLAN.................................................................................................. 261
Rate limiting multicast traffic over a VLAN interface ......................................................................... 262
Assign a QAM port to a VLAN ............................................................................................................. 262
Assigning an IP access group to a VLAN interface .............................................................................. 263
Assigning a trunk to a VLAN interface ................................................................................................ 264
Displaying all VLAN configurations ..................................................................................................... 265
Displaying a VLAN interface (Release 5.4) .......................................................................................... 265
Displaying ARP entries from the current VLAN ................................................................................... 266
12
CASA CMTS
CONFIGURING L2VPN ................................................................................................................................. 266
Specifying ports/interfaces on the NSI side of the L2VPN VLAN ......................................................... 267
Specifying GigE/trunk interfaces on the L2VPN VLAN ........................................................................ 268
Preventing and permitting station movement and local forwarding ................................................. 268
Displaying the station movement and local forwarding configuration .............................................. 269
Displaying configured L2VPNs ............................................................................................................ 269
Displaying L2VPN statistics on QAM modules .................................................................................... 269
CONFIGURING TACACS (RELEASE 5.4) ........................................................................................................... 270
Configuring the TACACS host IP .......................................................................................................... 270
Configuring a TACACS key .................................................................................................................. 271
Enabling password authentication at the TACACS+ server................................................................. 271
Disabling the TACACS+ authentication password............................................................................... 271
Using RADIUS/TACACS+ Server for default server group for AAA login authentication ..................... 271
Configuring the AAA authentication login .......................................................................................... 272
Configuring AAA authorization ........................................................................................................... 272
Enabling accounting ........................................................................................................................... 273
Command accounting ......................................................................................................................... 274
Configuring AAA accounting for start-stop events ............................................................................. 274
Configuring AAA RADIUS-source loopback interface configuration ................................................... 274
Disabling the AAA RADIUS source ...................................................................................................... 275
Configuring the RADIUS server ........................................................................................................... 275
Disabling a specified RADIUS server or RADIUS encryption key ......................................................... 275
Displaying the AAA configuration ....................................................................................................... 276
STREAM CONFIGURATION AND MANAGEMENT................................................................................................... 276
Modes for mapping input streams to QAM output channels ............................................................. 276
Enabling manual operation mode ...................................................................................................... 277
Enabling RPC mode ............................................................................................................................. 278
Using auto-operation mode................................................................................................................ 278
Enabling auto-multiplex mode ........................................................................................................... 279
Enabling Group-4-port operation mode ............................................................................................. 280
Enabling Group-2-port operation mode ............................................................................................. 281
Setting the de-jitter interval ............................................................................................................... 282
Entering stream configuration mode.................................................................................................. 283
Ending stream configuration mode .................................................................................................... 283
Setting the stream source IP address ................................................................................................. 283
13
CASA CMTS
Setting the stream destination IP address .......................................................................................... 284
Setting the stream source UDP port ................................................................................................... 285
Setting the stream destination UDP port............................................................................................ 285
Displaying configured streams ........................................................................................................... 286
Binding a stream to a QAM output channel ....................................................................................... 287
Displaying unmapped streams ........................................................................................................... 288
Stream configuration example ........................................................................................................... 288
CONFIGURING DOWNSTREAM QAM PORTS ...................................................................................................... 289
Entering QAM interface configuration mode ..................................................................................... 290
Ending QAM interface configuration mode ........................................................................................ 290
Enabling QAM output ports ................................................................................................................ 291
Disabling QAM output port ................................................................................................................ 291
Enabling QAM output channels .......................................................................................................... 292
Disable QAM output channels ............................................................................................................ 292
Setting the QAM port IP address and subnet mask ............................................................................ 293
Setting the QAM port MAC address ................................................................................................... 294
Setting the QAM modulation type ...................................................................................................... 294
Setting the QAM channel annex ......................................................................................................... 295
Setting the QAM frequency ................................................................................................................ 296
Setting the QAM output power .......................................................................................................... 297
Setting the QAM interleave level ........................................................................................................ 298
Setting the QAM spectral inversion .................................................................................................... 299
Displaying QAM interface configurations ........................................................................................... 300
Displaying QAM channel counters and utilization rates ..................................................................... 300
CONFIGURING UPSTREAM PORT INTERFACES ..................................................................................................... 301
Showing upstream port interface configurations ............................................................................... 302
Showing upstream port interface configurations ............................................................................... 302
Displaying upstream interface status ................................................................................................. 304
Displaying upstream interface statistics ............................................................................................. 304
Changing the upstream MAP size ....................................................................................................... 305
Entering the upstream port interface configuration mode ................................................................ 305
Ending an upstream port interface configuration session .................................................................. 306
Enabling upstream ports .................................................................................................................... 306
Disabling upstream ports ................................................................................................................... 307
Setting the logical-channel channel-frequency................................................................................... 307
14
CASA CMTS
Setting the upstream input power level ............................................................................................. 308
Adjusting the upstream input power threshold .................................................................................. 308
Adjusting the upstream input power level.......................................................................................... 309
Setting the upstream map-advance ................................................................................................... 310
Enabling the upstream logical-channels ............................................................................................. 312
Disabling the upstream logical-channels ............................................................................................ 312
Setting upstream channel backoff values ........................................................................................... 313
Setting the upstream channel mini-slot size ....................................................................................... 315
Setting the upstream channel modulation profile .............................................................................. 316
Setting the upstream channel pre-equalization ................................................................................. 317
Enabling/disabling ingress noise cancellation .................................................................................... 317
Setting up voice bandwidth reserve percentage ................................................................................ 318
Enabling rate limiting ......................................................................................................................... 319
Displaying the upstream channel utilization rates ............................................................................. 319
Displaying the upstream channel signal quality ................................................................................. 320
Displaying the upstream-channel set ID ............................................................................................. 321
Displaying upstream interface statistics ............................................................................................. 321
Displaying voice information .............................................................................................................. 322
CONFIGURING IP-BUNDLE INTERFACES ............................................................................................................. 322
Adding the primary IP interface.......................................................................................................... 323
Adding a secondary IP bundle interface ............................................................................................. 323
Remove an IP bundle secondary IP address........................................................................................ 324
Adding primary and secondary IPv6 interfaces .................................................................................. 325
Adding a helper-address ..................................................................................................................... 326
Configure IP bundle sub-interfaces (Release 5.4) ............................................................................... 327
Applying IP bundle interfaces to MAC domains .................................................................................. 327
Classifying CPE devices for DHCP option 60 string matching ............................................................. 328
Configuring the IP RIP authentication key chain ................................................................................ 329
Configuring an IP RIP authentication string ....................................................................................... 330
Configuring the IP RIP authentication mode ...................................................................................... 331
Displaying the IP bundle interface configuration and statistics ......................................................... 331
CONFIGURING MAC DOMAINS....................................................................................................................... 333
Displaying domain interface configurations ....................................................................................... 334
Creating new domain interfaces ......................................................................................................... 335
Binding IP-bundle interfaces ............................................................................................................... 335
15
CASA CMTS
Binding upstream interfaces ............................................................................................................... 336
Deleting upstream interface bindings ................................................................................................ 337
Binding downstream interfaces .......................................................................................................... 337
Binding secondary downstream interfaces (5.4 only)......................................................................... 338
Deleting downstream interface bindings............................................................................................ 339
Enabling MAC domain interfaces ....................................................................................................... 339
Disabling MAC domain interfaces ...................................................................................................... 340
Setting MAC domain interface IP addresses ....................................................................................... 340
Setting MAC domain interface IPv6 addresses (Rel. 5.2 and earlier).................................................. 341
Removing MAC domain interface IPv6 addresses (Rel. 5.2 and earlier) ............................................. 342
Setting the helper-address (Software Version 5.2 and Earlier) ........................................................... 342
Configuring MAC domain IP bundle interfaces ................................................................................... 343
Setting the domain sync-interval ........................................................................................................ 344
Setting the upstream insertion-interval.............................................................................................. 345
Configuring the MDD interval ............................................................................................................. 346
Enabling a domain interface gateway IP address .............................................................................. 346
Enabling a domain interface TFTP proxy ............................................................................................ 347
Rejecting modem registrations with TFTP enforce ............................................................................. 347
Displaying modem registrations that have bypassed TFTP ................................................................ 348
Enabling/disabling IP policies on a domain interface ......................................................................... 349
Configuring multicast on MAC domain interfaces .............................................................................. 349
Enabling/disabling DHCP authorization on a MAC domain interface ................................................ 350
Configuring channel bonding on MAC domain interface .................................................................... 350
Enabling MAC domain multicast DSID forwarding ............................................................................. 351
Configuring IP-provisioning-mode on a MAC domain interface ......................................................... 352
Configuring MAC domain IPv6 router advertisement parameters ..................................................... 353
Displaying the router advertisement table ......................................................................................... 355
Configuring BPI+ on a MAC domain interface .................................................................................... 356
Configuring cable modem trap generation and interval .................................................................... 356
Displaying the MAC domain interface configuration.......................................................................... 357
Displaying MAC domain statistics ...................................................................................................... 357
CONFIGURING SERVICE GROUPS ...................................................................................................................... 358
Creating a new service group ............................................................................................................. 359
Binding upstream interfaces ............................................................................................................... 359
Binding downstream interfaces .......................................................................................................... 360
16
CASA CMTS
Displaying service groups ................................................................................................................... 360
Displaying MAC domain downstream service groups (Release 5.4) ................................................... 361
Displaying specific MAC domain downstream service groups ............................................................ 361
Displaying a specific downstream service group ................................................................................ 362
Displaying MAC domain upstream service group information ........................................................... 362
CONFIGURING BONDING GROUPS .................................................................................................................... 363
Creating new downstream/upstream bonding groups ...................................................................... 363
Binding upstream interfaces to a bonding group ............................................................................... 364
Binding downstream interfaces to a bonding group .......................................................................... 365
Displaying bonding groups ................................................................................................................. 366
Setting up the receive channel configuration ..................................................................................... 366
Assigning a receive module ................................................................................................................ 367
Assigning a receive channel ................................................................................................................ 367
Displaying the receive channel configuration ..................................................................................... 368
CONFIGURING MODULATION PROFILES ............................................................................................................. 369
Predefined modulation-profile 1 parameters ..................................................................................... 369
Configuring a modulation profile........................................................................................................ 372
Configuring TDMA burst types............................................................................................................ 372
Configuring ATDMA burst types ......................................................................................................... 374
Configuring MTDMA burst types ........................................................................................................ 376
Auto-mode MTDMA-type modulation profile configuration .............................................................. 376
Manual mode MTDMA-type modulation profile configuration.......................................................... 376
Configuring SCDMA burst types.......................................................................................................... 378
Retrieving configured modulation profiles ......................................................................................... 379
Removing modulation profiles ............................................................................................................ 380
CONFIGURING MULTICAST OPERATIONS ........................................................................................................... 380
Setting the multicast maximum channel utilization ........................................................................... 381
Enabling/disabling multicast session authorization ........................................................................... 382
Configuring a multicast session authorization profile ........................................................................ 382
Configuring a multicast session rule ................................................................................................... 383
Configuring the default action for a multicast join request ................................................................ 384
17
CASA CMTS
Configuring a maximum session number for multicast authorization ............................................... 384
Assigning a profile to multicast authorization .................................................................................... 384
Displaying multicast authorization configurations ............................................................................. 385
Displaying multicast authorization sessions ....................................................................................... 385
Configuring a multicast group table ................................................................................................... 386
Configuring multicast group encryption ............................................................................................. 387
Configuring multicast group QoS........................................................................................................ 388
Configuring a multicast group service class........................................................................................ 389
Configuring a default service class for a multicast group ................................................................... 390
Displaying multicast group configurations ......................................................................................... 391
Creating static multicast sessions ....................................................................................................... 391
Removing a static multicast session ................................................................................................... 392
Displaying static multicast sessions .................................................................................................... 393
Configuring IGMP packet filtering ...................................................................................................... 393
Displaying all filtering settings in the running configuration ............................................................. 394
Managing multicast for IPTV as a limited multicast session .............................................................. 394
Limited multicast sessions .................................................................................................................. 394
General multicast sessions ................................................................................................................. 394
How to identify limited multicast sessions ......................................................................................... 394
CONFIGURING CABLE SERVICE CLASSES ............................................................................................................. 395
Creating a cable service class ............................................................................................................. 395
Specifying the cable service class parameters .................................................................................... 396
Displaying service class parameters ................................................................................................... 397
Applying service classes to modem configuration files....................................................................... 399
CONFIGURING PACKETCABLE ......................................................................................................................... 400
Enabling PacketCable operation ......................................................................................................... 401
Displaying event messages ................................................................................................................. 401
Enabling DSCP checking ...................................................................................................................... 401
Configuring event messages ............................................................................................................... 402
Configuring an IP address ................................................................................................................... 402
Configuring an FTP user ...................................................................................................................... 402
Configuring FTP user passwords ......................................................................................................... 403
Configuring the T0 timer..................................................................................................................... 403
Configuring the T1 timer..................................................................................................................... 403
Configuring network layer signaling (NLS) ......................................................................................... 404
18
CASA CMTS
Configuring maximum normal calls .................................................................................................... 404
Configuring maximum emergency calls.............................................................................................. 405
Configuring inactive call aging (Rel. 6.1 and later) ............................................................................. 405
Enabling PacketCable admission control preempt voice priority........................................................ 405
Enabling PacketCable Multimedia (PCMM)........................................................................................ 406
Enabling Packetcable Multimedia version setup ................................................................................ 406
Displaying Packetcable Multimedia specifications ............................................................................. 407
Setting the cable service flow timeout................................................................................................ 407
Assigning dynamic service flows to downstream channels ................................................................ 408
Displaying the PCMM policy server .................................................................................................... 408
Displaying the PacketCable configuration .......................................................................................... 408
Specifying a timeout for the RKS server .............................................................................................. 409
Specifying a retry count for the RKS server ......................................................................................... 410
Specifying batch file send mode ......................................................................................................... 410
Specifying the batch file sending time interval ................................................................................... 410
Specifying the maximum size of the event message batch file ........................................................... 411
Specifying the maximum messages in the batch file .......................................................................... 411
Specifying the RKS server media alive time ........................................................................................ 412
Specifying the RKS server maximum gates ......................................................................................... 412
Displaying RKS server information...................................................................................................... 412
Displaying live gate summary information ......................................................................................... 413
Displaying upstream or downstream gate information ..................................................................... 413
Displaying the total gate number ....................................................................................................... 413
Displaying COPS server information ................................................................................................... 413
CONFIGURING DSG ..................................................................................................................................... 414
Creating a new DSG tunnel ................................................................................................................. 414
Creating a DSG tunnel-group .............................................................................................................. 415
Associating a DSG tunnel with a tunnel-group ................................................................................... 415
Displaying DSG tunnel groups ............................................................................................................ 416
Ending a DSG tunnel-group configuration session ............................................................................. 416
Assigning a destination MAC address to a DSG tunnel....................................................................... 416
Assigning a client list to a DSG tunnel ................................................................................................ 417
Assigning a service-class to a DSG tunnel ........................................................................................... 417
Assigning a classifier to a DSG tunnel ................................................................................................. 418
Displaying the DSG tunnel configuration (Release 5.4) ...................................................................... 419
19
CASA CMTS
Displaying the cable DSG tunnel configuration (Release 5.4) ............................................................. 420
Associating a downstream channel with a DSG tunnel-group ........................................................... 420
Displaying the downstream DSG configuration (Release 5.4) ............................................................ 421
Displaying DSG channel and tunnel group information...................................................................... 421
Setting a DSG timer to a downstream channel................................................................................... 422
Assigning a DSG vendor-parameter ID to a downstream channel ..................................................... 422
Assigning a DSG channel-list to a downstream channel ..................................................................... 423
Assigning DSG DCD ENABLE to a downstream channel ...................................................................... 423
Setting a DSG time interval on a downstream channel ...................................................................... 424
Displaying the DSG downstream-table settings ................................................................................. 424
Configuring a DSG client list ............................................................................................................... 425
Displaying DSG client lists ................................................................................................................... 426
Configuring DSG vendor parameters .................................................................................................. 426
Displaying DSG vendor parameters .................................................................................................... 427
Configuring a DSG channel list ........................................................................................................... 427
Displaying a DSG channel list.............................................................................................................. 428
Configuring DSG timers ...................................................................................................................... 428
Displaying DSG timers......................................................................................................................... 429
Configuring DSG unicast ..................................................................................................................... 429
Displaying DSG statistics..................................................................................................................... 429
Displaying the DSG running configuration ......................................................................................... 429
Using the DSG feature ........................................................................................................................ 430
Verify DSG DCD message and DSG data forwarding .......................................................................... 432
CONFIGURING DOCSIS BPI/BPI+ ................................................................................................................. 432
Configuring shared secrets to protect the modem configuration file ................................................. 433
Adding the privacy certificate (DOCSIS 3.0 only) ................................................................................ 435
Displaying the privacy certificate configuration (DOCSIS 3.0 only) .................................................... 436
Enforcing BPI and BPI+ ....................................................................................................................... 436
Setting the privacy hotlist (DOCSIS 3.0 only) ...................................................................................... 437
Configuring an encryption algorithm.................................................................................................. 438
Managing revocation certificates ....................................................................................................... 439
Configuring the source address verification rule ................................................................................ 441
Enabling SAV authorization ................................................................................................................ 442
Displaying the SAV configuration ....................................................................................................... 442
Enabling configuration file learning ................................................................................................... 443
20
CASA CMTS
Configuring TFTP proxies .................................................................................................................... 443
Displaying config file learning status .................................................................................................. 443
Displaying the TFTP option setting ..................................................................................................... 444
Configuring the EAE exclusion list ....................................................................................................... 444
Adding cable modems to the EAE exclusion list .................................................................................. 444
Displaying the EAE exclusion list ......................................................................................................... 445
SOURCE ADDRESS VERIFICATION (SAV) ........................................................................................................... 445
LEASEQUERY ............................................................................................................................................... 447
SPECTRUM MANAGEMENT............................................................................................................................. 448
CSM algorithm .................................................................................................................................... 449
Spectrum management procedures ................................................................................................... 450
SPECTRUM MEASUREMENT (DOCSIS 3.0 ONLY) ............................................................................................... 466
Displaying spectrum measurement results......................................................................................... 466
Running spectrum analysis across the entire spectrum...................................................................... 468
CONFIGURING LOAD BALANCING ..................................................................................................................... 469
Enabling and disabling load balancing ............................................................................................... 471
Enabling load balancing across MAC domains ................................................................................... 472
General load balancing groups ........................................................................................................... 472
Load balancing basic rules .................................................................................................................. 475
Load balance execution rules.............................................................................................................. 476
Load balancing policies ....................................................................................................................... 481
Restricted load balance groups .......................................................................................................... 482
Exclusion lists ...................................................................................................................................... 486
Restricted cable modems.................................................................................................................... 487
CM frequency and channel relocation ................................................................................................ 489
Displaying load balancing information ............................................................................................... 493
Command ordering ............................................................................................................................. 495
Command default values .................................................................................................................... 496
Sample configuration.......................................................................................................................... 496
CONFIGURING CHANNEL BONDING OPERATIONS................................................................................................. 502
Service group configuration................................................................................................................ 502
DOCSIS-MAC interface configuration ................................................................................................. 503
Channel bonding example .................................................................................................................. 504
CREATING STATIC CM BONDING GROUPS ......................................................................................................... 506
Adding a static downstream CM bonding group ................................................................................ 506
21
CASA CMTS
Adding a static upstream CM bonding group ..................................................................................... 506
Setting the provisioned attribute mask in an upstream/downstream bonding group ....................... 507
Adding an upstream channel to a bonding group .............................................................................. 508
Adding a downstream channel to a bonding group ........................................................................... 508
Setting the DSID re-sequencing wait time in a downstream bonding group ...................................... 509
Setting the DSID re-sequencing warning threshold in a downstream bonding group ........................ 509
QOS SUPPORT ............................................................................................................................................ 510
QoS support in DQM modules ............................................................................................................ 510
QoS support in DCU modules .............................................................................................................. 510
QoS support in switch fabric and Gigabit Ethernet interfaces ............................................................ 511
CONFIGURING QOS ..................................................................................................................................... 511
Configuring the service class (DOCSIS 1.1).......................................................................................... 512
Showing the service class.................................................................................................................... 512
QoS class and policy (C3200, C10200, C10G only) .............................................................................. 513
CONFIGURING SNMP (ENHANCED IN 5.4) ....................................................................................................... 516
Configuring the SNMP engineID ......................................................................................................... 517
Enabling SNMP traps .......................................................................................................................... 517
Setting an SNMP traphost .................................................................................................................. 518
Configuring SNMP server contact and location strings ...................................................................... 518
Configuring the SNMP trap source IP address .................................................................................... 519
Enabling SNMP inform requests ......................................................................................................... 519
Setting the SNMP community ............................................................................................................. 520
Disabling default SNMP public and private community ..................................................................... 520
Configuring the SNMP access table .................................................................................................... 520
Deleting the SNMP access table ......................................................................................................... 521
Configuring the community table ....................................................................................................... 522
Deleting the SNMP community table ................................................................................................. 522
Configuring the notification table....................................................................................................... 522
Deleting the notification table ............................................................................................................ 523
Configuring the securityToGroup table............................................................................................... 523
Configuring the TargetAddress table .................................................................................................. 524
Deleting the TargetAddress table ....................................................................................................... 525
Configuring the TargetParameter table ............................................................................................. 525
Deleting the TargetParameter table................................................................................................... 526
Configure the ViewTreeFamily table................................................................................................... 526
22
CASA CMTS
Deleting the ViewTreeFamily table..................................................................................................... 527
Configuring the SNMP user table ....................................................................................................... 527
Deleting the SNMP user table ............................................................................................................. 528
Displaying the SNMP configuration and statistics .............................................................................. 528
Monitoring the SNMP process at the CMTS ....................................................................................... 532
CONFIGURING IPDR .................................................................................................................................... 532
Displaying IPDR connections............................................................................................................... 533
Displaying IPDR sessions ..................................................................................................................... 533
Restarting and stopping the IPDR daemon......................................................................................... 533
Configuring IPDR collector mastership ............................................................................................... 534
Configuring the IPDR keepalive time interval ..................................................................................... 534
Configuring the IPDR acknowledge sequence interval ....................................................................... 534
Configuring the IPDR ACK interval ...................................................................................................... 534
Configuring the IPDR spectrum measurement interval ...................................................................... 535
Configuring the IPDR connection to be primary ................................................................................. 535
Configuring the IPDR loopback interface ............................................................................................ 535
CONFIGURING IPSEC .................................................................................................................................... 536
Enabling and disabling the IPsec service ............................................................................................ 536
Configuring the IPsec PreKey .............................................................................................................. 537
Displaying the IPsec PreKey ................................................................................................................ 537
Configuring IPsec Phase 1 ................................................................................................................... 537
Configuring IPsec Phase 2 ................................................................................................................... 538
Displaying IPsec information .............................................................................................................. 539
Deleting the IPsec configuration ......................................................................................................... 540
Adding an IPsec security policy ........................................................................................................... 540
Displaying the IPsec security policy database..................................................................................... 541
MANAGING CABLE MODEMS .......................................................................................................................... 542
Displaying cable modem status .......................................................................................................... 542
Displaying cable modem CPE devices ................................................................................................. 549
Displaying cable modems by state ..................................................................................................... 549
Cable modem summary information .................................................................................................. 550
Configuring the cable modem flap list ................................................................................................ 552
Showing the cable modem flap-list .................................................................................................... 554
Showing the cable modem summary (Release 5.2) ............................................................................ 555
Displaying the cable modem summary (Release 5.4) ......................................................................... 556
23
CASA CMTS
Displaying the cable modem on downstream channels ..................................................................... 557
Displaying cable modem physical information ................................................................................... 558
Showing the cable modem remote-query........................................................................................... 558
Configuring the remote-query polling interval ................................................................................... 560
Displaying the cable modem remote-query with a specified MAC address........................................ 560
Showing the cable modem remote-query with a specified IP address ............................................... 561
Setting the cable modem flap-list aging interval ................................................................................ 561
Accelerating cable modem registration.............................................................................................. 561
Registering DOCSIS 2.0 bonding modems........................................................................................... 562
Enabling the cable modem flap-list trap (Release 5.2) ....................................................................... 562
Enabling the cable modem flap-list trap (Release 5.4) ....................................................................... 563
Configuring a cable modem deny list ................................................................................................. 563
Enabling PacketCable admission control preempt voice priority........................................................ 563
Enabling cable DSX authorization ....................................................................................................... 564
Enabling Receive Channel Profile (RCP) fragment support ................................................................. 564
Controlling CMTS upstream power levels (Rel. 6.1 and later) ............................................................ 564
Adjusting modem upstream power levels (Rel. 6.1 and later) ............................................................ 565
Resetting cable modems and clearing cable modem counters .......................................................... 565
Clearing offline cable modems immediately ...................................................................................... 567
Clearing offline cable modems after aging ......................................................................................... 567
Displaying cable modem vendors ....................................................................................................... 568
Displaying vendor-specific information on cable modems ................................................................. 569
Adding and modifying cable modem vendor information .................................................................. 569
Deleting cable modem vendor information ........................................................................................ 570
Displaying vendor OUI information .................................................................................................... 570
Setting the default cable modem vendor ........................................................................................... 571
Displaying cable modem classifiers .................................................................................................... 571
Showing cable modem errors ............................................................................................................. 574
Displaying cable modem MAC information ........................................................................................ 574
Displaying cable modem spoof information ....................................................................................... 575
Displaying cable modem maintenance ranging information ............................................................. 576
Displaying denied cable modem ......................................................................................................... 576
Displaying the cable modem MAC summary ...................................................................................... 577
Displaying the cable modem status event report ............................................................................... 577
Displaying cable modem quality-of-service (QOS) .............................................................................. 578
24
CASA CMTS
Displaying the cable modem docsis-mac summary ............................................................................ 579
SUBSCRIBER MANAGEMENT ........................................................................................................................... 580
Enabling subscriber management ...................................................................................................... 581
Setting the mode for a CM to learn the CPE IP address without DHCP .............................................. 582
Setting maximum IPv4 CPEs behind a CM .......................................................................................... 582
Setting maximum IPv6 CPEs behind a CM .......................................................................................... 583
Resetting IP addresses of all CPEs behind a CM ................................................................................. 583
Using the subscriber management default settings ........................................................................... 583
Setting a filter rule .............................................................................................................................. 585
Removing all IP and TCP-UDP filters ................................................................................................... 585
Displaying cable modem information ................................................................................................. 586
Displaying the cable modem control table ......................................................................................... 586
Displaying CPE information ................................................................................................................ 587
Displaying IP filter ............................................................................................................................... 587
Enabling/disabling cable modem host authorization ......................................................................... 588
Displaying the cable host authorization ............................................................................................. 588
CONFIGURING MPEG COMPLIANT FEATURES ................................................................................................... 588
Setting the PAT insertion interval ....................................................................................................... 588
Setting the PMT insertion interval ...................................................................................................... 589
CONFIGURING DVB-COMPLIANT FEATURES ...................................................................................................... 589
Enabling SI table generation and insertion......................................................................................... 590
Setting the network ID ........................................................................................................................ 591
Setting the channel transport stream ID ............................................................................................ 592
CONFIGURING TOT ..................................................................................................................................... 593
Setting the time zone .......................................................................................................................... 593
Setting the time offset ........................................................................................................................ 594
Setting daylight saving time (US only) ................................................................................................ 595
CONFIGURING THE DOCSIS EVENT NOTIFICATION POLICY .................................................................................... 595
Enabling DOCSIS cable event reporting .............................................................................................. 596
Configuring event reporting by unique identifier ............................................................................... 596
Displaying the cable event identifiers ................................................................................................. 597
Configure the event reporting flags for DOCSIS event messages ....................................................... 597
Displaying the current priority and flags for cable event logging....................................................... 598
Enabling logging of DOCSIS event messages to a SYSLOG server ....................................................... 599
Configuring the TRAP/INFORM and SYSLOG throttling and limiting attribute ................................... 599
25
CASA CMTS
Specifying the throttle interval ........................................................................................................... 600
Specifying the throttle threshold ........................................................................................................ 600
USING THE LOGGING COMMANDS ................................................................................................................... 601
Configuring logging targets and levels ............................................................................................... 602
Excluding user messages from the log file by severity level ............................................................... 603
Displaying the current logging settings .............................................................................................. 604
26
CASA CMTS
Preface
Purpose of the guide
This guide provides software configuration instructions for Release 5 of the Casa CMTS series:
C2200, C3200, C10200, and C10G. Although these three platforms have different hardware
features, they share the same set of software features and commands.
For the descriptions of the hardware features and installation of different platforms, please refer to
the documents:
C2200 CMTS Hardware Installation Guide

C10G CMTS Hardware Installation Guide
For the debugging and diagnostic information, refer to the Casa Systems CMTS Debugging and
Diagnostic Reference Guide.
Audience
This guide is intended for system administrators, support engineers, and operators who configure
and manage Casa CMTS products. Users who perform these tasks should be familiar with the
Casa CMTS hardware and cabling, and also have experience with the following:
MPEG-2 protocol
UDP/IP protocol
RF cable plants
DOCSIS protocol
Revision information
Version
Additions/Changes
V 5.0.7 / Feb 2008
Same as release C3200.5.0.7
V6.0.1 / July 2008
- DSG configuration section

- SCDMA modulation profile
V6.0.2 / Aug 2008
- Multicast configuration section
V6.0.3 / Aug 2008
- Bonding group configuration

- Monitor line card
- Monitor gige
27
CASA CMTS
- IGMP configuration
- Multicast on mac-domain interface
- ARP management
V6.0.4 / Aug 2008
- Trunk-interface configuration section

- Show cable modem remote query
- DOCSIS 3.0 functions in BPI/BPI+ section
Sept 09 2008
- Remove preamble-offset field from modulation profile
Oct 16 2008
- Add more commands to Load Balancing section
Rel5.2.1 / Nov 14 2008
- Access-class configuration
- L2VPN configuration
- TACACS (AAA) configuration
- Loopback interface configuration
- Ingress noise cancellation configuration
- Debug functionality configuration
- DSG command update
- PacketCable 1.5
- Subscriber management
Rel5.2.1/Dec 16 2008
- IPDR configuration
- IPsec configuration
- SNMP command update
- grammar/wording revision
Rel5.2.1/Dec 19 2008
- Remove BPI commands of privacy kek/tek grace-time

- IPDR configuration
- IPsec configuration
- Update SNMP configuration
- More TACACS+ commands
Rel5.2.1/Jan 8 2009
- Upstream channel-frequency range for J-DOCSIS

- Update on some ACL commands
Rel5.4/June 29, 2009
- IPsec command update

- PacketCable command update
- Change minimum upstream frequency to 47 MHz
- System reboot commands update
- Add cm-hop commands in spectrum manager section
-Corrections to the Spectrum Management section
-Corrections to PacketCable section
-Major corrections throughout, including updated examples and
commands
Sept. 2009
-Added alias command for privileged mode.

-Added Link Aggregation Control Protocol.
-Added more VLAN commands.
-Added bootstrap router support.
28
CASA CMTS
-Added PIM commands.
-Added RADIUS and TACACS+ command information.
-Added MAC domain and service group commands.
-Added and changed PacketCable commands.
-Added commands to DSG.
-Added cable modem commands.
-Added IP policy routing.
-Added commands to L2VPN.
-Added BPI+ configuration on MAC domain interfaces.
-Added commands to bonding group configuration.
-Corrected errors in spectrum noise level and remove cable
modems.
-Added IS-IS protocol.
-Added cable modem vendor commands.
-Added IP policy routing.
-Added bonding group commands.
-Added SSH support.
-Add flap list commands.
Added new features to spectrum management, including multiple
secondary profiles, usage tips, corrections, and examples.
Dec. 2009
Added Source Address Verification

Added IPv6 addresses for GigE and MAC domain interfaces
Added section on BGP configuration
Added commands for enabling/disabling DOCSIS logging
Added individual CPE MAC address, IP address and IP subnet
authorization
Added description of voice-bw-reserve and rate-limit commands
Added new spectrum management feature and additional usage
tips.
Added description of QoS support
Added command to allow one downstream channel to be bonded to
one MAC domain over primary and secondary downstream
channels.
Added command to support background remote query
configuration.
Added configuration to set upstream frequency difference limit on
DCC when the initial technique is direct
Added new option in show cable modem remote-query command
the option is for getting remote query info directly from the cable
modem when background remote query feature is turned on
Added module installed/removed trap for 3K/10K CMTS
29
CASA CMTS
Added feature that loopback interface supports IPv6
Added new feature to use downstream frequency override in RNGRSP messages to direct a modem to its correct mac domain
Added commands for QoS class and policy
Added SFP CWDM type for show gige interface command
Added description for timezone command
Added L2VPN overview
Added cable service class configuration section
Added section on leasequery
Added description of show gige stat command
March 2010
Added loopback address features for FTP/TFTP and IPv6 support

Added auto-reboot command
Added MAC domain sub-interfaces
Added new spectrum management functionality
Added command for booting from CFE
Distinguished 5.4 features from 5.2 features.
April 7, 2010
Added extended ping command.

Added dhcp-giaddr command.
Added IP access control for MAC domains command.
Added IP policy to MAC domain command.
Added debug cable commands: load-balance, LACP, and TLV.
Added ACL commands for match counts: show interface <type>
<num> acl-count [details]; show ip access-list <string> applications;
show ip access-list <string> details.
Documented option to configure hop back threshold.
Added verbose option to debug cable dhcp command.
Added hyperlinks to table of contents.
Added command for disabling TCC for older bonding modems.
Added command to apply policy-map to VLAN interfaces.
April 12, 2010
Added command for encrypting passwords.

Added modifiers to show ip route command.
Fixed typos in debug ospf nsm command.
Added version 5.4 changes to debug ospf commands.
Modified the IP bundle interface command description.
Corrected the TOT time zone modifier.
Added command for excluding user log-in entries from the log file.
Added note about reboot messages.
Updated ACLs to include support for 256 rules and counters.
April 19, 2010
Corrected error about downstream interfaces and service groups.

Added new commands: upstream map size and channel utilization
interval.
30
CASA CMTS
Added command for encrypting passwords in the configuration
files.
Added show interface ip-bundle parameters.
Added description of password encryption command.
Added description of RIP authentication to IP bundle interfaces.
Add VLANs to passive interface configuration.
Updated QoS policy, class, and rules.
Corrected discrepancies in description of user privileges.
Added sample service class configuration.
Added description of commands show cable voice summary
show interface gige debug cable cm-ctrl and debug cable cmstatus.
Added description of command for configuring ip access group on
eth0.
May 16, 2010
Added stat and throughput options to show interface trunk

command.
Added information on applying access lists to specific interfaces.
Added summary of options to show cable modem command.
SAV supported in 5.2.
Added clear arp-cache command.
Add command for configuring MTU size.
Corrected show cable modem verbose output.
Added command for configuring VLAN interface MAC addresses.
Added command for setting the service flow timeout.
Added command to show the ACL counters by interface.
Added service group as an option to the show load balance
command.
Added command to configure cable modem traps and the cable
modem trap interval under the MAC domain.
Corrected output of show load-balance dynamic
Added lawful-intercept source-interface loopback 0 command.
Added the maximum number of supported service groups.
Added description of criteria for modems displayed with show cable
modem non-bonding.
Added command for assigning a service policy to a VLAN.
June 1, 2010
Corrected upper range of VLAN interfaces.

Corrected information on using masks instead of wildcards to
exclude modems by type from load balancing.
Updated the cable modem status section.
Corrected information about storage devices and copying software
to flash.
31
CASA CMTS
Corrected gige command.
Corrected Table numbering and references.
Added command: debug service group.
Corrected show interface ip-bundle command option.
Corrected show user current command.
June 14, 2010
Noted that si generator tot command is not used with EuroDOCSIS.

Corrected errors in arguments to the debug ip ospf command.
July 6, 2010
September 24, 2010
November 18, 2010

December 30, 2010
Added brief description of pre-equalization.

Clarified auto-reboot operation in 5.2 vs. 5.4.
Added IPv6 display commands.
Updated table describing cable modem information.
Consolidated all VLAN configuration information into a dedicated
section.
Added commands for configuring system monitor.
Added commands to configure lawful intercept.
Added description of load balancing type in show load balance
output.
Reformatted document to provide better procedure visibility.
Consolidated all debug and diagnostic commands in the Casa
CMTS Debugging and Diagnostics Reference Guide.
Revised document to support CMTS software up to 5.4.19.9.
January 14, 2011
Reformatted document to reduce page count.

Corrected reported issues and inaccuracies.
Added missing route-map functionality.
Commands that operate in configuration mode now have a config
indication in the command table headers.
Release 5.4.19.10 general availability.
March 18, 2011
Added IS-IS router configuration.
June 15, 2011
Release 5.4.21 availability update. See the Release Notes for

additional information.
information.
Added missed 5.4.21 command; software-health-check snmpd
July 15, 2011

September 7, 2011
November 14, 2011

information.
Content
This guide covers the software configuration commands for Casa CMTS products, and is
organized in following chapters:
Chapter
Description
1. Casa CMTS Configuration

Overview
Describes the Casa CMTS series major interfaces and

how to start configuration.
2. Configuring and Managing the
Describes how to use CLI (Command Line Interface) to
32
CASA CMTS
Casa CMTS from the Command

Line Interface
configure, manage, and monitor the system.
For information on diagnostic and debugging commands, refer to the CMTS Debugging and
Diagnostic Reference.
Notation conventions
This manual uses the following conventions for command syntax descriptions and for textual
emphasis:
Convention
Boldface font
Description
Commands and keywords are in boldface.
Italic font
Arguments for which you supply values are in italics.
[]
Elements in square brackets are optional.
{x | y | z}
Alternative, mutually exclusive, keywords are grouped in

braces and separated by vertical bars.
Optional alternative keywords are grouped in brackets and
separated by vertical bars.
A non-quoted set of characters. Do not use quotation marks
around the string or the string will include the quotation marks.
Terminal sessions and information the system displays are in
screen font.
Information you must enter is in boldface screen font.
[x | y | z]
String
Screen font
Boldface screen font
^
<>
!, #
The symbol ^ represents the key labeled Controlfor

example, the key combination ^D in a screen display means
hold down the Control key while you press the D key.
Nonprinting characters, such as passwords, are in angle
brackets in contexts where italics are not available. Angle
brackets are also used for variables.
An exclamation point (!) or a pound sign (#) at the beginning
of a line of code indicates a comment line.
33
CASA CMTS
1 Casa CMTS configuration overview

This chapter describes how to start up and configure the Casa CMTS in basic operation. It
contains the following sections:
Slot and port numbering

Completing pre-configuration
Starting system configuration
Sample configuration files
Slot and port numbering

In Casa CMTS configuration, interfaces are specified using slot/port format. The slot number is
the chassis slot in which an interface line card is installed. The port number is the physical
location of the port on an interface line card. This section describes the slot and port numbering
for the three platforms, C2200, C3200, and C10200.
C2200 slot and port numbering

Network interface numbering
The network interfaces are connected through the 4 GigE SFP ports located on the right side on
the front panel of the C2200 chassis. The ports are numbered 0 to 3 from left to right. Refer to
Figure 1-1.
0 1 2 3
s GigE SFP
Figure 1-1. C2200 Front Panel
RF interface numbering
C2200 contains 4 line-card slots located at the rear of the chassis (See Figure 1-2). The 4 slots
can install any combination of the two types of DOCSIS modules, DQM module or DCU module.
Slot numbers are 0 through 3 counting from left to right.
34
CASA CMTS
Slot
RF Output
Burst Receiver
Input
Burst Receiver
Input
Burst Receiver
Input
Figure 1-2. C2200 Rear Panel
Port numbers for DQM module are 0 through 3 counting from left to right (See Figure 1-3).
Figure 1-3. DQM Module Faceplate
The double-row ports of the DCU module are numbered 0 to 7 counting from left to right on the
bottom row and then from left to right on the top (See Figure 1-4).
Figure 1-4. DCU Module Faceplate
35
CASA CMTS
C3200 slot and port numbering

Network interface numbering
The network interfaces are connected through the 12 GigE SFP ports that locate on the rear
panel of the C3200 chassis (See Figure 1-5.) The ports are numbered 0 to 11 from left to right.
GigE SFP Port 0 1 2 3 4 5
Line-Card Slot 0
6 7 8 9 10 11
Figure 1-5. C3200 Chassis Rear View
RF interface numbering
The C3200 contains 6 line-card slots located at the rear of the chassis. The 6 slots can accept
any combination of the two types of DOCSIS modules, DQM modules or DCU modules. Slots are
numbered 0 to 2 counting from left to right on the bottom row and then 3 to 5 from left to right on
the top row (See Figure 1-5). Since the C3200 uses the same types of DOCSIS modules (DQM
and DCU) as C2200 platform does, the numbering schemes for the ports of DOCSIS modules are
the same as well. See figures 1-3 and 1-4 above.
C10200 and C10G slot and port numbering

The RF ports for the C10200 and C10G platforms are located in the back and are numbered from
0-15, top to bottom on each I/O module. The card slots are located in the front and are numbered
from 0-13, left to right. The GigE Ethernet ports are numbered from top to bottom on each SMM
module.
For detailed information, see the following publications:
Casa Systems C10G CMTS Hardware Installation Guide

Casa Systems C10200 CMTS Hardware Installation Guide
36
CASA CMTS
C10G redundancy operations

The C10G CMTS supports redundancy and failover for the SMM and the DOCSIS line cards
using a combination of front- and rear-installed modules to switch existing RF connections from
the module at fault to the redundant standby module for uninterrupted operation.
Slot information and cabling on the network side

For redundancy to operate correctly, SMM and DOCSIS line cards must be installed into specific
chassis slots, as follows:
SMM Slot 6 and Slot 7; redundant module in either slot; one will be active and one will be
in standby mode. Both SMMs are fully operational during system operation with SMM
redundancy enabled.
IP addresses on GigE/10GigE interfaces must be unique between slots 6 and 7 and

the IP addresses must not be on the same subnet. This means that the IP addresses
on the SMM slot 6 interfaces must not be assigned or overlap with the IP addresses
assigned to the SMM slot 7 interfaces.
The 10/100 Fast Ethernet ports (eth0) must have unique IP addresses between the
SMMs in slots 6 and 7. However, these addresses can be on the same IP subnet.
DQM (QAM) downstream Redundant module in Slot 5 or in Slot 8.

DCU upstream (UPS) Redundant module in Slot 5 or in Slot 8.
To ensure proper cabling to support redundancy, be certain that the GigE ports on the active
SMM have corresponding standby cabling to the redundant SMM (using ports of matching speed)
to connect to your network switches and routers.
Note: If the C10G is rebooted, all modules are reset and the redundant modules automatically
assume Standby status as soon as the CMTS is fully operational.
Slot information on the RF I/O side

At the rear of the system, there are two types of RF I/O switching modules that occupy slots 5, 6,
7, and 8:
LC switch (rear slots 5 and 8) -- Operates with DOCSIS line-card module (either DQM or
DCU) to provide N+1 redundancy. If a DOCSIS line-card module fails, a redundant DOCSIS
line-card module automatically assumes operation. The LC switch module cuts off the
connection between failed module and its associated RF I/O module and establishes the
traffic connection between the redundant and the RF I/O module.
With the LC switch module, the front-installed line cards in slots 5 and 8 are available for
redundancy operations.
37
CASA CMTS
SMM switch (rear slots 6 and 7) Operates with the front-installed SMM modules. If the
active SMM module fails, the redundant SMM automatically assumes L3 routing operations.
The SMM switch module cuts off the routing operations between the failed SMM to the
upstream and downstream line-card modules and RF I/Os, and then transfers routing
operations to the currently active SMM.
These modules connect to the switching backplane and can be installed during system operation.
There is no need to power down the CMTS for installation or removal.
Caution: The LC and SMM switch modules MUST be installed in their specific chassis slots, and
ALL four slots (5, 6, 7 and 8) must be occupied for redundancy operations. Both modules are
appropriately labeled for identification; either LC SWITCH or SMM SWITCH.
In most cases, you should never have to remove the SMM Switch module in rear slots 6 and 7, or
the LC Switch module in slots 5 and 8. However, in the event that removal is necessary, ensure
that the associated front slots 5 and 8 are not in a redundant state (ACTIVE LED is off).
If the SMM Switch and LC Switch modules are removed at any time, future redundancy
operations will not be available.
See the Casa Systems C10G CMTS Hardware Installation Guide for information on installing
and removing these modules.
High availability (HA) redundancy commands

The Release 6.0 software includes the high availability (ha) commands that allow you to switch
between the active and redundant standby modules in a C10G and upgraded C10200 systems.
Redundancy is supported through the RF Switch (LC Switch and SMM Switch) installed in the
chassis rear slots 5 to 8, and the two SMMs in front slots 6 and 7 (with either SMM as a
redundant standby).
Enabling and disabling redundancy on the C10G

The CMTS allows you to fully control redundancy operations on the C10G platform. In addition to
enabling and disabling redundancy protection, you can specify the modules by system slot
number to be available for failover, and at the same time have modules that are unavailable, or
unprotected, should a failure occur.
By default, the CMTS software protects all modules by making them available for switching to a
redundant standby.
Example:
To enable redundancy protection on selected CMTS modules, enter configuration mode and use
the following command:
38
CASA CMTS
CASA-CMTS# config
CASA-CMTS(config)# ha redundancy [module list]
Specify the modules by slot number, separating each module in the list with a comma (). Valid
values are 0 to 13.
CASA-CMTS(config)# ha redundancy 0,1,2,5,6,7,8,11,12
In the above example, the modules in system slots 3, 4, 9, 10, and 13 are not redundancy
protected.
Example:
To enable redundancy protection on ALL CMTS modules in slots 0 to 13, enter the following
command:
CASA-CMTS(config)# ha redundancy
Example:
To disable redundancy protection on any previously-specified modules, enter the following
command:
CASA-CMTS(config)# no ha redundancy [<module>]
Specify a module by slot number. Valid values are 0 to 13. Repeat the command to remove
additional modules from the previously-configured module list.
CASA-CMTS(config)# no ha redundancy 2
In the above example, the module in system slot 2 is removed from the list of redundancyprotected modules.
Reverting to the primary modules after recovery

After a failover condition where the standby module is now active, you can configure the CMTS to
revert back to the primary module after it has rebooted and is in the standby state. By default,
reverting to the primary is disabled. However, you can schedule the switch-back so that it
happens after 30 minutes (the default setting), or after a specified number of minutes in the range
1 to 1440 (1 minute to 24 hours).
Example:
To revert back to the primary module after 30 minutes (default), enter the following command:
CASA-CMTS(config)# ha redundancy revert
Example:
39
CASA CMTS
To revert back to the primary module after 2 hours (120 minutes), enter the following command:
CASA-CMTS(config)# ha redundancy revert 120
Example:
To disable reverting to the primary modules after recovery to the standby state, enter the
following command:
CASA-CMTS(config)# no ha redundancy revert
Interactively switching between the active and standby

The CMTS software includes high-availability commands from the top level of the CLI that allow
you to interactively switch between the active and standby modules immediately. This means that
you can toggle between two modules without waiting for the modules to revert automatically
after a configured time period, as covered in the previous section.
Placing a module in the standby state allows you to pull and replace the module in the chassis (if
necessary) without service interruption.
Example:
To switch from the active primary line card to the standby module immediately, enter the following
command:
CASA-CMTS# ha module <module> protect
where <module> is the primary line card that will switch over to the standby. The CMTS software
will look for the standby card, examine its current status, and will either permit or deny the failover
(if the standby is not ready, has an unknown status, or is not found).
To revert back from the redundant standby (currently active in slots 5 or 8) to the primary line
card (slots 0 to 4, 9 to 13), enter the following command:
CASA-CMTS# ha module <module> revert
where <module> is the primary line card to which the standby module will switch back.
Note:
The ha module <module> revert command is not supported for SMM operations in
slots 6 and 7.
Displaying the current high availability settings and log file

To display the current high availability status, use the following commands:
40
CASA CMTS
show ha configuration
show ha log
clear ha log
Example:
CASA-CMTS# show ha configuration
ha redundancy revert 30
ha redundancy 0,1,2,3,4,6,7,9,10,11,12,13
Use the show ha log command to display high-availability event history, including the time of the
failover, type of failure, and the affected system slots. Executing the clear ha log will erase the
current high-availability logged entries.
Note:
If ha redundancy is set for a specific set of modules, the show running-config

command will display those modules with the entry ha redundancy <module-list>.
Similarly, if redundancy is disabled for all modules, then entry no ha redundancy will
display.
Using software auto-recovery

The ha software auto-recovery command instructs the CMTS to perform automatic recovery of
software processes in the event of a module failure. By enabling this option, software recovery
becomes preferred method of handling a failure at the affected module. When disabled,
automatic recovery is not performed and a failover to the standby SMM will take place.
Example:
CASA-CMTS(config)# ha software auto-recovery
To disable the software auto-recovery to revert to the default setting, use the no form of the
command.
CASA-CMTS(config)#
no ha software auto-recovery
Fan, power, and temperature status on the C10G

For C10G platforms, the CLI provides the show envm command to selectively display fan,
power, and temperature status. If a specific argument is not specified, the CMTS displays the
current status for all arguments.
CASA-C10G# show envm [fan | power | temperature]
CASA-C10G# show envm fan [left [0-1]| middle [0-1] | right [0-1]]
CASA-C10G# show envm temperature [module <number> | QAM | SMM | UPS]
41
CASA CMTS
CASA-C10G# show envm power

Example:
CASA-C10G# show envm
PEM A (-48V)
Input 1
Input 1 FUSE
Input 2
Input 2 FUSE
Input 3
Input 4 FUSE
Input 4
Input 4 FUSE
Temperature
:
:
:
:
:
:
:
:
:
FAN_Tray
Temperature
LEFT**
MIDDLE**
RIGHT**
22C/ 71F
23C/ 73F
23C/ 73F
Module
2
6
PEM B (-48V)
Input 1
Input 1 FUSE
Input 2
Input 2 FUSE
Input 3
Input 3 FUSE
Input 4
Input 4 FUSE
Temperature
Present
Good
Present
Good
Present
Good
Present
Good
78 F/26 C
DC_A/DC_B
-48V/
-48V/
-48V/
Temperature
86F/ 30C
89F/ 32C
Front/Back
Fan RPM
2200/2700
1700/2900
2600/2000
0V
0V
0V
:
:
:
:
:
:
:
:
:
Present
Good
Present
Good
Present
Good
Present
Good
80 F/27 C
Switch
Present
ON
ON
ON
YES
YES
YES
Status
Normal
Normal
Type
UPS
SMM
CASA-C10G(config)#show envm temperature

Module
Temperature
Status
1
87F/ 31C
Normal
5
78F/ 26C
Normal
6
89F/ 32C
Normal
7
89F/ 32C
Normal
8
102F/ 39C
Normal
9
105F/ 41C
Normal
10
96F/ 36C
Normal
13
71F/ 22C
Normal
Type
QAM
QAM
SMM
SMM
UPS
UPS
UPS
QAM
Note that the C10G uses three fan modules: LEFT, CENTER and RIGHT. Each module has two
fans that are designated as either front or back, as follows:
LEFT 0 = Front, 1 = Back

MIDDLE 0 = Front, 1= Back
RIGHT 0= Front, 1= Back
C10G 8-channel QAM frequency configurations

With the introduction of the C10G CMTS platform with the new 8-port 64-channel (8x8)
downstream QAM module, 8 channels per port are configured in two contiguous or noncontiguous banks of 4 channels in the 47MHz to 999MHZ frequency range. As in previous
releases supporting 4 channels per port, the software automatically adjusts the frequencies on
channels 0 to 3, and on channels 4 to 7 based the configured Annex (A, B, or C) for frequency
separation. This means that if you specify the frequency for channel 1 (with Annex B separation
42
CASA CMTS
at 6MHz), channels 0, 2 and 3 will be correctly separated by 6MHz based on the specified
channel 1 frequency setting. The same applies to channels 4 to 7.
In the following example, the two 4-channel banks are contiguous across the port with 6MHz
separation.
interface qam 12/0
interleave 8
channel 0 frequency 549000000
no channel 0 shutdown
channel 1 shutdown
channel 2 shutdown
channel 3 shutdown
channel 4 shutdown
channel 5 shutdown
channel 6 shutdown
channel 7 shutdown
no shutdown
In the following example, the two 4-channel banks are non-contiguous across the
port with the range 50MHz to 68Mhz for channels 0 to 3, and 573MHz to 591MHz for
channels 4 to 7. Each 4-channel bank still maintains 6MHz frequency separation.
interface qam 12/0
interleave 8
channel 1 shutdown
channel 2 shutdown
channel 3 shutdown
channel 4 shutdown
channel 5 shutdown
channel 6 shutdown
channel 7 shutdown
no shutdown
C10G router redundancy

For information on routing redundancy on the Casa C10G, refer to the Casa Systems CMTS
Network Solutions Guide available with software release version 6.0.3 and later.
43
CASA CMTS
Completing pre-configuration
This section describes prerequisite steps you must complete prior to powering on and configuring
your Casa CMTS.
Step
Action
Ensure that your network supports reliable broadband data transmission.
Ensure that your Casa CMTS is installed according to the instruction in the Casa
CMTS Hardware Installation Guide. This includes connecting a CMTS GigE Ethernet
port to a GigE port on the network.
Ensure that all other required headend routing and network interface equipment is
installed, configured, and operational. This includes:
All routers, switches, etc.
Servers (DHCP, TFTP, ToD)
Network management systems

Ensure that the modem firmware can support the features, throughput, and
management requirements of the network.
Ensure that DHCP and DOCSIS configuration files have been created and pushed to
appropriate servers so that each CM, when initialized, can:
Transmit a DHCP request
Receive an IP address
Obtain TFTP and ToD server address
Download a DOCSIS configuration file

Ensure that CPEs and CMs meet requirements for your network and service offerings.
Be familiar with your channel plan to assign appropriate frequencies.
4
5
After these prerequisites are met, you are ready to configure your Casa CMTS.
Using the command line interface

The Command Line Interface (CLI) is a standard UNIX-like interface. It has the usual shortcuts:
Purpose
Action
Auto - Completion
Auto - Recognition
Use Tab key

The CMTS recognizes the
command once enough
characters are entered to
distinguish it from other
commands.
Use arrow keys
If command syntax is entered
incorrectly
? key displays commands
relevant to the current
Command history
Display error
messages
Display commands
and arguments
Example
copy run start
Instead of:
copy running-config
startup-config
44
CASA CMTS
configuration context as well

as the global commands
(those that function at multiple
levels of the CLI. Commands
that operate within the current
context appear first, followed
by the global command listing.
Shortcuts using the
alias command (Rel.
5.4 and later).
To shorten the show cable modem

command to scm, enter:
CASA-CMTS: alias scm show
cable modem
Starting the system configuration

This section describes some basic procedures to start your Casa CMTS configuration. It contains
following topics:
Connecting the console

Starting the system
Viewing loaded software version
Viewing the system hardware configuration
Viewing the system running configuration
Entering configuration mode
Configuring CMTS device contact and location strings
Saving the configuration to NVRAM
Resetting the IP address
Restoring factory defaults
For complete commands and syntax, refer to Chapter 2 of this document Configuring and
Managing Casa CMTS from the Command Line.
Connecting the console

Connect a console to the console port using the console cable (null modem cable) provided by
Casa. Set the speed to 115200.
Note: Use the console cable provided by Casa to ensure the connection will work. See the
appropriate hardware installation guide for the console pinouts.
Resetting the console

In the event that the console becomes inadvertently locked, use the reset-console command to
apply TTY default parameters to the console port.
Step
1
Command
Purpose
reset-console
Reapplies TTY console port
45
CASA CMTS
default parameters.
Example:
CASA-CMTS# reset-console
Starting the system

Follow the steps below to start your system:
Step
Command
Purpose
Toggle the power switch.
Turn on the power.
...
...
CASA-CMTS>
Observe the console

terminal for boot process.
enable
Example:
CASA-CMTS> enable
Password: casa
CASA-CMTS#
When booting is complete,

the system banner ends
with a system prompt (note
that you may see error
messages during boot-up.
These are the result of the
boot sequence and do not
indicate a problem unless
the system does not boot.
Enter privileged mode.
Enter the enable mode
password as, casa
(password can be changed
from enable mode). The
prompt changes to the
enable mode prompt.
Viewing the loaded software version

Use the following command to view the system software version after entering the enable mode.
Step
1
Command
Purpose
show version
Display the
system software
version.
Example:
CASA-CMTS# show version
Running Image: SMM Rel 5.4, Ver 19, Thu Nov 4
09:23:19 EST 2010, (xcheng)
Boot device: net
Target IP: 192.168.8.232, Host IP: 192.168.8.2
Boot Image: smm.gz.xc54
flash1: SMM Rel 5.4, Ver 19.2, Tue Sep 21 18:12:26
EDT 2010, ( relmgr)
flash2: SMM Rel 5.2, Ver 50, Fri Oct 29 12:50:37
EDT 2010, ( moly)
CFE Boot: Major 2, Minor 1, Build 4
46
CASA CMTS
Viewing the system hardware configuration

Use the following command to view the system hardware configuration after entering the enable
mode.
Step
1
Command
Purpose
show system
Display the CMTS hardware

configuration.
Example:
CASA-CMTS# show system
Viewing the system running configuration

Use the following command to view the system software configurations and settings after entering
the enable mode. By default, this command only displays a subset of values. To view all the
default values in the configuration, use the verbose option.
Step
1
Command
Purpose
show running-config
Display a subset of system

software configurations and
settings.
Example:
CASA-CMTS# show running-config
2
show running-config verbose

Example:
CASA-CMTS#show running-config verbose
Display all the default values

of system software
configurations and settings.
Entering and exiting configuration mode

Enter the configuration mode to make changes to configurations and settings. Use the following
commands:
Step
Command
Purpose
config
Enter configuration mode

(config).
Example:
CASA-CMTS#config
CASA-CMTS(config)#
end
Exits configuration mode.
Example:
CASA-CMTS(config)#end
CASA-CMTS#
47
CASA CMTS
Configuring CMTS device contact and location strings

To specify CMTS contact and location information:
Step
1
Command (config)
Purpose
device {contact <string> | location <string>}
Specify the
CMTS device
contact and
location
information
strings.
Where:
<string>
Specifies location and contact information

associated with the CMTS device being managed.
If blank spaces are necessary, enclose the string in
quotation marks, such as (string one).
Example:
CASA-CMTS(config)# device location rack5
CASA-CMTS(config)# device contact Fred Gamble at
978-123-4567
Use the no form

of the command
to delete the
current entries.
Setting security access to the system console

To configure security access to the CMTS system console, use the [no] secure
console command to enable or disable the console protection. When enabled, a secure
console requires a password that matches the password configured in the CMTS
software. Specify only one console password in your configuration.
The console-password and console-password encrypted commands allow you to
specify a secure console password as a normal (viewable as configured) string or as an
encrypted text string when the secure console is enabled.
Use the show running-config command to display the password string. Use the
logout command to end any password-protected console session.
To configure a secure console with password protection:
Step
1
Command (config)
Purpose
[no] secure console
Configure
console security
at the CMTS.
Example:
CASA-CMTS(config)# secure-console
CASA-CMTS(config)# no secure-console
console-password <string>
console-password encrypted <string>
Where:
<string>
Specifies either the normal or encrypted

password string using up to 32 alphanumeric
characters.
Use the no form

of the command
to remove
console security.
Configure either
a normal or
encrypted
password for
CMTS console
access.
48
CASA CMTS
Example:
CASA-CMTS(config# console-password 2b/~2b
CASA-CMTS(config)# console-password encrypted
2b/~2b
Saving the current configuration

When you are making changes to the running configuration, it is important you capture these
changes by executing the copy running-config startup-config command on a frequent basis
during the configuration session. If the CMTS is rebooted during an editing session, your most
recent changes will be lost as the startup configuration file will be applied at the reboot. Channel
up and down state errors may also occur as a result of not saving the configuration.
To save the current running-configuration settings to a storage location for the startupconfiguration settings:
Step
1
Command
copy running-config startup-config [unconditional]
Purpose
Save the current runningconfiguration settings to
a storage location for the
startup-configuration
settings.
If you attempt a copy run start when a module is not in the running state, the following message
is displayed, followed by the prompt:
One or more modules are not in running state. You might lose part of
your startup-config if you save now. You can wait or use 'copy run
start unconditional' to save your config anyway.
You can wait for the module to boot up or you can force the reboot by retyping the command and
adding the unconditional argument.
To store the configuration or changes to your startup configuration in NVRAM, perform the
following:
Step
1
Command
Purpose
copy running-config startup-config
Store the
configuration
or changes to
your startup
configuration
in NVRAM.
Example:
CASA-CMT#copy running-config startup-config
Note: This command operates at the top level of the CLI and in
configuration mode.
Refer to the Managing Configurations section of this guide for additional information on saving,
copying, and restoring CMTS configurations.
49
CASA CMTS
Resetting the IP address

To reset the IP address, log in through the console port and perform the following:
Step
Command
Purpose
Login through the console port
config
Reset the eth 0 IP

address requires
access through the
console port.
Enter configuration
mode.
Example:
CASA-CMTS#config
CASA-CMTS(config)#
interface 0
Example:
CASA-CMTS(config)#interface eth 0
CASA-CMTS(conf-if-eth 0)#
ip address <ip-address> <mask>
Where:
<ip-address>
<mask>
Select the eth 0

interface.
Reset the system

IP address.
IP address in dotted decimal format

A.B.C.D.
The network mask in dotted decimal
notation format ###.###.###.###.
Example:
CASA-CMTS(conf-if-eth 0)#ip address 135.2.2.2
255.255.252.0
Restoring factory defaults

To restore the factory defaults, perform the following:
Step
Command
Purpose
Login as root.
del startup-config
Root permission is required

to reset all defaults.
Delete the current
configuration.
Example:
CASA-CMTS# del startup-config
system reboot
Reboot the system so that

the default configuration is
applied.
50
CASA CMTS
Sample configuration files

This section contains two sample configuration files: basic and general. The basic configuration
allows the CMs to register. The general configuration demonstrates how to configure advanced
features, such as Spectrum Management, Channel Bonding, and Load Balancing.
Basic configuration
The following sample configuration provides basic settings for registering CMs.
hostname CASA-CMTS
interface eth 0
ip address 192.168.2.215 255.255.255.0
interface qam 0/0
no shutdown
power 580
interface qam 0/1
no shutdown
power 580
interface qam 0/2
no shutdown
power 580
interface qam 0/3
no shutdown
power 580
interface gige 0
ip address 192.168.3.106 255.255.255.0
ip igmp
no shutdown
route net 0.0.0.0 0 gw 192.168.3.7
igmp client version 2
51
CASA CMTS
interface upstream 1/0

no shutdown
no logical-channel 0
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
shutdown
shutdown
shutdown
shutdown
shutdown
shutdown
shutdown
shutdown
channel-utilization-interval 10
interface ip-bundle 1
ip address 192.168.7.1 255.255.255.0
cable helper-address 192.168.3.7
interface docsis-mac 1
no shutdown
ip bundle 1
downstream 1 interface qam 0/0/0
upstream 1 interface upstream 1/0/0
General configuration
The following sample configuration includes spectrum management, channel bonding, and loadbalancing configuration.
hostname CASA-CMTS
interface eth 0
ip address 192.168.2.215 255.255.255.0
spectrum rule 35
action modulation frequency channel-width
channel-width 3200000 1600000
snmp traphost 192.168.0.196 community public version 2
interface qam 0/0
no shutdown
52
CASA CMTS
power 580
interface qam 0/1
no shutdown
power 580
interface qam 0/2
no shutdown
power 580
interface qam 0/3
no shutdown
power 580
interface gige 0
ip address 192.168.3.106 255.255.255.0
ip igmp
no shutdown
route net 0.0.0.0 0 gw 192.168.3.7
ip address 192.168.6.1 255.255.255.0
ip address 122.8.74.1 255.255.254.0 secondary
service group 1
qam 0/0/0
qam 0/0/1
qam 0/0/2
qam 0/0/3
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
upstream 1/0/0
upstream 1/1/0
upstream 1/2/0
upstream 1/3/0
upstream 1/4/0
upstream 1/5/0
53
CASA CMTS
upstream 1/6/0
upstream 1/7/0
no shutdown
ip bundle 1
no shutdown
no logical-channel 0 shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
54
CASA CMTS
2 Configuring and managing the CMTS from the CLI

The CASA CMTS system is managed and configured through Casas CLI (Command Line
Interface). The initial configuration of the Casa CMTS is done from a console port. After an IP
address has been assigned to the management port, users can telnet to the system to perform
remote management and configuration.
This chapter covers the following topics:
Managing the system
Configuration:
Managing configurations
Managing NVRAM files
Updating system software
Management ports (Fast Ethernet)
GigE Ethernet, loopback, and trunk interfaces
LACP
PIM-SM
OSPF, RIP, and BGP
Virtual private networks (VPNs and L2VPNs)
TACACS+ and RADIUS AAA
Streams
Downstream QAM ports and upstream port interfaces
Logical upstream channels
MAC domains
IP bundles
Service and bonding groups
Modulation profiles
Multicast operations
Cable service classes
PacketCable
DSG tunnels and tunnel groups
DOCSIS BPI/BPI+
Source Address Verification
Leasequery
Spectrum Management
Load balancing
55
CASA CMTS
Channel bonding
Quality of Service (QoS)
SNMP
IPDR
IPsec
Cable modems
Subscriber management
Configuring MPEG-compliant features
Configuring DVB-compliant Features
Time zone settings
IP access lists
Configuring DOCSIS event notification policy
Logging commands
Managing the system

This section covers commands for the following operations:
Entering and exiting privileged mode
Changing passwords for privileged mode
Resetting passwords from privilege mode to default
Changing the privileged mode system prompt
Entering and ending configuration mode.
Adding user names for Telnet logins
Displaying Telnet user lists
Changing Telnet user passwords
Removing Telnet users
Displaying the current login user list
Removing users from the current login session
Rebooting the system
Rebooting a specified QAM/Upstream Receiver Module
Retrieving the system hardware version
Retrieving the system software version
Retrieving the system boot device
Setting the system clock
Synchronizing the system clock with a network time protocol (NTP) server
Retrieving the system clock
Adding an entry to the network routing table
Removing an entry from the network routing table
56
CASA CMTS
Adding an entry to the host routing table
Removing an entry from the host routing table
Showing alarm states
Showing system logs
Displaying Rapid Spanning Tree Protocol status
Displaying CPU usage information
Displaying memory usage information
Connectivity testing
Entering privileged mode

The Casa CLI supports two operation modes: private and privileged. These modes provide
different levels of access to the Casa CMTS system.
In Private mode, the user has limited access to the system resources, and cannot configure the
system. The default mode is private.
In Privileged mode, you can enter configuration mode and other modes to perform various
configuration tasks. Privileged mode is password-protected.
To enter the Privileged mode, perform the following:
Step
Command
Purpose
CASA-CMTS>
enable
At initial login, the prompt

appears with a > prefix.
Initiates the privileged mode.
Example:
CASA-CMTS> enable
Password: casa
Example:
CASA-CMTS> enable
Password: casa
CASA-CMTS#
Enter privileged mode. Enter the

password at the system prompt.
The default password is casa.
Once the password is accepted,
the prompt changes to # prefix.
Exiting privileged mode

To exit the Privileged mode, use the exit command:
Step
1
Command
Purpose
exit
Exits privileged mode.
Example:
CASA-CMTS# exit
57
CASA CMTS
Changing the privileged mode password

The password for entering privileged mode can be changed when the user is in the privileged
mode.
Step
1
Command
Purpose
password <new_password>
Change the password.
Where:
<new_password>
New password for entering

privileged mode.
Example:
CASA-CMTS# password mypassword
Resetting the privileged mode password to the default setting

You can reset the password for entering privileged mode to the default setting from the console
port only.
Step
1
Command
Purpose
reset password <new_password>
Reset the password.
Where:
<new_password>
New password for entering

privileged mode.
Example:
CASA-CMTS# reset password mypassword
Encrypting passwords
The service password-encryption command enables encryption of MD5 and other passwords,
such as BGP neighbor passwords, RIP, OSPF, and IS-IS protocol authentication passwords on
GigE interfaces. By default, passwords are not encrypted in the CMTS running configuration.
Use the show running-config command to verify the current password encryption setting.
Step
1
Command (config)
Purpose
[no] service password-encryption
Encrypts MD5 or other

passwords.
Example:
CASA-CMTS(config)# service password-encryption
CASA-CMTS#
58
CASA CMTS
Changing the prompt for privileged mode

The default prompt of privileged mode is CASA-CMTS#. This prompt can be changed during an
active session in the privileged mode.
Step
1
Command
Purpose
hostname <string>
Changes the CLI prompt

to the specified string.
Where:
<string>
New CLI prompt to be displayed in privileged

mode.
Example:
CASA-CMTS# hostname host_200
host_200#
Setting up a command alias

The command can be changed into an alias form in order to facilitate the input.
Step
1
Command
Purpose
[no] alias <command-alias> <original-command>
Enables a command
alias.
Where:
<command-alias>
The new command alias string

to apply. If blank spaces are
necessary, enclose the alias
string in quotation marks (such
as alias string).
<original-command>
The Casa command to which

the alias is associated.
Example:
CASA-CMTS# alias au adduser
CASA-CMTS#
CASA-CMTS# no alias au
CASA-CMTS#
59
CASA CMTS
Showing the configured command alias

Step
1
Command
Purpose
show aliases [<command-alias>]
Shows the configured

alias.
Where:
<command- alias>
Optional. The alias as previously

configured.
Example:
CASA-CMTS# show aliases sh
alias sh show
Note: This command operates at the top level of the CLI and
in configuration mode.
Managing configurations and files

Saving a running configuration to the startup configuration
Copying a startup configuration to a file
Restoring the startup configuration to a file in NVRAM
Restoring the startup configuration to the running configuration
Displaying the current running configuration
Displaying the system startup configuration
Saving a running configuration to the startup configuration

When you are making changes to the running configuration, it is important you capture these
changes by executing the copy running-config startup-config command on a frequent basis during
the configuration session. If the CMTS is rebooted during an editing session, your most recent
changes will be lost as the startup configuration file will be applied at the reboot. Channel up and
down state errors may also occur as a result of not saving the configuration.
To save the current running-configuration settings to a storage location for the startupconfiguration settings:
Step
1
Command
copy running-config startup-config [unconditional]
Purpose
Save the current
running-configuration
settings to a storage
location for the
settings.
60
CASA CMTS
If you attempt a copy run start when a module is not in the running state, the following message
is displayed, followed by the prompt:
One or more modules are not in running state. You might lose part of
your startup-config if you save now. You can wait or use 'copy run
start unconditional' to save your config anyway.
You can wait for the module to boot up or you can force the reboot by retyping the command and
adding the unconditional argument.
Copying the startup configuration to a file

To save the current startup-configuration file to a file stored in NVRAM:
Step
1
Command
Purpose
copy nvram startup-config nvram <filename>
Save the current

startupconfiguration file
to a file stored in
NVRAM.
Restoring a startup configuration from a file in NVRAM

To restore a startup configuration from a file in non-volatile NVRAM:
Step
1
Command
Purpose
copy nvram <filename> nvram startup-config
Restore a startup
configuration
from a file in
NVRAM.
Restoring the startup configuration to the running configuration

To load the stored startup-configuration settings to the running-configuration settings (overwriting
current running-configuration settings):
Step
1
Command
Purpose
copy startup-config running-config
Load the stored

settings to the
settings.
61
CASA CMTS
Copying the running configuration to an external location

The copy running-config command allows you to move the CMTS running configuration file to
an external location over FTP or TFTP. Prior to release 6.0, the software only supported copying
the running configuration to the startup configuration, and vice versa.
To copy the running configuration to an external location using FTP:
Step
1
Command
Purpose
copy running-config ftp <userID> <host-ipaddress>

<remote-dir-path>
Copy the running

configuration to a
new location over
FTP.
Where:
<userID>
Specifies the FTP user login ID.
<host-ipaddress>
Specifies the IP address of the FTP

location.
<remote-dir-path>
Specifies the FTP directory path

location and filename.
Example:
CASA-C10G(config)# copy running-config ftp casa
192.168.8.231 /tmp/config.1
Password: *****
To copy the running configuration to an external location using TFTP:

Step
1
Command
Purpose
copy running-config tftp <host-ipaddress>

[<dest-filename>]
Copy the running

configuration to a
new location over
TFTP.
Where:
<host-ipaddress>
Specifies the IP address of the TFTP

location.
<dest-filename>
Specifies the optional TFTP directory

path location and filename.
Example:
CASA-C10G(config)# copy running-config tftp
192.168.8.231 /tmp/config.1
62
CASA CMTS
Copying files over FTP/TFTP

The copy ftp and copy tftp commands allow you to move files from remote locations to CMTS
destinations over FTP and TFTP. Destinations include the Casa C10G fdsk2, C10G SMM slot
number, or to NVRAM.
To copy a source file to an external location over FTP:
Step
1
Command
Purpose
copy ftp <userID> <host-ipaddress> <source_file> fdsk2
Copy files
configuration to a
new location over
FTP.
copy ftp <userID> <host-ipaddress> <source_file> module

<smm_slot> {fdsk2 | nvram}
copy ftp <userID> <host-ipaddress> <source_file> nvram
Where:
<userID>
<host-ipaddress>

location.
<source-file>
Specifies the name of the file at the

CMTS to be copied over FTP to a
destination. Destinations include C10G
flash disk 2 (fdsk2), SMM module slot 6
or 7, or non-volatile RAM (NVRAM).
module
<smm_slot>
Specifies the destination C10G SMM

slot number, either 6 or 7, followed by
the target location, either fdsk2 or
nvram.
Examples:
CASA-C10G(config)# copy ftp casa 192.168.8.192
startup-config fdsk2
Password: *****
startup-config module 6 nvram
startup-config nvram
63
CASA CMTS
To copy a source file to an external location over TFTP:

Step
1
Command
Purpose
copy tftp <host-ipaddress> <source_file> fdsk2

[<dest-filename>]
Copy a file to a
new location over
TFTP.
copy tftp <host-ipaddress> <source_file> module

<smm_slot> {fdsk2 | nvram} [<dest-filename>]
copy ftp <host-ipaddress> <source_file> nvram
[<dest-filename>]
Where:
<host-ipaddress>

location.
<source-file>

CMTS to be copied over FTP to a
destination. Destinations include C10G
flash disk 2 (fdsk2), SMM module slot 6
or 7, or non-volatile RAM (NVRAM).
module
<smm_slot>
Specifies the destination C10G SMM

slot number, either 6 or 7, followed by
the target location, either fdsk2 or
nvram.
<dest-filename>
Specifies the optional TFTP directory

path location and filename.
Examples:
CASA-C10G(config)# copy tftp 192.168.8.192
startup-config fdsk2 /tmp/config.1
CASA-C10G(config)# copy tftp casa 192.168.8.192
startup-config module 6 nvram
CASA-C10G(config)# copy tftp casa 192.168.8.192
startup-config nvram
64
CASA CMTS
Copying files from fdsk2 to destinations over FTP/TFTP

The copy fdsk2 commands allow you to move files from the C10G fdsk2 drive to remote
destination locations over FTP and TFTP. Destinations include the Casa C10G fdsk2, FTP, and
TFTP targets.
To copy the startup-config file to an external location over FTP:
Step
1
Command
Purpose
copy fdsk2 <source_file> ftp <userID> <host-ipaddress>

<remote_directory>
Copy fdsk2 files to

a new location over
FTP or TFTP, or
copy an existing
file to a new name
under fdsk2.
copy fdsk2 <source_file> tftp <host-ipaddress>

[<dest-filename>]
copy fdsk2 <source_file> fdsk2 <dest-filename>
Where:
<userID>
<host-ipaddress

target location.
<source-file>

CMTS fdsk2 drive to be copied to a
remote target.
<dest-filename>
Specifies the filename or full directory

path location and filename to which
the file is sent.
<remote_directory>
Specifies the target directory to which

the current file is sent.
Examples:
CASA-C10G(config)# copy fdsk2 startup-config
ftp casa 192.168.8.192 /tmp
Password: *****
tftp 192.168.8.192 /tmp/startup-config
fdsk2 startup-config.backup
65
CASA CMTS
Displaying fdsk2 directory contents

The dir fdsk2 command lists the directories and files on the C10G fdsk2 drive.
Step
1
Command
Purpose
dir fdsk2
Displaying
the C10G
fdsk2
directory
contents.
Example:
CASA-C10G>
total 2079
-rw-r--r--rw-rw-rw-rw-r--r--rw-r--r--rw-r--r-CASA-C10G>
dir fdsk2
1
1
1
1
1
root
root
root
root
root
root
17538 Nov 4
root
23822 Oct 5
root 1035812 Nov 4
root 1048634 Nov 3
root
1209 Oct 28
13:19
16:04
13:30
15:46
15:24
cdb.log
docsislogfile
logfile
logfile.old
reboot_log
Displaying the running configuration

To display the current running-configuration settings:
Step
1
Command
Purpose
show running-config
Display the current

settings.
Displaying the system startup configuration

To display the system startup-configuration settings:
Step
1
Command
Purpose
show startup-config
Display the system

settings.
Displaying configuration settings within the current context

The show this command displays the configuration settings within the current configuration
context of the CLI. The CMTS integrates the current context within parentheses ( ) at the CLI
prompt.
Step
Command
Purpose
show this
Display the system

startup-conf
Example:
CASA-C10G(config-if-gige 6/1)# show this
interface gige 6/1
ipv6 address 1000::192/64
mpls mtu 0
auto negotiate
no shutdown
66
CASA CMTS
ip router isis EDGE-IPv6

ipv6 router isis EDGE-IPv6
isis network point-to-point
isis circuit-type level-2-only
CASA-C10G(config-if-gige 6/1)#
Managing NVRAM Files

This sub-section covers commands for the following operation:
Listing files in directory

Removing a file from the directory
Copying a file to a remote host
Listing files in the directory

The Casa CMTS supports two equivalent commands: dir (Windows-like) and ls (UNIX-like) to list
files in the directory of NVRAM.
To list files in the directory:
Step
1
Command
Purpose
ls | dir
List files in a
directory.
Example:
CASA-CMTS# dir
Total 9
-rwrr-1 root
1 root
8455 Aug 7 13:44 startup-config
CASA-CMTS#
Removing a file from the directory

The Casa CMTS supports two equivalent commands, del and remove, to remove a file from an
NVRAM directory.
To remove or delete a file from the directory:
Step
1
Command
remove <filename>
del <filename>
Example:
Remove a file from the directory using the remove command:
CASA-CMTS# remove startup-config
Purpose
Remove or
delete a file from
the current
directory.
CASA-CMTS# del startup-config

67
CASA CMTS
Copying a file to a remote host

Files stored in the NVRAM of a Casa CMTS can be saved in a remote host through the TFTP
protocol or FTP protocol.
To copy a file from NVRAM to a remote host:
Step
1
Command
Purpose
copy nvram <source-file-name> tftp <host-ip> <target-filename>
Copy a file
stored in NVRAM
to a remote host.
copy nvram <source-file-name> ftp <ftp-user-id> <host-ip>

<target-file-name>
copy nvram <source-file-name> nvram <target-file-name>
Where:
<source-filename>
Specifies the file name in NVRAM to

be copied.
<host-ip>
Specifies the IP address of the target

host.
<target-file-name>
Species the file name at the host

target.
Example:
Copy startup-config from NVRAM to host 192.168.2.39 as startupconfig-Casa CMTS:
CASA-CMTS# copy nvram startup-config tftp
192.168.2.39 startup-config-Casa
CASA-CMTS#
Updating Casa CMTS software

See the Casa Systems CMTS Release Notes for instructions on installing and upgrading Casa
software images from the Casa TFTP server to the CMTS boot device.
User management and security control

The user management and security control provide the administrative levels for accessing and
modifying aspects of the Casa CMTS. Users may be added, deleted or modified. Users are
assigned a privilege level during creation that may be modified later. The privilege level is a
number from 1 to 15, with 1 being the lowest and 15 the highest level. The users with privilege
level 15 are called super users.
68
CASA CMTS
User management and security control is possible only by super users in enabled mode. The
privilege level of a user determines the access rights of the user to view, monitor, change, and
maintain the configuration of the switch. A super user may perform all possible functions.
The capabilities of a given privilege level is predetermined in the system. The following table
illustrates the capabilities of all privilege levels. The operator can only view information on the
CMTS; this level cannot make changes, reboot the system, or enter diagnostic mode.
The maintenance level can update system information to manage the existing configuration, but
not change configuration information. Maintenance can do firmware upgrade, clock setting,
management and GigE Interface management, and reboot. The video level can manage the
stream and downstream module configurations (edge-QAM management).
The CMTS level can modify the configuration information. Video2 and CMTS2 combine the
configuration privileges with the maintenance privileges. The DCTS level is for DCTS commands
only.
The system administrator can access all commands except diagnostic mode.
Table 2-1. Privilege levels and capabilities
Privilege
Group
Level
1
2
3
4
5
6
Operator
Not Used
Not used
Not used
Not used
Maintenance
7
8
VIDEO
CMTS
9
10
11
12
13
14
15
VIDEO2
CMTS2
DCTS
System Admin
Diagnostics
Not Used
Super user
Capability
Lowest level of operation.
Firmware upgrade, clock, management and GigE

interface management, reboot.
Video stream and downstream configuration.
All upstream, downstream and MAC domain
configuration.
Video and maintenance.
CMTS and maintenance.
DCTS.
All of the above.
Diagnostics.
All privileges.
While user management allows valid users to gain access to the system and maintain the status
of the users, security control governs the specific actions performed by the users.
The user root is a special super user and cannot be deleted. The system will always have the
user root and the password of this user may be changed by a super user. Only a super user can
perform all user management. An exception to this is resetting the password of user root to a
69
CASA CMTS
default password. This operation is permitted only from the console of the switch and maybe
executed by any user. See the section Resetting Privileged Password to Default.
SSH support (Release 5.4 and later)

Only SSH version 2 is supported. SSH clients can be either local users, or authentication server
(TACACS+ or RADIUS) users. SSH Server is enabled by default. A maximum of 64 SSH
sessions can be supported.
The following SSH related CLI commands are available.
Step
Command
Purpose
show ssh server
Show SSH server

information.
Example:
CASA-CMTS# show ssh server
SSH Server Enabled: version 2, port 22
show ssh hostkey fingerprint [rsa | dsa]
Where:
dsa
rsa
DSA key fingerprint.

RSA key fingerprint
Example:
CASA-CMTS# show ssh hostkey fingerprint rsa
2048
fe:61:45:6b:48:3f:9e:19:f3:ce:5d:c8:f6:26:9f:a2
show ssh hostkey {dsa | rsa | fingerprint}
Where:
dsa
rsa
Check the
connected SSH
server (CMTS).
Displays hot key

information.
DSA key.
RSA key.
CMTS ssh server public host key fingerprint.

fingerprint
Example:
CASA-CMTS# show ssh hostkey dsa
---- BEGIN SSH2 PUBLIC KEY ---Comment: "1024-bit DSA, converted from OpenSSH by
root@C3200_155"
AAAAB3NzaC1kc3MAAACBAOFVGDGO85X4Ww4fZyazYXRPnOzj0/0
mMp5FLc7L5ka+W6ksOK
45BSrbVwb4Fk2oCyUJFHUgnfFpSKxSdgVLCeT8VfOSyaLxnLZW7
r2PnLIJnb4ft+sPtBYQ
Tf17uIJ/gE+o4AdqAq3KibUOlf9GyxzF8sVr8LYrsiENltaBLuD
dAAAAFQDWg6//lFi6BI
KUqaC7QjFsc6UXfwAAAIAjgo4/yRUASQi/sk8jL1wjL+kpeBoKi
qMtcsT/6MeTyxfequGf
TybeNxiI+YXI3xPWQKnYFEFr44EBj0pHXBe09hyHoHIHRFRYB55
JdGJDqk57DXiAS5yFFT
70
CASA CMTS
NXF2Griv5mPFvuwA2hnHOVJBucrYLfDZL3+YgKBkov65FyYtssm
AAAAIEAzhzwHRxVsU+v
wgWdTxLnDQEi6//U82ywJdQjVAK6q+daIarwj5I1YIzNFks/cLR
j0ZaBSkBtxoqrjNKdXM
nQFre0rbbAknFWk2fnt9mrisFKAe/T9O7Y72lqcd5reB54/Uioz
E1+WA5+K7oRcdaNKF8V
ph7p/2xn7ZeUxQ35ip0=
---- END SSH2 PUBLIC KEY ---CASA-CMTS# show ssh hostkey dsa
---- BEGIN SSH2 PUBLIC KEY ---Comment: "2048-bit RSA, converted from OpenSSH by
root@C3200_155"
AAAAB3NzaC1yc2EAAAABIwAAAQEArfdT9vRF5UcDc7fyR2Hgt5R
xDHqAsIV5AuFxZxZti8
nAdlmcu6pObu1daGQCYRXUQCWHXuy9Ygi1c2tYRMzTCP3I94hC3
ha4RaWZT2MpjfyL+5ml
5NlKX7lBz3yhLQaeHVVkMTQyVMB8kIDABykkKP3v44BMCvbWYdK
eA6TbjjADneovdbmdHX
tix7XQHDZPhEjYp9PD6tTbCOylp7zzjAcNzZGNG29hH7NECCaS7
jaBEIhe4qPKCTYIg6+E
2AY7koxmxcU8guXV4Zgvku8BJqDyje59+FYZF8N3jWAPIsR1Cp1
Au3ofgtBk2yjQtFcSux
SWzCDTWEH+WdeZfUmaxw==
---- END SSH2 PUBLIC KEY ---C3200_155#
CASA-CMTS# show ssh hostkey fingerprint
2048
ee:b7:aa:9f:c0:6c:69:5e:e0:96:ea:36:ff:d5:e9:d4
4
ssh start [port <2000-65535>]

Where:
<2000-65535>
Port number. The default port number is 22.
Example:
CASA-CMTS# ssh start [port <2000-65535>]
ssh stop
Example:
CASA-CMTS# ssh stop
SSH server stopped.
ssh gen-hostkey {dsa | rsa}
Where:
dsa
rsa
Enable the SSH

server.
Disable the SSH

server.
Replace the
default keys.
DSA key.
RSA key.
Example:
CASA-CMTS# ssh gen-hostkey {dsa | rsa}
71
CASA CMTS
Enabling and disabling SSH

The [no] ssh enable command allows you to control whether SSH sessions are allowed to the
CMTS. If you choose to disable SSH using the no form of the command, copy the running
configuration to the startup configuration and then reboot the CMTS, SSH will then be disabled by
default.
Step
1
Command (config)
Purpose
[no] ssh enable
Enables or
disables SSH
sessions to the
CMTS.
Example:
CASA-CMTS(config)# ssh enable
CASA-CMTS(config)# no ssh enable
Adding Telnet and SSH users

For security, the Casa CMTS allows only specified users to remotely login to the system through
Telnet. The default user name is root, and its password is casa. More users and associated
passwords can be added when user is in the Privileged mode.
Note: The SSH implementation on the Casa CMTS does not support public key authentication.
Step
1
Command
Purpose
adduser <user-name> [privilege <level>]

Enter new password: <password>
Re-enter new password: <password>
Where:
<user-name>
Add Telnet users.
Telnet user-name string.
<password>
User password associated with the user

name.
[privilege <level>]
Optional. If the privilege is not specified, a

default lowest privilege level of 1 is
assumed. The level is a number in the range
1 to 15.
Example:
Add operator as user-name with privilege level 9 and private as
password to Telnet login list:
CASA-CMTS# adduser operator privilege 9
Enter new password: private
Re-enter new password: private
CASA-CMTS#
72
CASA CMTS
Displaying Telnet and SSH users

To see the list of users who are allowed to log in over Telnet or SSH:
Step
1
Command
Purpose
show user [current]
Displays all
registered
users, or
displays the
users who are
currently
logged on to
the CMTS.
Example:
CASA-CMTS# show user
User
Level
----------------------------root
15
metro
15
Supp0rt
10
adrian
10
noct
15
CASA-CMTS# show user current
USER
TTY
TYPE
FROM
SINCE
--------------------------------------------------root
pts/0
ssh
135.244.224.74
Sun Oct 31 13:47:57
2010
henk
pts/1
ssh
135.85.12.131
Sun Oct 31 13:57:57
2010
Changing Telnet and SSH user passwords

To change a Telnet or SSH user password:
Step
1
Command
Purpose
user password <user-name>
Enter new password: <password>

Re-enter new password: <password>
Change user password

for Telnet login.
Where:
<user-name>
Telnet user name string.
<password>
Password associated with the user

name.
Example:
CASA-CMTS# user password operator
Enter new password: public

Re-enter new password: public
CASA-CMTS#
73
CASA CMTS
Note: All user passwords can be changed including the root password.
Removing Telnet or SSH users

To remove a Telnet or SSH user:
Step
1
Command
Purpose
deluser <username>
Remove a user from the

CMTS login list.
Where:
<username>
The configured user name text string.
Example:
CASA-CMTS# deluser operator
CASA-CMTS#
Note: The default user-name root cannot be removed from the configuration.
Removing a logged-in user

To remove a user from the currently logged-in list:
Step
1
Command
Purpose
deluser <user-id> session <term-id>
Remove a user from the

current login list.
Where:
<user-id>
User login ID found under the USER column

in the login list.
<term-id>
Terminal session ID found under the TTY

column of the user login list.
Example:
CASA-CMTS# show user current
USER
TTY
TYPE
FROM
SINCE
---------------------------------------------------------------------root
pts/1
telnet
192.168.2.38
Mon Aug 2 21:28:50 2010
CASA-CMTS# deluser root session pts/0

Connection closed by foreign host.
[user@gollum]$
74
CASA CMTS
Configuring and displaying the Telnet port

The telnet port command sets a user-defined Telnet port over for Telnet sessions to the CMTS.
The default Telnet port is 23 if the port is not modified.
Step
1
Command (config)
Purpose
[no] telnet port <number>
Set a Telnet port for

Telnet sessions to
the CMTS.
Where:
<number>
Specifies a user-defined Telnet port number in the

range 1 to 65535. The default Telnet port is 23.
To remove the
Telnet port, use the
no form.
Example:
CASA-CMTS# config
CASA-CMTS(config)# telnet port 23
CASA-CMTS (config)# show telnet port
telnet port 23
Setting the maximum number of concurrent Telnet session

The line vty command sets the maximum number of concurrent Telnet sessions to the CMTS.
The default setting is 31 session.
Step
Command (config)
Purpose
line vty <number>
Set a maximum
number of
concurrent Telnet
sessions to the
CMTS over the
configured Telnet
port.
Where:
<number>
Specifies a value in the range 1 to 31. The default

number of concurrent sessions is 31.
Example:
CASA-CMTS# config
CASA-CMTS(config)# line vty 12
Configuring Telnet and SSH timeout periods

Termination time for an inactive telnet session is a configurable feature. Default setting is no
time out.
Step
1
Command (config)
Purpose
[no] telnet timeout <minute>
Termination time to
inactivate the Telnet or
SSH session.
Where:
<minute>
The inactive Telnet or SSH session time in
To remove the
75
CASA CMTS
minutes in the range 1 to 1440 minutes.
termination time, use the

no form.
Example:
CASA-CMTS# config
CASA-CMTS(config)# telnet timeout 60
CASA-CMTS# config
CASA-CMTS(config)# no telnet timeout
Rebooting the system

Certain system and error messages occur during system bootup. These messages do not
necessarily indicate a problem with the system. These messages occur during the normal boot
sequence as system processes become active. If the system fails to boot up, then these
messages are meaningful in determining the cause of the problem.
There are several options available to reboot the system. The system may be rebooted right
away without any delay or may be scheduled for a reboot at a later time. All the reboot events are
saved in the system log-file and a reboot message will be broadcast to all CLI shell sessions.
Currently, these commands are available in Release 5.4.
Step
1
Command
Purpose
system reboot [reason <reason-text>] [in <mmm | hhh:mm> [remind

<num=1:60>]]
Reboot
the CMTS.
system reboot [reason <reason-text> [at <mmm | hhh:mm> [remind

<num=1:60> | <day month> [remind <num=1:60>]]
Where:
<reason-text>
Optional text to be displayed before system reboots. If

the text contains any embedded space, then the entire
text should be within quotes.
mmm |
hhh:mm
Reboot the system after a delay specified either by

minutes or hours and minutes.
Specify minutes in the range 0 to 999, a 0 implies
reboot immediately.
Specify hours and minutes in the range 0-168 and 059 respectively.
remind
<num=1:60>
Display reminder message before a scheduled reboot

(specify the time in minutes to send the reminder).
<day month>
Schedule a reboot on a particular day. day is the day

of the month (1-31) and month is the name of the
month (January, February, etc.). When specifying the
month, enter the full name or a partial name as long
76
CASA CMTS
as the name is unique among all other months.

If no day and month are specified and the time
specified has already passed, the reboot is scheduled
for the following day. If the specified time is too far
into the future (more the five weeks), specify the day
and month to be less than five weeks.
Examples:
CASA-CMTS# system reboot reason Use new release
5.4.19.9
CASA-CMTS#system reboot reason test at 22:00 11 December
Broadcast Message from root@CASA-CMTS
(/dev/pts/0) at 11:40 ..
System reboot scheduled for Fri Dec 11 22:00:00 2009

(/dev/pts/0) at 11:40 ..
System reboot reason: test
system reboot cancel
Example:
CASA-CMTS#system reboot cancel
(/dev/pts/0) at 10:00
***
*** ---SHUTDOWN ABORTED--***

show system reboot
Example:
CASA-CMTS#show system reboot
System reboot scheduled for Fri Dec 11 22:00:00 2010 (in
24 minutes, 53 seconds)
Reboot reason: test
Remind: 1 minute before system reboot
CASA-CMTS#
Cancel a
scheduled
or delayed
reboot.
Show a
scheduled
or delayed
reboot.
When a user logs into the system and if a reboot has been scheduled, a message containing the
reboot schedule will be displayed. When a scheduled reboot is cancelled, a cancel message will
be broadcast to all the CLI shell sessions and the event will be recorded in the system log-file.
Enabling a save configuration reminder at reboot

Use system reboot confirm command to instruct the CMTS software to display a save
configuration message to remind you to either save the configuration before a system reboot (in
privileged mode), or to proceed with the reboot without saving the latest configuration.
77
CASA CMTS
When executing the system reboot command, respond to the Save [yes/no]? prompt by typing
yes in lowercase characters to save the configuration, or type no to proceed without saving the
configuration. At the Proceed with reload? prompt, type confirm or press [Enter] to proceed with
the system reboot. To cancel the system reboot, type no at the Proceed with reload? prompt.
Caution: Pressing any key in response to the System configuration has been modified. Save?
prompt will NOT save the configuration prior to confirming the system reboot.
Step
Command
Purpose
system reboot confirm
Instructs the
CMTS software to
present a
reminder to save
the configuration
prior to reboot.
Example:
CASA-CMTS(config)#system reboot confirm
CASA-CMTS#system reboot
System configuration has been modified. Save
[yes/no]? yes
Proceed with reload? {confirm | no} [Enter]
Rebooting a downstream/upstream module

To reboot a downstream/upstream module:
Step
Command
Purpose
reboot module <module>
Reboot a
downstream/upstream
module.
Where:
<module>
QAM/Upstream Receiver module number.
Displaying the system boot device

To display system boot device:
Step
1
Command
Purpose
show bootdev
Show system boot

device.
Examples:
CASA-CMTS# show bootdev
System boot device is: flash1
CASA-CMTS#
78
CASA CMTS
Displaying the system hardware version

To display system hardware version:
Step
1
Command
Purpose
show system
Display the system

hardware version.
Example:
CASA-CMTS# show system
Product: C2200, Module: SMM
Major rev 1, Minor rev 1
serial_no = SV03B17S0016
CFE version 2.1.3
System Time: Sun Apr 12 20:32:40 EST 2009
System Uptime: 0 d, 0 h, 14 m, 49 s
128MHz T1 Clock
Module 1 UPS Running (8 ports, 2 phy
chans/port, 1 log chans/phy chan, scdma map
00)
serial_no = UV30B89S0003
CFE version 2.1.5
Module 2 QAM Running (4 ports, 4
channels/port, 1 banks/port, docsis enabled)
serial_no = QV46B89S0143
CFE version 2.1.3
Displaying the system software version

To display the system software version:
Step
1
Command
Purpose
show version
Display the system

software version.
Example:
CASA-CMTS#show version
Running Image: SMM Rel 5.2, Ver 28, Wed Jun 24
16:09:44 EDT 2009, (moly)
Boot device: flash2
flash1: SMM Rel 5.2, Ver 26B, Fri Jun 5
08:27:11 EDT 2009, ( moly)
flash2: SMM Rel 5.2, Ver 28, Wed Jun 24
16:12:39 EDT 2009, ( moly)
CFE Boot: Major 2, Minor 1, Build 3
79
CASA CMTS
Setting and displaying the system clock

To set the system clock:
Step
1
Command (config)
Purpose
system clock <clock>
Set the system clock.
Where:
<clock>
System clock in the format:

MMDDhhmmYYYY
MM month, DD -- day, hh hour, mm
minute, YYYY-- year.
Example:
CASA-CMTS(config)# system clock 071621082004
Fri Jul 16 21:08:00 UTC 2004
show clock
Display the system

clock.
Example:
CASA-CMTS# show clock
Fri Jul 16 21:08:06 UTC 2004
CASA-CMTS#
Setting and displaying the time zone

To set the time zone:
Step
1
Command (config)
Purpose
system timezone <setting>
Set the timezone

in which the CMTS
is located.
Where:
<setting>
Name of the timezone, such as UTC. Use the

show timezone list command to display the valid
settings. To use the GMT format, the string is:
Etc/GMT + | - <1 through 12>
Example:
CASA-CMTS(config)# system timezone
America/New_York
show timezone [list]
Where:
list
Optional: Displays the full list of valid time zones.
Display the
configured
timezone or the
option list of all
time zones.
Example:
To show the current time zone:
CASA-CMTS(config)# show timezone
80
CASA CMTS
Timezone set to "America/New_York", offset from UTC is -0400

To show all time zones:
CASA-CMTS(config)# show timezone list
Synchronizing the system clock with an NTP server

To synchronize the system clock with a Network Time Protocol (NTP) server:
Step
1
Command (config)
Purpose
ntp {server <server-ip> | scheck | sync <server-ip> | sourceinterface loopback}
Synchronize the
system clock
with an NTP
server.
Where:
<server-ip>
Specifies the IP address of the network time server.
scheck
Enables threshold checking at the NTP daemon.
sync
Synchronizes CMTS time with the specified NTP

server.
sourceinterface
loopback
Specifies the CMTS source interface for NTP client

traffic in the range 0 to 15. A warning message is
returned to the console if the loopback interface has
not yet been configured with an interface number
and IP address under the interface loopback
configuration.
Examples:
CASA-CMTS(config)# ntp server 192.168.4.200
CASA-CMTS(config)# ntp scheck
Restarting NTP server
Stopping NTP server: ntpd
Starting NTP server: ntpd.
CASA-CMTS (config)#
CASA-CMTS(config)# ntp sync 192.168.4.200
1 Nov 10:06:00 ntpdate[10661]:step time server
192.168.4.200 offset 0.075592
Restarting NTP server
Stopping NTP server: ntpd
Starting NTP server: ntpd.
CASA-CMTS(config)# ntp source-interface loopback 5
81
CASA CMTS
Configuring system rate limiting (Rel. 6.0)

The CMTS allows you set packet-per-second (PPS) rate limits that the system will use for Layer 2
destination lookup failure (DLF), broadcast, and multicast packets. Rate limit values are specified
in the range 0 to 4294967295. To disable rate limiting for any of these packet types, specify 0.
The default setting is no rate limiting.
Step
1
Command (config)
Purpose
system rate-limit {broadcast | dlf | multicast}

<0 to 4294967295>
Configure CMTS rate

limiting for specified
packet types in
number of packets
per second.
Where:
broadcast
Specifies rate limiting when the CMTS is

processing broadcast packets.
dlf

processing Layer 2 destination lookup failure
packets.
multicast

processing multicast packets.
<0 to
30000000>
Specifies the rate limit setting in number of

packets per second. The default setting for
all packet types is 500 PPS.
Example:
CASA-CMTS(config)# system rate limit broadcast
500
To disable the current rate limit setting, enter 0.
CASA-CMTS(config)# system rate limit broadcast 0
Configuring an NTP loopback interface

The [no] ntp source-interface loopback command specifies the CMTS source interface for NTP
client traffic.
Note: When configuring loopback settings, a warning message will be returned to the console if
the loopback interface port is not yet configured with the interface loopback command.
Step
1
Command (config)
Purpose
ntp source-interface loopback <interface-number>
Configure the NTP

loopback interface.
Where:
82
CASA CMTS
<interfacenumber>
Specifies the NTP loopback interface

number in the range 0 to 15.
Use the no form of the

command to remove the
current setting.
Example:
CASA-CMTS(config)# ntp source-interface
loopback 4
Adding and removing IPv4 network route entries

To manage IPv4 entries in the network routing table:
Step
1
Command (config)
Purpose
route net <net-ip> <mask-prefix> gw <gw-ip> [<metric_value>]
Add an entry to the

network routing
table.
Where:
Destination network IP address in the
format a.b.c.d.
<net-ip>
<mask- prefix>
IP network mask entered as 8, 16, 24, 32.
<gw- ip>
Gateway IP address in the format a.b.c.d.
[<metric_value>]
Optional. Preferred routing metric value in

the range 1-255 where 1 is most
preferred. The default value is 1.
Use the no form of

the command to
delete the IPv6
route entry.
Example:
CASA-CMTS(config)# route net 193.100.1.0 24 gw
192.168.2.177
CASA-CMTS(config)#
CASA-CMTS(config)# no route net 193.100.1.0 24 gw
192.168.0.177
Adding and removing IPv4 host table entries

To add an IPv4 entry to the host routing table:
Step
1
Command (config)
Purpose
[no] route host <host-ip> gw <gw-ip>
Add an entry to the host

routing table.
Where:
<host-ip>
Destination host IP address in the format

a.b.c.d.

command to delete the
entry from the host table.
83
CASA CMTS
<gw-ip>
Gateway IP address in the format a.b.c.d.
Example:
CASA-CMTS(config)# route host 192.168.10.1 gw
192.168.2.177
CASA-CMTS(config)# no route host 192.168.10.1
gw 192.168.2.177
Adding and removing IPv6 network route entries

To manage IPv6 entries in the network routing table:
Step
1
Command (config)
Purpose
[no] route6 net <ipv6_subnet_address/prefix_length> gw

<ipv6_address>
Add an IPv6 entry

to the network
routing table.
Where:
<ipv6_subnet_address
/prefix_length>
Specifies the destination IPv6

network address with up to eight
16-bit bytes followed by the prefix
length between 0 and 64.
<ipv6_address>
Specifies the gateway IPv6 network

address containing up to eight 16bit bytes in IPv6 standard address
notation.
Use the no form of

the command to
delete the IPv6
route.
Example:
CASA-CMTS(config)# route net
2001.1234.1234.1234::::/64 gw 2001:1234::0
CASA-CMTS(config)#
Displaying the IPv4 and IPv6 routing tables

To display IPv4 and IPv6 routing tables:
Step
1
Command
Purpose
show route
show route6
Display routing table,

either IPv4 or IPv6.
Example:
CASA-CMTS(config)#show route
Kernel IP routing table
Destination Gateway
Genmask
Flags Metric
84
CASA CMTS
Ref Use Iface

192.168.3.0 *
255.255.255.0 U 0 0 0
gige0
192.168.0.0 *
255.255.255.0 U 0 0 0
eth0
10.170.1.0 *
255.255.255.0 U 0 0 0
dmac1
10.121.0.0 192.168.0.135 255.255.0.0 UG 0
0 eth0
default
192.168.0.1 0.0.0.0
UG 0 0 0
eth0
Displaying alarm states

Under normal conditions, this command shows nothing. If there are one or more alarm states, this
command shows one or more alarm states, such as problems with power, fans, temperature, or
modules.
Step
1
Command
Purpose
show alarm
Display alarm status.
Example:
CASA-CMTS# show alarm
Displaying system logs

To show logged system messages:
Step
Command
Purpose
show log
Display logged system

messages.
Example:
CASA-CMTS# show log
[Tue Oct 27 23:53:26 2009]-AL-CLI-1: User user
logged in from 70.168.1.63
[Tue Oct 27 23:53:25 2009]-AL-CLI-1: User root
[Tue Oct 27 23:46:39 2009]-AL-SYS-1: Module 0
(QAM), is up
(UPS), is up
[Tue Oct 27 23:45:57 2009]-AL-CLI-1: User root
(UPS), in boot state
(QAM), in boot state
[Wed Oct 28 07:45:09 2009]-AL-CLI-1: Reboot

85
CASA CMTS
reason: Unspecified
[Wed Oct 28 07:45:09 2009]-AL-CLI-1: User root
Rebooting system
Configuring a log message source IP address

To specify a log message source IP address:
Step
1
Command (config)
Purpose
logging source-interface loopback <lo_id>
Specify a log
message source IP
address.
Where:
<lo-id>
Loopback interface number in the range 0 to 15.
Example:
CASA-CMTS(config)# logging source-interface
loopback <lo_id>
Configuring lawful intercept

The default source address for lawful intercept (LI) is the MAC domain IP address. However, you
can change the source address to the loopback address. The tid stream-id setting creates an
index for target identifiers (TIDs) included in LI packets for selected LI software.
To configure the loopback address as the source and a TID:
Step
1
Command (config)
Purpose
[no] lawful-intercept {source-interface loopback <0-15> |

tid stream-id}
Configure
lawful intercept
interface and a
configurable
TID to support
different
versions of LI
software.
Where:
source-interface
loopback <015>
tid stream-id
Loopback interface ID number in the range

0 to 15. The default source address is the MAC
domain IP address.
Create configurable target identifier to be
included in the lawful intercept packet to support
variations of LI software. By default, the
mediation table index is the TID value.
Note: The default call content connection identifier (CCCID) is the

intercept content ID.
Examples:
CASA-CMTS(config)# lawful-intercept tid stream-id
CASA_CMTS (config)# lawful-intercept sourceinterface loopback 0
86
CASA CMTS
Displaying Rapid Spanning Tree Protocol status

The Casa CMTS supports Rapid Spanning Tree Protocol (RSTP). RSTP provides fault tolerance
by automatically reconfiguring the spanning tree topology as a result of:
Bridge failure
Breakdown in a data path within the confines of the available Bridge LAN components
Automatic accommodation of any bridge port added to the Bridge LAN without the formation
of transient data loop.
To display RSTP status on bridge LAN components:

Step
1
Command
Purpose
show rstp bridge
Display RSTP status on

bridge LAN components
Example:
CASA-CMTS# show rstp bridge
To display RSTP status on GigE ports:
Step
1
Command
Purpose
show rstp port [<port-id>]
Display RSTP status on

GigE ports.
Where:
<port-id>
GigE port id, values are 0 to 11 for C3200 and

C10200 systems; 0 to 3 for the C2200. If
<port-id> is not specified, status of all GigE
ports will be displayed.
Example:
CASA-CMTS# show rstp port [<port-id>]
Displaying ARP entries

To display ARP entries in the system:
Step
Command
Purpose
show arp
Display ARP entries in

the system.
Example:
CASA-CMTS# show arp
Address
Age Hardware Addr
Interface
192.168.2.38
ARPA eth 0
192.168.2.39
State
Type
00:00:00 00c0.9f24.bfee
dynamic
00:19:03 000c.f1a6.36e8
dynamic
87
CASA CMTS
ARPA eth 0
192.168.2.114 00:14:18 000d.5663.d756
dynamic ARPA eth 0
192.168.2.238 00:10:00 0050.c231.c013 static
ARPA eth 0
192.168.3.6 00:10:00 0009.5bbd.b87e dynamic
ARPA Gige 0
192.168.3.131 00:00:00 0050.c231.c03b static
ARPA Gige 0
192.169.4.4 00:18:19 0050.c231.c03f static
ARPA CATV-MAC 1
192.169.4.120 00:00:48 0011.1ac8.326e
dynamic ARPA CATV-MAC 1
192.169.4.121 00:00:51 0016.b560.aef8
dynamic ARPA CATV-MAC 1
Configuring the ARP request interval

CMTS sends an ARP request to every CM and CPE periodically. To set ARP request period:
Step
1
Command (config)
Purpose
arp request-interval <interval>
Set the ARP

request period.
Where:
<interval>
The length of the ARP request period in unit

of second. Values are 0 to 28800. 0 stands
for infinite period. Otherwise, the longest
period is 8 hours (28800 seconds) and
shortest time is 10 seconds.
Example:
CASA-CMTS(config)# arp request-interval 2000
Note: The CMTS will round the ARP request interval from 1 to
9 seconds to 10 seconds. The default setting is 30 seconds. If
the CMTS does not receive an ARP response from a CM or
CPE in 6 * ARP request interval seconds, the CM or CPE is
ARP timed out, and the CMTS will remove the ARP entry for
the CM or CPE.
Configuring ARP packet filtering

To set number of ARP response packets to accept from the CM and CPE in a configured time
window (in seconds):
Step
1
Command (config)
Purpose
[no] cable arp filter <number> <seconds>
Set the number of ARP

packets to accept within
88
CASA CMTS
Where:
<number>
<seconds>
A value in the range 0 to 20 to specify the

maximum number of ARP response packets
to accept from the CM or CPE within the
specified time window. The default setting is
8 ARP packets.
the specified time

window.
command to revert to the
default settings.
The number of seconds in the range 2 to 5

to specify the time window for accepting
ARP packets from the CM or CPE. The
default is 2 seconds.
Example:
CASA-CMTS(config)# cable arp filter 5 2
Clearing an entry in the ARP cache

To clear the entire ARP cache on both the network and cables sides of the CMTS, use the clear
arp-cache all command.
The clear arp-cache command also supports the asterisk (*) wildcard when selectively clearing
IP addresses from the ARP cache. The software will stop scanning when the first asterisk is
detected in the IP address.
To clear an entry in the ARP cache:
Step
1
Command
Purpose
clear arp-cache {all | <ip-address>}
Clears an entry in
the ARP cache.
Where:
<ip-address>
The ARP cache IP address in the format

a.b.c.d.?
Example:
CASA-CMTS# clear arp-cache all
CASA-CMTS# clear arp-cache 192.168.2.177
CASA(config)# clear arp-cache 192.*.*.*
CASA(config)# clear arp-cache 10.223.*.*
89
CASA CMTS
Displaying the ARP request interval

To display ARP request interval at the CMTS:
Step Command
1
show arp request-interval
Purpose
Display ARP request
interval at the CMTS
Example:
CASA-CMTS# show arp request-interval
Enabling and disabling the ARP timeout reset

When a CM is timed out, the CMTS may reset the CM. To enable or disable the CM reset feature:
Step
1
Command (config)
Purpose
[no] arp timeout-cm-reset
Enable or disable CM
reset feature.
Example:
CASA-CMTS(config)# arp timeout-cm-reset
Disable the feature:
CASA-CMTS(config)# no arp timeout-cm-reset
Displaying IPv6 information

To display information about IPv6:
Step
1
Command
Purpose
show ipv6 route
Display information
about IPv6.
Example:
CASA-CMTS# show ipv6 route
|
Output modifiers
<cr>
<ipv6_addr>
xxxx:xxxx:...:xxxx
<netv6_addr>
xxxx:xxxx:...:xxxx/mask_len
bgp
show ipv6 route bgp
connected
show ipv6 route connected
isis
show ipv6 route isis
kernel
show ipv6 route kernel
ospf
show ipv6 route ospf
rip
show ipv6 route rip
static
show ipv6 route static
supernets-only
supernets-only
90
CASA CMTS
To display the IPv6 route advertisement table:

Step Command
1
show router-advertisement
Purpose
Display the IPv6 route
advertisement table.
Example:
CASA-CMTS# show router-advertisement
To display the IPv6 route table:
Step Command
1
show route6
Purpose
Display the IPv6 route
table.
Example:
CASA-CMTS# show route6
Displaying the ARP timeout reset configuration

Step
1
Command
Purpose
show arp timeout-cm-reset
Display the ARP timeout

reset configuration at the
CMTS.
Example:
CASA-CMTS# show arp timeout-cm-reset
Displaying CPU usage

To display CPU usage of the SMM module:
Step
1
Command
Purpose
show cpuinfo
Display CPU usage at

the SMM module.
Example:
CASA-CMTS# show cpuinfo
To display CPU usage of a line card module:

Step
1
Command
Purpose
show cpuinfo module <id>
Display CPU usage of a

line card module
Where:
<id>
Module ID for line cards.
Example:
CASA-CMTS# show cpuinfo module 0
91
CASA CMTS
Module 0:
cpu model
SiByte SB1 V0.3 FPU V0.3
BogoMIPS
532.48
microsecond timers yes
tlb_entries
64
11:01pm up 20 min, 0 users, load average:
0.13, 0.07, 0.01
44 processes: 43 sleeping, 1 running, 0
zombie, 0 stopped
CPU states: 2.3% user, 1.4% system, 0.0% nice,
96.3% idle
Mem: 245352K total, 192896K used, 52456K free,
500K buffers
CASA-CMTS#
To display CPU usage of all modules:
Step
1
Command
Purpose
show cpuinfo all
Display CPU usage of all

modules.
Example:
See example below.
Example: show cpuinfo all

CASA-CMTS# show cpuinfo all
SMM:
cpu model
BogoMIPS
265.42
tlb_entries
64
5:28pm up 1:24, 1 user, load average: 0.00, 0.00, 0.00
106 processes: 104 sleeping, 1 running, 1 zombie, 0 stopped
CPU states: 0.1% user, 0.7% system, 0.0% nice, 99.2% idle
Mem: 231684K total, 137320K used, 94364K free, 1004K buffers
Module 0:
cpu model
BogoMIPS
532.48
tlb_entries
64
5:28pm up 1:24, 0 users, load average: 0.02, 0.04, 0.00
Module 1:
cpu model
BogoMIPS
265.42
tlb_entries
64
5:28pm up 1:24, 0 users, load average: 0.21, 0.31, 0.28
92
CASA CMTS

Displaying memory usage

To display memory usage at the SMM module:
Step
1
Command
Purpose
show meminfo
Display memory usage

at the SMM module
Example:
CASA-CMTS# show meminfo
To display memory usage of a line card module:

Step
1
Command
Purpose
show meminfo module <id>

of a line card module
Where:
<id>
Module ID for line cards.
Example:
CASA-CMTS# show meminfo module 0
Module 0:
MemTotal:
245352 kB
MemFree :
52672 kB
CASA-CMTS#
To display memory usage of all modules:
Step
1
Command
Purpose
show meminfo all

of all modules.
Example:
CASA-CMTS# show meminfo all
SMM:
MemTotal:
231684 kB
MemFree:
94524 kB
Module 0:
MemTotal:
245352 kB
MemFree :
52672 kB
Module 1:
MemTotal:
245356 kB
MemFree :
105528 kB
CASA-CMTS#
93
CASA CMTS
Monitoring line card status

When enabled, line cards periodically send "keep-alive" ping packets to the SMM. If a line card is
determined to be hung, or down, the line card will be automatically reset. It is strongly
recommended to enable this feature. The default setting is enabled.
Step
1
Command (config)
Purpose
[no] monitor keepalive
Enable or disable linecard monitoring.
Example:
CASA-CMTS(config)# monitor keepalive
Disable monitoring:
CASA-CMTS(config)# no monitor keepalive
Monitoring Gigabit Ethernet interfaces

When enabled, the system periodically checks the activity of the GigE interfaces. If they are idle
for an excessive period of time, an automatic shutdown is performed.
Step
Command (config)
Purpose
[no] monitor gige
Enable GigE monitoring.
Example:
CASA-CMTS(config)# monitor gige
Disable monitoring:
CASA-CMTS(config)# no monitor gige
Displaying the current monitor settings (Rel. 6.0 and later)

The show monitor command allows you to display the enabled/disabled status for watching
GigE network activity, module keepalives, and the CMTS line card processes.
Step
Command (config)
Purpose
show monitor
Display the current

monitor status.
Example:
CASA-CMTS(config)# show monitor
Monitor GIG-E activity :
Monitor Keepalive
:
Monitor Daemon
:
Disabled
Disabled
Enabled
94
CASA CMTS
Enabling auto-reboot mode (5.2)

The CMTS supports auto-reboot mode. If it does not detect a response from a defined IP address
(usually the default gateway), after the specified number of consecutive pings (60 seconds) it will
collect system information and reboot automatically. A response will reset the timer to 0. The
command can be saved to the start-up configuration.
Step
1
Command (config)
Purpose
auto-reboot monitor <ip-address> [retries]
Enable GigE monitoring.
Where:
<ip-address>
[retries]
IP address to ping.
The number of consecutive pings before
reboot. The default is 30 (60 seconds).
Example:
CASA-CMTS(config)#auto-reboot monitor
192.168.2.177 30
Note: This command is available in 5.4, but it is not persistent and it cannot be saved in the
start-up configuration
Using the Ping and Ping6 commands

The Casa CMTS supports the ping and ping6 commands to test connectivity to an IP address.
Step
1
Command (config)
Purpose
ping
ping6
Run the
extended ping
command.
Example:
In the following example, a ping request is sent to IP address
192.168.8.113.
CASA-CMTS(conf-if-vlan 6/10)#ping 192.168.8.113
PING 192.168.8.113 (192.168.8.113) 56(84) bytes of
data.
64 bytes from 192.168.8.113: icmp_seq=1 ttl=64
time=0.102 ms
time=0.067 ms
time=0.082 ms
--- 192.168.8.113 ping statistics --3 packets transmitted, 3 received, 0% packet loss,
time 2000ms
95
CASA CMTS
rtt min/avg/max/mdev = 0.067/0.083/0.102/0.017 ms

CASA-CMTS(conf-if-vlan 6/10)#
In the following example, a ping request is sent to an IPv6 address.
CASA-CMTS(conf-if-vlan 6/10)# ping
2001:0db8:85a3:0000:0000:8a2e:0370:7334
Testing connectivity with extended Ping

The Casa CMTS supports the extended ping command. Enclose Linux arguments in quotations.
Step
1
Command (config)
Purpose
ping
ping6
Run the extended ping

command.
Example:
In the following example, 192.168.3.8 is a host on the gige
side and 10.248.1.1 is the IP-bundle interface. Consult the
Linux documentation for additional arguments.
CASA-CMTS#ping "-I 10.248.1.1 192.168.3.8"
PING 192.168.3.8 (192.168.3.8) from 10.248.1.1
: 56(84) bytes of data.
time=0.357 ms
time=0.372 ms
time=0.361 ms
Using the traceroute command (Rel. 6.0)

The traceroute command, previously only available in the CMTS diagnostic mode, now operates
at the top-level of the CLI. Use the traceroute command to show all IP address hops that make
up a route to a destination IP, the time in milliseconds to traverse each hop.
96
CASA CMTS
Step
1
Command
Purpose
traceroute <ip_address>
Trace the
number of IP
hops to a
destination IP
device.
traceroute help
traceroute "[ -dFInrvx ] [ -f first_ttl ] [ -g gateway] [ -i iface ] [ -m
max_ttl ] [ -p port ] [ -q nqueries ] " [ -s src_addr] [ -t tos ][ -w
waittime ] [ -z pausemsecs ] host [ packetlen ]"
Where:
<ip-address>
Specifies the destination IP address to which a

route is traced. A network mask is not used.
help
Specifies the traceroute command options that

you can provide on the command line.
-d
Enables socket level debugging.
-f
Sets the "Don't Fragment" bit.
-I
Use ICMP ECHO for probes.
-n
Do not try to map IP addresses to host names

when displaying them.
-r
Bypassed the normal routing tables and sends

directly to a host on an attached network. If the
host is not on a directly-attached network, an error
is returned. This option can be used to ping a
local host through an interface that has no route
through it.
-v
Verbose output. Received ICMP packets other

than TIME_EXCEEDED and UNREACHABLEs
are listed.
-x
Toggles IP checksums. Normally, this prevents

traceroute from calculating IP checksums. In
some cases, the operating system can overwrite
parts of the outgoing packet but not recalculate
the checksum (so in some cases the default is to
not calculate checksums and using x causes
them to be calculated). Note that checksums are
usually required for the last hop when using ICMP
ECHO probes ( -I ). So they are always calculated
when using ICMP.
-f first_ttl
Specifies with what TTL to start. Defaults to 1.
-g gateway
Tells traceroute to add an IP source routing option

to the outgoing packet that tells the network to
route the packet through the specified gateway.
Not very useful because most routers have
disabled source routing for security reasons
i iface
Specifies the interface through which traceroute

should send packets. By default, the interface is
97
CASA CMTS
selected according to the routing table.

-m max_ttl
Specifies the maximum number of hops (max

time-to-live value) traceroute will probe. The
default is 30.
-p port
For UDP tracing, specifies the destination port

base traceroute will use (the destination port
number will be incremented by each probe).
-q nqueries
Sets the number of probe packets per hop. The

default is 3
-s src_addr
Chooses an alternative source address. Note that

you must select the address of one of the
interfaces. By default, the address of the outgoing
interface is used.
-t tos
For IPv4, set the Type of Service (TOS) and

Precedence value. Useful values are 16 (low
delay) and 8 (high throughput). Note that in order
to use some TOS precendence values, you have
to be super user.
-w waittime
Set the time (in seconds) to wait for a response to

a probe (default 5.0 sec.).
-z pausemsec
Minimal time interval between probes (default 0).

If the value is more than 10, then it specifies a
number in milliseconds, else it is a number of
seconds (float point values allowed too). Useful
when some routers use rate-limit for ICMP
messages.
host
Specifies a host name or IP address.
packetlen
The default probe datagram length is 40 bytes,

but this may be increased by specifying a packet
size (in bytes) after the destination host name.
Example:
C10G-CMTS# traceroute 192.168.3.195
*****
Type Ctrl-C to exit
*****
traceroute to 192.168.3.195 (192.168.3.195), 30 hops
max, 40 byte pac
1 192.168.10.110 (192.168.10.110) 2.111 ms 2.228
ms 2.147 ms
2 192.168.20.108 (192.168.20.108) 1.241 ms 0.904
ms 0.948 ms
3 192.168.3.195 (192.168.3.195)
1.165 ms 1.218 ms 1.150 ms
C10G-CMTS# traceroute help
Usage: traceroute [ -dFInrvx ] [ -f first_ttl ] [ -g
gateway ]
[ -i iface ] [ -m max_ttl ] [ -p port ] [ -q
98
CASA CMTS
nqueries ]
[ -s src_addr ] [ -t tos ] [ -w waittime ] [
-z pausemsecs ] host [ packetlen ]
The entire argument list must be with quotation marks
Example: traceroute "pluto"
C10G-CMTS# traceroute 192.168.3.192 1500
*****
Type Ctrl-C to exit
*****
traceroute to 192.168.8.230 (192.168.8.230), 30 hops
max, 1500 byte packets
1 192.168.8.230 (192.168.8.230) 1.624 ms 0.943 ms
0.748 ms
Example output:
traceroute to verizon.net (206.46.232.39), 30 hops max, 40 byte packets
1 192.168.2.1 (192.168.2.1) 0.564 ms 0.438 ms 0.402 ms
2 192.168.1.1 (192.168.1.1) 1.724 ms 1.482 ms 1.334 ms
3 192.168.0.1 (192.168.0.1) 3.573 ms 3.308 ms 3.400 ms
4 209.101.35.209 (209.101.35.209) 4.334 ms * 4.179 ms
5 208-41-205-1.client.dsl.net (208.41.205.1) 20.577 ms 16.912 ms 19.954 ms
6 ge-2-2-0.c00.nyc.megapath.net (155.229.123.121) 19.863 ms 17.526 ms
19.568 ms
7 ge-6-5.car1.NewYork1.Level3.net (209.246.126.1) 19.946 ms 17.224 ms
19.897 ms
8 vlan69.csw1.NewYork1.Level3.net (4.68.16.62) 19.893 ms 17.967 ms 19.767
ms
9 ae-64-64.ebr4.NewYork1.Level3.net (4.69.134.113) 24.904 ms 22.647 ms *
10 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 19.224 ms 17.346 ms 19.626
ms
11 ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227) 23.098 ms 17.541 ms ae1-51.edge2.NewYork2.Level3.net (4.69.138.195) 25.399 ms
12 0.ge-2-0-0.BR3.NYC4.ALTER.NET (204.255.173.53) 17.668 ms mci-level3xe.newyork2.Level3.net (4.68.110.234) 17.970 ms mci-level3xe.newyork2.Level3.net (4.68.110.106) 57.640 ms
13 0.xe-0-1-3.XL3.NYC4.ALTER.NET (152.63.17.58) 18.088 ms 0.xe-5-03.XL3.NYC4.ALTER.NET (152.63.18.6) 17.976 ms 0.xe-5-1-3.XL3.NYC4.ALTER.NET
(152.63.16.182) 19.120 ms
14 0.ge-7-2-0.XL3.DFW7.ALTER.NET (152.63.0.34) 102.254 ms 101.897 ms
104.069 ms
15 POS7-0.GW2.DFW13.ALTER.NET (152.63.103.229) 103.922 ms POS60.GW2.DFW13.ALTER.NET (152.63.103.225) 102.292 ms 101.520 ms
16 verizon-gw.customer.alter.net (63.65.122.26) 104.015 ms 102.131 ms
103.928 ms
17 po121.ctn-core1.vzlink.com (206.46.225.18) 114.777 ms 101.656 ms 103.760
ms
18 206.46.228.130 (206.46.228.130) 104.236 ms 101.775 ms 104.338 ms
19 206.46.232.34 (206.46.232.34) 103.508 ms 102.530 ms 103.747 ms
99
CASA CMTS
Configuring ICMP packet filtering

To set number of ICMP response packets to accept from the CM and CPE in a configured time
Step
1
Command (config)
Purpose
[no] cable icmp filter <number> <seconds>
Set the number of ICMP

the specified time
window.
Where:
<number>
<seconds>

maximum number of ICMP response
packets to accept from the CM or CPE within
the specified time window. The default
setting is 0 ICMP packets, or no filtering.

default settings.

ICMP packets from the CM or CPE. The
Example:
CASA-CMTS(config)# cable icmp filter 100 2
Configuring DHCP packet filtering

To set number of DHCP response packets to accept from the CM and CPE in a configured time
Step
1
Command (config)
Purpose
[no] cable dhcp filter <number> <seconds>
Set the number of DHCP

the specified time
window.
Where:
<number>
<seconds>

maximum number of ICMP response
setting is 0 DHCP packets, or no filtering.

default settings.

DHCP packets from the CM or CPE. The
Example:
CASA-CMTS(config)# cable dhcp filter 100 2
100
CASA CMTS
Displaying all filtering settings in the running configuration

To display all filtering settings from the running CMTS configuration:
Step
1
Command (config)
Purpose
show cable filter running-config
Display the filter settings

from the running
configuration.
Example:
CASA-C3000(config)#show cable filter runningconfig
cable arp filter 8 2
cable dhcp filter 100 2
cable icmp filter 0 2
cable igmp filter 4 2
CASA-C3000(config)#
Setting channel utilization intervals

To set the channel utilization interval (the interval over which the channel utilization information is
collected and averaged):
Step
1
Command (config)
Purpose
channel-utilization-interval <0-86400>
Set the channel

utilization interval in
seconds.
Where:
<0-86400>
The utilization interval in seconds. The

default is 30 seconds. Setting this value to
0 turns off utilization collection. It is not
advisable to use a value lower than 10 in
an operational system.
Example:
CMTS(config)# channel-utilization-interval 100
Displaying channel utilization

To see the utilization on all channels:
Step
1
Command
Purpose
show docsis channel utilization
Show the utilization on

all channels
Example:
CMTS(config)# show docsis channel utilization
101
CASA CMTS
Example: Display channel utilization

Downstream
Operational Utilization Online Secondary Channel
Slot/Port/Channel
Status
Percentage Modems Modems
Description
----------------------------------------------------------------------------0/0/0 (549000000 Hz)
down
0
0
0
0/0/1 (555000000 Hz)
down
0
0
0
0/0/2 (561000000 Hz)
down
0
0
0
0/0/3 (567000000 Hz)
down
0
0
0
0/1/0 (549000000 Hz)
down
0
0
0
0/1/1 (555000000 Hz)
down
0
0
0
0/1/2 (561000000 Hz)
down
0
0
0
0/1/3 (567000000 Hz)
down
0
0
0
0/2/0 (549000000 Hz)
down
0
0
0
0/2/1 (555000000 Hz)
down
0
0
0
0/2/2 (561000000 Hz)
down
0
0
0
0/2/3 (567000000 Hz)
down
0
0
0
0/3/0 (549000000 Hz)
down
0
0
0
0/3/1 (555000000 Hz)
down
0
0
0
0/3/2 (561000000 Hz)
down
0
0
0
0/3/3 (567000000 Hz)
down
0
0
0
1/0/0 (549000000 Hz)
down
0
0
0
1/0/1 (555000000 Hz)
down
0
0
0
1/0/2 (561000000 Hz)
down
0
0
0
1/0/3 (567000000 Hz)
down
0
0
0
1/1/0 (549000000 Hz)
down
0
0
0
1/1/1 (555000000 Hz)
down
0
0
0
1/1/2 (561000000 Hz)
down
0
0
0
1/1/3 (567000000 Hz)
down
0
0
0
1/2/0 (549000000 Hz)
down
0
0
0
1/2/1 (555000000 Hz)
down
0
0
0
1/2/2 (561000000 Hz)
down
0
0
0
1/2/3 (567000000 Hz)
down
0
0
0
1/3/0 (549000000 Hz)
down
0
0
0
1/3/1 (555000000 Hz)
down
0
0
0
1/3/2 (561000000 Hz)
down
0
0
0
1/3/3 (567000000 Hz)
down
0
0
0
2/0/0 (549000000 Hz)
down
0
0
0
2/0/1 (555000000 Hz)
down
0
0
0
2/0/2 (561000000 Hz)
down
0
0
0
2/0/3 (567000000 Hz)
down
0
0
0
2/1/0 (549000000 Hz)
down
0
0
0
2/1/1 (555000000 Hz)
down
0
0
0
2/1/2 (561000000 Hz)
down
0
0
0
2/1/3 (567000000 Hz)
down
0
0
0
2/2/0 (549000000 Hz)
down
0
0
0
2/2/1 (555000000 Hz)
down
0
0
0
2/2/2 (561000000 Hz)
down
0
0
0
2/2/3 (567000000 Hz)
down
0
0
0
2/3/0 (549000000 Hz)
down
0
0
0
2/3/1 (555000000 Hz)
down
0
0
0
2/3/2 (561000000 Hz)
down
0
0
0
2/3/3 (567000000 Hz)
down
0
0
0
3/0.0 (20000000 Hz)
down
0
0
0
3/0.1 (20000000 Hz)
down
0
0
0
3/1.0 (20000000 Hz)
down
0
0
0
3/1.1 (20000000 Hz)
down
0
0
0
3/2.0 (20000000 Hz)
down
0
0
0
3/2.1 (20000000 Hz)
down
0
0
0
3/3.0 (20000000 Hz)
down
0
0
0
3/3.1 (20000000 Hz)
down
0
0
0
3/4.0 (20000000 Hz)
down
0
0
0
102
CASA CMTS
3/4.1
3/5.0
3/5.1
3/6.0
3/6.1
3/7.0
3/7.1
4/0.0
4/0.1
4/1.0
4/1.1
4/2.0
4/2.1
4/3.0
4/3.1
4/4.0
4/4.1
4/5.0
4/5.1
4/6.0
4/6.1
4/7.0
4/7.1
5/0.0
5/0.1
5/1.0
5/1.1
5/2.0
5/2.1
5/3.0
5/3.1
5/4.0
5/4.1
5/5.0
5/5.1
5/6.0
5/6.1
5/7.0
5/7.1
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
(20000000
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Displaying upstream channel utilization

To display the utilization on all upstream channels:
Step
1
Command (config)
Purpose

upstream channels
Example:
CMTS(config)# show docsis upstream channel
utilization
Example: Display upstream channel utilization

Upstream
Slot/Port.Channel
Operational
Status
Utilization Online Secondary Channel

Description
103
CASA CMTS
------------------------------------------------------------------------------2/0.0 (18000000 Hz)

up
0
1
4
Certification
2/0.1 (20000000 Hz)
down
0
0
0
2/1.0 (25000000 Hz)
up
0
8
3
2/1.1 (20000000 Hz)
down
0
0
0
2/2.0 (32000000 Hz)
up
2
7
4
2/2.1 (20000000 Hz)
down
0
0
0
2/3.0 (11000000 Hz)
up
0
4
3
2/3.1 (20000000 Hz)
down
0
0
0
2/4.0 (16000000 Hz)
up
0
0
0
2/4.1 (20000000 Hz)
down
0
0
0
2/5.0 (20000000 Hz)
up
0
0
0
2/5.1 (20000000 Hz)
down
0
0
0
2/6.0 ( 8000000 Hz)
down
0
0
0
docsis
2/6.1 (20000000 Hz)
down
0
0
0
2/7.0 (32000000 Hz)
down
0
0
0
2/7.1 (20000000 Hz)
down
0
0
0
4/0.0 (32600000 Hz)
up
0
0
0
4/0.1 (34200000 Hz)
up
0
0
0
4/1.0 (35800000 Hz)
up
0
0
0
4/1.1 (37400000 Hz)
up
0
0
0
Displaying downstream channel utilization

To see the utilization on all downstream channels:
Step
1
Command
Purpose

all downstream channels
Example:
CMTS(config)# show docsis downstream channel
utilization
Example: Display downstream channel utilization

Downstream
Operational Utilization Online Secondary Channel
Slot/Port/Channel
Status
Description
----------------------------------------------------------------------------0/0/0 (525000000 Hz)
up
0
0
5
testing
0/0/1 (531000000 Hz)
up
0
0
5
0/0/2 (537000000 Hz)
up
0
0
5
0/0/3 (543000000 Hz)
up
0
0
5
0/1/0 (465000000 Hz)
up
0
0
0
0/1/1 (471000000 Hz)
up
0
0
0
0/1/2 (477000000 Hz)
up
0
0
0
0/1/3 (483000000 Hz)
up
0
0
0
0/2/0 ( 47000000 Hz)
down
0
0
0
Certification
0/2/1 ( 53000000 Hz)
down
0
0
0
Rotterdam 5
0/2/2 ( 59000000 Hz)
down
0
0
0
104
CASA CMTS
0/2/3
0/3/0
0/3/1
0/3/2
0/3/3
1/0/0
1/0/1
1/0/2
1/0/3
1/1/0
1/1/1
1/1/2
1/1/3
1/2/0
1/2/1
1/2/2
1/2/3
1/3/0
1/3/1
1/3/2
1/3/3
( 65000000
(549000000
(555000000
(561000000
(567000000
(129000000
(135000000
(141000000
(147000000
(549000000
(555000000
(561000000
(567000000
(549000000
(555000000
(561000000
(567000000
(549000000
(555000000
(561000000
(567000000
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
Hz)
down
up
up
up
up
down
up
up
up
down
down
down
down
down
down
down
down
up
up
up
up
0
0
4
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
20
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
6
0
6
6
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
testing
casacasa
Configuring the system monitor (Release 5.4 and later)

The following parameters can be monitored:
cpu
Set CPU monitor.
fan
Set fan monitor.
memory
Set memory monitor.
power
Set power monitor.
temperature
Set temperature monitor
To enable or disable the monitors:

Step
1
Command (config)
Purpose
system monitor <unit> enable | disable
Enable or disable the

system monitor.
Where:
<unit>
CPU, fan, memory, power, or temperature
Example:
CASA-CMTS(config)#system monitor cpu enable
105
CASA CMTS
In addition, the CPU and memory usage thresholds can be defined in each module. To configure
the CPU monitor:
Step
1
Command (config)
Purpose
system monitor cpu <num> threshold <pct>
Configure the CPU

monitor.
Where:
<num>
<pct>
Slot number of the module (enter smm for the

Switch and Management module.
Percentage of idle time to trigger a notification.
Note: The CPU and memory usage thresholds can be
defined in each module.

To configure the memory monitor:
Step
Command
Purpose
system monitor memory <num> threshold <amt>
Configure the
memory monitor.
Where:
<num>
<amt>
Slot number of the module. Enter smm for the

Switch and Management Module.
Amount of memory used in the range (1 to 512 MB).
Configuring the management port

The management port allows the user to configure the system over an IP network. The Casa
CMTS provides a separate Fast Ethernet management ports. After configuration, the user can
use either the Fast Ethernet port or the gige port to manage the system remotely. This section
covers commands for the setting the Fast Ethernet port as the management port.
Setting the Fast Ethernet port as the management port

To set fast Ethernet port as the management port:
Step 1.
Step 2.
Step 3.
Step 4.
Enter configuration mode.

Enter fast Ethernet interface mode.
Set an IP address to the interface.
Exit from the interface.
The fast Ethernet interface has a default IP address and subnet mask: 192.168.2.100
255.255.255.0. The commands are:
106
CASA CMTS
Step
Command (config)
Purpose
interface <eth-port>
Enter fast Ethernet

interface mode.
Where:
<ethport>
ethernet port
Example:
CASA-CMTS(config)# interface eth 0
2
[no] ip address <ip-address> <subnet-mask>

Where:
<ip-address>
<subnet-mask>
Set the fast Ethernet port

as the management port.
Text string for standard IP address in

format a.b.c.d.
Text string for standard subnet mask
in format p.q.r.s
Example:
Set the IP address of Fast Ethernet port to 192.168.2.211 and
subnet mask to 255.255.255.0:
CASA-CMTS(config-if-eth 0)# ip address

192.168.2.211 255.255.255.0
Reset to the default:
CASA-CMTS(config-if-eth 0)# no ip address
end
Exit the interface mode.
Example:
CASA-CMTS(config-if-eth 0)# end
Obtaining the IP address of the Fast Ethernet port from the DHCP
server
Instead of specifying an IP address to the Fast Ethernet port, the IP address can also be
assigned by the DHCP server.
Step
Command (config)
Purpose
Enter fast Ethernet

interface mode.
Where:
<eth-port>
Specifies the ethernet port number.
Example:
2
ip address dhcp
Example:
CASA-CMTS(config-if-eth 0)# ip address dhcp
Obtain an IP address
from the DHCP server.
107
CASA CMTS
Configuring an IP access group on eth0 (C3200 and C10200 only)

To configure an IP access group on eth0:
Step
Command (config)
Purpose
Enter fast Ethernet

interface mode.
Where:
<eth-port>
ethernet port
Example:
ip access-group <string>
Where:
<string>
Configure an IP Access
Group on eth0 or delete
the group.
The access group name.
Example:
Configure my_access_group on eth0:
CASA-CMTS(config-if-eth0)# ip access-group
my_access_group
Delete the group:
CASA-CMTS(config-if-eth0)# no ip access-group
Configuring Gigabit Ethernet (GigE) ports

This section describes commands for the following operations:
Enabling a Gigabit Ethernet port
Disabling a Gigabit Ethernet port
Enabling Auto-Negotiation Mode on a Gigabit Ethernet port
Setting the GigE Port IP address and subnet mask
Assigning an IPv6 address to the GigE port
Enabling Auto-Negotiation Mode on a Gigabit Ethernet port
Disabling Auto-Negotiation Mode on a Gigabit Ethernet port
Enabling/Disabling IGMP Client Service on a Gigabit Ethernet port
Displaying Gigabit Ethernet interface configuration
Enabling a Gigabit Ethernet port
108
CASA CMTS
To enable a Gigabit Ethernet port (all ports are disabled by default):

Step
1
Command (config)
Purpose
interface gige [<slot>/]<port>
Enter gige Ethernet

interface mode.
interface xgige <slot>/<port>

Where:
<port>
<slot>
Gigabit Ethernet port number in the

range 0 to 11 for C3200/C10200 , 0 to
3 for C2200, 0 to 7 on the C10G
System slot number on C10G; either 6
or 7
Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
no shutdown
Enable the GigE port
Example:
CASA-CMTS(config-if-gige 1)# no shutdown
CASA-CMTS(config-if-gige 1)# end
To disable the port:
CASA-CMTS(config-if-gige 1)# shutdown
CASA-CMTS(config-if-gige 1)# end
Enabling/disabling auto-negotiation mode on a Gigabit Ethernet port

The Casa CMTS supports auto-negotiation capability for its Gigabit Ethernet ports. The default
setting is auto negotiation enable.
The auto-negotiation mode needs to be disabled when the other side of Gigabit Ethernet
connection does not support auto negotiation or is in simplex mode. The disable mode only
applies to optical connections.
Note that the Gigabit port does not negotiate the data rate; it must be connected to another
Gigabit interface.
Step
1
Command (config)
Purpose
interface gige <port>
Enter GigE Ethernet

interface mode.
Where:
<port>

range 0 to 11 for C3200/C10200 and 0
to 3 for C2200.
Example:
109
CASA CMTS
2
Enable or disable autonegotiation mode.
[no] auto negotiate

Where:
<port>
Gigabit Ethernet port number in the range 0 to

11.
Example:
CASA-CMTS(config-if-gige 1)# auto negotiate
Disable mode:
CASA-CMTS(config-if-gige 1)# no auto negotiate
Assigning or removing a Gigabit Ethernet port IP address

To assign an IP address to a Gigabit Ethernet port:
Step
1
Command (config)
Purpose
Enter GigE interface

mode.
Where:
<port>

range 0 to 11 for C3200/C10200 and 0
to 3 for C2200.
Example:
Where:
<ip-address>
<subnet-mask>
Assign an IP address to
a GigE port.

the format a.b.c.d.
in the format p.q.r.s
Example:
Assign IP address 192.168.3.100 to Gigabit Ethernet port 1:
CASA-CMTS(config-if-gige)# ip address
192.168.3.100 255.255.255.0
CASA-CMTS(config-if-gige)#
110
CASA CMTS
Assigning an IP access group to a Gigabit Ethernet port

To assign an IP access group to a Gigabit Ethernet port:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

11 for C3200/C10200 and 0 to 3 for C2200.
Example:
ip access-group <string>
Where:
<string>
Assign an IP access
group to a GigE port.
Example:
CASA-CMTS(config-if-gige 1)# ip access-group
my_access_group
Delete the IP access group:
CASA-CMTS(config-if-gige 1)# no ip accessgroup
Assigning an IPv6 address to a Gigabit Ethernet port

By default, IPv6 addressing is disabled on all Gigabit Ethernet interfaces available at the CMTS.
IPv6 addressing is ONLY enabled when an IPv6 address is configured on one or more interfaces.
Removing the IPv6 address from an interface also disables IPv6 on that interface.
Step
1
Command (config)
Purpose
Enter Gigabit
Ethernet
interface mode.
Where:
<port>
Gigabit Ethernet port number. Valid values are 0 to 11

for C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ipv6 address <ipv6-address>/<mask_len>
Where:
Assign an IPv6
address to a
Gigabit Ethernet
port.
111
CASA CMTS
<ipv6-address>
Text string for standard IPv6 address format :

xxxx:xxxx:xxxx:...:xxxx
<mask_len>
Standard subnet mask.Usable addresses:

2001:0db8:0100:f101:0210:a4ff:fee3:9566
2001:0000:0000:0000:0000:0000:1000:1 (This
can be shortened to: 2001::1000:1)
One sequence of 20 bit blocks containing only
zeroes can be replaced with ::
Example:
Assign IPv6 address 2000::1000:1/64 to Gigabit Ethernet port 1:
CASA-CMTS(config-if-gige 1)# ipv6 address
2000::1000:1/64
Remove the IPv6 address:
CASA-CMTS(config-if-gige 1)# no ipv6 address
Assigning a Gigabit Ethernet port to a VLAN

To assign a Gigabit Ethernet port to a VLAN or to remove the assignment:
Step
1
Command (config)
Purpose

mode.
Where:
<port>
GigE port number in the range 0 to 11 for

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] vlan <vlan-id>
Where:
<port>
<vlan-id>
Assign a GigE port to a

VLAN or remove the
assignment.
GigE port number in the range 0 to 11.

VLAN ID. Valid values are 256 to 4,096
(Release 5.2).
VLAN ID. Valid values are 2 to 3,700
(Release 5.4).
Example:
Assign Gigabit Ethernet port 1 to VLAN 256:
CASA-CMTS(config-if-gige 1)# vlan 256
Remove a Gigabit Ethernet port from a VLAN:
CASA-CMTS(config-if-gige 1)# no vlan
112
CASA CMTS
Enabling/disabling the IGMP client service on a Gigabit Ethernet port

To enable or disable IGMP (Internet Group Management Protocol) client service:
The default setting is disabled.
Step
1
Command (config)
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>

11 for C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip igmp
Enable or disable IGMP

client service.
Example:
Enable IGMP client service on Gigabit Ethernet port 1:
CASA-CMTS(config-if-gige 1)# ip igmp
Disable IGMP client service on Gigabit Ethernet port 1:
CASA-CMTS(config-if-gige 1)# no ip igmp
To configure the IGMP version:
Step Command (config)
1
igmp client version <version_number>

Where:
<version_n
umber>
Purpose
Configure the IGMP
version on the CMTS.
IGMP version 1, 2 and 3. The default IGMP

version is 3. The system switches back to
using earlier versions of IGMP if it detects
their presence on the network, even if a later
version of IGMP has been configured on the
system.
Example:
CASA-CMTS(config)#igmp client version 2
113
CASA CMTS
Configuring the MTU size on a Gigabit Ethernet interface (5.4)

To configure the MTU size of a GigE port interface:
Step
1
Command (config)
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
mtu <1500-1800>
Where:
<1500-1800>
Configure the MTU size

of a GigE port interface
The values are in bytes. Default is 1500

bytes.
Example:
CASA-CMTS(config-if-gige 1)# mtu 1800
Displaying the Gigabit Ethernet interface configuration

To show the configuration of the GigE port interfaces:
Step
1
Command
Purpose
show interface gige [<port>]
Display the GigE

interface configuration.
Where:
<port>
Specifies the GigE port number in the range 0

to 11 depending on the CMTS being managed.
Example:
Show all Gigabit Ethernet interfaces:
CASA-CMTS# show interface gige
interface gige 0
ip address 192.168.3.110 255.255.255.0
no ip igmp
.auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 1
no ip igmp
auto negotiate
no shutdown
114
CASA CMTS
interface gige 2
no ip igmp
auto negotiate
no shutdown
interface gige 3
no ip igmp
auto negotiate
no shutdown
interface gige 4
no ip igmp
auto negotiate
no shutdown
interface gige 5
no ip igmp
auto negotiate
no shutdown
interface gige 6
no ip igmp
auto negotiate
no shutdown
interface gige 7
no ip igmp
auto negotiate
no shutdown
interface gige 8
no ip igmp
auto negotiate
no shutdown
interface gige 9
no ip igmp
auto negotiate
no shutdown
interface gige 10
no ip igmp
auto negotiate
no shutdown
interface gige 11
115
CASA CMTS
no ip igmp
auto negotiate
no shutdown
Displaying the 10Gigabit Ethernet interface configuration

To show the configuration of the 10GigE port interfaces:
Step
1
Command
Purpose
show interface xgige [<slot>/<port>]
Display the 10 GigE

interface
configuration.
Where:
<port>
Specifies the 10GigE port number in the range 0

to 1 using the system slot and interface number.
Example:
Show all 10Gigabit Ethernet interfaces:
CASA-C10G> show interface xgige
interface xgige 6/0
ipv6 address 5000:0:130::13/64
mac address 00:17:10:03:60:ca
no ip igmp
no auto negotiate
shutdown
interface xgige 6/1
ipv6 address 5000:0:130::23/64
mac address 00:17:10:03:60:cb
no ip igmp
no auto negotiate
shutdown
Displaying the Gigabit Ethernet interface statistics

To show the GigE port statistics:
Step
1
Command
Purpose
show interface { gige | xgige} <port> {acl-count [details] | brief |

lacp status | service-policy-count [details] | stat | throughput
[duration <seconds>]}
Display the GigE

interface
statistics.
Where:
116
CASA CMTS
<port>
Specifies the GigE port number using slot and

interface number.
acl-count
Indicates the packet drop count from ACL deny

rules. Use the optional details parameter to show
the packet count per rule.
brief
Displays minimum information about the GigE

interface.
lacp status
Displays LACP status details.
servicepolicy-count
Shows the packet count associated with one or

more policy rules. Use the optional details
parameter to show the packet count per rule.
stat
Displays GigE interface statistics, including interface

status, speed, duplex, and packet counts.
throughput
Shows interface packet throughput. Use the

optional duration parameter to display throughput
over a specified number of seconds (1 to 100).
This command accepts output modifiers.

Example:
CASA-CMTS# show interface gige 0 stat
Interface GIGE 0 statistics
interface status UP
link status
DOWN
auto-negotiation Enabled
interface speed
1000
duplex status
Full
SFP vendor
FINISAR CORP.
SFP Serial Number P6E0JP6
SFP Type
1000BASE-T
IfInOctets
0
IfInUcastPkts
0
IfInNUcastPkts
0
IfInDiscards
0
IfInErrors
0
IfInUnknownProtos 0
IfOutOctets
540
IfOutUcastPkts
0
IfOutNUcastPkts
6
IfOutErrors
0
IfOutDiscards
0
IpForwDatagrams
0
IpInReceives
0
IpInDiscards
0
CASA-C10G> show interface xgige 6/0 throughput
Interface XGIGE 6/0 throughput
IfInOctets
0 bytes/second
IfInUcastPkts
0 packets/second
IfInNUcastPkts
0 packets/second
117
CASA CMTS
IfInTotalPkts
IfOutOctets
IfOutUcastPkts
IfOutNUcastPkts
IfOutTotalPkts
0
0
0
0
0
packets/second
bytes/second
packets/second
packets/second
packets/second
Configuring loopback interfaces

This section describes commands for the following operations:
Entering interface loopback mode
Specifying the IP address subnet for a loopback interface
Enabling interface loopback mode

To enter Interface Loopback mode:
Step
1
Command (config)
Purpose
interface loopback <if_id>
Enter interface loopback

mode.
Where:
<if_id>
Example:
CASA-CMTS(config)# interface loopback 12
CASA-CMTS(conf-if-lo 12)#
Configuring an IPv6 address on a loopback interface

To specify an IPv6 address on a loopback interface:
Step
1
Command (config)
Purpose
Enter interface
loopback mode.
Where:
<if_id>
Example:
2
Assign an IPv6
address to a
118
CASA CMTS
Where:
<ipv6-address>
loopback interface.
Text string for standard IPv6 address in the
format xxxx:xxxx:xxxx:...:xxxx
2001:0db8:0100:f101:0210:a4ff:fee3:9566
2001:0000:0000:0000:0000:0000:1000:1
(This can be shortened to: 2001::1000:1)
One sequence of 20 bit blocks containing
only zeroes can be replaced with ::
<mask_len>
Example:
Assign IPv6 address 2000::1000:1/64 to GigE port 4:
CASA-CMTS(config-if-lo 4)# ipv6 address
2000::1000:1/64
CASA-CMTS(config-if-lo 4)# no ipv6 address
Configuring an IPv4 address on a loopback interface

To configure an IPv4 address on a loopback interface:
Step
1
Command (config)
Purpose

mode.
Where:
<if_id>
Loopback interface ID in the range 0 to 15.
Example:
2
ip address <address> <mask>

Where:
<address>
<mask>
Specify the IPv4 address

subnet for a loopback
interface.
Specifies the IPv4 address on this loopback

interface in standard decimal format.
Specifies the subnet mask in decimal format.
Example:
CASA-CMTS(conf-if-lo 0)#ip address 60.1.2.3
255.255.0.0
119
CASA CMTS
Assigning an access group to a loopback interface

To assign an access group to a loopback interface:
Step
1
Command (config)
Purpose

mode.
Where:
<if_id>
Example:
[no] ip access-group <string>
Where:
<string>
Assign an access group

to a loopback interface.
Example:
CASA-CMTS(config-if-lo 0)#ip access-group
my_access_group
Delete an access group:
CASA-CMTS(config-if-lo 0)# no ip access-group
Configuring a log message source IP address

To specify a log message source IP address:
Step
1
Command (config)
Purpose
logging source-interface loopback <lo_id>
Configure the log

message source IP
address
Where:
<loid>
Example:
CASA-CMTS(config)# logging source-interface
loopback 0
Configuring a loopback interface as source IP address on FTP/TFTP

packets
To specify a loopback interface as source IP address on FTP/TFTP packets initiated from the
CMTS. (This will also apply to TFTP packets for tftp-proxy feature).
120
CASA CMTS
Step
1
Command (config)
Purpose
[no] ftp-tftp source-interface loopback <id>
Configure a loopback
interface as source IP
address on FTP/TFTP.
Where:
<id>
Example:
CASA-CMTS(config)# ftp-tftp source-interface
loopback 0
Remove the configuration:
CASA-CMTS(config)# no ftp-tftp sourceinterface loopback 0
Setting the source IP address of lawful intercept packets to the

loopback IP interface
To set the source IP address of lawful intercept packets to the loopback IP interface:
Step
1
Command (config)
Purpose
lawful-intercept source-interface loopback <number>
Set the source

loopback interface
number for lawful
intercept packets.
Where:
<number>
The loopback interface number in the range

0 to 15.
Example:
CASA-CMTS(config)# lawful-intercept sourceinterface loopback 2
Configuring trunk interfaces

A trunk interface comprises of a set of gigabit interfaces in the same CMTS. The Casa CMTS
supports up to four trunk interfaces in the C2200 and 12 trunk interfaces in the C3200 and
C10200. This section describes commands for the following operations:
Creating/removing a trunk interface
Setting/removing an IP Address to/from trunk Interface
Enabling/disabling a trunk interface
Adding/removing a Gigabit Interface to/from trunk interface
Enabling/disabling IGMP on a trunk interface
Applying/removing an IP-Access list on/from trunk interface
Displaying a trunk-interface configuration
121
CASA CMTS
Creating a trunk interface

The Casa CMTS supports up to 12 trunk interfaces:
Step
1
Command (config)
Purpose
[no] interface trunk <num>
Create or remove a trunk

interface.
Where:
<num>
Trunk interface number in the range 1 to 12.
Example:
CASA-CMTS(config)# interface trunk 1
CASA-CMTS(conf-if-trunk 1#
Remove the interface:
CASA-CMTS(config)# no interface trunk <num>
Assigning an IP address to a trunk interface

To set an IP address to the trunk Interface:
Step
1
Command (config)
Purpose
Create a trunk
interface.
Where:
<num>
Example:
[no] ip address <address> <mask>
Where:
<address>
Assign an IP
address to a
trunk interface.
IP address assigned to the trunk interface.
<mask>
IP address mask.
<ipv6-address>
Text string for standard IPv6 address format:

<mask_len>

2001:0db8:0100:f101:0210:a4ff:fee3:9566
2001:0000:0000:0000:0000:0000:1000:1 (This
Examples:
122
CASA CMTS
CASA-CMTS(conf-if-trunk 6/1)# ip address

192.168.3.112 255.255.255.0
CASA-CMTS(conf-if-trunk 6/1)# ipv6 address
2000::1000:1/64
Remove the IP address:
CASA-CMTS(conf-if-trunk)# no ipv6 address
CASA-CMTS(conf-if-trunk)# no ip address
Enabling/disabling a trunk interface

To enable or disable a trunk interface:
Step
1
Command (config)
Purpose
Create a trunk interface
Where:
<num>
Example:
[no] shutdown
Example:
Enable an interface:
CASA-CMTS(conf-if-trunk num)# no shutdown
Enable or disable a trunk

interface. The default is
disabled.
Disable an interface:
CASA-CMTS(conf-if-trunk num)# shutdown
Adding a GigE port to a trunk interface

Be aware that a given gigabit interface may be present only in one trunking interface at a time.
Before adding a gigabit interface to a trunk interface, make sure that the interface has no IP
address assigned (e.g. interface gige 0 should not have an IP address).
To add or remove a GigE port on a trunk interface:
Step
1
Command (config)
Purpose
Where:
<num>
123
CASA CMTS
Example:
2
[no] gige <port>

Where:
<port>
Add or remove a GigE

port on a trunk interface.
GigE interface port number.
Example:
Add gige port 0 to trunk interface 1:
CASA-CMTS(conf-if-trunk 1# gige 0
Remove gige port 0 to trunk interface 1:
CASA-CMTS(conf-if-trunk num)# no gige 0
Enabling IGMP client services on a trunk interface

To enable IGMP client services on a trunk interface:
Step
1
Command (config)
Purpose
Where:
<num>
Example:
2
[no] ip igmp
Example:
Enable IGMP client services on trunk interface 1:
CASA-CMTS(conf-if-trunk 1# ip igmp
Enable IGMP client

services on a trunk
interface.
Disable IGMP client services on trunk interface 1:

CASA-CMTS(conf-if-trunk 1# no ip igmp
Applying an IP access group to a trunk interface

To apply an IP-access group to a trunk interface:
Step
1
Command (config)
Purpose
Create a trunk interface.
Where:
<num>
124
CASA CMTS
Example:
CASA-CMTS(conf-if-trunk 1)#
[no] ip access-group <name>
Where:
<name>
Apply or remove an IP
access group on a truck
interface.
IP access list name.
Example:
Apply IP-access list my_list to trunk interface 1:
CASA-CMTS(conf-if-trunk 1)# ip access-group
my_list
Remove IP-access list my_list from trunk interface 1:
CASA-CMTS(conf-if-trunk 1)# no ip access-group
my_list
Displaying a trunk interface configuration

To display a trunk interface configuration:
Step
1
Command (config)
Purpose
show interface trunk [<num>] [acl-count [details] | stat |

throughput [duration] | service-policy-count [details] ]
Display trunk interface

configurations.
Where:
<num>
Specifies the trunk interface number in the

range 1 to 12.
acl-count
Indicates the packet drop count from ACL

deny rules. Use the optional details
parameter to show the packet count per
rule.
stat
Shows trunk interface statistics.
throughput
Shows trunk interface throughput. Shows

Use the optional duration parameter to
display throughput over a specified
number of seconds (1 to 100).
servicepolicy-count
Shows the packet count associated with

one or more policy rules. Use the optional
details parameter to show the packet
count per rule.
Example:
Display all trunk interface configurations:
CASA-CMTS(config)# show interface trunk
Display configuration of trunk interface 1:
125
CASA CMTS
CASA-CMTS(config)# show interface trunk 1

!
interface trunk 1
gige 4 mode active
gige 5 mode active
gige 6 mode active
gige 7 mode active
gige 8 mode active
ip address 192.168.0.111 255.255.255.0
ip igmp
ip access-group telnet_host
!
no shutdown!
Displaying ARP entries from a trunk interface

To display the ARP entries from the current trunk interface:
Step
1
Command (config)
Purpose
Create a trunk
interface.
Where:
<num>
Example:
show arp
Example:
CASA-CMTS(conf-if-trunk 6/10)# show arp
Interface
Age
Hardware Addr
Address
eth 6/0
00:00:01 0017.1001.5cab
192.168.8.1
eth 6/0
00:08:40 0022.0c9a.ea41
192.168.8.12
eth 6/0
00:18:01 bc30.5bd8.0f8e
192.168.8.90
eth 6/0
00:00:01 b8ac.6f8f.181f
192.168.8.92
eth 6/0
00:00:01 0017.1002.cc40
192.168.8.113
eth 7/0
00:08:24 0022.0c9a.ea41
192.168.8.12
eth 7/0
00:00:01 0017.1002.c4c0
192.168.8.114
CATV-MAC 1 00:00:01 0017.1002.cc4d
fe80::217:10ff:fe02:cc4d
State
Type IP
dynamic ARPA
dynamic ARPA
dynamic ARPA
dynamic ARPA
static
ARPA
dynamic ARPA
static
ARPA
static
ARPA
126
CASA CMTS
CATV-MAC 2 00:00:01 0017.1002.cc4e static

fe80::217:10ff:fe02:cc4e
ARPA
Configuring Link Aggregation Control Protocol (LACP) (5.4)

Casa supports the IEEE Link Aggregation Control Protocol (LACP) for controlling the bundling of
several physical ports together to form a single logical channel. This section describes commands
for the following operations:
LACP Global Configure
LACP Administrative Key
LACP Port Priority
LACP Group Configure and Display
LACP GigE Interface Configure and Display
LACP Trunk Interface Configure and Display
Enabling the LACP global configuration

To enable/disable the LACP protocol:
Step
Command (config)
Purpose
[no] lacp shutdown
Enable the LACP

protocol.
Example:
CASA-CMTS(config)# no lacp shutdown
Disable LACP protocol:
CASA-CMTS(config)# lacp shutdown
To configure or disable the LACP priority:
Step
1
Command (config)
Purpose
[no] lacp system priority <number>
Configure or disable the

LACP priority.
Where:
<number>
Priority number in the range 1 to

65535.
Example:
CASA-CMTS(config)# lacp system priority 60000
Disable LACP priority:
CASA-CMTS(config)# no lacp system priority
To display the LACP system ID:
127
CASA CMTS
Step
1
Command (config)
Purpose
Display the LACP
system ID.
show lacp system-id

Example:
CASA-CMTS(config)#show lacp system-id
Note: The system ID is the system priority and system
MAC.
Setting LACP port priority (5.4)

To configure LACP port priority value:
Step
1
Command (config)
Purpose
Enter gige Ethernet

interface mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
lacp port-priority <number>
Where:
<number>
Configure LACP port

priority value.
Port priority number in the range 1 to

65535
Example:
CASA-CMTS(config-if-gige 1)#lacp port-priority
1
Setting the LACP system port priority (5.4)

To configure LACP system priority:
Step
1
Command (config)
Purpose
[no] lacp system priority <num=1:65535>
Configure LACP system

port priority value.
Where:
<num=1:65535>
Priority range from 1 to 65535.
Example:
CASA-C2200(config)#lacp system priority 1
128
CASA CMTS
Displaying LACP group information

To display the summary information of all the LACP groups:
Step
1
Command
Purpose
show lacp summary
Display the summary

information of all LACP
groups.
Example:
CASA-CMTS#show lacp summary
Example: Display LACP summary

CASA-CMTS#show lacp summary
Flag: A--LACP Activity, B--LACP Timeout, C--Aggregation, DSynchronization
E--Collecting,
F--Distributing, G--Defaulted,
HExpired
Port
Trunk
Mode
State
Priority
Flag
Receive
Send
gige1
active
down
1000
ACG
gige2
active
down
2000
ACG
gige3
passive
down
3000
CG
Configuring and displaying LACP port priority on GigE interfaces

To configure the port priority in the LACP group:
Step
1
Command (config)
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
lacp port-priority <number>
Where:
<number>
Configure LACP Port

priority value.
Port priority number in the range 1 to

65535
Example:
CASA-CMTS(config-if-gige 1)#lacp port-priority
1
To configure the LACP port priority to default:
129
CASA CMTS
Step
1
Command (config)
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
2
no lacp priority
Example:
CASA-CMTS(config-if-gige 1)# no lacp priority
Configure the LACP port

priority to the default
setting.
To display the LACP status of the port defined by the port number:
Step
1
Command
Purpose
show interface gige <port num> lacp status
Display the LACP status

of the port defined by the
port number.
Where:
<port
num>

C3200/C10200; 0 to 3 for C2200.
Example:
CASA-CMTS# show interface gige 3 lacp status
Example: Displaying LACP status

CASA-CMTS# show interface gige 3 lacp status
Flag: A--LACP Activity, B--LACP Timeout, C--Aggregation, DSynchronization
E--Collecting,
F--Distributing, G--Defaulted,
HExpired
Gige 3
In_Trunk 1,State: down
Port Priority 32768,
Oper Key 0x1, Port Flag: CG
Receive Packets: 0, Send Packets: 0, Illegal Packets: 0
130
CASA CMTS
Configuring and displaying LACP trunk interfaces

Step
1
Command (config)
Purpose
Where:
<num>
Example:
[no] gige 1 [mode active]
Add or remove a gige

port to a channel group.
Example:
CASA-CMTS(config-if-trunk 1)#gige 1 mode
active.
.
CASA-CMTS# show interface trunk 1
!
interface trunk 1
gige 1 mode active
gige 2 mode active
gige 3 mode passive
load-balance sdip
no shutdown
Remove the port:

CASA-CMTS(config-if-trunk 1)# no gige 1
To configure the trunk load-balance mode:
Step
1
Command (config)
Purpose
Where:
<num>
Example:
[no] load-balance {smac | dmac | sdmac | sip | dip | sdip}
Example:
CASA-CMTS(conf-if-trunk 1)# load balance smac

trunk load-balance
mode.
Disable trunk load balance mode:

CASA-CMTS(conf-if-trunk 1# no load balance
smac
131
CASA CMTS
Displaying the LACP system ID

To display LACP system information:
Step
1
Command
Purpose
show lacp system-id
Display LACP system

information.
Example:
CASA-C2200(config)#show lacp system-id
System ID: 32768,00:17:10:00:13:67
Configuring IS-IS Routing Protocol (5.4 only)

Casa CMTS supports routing protocol IS-IS (Intermediate System to Intermediate System). This
section describes the commands for configuring and monitoring IS-IS routing capabilities and
features.
Configuring IPv4 IS-IS under a GigE Port

Configure an IPv4 ISIS under a GigE Port.
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip router isis <string>
Where:
<string>
Configure or disable an
IPv4 IS-IS under a GigE
port.
IPv4 routing process tag.
Example:
CASA-CMTS(config-if-gige 4)#ip router isis ABC
Disable the ISIS:
CASA-CMTS(config-if-gige 6/4)#no ip router
isis ABC
Configuring IPv6 IS-IS under a GigE port

To apply an IPv6 ISIS under a GigE port, follow the command below:
132
CASA CMTS
Step
1
Command
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>
GigE port number in the range 0 to 11

for C3200/C10200 and 0 to 3 for
C2200.
Example:
[no] ipv6 router isis <string>
Where:
<string>
Configure or disable an
IPv6 ISIS under a GigE
port.
IPv6 routing process tag.
Example:
CASA-CMTS(config-if-gige 0)#ipv6 router isis
ABC
Disable the ISIS:
CASA-CMTS(config-if-gige id)#no ipv6 router
isis <string>
Configuring an IS-IS circuit type on a GigE interface

To configure circuit type on a GigE Interface:
Step
1
Command (config)
Purpose
Enter gige Ethernet

interface mode.
Where:
<port>

C2200.
Example:
isis circuit-type (level-1|level-1-2|level-2-only)
Where:
Circuit-type
Configure circuit type for interface.
Level-1
Level-1 only adjacencies are formed
Level-1-2
Level-1-2 adjacencies are formed
Level-2-only
Level-2-only adjacencies are formed
Configure or disable
circuit type for a GigE
interface.
133
CASA CMTS
Example:
CASA-CMTS(config-if-gige 0)#isis circuit-type
level-2-only
Disable the circuit type:
CASA-CMTS(config-if-gige 0)#no isis circuittype level-2-only
Configuring IS-IS point-to-point links

To configure two networking devices that use broadcast media (and the IS-IS routing protocol) to
operate together over a point-to-point link, specify the isis network point-to-point command:
Step
1
Command (config)
Purpose
Enter gige Ethernet

interface mode.
Where:
<port>

C2200.
Example:
[no] isis network point-to-point
Example:
CASA-CMTS(config-if-gige 0)#isis network
point-to-point
Configure a point-topoint link between two

IS-IS devices.
To disable:
CASA-CMTS(config-if-gige 0)#no isis network
point-to-point
Configuring the complete sequence number PDU (CSNP) interval

To configure the CSNP interval in seconds:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
134
CASA CMTS
Example:
[no] isis csnp-interval <num=0:65535> [(level-1|level-2)]
Where:
<num=0:65535>

CSNP interval in
seconds.
CSNP interval value.
level-1
Level-1-2 adjacencies are formed
level-2
Level-2 only adjacencies are formed
Example:
CASA-CMTS(config-if-gige 0)#isis csnp-interval
40 level-1
Disable the CSNP interval:
CASA-CMTS(config-if-gige 0)#no isis csnpinterval 40 level-1
Configuring the IS-IS Hello interval

To setup the ISIS Hello interval in seconds
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
Example:
[no] isis hello-interval <num=1:65535> [(level-1 | level-2)]
Where:
<num=1:65535>
Setup or disable the ISIS

Hello interval in seconds
Hello interval in seconds.
level-1
Specify hello-interval for level-1 IIHs
level-2
Specify hello-interval for level-2 IIHs
Example:
CASA-CMTS(config-if-gige 0)#isis hellointerval 40 level-2
Disable the ISIS Hello interval:
CASA-CMTS(config-if-gige 0)#no isis hellointerval 40 level-2
135
CASA CMTS
Configuring the IS-IS Multiplier for Hello holding time

To configure the ISIS Multiplier for the Hello holding time:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] isis hello-multiplier <num=2:100> [(level-1 | level-2)]
Where:
<num=2:100>

ISIS Multiplier for Hello
Holding time
Hello multiplier value.
level-1
Specify hello multiplier for level-1 IIHs
level-2
Specify hello multiplier for level-2 IIHs
Example:
CASA-CMTS(config-if-gige 0)#isis hellomultiplier 5 level-2
Disable the ISIS multiplier:
CASA-CMTS(config-if-gige 0)#no isis hellomultiplier
Enabling padding on IS-IS Hello packets

To pad Hello packets:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
Example:
136
CASA CMTS
Enable padding on Hello

packets.
[no] isis hello padding

Example:
CASA-CMTS(config-if-gige 0)#isis hello padding
Disable:
CASA-CMTS(config-if-gige 0)#no isis hello
padding
Configuring the IS-IS default metric

The IS-IS default metric command calculates path cost for IS-IS links to network destinations.
Lower metric settings are preferred over higher metric setting.
To configure the IS-IS default metric:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
Example:
[no] isis metric <num=1:16777214> [level-1 | level-2]
Where:
<num=0:16777214>
Configure or delete the

default IS-IS metric .
Sets the default metric for IS-IS

circuit in the range 1 to 16777214.
level-1
Optional. Applies the specified

metric to Level-1 links.
level-2

metric to Level-2 links.
Example:
CASA-CMTS(config-if-gige 0)#isis metric 40
To disable the default metric:
CASA-CMTS(config-if-gige 0)#no isis metric
137
CASA CMTS
Configuring the authentication password for a GigE interface

IS-IS passwords can be encrypted using the [no] service password-encryption command from
the top-level configuration mode.
To configure the authentication password for a GigE interface:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] isis password <string> [level-1 | level-2]
Where:
<string>
Specifies the password string using up

to 255 characters.
level-1

password to Level-1 Hello packets
only.
level-2

password to Level-2 Hello packets
only.
the IS-IS
authentication
password for a GigE
interface.
Example:
CASA-CMTS(config-if-gige 0)#isis password AAA
Disable the password:
CASA-CMTS(config-if-gige 0)#no isis password AAA
Configuring the IS-IS priority

To setup IS-IS priority:
Step
1
Command (config)
Purpose
Enter GigE
Ethernet
interface mode.
Where:
<port>

for C3200/C10200 and 0 to 3 for C2200.
138
CASA CMTS
Example:
2
[no] isis priority <num=0:127> [(level-1|level-2)]

Where:
priority <num=0:127>
Setup IS-IS
priority.
ISIS priority ranged from 0 to 127.
level-1
Specify priority for level-1 routing.
level-2
Specify priority for level-2 routing.
Example:
CASA-CMTS(config-if-gige 0)#isis priority 2 level-2
Configuring the IS-IS retransmit-interval

The isis retransmit-interval specifies the amount of time between retransmission of each
Intermediate System-to-Intermediate System (IS-IS) link-state packet (LSP) on a point-to-point
link. Specify a time in seconds in the range 0 to 65535.
Step
1
Command (config)
Purpose
Enter GigE
Ethernet
interface mode.
Where:
<port>

for C3200/C10200, 0 to 7 on the C10g, and 0 to 3 for
C2200.
Example:
[no] isis retransmit-interval <0-65535>
Where:
<0-65535>
Specifies the time in seconds in the

range 0 to 65535.
Example:
CASA-CMTS(config-if-gige 0)#isis retransmit-interval
10
Set the time

interval between
retransmission
of the same
LSPs over a
point-to-point
link.
139
CASA CMTS
Configuring IS-IS router area tag

A single IS-IS router resides in one area, where the border between IS-IS routers in different
areas is on the GigE link that connects the routers together. To configure an IS-IS area tag to be
associated with the IS-IS router process, enter the config-router-isis configuration context. To
display the IS-IS area tag, use the show isis area command.
Step
1
Command (config)
Purpose
[no] router isis <string>
Configure the ISIS router area

tag.
Where:
<string>
ISO routing area tag associated with the IS-IS

routing process.
Example:
CASA-CMTS(config)#router isis local
CASA-CMTS(config-router-isis)#
Delete an ISO IS-IS area tag:
CASA-CMTS(config-router-isis)#no router isis local
Displaying the IS-IS command list

To show the IS-IS command list, enter the list command from the IS-IS router configuration mode.
Step
1
Command (config-router-isis)
Purpose
list
Display the IS-IS

command list.
Example:
CASA-CMTS(config-router-isis)# list
area-password WORD
area-password WORD authenticate snp
(send-only|validate)
authentication key-chain XXX
authentication key-chain XXX (level-1|level-2)
authentication mode (md5|txt)
authentication mode (md5|txt) (level-1|level-2)
domain-password WORD
domain-password WORD authenticate snp
(send-only|validate)
end
exit
hostname dynamic
is-type (level-1|level-1-2|level-2-only)
list
lsp-gen-interval <1-120>
lsp-gen-interval level-1 <1-120>
140
CASA CMTS
lsp-gen-interval level-2 <1-120>

lsp-lifetime <380-65535>
lsp-lifetime level-1 <380-65535>
lsp-lifetime level-2 <380-65535>
metric-style (narrow|transition|wide)
net WORD
.
.
Specifying the IS-IS IPv6 address family paramters

To configure a routing session using IP Version 6, use the address-family parameter in router
configuration mode to support redistribution of IPv6 routes. Use the no form of the addressfamily command to remove the IPv6 setting.
Step
1
Command (config)
Purpose
[no] router isis <string>
Configure the
IS-IS router
area tag.
Where:
<string>
ISO routing area tag associated with the IS-IS routing

process.
Example:
Delete an ISO IS-IS area tag:
CASA-CMTS(config-router)#no router isis local
2
[no] address-family ipv6 [unicast]

Parameter settings:
Configure the
IPv6
parameter for
IS-IS.
default-information originate
exit-address-family
multi-topology [level-1 | level-2 | level-1-2 | transition]
redistribute {bgp | connected | isis | static} {level-1 | level-2 | level-1-2}
metric <number> metric-type {internal | external} [route-map <name>
metric <number> metric-type {internal | external} [route-map <name>
route-map <name>
summary-prefix X:X::X:X/M
Where:
141
CASA CMTS
ipv6
Internet Protocol Version 6; unicast only
unicast
Optional. Specifies IPv6 unicast address prefixes.

This is the default setting.
defaultinformation
originate
Generates a default route within the IS-IS routing

domain for distribution to other IS-IS neighbors.
exit-addressfamily
Exits the address-family configuration context

(config-router-isis-af) and places the user at the
previous context (config-router-isis).
multi-topology
Enables IS-IS multi-topology support for aligning

IPv4 and IPv6 IS-IS routers within an area.
Specify level-1, level-2, level-1-2, or transition.
If IPv4 and IPv6 are configured on the same
interface, then both must be configured at the
same level.
All IPv6 routers within the IS-IS area must have the
multi-topology option enabled.
Use the transition option for transitioning from an
existing IPv6 network to multi-topology.
The router isis metric-style parameter must be set
to wide if the multi-topology option is enabled.
Captures routes from other routing protocols. IS-IS
then advertises these routes to Level-1, Level-2, or
both Level-1 and -2 routers.
redistribute
bgp -- Specifies IS-IS to advertise Border

Gateway Protocol (BGP) routes.
connected -- Specifies IS-IS to advertise

connected routes from a directly-connected
subnet or host.
isis -- Specifies IS-IS level-1/level-2 route

distribution.
static -- Specifies IS-IS to advertise staticallyconfigured routes. A level option is not

required.
metric-type
Specifies an internal or external metric type.
route-map
<name>
Optional. Instructs IS-IS to apply a previouslyconfigured route map to control route

advertisements to IS-IS routers. See the
Configuring Route Maps section of this manual
for information.
summary-prefix
Specifies the address-family IPv6 prefix in the

shortened format x:x::x:x/<mask>.
Example:
CASA-CMTS(config-router-isis)# address-family ipv6
unicast
142
CASA CMTS
CASA-CMTS(config-router-isis-af)# default-information
originate
CASA-CMTS(config-router-isis-af)# multi-topology
transition
CASA-CMTS(config-router-isis-af)# summary-prefix
2001:1234::/64
CASA-CMTS(config-router-isis-af)# exit-address-family
Configuring the IS-IS router area authentication password

Use the area-password command to create a password for all routers within an area to prevent
routing updates to the CMTS IS-IS link-state database from unauthorized routers. The password
in inserted in Level 1 link state packets (LSPs), partial sequence number PDUs (PNSP), and
complete sequence number PDUs (CSNP).
Step
1
Command (config-router)
Purpose
[no] area-password <password> [authenticate snp {send-only |

validate}]
Enter or disable
the IS-IS area
plain text
password
setting.
Where:
<password>
Specifies the IS-IS area password for routers in

this area.
authenticate
snp
Optional parameter. Specifies that the password is

inserted into sequence number PDUs (SNPs). If
not specified with the send-only or the validate
option, the IS-IS protocol does not insert the
password into SNPs.
send-only
Inserts the password into SNPs, but does not

check the password in SNPs that it receives.
validate
Inserts the password into SNPs and checks the

password in SNPs that it receives.
Example:
CASA-CMTS(config-router-isis)# area-password abcXyZ
CASA-CMTS(config-router-isis)# area-password abcXyZ
authenticate snp validate
Disable the IS-IS area-password:
CASA-CMTS(config-router-isis)#no area-password
143
CASA CMTS
Configuring the IS-IS router authentication key chain

The authentication key-chain command enables either clear text or MD5 authentication for
Level 1 and/or Level 2 IS-IS packets, or both levels (by default). Use the authentication-mode
command to instruct the IS-IS protocol to use clear text or MD5. Only one key chain is allowed. If
an authentication key chain is not configured, then IS-IS key chain authentication is disabled.
Step
1
Purpose
[no] authentication key-chain <name> [level-1 | level-2]
Specify or delete
the IS-IS key
chain name for
IS-IS
authentication.
Where:
<name>
Specifies the name of the IS-IS authentication key

chain to enable authentication of both level 1 and
level 2 packets.
level-1
Optional. Enables authentication of level 1 packets

only.
level-2
Optional. Enables authentication of level 2 packets

only.
Example:
CASA-CMTS(config-router-isis)# authentication keychain charlie
Disable the IS-IS authentication key chain:
CASA-CMTS(config-router-isis)#no authentication keychain
CASA-CMTS(config-router-isis)#no authentication keychain charlie
Configuring the IS-IS router authentication mode

Use the authentication mode command to instruct the IS-IS protocol to use clear text or
Message Digest 5 (MD5) authentication for Level 1, Level 2, or both Level 1 and Level 2 IS-IS
packets. Once configured, you will not be able to use the area-password or domain-password
commands. To do so, use the no authentication mode command followed by the areapassword or the domain-password command.
Step
1
Purpose
[no] authentication mode md5 [level-1 | level-2]
Specify or
remove the IS-IS
authentication
mode setting.
Where:
md5
Specifies Message Digest 5 (MD5) authentication

of both Level 1 and Level 2 packets (by default) if
144
CASA CMTS
the level-1 or level-2 options are not specified.

level-1
Optional. Enables clear text or MD5 authentication

of Level 1 packets only.
level-2
Optional. Enables clear text or MD5 authentication

of Level 2 packets only.
Example:
CASA-CMTS(config-router-isis)# authentication mode
md5 level-1
Disable the IS-IS authentication mode:
CASA-CMTS(config-router-isis)#no authentication mode
txt level-1
Configuring the IS-IS router authentication send-only option

Use the authentication send-only command to perform authentication on IS-IS packets that are
sent over an interface. Authentication is NOT performed on packets received on the interface.
Step
1
Purpose
[no] authentication send-only [level 1 | level-2]
Enable the IS-IS

send-only
option.
Where:
level-1
level-2
Optional. Enables authentication of Level 1 packets

sent over the IS-IS interface.
Optional. Enables authentication of Level 2
packets sent over the IS-IS interface.
Use the no form

of the command
to disable the
send-only option
Example:
CASA-CMTS(config-router-isis)# authentication sendonly
Disable the IS-IS authentication mode:
CASA-CMTS(config-router-isis)#no authentication
send-only
145
CASA CMTS
Configuring the IS-IS router default route distribution

Use the default-information originate command to generate a default route within the IS-IS
routing domain for distribution to other IS-IS neighbors.
Step
1
Purpose
[no] default-information originate
Generate a
default route
within the IS-IS
routing domain.
Example:
CASA-CMTS(config-router-isis)# default-information
orginate
Disable the default-information originate:
CASA-CMTS(config-router-isis)#no default-information
originate
Use the no form

of the command
to remove this
parameter
setting.
Configuring the IS-IS router domain authentication password

Use the domain-password command to create a password for all routers within a routing domain
to prevent routing updates to the CMTS IS-IS link-state database from unauthorized routers. The
password in inserted in Level 1 link state packets (LSPs), partial sequence number PDUs
(PNSP), and complete sequence number PDUs (CSNP).
Step
1
Purpose
[no] domain-password <password> [authenticate snp {send-only

| validate}]
Enter or disable
the IS-IS domain
plain text
password
setting.
Where:
<password>
Specifies the IS-IS domain password for routers in

this domain.
authenticate
snp
Optional parameter. Specifies that the password is

inserted into sequence number PDUs (SNPs). If
not specified with the send-only or the validate
option, the IS-IS protocol does not insert the
password into SNPs.
send-only
Inserts the password into SNPs, but does not

check the password in SNPs that it receives.
validate
Inserts the password into SNPs and checks the

password in SNPs that it receives.
Example:
CASA-CMTS(config-router-isis)# domain-password
abcXyZ
CASA-CMTS(config-router-isis)# domain-password
abcXyZ authenticate snp validate
146
CASA CMTS
Disable the IS-IS area-password:

CASA-CMTS(config-router-isis)# no area-password
Configuring the IS area types

IS-IS networks are made up of end systems that send and receive network traffic within the
routing domain (called an autonomous system (AS)). The intermediate systems within the AS are
responsible for forwarding packets between the end systems. An IS-IS AS comprises two types
of non-backbone areas: Level 1 and Level 2
Level 1 areas share routing information within an area, while Level 2 routers share IP address
information among the IS-IS areas. Level 2 areas also interconnect all Level 1 areas, as well as
share link state information. IS-IS routers can also be configured as both Level 1 and Level 2
routers that share intra-area routes with other Level 1 routers and inter-area routes with other
Level 2 routers. Note that in networks having only one area, there is no need to run both Level 1
and Level 2 routing agorithms.
All routers maintain a link-state database of all other routers within the same level. Using the linkstate database, each router determines the shortest path to other routers. Use the show isis
database command to display the current link state statis
Step
1
Purpose
[no] is-type {level-1 | level-1-2 | level-2-only}
Configure the
IS-IS routing
algorithm.
Where:
level-1
Specifies Level-1 intra-area routing only where the router

discovers routes in its own area. Inter-area routing is
performed by the nearest level-1-2 router
level-1-2
Specifies Level-1 intra-area and Level-2 inter-area routing.

In a multi-area domain, this is the default setting for the first
routing instance if the is-type command is not used.
level-2
only
Specifies Level-2 inter-area routing only. It does not share

information to the Level-1 routers in its own area.
Example:
CASA-CMTS(config-router-isis)is-type level-1#
Reset the current IS type setting:
CASA-CMTS(config-router-isis)#no is-type level-1
147
CASA CMTS
Configuring the IS-IS LSP generation interval

The lsp-gen-interval command specifies the mimumum number of seconds to elapse between
generated link state packets (LSPs). LSPs contain information about each router in the network
and its connected interfaces and is used to provide updates to the IS-IS router link state
database(s). The interval is specified in the range 0 to 120 seconds for all routers, level-1 areas
only, or level-2areas only. Specifying a greater number of seconds reduces network load
associated with link state change. Individual settings are supported for Level-1 and Level-2
routers.
Step
1
Purpose
[no] lsp-gen-interval {<seconds> | level-1 <seconds> | level-2

<seconds>]
Configure the
minimum
elapsed time
in seconds
between
generated
LSPs.
Where:
<seconds>
Specifies the number of seconds to elapse between

IS-IS generated LSPs for all IS-IS routers. The range
is 0 to120 seconds. The default setting is 5 seconds.
level-1
Specifies that the configured interval applies to

Level-1 areas only.
level-2
Specifies that the configured interval applies to

Level-2 areas only.
Examples:
CASA-CMTS(config-router)# lsp-gen-interval level-1 20
CASA-CMTS(config-router)# lsp-gen-interval level-2 10
Reset the LSP generation interval to the default setting:
CASA-CMTS(config-router)#no lsp-gen-interval 50
Configuring the IS-IS LSP lifetime

The lsp-lifetime command specifies the maximum umum number of seconds that an LSP is
allowed to remain in a routers link state database without being updated. LSPs contain
information about each router in the network and its connected interfaces and is used to provide
updates to the IS-IS router link state database(s). The maximum lifetime is specified in the range
350 to 65535 seconds for all routers. If not specified the default is 1200 seconds for all IS-IS
routers. .
Step
1
Purpose
[no] lsp-lifetime <seconds>
Configure the
maximum
time in
seconds for an
LSP to exist in
Where:
<seconds>
Specifies the maximum number of seconds that an
148
CASA CMTS
LSP is allowed to exist in the routers link state

database without being updated. The range is 350 to
65535 seconds for all routers. The default setting is
1200 seconds (or 20 minutes).
the link state

database with
being updated.
Examples:
CASA-CMTS(config-router-isis)# lsp-lifetime 1300
Reset the LSP generation interval to the default setting:
CASA-CMTS(config-router)#no lsp-lifetime
Configuring the IS-IS route redistribution metric style

The metric-style command specifies the type length style (TLV) metric to be used for the
redistribution of IS-IS routes, either narrow, transition, or wide.
Step
1
Purpose
[no] metric-style {narrow | transition | wide]
Configure the
IS-IS route
redistribution
metric style.
Where:
narrow
Specifies the old TLV style (using a metric value

number in the range 0 to 63) for route redistribution. A
warning message is logged if a metric value greater
than 63 is specified when the narrow option is
enabled.
transition
Specifies both old (narrow) and new (wide) TLV styles

(using a metric value in the range 0 to 16777215) for
route redistribution.
wide
Specifies the new TLV style (using a metric value in

the range 0 to 16777215) for route redistribution.
Examples:
CASA-CMTS(config-router)# metric-style transition
Remove the current metric-style setting:
CASA-CMTS(config-router)#no metric-style
Configuring the network entity title (NET)

The network entity title (NET) is a special network address that defines the router system ID and
area ID as a hexadecimal address in the range 8 to 20 octets. The NET address consists of a
format identifier (AFI), an area ID, a system ID, and a selector. For example:
47 AFI
0004.0000.0000 area identifier
149
CASA CMTS
1234.5678.2005 system identifier

00 selector (always 00)
While the area identifier must be unique for each IS-IS area, the system identifier must the same
across all areas.
Step
1
Purpose
[no] net <network-entity-title>
Enable or
disable the
network entity
title.
Where:
<networkentity-title>
Specifies the 8 to 20 octet NET address.
Example:
CASA-CMTS(config-router-isis)# net
47.0004.0000.0000.1234.5678.2005.00
Disable the network entity title:
CASA-CMTS(config-router-isis)#no net
47.0004.0000.0000.1234.5678.2005.00
Enabling the IS-IS dynamic hostname capability

In an IS-IS networking domain, the system-ID, which is built using the network entity title (NET), is
used to represent each router. The hostname dynamic command uses LSP to distribute the
router name to system-ID mappings to other routers. When received, the routers will install the
mappings in their routing tables.
Step
1
Purpose
[no] hostname dynamic
Enable or
disable the
dynamic
hostname
capability.
Example:
CASA-CMTS(config-router-isis)# hostname dynamic
Disable the IS-IS dynamic hostname:
CASA-CMTS(config-router)#no hostname dynamic
Configuring IS-IS passive interfaces

The passive-interface command specifies those interfaces over which IS-IS LSPs are neither
send or received. A passive interface only advertises its own IP address in LSPs and does not
send or receive IS-IS packets. Specify as many passive interfaces as required.
150
CASA CMTS
Step
1
Purpose
[no] passive-interface {gige | ip-bundle | loopback | trunk | vlan |

xgige} <interface_name>
Configure the
IS-IS passive
interfaces.
Where:
<interface_name>
Specifies the name of and existing CMTS

network interface at the CMTS, such as
loopback, gige0, gige1, and so on.
Examples:
CASA-CMTS(config-router-isis)# passive-interface
gige4
CASA-CMTS(config-router-isis)# passive-interface
loopback0
Remove the current passive-interface setting:
CASA-CMTS(config-router)#no passive-interface gige4
Configuring IS-IS to redistribute route advertisements from other

protocols
The redistribute command captures routes from other routing protocols; IS-IS then advertises
these routes to Level-1, Level-2, or both Level-1 and -2 routers.
Step
1
Command (config router)
Purpose
redistribute {bgp | connected | isis | rip | static | ospf}

{level-1 | level-2 | level-1-2) metric <number> metric-type
{internal | external} [route-map <name>]
Configure IS-IS to
advertise routes
from other protocols
to Level-1, Level-2,
or Level-1-2 routers.
redistribute {bgp | connected | isis | rip | static | ospf}

{level-1 | level-2 | level-1-2) route-map <name>
Where:
bgp
Specifies IS-IS to advertise Border Gateway

Protocol (BGP) routes.
connected
Specifies IS-IS to advertise connected routes

from a directly-connected subnet or host.
isis
Specifies IS-IS level-1/level-2 route distribution.
ospf
Specifies IS-IS to advertise Open Shortest Path

First Version 2 (OSPFv2) routes.
rip
Specifies IS to advertise Routing Information

Protocol (RIP) routes.
static
Specifies IS-IS to advertise statically-configured

routes.
151
CASA CMTS
level-1,
level-2,
level-1-2
Specifies IS-IS to advertise the specified protocol

routes to Level-1, Level-2, or both Level-1 and
Level-2 routers.
metric
<number>
Specifies the metric to be applied to IS-IS route

distribution in the range 0 to 4261412864.
metric-type
Specifies an internal or external metric type.

Internal metrics (less than 64) are generated
within the IS-IS domain; external metrics (greater
than 64) are generated outside of the IS-IS
routing domain or from other protocols. The
default metric-type is internal.
route-map
<name>
Optional. Instructs IS-IS to apply a previouslyconfigured route map to control route

advertisements to IS-IS neighbors. See the
Configuring Route Maps section of this manual
for information.
Example:
Configure IS-IS to advertise static routes to Level-2 routers:
CASA-CMTS(config-router-isis)# redistribute static
l2
Setting the IS-IS overload bit

The IS-IS set-overload-bit command enables the CMTS IS-IS router to inform neighbor routers
that an overload or unavailable condition exists and that the CMTS is not ready to forward link
state packets after a CMTS reboot (on-startup), or to suppress route advertisement s for a
specified period.
152
CASA CMTS
Step
1
Purpose
set-overload-bit on-startup <seconds> [suppress external]

[interlevel]
Configure IS-IS to
notify neighbor
routers that the
CMTS is
unavailable to
forward packets
after a system
reboot.
set-overload-bit on-startup <seconds> [suppress interlevel]

[exernal]
set-overload-bit suppress external [interlevel] [on-startup
<seconds>]
set-overload-bit suppress interlevel [external ] [on-startup
<seconds>]
Where:
on-startup
<seconds>
Specifies the temportary time in seconds to

advertise the CMTS as overloaded after a system
reboot in the range 5 to 86400 seconds.
suppress
external
Specifies that IP prefixes from other protocols not

be advertised when the overload bit is set.
Additionally, the interlevel option may be specified
to also suppress IS-IS routes.
suppress
interlevel
Specifies that IP prefixes from other IS-IS protocol

levels not be advertised when the overload bit is
set. Additionally, the external option may be
specified to also suppress IP prefixes from other
protocols.
Example:
Setting the IS-IS shortest path first (SPF) calculations

The IS-IS spf-interval-exp command sets the minimum and maximum time intervals (in
milliseconds) between shortest past first (SPF) calculation changes from neighbor routers when
topology changes take place. The minimum and maximum interval settings provide a throttling
window for preventing the simultaneous flooding of new SPF calculations received by the CMTS
IS-IS router.
Step
1
Purpose
[no] spf-interval-exp <minimum_delay> <maximum_delay>
Set the shortest

path first (SPF)
time interval to
elapse between
received SPF
updates.
[no] spf-interval-exp [level-1 | level-2] <minimum_delay>

<maximum_delay>
Where:
153
CASA CMTS
<minimum_delay>
Specifies the minimum time in milliseconds

between consecutive SPF change
calculations in the range 0-2147483647
msec. The default setting is 500 ms.
<maximum_delay>
Specifies the maximum time in

milliseconds between consecutive SPF
change calculations in the range 02147483647 msec. The default setting is
5000 ms, or 50 seconds.
level-1
Applies the SPF interval to Level-1 areas

only.
level-2
Applies the SPF interval to Level-2 areas

only.
Use the no form of

the command to
remove the current
setting.
Examples:
CASA-CMTS(config-router-isis)#spf-interval-exp 50
500
CASA-CMTS(config-router-isis)#spf-interval-exp
level-1 50 500
Setting the IPv4 summary address prefix

The IS-IS summary-address command sets the specified IPv4 prefix to be announced in CMTS
link state packets distributed to IS-IS neighbors routers. This setting designates the range of
addresses and the network mask for the summary route redistributed to Level-1 or Level-2 areas,
or both Level-1/Level-2 areas. Aggregating routes using the summary-address command
simplifies neighbor routing tables using one address and network mask.
Step
1
Purpose
[no] summary-address <ip_address/netmask> [level-1 | level-2 |

level-1-2]
Set the IPv4

summary prefix to
be included in ISIS advertisements
neighbor routers.
Where:
ip_address/netmask
Specifies the IPv4 summary address and

the network mask to be announced in
IS-IS link state packets forwarded to ISIS neighbor routers. By default, if a level
option is not specified, then the specified
summary address is announced to
Level-2 areas.
level-1
Optional. Forwards the IPv4 summaryaddress prefix setting to Level-1 areas

only.
level-2
Optional. Forwards the IPv4 summary-
Use the no form of

the command to
remove the current
setting.
154
CASA CMTS
address prefix setting to Level-2 areas

only.
Optional. Forwards the IPv4 summaryaddress prefix setting to both Level-1
and Level-2 areas.
level-1-2
Examples:
CASA-CMTS(config-router-isis)#spf-interval-exp
level-1 50 500
Displaying the IS-IS area configuration

To show the IS-IS area configuration:
Step
1
Command (config)
Purpose
show isis area <tag> database [detail [slot <number>] | l1 | l2 |

level-1 | level-2 | slot <number> ]
Display the IS-IS

area configuration.
show isis area <tag> neighbors [detail [slot <number>] | slot

<number>]
show isis area <tag> topology [level-1 [slot <number>] |
level-2 [slot <number>] | slot <number>]
show ipv6 isis area area <tag> topology [level-1 [slot
<number>] | level-2 [slot <number>] | slot <number>]
Where:
<tag>
Specifies the unique IS-IS routing area tag string.
database
See Displaying the IS-IS link state database.
neighbors
See Displaying the IS-IS neighbor routers.
topology
See Displaying the IS-IS topologies.
detail
Displays full IS-IS link state database information.

Optional system slot number may be specified.
l1
Level-1 link state database only.
l2
level-1
level-2
slot
IS-IS database statistics per specified system slot

number.
verbose

155
CASA CMTS
Examples:
CASA-CMTS(config)#show isis area local database
detail
CASA-CMTS(config)#show isis area local neighbors
detail slot 3
CASA-CMTS(config)#show isis area local topology
level-1
Displaying the IS-IS counter statistics

To show the ISIS statistics counters:
Step
1
Command (config)
Purpose
show isis counter [slot <number>}
Show ISIS route

statistics for all
configured areas.
Where:
slot <number>
Specifies the CMTS system slot number over

which IS-IS is running.
Example:
CASA-CMTS(config)#show isis counte
Area local:
IS-IS Level-1 isisSystemCounterEntry:
isisSysStatCorrLSPs: 0
isisSysStatAuthTypeFails: 0
isisSysStatAuthFails: 0
isisSysStatLSPDbaseOloads: 0
isisSysStatManAddrDropFromAreas: 0
isisSysStatAttmptToExMaxSeqNums: 0
isisSysStatSeqNumSkips: 0
isisSysStatOwnLSPPurges: 0
isisSysStatIDFieldLenMismatches: 0
isisSysStatMaxAreaAddrMismatches: 0
isisSysStatPartChanges:
Displaying the IS-IS link state database

To show the IS-IS database:
Step
1
Command (config)
Purpose
show isis database [detail [slot <number> ]| l1 | l2 | level-1 |

level-2 | slot | verbose [slot <number>] ]
Display the IS-IS

database.
Where:
detail

156
CASA CMTS
l1
Specifies the level-1 link state database only.
l2
level-1
level-2
slot
<number>
Specifies the IS-IS database statistics per specified

system slot number.
verbose

Example:
CASA-CMTS(config)#show isis database slot 6
Area casa:
IS-IS Level-2 Link State Database:
LSPID
LSP Seq Num LSP Checksum
LSP Holdtime
ATT/P/OL
CASA-C10G.00-00
* 0x0000003E
0x6BAF
65227
0/0/0
Displaying the IS-IS interface statistics

To show the ISIS statistics counters:
Step
1
Command (config)
Purpose
show
show
show
show
show
show
show
Show ISIS route

statistics for all
configured areas.
isis interface counter [slot <number>]]

isis interface docsis-mac <id>
isis interface gige <slot/port>
isis interface loopback <number>
isis interface trunk <id>
isis interface vlan <slot/vlanId>
isis interface xgige <slot/port>
Where:
slot <number>
Specifies the CMTS system slot number

over which IS-IS is running.
docsis-mac <id>
Specifies the docsis-mac interface

number in the range 1 to 32
gige <slot/port>
Specifies the CMTS GigE port number, or

the CMTS slot and port number
combination for C10200 and C10G
systems. GigE port number in the range
0 to 11 for C3200/C10200 and 0 to 3 for
C2200, and 0 to 7 on the C10G.
loopback <number>
Specifies the logical loopback interface in

the range 0 to 15.
157
CASA CMTS
trunk <slot/trunkId>
Specifies the trunk identifier, or the CMTS

slot/ trunk ID combination for C10200 and
C10G platforms in the range 1 to 12.
vlan <slot/vlanId>
Specifies the VLAN identifier, or the

CMTS slot/ vlan ID combination in the
range 2 to 3700.
xgige <slot/port>
On the C10G platform, specifes the

10GigE interface in the range 0 to 1 on
system slots 6 or 7.
Example:
CASA-C3000(confi))#show isis interface counter
gige1:
IS-IS LAN Level-1 isisCircuitCounterEntry:
isisCircAdjChanges: 0
isisCircNumAdj: 0
isisCircInitFails: 0
isisCircRejAdjs: 0
isisCircIDFieldLenMismatches: 0
isisCircMaxAreaAddrMismatches: 0
isisCircAuthTypeFails: 0
isisCircAuthFails: 0
isisCircLanDesISChanges: 0
IS-IS Level-1 isisPacketCounterEntry:
isisPacketCountIIHello in/out: 0/0
isisPacketCountLSP in/out: 0/0
isisPacketCountCSNP in/out: 0/0
isisPacketCountPSNP in/out: 0/0
isisPacketCountUnknown in/out: 0/0
Displaying the IS-IS neighbor routers

To show the ISIS neighbor routers:
Step
1
Command (config)
Purpose
show isis neighbors [detail [slot <number>] | slot

<number> ]
Show the ISIS neighbor

database.
Where:
detail
slot
<number>
Displays full IS-IS neighbor information.

Optional system slot number may be
specified.
Specifies the IS-IS neighbor statistics per
specified system slot number.
Example:
CASA-CMTS(config)#show isis neighbors
Area 160_isis:
158
CASA CMTS
Area chris:
Area AAA:
Displaying the IS-IS topology information

To show the ISIS routing topology across Level-1 and Level-2 areas:
Step
1
Command (config)
Purpose
show isis topology [level-1 [slot <number>] |

level-2 [slot <number>] | slot <number> ]
Show the ISIS topology

database.
show ipv6 isis topology [level-1 [slot <number>] |

level-2 [slot <number>] | slot <number> ]
Where:
level-1
Specifies the level-1 topology database

only.
level-2
Specifies the level-2 topology database

only.
slot
<number>
Specifies the IS-IS topology statistics per

specified system slot number.
Example:
CASA-CMTS(config)#show isis topology
Area 160_isis:
Area chris:
Area AAA:
Displaying the IPv4 and IPv6 IS-IS routing table

To show the IPv4 routing table:
Step
Command (config)
Purpose
show ip route isis
Display the IPv4 or IPv6

IS-IS routing table.
show ipv6 route isis

Example:
CASA-CMTS(config)#show ip route isis
Configuring Protocol Independent Multicast in Sparse Mode

Protocol Independent Multicast in Sparse Mode (PIM-SM), as defined in RFC 2362, is a
multicast routing protocol that maintains multicast datagram forwarding tables for wide
area and sparse multicast distribution. The PIM-SM implementation on the CMTS
159
CASA CMTS
supports shared distribution from a configured Rendezvous Point (RP), RP discovery

using a static configuration or a bootstrap router (BSR), and sourced-based trees over
Source-Specific Multicast (SSM) where hosts can specify the source and multicast group
from which to receive multicast data streams.
PIM-SM is enabled and configured on GigE and loopback interfaces. Both IGMP and
PIM-SM cannot coexist on the same interface. To configure PIM-SM, IGMP (if previously
enabled) must be disabled in order for PIM-SM to operate on a CMTS interface.
The PIM-SM configuration on a CMTS GigE or loopback interface uses the following
elements:
Rendezvous Point (RP) address
RP candidate
Bootstrap router (BSR) candidate
Shortest Path Tree (SPT) threshold
Source-Specific Multicast (SSM)
Enabling PIM-SM on a GigE or loopback interface

To enable PIM-SM on a GigE interface:
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip pim sparse-mode
Example:
CASA-CMTS(conf-if-gige 1)# ip pim sparse-mode
Enable PIM-SM.
command to disable
PIM-SM on a previouslyconfigured GigE
interface.
160
CASA CMTS
Displaying the current PIM-SM interface and neighbor configurations

To display the PIM-SM interface and neighbor configurations:
Step
1
Command
Purpose
show ip pim interface

show ip pim neighbor
Display the
current PIMSM
configuration.
Example:
CASA-CMTS# show ip pim interface
Address
192.168.6.170
170.1.1.1
Interface
Gige0
Lookback1
Ver
v2
v2
Nbr Count
2
1
0
0
DR Prior DR
192.168.6.144
0.0.0.0
CASA-CMTS# show ip pim neighbor

Neighbor Address
Interface
Uptime/Expires
DR Priority
Configuring rendezvous point addresses

PIM-SM requires a static rendezvous point (RP) address of the router interface that accepts
multicast traffic from other hosts before forwarding the traffic to members of the multicast group.
To configure a static RP address for PIM-SM:
1
[no] ip pim rp-address <ip_address> [access-list <name> |

override]
Where :
<ip_address>
The IP address of the multicast group

rendezvous point.
access-list
<name>
Optional: The named access-list reference

associated with the multicast group.
override
Optional: Overrides dynamically learned

rendezvous point mappings.
Purpose
Specify the static
RP address
Use the no form of

the command to
delete the RP
address
assignment.
By default, if the access-list option is not specified, 224.0.0.0/4

becomes the IP address of the access group. The override option
causes the static RP-address to override a dynamically-learned RP
Example:
CASA-CMTS(config)# ip pim rp-address 143.1.1.1.
access-list multicastList1
161
CASA CMTS
show ip pim rp [mapping]

show ip pim rp-hash <ip_address>
Where:
<ip_address>
Display the RP
groups and
mappings.

rendezvous point.
Example :
CASA-CMTS(config)#show ip pim rp
Group(s) 224.0.0.0/4, Static
RP 143.1.1.1, static
CASA-CMTS(config)#show ip pim rp mapping
Group(s) 224.0.0.0/4
RP 192.168.3.232, v2
Info source: 192.168.3.232, via bootstrap, priority 0,
holdtime 150
Uptime: 0:0:44:8, expires: 148
CASA-CMTS(config)#show ip pim rp-hash

192.168.8.232
rp address :76.160.35.72
RP 76.160.35.72, v2
holdtime 1
Uptime: 14677:11:17:52, expires:0
PIMv2 Hash Value (mask 192.168.3.232)
Configuring the rendezvous point candidate

The RP candidate can be either a GigE interface or a loopback interface (number) at the CMTS.
The configured RP candidate advertises itself at a specified interval setting and priority for
possible election as the router over which all sources distribute traffic to the multicast group.
To configure an RP-candidate:
Step
1
Command (config)
Purpose
[no] ip pim rp-candidate {gige <number> | loopback <number>}

[group-list <string> | interval <seconds> | priority <range>]
Specify the RP
candidate.
Where :
<number>
The GigE or loopback interface number.
Use the no
form of the
command to
162
CASA CMTS
group-list
<string>
Optional: The name or number of the previouslyconfigured multicast access control list.
interval
<seconds>
Optional: The time in seconds to elapse between

RP candidate advertisements.
The metric used to select the RP candidate when
there are multiple RP candidates. 0 is the highest
priority; 255 is the lowest priority. The range is 0 to
255.
priority
<range>
Example:
CASA-CMTS(config)# ip pim rp-candidate gige1 priority
5
show ip pim rp [mapping]
show ip pim rp-hash <ip_address>
Where :
<ip_address>
delete the RP
candidate
assignment.
Display the RP
groups and
mappings.

rendezvous point.
Example :
CASA-CMTS(config)#show ip pim rp
Group(s) 224.0.0.0/4, Static
RP 143.1.1.1, static
CASA-CMTS(config)#show ip pim rp mapping
Group(s) 224.0.0.0/4
RP 192.168.3.232, v2
holdtime 150
Uptime: 0:0:44:8, expires: 148
CASA-CMTS(config)#show ip pim rp-hash 192.168.8.232

rp address :76.160.35.72
RP 76.160.35.72, v2
holdtime 1
Uptime: 14677:11:17:52, expires:0
PIMv2 Hash Value (mask 192.168.3.232)
163
CASA CMTS
Configuring the bootstrap router candidate

The bootstrap router (BSR) candidate can be either a GigE interface or a loopback interface
(number) at the CMTS. The BSR advertises itself as a candidate router for dynamically
distributing group-to-RP mapping information rapidly over the multicast domain. The BSR router
selection is based on priority, where the candidate with the highest priority becomes the BSR for
the multicast domain.
To configure a BSR-candidate:
Step
1
Command (config)
Purpose
[no] ip pim bsr-candidate {gige <number> | loopback

<number>} [<hash_mask> <piority>]
Specify the
bootstrap router
candidate.
Where :
<number>
<hash_mask>
<priority>
The GigE or loopback interface number.

Optional: 0 to 32 is the IP hash mask among
the RP candidates. This value specifies the
length (number of significant bits) to consider
when allocating distribution of multicast
groups among RP candidates. A longer hash
mask length results in fewer multicast groups
in each set of group addresses assigned to
the various RPs.
0 to 255 is the priority value for the candidate
bootstrap router. PIM-SM selects the BSR
candidate based on the priority setting. 0 is
the lowest priority; 255 is the highest priority.
The range is 0 to 255.
Example:
CASA-CMTS(config)# ip pim bsr-candidate gige1 10
5
show ip pim bsr-router
Use the no form of

the command to
delete the BSR
candidate
assignment.
Display the BSR

router configuration.
Example :
CASA-CMTS(config)#show ip pim bsr-router
This system is the Bootstrap Router (BSR)
BSR address:192.168.3.232
Uptime:
length:10
0:0:10:8,BSR Priority:0, Hash mask
Next bootstrap message in 7

Candidate RP: 192.168.3.232(gige 1)
Holdtime 150 seconds
Advertisement interval 60 seconds
Next advertisement in 7
164
CASA CMTS
Setting the Shortest Path Tree threshold

The Shortest Path Tree (SPT) threshold controls the multicast traffic rate (in Kbps) between the
rendezvous point and the traffic source, and whether all traffic sources use a shortest path source
tree or only shared trees (infinity).
To configure SPT thresholds:
1
[no] ip pim spt-threshold {<number > | infinity}

Where :
<number>
infinity
The traffic rate in kilobits per second (Kbps) .

The valid range is 1 to 4294967.
Prevents PIM sparse mode from switching to
a source tree; only shared trees are used
when infinity is set.
Example:
CASA-CMTS(config)# ip pim spt-threshold 1500
CASA-CMTA(config)# ip pim spt-threshold infinity
show ip pim spt-threshold
Purpose
Specify the SPT
threshold.
Use the no form of
the command to
delete the configured
SPT threshold.
Display the SPT

threshold setting.
Example :
CASA-CMTS(config)#show ip pim spt-threshold
ip pim spt-threshold 1500
Configuring source-specific multicast

Source-Specific Multicast (SSM) allows hosts to specify the source IP address range from which
to receive multicast traffic. SSM also allows hosts to subscribe to a specific multicast group. SSM
creates a source and group address pair (S,G) from which a host identifies a multicast data
stream.
To configure SSM:
1
[no] ip pim ssm {default | range <string>}

Where :
default
range
<string>
Specifies the group IP address range

232.255.0.0/8.
Specifies the group range associated with an
ACL name or number to be used with SSM.
Purpose
Specify the SSM
group range.
Use the no form of
the command to
remove the SSM
setting.
Example:
CASA-CMTS(config)# ip pim ssm default
CASA-CMTA(config)# ip pim ssm range acl1
165
CASA CMTS
Configuring the OSPF Routing Protocol

Casa CMTS supports IP-routing protocol OSPF (Open Shortest Path First). This section
describes the commands used to configure and monitor OSPF routing capabilities and features.
The OSPF commands are:
area authentication
area default-cost
area filter-list
area export-list
area import-list
area nssa
area range
area shortcut
area stub
area virtual-link
auto-cost
default-information
default-metric
distance
distribute-list
list
neighbor
network
ospf abr-type
passive-interface
refresh
router-id
timers
ip ospf authentication
ip ospf authentication-key
ip ospf cost
ip ospf hello-interval
ip ospf authentication
ip ospf message-digest-key
ip ospf retransmit-interval
ip ospf transmit-delay
show ip ospf
show ip ospf border-routers
166
CASA CMTS
show ip ospf database
show ip ospf interface
show ip ospf neighbor
show ip ospf route
show ip route
Entering OSPF configuration mode

To enter OSPF configuration mode:
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router)#
Exiting OSPF configuration mode

To exit OSPF Configuration mode:
Step
1
Command (config)
Purpose
end
Exit OSPF configuration

mode.
Example:
CASA-CMTS(config-router)# end
Enabling OSPF area authentication

To enable authentication for an OSPF area, use the area authentication command in router
configuration mode.
To remove an authentication specification of an OSPF area, use the no form of this command.
Purpose
1
router ospf
Enter OSPF
configuration mode.
Example:
167
CASA CMTS
[no] area <id> authentication [message-digest]
Enable or disable OSPF

area authentication.
Where:
<id>
The area identifier specified as either

a decimal value (04294967295) or an
IP address (A.B.C.D).
message-digest
Optional. Enables Message Digest 5

(MD5) authentication on the area
specified by the area-id argument.
Example:
Enable authentication for areas 10 of OSPF routing process:
CASA-CMTS(config-router)# area 10
authentication
Disable area authentication:
CASA-CMTS(config-router)# no area 10
authentication
Configuring the OSPF area default cost

To configure a cost for the default summary route, use the command area default-cost. To
remove an authentication specification of an OSPF area, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
2
[no] area <id> default-cost <cost>

Where:
<id>
Area identifier specified as either a decimal value (04294967295) or an IP address (A.B.C.D).
<cost>
Cost for the default summary route used for a stub or

NSSA. The acceptable value is a 24-bit number. The
default is 1. Valid values are from 0 to 16777215.
Configure or
disable a cost for
the default
summary route.
Example:
Assigns a default cost of 35 to stub network 192.168.3.2:
CASA-CMTS(config-router)# area 192.168.3.2 defaultcost 35
Disable a cost:
168
CASA CMTS
CASA-CMTS(config-router)# no area 192.168.3.2

default-cost 35
Configuring the OSPF area filter list

To filter prefixes between OSPF areas of an Area Border Router (ABR), use the filter-list
command. To cancel the filter, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] area <id> filter-list prefix {<list-name> in | out}
Where:
<id>

OSPF area filter list.
Area identifier specified as either a decimal value

(0-4294967295) or an IP address (A.B.C.D).
prefix
Keyword to indicate that a prefix list is used.
<listname>
Prefix list name.
in
Prefixes advertised to the specified area from

other areas.
out
Prefixes advertised out of the specified area from

other areas.
Example:
Filters prefixes that are sent from all other areas to area 3:
CASA-CMTS(config-router)# area 3 filter-list
prefix area_3 in
169
CASA CMTS
Configuring the OSPF area export list

To filter networks announced to other OSPF areas of an Area Border Router (ABR), use the area
export-list command. To cancel the filter, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
2
area <id> export-list <list-name>

Where:
<id>
<list-name>
Configure the OSPF

area export list.
Area identifier. It can be specified as either

a decimal value (0-4294967295) or an
name of an export list.
Example:
CASA-CMTS(config-router)# area 3 filter-list
prefix area_3 in
Remove or cancel a list:
CASA-CMTS(config-router)# no area 3 filterlist prefix area_3 in
Configuring the OSPF area import list

To filter for networks from other areas announced to a specified one, use the area import-list
command. To cancel the filter, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
2
[no] area id import-list <list-name>

Where:
Id
Configure or remove the

OSPF area import list.
Area identifier specified as either a

decimal value (0-4294967295) or an
170
CASA CMTS
<list-name>
Import list name.
Configuring the OSPF area NSSA

To configure an area as a not-so-stubby area (NSSA), use the nssa command. To remove the
NSSA distinction from the area, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
[no] area <id> nssa [translate-always | translate-candidate |
translate-never] [no-summary]
Where:
<id>
Configure or
remove OSPF
Area NSSA

decimal value (0-4294967295) or an IP
address (A.B.C.D).
translate-always
Optional. Configure NSSA-ABR to

always translate.
translate-candidate
Optional. Configure NSSA-ABR for

translate election.
translate-never
Optional. Configure NSSA-ABR to

never translate.
no-summary
Optional. Do not inject inter-area

routes into NSSA.
Example:
Make area 3 a NSSA area with translate-always:
CASA-CMTS(config-router)# area 3 nssa translatealways no-summary
Remove NSSA configuration:
CASA-CMTS(config-router)# no area 3 nssa
translate-always no-summary
171
CASA CMTS
Configuring the OSPF area range

To consolidate and summarize routes at an area boundary, use the area range command in
router configuration mode. To disable this function, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
[no] area <id> range <ip-address>/<mask> [advertise | notadvertise] [cost <cost>]
Where:
<id>
Configure or
disable the OSPF
area range.
Area identifier specified as either a decimal

value (04294967295) or an IP address
(A.B.C.D).
<ip-address>
IP address with mask in the form of

A.B.C.D/M.
<mask>
Mask prefix of the IP address.
advertise
Optional. Set the address range status to

advertise and generate a Type 3 summary
link-state advertisement (LSA).
not-advertise
Optional. Set the address range status to

DoNotAdvertise. The Type 3 summary LSA
is suppressed; the component networks
remain hidden from other networks.
<cost>
Optional. Metric or cost for this summary

route, which is used during OSPF SPF
calculation to determine the shortest paths to
the destination. The range of this value is from
0 to 16777215.
Example:
Specify one summary route to be advertised by the ABR to other
areas for all subnets on network 192.168.2.3/24 with cost 20:
CASA-CMTS(config-router)# area 3 range
192.168.2.3/24 cost 20
Disable:
CASA-CMTS(config-router)# no area 3 range
192.168.2.3/24 cost 20
172
CASA CMTS
Configuring the OSPF area shortcut

To configure the areas shortcutting mode, use the area shortcut command in router configuration
mode. To disable this function, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
2
[no] area <id> shortcut {enable | disable | default}

Where:
<id>

OSPF area shortcut.

decimal value (04294967295) or an
enable
Enable shortcutting through the area.
disable
Disable shortcutting through the area.
default
Set default shortcutting behavior.
Example:
CASA-CMTS(config-router)# area 3 SC enable
Disable:
CASA-CMTS(config-router)# no area 3 SC enable
Configuring the OSPF area stub

To enable an area as a stub area, use the area stub command in router Configuration mode. To
disable this function, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
2
[no] area <id> stub [no-summary]

Where:
<id>
no-summary
Enable or disable
the OSPF area
stub.
Area identifier specified as either a decimal value

(04294967295) or an IP address (A.B.C.D).
Optional. Prevents an Area Border Router (ABR)
from sending summary link advertisements into
the stub area.
173
CASA CMTS
Example:
Enable stub in area 3:
CASA-CMTS(config-router)# area 3 stub
Disable:
CASA-CMTS(config-router)# no area 3 stub
Configuring the OSPF area virtual link

To define an OSPF virtual link, use the area virtual-link command in router configuration mode
with the optional parameters. To remove a virtual link, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Example:
[no] area <id> virtual-link <router-id> [authentication [messagedigest|null]] [hello-interval <num>] [retransmit-interval <num>]
[transmit-delay <num>] [dead-interval <num>] [[authenticationkey <key>] | [message-digest-key <key-id> md5 <key>]]
Enter OSPF
configuration
mode.
Configure or
remove the OSPF
area virtual link.
Where:
<id>

decimal value (0-4294967295) OR AN
<router-id>
Router ID associated with the virtual link

neighbor. The router ID appears in the
show ip ospf display and is internally
derived by each router from the interface
IP addresses. This value must be entered
in the format of an IP address. There is no
default.
messagedigest|null
Optional. Specifies authentication type

and if message-digest authentication is
used. If NULL, no authentication is used.
Overrides password or message digest
authentication if configured for the area.
hello-interval
<num>
Optional .Time (in seconds) between the

hello packets that the CMTS software
sends on an interface. Unsigned integer
value to be advertised in the hello
packets. The value must be the same for
all routers and access servers attached to
a common network. The default is
10 seconds. The range is from 1 to 8192.
retransmit-
Optional. Time (in seconds) between link
174
CASA CMTS
interval <num>
state advertisement (LSA)

retransmissions for adjacencies belonging
to the interface. Expected round trip delay
between any two routers on the attached
network. The value must be greater than
the expected round trip delay. The default
is 5 seconds. The range is from 1 to 8192.
transmit-delay
<num>
Optional. Estimated time (in seconds)

required to send a link state update
packet on the interface. Integer value that
must be greater than zero. LSAs in the
update packet have their age incremented
by this amount before transmission. The
default value is 1 second. The range is
from 1 to 8192.
dead-interval
<num>
Optional.Time (in seconds) that hello

packets are not seen before a neighbor
declares the router down. Unsigned
integer value. The default is four times the
hello interval, or 40 seconds. As with the
hello interval, this value must be the same
for all routers and access servers
attached to a common network. The
range is from 1 to 8192.
authenticationkey <key>
Optional. Password to be used by

neighboring routers. It is any continuous
string of characters that the user can
enter from the keyboard up to 8 bytes
long. This string acts as a key that will
allow the authentication procedure to
generate or verify the authentication field
in the OSPF header. This key is inserted
directly into the OSPF header when
originating routing protocol packets. A
separate password can be assigned to
each network on a per interface basis. All
neighboring routers on the same network
must have the same password to be able
to route OSPF traffic. The password is
encrypted in the configuration file if the
service password encryption command
is enabled. There is no default value.
messagedigestkey <key id>

md5 <key>
(Optional) Key identifier and password to

be used by neighboring routers and this
router for Message Digest 5 (MD5)
authentication. The keyid argument is a
number in the range from 1 to 255. The
key is an alphanumeric string of up to 16
characters. All neighboring routers on the
same network must have the same key
identifier and key to be able to route
OSPF traffic. There is no default value.
175
CASA CMTS
Example:
Establish a virtual link with MD5 authentication:
CASA-CMTS(config-router)# area 3 virtual-link
10.10.10.3 message-digest-key 3 md5 3fk4j5ry76
Configuring the OSPF interface auto cost

To control how OSPF calculates default metrics for the interface, use the auto-cost command.
To assign cost based only on the interface type, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] auto-cost reference-bandwidth <ref-bw>
Where:
<ref-bw>
Configure the OSPF

interface auto cost.
Rate in Mbps. The range is 1 to 4294967.

Default is 100.
Example:
Changes the cost of the FDDI link to 20:
CASA-CMTS(config-router)# auto-cost referencebandwidth 20
Assign cost based only:
CASA-CMTS(config-router)# no auto-cost
reference-bandwidth 20
Configuring OSPF-compatible RFC1583

To restore the method used to calculate summary route costs per RFC 1583, use the compatible
rfc1583 command in router configuration mode.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
176
CASA CMTS
[no] compatible rfc1583

or
[no] ospf rfc1583compatibility
Enable or disable RFC

1583 compatibility.
Example:
CASA-CMTS(config-router)# compatible rfc1583
Disable:
CASA-CMTS(config-router)# no compatible
rfc1583
Configuring OSPF control-distribution default information

To generate a default external route into an OSPF routing domain, uses the default-information
originate command in router configuration mode. To disable this feature, use the no form of this
command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] default-information originate [always] [metric
<metric-value>] [metric-type <type-value>] [route-map
<map-name>]
Where:
always
OSPF control-distribution
default Information.
Optional. Always advertises the

default route regardless of whether the
software has a default route.
metric <metricvalue>
Optional. Metric used for generating

the default route. If you omit a value
and do not specify a value using the
default-metric router configuration
command, the default metric value is
1. The value used is specific to the
protocol.
metric type
<type-value>
Optional. External link type associated

with the default route advertised into
the OSPF routing domain. It can be
one of the following values: 1 for Type
1 external route, 2 for Type 2 external
route. The default is type 2.
route-map <mapname>
Optional. Routing process will

generate the default route if the route
map is satisfied.
177
CASA CMTS
Example:
Specifies a metric of 50 for the default route redistributed into
the OSPF routing domain and an external metric type of Type
1:
CASA-CMTS(config-router)# default-information
originate metric 50 metric-type 1
Note: Route maps are not supported in Release 5.2.
Configuring the OSPF default metric

To set default metric values for the OSPF routing protocol, use the default-metric command. To
return to the default setting, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
2
[no] default-metric <metric-value>

Where:
metric-value
OSPF default metric
Default metric value appropriate for the

specified routing protocol. Valid values
are 0 to 16777214.
Example:
Set default-metric value to 20:
CASA-CMTS(config-router)# default-metric 20
Configuring the OSPF administrative distance

To define OSPF route administrative distances based on route type, use the distance ospf
command. To restore the default value, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
distance { <dist0> | ospf {intra-area <dist1> | inter-area <dist2> |
external <dist3> } }
Where:
Configure the
OSPF
administrative
distance.
178
CASA CMTS
<dist0>
Sets the distance for all routes within an

area. Valid values are 1 to 255. The default
value is 110.
intra-area <dist1>
Sets the distance for all routes within an

area. Valid values are 1 to 255. The default
value is 110.
intra-area <dist2>
Sets the distance for all routes from one

area to another area. Valid values are 1 to
255. The default value is 110.
external <dist3>
Sets the distance for routes from other

routing domains, learned by redistribution.
Valid values are 1 to 255. The default
value is 110.
Example:
Set the external distance to 200:
CASA-CMTS(config-router)# distance ospf external
200
Displaying the OSPF command list

To show the OSFP command list, follow the command provided below.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
list
Display the OSFP

command list.
Example:
Set the external distance to 200:
CASA-C3000(config-router)# list
area (A.B.C.D|<0-4294967295>) authentication
area (A.B.C.D|<0-4294967295>) authentication
message-digest
area (A.B.C.D|<0-4294967295>) default-cost
<0-16777215>
area (A.B.C.D|<0-4294967295>) export-list
NAME
area (A.B.C.D|<0-4294967295>) filter-list
prefix WORD (in|out)
area (A.B.C.D|<0-4294967295>) import-list
NAME
area (A.B.C.D|<0-4294967295>) nssa
area (A.B.C.D|<0-4294967295>) nssa
(translate-candidate|translateCasa CMTS Software Configuration Guide
179
CASA CMTS
never|translate-always)
area (A.B.C.D|<0-4294967295>) nssa
(translate-candidate|translatenever|translate-always) no-summary
area (A.B.C.D|<0-4294967295>) nssa no-summary
area (A.B.C.D|<0-4294967295>) range A.B.C.D/M
advertise
advertise cost <0-16777215>
Configuring the OSPF neighbor router

To configure OSPF routers interconnecting to non-broadcast networks, use the neighbor
command. To remove a configuration, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
[no] neighbor <ip-address> [priority <num>] [poll-interval
<num>]
Where:
<ip-address>
Configure the
OSPF neighbor
route.
Interface IP address of the neighbor.
priority <num>
Optional. A number that indicates the

router priority value of the nonbroadcast neighbor associated with the
IP address specified. Valid numbers
are 0 to 255. The default is 0.
Poll-interval <num>
Optional. A number value that

represents the poll interval time in
seconds. RFC 1247 recommends that
this value be much larger than the
hello interval. The default is 120
seconds.
Example:
This example declares a router at address 192.168.3.20 on a nonbroadcast network, with a priority of 1 and a poll interval of 140
seconds:
CASA-CMTS(config-router)# neighbor 192.168.3.20
priority 1 poll-interval 140
Note: This keyword does not apply to point-to-multipoint
interfaces. The range is from 1 to 65535 seconds.
180
CASA CMTS
Configuring OSPF routing on an IP network

To enable the interfaces on which OSPF runs and to define the area ID for those interfaces, use
the network area command. To disable OSPF routing for interfaces defined with the address
wildcard-mask pair, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Example:
[no] network <ip-address>/<mask_prefix> area <area-id>
Enter OSPF
configuration
mode.
Where:
<ip-address/mask>
Configure OSPF
routing on an IP
network.
IP address and mask in form of

A.B.C.D/M.
The area to be associated with the
OSPF address range. It can be specified
as either a decimal value or as an IP
address. To associate areas with IP
subnets, specify a subnet address as the
value of the area-id argument.
<area-id>
Example:
Defines two OSPF areas: 1 and 2. Areas 1 and 2 mask specific
address ranges:
CASA-CMTS(config-router)# network 10.10.10.0/24
area 1
CASA-CMTS(config-router)# network 10.10.20.1/24
area 2
Configuring the OSPF ABR type

To configure OSPF ABR type, use the ospf abr-type command. To remove configured OSPF
ABR type, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] ospf abr-type [cisco | ibm | shortcut | standard]
Where:
cisco
Configure the OSPF

ABR type.
Alternative ABR in Cisco implementation.
181
CASA CMTS
ibm
Alternative ABR in IBM implementation.
shortcut
Shortcut ABR in Cisco implementation.
standard
Standard behavior (RFC2328).
Example:
Set ABR type to cisco:
CASA-CMTS(config-router)# ospf abr-type cisco
Configuring the OSPF route ID

To use a fixed router ID, use the ospf router-id command in router configuration mode. To force
OSPF to use the previous OSPF router ID behavior, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] ospf router-id <router_id>
Where:
<router_id>
Configure or remove the

OSPF route ID.
OSPF router id in IP address format.
Example:
CASA-CMTS(config-router)# ospf router-id
192.168.3.20
Configuring the OSPF passive interface

To suppress routing updates on an interface, use the passive-interface command. To disable
this feature, use the no form of this command.
Step
Command
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
2
[no] passive-interface {dmac | gige | vlan} <id> [<ip_address>]

Where:
<id>
<ip_address>
Configure or remove
the OSPF passive
interface command.
GigE port ID, docsis-mac ID, or VLAN ID

IP address of the interface in the form
182
CASA CMTS
A.B.C.D.
Example:
Configure OSPF passive interface ifname with address
10.10.10.3:
CASA-CMTS(config-router)# passive-interface gige
1 10.10.10.3
Configuring the OSPF distribute list

To filter networks in routing updates, use the distribute-list command. To restore the default
value, use the no form of this command.
Step
1
Command (config)
Purpose
router ospf
Enter OSPF
configuration
mode.
Example:
[no] distribute-list <list-name> out { bgp | connected | kernel | rip
| static }
Where:
<list-name>
Configure or
disable the OSPF
default metric.
Standard IP access list name. The list defines

which networks are to be received and which are
to be suppressed in routing updates.
in
Applies the access list to incoming routing

updates.
out
Applies the access list to incoming routing

updates. The out keyword is available only in
router configuration mode.
bgp
Optional. Applies the access list to BGP routes.
connected
Optional. Applies the access list to connected

routes.
ospf
Optional. Applies the access list to OSPF routes

(not the current OSPF process).
static
Optional. Applies the access list to staticallyconfigured routes.
Example:
CASA-CMTS(config-router)# distribute-list list1 out
static
If this command is not specified in the interface configuration mode, then the interface adopts the
distribute list parameter specified by the area. If this command is not specified in the area
183
CASA CMTS
configuration mode, then the interface adopts the distribute list parameter specified for the
process. If this command is not specified at any level, then the distribute list is disabled.
Configuring OSPF redistribute information

This command redistributes routes from another routing protocol.
Step
Command (config)
Purpose
router ospf
Example:
redistribute {bgp | connected | kernel | rip | static}
Enter OSPF
configuration
mode.
Where:
bgp
Applies the access list to BGP routes.
connected
Applies the access list to connected routes.
ospf
Applies the access list to OSPF routes (not the

current OSPF process).
static
Applies the access list to statically-configured

routes.
Configure OSPF
redistribute
information.
Example:
Configure OSPF to redistribute routes from static routes:
CASA-CMTS(config-router)# redistribute static
Configuring the OSPF refresh parameters

To adjust OSPF refresh parameters, use the refresh command. To reset OSPF refresh
parameters, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Example:
[no] refresh timer <num>
Enter OSPF
configuration
mode.
Where:
<num>
Configure the
OSPF refresh
parameters.
Timer value in the range 10 to 1800 seconds.
Example:
Set OSPF refresh value to 100 :
CASA-CMTS(config-router)# refresh timer 100
184
CASA CMTS
Configuring the OSPF route ID

To use a fixed router ID, use the router-id command in router configuration mode. To force OSPF
to use the previous OSPF router ID behavior, use the no form of this command.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] route-id <ip-address>
Where:
<ip-address>

OSPF route ID.
Router ID in IP address format.
Example:
CASA-CMTS(config-router)# route-id
192.168.3.20
Configuring the OSPF routing timers

To configure the OSPF routing timer, use the timers spf command. To restore the default value,
use the no form of this command.
Step
Command (config)
Purpose
router ospf
Enter OSPF
configuration mode.
Example:
[no] timers spf <delay-time> <hold-time>
Where:
<delay-time>
<hold-time>

OSPF routing timer.
Delay between receiving a change to SPF

calculation in the range 0 to 4294967295
in milliseconds. The default value is 33
milliseconds.
Hold between consecutive SPF
calculations in the range 0 to 4294967295
in milliseconds. The default value is 33
milliseconds.
Example:
Configures routing timer in 60-millisecond intervals and
holding for 40 milliseconds:
185
CASA CMTS
CASA-CMTS(config-router)# timers spf 60 40
Configuring IP OSPF authentication

To specify the authentication type for an interface, use the ip ospf authentication command in
interface configuration mode. To remove the authentication type for an interface, use the no form
of this command.
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
Example:
[no] timers spf <delay-time> <hold-time ip ospf
authentication [message-digest | null]
Where:
Message-digest
null
Configure or disable IP
OSPF Authentication.
Optional. Specifies that message

digest authentication will be used.
Optional. No authentication is
used. Useful for overriding
password or message digest
authentication if configured for an
area.
The area default is no authentication (null authentication).

Example:
Enables message-digest authentication:
CASA-CMTS(config-if-gige 0)# ip ospf
authentication message-digest
Configuring the IP OSPF authentication-key

To assign a password to be used by neighboring routers that are using the OSPF simple
password authentication, use the ip ospf authentication-key command in interface configuration
mode. To remove a previously assigned OSPF password, use the no form of this command.
186
CASA CMTS
Step
1
Command (config)
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>

C2200.
Example:
[no] ip ospf authentication-key <password>
Where:
<password>
OSPF password
authentication.
Any continuous string of characters that

can be entered from the keyboard up to 8
bytes in length.
Example:
Enables the authentication key with password neighbor:
CASA-CMTS(config-if-gige 0)# ip ospf
authentication-key neighbor
Configuring the IP OSPF cost

To explicitly specify the cost of sending a packet on an interface, use the ip ospf cost command
in interface configuration mode. To reset the path cost to the default value, use the no form of this
command.
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
Example:
[no] ip ospf cost <if-cost>
Where:
<if-cost>

IP OSPF cost.
Unsigned integer value expressed as the link

state metric in the range from 1 to 65535.
Example:
Set the interface cost value to 40:
187
CASA CMTS
CASA-CMTS(config-if-gige 0)# ip ospf cost 40
Configuring the IP OSPF dead interval

To set the interval during which at least one hello packet must be received from a neighbor before
the router declares that neighbor down, use the ip ospf dead-interval command in interface
configuration mode.
To restore the default value, use the no form of this command.
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip ospf dead-interval <num>
Where:
<num>
the IP OSPF dead
interval.
Interval (in seconds) during which the router must

receive at least one hello packet from a neighbor or
else that neighbor is removed from the peer list and
does not participate in routing. The range is 1 to
65535. The value must be the same for all nodes on
the network.
The default is four times the interval set by the ip ospf hellointerval.
Example:
Set the OSPF dead interval to 33 seconds:
CASA-CMTS(config-if-gige 0)# ip ospf deadinterval 33
188
CASA CMTS
Configuring the IP OSPF Hello interval

To specify the interval between hello packets that the CMTS software sends on the interface, use
the ip ospf hello-interval command in interface configuration mode. To return to the default time,
use the no form of this command.
Step
1
Command (config)
Enter GigE
interface mode.

Where:
<port>
Purpose

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip ospf hello-interval <num>
Where:
<num>
Specifies the interval (in seconds). The value must

be the same for all nodes on a specific network.
The range is 1 to 65535 seconds.
Configure or
disable the IP
OSPF Hello
interval.
The default is 10 seconds for Ethernet, or 30 seconds for nonbroadcast.

Example:
Set the interval between hello packets to 26 seconds:
CASA-CMTS(config-if-gige 0)# ip ospf hellointerval 26
Configuring the IP OSPF message digest key

To enable OSPF Message Digest 5 (MD5) authentication, use the ip ospf message-digest-key
command in interface configuration mode. To remove an old MD5 key, use the no form of this
command.
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
189
CASA CMTS
[no] ip ospf message-digest-key <key-id> md5 <key>

Where:
<key-id>
<key>
Enable or disable
the IP OSPF
message digest key.
An identifier in the range from 1 to 255.

Alphanumeric password of up to 16 bytes.
By default, OSPF MD5 authentication is disabled.

Example:
Set a new key 19 with the password 1007:
CASA-CMTS(config-if-gige 0)# ip ospf messagedigest-key 12 md5 1007
Configuring the IP OSPF retransmit interval

To specify the time between link-state advertisement (LSA) retransmissions for adjacencies
belonging to the interface, use the ip ospf retransmit-interval command in interface
configuration mode. To return to the default value, use the no form of this command.
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip ospf retransmit-interval <num>
Where:
<num>
Enable or disable
the IP OSPF
retransmit interval.
Time (in seconds) between retransmissions. It

must be greater than the expected round trip delay
between any two routers on the attached network.
The range is from 1 to 65535 seconds. The default
is 5 seconds.
Example:
Set the retransmit interval value to 10 seconds:
CASA-CMTS(config-if-gige 0)# ip ospf retransmitinterval 10
190
CASA CMTS
Configuring the IP OSPF transmit delay

To set the estimated time required to send a link-state update packet on the interface, use the ip
ospf transmit-delay command in interface configuration mode. To return to the default value, use
the no form of this command.
Step
1
Command (config)
Purpose
Enter GigE Ethernet

interface mode.
Where:
<port>

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip ospf transmit-delay <num>
Where:
<num>
Enable or disable
the IP OSPF
transmit delay.
Time (in seconds) required to send a link state

update. The range is1 to 65535 seconds. The default
setting is 1 second.
Example:
Set the transmit delay value to 10 seconds:
CASA-CMTS(config-if-gige 0)# ip ospf transmitdelay 10
Displaying OSPF general information

To display general information about Open Shortest Path First (OSPF) routing processes, use the
show ip ospf command.
Step
1
Command (config)
Purpose
show ip ospf
Display OSPF
general
information.
Example:
CASA-CMTS(config)# show ip ospf
OSPF Routing Process, Router ID: 192.168.3.95
Supports only single TOS (TOS0) routes
This implementation conforms to RFC2328
RFC1583Compatibility flag is disabled
SPF schedule delay 1 secs, Hold time between two
SPFs 1 secs
Refresh timer 10 secs
Number of external LSA 0. Checksum Sum 0x0000000
Number of area attached to this router: 1
Area ID: 0.0.0.0 (Backbone)
191
CASA CMTS
Number of interfaces in this area: Total: 1,

Active: 1
Number of fully adjacent neighbors in this area: 2
Area has no authentication
SPF algorithm executed 30 times
Number of router LSA 3. Checksum Sum0x0001c3bf
Number of network LSA 1. Checksum Sum0x0000449d
Number of summary LSA 1. Checksum Sum0x0000332c
Number of ASBP summary LSA 0. Checksum
Sum0x00000000
Number of NSSA LSA 0. Checksum Sum0x00000000
Displaying the OSPF internal routing table entries

To display the internal OSPF routing table entries to an Area Border Router (ABR) and
Autonomous System Boundary Router (ASBR), use the show ip ospf border-routers command.
Step
1
Command (config)
Purpose
show ip ospf border-routers
Display the OSPF

internal routing table
entries.
Example:
CASA-CMTS(config)# show ip ospf border-routers
Displaying the OSPF database for a specified router

To display lists of information related to the OSPF database for a specific router, use the show ip
ospf database command.
Step
1
Command (config)
Purpose
show ip ospf database
Display the OSPF

database for a specified
router.
Example:
CASA-CMTS(config)# show ip ospf database
Displaying OSPF interface information

To display OSPF related interface information, use the show ip ospf interface command.
Step
1
Command (config)
Purpose
show ip ospf interface
Display OSPF interface

information.
Example:
CASA-CMTS(config)# show ip ospf interface
192
CASA CMTS
Displaying OSPF neighbor information

To display OSPF neighbor information on a per-interface basis, use the show ip ospf neighbor
command.
Step
1
Command (config)
Purpose
show ip ospf neighbor [neighbor-id] [detail]
Display OSPF
neighbor
information.
Where:
neighbor-id
detail
Optional. Neighbor ID in form of A.B.C.D.

Optional. Displays all neighbors in detail.
Displaying the OSPF routing table

To display the current state of the routing table, use the show ip route command.
Purpose
1
Display the OSPF

routing table.
show ip ospf route

Example:
CASA-CMTS(config)# show ip ospf route
Displaying IPv4 route information

To display IPv4 route information, use the show ip route command.
Step
1
Command (config)
Purpose
show ip route [a.b.c.d | a.b.c.d/m | connected | kernel | ospf |

static | bgp | rip | supernets-only ]
Display IPv4 OSPF

routing information.
Where:
a.b.c.d
Internet address in standard format.
IP mask.
bgp
Border Gateway Protocol routes.
connected
Connected routes.
kernel
Kernel routes.
isis
IS-IS routes.
ospf
OSPF routes.
static
Static routes.
rip
Routing Information Protocol routes.
193
CASA CMTS
supernets-only
Supernets.
Example:
CASA-CMTS(config)# show ip route
Codes:
K Kernel route, C - connected, S
static, R RIP, O OSPF,
I ISIS, B BGP, > - selected
route, * - FIB route
C>* 10.109.2.0/24 is directly connected, bcm3
C>* 127.0.0.0/8 is directly connected, lo
C>* 10.168.2.0/24 is directly connected, eth0
CASA-CMTS(config)#

To display IPv6 route Information, use the show ipv6 route command.
Step
1
Command (config)
Purpose
show ipv6 route [a.b.c.d | a.b.c.d/m | connected | kernel | isis |

ospf | static | rip | bgp | supernets-only ]
Display IPv6 OSPF

routing information.
Where:
a.b.c.d
IP mask.
bgp
connected
Connected routes.
kernel
Kernel routes.
isis
IS-IS routes.
ospf
OSPF routes.
static
Static routes.
rip
supernets-only
Supernets.
Example:
CASA-CMTS(config)# show ipv6 route
Sample OSPF configurations

Example 1:
194
CASA CMTS
Run OSPF actively on the gige interface, and redistribute the connected network in OSPF. All the
IP bundle networks will be injected into OSPF as external OSPF routes.
Step
Command (config)
Purpose
CASA-CMTS# config
CASA-CMTS(config)#
Enter configuration
mode.

Enter OSPF
configuration mode.
CASA-CMTS(config-router)# redistribute
connected
Configure OSPF
redistribute information.
CASA-CMTS(config-router)# network
192.168.3.0/24 area 0.0.0.0
Configure the network
Example 2:
Run OSPF actively on the GigE interface.
Step
Command (config)
Purpose
CASA-CMTS# config
CASA-CMTS(config)#
Enter configuration
mode.

Enter OSPF
CASA-CMTS(config-router)#network
192.168.3.0/24 area 0.0.0.0
CASA-CMTS(config-router)#network 10.237.1.0/24
area 0.0.0.0
CASA-CMTS(config-router)#network 10.237.2.0/24
area 0.0.0.0
Configure the network.
configuration mode.
Configuring the Routing Information Protocol

The Casa CMTS supports IP-routing protocol RIP (Routing Information Protocol). This section
describes the commands used to configure and monitor RIP routing capabilities and features.
The commands are:
default-information
default-metric
distance
distribute-list
list
neighbor
195
CASA CMTS
network
offset-list
passive-interface
route
router-map
timers
version
ip rip authentication key-chain
ip rip authentication string
ip rip authentication mode
show ip rip
show ip rip status
show ip rip route
Entering RIP configuration mode

To enter RIP configuration mode:
Step
1
Command (config)
Purpose
router rip
Enter RIP configuration

mode.
Example :
CASA-CMTS(config)# router rip
Exiting RIP configuration mode

To exit RIP configuration mode:
Step
1
Command (config)
Purpose
End
Exit RIP configuration

mode.
Example :
CASA-CMTS(config-router)# end
Configuring the RIP default route

To generate a default route into RIP, use the default-information originate command in router rip
configuration mode. To disable this feature, use the no form of this command.
196
CASA CMTS
Step
1
Command (config)
Purpose
router rip

mode.
Example :
2
[no] default-information originate
Configure or disable RIP

default route.
Example:
Distribute a default route:
CASA-CMTS(config-router)#default-information
originate
Configuring the RIP default metric

To set default metric values for RIP, use the default-metric command in router rip configuration
mode. To return to the default state, use the no form of this command.
Step
1
Command (config)
Purpose
router rip

mode.
Example :
2
[no] default-metric <metric-value>

Where:
<metric-value>
Configure or cancel
default metric values for
RIP.
Default metric value in the range 1 to 16.
Example:
Assign the OSPF-derived routes a RIP metric of 10:
CASA-CMTS(config-router)# default-metric 10
197
CASA CMTS
Configuring the RIP administrative distance

To define RIP route administrative distances based on route type, use the distance command in
router rip configuration mode. To restore the default value, use the no form of this command.
Step
Command (config)
Purpose
router rip
Example :
Enter RIP
configuration mode.
[no] distance <value> [<ip-address>/<mask_prefix> [name]]
Configure RIP
administrative
distance.
Where:
<value>
Distance value in the range 1 to

255.
<ip-address>/
<mask_prefix>
Optional. IP source prefix, in the

format A.B.C.D/M with mask
prefix.
name
access list name
Example:
Change the RIP routing distance to 100:
CASA-CMTS(config-router-rip)# distance 100
Configuring the RIP filter list

To filter prefixes between RIP areas of an Area Border Router (ABR), use the distribute-list
command in router rip configuration mode. To cancel the filter, use the no form of this command.
Step
1
Command (config)
Purpose
router rip

mode.
Example :
2
[no] distribute-list {<access-list> | prefix <list> {in | out [iflist] } }

Where:
access-list
Configure the RIP filter

list.
Access list name.
prefix
Indicate that a prefix list is used.
list
Name of IP prefix-list.
in
Prefixes advertised to the specified area
198
CASA CMTS
from other areas.

out
Prefixes advertised out of the specified area

from other areas.
if-name
Optional. Interface name
Example:
CASA-CMTS(config-router)# distribute-list
prefix area_3 in
Displaying the RIP command list

To show the RIP command list, use the list command in router rip configuration mode.
Step
Command (config)
Purpose
router rip

mode.
Example :
list
Configure the RIP

command list.
Example:
CASA-CMTS(config-router)# list
default-information originate
default-metric <1-16>
distance <1-255>
distance <1-255> A.B.C.D/M
distance <1-255> A.B.C.D/M WORD
distribute-list WORD (in|out)
distribute-list WORD (in|out) WORD
distribute-list prefix WORD (in|out)
distribute-list prefix WORD (in|out) WORD
end
exit
list
neighbor A.B.C.D
network (A.B.C.D/M|WORD)
no default-information originate
no default-metric
no default-metric <1-16>
no distance <1-255>
no distance <1-255> A.B.C.D/M
no distance <1-255> A.B.C.D/M WORD
no distribute-list WORD (in|out)
no distribute-list WORD (in|out) WORD
no distribute-list prefix WORD (in|out)
no distribute-list prefix WORD (in|out) WORD
no neighbor A.B.C.D
199
CASA CMTS
Configuring the RIP neighbor router

To define a neighboring router with which to exchange routing information, use the neighbor
command in router rip configuration mode. To remove an entry, use the no form of this command.
Step
1
Command (config)
Purpose
router rip

mode.
Example :
2
[no] neighbor <ip-address>

Where:
<ip-address>
Configure RIP neighbor

router.
IP address of a peer router with which

routing information will be exchanged.
Example:
Send RIP updates to all interfaces on network 10.10.10.3:
Configuring RIP routing on an IP network

To specify a list of networks for the RIP routing process, use the network command in router rip
configuration mode. To remove an entry, use the no form of this command.
Step
Command (config)
Purpose
router rip

mode.
Example :
[no] network {<ip-address>/<mask_prefix> | <if-name> }>
Where:
<ip-address>/
<mask_prefix>
<if-name>
Configure or remove RIP

routing on an IP network.
IP address directly connected

networks, in the form of A.B.C.D/M.
Interface name.
Example:
Defines RIP as the routing protocol to be used on all
interfaces connected to networks 10.10.10.3 and 192.168.3.4:
10.10.10.3/24
200
CASA CMTS
192.168.3.4/24
Configuring the RIP offset list

To add an offset to incoming and outgoing metrics to routes learned via RIP, use the offset-list
command in router rip configuration mode. To remove an offset list, use the no form of this
command.
Step
1
Command (config)
Purpose
router rip
Enter RIP
configuration
mode.
Example :
2
[no] offset-list <list-name> {in | out} <metric_value> [if-name]

Where:
<list-name>
Configure the RIP

offset list.
Standard access list name to be applied.
in
Applies the access list to incoming

metrics.
out
Applies the access list to outgoing

metrics.
<metric_value>
Valid values are from 0 to 16.
<if-name>
(Optional) Interface type to which the

offset list is applied.
Example:
Applies an offset of 15 to the delay component of a router only to
access list acl2:
CASA-CMTS(config-router)# offset-list acl2 out 15
201
CASA CMTS
Configuring the RIP passive interface

To disable sending routing updates on an interface, use the passive-interface command in router
RIP configuration mode. To re-enable the sending of routing updates, use the no form of this
command.
Step
1
Command (config)
Purpose
router rip

mode.
Example :
2
[no] passive-interface { <if-name> | default }

Where:
<if-name>
default
Name of the interface to become passive.
Configure RIP passive

interface or enable
sending of route
updates.
All interfaces become passive.
Example:
CASA-CMTS(config-router)# passive interface
default
Configuring RIP redistribute information

This command redistributes routes from another routing protocol.
Step
1
Command (config)
Purpose
router rip

mode.
Example :
2
redistribute { bgp | connected | kernel | ospf | static }

Where:
bgp
Configure RIP
redistribute Information.
Border Gateway Protocol (BGP)
connected
Connected protocol
kernel
Same as static
ospf
Open Shortest Path First protocol
static
Static routes.
Example:
Configure RIP to redistribute routes from static routes:
CASA-CMTS(config-router)# redistribute static
202
CASA CMTS
Configuring RIP static routes

To configure RIP static route, use the route command in router rip configuration mode. To remove
the route, use the no form of this command.
Step
1
Command (config)
Purpose
router rip

mode.
Example:
2
[no] route <ip-address>/<mask_prefix>

Where:
<ip-address>/
<mask_prefix>
Configure or remove RIP

static routes.
IP address and mask in the

format A.B.C.D/M.
Example:
CASA-CMTS(config-router)# route 192.168.2.3/24
Configuring the RIP router map

To define the conditions for redistributing routes from one routing protocol into another, or to
enable policy routing, use the route-map command. To delete an entry, use the no form of this
command.
Step
1
Command (config)
Purpose
router rip
Enter RIP
configuration mode.
Example :
CASA-CMTS(config-router-rip)#
2
[no] route-map <map-tag> {in | out <if-name> }

Where:
<map-tag>
Configure or delete
the RIP static route
map.
Defines a meaningful name for the route map.

Multiple route maps may share the same map
tag name.
in
Route map set for input filtering.
out
Route map set for output filtering.
<if-name>
Route map interface name
Example:
203
CASA CMTS
CASA-CMTS(config-router-rip)# route-map test in

gige2
Note: Route maps are not supported in 5.2.
Configuring the RIP routing timers

To adjust RIP network timers, use the timer basic command. To restore the default timers, use
the no form of this command.
Step
1
Command (config)
Purpose
router rip
Enter RIP
configuration mode.
Example :
2
[no] timers basic <update_timer> <timeout_timer>

garbage_col_timer>
Where:
<update_timer>
Configure RIP
routing timers.
Rate (in seconds) at which updates

are sent. This is the fundamental
timing parameter of the routing
protocol. Values are 5 to
2147483647. The default is 30
seconds.
<timeout_timer>
Routing information timeout timer in

the range 5 to 2147483647 seconds.
The default is 180 seconds.
<garbage_col_timer>
Garbage collection timer in the range

5 to 2147483647. The default is 120
seconds.
Example:
Set updates to be broadcast every 5 seconds. If a router is not
heard from in 15 seconds, the route is declared unusable. Further
information is suppressed for an additional 15 seconds:
CASA-CMTS(config-router)# timers basic 5 15 15
Configuring the RIP version

To specify a RIP version used globally by the router, use the version command. To restore the
default value, use the no form of this command.
204
CASA CMTS
Step
Command (config)
Purpose
[no] version {1 | 2}
Configure the RIP

version running on the
CMTS.
Where:
1 - Specifies first RIP Version.
2 -Specifies RIP second Version.
Example:
CASA-CMTS(config-router)# version 2

command to restore the
default version.
Configuring the IP RIP authentication key chain

To enable authentication of RIP packets, use the ip authentication key-chain command in
interface configuration mode. To disable such authentication, use the no form of this command.
The authentication key chain can be configured on a GigE interface or an IP bundle interface.
Step
1
Command (config)
Purpose

mode.
Where:
<port>
GigE t port number in the range 0 to 11 for

C3200/C10200 and 0 to 3 for C2200.
Example:
[no] ip rip authentication key-chain <name>
Where:
<name>

RIP authentication Key
chain.
Name of the authentication key chain.
Example:
Applies authentication to autonomous system school:
CASA-CMTS(config-if-gige 0)# ip rip
authentication key-chain school
Disable:
CASA-CMTS(config-if-gige id)# no ip rip
authentication key-chain
Configuring an IP RIP authentication string

To enable authentication string, use the ip authentication string command in interface
configuration mode. To disable such authentication, use the no form of this command. The
authentication string can be configured on a gigabit interface or an IP bundle interface.
205
CASA CMTS
Step
1
Command (config)
Purpose

mode.
Where:
<port>

C2200.
Example:
[no] ip rip authentication string <name>
Where:
<name>

RIP authentication string.
Authentication string name up to 16 characters.
Example:
Configure authentication string as public:
authentication string public
Disable:
CASA-CMTS(config-if-gige id)# no ip rip
authentication string
Configuring the IP RIP authentication mode

To specify the type of authentication used in RIP packets, use the ip authentication mode
command in interface configuration mode. To disable that type of authentication, use the no form
of this command.
Step
1
Command (config)
Purpose

mode.
Where:
<port>
GigE port number. Valid values are 0

to 11 for C3200/C10200 and 0 to 3 for
C2200.
Example:
[no] ip rip authentication mode { text | md5 [auth-length
rfc] }
Where:
text
RIP authentication
mode.
Text authentication mode.
206
CASA CMTS
MD5 authentication mode.
md5
Example:
Configure the interface to use MD5 authentication:
authentication mode md5 auth-length rfc
Displaying RIP routing information

To display routing information about RIP routing processes, use the show ip rip command.
Step
1
Command (config)
Purpose
show ip rip
Display RIP routing

information.
Example:
CASA-CMTS(config)# show ip rip
Codes: R RIP, C connected, S static, O
OSPF, B BGP
Sub-codes:
(n) normal, (s) static, (d) default.
(r) redistribute, (i) - interface
Network
Metric From Tag Time
C(i) 192.168.3.0/24
1 self
0
Next Hop
0.0.0.0
Displaying RIP status information

To display status information about RIP routing processes, use the show ip rip status command.
Step
Command (config)
Purpose
show ip rip status
Display RIP status

information.
Example:
CASA-CMTS(config)# show ip rip status
Routing Protocol is rip
Sending updates every 30 seconds with +/-50%
next due in 4 seconds
Timeout after 180 seconds, garbage collect
after 120 seconds
Outgoing update filter list for all interface
in not set
Incoming update filter list for all interface
in not set
Default redistribution metric is 1
Redistributing:
Default version control: send version 2,
receive any version
Interface
Send Recv Key-chain
207
CASA CMTS
Bcm2
2
1
2
Routing for Networks:
192.168.3.0/24
Routing Information Sources:
Gateway
Badpackets BadRoutes
Distance
Last Update
Distance: (default is 120)
CASA-CMTS(config)#
Displaying IP route Information

To display IP route information, use the show ip route command.
Step
1
Command (config)
Purpose
show ip route [a.b.c.d | a.b.c.d/m | connected | kernel | isis

| static | rip | bgp| ospf | supernets-only ]
Display IP route
information.
Where:
a.b.c.d
IP mask.
bgp
connected
Connected routes.
kernel
Kernel routes.
isis
IS-IS routes.
ospf
OSPF routes.
static
Static routes.
rip
supernets-only
Supernets.
Example:
CASA-CMTS(config)# show ip route
Codes:
K Kernel route, C - connected, S
static, R RIP, O OSPF,
I ISIS, B BGP, > - selected
route, * - FIB route
C>* 127.0.0.0/8 is directly connected, lo
C>* 10.168.2.0/24 is directly connected, eth0
C>* 10.168.66.0/24 is directly connected,
bcm26
CASA-CMTS(config)#
208
CASA CMTS

To display IPv6 route information, use the show ipv6 route command.
Step
1
Command (config)
Purpose
show ipv6 route [a.b.c.d | a.b.c.d/m | connected | kernel |

isis | rip | static | bgp| ospf | rip | supernets-only ]
Display IPv6 route

information.
Where:
a.b.c.d
IP mask.
bgp
connected
Connected routes.
kernel
Kernel routes.
isis
IS-IS routes.
ospf
OSPF routes.
static
Static routes.
rip
supernets-only
Supernets.
Example:
CASA-CMTS(config)# show ipv6 route
Configuring the BGP Routing Protocol (Release 5.4 only)

BGP configuration tasks are discussed in the following sections:
Enable BGP routing
BGP decision process
BGP network
BGP peers
BGP address family
Autonomous system
BGP communities
Displaying BGP routes
Capability negotiation
Route reflector
209
CASA CMTS
Enabling BGP routing

To configure BGP routing, you need the autonomous system number (ASN). The ASN identifies
the autonomous system. BGP protocol uses the ASN for detecting whether the BGP connection
is an internal one or an external one.
To enable a BGP protocol process with the specified autonomous system number (ASN), use the
BGP router command. This puts you in router configuration mode. After this statement you can
input any BGP commands. You cannot create different BGP processes under different ASNs
without specifying multiple-instance, as described later in this section.
Step
1
Command (config)
Purpose
[no] router bgp <asn>
Enable or disable BGP

routing.
Where:
<asn>
The autonomous system number in the

range 1 to 65535.
Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
To specify the router-ID, using the following command:

Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
The autonomous system number in the

range 1 to 65535.
Example:
bgp router-id A.B.C.D
Specify the router-ID.
Example:
CASA-CMTS(config-router-bgp)# bgp router-id
A.B.C.D
210
CASA CMTS
Setting the BGP distance

To change the distance value of BGP, use the distance command. Each argument is the
distance value for external routes, internal routes and local routes.
Step
1
Command (config)
Enable BGP routing.
router bgp <asn>

Where:
<asn>
Purpose
The autonomous system number.
Example:
distance bgp <1-255> <1-255> <1-255>
Where:
<1-255>
Specifies the external distance
<1-255>
Specifies the internal distance
<1-255>
Specifies the local distance
Change the BGP

distance value.
Example:
CASA-CMTS(config-router-bgp)# distance bgp <1255> <1-255> <1-255>
To set a distance value to a specified network:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
distance <1-255> A.B.C.D/M [name]
Where:
<1-255>
Set a distance value to a

specified network.
Defines the administrative distance value in

the range 1 to 255. A.B.C.D/M defines the
IP source prefix. The optional name defines
an IP access list name.
Example:
CASA-CMTS(config-router-bgp)# distance 5
60.3.4.5/24 list5
211
CASA CMTS
BGP decision processing

When selecting which path to use, BGP uses the following factors in the order below:
1. The CMTS will prefer the path with the largest value. The value is usually used to prefer
routes originated by the CMTS over routes originated by other routers.
2. If the routes have the same value, the CMTS will prefer the route with the largest local
preference.
3. If the route is originated locally, the CMTS will prefer it over a route that is not originated
locally.
4. The CMTS will use the shortest autonomous system (AS) path length.
5. If the autonomous system path length is the same, the CMTS will prefer the route with the
lowest origin code
6. If the origin codes are the same, the CMTS will prefer the route with the lowest Multi Exit
Discriminator (MED).
Enabling BGP networks

BGP routes
To announce a network to all neighbors (use the no form of the command to cancel the
announcement):
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] network <A.B.C.D/M>
Where:
A.B.C.D/M
IP network address and mask length.
Example:
In this example network 10.0.0.0/8 will be announced to all
neighbors.
Announce a network to
all neighbors.
command to cancel the
announcement.
CASA-CMTS(config-router-bgp)# network
10.0.0.0/8
Some vendor routers do not advertise routes if the routes are
not present in the BGP routing tables; BGP does not use IGP
routes when announcing BGP routes.
212
CASA CMTS
Enable route aggregation

To specify an aggregate address:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
aggregate-address A.B.C.D [as-set] [summary-only]
or
aggregate-address A.B.C.D/M [as-set] [summary-only]
Where:
A.B.C.D
Enable route
aggregation.
The network number.
A.B.C.D/M
The IP prefix and mask length.
as-set
Generate AS set path information.
summaryonly
Specify an aggregate address but not

announce aggregated routes.
Example:
CASA-CMTS(config-router-bbp)# aggregateaddress 192.168.6.7/24 as-set summary-only
Redistribute to BGP
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
redistribute kernel|static|connected|rip|ospf
Where:
kernel
Redistribute routes.
Redistribute a kernel route to a BGP process
static
Redistribute static route to a BGP process:
connected
Redistribute a connected route to a BGP

process
213
CASA CMTS
rip
Redistribute a RIP route to a BGP process
ospf
Redistribute an OSPF route to a BGP

process
Example:
CASA-CMTS(config-router-bgp)# redistribute
kernel
CASA-CMTS(config-router-bgp)# redistribute
static
Defining BGP peers

The BGP peer command must be the first command used when configuring a neighbor. If the
remote-as is not specified, the error message: cant find neighbor A.B.C.D will appear.
To configure a BGP peer:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> remote-as <asn>
Where:
<peer_ip-address>
<asn>
The IP address of the BGP peer.

Creates a new neighbor

whose remote-AS is
ASN. A peer can be an
IPv4 address or an IPv6
address.
To delete the neighbor
configuration use the no
form.
Example:
In this case the router in AS-1 is attempting to peer with AS-2
at 10.0.0.1.
CASA-CMTS(config-router-bgp)# neighbor
10.0.0.1 remote-as 2
Defining BGP peer passwords

To perform MD5 authentication with BGP peers, specify the neighbor IP address and a password.
Neighbor passwords can be encrypted using the [no] service password-encryption command
from the top-level configuration mode.
214
CASA CMTS
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> password <string>
Where:
<peer_ip-address>

The password text string associated
with this BGP peer.
<string>
Creates an MD5
authentication password
associated with the BGP
peer at the specified IP
address.
To delete the neighbor
password configuration
use the no form.
Example:
In this case the router in AS-1 is attempting to peer with AS-2
at 10.0.0.1.
CASA-CMTS(config-router-bgp)# neighbor
10.0.0.1 password
BGP peer commands

To specify the neighbor-specific configurations, use the commands described in this section.
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[ no] neighbor <peer_ip-address> shutdown
Where:
<peer_ip-address>
Specify shutdown or noshutdown of neighborspecific configurations.
IP address of the BGP peer.
Example:
CASA-CMTS(config-router-bgp)# no neighbor
64.10.1.0 shutdown
215
CASA CMTS
To allow EBGP neighbors that are not on directly-connected networks:

Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> ebgp-multihop [maxhop-count]
Where:
<peer_ip-address>
<max-hop-count>
EBGP neighbors not on

directly connected
networks
IP address of the BGP peer.

The maximum number of hops when
connecting to this BGP peer.
Example:
EBGP neighbors not on directly connected networks
ebgp-multihop 50
To add a description to a peer (up to 80 lines):
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor peer description <line>
Add a description to a
peer (up to 80 lines):
Example:
CASA-CMTS(config-router)#[ no] neighbor peer
description <line>
To set up the neighbors BGP version, use the following.
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
216
CASA CMTS
Example:
neighbor <peer_ip-address> version <version>
Where:
<peer_ip-address>
Set up the neighbors

BGP version.

The version can be 4, 4+ or 4-. BGP
version 4 is the default value used
for BGP peering. BGP version 4+
means that the neighbor supports
Multiprotocol Extensions for BGP-4.
BGP version 4- is similar but the
neighbor uses the old Internet-Draft
revision 00s Multiprotocol
Extensions for BGP-4. Some routing
software is still using this version.
<version>
Example:
CASA-CMTS(config-router)#neighbor 192.168.3.1
version 4
When connecting to a BGP peer over an IPv6 link-local address, specify the ifname of the
interface used for the connection:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> interface <ifname>
Where:
<peer_ip-address>
<ifname>
Connect to a BGP peer

over an IPv6 link-local
address.

The interface name specified as a
text string.
Example:
interface ifname
217
CASA CMTS
To specify an announced routes nexthop as being equivalent to the address of the BGP router:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Specifies the autonomous system

number.
Example:
[no] neighbor <peer_ip-address> next-hop-self
Where:
<peer_ip-address>
Specify an announced
routes next hop as being
equivalent to the address
of the BGP router
Example:
next-hop-self
To announce default routes to the peer, use this command. The default is to not announce the
default route (0.0.0.0/0) even if it is in the routing table.
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> default-originate
Where:
<peer_ipaddress>
Announce default routes

to the peer.
Example:
CASA-CMTS(config-router)#[no] neighbor
192.168.3.4 default-originate
218
CASA CMTS
To define the source of routing updates:

Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> update-source <asn>
Where:
<peer_ipaddress>
<asn>
Define the source of

routing updates

The autonomous system number or
interface name.
Example:
CASA-CMTS(config-router)#[no] neighbor peer
update-source 4
To send community attributes to this neighbor:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> send-community
Where:
<peer_ipaddress>
Send community
attributes to this
neighbor.
Specifies the IP address of the BGP peer.
Example:
send-community
219
CASA CMTS
To specify a default value for the neighbor routes:

Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> weight <value>
Where:
<peer_ipaddress>
<value>
Specify a default value

for the neighbors routes

The default weight value for neighbor
routes in the range 0 to 65535.
Example:
CASA-CMTS(config)# neighbor 192.168.3.4 weight
5
To specify the maximum number of prefixes accepted from this peer:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
2
[no] neighbor <peer_ip-address> maximum-prefix

<number>
Specify the maximum

number of prefixes
accepted from this peer.
Where:
<peer_ipaddress>
<number>
The maximum number of prefixes in the

range 1 to 4294967295.
Example:
CASA-CMTS(config)# neighbor 192.168.3.4
maximum-prefix 100
220
CASA CMTS
Peer filtering
Specify a distribute-list for the peer (direct is in or out):
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
neighbor <peer_ip-address> distribute-list {<name> |
<number> } {in | out}
Where:
<peer_ipaddress>
Specify a distribute-list
for the peer.
<name>
The name of an IP access list.
<number>
The IP access list number in the range 1

to 199, or in the expanded range 1300 to
2699.
in
Filters inbound updates.
out
Filters outbound updates.
Example:
distribute-list list1 in
Specify a prefix-list for the BGP peer:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Specifies the autonomous system

number.
Example:
neighbor <peer_ip-address> prefix-list <name> {in | out}
Specify a prefix-list for

the peer.
Where:
<peer_ipaddress>
Specifies the IP address of the BGP

peer.
<name>
Specifies the name of the prefix list.
221
CASA CMTS
in
out
Example:
CASA-CMTS(config-router)#neighbor peer prefixlist prefixList1 out
Specify a filter-list for the peer:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
neighbor <peer_ip-address> filter-list <name> [in | out]
Specify a filer-list for the

peer:
Where:
<peer_ipaddress>
<name>
The filter list name.
in
out
Example:
CASA-CMTS(config-router)#neighbor peer filterlist filterList1 in
Apply a route-map (Release 5.4 only) to a neighbor:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
neighbor <peer_ip-address> route-map <name> {in | out}
Where:
<peer_ip-
Apply a route map (5.4

only) to a neighbor.
222
CASA CMTS
address>
<name>
The name of the route-map.
in
out
Example:
CASA-CMTS(config-router)#neighbor peer routemap <name> [in | out]
BGP peer groups

To define a new BGP peer group:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
neighbor word peer-group
Define a new peer group
Example:
CASA-CMTS(config-router)#neighbor word peergroup
Bind a specific peer to a peer group word:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
neighbor <ip_-address> peer-group <name>
Bind a specific peer to a

named peer group.
Example:
peer-group peerGroup1
223
CASA CMTS
Setting the BGP address family

To configure a routing session using standard IP Version 4, IP Version 6, or Virtual Private
Network (VPN) Version 4 address prefixes, use the address-family command in router
configuration mode. Use the exit-address-family command to return to the router configuration
mod. Use the no form of the address-family command to remove the address-family
configuration from the running configuration.
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] address-family {ipv4 | ipv6 | vpnv4} [multicast |
unicast]
Where:
ipv4
Configure a routing
session using addressfamily ipv4, ipv6 or
vpnv4.
Internet Protocol Version 4; multicast or

unicast
ipv6
Internet Protocol Version 6; unicast only
vpnv4
Virtual Private Network Version 4 address

prefixes; unicast only.
multicast
Optional. Specifies IP Version 4 multicast

address prefixes.
unicast
Optional. Specifies IPv4, IPv6, or vpnv4

unicast address prefixes. This is the default
setting.
Example:
CASA-CMTS(config-router)# address-family ipv4
multicast
Configuring autonomous systems

The Autonomous System (AS) is an essential element of BGP. BGP is a distance vector routing
protocol. The AS framework provides distance vector metric and loop detection to BGP.
RFC1930 (Guidelines for Creation, Selection, And Registration of an Autonomous System (AS))
describes how to use an AS. The AS number is a two-octet digital value in the range 1 to 65535.
AS numbers 64512 through 65535 are defined as private AS numbers. Private AS numbers are
not advertised to the global Internet.
224
CASA CMTS
AS path access list

To define new AS path access-list:
Step
1
Command (config)
Purpose
[no] ip as-path access-list <name> [permit | deny]

<string>
Define a new AS path

access list.
Where:
<name>
Access-list name.
permit
Forward packets specified by the regular

expression string.
deny
Reject packets specified by the regular

expression string.
<string>
AS path regular expression.
Example:
CASA-CMTS(config)#ip as-path access-list list1
permit regExpression
Using the BGP communities attribute

The BGP communities attribute is widely used for implementing policy routing. Network operators
can manipulate the BGP communities attribute based on their network policy. The BGP
communities attribute is defined in RFC1997 (BGP Communities Attribute) and RFC1998 (An
Application of the BGP Community Attribute in Multi-home Routing). It is an optional transitive
attribute that allows local policy to traverse different autonomous systems.
The communities attribute is a set of values where each value is 4 octets long. The following
format defines the communities attribute value.
Format
Explanation
AA:NN
This format represents 4 octet communities value. AA is high order 2

octet in digit format. NN is low order 2 octet in digit format. This format
is useful to define AS oriented policy value. For example, 7675:80
can be used when AS 675 wants to pass local policy value 80 to
neighboring peer.
internet
Represents well-known communities attribute value 0.
no-export
Represents well-known communities value NO_EXPORT

(0xFFFFFF01). All routes carrying this value must not be advertised
outside a BGP confederation boundary. If a neighboring BGP peer is
part of a BGP confederation, the peer is considered as inside a BGP
confederation boundary, so the route will be announced to the peer.
no-advertise
Represents well-known communities value NO_ADVERTISE

(0xFFFFFF02). All routes carrying this value must not be advertised
225
CASA CMTS
to other BGP peers.

local-AS
Represents well-known communities value

NO_EXPORT_SUBCONFED (0xFFFFFF03). All routes carrying this
value must not be advertised to external BGP peers. Even if the
neighboring router is part of the confederation, it is considered as an
external BGP peer, so the route will not be announced to the peer.
When the BGP communities attribute is received, the duplicate values in the communities
attribute are ignored. The values are sorted in numerical order.
Configuring BGP community lists

A BGP community list is a user-defined BGP community attribute list. A BGP community list is
used to match or manipulate the BGP community attribute in BGP updates.
There are two types of community lists: standard community and expanded community. The
standard community list defines the community attributes. The expanded community lists defines
the community attribute strings with regular expressions. The standard community list is compiled
into binary format when it is define and is directly compared to a BGP community attribute in BGP
updates. Therefore, the comparison is faster than the expanded community list.
To define a new standard community list, use the following command.
Step
1
Command
Purpose
ip community-list <number> {permit | deny}

{<community_number> | internet | no-advertise | local-AS | noexport}
Define a new
standard
community list.
Where:
<number>
The standard community list number.
permit
Community to forward as specified by the

community_number.
deny
Community to reject as specified by the

community_number.
<community_
number>
The community number in AA:NN format or

internet, local-AS, no-advertise, or no-export.
Community is compiled into the community
structure. The multiple community list is
defined under same name. In this case a
match will occur in the user-defined order.
Once the community list matches the
communities attribute in BGP updates, it
returns permit or deny by the community list
definition. When there is no matched entry, a
deny message is returned. When community
is empty it matches any routes.
226
CASA CMTS
Example:
CASA-CMTS(config)#ip community-list 123 permit
internet
To delete community lists specified by number, use the following command. All of the community
lists share a single namespace, so community lists can be removed by simply specifying the
community list number. Use the show running-config command to display BGP community
settings.
Step
1
Command
Purpose
no ip community-list <number>
Delete community list.
BGP community in route map

In the route-map (see the Route Map section), the BGP community attribute can be matched or
set. By using this feature, you can implement a network policy based on the BGP community
attribute.
Using the BGP community attribute

Example 1
The following configuration example is the most typical usage of the BGP community attribute.
AS 7675 provides upstream Internet connection to AS 100. When the following configuration
exists in AS 7675, the AS 100 network operator can set local preference in AS 7675 network by
setting the BGP community attributes to the updates.
router bgp 7675
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
ip community-list 70 permit 7675:70 ip community-list 70 deny
!
route-map RMAP permit 10 match community 70
set local-preference 70
!
!
Example 2
The following configuration announces 10.0.0.0/8 from AS 100 to AS 7675. The route has
communities value 7675:80 so when the above configuration exists in AS 7675, announced
routes local preference will be set to value 80.
227
CASA CMTS
router bgp 100 network 10.0.0.0/8

neighbor 192.168.0.2 route-map RMAP out
!
ip access-list
!
Permit all 10.0.0.0 255.0.0.0 any any
route-map RMAP permit 10
match ip address acl
set community 7675:80
Example 3
The following configuration is an example of BGP route filtering using communities attribute. This
configuration only permits BGP routes that have a BGP communities value 0:80 or 0:90. The
network operator can put a special internal communities value at BGP border router and then limit
the BGP routes announcement into the internal network.
router bgp 7675
!
ip community-list 1 permit 0:80 0:90
!
route-map RMAP permit in match community 1
Example 4
The following example filters BGP routes that have community value 1:1. When there is no match
the community-list returns a deny response. To avoid filtering all of routes, define permit any at
the end.
router bgp 7675
!
ip community-list standard FILTER deny 1:1 ip community-list standard
FILTER permit
!
route-map RMAP permit 10 match community FILTER
Community value keyword internet has a special meaning in standard community lists. In the
following example internet acts as match any. It matches all of the BGP routes even if the route
does not have a community attribute at all. So community list INTERNET is the same as above
examples FILTER.
ip community-list standard INTERNET deny 1:1
ip community-list standard INTERNET permit internet
228
CASA CMTS
Example 5
The following configuration is an example of community value deletion. With this configuration
communities value 100:1 and 100:2 is removed from BGP updates. For community value
deletion, only permit community-list is used. The deny community-list is ignored.
router bgp 7675
!
ip community-list standard DEL permit 100:1 100:2
!
set comm-list DEL delete
router bgp 7675
!
!
!
!
Example 6
The following configuration announces 10.0.0.0/8 from AS 100 to AS 7675. The route has
communities value 7675:80 so when the above configuration exists in AS 7675, announced
routes local preference will be set to value 80.
router bgp 100 network 10.0.0.0/8
neighbor 192.168.0.2 route-map RMAP out
!
ip ip access-list acl
!
Permit all 10.0.0.0 255.0.0.0 any
match ip address acl
set community 7675:80
229
CASA CMTS
Example 7
The following configuration is an example of BGP route filtering using communities attribute. This
configuration only permits BGP routes that have BGP community value 0:80 or 0:90. The network
operator can put a special internal community value at the BGP border router, and then limit the
BGP routes announcement into the internal network.
router bgp 7675
!
ip community-list 1 permit 0:80 0:90
!
route-map RMAP permit in match community 1
Example 8
The following example filters BGP routes that have the community value 1:1. When there is no
match the community-list returns a deny response. To avoid filtering all of routes, define permit
any at the end.
router bgp 7675
!
ip community-list standard FILTER deny 1:1 ip community-list standard
FILTER permit
!
route-map RMAP permit 10 match community FILTER
Community value keyword internet has a special meaning in standard community lists. In the
following example internet acts as match any. It matches all of the BGP routes even if the route
does not have a communities attribute. So community list INTERNET is the same as above
examples FILTER.
ip community-list standard INTERNET deny 1:1
ip community-list standard INTERNET permit internet
Example 9
The following configuration is an example of community value deletion. With this configuration
community value 100:1 and 100:2 are removed from BGP updates.
router bgp 7675
!
ip community-list standard DEL permit 100:1 100:2
!
set comm-list DEL delete
230
CASA CMTS
Displaying BGP routes

To display information about BGP routes, use the following commands. To list all the BGP
attribute information:
Step
1
Command
Purpose
show ip bgp attribute-info
List all the BGP attribute

information.
Example:
CASA-CMTS# show ip bdg attribute-info
Display paths suppressed due to dampening:
Step
1
Command
show ip bgp dampened-paths
Example:
CASA-CMTS# show ip bgp dampened-paths
Purpose
Display paths
suppressed due to
dampening.
Display detailed information on TCP and BGP neighbor connections:

Step
1
Command
show ip bgp neighbors
Example:
CASA-CMTS# show ip bgp neighbors
Purpose
Display detailed
information on TCP and
BGP neighbor
connections.
Display path information:

Step
1
Command
Purpose
show ip bgp paths
Display path information.
Example:
CASA-CMTS# show ip bgp paths
Display information about the route server client:
Step
1
Command
Purpose
show ip bgp rsclient
Display information
about the route server
client.
Example:
CASA-CMTS# show ip bgp rsclient
Display the BGP scan status:
Step
1
Command
Purpose
show ip bgp scan
Display the BGP scan

status.
231
CASA CMTS
Example:
CASA-CMTS# show ip bgp scan
Display a summary of BGP neighbor status:
Step
1
Command
Purpose
show ip bgp summary
Display a summary of
BGP neighbor status.
Example:
CASA-CMTS# show ip bgp summary
Display the BGP attributes:
Step Command
1
show ip bgp attribute-info
Purpose
Display BGP attributes.
Example:
CASA-CMTS# show ip bgp attribute-info
Display path suppressed due to dampening:
Step
1
Command
Purpose
show ip bgp dampened-paths
Display suppressed
paths.
Example:
CASA-CMTS# show ip bgp dampened-paths
Clearing and reestablishing BGP routes

The clear ip bgp command allows you to selectively reset current BGP routes so that new routes
to BGP neighbors are relearned and reestablished. Based on your requirements, use the clear
ip bgp command to reset all BGP peers, peers uniquely identified by IPv4 or IPv6 address,
peers belonging to a particular AS number, external peers residing outside of the AS to which the
CMTS belongs, or peers belonging to a configured BGP peer group.
Optionally, you can specify that the CMTS perform a soft reconfiguration update with one or
BGP peers without performing a full reset and losing connectivity to existing peers.
To selectively clear BGP routes:
Step
1
Command
Purpose
clear ip bgp { * | A.B.C.D | X:X::X:X | <1-65535> | external | peergroup }

[ in [prefix-filter] | ipv4 {multicast | unicast} {in [prefix-filter] |
out | soft [in [prefix-filter] | out]} | out | rsclient | soft [in[prefixfilter] | out] | vpnv4 unicast {in [prefix-filter] | out | soft [in | out]} ]
Clear the
specified BGP
route (s) to one
or more BGP
peers.
Where:
232
CASA CMTS
Clears all routes to existing BGP peers.
A.B.C.D
Specifies the IPv4 address of the BGP peer to

which the BGP route is cleared.
X:X::X:X
Specifies the IPv6 address of the BGP peer to

which the BGP route is cleared.
<1-65535>
Specifies the autonomous system number (AS)

to which all BGP routes are cleared. All BGP
routes to peers within that AS are cleared.
external
Clears all routes to BGP peers outside of the AS

to which the CMTS belongs.
peer-group
Specifies the previously-configured peer group

containing one or more BGP peers.
in
Performs a reconfiguration update on inbound

BGP routes only based on the specified peer(s).
This is an optional setting.
out
Performs a reconfiguration update on outbound

BGP routes only based on the specified peer(s).
This is an optional setting.
soft
Performs a reconfiguration update on all BGP

routes only based on the specified peer(s). This
is an optional setting.
ipv4
Performs a reconfiguration update on all IPv4

BGP unicast or multicast routes only based on
the specified peer(s). This is an optional setting.
rsclient
Performs a reconfiguration update on all IPv6

BGP routes to route-server (RS) clients. This is
an optional setting.
vpnv4
Performs a reconfiguration update on IPv4

virtual private network (VPNv4) BGP unicast
routes. This is an optional setting.
prefix-filter
Specifies inbound reconfiguration BGP updates

based on a configured BGP neighbor prefix list
and outbound route filtering (ORF). ORF
reduces the number of BGP updates between
peers.
Examples:
To reset all external BGP routes :
CASA-CMTS# clear ip bgp external
To perform a soft reconfiguration updates on inbound BGP updates
from a BGP neighbor at specific IPv4 address:
CASA-CMTS# clear ip bgp 60.5.6.7 in
233
CASA CMTS
Enabling capability negotiation

This version of BGP supports Multiprotocol Extension for BGP (described in RFC2283). The
protocol does not define new protocols. It defines new attributes to existing BGP. When it is used
for exchanging IPv6 routing information it is called BGP-4+. When it is used for exchanging
multicast routing information it is called MBGP. If the remote peer supports the protocol, BGP can
exchange IPv6 and/or multicast routing information.
Traditional BGP does not have the feature to detect the remote peers capability to handle other
than IPv4 unicast routes. This version of BGP uses a feature called Capability Negotiation to
detect the remote peers capabilities. If the peer is only configured as an IPv4 unicast neighbor,
the BGP daemon does not send these Capability Negotiation packets.
By default, this version of BGP will bring up peering with minimal common capability for both
sides. For example, if a local router has unicast and multicast capabilities and the remote router
has unicast capability, the local router will establish the connection with unicast only capability.
When there are no common capabilities, BGP sends Unsupported Capability error and then
resets the connection.
To disable sending the capability negotiation OPEN message optional parameter to the peer
when the remote peer does not implement capability negotiation, use the following:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> dont-capabilitynegotiate
Where:
<peer_ipaddress>>
Disable sending the

capability negotiation
OPEN message.
Example:
dont-capability-negotiate
The no form of the command will suppress sending the capability negotiation as OPEN message
optional parameter to the peer. This command only affects the peer if it is configured other than
IPv4 unicast configuration.
234
CASA CMTS
Configuring route reflectors

BGP requires that all of the IBGP speakers be fully meshed. However, when there are many
IBGP speakers, this does not scale. Configuring a router reflector is a way to reduce the IBGP
mesh when there are many IBGP speakers. Instead of configuring a confederation, another way
to reduce the IBGP mesh is to configure a route reflector.
To configure a route reflector:
Step
1
Command (config)
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
bgp cluster-id <cluster_id> |
Where:
<cluster_id>
Configure route-reflector
cluster identifier.
Router reflector cluster identifier in IP

address format or in the range 1 to
4294967295
Example:
CASA-CMTS(config-router)# bgp cluster-id 300
Configure a BGP neighbor as a route-reflector:
Step
1
Command
Purpose
router bgp <asn>
Enable BGP routing.
Where:
<asn>
Example:
[no] neighbor <peer_ip-address> route-reflector-client
Where:
<peer_ipaddress>>
Configure a BGP
neighbor as a routereflector.
Example:
CASA-CMTS(config-router)# [no] neighbor peer
route-reflector-client
235
CASA CMTS
IP access control
The Casa CMTS provides a set of commands for users to control IP access to the system via
certain interfaces and access classes. The interfaces are the Ethernet management interface,
gigabit Ethernet data traffic interfaces, and DOCSIS mac-domain interfaces. The access classes
are incoming and outgoing classes. The access controls, deny or permit the flow of data traffic to
or from user-defined IP addresses and upper layer protocols specified in the IP protocol (TCP,
UDP) field, such as tcp, udp, tftp, telnet, etc.
To implement IP access control, the user needs to create an Access Control List (ACL) and apply
the ACL to specified system interfaces or access classes.
ACL is an ordered sequence of rules that control the flow of data packets through the system.
These rules may be used to permit or deny the flow of data traffic. ACLs help in restricting the use
of the system as desired based on the data traffic.
This section covers commands for the following operation:
Creating and removing ACLs

Entering and exiting ACL editing mode
Adding and removing control rules
Numbering the control rules
Displaying control rules
Applying and removing an ACL on a specified IP interface
Creating and deleting IP access classes
Displaying access class information
Creating and removing ACLs

ACL (access control list) management is possible only in privileged (enabled) and configuration
mode.
To create an ACL:
Step
1
Command (config)
Purpose
[no] ip access-list <acl_name> [resequence]
Create an
access control
list.
Where:
<acl_name>
Name of ACL. A maximum of 32 ACLs are

allowed.
Example:
Create an ACL with name telnet_host:
CASA-CMTS(config)# ip access-list telnet_host
CASA-CMTS(conf-acl telnet_host)#
Remove ACL telnet_host:
CASA-CMTS(config)# no ip access-list telnet_host
236
CASA CMTS
Entering and exiting ACL editing mode

To enter ACL editing mode:
Step
1
Command (config)
Purpose
ip access-list <acl_name>
Enter ACL
editing mode.
Where:
<acl_name>
ACL name; up to 32 ACLs are allowed.
Example:
To exit:
CASA-CMTS(conf-acl telnet_host)# end
CASA-CMTS(config)
Adding and removing control rules

An access list may have up to 128 rules in it (256 in version 5.4). Rules may be inserted in any
order in an access list. A sequence number is used to insert a rule in the desired position in the
list.
To add ACL rules:
Step
1
Command (config)
Purpose
ip access-list <acl_name>
Enter ACL
editing
mode.
Where:
<acl_name>
Name of ACL. A maximum of 32 ACLs are

allowed.
Example:
2
[sequence-number] permit[6] | deny[6] <protocol_name>|all

[sourceIP sourceMask destIP destMask destPort sourcePort]
Where:
[sequence-number]
Adds the
ACL rule.
Specifies the order of the rule in the list. If

the sequence number is not specified, the
rule will be appended to the list. A
sequence number is a number from 1 to
32000. Sequence numbers are only for
informational purposes. They are not
237
CASA CMTS
saved as part of the configuration. See

Numbering Control Rules in ACL later in
this section for more information.
permit
Allows the IPv4 packet if the rule is

satisfied.
permit6
Allows the IPv6 packet if the rule is

satisfied
deny
Discards the IPv4 packet if the rule is not

satisfied.
deny6
Discards the IPv6 packet if the rule is not

satisfied
<protocol_name>
Specifies the IP protocol (TCP, UDP) field

in the data packet. Protocol is a number in
the range 1 to 255. A few well-known and
popularly-used protocols like tcp, udp, ftp,
tftp, telnet, snmp, etc. may also be
specified by key word. That means permit
tcp any any is equivalent to permit 6 any
any. A complete list of key words can be
found online using help (?).
all
Implies all IP traffic.
SourceIP,
sourceMask, destIP
destMask,
sourcePort, destPort
Source and destination IP addresses in the

packet and source and destination port in
the respective protocol header. A source
and destination mask may be specified for
the IP addresses to allow or disallow the
data packets for a set of contiguous IP
addresses. IP addresses and masks are
specified in the dotted notation A.B.C.D.
Port numbers are in the range 1 to 65535.
any
A key word maybe used to specify any IP

address and corresponding mask of
255.255.255.255. For example, permit tcp
any any is equivalent to permit 6 0.0.0.0
255.255.255.255 0.0.0.0
255.255.255.255.
Example:
ACL rule to permit telnet access from host 192.168.2.222:
CASA-CMTS(conf-acl telnet_host)# 100 permit telnet 192.168.2.222

Removes
no <sequence-number>
the specific
rule.
Where:
The sequence number of the rule in the
<sequence-number>
list.
Example:
To remove control rule 100 from ACL telnet_host:
238
CASA CMTS
CASA-CMTS(conf-acl telnet_host)# no 100

Adding remark statements to the ACL

The IP access-list supports up to 256 remarks on top of 256 rules. Each remark supports up to 80
keyboard characters. The remark must be enclosed in quotations marks ( ) if embedded spaces
are used. Use the show ip access-list command to display the remark statements in the ACL.
If you choose not to use the optional sequence number, the CMTS will add the remark to the next
available sequence number (incremented by 10). See Numbering Control Rules in ACL later in
this section for more information.
To add remark statements to the ACL:
Step
1
Command (config)
Purpose
ip access-list <acl-name>
Create or open
the named
ACL.
Where:
<acl-name>
Specifies the name of the ACL.
Example:
2
[sequence-number] remark <string>

Example:
To add a remark with the sequence number 10:
CASA-CMTS(conf-acl telnet_host)#10 remark This is
a remark.
Create or
remove an
ACL remark
statement.
To remove a remark by sequence number:

CASA-CMTS(conf-acl telnet_host)# no 10
Displaying a control rule in an ACL

To display a control rule:
Step
1
Command (config)
Purpose
show ip access-list <acl-name> [details]
Display the
control rules.
Where:
<acl-name>
Name of ACL.
239
CASA CMTS
details
Shows the match count.
Example:
Display control rules specified in ACL telnet_host:
CASA-CMTS(config)# show ip access-list telnet_host
10 permit telnet 192.168.2.38 255.255.255.255.254
any
20 deny telnet any any
30 deny icmp 192.168.2.19 255.255.255.255 any
Displaying ACL names

To display the names of all access lists in the system:
Step
Command (config)
Purpose
show ip access-list
Displays the
names of all
access lists in
the system.
Example:
CASA-CMTS(config)# show ip access-list
ip access-list telnet_host
ip access-list ftp_host
ip access-list tftp_host
Numbering control rules in ACLs

Sequence numbers may be used to insert a rule in a list at a specific location. As the access list
is an ordered list, it is important to maintain the hierarchy. Sequence numbers are used only while
entering or deleting a rule in a list or while displaying the contents of a list. By default sequence
numbers start from 10 and increment by 10.
The following commands illustrate a sample hierarchy.
CASA-CMTS(conf-acl telnet_host)# 100 permit telnet 192.168.2.222
CASA-CMTS(conf-acl telnet_host)# 200 deny telnet any
The above commands first permit telnet access from the host 192.168.2.222, and then disallows
telnet access from all hosts. If the order of the above two commands is reversed, all the telnet
access to the system will be denied.
The following example demonstrates a way of inserting another rule in a list.
CASA-CMTS(conf-acl telnet_host)# show ip access-list telnet_host
10 permit telnet 192.168.2.238 255.255.255.255 any
To insert another rule between sequences 10 and 20:
240
CASA CMTS
10 permit telnet 192.168.2.238

show ip access-list telnet_host
255.255.255.255 any
255.255.255.255 any
When certain sequence numbers in a list are contiguous and it is necessary to insert a rule
between the successive sequence numbers, use the resequence command.
resequence
show ip access-list telnet_host
255.255.255.255 any
255.255.255.255 any
The sequence number is never stored as part of the system configuration. On restarting the
system, the starting sequence number defaults to 10 and the rules are resequenced to be in tens.
Applying an ACL to an IP interface (C3200 and C10200 only)

An ACL can be applied to any of the following interfaces:
eth0
gige
loopback
trunk
vlan
docsis-mac
ip-bundle
Only one ACL may be specified per interface. The same list may be specified on multiple
interfaces.
To apply an ACL to an interface, first enter configuration mode for that interface and then specify
the access list name.
Step
1
Command (config)
Purpose
interface eth <eth_int>
Enter interface
configuration
mode.
Where:
<eth_int>
Ethernet management interface.
Example:
CASA-CMTS(config-if-eth 0)#
241
CASA CMTS
Apply the ACL.
ip access-group <acl-name>
Where:
<acl-name>
Name of ACL.
Example:
Apply ACL telnet_host to Ethernet management interface:
CASA-CMTS(config-if-eth 0)# ip access-group
telnet_host
To apply an ACL to a specified gigabit Ethernet interface:

Step
1
Command (config)
Purpose
interface gige <port-id>
Enter interface
configuration
mode.
Where:
<port-id>
GigE port id.
Example:
Where:
<acl-name>
Apply the ACL.
Name of ACL.
Example:
Apply ACL telnet_host to gigabit Ethernet port 1 interface:
CASA-CMTS(config-if-gige
telnet_host
1)# ip access-group
To apply an ACL to a specified DOCSIS mac-domain interface:

Step
1
Command (config)
Purpose
interface docsis-mac <domain-id>
Enter interface
configuration
mode.
Where:
<domain-id >
DOCSIS MAC domain ID.
Example:
Where:
<acl-name>
Apply the ACL.
Name of ACL.
242
CASA CMTS
Example:
Apply ACL tftp_host to MAC-domain 1 interface:
CASA-CMTS(config-if-mac 1)# ip access-group
tftp_host
Removing the ACL from an IP interface

To disable the access list from an interface use the no command.
CASA-CMTS(config-if-eth 0)# no ip access-group
Creating and deleting IP access classes

The Casa CMTS provides configuration of access classes that control IP data traffic originating or
terminating at the CMTS. This controls the IP data access to the CMTS. Data may arrive or leave
from any of the CMTS interfaces. Instead of applying ACL to each of the interface, the user may
just create an access class to control the incoming and outgoing IP data traffic via any physical
interface. There are two types of access classes: incoming and outgoing. Incoming access
classes control the IP data traffic arriving at the CMTS and destined to the CMTS from any of its
physical interfaces. Outgoing access classes control the IP data traffic originating and leaving the
CMTS from any of its physical interfaces.
To create or delete an incoming access class:
Step
1
Command (config)
Purpose
[no] access-class in <acl_name>
Create or delete
an incoming
access class.
To delete an
incoming access
class use the no
command. The
access list name
is optional.
Where:
<acl-name>
Name of ACL.
Example:
CASA-CMTS(config)# access-class in tftp_host
CASA-CMTS(config)# no access-class in
To create an outgoing access class:

Step
1
Command (config)
Purpose
[no] access-class out <acl_name>
Create or delete
an outgoing
access class.
To delete an
incoming access
class use the no
command. The
Where:
<acl-name>
Name of ACL.
Example:
243
CASA CMTS
CASA-CMTS(config)# access-class out tftp_host

CASA-CMTS(config)# no access-class out
access list name

is optional.
Displaying access class information (Release 5.4)

To show the ACL counters for a specific interface:
Step
1
Command
Purpose
show interface <type> <num> acl-count [details]
Show the ACL

counters.
Where:
<type>
<num>
Interface (docsis-mac, eth, gige, ip-bundle, loopback,

qam, trunk, vlan upstream).
Interface number.
Example:
Show the eth0 ACL count details:
CASA-CMTS# show interface eth 0 acl-count details
10 deny icmp 192.168.0.250 255.255.255.255
192.168.0.188 255.255.255.255 (8 matches)
To list all the interfaces that currently have a specific ACL applied (in 5.2; this command is
accessible from diagnostic mode in 5.4):
Step
1
Command
Purpose
show ip access-list <string> applications
List all the interfaces that

currently have a specific
ACL applied.
Where:
<string>
Access list name.
To show the access list with counters:

Step
1
Command
Purpose
show ip access-list <string> details
List the access list with

counters.
Where:
<string>
Access list name.
To show the packets dropped by the access list from the deny rules:
Step
1
Command
Purpose
show interface access-class [in | out] acl-count

[details]
List the packets dropped

by the access list from the
deny rules.
244
CASA CMTS
Note that the first 128 rules are implemented in one applied processor while the other 128 (when
an ACL has more than 128 rules) are implemented in another applied processor. If a packet
matches a rule in both lists, then both counters will increment. But the action will occur with the
first processor. The C2200 does not support 256 rules.
Configuring route maps

Route maps provide a mechanism for permitting or denying route announcements that are
redistributed by dynamic routing protocols such as BGP and OSPF. Route maps are similar in
function to access-control lists (ACLs) when permitting or denying IP traffic. However, a routemap applies only to matched inbound IP routes; route information can then be modified before it
is redistributed by the intended protocol.
You create named route maps using match and set criteria at the CMTS. The match command
allows you to configure the criteria for selecting the route(s) to which a route-map applies, while
the set command modifies route information prior to redistribution.
When an inbound route is received at a CMTS interface, the CMTS evaluates the route against
configured route maps in numbered sequence for matching criteria, as follows:
If matched, the route is then redistributed using the newly-modified settings.

If the route-map does not contain at least one match command, then all routes match.
If the route-map is matched, but does not contain at least one set command instance, then
the unmodified route is redistributed.
When configuring BGP or OSPF, specify a named route-map with the redistribute command for
the targeted protocol.
Creating a named and sequenced route-map

A basic route-map consists of a name, a permit or deny statement, and a sequence number.
Step
1
Command (config)
Purpose
[no] route-map <routemap-name> [ {permit | deny}

<sequence-number>]
Create a named
route-map and
sequence
number.
Where:
<routemapname>
The named route-map up to 128 alphanumeric

characters. The name is case-sensitive.
permit
If the inbound route meets the match criteria,

permit the route on the received interface and
evaluate the route-map for route redistribution. If
not specified, the default setting is permit.
deny
If the inbound route meets the match criteria, deny

the route on the received interface. Further
evaluation of the route for redistribution is
Use the no form

of the command
to delete the
named routemap.
245
CASA CMTS
dropped.
<sequencenumber>
The line number of the named route map in the

range 1 to 65535. The CMTS evaluates route
maps in sequence from the lowest number to the
highest number. The first match takes
precedence. If not specified, the default
sequence number is 10.
Example:
CASA-CMTS(config)# route-map cmtsNet1 permit 100
To remove a named route-map:
CASA-CMTS(config)# no route-map cmtsNet1
Using the route-map match commands

The match commands provide the basic criteria for evaluating routes for redistribution. You can
specify the following criteria to match:
as-path
community
ip
metric
origin
peer
You must have at least one match entry in the route-map. Otherwise, all permitted inbound
routes on CMTS interfaces will be matched for redistribution to peer routers.
Matching BGP autonomous system paths

To match inbound routes from a specific BGP autonomous system path (AS-path), perform the
following steps:
Step
1
Command (config)
Purpose
[no] match as-path <acl-name>
Specify the BGP

autonomous
system path
access-list
name.
Where:
<acl-name>
The named access-list (ACL) associated with a

specific BGP autonomous system path from
which the CMTS receives route updates. An AS
path is list of autonomous systems through
which a route passes in order to reach a
destination.
Only one as-path may be specified per routemap.
Use the no form

of the command
to delete the
named as-path
setting.
Example:
246
CASA CMTS
CASA-CMTS(conf-route-map cmtsNet1)# match as-path

as10
To remove the configured as-path:
CASA-CMTS(conf-route-map cmtsNet1)# no match aspath as10
Matching the BGP community list

A BGP community list contains BGP community attributes contained in BGP updates. See the
BGP section of this guide for information on the BGP community lists and attributes.
To match inbound routes from a specific BGP community list, perform the following steps:
Step
1
Command (config)
Purpose
[no] match community <BGP-communityList-name> [exact-match]
Specify the
BGP
community list
name or
number.
Where:
<BGPcommunityList name>
exact-match
The BGP community list name or number. If

inbound BGP route matches the configured
community list name or number in the routemap configuration, the route is either
permitted or denied for redistribution.
Only one community attributes list may be
specified per route-map.
Perform exact matching on the configured
BGP community attribute list name or
number.
Use the no
form of the
command to
delete the
route-map
community.
Example:
CASA-CMTS(conf-route-map cmtsNet1)# match community
70
To remove the configured BGP community list:
CASA-CMTS#(conf-route-map cmtsNet1)#
community
no match
Matching IPv4 and IPv6 addresses

Use the match ip command to allow the CMTS route-map to evaluate routes to an IP destination
using a configured IP access-list, or an access-list associated with a next hop IP router. If
matched, the CMTS will either permit or deny the route for redistribution.
247
CASA CMTS
Step
1
Command
Purpose
[no] match {ip | ipv6} {address | next-hop} <acl-name>
Specify the
access-list
name
associated with
a destination or
next-hop IP
address.
Where:
<acl-name>
The named access-list (ACL) associated with a

destination IP to which the CMTS redistributes
route updates, or the next-hop IP address to which
route updates are forwarded. If matched, the
CMTS will either permit or deny the route
redistribution.
Only one IP access-list may be specified per routemap.
Use the no form

of the command
to delete the
match ip entry.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# match ip
address as2
CASA-CMTS(conf-route-map cmtsNet1)# # match ip
next-hop as4
To remove the configured match ip entry, execute the following
commands.
CASA-CMTS(conf-route-map cmtsNet1)# no match ip
address
CASA-CMTS(conf-route-map cmtsNet1)# no match ip
next-hop
Matching route metrics

Inbound routes with route metrics matching the route-map metric setting are either permitted or
denied for redistribution. Route metrics are used to indicate preferred routes with the least cost
over routes with higher metrics using higher routing costs.
Step
1
Command (config)
Purpose
[no] match metric <metric-number>
Specify the
route metric to
match with an
inbound route
for
redistribution.
Where:
<metricnumber>
The route metric number in the range 0 to

4294967295. If matched with the inbound route
metric, the CMTS will either permit or deny the
route redistribution.
Only one metric may be specified per route-map.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# match metric 5
Use the no form

of the command
to delete the
metric entry.
248
CASA CMTS
To remove the configured metric entry:

CASA-CMTS(conf-route-map cmtsNet1)# no match metric
Matching route origins

A route with a path origin attribute matching the route-map origin setting are either permitted or
denied for redistribution.
Step
1
Command (config)
Purpose
[no] match origin {egp | igp | incomplete}
Specify the route

origin to match
with an inbound
route for
redistribution.
Where:
origin
Specifies the origin of the route, either Exterior

Gateway Protocol (EGP), Interior Gateway
Protocol (IGP), or incomplete where the source
of the route path is unknown.
Only one origin may be specified per route-map.
egp
Exterior Gateway Protocol, such as BGP

exchanges among autonomous systems (AS).
Path information originated in another AS.
igp
Interior Gateway Protocol, such as RIP and

OSPF protocols running and exchanging routing
information within the local autonomous system.
Path information originated in the local AS.
incomplete
Unknown source for route. Path was learned by

another method.
Use the no form

of the command
to delete the
origin entry.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# match origin
egp
To remove the configured origin entry:
CASA-CMTS(conf-route-map cmtsNet1)# no match
origin egp
249
CASA CMTS
Matching peer routes

Inbound routes from peer routers matching the peer setting are either permitted or denied for
redistribution.
Step
1
Command (config)
Purpose
[no] match peer {<ip-address> | local}
Specify the peer

router to match
with an inbound
route for
redistribution.
Where:
<ip-address>
local
Specifies the IP address of peer router from

which routes are received at the CMTS.
Only one peer may be specified per routemap.
Specifies the peer router as a local AS router.
Use the no form

of the command
to delete the
peer entry.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# match peer
192.168.8.7
CASA-CMTS(conf-route-map cmtsNet1)# match peer
local
To remove the configured peer entry:
CASA-CMTS(conf-route-map cmtsNet1)# no match peer
192.168.8.7
CASA-CMTS(conf-route-map cmtsNet1)# no match peer
local
Matching route tags

Inbound routes matching the tag setting are either permitted or denied for redistribution.
Step
1
Command (config)
Purpose
[no] match tag <0-65535>
Specify the route

tag to match with
an inbound route
for redistribution.
Where:
<0-65535>
Specifies the route tag in the number range 0

to 65535.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# match tag 57
Use the no form

of the command
to delete the tag
entry.
To remove the configured tag entry:

CASA-CMTS(conf-route-map cmtsNet1)# no match tag
57
250
CASA CMTS
Using the route-map set commands

The set commands allow you to modify matched routes at the CMTS for redistribution to peer
routers. You can set the following route-map objects:
as-path
atomic-aggregate
community
ip
local-preference
metric
origin
originator-id
weight
You must have at least one set entry in the route-map. Otherwise, all permitted inbound routes
on CMTS interfaces will be redistributed to peer routers.
Modifying BGP autonomous system paths

To modify an inbound route from an autonomous system path (AS-path) for redistribution,
perform the following steps:
Step
1
Command (config)
Purpose
[no] set as-path prepend <as-number>
Prepend the
autonomous
system path with
the new AS
number.
Where:
<as-number>
Prepends the matched as-path with the

specified autonomous system (AS) number in
the range 1 to 65535. An AS-path is the list of
autonomous systems through which a route
passes in order to reach a destination.
Only one prepended as-path may be specified
per route-map.
Use the no form

of the command
to delete the
prepended aspath setting.
Example:
CASA-CMTS(conf-route-map cmtsNet1# set as-path
prepend 5
To remove the prepended as-path:
CASA-CMTS(conf-route-map cmtsNet1# no set as-path
prepend 5
Setting the atomic aggregate

The atomic-aggregate setting, when enabled in the route-map, adds the atomic-aggregate path
attribute to route announcements distributed to BGP peers. When there are overlapping routes
presented to a BGP peer, the less-specific route is selected rather than the more-specific route.
251
CASA CMTS
Step
1
Command (config)
Purpose
[no] set atomic-aggregate
Enables the atomicaggregate setting.
Example:
CASA-CMTS(conf-route-map cmtsNet1)# set
atomic-aggregate
To remove the atomic-aggregate setting:
CASA-CMTS(conf-route-map cmtsNet1)# no set
atomic-aggregate

command to remove
atomic-aggregate
setting.
Modifying the BGP community attribute

The following communities attribute values are:
Format
Explanation
AA:NN
The 4-octet communities value.

AA is high order 2-octet in digit format that identifies the AS in the
range 1 to 65535.
NN is low order 2 octet in digit format that identifies the community in
the range 1 to 65535.
internet
Represents the known communities attribute value 0.
no-export
Prevent route announcements beyond the BGP confederation.
no-advertise
All routes carrying this value must not be advertised to other BGP
peers.
local-AS
Prevents route announcements outside of the local AS.
additive
Adds a community number to the community lists.
To modify a matched community value, perform the following steps:

Step
1
Command (config)
Purpose
[no] set community <community-number>
Specify the
community
number.
Where:
<communitynumber>
The community number in AA:NN format or

internet, local-AS, no-advertise, no-export,
or additive.
Only one community number may be
specified per route-map.
Use the no
form of the
command to
delete
community
setting.
Example:
252
CASA CMTS
CASA-CMTS(conf-route-map cmtsNet1)# set community

225:1
To remove the configured community number:
community
Modifying next-hop IP addresses

Use the set ip command to modify the next-hop router IP addresses to which route
announcements are forwarded.
Step
1
Command (config)
Purpose
[no] set ip next-hop <ip-address> [<ip-address> <ip-address>]
Specify the routemap next-hop IP

address(es). Up
to three IP
addresses may
be specified.
Where:
<ip-address>
The next-hop IP address in decimal format to

which route announcements are forwarded.
Specify up to three IP addresses.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# set ip nexthop 192.168.3.0
Use the no form

of the command
to delete the ip
next-hop entry.
To remove the configured ip next-hop entries:

CASA-CMTS(conf-route-map cmtsNet1)# no set ip
next-hop
Setting the BGP local-preference path attribute

Use the set local-preference command to set the path attribute metric used by local BGP
sessions that are processing external routes learned by BGP, as matched by the route-map. The
route with high precedence is the preferred route. These routes are advertised to internal BGP
peers and BGP confederations and are not advertised to external BGP peers.
253
CASA CMTS
Step
1
Command (config)
Purpose
[no] set local-preference <localPref-value>
Specify the local

preference
metric value
Where:
<localPefvalue>
The local-preference path attribute used by

internal BGP peers handling external routes
learned by BGP. Specify a metric value in the
range 1 to 4294967295, where higher values
indicate the most preferred routes.
Use the no form

of the command
to delete the
localpreference
entry.
Examples:
CASA-CMTS(conf-route-map cmtsNet1# set localpreference 5
To remove the configured local-preference entry:
CASA-CMTS(conf-route-map cmtsNet1# no set localpreference
Setting the metric for destination routing

Use the set metric command to set the metric value for preferred routes learned by BGP and
matched by the route-map, to destination external BGP peers. Routes with high metric values
(lowest number) are preferred over routes low metric values.
Step
1
Command (config)
Purpose
[no] set metric <metric-value>
Specify the
metric value for
routes
advertised to
external BGP
peers.
Where:
<metric-value>
The routing metric to apply to external routes

learned by BGP, as originally matched by the
route-map, and forwarded to external BGP
peers. Specify a metric value in the range 1
to 4294967295, where higher values indicate
the most preferred routes.
Use the no form

of the command
to delete the
metric setting.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# set metric 5
To remove the configured metric setting:
CASA-CMTS(conf-route-map cmtsNet1)# no set metric
Modifying route origins

Use the set origin command to modify the path origin attribute, as originally matched by routemap.
254
CASA CMTS
Step
1
Command (config)
Purpose
[no] set origin {egp | igp | incomplete}
Modify the route

origin, as
originally
matched by the
route-map.
Where:
origin
Modifies the origin of the route, either Exterior

Gateway Protocol (EGP), Interior Gateway
Protocol (IGP), or incomplete where the source
of the route path is unknown.
Only one origin may be specified per route-map.
egp
Exterior Gateway Protocol, such as BGP

exchanges among autonomous systems (AS).
Path information originated in another AS.
igp
Interior Gateway Protocol, such as RIP and

OSPF protocols running and exchanging routing
information within the local autonomous system.
Path information originated in the local AS.
incomplete
Unknown source for route. Path was learned by

another method.
Use the no form

of the command
to delete the set
origin entry.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# set origin egp
To remove the configured origin entry:
CASA-CMTS(conf-route-map cmtsNet1)# no set origin
egp
Setting the BGP originator-id attribute

Use the set originator-id command to modify the BGP originator-id attribute. This is the IP
address of the router where the route updated originated. In networks where route reflectors are
implemented, the originator-id prevents routing loops within an autonomous system (AS).
Step
1
Command (config)
Purpose
[no] set originator-id <ip-address>
Specify the IP
address of the
router where the
matched route
originated.
Where:
<ip-address>
The IP address of the router where the route

update originated.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# set originatorid 192.268.3.4
Use the no form

of the command
to delete the
originator-id
setting.
255
CASA CMTS

originator-id
Setting the BGP weight attribute

Use the set weight command to modify the BGP weight attribute on a matched route. The
weight attribute is used by the local router (CMTS) to select the preferred path when there is
more than one route to a destination. The higher the weight, the more preferred the route.
Step
1
Command (config)
Purpose
[no] set weight <weight-value>
Specify the IP
weight of a
matched route
when there is
more than one
route to a
destination.
Where:
<weight-value>
The weight of the route in the range 0 to

4294967295. When there is more than one
route to a destination, the route with the
higher configured weight is the selected path
for the route announcement.
Examples:
CASA-CMTS(conf-route-map cmtsNet1)# set weight 100
Use the no form

of the command
to delete the
weight setting.

CASA-CMTS(conf-route-map cmtsNet1)# no set weight
Displaying route-map details

Use the show route-map command from configuration mode or from the top level of the CLI to
show the currently configured route-maps and settings.
Configuring Virtual Local Area Networks (VLANs)

Casa CMTS supports VLAN (IEEE 802.1Q) configuration for its interfaces of gigabit Ethernet and
QAM. This section covers commands for the following VLAN operations:
Assigning a Gigabit Ethernet Port to a VLAN
Removing a Gigabit Ethernet Port from a VLAN
Assigning a QAM Port to a VLAN
Removing a QAM Port from a VLAN
Displaying VLAN configurations
Configuring a VLAN
To configure a VLAN:
256
CASA CMTS
Step
1
Command (config)
Purpose
[no] interface vlan <num>
Configure a VLAN.
Where:
<num>
VLAN ID from 2 to 3700 (5.4) or 256 to 4095

(5.2)
Example:
CASA-CMTS(config)#interface vlan 2
Configuring up to six VLANs concurrently (Release 5.4)

Step
1
Command (config)
Purpose
[no] interface vlan <num> <num> [<num>] [<num>]

[<num>] [<num>]
Where:
Specifies the VLAN identifier from 2 to 3700
<num>
(5.4) or 256 to 4095 (5.2)
Configure up to 5
VLANs. To remove the
VLANs, use the no form
of the command.
Example:
CASA-CMTS(config)#interface vlan 300 1000 2000
3000 3500 3600
or
CASA-CMTS(config)#no interface vlan 300 1000
2000 3000 3500 3600
Configuring VLANs in a range (Release 5.4)

Step
1
Command (config)
Purpose
[no] interface vlan range <snum> <enum>
Configure a VLAN range

from the first to last ID.
Where:
<snum>
<enum>
Specifies the beginning of the VLAN range.

Specifies the end of the VLAN range.
Example:
CASA-CMTS(config)#interface vlan range 300 400
CASA-CMTS(conf-if-vlan 300)#
or
CASA-CMTS(config)#no interface vlan range 300
400
257
CASA CMTS
Configuring the MAC address on each VLAN interface

Step
1
Command (config)
Purpose
[no] interface vlan <vlan-id>
Enter a VLAN interface.
Where:
<vlan-id>
Specifies the VLAN identifier from 2 to 3700

(5.4) or 256 to 4095 (5.2)
Example:
CASA-CMTS(conf-if-vlan 2)
mac address xxxx.xxxx.xxxx
Where:
xxxx.xxxx.xxxx
Configure the MAC

address.
Specifies the MAC address of the VLAN

interface.
Example:
CASA-CMTS(conf-if-vlan 2)#mac address
xxxx.xxxx.xxxx
Enabling/disabling VLAN Interfaces (5.4)

A VLAN interface can be shutdown (or not shutdown). When a VLAN interface is created, it is in
no shutdown state by default. When the user shuts down the interface, the VLAN will be down
only if all the GigE ports under it are down. Issuing a no shutdown command on the interface will
bring up the VLAN up if one or more GigE ports assigned to it are up.
Assigning a Gigabit Ethernet port to a VLAN

To assign a gigabit Ethernet port to a VLAN:
Step
1
Command (config)
Purpose
interface vlan <vlan-id>
Configure the VLAN

interface
Where:
<vlan-id>
Specifies the VLAN identifier in the range

256 to 4095 (with Release 5.2); 2 to 3700
(with Rel. 5.4.)
Example:
CASA-CMTS(config)# interface vlan 256
gige <port>
Where:
Specify the GigE

interface port
number.
258
CASA CMTS
<port>
Specifies the GigE interface port number.
Example:
CASA-CMTS(conf-if-vlan 256)# gige 1
Assigning a 10Gigabit Ethernet port to a VLAN

To assign a 10GigE Ethernet port to a VLAN:
Step
1
Command (config)
Purpose
Configure the VLAN

interface.
Where:
<vlan-id>
Specifies the VLAN identifier in the range 2

to 3700. On the C10g platform, the software
default to slot 6 as the active SMM.
Example:
xgige <port>
Where:
<port>
Specify the 10GigE

interface port
number.
Specifies the system slot number and

Ethernet port. On the C10G platform, valids
slot are 6 and 7; valid ports are 0 and 1.
Example:
CASA-CMTS(conf-if-vlan 6/10)# xgige 6/0
Removing a Gigabit Ethernet port from a VLAN

To remove a gigabit Ethernet port from a VLAN:
Step
1
Command (config)
Purpose
Configure the
VLAN interface.
Where:
<vlan-id>

to 4095 (with Release 5.2); 2 to 3700 (with
Release 5.4.)
Example:
no gige <port>
Where:
Specify the GigE

interface port
number.
259
CASA CMTS
<port>
Specifies the GigE interface port number.
Example:
CASA-CMTS(conf-if-vlan 256)# no gige 1
Removing a 10Gigabit Ethernet port from a VLAN

To remove a 10GigE Ethernet port from a VLAN:
Step
1
Command (config)
Purpose
Configure the
VLAN interface.
Where:
<vlan-id>
Specifies the VLAN identifier in the range 2 to

3700. On the C10g platform, the software
Example:
xgige <port>
Where:
<port>
Specifies the system slot number and Ethernet

port. On the C10G platform, valids slot are 6
and 7; valid ports are 0 and 1.
Specify the
10GigE interface
port number for
removal.
Example:
CASA-CMTS(conf-if-vlan 6/10)# no xgige 6/0
Assigning an IPv4 address to a VLAN

To assign an IP address to a VLAN:
Step
1
Command (config)
Purpose
Configure the VLAN

interface
Where:
<vlan-id>

(with Rel. 5.4.)
Example:
CASA-CMTS(conf-if-vlan 6/10)# gige 4
260
CASA CMTS
CASA-CMTS(conf-if-vlan 6/10)# show this

interface vlan 6/10
gige 6/4
no shutdown
Where:
<ip-address>
a VLAN.

the format a.b.c.d.
in the format p.q.r.s
<subnet-mask>
Example:
Assign IP address 192.168.3.100 to VLAN 10:
CASA-CMTS(config-if-vlan 10)# ip address
192.168.3.100 255.255.255.0
CASA-CMTS(config-if-vlan 10)#
Assigning an IPv6 address to a VLAN

To assign a IPv6 address to a VLAN:
Step
1
Command (config)
Purpose
Configure the VLAN

interface
Where:
<vlan-id>

(with Rel. 5.4 and later.)
Example:
CASA-CMTS(conf-if-vlan 6/10)# gige 4
CASA-CMTS(conf-if-vlan 6/10)# show this
interface vlan 6/10
gige 6/4
no shutdown
2

Where:
<ipv6address>
Assign an IPv6
address to VLAN.
Text string for standard IPv6 address in the

format xxxx:xxxx:xxxx:...:xxxx
261
CASA CMTS
<mask_len>
Standard subnet mask. Usable addresses:

2001:0db8:0100:f101:0210:a4ff:fee3:9566
2001:0000:0000:0000:0000:0000:1000:1 (This
Example:
Assign IPv6 address 2000::1000:1/64 to VLAN 10:
CASA-CMTS(config-if-vlan 6/10)# ipv6 address
2000::1000:1/64
CASA-CMTS(config-if-gige 1)# no ipv6 address
Rate limiting multicast traffic over a VLAN interface

Set the rate-limit multicast parameter to specify the number of multicast packets per second to
be allowed over a VLAN interface. The default is no rate limiting. The valid range is 16 to
9999999 packets per second.
Step
1
Command (config)
Purpose
interface vlan <vlan_id>
Enter a VLAN
interface by
specifying the
VLAN ID.
Where:
<vlan_id>
Specifies the VLAN identifier from 2 to 3700 (5.4)

or 256 to 4095 (5.2)
Example:
rate-limit multicast <16 to 9999999>
Where:
<16 to 9999999>
Specifies the number of multicast packets

per second to be transmitted over this
VLAN interface. The default setting is no
rate limiting.
Configure the
number of
multicast packets
per second.
Example:
CASA-CMTS(conf-if-vlan 2)# rate-limit multicast
1500
Assign a QAM port to a VLAN

To assign a QAM port to a VLAN:
262
CASA CMTS
Step
1
Command (config)
Purpose
interface qam <module>/<port>

Where:
Module number.
<module>
Enter QAM interface

mode.
<port>
QAM port number.
Example:
Enter QAM Interface mode for interface on module 0, port 2:
CASA-CMTS(config)# interface qam 0/2
CASA-CMTS(conf-if-qam)#
[no] vlan <vlan-id>
Where:
<vlan-id> VLAN ID. Valid values are 256 to 4095.
(Release 5.2); 2 to 3700 (Release 5.4)
Assign a QAM port a

VLAN. Use the no form
of the command to unassign the QAM port.
Example:
Assign QAM port 0/2 to VLAN 256:
CASA-CMTS(conf-if-qam 0/2)# vlan 256
CASA-CMTS(config-if-qam 0/2)#
Remove QAM port 0/2 from VLAN:
CASA-CMTS(conf-if-qam 0/2)# no vlan
CASA-CMTS(conf-if-qam)#
Assigning an IP access group to a VLAN interface

To assign an IP access group to a VLAN:
Step
1
Command (config)
Purpose
[no] interface vlan <num>
Enter a VLAN interface.
Where:
<num>
VLAN ID from 2 to 3700 (5.4) or 256 to 4095

(5.2)
Example:
[no] ip access-group <string>
Where:
<string>
Specifies the access group name.
Assign an IP access
group to a VLAN. Use
the no form of the
command to remove the
assignment.
Example:
CASA-CMTS(conf-if-vlan)# ip access-group
my_access_group
Remove the assignment:
263
CASA CMTS
CASA-CMTS(conf-if-vlan)# no ip access-group
my_access_group
Assigning a trunk to a VLAN interface

To assign a trunk to a VLAN, perform the following steps:
1. Create a VLAN using a unique ID under the interface configuration.
2. Create a trunk under the interface configuration and proceed to add the GigE interfaces.
Note: A given GigE interface may be present in only one trunk interface at a time. Before adding
a gigabit interface to a trunk interface, make sure that the interface has no IP address assigned.
For example, adding interface GigE 0 should not have an IP address.
To assign a trunk to a VLAN:
Step
1
Command (config)
Purpose
[no] interface vlan <vlan_id>

Where:
VLAN ID from 2 to 3700 (5.4) or 256 to 4095 (5.2)
<vlan_id>
Enter a VLAN
interface by
specifying the
VLAN ID.
Example:
2
[no] trunk <number>

Where:
<number>
The trunk interface number in the range 1 to 12.
CASA-CMTS(conf-if-vlan 10)# trunk 24

Remove the assignment:
CASA-CMTS(conf-if-vlan)# no trunk 12
Specify the
previously configured trunk
number.
Use the no form of
the command to
remove the trunk
from the
Example: Create trunk and add interfaces; add trunk to VLAN.

CASA-CMTS(conf-if-trunk 12)#gige 3
CASA-CMTS(conf-if-trunk 12)#gige 4
CASA-CMTS(conf-if-trunk 12)#end
CASA-CMTS(conf-if-vlan 10)#trunk 10
CASA-CMTS(conf-if-vlan 10)#ip address 192.67.43.1 255.255.0.0
264
CASA CMTS
Displaying all VLAN configurations

To display all configured VLANs:
Step
Command (config)
Purpose
show interface vlan
Display all configured

VLANs.
Example:
Display VLAN configurations:
CASA-CMTS(config)# show interface vlan
interface gige 0, vlan 2
interface qam 0/0, vlan 2
Note: All unassigned interfaces have default VLAN-ID=2.
Displaying a VLAN interface (Release 5.4)

To display a specific VLAN:
Step
1
Command (config)
Purpose
show interface vlan [<vlan-id>] [ acl-count [details] | brief |

service-policy-count [details] ]
Display a specific
VLAN.
Where:
<vlan-id>
VLAN ID from 256 to 4095 (with Release

5.2); 2 to 3700 (with Release 5.4)
acl-count
Indicates the packet drop count from ACL

deny rules.
brief
Display the specified VLAN in abbreviated

form.
service-policycount
Shows the packet count associated with

one or more policy rules. Use the optional
details parameter to show the packet
count per rule.
Example:
CASA-CMTS(config)#show interface vlan
interface vlan 2
no ip igmp
interface vlan 300
gige 0
no ip igmp
CASA-CMTS(config)#
265
CASA CMTS
Displaying ARP entries from the current VLAN

To display the ARP entries from the current VLAN:
Step
1
Command (config)
Purpose
Configure the VLAN

interface.
Where:
<vlan-id>

to 3700. On the C10g platform, the software
Example:
show arp
Example:
CASA-CMTS(conf-if-vlan 6/10)# show arp
Interface
Age
Hardware Addr
IP Address
eth 6/0
00:00:01 0017.1001.5cab
192.168.8.1
eth 6/0
00:08:40 0022.0c9a.ea41
192.168.8.12
eth 6/0
00:18:01 bc30.5bd8.0f8e
192.168.8.90
eth 6/0
00:00:01 b8ac.6f8f.181f
192.168.8.92
eth 6/0
00:00:01 0017.1002.cc40
192.168.8.113
eth 7/0
00:08:24 0022.0c9a.ea41
192.168.8.12
eth 7/0
00:00:01 0017.1002.c4c0
192.168.8.114
CATV-MAC 1 00:00:01 0017.1002.cc4d
fe80::217:10ff:fe02:cc4d
CATV-MAC 2 00:00:01 0017.1002.cc4e
fe80::217:10ff:fe02:cc4e
State
Type
dynamic ARPA
dynamic ARPA
dynamic ARPA
dynamic ARPA
static
ARPA
dynamic ARPA
static
ARPA
static
ARPA
static
ARPA
Configuring L2VPN
Casa CMTS supports L2VPN protocol which provides an end-to-end connection to an enterprise
office over a SPs MPLS or IP core. This section covers commands for the following L2VPN
operations:
Specify Ports/Interfaces on NSI Side of a L2VPN VLAN
Specify a Gige/Trunk Interface on a L2VPN VLAN
266
CASA CMTS
Display configured L2VPN
Prevent/Permit Station Movement/Local Forwarding
Show Station Movement/Local Forwarding Configuration
L2VPN is primarily used by customers with multiple sites (like a business) who want all users to
be on the same LAN by virtually connecting cable modems and routers. The L2VPN is defined
outside of the CMTS where the cable modem configuration file contains the information about the
L2VPN. Because all L2VPN traffic is tagged before it reaches the CMTS, the CMTS knows which
cable modems are assigned to which L2VPN. When the CMTS receives the traffic tagged for a
particular L2VPN, it strips off the tag and forwards the traffic to the cable modem. When the cable
modem sends traffic to the CMTS, it adds the tag and forwards the traffic.
The CMTS also recognizes local traffic and can send that traffic directly to another cable modem
that is directly connected to it.
To retrieve information about the VPN on the CMTS, use the following command:
Step
1
Command
Purpose
show interface vlan [<vlan_id>]
Find out information

about the VLAN
Example:
C10G-203(config)#show interface vlan 10
interface vlan 6/10
xgige 6/1
no ip igmp
no shutdown
Specifying ports/interfaces on the NSI side of the L2VPN VLAN

To specify ports/interfaces on the NSI side of the L2VPN VLAN:
Step
1
Command (config)
Purpose
Find out the information

about the VPN on the
CMTS.
Where:
<vlan_id>
VLAN ID. Valid values are 256 to 4095

(with Release 5.2); 2 to 3700 (with
Release 5.4)
Example:
267
CASA CMTS
Specifying GigE/trunk interfaces on the L2VPN VLAN

Step
1
Command (config)
Purpose
Enter interface
mode.
Where:
<vlan_id>
VLAN ID. Valid values are 256 to 1000.
Example:
2
Specify GigE or
trunk interface on a
L2VPN VLAN.
[no] gige <port_num>

[no] trunk <trunk_num>
Where:
<port_num>
<trunk_num>
GigE port number.

Trunk interface number. Values are 1 to 16.
Note: A L2VPN may have more than one gige and trunk
interfaces.
Preventing and permitting station movement and local forwarding

To prevent or permit a host to use the mac address which is being used by another host or traffic
to be exchanged within the same QAM:
Step
1
Command
Purpose
[no] l2vpn {mac-address-movable | local-trafficforwarding}
Preventing/permitting
station movement and
local forwarding.
Where:
mac-address-movable
local-traffic-forwarding
Specifies a change of locations

for MAC addresses attached to
a permitted l2vpn.
Traffic destined to local
addresses permitted
Example:
CASA-CMTS(config)# no l2vpn mac-addressmovable
268
CASA CMTS
Displaying the station movement and local forwarding configuration

To show configuration of preventing or permitting station movement and local traffic forwarding:
Step
1
Command
Purpose
show l2vpn {mac-address-movable | local-trafficforwarding}
Display the station

movement and local
forwarding configuration.
Where:
mac-address-movable
local-traffic-forwarding
Specifies a change of
locations of MAC addresses
attached to a permitted
l2vpn.
Traffic destined to local
addresses permitted.
Example:
CASA-CMTS# show l2vpn local-traffic-forwarding
no l2vpn mac-address-movable
no l2vpn local-traffic-forwarding
Displaying configured L2VPNs

To display configured L2VPN VLANs:
Step
1
Command
Purpose
show l2vpn vlan [<vlan_id>]
Display a configured
L2VPN VLAN:
Where:
<vlan_id>
Specifies the VLAN identifier. Valid values

are 256 to 4095 (with Release 5.2); 2 to
3700 (with Release 5.4).
Example:
C10G-203(config)#show l2vpn vlan 10
l2vpn vlan table: vlan_id=10
Displaying L2VPN statistics on QAM modules

To display configured L2VPN VLANs:
Step
1
Command
Purpose
show l2vpn qam [<module_id>]
Display L2VPN statistics

over a specified QAM
module.
Where:
<module_id>
Specifies the QAM module slot on the
269
CASA CMTS
CMTS in the range 0 to 14.

Example:
C10G-203(config)#show l2vpn qam 1
lc: logical=1 phy=1
L2VPN US: ttl=0 drop=0
DS: ttl=0 drop=0
NotDefined pkt=0 id=0 bc_src=0
local: mac_addr_movable 0 traffic_fwd 0
l2vpn_vlan_tbl_prt():
l2vpn_addr_hs_tbl_prt():
Configuring TACACS (Release 5.4)

Terminal Access Controller Access Control System (TACACS) is a security application that
provides centralized validation of users attempting to gain access to a router or network access
server. Casa CMTS supports the following CLI commands to control access to a TACACS server
with Authentication, Authorization, and Accounting (AAA).
Configuring the host IP
Configuring the key
Enabling authentication
Configuring authentication
Enabling enable password authentication through a TACACS+ server
Disabling enable password of TACACS+ authentication
Enabling authorization
Configuring authorization
Enabling accounting
Logging in to accounting
Command accounting
Displaying the AAA configuration
Configuring the TACACS host IP

To configure a host IP:
Step
1
Command (config)
Purpose
tacacs-server host <host_addr>
Configure a host IP.
Where:
<host_addr>
AAA host IP address in decimal format a.b.c.d.
Example:
CASA-CMTS(config)tacacs-server host 192.168.10.1#
270
CASA CMTS
Configuring a TACACS key

To configure a TACACS key:
Step
1
Command (config)
Purpose
tacacs-server key <key>
Specify the key.
Where:
<key>
Server access keyword, and is case sensitive.
Enabling password authentication at the TACACS+ server

To enable password authentication at the TACACS+ server:
Step
1
Command (config)
Purpose
aaa authentication enable default group {radius | tacacsplus}

enable
Enable enable
password
authentication at
TACACS+ server.
Where:
radius
tacacsplus
Use RADIUS server.

Use TACACS plus server.
Example:
CASA-CMTS(config)# aaa authentication enable
default group radius
Disabling the TACACS+ authentication password

To disable the TACACS+ password authentication:
Step
1
Command (config)
Purpose
no aaa authentication enable
Disable TACACS+
password authentication.
Example:
CASA-CMTS(config)# no aaa authentication
enable
Using RADIUS/TACACS+ Server for default server group for AAA

login authentication
Step
1
Command (config)
aaa authentication login default group {radius |
tacacsplus}
Where:
Purpose
Use RADIUS/TACACS+
server for default server
group for AAA login
authentication.
271
CASA CMTS
radius
Use RADIUS server.
tacacsplus
Use TACACS plus server.
Example:
CASA-CMTS(config)# aaa authentication login
default group tacacsplus
Configuring the AAA authentication login

Step
1
Command (config)
Purpose
aaa authentication login { local | radius | radius-local |

tacacsplus | tacacsplus-local )
Where:
default
Setup AAA
authentication login.
Use default login.
local
Use local database.
radius
Use radius server.
radius-local
Use the sequence of radius then

local.
tacacsplus
Use tacacsplus server.
tacacsplus-local
Use the sequence of tacacsplus

then local
Example:
CASA-CMTS(config)# aaa authentication login
radius
Configuring AAA authorization

To configure the authorization shell command:
Step
1
Command (config)
Purpose
aaa authorization command <num> default {group | ifauthenticated | local | none}
Configure authorization
shell command.
Where:
<num>
Enable level
group
Authorization group
if-authenticated
Go ahead if authenticated
local
Use local
none
No authorization
272
CASA CMTS
Example:
CASA-CMTS(config)# aaa authorization command 1
default local tacacsplus
To configure authorization exec shell default server group by tacacs plus server:
Step
1
Command (config)
Purpose
aaa authorization exec default group tacacsplus {ifauthenticated | local | none}
exec shell default server
group by tacacs plus
server.
Where:
if-authenticated
Go ahead if authenticated.
local
Use local.
none
No authorization
Example:
CASA-CMTS(config)# aaa authorization exec
default group tacacsplus local
To configure the authorization exec shell default login:
Step
1
Command (config)
Purpose
aaa authorization exec default {if-authenticated group |

group | local group | none group } tacacsplus
Where:
if-authenticated
exec shell default login
Proceed if authenticated.
local
Use local.
none
No authorization.
group
Server Group.
tacacsplus
Tacacs plus server
Example:
aaa authorization exec default ifauthenticated group tacacsplus
Enabling accounting
To enable accounting:
Step
1
Command (config)
Purpose
aaa accounting
Enable accounting
273
CASA CMTS
Command accounting
To perform command accounting:
Step
1
Command (config)
Purpose
aaa accounting commands <num> default {none | startstop | stop-only}
Command accounting.
Where:
<num>
Command level in the range 0 to 15.
none
None.
start-stop
Action start-stop.
stop-only
Action on stop only.
Example:
CASA-CMTS(config)# aaa accounting commands 4
default start-stop
Configuring AAA accounting for start-stop events

Step
1
Command (config)
aaa accounting exec default start-stop group {radius |
tacacsplus}
Where:
radius
tacacsplus
Purpose
Configure AAA
accounting for start-stop
events.
Use radius protocol.

Use tacacs protocol
Configuring AAA RADIUS-source loopback interface configuration

To configure AAA RADIUS source loopback interface:
Step
1
Command (config)
Purpose
aaa radius-source loopback <num=0:15>
Setup AAA radius

source loopback
interface.
Where:
<num=0:15>
The index number in the range 0 to 15.
Example:
CASA-CMTS(config)# aaa radius-source loopback 4
274
CASA CMTS
Disabling the AAA RADIUS source

Step
1
Command (config)
Purpose
no aaa radius-source
Disable AAA RADIUS

source.
Configuring the RADIUS server

Step
1
Command (config)
Purpose
radius-server {host <string> key <string> <number>

| key <string> | retry-max <0-5> | timeout <1-60>}
Configure the RADIUS

server.
Where:
host <string>
Specify a RADIUS server with a certain

string.
key <string>
Set RADIUS encryption key.
<number>
0 clear key to follow; 7 encrypted key

to follow.
retry-max
Maximum retry value to connect to server,

default is 0.
timeout
Timeout value in second, default is 5

second, won't be shown in startup.
Example:
CASA-CMTS(config)# radius server host server1
key 123 7
Disabling a specified RADIUS server or RADIUS encryption key

Step
1
Command (config)
no radius-server host<string>/key
Where:
host
Specify a RADIUS server.
<string>
IP address in dotted decimal format.
key
Set RADIUS encryption key.
Purpose
Disable a specified
RADIUS server or
RADIUS
encryption key
Example:
CASA-CMTS(config)# no radius server host
server1/123
275
CASA CMTS
Displaying the AAA configuration

To display AAA configuration:
Step
1
Command (config)
Purpose
show aaa
Display the
AAA
configuration.
Example:
CASA-CMTS# show aaa
----------------- AAA Configurations ---------------AAA Server IP Address : 192.168.100.1 (KEY: test)
AAA Server Encryption Key : test
AAA Authentication : LOGIN, ON
ENABLE, ON
AAA Authentication method : TACACS+, LOCAL
AAA CMD Authorization : ON
: COMMAND 15 TACACSPLUS
: OTHER COMMAND LEVEL(S) LOCAL
AAA Accounting
: COMMAND LEVEL 15 TRIGGERSTARTSTOP
: NO COMMAND ACC TRIGGER FOR OTHER LEVEL(S)
: EXEC ACC TRIGGER LOGIN-LOGOUT
Stream configuration and management

The CMTS can receive up to 1 gigabit per second IP encapsulated MPEG-2 transport streams
(SPTS or MPTS) per Gigabit Ethernet interface. The CMTS de-encapsulates the MPEG-2
streams, de-multiplexes the MPTS and re-multiplexes them to MPEG-2 Multi Program Transport
Streams (MPTS). The re-multiplexed MPEG-2 streams are QAM modulated for distribution in the
HFC networks.
The mapping of the IP encapsulated input SPTS to the output MPTS on QAM channels can be
done through translating a 4-tuple (source IP address, destination IP address, source UDP port
number, destination UDP port number) on the ingress side to a 2-tuple (QAM channel number
and PID) on the egress side.
Modes for mapping input streams to QAM output channels

Casa CMTS provides five operation modes for mapping input streams to QAM output channels.
They are the manual mode, the RPC (Remote Procedure Call) mode, the auto mode, the group4-port mode, and the group-2-port mode.
Mode
Description
Manual mode
The C2200 system maps an incoming program to a QAM output

channel by using source and destination information specified in
276
CASA CMTS
RPC mode
Auto Multiplex mode
Group-4-port mode
Group-2-port mode
stream configurations
Similar to manual mode, but mapping configuration is remotely
provisioned from SDV (Switched Digital Video) server.
The Casa CMTS automatically maps the incoming program
using the destination IP address and UDP port number
embedded in the incoming program.
Similar to auto mode, but with a different mapping scheme. The
Casa CMTS translates 16 (8 for 2-chans/port) incoming
programs to 16 (8 for 2-chans/port) QAM output channels of 4
ports in a group. The ports in each group key off the IP address
of the first QAM port in each group.
Similar to auto mode, but with a different mapping scheme. The
Casa CMTS system translates 8 (4 for 2-chans/port) incoming
programs to 8 (4 for 2-chans/port) QAM output channels of 2
ports in a group. The ports in each group key off the IP address
of the first QAM port in each group.
Enabling manual operation mode

When the Casa CMTS system is in manual mode, the system maps incoming streams to QAM
output channels by using values configured in the object stream, which includes the following
fields:
source IP address
destination IP address
source UDP port number
destination UDP port number
For an incoming program, only the destination UDP port number needs to be specified; the
remaining fields can be used as wildcards.
Streams are indexed 1 9999. Each stream intended for unicast distribution can be mapped to
only one QAM channel. Streams for multicast distribution can be mapped to more than one QAM
channel.
You can map any number of streams to a single QAM channel. Each stream mapped to a QAM
channel occupies a program space whenever the stream is active. However, when mapping
streams to QAM channels, you must make sure that you do not exceed the maximum bit rate of
38/27 Mbps (with 256/64QAM modulation, Annex B) for all activated programs on each QAM
channel.
QAM manual operation mode is chassis based, applicable to all QAM ports as a group. To enable
the manual operation mode:
277
CASA CMTS
Step
1
Command (config)
Purpose
operation mode manual [module <id>]
Enable manual operation

mode.
Where:
<id>
QAM module ID.
Example:
Enable QAM manual operation mode:
CASA-CMTS(config)# operation mode manual
CASA-CMTS(config)#
Enabling RPC mode

When the Casa CMTS system is in RPC mode, the system will obtain the stream-mapping
configuration from remote SDV servers. The mapping configuration has the same format as
manual mode. Refer to the section Configuring Switched Digital Video on how to engage with
specified SDV or NDCS servers.
QAM RPC operation mode is chassis based, applicable to all QAM ports as a group. To enable
the RPC operation mode:
Step
1
Command (config)
Purpose
operation mode rpc [module <id>]

Where:
QAM module ID.
<id>
Enable RPC mode.
Example:
Enable QAM RPC operation mode:
CASA-CMTS(config)# operation mode rpc
CASA-CMTS(config)#
Using auto-operation mode

This section describes the commands for auto operation mode, group-4-port mode, group-2-port,
as well as the commands for manual operation mode including stream-configuration and the
mapping between streams and QAM channels.
The operation commands covered in this section are:
Enabling auto-multiplex operation mode
Enabling Group-4-Port operation mode
Enabling Group-2-Port operation mode
Enabling manual operation mode
278
CASA CMTS
Setting de-jitter interval time
Entering stream configuration mode
Ending stream configuration mode.
Removing a configured stream
Setting stream source IP address
Removing a configured stream source IP address
Setting stream destination IP address
Removing a configured stream destination IP address
Setting stream source UDP port
Removing a configured stream source UDP port
Setting stream destination UDP port
Removing a configured stream destination UDP port
Showing the configured streams
Binding a stream with a QAM output channel
Removing the binding between a stream and a QAM output channel
Showing unmapped streams
Enabling auto-multiplex mode

In auto mode, all manually configured bindings among configured streams and QAM channels
are disabled. The mapping of an incoming program to a QAM output channel is embedded in the
destination IP address and the destination UDP port number of the encapsulated incoming
program.
The destination IP address is defined as the QAM port IP address. The destination UPD port
number is a 2-byte number of the form qqqqqqqqpppppppp. The bytes are defined as:
qqqqqqqq = QAM channel, 0 to 3 (or 0 to 1 for 2-chans/port)

pppppppp = Assigned program number, 1 to 255
With these definitions, an incoming program can be uniquely mapped to a QAM output channel
(QAM port number, QAM channel number, and PID) automatically.
QAM auto-multiplex operation mode is chassis based, applicable to all QAM ports as a group.
The default is the auto-multiplex operation mode.
Step
1
Command (config)
Purpose
operation mode auto [module <id>]
Enable the automultiplex operation

mode.
Where:
<id>
QAM module ID.
Example:
279
CASA CMTS
Enable QAM auto-multiplex operation mode:

CASA-CMTS(config)# operation mode auto
CASA-CMTS(config)#
Enabling Group-4-port operation mode

Operation modes group-4-port is similar to the auto mode, but with different mapping format
between incoming programs and QAM output channel. In group-4-port mode, the mapping
formats are:
1. The destination IP address is defined as the IP address configured to the first QAM port of a
QAM module, such as QAM output port-0/0, port-1/0, port-2/0, or port-3/0.
2. The destination UPD port number is a 2-byte number of the form qqqqqqqqpppppppp. The
bytes are defined as:
qqqqqqqq = QAM channel, 1 to 16 (1 to 8 for 2-chans/port)
Table 2-2 lists the explicit mapping between incoming UDP QAM-channels and output QAMchannels for group-4-port mode.
Table 2-2. Mapping of Incoming UDP QAM Channels to QAM Output in Group-4-Port Mode
UDP QAM-Chan
Output QAM-Chan <port>/<channel>
0/0
0/1
0/2
0/3
1/0
1/1
1/2
1/3
2/0
10
2/1
11
2/2
12
2/3
13
3/0
14
3/1
15
3/2
16
3/3
280
CASA CMTS
QAM group-4-port operation mode is chassis-based, applicable to all QAM ports as a group. To
enable the group-4-port operation mode:
Step
1
Command (config)
Purpose
operation mode group-4-port [module <id>]

Where:
QAM module ID.
<id>
Enable the Group-4-port

operation mode.
Example:
Enable QAM group-4-port operation mode:
CASA-CMTS(config)# operation mode group-4-port
CASA-CMTS(config)#
Enabling Group-2-port operation mode

Operation modes group-2-port is also similar to the auto mode, but with different mapping format
between incoming programs and QAM output channel.
In group-2-port mode, the 4 QAM output ports of each QAM module are divided into two groups,
with each group having 2 ports and 8 channels. The mapping formats are:
1. The destination IP address is defined as the IP address configured to the first QAM port of a
desired group, such as port-0/0, port-0/2, port-1/0, or port-1/2, etc.
2. The destination UPD port number is a 2-byte number of the form qqqqqqqqpppppppp. The
bytes are defined as:
qqqqqqqq = QAM channel, 1 to 8
Table 2-3 illustrates the explicit mapping between incoming UDP QAM-channels and output
QAM-channels for group-2-port mode.
Table 2-3. Mapping of Incoming to Output UDP QAM Channels in Group-2-Port Mode
UDP QAMChan
Output QAM-Chan <port>/<channel>

Destination IP =
Destination IP =
QAM-port-0 IP
QAM-port-2 IP
0/0
2/0
0/1
2/1
0/2
2/2
0/3
2/3
1/0
3/0
1/1
3/1
281
CASA CMTS
1/2
3/2
1/3
3/3
QAM group-2-port operation mode is chassis based, applicable to all QAM ports as a group. To
enable the group-2-port operation mode:
Step
1
Command (config)
Purpose
operation mode group-2-port [module <id>]
Enable the Group-2-port

operation mode.
Where:
<id>
QAM module ID.
Example:
Enable QAM group-2-port operation mode:
CASA-CMTS(config)# operation mode group-2-port
CASA-CMTS(config)#
Setting the de-jitter interval

Casa CMTS can receive and process packets transmitted at uneven rates. Jitter results when
packets are sent at uneven intervals. The dejitter-setting smooths out the transmission jitters and
improves the viewing quality of the streams. Casa CMTS buffers video packets before
transmitting them one by one at a fixed rate, defined by the dejitter interval.
The de-jitter interval is a global setting; it applies to all streams in the system in either automultiplex operation mode or manual mode.
Step
1
Command (config)
Purpose
[no] dejitter interval <size>
Set de-jitter interval or

return de-jitter interval to
the default value of 400
milliseconds.
Where:
<size>
De-jitter interval time in the range 50 to 500

milliseconds. The default is 400.
Example:
Set de-jitter interval to 200 milliseconds:
CASA-CMTS(config)# dejitter interval 200
CASA-CMTS(config)#
Set de-jitter interval to the default 400 milliseconds:
CASA-CMTS(config)# no dejitter interval
CASA-CMTS(config)#
282
CASA CMTS
Entering stream configuration mode

To enter stream configuration mode:
Step
1
Command (config)
Purpose
[no] stream <stream-id>
Enter stream
configuration mode.
Where:
<stream-id>
Stream ID in the range 1 to 9999.
Example:
Enter stream configuration mode. for stream 123:
CASA-CMTS(config)# stream 123
CASA-CMTS(config-stream 123)#
Ending stream configuration mode

To end stream configuration mode:
Step
1
Command (config)
Purpose
End stream configuration
mode.
end
Example:
End stream configuration mode:
CASA-CMTS(config-stream)# end
CASA-CMTS(config)#
Setting the stream source IP address

To set stream source IP address:
Step
1
Command (config)
Purpose
Enter or end stream

configuration mode.
Where:
<stream-id>
Example:

[no] ip source address <ip-address>
Where:
<ip-address>
Set or remove a stream

source IP address.
Source IP address in format of a.b.c.d.
283
CASA CMTS
Example:
Set source IP address for stream 123 to 192.168.4.10:
CASA-CMTS(config-stream 123) ip source address
192.168.4.10
Remove the configured source IP address for stream 123:
CASA-CMTS(config-stream 123)# no ip source
address
CASA-CMTS(config-stream)
Setting the stream destination IP address

To set stream destination IP address:
Step
1
Command (config)
Purpose
Enter or end stream

configuration mode.
Where:
<stream-id>
Example:
2
[no] ip destination address <ip-address>

Where:
<ip-address>
Set or remove a stream

destination IP address.
Source IP address in format of a.b.c.d.
Example:
Set destination IP address for stream 123 to 192.168.3.10:
CASA-CMTS(config-stream 123) ip destination
address 192.168.3.10
Remove the configured destination IP address for stream 123:
CASA-CMTS(config-stream 123)# no ip
destination address
284
CASA CMTS
Setting the stream source UDP port

To set stream source UDP port:
Step
1
Command (config)
Purpose
stream <id>
Enter stream
configuration mode.
Where:
<id>
Example:
[no] udp source port <source-port>
Where:
<source-port>
Set or remove stream

source UDP port.
Source UDP port number in the range 1

to 9999.
Example:
Set source UDP port for stream 123 to 1234:
CASA-CMTS(config-stream 123)# udp source port
1234
Example:
Remove the configured source UDP port for stream 123:
CASA-CMTS(config-stream 123)# no udp source
port
Setting the stream destination UDP port

To set or remove a stream destination UDP port:
Step
1
Command (config)
Purpose
stream <id>
Enter stream
configuration mode.
Where:
<id>
Example:
udp destination port <destination-port>
Where:
<destination-port>
Set or remove stream

destination UDP port.
Destination UDP port number in the
285
CASA CMTS
range 1 to 9999.
Example:
Set source UDP port for stream 123 to 4321:
CASA-CMTS(config-stream 123)# udp destination
port 4321
Remove the configured destination UDP port for stream 123:
CASA-CMTS(config-stream 123)# no udp
destination port
Displaying configured streams

To show the current stream configurations:
Step
1
Command (config)
Purpose
show stream config [<stream-id>]
Show the
configured streams.
Where:
<stream-id>
Optional. Stream ID in the range 1 to

9999. If no <stream-id> is specified, all
configured streams will be displayed.
Example:
Show the configuration of stream 14:
CASA-CMTS(config)# show stream config 14
configuration for stream 14
------------------------------------------------ip source address is
wildcard
ip destination address is
wildcard
udp source port is
wildcard
udp destination port is
3014
Dejitter buffer is
400
millisecond
Show the configuration of all configured streams:
CASA-CMTS(config)# show stream config
stream configuration:
stream 1
ip source address is
wildcard
wildcard
udp source port is
wildcard
3001
Dejitter buffer is
400
millisecond
stream 2
286
CASA CMTS
udp source port is
Dejitter buffer is
millisecond
stream 14
udp source port is
Dejitter buffer is
millisecond
CASA-CMTS(config)#
wildcard
wildcard
wildcard
3002
400
wildcard
wildcard
wildcard
3014
400
Binding a stream to a QAM output channel

Either SPTS or MPTS streams can be bound to a QAM channel.
For SPTS streams, use the following command to bind to a QAM output channel with an egress
program number:
For MPTS stream, use key word pass-through to bind the stream to a QAM output channel. In
this operation PCR will be re-stamped, but PIDs will be passed through unmodified.
Step
1
Command (config)
Purpose

Where:
Module number
<module>
Enter QAM interface

mode.
<port>
QAM port number
Example:

CASA-CMTS(config-if-qam)#
[no] channel <ch-id> stream <st-id> program <pr-id>
[pass-through]
Where:
<ch-id>
Bind a stream to a QAM

output channel or
removes the bind.
QAM channel number; values are 0 to 3 (0 or 1

for 2 chans/port)
<st-id>
Stream number in the range 1 to 9999.
<pr-id>
Egress program number in the range 1 to 1000.
Example:
Bind the SPTS stream 123 to QAM channel 1 on port 0/2 with
egress program number 100:
287
CASA CMTS
CASA-CMTS(config-if-qam)# channel 1 stream 123

program 100
Bind the MPTS stream 223 to QAM channel 0 on port 0/0:

CASA-CMTS(config-if-qam)# channel 0 stream 223
pass-through
Remove the binding between stream 123 and QAM channel 1
on, port 0/2:
CASA-C2150(config-if-qam)# no channel 1 stream
123
CASA-C2150(config-if-qam)#
Displaying unmapped streams

Unmapped streams are streams which ingress to a QAM module, but do not map to any output
interface and are dropped.
Step
1
Command (config)
Purpose
show module <module-id> stream no-mapping
Show unmapped
streams.
Where
<module-id>
Stream with no mapping
Example:
Show unmapped streams in QAM module 0:
CASA-CMTS# show module 0 stream no-mapping
Module 0 - Stream with no mapping
Stream configuration example

To set up a video stream, enter configuration mode, then stream operation mode:
Step
1
Command (config)
Purpose
CASA-CMTS(config)# operation mode group-4 port
Enter operation mode.
288
CASA CMTS
Select a gigabit Ethernet

port that has no IP
address (port 3 in this
example).
CASA-CMTS(config-if-gige 3)# no shutdown
Enable the interface.
N/A
Connect a cable to the

gige port and make sure
the link is up.

CASA-CMTS(config-if-qam0/0)# ip add a.b.c.d
<mask>
the QAM port (0/0 in this
example). Keep the
video server and the
QAM port on the same
subnet for simplicity:
To test the set-up, ping the QAM IP address from the video server. Then verify that streaming is
working by sending the stream to a.b.c.d/257. UDP port 257 will map to QAM 0/0 channel 0.
Finally, tune the set top box to the frequency of the QAM 0/0 channel (0).
Note: Some set-top boxes need to do DP scanning.
Configuring downstream QAM ports

This sub-section covers commands for the following operations:
Entering the QAM interface configuration mode
Ending the QAM interface configuration mode
Enabling the QAM output ports
Disabling the QAM output ports
Enabling QAM output channels
Disabling QAM output channels
Setting the QAM port IP address and subnet mask
Setting QAM port MAC address
Setting QAM modulation type
Setting QAM channel annex
Setting QAM frequency
Setting QAM output power
Setting QAM interleave level
Setting QAM spectral inversion
Setting QAM channel rate-limit
Setting QAM channel bandwidth
289
CASA CMTS
Showing QAM interface configurations
Showing QAM channel utilization rates
Entering QAM interface configuration mode

To enter QAM Interface Configuration mode:
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number.
QAM port number.
Example:

Ending QAM interface configuration mode

To end QAM interface mode:
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number
QAM port number
Example:

end
End QAM interface

mode.
Example:
CASA-CMTS(config-if-qam 0/0)# end

CASA-CMTS(config)#
290
CASA CMTS
Enabling QAM output ports

Each QAM output port on Casa CMTS contains 4 QAM output channels. Each QAM port or
channel can be enabled or disabled separately.
Note: The default state for all QAM ports and channels is shutdown. This prevents interference
with existing cable-channel configurations. If the QAM port is disabled, enabling the individual
channel will have no effect until the QAM port is enabled.
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number
QAM port number
Example:

no shutdown
Enable a QAM port.
Example:
Enable QAM port 0 on module 0:

CASA-CMTS(config-if-qam)# no shutdown
Disabling QAM output port

To disable a QAM port:
Step
1
Command (config)
Purpose
Enter QAM interface

Mode
Where:
<module>
<port>
Module number.
QAM port number.
Example:

shutdown
Enable a QAM port.
Example:
Enable QAM port 0 on module 0:

291
CASA CMTS
CASA-CMTS(config-if-qam)# shutdown
Enabling QAM output channels

To enable QAM output channels:
Step
Command (config)
Purpose
config
Enter configuration
mode.
Example:
CASA-CMTS#config
CASA-CMTS(config)#
Where:
<module>
<port>
Enter QAM interface

mode.
Module number.
QAM port number.
Example:

no channel <chan-id> shutdown
Where:
<chan-id>
Enable a QAM channel.
QAM channel number; valid values are 0

through 3.
Example:
Enable QAM channel 1 on module 1, port 3:

CASA-CMTS(config-if-qam 1/3)# no channel 1
shutdown
Disable QAM output channels

To disable a QAM channel follow the command below:
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number.
QAM port number.
292
CASA CMTS
Example:

2
channel <channel id> shutdown
Disable a QAM channel.
Example:
Disable QAM channel 2 on module 0, port 2:

CASA-CMTS(config-if-qam 0/2)# channel 2
shutdown
Setting the QAM port IP address and subnet mask

To set the IP address and subnet mask for a QAM port:
Step
1
Command (config)
Purpose

Where:
Module number.
<module>
Enter QAM interface

mode.
<port>
QAM port number.
Example:

2

Where:
<ip-address>
<subnet-mask>
Set or remove the QAM

port IP address and
subnet mask.
Text string for standard IP address,

in format a.b.c.d
Text string for standard subnet
mask, in format p.q.r.s
Example:
Set IP address to 192.168.3.211 and subnet mask to

255.255.255.0 for QAM port 2 on module 1:
CASA-CMTS(config-if-qam 1/2)# ip address
192.168.3.211 255.255.255.0
CASA-CMTS(config-if-qam 1/2)# no ip address
293
CASA CMTS
Setting the QAM port MAC address

The Casa CMTS allows users to override the built-in manufacturers MAC address. To override
the default MAC address on a QAM port, follow the command below:
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number.
QAM port number.
Example:

2
mac address <mac-address>

Where:
<macaddress>
Set or remove the QAM

port default MAC
address.
MAC address in format xxxx.xxxx.xxxx.
Example:
Set MAC address to 1234.2345.3456 for QAM port 2 on

module 1:
CASA-CMTS(config-if-qam)# mac address
1234.2345.3456
Return to the manufacturers built-in MAC
address:
CASA-CMTS(config-if-qam)# no mac address
Setting the QAM modulation type

To set the modulation rate for all QAM output channels on the selected QAM port:
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
Module number.
<port>
QAM port number.
294
CASA CMTS
Example:

modulation <type>
Where:
<type>
Set the QAM modulation

type.
Text string for QAM modulation scheme. Valid

values are 64qam, 128qam, 256qam, and off.
The default is 256qam.
Example:
Set the modulation type for QAM outputs on module 0, port 3

to 64qam:
CASA-CMTS(config-if-qam 0/3)# modulation 64qam
Note: QAM modulation is a port property. It applies to all four channels on the port. When the
modulation type is set to off, no modulation signal is transmitted to the QAM port. The RF output
of the port is a continuous wave.
Setting the QAM channel annex

There are three MPEG framing formats for a QAM channel, Annex A (Europe), Annex B (North
America), and Annex C (Japan).
Step
1
Command (config)
Purpose
Enter QAM
interface
mode.
Where:
<module>
<port>
Module number.
QAM port number.
Example:

annex <type>
Where:
<type>
Set the
Annex type.
Annex type. Values are A, B, or C. The default

setting is Annex B.
Example:
Set the MPEG framing format to Annex B for QAM outputs on module 0,
port 2:
CASA-CMTS(config-if-qam 0/2)# annex B
295
CASA CMTS
annex A [symbol rate <rate>] [channel spacing <value>]

When Annex A is chosen, two other channel parameters also need to be
configured: symbol-rate and channel-space.
Set the
Annex A
symbol rate.
Where:
<rate>
Annex A symbol rate in unit of kilo-symbol per second.

Values are 5000 to 6952. The default setting is 6952.
For DOCSIS channel 6952 is the only setting.
<value>
Annex A channel spacing in unit of Hz. Values are

6000000 to 8000000. The default setting is 8000000.
After an Annex type is set all four channels on the same
QAM port interface are set to the same Annex type
automatically. Because Annex type setting affects the
bandwidth of the channel changing the Annex type
setting also adjusts center frequencies of the four
channels on the same QAM port. The rule is that the
center frequency of channel 0 stays the same while the
other three are separated upward by 6 MHz each for
Annex B or by the specified channel space for Annex A
or Annex C.
Example:
Set the MPEG framing format to Annex A for QAM outputs on module 0,
port 3 with symbol rate 6000 and channel spacing 7000000:
CASA-CMTS(config-if-qam 0/2)# annex A symbol rate 6000
channel spacing 7000000
Note: In this example, assuming the center frequency of channel 0 was at 555 MHz, after the
Annex type setting, the center frequency of QAM channel 1 is then automatically adjusted to 562
MHz, channel 2 to 569 MHz, and channel 3 to 576 MHz
Setting the QAM frequency

The Casa QAM module has two modes of operation: normal and high frequency. Normal mode
requires all channels on a given QAM module to be contained in the range of 47 to 860 MHz.
High frequency mode requires all channels on a module in the range of 295 to 999 MHz.
For example, to change the channel frequency from one mode to the other, if the module starts
with port 0 at 100 MHz, then all other ports are set at 500 MHz with the module in normal mode.
If you attempt to set port 3 to 900 MHz, the module will NOT accept the setting because it
requires high-frequency mode (295-999 MHz). Because port 0 is currently in normal mode, you
must first set port 0 to at least 295 MHz before attempting to set port 3 to 900 MHz. This means
that if any channel frequency is greater than 860 Mhz, then all ports must be greater than 300
Mhz.
296
CASA CMTS
Each QAM module is completely independent of other modules within the same chassis. That
means some modules can be in high-frequency mode, while others are in normal mode.To set
the center frequency of the selected QAM channel follow the command provided below:
Step
1
Command (config)
Purpose
Enter QAM
interface mode
Where:
<module>
<port>
Module number
QAM port number
Example:

channel <channel-id> frequency <freq>
Set the QAM

frequency.
Note: The center frequencies for the four channels on the
same port are correlated. When any one is set, the others
change accordingly. The center frequency of each channel is
separated by 6 to 8 MHz, depending on whether the QAM port
is configured as Annex type B, C, or A.
Where:
<channel-id>
<freq>
QAM channel number; valid values are 0

through 3
QAM channel center frequency in Hz, from
47,000,000 to 999,000,000. The default
value for channel 1 is 549,000,000.
Example:
Set the center frequency of QAM channel 1 on module 0, port 3, to
555 MHz:
CASA-CMTS(config-if-qam 0/3)# channel 1 frequency
555000000
Note: In this example, assuming the channel bandwidth is 6
MHz, the center frequency of QAM channel 0 is then

automatically adjusted to 549 MHz, channel 2 to 561 MHz, and
channel 3 to 567 MHz.
Setting the QAM output power

To set the output power level for a QAM channel on a QAM port:
297
CASA CMTS
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number.
QAM port number
Example:

power <level>
Where:
<level>
Set the QAM output

power.
Downstream power output level in one tenth of

dBmV. The range is from 450 to 620. The
default setting is 510.
Example:
Set the output power level for RF port 0/2 to 550:
CASA-CMTS(config-if-qam 0/2)# power 550
This power setting is for the RF output port that is also the sum of all enabled QAM channels on
the same port. The actual QAM channel output level depends on how many QAM channels are
enabled on that port. For example, a setting of 550 (55 dBmV for the port) with 1 channel
enabled, sets the QAM channel level to 55 dBmv. A setting of 550 with 2 channels enabled sets
each QAM channel to an output level of 52 dBmV. A setting of 550 with 4 channels enabled sets
each QAM channel to an output level of 49 dBmV.
The maximum output level per QAM channel is:
62 dBmV at 1-channel/port
Setting the QAM interleave level

To set the interleave level for a QAM channel on a port:
Step
1
Command (config)
Purpose
Enter QAM interface

mode
Where:
<module>
Module number.
298
CASA CMTS
<port>
QAM port number.
Example:

interleave <level>
Where:
<level>
Set the QAM interleave

level.
QAM interleave level. The valid values are 8, 16,

32, 64, 128x1, 128x2, 128x3, 128x4, 128x5,
128x6, 128x7, and 128x8. The default is 128x1.
Example:
Set the interleave level to 128x8 for QAM port 3 on module 0:
CASA-CMTS(config-if-qam)# interleave 128x8
Note: When an interleave level is set, all channels on the port are set to the same interleave level
automatically
Setting the QAM spectral inversion

Spectrum inversion is a characteristic of a QAM port. To enable spectral inversion, follow the
command below:
Step
1
Command (config)
Purpose
Enter QAM interface

mode.
Where:
<module>
<port>
Module number.
QAM port number.
Example:
2
[no] spectral inversion on
Setting or disabling QAM

spectral inversion.
Example:
CASA-CMTS(config-if-qam 0/3)# spectral
inversion on
Disable QAM spectral inversion:
CASA-CMTS(config-if-qam 0/3)# no spectral
inversion on
299
CASA CMTS
Displaying QAM interface configurations

The following show interface commands include:
Showing the configurations and stream status of a specified QAM port interface.
Showing the configuration of a QAM channel and the streams bonded to it.
To show the configurations and stream status of a specified QAM port interface:
Step
1
Command (config)
Purpose
show interface qam <module>/<port> [brief]
Show configurations and

stream status for the
specified QAM port
interface.
Where:
<module>
Module number.
<port>
QAM port number.
[brief]
Optional. Show only the interface

configurations.
To show the configurations of a QAM channel and the stream bonded to it:
Step
1
Command (config)
Purpose
show interface qam <module>/<port>/<ch-id>
Show the
configurations of a
QAM channel and
the stream bonded
Where:
<module>
Module number.
<port>
QAM port number.
<ch-id>
QAM channel number 0 to 3.
Example:
CASA-CMTS(config) show interface qam 2/1/0
Displaying QAM channel counters and utilization rates

This command is used to display the utilization rates of all downstream channels:
To show the utilization rates of all downstream channels:
1
show docsis downstream channel {count | utilization}

Example:
Show the utilization rates of all the downstream channels in the
system:
Purpose
Show the
utilization rates of
all downstream
channels.
CASA-2200(config)# show docsis downstream channel

300
CASA CMTS
utilization
Downstream Slot/Port/Channel
2/0/0
2/0/1
2/0/2
2/0/3
2/1/0
2/1/1
2/1/2
2/1/3
2/2/0
2/2/1
2/2/2
2/2/3
2/3/0
2/3/1
2/3/2
2/3/3
Utilization (%)
2
2
2
2
0
0
0
0
0
0
0
0
0
0
0
0
Configuring upstream port interfaces

Upstream ports are physical interfaces the cable modem return paths connect to. The Casa
CMTS allows up to two logical-channels in each upstream port (in SCDMA mode, one for ATDMA mode). Each upstream port and logical-channel can be enabled or disabled independently.
The default state for all upstream ports and channels is shutdown. If an upstream port is
disabled, individual logical-channel cannot be enabled.
This section describes following operations:
Showing configurations of upstream port interfaces
Entering upstream port interface configuration mode
Ending upstream port interface configuration session
Enabling upstream port interfaces
Disabling upstream port interfaces
Setting logical-channel frequency
Setting logical-channel input-power level
Setting upstream-channel map-advance
Enabling the upstream logical-channel
Disabling the upstream logical-channel
Setting the upstream channel-types
Setting the upstream-channel backoff-values
Setting the upstream-channel mini-slot-size
Setting the upstream-channel modulation-profile
Setting the upstream-channel pre-equalization
Setting ingress noise cancellation
301
CASA CMTS
Showing upstream channel configurations
Showing upstream channel utilization rates
Showing upstream channel signal quality
Showing upstream port interface configurations

To show configurations of all upstream port interfaces in the system:
Step
1
Command (config)
Purpose
show interface upstream [brief]
Show configurations of
all upstream port
interfaces.
Example:
CASA-CMTS(config)# show interface upstream
To show configurations of all upstream port interfaces in a module:

Step
Command (config)
Purpose
config
Enter configuration
mode.
Example:
CASA-CMTS#config
CASA-CMTS(config)#
show interface upstream <module> [brief]
Where:
<module>
Module number.
Show configurations of
all upstream port
interfaces in the
specified module.
Example:
See example below.
Showing upstream port interface configurations

CASA-CMTS# show interface upstream 1
frequency 20000000
channel-width 6400000
power-level 0
power-adjustment continue 2
power-adjust threshold 1
map-advance static 200
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 profile 3
logical-channel 0 minislot 4
logical-channel 0 data-backoff automatic
302
CASA CMTS
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no shutdown
frequency 28000000
power-level 0
rate-limit
no shutdown
frequency 36000000
power-level 0
rate-limit
no shutdown
frequency 44000000
power-level 0
303
CASA CMTS
rate-limit
no shutdown
Displaying upstream interface status

To show the status of an upstream interface:
Step
1
Command (config)
Purpose
show interface upstream <module>/<port> [brief]
Show the status of an

upstream interface.
Where:
<module>
<port>
Module number.
Upstream port number.
Example:
Show interface upstream 1/0:

CASA-CMTS(config)# show interface upstream 1/0
frequency 20000000
power-level 0
rate-limit
no shutdown
Displaying upstream interface statistics

To show the statistics of an upstream interface:
304
CASA CMTS
Step
1
Command (config)
Purpose
show interface upstream <module>/<port> stat
Display
upstream
interface
statistics.
Where:
<module>
Module number.
<port>
Example:
Show interface upstream 1/0:
CASA-CMTS(config)# show interface upstream 1/0 stat
Interface upstream 1/0 statistics
Interface upstream 1/0.0 statistics
Admin status: UP
Received 1272 broadcasts, 0 multicasts, 2890
unicasts
0 discards, 0 errors, 0 unknown protocol
12846 Unerroreds, 0 Correcteds, 5 Uncorrectables
Total Modems On This Upstream Channel: 7 ,7
active cm,0 secondary cm
Req Mslots 34205744, Used Req Mslots 1272
Init Mtn Mslots 805752, Used Init Mtn Mslots 0
Total Mslots 35032311, Ucast Granted Mslots 20807
Avg upstream channel utilization: 0
Channel utilization interval: 10
Changing the upstream MAP size

Upstream map size specifies the minimum map size. The unit is in milliseconds. Smaller map
size reduces upstream latency at the expense of more frequent MAP messages that consume
more downstream bandwidth. To change the upstream MAP size:
Step
1
Command (config)
Purpose
upstream map size <2-10>
Change the
upstream MAP
size.
Where:
<2-10>
Values are in milliseconds. The default is 5. Casa

recommends using the default value.
Example:
Enter upstream
CASA-CMTS(config)# upstream map-size 6
Entering the upstream port interface configuration mode

To enter upstream port interface configuration mode:
305
CASA CMTS
Step
1
Command (config)
Purpose
interface upstream <module>/<port>
Enter upstream
port interface
configuration
mode.
Where:
<module>
<port>
Module number.
Example:
Enter upstream interface mode for upstream port 6 on module 2:
CASA-CMTS(config)# interface upstream 2/6
CASA-CMTS(config-if-ups 2/6)#
Ending an upstream port interface configuration session

To end an upstream port interface configuration session:
Step
1
Command (config)
Purpose
end
End an upstream port

interface configuration
session.
Example:
Exit upstream interface mode:

CASA-CMTS(config-if-ups 2/0)# end
CASA-CMTS(config)#
Enabling upstream ports

To enable an upstream port, use the following command:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:
Enter upstream interface mode for upstream port 6 on module
2:
no shutdown
Enable an upstream
port.
Example:
Enable upstream port 7 on module 3:
CASA-CMTS(config-if-ups 3/7)# no shutdown
306
CASA CMTS
Disabling upstream ports

To disable an upstream port:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:

2:
shutdown
Disable an upstream
port.
Example:
Disable upstream port 7 on module 3:
CASA-CMTS(config-if-ups 3/7)# shutdown
Setting the logical-channel channel-frequency

Channel-frequency is an upstream port parameter. To set the upstream channel frequency:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number
Upstream port number
Example:

2:
2
frequency <frequency>
Set the logical-channel

channel-frequency.
Example:
Set frequency to 10,000,000 Hz for upstream port 2/6:
CASA-CMTS(config-if-ups 2/6)# frequency
10000000
307
CASA CMTS
Setting the upstream input power level

The Casa CMTS controls the output power-levels of CMs to meet the desired upstream input
power level. The nominal input power-level for the upstream RF carrier is specified in decibels per
millivolt (dBmV). The default setting of 0 dBmV is the optimal setting for the upstream powerlevel.
Power-level is an upstream port parameter. To set the upstream input power-level:
Purpose
1

Where:
<module>
<port>
Enter upstream port

mode.
module number
upstream port number
Example:

2:
power-level <level>
Where:
<level>
Set the upstream input

power level.
Upstream input power level in dBmV. The

default setting is 0 dBmV. The valid range
depends on the data rate. At 1.6 MHz, the valid
range is 10 to 25 dBmV.
Example:
Set input power- level to 10 dBmV for upstream port 2/6:
CASA-CMTS(config-if-ups 2/6)# power-level 10
Caution: Increases in the upstream port input power-level will lead to an increase in the CMs
transmit power-level. This creates higher carrier-to-noise ratio (C/N), but also generates distortion
products. Composite Second Order Beat (CSO) and Composite Triple Beat (CTB) values worsen
by 2 dB for every 1 dB-increased C/N. The return path laser immediately enters a nonlinear mode
called clipping, and all communication becomes unreliable. Many return lasers send short bursts
above the clipping thresholds and fail on longer or successive bursts. Input power level should
not be adjusted by more than 5 dB in a 30-second interval. If the power level is increased or
decreased by more than 5 dB within 30 seconds, cable interfaces are disrupted.
Adjusting the upstream input power threshold

The upstream input power threshold determines whether or not the CMTS will send power
adjustments. If the modem transmits power is within the threshold, the CMTS sends no
adjustment. If it is beyond the threshold, then the CMTS sends a power adjustment. After 16
308
CASA CMTS
failed attempts, the CMTS stops sending ranging and the modem remains offline. For normal
operation, use the default value.
To adjust the upstream input power threshold, use the command power-adjustment threshold:
Step
1
Command (config)
Purpose
Enter upstream port

interface
configuration mode.
Where:
<module>
<port>
Module number.
Example:

power-adjustment threshold <level>
Where:
<level>
Adjust the upstream

input power threshold
Upstream input power adjusts level in dBmV.

The default setting is 1 dBmV. The valid range
is 0 to 2 dBmV.
Example:
CASA-CMTS(config-if-ups 2/6)# power-adjustment
threshold 2
Adjusting the upstream input power level

The CMTS can be set to continue to adjust the modem power output during ranging response. If
the power offset is within the power set by the power-adjust continue command, then the CM is
properly ranged in transmit power. If it is beyond this, the CMTS continues to send power adjust
messages.
This command is helpful during troubleshooting, when a modem fails to complete ranging due to
the power level. This is usually due to attenuation in the cable plant. By setting the power-adjust
level higher, it is possible for the modem to complete ranging. For normal operation, use the
default value.
To adjust the upstream input power level to make it easier for CM to complete ranging, use the
command power-adjustment continue:
Step
1
Command config)
Purpose
Enter upstream port

mode.
Where:
309
CASA CMTS
<module>
Module number.
<port>
Upstream port number
Example:

power-adjustment continue <level>
Where:
<level>
Adjust the upstream

input power level.
Upstream input power adjusts level in dBmV.

The default setting is 2 dBmV. The valid range
is 2 to 15 dBmV.
Example:
Set input power adjust level to 5 dBmV for upstream port 1/0:
CASA-CMTS(config-if-ups 1/0)# power-adjustment
continue 5
Setting the upstream map-advance

Map-advance is an upstream port parameter. To configure the dynamic map advance algorithm,
use the map-advance command in upstream configuration mode. Use the no form of this
command to disable this function.
MAP advance defines the amount of look-ahead time for MAPs based on the plant
characteristics. The system already has a built-in look-ahead time to account for internal
operation, like generating the MAP. You can set the MAP advance on the CMTS in either
dynamic or static mode.
Dynamic MAP advance automatically tunes the look-ahead time by calculating the offset to the
farthest modem on that upstream port. You can then specify a delay value that defines an
additional look-ahead time for MAPs to allow for internal latencies and inaccuracies in the
measurement system. The minimum delay value is 200 microseconds; the maximum is 2000
microseconds.
For example, map-advance dynamic 200 will set the look-ahead time to 200 microseconds more
than the time calculated by the dynamic MAP advance algorithm for the farthest modem on that
port.
Static MAP advance uses a fixed look-ahead time specified by the user. (For reference, a mile of
coax cable has a delay of about 7 microseconds; a mile of fiber has a delay of about 8
microseconds.) The minimum value is 200 microseconds; the maximum is 4000 microseconds.
For example, map-advance static 400 will set the look-ahead time to 400 microseconds.
The default is equivalent to map-advance static 3000. This is a conservative value. Using
large delay values increases the run-time look-ahead in MAPs, but is also reduces the upstream
310
CASA CMTS
performance. Casa recommends that that the MAP advance be adjusted for the physical
characteristics of the plant. A delay value of 200 ms is usually adequate.
For optimal performance, measure the throughput relative to the percent utilization and adjust the
delay value to achieve maximum throughput.
Step
1
Command (config
Purpose
Enter upstream
port interface
configuration
mode.
Where:
<module>
<port>
module number
Example:

[no] map-advance [dynamic <max-delay> | static <max-delay>]
Note: Using larger max-delay increases the run time look ahead in
MAPs, but reduces the upstream performance.
Where:
dynamic
max-delay
Set the
upstream mapadvance.
Enables the dynamic MAP advance algorithm

that automatically tunes look-ahead time in
MAPs based on the current farthest CM on a
particular upstream port. This value controls the
amount of extra look-ahead time in MAPs to
account for inaccuracies of the measurement
system and internal software latencies. The valid
range is 200 to 2000 microseconds, with a
default of 1000.
static
Enables the static map advance algorithm that

uses a fixed look-ahead time value in MAPs
based on the worst case propagation delay of
100 mile HFC cable network.
max-delay
Specifies the maximum round trip delay between

the CMTS and furthest CM in microseconds. The
valid range is 200 to 4000 microseconds, with a
default of 1800. The typical delay for a mile of
coaxial cable is approximately 7 microseconds.
The typical delay for a mile of fiber cable is
approximately 8 microseconds.
Example:
Set the dynamic map advance to 400 microseconds:
311
CASA CMTS
CASA-CMTS(config-if-ups 3/1.0)# map-advance dynamic

400
CASA-CMTS(config-if-ups 3/1.0)#
Defaults: Dynamic map-advance with a safety factor of 1000 microseconds and a max-delay of
1800 microseconds.
Enabling the upstream logical-channels

To enable an upstream logical-channel:
Step
1
Command (config)
Purpose
Enter the upstream

port interface
configuration mode.
Where:
<module>
<port>
Module number.
Example:
2
no logical-channel <num> shutdown

Where:
<num>
Enable the
upstream
logical-channels.
logical channel number. Valid values are 0 to the

supported logical channel minus one.
Example:
Enable logical-channel 0 under upstream 2/6:
CASA-CMTS(config-if-ups 2/6)# no logical-channel
0 shutdown
Disabling the upstream logical-channels

To disable an upstream logical-channel:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
312
CASA CMTS
Example:

logical-channel <num> shutdown
Where:
<num>
Disable the upstream

logical-channels.
Logical channel number. Valid values are 0 to

the supported logical channel minus one.
Example:
Disable logical-channel 0 under upstream 2/6:

CASA-CMTS(config-if-ups 2/6)# logical-channel 0
shutdown
Setting upstream channel backoff values

The DOCSIS-specified method of contention resolution for CMs wanting to transmit on the
upstream channel is a truncated binary exponential backoff value, with the initial backoff window
and the maximum backoff window controlled by the CMTS. The CMTS specifies backoff window
values for both data transmission and initial ranging. It sends these values downstream as part of
the Bandwidth Allocation Map (MAP) MAC message.
The values are configurable and are power-of-two values. For example, a value of 4 indicates a
window between 0 and 15; a value of 10 indicates a window between 0 and 1023. The user can
set fixed start and end values for data backoff on the upstream ports, or set the upstream ports
for automatic data backoff. The user has the same options for ranging backoff. For both backoff
windows, the default start value is 0; the default end value is 4. Valid values are from 0 to 15.
Note: Automatic dynamic backoff algorithm is recommended for data transmission. For initial
ranging, use 4 and 10.
To set data-backoff values, use the following command:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:

2:
313
CASA CMTS
logical-channel <num> data-backoff { automatic | <start>

<end> }
Where:
<num>
Set upstream channel

backoff values.
Logical-channel number. Valid values are 0

to the supported logical channel minus one.
automatic
Automatic data backoff adjustment
<start>
Data backoff start value in the range 0 to 15.
<end>
Data backoff end value, in the range 0 to 15.
Example:
Set data-backoff to 2 and 8 for channel 0 on interface 2/6:
CASA-CMTS(config-if-ups 2/6)# logical-channel
0 data-backoff 2 8
To set data-backoff values to the default values of 0 and 4:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:
2:
logical-channel <num> data-backoff
Example:
Set upstream data backoff to default values 0 and 4 for
channel 0:
Set data-backoff values

to the default values of 0
and 4.

0 data-backoff 0 4
To set ranging-backoff values:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
module number
314
CASA CMTS
Example:
2:
logical-channel <num> ranging-backoff <start> <end>
Where:
<num>
Set ranging-backoff
values.
Logical-channel number in the range 0 to the

supported logical channel minus one.
<start>
Ranging backoff start value; valid values are 0 to

15.
<end>
Ranging backoff end value; valid values are 0 to

15.
Example:
Set ranging-backoff to 4 and 10 (recommended) for channel 0
on upstream 2/6:
0 ranging-backoff 4 10
The upstream interface reconnection time after a power outage is related to the following factors:
DHCP, ToD, and TFTP servers often operate well below 1 percent load under normal
situations, but can jump to 100 percent after an outage.
Increasing backoff slows upstream interface reconnection and reduces server load.
Small backoffs result in upstream interfaces failing to range the upstream RF levels correctly
and cycling to maximum power, thus increasing connection time and reducing network
performance.
Large backoffs result in increased recovery time after a large scale service outage.
There is significant variation in cable interface performance (brand to brand) in

upstream interface restart time.
All upstream interfaces should recover in 0 to 10 minutes after all services are restored (Casa
CMTS, RF transport, DHCP, TFTP, and ToD servers). Problems in the cable modem
configuration, CMTS configuration, and the DOCSIS provisioning servers could lead to longer
recovery time.
Setting the upstream channel mini-slot size

To set the upstream minislot size:
Step
1
Command (config)
Purpose
Enter Upstream Port

Interface Configuration
mode.
Where:
<module>
Module number.
315
CASA CMTS
<port>
Example:

logical-channel <num> minislot <size>
Where:
<num>
<size>
Set the upstream

channel mini-slot size.
Logical-channel number. Valid values are 0 to

Upstream minislot size in ticks. Valid values
are 1, 2, 4, 8, 16, 32, 64, 128. The default is 8.
Example:
Set minislot size to 64 ticks for channel 0:
minislot 64
Setting the upstream channel modulation profile

A modulation profile is a collection of burst profiles that are sent to the CMs in upstream channel
descriptor (UCD) messages to configure modem transmit parameters.
To set the modulation profile:
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:

logical-channel <num> profile <profile>
Where:
<num>
<profile>
Set the upstream

channel modulation
profile.
Logical-channel number. Valid values are 0 to

Modulation profile ID.
Example:
316
CASA CMTS
Set modulation-profile to profile 2 for channel 0:

profile 2
Setting the upstream channel pre-equalization

Pre-equalization compensates for the difference in delays between the signal on the lower part of
the 6Mhzchannel spectrum and the higher part caused by imperfections in the cable plant. The
default state is disabled, but Casa recommends that it be enabled.
To enable/disable the pre-equalization follow the command below:
Step
1
Command (config)
Purpose
Enter Upstream Port

Interface Configuration
mode.
Where:
<module>
<port>
Module number.
Example:

[no] logical-channel <num> pre-equalization
Where:
<num>
Set the upstream

channel preequalization.
Logical channel number. Valid values are 0

to the supported logical channel minus one.
Example:
Enable pre-equalization for channel 0:
pre-equalization
Disable pre-equalization for channel 0:
CASA-CMTS(config-if-ups 2/6)# no logicalchannel 0 pre-equalization
Enabling/disabling ingress noise cancellation

The default state is disabled. To enable ingress noise cancellation follows the command below:
317
CASA CMTS
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:
2:
[no] ingress-cancellation <intv>
Where:
<intv>
Enable or disable
ingress noise
cancellation.
Sampling interval time for ingress cancellation in

milliseconds. Valid values are 10 to 1000. The
default setting is 200 milliseconds.
Example:
CASA-CMTS(config-if-ups 2/6)#ingresscancellation 100
Setting up voice bandwidth reserve percentage

To configure the percentage of reserved bandwidth dedicated for voice calls on upstream
channels, use the voice-bw-reserve parameter. When the configured percentage threshold is
reached, no new voice calls are accepted on that channel. Any unused portion of the configured
percentage will be available for data sessions. However, new voice calls will assume priority and
preempt any data sessions. Additionally, you can also reserve a portion of the configured voice
bandwidth percentage for emergency calls.
Step
1
Command (config)
Purpose
Enter upstream port

mode.
Where:
<module>
<port>
Module number.
Example:

voice-bw-reserve <num=0:100> [emergency <num=0:100>]
Where:
Specify reserve
bandwidth percentage
for upstream voice
318
CASA CMTS
<num=0:100>
emergency <num=0:100>
Percentage; default is 75
percent
Percentage; default is 0
percent
calls.
Example:
casa-121(config-if-ups 3/6)#voice-bw-reserve 75
emergency 10
casa-121(config-if-ups 3/6)#
In the above example, 75% of the bandwidth on upstream
interface 3.1.0 is reserved for voice calls, with 10% of that
percentage available for emergency calls. The remaining 25%
bandwidth is available for data and video traffic.
Note: To allow emergency calls to preempt all other calls, use the top-level cable admissioncontrol preempt priority voice command. The default setting is enabled. Additionally, the
interface upstream rate-limit setting that enforces cable modem limits at the CMTS is enabled by
default.
Enabling rate limiting

The Casa CMTS enforces the rate limit defined in the modem configuration. This is the default.
To turn off rate limiting:
1

Where:
<module>
<port>
Purpose
Enter upstream port
mode.
Module number.
Example:

[no] rate-limit
Enable or disable rate

limiting.
Example:
CASA-CMTS(config-if-ups 2/6)# rate-limit
Displaying the upstream channel utilization rates

This command is used to display the utilization rates of all upstream channels. To show the
utilization rates of all upstream channels:
319
CASA CMTS
Step
1
Command (config)
Purpose
show docsis upstream channel utilization
Show the utilization rates

of all upstream channels.
Example:
See example below.
Example: Displaying the utilization rates of upstream channels

CASA-CMTS(config)# show docsis upstream channel utilization
Upstream Slot/Port.Channel
Utilization (%)
1/0
0
1/1
0
1/2
0
1/3
0
Displaying the upstream channel signal quality

This command is used to display the average signal-to-noise ratio (SNR) of the upstream
channels in dB units. To show the SNR of upstream channels:
Step
1
Command (config)
Purpose
show upstream {[<module>/<port>] signal-quality | channel set}
Show the
upstream channel
signal quality.
Where:
<module>
<port>
Module number.
Upstream port number. The valid values are
0 to 15.
Example:
To show the SNR of all the upstream channels:
CASA-CMTS(config)# show upstream signal-quality
upstream port
signal noise
1/0
42.0
1/1
42.0
1/2
42.0
1/3
38.2
To show the SNR of upstream port 1/0:
CASA-CMTS(config)#show upstream 1/0 signal-quality
upstream port
signal noise
1/0
42.0
320
CASA CMTS
Displaying the upstream-channel set ID

To show the upstream channel set IDs:
Step
1
Command (config)
Purpose
show upstream channel set
Displaying the upstreamchannel set ID.
Example:
To show all the upstream-channel set IDs:

CASA-CMTS(config)# show upstream channel set
MAC Chan Channel
ID
Set
List
1
1 1/0/0
1
2 1/1/0
1
3 1/2/0
1
4 1/3/0
1
256 1/0/0, 1/1/0, 1/2/0, 1/3/0
Displaying upstream interface statistics

To show the statistics of upstream interfaces:
Step
1
Command
Purpose
show interface upstream <module>/<port> stat
Show the statistics of

upstream interfaces.
Where:
<module>
<port>
Module number.
Upstream port number in the range 0 to
15.
Example:
To show the statistics of upstream interface 1/0:

CASA-CMTS#show interface upstream 1/0 stat
Interface upstream 1/0 statistics
Admin status: UP
Received 119 broadcasts, 0 multicasts, 822
unicasts
0 discards, 0 errors, 0 unknown protocol
1233 Unerroreds, 0 Correcteds, 0
Uncorrectables
Total Modems On This Upstream Channel: 1 (1
active)
Req Mslots 134961624, Used Req Mslots 267
Init Mtn Mslots 2930375, Used Init Mtn
Mslots 0
Total Mslots 137896022, Ucast Granted
Mslots 3991
Avg upstream channel utilization: 0
Channel utilization interval: 10
321
CASA CMTS
Displaying voice information

To show the voice information on the upstream interfaces:
Step
1
Command
Purpose
show cable voice summary
Display voice
information.
Where:
<module>
Module number.
Configuring IP-bundle interfaces

The IP-bundle interface is used to group many physical interfaces as an IP subnet for a defined
MAC domain. In the 5.4 and following software versions, all MAC domains must use the IP
bundle. The cable helper and IP address information cannot be entered separately in the MAC
domain interface. This section covers the following IP-bundle operations:
Creating the IP-bundle interface
Adding the primary IP interface
Adding the secondary IP interface
Removing the secondary IP interface
Adding the helper-address
Configuring an IP-bundle sub interface
Applying IP bundle interfaces to MAC domains
Displaying the IP-bundle interface configuration
To create or enter an IP-bundle interface, use the interface ip-bundle command in configuration
mode.
Step
1
Command (config)
Purpose
interface ip-bundle <id>
Create or enter the IPbundle interface.
Where:
<id>
IP bundle interface ID. Valid values are 1 to 16.
Example:
Create an IP-bundle interface with ID=2:
CASA-CMTS(config)# interface ip-bundle 2
CASA-CMTS(ip-bundle 2)#
322
CASA CMTS
Adding the primary IP interface

To add the primary IP address to IP-bundle interface:
Step
1
Command (config)
Purpose
Create or enter
the IP-bundle
interface
Where:
<id>
Example:

ip address <addr> <mask>
Where:
<addr>
<mask>
Add the primary

IP interface.
IP address of the primary sub interface in

decimal format.
Mask of the primary sub interface in decimal
format.
If only the primary IP is configured (no secondary IP or dhcp-addr), all

DHCP discovery messages (CM, MTA and CPE) will be relayed to the
DHCP server with a source IP address of the primary IP.
Example:
Add primary IP address 10.248.1.1 to IP-bundle interface 2:
CASA-CMTS(ip-bundle 2)# ip address 10.248.1.1
255.255.255.0
Adding a secondary IP bundle interface

Many secondary IP interfaces can be bundled to each IP-bundle interface. Up to 512 secondary
IP addresses are supported. To add a secondary IP address to IP-bundle interface:
Step
1
Command (config)
Purpose
interface ip-bundle <id.num>
Create or
enter the IPbundle
Interface.
Where:
<id.num>
Specifies the IP bundle interface number and subinterface number separated by a period (.) character.
IP bundle valid values are 1 to 16; sub-interfaces
values are 1 to 511
Example:
323
CASA CMTS
Create an IP-bundle sub-interface with the identifier 1.511
CASA-CMTS(config)# interface ip-bundle 1.511

CASA-CMTS(ip-bundle 1.155)#
ip address <addr> <mask> secondary
Where:
<addr>
<mask>
IP address of the primary subinterface in decimal

format.
Add an IP
address to an
IP bundle subinterface.
Primary subinterface mask in decimal format.
If the primary IP and at least one secondary IP (no dhcp-giaddr) is

configured, the DHCP discovery from the CM will be relayed to the
DHCP server with a source IP address of the primary while the DHCP
discovery from the MTA and CPE will be relayed to the DHCP server
with a source IP address of the first secondary IP. If more than one
secondary IP address is configured, the DHCP server assigns the IP
addresses in the different subnets to the CPE or MTA.
Example:
Add a secondary IP address 10.248.4.1 to IP-bundle interface 1.511.
CASA-CMTS(ip-bundle 1.511)# ip address 10.248.4.1
255.255.255.0 secondary
Remove an IP bundle secondary IP address

To remove a secondary IP address from an IP bundle interface:
Step
1
Command
Purpose
Create or enter
the IP-bundle
Interface.
Where:
<id.num>
values are 1 to 511.
Example:
Create an IP-bundle sub-interface with the identifier 1.511

no ip address <addr> <mask> secondary
Where:
<addr>
<mask>
Remove a
secondary IP
interface.
IP address of the primary sub interface, in

decimal format.
Network mask of the primary sub interface in
324
CASA CMTS
decimal format.
Example:
Remove a secondary IP address 10.248.4.1 to IP-bundle
interface1.511:
CASA-CMTS(ip-bundle 1.511)# no ip address 10.248.4.1
255.255.255.0 secondary
Adding primary and secondary IPv6 interfaces

To add primary and secondary IP addresss to IP-bundle interface:
Step
1
Command (config)
Purpose
Create or enter
the IP-bundle
Interface.
Where:
<id.num>
Example:
Create an IP-bundle sub-interface with the identifier 1.511:

[no] ipv6 address <ipv6-address>/<mask_len> [secondary]
Where:
<ipv6address>
Text string for standard IPv6 address format:

<mask_len>

2001:0db8:0100:f101:0210:a4ff:fee3:9566
2001:0000:0000:0000:0000:0000:1000:1 (This can
be shortened to: 2001::1000:1)
secondary
Specify secondary to indicate a secondary IPv6 IP

bundle interface.
Assign an IPv6
address to a
primary or
secondary IPbundle interface.
Example:
Assign IPv6 address 2000::1000:1/64 to a secondary IP bundle
interface.
CASA-CMTS(ip-bundle 1.155)# ipv6 address
2000::1000:1/64 secondary
CASA-CMTS(ip-bundle 1.155)# no ipv6 address
325
CASA CMTS
Adding a helper-address
To specify a destination IP address for User Datagram Protocol (UDP) broadcast Dynamic Host
Configuration Protocol (DHCP) packets, use the helper-address command in the ip-bundle
configuration mode. To disable this feature, use the no form of this command. Many helperaddresses can be added in each IP-bundle interface.
Step
1
Command (config)
Purpose
Create or enter
the IP-bundle
interface
Where:
<id>
Example:

[no] cable helper-address <ip _addr> [cable-modem | host | mta]
Add a helperaddress.
[no] cable helper-address <ipv6 _addr> [cable-modem | host |

mta]
Where:
<ip_addr>
The IP address of a DHCP server to which

UDP broadcast packets will be sent.
<ipv6_address>/
The IP address of a DHCP server to which

UDP broadcast packets will be sent in standard
IPv6 address format: xxx:xxxx:xxxx:...:xxxx
host
(Optional) Specifies that only host UDP

broadcasts are forwarded by the CMTS
mta
(Optional) Specifies that only MTA UDP

broadcasts are forwarded by the CMTS
If no options are specified, all the broadcasts are forwarded to the

same DHCP server IP.
Example:
Forward UDP broadcasts from both CMs and CPE devices to the
DHCP server at 10.243.6.4:
CASA-CMTS(ip-bundle 2)# cable helper-address
10.243.6.4
CASA-CMTS(ip-bundle 2)# cable helper-ipv6-address
3000::6
CASA-CMTS(config)#
326
CASA CMTS
Configure IP bundle sub-interfaces (Release 5.4)

Release 5.4 and later supports up to eight IP bundle sub-interfaces. This allows the network to be
partitioned into multiple subnets. The cable modems can receive IP addresses on different
subnets from the DHCP server. The CPE DISCOVER message will have an IP address from the
subnet associated with the cable modems IP address. In the example below:
If the CM's IP is in the subnet of 172.18.32.0/24, the DHCP discovery for the CPE will have
source IP of 192.168.254.254;
If the CM's IP is in the subnet of 10.0.0.0/24, the DHCP discovery will have source IP of
192.168.54.254;
If the CM's IP is in the subnet of 192.168.5.0/24, the DHCP discovery will have source IP of
10.110.50.25.
ip address 172.18.32.4 255.255.255.0
ip access-group 123
interface ip-bundle 1.1
ip address 10.0.0.3 255.255.255.0
ip access-group 123
interface ip-bundle 1.2
ip address 192.168.5.1 255.255.255.0
ip access-group 123
Applying IP bundle interfaces to MAC domains

After creating one or more IP bundles, you will need to apply the configured IP bundles to the
DOCSIS MAC interfaces, as covered in the next section. This ensures that all primary and
secondary IP interfaces, access groups (using configured ACLs) and helper addresses are
associated with specific MAC domain.
To bind an IP-bundle interface to a MAC domain:
Step
1
Command (config)
Purpose
[no] interface docsis-mac <domain-id>
Create new domain

interfaces or enter an
existing one.
Where:
<domain-id>
MAC domain number. The valid values

are 1 to 32.
327
CASA CMTS
Example:
Create a new MAC domain interface with domain id = 2 or
enter an existing one:
CASA-CMTS(config)# interface docsis-mac 2

CASA-CMTS(config-if-mac 2)#
ip bundle <id>
Where:
<id>
Bind IP-bundle
interfaces.
User-defined IP bundle interface identity in the

range 1 to 16 and is unique within a MAC domain.
Example:
Bind ip-bundle 6 to MAC domain:
CASA-CMTS(config-if-mac 2)# ip bundle 6
Classifying CPE devices for DHCP option 60 string matching

The CMTS allows you to classify CPE devices, such as IP phones, personal computers, and settop boxes so that DHCP requests from those CPEs for IP addresses are forwarded by the CMTS
to specific DHCP servers.
Using the cpe-class command, define a named cpe-class grouping, and then specify any
number of DHCP option 60 strings that the CMTS will match to configured DHCP server IPs.
When the CMTS receives a DHCP option 60 string from a vendor CPE device, the CMTS will
check the IP-bundle and cable helper addresses for a matching string. If the string match exists,
the CMTS forwards the request to the DHCP server IP address and awaits a DHCP response
that the CMTS will return to the requesting CPE.
In the following CLI session, the cpe-class command defines two CPE classes: setTopBoxes
and computers. A CPE class name can have up to 11 alphanumeric characters. Each class
includes one or more DHCP option 60 strings (with up to 32 alphanumeric characters).
In this example, stbUser1 and pcUser1 are the expected DHCP option 60 strings from the CPEs.
The CMTS will check the IP-bundle and cable helper-address (DHCP server address) CPE
classes for the matching strings.
The CPE device with the DHCP option 60 string of stbUser1 will get its IP address from the
DHCP server at IP 192.168.3.16. Similarly, the CPE device with DHCP option 60 string of
pcUser1 will get its IP address from the DHCP server at 192.168.3.17.
CASA(config)#cpe-class setTopBoxes
CASA(conf-cpe-class stb)#dhcp option 60 stbUser1
CASA(config)#cpe-class computers
CASA(conf-cpe-class stb1)#dhcp option 60 pcUser1
CASA(conf-cpe-class stb1)#end
328
CASA CMTS
CASA(config)#interface ip-bundle 1
CASA(ip-bundle 1)# ip address 10.231.1.1 255.255.255.0
CASA(ip-bundle 1)# ip address 10.231.13.1 255.255.255.0 setTopBoxes
CASA(ip-bundle 1)# ip address 10.231.20.1 255.255.255.0 computers
CASA(ip-bundle 1)# cable helper-address 192.168.3.16 setTopBoxes
CASA(ip-bundle 1)# cable helper-address 192.168.3.17 computers
CASA(ip-bundle 1)# cable helper-address 192.168.3.6
If a received DHCP option 60 string does not match the CMTS configuration, the CPE client
request will be forwarded to the default DHCP server (at 192.168.3.6 in the above example.)
Use the show cpe-class command to display the configured DHCP classes and option 60
strings.
Step
1
Command (config)
Purpose
[no] cpe-class <string>
Create a new CPE class,

or open and existing
class for editing.
Where:
<string>
Specifies the user-defined name of the CPE

class with up to 11 alphanumeric characters.
Example:
Create a new cpe-class named computers.
CASA-CMTS(config)# cpe-class computers

CASA-CMTS(conf-cpe-class computers)#
dhcp option 60 <string>
Where:
<string>
Specify the DHCP option

60 string to match.
Specifies the DHCP option 60 string to match

using up to 32 alphanumeric characters.
Example:
Bind ip-bundle 6
Configuring the IP RIP authentication key chain

To enable authentication of RIP packets, use the ip authentication key-chain command in
interface configuration mode. To disable such authentication, use the no form of this command.
329
CASA CMTS
Step
1
Command (config)
Purpose
Enter ip-bundle interface

mode.
<id>
Example:
[no] ip rip authentication key-chain <name>
Where:
<name>

RIP authentication Key
chain.
Name of the authentication key chain.
Example:
Applies authentication to the autonomous system named
school:
CASA-CMTS(ip-bundle 1)# # ip rip
authentication key-chain school
To disable:
CASA-CMTS(ip-bundle 1)# no ip rip
authentication key-chain
Configuring an IP RIP authentication string

To enable authentication string, use the ip authentication string command in interface
configuration mode. To disable such authentication, use the no form of this command.
Step
1
Command (config)
Purpose
Enter the ip-bundle

interface mode.
<id>
Example:
[no] ip rip authentication string <name>
Where:
<name>

RIP authentication string.
Authentication string name up to 16 characters.
Example:
Configure authentication string as public:
CASA-CMTS(ip-bundle 1)# ip rip authentication
string public
330
CASA CMTS
To disable:
CASA-CMTS(ip-bundle 1)# no ip rip
authentication string
Configuring the IP RIP authentication mode

To specify the type of authentication used in RIP packets, use the ip authentication mode
command in interface configuration mode. To disable that type of authentication, use the no form
of this command.
Step
1
Command (config)
Purpose
Enter the ip-bundle

interface mode.
<id>
Example:
[no] ip rip authentication mode { text | md5 [auth-length
rfc] }
Where:
text
Text authentication mode.
md5
MD5 authentication mode.
RIP authentication
mode.
Example:
Configure the interface to use MD5 authentication:
authentication mode md5 auth-length rfc
Displaying the IP bundle interface configuration and statistics

To display the IP-bundle configuration:
Step
1
Command (config)
Purpose
show interface ip-bundle [<num>] [acl-count [details] | brief | stat |

throughput [duration] | service-policy-count [details] ]
Display the IPbundle

configuration
and statistics.
Where:
<num>
acl-count
The number of the IP bundle interface in the range

1 to 16.
Indicates the packet drop count from ACL deny
rules. Use the optional details parameter to show
the packet count per rule.
331
CASA CMTS
brief
Displays minimum information about the IP bundle

interface.
stat
Shows trunk interface statistics.
throughput
Shows IP bundle interface throughput. Use the

optional duration parameter to display throughput
over a specified number of seconds (1 to 100).
servicepolicy-count
Shows the packet count associated with one or

more policy rules. Use the optional details
parameter to show the packet count per rule.
This command accepts output modifiers.

Example:
CASA-CMTS(config)# show interface ip-bundle
ip address 10.232.1.1 255.255.255.0
ipv6 address 2000:232:1::1/60
ipv6 address 2000:232:2::1/60 secondary
cable helper-ipv6-address 3000::10
CASA-CMTS(config)# show interface ip-bundle 1 stat
ip-bundle:
upstream bytes:
upstream packets:
downstream unicast bytes:
downstream multicast bytes:
downstream total bytes:
downstream unicast packets:
downstream multicast packets:
downstream total packets:
1
144574
2118
96070
0
96070
446
0
446
CASA-CMTS(config)# show interface ip-bundle

throughput
ip-bundle:
1
upstream:
0 kbps
upstream:
0 packet/second
downstream:
0 kbps
downstream:
0 packet/second
332
CASA CMTS
Configuring MAC domains

A MAC sub-layer domain is a collection of upstream and downstream channels for which a single
MAC Allocation and Managautement protocol operates.
Upstream and downstream channels operation is in shutdown state unless they are bounded in
an enabled MAC domain. A MAC domain cannot be enabled without IP address, helper address,
at least one downstream and upstream. In the 5.4 and later versions of the software, the IP
addresses must be configured in an IP bundle interface that is assigned to the MAC domain.
This section describes the commands for domain management. It covers following:
Displaying domain interface configurations
Creating new domain interfaces
Entering domain interface configuration mode
Ending the domain interface configuration session
Removing domain interfaces
Binding IP-bundle interfaces
Binding upstream interfaces
Binding downstream interfaces
Binding secondary downstream interfaces
Deleting upstream interfaces
Deleting downstream interfaces
Enabling MAC domain interfaces
Disabling MAC domain interfaces
Setting domain interface IP addresses (5.2 only)
Setting domain interface IPv6 addresses
Removing domain interface IPv6 addresses
Setting the helper-address (5.2 only)
Setting IP bundle interfaces
Setting the domain sync-interval
Setting the upstream insertion interval
Setting the MDD interval
Enabling/disabling the TFTP proxy on MAC domain interfaces
Configuring multicast on MAC domain interface
Enabling/disabling DHCP authorization on MAC domain interface
Configuring channel bonding on MAC domain interfaces
Configuring IP-provisioning-mode on MAC domain interfaces
Displaying MAC domain interface configurations and statistics
333
CASA CMTS
Displaying domain interface configurations

To show a specified domain interface configuration or all configurations:
Step
1
Command
Purpose
show interface docsis-mac [brief]

or
show interface docsis-mac <domain-id> [brief]
Show a specified
domain interface
configuration.
Where:
<domain-id>
MAC domain number. The valid values are

1 to 32.
Example:
Show configurations for all MAC domains, assume the chassis has
48 downstream channels and 8 upstream channels that bound to 8
upstream-port interfaces:
CASA-CMTS# show interface docsis-mac
no shutdown
sync-interval 10
insertion-interval 20
ucd-interval 1000
no dhcp-authorization
invited-ranging-attempts 16
ip-provisioning-mode ipv4-only
no early-authentication-encryption
no extended-upstream-frequency-range
cm-status event report
multicast-dsid-forward
downstream channel bonding
upstream channel bonding
no tftp-proxy
no upstream drop classifier
no send udc rules
no dhcp-giaddr-primary
mdd interval 2000
sid-cluster max-requests 0
sid-cluster max-outstanding-bytes 0
sid-cluster max-total-bytes 0
sid-cluster max-time 0
max sid-cluster per-service-flow 2
ip bundle 1
upstream 1 interface upstream 1/0.0/0
334
CASA CMTS

mgmd ipv4 query-interval 125
mgmd ipv4 version 3
mgmd ipv4 max-query-response-time 100
mgmd ipv4 proxy-interface gige 0
mgmd ipv4 robustness 2
mgmd ipv4 last-member-query-interval 10
mgmd ipv4 shutdown
mgmd ipv6 query-interval 125
mgmd ipv6 version 2
mgmd ipv6 max-query-response-time 100
mgmd ipv6 proxy-interface gige 0
mgmd ipv6 robustness 2
mgmd ipv6 last-member-query-interval 10
mgmd ipv6 shutdown
privacy kek life-time 604800
privacy tek life-time 43200
Creating new domain interfaces

To create a new MAC domain interface or enter an existing one:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>
MAC domain number. The valid

values are 1 to 32.
Example:
Use the no form to

remove a MAC domain
interface.

CASA-CMTS(config-if-mac 2)# end
CASA-CMTS(config)#
Remove the interface:
CASA-CMTS(config)# no interface docsis-mac 2
Binding IP-bundle interfaces

To bind an IP-bundle interface to a MAC domain:
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
335
CASA CMTS

are 1 to 32.
<domain-id>
Example:
Create a new MAC domain interface with domain id = 2 or enter
an existing one:

ip bundle <id>
Where:
<id>
Bind IP-bundle
interfaces.
User-defined IP bundle interface identity in the

range 1 to 16 and is unique within a MAC domain.
Example:
Bind ip-bundle 6 to MAC domain:

To bind an upstream interface to a MAC domain:
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.
Example:
an existing one:

upstream <chan-id> interface upstream <X/Y.C/Z>
Where:
<chan-id>
Bind upstream
interfaces.
User-defined channel identity in the range 1 to

255 and is unique within a MAC domain.
<X>
Module (or slot) number.
<Y>
Port number.
<C>
Physical channel (RTN3 upstream line card

supports 2 physical channels.)
<Z>
Logical-channel number (RTN3 upstream line

card supports 2 logical channels.)
336
CASA CMTS
Example:
Bind upstream 1/1/0 to domain 2 with channel ID 5:

CASA-CMTS(config-if-mac 2)# upstream 5 interface
upstream 1/1/0
Deleting upstream interface bindings

To delete a bond upstream interface from a MAC domain:
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.
Example:
an existing one:

no upstream <chan-id>
Where:
<chan-id>
Delete upstream
interface bindings.
User-defined channel identity.
Example:
Remove bond upstream 5 from domain 2:
CASA-CMTS(config-if-mac 2)# no upstream 5

To bind a downstream interface to a MAC domain interface:
Step
1
Command (config)
Purpose
Create new
domain interfaces
or enter an
existing one.
Where:
<domain-id>

are 1 to 32.
Example:
Create a new MAC domain interface with domain id = 2 or enter an
existing one:
337
CASA CMTS
2
downstream <chan-id> interface qam <x/y/z>

Where:
<chan-id>
Bind downstream
interfaces.

<x>
Module number.
<y>
Port number.
<z>
Channel number in the range from 0 to 3.
Example:
Bind downstream 0/2/1 to domain 2 with channel ID 3:
CASA-CMTS(config-if-mac 2)# downstream 3 interface
qam 0/2/1
Note: One primary downstream channel can only bind to one MAC domain.
Binding secondary downstream interfaces (5.4 only)

Since the MAC domain supports a maximum of 8,191 service IDs, it is sometimes desirable to
bind secondary downstream interfaces to multiple MAC domains. This allows 3.0 modems to load
balance across several MAC domains without requiring all the downstream interfaces to be in the
same MAC domain. The secondary interfaces can be in up to four MAC domains.
Step
1
Command (config)
Purpose
Create new
domain interfaces
or enter an
existing one.
Where:
<domain-id>
MAC domain number. The valid values are

1 to 32.
Example:

existing one:

downstream <chan-id> interface qam <x/y/z> [secondary]
Where:
<chan-id>
Bind secondary
downstream
interfaces

<x>
Module number.
<y>
Port number.
<z>
Channel number in the range 0 to 3.
338
CASA CMTS
secondary:
Not primary-capable downstream.
Example:
Bind secondary downstream 0/2/1 to domain 2 with channel ID 3:

CASA-CMTS(config-if-mac 2)# downstream 3 interface
qam 0/2/1 secondary
Deleting downstream interface bindings

To delete a bound downstream interface from a MAC domain:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

values are 1 to 32.
Example:

no downstream <chan_id>
Where:
<chan_id>
Delete downstream
interface bindings.
User-defined channel identity.
Example:
Remove bound downstream 3 from domain 2:
CASA-CMTS(config-if-mac 2)# no downstream 3
Enabling MAC domain interfaces

To enable MAC domain interface 2:
Step
1
Command
Purpose
Create new domain

existing one.
Where:
<domain-id>

values are 1 to 32.
Example:
339
CASA CMTS

2
Enable MAC domain

interfaces.
no shutdown
Example:
CASA-CMTS(config-if-mac 2)# no shutdown
Disabling MAC domain interfaces

To disable MAC domain interface 2:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

values are 1 to 32.
Example:

shutdown
Disable MAC domain

interface
Example:
CASA-CMTS(config-if-mac 2)# shutdown
Setting MAC domain interface IP addresses

To set the IP address for a MAC domain interface:
Step
1
Command (config)
Purpose

Where:
<domain-id>
are 1 to 32.
Create new domain

interfaces or enter
an existing one.
Example:
existing one:
2

Where:
Set the IP address

for a MAC domain
interface
340
CASA CMTS
<ip-address>
Text string for standard IP address, in format

a.b.c.d
<subnet-mask>
Text string for standard subnet mask, in

format p.q.r.s.
To remove the IP
address for a MAC
domain interface,
use the no form of
the command.
Example:
Set IP address to 192.168.3.211 and subnet mask to
255.255.255.0 for domain 2:
CASA-CMTS(config-if-mac 2)# ip address
192.168.3.211 255.255.255.0
Setting MAC domain interface IPv6 addresses (Rel. 5.2 and earlier)
To set the IPv6 address for a MAC domain interface:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.
Example:

ipv6 address <ipv6-address> <subnet-mask>
Where:
<ipv6address>
Set the IPv6 address for

a MAC domain interface
Text string for standard IPv6 address in

format A.B.C.D
<subnetmask>
Numeric number for standard subnet mask
Usable
addresses:
2001:0db8:0100:f101:0210:a4ff:fee3:9566
2001:0000:0000:0000:0000:0000:1000:1
(This can be shortened to: 2001::1000:1)
One sequence of 20 bit blocks containing
only zeroes can be replaced with ::
Example:
Assign IPv6 address 2000::1000:1/64 to domain 2:
CASA-CMTS(config-if-mac 2)# ipv6 address

2000::1000:1/64
341
CASA CMTS
Removing MAC domain interface IPv6 addresses (Rel. 5.2 and earlier)
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.


no ipv6 address
Example:
CASA-CMTS(config-if-mac 2)# no ipv6 address
Remove IPv6 addresses

from MAC domain
interfaces.
Setting the helper-address (Software Version 5.2 and Earlier)

To specify a destination IP address for User Datagram Protocol (UDP) broadcast Dynamic Host
Configuration Protocol (DHCP) packets, use the helper-address command in MAC domain
interface configuration mode. To disable this feature, use the no form of this command.
Many helper-addresses can be specified in each MAC-domain interface.
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>
MAC domain number. The

valid values are 1 to 32.
Example:

[no] cable helper-address <ip_addr> [cable-modem | host
| mta]
Where:
<ip_addr>
cable-modem
Set or disable the helperaddress.
The IP address of a DHCP server to

which UDP broadcast packets are sent.
Optional. Specifies that only CM UDP
broadcasts are forwarded.
342
CASA CMTS
host
Optional. Specifies that only host UDP

mta
Optional. Specifies that only MTA UDP

Example:
Forward UDP broadcasts from both CMs and CPE devices to
the DHCP server at 172.23.66.44:
CASA-CMTS(config-if-mac 2)# helper-address
172.23.66.44
CASA-CMTS(config)#
Forward UDP broadcasts from CMs, MTA and CPE devices to
separate DHCP servers:
172.23.66.143 host
172.23.66.144 cable-modem
172.23.66.145 mta
CASA-CMTS(config)#
helper-address
helper-address
helper-address
end
Defaults: If no options are specified, both CM and host UDP broadcasts are forwarded.
Note: The user must specify both the cable-modem or host options in separate commands, using
separate IP addresses, if using them. If the user specifies only one option, then the other type of
device (cable modem or host) will not be able to connect with a DHCP server. In addition, if the
cable-modem or host option is used with the same IP address that was previously configured with
this command, the new configuration overwrites the old configuration
This command enables CMs and their attached CPE devices (hosts) to use separate DHCP
servers, so that CMs and hosts receive their IP addresses from separate address pools. The
cable-modem keyword specifies that only UDP DHCP broadcasts from CMs are forwarded to
that particular destination IP address. The host keyword specifies that only UDP broadcasts from
hosts (CPE devices) are forwarded to that particular destination IP address.
Configuring MAC domain IP bundle interfaces

To set an IP bundle interface for mac domain interface instead of setting IP address or cable
helper-address:
343
CASA CMTS
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.
Example:
an existing one:

[no] ip bundle <id>
Where:
<id>
Bundle group id. Valid values are from 1 to 16.
Example:
Set IP bundle 1 to mac domain interface 2:

Set the IP bundle

interface for the
MAC domain.
To remove an IP
bundle interface
from MAC domain,
use the no form of
the command.
Setting the domain sync-interval

To specify the interval between successive sync message transmissions from the Casa CMTS,
use the sync-interval command in MAC domain interface configuration mode. To return the sync
message interval to its default value, use the no form of this command.
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.

an existing one:

[no] sync-interval <msec>
Where:
<msec>
Specifies the interval in milliseconds (ms)

between successive sync message transmissions
from the Casa CMTS. Valid values are from 1 to
200 ms. Default value is 10 ms.
Set the domain

sync-interval.
To return the sync
message interval,
use the no form.
344
CASA CMTS
Example:
Set the interval for the sync message transmissions to 100 ms:
CASA-CMTS(config-if-mac 2)# sync-interval 100
Setting the upstream insertion-interval

Upstream insertion-interval specifies the time interval between consecutive initial ranging slots on
an upstream. It is a MAC domain characteristic. When it is set, it applies to all upstream channels
bond to the MAC domain. To configure the automatic setting and ignore any minimum or
maximum time settings, use the no form of this command.
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.

an existing one:
2
[no] insertion-interval <fixed-intrvl>

Where:
<fixed- intrvl>
Interval between initial ranging slots in

1/100 of second. The valid range is 10 to
200.
Set the upstream

insertion-interval.
To disable upstream
insertion-interval,
use the no form.
Example:
Set the minimum insertion interval to 100 ms:
CASA-CMTS(config-if-mac 2)# insertion-interval 10
345
CASA CMTS
Configuring the MDD interval

To configure the MDD interval:
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.
Example:
an existing one:

mdd interval <num>
Where:
<num>
Configure the MDD

interval.
Interval between two successive MDD messages

in milliseconds. The valid range is 0 to 2000, 0 to
disable mdd.
Example:
Set the minimum insertion interval to 100 ms:
CASA-CMTS(config-if-mac 2)# mdd interval 10
Enabling a domain interface gateway IP address

To enable a gateway IP address on a domain interface:
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

values are 1 to 32.
Example:
an existing one:
346
CASA CMTS
[no] dhcp-giaddr-primary
The command will enable the DHCP discovery messages (CM,
MTA and CPE) to be relayed to the DHCP server with source IP
address of the dhcp-giaddr. The default setting is disabled.
Enable a gateway IP
address on a domain
interface
Example:
CASA-CMTS(config-if-mac 2)# dhcp-giaddr-primary
Enabling a domain interface TFTP proxy

To enable the TFTP proxy on a domain interface in order for the cable modem to get the DOCSIS
configuration file:
Step
1
Command (config)
Purpose
Create new domain

interfaces or enter
an existing one.
Where:
<domain-id>

are 1 to 32.
Example:
an existing one:

[no] tftp-proxy
Example:
CASA-CMTS(config-if-mac 2)#tftp-proxy
Enable the TFTP

proxy on the domain
interface.
Rejecting modem registrations with TFTP enforce

The tftp-enforce command enables the CMTS to reject registration requests from cable modems
on the specific MAC domain. Cable modems must first download their DOCSIS configuration files
from a TFTP server before the modems are allowed to register with the CMTS. The default
setting is disabled.
347
CASA CMTS
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.
Example:
an existing one:

[no] tftp-enforce
Example:
CASA-CMTS(config-if-mac 2)#tftp-enforce
Enable TFTP-enforce
to prevent cable
modems from
registering with the
CMTS until the
DOCSIS configuration
file is downloaded to
the modem via TFTP
server.
Displaying modem registrations that have bypassed TFTP

Th show cable modem tftp-bypass command displays the cable modems that have registered
with the CMTS without using TFTP. When the tftp-enforce setting is disabled (by default), cable
modems are allowed to register with the CMTS and come online without first downloading their
DOCSIS configuration file from a TFTP server.
Step
1
Command (config)
Purpose
show cable modem tftp-bypass
Display cable modems

that have bypassed
TFTP download of the
DOCSIS configuration
file and have
registered with the
CMTS.
Example:
CASA-CMTS(config)# show cable modem tftp-bypass
MAC Address
IP Address
US
DS
MAC
Prim RxPwr Timing Num BPI
Intf
Intf
Status
Sid (dB) Offset CPEs Enb
total cm 0
348
CASA CMTS
Enabling/disabling IP policies on a domain interface

To enable an IP policy on a domain interface:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.
Example:

[no] ip policy route-map <string>
Where:
<string>
Specifies the name of the route map.
Enable an IP policy on a
domain interface.
To disable an IP policy
on a domain interface,
use the no form.
Configuring multicast on MAC domain interfaces

To enable the multicast group membership discovery (mgmd) protocol on a docsis-mac domain
interface (IGMP for IPv4 and MLD for IPv6), perform the following steps: The default setting is
disabled.
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.

2
no mgmd <ipv4 | ipv6> shutdown

Example:
Enable multicast for IPv4 on docsis-mac domain 2:
CASA-CMTS(config-if-mac 2)# no mgmd ipv4
shutdown
Enable the group

membership discovery
(mgmd) protocol on a
docsis-mac domain
interface.
To disable the mgmd
protocol on a docsis-mac
349
CASA CMTS
Disable:
CASA-CMTS(config-if-mac 2)# mgmd ipv4 shutdown
domain interface,
remove the no command
at the beginning of the
command.
Enabling/disabling DHCP authorization on a MAC domain interface

To enable DHCP authorization on MAC Domain to prevent IP address and mac-address
spoofing, use the command dhcp-authorization:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

values are 1 to 32.
Example:

[no] dhcp-authorization
The default setting is enabled.
Example:
CASA-CMTS(config-if-mac 2)# dhcp-authorization
Disable:
CASA-CMTS(config-if-mac 2)# no dhcpauthorization
Enable DHCP
authorization on MAC
domain to prevent IP
address and macaddress spoofing.
To disable DHCP
authorization on a
docsis-mac domain
interface, use the no
form of the command.
Configuring channel bonding on MAC domain interface

To enable the DOCSIS3.0 CM to bond more than one upstream or downstream channel of the
MAC domain:
350
CASA CMTS
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.
Example:

[no] {upstream | downstream } channel bonding
Enable or disable
channel bonding.
Example:
Enable upstream channel bonding:
CASA-CMTS(config-if-mac 2)# upstream channel
bonding
Disable:
CASA-CMTS(config-if-mac 2)# no upstream
channel bonding
Enabling MAC domain multicast DSID forwarding

Enabling muliticast DSID forwarding allows cable modems to filter multicast traffic before
forwarding the traffic to CPE devices. DSIDs uniquely identify multicast streams over a MAC
domain bonding group.
To enable multicast DSID packet forwarding to cable modem CPEs:
Step
1
Command
Purpose
Create new domain

existing one.
Where:
<domain-id>

values are 1 to 32.
Example:
2
[no] multicast-dsid-forward
Example:
Enable or disable
forwarding of multicast
downstream IDs to cable
modem CPE devices.
351
CASA CMTS
CASA-CMTS(config-if-mac 2)# multicast-dsidforward

command to disable
DSID forwarding.
Configuring IP-provisioning-mode on a MAC domain interface

To configure the IP-provisioning-mode for IP addressing schemes on a MAC domain interface:
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>

are 1 to 32.
Example:

ip-provisioning-mode {alternate | dual-stack | ipv4-only |
ipv6-only}
Where:
alternate
Attempt IPV6 provisioning; if IPV6

provisioning fails, then revert to IPV4
provisioning.
dual-stack
Attempt IPV4 and IPV6 provisioning

concurrently with dual IP addressing; if
one or the other fails, then the
successful provisioning remains in
effect.
ipv4-only
IP Version 4 provisioning only; default

setting
ipv6-only
IP Version 6 provisioning only.
Configure IPprovisioning-mode to
select the IP addressing
scheme for a MAC
domain interface.
Example:
Enable dual-stack ip-provisioning-mode on docsis-mac
domain 2:
CASA-CMTS(config-if-mac 2)# ip-provisioningmode dual-stack
352
CASA CMTS
Configuring MAC domain IPv6 router advertisement parameters

Route adverstisements must be enabled when a MAC domain has a cable modem or CPE in
IPv6 mode. The following router-advertisement parameters are supported in Release 6.1.
enable
cur-hop-limit
life-time
link-mtu
managed-flag
max-advertising-interval
min-advertising-interval
other-config-flag
prefix
reachable-time
retransmit-time
To configure the router-advertisement parameters:

Step
1
Command (config)
Purpose
Create new
domain
interfaces or
enter an
existing one.
Where:
<domain-id>
MAC domain number in the range 1 to 32.
Example:
existing one:

[no] router-advertisement enable
[no] router-advertisement prefix suppression
router-advertisement cur-hop-limit
router-advertisement life-time
router-advertisement link-mtu
router-advertisement managed-flag
router-advertisement max-advert-interval
router-advertisement min-advert-interval
router-advertisement other-config-flag
router-advertisement reachable-time
router-advertisement retransmit-timer
Where:
enable
Configure
routeradvertisement
parameters.
Specifies the default router-advertisement setting.

Use the no form of the command to disable IPv6
router advertisements.
353
CASA CMTS
prefix
suppression
Removes the IPv6 prefix in router advertisement

messages. Suppressed prefixes are not advertised.
Prefixes are comprised of a portion of the IPv6
address and the prefix length, such as
10FE:5506:8246: 6403:/64.
cur-hop-limit
Specifies the maximum number of hops placed in

the IP header of the router-advertisement message
for outbound packets. The default setting is 64.
Enter a value in the range 0 to 255. 0 indicates not
specified.
life-time
Specifies the value of the default router lifetime field

in router-advertisement messages. The default
setting is 3*max-advert-interval setting. Specify a
number in the range 4 to 9000 seconds.
link-mtu
Specific the maximum transmission unit (MTU) size

for router-advertisement messages over the current
docsis-mac interface. The default setting is 1500
bytes. Specify a number in the range 512 to 1500.
managedflag
Specifies the state of the managed address

configuration flag, either true or false. Including the
flag in router-advertisement messages informs other
routers to use stateless address autoconfiguration,
as defined in RFC 4941, or over DHCPv6.
The default setting is true. Specify false to unset the
flag.
max-advertinterval
Specifies the maximum time in seconds between

transmissions of multicast router advertisement
messages over the docsis-mac interface.
The default setting is 600 seconds.
Specify a number in the ranage 4 to 1800 seconds.
min-advertinterval
Specifies the minimum time in seconds between

transmissions of multicast router advertisement
messages over the docsis-mac interface.
The default setting is 200 seconds.
Specify a number in the ranage 3 to 1350 seconds.
other-configflag
Specifies the true or false setting placed in the

other configuration flag field in the router
advertisement message. Including the flag in
router-advertisement messages informs other
routers to use administered stateful address
autoconfiguration, such as DHCPv6.
The default setting is true. Specify false to unset the
flag.
reachabletime
Specifies the time in milliseconds placed in the

reachable time field of the router advertisement
message. The setting detects unreachable
neighbor routers at expiration.
The default setting is 0 (unspecified). Specify a time
354
CASA CMTS
in the range 0 to 3600000 milliseconds (one hour).

retransmittimer
Specifies the time in milliseconds placed in the

retransmit timer field of the router advertisement
message. The value indicates the time interval to
elapse between router advertisement
retransmissions.
The default setting is 0. Specify a value in the
range 0 to 65535 milliseconds.
Examples:
CASA-CMTS(config-if-mac 1)# router-advertisement
enable
CASA-CMTS(config-if-mac 1)# router-advertisement
other-config-flag false
Displaying the router advertisement table

To display the IPv6 route advertisement table:
Step Command
1
show router-advertisement
Purpose
Display the IPv6 router
advertisement table.
Example:
CASA-CMTS# show router-advertisement
router advert table, domain=22
SendAdverts=1
MaxInterval=600
MinInterval=200
ManagedFlag=1
OtherConfigFlag=1
LinkMTU=1500
ReachableTime=0
RetransmitTime=0
CurrHopLimit=64
DefaultLifetime=1800
RowStatus=1
Prefix_flag = 1
355
CASA CMTS
Configuring BPI+ on a MAC domain interface

To configure KEK and TEK life-time on MAC domain Interfaces.
Step
1
Command (config)
Purpose
Create new domain

existing one.
Where:
<domain-id>
MAC domain number in the range 1 to

32.
Example:

privacy {kek | tek } life-time <length>
Where:
kek
Configure BPI+ on a
MAC domain interface.
Key encryption keys.
tek
Traffic encryption keys.
<length>
Length of the key encryption life-time in

seconds. Valid range: 1 to 6048000 for kek
and 1 to 604800 for tek.
Example:
Set tek life-time to be 300 on docsis-mac domain 1:
CASA-CMTS(config-if-mac 1)# privacy tek lifetime 300
Configuring cable modem trap generation and interval

The cm trap command enables CMTS trap generation anytime there are changes to cable
modem status over a DOCSIS-MAC interface, such as going from online status to offline status.
Optionally, a time interval may be specified to control the minimum time to elapse between CMTS
trap notifications.
To configure the cable modem trap and the trap interval on a MAC domain interface:
Purpose
1

Where:
<domain-id>
Create new domain

existing one.

are 1 to 32.
356
CASA CMTS
Example:

cm trap
cm trap interval <seconds>
Where :
<seconds>
Specifies the time interval in the range 1 to

86400 seconds.
Enables cable modem

trap notification and sets
the minimum time
interval between CMTS
notifications in seconds.
Example:
CASA-CMTS(config-if-mac 2)# cm trap
CASA-CMTS(config-if-mac 2)# cm trap interval
20000
Displaying the MAC domain interface configuration

To display the MAC domain configuration:
Step
1
Command
Purpose
show interface docsis-mac [<num>]
Display the MAC domain

configuration.
Example:
CASA-CMTS# show interface docsis-mac 8

To display the MAC domain statistics:
Step
1
Command
Purpose
show interface docsis-mac stat
Display the MAC domain

Statistics
Example:
See example below.
Displaying MAC domain statistics

To show MAC domain statistics:
Step
1
Command
Purpose
show interface docsis-mac stat

Example:
CASA-CMTS# show interface docsis-mac stat
Interface docsis-mac 1 statistics
357
CASA CMTS
Ifindex:
Administrated status:
Operation status:
Mac address:
DSA Request
:
DSA Response
:
DSA Acknowledgements :
DSA Success
:
DsA Fail
:
DSC Request
:
DSC Response
:
DSC Acknowledgements :
DSC Success
:
DSC Fail
:
DSD Request
:
DSD Response
:
DSD Success
:
DSD Fail
:
DCC Request
:
DCC Response
:
DCC Acknowledgements :
DCC Success
:
DCC Fail
:
DCC RSP Depart
:
DCC RSP Arrive
:
DBC Request
:
DBC Response
:
DBC Acknowledgements :
DBC Success
:
DBC Fail
:
DBC Partial Service :
77
UP
UP
0017.1000.2647
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
2/ups;
0/ups;
0/ups;
0/ups;
1/ups;
1/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ups;
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
1/ds
0/ds
1/ds
1/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
0/ds
Configuring service groups

A service group is a collection of upstream and downstream channels that is allocated to a single
fiber node that supports a given service area.
This section describes the service group management commands. It covers the following:
Creating a new service group
Entering service group configuration mode
Ending a service group configuration session
Removing a service group
Removing upstream interfaces
358
CASA CMTS
Removing downstream interfaces
Displaying configured service groups
Creating a new service group

To create a new service group:
Step
1
Command
Purpose
[no] service group <string>
Create or enter a
new service group
Where:
<string>
Service group name, up to 16 characters. Up

to 160 service groups are supported.
Example:
Create a new service group 2:
CASA-CMTS(config)# service group 2
CASA-CMTS(conf-svc-grp 2)# end
CASA-CMTS(config)#
To remove a service
group, use the no
form of the
command.
Remove the service group:

CASA-CMTS(config)# no service group 2
CASA-CMTS(conf-svc-grp 2)# end
CASA-CMTS(config)#

To bind an upstream interface to a service group:
Step
1
Command (config)
Where:
<string>
Service group name containing up to 16

characters. Up to 160 service groups are
supported.
Example:
[no] upstream [<X/Y.Z> | <X/Y>]
Where:
<X>
Module number.
<Y>
Port number.
<Z>
Physical channel number, RTN3 upstream module

supports two physical channels for each port.
Purpose
Create or enter a
new service group
To remove a service
group, use the no
form.
Bind upstream
interfaces.
To remove upstream
interface binding,
use the no form of
the command.
359
CASA CMTS
Example:
Bind upstream 1/1.0 to service group 2:
CASA-CMTS(conf-svc-grp 2)# upstream 1/1.0
Remove the binding:
CASA-CMTS(conf-svc-grp 2)# no upstream 1/1.0

To bind a downstream interface to a service group:
Step
1
Command (config)
Purpose
Create or enter a
new service group
Where:
<string>
Service group name containing up to 16

characters. Up to 160 service groups are
supported.
Example:
[no] qam <X/Y/Z>
Where:
<X>
Module number.
<Y>
Port number.
<Z>
To remove a service
group, use the no
form of the
command.
Bind downstream
interfaces.
To remove
downstream
interface bindings,
use the no form of
the command.
Example:
Bind downstream 0/2/1 to service group 2:
CASA-CMTS(conf-svc-grp 2)# qam 0/2/1
Remove the binding:
CASA-CMTS(conf-svc-grp 2)# no qam 0/2/1
Displaying service groups

To display the configured service groups:
Step
1
Command (config)
Purpose
show service group [<string>]
Display configured
service groups.
Where:
360
CASA CMTS
<string>
Service group name entered as a string.
Example:
Display service group 1:
service group 1
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
upstream 3/0
upstream 3/1
upstream 3/2
upstream 3/3
Displaying MAC domain downstream service groups (Release 5.4)

To display the downstream service groups:
Step
1
Command
Purpose
show md-ds-sg {mac-domain} [service-group]
Display the
downstream
service groups.
Where:
mac-domain
service group
MAC domain number.

Service group name.
Example:
CASA-CMTS(config)#show md-ds-sg
docsis-mac 1 service-group 1
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
qam 0/2/0
qam 0/2/1
qam 0/2/2
qam 0/2/3
Displaying specific MAC domain downstream service groups

To display a specific downstream service group associated with a MAC domain:
Step
1
Command
Purpose
show md-ds-sg mac <num=1:32> [service-group <string>]
Display a specific
MAC domain
downstream
service group.
Where:
361
CASA CMTS
mac:<num=1:16>
Specify a MAC domain in the

range 1 to 32.
service group <string>
To specify which service group.
Example:
CASA-CMTS#show md-ds-sg mac 1 service-group 1
qam 0/2/0
qam 0/2/1
qam 0/2/2
qam 0/2/3
Displaying a specific downstream service group

To display a named downstream service group:
Step
1
Command
Purpose
show md-ds-sg service-group <string>
Display a specific
downstream service
group.
Where:
<string>
Specifies the service group.
Example:
CASA-CMTS#show md-ds-sg service-group 1

qam 0/2/0
qam 0/2/1
qam 0/2/2
qam 0/2/3
Displaying MAC domain upstream service group information

To display MAC domain service group information:
Step
1
Command
Purpose
show md-us-sg [mac <num=1:32>][service-group

<string>]
Display MAC domain

upstream service group
information.
Where:
<mac>
servicegroup

The named service group string.
Example:
CASA-CMTS#show md-us-sg mac 1 service-group 1

upstream 1/4/0
362
CASA CMTS
upstream 1/5/0
upstream 1/6/0
upstream 1/7/0
Configuring bonding groups

A bonding group defines a fixed collection of upstream or downstream channels under a given
MAC domain and is specified by bonding-group ID.
A bonding group automatically forms when a MAC domain and service group is configured. A
bonding group will form for each unique intersection of the service group channels and the MAC
domain channels.
This section describes the commands for bonding-group management. It covers the following:
Creating a new downstream/upstream bonding group
Entering downstream/upstream bonding-group configuration mode
Removing a downstream/upstream bonding group
Binding downstream/upstream interfaces to a bonding group
Removing downstream/upstream interfaces from a bonding group
Displaying configured bonding groups
Creating new downstream/upstream bonding groups

To create a new downstream bonding group:
Step
1
Command (config)
Purpose
[no] bonding-group downstream mac-domain <mac_id>

group-id <group_id>
Create or enter a new

downstream bonding
group.
Where:
<mac_id>
<grp_id>
MAC domain ID in the range 1 to 32.

Bonding group ID in the range 1-65535.
To remove the bonding

group, use the no form
of the command.
Example:
Create a new downstream bonding-group with mac-domain 1
and group ID 1:
CASA-CMTS(config)# bonding-group downstream
mac-domain 1 group-id 1
CASA-CMTS(bond-ds-mac-1-group-1)#
Remove the group:
CASA-CMTS(config)# no bonding-group downstream
363
CASA CMTS
To create a new upstream bonding group:

Step
1
Command (config)
Purpose
[no] bonding-group upstream mac-domain <mac_id>

group-id <grp_id>

upstream bonding group
Where:
<mac_id>
To remove the bonding

group, use the no form
of the command.
<grp_id>

Bonding group ID in the range 1-65535.
Example:
and group ID 1:
CASA-CMTS(config)# bonding-group upstream macdomain 1 group-id 1
Remove the group:
CASA-CMTS(config)# no bonding-group upstream
Binding upstream interfaces to a bonding group

To bind an upstream interface to a bonding group:
Step
1
Command (config)
Purpose
[no] bonding-group upstream mac-domain <mac_id>

group-id <group_id>

upstream bonding group.
Where:
<md_id>
<grp_id>

Bonding group ID in the range 1 to
65535
Example:
Create a new upstream bonding-group with mac-domain 1
and group ID 1:
2
[no] upstream <X/Y.C/Z>

Where:
<X>
Module number.
Bind upstream interfaces

to a bonding group.
To remove upstream
interface binding from a
364
CASA CMTS
<Y>
Port number.
<C>
Physical channel number, RTN3 upstream line

card supports up to 2 physical channels.
<Z>
Logical channel number. RTN3 upstream line

card supports up to 2 logical channels.
bonding group, use the

no form of the
command.
Example:
Bind upstream 1/1.0/0 to bonding-group 1:
CASA-CMTS(bond-us-mac-1group-1)# upstream
1/1.0/0
Remove the binding:
CASA-CMTS(bond-us-mac-1group-1)# no upstream
1/1.0/0
Binding downstream interfaces to a bonding group

To bind a downstream interface to a bonding group:
Step
1
Command (config)
Purpose
[no] bonding-group downstream mac-domain <mac_id>

group-id <group_id>

downstream bonding
group.
Where:
<md_id>
<grp_id>

Bonding group ID in the range 1 to
65535.
Example:
and group ID 1:
CASA-CMTS(config)# bonding-group downstream

[no] qam <X/Y/Z>
Where:
Module number.
<X>
<Y>
Port number.
<Z>
Example:
Bind downstream 0/2/1 to binding-group 2:
CASA-CMTS(bond-ds-mac-1-group-1)# qam 0/2/1
Bind a downstream
interface to a bonding
group.
To remove a bound
downstream interface
from a bonding group,
use the no form.
Remove the binging:

CASA-CMTS(bond-ds-mac-1-group-1)# no qam 0/2/1
365
CASA CMTS
Displaying bonding groups

To display bonding groups:
Step
1
Command
Purpose
show bonding-group [mac-domain <mac-id>]
Display a bonding group.
Where:
<mac-id>
Specifies the MAC domain identifier.
Example:
Display all the bonding groups on domain interface 1:
CASA-CMTS# show bonding-group mac-domain
bonding-group downstream mac-domain 1 group-id
1
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
bonding-group upstream mac-domain 1 group-id 1
upstream 3/0/0
upstream 3/1/0
upstream 3/2/0
upstream 3/3/0
Setting up the receive channel configuration

To set up receive channel configuration (RCC) for downstream channel bonding:
Step
1
Command (config)
Purpose
[no] rcc mac <mac_id> rcp-id <rcp_id> <cfg_id>
Set up the receive

channel configuration
(RCC) for downstream
channel bonding to the
CM.
Where:
<mac_id>
<rcp_id>
<cfg_id>

Receive channel profile ID in the format
xx:xx:xx:xx:xx
rcc cfg id in the range 1 to 4294967295.
To remove a receive
channel, use the no form
of the command.
Example:
Set up rcc 1 with mac-domain 1:
CASA-CMTS(config)# rcc mac 1 rcp-id
10:00:00:00:01 1
CASA-CMTS(conf-mac 1 rcc 1)#
366
CASA CMTS
Assigning a receive module

To assign a receive module to receive channel configuration:
Step
1
Command (config)
Purpose
Set up receive channel

configuration (RCC) for
downstream channel
bonding to the CM.
Where:
<mac_id>
MAC domain ID. Value Range: 1-32
<rcp_id>
Receive channel profile ID in the format

xx:xx:xx:xx:xx
<cfg_id>
rcc cfg id. Value Range: 1-4294967295.
Example:

10:00:00:00:01 1
rm <rm_id> frequency <freq> connect <connect_id>
Where:
<rm_id>
Assign a receive module

to receive channel
configuration.
Receive module ID in the range 1 to

255.
<freq>
Downstream channel frequency value in

<connect_id>
RM connectivity ID in the range 0 to 255.

0 means that there is no other receive
module connected to this receive
module.
Example:
Assign receive module 1 at frequency 549000000 to rcc 1:
CASA-CMTS(conf-mac 1 rcc 1)# rm 1 frequency
549000000 connect 0
Assigning a receive channel

To assign a receive channel to receive channel configuration:
Step
1
Command (config)
Purpose
Set up receive channel

configuration (RCC) for
downstream channel
bonding to the CM.
Where:
<mac_id>
<rcp_id>
Receive channel profile id, in form of
367
CASA CMTS
xx:xx:xx:xx:xx
<cfg_id>
rcc cfg id. Value Range: 1-4294967295.
Example:

10:00:00:00:01 1
rc <rc_id> downstream <downstream_id>
primary|secondary connect <rm_id>
Where:
<rc_id>
Assign a receive channel

to receive channel
configuration.
Receive channel ID in the range 1 to

255.
<downstream_id>
Downstream channel ID in MAC

domain in the range 0-255. 0 is used
to describe a downstream channel
with abnormal status.
primary
Enable primary-capable downstream

channel
secondary:
Disable primary-capable
downstream channel
<rm_id>
rm connectivity ID in the range 0 to

255.
Example:
Assign downstream 1 of rm 1 to rcc 1 as a primary channel:
CASA-CMTS(conf-mac 1 rcc 1)# rc 1 downstream 1
primary connect 1
Displaying the receive channel configuration

To display the receive channel configuration (RCC):
Step
1
Command
Purpose
show rcc [mac <mac_id> [rcp-id <rcp_id> <cfg_id>]]
Display the receive

channel configuration.
Where:
<mac_id>
<rcp_id>
Receive channel profile id, in form of

xx:xx:xx:xx:xx
<cfg_id>
rcc cfg id in the range 1 to 4294967295.
Example:
Show the RCC on MAC domain 1:
368
CASA CMTS
CASA-CMTS# show rcc mac 1

rcc mac 1 rcp-id 10:00:00:00:01 1
vendor-specific spacing6
rcc-desc spacing=6;
rc 1 downstream 1 primary connect 1
rm 1 frequency 549000000 connect 0
Configuring modulation profiles

This section lists the detailed parameters of predefined profiles, and the commands for
configuring modulation profiles.
Parameters for predefined modulation profile 1 to 5

Configuring modulation profiles
Configuring TDMA burst types
Configuring ATDMA burst types
Configuring MTDMA burst types
Configuring SCDMA burst types
Retrieving and removing configured modulation profiles
Predefined modulation-profile 1 parameters

This TDMA profile uses QPSK for all burst types. It can be used for TDMA upstream channels.
The following table shows all attributes.
iuc
modulation-type
diff-encoding
preamble-len
fec-tbytes
fec-kbytes
scrambler-seed
max-burst-size
guard-time
code-word-len
scrambler-mode
interleave-depth
interleave-block
preamble-type
request
qpsk
off
64
0
16
338
0
16
fixed
on
-
initial
qpsk
off
640
5
34
338
0
48
fixed
on
-
station
qpsk
off
384
5
34
338
0
48
fixed
on
-
short
qpsk
off
84
6
75
338
13
8
fixed
on
-
long
qpsk
off
96
8
220
338
0
8
fixed
on
-
a-short
-
a-long
-
369
CASA CMTS

This TDMA profile is similar to the above profile, except that it uses 16qam for short and long data
burst types. It can be used for TDMA upstream channels. The following table shows all
attributes.
iuc
modulation-type
diff-encoding
preamble-len
fec-tbytes
fec-kbytes
scrambler-seed
max-burst-size
guard-time
code-word-len
scrambler-mode
interleave-depth
interleave-block
preamble-type
request
qpsk
off
64
0
16
338
0
16
fixed
on
-
initial
qpsk
off
640
5
34
338
0
48
fixed
on
-
station
qpsk
off
384
5
34
338
0
48
Fixed
on
-
short
16qam
off
168
6
75
338
7
8
fixed
on
-
long
16qam
off
192
8
220
338
0
8
fixed
on
-
a-short
-
a-long
-

Profile 3 is an ATDMA type profile. It uses QPSK for management bursts, and 64qam for data
traffic. The following table shows all attributes.
iuc
modulation-type
diff-encoding
preamble-len
fec-tbytes
fec-kbytes
scrambler-seed
max-burst-size
guard-time
code-word-len
scrambler-mode
interleave-depth
interleave-block
preamble-type
request
qpsk
off
64
0
16
338
0
16
fixed
on
1
1536
qpsk0
initial
qpsk
off
640
5
34
338
0
48
fixed
on
1
1536
qpsk0
station
qpsk
off
384
5
34
338
0
48
fixed
on
1
1536
qpsk0
short
-
long
-
a-short
64qam
off
104
12
75
338
6
8
shortened
on
1
1536
qpsk1
a-long
64qam
off
104
16
220
338
0
8
shortened
on
1
1536
qpsk1

Profile 4 is an mtdma type profile. It uses qpsk for management bursts, 16qam for tdma data
traffic, and 64qam for atdma data traffic. The following table shows all attributes.
370
CASA CMTS
iuc
modulationtype
diff-encoding
preamble-len
fec-tbytes
fec-kbytes
scrambler-seed
max-burst-size
guard-time
code-word-len
scramblermode
interleavedepth
interleaveblock
preamble-type
request
qpsk
initial
qpsk
station
qpsk
short
16qam
long
16qam
a-short
64qam
a-long
64qam
off
64
0
16
338
0
16
fixed
on
off
640
5
34
338
0
48
fixed
on
off
384
5
34
338
0
48
fixed
on
off
168
6
75
338
7
8
fixed
on
off
192
8
220
338
0
8
shortened
on
off
104
12
75
338
6
8
shortened
on
off
104
16
220
338
0
8
shortened
on
1536
1536
1536
1536
1536
1536
1536
qpsk0
qpsk0
qpsk0
qpsk1
qpsk1
qpsk1
qpsk1

Profile 5 is a SCDMA type profile. It uses qpsk for management bursts, 128qam for scdma data
traffic. The following table shows all attributes.
iuc
modulation-type
diff-encoding
preamble-len
fec-tbytes
fec-kbytes
scrambler-seed
max-burst-size
guard-time
code-word-len
scrambler-mode
interleave-depth
interleave-block
Preamble-type
Interleave-step
spreader
subframe-code
TCM-encode
request
qpsk
off
64
0
16
338
1
0
fixed
on
0
0
qpsk0
1
on
2
off
initial
qpsk
off
640
5
34
338
0
0
fixed
on
0
0
qpsk0
1
off
2
off
station
qpsk
off
512
5
34
338
0
0
fixed
on
0
0
qpsk0
1
off
2
off
short
-
long
-
a-short
128qam
off
64
5
33
338
12
0
shortened
on
0
0
qpsk0
1
on
128
on
a-long
128qam
off
64
10
156
338
0
0
shortened
on
0
0
qpsk0
1
on
128
on
371
CASA CMTS
Configuring a modulation profile

Modulation profile modifications cause changes to the physical layer. Because changing physical
layer characteristics affects Casa CMTS performance and function, this task should be reserved
for expert users who have a thorough understanding of DOCSIS systems and how each
parameter affects network performance.
NOTE: Casa strongly recommends that users create modulation profiles automatically with the
provided tools. Modulation profiles created this way are more likely to work effectively. Of course,
users are free to modify any values in an auto-created profile based on field conditions. Automatic
creation of modulation profiles are described in the following subsections.
Configuring TDMA burst types

The Casa CMTS provides two ways to configure a TDMA-type modulation profile: auto mode and
manual mode.
Auto-mode TDMA-type modulation profile configuration

In auto mode, the user only specifies the modulation type, either qpsk or 16qam; the rest of the
attributes will be automatically set to be the same as predefined modulation-profile 1 or 2.
When qpsk is specified, the profile is the same as predefined modulation-profile 1. When 16qam
is specified, the profile is the same as predefined modulation-profile 2.
Step
1
Command (config)
Purpose
modulation-profile <profile> tdma [<mod-type>]
Automatically
configure the
TDMA-type
modulation
profile.
Where:
<profile>
<mod-type>
Profile ID in the range 6 to 64.

Optional. Modulation type is qpsk or 16qam.
Example:
CASA-CMTS(config)#modulation profile 22 tdma qpsk
CASA-CMTS(config-mod-prof)#
Manual mode TDMA-type modulation profile configuration

To manually specify the individual bursts, enter a line with all parameters for each upstream burst
type. Then repeat this command for each burst type, which also must be fully specified.
Step
1
Command (config)
Purpose
modulation-profile <profile>
Select the profile

to configure.
Where:
<profile>
372
CASA CMTS
Example:
CASA-CMTS(config)#modulation-profile 22
<iuc> tdma <mod-type> <diff-encoding> <preamble-len> <fect> <fec-k> <scramble-seed> <bust-size> <guard-time> <cwlen> <scramble-mode>
Specify the
profile parameter
values.
Where:
<iuc>
<mod-type>
<diff-encoding>
<preamble-len>
<fec-t>
<fec-k>
<scrambler-seed>
<max-burst-size>
<guard-time>
<code-word-len>
<scrambler-mode>
request, initial, station, short,

long
qpsk,16qam
on, off
1-1024 (bits)
0-16
0, 16-253
15-bit seed (0-32767)
0-255 (mini-slots)
4-255 (modulation intervals)
fixed, shortened
On, off
Example:
See below.
Configuring modulation-profile 6
CASA-CMTS# config
CASA-CMTS(config)# modulation-profile 6
CASA-CMTS(config-mod-prof)# request tdma qpsk off 64 0 16 338 1 8 fixed on
CASA-CMTS(config-mod-prof)# initial tdma qpsk off 128 5 34 338 0 48 fixed on
CASA-CMTS(config-mod-prof)# station tdma qpsk off 128 5 34 338 0 48 fixed on
CASA-CMTS(config-mod-prof)# short tdma qpsk off 72 6 75 338 6 8 fixed on
CASA-CMTS(config-mod-prof)# long tdma qpsk off 80 8 220 338 0 8 fixed on
CASA-CMTS(config-mod-prof)# end
CASA-CMTS(config)#
The modulation-profile 6 example uses the following parameter values:

<iuc>
<mod-type>
<diff-encoding>
<preamble-len>
<fec-t>
<fec-k>
<scrambler-seed>
<max-burst-size>
<guard-time>
<code-word-len>
<scrambler-mode>
request
qpsk
off
64
0
16
338
1
8
fixed
on
initial
qpsk
off
128
5
34
338
0
48
fixed
on
station
qpsk
off
128
5
34
338
0
48
fixed
on
short
qpsk
off
72
6
75
338
6
8
fixed
on
long
qpsk
off
80
8
220
338
0
8
fixed
on
373
CASA CMTS
Configuring ATDMA burst types

There are two ways to configure an atdma-type modulation profile: auto mode and manual mode.
Auto-mode ATDMA-type modulation profile configuration

In auto mode, the user only specifies the modulation type; the rest of the attributes will be
automatically set to be the same as predefined modulation-profile 3.
Step
1
Command (config)
Purpose
modulation-profile <profile> atdma [<mod-type>]
Automatically
configure the
ATDMA-type
modulation
profile.
Where:
<profile>
<mod-type>

Modulation type: qpsk, 16qam, 8qam,
32qam, or 64qam. If omitted, the profile
is the same as predefined modulationprofile 3.
Example:
CASA-CMTS(config)#modulation profile 22 atdma qpsk
Note: The specified modulation type applies only to the burst types a-short and a-long.
Manual mode ATDMA-type modulation profile configuration

Step
1
Command (config)
Purpose
Select the profile

to configure
Where:
<profile>
Example:
CASA-CMTS(config)#modulation profile 22
<iuc> atdma <mod-type> <diff-encoding> <preamble-len>
<fec-t> <fec-k> <scramble-seed> <bust-size> <guard-time>
<cw-len> <scramble-mode> <intlv-depth> <intlv-block>
<preamble-type>
Specify the
profile parameter
values.
Where:
374
CASA CMTS
<iuc>
<mod-type>
<diff-encoding>
<preamble-len>
<fec-t> = T
<fec-k> = k
<scrambler-seed>
<max-burst-size>
<guard-time>
<code-word-len>
<scrambler-mode>
<intlv-depth>
<intlv-block>
<preamble-type>
Example:
See below.
request, initial, station, a-short, a-long

qpsk,16qam, 8qam, 32qam, 64qam
on, off
1-1536 (bits)
0-16
0, 16-253
15-bit seed (0-32767)
0-255 (mini-slots)
fixed, shortened
on, off
0 to [2048/(k+2T)]
2*(k+2T) to 2048
qpsk0, qpsk1
Configure modulation-profile 7
CASA-CMTS# config
CASA-CMTS(config-mod-prof)# request atdma qpsk
1536 qpsk0
CASA-CMTS(config-mod-prof)# initial atdma qpsk
1536 qpsk0
CASA-CMTS(config-mod-prof)# station atdma qpsk
1536 qpsk0
CASA-CMTS(config-mod-prof)# a-shot atdma 16qam
1536 qpsk0
CASA-CMTS(config-mod-prof)# a-long atdma 16qam
1536 qpsk0
CASA-CMTS(config)#
off 64 0 16 338 1 8 fixed on 1

off 128 5 34 338 0 48 fixed on 1
off 128 5 34 338 0 48 fixed on 1
off 72 6 75 338 6 8 fixed on 1
off 80 8 220 338 0 8 fixed on 1
The modulation-profile 7 uses the following parameter values:

<iuc>
<mod-type>
<diff-encoding>
<preamble-len>
<fec-t> = T
<fec-k> = k
<scrambler-seed>
<max-burst-size>
<guard-time>
<code-word-len>
<scrambler-mode>
<intlv-depth>
<intlv-block>
<preamble-type>
Request
Qpsk
Off
64
0
16
338
1
8
Fixed
On
1
1536
qpsk0
initial
qpsk
off
128
5
34
338
0
48
fixed
on
1
1536
qpsk0
station
qpsk
off
128
5
34
338
0
48
fixed
on
1
1536
qpsk0
a-short
16qam
off
72
6
75
338
6
8
fixed
on
1
1536
qpsk0
a-long
16qam
off
80
8
220
338
0
8
fixed
on
1
1536
qpsk0
375
CASA CMTS
Configuring MTDMA burst types

There are two ways to configure an mtdma-type modulation profile: auto mode and manual mode.
Note: MTDMA does not support the 6.4MHz US channel width. TDMA supports DOCSIS 1.0/1.1
with a channel width limit of 3.2MHz. If you attempt to set a US channel that has a channel width
of 6.4.MHz to the MTDMA profile, you will receive an error message notifying you that there is a
conflict between the channel width and the modulation profile. Use the auto-mode ATDMA-type
modulation profile configuration to specify the modulation type only; the remaining attributes will
be automatically set to those predefined in modulation-profile 3.
Auto-mode MTDMA-type modulation profile configuration

In auto mode, the user only specifies the modulation type; the rest of the attributes will be
automatically set to be the same as the predefined modulation-profile 4.
Step
1
Command (config)
Purpose
modulation-profile <profile> mtdma [<mod-type>]
Automatically
configure the
MTDMA-type
modulation
profile.
Where:
<profile>
<mod-type>

32qam, or 64qam. If omitted, the profile
is the same as predefined modulationprofile 4.
Example:
CASA-CMTS(config)#modulation-profile 22 mtdma qpsk
Note: The specified modulation type applies to the profile in following way:
Specified
mod-type
qpsk
8qam
16qam
32qam
64qam
short
qpsk
16qam
16qam
16qam
16qam
long
qpsk
16qam
16qam
16qam
16qam
Burst Type
a-short
qpsk
8qam
16qam
32qam
64qam
a-long
qpsk
8qam
16qam
32qam
64qam
Manual mode MTDMA-type modulation profile configuration

376
CASA CMTS
Step
1
Command (config)
Purpose
Select the profile

to configure.
Where:
<profile>
Example:
CASA-CMTS(config)#modulation-profile 22
<iuc> mtdma <mod-type> <diff-encoding> <preamble-len>
<fec-t> <fec-k> <scramble-seed> <bust-size> <guard-time>
<cw-len> <scramble-mode> <intlv-depth> <intlv-block>
<preamble-type>
Specify the
profile parameter
values.
Where:
<iuc>
<mod-type>
<diff-encoding>
<preamble-len>
<fec-t> = T
<fec-k> = k
<scrambler-seed>
<max-burst-size>
<guard-time>
<code-word-len>
<scrambler-mode>
<intlv-depth>
<intlv-block>
<preamble-type>
request, initial, station, a-short, a-long

qpsk,16qam, 8qam, 32qam, 64qam
on, off
1-1536 (bits)
0-16
0, 16-253
15-bit seed
0-255 (mini-slots)
fixed, shortened
on, off
0 to [2048/(k+2T)]
2*(k+2T) to 2048
qpsk0, qpsk1
Example:
See below.
Configuring modulation-profile 8
CASA-CMTS# config
CASA-CMTS(config-mod-prof)# request mtdma qpsk off 64 0 16 338 1 8 fixed on 1
1536 qpsk0
CASA-CMTS(config-mod-prof)# initial mtdma qpsk off 128 5 34 338 0 48 fixed on 1
1536 qpsk0
CASA-CMTS(config-mod-prof)# station mtdma qpsk off 128 5 34 338 0 48 fixed on 1
1536 qpsk0
CASA-CMTS(config-mod-prof)# shot mtdma 16qam off 72 6 75 338 6 8 fixed on 1
1536 qpsk0
CASA-CMTS(config-mod-prof)# long mtdma 16qam off 80 8 220 338 0 8 fixed on 1
1536 qpsk0
CASA-CMTS(config-mod-prof)# a-shot mtdma 16qam off 72 6 75 338 6 8 fixed on 1
1536 qpsk0
CASA-CMTS(config-mod-prof)# a-long mtdma 16qam off 80 8 220 338 0 8 fixed on 1
1536 qpsk0
377
CASA CMTS
CASA-CMTS(config)#
The modulation-profile 8 Example: uses the following parameter values:

<iuc>
request
initial
station
short
long
a-short
a-long
<mod-type>
qpsk
qpsk
qpsk
16qam
16qam
16qam
16qam
<diff-encoding>
off
off
off
off
off
off
Off
<preamble-len>
64
128
128
72
80
72
80
<fec-t> = T
<fec-k> = k
16
34
34
75
220
75
220
<scrambler-seed>
338
338
338
338
338
338
338
<max-burst-size>
<guard-time>
48
48
<code-word-len>
fixed
fixed
fixed
fixed
fixed
fixed
Fixed
<scrambler-mode>
on
on
on
on
on
on
On
<intlv-depth>
<intlv-block>
1536
1536
1536
1536
1536
1536
1536
<preamble-type>
qpsk0
qpsk0
qpsk0
qpsk0
qpsk0
qpsk0
qpsk0
Configuring SCDMA burst types

To configure a scdma-type modulation profile, the user only specifies the modulation type, the
rest of the attributes will be automatically set to be the same as predefined modulation-profile 5.
Step
1
Command (config)
Purpose
modulation-profile <profile> scdma [<mod-type>]
Automatically
configure the
SCDMA-type
modulation
profile.
Where:
<profile>
<mod-type>

32qam, 64qam or 128qam. If omitted,
the profile is the same as predefined
modulation-profile 5.
Example:
CASA-CMTS(config)#modulation-profile 22 scdma
qpsk
Note: The specified modulation type applies only to the burst types a-short and a-long.
378
CASA CMTS
Retrieving configured modulation profiles

To retrieve the names of configured modulation profiles:
Step
1
Command (config)
Purpose
show modulation-profile [<profile>]
Display the
names and
details of one or
all configured
modulation
profiles.
Where:
[<profile>]
ID of configured modulation profile in the

range 1 to 64. Omitting the ID displays all
configured profiles. Profiles 1 to 5 are
default profiles.
Example:
See below.
Example: show modulation-profile, all profiles

CASA-CMTS# config
CASA-CMTS(config)# show modulation-profile
modulation-profile 1
request tdma qpsk off 64 0 16 338 0 16 fixed on
initial tdma qpsk off 640 5 34 338 0 48 fixed on
station tdma qpsk off 384 5 34 338 0 48 fixed on
short tdma qpsk off 84 6 75 338 13 8 shortened on
long tdma qpsk off 96 8 220 338 0 8 shortened on
short tdma 16qam off 168 6 75 338 7 8 shortened on
long tdma 16qam off 192 8 220 338 0 8 shortened on
request atdma qpsk off 64 0 16 338 0 16 fixed on 1 1536 qpsk0
initial atdma qpsk off 640 5 34 338 0 48 fixed on 1 1536 qpsk0
station atdma qpsk off 384 5 34 338 0 48 fixed on 1 1536 qpsk0
a-short atdma 64qam off 104 12 75 338 6 8 shortened on 1 1536 qpsk1
a-long atdma 64qam off 104 16 220 338 0 8 shortened on 1 1536 qpsk1
request mtdma qpsk off 64 0 16 338 0 16 fixed on 1 1536 qpsk0
initial mtdma qpsk off 640 5 34 338 0 48 fixed on 1 1536 qpsk0
station mtdma qpsk off 384 5 34 338 0 48 fixed on 1 1536 qpsk0
short mtdma 16qam off 168 6 75 338 7 8 shortened on 1 1536 qpsk1
long mtdma 16qam off 192 8 220 338 0 8 shortened on 1 1536 qpsk1
a-short mtdma 64qam off 104 12 75 338 6 8 shortened on 1 1536 qpsk1
a-long mtdma 64qam off 104 16 220 338 0 8 shortened on 1 1536 qpsk1
request scdma qpsk off 64 0 16 338 1 0 fixed on qpsk0 on 2 1
initial scdma qpsk off 640 5 34 338 0 0 fixed on qpsk0 off 2
station scdma qpsk off 512 5 34 338 0 0 fixed on qpsk0 off 2
a-short scdma 128qam off 64 5 33 338 12 0 shortened on qpsk0
a-long scdma 128qam off 64 10 156 338 0 0 shortened on qpsk0
off
1 off
1 off
on 128 1 on
on 128 1 on
379
CASA CMTS
show modulation-profile, one profile

CASA-CMTS# config
CASA-CMTS(config)# show modulation-profile 1
short tdma qpsk off 84 6 75 338 13 8 shortened on
long tdma qpsk off 96 8 220 338 0 8 shortened on
Removing modulation profiles

Rules for removing modulation profiles are:
1) Pre-configured modulation profiles are not removable.
2) When a configured modulation profile is in use by any upstream channels, it is not
removable.
To remove a configured modulation profile, enter following command:
Step
1
Command (config)
Purpose
no modulation-profile <profile>
Remove the
specified
modulation
profile.
Where:
<profile>
ID of configured modulation profile in

the range 1 to 64.
Example:
CASA-CMTS(config)# no modulation-profile 7
CASA-CMTS(config)#
Configuring multicast operations

CASA CMTS software supports DOCSIS 3.0 enhanced IP Multicast features such as Source
Specific Multicast, Quality of Service support for multicast traffic, IPv6 multicast, and bonded
multicast. These enhanced IP Multicast features enable cable operators to offer various IP
Multicast-based multimedia services, such as Internet Protocol Television (IPTV), over the
DOCSIS network.
This section describes the commands for Multicast configuration. The commands are organized
in 4 groups:
Multicast channel utilization
Multicast session authorization
Multicast group configuration
Static multicast configuration
380
CASA CMTS
Multicast management for IPTV
In each group, the supported multicast commands are:

Multicast Session Authorization
Enabling/disabling multicast session authorization
Configuring multicast session authorization profile
Configuring multicast session rule
Configuring multicast authorization default action
Configuring multicast authorization maximum sessions
Assigning profile to multicast authorization session
Displaying configurations of multicast authorization
Multicast Group Configuration
Configuring multicast group configuration table
Configuring multicast group encryption
Configuring multicast group QoS
Configuring multicast group PHS
Configuring multicast group service class
Configuring multicast group default service class
Displaying multicast group configurations
Static Multicast Configuration
Creating static multicast
Removing static multicast
Displaying Static Multicast Configurations
Multicast Management for IPTV
Managing IPTV multicast session
Setting the multicast maximum channel utilization

To set the maximum percentage threshold for multicast streams per channel, set the global
multicast max channel-util parameter. Once the channel reaches the configured threshold, no
further multicast sessions are allowed on that channel. If the threshold percentage is too low,
bandwidth may be wasted (unusable for multicast), or the channel will be used entirely for unicast
traffic. If the threshold percentage is too high, the channel may become congested with multicast
traffic. Casa recommends that you monitor the default configuration setting of 60 and then tune
the value for best performance.
Step
1
Command
Purpose
multicast max channel-util <number>
Enable multicast
authorization
globally.
Where:
381
CASA CMTS
<number>
The numerical percentage in the range 1 to

100. The default setting is 60.
Example:
CASA-CMTS(config)# multicast authorization profile my-profile
Example:
CASA-CMTS(config)# multicast authorization enable
Enabling/disabling multicast session authorization

To enable multicast authorization globally, use the following procedure.
Step
1
Command (config)
Purpose
multicast authorization enable
Enable multicast
authorization
globally.
Example:
CASA-CMTS(config)# multicast authorization enable
To disable multicast authorization, use the following procedure. The default setting for multicast
authorization is disabled.
Step
1
Command (config)
Purpose
no multicast authorization enable
Disable
multicast
authorization
globally.
Example:
CASA-CMTS(config)# no multicast authorization enable
Configuring a multicast session authorization profile

To configure an authorization profile:
Step
1
Command (config)
Purpose
multicast authorization profile <profile_name>
Configure a
specified
authorization
profile.
Where:
<profile_name>
Multicast authorization profile name with

a string length of 1 to 15 characters.
Example:
CASA-CMTS(config)# multicast authorization profile
my-profile
382
CASA CMTS
Configuring a multicast session rule

The session rule is used to decide whether or not a specific multicast join request is accepted or
denied. To configure a session rule under authorization profile mode:
Step
1
Command (config)
Purpose
multicast authorization profile <profile_name>
Configure a
specified
authorization
profile.
Where:
<profile_name>
Multicast authorization profile name with

string length of 1 to 15 characters.
Example:
CASA-CMTS(config)# multicast authorization
profile my-profile
CASA-CMTS(conf-auth-profile my-profile)#
2
session-rule <rule-id> <accept|deny> [ipv6]

<sourceAddr/mask_len> <groupAddr/mask_len> priority
<num>
Where:
<rule-id>
Configure
specific session
rules.
Identifier for each CMTS configured

Multicast Authorization Profile Session
rule within a Multicast Authorization
Profile Name. Values are 1 to
4294967295.
<accept | deny>
Indicates whether the rule permits a

matching multicast join request to be
allowed or denied.
[ipv6]
Set multicast IPv6 mode.
<sourceAddr/mask
_len>
Identifies a range of source IP

addresses. mask_len value are 0 for
ASM based sessions, 0 to 32 for IPv4,
and 1 to 128 for IPv6.
<groupAddr/mask_
len>
Identifies a range of multicast group IP

addresses. mask_len value are 0 to 32
for ipv4, and 1 to 128 for ipv6.
<num>
Priority number of a session rule.

Higher value indicates a higher priority.
If more than one session rule matches
a joined session, the session rule with
the highest rule priority determines the
authorization action. Values are 0 to
255.
Example:
CASA-CMTS(conf-auth-profile my-profile)# sessionrule 1 accept 192.168.2.1/24 224.0.100.1/24
priority 1
383
CASA CMTS
Session matching rule:
If a multicast join request matches this rule, the request is accepted and the session is
established.
If the accept is changed to deny, then the request would be denied.
If more than one rule matches the join request, the rule with the highest priority is used.
If a mask_len of zero is configured for the source address, then requests with any source
address will match this rule.
If no rules match the multicast join request, the request will take the default setting of either
accept or deny.
Configuring the default action for a multicast join request

To change the default behavior for a multicast join request:
Step
1
Command (config)
Purpose
multicast authorization default-action <permit | deny>
Change the
default behavior
for a multicast
join request.
Where:
<permit | deny>
Change default action to permit or deny.
Example:
CASA-CMTS(config)# multicast authorization
default-action permit
Configuring a maximum session number for multicast authorization

To restrict the number of join request that will be accepted from each cable modem:
Step
1
Command (config)
Purpose
multicast authorization max-session-num <number>
Restrict the
number of join
requests that will
be accepted from
each cable
modem.
Where:
<number>
Default maximum number of multicast

sessions allowed. If set to zero, the maximum
number of sessions is not limited by the CMTS.
A DefMaxNumSess value of 0 indicates that no
dynamic joins are permitted.
Example:
CASA-CMTS(config)# multicast authorization maxsession-num 5
Assigning a profile to multicast authorization

To specify the name of a profile to be used for multicast authorization:
384
CASA CMTS
Step
1
Command (config)
Purpose
multicast authorization match-profile <name>
Name the profile

to be used for
multicast
authorization.
Where:
<name>
When IP multicast authorization is enforced,

this attribute provides the default set of
multicast authorization profiles the CMTS
enforces for a CM if this CM did not signal a set
of profiles during the registration process.
Name length is 1 to 255.
To use more
than one profile,
specify more
profile names.
Example:
CASA-CMTS(config)# multicast authorization matchprofile my-profile1
CASA-CMTS(config)# multicast authorization matchprofile my-profile2
Displaying multicast authorization configurations

To display the multicast authorization configurations:
Step
1
Command (config)
Purpose
show running-config | include multicast
Display the
multicast group
configurations.
Example:
CASA-CMTS(config)#show running-config | include
multicast
!multicast
multicast authorization match-profile my-profile1
multicast authorization default-action permit
multicast authorization max-session-num 5
multicast authorization profile 1
multicast group config 1
multicast group encryption 1 algorithm cmts
multicast group qos 1 IPTV aggregate max-sess 10
app-id 1234
Displaying multicast authorization sessions

To display the multicast sessions:
Step
1
Command (config)
Purpose
show igmp client
Display the
multicast
sessions.
Example:
CASA-CMTS(config)#show igmp client
Number Module
Vlan
Multicast Group
385
CASA CMTS
------ --------IPV6 Multicast Groups:

Number Module
Vlan
------ ---------
--------- ----Multicast Group

--------- -----
Configuring a multicast group table

To configure a multicast group configuration table:
Step
1
Command (config)
Purpose
multicast group config <id>
Select the
multicast
group
configuration
object.
Where:
<id>
Identifier of the instances of a group configuration

object. Value: 1 to 4294967295
Example:
CASA-CMTS(config)# multicast group config 1
CASA-CMTS(conf-grp-config 1)#
source-address <sourceAddr/mask_len>
group-address <groupAddr/mask_len>
tos-low <tos_low_number>
tos-high <tos_high_number>
tos-mask <tos_mask_number>
qos-id <gos_id>
priority <level>
encryption-id <encryption_id_number>
phs-id <phs_id_number_>
Where:
<sourceAddr/mask_len>
Configure the
table entries.
Identifies a range of source IP

addresses. The mask_len value is 0
for ASM-based sessions, 0 to 32 for
IPv4, and 1 to 128 for IPv6.
<groupAddr/mask_len>
Identifies a range of multicast group

IP addresses. The mask_len value is
0 to 32 for IPv4, and 1 to 128 for
ipv6.
<tos_low_number>
Identifies the low value of a range of

the TOS byte value to be defined in
a packet classifier. Value: 0 to 255.
<tos_high_number>
Identifies the high value of a range of

the TOS byte value to be defined in
a packet classifier. Value: 0 to 255.
<tos_mask_number>
Identifies the mask value bitwise

AND with a TOS byte value to be
defined in a packet classifier. Value:
0 to 255.
<qos_id>
Identifies an instance in
386
CASA CMTS
CmtsGrpQosCfg for configuring the

QOS for the replications of the
sessions matching this GC. The
value 0 indicates that QOS is
allocated based on the default SCN
for all replications derived from this
group configure. Value: 0 to 65535.
<level>
Indicates the priority of the entry

when a newly replicated multicast
session matches multiple entries.
Higher values indicate a higher
priority. Value:0 to 255
<encryption_id_number>
Indicates the multicast encryption ID.

Value: 0 to 65535
<phs_id_number>
Indicates the payload header

suppression (PHS) identifier. PHS
reduces redundant packet header
information during the multicast
session. Any suppression
information is re-inserted at the
destination.
Value: 0 to 65535
Example:
Specify qos for a multicast session with a specific service class:
CASA-CMTS(conf-grp-config
192.168.0.1/32
244.0.0.1/32
1)# source-address
1)# group-address
1)#
1)#
1)#
1)#
1)#
1)#
1)#
tos-low 0
tos-high 0
tos-mask 0
qos-id 13
encryption-id 0
phs-id 0
priority 1
Configuring multicast group encryption

To configure encryption:
Step
1
Command (config)
Purpose
multicast group encryption <number> algorithm

<cmts|aes128|des40|des56>
Configure
multicast group
encryption.
Where:
<number>
Identifier of instances of the

encryption in the range 1 to
387
CASA CMTS
65535.
<cmts|aes128|des40|des
56>
Defines which encryption

algorithm will be used for an SA
referenced by this object.
Example:
CASA-CMTS(config)# multicast group encryption 1
algorithm cmts
Configuring multicast group QoS

To configure QoS:
Step
1
Command (config)
Purpose
multicast group qos <qos_num> <service-class-name>

<single | aggregate> [max-sess <max_sess_num>] app-id
<app_id>
Configure
multicast group
QoS.
Where:
<qos_num>
QoS identifier. Value: 1 to 65535.
<service-class-name>
Identifies the Service class name

reference for the set of QoS
parameters for this GQC object.
String-length: 1 to 15.
<single>
The CMTS creates a unique GCR

and a unique GSF for the session.
If the multicast group qos is
configured to be single, a new
downstream service flow will be
used for each session.
<aggregate>
All sessions matching this criterion

are aggregated into the same
GCR. If aggregate is configured,
only one service flow will be used
for all sessions and the maxsess number will determine the
maximum number of sessions that
will be allowed to use the service
flow.
<max_sess_num>
Identifies the maximum number of

sessions that may be aggregated
in an aggregated Service Flow.
This value is ignored in case of a
CGR with QosCtrl set to 'single'.
Value: 0 to 65535. The default
setting is 0.
<app_id>
Configures an application identifier

that an operator configures to
388
CASA CMTS
enable special features for QoS

admission control or other
policies. The behavior and usage
of the application identifier is
vendor specific. Value: 1 to
4294967295.
Example:
Specify qos for a multicast session with a specific service class:
CASA-CMTS(config)# multicast group qos 13 mysrvs-class single app-id 1
Configuring a multicast group service class

See the next section for more information on configuring a service class.
To configure a service class:
Step
1
Command (config)
Purpose
cable service class <class_id>
Enter the service

class
Where:
<class_id>
Service class ID in the range 1 to 255.
Example:
CASA-CMTS(config)# cable service class 1
CASA-CMTS(conf-service-class 1)#
name <name>
min-packet-size <min_packet_size>
min-reserve-rate <min_reserve_rate>
max-concat-burst <max_concat_burst>
max-latency <max_latency>
max-outstanding-bytes-per-sid-cluster <bytes>
max-req-per-sid-cluster <max_req>
max-time-in-sid-cluster <max_time>
max-tot-bytes-req-per-sid-cluster <max_tot>
max-traffic-burst <max_traffic_burst>
max-traffic-rate <max_traffic_rate>
req-trans-policy <req_trans_policy>
required-attr-mask <req_attr-mask>
tos-overwrite <tos_overwrite>
Where:
<name>
Configure the
table entries.
Service class name associated

with this service class object
instance. String length: 1 to 15.
<min_packet_size>
Minimum packet size. Value: 0 to

65535.
<min_reserve_rate>
Minimum reserve rate. Value: 0 to

4294967295.
389
CASA CMTS
<max_concat_burst>
Maximum concatenation burst.

Value: 0 to 65535.
<max_latency>
Maximum latency. Value: 0 to

4294967295.
<bytes>
Maximum outstanding bytes per

SID cluster in the range 0 to
4294967295.
<max_req>
Maximum requests per SID cluster

in the range 0 to 255.
<max_time>
Maximum time in SID cluster in

<max_tot>
Maximum total bytes required per

SID cluster in the range 0 to
4294967295.
<max_traffic_burst>
Maximum traffic burst. Value: 0 to

4294967295.
<max_traffic_rate>
Maximum traffic rate. Value: 0 to

4294967295.
<req_trans_policy>
QOS service class request policy

in the range 0x0 to 0xFFFFFFFF.
<required_attr_mask>
QOS service class required

attribute bit mask in the range 0x0
to 0xFFFFFFFF.
<tos_overwrite>
QOS service class TOS mask in

the range 0x0 to 0xFF.
Example:
CASA-CMTS(config)# cable service-class 1
CASA-CMTS(conf-service-class 1)# name
my_srvs_class
CASA-CMTS(conf-service-class 1)# min-packet-size
100
CASA-CMTS(conf-service-class 1)# min-reserve-rate
200
CASA-CMTS(conf-service-class 1)# max-concat-burst
123
CASA-CMTS(conf-service-class 1)# max-latency 112
CASA-CMTS(conf-service-class 1)# max-trafficburst 10
CASA-CMTS(conf-service-class 1)# max-traffic-rate
13
Configuring a default service class for a multicast group

A default service class will be used if a join request does not match any of the multicast group
configuration table entries. If a default service class is not configured, the request will be denied.
390
CASA CMTS
To configure a default service class:

1
Purpose
multicast default group-service-class <class_name>

Where:
<class_name>
Configure the
default service
class.
Default group service-class name

containing up to 15 characters.
Example:
CASA-CMTS(config)# multicast default groupservice-class dgsc1
Displaying multicast group configurations

To display the multicast group configurations:
Step
1
Command (config)
Purpose
show running-config | include multicast
Display the
multicast group
configuration.
Example:
CASA-CMTS(config)#show running-config | include
multicast
!multicast
multicast authorization match-profile my-profile1
multicast authorization default-action permit
multicast authorization max-session-num 5
multicast authorization profile 1
multicast group encryption 1 algorithm cmts
multicast group qos 1 IPTV aggregate max-sess 10
app-id 1234
Creating static multicast sessions

To create a static multicast session for any-source-multicast:
Step
1
Command (config)
Purpose
cable igmp static-group <grpAddr>
Specify the group

address.
Where:
<grpAddr>
IP multicast group address.
Example:
CASA-CMTS(config)# cable igmp static-group
224.0.100.100
To create a static multicast session for source-specific-multicast:
391
CASA CMTS
Step
1
Command (config)
Purpose
cable igmp static-group <grpAddr> source <srcAddr>

or
cable igmp static-group <grpAddr> source <srcAddr> dsid <dsid>
Specify the
group and
source
address.
Where:
<grpAddr>
<srcAddr>
The source IP address for SSM

session.
<dsid>
DSID value in the range 85689 to

86688.
Example:
CASA-CMTS(config)# cable igmp static-group
224.0.100.100 source 192.168.0.1
CASA-CMTS(conf-igmp-static-group 224.0.100.100)#
qam X/Y/Z
Where:
<X/Y/Z>
Specify the
QAM ID for
downstream
binding.
QAM ID.
Example:
CASA-CMTS(conf-igmp-static-group 224.0.100.100)# qam
2/0/0
Removing a static multicast session

To remove all static sessions:
Step
1
Command (config)
Purpose
no cable igmp static-group
Remove all static

sessions.
Example:
CASA-CMTS(config)# no cable igmp static-group
To remove a specific static session for any-source-multicast:
Step
1
Command (config)
Purpose
no cable igmp static-group <grpAddr>
Remove the
static session
specified.
Where:
<grpAddr>
Example:
224.0.100.100
To remove a specific static session for source-specific-multicast:
392
CASA CMTS
Step
1
Command (config)
Purpose
no cable igmp static-group <grpAddr> source <srcAddr>
Remove the
static session for
a source-specific
multi-cast.
Where:
<grpAddr>

The source IP address for SSM session.
<srcAddr>
Example:
224.0.100.100 source 192.168.0.1
Displaying static multicast sessions

To display the static multicast session configurations:
Step
1
Command (config)
Purpose
show running-config
Display the static

multicast
sessions.
Example:
CASA-CMTS(config)# show running-config
cable igmp static-group 224.0.100.1

qam 2/0/0
Configuring IGMP packet filtering

To set number of IGMP response packets to accept from the CM and CPE in a configured time
Step
1
Command (config)
Purpose
[no] cable igmp filter <number> <seconds>
Set the number of IGMP

the specified time
window.
Where:
<number>
<seconds>

maximum number of IGMP response
setting is 4 IGMP packets.

default settings.

IGMP packets from the CM or CPE. The
Example:
CASA-CMTS(config)# cable igmp filter 10 2
393
CASA CMTS
Displaying all filtering settings in the running configuration

To display the IGMP filter setting and all filtering settings from the running CMTS configuration:
Step
1
Command (config)
Purpose
show cable filter running-config
Display the filter settings

from the running
configuration.
Example:
CASA-C3000(config)#show cable filter runningconfig
cable arp filter 8 2
cable source-verify leasequery-filter 32 10
cable icmp filter 0 2
cable igmp filter 4 2
CASA-C3000(config)#
Managing multicast for IPTV as a limited multicast session

DOCSIS 3.0 introduced extensive changes to multicast functionality, particularly multicast QoS
and authorization.
Limited multicast sessions

In order to conserve bandwidth, it is desirable to minimize multicast replication for IPTV
programs. A modem that is joining a multicast session that is replicated on a different channel
should be moved to that channel, if that channel is reachable by the modem. In this document,
multicast sessions that desire minimum replication are termed limited multicast sessions.
General multicast sessions

There are multicast sessions that many clients join. For example, multicast sessions used to
distribute EPG information are referred to as general multicast sessions. General multicast
sessions should be replicated to current channels, and must not trigger DCC/DBC transactions.
How to identify limited multicast sessions

You can identify limited multicast sessions by using the application ID. The application ID is an
attribute that can be configured into a group QoS configuration. Currently, it has no significance to
the CMTS. An application policy is a new object that is used to store application attributes, such
as limiting replication for multicast sessions.
The procedure for identifying a limited multicast session is:
1. Configure a multicast group table with matching group-address and qos-id.
2. Configure the multicast group qos with a specified app-id.
3. Configure the app-id with limit replication and max IPTV channels.
For example, to identify multicast session matching group address 230.0.1.0/24 as limited
multicast sessions, define the following configurations:
394
CASA CMTS
CASA-CMTS(config)# multicast group config 1

CASA-CMTS(conf-grp-config 1) source-address 0.0.0.0/0
CASA-CMTS(conf-grp-config 1) group-address 230.0.1.0/24
CASA-CMTS(conf-grp-config 1) qos-id 1
CASA-CMTS(conf-grp-config 1) end
CASA-CMTS(config) multicast group qos 1 IPTV aggregate max-sess 10 appid 1
CASA-CMTS(config) application policy 1
CASA-CMTS(conf-app-policy 1234) limit replication
CASA-CMTS(conf-app-policy 1234) max iptv channel <num=0:2>
Configuring cable service classes

This section describes the basic steps for configuring service classes:
Create the service class
Specify and verify the parameters; apply the service class to the modem configuration file
Creating a cable service class

To create the service class:
Step
1
Command (config)
Purpose
cable service-class <index>
Initiate the
service class
Where:
<index>
Example:
name <name>
Where:
<name>
The qos service class index (1 255).
The service class name.
Example:
CASA-CMTS(conf-service-class 1)# name my_class
<direction>
Where:
<direction>
Name the class.
Define the
direction.
Upstream or downstream.
Example:
CASA-CMTS(conf-service-class 1)# upstream
395
CASA CMTS
Specifying the cable service class parameters

Perform the following steps:
Step
1
Command
Purpose
<param>
Service class
parameters to
be applied.
Where:
The following parameters are supported.
activity-timeout
admission-timeout
attr-aggr-rule-mask
ds-resequencing
dscp-overwrite
forbidden-attr-mask
grant-interval
grant-jitter
grant-size
grants-per-interval
max-concat-burst
max-latency
max-outstandingbytes-per-sid-cluster
max-req-per-sidcluster
max-time-in-sidcluster
max-tot-bytes-reqper-sid-cluster
max-traffic-burst
max-traffic-rate
min-packet-size
min-reserved-rate
multiplier-bytes-req
multiplier-contentionreq-window
name
no
peak-traffic-rate
poll-interval
poll-jitter
priority
req-trans-policy
required-attr-mask
sched-type
tos-overwrite
qos service class activity timeout

qos service class admission timeout
qos service class attribute aggregation rule
mask
qos service class ds-resequencing
qos service class dscp overwrite
qos service class forbidden attribute mask
qos service class grant-interval
qos service class grant-jitter
qos service class grant-size
qos service class grants-per-interval
qos service class max-concat-burst
qos service class max-latency
qos service class max-outstanding-bytesper-sid-cluster
qos service class max-req-per-sid-cluster
qos service class max-time-in-sid-cluster
qos service class max-tot-bytes-req-per-sidcluster
qos service class max traffic burst
qos service class max traffic rate
qos service class min-packet-size
qos service class min reserved rate
qos service class multiplier-bytes-req
qos service class multiplier-contention-reqwindow
unique name of qos service class to create
no command
qos service class peak-traffic-rate
qos service class poll-interval
qos service class poll-jitter
set multicast group priority
qos service class request policy
qos service class required attribute mask
qos service class schedule type
qos service class tos mask
Example:
CASA-CMTS(conf-service-class 1)#max-traffic-burst
20000000
396
CASA CMTS
Exits the
service class
configuration.
end
Example:
CASA-CMTS(conf-service-class 1)#end
CASA-CMTS(config)#show cable service-class
Index
Name
Dir
Sched
Prio
MaxSusRate
MaxBurst
MinRsvRate
1
test
US
BE
0
20000000
0
Displaying service class parameters

To display the service class parameters:
397
CASA CMTS
Step
1
Command (config)
Purpose
show cable service-class [<unum=1:255>] [(brief|verbose)]
Display the
service class
parameters.
Where:
No option
Displays class parameters of all service

classes.
[<unum=1:255>]
A specific service class.
[(brief|verbose)]
Displays a subset or all parameters of the

service class(s).
Example:
To display the service class parameters of all service classes:
CASA-CMTS(config)#show cable service-class
Index
Name
Dir
Sched
Prio
MaxSusRate
MaxBurst MinRsvRate
1
PCMM-US
US
BE
0
0
24480
0
2
PCMM-DS
DS
BE
0
512000
3044
0
3
DefD3Down
US
BE
0
0
3044
0
To display the detailed service class parameters of a specific service
class:
CASA-CMTS(config)#show cable service-class 1 verbose
Index: 1
Name: UP_UGS
Direction: Upstream/Downstream
Traffic Priority: 0
Maximum Sustained Rate: 0 bits/sec
Max Burst: 1522 bytes
Minimum Reserved Rate: 0 bits/sec
Minimum Packet Size 100 bytes
Admitted QoS Timeout 200 seconds
Active QoS Timeout 30 seconds
Scheduling Type: Unsolicited Grant Service
Request/Transmission Policy: 0x1FF
Unsolicited Grant Size: 100 bytes
Nominal Grant Interval: 20000 usecs
Tolerated Grant Jitter: 4000 usecs
Grants per Interval: 1
IP ToS Overwrite [AND-mask,OR-mask]: 0xE0,0xA0
Max Latency: 0 usecs
Parameter Presence Bitfield: {0xE08, 0xBCC000}
398
CASA CMTS
Applying service classes to modem configuration files

To apply the service class parameters, specify the service class name in TLV 24/25.4. For
example:
Main
{
NetworkAccess 1;
UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
ServiceClassName test; >specify name here
SchedulingType 2;
}
DsServiceFlow
{
DsServiceFlowRef 3;
ServiceClassName test-ds; >specify name here; suppose you have define a service class name testds on cmts.
QosParamSetType 7;
}
MaxCPE 8;
GlobalPrivacyEnable 0;
/* CmMic 1be76c7df4777d078f76a3eb45d650d5; */
/* CmtsMic 6cf3523752bbd5bd627bb05460f1ff27; */
/*EndOfDataMkr*/
/* Pad */
}
Example: Service class configuration

CASA-CMTS(config)#cable service-class 1
CASA-CMTS(conf-service-class 1)# name PCMM-US
CASA-CMTS(conf-service-class 1)# max-traffic-burst 24480
CASA-CMTS(conf-service-class 1)# min-packet-size 0
CASA-CMTS(conf-service-class 1)# max-concat-burst 24480
CASA-CMTS(conf-service-class 1)# req-trans-policy 0x0
CASA-CMTS(conf-service-class 1)# tos-overwrite 0xFF 0x0
CASA-CMTS(conf-service-class 1)# app-id 0
CASA-CMTS(conf-service-class 2)# name PCMM-DS
CASA-CMTS(conf-service-class 2)# max-traffic-rate 512000
CASA-CMTS(conf-service-class 2)# downstream
CASA-CMTS(conf-service-class 3)# name DefD3Down
399
CASA CMTS

CASA-CMTS(conf-service-class 3)#end
CASA-CMTS(config)#end
CASA-CMTS#show cable service-class
Index
1
2
3
Name
Dir
PCMM-US US
PCMM-DS DS
DefD3Down
Sched
BE
BE
US
Prio
0
0
BE
MaxSusRate
0
512000
0
MaxBurst
24480
3044
3044
MinRsvRate
0
0
0
Configuring PacketCable
The CASA CMTS supports the latest PacketCable specification from CableLabs. Those
PacketCable features offer an end-to-end solution for traffic that originates or terminates on a
cable network, simplifying the task of providing multimedia services over an infrastructure
composed of disparate networks and media types, and also provides an integrated approach to
end-to-end call signaling, provisioning, quality of service (QoS), security, billing, and network
management.
This section describes the commands for configuring PacketCable. The commands are
organized in 3 groups:
Configuring PacketCable operations
Configuring RADIUS Accounting for RKS Server
Monitoring and maintaining PacketCable Operations
In each group, the supported commands are:
Configuring PacketCable operations

Enabling/disabling PacketCable
Displaying event messages
Configuring event messages
Configuring the IP address
Configuring FTP users
Configuring FTP user passwords
Configuring the T0 timer
Configuring maximum normal calls
Configuring maximum emergency calls
Displaying the PacketCable configuration
Configuring RADIUS accounting for the RKS server

Specifying timeouts for RKS servers
Specifying retry counts for RKS servers
Specifying batch file sendmode
Specifying the time interval for sending the event message batch file to the RKS server
400
CASA CMTS
Specifying the max size of the event messages batch file

Specifying the max massages in the event message batch file
Specifying the media alive time for the RKS server
Displaying RKS server information
Monitoring and maintaining PacketCable operations

Displaying summary information for alive gates
Displaying upstream information for a specific gate
Displaying downstream information for a specific gate
Displaying total number of gates
Displaying COPS server information
Enabling PacketCable operation

To enable or disable PacketCable operation:
Step
1
Command (config)
Purpose
[no] packetcable
Enable or disable
PacketCable
operation
Where:
[no]
Disables PacketCable operation.
Example:
CASA-CMTS(config)# packetcable
Displaying event messages

To show event messages:
Step
1
Command (config)
Purpose
show packetcable log
Display the
PacketCable log.
Example:
CASA-CMTS(config)# show packetcable log
Enabling DSCP checking

To enable checking of the Differentiated Services Code Point (DSCP) level of service setting in IP
headers:
Step
1
Command (config)
Purpose
[no] packetcable dscp check
Configure an
event message.
Example:
CASA-CMTS(config)# packetcable dscp check
401
CASA CMTS
Configuring event messages

To configure event message:
Step
1
Command (config)
Purpose
[no] packetcable elemid <ele_id>
Configure an
event message.
Where:
[no]
Sets event-message ID to default value

9999
Event-message ID. Values are 1 to 9999
with a default 9999.
<ele_id>
Example:
CASA-CMTS(config)# packetcable elemid 9996
Configuring an IP address
To configure an IP address for the CASA CMTS:
Step
1
Command (config)
Purpose
[no] packetcable myaddress <ip_addr>
Configure an IP
address.
Where:
[no]
<ip_addr>
Sets IP address to default value 0.0.0.0.

IP address of CMTS in decimal form. Default
is 0.0.0.0.
Example:
CASA-CMTS(config)# packetcable myaddress 1.1.1.1
Configuring an FTP user

To configure an FTP user name:
Step
1
Command (config)
Purpose
[no] packetcable ftp newuser <name>
Configure an FTP
user name.
Where:
[no]
<name>
If the user is not manually configured, the default

is casa. The no form of this command sets user
name to default.
FTP user name.
Example:
CASA-CMTS(config)# packetcable ftp newuser cucu
402
CASA CMTS
Configuring FTP user passwords

To configure a password for the current FTP user:
Step
1
Command (config)
Purpose
[no] packetcable ftp user password <pswd>
Configure a
password for the
current FTP user.
Where:
[no]
Sets user password to default.

User password. The default is casa.
<pswd>
Example:
CASA-CMTS(config)# packetcable ftp user password
mypswd

To configure the t0 timer:
Step
1
Command (config)
Purpose
[no] packetcable t0 <time>
Configure the T0
timer.
Where:
[no]
<time>
Sets t0 timer to default.

Time of t0 timer in seconds, values are 1 to
65535. The default is 30.
Example:
CASA-CMTS(config)# packetcable t0 15

To configure the t1 timer:
Step
1
Command (config)
Purpose
[no] packetcable t1 <time>
Configure the T0
timer.
Where:
[no]
<time>
Sets t1 timer to default.

Time of t1 timer in seconds; values are 1 to 65535.
The default is 200.
Example:
CASA-CMTS(config)# packetcable t1 10
403
CASA CMTS
Configuring network layer signaling (NLS)

The packetcable nls command sets Network Layer Signaling (NLS) for transporting Control
Point Discovery (CPD) messages, setting the Authentication Group Identifier (AGID), and the
CMTS loopback interface for NLS traffic.
Step
1
Command (config)
Purpose
[no] packetcable nls [agid <number> key <string> | cpd |

source-interface loopback <0 to 15>]
Configure
PacketCable
Network Layer
Signaling.
Where:
agid
<number>
key <string>
Specifies the authentication group identifier and

key TLV to be carried over NLS authentication
message exchanges. The AGID and variable
key string must be matched for a successful
request and reply exchange.
cpd
Specifies Control Point Discovery (CPD)

messaging. CPD protocol messages are carried
by the NLS protocol to media endpoints (MTAs)
to gather the IP addresses of end devices.
sourceinterface
loopback
Specifies the CMTS logical interface for NLS

traffic in the range 0 to15.
Example:
CASA-CMTS(config)#
CASA-CMTS(config)#
interface loopback
CASA-CMTS(config)#
alpha
packetcable nls cpd

packetcable nls source10
packetcable nsl agid 124 key
Configuring maximum normal calls

To configure maximum normal calls for the CMTS:
Step
1
Command (config)
Purpose
[no] packetcable max normal call <num>
Configure the
maximum normal
calls.
Where:
[no]
<num>
Sets max normal calls to the emergency

(emerg) default setting.
Number of max normal calls in the range 1 to
Example:
CASA-CMTS(config)# packetcable max normal call 5
404
CASA CMTS
Configuring maximum emergency calls

To configure max emergency calls for the CMTS:
Step
1
Command (config)
Purpose
[no] packetcable max emerg call <num>
Configure the
maximum normal
calls.
Where:
[no]
<num>
Sets max emergency calls to default.

Number of max emergency calls; values are 1
to 1024. The default is 1000.
Example:
CASA-CMTS(config)# packetcable max emerg call 100
Configuring inactive call aging (Rel. 6.1 and later)

The packetcable inactive call aging command controls freeing of packet cable gates when
service flows become inactive. Previously, PacketCable gates remained active and calls were not
being torn down after a call ended, consuming system resources and bandwidth. This command
sets the number of hours to pass before tearing down a call, as well as sets an optional minimum
voice downstream throughput threshold (in kilobits) to determine if the call session should be torn
down.
To configure inactive call aging:
Step
1
Command (config)
Purpose
packetcable inactive call aging <0-24> [minimum traffic <01000>]
Configure the
inactive call aging
time in hours and
the optional
minimum
downstream
throughput in
kilobit before
determining call
teardown.
Where:
<0-24>
<0-1000>
Specifies the call aging time in hours 0 to 24.

The default setting is 2 hours. Enter 0 to
disable the inactive call aging setting.
Specifies the minimum downstream
throughput in kilobits before determining if a
call should be torn down (if the minimum
setting is not met). The default setting is 30
kbps.
Example:
CASA-CMTS(config)# packetcable inactive call
aging 4 minimum traffic 50
Enabling PacketCable admission control preempt voice priority

To enable or disable PacketCable admission-control preempt voice priority:
405
CASA CMTS
Step
1
Command (config)
Purpose
[no] cable admission-control preempt priority-voice
Enable or disable
PacketCable
admission control
preempt voice
priority.
Where:
[no]
Disables admission-control preempt voice priority.
Example:
CASA-CMTS(config)#cable admission-control preempt
priority-voice
Enabling PacketCable Multimedia (PCMM)

The packetcable multimedia command enables PCMM so that the CMTS generates and
responds to PCMM Common Open Policy Service (COPS) commands. Once enabled, the
CMTS attempts a COPS connection over a TCP connection to a PCMM policy server.
Step
1
Command (config)
Purpose
[no] packetcable multimedia [T1 <1 to 1000>]
Enable or disable
PacketCable
multimedia.
Where:
[no]
T1
Disables PacketCable multimedia.

Specifies the optional T1 timer in seconds.
This setting configures the amount of time
that PCMM will remain in an authorized state.
Example:
CASA-CMTS(config)# packetcable multimedia
CASA-CMTS(config)# packetcable multimedia t1 100
Enabling Packetcable Multimedia version setup

To enable or disable Packetcable Multimedia Version setup:
Step
1
Command (config)
Purpose
[no] pcmm mmversion major <num=1:10> minor <num=0:10>
Enable or
disable
PacketCable
multimedia
version
setup.
Where:
[no]
Disables PacketCable multimedia.
<num=1:10>
Major number from 1 to 10.
<num=0:10>
Minor number from 0 to 10.
Example:
casa-CMTS(config)#pcmm mmversion major 1 minor 10
casa-CMTS(config)#
casa-CMTS(config)#no pcmm mmversion major 1 minor 10
406
CASA CMTS
Displaying Packetcable Multimedia specifications

To show the Packetcable Multimedia specifications:
Step
1
Command (config)
Purpose
show pcmm gateid <0-0xffffffff> [clsfy | spec | traffic]
Display the
selected
specification.
Where:
<0-0xffffffff>
Gate ID ranged from 0 to 0xffffffff.
[clsfy | spec | traffic]
Classifier, Specification, or Traffic

Specification.
Example:
casa-CMTS(config)#show pcmm gateid 1 clsfy spec
Cable Modem:
0015.f2fe.8d6a
GateID:
0x40002
PCMM gate state:
AUTH
Direction:
upstream
Type:
multicast
PCMM service-flow:
0
PCMM T1 timer:
200s
PCMM T2 timer:
0s
PCMM T3 timer:
60s
PCMM T4 timer:
0s
PCMM classify count:
1
PCMM traffic profile type:
1
PCMM traffic profile:
Flow Spec
PCMM envelope type:
1
PCMM Time Usage Limit:
0s
PCMM Time Usage:
0s
PCMM Volume Usage Limit:
0 Kbytes
PCMM Volume Usage:
0 Kbytes
casa-CMTS(config)#show pcmm gateid 5 spec
casa-CMTS(config)#show pcmm gateid 1 traffic spec
Setting the cable service flow timeout

To set the active service flow timeout for PacketCable implementations where a policy server is
not used:
Step
1
Command (config)
Purpose
[no] cable service-flow active-timeout <seconds>
Sets the active

service flow
timeout for
PacketCable
implementations
that do not use a
Where:
[no]
<seconds>
Resets the service flow to the default.

The number of seconds before the service
407
CASA CMTS
flow times out. Valid values are 0- 200. The

default is 0 (no timeout).
policy server:
Example:
CASA-CMTS(config)# cable service-flow activetimeout 100
Assigning dynamic service flows to downstream channels

Use the cable dynamic-service-flow command to assign dynamic service flows to bonded
downsteam channels (default), to any one of the downstream channels (non-bonding), or to the
modems primary downstream channel. For example, to assign VoIP traffic to the modems
primary downstream channel, use the cable dynamic-service-flow primary command.
Step
1
Command (config)
Purpose
[no] cable dynamic-service-flow {bonding | non-bonding |

primary}
Assigns dynamic
service flows to
modem
downstream
channels.
Where:
bonding
Assigns dynamic service flows to bonded

downstream channels. This is the default
setting.
non-bonding
Assigns dynamic service flows to any one of

the downstream channels.
primary
Assigns dynamic service flows to the modems

primary downstream channel.
Example:
CASA-CMTS(config)# cable dynamic service-flow
primary
Displaying the PCMM policy server

To show PCMM ps server:
Step
1
Command (config)
Purpose
show pcmm ps server
Shows the
PCMM policy
server.
Example:
casa-CMTS(config)#show pcmm ps server
IP
Port
PSID
Displaying the PacketCable configuration

To show the PacketCable configuration:
408
CASA CMTS
Step
1
Command (config)
Purpose
show packetcable global
Shows the
PacketCable
configuration.
Example:
CASA-CMTS(config)# show packetcable global
**********PacketCable Global**********
PacketCable:
enable
Element ID:
9999
MyIPaddr:
0.0.0.0
Gate ID Used:
0
Max Gate:
8000
COPS Server Listen Port:
2126
RKS_Receive_Port:
1813
PCMM Listen Port :
3918
PCMM version:
2.0
T0 Timer:
30
T1 Timer:
200
Max Batch File Size:
65535
Batch File Send Mode:
UDP
Batch File Send Time:
1
Batch File Ftp User:
casa
Normal Calls:
0
Emerg Calls:
0
Max Normal Calls:
1000
Max Emerg Calls:
1000
RKS tries:
3
Media Alive:
00:00
inactive call aging:
2
inactive call mini traffic:
30
no cable admission-control preempt priority-voice
**************************************
Specifying a timeout for the RKS server

Timeout is the time interval that the router waits for the RKS server to reply before retransmitting.
To specify or remove the timeout:
Step
1
Command (config)
Purpose
[no] packetcable rks timeout <time>
Set or removes
the RKS server
timeout.
Where:
<time>
[no]
Time interval for router retransmitting to RKS

server, values are 1 to 30. The default is 5.
Removes the timeout setting.
Example:
CASA-CMTS(config)# packetcable rks timeout 9
CASA-CMTS(config)# no packetcable rks timeout
409
CASA CMTS
Specifying a retry count for the RKS server

The retry count is the number of times that a RADIUS request is re-sent to a RKS server. To
specify or remove the retry count:
Step
1
Command (config)
Purpose
[no] packetcable rks retry <count>
Set or remove
the retry count.
Where:
<count>
[no]
Retry count, values are 1 to 10. The default is

3.
Removes the retry count.
Example:
CASA-CMTS(config)# packetcable rks retry 6
CASA-CMTS(config)# no packetcable rks retry
Specifying batch file send mode

A batchfile can be sent to the RKS server by UDP or FTP. To specify or reset send mode:
Step
1
Command (config)
Purpose
[no] packetcable rks batchfile sendmode <udp | ftp>
Sets or resets the

send mode.
Where:
<udp | ftp>
[no]
Specifies send mode.

Resets the send mode.
Example:
CASA-CMTS(config)# packetcable rks batchfile
sendmode udp
Disable:
CASA-CMTS(config)# no packetcable rks batchfile
sendmode
Specifying the batch file sending time interval

To specify a time interval for sending the batchfile to the RKS server:
Step
1
Command (config)
Purpose
[no] packetcable rks batchfile time <interval>
Set or remove
the batch file
send interval.
Where:
<interval>
Time interval of sending the batch file to the

RKS server in the range 1 to 200 seconds.
The default is 200 seconds.
410
CASA CMTS
[no]
Removes the time interval.
Example:
CASA-CMTS(config)# packetcable rks batchfile time
120
time
Specifying the maximum size of the event message batch file

To specify the maximum size of the batch file sent to the RKS server:
Step
1
Command (config)
Purpose
[no] packetcable rks batchfile max size <size>
Specify the
maximum size of
the batch file.
Where:
<size>
[no]
The max size of batchfile in the range 1024 to

Sets max event messages to default.
Example:
CASA-CMTS(config)# packetcable rks batchfile max
size 4096
Disable:
max size
Specifying the maximum messages in the batch file

To specify maximum number of messages in a batch file:
Step
1
Command (config)
Purpose
[no] packetcable rks batchfile max msg <num>
Specify the
maximum
number of
messages in a
batch file.
Where:
<num>
[no]
The max messages in batchfile, values are 1

to 20. The default is 20.
Sets max event messages to default.
Example:
CASA-CMTS(config)# packetcable rks batchfile max
msg 10
Disable:
max msg
411
CASA CMTS
Specifying the RKS server media alive time

Media Alive Time is an EM message. To specify the media alive time:
Step
1
Command (config)
Purpose
[no] packetcable media alive time <time>
Set or reset the

media alive
time setting.
Where:
<time>
[no]
Media alive time in form hh:mm.

Removes the time setting.
Example:
CASA-CMTS(config)# packetcable media alive time
10:30
CASA-CMTS(config)# no packetcable media alive
Specifying the RKS server maximum gates

To specify or reset the RKS server maximum gates:
Step
1
Command (config)
Purpose
[no] packetcable max gate <number>
Specify the
maximum gates
or reset to
default.
Where:
<number>
[no]
Max gate number, from 1 to 9999. The default

setting is 8000.
Sets maximum gates to default.
Example:
CASA-CMTS(config)# packetcable max gate 1000
CASA-CMTS(config)# no packetcable max gate
Displaying RKS server information

To show RKS server information:
Step
1
Command (config)
Purpose
show packetcable rks server
Display RKS
server
information.
Example:
CASA-CMTS(config)# show packetcable rks server
412
CASA CMTS
Displaying live gate summary information

To show a summary of live gates:
Step
1
Command (config)
Purpose
show packetcable gate
Display live gates

summary.
Example:
CASA-CMTS(config)# show packetcable gate
GateID
SubID
State
U_stream
D_stream
RKSIP
1
10.237.2.200 committed
enable
enable
192.168.0.155
Displaying upstream or downstream gate information

To show upstream or downstream information for a specific gate:
Step
1
Command (config)
Purpose
show packetcable gateid <gate_id> [uspec | dspec]
Display the
upstream or
downstream
information.
Where:
<gate_id>
[uspec | dspec]
Gate ID.
Downstream specifications or upstream
specifications.
Example:
CASA-CMTS(config)# show packetcable gateid 1
uspec
Displaying the total gate number

To show the total number of gates:
Step
1
Command (config)
Purpose
show packetcable commit gate
Display the total

number of gates.
Example:
CASA-CMTS(config)# show packetcable commit gate
Displaying COPS server information

To show COPS server information:
Step
1
Command (config)
Purpose
show packetcable cms server
Display the
413
CASA CMTS
Example:
CASA-CMTS(config)# show packetcable cms server
COPS server
information.
Configuring DSG
The CASA CMTS supports the latest DOCSIS Set-Top Gateway (DSG) specification from
CableLabs. DSG offers substantial support for enhanced DOCSIS implementation in the
Broadband Cable environment.
This section describes the commands of DSG configuration and provides an example at the end
of the section. The commands are organized in 7 groups:
Configuring a DSG tunnel and classifier
Associating a DSG tunnel with a tunnel-group
Configuring a DSG downstream table
Configuring a DSG client list
Configuring DSG vendor parameters
Configuring a DSG channel list
Configuring DSG timers
The following section describes the DSG configuration commands.
Creating a new DSG tunnel

To create a new DSG tunnel, delete a tunnel or enter DSG tunnel configuration mode:
Step
1
Command (config)
Purpose
[no] dsg tunnel <tunnel-id>
Create a new
DSG tunnel,
delete the tunnel,
or enter
configuration
mode for an
existing tunnel.
Where:
<tunnel-id>
[no]
DSG tunnel identifier in the range 1 to

4294967295.
Removes the specified tunnel.
Example:
CASA-CMTS(config)# dsg tunnel 2
CASA-CMTS(conf-dsg-tunnel-2)# end
CASA-CMTS(config)#
Disable:
CASA-CMTS(config)# no dsg tunnel 2
414
CASA CMTS
Creating a DSG tunnel-group

To create a new DSG tunnel-group, or to enter an existing group, perform the following. Note
that the maximum number of tunnel groups is 32.
Step
1
Command (config)
Purpose
[no] dsg tunnel-group <tg-id>
Create a new
tunnel group,
delete a group, or
enter an existing
group.
Where:
<tg-id>
[no]
DSG tunnel-group identifier. The valid values

are 1 to 429496729.
Removes a tunnel group.
Example:
CASA-CMTS(config)# no dsg tunnel-group 2
Associating a DSG tunnel with a tunnel-group

To include a configured tunnel with a DSG tunnel-group:
Step
1
Command (config)
Purpose
Create a new
DSG tunnel,
delete the tunnel,
or enter
configuration
mode for an
existing tunnel.
Where:
<tunnel-id>
[no]
DSG tunnel identifier. The valid values are 1 to

4294967295.
Example:
CASA-CMTS(config)# dsg tunnel-group 2
CASA-CMTS(conf-dsg-tunnel-grp 2)#
Disable:
[no] group <grp_id>
Where:
<grp-id>
[no]
Associates the
tunnel with a
tunnel group.
Tunnel-group identifier. Valid values are 1 to

4294967295.
Removes the specified tunnel group
association.
Example:
CASA-CMTS(conf-dsg-tunnel-2)# group 3
Disable:
CASA-CMTS(conf-dsg-tunnel-2)# no group 3
415
CASA CMTS
Displaying DSG tunnel groups

To show DSG tunnel-group settings:
Step
1
Command (config)
Purpose
show dsg tunnel-group <tg-id>
Display DSG
tunnel group
settings.
Where:
<tg-id>

are 1 to 429496729.
Example:
CASA-CMTS(config)# show dsg tunnel-group 2
channel 1 qam x/y/z rule-priority 20 vendorparam-id 1 ucid-list 1
channel 2 qam x/y/z rule-priority 30 vendorparam-id 500 ucid-list 2
Ending a DSG tunnel-group configuration session

To end a DSG tunnel-group configuration session:
Step
1
Command (config)
Purpose
end
End a DSG
tunnel-group
session.
Example:
CASA-CMTS(conf-dsg-tunnel-grp-2)# end
Assigning a destination MAC address to a DSG tunnel

To set a MAC address to DSG tunnel:
Step
1
Command
Purpose
Create the new

DSG tunnel,
delete the tunnel,
or enter
configuration
mode for an
existing tunnel.
Where:
<tunnel-id>
[no]

4294967295.
Removes the specified tunnel
Example:
CASA-CMTS(conf-dsg-tunnel-2)#
CASA-CMTS(conf-dsg-tunnel-id)# end
CASA-CMTS(config)#
To disable:
416
CASA CMTS
dst_addr <mac_addr>
Where:
<macaddress>
Set a destination
MAC address to
the tunnel.
DSG tunnel destination MAC address in the

format xxxx.xxxx.xxxx.
Example:
CASA-CMTS(conf-dsg-tunnel-2)# dst-address
1234.2345.3456
Assigning a client list to a DSG tunnel

To assign a client-list to a DSG tunnel:
Step
1
Command (config)
Purpose
Create the new

DSG tunnel,
delete the tunnel,
or enter
configuration
mode for an
existing tunnel.
Where:
<tunnel-id>
[no]

4294967295.
Removes the specified tunnel
Example:
CASA-CMTS(config)#
Disable:
client-list <list_id>
Where:
<list_id>
[no]
Sets the tunnel

with a destination
MAC address.
DSG client list identifier. Valid values are 1

to 4294967295.
Removes the client list from the tunnel.
Example:
CASA-CMTS(conf-dsg-tunnel-2)# client-list 123
Disable:
CASA-CMTS(conf-dsg-tunnel-2)# no client-list 123
Assigning a service-class to a DSG tunnel

To assign a service-class to a DSG tunnel:
417
CASA CMTS
Step
1
Command (config)
Purpose
Create the new

DSG tunnel,
delete the tunnel,
or enter
configuration
mode for an
existing tunnel.
Where:
<tunnel-id>
[no]

4294967295.
Example:
CASA-CMTS(config)#
To disable:
[no] service-class <string>
Where:
<string>
[no]
Set the service

class to the
tunnel.
Service-class name. The max number of the

string of service-class name is 16.
Removes the client list from the tunnel.
Example:
CASA-CMTS(conf-dsg-tunnel-2)# service-class
private-class
Disable:
CASA-CMTS(conf-dsg-tunnel-2)# no service-class
private-class
Assigning a classifier to a DSG tunnel

To assign a classifier to a DSG tunnel:
Step
1
Command (config)
Purpose
Create the new

DSG tunnel,
delete the
tunnel, or enter
configuration
mode for an
existing tunnel.
Where:
<tunnel-id>
[no]

4294967295.
Example:
CASA-CMTS(config)#
418
CASA CMTS
classifier [no] <classifier_id> <priority> [ipv6] <src_ip_addr>

<dst_ip_addr> [indcd [<src_port> <dst_port>]] [secondary-srcip <sec_ip_addr>] [primary-gige <pri_gige_port> secondarygige <sec_gige_port>]
Where:
<classifier_id>
Sets a classifier
to the tunnel.
Classifier identifier. Valid values are 1 to

65535.
<priority>
Classifier priority. Valid values are 1 to

255.
[ipv6]
Set to ipv6 mode
<src_ip_addr>
Source IP address with mask prefix in

format of x.x.x.x/n.
<dst_ip_addr>
Destination IP address in format of

x.x.x.x.
indcd
Keyword specifies whether or not the

classifier is included in the DCD
message.
<src_port>
Source TCP/UDT port number.
<dst_port>
Destination TCP/UDT port number.
secondary-src-ip
<sec_ip_addr>
Secondary source IP address.
primary-gige
<pri_gige_port
Primary GigE port number; values are 0

to 11.
secondary-gige
<sec_gige_port>]
Secondary GigE port number; values

are 0 to 11.
[no]
Remove a classifier from a DSG tunnel.
Example:
CASA-CMTS(conf-dsg-tunnel-2)# classifier 1 20
192.168.0.1/24 224.0.0.100 indcd 6666 6667
CASA-CMTS(conf-dsg-tunnel-2)# no classifier 1 20
192.168.0.1/24 224.0.0.100 indcd 6666 6667
Displaying the DSG tunnel configuration (Release 5.4)

To display DSG tunnel configuration:
Step
1
Command (config)
Purpose
show dsg tunnel <tunnel-id>
Display the DSG

tunnel
configuration.
Where:
<tunnel-id>
419
CASA CMTS
4294967295.
Example:
CASA-CMTS(config)# show dsg tunnel 2
client-list 123
service-class private-class
classifier 1 20 192.168.0.1/24 224.0.0.100 indcd
Displaying the cable DSG tunnel configuration (Release 5.4)

To display the cable DSG tunnel configuration:
Step
1
Command (config)
Purpose
show cable dsg tunnel <num=1:4294967295> [(cfrs | clients |

interface | verbose)]
Display the cable

DSG tunnel
configuration.
Where:
<num=1:4294967295>
DSG tunnel identifier.
cfrs
DSG classifier.
clients
DSG client.
interface
Show DSG interface.
verbose
Show detailed DSG information.
Example:
CASA-CMTS# show cable dsg tunnel 1 cfrs
cfr
cfr
cfr destination ip
source ip
srcPre d_port d_port
id
state pri address
address
length start
end
Associating a downstream channel with a DSG tunnel-group

To associate a downstream channel and a tunnel-group:
Step
1
Command (config)
Purpose
[no] dsg tunnel-group <tg-id>
Create a new
tunnel group,
delete a group, or
enter an existing
group.
Where:
<tg-id>
[no]

are 1 to 429496729.
Removes a tunnel group.
Example:
CASA-CMTS(config)# no dsg tunnel-group 2
2
channel [no] <ch_id> qam x/y/z rule-priority <level> [vendorparam-id <vnd_id>] [ucid-list <usid_list>]
Associate a
downstream
channel and a
420
CASA CMTS
tunnel-group.
Where:
<ch_id>
User defined channel identity ranges from

1 to 4294967295.
<level>
Rule priority level ranges from 0 to 255

with 255 the highest priority.
<vnd_id>
DSG vendor parameter group identifier.

Valid values are 1 to 4294967295.
<ucid_list>
List of upstream channel IDs from which the

rule applies. Values are 1 to 255.
Removes the association.
[no]
Use the no form

of the command
to remove the
association.
Example:
CASA-CMTS(conf-dsg-tunnel-grp-2)# channel 1 qam
x/y/z rule-priority 20 vendor-param-id 1 ucidlist 1
CASA-CMTS(conf-dsg-tunnel-grp-2)# no channel 1
Displaying the downstream DSG configuration (Release 5.4)

Step
1
Command (config)
Purpose
show dsg downstream [<ds_chan>] [dcd/decoded-dcd]
Display a
downstream
DSG
configuration.
Where:
<ds_chan>
Downstream channel ID.
dcd
Downstream channel descriptor.
decoded-dcd
DSG decoded-dcd TLV information.
Example:
CASA-CMTS(config)#show dsg downstream dcd
ds
dcd
dcd
num of dcd
num of dcd
num of
i/f
state
Tx
sent
change cnt
fragment
0/1/0
dis
off
0
0
0/1/1
dis
off
0
0
0/1/2
dis
off
0
0
0/1/3
dis
off
0
0
0
0
0
0
Displaying DSG channel and tunnel group information

Step
1
Command (config)
Purpose
show dsg downstream <ds_chan> tunnel

[<num=1:4294967295>]
Display DSG
channel and
tunnel group
information.
Where:
421
CASA CMTS
<ds_chan>
Downstream channel ID.
<num=1:4294967295>
Tunnel ID range from 1 to

4294967295.
Example:
CASA-CMTS(config)#show dsg downstream 1 tunnel 1
Setting a DSG timer to a downstream channel

To set a DSG timer:
Step
Command (config)
Purpose
interface qam <x/y>
Enter
configuration
mode for a
specific
interface.
Where:
x
y
QAM slot number.

QAM port number.
Example:
[no] channel <ch_id> dsg timer-id <tmr_id>
Where:
<ch_id>
Set the DSG

timer.
Downstream channel ID, 0 to 3.
<tmr_id >
DSG timer ID, 1 to 4294967295.
[no]
Removes a DSG timer from a

downstream channel.
Example:
CASA-CMTS(conf-qam 0/1)# channel 0 dsg timer-id 1
Assigning a DSG vendor-parameter ID to a downstream channel

To set a DSG vendor-parameter ID:
Step
Command (config)
Purpose
interface qam <x/y>
Enter
configuration
mode for a
specific
interface.
Where:
x
y
QAM slot number.

QAM port number.
Example:
2
[no] channel <ch_id> dsg vendor-param-id <vnd_id>
Set the DSG

422
CASA CMTS
vendorparameter ID.
Where:
<ch_id>
<vnd_id >
DSG vendor-param ID, 1 to

4294967295.
Example:
CASA-CMTS(conf-qam 0/1)# channel 0 dsg vendorparam-id 2
Use the no
form of the
command to
remove the
assignment.
Assigning a DSG channel-list to a downstream channel

To set the DSG channel list:
Step
1
Command
Purpose
interface qam <x/y>
Enter
configuration
mode for a
specific
interface.
Where:
x
y
QAM slot number.

QAM port number.
Example:
2
[no] channel <ch_id> dsg channel-list <list_id>

Where:
<ch_id>
<list_id >

DSG channel list ID, 1 to
4294967295
Set the DSG

channel list.
Use the no
form of the
command to
remove the
assignment.
Example:
CASA-CMTS(conf-qam 0/1)# channel 0 dsg channellist 3
To remove the assignment:
CASA-CMTS(conf-qam-id)# no channel 0 dsg channellist 3
Assigning DSG DCD ENABLE to a downstream channel

To set DSG DCD ENABLE:
Step
Command (config)
Purpose
interface qam <x/y>
Enter
configuration
mode for a
specific
Where:
423
CASA CMTS
interface.
QAM slot number.
QAM port number.
Example:
[no] channel <ch_id> dsg dcd-enable
Where:
<ch_id>
Enable or
disable DSG
DCD ENABLE.
Downstream channel ID; 0 to 3.
Example:
CASA-CMTS(conf-qam 0/1)# channel 0 dsg dcd-enable
To disable:
CASA-CMTS(conf-qam-id)# no channel 0 dsg dcdenable
Setting a DSG time interval on a downstream channel

To set a DSG time interval:
Step
Command (config)
Purpose
interface qam <x/y>
Enter
configuration
mode for a
specific
interface.
Where:
x
y
QAM slot number.

QAM port number.
Example:
2
[no] channel <ch_id> dsg interval <ticks>

Where:
<ch_id>
<ticks>
Downstream channel ID; 0 to 3.
Set a DSG
time interval
to a
downstream
channel.
DSG time interval in unit of time

ticks from 2 to 10.
Example:
CASA-CMTS(conf-qam 0/1)# channel 0 dsg interval 5
Remove:
CASA-CMTS(conf-qam 0/1)# no channel 0 dsg interval 5
Displaying the DSG downstream-table settings

To show a DSG downstream table:
424
CASA CMTS
Step
1
Command (config)
Purpose
show interface qam <x/y>
Display DSG
downstream
table settings.
Where:
x
y
QAM slot number.

QAM port number.
Example:
CASA-CMTS(config)#show interface qam 2/0
interface qam 2/0
no spectral inversion on
annex B
modulation 256qam
interleave 128x1
power 510
channel 0 dsg channel-list 3
channel 0 dsg timer-id 1
channel 0 dsg vendor-param-id 2
channel 0 dsg interval 5
channel 0 dsg dcd-enable
no shutdown!
Configuring a DSG client list

To configure a DSG client list:
Step
1
Command (config)
Purpose
dsg client-list <list_id> client <client_id> id-type (broadcast |

macAddr | caSysId|appId) id-value <value> vendor-param-id
<vp_id>
Configures the
DSG client list.
[no] dsg client-list <list_id> client <client_id>
Use the no
form of the
command to
remove the
client list.
Where:
<list_id>
Client-list ID. Values are 1 to 4294967295.
<client_id>
Client ID. Values are 1 to 4294967295.
broadcast
Sets the DSG Client type broadcast identifier

with the broadcast-id value.
macAddr
The DSG Client type MAC address with macaddr value.
425
CASA CMTS
caSysId
The DSG Client type CA system ID, with value

provided for sys-id.
appId
Sets the index to use for DSG Client ID

settings, with index identifier value specified
with id.
<value>
Sets the vendor parameter index for the

vendor-specific parameters, and applied to the
specified vendor group. The values are 1 to
4294967295.
<vp_id>
Example:
CASA-CMTS(config)# dsg client-list 1 client 1 idtype broadcast id-value 2048 vendor-param-id 2
CASA-CMTS(config)# no dsg client-list 1 client 1
Displaying DSG client lists

To display DSG client lists:
Step
1
Command (config)
Purpose
show dsg client-list <list_id>
Display the
DSG client list.
Where:
<list_id>
Client-list ID. Values are 1 to 4294967295.
Example:
CASA-CMTS(config)# show dsg client-list 1
dsg client-list 1 client 1 id-type broadcast idvalue 2048 vendor-param-id 2
Configuring DSG vendor parameters

To set DSG vendor parameters:
Step
1
Command (config)
Purpose
[no] dsg vendor-param-id <vp_id> vendor <vnd_id> oui <oui>

value <value>
Set the DSG

vendor
parameters.
Where:
<vp_id>
Sets the vendor parameter index for the vendorspecific parameters, and applied to the specified
vendor group. Values are 1 to 4294967295.
<vnd_id>
DSG vendor parameters vendor index setting. Values

are 1 to 4294967295.
<oui>
DSG vendor parameters vendor OUI. Includes the

0803 <oui> tlv in the VSIF.
<value>
DSG vendor parameters vendor value.
Use the no
form of the
command to
remove the
vendor
parameters.
426
CASA CMTS
Example:
CASA-CMTS(config)# dsg vendor-param-id 1 vendor 1
oui 01:02:03 value abc
CASA-CMTS(config)# no dsg vendor-param-id 1 vendor 1
Displaying DSG vendor parameters

To show DSG vendor parameters:
Step
1
Command (config)
Purpose
show dsg vendor-param-id <vp_id>
Display the
DSG vendor
parameters.
Where:
<vp_id>
Sets the vendor parameter index for the

vendor-specific parameters, and applied to
the specified vendor group. Values are 1 to
4294967295.
Example:
CASA-CMTS(config)# show dsg vendor-param- 1
dsg vendor-param-id 1 vendor 1 oui 01:02:03 value
abc
Configuring a DSG channel list

To configure a DSG channel list:
Step
1
Command (config)
Purpose
[no] dsg channel-list <ch-list> channel <ch-id> frequency <freq>
Configure a
DSG channel
list.
Where:
<ch-list>
A list of DSG channels that could carry DSG

tunnels. Values are 1 to 4294967295.
<ch-id>
Downstream channel index. Values are 1 to

4294967295.
<freq>
Center frequency of the downstream

channel in Hz.
Use the no
form of the
command to
remove the
channel list.
Example:
CASA-CMTS(config)# dsg channel-list 1 channel 1
frequency 526000000
CASA-CMTS(config)# no dsg channel-list 1 channel 1
427
CASA CMTS
Displaying a DSG channel list

To show a DSG channel list:
Step
1
Command (config)
Purpose
show dsg channel-list <ch-list>
Displays the
DSG channel
list.
Where:
<ch-list>
A list of DSG channels that could carry DSG

tunnels. Values are 1 to 4294967295.
Example:
CASA-CMTS(config)# show dsg channel-list 1
dsg channel-list 1 channel 1 frequency 526000000
Configuring DSG timers

DSG timer entry is linked with the downstream channel and is encoded into the DCD message.
To set DSG timers:
1
Purpose
[no] dsg timer-id <timer_id> t1 <t1> t2 <t2> t3 <t3> t4 <t4>

Where:
<timer_id>
Timer identifier. Values are 1 to

4294967295.
<t1>
DSG initialization timeout. Values are 1 to

65535
<t2>
DSG operational timeout. Values are 1 to

65535.
<t3>
DSG two-way retry timer. Values are 1 to

65535.
<t4>
DSG one-way retry timer. Values are 1 to

65535.
Set the DSG

timers.
Use the no
form of the
command to
remove the
DSG timer.
Example:
CASA-CMTS(config)# dsg timer-id 1 t1 20 t2 30 t3
40 t4 50
CASA-CMTS(config)# no dsg timer-id 1
428
CASA CMTS
Displaying DSG timers

To display DSG timers:
Step
1
Command (config)
Purpose
show dsg timer-id <timer_id>
Show the timer

ID
configuration.
Where:
<timer_id>
Timer identifier. Values are 1 to

4294967295.
Example:
CASA-CMTS(config)#show dsg timer 1
dsg timer-id 1 t1 20 t2 30 t3 40 t4 50
Configuring DSG unicast

To configure DSG unicast:
Step
1
Command (config)
Purpose
dsg unicast-port <port_id>
Configure DSG
unicast.
Where:
<port_id>
Unicast port ID. Values are 1 to 65535.
Example:
CASA-CMTS(config)# dsg unicast-port 1
Displaying DSG statistics

To display DSG statistics:
Step
1
Command (config)
Purpose
show dsg statistics [(dcd | traffic)]
Display the
DCD or traffic
statistics.
Example:
CASA-CMTS(config)# show dsg statistics dcd
Displaying the DSG running configuration

To display the current DSG running configuration:
Step
1
Command (config)
Purpose
show dsg running-config
Display the
current DSG
running
Example:
429
CASA CMTS
CASA-CMTS(config)# show dsg running-config

dsg tunnel-group 1
channel 2 qam 0/1/0 rule-priority 1
dsg tunnel 1
group 1
dst-address 0010.5e00.1123
classifier 20 20 10.100.1.10/24 224.0.0.4
dsg client-list 1 client 1 id-type
broadcast id-value 1 vendor-param-id 1
dsg vendor-param-id 1 vendor 1 oui 00:11:22 value
1
dsg channel-list 1 channel 1 frequency 640000
dsg timer-id 1 t1 1 t2 2 t3 3 t4 4
dsg server-redundancy enable
dsg unicast port : 8888
configuration.
Using the DSG feature

To use the DSG feature, first complete the basic CMTS configuration and then configure the DSG
feature. The following procedure outlines the initial configuration steps.
Step
Purpose
Command Example:
Enable the IGMP client.
CASA-CMTS(config)#igmp client version 3
Enable multicast on the

GigE interface.
CASA-CMTS(config)#interface gige 0
CASA-CMTS(conf-if-gige0)#ip igmp
Enable IGMP query on the

MAC domain.
CASA-CMTS(config)#interface docsis-mac 3
CASA-CMTS(conf-if-mac3)# mgmd ipv4
version 3
CASA-CMTS(conf-if-mac3)# no mgmd ipv4
shutdown
Configure the default

service class for multicast.
CASA-CMTS(config)# multicast default grpservice-class-name xyz
Specify the service class to

be used.
CASA-CMTS(conf-service-class1)# name
<string>
The following procedure summarizes the DSG configuration steps.

Step
1
Purpose
Command
Set up the tunnel group.

This defines the mapping
CASA-CMTS(config)# dsg tunnel-group <grpid>
430
CASA CMTS
between a tunnel to
downstream channels
and DSG rule-related
data.
CASA-CMTS(conf-dsg-tunnel-grp1)# dsg
channel <chan id> qam <x/y/z> rule-priority
<pri> [vendor-param-id <vpid>] [ucid-list
<string>]
Example:
dsg tunnel-group 1
channel 1 qam 0/0/0 rule-priority
20
20
11
11
Define the DSG tunnel

ID.
CASA-CMTS(config)# dsg tunnel <id>
Define the tunnel

destination MAC address.
CASA-CMTS(conf-dsg-tunnel 1)# dst-address

xxxx.xxxx.xxxxx
Define the service class,

if any.
CASA-CMTS(conf-dsg-tunnel 1)# service-class

<name>
Define the client list for

DCD messages.
CASA-CMTS(conf-dsg-tunnel 1)# client-list

<cls id>
Define the classifier.
CASA-CMTS(conf-dsg-tunnel 1)# classifier <cls

id> <priority> <src ipv4 addr>/<prefixlen>
<group addr> [indcd .]
dsg tunnel 1
group 1
client-list 1
dst-address 1111.2222.3333
classifier 1 10 192.168.3.6/32 239.1.1.8
indcd
classifier 2 11 0.0.0.0/0 239.100.1.9
indcd
Configure the DCD

parameters.
The following examples illustrate how to configure the DCD

parameters: dsg client-list 1 client 1 id-type macAddr idvalue xxxx.xxxx.xxxx vendor-param-id 1 dsg client-list 2
client 2 id-type broadcast id-value 2048 vendor-param-id 1.
CASA-CMTS(config)# dsg vendor-param-id 1
vendor 1 oui 1:1:0 value cj_vid
CASA-CMTS(config)# dsg channel-list 1
channel 1 frequency 567000000 dsg channellist 1 channel 2 frequency 573000000 dsg
channel-list 1 channel 3 frequency
579000000
CASA-CMTS(config)# dsg timer-id 1 t1 20 t2
30 t3 40 t4 50
431
CASA CMTS
Configure the DSD

message configuration
and enable it on a QAM
interface.

CASA-CMTS(conf-if-qam 0/0)# channel 0
channel-list 1
timer-id 1
vendor-param-id 1
interval 5
dcd-enable
dsg
dsg
dsg
dsg
dsg
Verify DSG DCD message and DSG data forwarding

To verify the DSG DCD message and DSG data forwarding, use the following show commands.
To show the counters of the DCD messages and DSG data packets sent through each
downstream interface:
CASA-CMTS# show dsg statistics [dcd | traffic]
To show multicast replication in general (DSG replication will be shown as well, if configured):
CASA-CMTS# show multicast replication
Configuring DOCSIS BPI/BPI+

Baseline Privacy Interface (BPI) is defined as a set of extended services within the DOCSIS MAC
sub-layer. BPI gives subscribers data privacy across the RF network, encrypting traffic flows
between the CMTS and CM.
Configuring shared-secret MIC
Adding a privacy certificate
Displaying the privacy certificate
Setting the privacy hotlist
Configuring the encryption algorithm
Managing the revocation certificate
Choosing the Revocation Certificate management method
Setting the CRL method refresh interval
Setting the CRL method URL address
Setting the OCPS client URL address
Setting the OCSP client signature
Displaying the Revocation Certificate method configuration
Displaying the CRL configuration
Displaying the OCSP configuration
432
CASA CMTS
Configuring the Source Address Verification rule

Enabling SAV authorization
Displaying the SAV configuration
Enabling the TFTP proxy
Configuring the TFTP proxy
Displaying TFTP proxy status
Configuring the EAE exclusion list
Adding CMs to the EAE exclusion list
Displaying the EAE exclusion List
Displaying BPI information
Configuring shared secrets to protect the modem configuration file

Because DOCSIS configuration files from an authorized TFTP server provide critical quality of
service (QoS) definitions and other data for cable modems, security measures must be applied to
protect the configuration file from unauthorized intercept, theft, substitution, and potential
modification.
The DOCSIS specification supports the shared-secret and shared-secondary secret
passwords to protect modem configuration files from possible tampering. Once configured, these
passwords calculate the CMTS Message Integrity Check (MIC) field that is attached to all
DOCSIS configuration files.
The shared-secondary-secret provides a second password should a cable modem fail to
authenticate with the primary shared-secret. With the secondary secret configured, the cable
modem must authenticate using either the primary or secondary password in order for the
modem to register and come online. Using a secondary secret allows CMTS operators to
frequently revise the primary password without interrupting a currently active and online cable
modem with a primary password update.
The CMTS supports a maximum of 198 shared secrets (primary, secondary, and
primary/secondary extended), including those shared secrets defined under the interface
docsis-mac configuration.
To configure a primary shared-secret:
Step
1
Command (config)
Purpose
shared-secret {0 | 7} <mic_string> [extend]
Configure a
shared-secret
password.
Where:
0
Specifies that an unencrypted message

(clear text) will follow.
Specifies that an encrypted message will

follow.
<mic_string>
MIC string used to encrypt and decrypt the

configuration file. String length is 1 to 32.
extend
Sets share-secret MIC for the extend TLVs

received from Reg-Req message.
433
CASA CMTS
Example:
To set the shared-secret for non-encrypted messages or
encrypted messages:
CASA-CMTS(config)# shared-secret 0 DOCSIS
To set share-secret MIC globally:
CASA-CMTS(config)# shared-secret DOCSIS
To set share-secret MIC for the extend TLVs received from RegReq message:
CASA-CMTS(config)# shared-secret DOCSIS extend
To unset shared-secret MIC:

CASA-CMTS(config)# no shared-secret
CASA-CMTS(config)# no shared-secret extend
show running-config | i secret
Example:
CASA-CMTS(config)# show running-config | i secret
shared-secret 7 d6ab86abb7242b65
Display the
configured
shared secret.
To configure up to two shared-secondary secrets:

Step
1
Command (config)
Purpose
shared-secondary -secret {1|2} {0|7} <mic_string> [extend]
Configure a
sharedsecondary secret
password.
Where:
{1|2}
Specifies the index number of the secondary

shared-secret, either 1 or 2. If two
secondary secrets are configure, the index
determines which secondary secret
password is checked first.
Specifies that an unencrypted message

(clear text) will follow.
Specifies that an encrypted message will

follow.
<mic_string>
MIC string used to encrypt and decrypt the

configuration file. String length is 1 to 32.
extend
Sets share-secret MIC for the extend TLVs

received from Reg-Req message.
Example:
To set the shared-secondary-secret for non-encrypted messages
or encrypted messages:
CASA-CMTS(config)# shared-secondary-secret 1 0
DOCSIS
To set the shared-secondary-secret MIC for the extend TLVs
received from Reg-Req message:
CASA-CMTS(config)# shared-secondary-secret 1 0 DOCSIS
extend
434
CASA CMTS
To remove shared-secret MIC:

CASA-CMTS(config)# no shared-secondary-secret 1
CASA-CMTS(config)# no shared-secondary-secret 2
extend
show running-config | i secret
Example:
CASA-CMTS(config)# show running-config | i secret
shared-secondary-secret 1 7 d6ab86abb7242b65
Display the
configured
sharedsecondary
secret.
Adding the privacy certificate (DOCSIS 3.0 only)

To add a manufacturer or root CA certificate to the list of trusted certificates, use the privacy addcertificate command in global configuration mode. To remove a particular certificate, use the no
form of this command.
Step
1
Command (config)
Purpose
[no] cable privacy add-certificate {manufacturer|root} <hexdata>
Add a
manufacturer or
root CA
certificate to the
list of trusted
certificates.
Where:
manufacturer
<hex-data>
Specifies the hexadecimal data for the

manufacturer CA certificate. Enter multiple
lines as needed, and use a blank line to
terminate the string.
root <hexdata>
Specifies the hexadecimal data for the root CA

certificate. Enter multiple lines as needed, and
use a blank line to terminate the string.
Example:
Add a manufacturer CA certificate to the CMTS list of trusted
certificates:
CASA-CMTS(config)# cable privacy add-certificate
manufacturer
35c146353431a541463b41337343938333373142
FEF03A8BC7A441313134749A0A592C9C66831412
Add a root CA certificate to the CMTS list of trusted certificates:
CASA-CMTS(config)# cable privacy add-certificate
root 00908300 00300501
308202A1 3082020A A0030201 02020800 90830000
00000130 0D06092A 864886F7
0D010105 05003081 92310B30 09060355 04061302
4A503110 300E0603 55040A13
07546F73 68696261 310F300D 06035504 0B130644
4F435349 53312730 25060355
040B131E 312D312D 31205368 69626175 7261204D
696E6174 6F2D6B75 20546F6B
435
CASA CMTS
796F3137
20436162
20526F6F
74686F72
30303331
30383030
30090603
1307546F
0D060355
55040B13
68696261
6B796F31
30350603
6C65204D
74204365
69747930
38303830
30305A30
55040613
73686962
040B1306
1E312D31
75726120
37303506
55040313 2E546F73
6F64656D
72746966 69636174
1E170D30
3030305A 170D3230
8192310B
024A5031 10300E06
61310F30
444F4353 49533127
2D312053
4D696E61 746F2D6B
03550403
68696261
65204175
30333138
0355040A
30250603
7520546F
Displaying the privacy certificate configuration (DOCSIS 3.0 only)

To show configuration of privacy certification:
Step
1
Command
Purpose
show cable privacy {manufacturer-cert-list | root-cert-list}
Show the
configuration of
privacy
certification for
manufacturer
certificates that
have been added
to the CMTS.
Where:
manufacturer- Displays the BPI manufacturer certificate
verification list.
cert-list
root-cert-list
Displays the BPI root certificate verification list.
Example:
Display BPI+ certificate information using the show cable privacy
command:
CASA-CMTS# show cable privacy manufacturer-certlist
Cable Manufacturer certificate chain:
<certificate dump>
CASA-CMTS# show cable privacy root-cert-list
Cable Root certificate chain:
<certificate dump>
Enforcing BPI and BPI+

The CMTS provides commands that enforce the Baseline Privacy Interface (BPI) and BPI+
security protocols running between the CMTS and the cable modems (CMs). BPI authentication
protocols protect cable modem data traffic by preventing upstream and downstream
eavesdropping by other users who are connected over the same cable. Traffic between the
CMTS and the CMs is encrypted using an encapsulation protocol, as well as a key management
protocol called Baseline Privacy Key Management (BKPM) for processing authentication and
authorization key exchanges between the CM and CMTS.
436
CASA CMTS
BPI+ is required on all DOCSIS 1.1 (and later) compliant cable modems. Earlier cable modems
use BPI.
bpi-enforce Enforces BPI-authenticated cable modem and prohibits traffic for non-BPI
authenticated cable modems. Data is not forwarded before a BPI-enabled cable modem
completes BPI initialization.
bpi-plus-enforce Enforces BPI-plus for DOCSIS 1.1 or later cable modems. When
enabled, cable modems running DOCSIS 1.1 or higher that are not running BPI-plus are
rejected.
Both options are disabled by default.

To enable BPI and BPI+ enforcement:
Step
1
Command (config)
Purpose
[no] cable privacy bpi-enforce

[no] cable privacy bpi-plus-enforce
Enable
enforcement of
BPI and BPI
plus.
Example:
To enable BPI and BPI+ enforcement:
CASA-CMTS# cable privacy bpi-enforce
CASA-CMTS# cable privacy bpi-plus-enforce
Use the no form

of the command
to disable the
current setting.
Setting the privacy hotlist (DOCSIS 3.0 only)

To mark a manufacturer's or CM certificate as distrusted and to add the certificate to the CMTS
hotlist of invalid certificates to prevent those CMs from registering, use the privacy hotlist
command in global configuration mode. To remove a particular CM or manufacturer's certificate
from the hotlist, use the no form of this command.
Step
1
Command (config)
Purpose
[no] privacy hotlist {cm <mac-address> | manufacturer <certserial-number>}
Mark a
manufacturer's or
CM certificate as
distrusted and
add them to the
CMTS hotlist.
Where:
cm mac-addr
Specifies the MAC address for the CM

certificate to be added to the hotlist. The macaddress should be specified as a hexadecimal
string, without periods or other separators.
437
CASA CMTS
manufacturer
cert-serialnumber
Specifies the serial number for the particular

manufacturer CA certificate. The cert-serialnumber should be specified as a hexadecimal
string up to 32 bytes in length. Enter multiple
lines as needed, and use a blank line to
terminate the string.
Example:
Add the CM certificate with the MAC address of 00C0.8345.de51
to the hotlist, so that this particular CM cannot register with the
CMTS:
CASA-CMTS(config)# privacy hotlist cm
00C08345de51
CASA-CMTS(config)#
Add a manufacturer CA certificate into the BPI+ hotlist, so that the
CMTS will reject any CM attempting to register with a certificate
from that particular manufacturer:
CASA-CMTS(config)# privacy hotlist manufacturer
1eabdef39b3f171c2e89c6df1143e40b21e4a1b29acc2d906
4a30263167eb001053e419c8742842ab74778f07328f5c842
768e3136b1068117a1f9f5c8493c606996fa4d6b362ee87ff
403f85c41cfae80d5cc123515c3fe3f1e26f2bef2195f92b2
5b63516961ebce0e89c9b6277ad98cdf414e0203a031cfb44
54738e986af1ba42a0355bf7f21ba34f0567780a800172fa9
bd99bcad4afb8909026083ac9a0d638298b8873e3e4c8a6e5
1d057aa366e53c9917886fc0ac5a31848ca57eae79cdd7d8e
fb2b0e4e100143fcd126f59acb5891fcba76e497472d08111
d84472cbb4a4c6b1d90203010001a326302430120603551d1
30101ff040830060101ff020100300e0603551d0f0101ff04
0403020106300d06092a864886f70d0101050500038201010
09cbca0b3ee06d0ac1198291eef1bde42040cbfb442f72492
44866d3e1385365454449ced03b6da62218d0baa59c332ae7
9288aaba988d457161670eb77ebfd8eb4b7a545f1c8a9cbf6
a52b7e2b8d65ad1369ac831ecdc3aec0cc2b24d199f971b0c
9add78d6a75cc0e1b04d4c005dcae67543d205be2f39c0651
50a756555d965cb941d8b5eb92afbc8c0ac9ee880c989f53d
0c5f8408a5ca679b0e65b198e33791ca347e30eb373a82243
ac63ac8440faa83e1486a59ec991352f4d31e434551a258f6
f60564c88e9d91e22917be8557a63472bb8bd2cc8bd0ba36a
b826db3e6fc8a572a6c2fbff6c736df5cb970a900b4f6ba4f
5a7e53e38b87325c08934ef
CASA-CMTS(config)#
Configuring an encryption algorithm

Casa CMTS supports three encryption algorithms: 40-bit-des, 56-bit-des, and 128-bit-aes.
To force a CM use 40-bit-des algorithm for data traffic encryption, perform the following. Note, if
CMs do not support 40-bit-des encryption algorithm, the CMs will not be able to complete BPI.
438
CASA CMTS
Step
1
Command (config)
Purpose
[no] cable privacy 40-bit-des
Set the cable

encryption
algorithm to 40bit-des.
Example:
CASA-CMTS(config)# cable privacy 40-bit-des
To set encryption algorithms with priorities:

Step
1
Command (config)
Purpose
cable sec encrypt-alg-priority <alg1> [<alg2> <alg3>]
Set the
encryption
algorithm priority
when more than
one encryption
algorithm is set.
Where:
<alg1>, <alg2> One of the three encryption algorithms:
- aes128CbcMode 128 bit AES
and <alg3>
- des40CbcMode 40 bit DES
- des56CbcMode 56 bit DES
If more than one algorithm is set, the CMTS will
choose the highest priority algorithm which the
CM supports for data traffic encryption.
Example:
CASA-CMTS(config)# cable sec encrypt-alg-priority
aes128CbcMode des40CbcMode des56CbcMode
Managing revocation certificates

The Casa CMTS provides following CLI commands in managing revocation certificate:
Choosing the management method for revocation certification
Setting the CRL method refresh interval
Setting the CRL method URL address
Setting the OCPS client URL address
Setting the OCPS client signature
Displaying the revocation method configuration
Displaying the OCPS configuration
Choosing a revocation certificate management method

To choose a method:
Step
1
Command (config)
Purpose
[no] cable sec cert-revocation-method [crl | crlAndOcsp |

none | ocsp]
Choose the
method.
Where:
439
CASA CMTS
crl
Management method for CRL
crlAndOcsp
Management method for CRL and OCSP
ocsp
Management method for OCSP
none
No revocation certificate
Example:
CASA-CMTS(config)# cable sec cert-revocationmethod crl
Setting a CRL method URL address

Once the CRL or the crlAndOcsp method is chosen, a URL address should also be set.
To set a URL address:
1
Purpose
[no] cable sec cert-revocation-list url <url_string>
Set a URL
address.
Where:
<url_string>
URL address, such as http://www.revocert-list.com.
Example:
CASA-CMTS(config)# cable sec cert-revocation-list
url http://www.cert.com
Setting an OCSP client URL address

Once ocsp or crlAndOcsp method is chosen, a URL address should also be set.
To set URL address:
Step
1
Command (config)
Purpose
[no] cable sec ocsp protocol-url <url_string>
Set a URL
address
Where:
<url_string>
URL address of ocsp client (usually is

CMTS).
Example:
CASA-CMTS(config)# cable sec ocsp protocol-url
http://www.ocsp.net
Setting an OCSP client signature

Once ocsp or crlAndOcsp method is chosen, a client should also be set.
440
CASA CMTS
To set client signature:

Step
1
Command (config)
Purpose
[no] cable sec ocsp signature-bypass
Set a client
signature.
Example:
CASA-CMTS(config)# cable sec ocsp signaturebypass
Displaying the revocation certificate configuration

To show configured revocation certificate method:
Step
1
Command (config)
Purpose
show cable sec certrevocation-method
Show configured
revocation
certificate
method.
Example:
CASA-CMTS(config)# show cable sec cert
revocation-method
cable sec cert-revocation-method ocsp

To show the CRL configuration:
Step
1
Command (config)
Purpose
show cable sec cert-revocation-list [url | refresh-interval]
Show the CRL

configuration.
Example:
CASA-CMTS(config)# show cable sec cert-revocationlist
cable sec cert-revocation-list url
http://www.cert.com
cable sec cert-revocation-list refresh-interval 10
Displaying the OCSP configuration

To display the OCSP configuration:
Step
1
Command (config)
Purpose
show cable sec ocsp [protocol-url | signature-bypass]
Show the OCSP

configuration.
Example:
CASA-CMTS(config)# show cable sec ocsp
cable sec ocsp protocol-url http://www.ocsp.net
no cable sec ocsp signature-bypass
Configuring the source address verification rule

For more information on source address verification (SAV), see the next section. To set a rule for
a SAV (Source Address Verification) group:
441
CASA CMTS
Step
1
Command (config)
Purpose
[no] cable sec sav-cfg-list <group_name> <rule_id>

[<ipv4_addr> | <ipv6_addr>]
Set a rule for a

SAV group.
Where:
<group_name>
SAV group name. String length is 1 to 32

characters.
<rule_id>
Rule ID in the range 1 to 4,294,967,295.
<ipv4_addr>
Version 4 IP address in the format

xxx.xxx.xxx.xxx/mask_len
<ipv6_addr>
Version 6 IP address in the format

xxxx:xxx:..:xxx/mask_len
Example:
CASA-CMTS(config)# cable sec sav-cfg-list
OneSubNet 1 10.150.3.1/24
CASA-CMTS(config)# cable sec sav-cfg-list Ipv6Exp
1 ipv6 2001:180::1/64
Enabling SAV authorization

To enable or disable SAV authorization globally:
Step
1
Command (config)
Purpose
[no] cable sec sav-auth-enable
Enable SAV
authorization
globally.
Example:
CASA-CMTS(config)# cable sec sav-auth-enable
CASA-CMTS(config)# no cable sec sav-authenable
Use the no form of

the command to
disable authorization.
Displaying the SAV configuration

To show rules for all SAV groups:
Step
1
Command (config)
Purpose
show cable sec sav-cfg-list[ <group_name> <rule_id>]
Show rules of all

existing SAV
groups. If no
options are
specified, all
rules are shown.
Where:
<group_name>
SAV group name. String length is 1 to 32

characters.
<rule_id>
Rule ID in the range 1 to 4,294,967,295.
Example:
442
CASA CMTS
CASA-CMTS(config)# show cable sec sav-cfg-list

cable sec sav-cfg-list Ipv6Exp 1 ipv6
2001:180:0:0:0:0:0:1/64
cable sec sav-cfg-list OneSubNet 1 10.150.3.1/24
Enabling configuration file learning

When config-file-learning is enabled, the CMTS will record the CMTS-MIC and CM-MIC from the
received configuration file.
To enable or disable the config-file-learning:
Step
1
Command (config)
Purpose
[no] cable sec config-file-learning
Enable or disable
config-filelearning.
Example:
CASA-CMTS(config)# cable sec config-file-learning
CASA-CMTS(config)# no cable sec config-filelearning
Configuring TFTP proxies

Once an option for TFTP proxies is configured, the CMTS will add the corresponding address into
the TFTP message. To configure TFTP proxy:
Step
1
Command (config)
Purpose
cable sec tftp-option [both | hw-addr | net-addr | none]
Configure TFTP
proxy.
Where:
both
Both hardware address and net address

will be added.
hw-addr
Only hardware address will be added.
net-addr
net-addr: only net address will be added.
none
Neither hardware address nor net

address will be added.
Example:
CASA-CMTS(config)# cable sec tftp-option both
Displaying config file learning status

To display config-file-learning status:
Step
1
Command (config)
Purpose
show cable sec config-file-learning
Display config-file-
443
CASA CMTS
learning status.
Example:
CASA-CMTS(config)# show cable sec config-filelearning
no cable sec config-file-learning
Displaying the TFTP option setting

To show the TFTP option setting:
Step
1
Command (config)
Purpose
show cable sec tftp-option
Display TFTP
options setting.
Example:
CASA-CMTS(config)# cable sec tftp-option
cable sec tftp-options both
Configuring the EAE exclusion list

The Casa CMTS supports the capability of excluding individual CMs from EAE enforcement
based on their MAC addresses. To add or remove an EAE exclusion list:
Step
1
Command (config)
Purpose
[no] cable sec eae-exclusion <list_id>
Add an EAE
exclusion list.
Where:
<list_id>
EAE exclusive list ID in the range 1 to

4,294,967,295.
Example:
CASA-CMTS(config)# cable sec eae-exclusion 1
0015.f2fe.c904
Use the no form

of the command
to remove the
exclusion list.
Adding cable modems to the EAE exclusion list

Once a MAC address is added into the exclusion list, the CMTS will not allow the cable modem at
the specified MAC address to perform EAE. To add a MAC address to the existing EAE
exclusion list:
Step
1
Command (config)
Purpose
[no] cable sec eae-exclusion <list_id> <mac_addr>
Add a MAC
address to an
existing EAE
exclusion list.
Where:
<list_id>
EAE exclusive list ID, values are 1 to

4,294,967,295.
<mac_addr>
MAC address of the CM in format
Use the no form

444
CASA CMTS
xxxx.xxxx.xxxx.
Example:
CASA-CMTS(config)#cable sec eae-exclusion 1
0050.f112.b764
of the command
to remove the
MAC address
from the
exclusion list.
Displaying the EAE exclusion list

To show the EAE exclusion list:
Step
1
Command (config)
Purpose
show cable sec eae-exclusion
Display the EAE

exclusion list.
Example:
CASA-CMTS(config)# show cable sec eae-exclusion
cable sec eae-exclusion 1 0015.f2fe.c904
ffff.ffff.ffff
Source Address Verification (SAV)

When dhcp-authorization is disabled on a DOCSIS MAC domain, anyone can assign their own IP
address. This may cause conflicts and may not be desirable by the service provider. One secure
way to allow customers authorized by their ISPs to use static IP addresses is to enable DHCP
authorization and use the Source Address Verification (SAV) feature of DOCSIS/CMTS/CM. To
do this, the CM receives a configuration file with SAV Group Name Subtype encoded.
For example (docsis -d sav_merlin.bin):
Main
{
NetworkAccess 1;
VendorSpecific
{
VendorIdentifier 0xffffff;
GenericTLV TlvCode 7 TlvLength 8 TlvValue
0x01066d65726c696e;
}
MaxCPE 16;
UsServiceFlow
{
UsServiceFlowRef 1;
QosParamSetType 7;
SchedulingType 2;
}
DsServiceFlow
{
DsServiceFlowRef 2;
QosParamSetType 7;
}
445
CASA CMTS
/* CmMic 49b9d8d459f9a9119f43188372a00422; */
/* CmtsMic 0dc1e7ce52cb806a57f13d9eea9c4db8; */
/*EndOfDataMkr*/
)
In the config file above, the TLV value for SAV Group Name Subtype is merlin (in hex format:
6d65726c696e). When the CM registers with the CMTS, the CMTS will note the SAV for the CM.
The CMTS must be configured as:
CMTS(config)#cable sec sav-cfg-list merlin 1 192.168.7.77/32
192.168.7.77 is the static IP used by the CPE. The 32-bit mask specifies only this IP. Use a
mask to allow a contiguous range of IP addresses. The number 1 after the merlin string is the
SAV Group Name Subtype.
By default the dhcp-authorization is enabled. Unauthorized IP addresses are not allowed. The
cable modem security configuration will allow authorized IPs behind a given CM. By default, cab
sec sav-auth-enable command is enabled.
To authorize an individual MAC address without changing the modem config file, use the
following command:
Step
1
Command (config)
Purpose
[no] cable host authorization <mac_addr> <ip_address>
Authorize
individual cpe
MAC address.
Where:
<mac_addr>
CPE MAC address in the format:

xxxx.xxxx.xxxx
<ip_address>
CPE IP address in the format: A.B.C.D
Example:
CASA-CMTS(config)# cable sec eae-exclusion 1
0015.f2fe.c904
To authorize an IP address or IP subnet (specified in SAV config list) for a specified CM:
Step
1
Command (config)
Purpose
[no] cable host authorization <mac_addr> <string>
Authorize an IP
address or IP
subnet (specified
in SAV config
list) for a
specified CM.
Where:
<mac_addr>
CPE MAC address in the format:

xxxx.xxxx.xxxx
<string>
SAV config list name.
Example:
CASA-CMTS(config)#cable sec sav-cfg-list host1 1
192.168.9.0/24
446
CASA CMTS
Leasequery
Use the DHCP leasequery command to configure the Casa CMTS to send DHCP lease query
requests to the DHCP server. Ensure that the dhcp-authorization parameter on the docsis-mac
interface is currently enabled (default). Since leasequery uses the dhcp.conf file at the DHCP
server, do not set an IP address on CPE/PC devices. The TCP/IP properties on these devices
must be set so that IP addresses are obtained automatically from the dhcpd.conf host setting.
At the DHCP server, you will need to modify the dhcp.conf as follows:
/etc/dhcpd.conf
allow leasequery;
<---- Enables dhcp lease query on the DHCP server
host cpe_lab {
hardware ethernet 00:14:22:fa:87:19; <----MAC address of cpe/pc
fixed-address 10.10.9.202;
<----Note this must not be a host IP in the
option routers 10.10.9.1;
IP bundle range
<----IP secondary address gateway from the
IP bundle setting
}
subnet 10.10.9.0 netmask 255.255.255.0 {
default-lease-time 3000000; # 5 min
max-lease-time 31557600;
# one year
option routers 10.10.9.1;
filename "cm231.cfg";
next-server 192.168.9.1;
option time-offset -18000;
option time-servers 192.168.9.1;
option log-servers 192.168.9.1;
option bootfile-name "cm231.cfg";
option tftp-server-name "192.168.9.1";
range 10.10.9.100 10.10.9.200;
<-----IP bundle host range
}
Step
1
Command (config)
Purpose
dhcp leasequery enforce

dhcpv6 leasequery [enforce]
Configure the
Casa CMTS to
send DHCP
lease query
requests to the
DHCP server.
Example:
CASA-CMTS(config)#dhcp leasequery enforce
447
CASA CMTS
show running-config | i leasequery

Example:
CASA-CMTS(config)#show running-config | i
leasequery
dhcp leasequery enforce
Display the
current lease
query setting.
This allows IP addresses of the CPE to be verified. The DHCP server will return an
acknowledgement message that contains the MAC address of the CPE assigned to this IP
address, if there is one. This function will not interfere with valid RF traffic while it prevents users
from assigning unauthorized IP addresses to CPE.
The default configuration for these commands is off. DHCP authorization must also
be enabled in the MAC domain for lease queries to be sent.
If dhcpv6 leasequery is set, a leasequery will be sent to the DHCP server when a
packet with a source IPv6 address (that is not present in the ARP and local DHCPv6
CPE lease table) is received.
If dhcpv6 leasequery enforce is set, a leasequery will be sent when a packet with a
source IPv6 address (that is not present in the ARP table) is received.
The messages returned from the server have the following default values:
30 query
31 - unassigned
32 unknown
33 active
To change the default coding:
Step
1
Command (config)
Purpose
dhcp leasequery message-coding
Change the
default coding
Example:
CASA-CMTS(config)#dhcp leasequery message-coding
Press the tab key to get 1-query and enter a value (up to 2 digits) for the message type and a
space. Tab over on the same command line to get 1-unassigned and type up a value (up to two
digits) and a space. Repeat for 1-unknown and 1-active.
Spectrum management
Casa Spectrum Management (CSM) allows the Casa CMTS to monitor the quality of upstream
paths and automatically perform correcting actions when upstream plant impairments are
detected. The monitored upstream plant impairments include Signal to Noise Ratio (SNR),
correctable FECs, and uncorrectable FECs. The automatic corrections include frequency
hopping, upstream channel-width adjustment, and dynamic upstream modulation profile changes.
CSM also provides a means to report the configurations, actions, and some test facilities.
448
CASA CMTS
This section describes briefly the algorithm of CSM, and then the operation commands.
Creating spectrum rules

Setting the frequency band
Setting hopping periods and priorities
Setting the channel-width adjustment range
Specifying the modulation profile
Setting the FEC threshold
Assigning spectrum rules to upstream interfaces
Setting the monitoring period
Displaying the spectrum map
Displaying the spectrum noise level
Enabling and disabling CM hopping
Displaying and removing CM hopping history
CSM algorithm
Casa Spectrum manager uses the Fast Fourier Transform (FFT) technique to monitor signal
quality on the return path. The FFT screening results, SNR and FEC errors in particular, are the
main error events monitored to determine whether plant noise exists and corrective actions are
necessary. Corrective action(s) can be one, two or all three of: frequency hopping, channel width
adjustment, and dynamic modulation profile change.
Spectrum manager maintains a list of discrete channel frequencies and/or one or more frequency
bands for each upstream interface as frequency hopping targets. This is called the spectrum
map. CSM scans through the spectrum map to select the cleanest channel. The spectrum map is
updated when a hop is performed. CSM uses spectrum rule to manage the corrective actions. A
spectrum rule consists of a set of thresholds and a sequential list of actions. An action can be
frequency hopping, channel width adjustment, or modulation profile. A FFT procedure is triggered
when a monitored indicator to an upstream interface hits a defined or default threshold.
The actions take place in an order defined by the operator in the action commands. If plant signal
quality is maintained within the thresholds due to one or more actions, the subsequent actions in
a rule will not be performed since it is not necessary.
If the upstream channel signal with corrected modulation and/or adjusted channel width returns to
3 dB above normal, the spectrum manager may roll back the settings to their original channel
width or modulation profile setting. The hop back threshold can also be specified in the CLI.
To activate CSM on specified upstream interfaces, spectrum rules need to be defined and
assigned to upstream interfaces.
449
CASA CMTS
Spectrum management procedures

Creating spectrum rules
To create a spectrum rule or to enter the spectrum rule setting mode:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum rule or
enter spectrum
rule setting
mode.
Where:
<id>
Spectrum rule ID number. Valid values are 1

to 40.
Example:
CASA-CMTS(config)# spectrum rule 2
CASA-CMTS(conf-spec-rule 2)#
Exiting spectrum rule mode

To exit from spectrum rule setting mode:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum rule or
enter spectrum
rule setting
mode.
Where:
<id>

to 40.
Example:
end
Example:
CASA-CMTS(config-spec-rule 2)# end
CASA-CMTS(config)#
Exit from the

spectrum rule
setting mode.
Setting a frequency band

To set a frequency band:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum rule or
enter spectrum
rule setting
mode.
Where:
<id>

to 40.
450
CASA CMTS
Example:
2
Set or remove a
frequency band.
[no] frequency band <freq1> <freq2>

Where:
<freq1>
Left edge of the frequency band, unit in Hz.

Right edge of the frequency band, unit in Hz.
<freq2>
Example:
Set two frequency bands, 14-20 and 30-60 MHz, to spectrum rule
2:
CASA-CMTS(conf-spec-rule 2)# frequency band
14000000 20000000
30000000 60000000
Remove frequency band 30-33 MHz from a
spectrum group:
defined

14000000 20000000
30000000 60000000
CASA-CMTS(conf-spec-rule 2)# no frequency band
30000000 33000000
CASA-CMTS(conf-spec-rule 2)# show running-config
spectrum rule 2
frequency band 14000000 20000000
Setting a discrete frequency

To set a discrete frequency:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum rule or
enter spectrum
rule setting
mode.
Where:
<id>
Spectrum rule ID number. Valid values are 1 to 40.
Example:
2
frequency <freq>
Set or remove a
frequency band.
451
CASA CMTS
Where:
<freq>
Frequency in Hz.
Example:
CASA-CMTS(conf-spec-rule 2)# frequency 34000000
Note: After the spectrum rule is assigned to an upstream interface, the discrete frequency
becomes a frequency band with the same width as that of the upstream interface
Setting the hopping period

This command sets a time period between two consecutive frequency hops. This period allows
new channels to stabilize before making a frequency hopping decision to assign the traffic to
cleaner unstream channels.
To set the hopping period:
Step
Command (config)
Purpose
hop period <time>
Specifies the
time period to
transpire before
a frequency hops
to a cleaner
channel.
Where:
<time>
Specifies the hopping period in seconds. Valid

values are 1 to 3,600. The default is 30 seconds.
Example:
CASA-CMTS(config)# hop period 100
Setting the hopping priority

This command specifies the order of effort of trying correcting actions (frequency hopping,
upstream channel-width adjustment, and dynamic upstream modulation change). There is no
default action or default order of actions. The action(s) has to be explicitly specified in the action
command.
To set the priority:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum
rule or enter
spectrum
rule setting
mode.
Where:
<id>
Example:
2
action frequency modulation channel-width

or
Set the
frequency
hopping
452
CASA CMTS
or
action frequency channel-width modulation
priority.
Example:
Note: Frequency hopping will not occur if no frequency band is specified to a spectrum rule.
Modulation profile change will not occur if the no secondary profile defined in the upstream.
Channel-width adjustment will not occur if no channel width range specified.
Setting the channel-width adjustment range

To set the channel-width adjustment range:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum
rule or enter
spectrum
rule setting
mode.
Where:
<id>
Example:
2
[no] channel-width <start-width> <end-width>

Where:
<start-width>
<end-width>
Start channel-width in Hz. Valid values are

400000, 800000, 1600000, 3200000, and
6400000.
Set the
channelwidth
adjustment
range.
End channel-width in Hz. Valid values are

200000, 400000, 800000, 1600000, and
3200000, and should also be less or equal to
the specified start-width.
Example:
CASA-CMTS(conf-spec-rule 2)# channel-width 3200000
1600000
Note: If the specified start-width is larger than current effective width, channel-width change
starts from start-width. Otherwise, the change starts with current effective width.
To return the channel width to its default setting of 1,600,000 Hz for a specified spectrum rule,
enter the following command:
Specifying a modulation profile SNR

To specify a modulation profile SNR threshold:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
453
CASA CMTS
Where:
<id>
Example:
[no] profile <id> snr-threshold <tenth-dB>
Where:
<id>
<tenth-dB>
Modulation profile ID which can be predefined

or user defined.
spectrum
rule or enter
spectrum
rule setting
mode.
Specify a
modulation
profile SNR
threshold.
SNR threshold number in units of tenth dB.
Example:
Specify profiles 3 and 4 to spectrum rule 2 with SNR 130 and 200:
CASA-CMTS(conf-spec-rule 2)# profile 3 snr-threshold
130
200
To remove a spectrum rule profile:
CASA-CMTS(conf-spec-rule 2)# no profile 3
Note: 0 or more profiles with an SNR threshold can be specified for a spectrum rule.
Casa Spectrum Management (CSM) uses the SNR threshold of a modulation profile for two
purposes:
1. One of the three triggers (SNR, correctable FEC and uncorrectable FEC) for possible
corrective actions.
2. As a reference to evaluate a calculated SNR (based on FFT data) is sufficient for a particular
modulation profile in an effort of corrective or improvement action.
Specifying a modulation profile SNR threshold

If no SNR threshold is specified for a modulation profile in a spectrum rule, it defaults to 0. This
means the SNR will not be a trigger for a possible action if an upstream channel is using this
modulation profile (number 1 above). Only correctable FEC and uncorrectable FEC are possible
triggers to start a corrective action.
To prevent SNR from triggering a possible corrective action for a particular modulation profile, do
not specify the SNR threshold for the modulation profile, or use the following command:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum
rule or enter
spectrum
rule setting
Where:
<id>
454
CASA CMTS
to 40.
mode.
Example:
2
profile <id> snr-threshold 0

Where:
<id>
Modulation profile ID which can be

predefined or user defined.
Specify a
modulation
profile SNR
threshold
setting to 0.
Example:
0
Specifying the hop-back threshold

To set the threshold for hopping back:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum
rule or enter
spectrum
rule setting
mode.
Where:
<id>

to 40.
Example:
2
profile <id> snr-threshold <first> [<second>]

Where:
<id>
Modulation profile ID which can be

predefined or user defined.
<first>
The threshold for hopping to the next profile.
<second>
The threshold for hopping back to the

original profile. When <second> is
configured, CSM will use <second> as hopback threshold instead of <first> + 3dB.
Set the
threshold for
hopping
back.
Example:
100
455
CASA CMTS
Default SNR threshold for different modulations

CSM has a built-in default SNR threshold for each modulation type and for each modulation
profile. The default SNR threshold takes effect for a spectrum rule, if there is no threshold
specified in a spectrum rule for a particular modulation profile.
CASA-CMTS#show spectrum snr-threshold-default
Default SNR threshold per modulation type (tenth dB):
Modulation Conservative
Addressive
QPSK:
130
100
8QAM:
190
160
16QAM:
220
190
32QAM:
250
220
64QAM:
280
250
128QAM:
310
290
Setting the FEC threshold

To set the correctable-FEC threshold:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum
rule or enter
spectrum
rule setting
mode.
Where:
<id>

to 40.
Example:
2
correctable-fec threshold <percentage>

Where:
<percentage>
Correctable-fec threshold percentage. Valid

values are 0 to 100. The default is 3.
Set the
correctableFEC
threshold.
Example:
CASA-CMTS(conf-spec-rule 2)# correctable-fec
threshold 5
To set the uncorrectable-FEC threshold:
Step
Command (config)
Purpose
spectrum rule <id>
Create a
spectrum rule
or enter
spectrum rule
setting mode.
Where:
<id>

to 40.
456
CASA CMTS
Example:
2
uncorrectable-fec threshold <percentage>

Where:
<percentage>
Set the
uncorrectableFEC threshold.
Uncorrectable-fec threshold percentage.

Valid values are 0 to 30. The default is 1.
Example:
CASA-CMTS(conf-spec-rule 2)# uncorrectable-fec
threshold 0
Assigning a spectrum rule to an upstream interface

To assign a spectrum rule to an upstream interface:
Step
1
Command (config)
Purpose
interface upstream <int_id>
Enter
interface
configuration
mode.
Where:
<int_id>
The interface ID.
Example:
spectrum-rule <id>
Where:
<id>
Spectrum rule ID (1 40)
Assign a
spectrum
rule to an
upstream
interface.
Example:
CASA-CMTS(config-if-ups 1/2)# spectrum-rule 2
With a spectrum rule assigned to an upstream interface, the actions defined in the rule will take
place in the specified (or default) order of priority if:
Plant noise level exceeds SNR threshold defined explicitly in the commands or by default
Percentage of correctable FEC errors of total packets received on the upstream (during
polling period) exceeds the defined or default threshold
Percentage of un-correctable FEC errors of total packets received on the upstream (during
polling period) exceeds the defined or default threshold
A rule can be assigned to any number of upstream interfaces. However, only one rule assignment
per upstream interface is allowed.
457
CASA CMTS
Assigning the secondary profile to an upstream interface

To assign the secondary profile to an upstream interface:
Step
1
Command (config)
Purpose
interface upstream <int_id>
Enter
interface
configuration
mode.
Where:
<int_id>
The interface ID.
Example:
CASA-CMTS(config)# interface upstream
2
logical-channel <id> profile <p> secondary-profile <s>

Where:
<id>
Spectrum rule ID (1 40).
<p>
ID of primary modulation profile.
<s>
ID of secondary modulation profile.
Assign a
spectrum
rule to an
upstream
interface.
Example:
Assign primary profile 1 and secondary profile 5 to upstream interface
1/2:
profile 1 secondary-profile 5
Note: Both profiles have to match the upstream channel type. CSM will not change to a
mismatched profile. The secondary profile has to be less bandwidth-efficient than the primary
one. When plant signal quality deterioration causes any one of the (correctable-FEC,
uncorrectable-FEC of profile P) thresholds hits, CSM changes modulation profile to S (show
running-config will show transit config as logical-channel id profile S secondary-profile S).
When signal quality (calculated SNR, based on FFT) satisfies profile Ps SNR (or default SNR
threshold for profile Ps modulation type, if SNR threshold for profile P is not defined in the rule)
plus 3dB, CSM changes modulation profile back to P.
Specifying multiple secondary profiles to an upstream interface

(Release 5.4 only)
Multiple (up to 5; 2 in 5.2) secondary profiles can be specified for an upstream interface, so
multiple steps can be achieved for dynamic modulation profile change.
CASA-CMTS(config-if-ups 1/2)# logical-channel 0 profile 3 secondaryprofile 12,20,33
Where:
1. Modulation profile 12, 20 and 33 have compatible channel types.
2. The order of 12,20,33 specifies the priority which CSM tries to use the profiles.
3. Lower priority suggests a less bandwidth efficient modulation profile.
458
CASA CMTS
Setting the monitoring period

CSM monitors the quality of all upstream channels by periodically polling measured parameters
of SNR, correctable and uncorrectable FECs. The user can configure this monitoring period. The
default setting is 30 seconds.
To configure the polling period:
Step
1
Command (config)
Purpose
cable monitor-period <seconds>
Configure
the polling
period.
Where:
<seconds>
Polling period in second. Valid values are 1

to 3600.
Example:
Set monitoring polling-period to 100 seconds:
CASA-CMTS(config)# cable monitor-period 100
Displaying hopping history

To display hopping history:
Step
1
Command (config)
Purpose
show spectrum hop-history [upstream X/Y]
Displays the
hopping
history.
Example:
CASA-CMTS# show spectrum hop-history upstream 1/4
Port
Action Time
Code From
To
Reason
1/4/0
Mon Oct 26 22:12:26 2009
C
800000
1600000
SNR 283 (220)
1/4/0
Mon Oct 26 22:11:26 2009
C
1600000
800000
SNR 243 (220) cFEC 0 (3) uFEC 3 (1)
1/4/0
Mon Oct 26 21:34:26 2009
C
3200000
1600000
SNR 210 (220) cFEC 90 (3) uFEC 0 (1)
1/4/0
Mon Oct 26 21:33:56 2009
C
800000
3200000
SNR 281 (220)
1/4/0
Mon Oct 26 21:32:56 2009
M
12
22
SNR 285 (220) cFEC 0 (3) uFEC 20 (1)
1/4/0
Mon Oct 26 21:32:26 2009
C
1600000
800000
SNR 252 (250) cFEC 6 (3) uFEC 6 (1)
1/4/0
Mon Oct 26 21:31:56 2009
C
800000
1600000
SNR 288 (250)
1/4/0
Mon Oct 26 21:31:26 2009
C
1600000
800000
SNR 254 (250) cFEC 5 (3) uFEC 0 (1)
1/4/0
Mon Oct 26 21:30:56 2009
C
3200000
1600000
SNR 218 (250) cFEC 113 (3) uFEC 0 (1)
1/4/0
Mon Oct 26 21:30:26 2009
C
800000
3200000
SNR 285 (250)
1/4/0
Mon Oct 26 21:29:56 2009
C
1600000
800000
SNR 247 (250) cFEC 38 (3) uFEC 0 (1)
459
CASA CMTS
1/4/0
1600000
1/4/0
800000
1/4/0
1600000
1/4/0
800000
1/4/0
1600000
1/4/0
6400000
1/4/0
12
1/4/0
10
1/4/0
800000
1/4/0
3
1/4/0
6400000
1/4/0
17000000
Mon Oct 26 21:29:26 2009

C
800000
SNR 282 (250)
Mon Oct 26 21:28:26 2009
C
1600000
SNR 258 (250) cFEC 4 (3) uFEC 0 (1)
Mon Oct 26 21:27:56 2009
C
800000
SNR 281 (250)
Mon Oct 26 21:26:56 2009
C
1600000
SNR 253 (250) cFEC 13 (3) uFEC 0 (1)
Mon Oct 26 21:26:26 2009
C
6400000
SNR 192 (250) cFEC 100 (3) uFEC 19 (1)
Mon Oct 26 21:25:56 2009
C
800000
SNR 288 (250)
Mon Oct 26 21:20:26 2009
M
10
SNR 283 (250) cFEC 0 (3) uFEC 25 (1)
Mon Oct 26 21:19:56 2009
M
3
SNR 286 (290) cFEC 0 (3) uFEC 3 (1)
Mon Oct 26 21:18:26 2009
C
6400000
SNR 211 (280) cFEC 202 (3) uFEC 0 (1)
Mon Oct 26 21:17:25 2009
M
0
Configuration change
Mon Oct 26 21:17:25 2009
C
0
Mon Oct 26 21:17:25 2009
F
0
Displaying the spectrum map

The spectrum map is a collection of possible frequency slots for the frequency hopping operation
to target. The map is dynamic for each upstream channel. It depends on the frequency ranges
defined in the rule and the current frequency used by other channels in the same Service Group.
The operator does not need to be concerned about frequency overlap in the same Service Group
(fiber node). It is recommended to use larger frequency ranges as hopping targets.
To display the spectrum map for an upstream interface:
Step
1
Command (config)
Purpose
show spectrum-map upstream <X/Y>
Displays the
spectrum
map.
Where:
<X/Y>
Upstream interface indices. X is module

index; Y is port index.
Example:
CASA-CMTS(config)# show spectrum-map upstream 1/2
Spectrum Map for interface 1 /2.0
band 0: [18000000, 20000000] ...narrower than
current chan-width 3200000
band 1: [22000000, 25400000]
band 2: [28600000, 40000000]
band 3: [58400000, 61600000]
460
CASA CMTS
Note: A frequency band narrower than current chan-width of the

channel will not be useful in frequency hopping.
Displaying the spectrum noise level

To display the spectrum noise level for all possible upstream frequencies at channel-width
3.2MHz:
Step
1
Command (config)
Purpose
show spectrum upstream <X/Y> [channel-width <chan_width>]

[raw]
Displays the
spectrum
map.
Where:
<X/Y>

<chan_width>
By channel width. Valid values are 200000,

400000, 800000, 1600000, 3200000 and
6400000.
raw
In dB. In the 5.4 release, if raw is added to

the show spectrum upstream command, the
result is showed in dB. Without this
parameter, the result is displayed in dBmV.
Example:
Display spectrum noise levels for upstream interface 2/0:
CASA-CMTS(config)# show spectrum upstream 2/0 raw
FREQUENCY NOISE-LEVEL at channel-width 3200000
(dBmV)
5000000: -42.1
8200000: -42.1
11400000: -42.1
14600000: -42.1
17800000: -42.1
21000000: -42.1
24200000: -42.1
27400000: -42.1
30600000: -42.1
33800000: -42.1
37000000: -42.1
40200000: -35.1
43400000: -42.1
46600000: -42.1
49800000: -42.1
53000000: -42.1
56200000: -42.1
59400000: -42.1
62600000: -42.1
Display spectrum noise levels for upstream interface 2/0 in dB:
CASA-CMTS(config)# show spectrum upstream 2/0 chanwidth 6400000 raw
FREQUENCY
NOISE-LEVEL
(dB)
5000000:
9.5
11400000:
0.0
17800000:
7.8
24200000:
7.8
at channel-width 6400000
461
CASA CMTS
30600000:
37000000:
43400000:
49800000:
56200000:
62600000:
6.0
7.0
17.2
9.5
9.5
6.0
Enabling CM hopping
When multiple logical channels are configured with different modulation profiles in an upstream
physical channel and a cm-hop command is issued, a cable modem can be moved among the
channels based on specified thresholds. If the thresholds specified are exceeded for the cable
modem, it will move to the next (more reliable) logical channel.
To enable or disable CM hopping:
Step
1
Command (config)
Purpose
spectrum rule <rule_id>
Select the
spectrum rule.
Where:
<rule_id>
The rule ID.
Example:
CASA-CMTS(conf-rule 1)#
[no] cm-hop
Example:
CASA-CMTS(conf-rule
CASA-CMTS(conf-rule
3
CASA-CMTS(conf-rule
CASA-CMTS(conf-rule
Enable or
disable CM
hopping.
1)# correctablefec threshold 5

1)# uncorrectablefec threshold
1)# cm-hop
1)# interface ups 1/0
CASA-CMTS(conf-rule 1)# no cm-hop
Displaying CM hopping history

To display or remove logged events of CM hopping:
Step
1
Command (config)
Purpose
spectrum rule <rule_id>
Select the
spectrum
rule.
Where:
<rule_id>
The rule ID.
Example:
CASA-CMTS(conf-rule 1)#
show cm-hop log
Show or
462
CASA CMTS
clear cm-hop log

Example:
CASA-CMTS(conf-rule 1)# show cm-hop log
remove CM
hopping
history.
Considerations when using CSM

1. Spectrum Map is a collection of frequency ranges where a target frequency can be
selected when performing frequency hopping for an upstream channel. It is dynamic
(calculated when it is used) and upstream interface specific. It is calculated based on two
factors. First, frequency ranges specified in a given spectrum rule. And second, current
frequencies used by other upstream channels in the same service group. The user can
give a large frequency range(s) and let CSM take care it without concerns about
frequency overlapping.
2. Discrete frequency in a spectrum rule can be viewed as a frequency band with a given
center frequency and current channel width.
3. There is no frequency hopping back when a channels impairments disappear; only
modulation and channel width.
4. Meaningful order of modulation profiles specified for dynamic modulation profile change
is the order of bandwidth efficiency (or reliability), most efficient one first (most reliable
last).
5. If the configured channel width differs from the start channel width in a spectrum rule, the
start channel width in the rule governs. For example, if the configured channel width is
3.2MHz and chan-width 6400000 800000 is in the rule, then when a channel width
adjustment occurs, it will change to 1.6 MHz or lower. When it recovers, it will try from
6.4 MHZ (the high end) first, then the lower widths.
6. The show interface upstream x/y and show running-config commands show
configurations, not necessarily the current configuration of an upstream interface. If CSM
is in use, use show interface upstream x/y current and show spectrum hop-history
upstream x/y.
7. CSM has a built-in default SNR threshold for each modulation type. To view them, use
the CLI command show spectrum snr-threshold-default. CSM can work without an SNR
threshold for a modulation profile specified in a spectrum rule; that is, using the default
SNR threshold. However, a corrective action will not take place due to low polled SNR.
8. There can be up to three action command items in the spectrum rule. There is no default
action. CSM will attempt a corrective (or improvement) action in the order specified in the
command. However, this does not guarantee that the action will take place. It is important
to know how the action helps before performing it. If an action does not help, it attempts
the next one. The most common reason for an action not helping is that the calculated
SNR for that action does not satisfy the SNR threshold for a modulation profile.
9. If the user wants to change configuration based on modulation profile or channel width
(whatever the user wants CSM to manage), the user should remove spectrum rule from
the channel first, and put the spectrum rule back in the channel list after the configuration
change. This will avoid a conflict between the manual change and CSM control.
463
CASA CMTS
Frequency hop case study

If CSM cannot find a frequency to hop to, it will not hop, even if the current frequency is too noisy
to support modems. For example, if there is noise at 31 MHz on interface 5/1/0, then it should
perform a frequency hop. However, if the spectrum map is,
CASA-CMTS(config)#show spectrum-map upstream 8/1
Spectrum Map for interface 8/1/0
band 0: [28000000, 32800000]
band 1: [36000000, 38400000]
band 2: [41600000, 42000000]
There is no to hop to avoid the noise. The three bands (0-2) are too narrow to escape the noise.
When CSM tries a hop (frequency, modulation, or channel width), it checks if the calculated SNR
at the destination (new freq, etc.) is good enough to accommodate the SNR threshold (280, in
this case). If so, hopping is performed. Otherwise, it tries the next action. In this example, there
is no other action.
However, if the 8/4 frequency is moved to 45MHz (away from 25+1.6=26.6MHz) to give channel
8/1 more room, as in,
spectrum rule 2
action frequency
then move channel 8/1 back to 30MHz (resetting the CSM state machine at channel 8/1), and
then apply the rule 2 to upstream 8/1, to acquire:
CASA-CMTS(config-if-ups 8/1)#show spectrum-map upstream 8/1
Spectrum Map for interface 8/1/0
band 0: [26000000, 32800000]
band 1: [36000000, 38400000]
band 2: [41600000, 42000000]
When the CSM poll reaches a threshold, the channel hops to freq 27.6MHz, as indicated by the
following debug message:
[Wed Dec 2 21:26:18 2009]-DE-CSM-FSM-1:
30000000 to 27600000
CASA-CMTS#show spectrum hop-history
Port
Action Time
8/1/0
Wed Dec 2 21:26:18 2009
cFEC 2 (3) uFEC 30 (1)
8/1/0
Wed Dec 2 21:20:29 2009
change
8/1/0
Wed Dec 2 20:58:46 2009
cFEC 0 (3) uFEC 29 (1)
8/1/0
Wed Dec 2 20:54:16 2009
change
8/1/0
Wed Dec 2 20:31:14 2009
H -> R on 8/1/0.. freq hop
upstream 8/1
Code From
F
30000000
To
27600000
Reason
SNR 80 (280)
30000000
Configuration
30000000
29600000
SNR 131 (280)
30000000
Configuration
30000000
29600000
SNR 100 (280)
464
CASA CMTS
cFEC 1 (3) uFEC 29 (1)

8/1/0
Wed Dec 2 20:29:33
Configuration
8/1/0
Wed Dec 2 17:08:59
cFEC 1 (3) uFEC 28 (1)
8/1/0
Wed Dec 2 16:41:45
change
8/1/0
Wed Dec 2 16:41:45
change
8/1/0
Wed Dec 2 16:41:45
change
2009
29600000
30000000
Back to
2009
30000000
29600000
SNR 106 (280)
2009
10
Configuration
2009
3200000
Configuration
2009
30000000
Configuration
CSM configuration example

Example: 1: Modulation and channel width
spectrum rule 1
action modulation channel-width
correctable-fec threshold 3
uncorrectable-fec threshold 1
profile 3 snr-threshold 280
spectrum-rule 1
logical-channel 0 profile 3 secondary-profile 12,22,30,33

Example: 2: Frequency, channel width, and modulation
spectrum rule 20
frequency 60000000
action frequency channel-width modulation
correctable-fec threshold 3
uncorrectable-fec threshold 0
interface upstream 2/0.0
spectrum-rule 20
.
logical-channel 0 profile 10 secondary-profile 20
465
CASA CMTS
Spectrum measurement (DOCSIS 3.0 only)

The Casa CMTS is Spectrum Measurement DOCSIS 3.0 compliant. A CLI command is used to
show the measured results. Note that the measurement must be triggered through an MIB setting
by creating a table entry for docsIf3CmtsSpectrumAnalysisMeasTable for an interested upstream
channel. The user may have a spectrum analysis application to poll the MIB entry
docsIf3CmtsSpectrumAnalysisMeasAmplitudeData and to retrieve the spectrum measurement
data and show the data in graph form.
Displaying spectrum measurement results

To display spectrum measurement results for a specified upstream channel:
Step
1
Command (config)
Purpose
show spectrum-meas upstream <X/Y>
Display the
spectrum
measurement
results.
Where:
<x/y>

Example:
CASA-CMTS(config)# show spectrum-meas upstream 2/0
See below.
Displaying spectrum measurement results for upstream interface 2/0

2/0 (0) Spectrum MEAS data (in Hz):
chan cnter freq:
8000000
frequency span:
10240000
number of bins:
513
resolution
bw:
20000
bin
spacing:
20000
F4
F4
F2
F2
F4
F4
F2
F2
F4
F2
F2
F4
F4
F2
F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2
F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4
F2
466
CASA CMTS
F4
F4
F2
F2
F4
F4
F2
F4
F4
F2
F2
F4
F2
F2
F4
F4
F2
F2
F4
F4
F2
F2
F4
F7
4C
F4
F4
F2
F2
F4
F4
F2
F2
F4
F4
F2
F4
F4
F2
F2
F4
F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F7 4C F8 DA
F4
F2
F2
F4
F4
F2
F2
F4
F2
F2
F4
F4
F2
F4
F4
467
CASA CMTS
F2
F4
F2
Running spectrum analysis across the entire spectrum

With the following CLI command, the Casa CMTS displays full spectrum data in the same MIB
entry and same format, which, in turn, can be used for same purpose. Note that this command
will always display 40960000, which is the center frequency (chan cnter freq) of the full spectrum.
Step
1
Command (config)
Purpose
spectrum analysis full-spectrum
Select the
full spectrum.
Example:
See below.
Spectrum analysis across the entire spectrum

CASA-CMTS(config)# spectrum analysis full-spectrum
CASA-CMTS# show spectrum-meas upstream 1/0
1/0 (0) Spectrum MEAS data (in Hz):
chan cnter freq:
40960000
frequency span:
81920000
number of bins:
1024
resolution
bw:
80000
bin
spacing:
80000
FC
F6
52
52
F6
F6
52
52
F6
52
52
F6
66 FE C0 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52
F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6
52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52
F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6
52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6
F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6
52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 .
468
CASA CMTS
Configuring load balancing

The load balancing feature for the Casa CMTS allows system operators to distribute cable
modems across radio frequency downstream and upstream channels on the same cable interface
line card, or across multiple cable interface line cards in some circumstances. Load balancing
maximizes bandwidth and usage of the cable plant.
Load balancing supports multiple methods to achieve greater bandwidth availability. These
include static and dynamic load balancing schemes, inter-line card and intra-line card support,
and in some circumstances, configuration of load balancing groups that entail multiple interfaces,
multiple load balancing policies, and the option to configure multiple additional load balancing
parameters.
A CMTS channel can be load-balanced using two methods:
Number of cable modems -- Load balancing according to the number of cable modems on
the interface.
Utilization -- Load balancing according to the current percentage of channel utilization.
Each of the methods can further be operated in two types: static or dynamic.
Static -- Static load balancing is done at ranging request time. When a cable modem sends
its initial ranging request message, the CMTS responds with a ranging response message
that includes either a Downstream Frequency Override or an Upstream Channel ID Override
field that instructs the cable modem which channels it should use.
Dynamic -- This is a form of load balancing in which cable modems are moved among
upstream and downstream channels within the same service group after their initial difference
between two interfaces exceeds a user-defined percentage. The CMTS will use DCC/UCC
messages to move CMs with single upstream/downstream channels and DBC (dynamic
bonding change) messages to move CMs with bonding upstream/downstream channels to
different bonding groups.
For DOCSIS and EuroDOCSIS 3.0 modems, the dynamic load-balancing software generates
a downstream channel set with a minimum load to fit the modems RCP. This prevents
rejection of the new channel set so that load balancing is not canceled when the assigned
modem is under load.
The Casa CMTS supports both methods and types to load balance upstream and downstream
channels. You can configure a Casa CMTS using static load balancing only, or using static load
balancing and dynamic load balancing together.
Because load balancing can only be done to upstream and downstream interfaces sharing the
same physical connectivity, the upstream and downstream interfaces have to belong to the same
service group.
Both channel bonding and non-channel bonding modems can participate in load balancing.
Channel bonding modems will count as one CM for each of its channels.
469
CASA CMTS
To configure load balancing, first define the MAC domains and the service groups. Then define
the basic rules and/or the execution rules. Next, define the load balancing policy and assign the
rules to the policy. Finally, apply the policy to a load balancing group, either the default group or
a restricted load balance group.
To apply a load balancing policy globally, apply it to the default group. To apply different load
balancing policies to different MAC Domain/Service Groups, first define the rules and the policies.
Then create a restricted load balance group, and assign it to the MAC Domain/Service group.
Enable/disable load balancing
General load balance groups
Enter general load balance group default
Enable or disable load balance function on mac-sg general group
Specify technique to move cable modems
Remove technique
Specify the policy to use for load balancing execution
Load balancing basic rules
Enter a basic rule
Enable or disable this rule
Specify a time period
Load balancing execution rules
Enter a load balance execution rule
Specify minimum time interval between each load balance
Specify minimum time interval between each upstream load balance
Specify minimum time interval to move the same modem
Specify method for load balance calculation
Specify method of upstream load balance for load balance calculation
Load balancing policies
Enter a load balance policy
Add or remove basic rule into a policy
Add/replace or remove execution rule into a policy
Restricted load balancing groups
Enter load balance restricted group
Specify mac domain on a restricted group
Enable or disable load balance function on this restricted group
Specify technique to move cable modems
Remove technique
Add service type ID
Add or remove upstream and downstream channel
470
CASA CMTS
Exclusion lists
Add a CM into exclusion list
Remove a CM from exclusion list
Restricted cable modems
Enter to restricted CM configuration
Enter or remove CM mac-address information
Add or remove service type ID
Add or remove reference to a restricted load balance group
CM frequency and channel relocation
Change both upstream and downstream via DCC method
Change downstream via DCC method
Change upstream via DCC method
Change upstream via UCC method
Change bonded CMs upstream and downstream via DBC method
Change bonded CMs downstream via DBC method
Change bonded CMs upstream via DBC method
Displaying load balancing
Show load balance
Clear all load-balance logs
Static CM bonding groups
Add or delete a static downstream CM bonding group
Add or delete a static upstream CM bonding group
Set the provisioned attribute mask
Add or remove upstream channel
Set the DSID re-sequencing wait time
Set the DSID re-sequencing warning threshold
Command default values
Default values for general load-balance group default
Default values for general/restricted load-balance group
Default values for load-balance basic rule
Default values for load-balance execution rule
Enabling and disabling load balancing

This command corresponds to MIB docsLoadbal3System. To enable or disable the load
balancing function globally:
Step
1
Command (config)
Purpose
[no] load-balance enable
Enable or
disable load
balancing.
Example:
CASA-CMTS(config)# load-balance enable
CASA-CMTS(config)# no load-balance enable
471
CASA CMTS
Disabling upstream load balancing

To disable upstream load balancing only, specify upstream load balancing and set the load and
enforce values to 0 in the execution rule. See the sections on specifying upstream method and
threshold.
Enabling load balancing across MAC domains

The CMTS supports static load balancing across MAC domains in networks where upstream and
downstream channels are on two MAC domains, such as docsis mac 1 and docsis mac 2. Use
the load-balance enable across-mac command to specify upstream precedence (default), or
specify the downstream option for downstream load balancing precedence.
By default, the upstream channel has precedence in load balancing across MAC domains, where
the lowest loaded (least busy) upstream channel is selected within the service group. Then, the
lowest loaded downstream channel is selected within the MAC domain of the selected upstream
channel. If the downstream precedence is configured, then the downstream channel is selected
first.
The CMTS will use downstream frequency override and the upstream channel ID override in the
ranging response message to move modems to a different MAC domain if needed. This applies
to all DOCSIS 1.0, 1.1, 2.0 and 3.0 modems. The SID in the ranging response message is 0x3fff.
Additionally, the load-balance enable downstream command specifies downstream load
balancing preference on channels within a MAC domain.
Step
1
Command (config)
Purpose
[no] load-balance enable across-mac [downstream]
Enable or
disable static
load
balancing
across MAC
domains.
Example:
CASA-CMTS(config)# load-balance enable across-mac
CASA-CMTS(config)# no load-balance enable across-mac
General load balancing groups

The general load balance group default contains the default settings for newly-created general
load-balance groups.
Entering the general load balance group default

To enter the general load balance group defaults:
Step
1
Command (config)
Purpose
load-balance general-group default-settings
Enter load
balance
group default
472
CASA CMTS
Example:
CASA-CMTS(config)# load-balance general-group
default-settings
CASA-CMTS(load-bal-general-default)#
mode.
Entering the general load balance group

Once docsis mac interfaces and service groups are configured, a General Load Balance Group
will form automatically for each MAC Domain Service Group (MD-SG). General Load Balance
Group will use the load balancing settings from general load balance default settings. The user
can also configure different load balancing settings using the following commands.
To enter the general load balance group to configure load balancing settings:
Step
1
Command (config)
Purpose
load-balance general-group mac-domain <num> service-group

<string>
Enter the
load balance
group.
Where:
<num>
<string>

Service group name.
Example:
CASA-CMTS(config)# load-balance general-group macdomain 1 service-group FN_A
CASA-CMTS(load-bal-general-mac-1-sg-FN_A)#
In the example above, the service-group definition must be
configured prior to running this command.
Enabling the load balance function on a MAC-SG general group

To enable or disable the load balance function on a mac-sg general group:
Step
Command (config)
Purpose
Example:
default-settings
[no] enable
Enter load
balance
group default
mode.
Example:
CASA-CMTS(load-bal-general-default)# enable
CASA-CMTS(load-bal-general-default)# no enable
Enable or
disable the
load balance
function.
473
CASA CMTS
Specifying the technique for moving cable modems

The user can specify only one technique to move cable modems:
Step
1
Command (config)
Purpose
Enter load
balance
group default
mode.
Example:
default-settings
initial-tech <broadcast-ranging> | <direct> | <period-ranging> |
<reinitialize-mac> | <unicast-ranging>
Where:
<broadcastranging>
Enter the
move cable
modem
technique.
Use broadcast initial-ranging opportunity
<direct>
Move to the new channel directly
<periodranging>
Use period ranging opportunity
<reinitializemac>
Reinitialize mac
<unicastranging>
Use unicast initial-ranging opportunity
Example:
CASA-CMTS(load-bal-general-default)#initial-tech
broadcast-ranging
Specifying the policy for load balancing execution

To specify the policy to use for load balancing execution:
Step
1
Command (config)
Purpose
Enter load
balance
group default
mode.
Example:
default-settings
2
policy-id <num>
Where:
<num>
Load-balance policy ID in the range

0 to 4,294,967,295.
Specify the
policy for
load
balancing.
Example:
CASA-CMTS(load-bal-general-default)# policy-id 2
474
CASA CMTS
Load balancing basic rules

DOCS-LOADBAL3-MIB defines the load balance basic rules.
Entering a basic rule configuration

To enter a basic rule configuration:
Step
1
Command (config)
Purpose
load-balance basic-rule <num>
Enter basic
rule
configuration
mode.
Where:
<num>
load-balance basic rule ID in the range 1 to

4,294,967,295.
Example:
CASA-CMTS(config)# load-balance basic-rule 1
Enabling a basic rule

To enable or disable this rule:
Step
1
Command (config)
Purpose
Enter basic
rule
configuration
mode.
Where:
<num>
Specifies the load-balance basic rule ID; valid values are

1 to 4,294,967,295.
Example:
CASA-CMTS(config)# load-balance basic-rule 1
[no] enable
Example:
CASA-CMTS(load-balance basic-rule 1)# enable
CASA-CMTS(load-balance basic-rule 1)# no enable
Enable or
disable the
basic rule.
Specifying a time period on a basic rule to disable a load balance function

To specify a time period on a basic rule to a disable load balance function:
Step
1
Command (config)
Purpose
Enter basic
rule
configuration
mode.
Where:
<num>
load-balance basic rule ID, valid values are 1 to

4,294,967,295.
Example:
CASA-CMTS(config)# load-balance execution-rule 1
CASA-CMTS(load-bal-exe-rule 1)#
475
CASA CMTS
suspend-load-balancing from <t-start> to <t-end>

Where:
<t-start>
Specify time
period.
Start time for disabling load balance in the format

HH:MM:SS.
End time for disabling load balance in the format
HH:MM:SS.
<t-end>
Load balance execution rules

To enter a load balance execution rule, perform the following. Execution rule is always enabled,
there is no command to enable or disable it.
Step
1
Command (config)
Purpose
load-balance execution-rule <num>
Enter load
balance
execution
rule
configuration
mode.
Where:
<num>
Execution rule ID in the range 1 to 16.
Example:
Specifying a minimum time Interval between each load balance calculation

To specify a minimum time interval between each load balance calculation:
Step
1
Command (config)
Purpose
Enter load
balance
execution
rule
configuration
mode.
Where:
<num>
Example:
2
interval <num>
Where:
<num>
Specify
minimum
time interval.
Minimum time interval in seconds, valid values are 10 to

3600.
Example:
CASA-CMTS(load-bal-exe-rule 1)# interval 200
476
CASA CMTS
Specifying a minimum time interval between upstream load balance

calculations
To specify a minimum time interval between each upstream load balance calculation, perform the
following.
Note: If upstream-interval is not configured, interval value will apply to both upstream and
downstream load balance. If upstream-interval is configured, upstream-interval value will apply to
upstream load balance while the interval value will only apply to downstream load balance.
Step
1
Command (config)
Purpose
Enter load
balance
execution
rule
configuration
mode.
Where:
<num>
Example:
2
upstream-interval <num>
Where:
<num>
Specify
minimum
time interval.
Minimum time interval in seconds.
Example:
CASA-CMTS(load-bal-exe-rule 1)# interval 200
Specifying the minimum time interval to move the same modem

To specify a minimum time interval to move the same modem:
Step
1
Command (config)
Purpose
Enter load
balance
execution
rule
configuration
mode.
Where:
<num>
Example:
2
cable modem rebalance-interval <num>

Where:
<num>
Specify
minimum
time interval.
Minimum rebalance-time interval in seconds; valid values

are 60 to 3600. The default is 3600.
Example:
477
CASA CMTS
cable modem rebalance-interval 2000
To specify a minimum time interval to move the same modem if previous load-balancing failed for
the modem:
Step
1
Command (config)
Purpose
Enter load
balance
execution
rule
configuration
mode.
Where:
<num>
Execution rule ID; valid values are 1 to 16.
Example:
2
Specify the
minimum
time interval.
cable modem retry-interval first <first> second <second>

Where:
<first>
<second>
First retry interval time in seconds; valid values are

60 to 86,400. The default is 86,400 seconds (1 day).
Second retry interval time in seconds; valid values
are 60 to 432,000. The default is 432,000 seconds (4
days).
Example:
CASA-CMTS(load-bal-exe-rule 1)# cable modem retryinterval first 35000 second 87000
Specifying a method for load balance calculations

A method can apply to dynamic, static or both types of load balancing. If method dynamic is not
configured, the method will apply to both static and dynamic load balance; it is not necessary to
specify the dynamic parameters.
If method dynamic is configured, the method will only apply to static load balancing while method
dynamic will apply to dynamic load balance. To disable static load balancing, set the threshold to
0.
To specify a method of utilization for load balance calculations:
Step
1
Command (config)
Purpose
Enter load
balance
execution rule
configuration
mode.
<num>
Where:
Example:
478
CASA CMTS

method utilization [dynamic]
Example:
CASA-CMTS(load-bal-exe-rul 5)#method utilization
Configure the
method of
utilization.
To specify a method of modem for load balance calculation:

Step
1
Command (config)
Purpose
Enter load
balance
execution rule
configuration
mode.
Where:
<num>
Example:
method modem [dynamic]
Example:
CASA-CMTS(load-bal-exe-rul 5)#method modem
Configure the
method of
modem.
Specifying a method for upstream load balance calculations

To specify a method of utilization for upstream load balance calculations:
Step
1
Command (config)
Purpose
Enter load
balance
execution rule
configuration
mode.
Where:
<num>
Example:
upstream-method utilization [dynamic]
Example:
CASA-CMTS(load-bal-exe-rul 5)# upstream-method
utilization
Configure the
upstream
method of
utilization.
To specify a method of modem for upstream load balance calculations:
479
CASA CMTS
Step
1
Command (config)
Purpose
Enter load
balance
execution rule
configuration
mode.
Where:
<num>
Example:
2
upstream-method modem [dynamic]

Example:
CASA-CMTS(load-bal-exe-rul 5)#method modem
Configure the
upstream
method of
modem.
Specifying a utilization method for upstream load balance calculations

To specify a method of utilization for upstream load balance calculations:
Step
1
Command (config)
Purpose
Enter load
balance
execution rule
configuration
mode.
Where:
<num>
Example:
480
CASA CMTS
upstream-threshold load <load_num> enforce <enforce_num>

minimum <min_num> [dynamic minimum <dyn_num>]
Set the method

of utilization.
Where:
<load_num>
Set load difference between interfaces to

start static load balance.
enforce
<enforce_num>
Enforce sets the load difference between

interfaces to start dynamic load balance.
<enforce_num> is the number of modems
on modem method or utilization percentage
on utilization method; valid values are 0 to
<min_num>
Set minimum number of modems on

modem method or minimum utilization
percentage on utilization method. For
static load balance, values are 2 to 100.
The default is 10.
dynamic
minimum
<dyn_num>]
Minimum number of modems for dynamic

load balance; values are 2 to 100. The
default is 0.
To disable upstream load balancing, set the threshold and enforce values to 0.
Load balancing policies

To enter a load balance policy:
Step
1
Command (config)
Purpose
load-balance policy <id>
Enter load
balance policy
mode.
Where:
<id>
Load-balance policy ID, valid values are 1 to

4,294,967,295.
Example:
CASA-CMTS(config)# load-balance policy 5
CASA-CMTS(load-bal-policy 5)#
Adding a basic rule

Load balance policy can have multiple basic rules. To add or remove a basic rule in a policy:
Step
1
Command (config)
Purpose
Enter load
balance policy
mode.
Where:
481
CASA CMTS
<id>
Load-balance policy ID; valid values are 1 to

4,294,967,295.
Example:
2
[no] rule basic <id>
Add or remove a
policy basic rule.
Where:
<id>
Load-balance basic rule ID in the range 1 to

4,294,967,295.
Example:
CASA-CMTS(load-bal-policy 5)# rule basic 10
Adding an execution rule

Load balance policy can have only one execution rule. To add/replace or remove an execution
rule in a policy:
Step
1
Command (config)
Purpose
Enter load
balance policy
mode.
Where:
<id>
Load-balance policy ID; valid values are 1 to

4,294,967,295.
Example:
[no] rule execution <id>
Where:
<id>
Add or remove
a policy
execution rule.
Load-balance execution rule ID; valid values are 1 to

16.
Example:
CASA-CMTS(load-bal-policy 5)# rule execution 10
Restricted load balance groups

Restricted Load Balance Group is very similar to the General Load Balance Group except the
user needs to enter the upstream and downstream channel set.
482
CASA CMTS
Entering the load balance restricted group

To enter load balance restricted group:
Step
1
Command (config)
Purpose
load-balance restricted-group <group-id>
Enter load
balance
restricted group.
Where:
<group-id>
Restricted group ID in the range 1 to 255.
Example:
CASA-CMTS(config)# load-balance restricted-group
2
CASA-CMTS(load-bal-restrict-group-2)#
Specifying the MAC domain on a restricted group

To specify the mac domain on a restricted group:
Step
1
Command (config)
Purpose
Enter load
balance
restricted group.
Where:
<group-id>
Example:
2
2
docsis-mac <num>
Specify the MAC

domain.
Where:
<num>
Example:
CASA-CMTS(load-bal-restrict-2)# docsis-mac 1
Enabling load balancing on a restricted group

To enable or disable the load balance function on a restricted group:
Step
1
Command (config)
Purpose
Enter the load

balance
restricted group.
Where:
<group-id>
483
CASA CMTS
Example:
group-id 2
2
docsis-mac <num>
Specify the MAC

domain.
Where:
<num>
Example:
CASA-CMTS(load-bal-restrict-group-2)# docsis-mac
1
CASA-CMTS(load-bal-restrict-mac-id-group-1)#
[no] enable
Example:
enable
Enable or disable
the load balance
function.
Adding the service type ID to a restricted group

To add service type ID to a restricted group:
Command (config)
Purpose
config
Example:
CASA-CMTS#config
CASA-CMTS(config)#
Enter
configuration
mode.
Step
Where:
<group-id>
Restricted group ID; valid values are 1 to 255.
Enter load
balance
restricted
group.
Example:
group-id 2
3
docsis-mac <num>
Specify the
MAC domain.
Where:
<num>
MAC domain number; valid values are 1 to 255.
Example:
CASA-CMTS(load-bal-restrict-group-2)# docsis-mac 1
484
CASA CMTS
policy-id <string>
Where:
<string>
Add the
service type
ID.
Policy ID in string form.
Adding an upstream channel to a restricted group

To add or remove an upstream channel on a restricted group:
Step
1
Command (config)
Purpose
Enter load
balance
restricted group.
Where:
<group-id>
Example:
group-id 2
2
docsis-mac <num>
Specify the MAC

domain.
Where:
<num>
MAC domain number; valid values are 1 to

255.
Example:
1
[no] upstream <x/y/z>
Where:
<x/y/z>
Upstream channel in form of slot/port/logicchannel.
Add or remove
an upstream
channel on a
restricted group.
Adding a downstream channel to a restricted group

To add a downstream channel to a restricted group:
Step
1
Command (config)
Purpose
Enter load
balance
restricted group.
Where:
485
CASA CMTS

<group-id>
Example:
group-id 2
docsis-mac <num>
Specify the MAC

domain.
Where:
<num>
MAC domain number, valid values are 1 to

255.
Example:
1
[no] qam <x/y/z>
Where:
<x/y/z>
Downstream channel in form of slot/port/logicchannel.
Add or remove a
downstream
channel on a
restricted group.
Exclusion lists
Cable modems can be set not to move by putting them into an exclusion list.
Adding a CM to an exclusion list

To add or remove a CM into an exclusion list:
Step
Command (config)
Purpose
load-balance exclusion list
Example:
CASA-CMTS(config)# load-balance exclusion list
CASA-CMTS(load-bal-exclusion-list)#
[no] mac addr <mac_addr> mask <mask> [static | both]
Enter load
balance
exclusion list
mode.
Where:
Add or remove a
CM into an
exclusion list.
486
CASA CMTS
<mac_addr>
Modem MAC address in 32-bit hex format.
<mask>
MAC address mask in decimal format

xxxx.xxxx.xxxx.
static|both
If neither static nor both is specified,

modems are only excluded from dynamic load
balance. If static is specified, modems are
only excluded from static load balance. If both
is specified, modems are excluded from both
static and dynamic load balance.
Note that modem types can also be excluded
by using a mask.
Example:
To exclude all modems with MAC address 0014:
CASA-CMTS(config)# load-balance exclusion list
CASA-CMTS(load-bal-exclusion-list)# mac addr
0014.0000.0000 mask ffff.0000.0000
Restricted cable modems

Entering the restricted CM configuration
To enter restricted CM configuration:
Step
1
Command (config)
Purpose
load-balance restricted-cm <id>
Enter the
restricted CM
configuration.
Where:
<id>
Restricted modem ID in the range 1 to

4,294,967,295.
Example:
CASA-CMTS(config)# load-balance restricted-cm 1
CASA-CMTS(load-bal-restrict-cm 1)#
Entering the CM MAC address

To enter CM MAC address:
Step
1
Command (config)
Purpose
Enter restricted
CM
configuration.
Where:
<id>

4,294,967,295.
Example:
487
CASA CMTS

2
[no] mac addr <mac_addr> [mask <mask>]

Where:
<mac_addr>
<mask>
Mask in 32-bit hex format. If omitted, the mask

defaults to ffff.ffff.ffff.
[no]
Removes the CM MAC address. This sets mac

addr = 0 and mask = 0xffffffff.
Enter the CM
MAC address.
Example:
Adding a service type ID

To add a service type ID:
Step
1
Command (config)
Purpose
Enter restricted
CM
configuration.
Where:
<id>

4,294,967,295.
Example:
2
service-type-id <string>
Where:
<string>
Add a service
type ID.
Service type ID in string form. Up to 16 characters.

Important: If the description has embedded space
then the whole string needs to be within quotes ("").
Adding a reference to a restricted load balance group

To add or remove a reference to a restricted load balance group:
Step
1
Command (config)
Purpose
Enter restricted
CM
configuration.
Where:
488
CASA CMTS
<id>

4,294,967,295.
Example:
2
restricted-load-balance-group <id>
Where:
<id>
Restrict group ID in the range 0 to 4,294,967,295.
Example:
Add restricted group 3:
load-balance-group 3
restricted-
Remove reference to restricted group 3:

load-balance-group
restricted-
Add or remove a
reference to a
restricted load
balance group.
CM frequency and channel relocation

The CLI commands provide the capability for a user to move a cable modem to a different
downstream frequency or upstream channel.
Changing upstream and downstream channels with the DCC method

To change both upstream and downstream with the DCC method:
Step
1
Command (config)
Purpose
cable modem <mac_addr> dcc change-frequency <freq>

upstream <chan_num> initial-tech (reinitialize-mac |
broadcast-ranging | unicast-ranging | period-ranging | direct)
Change both
upstream and
downstream
channels using
the DCC method.
Where:
<mac_addr>
dcc:
Use DCC method to change channel.
<freq>
Downstream channel frequency in MHz; valid

<chan_num>
Upstream channel number; valid values are 1

to 255.
489
CASA CMTS
Changing a downstream channel with the DCC method

To change a downstream channel with the DCC method:
Step
1
Command (config)
Purpose

initial-tech (reinitialize-mac | broadcast-ranging | unicastranging | period-ranging | direct)
Change
downstream via
the DCC method.
Where:
<mac_addr>
dcc:
<freq>
Downstream channel frequency in MHz in the

range 50 to 999.
Changing an upstream channel with the DCC method

To change an upstream via the DCC method:
Step
1
Command (config)
Purpose
cable modem <mac_addr> dcc upstream <chan_num> initialtech (reinitialize-mac | broadcast-ranging | unicast-ranging |
period-ranging | direct)
Change the
upstream
channel with the
DCC method.
Where:
<mac_addr>
dcc
<chan_num>

to 255.
Changing the CM to another CMTS with the DCC method

To move a CM to another CMTS by overriding the downstream channel frequency via dcc
method, perform the following.
Note: Currently this function is for CMs without channel bonding only. Do not specify the
upstream channel ID here.
Step
1
Command (config)
Purpose

initial-tech reinitialize-mac
Move the CM.
Where:
490
CASA CMTS
<mac_addr>
<freq>
Downstream channel frequency in MHz; valid

Example:
Move CM 0015.f2fe.c904 to another CMTS:
CASA-CMTS(config)# cable modem 0015.f2fe.c904 dcc
change-frequency 593 initial-tech reinitializemac
Setting the upstream channel frequency difference limit on the DCC when
the initial technique is direct
When this limit is set, if the CMTS needs to move a modem to a new upstream channel with a
frequency difference greater than the set limit during dynamic load balancing, it will use the initial
technique of broadcast-ranging (1) instead of direct (4).
To set the difference limit from 1 MHz to 60MHz (if set to 0, then there is no limit):
Purpose
1
load-balance general-default
Example:
CASA-CMTS(config)# load-balance general-default
initial-tech direct frequency-limit <0-60>

Where:
<0-60>
Enter general
default.
.
Set the
difference limit.
Difference limit range in MHz.
Example:
CASA-CMTS(load-bal-general-default)# initial-tech
direct frequency-limit 40
491
CASA CMTS
Changing an upstream channel with the UCC method

To change an upstream channel with the UCC method:
Step
1
Command (config)
Purpose
cable modem <mac_addr> ucc upstream <chan_num>
Change
upstream via the
UCC method.
Where:
<mac_addr>
ucc
Use UCC method to change channel.
<chan_num>

to 255.
Changing a bonded CMs upstream and downstream with the DBC method
To change a bonded CMs upstream and downstream channels via the DBC method:
Step
Command (config)
Purpose
cable modem <mac_addr> dbc [rcp-id <rcp_id> rcc-id <rcc_id>]

upstream-list <string> initial-tech (reinitialize-mac | broadcastranging | unicast-ranging | period-ranging | direct)
Change
bonded CM
upstream
and
downstream
channels with
the DBC
method.
Where:
<mac_addr>
dbc
Dynamic bonding change.
<rcp_id>
Optional RCP ID in the format xx:xx:xx:xx:xx.
<rcc_id>
Optional RCC ID in the range 1 to 255.
<string>
Name of upstream list in string format.
492
CASA CMTS
Changing a bonded CMs downstream channel with the DBC method

To change a bonded CMs downstream channel with the DBC method:
Step
Command (config)
Purpose
cable modem <mac_addr> dbc downstream-list <string> initialtech (reinitialize-mac | broadcast-ranging | unicast-ranging |
period-ranging | direct)
Change
bonded
downstream
channel with
the DBC
method.
Where:
<mac_addr>
dbc
<string>
Name of downstream list in string format.
Changing a bonded CMs upstream channel via the DBC method

To change a bonded CMs upstream via the DBC method:
Step
1
Command (config)
Purpose
cable modem <mac_addr> dbc upstream-list <string> initial-tech

(reinitialize-mac | broadcast-ranging | unicast-ranging | periodranging | direct)
Change
bonded
upstream
channel via
the DBC
method.
Where:
<mac_addr>
dbc
<string>
Name of upstream list in string format.
Displaying load balancing information

To show load balance:
Step
1
Command
Purpose
show load-balance (dynamic|static) [begin <b_date> < b_time>]

[end <e_date> <e_time>] [(begin | count | count-only | exclude |
include) <string>]
Display
load
balancing.
Where:
493
CASA CMTS
<date>
load-balance beginning date in form YYY-MMDD.
<b_time>
load-balance
HH:MM:SS.
<e_date>
load-balance ending date in form YYY-MM-DD.
<e_time>
load-balance ending time in form HH:MM:SS.
begin
Begin with the line that matches
count
count lines output
count-only
Count lines output while suppressing output.
exclude
Exclude lines that match
Include
Include lines that match.
<string>
String to match.
beginning
time
in
form
Example:
CASA-CMTS# show load-balance dynamic
See below.
show load-balance dynamic

Mac address
Mac-id upstream-channel
downstream-channel
initial_tech
cmd
status
type
time
0015.f2fe.c643
0
3
-1
dcc
WaitToSendMsg
GLB 2008-04-06 23:25:17
0015.f2fe.c643
0
2
-1
dcc
WaitToSendMsg
RGLB 2008-04-06 23:28:41
----------------------------------------------------------------------total: 2;
success:0;
other:2
Where type is:
BAL -- Balancing done by the system.
MLT -- DCC by limit replication multicast.
CLI -- Load balancing done manually from the CLI.
MIB -- Load balancing done manually from SNMP.
CSM -- DCC done by CSM per cable modem.
DSA -- DCC done by voice.
RSLB -- DCC moved a cable modem into a restricted load-balance group.
RGLB -- General load balancing done until registration.
SG -- Channel is not in the channel set of the configured service group.
494
CASA CMTS
Clearing all load-balance logs

To clear all load-balance logs:
Step
1
Command
Purpose
clear load-balance log
Clear
the
load balance
logs.
Example:
CASA-CMTS# clear load-balance log
Command ordering
Because many of the load balancing commands depend on the existence of other objects, the
ordering of these commands is critical. For example, load-balance general-group depends on the
existence of mac domain, service group, and policy. And policy depends on basic rule and
execution rule.
In show run, the command described in this document should come after all the interface
configuration commands and follow the order outlined below:
service-group
.
.
interface upstream x/y
.
load-balance enable
.
load-balance basic-rule
.
load-balance execution-rule
.
load-balance policy x
.
.
load-balance general-group mac-domain x service-group y
.
load-balance restricted-group group-id y
.
load-balance restricted-cm x
.
bonding-group downstream mac-domain x group-id y
.
bonding-group upstream mac-domain x group-id y
495
CASA CMTS
Command default values

Default values for general load-balance group default
enable
initial-tech-none
no policy-id
Default values for general/restricted load-balance group

The default values for a newly created General Load-Balance Group shall be taken directly from
the General Load-Balance Group Default.
Default values for load-balance basic rule

-
no enable
Default values for load-balance execution rule

interval 10
method modem
threshold load 10 enforce 0 minimum 10
Sample configuration
CASA-CMTS# show run
!
! CASA-CMTS system running configuration
!
hostname "sada"
!
password casa
!
!
interface eth 0
ip address 192.168.2.240 255.255.255.0
!
ip address 10.248.1.1 255.255.255.0
!
!
interface gige 0
ip address 192.168.3.48 255.255.255.0
ipv6 address 2001:50:1::3/64
no shutdown
!
interface gige 1
496
CASA CMTS
shutdown
!
interface gige 2
shutdown
!
interface gige 3
shutdown
!
!
cable sec tftp-options none
no cable sec config-file-learning
cable sec cert-revocation-list url
cable sec ocsp protocol-url
!
!
interface qam 0/0
interleave 128x1
power 540
no shutdown
interface qam 0/1
interleave 128x1
power 540
no shutdown
interface qam 0/2
interleave 128x1
channel 0 frequency
channel 0 shutdown
channel 1 frequency
channel 1 shutdown
channel 2 frequency
channel 2 shutdown
channel 3 frequency
channel 3 shutdown
shutdown
549000000
555000000
561000000
567000000
interface qam 0/3

interleave 128x1
power 450
497
CASA CMTS
shutdown
!
igmp client version 2
!
service group FN_A
qam 0/0/0
qam 0/0/1
qam 0/0/2
qam 0/0/3
upstream 1/0
upstream 1/1
service group FN_B
qam 0/1/0
qam 0/1/1
qam 0/1/2
qam 0/1/3
upstream 1/2
upstream 1/3
upstream map size 5
no shutdown
no dhcp-authorization
no early-authentication-encryption
no multicast-dsid-forward
no tftp-proxy
ip bundle 1
!
!
frequency 8000000
498
CASA CMTS
logical-channel 0 pre-equalization
logical-channel 1 frame 16 8 128
no shutdown
frequency 12000000
no shutdown
frequency 16000000
no shutdown
frequency 20000000
no shutdown
frequency 24000000
logical-channel 1 shutdown
no shutdown
frequency 28000000
499
CASA CMTS
no shutdown
frequency 32000000
no shutdown
frequency 36000000
no shutdown
!
!
! load balance commands
!
load-balance enable
load-balance basic-rule 1
enable
suspend-load-balance from 13:00:00 to 20:00:00
enable
enable
load-balance execution-rule 1
enable
method modem
threshold load 10 enforce 30 minimum 35
load-balance policy 1
500
CASA CMTS
rule basic 1
rule basic 3
rule execution 1
initial-tech unicast-ranging
load-balance general-group mac-domain 1 service-group FN_A
enable
initial-tech direct
policy-id 1
load-balance general-group mac-domain 1 service-group FN_B
no enable
initial-tech direct
policy-id 1
load-balance restricted-group group-id 10
enable
docsis-mac 1
initial-tech broadcast-ranging
policy-id 1
service-type-id restict1
qam 0/1/0
qam 0/1/1
qam 0/1/2
upstream 1/2
upstream 1/3
load-balance restricted-cm 1
mac addr 0018.0123.5678
restricted-load-balance-group 10
load-balance restricted-cm 2
mac addr 0019.0000.0000 mask ffff.0000.0000
restricted-load-balance-group 10
bonding-group downstream mac-domain 1 group-id 1
prov-attr-mask 0x00ff
reseq wait-time 1000
reseq warn-thrshld 1200
qam 0/0/0
qam 0/0/1
qam 0/0/2
qam 0/0/3
bonding-group upstream mac-domain 1 group-id 1
prov-attr-mask 0x00ff
upstream 1/0/0
upstream 1/1/0
!
!
!
end of config
501
CASA CMTS
Configuring channel bonding operations

In order for the Casa CMTS to operate in channel bonding mode, the docsis-mac interface must
be configured, as well as a service group with at least one downstream channel and one
upstream channel.
For cable modems that support channel bonding operation, the Casa CMTS automatically
creates channel bonding groups with channels that belong to the same service group, and the
same docsis-mac interface.
The Casa CMTS supports channel bonding in the same line card module. The maximum number
of downstream channels per QAM module is 16, and the maximum number of upstream channels
per upstream DCU module is 16.
Service group configuration

A service group is used to represent RF topology. A service group must have at least one
upstream channel and one downstream channel to allow channel-bonding operation. A
downstream channel and an upstream channel can be associated with multiple service groups.
To configure a service group:
Step
1
Command (config)
Purpose
service group <grp_id>
Enter the service

group
configuration
mode.
Where:
<grp_id>
Service group ID.
Example:
CASA-CMTS(conf-svc-grp 1)#
[no] qam <slot/port/channel>
Where:
<slot/port/channel>
Add or remove a
downstream
channel.
Slot, port and channel numbers.
Example:
CASA-CMTS(conf-svc-grp 1)# qam 0/0/0
Remove:
CASA-CMTS(conf-svc-grp 1)#no qam 0/0/0
502
CASA CMTS
[no] upstream <slot/port.phy_channel>

Where:
<slot/port.phy_channel>
Add or remove
an upstream
channel.
Slot, port and logical channel

numbers.
Example:
CASA-CMTS(conf-svc-grp 1)# upstream ?
X/Y.C
X-slot number, Y-port number, Cphysical channel index 0 or 1
CASA-CMTS(conf-svc-grp 1)# upstream 3/0.1
CASA-CMTS(conf-svc-grp 1)# show service group
CASA-CMTS(conf-svc-grp 1)# no upstream 3/0.1
DOCSIS-MAC interface configuration

For normal DOCSIS operation, a docsis-mac interface must be configured. The docsis-mac
interface creates an association between downstream channels and upstream channels.
A downstream channel or an upstream logic-channel can only be associated with one docsismac interface. The channel id must be unique in a docsis-mac interface.
To configure a docsis-mac interface:
Step
1
Command (config)
Purpose
interface docsis-mac <dsm_id>
Enter the docsismac

configuration
mode.
Where:
<grp_id>
DOCSIS MAC ID.
Example:
CASA-CMTS(conf-if-mac 1)#
[no] downstream <chan_id> interface qam
<slot/port/channel>
Where:
<chan_id>
<slot/port/channel>
Add or remove a
downstream
channel.
Channel ID.
Example:
CASA-CMTS(conf-if-mac 1)#downstream 1 interface
qam 0/0/0
503
CASA CMTS
[no] upstream <chan_id> interface upstream

<slot/port.channel/logical_channel>
Where:
<chan_id>
<slot/port/channel>
Add or remove
an upstream
channel.
Channel ID.
Example:
CASA-CMTS(conf-if-mac 1)# upstream 1 interface
upstream ?
X/Y.C/Z
X - slot, Y - port (0-7), C upstream physical channel(0-1), Z - upstream
logical channel(0-1
CASA-CMTS(conf-if-mac 1)# upstream 1 interface
upstream 4/1.0/0
CASA-CMTS(conf-if-mac 1)# show interface docsismac 1
CASA-CMTS(conf-if-mac 1)#no upstream 1
Channel bonding example

In the following example, one service group is formed with 16 downstream and 8 upstream
channels from the same downstream/upstream modules, with two mac domain interfaces created
within the service group. Each domain contains 8 downstream and 4 upstream channels. The
channel bonding then occurs inside each of the domains, or 8 downstream and 4 upstream
channels.
CASA-CMTS(config-svc-grp 1)# qam 0/0/0
CASA-CMTS(config-svc-grp 1)# upstream 1/0
504
CASA CMTS

CASA-CMTS(config-svc-grp 1)# end
CASA-CMTS(config-if-mac 1)# no dhcp-authorization
CASA-CMTS(config-if-mac 1)# no early-authentication-encryption
CASA-CMTS(config-if-mac 1)# no tftp-proxy
CASA-CMTS(config-if-mac 1)# ip address 10.15.131.1 255.255.255.0
CASA-CMTS(config-if-mac 1)# cable helper-address 192.168.3.6
CASA-CMTS(config-if-mac 1)# downstream 1 interface qam 0/0/0
CASA-CMTS(config-if-mac 1)# upstream 1 interface upstream 1/0/0
CASA-CMTS(config-if-mac 2)# no dhcp-authorization
CASA-CMTS(config-if-mac 2)# no early-authentication-encryption
CASA-CMTS(config-if-mac 2)# no tftp-proxy
CASA-CMTS(config-if-mac 2)# ip address 10.15.131.2 255.255.255.0
CASA-CMTS(config-if-mac 2)# cable helper-address 192.168.3.6
CASA-CMTS(config)#
505
CASA CMTS
Creating static CM bonding groups

The bonding group commands configure the static channel bonding combination that is available
in the MAC domain for cable modems. Casa Systems does not recommend the use of static
bonding.
Adding a static downstream CM bonding group

To add or delete a static downstream CM bonding group:
Step
1
Command (config)
Purpose
[no] bonding-group downstream mac-domain <dmn_id>

group-id <grp_id>
Add or delete a
static
downstream CM
bonding group.
Where:
<dmn_id>
<grp_id>

Bonding group ID in the range 1 to 65,535.
Example:
CASA-CMTS(config)# bonding-group downstream macdomain 7 group-id 1
Adding a static upstream CM bonding group

To add or delete a static upstream CM bonding group:
Step
1
Command (config)
Purpose
[no] bonding-group upstream mac-domain <dmn_id> groupid <grp_id>
Add or delete a
static upstream
CM bonding
group.
Where:
<dmn_id>
<grp_id>

Example:
CASA-CMTS(bond-us-mac-7-group-1)#
506
CASA CMTS
Setting the provisioned attribute mask in an upstream/downstream

bonding group
To set the provisioned attribute mask in an upstream bonding group:
Step
1
Command (config)
Purpose
Add or delete a
static upstream
CM bonding
group.
Where:
<dmn_id>
<grp_id>

Example:
prov-attr-mask <mask>
Where:
<mask>
Set the
provisioned
attribute mask.
Provisioned attribute mask in hex format 0x0

to 0xffffffff.
To set the provisioned attribute mask in a downstream bonding group:

Step
1
Command (config)
Purpose

group-id <grp_id>
Add or delete a
static
downstream CM
bonding group.
Where:
<dmn_id>
<grp_id>

Bonding group ID in the range 1 to 65535.
Example:
prov-attr-mask <mask>
Where:
<mask>
Set the
provisioned
attribute mask.
Provisioned attribute mask in hex format 0x0

to 0xffffffff.
507
CASA CMTS
Adding an upstream channel to a bonding group

To add or remove the upstream channel to a bonding group:
Step
1
Command (config)
Purpose
Add or delete a
static upstream
CM bonding
group.
Where:
<dmn_id>
<grp_id>

Example:
[no] upstream <x/y/z>
Where:
Upstream channel in form of slot/port/logic<x/y/z>
channel.
Add or remove
the upstream
channel.
Adding a downstream channel to a bonding group

To add or remove a downstream channel to a bonding group:
Step
1
Command (config)
Purpose

group-id <grp_id>
Add or delete a
static
downstream CM
bonding group.
Where:
<dmn_id>
<grp_id>

Example:
[no] qam <x/y/z>
Where:
<x/y/z>
Add or remove
the downstream
channel.
Downstream channel in form of

slot/port/channel.
508
CASA CMTS
Setting the DSID re-sequencing wait time in a downstream bonding

group
To set the DSID re-sequencing wait time:
Step
1
Command
Purpose

group-id <grp_id>
Add or delete a
static
downstream CM
bonding group.
Where:
<dmn_id>
<grp_id>

Example:
reseq wait-time <value>
Where:
<value>
Set the DSID resequencing wait

time.
Re-sequencing waiting time value; 0 to 255.
Setting the DSID re-sequencing warning threshold in a downstream

bonding group
To set the DSID warning threshold:
Step
1
Command (config)
Purpose

group-id <grp_id>
Add or delete a
static
downstream CM
bonding group.
Where:
<dmn_id>
<grp_id>

Example:
reseq warn-threshold <level>
Where:
<level>
Set the DSID

warning
threshold.
Re-sequencing threshold level; 0 to 255.
509
CASA CMTS
QoS support
The C10200 and C3200 provide Quality of Service (QoS) through fine grain, per-flow queuing in
the DQM and DCU modules, and class-based strict priority scheduling in the switch fabric and
Gigabit interfaces.
QoS support in DQM modules

The DQM module provides QoS support through a two-level hierarchical scheduler. The top level
is priority based, and the second level is a fair scheduler based on round robin.
Each packet destined for a downstream interface is assigned a service flow through classification
by the DOCSIS forwarding engine. The packet scheduler in the DQM module supports minimum
guaranteed rate, as well as maximum transmitted rate. Packets are serviced in the order of
priority specified by the service flow. Service flow that is within minimum guaranteed rate is
served first. Within the same priority, round robin is used to schedule between different service
flows.
If the service flow has minimum guaranteed rate, and the current rate is within the specified rate,
the packet is queued in the guaranteed class, which has the highest priority. The packet is
subsequently rate limited through a token bucket to conform to the maximum transmitted rate
specified for the service flow. Packets that exceed the maximum transmitted rate are rate-shaped
by deferring their transmission. Packets are only dropped if the buffer utilization is high and the
buffer usage by the service flow is above the drop threshold.
The packet scheduler is driven by availability of transmission opportunities on the downstream
channel. The scheduler can provide millisecond level latency guarantees for high priority traffic
through the use of shallow transmit queues. Every time a channel transmit queue becomes
available, the scheduler services the service flows in the order of priority until the transmit queue
is full or all eligible packets are serviced.
For downstream channel bonding operation, the service flow is serviced by each of the channels
in the bonding channel set in parallel.
QoS support in DCU modules

In the DCU module, the upstream scheduler handles modem transmission opportunities. In
addition to providing minimum guaranteed rate and rate limiting support, it also provides jitter
guarantees for jitter-sensitive services, such as unsolicited grant service (UGS).
The hierarchical upstream scheduler serves upstream service flows based on priority. Jittersensitive service flows are serviced first, followed by service flows that are within its guaranteed
rate. Best effort service flows are then serviced in the order of priority. Within each priority, the
service flows are serviced by a round robin scheduler.
510
CASA CMTS
For best effort services, the minimum guaranteed rate is checked first. If the transmission rate of
the service flow is within its specified guaranteed rate, the request is placed in the guaranteed
queue, which is serviced before other best effort queues. Token bucket is used to rate limit the
service flow within its configured maximum transmission rate and maximum burst size. Requests
that exceed the maximum transmission rate are deferred. Requests that conform to the maximum
transmission rate are placed into the queue determined by the priority of the service flow.
Jitter-sensitive service flows are scheduled by the real-time scheduler. To provide jitter
guarantees, the transmission opportunities are pre-allocated when the service flow is admitted to
prevent overlap. At MAP generation time, the real time scheduler aggregates jitter-sensitive
grants into clusters. The best effort grants are then placed into the gaps between the real time
grant clusters. If the gap is not big enough, the cluster is allowed to move to increase the gap, as
long as jitter guarantees can be met for the real time grants in the cluster. If the gap is still not
enough to place the best effort grant, the best effort grant is then fragmented. The scheduler
keeps track of the remainder of the fragments and continues to serve the fragments until the
request is fulfilled.
For service flows that are serviced by upstream channel bonding, the service flow is inserted into
multiple queues, one for each of the upstream channels in the bonding channel set. The service
flow is serviced by each of the upstream channels until all the outstanding bytes requested are
served.
QoS support in switch fabric and Gigabit Ethernet interfaces

The switch fabric connects to the RF modules and Gigabit Ethernet interfaces. Each of the fabric
ports supports eight classed-based queues. The scheduler in the switch fabric is straight priority.
For packets entering the switch fabric from the DCU module, the priority is determined by the
priority value in the upstream service flow. For packets entering the switch fabric from Gigabit
Ethernet interfaces, the priority is from the 802.1p field if the packet is VLAN-tagged. For
untagged packets, the DSCP value in the IP header is used to determine the priority.
The filtering engine can be used to overwrite the DSCP value using access list. The priority value
can also be modified based on access lists.
To prevent head-of-line blocking, the switch fabric keeps track of the outstanding buffer count and
packet count for each of the ingress ports and each of the classes. When an egress port on the
switch fabric becomes congested, a packet is discarded at ingress if the outstanding buffer count
or packet count from the ingress port exceeds the discard threshold for the class it belongs to.
Configuring QoS
The Casa CMTS supports quality of services (QoS) as defined by the DOCSIS 1.0, 1.1
specifications. Service classes can be configured through the command-line interface to support
the QoS profile number, traffic priority, maximum upstream bandwidth, guaranteed upstream
bandwidth, maximum downstream bandwidth, maximum transmit burst length, baseline privacy
511
CASA CMTS
enable/disable, and type of service (ToS) overwrite byte. This section covers commands for the
following operations:
Configuring service classes (DOCSIS 1.1)
Showing the service class
Configuring the service class (DOCSIS 1.1)

To set parameters for DOCSIS 1.1 cable service class, use the cable service class command in
global configuration mode. To delete a service class or to remove a configuration, use the no
form of the command.
Step
1
Command (config)
Purpose
[no] cable service-class class-index
Set or delete
parameters for
DOCSIS 1.1
cable service
class.
Where:
class-index
Specifies the class ID for the class to be

modified. Valid range is 1 to 255.
Defaults: Values that are not specified are
set to their DOCSIS 1.1 defaults, if
applicable to the service-class schedule
type.
Example:
Showing the service class

To display the parameters for cable service class, use the show cable service class command in
privileged mode.
Step
1
Command
Purpose
show cable service-class [sclass-index] [verbose]
Display the
parameters for
cable service
class.
Where:
sclass-index
verbose
Identifies the index for a service class that

has already been defined (1 to 255).
Displays all of the defined attributes for the
service class.
Example:
Show the standard and verbose formats of the show cable service
class command:
CASA-CMTS# show cable service-class
512
CASA CMTS
Index Name
MaxSusRate MaxBurst
1
UP_UGS
1522
0
2
UP_UGSAD
1522
0
3
UP_RTPS
2000
64000
4
UP_BE
2000
0
5
DOWN_BE
3000
0
Dir
Sched
MinRsvRate
US/DS UGS
Prio
0
US/DS UGS_AD 0
US/DS RTPS
128000
US/DS BE
128000
US/DS BE
1000000
CASA-CMTS# show cable service-class 1 verbose

Index:
Name:
Direction:
Upstream/Downstream
Traffic Priority:
Maximum Sustained Rate:
bits/sec
Max Burst:
bytes
Minimum Reserved Rate:
bits/sec
Minimum Packet Size
Admitted QoS Timeout
seconds
Active QoS Timeout
seconds
Scheduling Type:
Unsolicited Grant Service
Request/Transmission Policy:
Unsolicited Grant Size:
Nominal Grant Interval:
usecs
Tolerated Grant Jitter:
usecs
Grants per Interval:
IP ToS Overwrite [AND-mask,OR-mask]:
Max Latency:
Parameter Presence Bitfield:
0xBCC000}
1
UP_UGS
0
0
1522
0
100 bytes
30
30
0x1FF
100 bytes
20000
4000
1
0xE0,0xA0
0 usecs
{0xE08,
QoS class and policy (C3200, C10200, C10G only)

To specify the QoS parameters, define a class map and assign it to a QoS policy. Then apply the
policy to a GigE interface, a trunk interface, a VLAN, and IP bundle, or a MAC domain.
To define a class map for QoS:
513
CASA CMTS
Step
1
Command (config)
Purpose
[no] class-map <string>
Define a class
map.
Where:
<string>
Class map name.
Only 'permit' rules are used for policy/class. A total of 128 ACL rules are supported for policy
service (set DSCP). ACL rules in the access-group take priority if a packet matches in both the
ACL and policy (for DSCP rewrite).
To assign an access control list to the class map:
Step
1
Command (config)
Purpose
[no] match access-group <acl_name>
Assign an access
control list.
Where:
<acl_name>
Access Control List name.
To define a class action (DSCP overwrite for matched packets):

Step
1
Command (config)
Purpose
[no] set-dscp <0:63>
Define a class
action.
To define a QoS policy (up to eight maps are supported):

Step
1
Command (config)
Purpose
[no] policy-map <policy-name>
Define a QoS
policy.
Where:
<policy-name>
Policy name.
To define classes within a policy:

Step
1
Command (config)
Purpose
[no] class <class-name>
Define a class
within a policy.
Where:
<class-name>
Class name. Up to 16 classes are

supported.
To show information about the QoS class and policy:

Step
1
Command (config)
Purpose
show class-map <name>

show policy-map <name>
Display QoS
class and policy
514
CASA CMTS
map information.
Where:
<name>
The class or policy name
To apply a policy to a GigE interface:

Step
Command (config)
Purpose
interface gige <id>
Enter GigE
interface mode.
Where:
<id>
GigE interface ID.
Example:
2
Specify the
service policy.
service-policy <policy-name>
Where:
<policy-name>
Policy name.
Example:
CASA-CMTS(conf-if-gige 5)#service-policy policy1
CASA-CMTS(conf-if-gige 5)#
To apply a policy to a MAC domain interface:

Step
1
Command (config)
Purpose
interface docsis-mac <id>
Enter the
interface.
Where:
<id>
The docsis mac ID.
Example:
2
Apply the policy.
service-policy <policy-name>
Where:
<policy-name>
The policy name.
Example:
CASA-CMTS(conf-if-mac 1)# service-policy policy1
515
CASA CMTS
To apply a policy to a VLAN interface:

Step
Command (config)
Purpose
interface vlan <id>
Enter VLAN
interface mode.
Where:
<id>
2
VLAN ID.
service-policy <policy_name>
Where:
<policy_name>
Apply the policy.
The policy name.
Example:
CASA-CMTS(conf-if-vlan 1)#service-policy policy1
Configuring SNMP (Enhanced in 5.4)

Casa CMTS supports SNMP protocol in both CLI and MIB operations. This section covers the
CLI commands for the following operations:
Configuring the SNMP engineId
Enabling SNMP traps
Setting the SNMP traphost
Setting the SNMP trap source IP address
Enabling SNMP Informs
Setting the SNMP community
Configuring the access table
Configuring the community table
Configuring the notification table
Configuring the securityToGroup table
Configuring the TargetAddress table
Configuring the TargetParameter table
Configuring the ViewFreeFamily table
Configuring the user table
Displaying the SNMP configuration and statistics
The command should be run under configuration mode. The configurations are persistent and a
copy running-config to startup-config is not required.
516
CASA CMTS
Configuring the SNMP engineID

The SNMP engineID is an administrative identifier that is required for SNMP V3, as specified in
RFC3411, An Architecture for Describing Simple Network Management Protocol (SNMP)
Management Frameworks. SNMP V3 authentication and encryption keys are generated using
the engineID and related passwords.
The engineID is expressed as a hexadecimal string (24 characters) in the SNMP configuration.
After configuring or changing the SNMP engineID, you will need to reconfigure any SNMP V3
users, as the keys will based on the prior engineID setting.
Step
1
Command (config)
Purpose
[no] snmp engineid <hexadecimal-string>
Configure the
SNMP
engineID.
Where:
<hexadecimal-string>>
Specifies the 24-character SNMP

engine identifier.
Example:
CASA-CMTS(config)# snmp engineid
112233445566778899001112
Use the no form

of the command
to remove the
engineID.
CASA-CMTS(config)# no snmp engineid
Enabling SNMP traps

To enable SNMP traps (the default is all versions of traps are enabled):
Step
1
Command (config)
Purpose
[no] snmp trap version <version>
Enable or disable
SNMP traps.
Where:
<version>
Trap version; values are 1, 2 or 3
Example:
Enable SNMP v2 trap
CASA-CMTS (config)# snmp trap version 2
Disable SNMP v2 trap:

CASA-CMTS (config)# no snmp trap version 2
show running-config | i no snmp trap
Example:
CMTS#config)#show running-config | i syslog
no snmp trap version 1
Check for traps

that are turned
off.
In the examples above, SNMP version 1 traps are turned off;

versions 2 and 3 are allowed are valid for a trap host
configuration.
517
CASA CMTS
Setting an SNMP traphost

To set an SNMP traphost:
Step
1
Command (config)
Purpose
snmp traphost <host-ip> community <community-string>

version <version>
Set the SNMP

traphost.
Where:
<host-ip>
Host server IP address in the format a.b.c.d.
<version>
Trap version; values are 1 or 2
<communitystring>
SNMP community name.
Example:
Set SNMP trap with host IP address 192.168.6.10, community
string as public, and trap version of 1:
CASA-CMTS (config)# snmp traphost 192.168.6.10
community public version 1
Configuring SNMP server contact and location strings

To specify SNMP contact and location information:
Step
1
Command (config)
Purpose
snmp-server {contact <string> | location <string>}
Specify the
SNMP contact
and location
information
strings.
Where:
<string>
Specifies location and contact information

associated with the SNMP server. The text
string can have up to 32 alphanumeric
characters. If blank spaces are necessary,
enclose the string in quotation marks ( ).
Example:
CASA-CMTS (config)# snmp-server location
bostonOffice
CASA-CMTS (config)# snmp-server contact Fred
Gamble at 978-123-4567
Use the no form

of the command
to delete the
current entries.
518
CASA CMTS
Configuring the SNMP trap source IP address

To specify the SNMP trap source IP address:
Step
1
Command
Purpose
snmp trap-source loopback <lo_id>
Specify the
SNMP trap
source IP
address.
Where:
<lo_id>
Loopback interface ID; values are 0 to 15.
Example:
CASA-CMTS (config)# snmp trap-source loopback 6
Enabling SNMP inform requests

To enable or disable SNMP inform requests. By default, v2 and v3 informs are enabled:
Step
1
Command (config)
Purpose
[no] snmp inform version <version>
Enable or disable
SNMP informs.
Where:
<version>
Inform version; values are 2 or 3
Example:
Enable SNMP v2 inform
CASA-CMTS (config)# snmp inform version 2
CASA-CMTS (config)#
Disable SNMP v2 inform

CASA-CMTS (config)# no snmp inform version 2
CASA-CMTS (config)#
show running-config | i no snmp inform
Example:
CMTS#config)#show running-config | i no snmp
inform
no snmp inform version 2
Check the current

SNMP inform
setting.
In the examples above, SNMP version 2 inform requests are

turned off; version 3 inform requests are enabled by default.
519
CASA CMTS
Setting the SNMP community

To set SNMP community:
Step
1
Command
Purpose
snmp community <community_string> { ro | rw }
Set SNMP
community.
Where:
<community_string>
Text string for SNMP community.
ro
Read only privilege.
rw
Read and write privilege.
Example:
Set SNMP community string to local with read-only privileges.
CASA-CMTS(config)# snmp community local ro
CASA-CMTS(config)# show snmp community
Community name:
local
Community Index:
local
Community SecurityName: rotesting
Community StorageType:
3
Community Status:
active
Disabling default SNMP public and private community

To disable the default SNMP public or private community:
Step
1
Command (config)
Purpose
no snmp comm-tbl public | private
Disable the
default SNMP
public or
private
community.
Example:
CASA-CMTS(config)# no snmp comm-tbl public
CASA-CMTS(config)# show snmp community
Configuring the SNMP access table

To configure the SNMP access table:
Step
1
Command (config)
Purpose
snmp access <group> <context> (snmpv1 | snmpv2c | usm)

(no-auth | auth-no-priv | auth-priv) (exact | prefix) <read>
<write> <notify> (other | volatile | non-volatile | permanent |
read-only) (mod)
Configure the
SNMP
access table.
Where:
<group>
group name in string form
520
CASA CMTS
<context>
snmpv1
snmpv2c
usm
no-auth
auth-no-priv
auth-priv
exact
prefix
<read>
<write>
<notify>
other
volatile
non-volatile
permanent
read-only
mod
context prefix in string form

snmp version 1
snmp version 2c
usm
no authentication no privacy
authentication no privacy
authentication and privacy
exact context match
prefix context match
read view name in string form
write view name in string form
notify view name in string form
storage other
storage volatile
storage non-volatile
storage permanent
storage read-only
modify an entry
Deleting the SNMP access table

To delete the SNMP access table:
Step
1
Command (config)
Purpose
no snmp access <group> <context> (snmpv1 | snmpv2c |

usm) (no-auth | auth-no-priv | auth-priv)
Delete the
SNMP
access table.
Where:
<group>:
<context> :
snmpv1:
snmpv2c:
usm:
no-auth:
auth-nopriv:
auth-priv:
group name in string form

context prefix in string form
snmp version 1
snmp version 2c
usm
no authentication no privacy
authentication no privacy
authentication and privacy
521
CASA CMTS
Configuring the community table

To configure the SNMP community table:
Step
1
Command
Purpose
snmp comm-tbl <comm_index> <comm_name> <sec_name>

<context_id> <context_name> <tag> (other | volatile | nonvolatile | permanent | read-only) [mod]
Configure the
SNMP
access table.
Where:
<comm_index>:
<comm_name> :
<sec_name>:
<context_id>:
<context_name>:
<tag>:
other:
volatile:
non-volatile:
permanent:
read-only:
mod:
community table index in string form

community name in string form
community security name in string form
context engine ID in string form
context name in string form
tag value in string form
storage other
storage volatile
storage permanent
storage read-only
modify an entry
Deleting the SNMP community table

To delete the SNMP community table:
Step
1
Command
Purpose
no snmp comm-tbl <comm_index>
Delete the
SNMP
access table.
Where:
<comm_index>
community table index in string form
Configuring the notification table

To configure the SNMP notification table:
Step
1
Command
Purpose
snmp notify <name> <tag> (trap | inform) (other | volatile |

non-volatile | permanent | read-only) [mod]
Configure the
SNMP
notification
table.
Where:
<name>:
<tag> :
notify name in string form

notify tag in string form
522
CASA CMTS
notify trap
notify inform
storage other
storage volatile
storage non volatile
storage permanent
storage read-only
modify an entry
trap:
inform:
other:
volatile:
non-volatile:
permanent:
read-only:
mod:
Example:
CASA-CMTS(config)#snmp notify
InformV2cSNMPv2cNotifyTagList
InformV2cSNMPv2cNotifyTagList inform n
on-volatile
CASA-CMTS(config) show snmp
Deleting the notification table

To delete the SNMP notification table:
Step
1
Command (config)
Purpose
no snmp notify <name>
Delete the
SNMP
notification
table.
Where:
<name>:
notify name in string form
Configuring the securityToGroup table

To configure the securityToGroup table:
Step
1
Command (config)
Purpose
snmp security (snmpv1 | snmpv2c | usm) <sec_name>

<group_name> (other | volatile | non-volatile | permanent |
read-only) (mod)
Configure the
securityToGr
oup table.
Where:
snmpv1:
snmpv2c:
usm:
<sec_name>:
<group_name>:
other:
volatile:
SNMP version 1
SNMP version 2c
usm
Security name in string form
Group name in string form
Storage other
Storage volatile
523
CASA CMTS
non-volatile:
permanent:
read-only:
mod:
Storage non-volatile
Storage permanent
Storage read-only
Modify an entry
Example:
CASA-CMTS(config)#snmp security snmpv1 rotesting
rotesting non-volatile
Configuring the TargetAddress table

To configure the TargetAddress table:
Step
1
Command (config)
Purpose
snmp tgt-addr <tgt_addr> snmpUDPDomain <td_addr>

<time_out_num> <retry_num> <tag_list> <param> (other |
volatile | non-volatile | permanent | read-only) <mask_value>
<num> [mod]
Configure the
security
TargetAddress
table.
Where:
<tgt_addr>:
snmpUDPDomain
:
<td_addr>:<port>
<time_out_num>:
<retry_num>:
<tag_list>:
<param>:
other:
volatile:
non-volatile:
permanent:
read-only
<mask_value>
<num>
Mod
Target address in string form

td UDP domain
td address and port in dotted decimal
notation.
time-out value
Number of retries
Tag list in string form
Parameters in string form
Storage other
Storage volatile
Storage non-volatile
Storage permanent
Storage read-only
Mask value in string form
MMS integer range 484 to 65535
Modify an entry
Example:
CASA-CMTS(config)# snmp tgt-addr anywhere
snmpUDPDomain 192.168.8.232:162 500 1
anywhereTag none non-volatile 255.255.0.0:162
500
524
CASA CMTS
Deleting the TargetAddress table

To delete the TargetAddress table:
Step
1
Command (config)
Purpose
no snmp tgt-addr <addr>
Delete the
TargetAddress
table.
Where:
<addr>
The target address in string form
Configuring the TargetParameter table

To configure the TargetParameter table:
Step
1
Command (config)
Purpose
snmp tgt-param <param> (0 | 1 | 3) (snmpv1 | snmpv2c |

usm) <sec_name> (no-auth | auth-no-priv | priv) (other |
volatile | non-volatile | permanent | read-only) [mod]
Configure the
TargetParameter
table.
Where:
<param>:
0
1
3
snmpv1
snmpv2c
usm
<sec_name>
no-auth
auth-no-priv
priv
other
volatile
non-volatile
permanent
read-only
mod
Target parameter in string form

snmpv1 processing
snmpv2c processing
snmpv3 processing
snmp v1 model
snmp v2c model
usm model
security name in string form
no auth
auth, no priv
priv
storage other
storage volatile
storage permanent
storage read-only
modify an entry
Example:
CASA-CMTS(config)# snmp tgt-param
InformV3SNMPv3Notify 3 snmpv2c
noAuthNoPrivUser no-auth non-volatile
525
CASA CMTS
Deleting the TargetParameter table

To delete the TargetParameter table:
Step
1
Command (config)
Purpose
no snmp tgt-param <param>
Delete the
TargetParameter
table.
Where:
<param>:
Target parameter in string form.
Configure the ViewTreeFamily table

To configure the ViewTreeFamily table:
Step
1
Command (config)
Purpose
snmp tree-family <view> <subtree> <mask> (include |

exclude) (other | volatile | non-volatile | permanent | readonly) [mod]
Configure the
ViewFreeFamily
table.
Where:
<view>:
<subtree>:
<mask>:
include
exclude
other
volatile
non-volatile
permanent
read-only
mod
view name in string form

subtree name in string form
mask name in string form
include
exclude
storage other
storage volatile
storage permanent
storage read-only
modify an entry
Example:
CASA-CMTS(config)# snmp tree-family
docsisManagerView 1.3.6.1.4.1.9.9 252 exclude
non-volatile
526
CASA CMTS
Deleting the ViewTreeFamily table

To delete the ViewTreeFamily table:
Step
1
Command (config)
Purpose
no snmp tree-family <view> <subtree>
Delete the
ViewFreeFamily
table.
Where:
<view>:
<subtree>:
View name in string form

Subtree name in string form
Configuring the SNMP user table

To configure the User table
Step
1
Command (config)
Purpose
snmp user <engine_id> <user_name> (no-auth | md5 | sha)

(0 | 1) <auth_pswd> (no-priv | des | aes) (0 | 1) <priv_pswd>
(other | volatile | non-volatile | permanent | read-only)
<target_string> [mod]
Configure the
SNMP user
table.
Where:
<engine_id>
<user_name>
no-auth
md5
sha
0
1
<auth_pswd>
no-priv
des
aes
0
1
<priv_pswd>
Other
volatile
local use engine id in string

form
user name in ASCII format
no authentication
MD5 authentication
SHA authentication
use clear authentication
password as input
use encrypted authentication
password as input
authentication password, use
- if no password
no privilege
use DES
use AES
use clear privilege password
as input
use encrypted privilege
password as input
privilege password, use - if no
password
storage other
storage volatile
527
CASA CMTS

storage permanent
storage read-only
target string, use - if no string
modify an entry
non-volatile
permanent
read-only
<target_string>
Mod
Example:
CASA-CMTS(config)#snmp user AuthPrivMD5User
user1 md5 1 zYtNm no-priv 1 - non-volatile
anyWhereTag
Deleting the SNMP user table

To delete the SNMP user table:
Step
1
Command (config)
Purpose
no snmp user <engine_id> <user_name>
Delete the
SNMP User
table.
Where:
<engine_id>
<user_name>
User engine id.

User name in ASCII format
Displaying the SNMP configuration and statistics

To show the SNMP configuration and statistics:
Step
1
Command (config)
Purpose
show snmp
Show the
SNMP
configuration
and statistics.
Example:
See example below.
Example: show snmp

CASA-CMTS (config)# show snmp
SNMP community information
Community
Community
Community
Community
Community
name:
Index:
SecurityName:
StorageType:
Status:
Community name:
private
private
rwtesting
3
active
public
528
CASA CMTS
Community
Community
Community
Community
Index:
SecurityName:
StorageType:
Status:
public
rotesting
3
active
Community
Community
Community
Community
Community
name:
Index:
SecurityName:
StorageType:
Status:
rotesting
rocablelabs
rotesting
3
active
Community
Community
Community
Community
Community
name:
Index:
SecurityName:
StorageType:
Status:
rwtesting
rwcablelabs
rwtesting
3
active
Community
Community
Community
Community
Community
name:
Index:
SecurityName:
StorageType:
Status:
testcom
testcom
rotesting
3
active
SNMP server hosts

Host address : 192.168.0.222
Security model: SNMPv2c
Security Name : rotesting
SNMP agent statistics
snmpInPkts:
11
snmpOutPkts:
2
snmpInBadVersions:
0
snmpInBadCommunityNames: 9
snmpInBadCommunityUses: 0
snmpInASNParseErrs:
0
snmpInTooBigs:
0
snmpInNoSuchNames:
0
snmpInBadValues:
0
snmpInReadOnlys:
0
snmpInGenErrs:
0
snmpInTotalReqVars:
1
snmpInTotalSetVars:
0
snmpInGetRequests:
0
snmpInGetNexts:
1
snmpInSetRequests:
0
snmpInGetResponses:
0
snmpInTraps:
0
snmpOutTooBigs:
0
snmpOutNoSuchNames:
0
snmpOutBadValues:
0
snmpOutGenErrs:
0
snmpOutGetRequests:
0
snmpOutGetNexts:
0
snmpOutSetRequests:
0
529
CASA CMTS
snmpOutGetResponses:
snmpOutTraps:
snmpEnableAuthenTraps:
snmpSilentDrops:
snmpProxyDrops:
0
0
1
0
0
snmp user - root no-auth - no-priv - non-volatile active anywhereTag

snmp user - tapuser md5 - no-priv - non-volatile active tapUserTagList
snmp user - rotesting no-auth - no-priv - non-volatile active
anywhereTag
snmp user - rwtesting no-auth - no-priv - non-volatile active
anywhereTag
snmp user - AuthPrivMD5User md5 - - non-volatile active anywhereTag
snmp user - AuthPrivSHAUser sha - - non-volatile active anywhereTag
snmp user - noAuthNoPrivUser no-auth - no-priv - non-volatile active
anywhereTag
snmp user - AuthNoPrivMD5User md5 - no-priv - non-volatile active
anywhereTag
snmp user - AuthNoPrivSHAUser sha - no-priv - non-volatile active
anywhereTag
snmp security snmpv1 rotesting rotesting non-volatile active
snmp security snmpv1 rwtesting rwtesting non-volatile active
snmp security snmpv2c rotesting rwtesting non-volatile active
snmp security snmpv2c rwtesting rwtesting non-volatile active
snmp security usm root root non-volatile active
snmp security usm tapuser tapUserGroup non-volatile active
snmp security usm AuthPrivMD5User AuthPrivMD5User non-volatile active
snmp security usm AuthPrivSHAUser AuthPrivSHAUser non-volatile active
snmp security usm noAuthNoPrivUser noAuthNoPrivUser non-volatile active
snmp security usm AuthNoPrivMD5User AuthNoPrivMD5User non-volatile
active
snmp security usm AuthNoPrivSHAUser AuthNoPrivSHAUser non-volatile
active
snmp access root usm no-auth exact SNMPv3View SNMPv3View SNMPv3View
non-volatile active
snmp access rotesting snmpv1 no-auth exact docsisManagerView
docsisManagerView non-volatile active
snmp access rotesting snmpv2c no-auth exact docsisManagerView
docsisManagerView non-volatile active
snmp access rwtesting snmpv1 no-auth exact docsisManagerView
docsisManagerView docsisManagerView non-volatile active
snmp access rwtesting snmpv2c no-auth exact docsisManagerView
docsisManagerView docsisManagerView non-volatile active
snmp access tapUserGroup usm auth-no-priv exact TapView TapView
TapView non-volatile active
snmp access AuthPrivMD5User usm auth-priv exact SNMPv3View SNMPv3View
SNMPv3View non-volatile active
snmp access AuthPrivSHAUser usm auth-priv exact SNMPv3View SNMPv3View
snmp access noAuthNoPrivUser usm no-auth exact SNMPv3View SNMPv3View
snmp access AuthNoPrivMD5User usm auth-no-priv exact SNMPv3View
SNMPv3View SNMPv3View non-volatile active
snmp access AuthNoPrivSHAUser usm auth-no-priv exact SNMPv3View
SNMPv3View SNMPv3View non-volatile active
530
CASA CMTS
snmp notify InformV2cSNMPv2cNotifyTagList InformV2cSNMPv2cNotifyTagList

inform non-volatile active
snmp notify InformV3SNMPv3NotifyTagList InformV3SNMPv3NotifyTagList
inform non-volatile active
snmp notify TrapV1SNMPv1TrapsTagList TrapV1SNMPv1TrapsTagList trap nonvolatile active
snmp notify TrapV2cSNMPv2cTrapsTagList TrapV2cSNMPv2cTrapsTagList trap
non-volatile active
snmp notify TrapV2cSNMPv3TrapsTagList TrapV2cSNMPv3TrapsTagList trap
non-volatile active
snmp notify tapUserTrapTagList tapUserTrapTagList trap non-volatile
active
snmp tgt-addr V1SNMPv1Traps snmpUDPDomain 192.168.0.222:162 500 1
V1SNMPv1TrapsTagList V1SNMPv1Traps other active
snmp tgt-param InformV2cSNMPv2cNotify 1 2 rotesting 1 non-volatile
active
snmp tgt-param InformV3SNMPv3Notify 3 3 noAuthNoPrivUser 1 non-volatile
active
snmp tgt-param TrapV1SNMPv1Traps 0 1 rotesting 1 non-volatile active
snmp tgt-param TrapV2cSNMPv2cTraps 1 2 rotesting 1 non-volatile active
snmp tgt-param TrapV2cSNMPv3Traps 3 3 noAuthNoPrivUser 1 non-volatile
active
snmp tgt-param tapUserTrapTag 3 3 tapuser 2 non-volatile active
snmp tree-family TapView 1.3.6.1 - excluded non-volatile active
snmp tree-family TapView 1.3.6.1.4.1.9.9.252 - included non-volatile
active
active
active
active
snmp tree-family TapView 1.3.6.1.4.1.20858.10.19 - included nonvolatile active
snmp tree-family TapView 1.3.6.1.4.1.4491.2.2.9.1.1 - included nonvolatile active
snmp tree-family TapView 1.3.6.1.4.1.4491.2.2.9.1.2 - included nonvolatile active
snmp tree-family SNMPv3View 1.3.6.1 - included non-volatile active
snmp tree-family SNMPv3View 1.3.6.1.4.1.9.9.252 - excluded non-volatile
active
active
active
active
snmp tree-family SNMPv3View 1.3.6.1.4.1.20858.10.19 - excluded nonvolatile active
snmp tree-family SNMPv3View 1.3.6.1.4.1.4491.2.2.9.1.1 - excluded nonvolatile active
snmp tree-family SNMPv3View 1.3.6.1.4.1.4491.2.2.9.1.2 - excluded nonvolatile active
snmp tree-family docsisManagerView 1.3.6.1 - included non-volatile
active
531
CASA CMTS
snmp tree-family docsisManagerView

volatile active
volatile active
volatile active
volatile active
non-volatile active
volatile active
excluded non-volatile active
excluded non-volatile active
1.3.6.1.4.1.9.9.252 - excluded non1.3.6.1.4.1.9.9.394 - excluded non1.3.6.1.4.1.9.9.395 - excluded non1.3.6.1.4.1.9.9.399 - excluded non1.3.6.1.4.1.20858.10.19 - excluded
1.3.6.1.6.3.16.1.5.2 - excluded non1.3.6.1.4.1.4491.2.2.9.1.1 1.3.6.1.4.1.4491.2.2.9.1.2 -
Monitoring the SNMP process at the CMTS

To monitor and restart the SNMP process whenever an unknown SNMP failure occurs, enable
the software-health-check snmpd setting in the CMTS configuration mode. The default setting
is disabled.
Step
1
Command (config)
Purpose
[no] software-health-check snmpd
Enable or
disable
monitoring and
restarting of the
SNMP process
after an SNMP
failure.
Example:
To enable monitoring of the SNMP process:
CASA-CMTS(config)#software-health-check snmpd
To disable monitoring of the SNMP process:
CASA-CMTS(config)# no software-health-check
snmpd
Configuring IPDR
CASA CMTS supports IP Detail Record (IPDR). IPDR is an open, vendor-independent standard
defined in the Network Data Management, and provides billing interface and record-keeping for
any type of services that can be delivered over an IP-based network.
The IPDR server should be set to the default port 4737.
This section describes the CLI commands for the following IPDR operations:
532
CASA CMTS
Displaying the IPDR connection

Displaying IPDR sessions
Restarting/Stopping the IPDR daemon
Configuring IPDR collector mastership
Configuring the IPDR keepalive interval
Configuring the IPDR ACK sequence interval
Configuring the IPDR ACK interval
Configuring the IPDR collector interval
Configuring the IPDR spectrum measurement interval
Setting the IPDR connection primary
Displaying IPDR connections

To display current IPDR connections:
1
show ipdr connection [<chann_name>]

Where:
<chann_name>
Purpose
Display current
IPDR
connections.
Connection channel name in string form.
Displaying IPDR sessions

To display current IPDR sessions:
Step
Command (config)
Purpose
show ipdr session
Display current
IPDR sessions.
Example:
CASA-CMTS(config)#show ipdr session
Restarting and stopping the IPDR daemon

To stop or restart the IPDR daemon:
Step
Command
Purpose
ipdr stop
ipdr restart
Stop or restart
the IPDR
daemon.
Example:
CASA-CMTS# ipdr stop
CASA-CMTS# ipdr restart
533
CASA CMTS
Configuring IPDR collector mastership

To configure an IPDR server as a master collector:
Step
1
Command (config)
Purpose
ipdr collector <conn_index> (primary | secondary)
Configure an
IPDR server.
Where:
<conn_index>
Specifies the connection index of the

collection from the show command.
primary
Specifies the primary collector.
secondary
Specifies the secondary collector.
Configuring the IPDR keepalive time interval

To configure the IPDR keepalive time interval:
Step
1
Command (config)
Purpose
ipdr keepalive <interval>
Configure the
IPDR keepalive
time interval.
Where:
<interval>
Specifies the keepalive time interval in

seconds; values are 1 to 600.
Configuring the IPDR acknowledge sequence interval

To configure the IPDR acknowledge sequence interval:
Step
1
Command (config)
Purpose
ipdr acksequence <interval>
Configure the
IPDR
acknowledge
sequence
interval.
Where:
<interval>
Specified the acknowledgement sequence

interval in seconds.
Configuring the IPDR ACK interval

To configure the IPDR acknowledge time interval:
Step
1
Command (config)
Purpose
ipdr ackTimeInterval <interval>
Configure the
IPDR
acknowledge
Where:
534
CASA CMTS
<interval>
Specifies the acknowledgement time interval in

seconds.
time interval.
Configuring the IPDR spectrum measurement interval

To configure the IPDR spectrum measurement interval:
Step
1
Command (config)
Purpose
ipdr sminterval <interval>
Configure the
IPDR spectrum
measurement
interval.
Where:
<interval>
Specifies the spectrum measurement collection

interval in seconds.
Configuring the IPDR connection to be primary

To configure the IPDR connection to be primary:
Step
1
Command
Purpose
ipdr master <ipaddr>
Configure the
IPDR
connection to
be primary.
Where:
<ipaddr>
Specifies the connection IP address.
Configuring the IPDR loopback interface

To configure the internal CMTS loopback interface for IPDR traffic:
Step
1
Command
Purpose
ipdr source-interface loopback <number>
Configure the
IPDR source
interface for
IPDR traffic.
Where:
<number>
Specifies the IPDR loopback interface in the

range 0 to 15.
Example:
CASA-CMTS# ipdr source-interface loopback 10
535
CASA CMTS
Configuring IPsec
This section describes the CLI commands for IPsec operations currently supported by the Casa
CMTS. The supported operations are:
Enabling IPsec services

Configuring the IPsec PreKey
Deleting the IPsec PreKey
Displaying IPsec PreKey
Configuring IPsec Phase 1
Displaying the IPsec information
Deleting the IPsec configuration
Adding the IPsec security policy
Removing the IPsec security policy
Displaying the IPsec security policy database
Steps to configure IPsec are:

1. Set the pre-shared key.
2. Configure the phase1 parameters.
3. Configure the phase2 parameters.
4. Configure the SPD.
Enabling and disabling the IPsec service

To enable or disable the IPsec service, use the following commands. Note that this command is
not executed in config mode; end the config session first.
IPsec will automatically start when all parameters are correctly configured the first time.
Step
1
Command (config)
Purpose
ipsec start
ipsec stop
Enable or
disable IPsec.
Example:
CASA-CMTS# ipsec start
CASA-CMTS# ipsec stop
All established
SAs will be
cleared after
ipsec stop.
To verify that IPsec is running:

CASA-CMTS# show ipsec info
IKE status: running
Phase I:
Phase II:
536
CASA CMTS
Configuring the IPsec PreKey

To configure or delete the IPsec prekey:
Step
1
Command (config)
Purpose
[no] ipsec <ip_addr> <prekey>
Configure or
delete the
IPsec PreKey.
Where:
<ip_addr>
<prekey>
Remote IP address in dotted decimal format

A.B.C.D. This is the IPsec tunnel peer.
Prekey in string format.
Example:
CASA-CMTS(config)# ipsec 192.168.2.125
PACKETCABLE
CASA-CMTS(config)# show ipsec prekey
192.168.2.125 PACKETCABLE
To delete:
CASA-CMTS(config)# no ipsec 192.168.2.125 prekey
CASA-CMTS(config)#
Displaying the IPsec PreKey

To show the IPsec PreKey:
Step
Command (config)
Purpose
show ipsec prekey
Show the IPsec

prekey.
Example:
CASA-CMTS(config)# ipsec 192.168.2.125
PACKETCABLE
CASA-CMTS(config)# show ipsec prekey
192.168.2.125 PACKETCABLE

To configure IPsec phase 1:
Step
1
Command (config)
Purpose
ipsec phase1 <policy_name> <ip_addr> <lifetime>

<dhgroup> <encry-algorith> <auth-algorith> <use-prekey>
<mode>
Configure IPsec
phase 1.
Where:
<policy_name>:
Policy name in string format. 'all' is

reserved, do not use it
537
CASA CMTS
<ip_addr>:
<lifetime>:
<dhgroup>:
<encryalgorith>:
<auth-algorith>:
<use-prekey>:
<mode>:
Remote IP address in dotted format

A.B.C.D, - for any
Llifetime in unit of minutes.
diffie-hellman group, 1 or 2
Encryption algorithm, 3des or des
Authentication algorithm,md5 or sha
Use pre-shared key or not.
Main or aggressive
Example:
CASA-CMTS(config)# ipsec phase1 test 10.170.1.1
60 1 3des md5 psk aggressive
To verify Phase 1 settings:
CASA-CMTS(config)# show ipsec info
IKE status: running phase I:
policy name : test
IP address
: 10.170.1.1
exchange mode: aggressive
lifetime
: 60
proposal
: encryption : tripple DES
hash
: MD5
auth-method: pre-shared key
dh-group
: 1

To configure IPsec phase 2:
Step
1
Command (config)
Purpose
ipsec phase2 <policy_name> <src_ip_addr> <dst_ip_addr>

<group> <lifetime> <encry-algorith> <auth-algorith> deflate
Configure IPsec
phase 2.
Where:
<policy_name>
<src_ip_addr>
<dst_ip_addr>
<group>
<lifetime>
Policy name, 'all' is reserved, please do

not use it
Source ip address; for any, then
destination IP will not take effect
Destination IP address in dotted format
A.B.C.D
diffie-hellman group, 0 refers to a group
not specified, 1 refers to PFS group 1
Interval for re-key in unit of minutes.
538
CASA CMTS
<encryalgorith>
<auth-algorith>
deflate
Encryption algorithm, 3des or des

Authentication algorithm.
Deflate compression.
Example:
CASA-CMTS(config)#
ipsec phase2
10.170.2.1 0 60 des md5 deflate
To verify Phase 2 settings:

CASA-CMTS(config)# show
IKE status: running
phase II:
policy name
:
IP address source :
IP address remote :
lifetime
:
encryption
:
hash
:
compression-method:
test
10.170.1.1
ipsec info
test
10.170.1.1
10.170.2.1
60
des
MD5
deflate
Displaying IPsec information

To show IPsec information:
Step
1
Command
Purpose
show ipsec info
Show IPsec
information.
Example:
IKE status: running
phase I:
policy name :
IP address
:
exchange mode:
lifetime
:
proposal
:
test
10.170.1.1
aggressive
60
encryption :
hash
:
auth-method:
dh-group
:
phase II:
policy name
:
IP address source :
IP address remote :
lifetime
:
encryption
:
hash
:
compression-method:
triple DES
MD5
pre-shared key
1
test
10.170.1.1
10.170.2.1
60
des
MD5
deflate
539
CASA CMTS
Deleting the IPsec configuration

To delete IPsec configuration:
Step
1
Command (config)
Purpose
no ipsec <phase_num> <policy_name>
Delete IPsec
configuration.
Where:
<phase_num>:
<policy_name>:
Phase1or phase2
Policy name in string format or all for all
policies.
Example:
CASA-CMTS(config)# no ipsec phase1
192.168.2.125server
IKE status: running
phase I:
phase II:
policy name : 192.168.2.125server
IP address source : 192.168.2.247
IP address remote : 192.168.2.125
lifetime : 5
encryption : 3des
hash : SHA
Adding an IPsec security policy

To add or remove an IPsec security policy:
Step
1
Command (config)
Purpose
[no] ipsec spd <local_ip_addr> <local_port_num>

<remote_ip_addr> <remote_port_num > (in | out)
Add or remove
an IPsec
security policy.
Where:
spd:
<local_ip_addr>:
<local_port_num>:
<remote_ip_addr>:
<remote_port_num>:
in:
out:
[no]
SPD command.
Local IP address in dotted format.
Local udp port number, 0 for all traffic.
Remote IP address in dotted decimal
format.
UDP port number, 0 for all traffic
Direction incoming.
Direction outgoing.
Remove the IPsec security policy.
540
CASA CMTS
Displaying the IPsec security policy database

To display the security policy database:
Step
1
Command (config)
Purpose
show ipsec spd [detail]
Display the
security policy
database.
Example:
CASA-CMTS(config)#show ipsec spd
IPsec SPD configuration:
remote ip address: 192.168.2.125
local ip address : 192.168.2.247
protocol
: any
direction
: in
ipsec mode
: ESP
local ip address :
remote ip address:
protocol
:
direction
:
ipsec mode
:
The detail view

shows all SAs
currently
existing in the
system.
192.168.2.247
192.168.2.125
any
out
ESP
Example:
CASA-CMTS(config)# show ipsec spd detail
192.168.2.125 192.168.2.247
esp mode=transport
spi=52611555(0x0322c9e3) reqid=0(0x00000000)
E: 3des-cbc 55ae1807 339b4a01 01a8f8a9
9c988f29 7f9cf461 d343cd21
A: hmac-sha1 bb6f05b7 06c68b44 15bab266
3ff302d1 09d4d374
seq=0x00000000 replay=4 flags=0x00000000
state=mature
created: Jun 30 14:11:09 2008
current:
Jun 30 14:11:12 2008
diff: 3(s)
hard: 300(s)
soft:
240(s)
last: Jun 30 14:11:09 2008
hard:
0(s)
soft: 0(s)
current: 128(bytes)
hard: 0(bytes)
soft: 0(bytes)
allocated: 2
hard: 0 soft: 0
sadb_seq=1 pid=924 refcnt=0
192.168.2.247 192.168.2.125
esp mode=transport
spi=4055512964(0xf1ba3784) reqid=0(0x00000000)
E: 3des-cbc e87c92e6 f13102d3 50840db3
d3f42dc9 5efce445 efe14f97
A: hmac-sha1 784a8db4 0386eede 8423adc9
281ddcf5 1fd49c84
seq=0x00000000 replay=4 flags=0x00000000
state=mature
created: Jun 30 14:11:09 2008
current:
Jun 30 14:11:12 2008
diff: 3(s)
hard: 300(s)
soft:
541
CASA CMTS
240(s)
last: Jun 30 14:11:09 2008
hard:
soft: 0(s)
current: 240(bytes)
hard: 0(bytes)
soft: 0(bytes)
allocated: 2
hard: 0 soft: 0
sadb_seq=0 pid=924 refcnt=0
0(s)
Managing cable modems

The Casa CMTS allows users to manage how cable modems operate in the HFC network. This
section covers commands for the following operations:
Showing cable modem status
Showing the cable modem CPEs
Showing the registered cable modems
Showing the cable modem flap list
Showing the cable modem summary
Showing the cable modem remote-query
Configuring the cable modem access-group
Changing the cable modem frequency
Setting the cable modem max-CPE
Setting the cable modem max-hosts
Setting the cable modem QoS profile
Enabling cable modem authentication
Clearing cable modem counts
Clearing the cable modem offline
Clearing the cable modem reset
Displaying cable modem status

To display information for the registered and unregistered CMs, use the show cable-modem
command in privileged mode. The output is sorted by cable interface and the CM MAC address.
Step
1
Command
Purpose
show cable modem [<ip-address> | <ipv6-address | macaddress] [verbose]
Show the cable

modem status.
Where:
ip-address
ipv6-address
Identifies the IP address of a specific CM to

be displayed. If you specify the IP address
542
CASA CMTS
for a CPE device behind a CM, information

for that CM is displayed.
mac-address
Identifies the MAC address of a specific CM

to be displayed. You can also specify the
MAC address for a CPE device behind a CM,
and information for that CM will be displayed.
verbose
Displays detailed information for the CMs.
Example:
Show the default displays for individual CMs.
CASA-CMTS# show cable modem
MAC Address
IP Address
US
MAC
Intf
Status
Sid (dB) Offset CPEs Enb
0011.8078.1950 0.0.0.0
3/2/0
offline
0
0.0
0
0
no
0011.e6bb.e3b1 10.190.1.98
3/3/0
online
3
0.0
1971
0
no
0014.6cb9.ffbb 10.190.1.99
3/0/0
online
4
-0.5 1989
1
no
0015.f2fe.cef5 0.0.0.0
3/0/0
init(rc)
6
0.0
2079
0
no
online cm 2 ; offline cm 1 ; ranging cm 1
DS
Intf
0/1/2
0/1/1
0/1/0*
0/1/3
Example: Show cable modem status

Show the default CM displays for the CM with the specified mac-address.
CASA-CMTS# show cable modem 0011.8078.1950
MAC Address
IP Address
US
DS
RxPwr Timing Num BPI
Intf
Intf
Offset CPEs Enb
0011.8078.1950 10.237.1.102
3/2/0
0/1/2
1906
1
yes
MAC
Prim
Status
Sid
(dB)
online
0.0
See Table 3 for a description of the MAC status field.
Table 3. MAC status fields

MAC State
Description of registration and status conditions
Value
init(r1)
Initial ranging request sent by cable modem (CM) to CMTS.
init(r2)
The CMTS received an initial ranging rquest from the CM. The CMTS has
responded and returned RF power information, timing offset, and frequency
adjustments to the CM. The CM and CMTS link is still in the ranging state, and
543
CASA CMTS
ranging is not complete.

Check the RF attenuations if initial ranging remains stuck. Use the debug cable
ranging command for information.
init(ov)
CMTS is static load balancing and is using the upstream channel ID override
and/or downstream frequency override to move the modem to new channel.
Check the modem power if stuck in this state.
init(rc)
CM ranging to the CMTS has completed. Check the cable helper address
configuration and IP connectivity to the DHCP server. Use debug cable dhcp
command for information.
Note: It is also possible that the upstream is at capacity and has no additional
bandwidth for the CM to finish registration and come online. If this is the case
make sure load balancing is enabled.
init(ua)
Upstream channel adjustment (for DOCSIS 3.0 modems).
init(d)
CMTS has received the DHCP discover message; first IP broadcast packet has
been received from the CM.
init(i)
The CM has received the DHCPOFFER reply from the DHCP server, but the CM
has not yet replied with a DHCPREQUEST message, nor has it sent an IP packet
with its assigned IP address.
It is possible that the CM has received the DHCPOFFER reply from the DHCP
server, but the reply might have invalid options for that particular CM.
init(e)
Early authentication and encryption started (3.0 modems).

Check the modem certificate if stuck in this state.
init(t)
Configuration file download complete; time-of-day (TOD) exchange started.
init(r)
CMTS received register-request from cm,but has not received reg-ack yet.
If stuck, check the modem config file. Use debug cable registration to debug
registration request received.
init(bpi)
Start baseline privacy. If stuck in this state, check the modem certificate and
ensure that the CM is synchronized with the BPI server.
resetting
The CM is being reset; registration process restarting.
Non-error Status Conditions

cc(r1)
The CM had previously registered and was online, but the CMTS has sent a
Downstream Channel Change (DCC) or Upstream Channel Change (UCC)
request message to the CM. The CM has started moving to the new channel,
sending an initial ranging request on the new downstream or upstream channel to
the CMTS. At the MAC layer, the CM is not yet passing traffic on the new channel
and is considered in the offline state. This state does not trigger the flap-list
counters.
cc(r2)
This state normally follows cc(r1) and indicates that the CM has finished its initial
ranging on the new channel, and is currently performing continuous ranging on the
new channel. At the MAC layer, the CM is not yet passing traffic on the new
channel and is considered in the offline state. This state does not trigger the flaplist counters.
544
CASA CMTS
offline
The CM is detected as offline, disconnected, or powered off.
online
The CM has registered; modem is ready to pass data on the network.
online(d)
The CM is registered. However, network access for CPE devices using this CM
has been disabled by the DOCSIS configuration file. The CMTS continues to
communicate with the CM using DOCSIS messages and IP traffic (such as SNMP)
but the CM does not forward traffic to or from the CPE devices,
Note: If BPI was enabled in the DOCSIS configuration file sent to the CM, the CM
is using BPI encryption unless other messages indicate that the BPI negotiation
and key assignments have failed.
online(pkd) The CM has registered with the CMTS. However, network access for CPE devices
using this CM has been disabled through the DOCSIS configuration file. BPI is
enabled and the key-encrypting key (KEK) is assigned.
online(pt)
The CM has registered with the CMTS. BPI is enabled and traffic-encrypting key
(TEK) is assigned. BPI encryption is now being performed.
online(ptd) The CM has registered with the CMTS. However, network access for CPE devices
using this CM has been disabled through the DOCSIS configuration file. BPI is
enabled and traffic-encrypting key (TEK) is assigned. BPI encryption is now being
performed. This state is equivalent to the online(d) and online(pt) states.
online(pk)
The CM has registered with the CMTS. BPI is enabled and the key-encrypting key
(KEK) is assigned.
expire(pk)
The CM has registered. BPI is enabled and the KEK was assigned, but the
current KEK expired before the CM could successfully renew a new KEK value
expire(pke) The CM has registered. However, network access for CPE devices using this CM
has been disabled through the DOCSIS configuration file. BPI is enabled and the
KEK was assigned, but the current KEK expired before the CM could successfully
renew a new KEK value. This state is equivalent to the online(d) and expire(pk)
states
expire(pt)
The CM has registered. BPI is enabled and the TEK was assigned. The current
TEK expired before the CM could successfully renew a new KEK value.
expire(ptd) The CM has registered. However, network access for CPE devices using this CM
has been disabled through the DOCSIS configuration file. BPI is enabled and
traffic-encrypting key (TEK) was assigned, but the current TEK expired before the
CM could successfully renew a new KEK value. This state is equivalent to the
online(d) and expire(pt) states.
Error status conditions
reject(pk)
The KEK assignment is rejected and BPI encryption has not been established.
reject(pkd) The CM has registereed. However, network access for CPE devices using this CM
has been disabled through the DOCSIS configuration file. BPI encryption was not
established because KEK assignment was rejected. This state is equivalent to the
online(d) and reject(pk) states.
reject(pt)
The TEK assignment is rejected and BPI encryption has not been established.
reject(ptd)
The CM has registered. However, network access for CPE devices using this CM
has been disabled through the DOCSIS configuration file. BPI encryption was not
established because TEK assignment was rejected. This state is equivalent to the
online(d) and reject(pt) states.
545
CASA CMTS
Example: show sample cable modem verbose

CASA-CMTS# show cable modem 0050.f112.b764 verbose
MAC Address
:0026.5e77.43b3
IP Address
:10.248.1.103
Prim Sid
:8
MAC Domain
:1
Upstream Channel Set
:1/0/0, 1/1/0, 1/4/0, 1/5/0
Downstream Channel Set
:0/1/0, 0/1/1, 0/1/2, 0/1/3
Unusable channel list
:
Timing Offset
:2030
Initial Timing Offset
:2026
Received Power
:0 dBmV
MAC Version
:DOC3.0
Qos Provisioned Mode
:DOC1.1
Enable DOCSIS2.0 Mode
:Y
Initial Ranging Message
:B-INIT-RNG-REQ
Registration Request Message
:REG-REQ-MP
Phy Operating Mode
:atdma
Capabilities
:{Frag=Y, Concat=Y, PHS=Y, Priv=BPI}
Optional Filtering Support
:{802.1P=N, 802.1Q=N}
Number of CPE IPs
:0
CFG Max-CPE
:16
Errors
:0 CRCs,0 HCSes
Stn Mtn Failures
:0 aborts,0 exhausted
Total US Flows
:1
Total DS Flows
:1
Total US Data
:128 packets,9074 bytes
Total US Throughput
:0 kbits/sec,0 packets/sec
Total DS Data
:6 packets,1039 bytes
Total DS Throughput
:0 kbits/sec,0 packets/sec
Upstream Dropped Packets
:0
Active Classifiers
:0
DSA/DSX messages
:permit all
Total Time Online
:0 d, 0 h, 58 m, 39 s
sysDescr
:Cisco EPC3212 DOCSIS 3.0 2-PORT EMTA
<<HW_REV: 1.0; VENDOR: Cisco; BOOTR: 2.3.0_R1; SW_REV: epc3212-E10-5-v302r12901-100121cZIG; MODEL: EPC3212>>z<AC>
Table 4. show cable modem fields

Field
Description
MAC Address
The MAC address of the CM.
IP Address
The IP address assigned by the DHCP server to the CM.
Prim Sid
The primary SID assigned to this CM.
MAC Domain
MAC domain ID.
Upstream
The line card/port/channel providing the upstream for this CM.
Downstream
The line card/port/channel providing the downstream for this CM.
Upstream
Channel Set
The set of upstream channels assigned to this modem for bonding (3.0
modems).
Downstream
Channel Set
The set of downstream channels assigned to this modem for bonding (3.0
modems).
546
CASA CMTS
Unusable
channel list
List of assigned channels that are not usable by the modem.
MAC State
The current state of the MAC layer.
Received
Power
The power level (in dB) received by the CM.
Timing Offset
The timing offset for the CM, in ticks, as recognized by the CMTS. (A tick is
6.25/64 microseconds.) This is the delay between when a particular cable
modem is scheduled to make a transmission and when the CMTS actually
receives it.
Note: The timing offset shown here is typically smaller than the TX Time
Offset value shown by the show cable modem remote-query command, since
the latter value is the offset as recognized on the CM (which will include any
internal delay between when the CM software begins the transmission and
when the bits actually appear on the local cable interface).
Initial Timing
Offset
The initial timing offset for the CM, in ticks, as recognized by the CMTS (see
above).
Num CPEs,
CFG Max-CPE
Indicates the number of CPE devices for which the CM is providing services.
Number of
CPE IPs
Indicates the maximum number of IP addresses assigned to CPE devices

behind this CM, as configured by the cable max-hosts command.
Ver, MAC
Version
Displays the maximum supported version of DOCSIS that the CM supports

(DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0, DOCSIS 3.0).
QoS Prov, QoS Displays the version of DOCSIS that the CM currently is provisioned for
(DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0).
Provisioned
Mode
Enable
DOCSIS 2.0
Mode
Indicates whether the CM is capable of DOCSIS 2.0 (ATDMA) operation, as

determined by the presence and value of the Enable 2.0 Mode (TLV39) field in
the CM's Registration Request message or in the DOCSIS configuration file.
The valid values are:
Y = TLV 39 was set to 1, indicating that the CM has enabled DOCSIS 2.0
mode. The CM could still be registered for DOCSIS 1.1 operations, however,
on DOCSIS 1.X interfaces.
N = Either the TLV 39 field was not present in the CM's Registration
Request message, indicating that the CM is not capable of DOCSIS 2.0
operations, or the TLV 39 field was set to 0 in the DOCSIS configuration file,
preventing the CM from using the DOCSIS 2.0 mode.
Initial Ranging Initial ranging message that the CM sends: RNG-REQ for DOCSIS 1.0/1.1/2.0
CMs, B-INIT-RNG-REQ for DOCSIS 3.0 CM.
Message
Registration
Registration request message that the CM sends: REG-REQ for DOCSIS
547
CASA CMTS
Request
Message
1.0/1.1/2.0 CMs, REG-REQ-MP for DOCSIS 3.0 CM.
Phy Operating
Mode
Indicates the type of PHY-layer modulation that the CM is using: tdma or

atdma.
BPI Enbld
Indicates whether Baseline Privacy Interface (BPI) or BPI Plus (BPI+)

encryption is enabled for the CM.
Capabilities
Indicates what the CM reported as its capabilities in its Registration Request

message: DOCSIS fragmentation, concatenation, packet header suppression
(PHS), and BPI encryption.
Optional
Filtering
Support
Indicates whether 802.1P or 802.1Q packet filtering is enabled for this CM.
Transmit
Equalizer
Support
Number of taps being used for transmit equalization.
Errors
Number of frame CRC and HCS errors reported for this CM.
Sn Mtn
Failures
Number of station maintenance failures (aborts and retries).
Total US Flows Total number of upstream service flows, with the number of active service
flows within the parentheses.
Total DS Flows Total number of downstream service flows, with the number of active service
flows within the parentheses.
Total US Data
Total data this CM has transmitted on the upstream, in packets and bytes.
Total US
Throughput
Calculated throughput for this CM on the upstream, if available.
Total DS Data
Total data this CM has received on the downstream, in packets and bytes.
Total DS
Throughput
Calculated throughput for this CM on the downstream, if available.
Upstream
Dropped
Packets
Number of packets dropped on the upstream interface.
Active
Classifiers
Current number of active classifiers for this CM, with the maximum number of
allowable classifiers for this CM within the parentheses.
DSA/DSX
messages
Indicates whether dynamic service changes (DSX) from the cable modem are
permitted (permit all) or disallowed (reject all).
Dynamic
Secret
Dynamically-generated shared secret (a 16-byte hexadecimal value) that was

used in the cable modem's previous registration cycle. If the cable modem is
currently offline, this field shows all zeroes.
Note: This field displays a value only when the cable dynamic-secret
548
CASA CMTS
command has been used on the CMTS interface.

Total Time
Online
Amount of time in days, hours, and minutes that this CM has been
continuously online since it last registered with the CMTS. This field begins
incrementing whenever the CM enters one of the online(x) MAC states, and is
reset to 0 whenever the CM enters any other MAC state.
sysDescr
Cable modem information.
Displaying cable modem CPE devices

To display the CPE devices accessing the cable interface through a particular CM, use the show
cable modem cpe command in privileged mode.
Step
1
Command
Purpose
show cable modem [<ip-address> |<ipv6-address> | macaddress] cpe
Display the
CPE devices.
Where:
<ip-address>
<ipv6-address>
Displays the CPE devices for the CM

with the specified IP address.
<mac-address>
Displays the CPE devices for the CM

with the specified MAC address.
Example:
List the CPE devices by their MAC and IP addresses:
CASA-CMTS# show cable modem 0050.bfb9.021d cpe
CPE IP Address Method CPE MAC Address
Address
CM MAC Address
10.190.1.143
static 0064.0102.0101
10.190.1.7
0050.bfb9.021d
CM IP
Displaying cable modems by state

To display a list of the CMs by state, use the show cable modem {init | offline | online}
command in privileged mode:
Step
1
Command
Purpose
show cable modem [init | offline | online]
Display the
CMs by state.
Example:
See examples below.
549
CASA CMTS
Example: Show cable modems by state

Show sample output for the default form of the show cable modem init command.
CASA-CMTS# show cable modem init
MAC Address
IP Address
US
Intf
0005.ca6d.0120 0.0.0.0
3/2.0/0
0024.d18e.b1cf 0.0.0.0
3/0.0/0
total cm 2
DS
Intf
0/1/0
0/0/2
MAC
Status
init(i)
init(d)
Prim
Sid
402
401
RxPwr
(dB)
-0.2
0.0
Timing
Offset
2487
2245
Num
CPEs
0
0
BPI
Enb
no
no
Show sample output for the default form of the show cable modem registered command.
CASA-CMTS# show cable modem online
Interface
Rx
RX
MAC Address
SM
Power
3/0/0
0.0
3/0/0
0.2
Exhaust Count
0015.f2fe.bf1a
0
0050.bfb9.021d
0
SNR
42.1
42.1
Prim
Previous
Online
Sid
State
Time
online
Tue May 12 08:56:31 2009
online
Tue May 12 08:56:30 2009
Cable modem summary information

The show cable modem command has the following options:
<ipAddress>
Cable modem IPv4 address; A.B.C.D
<mac_addr>
Cable modem MAC address; xxxx.xxxx.xxxx
<ipv6_address>
Cable modem IPv6 address; xxxx:xxxx:...:xxxx
authorization
Display trusted cable modem configurations
bonding
Display cable modem bonding
calls
Display total number of calls that have been processed at this cable
modem.
cm-status
Display the cable modem status log
counters
Display cable modem upstream and downstream counter information

in bytes.
cpe
Display customer premises equipment and the associated IP and

MAC addresses.
deny
Display cable modems that are denied registration at the CMTS.
docsis-deviceclass
Display DOCSIS device class information.
docsis-mac
Display cable modems per MAC domain.
downstream
Display cable modem statistics on CMTS downstream interfaces.
dropped-packets
Display dropped packet counts on upstream and downstream

interfaces.
errors
Display upstream and downstream CRC and HCS errors.
init
Display total cable ip modems that have initialized and are in the init
550
CASA CMTS
state.
ip-address
Display IPv4 and IPv6 cable modem addresses.
mac
Display cable modem MAC information.
maintenance
Display cable modem active time statistics per interface.
non-bonding
Display cable modem non-bonding (modems capable of bonding but

have only 1 channel assigned
offline
Display previously-registered cable modems that are now offline.
online
Display the current list of cable modems that have a MAC status of
online.
phy
Display cable modem physical information statistics, such as

transmission and signal-to-noise reduction data.
qos
Display quality-of-service statistics including transmission and

throughput rates.
remote-query
Display cable modem performance statistics immediately, or at the

specified upstream or downstream module.
rogue
Display cable modems spoofing statistics during ranging.
summary
Display cable modem summary information, including total modem

counts, active and offline modems, modems that have registered, and
secondary modems.
tftp-bypass
Display cables that have bypassed TFTP and have not uploaded a
modem configuration file.
upstream
Display cable modems per the specified system upstream slot, port
number, physical channel number, and upstream logical channel.
vendor
Display cable modem vendor-specific information, or filtered vendor

information using the all, config, default, or summary options.
verbose
Displays the extended version of the show cable modem command

output by including all statistics.
In addition, the following information can be displayed about each cable modem by specifying the
MAC or IP address: show cable modem [<mac-address> | <ip-address> | < ipv6-address>]:
classifiers
Displays downstream classifiers information.
calls
Display total number of calls that have been processed at this

cable modem.
counters
Display cable modem upstream and downstream counter

information in bytes.
cpe
Display customer premises equipment and the associated IP

and MAC addresses.
docsis-device-class
Display DOCSIS device class information.
dropped-packets
Display dropped packet counts on upstream and downstream
551
CASA CMTS
interfaces.
errors
Display upstream and downstream CRC and HCS errors.
mac
Display cable modem MAC information.
maintenance
Display cable modem active time statistics per interface.
multicast-session
Display multicast session information.
mask
Display remote query statistics
online
Display the current list of cable modems that have a MAC status
of online.
phy
Display cable modem physical information statistics, such as

transmission and signal-to-noise reduction data.
qos
Display quality-of-service statistics including transmission and

throughput rates.
remote-query
Display cable modem performance statistics immediately, or at

the specified upstream or downstream module.
vendor
Display cable modem vendor-specific information, or filtered

vendor information using the all, config, default, or summary
options.
verbose
Displays the extended version of the show cable modem

command output by including all statistics.
Configuring the cable modem flap list

The Casa CMTS has a flap-list command that can be used for detecting abnormal CM(s) in the
network. It provides a list of malfunctioning CM(s), and assists the user in identifying the
problem. The user can define several parameters for determining which modems are put in the
flap list. These parameters are:
Set the flap-list insertion time
Set the flap-list power-adjust threshold
Set the flap-list miss threshold
Set the flap list aging
Configure the flap-list check interval
Configure the flap-list size
552
CASA CMTS
Setting the flap list insertion time

During a certain period, if the CM constantly sends out initial ranging requests, then it will be put
into flap-list table for observation. The default value is 60 seconds. This command can be
disabled by a "no" form of this command:
Example: Set the flap-list insertion-time to 5 seconds:
CASA (config)# cable flap-list insertion-time 5
Example: Recover flap-list insertion-time default value:
CASA(config)# cable flap-list insertion-time default
Example: Cancel flap-list insertion-time configuration:
CASA(config)# no cable flap-list insertion-time
Setting the flap list power adjust threshold

After the CMs come online and the status is stable, if the power adjustment from the CMTS to the
CMs is greater than a certain unit of dB, the CMs will be moved to the flap-list table for
observation. This command can be disabled by the "no" form of the command:
Example: Set up flap-list power-adjust threshold as 5:
CASA(config)# cable flap-list power-adjust threshold 5
Example: Recover flap-list power adjust default value:
CASA(config)# cable flap-list power-adjust threshold default
Example: Cancel flap-list power adjust:
CASA(config)# no cable flap-list power-adjust threshold
Configuring the flap list miss threshold

When the CMs do not reply to the maintenance message sent from the CMTS after a certain
number of times, they will be put into the flap-list table for observation. The default value is 6
times. The command can be canceled using the "no" form of this command.
Example: Set up flap-list miss threshold as 5:
CASA(config)# cable flap-list miss threshold 5
Example: Recover flap-list miss threshold default value:
CASA(config)# cable flap-list miss threshold default
Example: Cancel flap-list miss threshold:
CASA(config)# no cable flap-list miss threshold
553
CASA CMTS
Configuring flap list aging

Configure the period which the CMs will be maintained in the flap-list table. If the time limit is
reached, the CMs will be removed from the flap-list table. After the CM is removed, the user
cannot get flap-list information about this CM. The default value is 10,080 minutes (one week).
Example: Configure the flap-list aging as 120 minutes:
CASA(config)# cable flap-list aging 120
Example: Recover flap-list aging default value:
CASA(config)# cable flap-list aging default
Configuring the flap list check interval

Set up the interval for the CMTS to scan the flap-list table. If the CMTS finds any CM that has
reached the aging limit, the CMTS will remove it from the flap-list table. When the CM is removed,
the user cannot check the CM's flap-list information. The default value is 120 minutes.
Example: Configure the flap-list check-interval as 20 minutes:
CASA(config)# cable flap-list check-interval 20
Example: Recover flap-list check-interval default value:

CASA(config)# cable flap-list check-interval default
Showing the cable modem flap-list

To display the CMs that are flapping on one or more cable interfaces, use the show cable flap-list
command in privileged mode. The command will display up to 100 records by default. The
command has several arguments that allow the user to display specific information about the
modems:
Example: show cable flap-list

Display all CM records in the flap-list:
CASA> show cable flap-list
Display specified CM record by MAC address:
CASA> show cable flap-list ****.****.****
Display specified CM record by MAC address and subnet mask:
CASA> show cable flap-list ****.****.**** mask ****.****.****
Display specified CM record by upstream physical channel:
CASA> show cable flap-list upstream x/y
Display specified CM record by upstream logical channel:
554
CASA CMTS
CASA> show cable flap-list upstream x/y/z

Display CM record of specified downstream channel:
CASA> show cable flap-list downstream x/y/z
Sort the displayed results by sequence of the latest offline:
CASA> show cable flap-list sort-time
CASA> show cable flap-list downstream x/y/z sort-time
Sequence the displayed results by the latest upstream logical channel order:
CASA> show cable flap-list sort-int
CASA> show cable flap-list downstream x/y/z sort-int
Order the displayed results by flap value:
CASA> show cable flap-list sort-flap
CASA> show cable flap-list downstream x/y/z sort-flap
Sequence the results by CM MAC address:
CASA> show cable flap-list sort-mac
CASA> show cable flap-list downstream x/y/z sort-mac
Display detailed flap-list of CMs with specified MAC address:
CASA> show cable flap-list ****.****.**** detail
Example: Show the modem flap list output

Start Time
Offline Time
-2009-08-23,21:51:20
2009-08-24,16:39:28
2009-08-24,20:20:35
2009-08-25,15:28:56
2009-08-25,18:53:52
Hit
Miss(%)
CRC
P-Adj
ARP-TO
1938
States
768 (28.4%)
online
1291
342 (20.9%)
init(r2)
1210
175 (12.6%)
init(r2)
Showing the cable modem summary (Release 5.2)

To display a summary of CMs on one or more cable interfaces, use the show cable modem
command in privileged mode.
Step
1
Command
Purpose
show cable modem summary [total]
Display a
summary of
CMs on one or
more cable
interfaces.
Where:
total
Displays the totals for each column.
Example:
See examples below.
555
CASA CMTS
Example: show cable modem summary

Default form of the show cable modem summary command:
CASA-CMTS# show cable modem summary
Upstream
Interface
1/0/0
1/0/1
1/1/0
1/1/1
1/2/0
1/2/1
1/3/0
1/3/1
Total
Modems
2
0
0
0
0
0
2
0
Active
Modems
2
0
0
0
0
0
1
0
Registered
Modems
2
0
0
0
0
0
1
0
Example: Show cable modem summary command with the total option:
CASA-CMTS# show cable modem summary total
CASA#show ca mo summary total
Upstream
Total
Active Registered
Interface Modems Modems Modems
1/0.0/0
0
0
0
1/0.1/0
1
1
1
1/1.0/0
0
0
0
1/1.1/0
0
0
0
1/2.0/0
0
0
0
1/2.1/0
0
0
0
1/3.0/0
0
0
0
1/3.1/0
0
0
0
1/4.0/0
0
0
0
1/4.1/0
0
0
0
1/5.0/0
0
0
0
1/5.1/0
0
0
0
1/6.0/0
0
0
0
1/6.1/0
0
0
0
1/7.0/0
0
0
0
1/7.1/0
0
0
0
Total:
1
1
1
Secondary
Modems
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Offline Channel
Modems Description
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Displaying the cable modem summary (Release 5.4)

To display a summary of CMs on one or more cable interfaces, use the show cable modem
command in privileged mode.
Step
1
Command
Purpose
show cable modem summary [total]
Display a
summary of
CMs on one or
more cable
interfaces.
Where:
total
The totals for each column.
556
CASA CMTS
Example:
See examples below.
Example: show cable modem summary

Default form of the show cable modem summary command:
CASA-CMTS# show cable modem summary tot
Upstream Total
Description
Interface Modems
1/0.0/0
0
WC-02322
1/0.1/0
0
WC-02323
1/1.0/0
0
WC-02324
Total:
0
Active
Modems
0
Registered
Secondary
Offline
Modems
0
Modems
0
Modems
Displaying the cable modem on downstream channels

To show all the cable modem on downstream channel:
Step
1
Command
Purpose
show cable modem downstream {< X/Y/Z> | summary}
Show all the

cable modem
on a
downstream
channel.
Where:
<x>
<y>
<z>
summary:
line card slot number.

port number.
channel number for downstream module.
display
cable
modem
summary
information.
Example:
See examples below.
Example: show cable modem on downstream channels

CASA-CMTS>show cable modem downstream summary
Downstream
Total
Active Registered
Interface
Modems Modems Modems
2/0/0
6
6
6
2/0/1
6
6
6
2/0/2
7
6
6
2/0/3
7
7
7
2/1/0
0
0
0
2/1/1
0
0
0
557
CASA CMTS
2/1/2
2/1/3
2/2/0
2/2/1
2/2/2
2/2/3
2/3/0
2/3/1
2/3/2
2/3/3
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
Example: show cable modem on downstream channel 2/0/0

CASA-CMTS#show cable modem downstream 2/0/0
MAC Address
IP Address
US
DS
Intf
Intf
0015.f2fe.9160 10.170.1.9
1/7.0/0
2/0/0
0015.f2fe.98a4 10.170.1.22
1/0.0/0
2/0/0
0015.f2fe.9ad5 10.170.1.27
1/0.0/0
2/0/0
0015.f2fe.9ad8 10.170.1.31
1/0.0/0
2/0/0
0015.f2fe.ba88 10.170.1.23
1/7.1/0
2/0/0
0015.f2fe.ce86 10.170.1.10
1/0.1/0
2/0/0
MAC
Status
online
online
online
online
online
online
Prim
Sid
282
269
288
279
274
257
RxPwr
(dB)
0.7
-0.5
1.0
0.5
0.0
0.5
Timing
Offset
2404
2404
2405
2404
2405
2405
Num
CPEs
0
0
0
0
0
0
BPI
Enb
no
no
no
no
no
no
Displaying cable modem physical information

To show all the cable modem physical information on all upstream and downstream channels, as
well as signal-to-noise ratios:
Step
1
Command
Purpose
show cable modem phy
Show all the

cable modem
physical
information.
Example:
See examples below.
Example: show cable modem physical information

CASA-CMTS#show cable modem phy
MAC Address
US IF
0018.4de7.3d2a 11/0.0/0
c446.199d.fee8 11/0.0/0
DS IF
Sid
1/0/0
1/0/0
1
5
USPwr(dB)
TX
RX
-0.5
0.7
USSNR
(dB)
30.8
27.4
Timing
Offset
-
MicroReflec
(dBc)
-
DSPwr
(dB)
-
DSSNR Mode
(dB)
tdma
tdma
Showing the cable modem remote-query

To show all the cable modem remote-query information:
Step
1
Command
Purpose
show cable modem [ mac-address> | <ip-address> | <ipv6address] remote-query [ verbose ] [ immediate [ communitystring <string> ] ]
Show all the

cable modem
remote-query
558
CASA CMTS
information.
Where:
<mac-address>
<ip-address>
<ipv6-address>
<verbose>
<immediate>
<string>
CM MAC address.
CM IPv4 or IPv6 address.
Provides detailed information.
Obtains remote query info directly
from the cable modem when
background remote query feature is
turned on.
SNMP community string to poll the
CMs.
To show the cable modem remote information according to the specific upstream:
Step
1
Command
Purpose
show cable modem remote-query upstream (<x/y> | <x/y/z>)
Show the cable

modem remote
information
according to the
specific
upstream
Where:
<x>
<y>
<z>
Line card slot number.

Port number.
Channel number for downstream module or logical
channel number for upstream module.
To show the cable modem remote information according to the specific downstream:
Step
1
Command
Purpose
show cable modem remote-query downstream (<x/y> |

<x/y/z>)
Show the cable

modem remote
information
according to the
specific
downstream.
Where:
<x>
<y>
<z>

Port number.
Channel number for downstream module or logical
channel number for upstream module.
The commands get all the CMs MAC-addresses from DDM, and then get the IP-addresses from
the CM MAC-addresses, and finally access the CMs remote information through SNMP
communication.
Example: show cable modem remote-query

CASA-CMTS>show cable modem remote-query
MAC Address
IP Address S/N
US
DS
TX Time Micro(dB)
Modem
Ratio Power Power Offset
Reflection State
0015.f2fe.c643 10.160.1.9 36.2
42.4
5.5
2435
7
online
559
CASA CMTS
Configuring the remote-query polling interval

To set the remote query polling interval:
Step
1
Command (config)
Purpose
cable modem remote-query <num=30:1800> [ <string> ]
Set the remote

query polling
interval.
Where:
<num>
<string>
Number of seconds from 30-1800

seconds (0 = turn off polling).
SNMP community string to poll the CMs
Example:
Change the community interval to be 1000:
CASA-CMTS(config)# cable modem remote-query
1000
Displaying the cable modem remote-query with a specified MAC

address
To show remote information with a specified MAC address:
Step
1
Command
Purpose
show cable modem <mac_addr> remote-query {(upstream |

downstream)(<x/y> | <x/y/z>)}
Show remote
information with
a specified
MAC address.
Where:
<mac_addr>
<x>
<y>
<z>
MAC address.
Port number.
Channel number for downstream
module or logical channel number for
upstream module.
Example: show cable modem remote-query with a specified MAC Address

CASA-C2200(config)#cable modem remote-query 30
CASA-C2200(config)#show cable modem 0015.* remote-query
MAC Address
IP Address
S/N
US
DS
Ratio
Power
Power
0015.f2fe.9247 10.160.1.241
39.6
41.1
3.4
0015.f2fe.baac 10.160.1.223
37.1
38.4
3.1
CASA-C2200(config)#show cable modem 0015.* remote-query
MAC Address
IP Address
S/N
US
DS
Ratio
Power
Power
0015.f2fe.baac 10.160.1.223
37.1
38.4
3.1
TX Time Micro(dB)
Offset Reflection
2434
11
2436
9
upstream 1/1/0
TX Time Micro(dB)
Offset Reflection
2436
9
Modem
State
online
online
Modem
State
online
560
CASA CMTS
Showing the cable modem remote-query with a specified IP address

To show remote information with a specified IP address:
Step
1
Command
Purpose
show cable modem <ip_addr> [mask <mask >] remote-query
Show remote
information with
a specified IP
address.
Where:
<ip_addr>
<mask>
IP address.
Optional mask of IP address.
Example: show cable modem remote-query with a specified IP address

CASA-CMTS# show cable modem 10.160.1.9 mask 255.255.255.255 remote-query
MAC Address
IP Address
S/N
US
DS
TX Time Micro(dB)
Modem
Ratio Power Power Offset
Reflection State
0015.f2fe.c643 10.160.1.9
36.2
42.4
5.5
2435
7
online
Setting the cable modem flap-list aging interval

Step
1
Command (config)
Purpose
cable flap-list aging {<num=15:86400> | default}
Set the cable

flap-list aging
interval.
Where:
<num=15:86400>
default
Period ranged from 15 minutes to 86400 minutes (60 days). This is the
length of period the cable modem can
remain in the flap list table.
Default value of 10-800 minutes (180
hours).
Example:
CASA-CMTS(config)# cable flap-list aging 15
Accelerating cable modem registration

Sometimes when cable modems come on line slowly, the system will trigger a lot of DOCSISevents (docsis-log/syslog/trap). These DOCSIS-logs will consume CPU usage and slow modem
registration even further. Use the following commands to drop the log messages and reduce
CPU usage:
CASA-CMTS(config)#cable event priority warning 0x00 0x00
CASA-CMTS(config)#cable event priority notice 0x00 0x00
CASA-CMTS(config)#show cable event notification-policy
priority
flash-log mem-log traps
syslog
------------------------------------------------Casa CMTS Software Configuration Guide
561
CASA CMTS
emergency
alert
critical
error
warning
notice
informational
debug
yes
yes
yes
yes
no
no
yes
yes
no
no
no
no
no
no
no
no
yes
yes
yes
yes
no
no
yes
yes
yes
yes
yes
yes
no
no
yes
yes
This configuration can be saved to the startup configuration. To turn the messages back on:
CASA-CMTS(config)#cable event priority warning <hex>
CASA-CMTS(config)#cable event priority notice <hex>
Where <hex>:
0x80
equals messages reported to the local log
0xA0
equals messages reported to the local log and SYSLOG servers
0xC0
equals messages reported to the local log and trap receivers
0xE0
equals messages reported to the local log, SYSLOG servers and trap
Registration can also be accelerated by changing the ranging back off values from the default (0
4) to 4 10. This is especially helpful on channels with 200 or more cable modems.
Registering DOCSIS 2.0 bonding modems

Some DOCSIS 2.0 cable modems will not register if TCC is included in the ranging response.
To turn TCC on or off for these modems:
Step
1
Command (config)
Purpose
[no] cable tcc us-bonding disable
Turn tcc on or
off. The default
is off.
Example:
CASA-CMTS(config)# cable tcc us-bonding disable
CASA-CMTS(config)# no cable tcc us-bonding
disable
Enabling the cable modem flap-list trap (Release 5.2)

To enable and disable the cable modem flap-list trap:
Step
1
Command (config)
Purpose
cable flap-list trap [(enabled | disabled)]
Enable or
disable the
cable modem
flap list.
Where:
enabled
Enable the cable modem flap list trap.
562
CASA CMTS
disabled
Disable the cable modem flap list trap.
Example:
CASA-CMTS(config)#cable flap-list trap enabled
Enabling the cable modem flap-list trap (Release 5.4)

To enable and disable the cable modem flap-list trap:
Step
1
Command (config)
Purpose
[no] cable flap-list trap
Enable or
disable the
cable modem
flap list trap.
Example:
CASA-CMTS(config)#cable flap-list trap
CASA-CMTS(config)#no cable flap-list trap
Configuring a cable modem deny list

Step
1
Command (config)
Purpose
[no] cable modem deny <mac_addr>
Setup or
disable a
cable modem
deny list.
Where:
[no]
Disable the cable modem denying.
Example:
CASA-CMTS(config)#cable modem deny 0015.f2fe.cef2
Enabling PacketCable admission control preempt voice priority

To enable or disable PacketCable admission-control preempt voice priority:
Step
1
Command (config)
Purpose
[no] cable admission-control preempt priority-voice
Enable or disable
PacketCable
admission control
preempt voice
priority.
Where:
[no]
Disables admission-control preempt voice priority.
Example:
CASA-CMTS(config)#cable admission-control preempt
priority-voice
563
CASA CMTS
Enabling cable DSX authorization

When enabled, the CMTS will check all DSX messages (DSA, DSC and DSD) for a valid gate ID
authorization value. If the DSX message is invalid, the CMTS rejects the message. Use the no
form of the command to disable checking of DSX messages.
Step
1
Command (config)
Purpose
[no] cable dsx authorization
Enable or
disable
checking of
DSX
messages.
Where:
[no]
Disable checking of DSX messages.
Example:
CASA-CMTS(config)#cable dsx authorization
CASA-CMTS(config)#no cable dsx authorization
Enabling Receive Channel Profile (RCP) fragment support

When enabled, the CMTS will inform registered cable modems that it supports fragmented
RCC/RCP TLV packet transmissions if the RCP length exceeds 255. The default setting is
disabled (no RCP fragment support). This command operates at the top level of the CLI and in
configuration mode.
Step
1
Command (config)
Purpose
[no] cable mdd rcp fragment support
Enable or
disable RCP
fragment
support
notifications to
registered cable
modems.
Where:
[no]
Disables RCP fragment support notifications.
Example:
CASA-CMTS(config)#cable mdd rcp fragment support
CASA-CMTS(config)#no cable mdd fragment support
Controlling CMTS upstream power levels (Rel. 6.1 and later)

The cable mdd extended tx-power support command configures the CMTS to support
extended transmission power over upstream channels. Specify 1 to support extended power
levels; specify 0 (default) to disable the extended transmission power support feature. This
command operates at the CLI top level and in the CMTS configuration mode.
564
CASA CMTS
Step
1
Command
Purpose
[no] cable mdd extended tx-power support [0 | 1]
Enable or
disable
extended
upstream
transmission
power support
at the CMTS.
Where:
0
1
Disables extended transmission power support.

This is the default setting.
Enables extended transmission power support.
Examples:
CASA-CMTS#cable mdd extended tx-power support 0
CASA-CMTS#cable mdd extended tx-power 1
Adjusting modem upstream power levels (Rel. 6.1 and later)

The cable upstream hi-power command sets the cable modem output level to a higher
upstream power level specified in decibels per millivolt (dBmV). Specify a value in the range 0 to
6, where 0 (default) specifies the optimum upstream power level, and 6 specifies an increase of
6dB. This command operates in the CMTS configuration mode.
Step
1
Command (config_
Purpose
[no] cable upstream hi-power <number 0-6>
Configure
modem
upstream
power level in
decibels per
millivolt.
Where:
0-6
Specifies the upstream power level, where 0

indicates the optimum power level and 6 indicates
a power level increase of 6dB. The default setting
is 0.
Examples:
Increase upstream modem power by 3dB.
CASA-CMTS(config)#cable upstream hi-power 3
Resetting cable modems and clearing cable modem counters

The clear cable modem command allows you to reset the cable modem upstream and
downstream counters to zero, or to reset cable modems using the modem IP or MAC address.
Step
1
Command (config)
Purpose
clear cable modem <mac_address> counters [downstream |

upstream]
Reset the CM
flap-list
counters to
zero.
565
CASA CMTS
clear cable modem <mac_address> reset

clear cable modem <ip_address> reset
clear cable modem <ipv6_address> reset
Where:
<mac_address>
Specifies the 48-bit hardware address

(MAC address) of an individual CM, or of
any CPE devices or hosts behind that CM.
If the optional downstream or upstream
parameter is specified, then the
downstream or upstream counts will be
reset respectively.
<ip_address>
Specifies the IPv4 address of the modem

in 32-bit dotted decimal notation. A.B.C.D
<ipv6_address>
Specifies the IPv4 address of the modem

in 128-bit notation. xxxx:xxxx:...:xxxx
downstream
Specifies clearing of downstream counters

only.
upstream
Specifies clearing of upstream counters

only.
reset
Resets the specified cable modem
Example:
CASA-CMTS(config)#clear cable modem 015.f2fe.cef2
If no options are specified, all CM counters will be reset. If a mac-address is specified, only the
counters for that cable modem will be reset.
Example: clear cable modem counters

Clear the counters for the CM at MAC address 0014. 6cb9.ff9f:
CASA-CMTS# show cable modem counters
MAC Address
US Packets
US Bytes
DS Packets
Bytes
0004.bd02.5050
9
1582
3
0011.e360.5655
0
0
0
0011.e62b.6c0f
0
0
0
0013.115d.25a2
0
0
0
0014.6cb9.ff9f
9
1495
4
0015.e9a0.b8c6
44
4480
0
0016.ce88.8ab2
0
0
0
0017.9a5f.dcf9
0
0
0
CASA-CMTS#
CASA-CMTS# clear cable modem 0014.6cb9.ff9f counters
CASA-CMTS# show cable modem counters
MAC Address
US Packets
US Bytes
DS Packets
Bytes
DS
406
0
0
0
927
0
0
0
DS
566
CASA CMTS
0004.bd02.5050
0011.e360.5655
0011.e62b.6c0f
0013.115d.25a2
0014.6cb9.ff9f
0015.e9a0.b8c6
0016.ce88.8ab2
0017.9a5f.dcf9
CASA-CMTS#
9
0
0
0
0
44
0
0
1582
0
0
0
0
4480
0
0
3
0
0
0
0
0
0
0
406
0
0
0
0
0
0
0
Clearing offline cable modems immediately

To remove all offline CMs from the show cable modem list, use the clear cable modem offline
command:
Step
1
Command (config)
Purpose
clear cable modem offline
Remove all
offline CMs
from the show
cable modem
list.
Example:
CASA-CMTS# clear cable modem offline
Clearing offline cable modems after aging

The cable modem offline aging command allows you to clear modems that have previously
registered with the CMTS but have been offline for a specified number of hours.
If set to 0 (default), the modem will maintain an offline state indefinitely and will not be cleared. If
set to a value in the range 1 to 8760 hours (1 year), the CMTS will clear all modems that have
been offline for the specified number of hours.
Step
1
Command (config)
Purpose
cable modem offline aging <hours>
Remove all
offline CMs
after the
specified aging
period.
Where:
<hours>
1 to 8760 hours (1 hour to 1 year).
Example:
CASA-CMTS# cable modem offline aging 10
In the above example, registered cable modems that have been in the offline for 10 hours will be
cleared by the CMTS and will reregister with the CMTS when they become available. Use the
show cable modem offline command to display the previous modem state and the total time
duration of the modem (s) being offline.
CASA(config)# show cable modem offline
MAC Address
US
DS
Prim Previous Offline
Rx
RX
SM
567
CASA CMTS
0008.0e41.5664
0015.f2fe.9a7e
0015.f2fe.b9fb
0015.f2fe.ba58
0015.f2fe.c643
0015.f2fe.ceb9
0022.102b.c609
0022.3ace.d9b9
0026.5e77.4463
0026.5e77.446c
Intf
Intf
Sid
State
Time
Power SNR
0/3.1/0
0/0.0/0
0/3.0/0
0/3.1/0
0/2.0/0
0/3.0/0
0/0.1/0
0/0.0/0
0/0.1/0
0/0.1/0
1/3/3
1/2/2
1/3/2
1/2/3
1/3/0
1/3/1
1/2/1
1/3/0
1/3/0
1/2/1
61
57
67
62
52
51
50
54
60
58
online
online
online
online
online
online
online
online
online
online
2010-11-13,03:02:30
2010-11-13,03:02:30
2010-11-13,03:02:29
2010-11-13,03:02:35
2010-11-13,03:02:32
2010-11-13,03:02:34
2010-11-13,03:02:27
2010-11-13,03:02:35
2010-11-13,03:02:34
2010-11-13,03:02:30
-0.5
-0.5
0.0
0.0
0.2
0.0
0.0
-0.2
0.0
0.0
40.4
40.4
42.1
45.1
35.6
42.1
45.1
39.1
40.4
39.1
Exh.Cnt
16
16
16
16
16
16
16
16
16
16
Displaying cable modem vendors

To display up to 512 cable modem vendors:
Step
1
Command (config)
Purpose
show cable modem [<ip-address> | ipv6-address | <macaddress>] vendor
Display cable
modem vendor
information.
Example:
See examples below.
Example: show cable modem vendor

CASA-CMTS# show cable modem vendor summary
Vendor
OUI
Cable Modem
Total Registered Unregistered Offline
ZDT
00:15:f2
1
1
0
0
Motorola
00:20:40
28
28
0
0
Show cable modem vendor details.
CASA-CMTS# show cable modem vendor
Vendor
MAC Address
US
DS
Num BPI
Intf
Intf
CPEs Enb
Motorola
0011.802c.43fe 3/4/0
1/0/0
0
no
Motorola
0013.7163.0f92 3/4/0
1/0/0
0
no
Motorola
0013.7163.3ea2 3/0/0
1/0/0
0
no
Motorola
0013.7163.6980 3/4/0
1/0/0
0
no
Motorola
0013.716c.e0de 3/4/0
1/0/0
0
no
Motorola
0013.716c.f33e 3/4/0
1/0/0
0
no
Motorola
0013.716d.72a6 3/0/0
1/0/0
0
no
MAC
Prim RxPwr Timing
State
Sid
(db)
Offset
online
-2.0
889
online
-2.0
882
online
-3.2
840
online
24
-1.7
895
online
61
-1.7
838
online
19
-1.5
876
online
-2.7
878
568
CASA CMTS
Motorola
0
no
Motorola
0
no
Motorola
0
no
Motorola
0
no
0013.7176.d8f4 3/4/0
1/0/0
online
-2.0
871
0013.7176.ef86 3/4/0
1/0/0
online
62
-1.2
850
0013.7176.f8e6 3/4/0
1/0/0
online
63
-1.5
885
0013.7178.0812 3/4/0
1/0/0
online
25
-1.2
877
Displaying vendor-specific information on cable modems

To display vendor information of a specific cable modem:
Step
1
Command
Purpose
show cable modem [<mac_address> | <ip_address> |

ipv6_address] vendor
Display cable
modem vendor
information.
Where:
<mac_address>
Cable modem MAC address in the

format xxxx.xxxx.xxxx.
IPv4 or IPv6 cable modem address.
<ip_address>
<ipv6_address>
Example:
See examples below.
Example: show vendor information

CASA-CMTS#show cable modem 0015.f2fe.c904 vendor
Vendor
MAC Address
US
DS
MAC
Intf
Intf
State
ZDT
0015.f2fe.c904 1/6/0
0/2/0
online

Sid (db) Offset CPEs Enb
10
1.7
2180
0
no
Adding and modifying cable modem vendor information

To add user-defined cable modem vendor information or to modify the system default CM vendor:
Step
1
Command
Purpose
cable modem vendor <vendor_id> <string>
Add a user
defined cable
modem vendor
information.
Where:
<vendor_id>
<string>
Organizational Unique Identifier. xx:xx:xx

Vendor-name. If spaces are included in the
vendor name, enclose the string in quotation
marks ().
569
CASA CMTS
Example:
CASA-CMTS# cable modem vendor 00:00:00 ABC
Deleting cable modem vendor information

To delete a user defined cable modem vendor:
Step
1
Command (config)
Purpose
no cable modem vendor <vendor_id>
Delete a user
defined cable
modem vendor.
Where:
<vendor_id>
Example:
CASA-CMTS(config)# no cable modem vendor 0:00:00
Displaying vendor OUI information

To show the vendor OUI information:
Step
1
Command
Purpose
show cable modem vendor [config | all | default | summary]
Show the
vendor OUI
information.
Where:
config
Show the user config OUI information.
all
Show all OUI information.
default
Show the default OUI database.
summary
Show abbreviated information only.
Example:
CASA-CMTS#show cable modem vendor all
system default cm vendor database:
cable modem vendor 00:0f:9f "Motorola"
cable modem vendor 00:11:1a "Motorola"
cable modem vendor 00:11:80 "Motorola"
cable modem vendor 00:14:e8 "Motorola"
cable modem vendor 00:18:c0 "Motorola"
cable modem vendor 00:1a:ad "Motorola"
cable modem vendor 00:1b:dd "Motorola"
cable modem vendor 00:0f:21 "Sci Atl"
cable modem vendor 00:11:e6 "Sci Atl"
cable modem vendor 00:14:f8 "Sci Atl"
cable modem vendor 00:16:92 "Sci Atl"
cable modem vendor 00:1c:ea "Sci Atl"
570
CASA CMTS
user config cm vendor:

cable modem vendor 00:26:5e "Ubee"
cable modem vendor 00:20:40 "Moto"
Example: show cable modem vendor summary

CASA-CMTS# show cable modem vendor summary
Vendor
OUI
Cable Modem
Total Registered Unregistered Offline
ZDT
00:15:f2
1
1
0
0
Motorola
00:20:40
28
28
0
0
Setting the default cable modem vendor

To set the system default vendor to default value after modifying them:
Step
1
Command (config)
Purpose
default cable modem vendor <vendor_id>
Set the
system
default
vendor to
default value.
Where:
<vendor_id>
Example:
Set 00:0f:9f to default value after modifying it
CASA-CMTS(config)#show cable modem vendor default
CASA-CMTS(config)#cable modem vendor 00:0f:9f ABC
CASA-CMTS(config)#show cable modem vendor all
user config cm vendor:
cable modem vendor 00:0f:9f "ABC"
CASA-CMTS(config)#default cable modem vendor
00:0f:9f
CASA-CMTS(config)#show cable modem vendor all
cable modem vendor 00:11:80 "Motorola
Displaying cable modem classifiers

To show classifiers in the configuration file that the CM is using:
571
CASA CMTS
Step
1
Command
Purpose
show cable modem [<mac-address> | <ip_address> | <ipv6address>] classifiers
Show
classifiers in the
config file.
Where:
<mac-address>
<ip_address>
Specifies the cable modem MAC

address in the format xxxx.xxxx.xxxx.
Specifies the cable modem IPv4 or IPv6
address.
Example:
See example below.
Example: show cable modem classifiers

CM Mac Address:
Classifier ID:
ServiceFlow ID:
Direction:
Rule Priority:
Activation State:
IP classifiers:
ToS:
Protocol:
Source Address:
Source Mask:
Destination Address:
Destination Mask:
Source Port Start:
Source Port End:
Destination Port Start:
Destination Port End:
LLC classifiers:
Destination Mac Address:
Destination Mac Mask:
Source Mac Mask:
Ether Type:
User Priority Low:
User Priority High:
Vlan ID:
Bit Map:
CM Interface Mask:
Classifier ID:
ServiceFlow ID:
Direction:
Rule Priority:
Activation State:
IP classifiers:
ToS:
Protocol:
Source Address:
Source Mask:
0050.f112.b764 classifiers
0050.f112.b764
3
514
Upstream
20
Active
0x00 0x00 0x00
17
0.0.0.0
255.255.255.255
0.0.0.0
255.255.255.255
0
65535
0
65535
0000.0000.0000
0000.0000.0000
0000.0000.0000
0x00
0x0
0x0
0x0
0xb
0x00.00.00.00
2
639
Upstream
10
Active
0x00 0x00 0x00
256
0.0.0.0
255.255.255.255
572
CASA CMTS
Destination Mask:
Source Port Start:
Source Port End:
LLC classifiers:
Source Mac Mask:
Ether Type:
User Priority Low:
User Priority High:
Vlan ID:
Bit Map:
CM Interface Mask:
0.0.0.0
255.255.255.255
0
65535
0
65535
Classifier ID:
ServiceFlow ID:
Direction:
Rule Priority:
Activation State:
IP classifiers:
ToS:
Protocol:
Source Address:
Source Mask:
Destination Mask:
Source Port Start:
Source Port End:
LLC classifiers:
Source Mac Mask:
Ether Type:
User Priority Low:
User Priority High:
Vlan ID:
Bit Map:
5
641
Down
20
Active
Classifier ID:
ServiceFlow ID:
Direction:
Rule Priority:
Activation State:
IP classifiers:
ToS:
Protocol:
Source Address:
Source Mask:
Destination Mask:
Source Port Start:
4
767
Down
10
Active
0000.0000.0000
0000.0000.0000
0000.0000.0000
0x00
0x0
0x0
0x0
0xb
0x00.00.00.00
0x00 0x00 0x00

17
0.0.0.0
255.255.255.255
0.0.0.0
255.255.255.255
0
65535
0
65535
0000.0000.0000
0000.0000.0000
0000.0000.0000
0x00
0x0
0x0
0x0
0xb
0x00 0x00 0x00

256
0.0.0.0
255.255.255.255
0.0.0.0
255.255.255.255
0
573
CASA CMTS
Source Port End:

LLC classifiers:
Source Mac Mask:
Ether Type:
User Priority Low:
User Priority High:
Vlan ID:
Bit Map:
65535
0
65535
0000.0000.0000
0000.0000.0000
0000.0000.0000
0x00
0x0
0x0
0x0
0xb
Showing cable modem errors

To show cable modem error information, such as CRC and HCS:
Step
1
Command
Purpose
show cable modem [<mac_addrress> | <ip_address> | <ipv6address>] errors
Show cable
modem errors
in the config
file.
Where:
<mac-address>
<ip_address>
Cable modem MAC address in the

format xxxx.xxxx.xxxx
Cable modem IP address in the format
A.B.C.D.
Example:
See example below.
Example: showing cable modem errors

C2800#show cable modem errors
MAC Address
US Intf
DS Intf
0008.0d55.da42 1/3/0
0/0/1
0015.f2fe.bea2 1/3/0
0/0/3
0050.f112.b764 1/3/0
0/0/1
CRC
0
0
0
HCS
0
0
0
Displaying cable modem MAC information

To show cable modem MAC information, such as the version number:
Step
1
Command
Purpose

ipv6_address>] mac
Display cable
modem MAC
information.
Where:
574
CASA CMTS
<mac_address>
Cable modem MAC address in the format

xxxx.xxxx.xxxx
<ip_address>
Cable modem IPv4 or IPv6 address
Example:
See example below.
Example: show cable modem mac information

CASA-C3000(config)#show cable modem upstream 4/1.1/0 mac
MAC Address
MAC
Prim Ver
QoS
Frag Concat
Priv DS
US
State
Sid
Prov
Saids Sids
0004.bd04.c1d8 online
17
DOC1.1 DOC1.1 YES YES
0
1
0005.caa3.d65c online
22
0
1
000e.5c69.0188 online
6
0
1
0011.8054.3af2 online
9
0
1
0012.c99f.700a online
10
0
1
0026.5e77.43ba online
27
0
1
0026.5e77.43ce online
24
0
1
0026.5e77.446e online
21
0
1
CASA-C3000(config)#
PHS
YES BPI
YES BPI
YES BPI
YES BPI
YES BPI
YES BPI
YES BPI
YES BPI
Displaying cable modem spoof information

To show spoof information of the cable modem during ranging.
Step
1
Command
Purpose

upstream < X/Y.C/Z>] rogue
Show spoof
information of
the cable
modem during
ranging.
Where:
<mac_address>

xxxx.xxxx.xxxx
<ip_address>
Cable modem IP address in the format

A.B.C.D.
< X/Y.C/Z >
X - slot, Y - port (0-7), C - upstream

physical channel(0-1), Z - upstream logical
channel(0-1)
575
CASA CMTS
Example:
See example below.
Example: show cable modem spoof information

CASA-CMTS#show cable modem rogue
MAC Address
Vendor
US Intf
Ds Intf
0011.8078.1950 3/0/0
0/0/0
ba052c3991df6a933fa2c857f9654104
0013.7192.5b04 3/2/0
0/0/0
ba052c3991df6a933fa2c857f9654104
Spoof Count Dynamic Secret

4
5
Displaying cable modem maintenance ranging information

To show CM maintenance ranging information:
Step
1
Command
Purpose

ipv6_address] maintenance
Show CM
maintenance
ranging
information.
Where:
<mac_address>
<ip_address>
<ipv6_address>

xxxx.xxxx.xxxx.
Cable modem IPv4 or IPv6 address.
Example:
See example below.
Example: show cable modem maintenance ranging information

CASA-CMTS#show cable modem maintenance
MAC Address
US Intf
Ds Intf
Prim
Time
Sid
0015.f2fe.c763 1/0/0
0/1/0
2
30,16:16:00
0015.f2fe.cee6 1/0/0
0/1/1
1
30,16:15:58
0015.f2fe.cef2 1/2/0
0/1/1
3
30,16:16:02
SM
Fail
Active-
Count
42
Count
0
2009-06-
43
2009-06-
44
2009-06-
Displaying denied cable modem

To show CM that are added to the deny list.
Step
1
Command
Purpose
show cable modem deny
Show CM that
576
CASA CMTS
are added to
the deny list.
Example:
CASA-CMTS# show cable modem deny
cable modem deny 0015.f2fe.cee6
Displaying the cable modem MAC summary

To show CM MAC layer information summary:
Step
1
Command
Purpose
show cable modem mac [downstream] summary
Show CM Mac
layer
information
summary.
Example: See example below.
Example: show cable modem mac summary

CASA-CMTS# show cable modem mac downstream summary
Mac Version
QoS Provision Mode
Interface Total DOC3.0 DOC2.0 DOC1.1 DOC1.0 Register DOC2.0 DOC1.1 DOC1.0
0/0/0
0
0
0
0
0
0
0
0
0
0/0/1
0
0
0
0
0
0
0
0
0
0/0/2
0
0
0
0
0
0
0
0
0
0/0/3
0
0
0
0
0
0
0
0
0
0/1/0
0
0
0
0
0
0
0
0
0
0/1/1
0
0
0
0
0
0
0
0
0
0/1/2
0
0
0
0
0
0
0
0
0
0/1/3
0
0
0
0
0
0
0
0
0
0/2/0
1
0
1
0
0
1
0
1
0
0/2/1
0
0
0
0
0
0
0
0
0
0/2/2
0
0
0
0
0
0
0
0
0
0/2/3
0
0
0
0
0
0
0
0
0
0/3/0
0
0
0
0
0
0
0
0
0
0/3/1
0
0
0
0
0
0
0
0
0
0/3/2
0
0
0
0
0
0
0
0
0
0/3/3
0
0
0
0
0
0
0
0
0
Total:
Displaying the cable modem status event report

To show the CM status event report for each DOCSIS-MAC interface, first enter DOCSIS-MAC
config mode and define the event:
Step
1
Command (config)
Purpose
interface docsis-mac <dsm_id>
Enter docsis-mac
configuration
mode.
Where:
577
CASA CMTS
Docsis-mac ID
<grp_id>
Example:
cable cm-status event <a> max-timer <b> max-number <c>
Where:
<a>
Specifies the event code; valid values are 1-10
<b>
Maximum Event Holdoff Timer
<c>
Timer value units in 20 milliseconds; valid values are

0-255.
cable cm-status report event-list <string>

Where:
<string>
Define the event.
Run the report.
The list of events in the format: 1,2,3 . . . ; valid

values are 1-10.
show interface docsis-mac <id>

Example:
CASA-CMTS(config)# show interface docsis-mac 1
cable cm-status report event-list 5
cable cm-status event 1 max-timer 1500 maxnumber 35
Check
configured cmstatus.
Displaying cable modem quality-of-service (QOS)

The show cable modem qos command display quality-of- service (QOS) information associated
with one or more cable modems. For QOS information relating to a specific cable modem,
specify the IP or the MAC address. Use the show cable modem qos command to display the
average number of service ID (SIDs) per cable modem.
Step
1
Command
Purpose
show cable modem [<ip-address> | ipv6-address | <macaddress>] qos [verbose]
Display QOS
information
associated with
the specified
cable modem,
or all cable
modems.
Where:
mac-address
ip-address
ipv6-address
verbose
Optional. Specifies the MAC address of

the target cable modem.
Optional. Specifies the IP address of the
target cable modem.
Optional. Provides detailed information
associated with each cable modem
578
CASA CMTS
service flow.
Example:
CASA-CMTS(config)#show cable modem qos
Example: show cable modem qos

CASA-CMTS> show cable modem qos
Sfid
Dir Curr
Sid
State
Sched
Prio MaxSusRate MaxBrst MinRsvRate Throughput
Type
(kbps)
(kbps)
(kbps)
Mac Addr : 0012.c99f.700a

Mac Addr : 0050.f112.b329
383
US
act
BE
3044
511
DS
act
N/A
UNDEF
3044
To display the total number of SIDs currently in use, enter the show cable modem qos
command with the count-only output modifier.
Example: show cable modem qos | count-only <string>

CASA-C3000> show cable modem qos | count-only "us act"
Sfid
Dir Curr
Sid
State
Sched
Type
Prio MaxSusRate MaxBrst MinRsvRate Throughput

(kbps)
(kbps)
(kbps)
Count Line: 9854
Displaying the cable modem docsis-mac summary

The show cable modem docsis-mac command displays the cable modems belonging to the
specified DOCSIS MAC interface.
Step
1
Command
Purpose
show cable modem docsis-mac <domain-id>
Display cable
modem
information
associated with
the specified
DOCSIS MAC
interface at the
CMTS.
Where:
<domain-id>
Specifies the MACdomain ID in the

range 1 to 32.
Example:
CASA-CMTS(config)#show cable modem docsis-mac 1
579
CASA CMTS
Example: show cable modem docsis-mac

CASA-CMTS> show cable modem docsis-mac 1
MAC Address
IP Address
US
DS
MAC
Prim RxPwr Timing Num
Intf
Intf
Status
Sid
(dB)
Offset CPEs Enb
BPI
0012.c99f.700a 0.0.0.0
5/1.1/0
0/0/1
offline
0.0
no
0050.f112.b329 10.230.1.145
5/1.0/0*
0/0/0*
online(pt)
0.0
2442
yes
c0cb.38d3.6e74 0.0.0.0
5/1.0/0
0/0/0
init(r2)
206
6.2
2391
no
CASA-C3000>
To display the total number of SIDs currently in use over the specified MAC domain, enter the
show cable modem docsis-mac ommand with the count-only output modifier.
Example: show cable modem docsis-mac <id> | count-only <string>

CASA-CMTS> show cable modem docsis-mac 1 | count-only online
MAC Address
Timing Num
IP Address
US
DS
MAC
Prim RxPwr
Intf
Intf
Status
Sid
BPI
(dB)
Offset CPEs Enb

Count Line: 515
Subscriber management
Casa CMTS supports Subscriber Management features defined in DOCSIS 3.0. This section
describes how to use CLI commands to configure those features. It covers the following
operations:
CM controls
Enabling subscriber management.

Setting a mode for the CM to learn the CPE IP address without DHCP.
Setting maximum ipv4 CPEs behind the CM.
Setting maximum ipv6 CPEs behind the CM.
Removing all CPEs behind the CM.
Default settings
Default settings if CM configuration file does not specify otherwise
Filters
Setting filter rule

Removing all IP and TCP-UDP filters
580
CASA CMTS
Show subscriber management information
Cable modem information

CM control table
CM CPE IP table
IP filter
Enabling subscriber management

To enable subscriber management on a CM after it is registered:
Step
1
Command (config)
Purpose
docsis submgt cm-control cm <cm_id> active true

docsis submgt cm-control cm <cm_id> active false
Enable or disable
subscriber
management on
a CM.
Where:
<cm_id>
CM ID as defined and distributed by the CMTS as

an identifier. Use the show cable modem and
then use the show qos ds cm qam command with
the cm_id modifier. The identifier can also be
retrieved by walking the MIB entry
docsIfCmtsCmStatusMacAddress
Example:
CASA-CMTS(config)#docsis submgt cm-control cm 1
active true
Example: Enabling subscriber management

MAC Address
IP Address
US
Intf
0005.caa3.c38c 10.160.1.250
1/1/0*
0015.f2fe.9247 10.160.1.241
1/2/0
0015.f2fe.baac 10.160.1.223
1/2/0
0020.4058.c984 10.160.1.251
1/3/0
0026.5e77.43aa 10.160.1.252
1/1/0*
DS
Intf
2/0/1*
2/0/0
2/0/2
2/0/3
2/0/2*
MAC
Status
online
online
online
online
online
Prim
Sid
40
36
37
39
38
RxPwr
(dB)
0.5
0.2
0.2
0.0
0.0
Timing
Offset
2443
2432
2437
1674
2392
Num
CPEs
0
0
0
0
0
BPI
Enb
yes
yes
yes
yes
yes
CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.252 | i cm_id

nx=0 ty= 1 lc= 2 mc=0000 pcnt=
6 ir=1 0 0 10.160.1.252 00265e7743aa cm_id=5 cid=2
cm_tbl_idx=
16 cm_id=5 cid= 2 psid=38 v=3 00265e7743aa tek=02af3628
10 ir=1 0 0 10.160.1.251 00204058c984 cm_id=4 cid=3
cm_tbl_idx=
17 cm_id=4 cid= 3 psid=39 v=0 00204058c984 tek=00000000
4 ir=1 0 0 10.160.1.223 0015f2febaac cm_id=3 cid=2
cm_tbl_idx=
15 cm_id=3 cid= 2 psid=37 v=0 0015f2febaac tek=02af36a8
4 ir=1 0 0 10.160.1.241 0015f2fe9247 cm_id=6 cid=0
cm_tbl_idx=
14 cm_id=6 cid= 0 psid=36 v=0 0015f2fe9247 tek=02af36e8
4 ir=1 0 0 10.160.1.250 0005caa3c38c cm_id=1 cid=1
cm_tbl_idx=
18 cm_id=1 cid= 1 psid=40 v=3 0005caa3c38c tek=02af3668
581
CASA CMTS
CASA-CMTS(config)#docsis submgt cm-control cm 1 active true

4 ir=1 0 0 10.160.1.250 0005caa3c38c cm_id=1 cid=1
cm_tbl_idx=
18 cm_id=1 cid= 1 psid=40 v=3 0005caa3c38c tek=02af3668
CASA-C2200(config)#show
Submgt Active = 1
Submgt Learnable = 1
Submgt Max IP = 10
Downstream Filter Entry
Upstream
Filter Entry
Upstream
Filter Entry
Upstream
Filter Entry
Upstream
Filter Entry
Upstream
Filter Entry
docsis submgt cm 1 module 2
0
0
1
1
2
2
3
3
4
4
=
=
=
=
=
=
=
=
=
=
0
0
0
0
0
0
0
0
0
0
Setting the mode for a CM to learn the CPE IP address without DHCP
To set or unset the mode for a CM to learn the CPE IP address:
Step
1
Command (config)
Purpose
docsis submgt cm-control cm <cm_id> learnable true

docsis submgt cm-control cm <cm_id> learnable false
Set or unset the

mode for a CM to
learn the CPE IP
address.
Where:
<cm_id>
CM ID as defined and distributed by the

CMTS as an identifier. Use the show cable
modem and then use the show qos ds cm
qam command with the cm_id modifier. The
identifier can also be retrieved by walking the
MIB entry docsIfCmtsCmStatusMacAddress.
Example:
learnable true
Setting maximum IPv4 CPEs behind a CM

To set maximum IPv4 CPEs:
Step
1
Command (config)
Purpose
docsis submgt cm-control cm <cm_id> max-cpe-ip <num>
Set maximum
IPv4 CPEs.
Where:
<num>
Maximum number of IPv4 CPEs behind the cable

modem in the range 0 to 1023.
Example:
582
CASA CMTS

max-cpe-ip 10
Setting maximum IPv6 CPEs behind a CM

To set max ipv6 CPEs:
Step
1
Command (config)
Purpose
docsis submgt cm-control cm <cm_id> max-cpe-ipv6-prefix

<num>
Set maximum
IPv6 CPEs.
Where:
<num>
Maximum number of ipv6 CPEs behind CM, values

are 0 to 1023.
Example:
max-cpe-ipv6-prefix 10
Resetting IP addresses of all CPEs behind a CM

To reset learnable IP addresses of CPEs behind a CM:
Step
1
Command (config)
Purpose
docsis submgt cm-control cm <cm_id> reset
Reset learnable
IP addresses of
CPEs behind a
CM.
Where:
<cm_id>
CM ID as defined and distributed by the CMTS

as an identifier. Use the show cable modem
and then use the show qos ds cm qam
command with the cm_id modifier. The identifier
can also be retrieved by walking the MIB entry
Using the subscriber management default settings

Each cable modem will receive subscriber management default settings from the CMTS if their
configuration file does not specify otherwise.
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
docsis
docsis
docsis
docsis
docsis
docsis
submgt
submgt
submgt
submgt
submgt
submgt
default
default
default
default
default
default
active [on|off]
learnable [on|off]
max-ip <0-1023>
max-ipv6-prefix <0-1023>
cm-filter-downstream <0-1024>
cm-filter-upstream <0-1024>
583
CASA CMTS
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
CASA-CMTS(config)#
docsis
docsis
docsis
docsis
docsis
docsis
docsis
docsis
submgt
submgt
submgt
submgt
submgt
submgt
submgt
submgt
default
default
default
default
default
default
default
default
cpe-filter-downstream <0-1024>
cpe-filter-upstream <0-1024>
mta-filter-downstream <0-1024>
mta-filter-upstream <0-1024>
stb-filter-downstream <0-1024>
stb-filter-upstream <0-1024>
ps-filter-downstream <0-1024>
ps-filter-upstream <0-1024>
To specify the DOCSIS subscriber management defaults:

Step
1
Command (config)
Purpose
docsis submgt default <option>
Configures
subscriber
management
default
settings to be
sent to
registered
cable
modems.
Where <option> is one of the following:

Turns on DOCSIS subscriber
active
management either ON or OFF. The
default is OFF.
Allows the cable modem to learn its IP
learnable
address. The default is ON.
Sets the maximum number of customer
max-ip
premises equipment (CPE) IP addresses
that can be allowed for each cable
modem connected to the CMTS. Enter a
number in the range 0 to 1023. The
default setting is 16 IP addresses to
indicate a maximum of 16 CPE devices
connected to each modem.
Sets the maximum number of IPV6
max-ipv6-prefix
prefixes that can be allowed for each
cable modem connected to the CMTS.
Enter a number in the range 0 to 1023.
The default setting is 16 prefixes.
Specifies the downstream packet size to
cm-filterthe CM in the range 0 to 1024 bytes. The
downstream
Specifies the upstream packet filtering
cm-filter-upstream
size from the CM in the range 0 to 1024
bytes. The default setting is 0.
cpe-filter-upstream
size from customer premise equipment
(CPE) devices in the range 0 to 1024
Specifies the downstream packet filtering
cpe-filtersize to CPE devices in the range 0 to
downstream
1024 bytes. The default setting is 0.
mta-filter-upstream
size from multimedia terminal adapter
(MTA) devices in the range 0 to 1024
584
CASA CMTS
mta-filterdownstream
stb-filter-upstream
stb-filterdownstream
ps-filter-upstream
ps-filter-downstream

size to MTA devices in the range 0 to
1024 bytes. The default setting is 0
size from set-top box (STB) devices in the
range 0 to 1024 bytes. The default
setting is 0.
size to STB devices in the range 0 to
1024 bytes. The default setting is 0
size from portal server (PS) devices in the
range 0 to 1024 bytes. The default setting
is 0.
size to PS devices in the range 0 to 1024
bytes. The default setting is 0
Setting a filter rule

To enter a filter rule:
Step
1
Command (config)
Purpose
docsis submgt ip-filter <filter_group> <filter_index> [accept |

deny] [src-ip <ip_address> <ip_mask>] [dst-ip <ip_addr>
<ip_mask>] [tos <tos_high> <tos_low> <tos_mask>] [
protocol <0-257>] [src-port <0-65535>] [dst-port <0-65535>]
[cm-intf-mask <bitmap>]
Enter a filter rule.
Where:
<filter_group>
<filter_index>
<bitmap>
Filter group, 1-65535

Filter index, 1-65535
bitmask, 0-ffffff
Removing all IP and TCP-UDP filters

To remove all IP and TCP-UDP filters in the system:
Step
1
Command (config)
Purpose
docsis submgt filters clear-all
Removes all IP
and TCP-UDP
filters.
585
CASA CMTS
Displaying cable modem information

To display cable modem information under subscriber management:
Step
1
Command (config)
Purpose
show docsis submgt cm <cm_id> module <module_num>
Display cable
modem
information
under
subscriber
management.
Where:
<cm_id>
<module_num>
CM ID as defined and distributed by the

CMTS as an identifier. Use the show cable
MIB entry docsIfCmtsCmStatusMacAddress
CMTS module slot location
Example:
CASA-CMTS# show docsis submgt cm 1 module 2
Submgt Active = 0
Submgt Learnable = 1
Submgt Max IP = 16
Downstream Filter Entry 0 = 0
Upstream
Filter Entry 0 = 0
Upstream
Filter Entry 1 = 0
Upstream
Filter Entry 2 = 0
Upstream
Filter Entry 3 = 0
Upstream
Filter Entry 4 = 0
Displaying the cable modem control table

To display cable modem control table:
Step
1
Command
Purpose
show docsis submgt cm-control cm <cm_id>
Display the
cable
modem
control
table.
Where:
<cm_id>
Cable modem ID as defined and distributed by the CMTS

as an identifier. Use the show cable modem and then
use the show qos ds cm qam command with the cm_id
modifier. The identifier can also be retrieved by walking
the MIB entry docsIfCmtsCmStatusMacAddress
Example:
CASA-CMTS# show docsis submgt cm-control cm 1
cm=1 maxCpe IPv4=16 IPv6=16 active=false
learnable=true reset=0 numOfCpeIp=0
586
CASA CMTS
Displaying CPE information

To display CPE information behind a modem under subscriber management:
Step
1
Command
Purpose
show docsis submgt cm-cpe-ip cm <cm_id>
Display CPE
information
behind a modem
under subscriber
management.
Where:
<cm_id>
Cable modem ID as defined and distributed by

the CMTS as an identifier. Use the show cable
MIB entry docsIfCmtsCmStatusMacAddress
Example:
CASA-CMTS#show docsis submgt cm-cpe-ip cm 3
Displaying IP filter
To display IP filter:
Step
1
Command
Purpose
show docsis submgt ip-filter [<cm_id>]
Display the IP
filter.
Where:
<cm_id>
Cable modem ID as defined and distributed by

the CMTS as an identifier. Use the show cable
modem and then use the show qos ds cm qam
command with the cm_id modifier. The identifier
can also be retrieved by walking the MIB entry
Example: Displaying the IP filter

CASA-CMTS#show docsis submgt ip-filter
Group
Index
Accept Src Ip Mask
Dst Ip Mask
TOShi
TOSMask Hit Cnt
1
1
1
0.0.0.0 0.0.0.0 10.200.3.5
10
0
255
0
0
UIP
TOSlo
255.255.255.255
587
CASA CMTS
Enabling/disabling cable modem host authorization

To enable or disable cable modem host authorization:
Step
1
Command (config)
Purpose
[no] cable host authorization <mac_address> <ip_address>
Enable or disable
Cable Modem
Host
Authorization.
Where:
<mac_address>
<ip_address>
CPE MAC address in the format

xxxx.xxxx.xxxx.
IP address in the format A.B.C.D.
Example:
CASA-CMTS(config)# cable host authorization
0015.f2fe.8d6a 10.160.1.40
CASA-CMTS(config)#
Disable cable modem host authorization:
CASA-CMTS(config)# no cable host authorization
0015.f2fe.8d6a 10.160.1.40
CASA-CMTS(config)#
Displaying the cable host authorization

To show trusted host configuration:
Step
1
Command
Purpose
show cable host authorization
Show the cable

host
configuration.
Example:
CASA-CMTS(config)#show cable host authorization
cable host authorization 0015.f2fe.8d6a
10.160.1.40
Configuring MPEG Compliant Features

The MPEG standard requires that the Casa CMTS system generate Program Association Tables
(PAT) and Program Mapping Tables (PMT), and then insert them into MPEG transport streams.
This section covers commands for the following PAT and PMT operations:
Setting the PAT insertion interval

Setting the PMT insertion interval
Setting the PAT insertion interval

To set the PAT insertion interval:
588
CASA CMTS
Step
Command (config)
Purpose
pat interval <time>
Set and verify

the PAT insertion
interval.
Where:
<time>
PAT insertion interval in the range 100 to 1000

ms. Default value is 250.
Example:
Set the PAT insertion interval to 500 ms:
CASA-CMTS(config)# pat interval 500
CASA-CMTS# show running-config | i pat
pat interval 500
Setting the PMT insertion interval

To set the PAT insertion interval:
Step
Command (config)
Purpose
pmt interval <time>
Set and verify

the PMT
insertion interval.
Where:
<time>
PMT insertion interval in the range 100 to

1000 ms. Default value is 250.
Example:
Set the PMT insertion interval to 500 ms:
CASA-CMTS(config)# pmt interval 500
CASA-CMTS# show running-config | i pmt
pmt interval 500
Configuring DVB-compliant features

The Casa CMTS supports the DVB standard. The DVB standard requires the generation of
Service Information (SI) tables and insertion of them into MPEG transport streams. This section
covers commands for the following SI table operations:
Enabling/disabling SI table generation and insertion
Setting the network ID
Setting the channel transport stream ID
589
CASA CMTS
Enabling SI table generation and insertion

The SI table contains four sub-tables: EIT (Event Information Table), NIT (Network Information
Table), SDT (Service Description Table), and TDT (Time of Day Table). Each of the four tables
can be turned on or off individually. The default setting is disabled for each of four tables.
SI table generation and insertion setting is chassis based. When enabled, it applies to all QAM
downstream channels on the chassis.
To enable or disable EIT:
Step
Command (config)
Purpose
[no] si generator eit
Enable or disable
EIT.
Example:
CASA-CMTS(config)# si generator eit
CASA-CMTS(config)# no si generator eit
To check the configured generator:
CASA-CMTS(config)# show running-config | i
generator
To enable or disable NIT:
Step
Command (config)
Purpose
[no] si generator nit
Enable or disable
NIT.
Example:
CASA-CMTS(config)# si generator nit
CASA-CMTS(config)# no si generator nit
generator
To enable or disable SDT:

Step
Command (config)
Purpose
Enable or disable
SDT.
Example:
CASA-CMTS(config)# si generator sdt
CASA-CMTS(config)# no si generator sdt
generator
590
CASA CMTS
To enable or disable TDT:

Step
Command (config)
Purpose
Enable or disable
TDT.
Example:
CASA-CMTS(config)# si generator tdt
CASA-CMTS(config)# no si generator tdt
generator
Setting the network ID

The Network ID is needed in SI table generation. The network ID setting is based on the QAM
downstream channel.
To set a network ID:
Step
Command (config)
Purpose
interface qam <x/y>
Specifies the
QAM module
number and port.
Where:
<x/y>
x=QAM module number; y=QAM port number
Example:
channel <ch-id> network id <net-id>
Where:
<ch-id>
<net-id>
Set and verify

the network ID.
QAM channel number in the range 0 to 3.

Network ID number in the range 0 to 65535. The
Example:
Set network ID to 16 for channel 2 of QAM port 4:
CASA-CMTS(config-if-qam)# channel 2 network id 16
CASA-CMTS(config-if-qam)# show interface qam 2/0
brief
interface qam 2/0

interleave 128x1
591
CASA CMTS

channel 2 transport stream id 500
channel 2 network id 16
no shutdown
Setting the channel transport stream ID

The channel transport stream ID is needed in SI table generation. The setting is QAM
downstream channel based.
To set a channel transport stream ID:
1
interface qam <x/y>

Where:
<x/y>
Purpose
Specifies
the QAM
interface.
x=QAM module number; y=QAM port number
Example:
592
CASA CMTS
channel <ch-id> transport stream id <ts-id>

Where:
<ch-id>
<net-id>
QAM downstream channel number. Valid values are 0 to 3.
Set a
channel
transport
stream
ID.
QAM channel transport-stream ID in the range 0 to 65535.

The default setting is 0.
Example:
Set transport stream ID to 500 for channel 2 of QAM port 4:
CASA-CMTS(config-if-qam)# channel 2 transport stream id
500
CASA-CMTS(config-if-qam)# show interface qam 2/0 brief
interface qam 2/0

interleave 128x1
channel 2 transport stream id 500
channel 2 network id 16
no shutdown
Configuring TOT
The TOT (Time Offset Table) carries the UTC-time and date information as well as the local time
offset. It is transmitted in TS packets with a PID value of 0x0014 and a table ID of 0x73. This
section covers commands for the following TOT configurations:
Setting Time Zone

Setting Time Offset
Setting Daylight Saving Time (US only)
Setting the time zone

To set the time zone (not to be used for EuroDOCSIS):
593
CASA CMTS
Step
1
Command (config)
Purpose
si generator tot country-code <string> region-id <0-60>
Set and verify

the time zone.
Where:
<string>
3-character country identifier. When the countrycode is set to cet the time is adjusted to daylight
saving time (CEST) and readjusted to CET
automatically.
<0-60>
Time zone: 0 for none, 1 for the most eastern

region, and so on. To display a list of time zones:
CASA-CMTS# show timezone list
Example:
Set the time zone to the Central European Time:
CASA-CMTS(config)# si generator tot country-code
cet region-id 0
To verify the time zone setting:
CASA-CMTS(config)#show running-config | i tot
si
si
si
si
generator
generator
generator
generator
tot
tot
tot
tot
country-code cet region-id 0

offset-hours 5 offset-minutes 30
dst begin month 4 week 1 time 2
dst end month 10 week 5 time 2
Setting the time offset

The time offset is relative to the Universal Time Coordinated (UTC) time.
To set the time offset:
Step
1
Command (config)
Purpose
si generator tot offset-hours <-12 to 13> offset-minutes <0, 30,

45>
Set and verify

the time offset.
Where:
<-12 to 13>
<0, 30, 45>
Offset hours to UTC-time. Valid values are 12

to 13.
Minute part of the offset. Valid values are 0,
30, and 45.
Example:
If the offset in a time zone is 5 hours and 30 minutes (such as in
India), the command is:
CASA-CMTS(config)# si generator tot offset-hours
5 offset-minutes 30
594
CASA CMTS
To verify the time offset:

CASA-CMTS(config)# show running-config | i tot
Setting daylight saving time (US only)

To configure daylight saving time (DST) use the following pair of commands. Both the beginning
and the end of DST need to be specified to complete the DST configuration.
Step
1
Command (config)
Purpose
si generator tot dst begin month <1-12> week (1-5> time <0-3>
si generator tot dst end month <1-12> week (1-5> time <0-3>
Set and verify

the DST setting.
Where:
<1-12>
Both the
beginning and
the end of DST
are required in
the configuration
<1-5>
<0-3>
Month number, January to December.

First to fourth; enter 5 for last Sunday of month.
0 for 12 a.m. midnight to 3 a.m. after midnight.
Example:
Set daylight saving time beginning in the first Sunday of April at
2am:
CASA-CMTS(config)# si generator tot dst begin
month 4 week 1 time 2
Set daylight saving time ending in the last Sunday of October at
2am:
CASA-CMTS(config)# si generator tot dst end month
10 week 5 time 2
To verify the DST setting:
CASA-CMTS(config)# show running-config | i tot
Configuring the DOCSIS event notification policy

Enabling cable event reporting

Configuring event reporting by unique identifier
Configuring the event reporting flags for DOCSIS event messages
Enabling logging of DOCSIS event messages to a SYSLOG server
Configuring TRAP/INFORM and SYSLOG throttling and limiting attribute
Specifying the throttle interval
Specifying the throttle threshold
595
CASA CMTS
Enabling DOCSIS cable event reporting

The [no] cable event command enables and disables the generation and dispatching of DOCSIS
cable event message notifications. This function is enabled by default. Use the show cable
event running-config command to display the list of cable event IDs.
Note: The local CMTS log file is not affected by cable events that have been disabled with the
cable event command.
Step
1
Command
Purpose
[no] cable event
Enables or
disables
dispatching of
DOCSIS cable
events.
Example:
CASA-C10G(config)# cable event
CASA-C10G(config)# no cable event
Configuring event reporting by unique identifier

The cable event <identifier> command controls the dispatching of DOCIS cable event
messages by event ID. By default, all cable event messages except 82010100 and 82010400
are enabled. Use the show cable event running-config command to display the list of cable
event IDs. Use the no form of the command to disable any cable events using a valid identifier.
Note: The local CMTS log file is not affected by cable events that have been disabled with the
cable event command.
Step
1
Command
Purpose
[no] cable event <number>
Controls
dispatching of
cable events by
event identifier.
Where:
<number>
Specifies a valid cable ID value in the range 14294967295. Use the show cable event
running-config command to display the valid
cable event identifiers.
Example:
CASA-C10G(config)# no cable event 83020203
CASA-C10G(config)# show cable event runningconfig
.
.
cable event 83020103
no cable event 83020203
596
CASA CMTS
Displaying the cable event identifiers

Use the show cable event running-config command to display the list of valid cable event IDs,
as well as those IDs that have been disabled for dispatch with the no cable event command.
Step
1
Command
Purpose
show cable event running-config [brief]
Displays the
cable event
identifiers from
the CMTS
running
configuration.
Where:
brief
Specifies the shortened version of the cable

event identifier list.
Example:
CASA-C10G(config)# show cable event runningconfig
.
.
.
no cable event 83020203
Configure the event reporting flags for DOCSIS event messages

To configure the event reporting flags for DOCSIS event messages, which determines how the
CMTS reports these events, use the cable event priority command in global configuration mode.
To return to the default settings found in the DOCS-CABLE-DEVICE-MIB, use the no form of this
command:
Step
1
Command (config)
Purpose
[no] cable event priority {emergency | alert | critical | error |

warning | notice | informational | debug} flags
Configure event
priority reporting
flags.
Where:
<flags>
See Table 5 below.
Table 5. DOCSIS event priority and flags

Keyword
emergency
Description
Sets the event reporting flag for emergency system error messages. (Emergency
messages indicate that the system has become unusable and requires
597
CASA CMTS
immediate attention. This problem might also be affecting other parts of the
network.)
alert
critical
error
warning
notice
informational
debug
flags
Sets the event reporting flag for alert system error messages. (Alert messages
indicate that some type of system or connection failure has occurred and
requires immediate attention.)
Sets the event reporting flag for critical system error messages. (Critical
messages indicate that an error occurred which requires immediate attention to
avoid system or connection failure.).
Sets the event reporting flag for error system error messages. (Error messages
indicate that an error condition occurred that requires attention to resolve. Failure
to address this problem will result in some type of system or connection failure in
the near future.).
Sets the event reporting flag for warning system error messages. (Warning
messages indicate that a condition occurred that indicates attention is needed in
near future to avoid potential problems. Failure to address this problem could
result in some type of system or connection failure later on.) .
Sets the event reporting flag for notice system error messages. (Notice
messages indicate that a situation occurred that is normal but is significant
enough that system administrators might want to notice.)
Sets the event reporting flag for informational system error messages.
(Informational messages might or might not be significant to the system
administrators.).
Sets the event reporting flag for debug system error messages. (Debug
messages appear only when debugging has been enabled.).
Sets the event reporting flags value, in hex, which specifies how this
particular type of event message should be reported. The valid values are shown
below:
0x00 DOCSIS messages are not reported.
0x80 DOCSIS messages are saved in a local log on the CMTS.
0xA0 DOCSIS messages are reported to the local log and SYSLOG
servers
0xC0 DOCSIS messages are reported to the local log and trap receivers
0xE0 DOCSIS messages are reported to the local log, SYSLOG servers
and trap receivers
Displaying the current priority and flags for cable event logging
To show the event reporting flags for cable event messages:
598
CASA CMTS
Step
1
Command (config)
Purpose
show cable event notification-policy
Display current
cable event
logging priority
and flags
Example:
CASA-CMTS#config)#show cable event notificationpolicy
priority
flash-log mem-log traps
syslog
------------------------------------------------emergency
yes
no
no
no
alert
yes
no
no
no
critical
yes
no
yes
yes
error
yes
no
yes
yes
warning
no
yes
yes
yes
notice
no
yes
yes
yes
informational no
no
no
no
debug
no
no
no
no
Enabling logging of DOCSIS event messages to a SYSLOG server

To enable logging of DOCSIS event messages to a SYSLOG server, use the cable event syslogserver command in global configuration mode.
To disable the logging of a DOCSIS syslog server, use the no form of this command.
Step
1
Command (config)
Purpose
[no] cable event syslog-server <ip_address>
Enable or disable
the logging of a
DOCSIS syslog
server.
Where:
<ip_address>
2
The DOCSIS server address.
show running-config | i syslog

Example:
CMTS#config)#show running-config | i syslog
!syslog server for DOCSIS events:
cable event syslog-server 192.168.0.163
Verify the current

syslog server for
DOCSIS events.
Configuring the TRAP/INFORM and SYSLOG throttling and limiting

attribute
To configure how the CMTS throttles the SNMP traps and SYSLOG messages it generates for
DOCSIS event messages, use the cable event throttle-adminStatus command in global
configuration mode. To restore the default behavior, use the no form of this command.
599
CASA CMTS
Step
1
Command (config)
Purpose
[no] cable event throttle-adminStatus {inhibited |

maintainBelowThreshold | stopAtThreshold | unconstrained}
Configures how
the CMTS
throttles the
SNMP traps and
SYSLOG
messages.
Where:
unconstrained(1)
Causes traps and syslog

messages to be transmitted
without regard to the threshold
settings.
maintainBelowThreshold(
2)
Causes trap transmission and

syslog messages to be
suppressed if the number of
traps would otherwise exceed
the threshold.
stopAtThreshold(3)
Causes trap transmission to

cease at the threshold, and not
resume until directed to do so.
inhibited(4)
Causes all trap transmission and

syslog messages to be
suppressed.
show running-config | i throttle-adminStatus

Example:
CMTS#config)#show running-config | i throttleadminStatus
Verify the current

throttleadmin Status
setting
cable event throttle-adminStatus stopAtThreshold
Specifying the throttle interval

To specify the throttle interval, which controls how often the CMTS generates SNMP traps and
SYSLOG messages for DOCSIS event messages, use the cable event throttle-interval command
in global configuration mode. To restore the default behavior, use the no form of this command.
Step
1
Command (config)
Purpose
[no] cable event throttle-interval <num>
Specify the
throttle interval.
Where:
<num>
Throttle interval in unit of seconds. Valid values are

from 1-2147483647.
Specifying the throttle threshold

To set the maximum number of SNMP traps and SYSLOG messages that the CMTS can
generate for DOCSIS event messages during the throttle interval, use the cable event throttleCasa CMTS Software Configuration Guide
600
CASA CMTS
threshold command in global configuration mode. To restore the default number, use the no form
of this command.
Step
1
Command (config)
[no] cable event throttle-threshold <num>
Where:
<num>
Purpose
Specify the
throttle threshold
Throttle threshold in unit of seconds. Valid values are

from 1-2147483647.
show running-config | i throttle-threshold

Example:
CMTS#config)#show running-config | i throttlethreshold
Verify the current

throttle-threshold
setting
cable event throttle-threshold 1000
Using the logging commands

By default, the Casa CMTS saves logging messages (debugging output) to local flash as a logfile.
To redirect logging messages to a destination other than local flash, use the logging command.
Possible destinations include the console, virtual terminals, and hosts running a Syslog server.
Logging levels determine the severity of the information that is collected in the log file. The user
can set the logging levels as needed. Table 6 lists and briefly describes the logging levels and
corresponding keywords used to set the logging levels for these types of messages. Level 0,
emergencies, is the highest level and logs only the most serious errors. Level 7, debugging, is the
lowest level. Level 7 logs include the most messages because Level 7 logs include messages
from all levels.
Table 6. Message logging keywords and levels
Level
Keyword
Description
Syslog definition
Emergencies
System is unusable.
LOG_EMERG
Alerts
Immediate action is needed.
LOG_ALERT
Critical
Critical conditions exist.
LOG_CRIT
Errors
Error conditions exist.
LOG_ERR
Warnings
Warning conditions exist.
LOG_WARNING
Notification
Normal, but significant, conditions

exist.
LOG_NOTICE
Informational
Informational messages.
LOG_INFO
Debugging
Debugging messages.
LOG_DEBUG
601
CASA CMTS
This sub-section explains how to use logging commands to redirect and limit the types of logging
messages.
Configuring the logging target destinations and levels
Excluding user log-in messages from the log file
Display the current logging settings
Configuring logging targets and levels

The logging command allows you to direct messages processed by the CMTS to a specified
target destination. The target can be a remote syslog host, the system console display, volatile or
non-volatile memory, or a loopback interface. For each logging target, you need to specify the
type of message based on a severity level, as listed in Table 6.
Step
1
Command
Purpose
[no] logging {host <ip-address> | non-volatile | source-interface

loopback <number>| syslog | system | volatile} <level>
Set the
logging
target and
level.
Where:
host
IP address of the syslog host. A maximum of

8 hosts can be configured.
non-volatile
Logging level on non-volatile memory (flash

memory)
source-interface
loopback
The port number of the loopback interface in

the range 0 to 15.
syslog
Logging level for the syslog hosts, as

configured with the host <ip-address> option.
system
Logging level to system console display.
volatile
Logging level for local log on volatile memory

(RAM FS)
<level>
alerts, critical, debugging, emergencies,

errors, informational, notifications, warnings
Use the no
form of the
command to
remove any
previous
logging
settings.
Example:
Set the level of messages displayed on monitors to notification:
CASA-CMTS(config)# logging system notifications
Send alert messages to two syslog hosts:
CASA-CMTS(config)#logging host 192.168.8.123
CASA-CMTS(config)#logging host 192.168.8.145
CASA-CMTS(config)#logging syslog alerts
602
CASA CMTS
Excluding user messages from the log file by severity level

To disable all logging for specific users (up to 16) or to selectively disable certain logs for a user,
first create an exclusion list, and then enter a maximum severity level. Messages associated with
the specified log level (and all lower severity levels) for the specified user are disabled and will
not be logged.
Specifying the highest severity level (alert) disables logging of all messages for the specified
user. This is useful when users log in regularly to run a process, for example. Each log-in and
log-out creates an entry in the log file. This can fill the log file with entries that are not useful.
To create the exclusion list, enter config mode:
Step
Command (config)
Purpose
user log exclusion-list
Example:
CASA-CMTS(config)#user log exclusion-list
CASA-CMTS(user-log-exclusive-list)#
user <name> <level>
Enter user log

configuration
mode.
Where:
<name>
User name
<level>
Logging level (use alert for log-in entries):
alert -- severity level 1 (alert and below)
critical severity level 2 (critical and below)
error severity level 3 (error and below)
warning severity level 4 (warning and below)
notification severity level 5 (notification and

below)
information severity level 6 (information and

below)
debugging severity level 7 (debugging)
Add the user

name and
specify alert to
exclude log-ins
by this user from
the log file.
Example:
Exclude all logging messages associated with user test1 from the
log file:
CASA-CMTS(user-log-exclusive-list)# user test1
alert
Example:
Exclude all error, warning, notification, information, and debugging
messages associated with user test1 from the log file. All alert
and critical messages associated with user test1 will continue to
603
CASA CMTS
be logged.
CASA-CMTS(user-log-exclusive-list)# user test1
error
Displaying the current logging settings

To display the logging settings associated with all configured logging targets:
Step
1
Command (config)
Purpose
show logging all
Display all
current logging
settings
Example:
CASA-CMTS(config)#show logging all
/dev/console
:
notifications
system log level
:
notifications
non-volatile log level
:
warnings
volatile log level
:
errors
syslog level
:
warnings
syslog host:
192.168.8.123
192.168.8.145
604

CMTS Software Config Guide 11-14-11 Release 6.1.1

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

CMTS Software Config Guide 11-14-11 Release 6.1.1

Încărcat de

Drepturi de autor:

Formate disponibile

CMTS Software Configuration Guide

Version: November 15, 2011

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

Casa CMTS Software Configuration Guide

C2200 CMTS Hardware Installation Guide

V 5.0.7 / Feb 2008

Same as release C3200.5.0.7

V6.0.1 / July 2008

- DSG configuration section

V6.0.2 / Aug 2008

- Multicast configuration section

V6.0.3 / Aug 2008

- Bonding group configuration

Casa CMTS Software Configuration Guide

- Trunk-interface configuration section

- Remove preamble-offset field from modulation profile

- Add more commands to Load Balancing section

Rel5.2.1 / Nov 14 2008

- Remove BPI commands of privacy kek/tek grace-time

- Upstream channel-frequency range for J-DOCSIS

Rel5.4/June 29, 2009

- IPsec command update

-Added alias command for privileged mode.

Casa CMTS Software Configuration Guide

Added Source Address Verification

Casa CMTS Software Configuration Guide

Added loopback address features for FTP/TFTP and IPv6 support

Added extended ping command.

April 12, 2010

Added command for encrypting passwords.

April 19, 2010

Corrected error about downstream interfaces and service groups.

Casa CMTS Software Configuration Guide

Added stat and throughput options to show interface trunk

Corrected upper range of VLAN interfaces.

Casa CMTS Software Configuration Guide

Noted that si generator tot command is not used with EuroDOCSIS.

September 24, 2010

November 18, 2010

Added brief description of pre-equalization.

January 14, 2011

Reformatted document to reduce page count.