You are on page 1of 678

CMTS Software Configuration Guide

Version: February 7, 2013


(For Software Releases 5.2, 5.4.19, 5.4.21, 6.0.3, 6.1.1, 6.1.2, 6.1.3,
and 1G.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 2013 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: FEBRUARY 7, 2013 ............................................................................................................................ 1
(FOR SOFTWARE RELEASES 5.2, 5.4.19, 5.4.21, 6.0.3, 6.1.1, 6.1.2, 6.1.3, AND 1G.1)........................................... 1
TABLE OF CONTENTS ............................................................................................................................. 3
PREFACE.............................................................................................................................................. 29
PURPOSE OF THE GUIDE .................................................................................................................................. 29
AUDIENCE .................................................................................................................................................... 29
REVISION INFORMATION ................................................................................................................................. 29
CONTENTS ................................................................................................................................................... 35
NOTATION CONVENTIONS ............................................................................................................................... 35
1 CASA CMTS CONFIGURATION OVERVIEW.......................................................................................... 36
SLOT AND PORT NUMBERING ........................................................................................................................... 36
C2200 slot and port numbering ............................................................................................................ 36
C3200 slot and port numbering ............................................................................................................ 38
C10200 and C10G slot and port numbering ......................................................................................... 38
C10G REDUNDANCY OPERATIONS..................................................................................................................... 39
Slot information and cabling on the network side ................................................................................ 39
Slot information on the RF I/O side....................................................................................................... 39
High availability (HA) redundancy commands...................................................................................... 40
Fan, power, and temperature status on the C10G ............................................................................... 44
C10G 8-channel QAM frequency configurations .................................................................................. 45
C10G router redundancy....................................................................................................................... 47
C1G/C1N FEATURES AND CONFIGURATION DIFFERENCES WITH LARGER PLATFORMS .................................................. 47
COMPLETING PRE-CONFIGURATION ................................................................................................................... 47
USING THE COMMAND LINE INTERFACE .............................................................................................................. 48
STARTING THE SYSTEM CONFIGURATION ............................................................................................................. 48
Connecting the console ......................................................................................................................... 49
Resetting the console............................................................................................................................ 49
Starting the system ............................................................................................................................... 49
Viewing the loaded software version ................................................................................................... 50
Viewing the system hardware configuration ........................................................................................ 50
Viewing the system running configuration ........................................................................................... 50

Casa CMTS Software Configuration Guide

CASA CMTS
Entering and exiting configuration mode ............................................................................................. 51
Configuring CMTS device contact and location strings......................................................................... 51
Setting security access to the system console ...................................................................................... 51
Setting the console timout .................................................................................................................... 52
Saving the current configuration .......................................................................................................... 53
Resetting the IP address ....................................................................................................................... 54
Restoring factory defaults .................................................................................................................... 54
SAMPLE CONFIGURATION FILES ......................................................................................................................... 55
Basic configuration ............................................................................................................................... 55
General configuration ........................................................................................................................... 57
2 CONFIGURING AND MANAGING THE CMTS FROM THE CLI ................................................................ 60
MANAGING THE SYSTEM ................................................................................................................................. 61
Entering privileged mode ...................................................................................................................... 62
Exiting privileged mode ........................................................................................................................ 62
Changing the privileged mode password ............................................................................................. 63
Resetting the privileged mode password to the default setting ........................................................... 63
Encrypting passwords ........................................................................................................................... 63
Changing the prompt for privileged mode ........................................................................................... 64
Setting up a command alias ................................................................................................................. 64
Showing the configured command alias............................................................................................... 65
MANAGING CONFIGURATIONS AND FILES............................................................................................................ 65
Saving a running configuration to the startup configuration ............................................................... 65
Copying the startup configuration to a file........................................................................................... 66
Restoring a startup configuration from a file in NVRAM ...................................................................... 66
Restoring the startup configuration to the running configuration ....................................................... 66
Copying the running configuration to an external location .................................................................. 67
Copying files over FTP/TFTP.................................................................................................................. 68
Copying files from fdsk2 to destinations over FTP/TFTP ....................................................................... 70
Specifying an MD5 checksum file ......................................................................................................... 71
Displaying fdsk2 directory contents ...................................................................................................... 71
Displaying the running configuration ................................................................................................... 71
Displaying the system startup configuration ........................................................................................ 72
Displaying configuration settings within the current context............................................................... 72
MANAGING NVRAM FILES ............................................................................................................................. 72
Listing files in the directory ................................................................................................................... 72
Casa CMTS Software Configuration Guide

CASA CMTS
Removing a file from the directory ....................................................................................................... 73
Copying a file to a remote host............................................................................................................. 73
UPDATING CASA CMTS SOFTWARE .................................................................................................................. 74
USER MANAGEMENT AND SECURITY CONTROL ..................................................................................................... 74
Assigning commands to user levels ...................................................................................................... 75
SSH support (Release 5.4 and later)...................................................................................................... 76
Enabling and disabling SSH................................................................................................................... 78
Adding Telnet and SSH users ................................................................................................................ 78
Displaying Telnet and SSH users ........................................................................................................... 79
Changing Telnet and SSH user passwords ............................................................................................ 80
Removing Telnet or SSH users .............................................................................................................. 80
Removing a logged-in user ................................................................................................................... 81
Configuring and displaying the Telnet port .......................................................................................... 81
Setting the maximum number of concurrent Telnet session ................................................................ 82
Configuring Telnet and SSH timeout periods ........................................................................................ 82
Rebooting the system ........................................................................................................................... 82
Enabling a save configuration reminder at reboot............................................................................ 84
Rebooting a downstream/upstream module ....................................................................................... 85
Displaying the system boot device........................................................................................................ 85
Displaying the system hardware version .............................................................................................. 85
Displaying the system software version ............................................................................................... 86
Setting and displaying the system clock ............................................................................................... 86
Setting and displaying the time zone.................................................................................................... 87
Synchronizing the system clock with an NTP server ............................................................................. 88
Displaying NTP status ........................................................................................................................... 89
Configuring system rate limiting (Rel. 6.0 and later) ............................................................................ 89
Configuring an NTP loopback interface ................................................................................................ 90
Adding and removing IPv4 network route entries ................................................................................ 90
Adding and removing IPv4 host table entries ....................................................................................... 91
Adding and removing IPv6 network route entries ................................................................................ 91
Displaying the IPv4 and IPv6 routing tables ......................................................................................... 92
Displaying IP interface status ............................................................................................................... 92
Displaying alarm states ........................................................................................................................ 93
Displaying system logs .......................................................................................................................... 94
Configuring a log message source IP address....................................................................................... 94

Casa CMTS Software Configuration Guide

CASA CMTS
Configuring lawful intercept ................................................................................................................. 94
Displaying Rapid Spanning Tree Protocol status .................................................................................. 95
Displaying ARP entries .......................................................................................................................... 96
Configuring the ARP request interval ................................................................................................... 97
Configuring ARP packet filtering........................................................................................................... 97
Clearing an entry in the ARP cache ....................................................................................................... 98
Displaying the ARP request interval ..................................................................................................... 98
Enabling and disabling the ARP timeout reset ..................................................................................... 99
Displaying IPv6 information.................................................................................................................. 99
Displaying the ARP timeout reset configuration................................................................................. 100
Displaying CPU usage ......................................................................................................................... 100
Displaying memory usage................................................................................................................... 103
Viewing module statistics ................................................................................................................... 104
Monitoring line card status ................................................................................................................ 107
Monitoring Gigabit Ethernet interfaces.............................................................................................. 107
Clearing interface statistics ................................................................................................................ 108
Displaying the current monitor settings (Rel. 6.0 and later)............................................................... 108
Enabling auto-reboot mode (5.2) ....................................................................................................... 108
Using the ping and ping6 commands ................................................................................................. 109
Testing connectivity with extended ping ............................................................................................ 110
Using the traceroute commands ........................................................................................................ 110
Configuring ICMP packet filtering....................................................................................................... 113
Configuring DHCP packet filtering ...................................................................................................... 114
Displaying all filtering settings in the running configuration ............................................................. 114
Setting channel utilization intervals ................................................................................................... 115
Displaying channel utilization ............................................................................................................. 115
Displaying upstream channel utilization............................................................................................. 117
Displaying downstream channel utilization........................................................................................ 118
Configuring the system monitor (Release 5.4 and later) .................................................................... 119
CONFIGURING THE MANAGEMENT PORT........................................................................................................... 120
Setting the Fast Ethernet port as the management port.................................................................... 120
Obtaining the IP address of the Fast Ethernet port from the DHCP server......................................... 121
Configuring an IP access group on eth0 (C3200 and C10200 only) .................................................... 121
CONFIGURING GIGABIT ETHERNET (GIGE) PORTS............................................................................................... 122
Enabling/disabling auto-negotiation mode on a Gigabit Ethernet port ............................................. 123

Casa CMTS Software Configuration Guide

CASA CMTS
Assigning or removing a Gigabit Ethernet port IP address ................................................................. 124
Assigning an IP access group to a Gigabit Ethernet port .................................................................... 124
Assigning an IPv6 address to a Gigabit Ethernet port ........................................................................ 125
Assigning a Gigabit Ethernet port to a VLAN ...................................................................................... 126
Enabling/disabling the IGMP client service on a Gigabit Ethernet port ............................................. 126
Configuring the MTU size on a Gigabit Ethernet interface (5.4)......................................................... 127
Displaying the Gigabit Ethernet interface configuration .................................................................... 128
Displaying the 10Gigabit Ethernet interface configuration ................................................................ 129
Displaying the Gigabit Ethernet interface statistics ........................................................................... 130
CONFIGURING LOOPBACK INTERFACES.............................................................................................................. 131
Enabling interface loopback mode ..................................................................................................... 132
Configuring an IPv6 address on a loopback interface ........................................................................ 132
Configuring an IPv4 address on a loopback interface ........................................................................ 133
Assigning an access group to a loopback interface ............................................................................ 133
Configuring a log message source IP address..................................................................................... 134
Configuring a loopback interface as source IP address on FTP/TFTP packets ................................... 134
Setting the source IP address of lawful intercept packets to the loopback IP interface ..................... 135
Configuring trunk interfaces ............................................................................................................... 135
Creating a trunk interface................................................................................................................... 135
Configuring a trunk description .......................................................................................................... 136
Assigning an IP address to a trunk interface ...................................................................................... 137
Enabling/disabling a trunk interface .................................................................................................. 138
Adding a GigE port to a trunk interface .............................................................................................. 138
Enabling IGMP client services on a trunk interface ............................................................................ 139
Applying an IP access group to a trunk interface ............................................................................... 139
Displaying a trunk interface configuration ......................................................................................... 140
Displaying ARP entries from a trunk interface.................................................................................... 141
CONFIGURING DNS ..................................................................................................................................... 142
CONFIGURING DHCP ................................................................................................................................... 142
Using the DHCP insert function........................................................................................................... 143
DHCP and DHCPv6 Leasequery ........................................................................................................... 144
CONFIGURING LINK AGGREGATION CONTROL PROTOCOL (LACP) (5.4) ................................................................. 146
Enabling the LACP global configuration ............................................................................................. 146
Setting LACP port priority ................................................................................................................... 147
Setting the LACP system port priority ................................................................................................. 147

Casa CMTS Software Configuration Guide

CASA CMTS
Displaying LACP group information .................................................................................................... 147
Configuring and displaying LACP port priority on GigE interfaces ...................................................... 148
Configuring and displaying LACP trunk interfaces .............................................................................. 149
Displaying the LACP system ID............................................................................................................ 150
CONFIGURING IS-IS ROUTING PROTOCOL (5.4 ONLY) ........................................................................................ 150
Configuring IPv4 IS-IS under a GigE Port............................................................................................. 150
Configuring IPv6 IS-IS under a GigE port............................................................................................. 151
Configuring an IS-IS circuit type on a GigE interface .......................................................................... 151
Configuring IS-IS point-to-point links .................................................................................................. 152
Configuring the complete sequence number PDU (CSNP) interval ..................................................... 153
Configuring the IS-IS Hello interval ..................................................................................................... 153
Configuring the IS-IS Multiplier for Hello holding time ....................................................................... 154
Enabling padding on IS-IS Hello packets ............................................................................................. 155
Configuring the IS-IS default metric .................................................................................................... 155
Configuring the authentication password for a GigE interface .......................................................... 156
Configuring the IS-IS priority ............................................................................................................... 157
Configuring the IS-IS retransmit-interval ............................................................................................ 157
Configuring IS-IS router area tag ........................................................................................................ 158
Displaying the IS-IS command list ....................................................................................................... 158
Specifying the IS-IS IPv6 address family parameters .......................................................................... 159
Configuring the IS-IS router area authentication password ............................................................... 161
Configuring the IS-IS router authentication key chain ........................................................................ 162
Configuring the IS-IS router authentication mode .............................................................................. 162
Configuring the IS-IS router authentication send-only option ............................................................ 163
Configuring the IS-IS router default route distribution ....................................................................... 164
Configuring the IS-IS router domain authentication password .......................................................... 164
Configuring the IS area types.............................................................................................................. 165
Configuring the IS-IS LSP generation interval ..................................................................................... 166
Configuring the IS-IS LSP lifetime ........................................................................................................ 166
Configuring the IS-IS route redistribution metric style........................................................................ 167
Configuring the network entity title (NET).......................................................................................... 167
Enabling the IS-IS dynamic hostname capability ................................................................................ 168
Configuring IS-IS passive interfaces .................................................................................................... 168
Configuring IS-IS to redistribute route advertisements from other protocols .................................... 169
Setting the IS-IS overload bit............................................................................................................... 170

Casa CMTS Software Configuration Guide

CASA CMTS
Setting the IS-IS shortest path first (SPF) calculations ........................................................................ 171
Setting the IPv4 summary address prefix ........................................................................................... 172
Displaying the IS-IS area configuration............................................................................................... 172
Displaying the IS-IS counter statistics ................................................................................................. 173
Displaying the IS-IS link state database .............................................................................................. 174
Displaying the IS-IS interface statistics ............................................................................................... 175
Displaying the IS-IS neighbor routers.................................................................................................. 176
Displaying the IS-IS topology information .......................................................................................... 176
Displaying the IPv4 and IPv6 IS-IS routing table ................................................................................. 177
CONFIGURING PROTOCOL INDEPENDENT MULTICAST IN SPARSE MODE ................................................................. 177
Enabling PIM-SM on a GigE or loopback interface ............................................................................. 178
Displaying the current PIM-SM interface and neighbor configurations ............................................. 178
Configuring rendezvous point addresses ............................................................................................ 178
Configuring the rendezvous point candidate ...................................................................................... 180
Configuring the bootstrap router candidate....................................................................................... 181
Setting the Shortest Path Tree threshold ............................................................................................ 182
Configuring source-specific multicast ................................................................................................. 183
CONFIGURING THE OSPF ROUTING PROTOCOL ................................................................................................. 183
Entering OSPF configuration mode..................................................................................................... 185
Exiting OSPF configuration mode ....................................................................................................... 185
Enabling OSPF area authentication .................................................................................................... 185
Configuring the OSPF area default cost .............................................................................................. 186
Configuring the OSPF area filter list.................................................................................................... 187
Configuring the OSPF area export list ................................................................................................. 187
Configuring the OSPF area import list ................................................................................................ 188
Configuring the OSPF area NSSA ........................................................................................................ 189
Configuring the OSPF area range ....................................................................................................... 190
Configuring the OSPF area shortcut ................................................................................................... 191
Configuring the OSPF area stub .......................................................................................................... 191
Configuring the OSPF area virtual link ................................................................................................ 192
Configuring the OSPF interface auto cost ........................................................................................... 194
Configuring OSPF-compatible RFC1583 .............................................................................................. 194
Configuring OSPF control-distribution default information ................................................................ 195
Configuring the OSPF default metric .................................................................................................. 196
Configuring the OSPF administrative distance ................................................................................... 197

Casa CMTS Software Configuration Guide

CASA CMTS
Displaying the OSPF command list ..................................................................................................... 197
Configuring the OSPF neighbor router ................................................................................................ 198
Configuring OSPF routing on an IP network ....................................................................................... 199
Configuring the OSPF ABR type .......................................................................................................... 200
Configuring the OSPF route ID ............................................................................................................ 200
Configuring the OSPF passive interface .............................................................................................. 201
Configuring the OSPF distribute list .................................................................................................... 201
Configuring OSPF route redistribution ................................................................................................ 202
Configuring the OSPF refresh parameters .......................................................................................... 203
Configuring the OSPF route ID ............................................................................................................ 204
Configuring the OSPF routing timers .................................................................................................. 204
Configuring IP OSPF authentication.................................................................................................... 205
Configuring the IP OSPF authentication-key ....................................................................................... 206
Configuring the IP OSPF cost .............................................................................................................. 206
Configuring the IP OSPF dead interval ................................................................................................ 207
Configuring the IP OSPF Hello interval................................................................................................ 208
Configuring the IP OSPF message digest key ...................................................................................... 208
Configuring the IP OSPF retransmit interval ....................................................................................... 209
Configuring the IP OSPF transmit delay .............................................................................................. 210
Displaying OSPF general information ................................................................................................. 210
Displaying the OSPF internal routing table entries ............................................................................. 211
Displaying the OSPF database for a specified router .......................................................................... 211
Displaying OSPF interface information ............................................................................................... 211
Displaying OSPF neighbor information ............................................................................................... 212
Displaying the OSPF routing table ...................................................................................................... 212
Displaying IPv4 route information ...................................................................................................... 212
Displaying IPv6 route information ...................................................................................................... 213
Sample OSPF configurations ............................................................................................................... 214
CONFIGURING THE ROUTING INFORMATION PROTOCOL ...................................................................................... 214
Entering RIP configuration mode ........................................................................................................ 215
Exiting RIP configuration mode .......................................................................................................... 215
Configuring the RIP default route ....................................................................................................... 215
Configuring the RIP default metric ..................................................................................................... 216
Configuring the RIP administrative distance ...................................................................................... 217
Configuring the RIP filter list ............................................................................................................... 217

Casa CMTS Software Configuration Guide

10

CASA CMTS
Displaying the RIP command list ........................................................................................................ 218
Configuring the RIP neighbor router ................................................................................................... 219
Configuring RIP routing on an IP network .......................................................................................... 219
Configuring the RIP offset list ............................................................................................................. 220
Configuring the RIP passive interface ................................................................................................. 221
Redistributing routes over RIP ............................................................................................................ 221
Configuring RIP static routes .............................................................................................................. 222
Configuring the RIP router map .......................................................................................................... 223
Configuring the RIP routing timers ..................................................................................................... 223
Configuring the RIP version ................................................................................................................ 224
Configuring the IP RIP authentication key chain ................................................................................ 224
Configuring an IP RIP authentication string ....................................................................................... 225
Configuring the IP RIP authentication mode ...................................................................................... 226
Displaying RIP routing information..................................................................................................... 226
Displaying RIP status information ...................................................................................................... 227
Displaying IPv4 route information ...................................................................................................... 227
Displaying IPv6 route information ...................................................................................................... 228
CONFIGURING THE BGP ROUTING PROTOCOL (RELEASE 5.4 AND LATER) ............................................................... 229
Enabling BGP routing.......................................................................................................................... 229
Setting the BGP distance .................................................................................................................... 230
BGP decision processing ..................................................................................................................... 231
Enabling BGP networks....................................................................................................................... 232
Configuring BGP routes ...................................................................................................................... 232
Enabling route aggregation ................................................................................................................ 232
Configuring BGP route redistribution ................................................................................................. 233
Defining BGP peers ............................................................................................................................. 234
Defining BGP peer passwords ............................................................................................................. 235
Configuring BGP peers ........................................................................................................................ 236
Peer filtering ....................................................................................................................................... 242
Configuring BGP peer groups.............................................................................................................. 245
Setting the BGP address family........................................................................................................... 246
Specifying the BGP IPv6 address family parameters .......................................................................... 247
Configuring autonomous systems ...................................................................................................... 252
Defining the AS path access list .......................................................................................................... 252
Using the BGP communities attribute ................................................................................................ 253

Casa CMTS Software Configuration Guide

11

CASA CMTS
Configuring BGP community lists ....................................................................................................... 254
BGP community in route map ............................................................................................................. 255
Using the BGP community attribute ................................................................................................... 255
Displaying BGP routes......................................................................................................................... 259
Clearing and reestablishing BGP routes ............................................................................................. 260
Enabling capability negotiation .......................................................................................................... 262
Configuring route reflectors................................................................................................................ 263
IP ACCESS CONTROL ..................................................................................................................................... 264
Creating and removing ACLs............................................................................................................... 265
Entering and exiting ACL editing mode............................................................................................... 265
Adding and removing control rules .................................................................................................... 265
Adding remark statements to the ACL ................................................................................................ 267
Displaying a control rule in an ACL ..................................................................................................... 268
Displaying ACL names ......................................................................................................................... 268
Numbering control rules in ACLs......................................................................................................... 269
Applying an ACL to an IP interface (C3200 and C10200 only) ............................................................ 269
Removing the ACL from an IP interface .............................................................................................. 271
Creating and deleting IP access classes .............................................................................................. 271
Displaying access class information (Release 5.4) .............................................................................. 272
CONFIGURING ROUTE MAPS ........................................................................................................................... 273
Creating a named and sequenced route-map .................................................................................... 273
Using the route-map match commands ............................................................................................. 274
Matching BGP autonomous system paths.......................................................................................... 274
Matching the BGP community list ...................................................................................................... 275
Matching IPv4 and IPv6 addresses ..................................................................................................... 276
Matching route metrics ...................................................................................................................... 276
Matching route origins ....................................................................................................................... 277
Matching peer routes ......................................................................................................................... 278
Matching route tags ........................................................................................................................... 278
Using the route-map set commands .................................................................................................. 279
Modifying BGP autonomous system paths ......................................................................................... 279
Setting the atomic aggregate ............................................................................................................. 279
Modifying the BGP community attribute............................................................................................ 280
Modifying next-hop IP addresses........................................................................................................ 281
Setting the BGP local-preference path attribute ................................................................................ 281

Casa CMTS Software Configuration Guide

12

CASA CMTS
Setting the metric for destination routing .......................................................................................... 282
Modifying route origins ...................................................................................................................... 283
Setting the BGP originator-id attribute .............................................................................................. 283
Setting the BGP weight attribute ........................................................................................................ 284
Displaying route-map details .............................................................................................................. 284
CONFIGURING VIRTUAL LOCAL AREA NETWORKS (VLANS) ................................................................................. 284
Configuring a VLAN............................................................................................................................. 285
Configuring a VLAN description .......................................................................................................... 285
Configuring up to six VLANs concurrently (Release 5.4 and later) ...................................................... 286
Configuring VLANs in a range (Release 5.4 and later) ........................................................................ 286
Configuring the MAC address on each VLAN interface....................................................................... 286
Enabling/disabling VLAN Interfaces (5.4) ........................................................................................... 287
Assigning a Gigabit Ethernet port to a VLAN ...................................................................................... 287
Assigning a 10Gigabit Ethernet port to a VLAN.................................................................................. 288
Removing a Gigabit Ethernet port from a VLAN ................................................................................. 288
Removing a 10Gigabit Ethernet port from a VLAN ............................................................................ 289
Assigning an IPv4 address to a VLAN.................................................................................................. 289
Assigning an IPv6 address to a VLAN.................................................................................................. 290
Rate limiting multicast traffic over a VLAN interface ......................................................................... 291
Assign a QAM port to a VLAN ............................................................................................................. 291
Assigning an IP access group to a VLAN interface .............................................................................. 292
Assigning a trunk to a VLAN interface ................................................................................................ 293
Displaying all VLAN configurations ..................................................................................................... 294
Displaying a VLAN interface (Release 5.4) .......................................................................................... 294
Displaying ARP entries from the current VLAN ................................................................................... 295
CONFIGURING L2VPN ................................................................................................................................. 296
Specifying ports/interfaces on the NSI side of the L2VPN VLAN ......................................................... 296
Specifying GigE/trunk interfaces on the L2VPN VLAN ........................................................................ 297
Preventing and permitting station movement and local forwarding ................................................. 297
Displaying the station movement and local forwarding configuration .............................................. 298
Displaying configured L2VPNs ............................................................................................................ 298
Displaying L2VPN statistics on QAM modules .................................................................................... 299
CONFIGURING TACACS (RELEASE 5.4) ........................................................................................................... 299
Configuring the TACACS host IP .......................................................................................................... 299
Configuring a TACACS key .................................................................................................................. 300

Casa CMTS Software Configuration Guide

13

CASA CMTS
Enabling password authentication at the TACACS+ server................................................................. 300
Disabling the TACACS+ authentication password............................................................................... 300
Enabling ASCII clear text authentication ............................................................................................ 301
Using RADIUS/TACACS+ Server for default server group for AAA login authentication ..................... 301
Configuring the AAA authentication login .......................................................................................... 301
Configuring AAA authorization ........................................................................................................... 302
Enabling accounting ........................................................................................................................... 303
Command accounting ......................................................................................................................... 303
Configuring AAA accounting for start-stop events ............................................................................. 303
Configuring AAA RADIUS-source loopback interface configuration ................................................... 304
Disabling the AAA RADIUS source ...................................................................................................... 304
Configuring the RADIUS server ........................................................................................................... 304
Disabling a specified RADIUS server or RADIUS encryption key ......................................................... 305
Displaying the AAA configuration ....................................................................................................... 305
STREAM CONFIGURATION AND MANAGEMENT................................................................................................... 306
Modes for mapping input streams to QAM output channels ............................................................. 306
Enabling manual operation mode ...................................................................................................... 306
Enabling RPC mode ............................................................................................................................. 307
Using auto-operation mode................................................................................................................ 308
Enabling auto-multiplex mode ........................................................................................................... 308
Enabling Group-4-port operation mode ............................................................................................. 309
Enabling Group-2-port operation mode ............................................................................................. 310
Setting the de-jitter interval ............................................................................................................... 311
Entering stream configuration mode.................................................................................................. 312
Ending stream configuration mode .................................................................................................... 312
Setting the stream source IP address ................................................................................................. 313
Setting the stream destination IP address .......................................................................................... 313
Setting the stream source UDP port ................................................................................................... 314
Setting the stream destination UDP port............................................................................................ 315
Displaying configured streams ........................................................................................................... 315
Binding a stream to a QAM output channel ....................................................................................... 316
Displaying unmapped streams ........................................................................................................... 317
Stream configuration example ........................................................................................................... 318
CONFIGURING DOWNSTREAM QAM PORTS ...................................................................................................... 319
Entering QAM interface configuration mode ..................................................................................... 319

Casa CMTS Software Configuration Guide

14

CASA CMTS
Ending QAM interface configuration mode ........................................................................................ 320
Enabling QAM output ports ................................................................................................................ 320
Disabling QAM output port ................................................................................................................ 321
Enabling QAM output channels .......................................................................................................... 321
Disabling QAM output channels ......................................................................................................... 322
Setting the QAM port IP address and subnet mask ............................................................................ 322
Setting the QAM port MAC address ................................................................................................... 323
Setting the QAM modulation type ...................................................................................................... 324
Setting the QAM channel annex ......................................................................................................... 325
Setting the QAM frequency ................................................................................................................ 326
Setting the QAM output power .......................................................................................................... 327
Setting the QAM interleave level ........................................................................................................ 328
Setting the QAM spectral inversion .................................................................................................... 329
Displaying QAM interface configurations ........................................................................................... 330
Displaying QAM channel counters and utilization rates ..................................................................... 330
Displaying QAM downstream channel sets ........................................................................................ 331
CONFIGURING UPSTREAM PORT INTERFACES ..................................................................................................... 332
About upstream interface configurations........................................................................................... 332
Multiple upstream logical channels, dynamic channel width switching, independent power levels 333
Entering the upstream port interface configuration mode ................................................................ 334
Ending an upstream port interface configuration session .................................................................. 334
Enabling upstream ports .................................................................................................................... 335
Disabling upstream ports ................................................................................................................... 335
Entering an upstream logical interface description ............................................................................ 336
Showing upstream port interface configurations ............................................................................... 337
Displaying upstream interface status ................................................................................................. 341
Setting the upstream logical channel frequency ................................................................................ 343
Setting the upstream logical channel width ....................................................................................... 344
Changing the upstream MAP size ....................................................................................................... 345
Setting the upstream input power level ............................................................................................. 346
Adjusting the upstream input power threshold .................................................................................. 347
Adjusting the upstream input power level .......................................................................................... 348
Setting the upstream map-advance ................................................................................................... 349
Enabling the upstream logical-channels ............................................................................................. 351
Disabling the upstream logical-channels ............................................................................................ 351

Casa CMTS Software Configuration Guide

15

CASA CMTS
Setting upstream channel data and ranging backoff values .............................................................. 352
Configuring the ranging hold-off priority bit ...................................................................................... 356
Setting the upstream channel mini-slot size ....................................................................................... 357
Enabling the upstream channel class identifier .................................................................................. 358
Setting the upstream channel S-CDMA frame interval ....................................................................... 359
Assigning modulation profiles to an upstream interface.................................................................... 360
Specifying multiple secondary profiles to an upstream interface ....................................................... 361
Setting the upstream channel pre-equalization ................................................................................. 361
Setting the provisioned attribute mask .............................................................................................. 362
Enabling/disabling ingress noise cancellation .................................................................................... 364
Setting up voice bandwidth reserve percentage ................................................................................ 365
Configuring the QoS traffic bandwidth reserve percentage ............................................................... 366
Applying spectrum rules to upstream channels .................................................................................. 367
Enabling rate limiting ......................................................................................................................... 368
Displaying the upstream channel utilization rates ............................................................................. 369
Displaying the upstream channel signal quality ................................................................................. 370
Displaying the upstream channel burst nose...................................................................................... 370
Displaying upstream channel sets ...................................................................................................... 372
Displaying voice information on upstream interfaces ........................................................................ 373
CONFIGURING IP-BUNDLE INTERFACES ............................................................................................................. 373
Adding the primary IP interface.......................................................................................................... 374
Adding a secondary IP bundle interface ............................................................................................. 375
Remove an IP bundle secondary IP address........................................................................................ 375
Adding primary and secondary IPv6 interfaces .................................................................................. 376
Specifying the IPv6 local link address ................................................................................................. 377
Displaying the IPv6 local link address ................................................................................................. 378
Adding a helper-address ..................................................................................................................... 378
Configure IP bundle sub-interfaces (Release 5.4) ............................................................................... 379
Applying IP bundle interfaces to MAC domains .................................................................................. 380
Classifying CPE devices for DHCP option 60 string matching ............................................................. 381
Configuring the IP RIP authentication key chain ................................................................................ 382
Configuring an IP RIP authentication string ....................................................................................... 383
Configuring the IP RIP authentication mode ...................................................................................... 383
Displaying the IP bundle interface configuration and statistics ......................................................... 384
CONFIGURING MAC DOMAINS....................................................................................................................... 385

Casa CMTS Software Configuration Guide

16

CASA CMTS
Displaying domain interface configurations ....................................................................................... 386
Creating new domain interfaces ......................................................................................................... 387
Binding IP-bundle interfaces ............................................................................................................... 388
Binding upstream interfaces ............................................................................................................... 388
Deleting upstream interface bindings ................................................................................................ 389
Binding downstream interfaces .......................................................................................................... 390
Binding secondary downstream interfaces (5.4 only)......................................................................... 390
Deleting downstream interface bindings............................................................................................ 391
Enabling MAC domain interfaces ....................................................................................................... 392
Disabling MAC domain interfaces ...................................................................................................... 392
Setting MAC domain interface IP addresses ....................................................................................... 393
Setting MAC domain interface IPv6 addresses (Rel. 5.2 and earlier).................................................. 393
Removing MAC domain interface IPv6 addresses (Rel. 5.2 and earlier) ............................................. 394
Setting the helper-address (Software Ver. 5.2 and earlier) ............................................................... 394
Configuring MAC domain IP bundle interfaces ................................................................................... 396
Setting the domain sync-interval ........................................................................................................ 397
Specifying the intial technique for moving cable modems to upstream channels.............................. 397
Setting the upstream insertion-interval.............................................................................................. 398
Configuring the MDD interval ............................................................................................................. 399
Enabling a domain interface gateway IP address .............................................................................. 400
Enabling a domain interface TFTP proxy ............................................................................................ 401
Rejecting modem registrations with TFTP enforce ............................................................................. 401
Displaying modem registrations that have bypassed TFTP ................................................................ 402
Enabling/disabling IP policies on a domain interface ......................................................................... 402
Configuring multicast on MAC domain interfaces .............................................................................. 403
Enabling/disabling DHCP authorization on a MAC domain interface ................................................ 404
Configuring channel bonding on MAC domain interface .................................................................... 404
Enabling MAC domain multicast DSID forwarding ............................................................................. 405
Configuring IP-provisioning-mode on a MAC domain interface ......................................................... 406
Configuring MAC domain IPv6 router advertisement parameters ..................................................... 406
Displaying the router advertisement table ......................................................................................... 409
Configuring BPI+ on a MAC domain interface .................................................................................... 409
Configuring cable modem trap generation and interval .................................................................... 410
Displaying the MAC domain interface configuration.......................................................................... 411
Displaying MAC domain statistics ...................................................................................................... 411

Casa CMTS Software Configuration Guide

17

CASA CMTS
CONFIGURING SERVICE GROUPS ...................................................................................................................... 412
Creating a new service group ............................................................................................................. 412
Binding upstream interfaces ............................................................................................................... 413
Binding downstream interfaces .......................................................................................................... 414
Displaying service groups ................................................................................................................... 415
Displaying MAC domain downstream service groups (Release 5.4) ................................................... 416
Displaying specific MAC domain downstream service groups ............................................................ 416
Displaying a specific downstream service group ................................................................................ 417
Displaying MAC domain upstream service group information ........................................................... 417
CONFIGURING BONDING GROUPS .................................................................................................................... 417
Creating new downstream/upstream bonding groups ...................................................................... 418
Binding upstream interfaces to a bonding group ............................................................................... 419
Binding downstream interfaces to a bonding group .......................................................................... 420
Displaying bonding groups ................................................................................................................. 421
Setting up the receive channel configuration ..................................................................................... 421
Assigning a receive module ................................................................................................................ 422
Assigning a receive channel ................................................................................................................ 422
Displaying the receive channel configuration ..................................................................................... 423
CONFIGURING MODULATION PROFILES ............................................................................................................. 424
Predefined modulation-profile 1 parameters ..................................................................................... 424
Predefined modulation-profile 2 parameters ..................................................................................... 425
Predefined modulation-profile 3 parameters ..................................................................................... 425
Predefined modulation-profile 4 parameters ..................................................................................... 425
Predefined modulation-profile 5 parameters ..................................................................................... 426
Configuring a modulation profile........................................................................................................ 427
Configuring TDMA burst types............................................................................................................ 427
Configuring ATDMA burst types ......................................................................................................... 429
Configuring MTDMA burst types ........................................................................................................ 431
Auto-mode MTDMA-type modulation profile configuration .............................................................. 431
Manual mode MTDMA-type modulation profile configuration.......................................................... 431
Configuring SCDMA burst types.......................................................................................................... 433
Retrieving configured modulation profiles ......................................................................................... 434
Removing modulation profiles ............................................................................................................ 435
Upstream burst noise detection and monitoring ................................................................................ 435
CONFIGURING MULTICAST OPERATIONS ........................................................................................................... 436

Casa CMTS Software Configuration Guide

18

CASA CMTS
Setting the multicast maximum channel utilization ........................................................................... 437
Enabling/disabling multicast session authorization ........................................................................... 438
Enabling/disabling the multicast single security association identifier .............................................. 438
Configuring a multicast session authorization profile ........................................................................ 439
Configuring a multicast session rule ................................................................................................... 439
Configuring the default action for a multicast join request ................................................................ 440
Configuring a maximum session number for multicast authorization ............................................... 441
Assigning a profile to multicast authorization .................................................................................... 441
Displaying multicast authorization configurations ............................................................................. 441
Displaying multicast authorization sessions ....................................................................................... 442
Configuring a multicast group table ................................................................................................... 442
Configuring multicast group encryption ............................................................................................. 444
Configuring multicast group QoS........................................................................................................ 444
Configuring a multicast group service class........................................................................................ 445
Configuring a default service class for a multicast group ................................................................... 447
Displaying multicast group configurations ......................................................................................... 447
Creating static multicast sessions ....................................................................................................... 448
Configuring redundant downstream multicast .................................................................................. 450
Removing a static multicast session ................................................................................................... 451
Displaying static multicast sessions .................................................................................................... 451
Configuring IGMP packet filtering ...................................................................................................... 452
Displaying all filtering settings in the running configuration ............................................................. 452
Managing multicast for IPTV as a limited multicast session .............................................................. 453
Limited multicast sessions .................................................................................................................. 453
General multicast sessions ................................................................................................................. 453
How to identify limited multicast sessions ......................................................................................... 453
Multicast Listener Discovery (RFC2710).............................................................................................. 454
CONFIGURING CABLE SERVICE CLASSES ............................................................................................................. 454
Creating a cable service class ............................................................................................................. 454
Specifying the cable service class parameters .................................................................................... 455
Displaying service class parameters ................................................................................................... 457
Applying service classes to modem configuration files....................................................................... 459
CONFIGURING PACKETCABLE ......................................................................................................................... 460
Enabling PacketCable operation ......................................................................................................... 461
Displaying event messages ................................................................................................................. 461

Casa CMTS Software Configuration Guide

19

CASA CMTS
Enabling DSCP checking ...................................................................................................................... 461
Configuring event messages ............................................................................................................... 462
Configuring an IP address ................................................................................................................... 462
Configuring an FTP user ...................................................................................................................... 462
Configuring FTP user passwords ......................................................................................................... 463
Configuring the T0 timer..................................................................................................................... 463
Configuring the T1 timer..................................................................................................................... 463
Configuring network layer signaling (NLS) ......................................................................................... 464
Configuring maximum normal calls .................................................................................................... 464
Configuring maximum emergency calls.............................................................................................. 465
Configuring inactive call aging (Rel. 6.1 and later) ............................................................................. 465
Enabling PacketCable admission control preempt voice priority........................................................ 466
Enabling PacketCable Multimedia (PCMM)........................................................................................ 466
Enabling Packetcable Multimedia version setup ................................................................................ 466
Displaying Packetcable Multimedia specifications ............................................................................. 467
Setting the cable service flow timeout................................................................................................ 468
Assigning dynamic service flows to downstream channels ................................................................ 468
Displaying the PCMM policy server .................................................................................................... 469
Displaying PCMM multicast................................................................................................................ 469
Displaying the PacketCable configuration .......................................................................................... 469
Specifying a timeout for the RKS server .............................................................................................. 470
Specifying a retry count for the RKS server ......................................................................................... 470
Specifying batch file send mode ......................................................................................................... 471
Specifying the batch file sending time interval ................................................................................... 471
Specifying the maximum size of the event message batch file ........................................................... 472
Specifying the maximum messages in the batch file .......................................................................... 472
Specifying the RKS server media alive time ........................................................................................ 473
Specifying the RKS server maximum gates ......................................................................................... 473
Displaying RKS server information...................................................................................................... 473
Displaying live gate summary information ......................................................................................... 474
Displaying upstream or downstream gate information ..................................................................... 474
Displaying the total gate number ....................................................................................................... 474
Displaying COPS server information ................................................................................................... 475
CONFIGURING DSG ..................................................................................................................................... 475
Creating a new DSG tunnel ................................................................................................................. 475

Casa CMTS Software Configuration Guide

20

CASA CMTS
Creating a DSG tunnel-group .............................................................................................................. 476
Associating a DSG tunnel with a tunnel-group ................................................................................... 476
Displaying DSG tunnel groups ............................................................................................................ 477
Ending a DSG tunnel-group configuration session ............................................................................. 477
Assigning a destination MAC address to a DSG tunnel....................................................................... 478
Assigning a client list to a DSG tunnel ................................................................................................ 478
Assigning a service-class to a DSG tunnel ........................................................................................... 479
Assigning a classifier to a DSG tunnel ................................................................................................. 480
Displaying the DSG tunnel configuration (Release 5.4) ...................................................................... 481
Displaying the cable DSG tunnel configuration (Release 5.4) ............................................................. 481
Associating a downstream channel with a DSG tunnel-group ........................................................... 482
Displaying the downstream DSG configuration (Release 5.4) ............................................................ 482
Displaying DSG channel and tunnel group information...................................................................... 483
Setting a DSG timer to a downstream channel................................................................................... 483
Assigning a DSG vendor-parameter ID to a downstream channel ..................................................... 484
Assigning a DSG channel-list to a downstream channel ..................................................................... 484
Assigning DSG DCD ENABLE to a downstream channel ...................................................................... 485
Setting a DSG time interval on a downstream channel ...................................................................... 485
Displaying the DSG downstream-table settings ................................................................................. 486
Configuring a DSG client list ............................................................................................................... 487
Displaying DSG client lists ................................................................................................................... 487
Configuring DSG vendor parameters .................................................................................................. 488
Displaying DSG vendor parameters .................................................................................................... 488
Configuring a DSG channel list ........................................................................................................... 489
Displaying a DSG channel list.............................................................................................................. 489
Configuring DSG timers ...................................................................................................................... 489
Displaying DSG timers......................................................................................................................... 490
Configuring DSG unicast ..................................................................................................................... 490
Displaying DSG statistics..................................................................................................................... 491
Displaying the DSG running configuration ......................................................................................... 491
Using the DSG feature ........................................................................................................................ 491
Verify DSG DCD message and DSG data forwarding .......................................................................... 493
CONFIGURING DOCSIS BPI/BPI+ ................................................................................................................. 494
Configuring shared secrets to protect the modem configuration file ................................................. 494
Adding the privacy certificate (DOCSIS 3.0 only) ................................................................................ 496

Casa CMTS Software Configuration Guide

21

CASA CMTS
Displaying the privacy certificate configuration (DOCSIS 3.0 only) .................................................... 498
Enforcing BPI and BPI+ ....................................................................................................................... 498
Changing the security association descriptor TLV length ................................................................... 499
Setting the privacy hotlist (DOCSIS 3.0 only) ...................................................................................... 499
Configuring an encryption algorithm.................................................................................................. 501
Managing revocation certificates ....................................................................................................... 501
Configuring the source address verification rule ................................................................................ 504
Enabling SAV authorization ................................................................................................................ 504
Displaying the SAV configuration ....................................................................................................... 504
Enabling configuration file learning ................................................................................................... 505
Configuring TFTP proxies .................................................................................................................... 505
Displaying config file learning status .................................................................................................. 506
Displaying the TFTP option setting ..................................................................................................... 506
Configuring the EAE exclusion list ....................................................................................................... 506
Adding cable modems to the EAE exclusion list .................................................................................. 506
Displaying the EAE exclusion list ......................................................................................................... 507
SOURCE ADDRESS VERIFICATION (SAV) ........................................................................................................... 507
SPECTRUM MANAGEMENT............................................................................................................................. 509
CSM algorithm .................................................................................................................................... 510
Creating spectrum rules...................................................................................................................... 510
Exiting spectrum rule mode ................................................................................................................ 510
Setting a frequency band .................................................................................................................... 511
Setting a discrete frequency ............................................................................................................... 512
Setting the hopping period ................................................................................................................. 513
Setting the hopping priority ................................................................................................................ 513
Setting the channel-width adjustment range ..................................................................................... 514
Specifying a modulation profile SNR................................................................................................... 514
Specifying a modulation profile SNR threshold .................................................................................. 515
Specifying the hop-back threshold...................................................................................................... 516
Default SNR threshold for different modulations ............................................................................... 517
Setting the FEC threshold.................................................................................................................... 517
Assigning a spectrum rule to an upstream interface .......................................................................... 518
Assigning modulation profiles to an upstream interface.................................................................... 519
Specifying multiple secondary profiles to an upstream interface (Release 5.4 and later) ................. 520
Setting the monitoring period ............................................................................................................ 521

Casa CMTS Software Configuration Guide

22

CASA CMTS
Displaying hopping history ................................................................................................................. 521
Displaying the spectrum map ............................................................................................................. 522
Displaying the spectrum noise level.................................................................................................... 523
Enabling CM hopping ......................................................................................................................... 524
Displaying CM hopping history ........................................................................................................... 524
Considerations when using CSM ......................................................................................................... 525
Frequency hop case study ................................................................................................................... 525
CSM configuration example................................................................................................................ 527
SPECTRUM MEASUREMENT (DOCSIS 3.0 ONLY) ............................................................................................... 527
Displaying spectrum measurement results......................................................................................... 528
Running spectrum analysis across the entire spectrum...................................................................... 530
CONFIGURING LOAD BALANCING ..................................................................................................................... 530
Enabling and disabling load balancing ............................................................................................... 533
Enabling load balancing across MAC domains ................................................................................... 534
General load balancing groups ........................................................................................................... 534
Load balancing basic rules .................................................................................................................. 537
Load balance execution rules.............................................................................................................. 538
Load balancing policies ....................................................................................................................... 544
Restricted load balance groups .......................................................................................................... 545
Exclusion lists ...................................................................................................................................... 550
Restricted cable modems.................................................................................................................... 551
CM frequency and channel relocation ................................................................................................ 554
Displaying load balancing information ............................................................................................... 562
Command ordering ............................................................................................................................. 563
Command default values .................................................................................................................... 564
Sample configuration.......................................................................................................................... 564
CONFIGURING CHANNEL BONDING OPERATIONS................................................................................................. 570
Service group configuration................................................................................................................ 570
DOCSIS-MAC interface configuration ................................................................................................. 571
Channel bonding example .................................................................................................................. 572
CREATING STATIC CM BONDING GROUPS ......................................................................................................... 573
Adding a static downstream CM bonding group ................................................................................ 574
Adding a static upstream CM bonding group ..................................................................................... 574
Setting the provisioned attribute mask in an upstream/downstream bonding group ....................... 575
Adding an upstream channel to a bonding group .............................................................................. 576

Casa CMTS Software Configuration Guide

23

CASA CMTS
Adding a downstream channel to a bonding group ........................................................................... 576
Setting the DSID re-sequencing wait time in a downstream bonding group ...................................... 577
Setting the DSID re-sequencing warning threshold in a downstream bonding group ........................ 577
QOS SUPPORT ............................................................................................................................................ 578
QoS support in DQM modules ............................................................................................................ 578
QoS support in DCU modules .............................................................................................................. 578
QoS support in switch fabric and Gigabit Ethernet interfaces ............................................................ 579
CONFIGURING QOS ..................................................................................................................................... 579
Configuring the service class (DOCSIS 1.1).......................................................................................... 580
Showing the service class.................................................................................................................... 580
QoS class and policy (C3200, C10200, C10G only) .............................................................................. 581
CONFIGURING SNMP (ENHANCED FOR REL. 5.4 AND LATER) .............................................................................. 584
Configuring the SNMP engineID ......................................................................................................... 585
Enabling SNMP traps .......................................................................................................................... 585
Setting an SNMP traphost .................................................................................................................. 586
Configuring SNMP server contact and location strings ...................................................................... 586
Configuring the SNMP trap source IP address .................................................................................... 587
Enabling SNMP inform requests ......................................................................................................... 587
Setting the SNMP community ............................................................................................................. 588
Disabling default SNMP public and private community ..................................................................... 588
Configuring the SNMP access table .................................................................................................... 588
Deleting the SNMP access table ......................................................................................................... 589
Configuring the community table ....................................................................................................... 590
Deleting the SNMP community table ................................................................................................. 590
Configuring the notification table....................................................................................................... 590
Deleting the notification table ............................................................................................................ 591
Configuring the securityToGroup table............................................................................................... 591
Configuring the TargetAddress table .................................................................................................. 592
Deleting the TargetAddress table ....................................................................................................... 593
Configuring the TargetParameter table ............................................................................................. 593
Deleting the TargetParameter table................................................................................................... 594
Configure the ViewTreeFamily table................................................................................................... 594
Deleting the ViewTreeFamily table..................................................................................................... 595
Configuring the SNMP user table ....................................................................................................... 595
Deleting the SNMP user table ............................................................................................................. 596

Casa CMTS Software Configuration Guide

24

CASA CMTS
Displaying the SNMP configuration and statistics .............................................................................. 596
Monitoring the SNMP process at the CMTS ....................................................................................... 600
CONFIGURING IPDR .................................................................................................................................... 600
Displaying IPDR connections............................................................................................................... 601
Displaying IPDR sessions ..................................................................................................................... 601
Displaying IPDR statistics from the running configuration ................................................................. 602
Restarting and stopping the IPDR daemon......................................................................................... 602
Configuring IPDR collector mastership ............................................................................................... 603
Enabling IPDR service types ................................................................................................................ 603
Configuring the IPDR keepalive time interval ..................................................................................... 604
Configuring the IPDR acknowledge sequence interval ....................................................................... 604
Configuring the IPDR ACK interval ...................................................................................................... 604
Configuring the IPDR spectrum measurement interval ...................................................................... 605
Configuring the IPDR connection to be primary ................................................................................. 605
Configuring the IPDR loopback interface ............................................................................................ 605
CONFIGURING IPSEC .................................................................................................................................... 606
Enabling and disabling the IPsec service ............................................................................................ 606
Configuring the IPsec PreKey .............................................................................................................. 607
Displaying the IPsec PreKey ................................................................................................................ 607
Configuring IPsec Phase 1 ................................................................................................................... 607
Configuring IPsec Phase 2 ................................................................................................................... 608
Displaying IPsec information .............................................................................................................. 609
Deleting the IPsec configuration ......................................................................................................... 610
Adding an IPsec security policy ........................................................................................................... 610
Displaying the IPsec security policy database..................................................................................... 611
MANAGING CABLE MODEMS .......................................................................................................................... 612
Displaying cable modem status .......................................................................................................... 612
Displaying cable modem CPE devices ................................................................................................. 619
Displaying cable modems by state ..................................................................................................... 619
Cable modem summary information .................................................................................................. 620
Configuring the cable modem flap list ................................................................................................ 622
Showing the cable modem flap-list .................................................................................................... 624
Showing the cable modem summary ................................................................................................. 625
Displaying the cable modem summary (Release 5.4) ......................................................................... 626
Displaying the cable modem on downstream channels ..................................................................... 627

Casa CMTS Software Configuration Guide

25

CASA CMTS
Displaying cable modem physical information ................................................................................... 628
Showing the cable modem remote-query........................................................................................... 628
Configuring the remote-query polling interval ................................................................................... 629
Configuring the remote-query loopback interface ............................................................................. 630
Displaying the cable modem remote-query with a specified MAC address........................................ 630
Showing the cable modem remote-query with a specified IP address ............................................... 631
Setting the cable modem flap-list aging interval ................................................................................ 631
Accelerating cable modem registration.............................................................................................. 632
Registering DOCSIS 2.0 bonding modems........................................................................................... 632
Enabling the cable modem flap-list trap (Release 5.2) ....................................................................... 633
Enabling the cable modem flap-list trap (Release 5.4) ....................................................................... 633
Configuring a cable modem deny list ................................................................................................. 633
Enabling PacketCable admission control preempt voice priority........................................................ 634
Setting global QoS bandwidth over upstream and downstream interfaces ....................................... 634
Configuring QoS temporary upstream service flows .......................................................................... 635
Enabling cable DSX authorization ....................................................................................................... 635
Enabling Receive Channel Profile (RCP) fragment support ................................................................. 636
Controlling CMTS upstream power levels (Rel. 6.1 and later) ............................................................ 636
Adjusting modem upstream power levels (Rel. 6.1 and later) ............................................................ 637
Setting the SNR averaging interval ..................................................................................................... 637
Resetting cable modems and clearing cable modem counters .......................................................... 638
Clearing offline cable modems immediately ...................................................................................... 639
Clearing offline cable modems after aging ......................................................................................... 639
Displaying cable modem vendors ....................................................................................................... 640
Displaying vendor-specific information on cable modems ................................................................. 641
Adding and modifying cable modem vendor information .................................................................. 642
Deleting cable modem vendor information ........................................................................................ 642
Displaying vendor OUI information .................................................................................................... 642
Setting the default cable modem vendor ........................................................................................... 643
Displaying cable modem classifiers .................................................................................................... 644
Showing cable modem errors ............................................................................................................. 646
Displaying cable modem MAC information ........................................................................................ 647
Displaying cable modem spoof information ....................................................................................... 648
Displaying cable modem maintenance ranging information ............................................................. 648
Displaying denied cable modem ......................................................................................................... 649

Casa CMTS Software Configuration Guide

26

CASA CMTS
Displaying the cable modem MAC summary ...................................................................................... 649
Displaying the cable modem status event report ............................................................................... 650
Displaying cable modem quality-of-service (QOS) .............................................................................. 651
Displaying the cable modem docsis-mac summary ............................................................................ 652
Enabling/disabling cable modem host authorization ......................................................................... 653
Displaying the cable host authorization ............................................................................................. 653
SUBSCRIBER MANAGEMENT ........................................................................................................................... 653
CM controls (Rel. 6.0.3 and earlier) .................................................................................................... 653
Default settings .................................................................................................................................. 654
Filters .................................................................................................................................................. 654
Enabling subscriber management ...................................................................................................... 654
Setting the mode for a CM to learn the CPE IP address without DHCP (Rel. 6.0.3 and earlier) .......... 655
Setting maximum IPv4 CPEs behind a CM (Rel. 6.0.3 and earlier) ...................................................... 655
Setting maximum IPv6 CPEs behind a CM (Rel. 6.0.3 and earlier)...................................................... 656
Resetting IP addresses of all CPEs behind a CM (Rel. 6.0.3 and earlier) ............................................. 656
Using the subscriber management default settings ........................................................................... 656
Displaying the DOCSIS subscriber management defaults ................................................................... 658
Setting a filter rule .............................................................................................................................. 659
Removing all IP and TCP-UDP filters ................................................................................................... 659
Displaying IP filters ............................................................................................................................. 659
Displaying cable modem information (Rel. 6.0.3 and earlier) ............................................................ 660
Displaying the cable modem control table (Rel. 6.0.3 and earlier)..................................................... 660
Displaying CPE information (Rel. 6.0.3 and earlier) ............................................................................ 661
CONFIGURING MPEG COMPLIANT FEATURES ................................................................................................... 661
Setting the PAT insertion interval ....................................................................................................... 661
Setting the PMT insertion interval ...................................................................................................... 662
CONFIGURING DVB-COMPLIANT FEATURES ...................................................................................................... 662
Enabling SI table generation and insertion......................................................................................... 662
Setting the network ID ........................................................................................................................ 664
Setting the channel transport stream ID ............................................................................................ 665
CONFIGURING THE TIME OFFSET TABLE ........................................................................................................... 666
Setting the time zone .......................................................................................................................... 667
Setting the time offset ........................................................................................................................ 667
Setting daylight saving time (US only) ................................................................................................ 668
CONFIGURING THE DOCSIS EVENT NOTIFICATION POLICY .................................................................................... 668

Casa CMTS Software Configuration Guide

27

CASA CMTS
Enabling DOCSIS cable event reporting .............................................................................................. 669
Configuring event reporting by unique identifier ............................................................................... 669
Displaying the cable event identifiers ................................................................................................. 670
Configure the event reporting flags for DOCSIS event messages ....................................................... 670
Displaying the current priority and flags for cable event logging....................................................... 672
Enabling logging of DOCSIS event messages to a SYSLOG server ....................................................... 672
Configuring the TRAP/INFORM and SYSLOG throttling and limiting attribute ................................... 673
Specifying the throttle interval ........................................................................................................... 673
Specifying the throttle threshold ........................................................................................................ 674
USING THE LOGGING COMMANDS ................................................................................................................... 674
Configuring logging targets and levels ............................................................................................... 675
Excluding user messages from the log file by severity level ............................................................... 676
Displaying the current logging settings .............................................................................................. 678

Casa CMTS Software Configuration Guide

28

CASA CMTS

Preface
Purpose of the guide
This guide provides software configuration instructions for Releases 5 and 6 of the Casa CMTS
series: C1G, C1N, C2200, C3200, C10200, and C10G. Although these three platforms have
different hardware features, they share the same set of software features and commands. See
the Release Notes provided with the Casa software for any operational limitations with the
features covered in this guide.
For the descriptions of the hardware features and installation of different platforms, please refer to
the documents:
C2200 CMTS Hardware Installation Guide
C3200 CMTS Hardware Installation Guide
C10200 CMTS Hardware Installation Guide
C10G CMTS Hardware Installation Guide
C1G CMTS Hardware Installation Guide
C1N 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:
DOCSIS protocols, including MPEG-2
IETF protocols, including TCP/IP, RIP, OSPF, BGP, unicast and multicast routing
RF cable plants

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

Casa CMTS Software Configuration Guide

29

CASA CMTS
- Monitor line card
- Monitor gige
- 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.

Casa CMTS Software Configuration Guide

30

CASA CMTS
-Added more VLAN commands.
-Added bootstrap router support.
-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

Casa CMTS Software Configuration Guide

31

CASA CMTS
modem when background remote query feature is turned on
Added module installed/removed trap for 3K/10K 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.

Casa CMTS Software Configuration Guide

32

CASA CMTS
Added new commands: upstream map size and channel utilization
interval.
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

June 1, 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.
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.
Corrected gige command.
Corrected Table numbering and references.
Added command: debug service group.

Casa CMTS Software Configuration Guide

33

CASA CMTS
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.
Release 6.0.3 availability update. See the Release Notes for
information.
Added missed 5.4.21 command; software-health-check snmpd

July 15, 2011


September 7, 2011
November 14, 2011
December 6, 2011
January 4, 2012
February 9, 2012
March 1, 2012
April 18, 2012
May 22, 2012
September 17, 2012
October 4, 2012
November 20, 2012
December 20, 2012
February 7, 2012

Release 6.1.1 availability update. See the Release Notes for


information.
Release 6.1.2 availability update.
Release 1G.1 software noted on front cover for Casa C1G CMTS
systems. See the Release Notes for information.

Final updates for Release 6.1.2.


Release 6.1.3 update.
Added the following commands:
[no] cable partial-service dbc
[no] cable ecn 770
[no] cable sa-des-tlvlen-2

Casa CMTS Software Configuration Guide

34

CASA CMTS

Contents
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


Casa CMTS from the Command
Line Interface

Describes how to use CLI (Command Line Interface) to


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

Emphasized terminology.

[]

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.

Casa CMTS Software Configuration Guide

35

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 following four platforms, C2200, C3200, C10200, and the C10G.

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.

Casa CMTS Software Configuration Guide

36

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

Casa CMTS Software Configuration Guide

37

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
Casa CMTS Software Configuration Guide

38

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.

Casa CMTS Software Configuration Guide

39

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:

Casa CMTS Software Configuration Guide

40

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_slot>]
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

Casa CMTS Software Configuration Guide

41

CASA CMTS

Example:
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

Rebooting of a failed card that is not redundancy-protected


In the event of line card failure, you can elect whether to reboot the failed line card or to leave the
line card in the failed state if the card is not on the redundancy-protected list. In a situation where
a line card replacement is necessary, then you can elect not to reboot the card.
Example:
To reboot a failed line card that is not redundancy-protected:
CASA-CMTS(config)#

ha redundancy reboot

Example:
To prevent the CMTS from rebooting a failed line card, use the no form of the command:
CASA-CMTS(config)#

no ha redundancy reboot

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 Software Configuration Guide

42

CASA CMTS

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:
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
Casa CMTS Software Configuration Guide

43

CASA CMTS

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#
CASA-C10G#
CASA-C10G#
CASA-C10G#

show
show
show
show

envm
envm
envm
envm

[fan | power | temperature]


fan [left [0-1]| middle [0-1] | right [0-1]]
temperature [module <number> | QAM | SMM | UPS]
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
LEFT**
MIDDLE**
RIGHT**
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

Temperature
22C/ 71F
23C/ 73F
23C/ 73F

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

:
:
:
:
:
:
:
:
:

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

Type
QAM

Casa CMTS Software Configuration Guide

Present
Good
Present
Good
Present
Good
Present
Good
80 F/27 C

44

CASA CMTS

5
6
7
8
9
10
13

78F/
89F/
89F/
102F/
105F/
96F/
71F/

26C
32C
32C
39C
41C
36C
22C

Normal
Normal
Normal
Normal
Normal
Normal
Normal

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 999 MHZ 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 A separation
at 8 MHz), channels 0, 2 and 3 will be correctly separated by 8 MHz 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 (0 to 3 and 4 to 7) are contiguous across the
frequency spectrum using Annex A separation at 8 MHz in the range 547 MHz to 603 MHz.
interface qam 1/4
no spectral inversion on
annex A
modulation 256qam
interleave 12
power 450
channel 0 frequency 547000000
no channel 0 shutdown
channel 1 frequency 555000000
no channel 1 shutdown
channel 2 frequency 563000000
no channel 2 shutdown
channel 3 frequency 571000000
no channel 3 shutdown
channel 4 frequency 579000000
no channel 4 shutdown
channel 5 frequency 587000000
no channel 5 shutdown
channel 6 frequency 595000000
no channel 6 shutdown
channel 7 frequency 603000000
no channel 7 shutdown
no shutdown

Casa CMTS Software Configuration Guide

45

CASA CMTS

In the following example, the channel command is used to update the channel 0 frequency to
470 MHz. After updating the channel 0 frequency to 470 MHz, channels 0 to 3 have been revised
based on the 470 MHz frequency and the 8 MHz separation.
C10G-195(config-if-qam 1/4)#channel 0 frequency 470000000
C10G-195(config-if-qam 1/4)#show interface qam 1/4
interface qam 1/4
no spectral inversion on
annex A
modulation 256qam
interleave 12
power 450
channel 0 frequency 470000000
no channel 0 shutdown
channel 1 frequency 478000000
no channel 1 shutdown
channel 2 frequency 486000000
no channel 2 shutdown
channel 3 frequency 494000000
no channel 3 shutdown
channel 4 frequency 579000000
no channel 4 shutdown
channel 5 frequency 587000000
no channel 5 shutdown
channel 6 frequency 595000000
no channel 6 shutdown
channel 7 frequency 603000000
no channel 7 shutdown
no shutdown

!
C10G-195(config-if-qam 1/4)#

In the following example, the two 4-channel banks are non-contiguous across the frequency
spectrum due to a frequency change at channel 7. The range 470 MHz to 494 MHz is applied to
channels 0 to 3, and 585 MHz to 609 MHz is applied to channels 4 to 7. Each 4-channel bank still
maintains 8 MHz frequency separation.
C10G-195(config-if-qam 1/4)#channel 7 frequency 609000000
C10G-195(config-if-qam 1/4)#show interface qam 1/4
interface qam 1/4
no spectral inversion on
annex A
modulation 256qam
interleave 12
power 450
channel 0 frequency 470000000
no channel 0 shutdown
channel 1 frequency 478000000
no channel 1 shutdown
channel 2 frequency 486000000
no channel 2 shutdown
channel 3 frequency 494000000
no channel 3 shutdown
channel 4 frequency 585000000
no channel 4 shutdown
channel 5 frequency 593000000
no channel 5 shutdown

Casa CMTS Software Configuration Guide

46

CASA CMTS

channel 6 frequency 601000000


no channel 6 shutdown
channel 7 frequency 609000000
no 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.

C1G/C1N features and configuration differences with larger


platforms
Refer to the Casa Systems C1G/C1N CMTS Release Notes for information on the supported
software features, capacities, product limitations, and configuration/provisioning differences.
Not all features covered in this guide are supported on the C1G platform.

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.
Casa CMTS Software Configuration Guide

47

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
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.

Command history
Display error
messages
Display commands
and arguments

Shortcuts using the


alias command (Rel.
5.4 and later).

Example
copy run start
Instead of:
copy running-config
startup-config

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.
Casa CMTS Software Configuration Guide

48

CASA CMTS

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 connectivity. 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


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#

Casa CMTS Software Configuration Guide

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.

49

CASA CMTS

Viewing the loaded software version


Use the show version 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

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

Casa CMTS Software Configuration Guide

Display all the default values


of system software
configurations and settings.
50

CASA CMTS

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#
To exit the current configuration mode context, use the keyboard CTRL-Z key sequence. This
functionality has the same result as the CLI end command.

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.
Casa CMTS Software Configuration Guide

51

CASA CMTS

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.

Example:
CASA-CMTS(config)# console-password 2b/~2b
CASA-CMTS(config)# console-password encrypted
2b/~2b

Setting the console timout


The console timeout command sets the period of elapsed time in minutes before a console
session automatically times out due to no session activity.
To configure the console timeout period:
Step
1

Command (config)

Purpose

[no] console timeout <minutes>

Configure the
elapsed time in
minutes before a
console session
times out due to
no activity. .

Where:
<minutes>

Specifies the number of minutes in the


range 1 to 1440.

Example:
CASA-CMTS(config)# console timeout 10
CASA-CMTS(config)#

Casa CMTS Software Configuration Guide

52

CASA CMTS

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-CMTS#copy running-config startup-config
Note: This command operates at the top level of the CLI while in
configuration mode.

Refer to the Managing Configurations section of this guide for additional information on saving,
copying, and restoring CMTS configurations.

Casa CMTS Software Configuration Guide

53

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 eth 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

Casa CMTS Software Configuration Guide

Reboot the system so that


the default configuration is
applied.

54

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
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 shutdown
power 580
interface qam 0/1
no shutdown
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 shutdown
power 580
interface qam 0/2
no shutdown
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 shutdown
power 580
interface qam 0/3
no shutdown
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 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
Casa CMTS Software Configuration Guide

55

CASA CMTS

interface upstream 1/0


no shutdown
no logical-channel 0
interface upstream 1/1
no shutdown
no logical-channel 0
interface upstream 1/2
no shutdown
no logical-channel 0
interface upstream 1/3
no shutdown
no logical-channel 0
interface upstream 1/4
no shutdown
no logical-channel 0
interface upstream 1/5
no shutdown
no logical-channel 0
interface upstream 1/6
no shutdown
no logical-channel 0
interface upstream 1/7
no shutdown
no logical-channel 0

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

Casa CMTS Software Configuration Guide

56

CASA CMTS

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
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 shutdown
power 580
interface qam 0/1
no shutdown
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 shutdown
power 580
interface qam 0/2
no shutdown
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 shutdown
power 580
interface qam 0/3
no shutdown
no channel 0 shutdown
no channel 1 shutdown
no channel 2 shutdown
no channel 3 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

Casa CMTS Software Configuration Guide

57

CASA CMTS

interface ip-bundle 1
ip address 192.168.6.1 255.255.255.0
ip address 122.8.74.1 255.255.254.0 secondary
cable helper-address 192.168.3.7
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
upstream 1/6.0
upstream 1/7.0
interface docsis-mac 1
no shutdown
ip bundle 1
downstream 1 interface qam 0/0/0
downstream 2 interface qam 0/0/1
downstream 3 interface qam 0/0/2
downstream 4 interface qam 0/0/3
downstream 5 interface qam 0/1/0
downstream 6 interface qam 0/1/1
downstream 7 interface qam 0/1/2
downstream 8 interface qam 0/1/3
upstream 1 interface upstream 1/0.0
upstream 2 interface upstream 1/1.0
upstream 3 interface upstream 1/2.0
upstream 4 interface upstream 1/3.0
upstream 5 interface upstream 1/4.0
upstream 6 interface upstream 1/5.0
upstream 7 interface upstream 1/6.0
upstream 8 interface upstream 1/7.0
channel-utilization-interval 10
interface upstream 1/0
no shutdown
no logical-channel 0 shutdown
interface upstream 1/1
no shutdown
no logical-channel 0 shutdown
interface upstream 1/2
no shutdown
no logical-channel 0 shutdown
Casa CMTS Software Configuration Guide

58

CASA CMTS

interface upstream 1/3


no shutdown
no logical-channel 0 shutdown
interface upstream 1/4
no shutdown
no logical-channel 0 shutdown
interface upstream 1/5
no shutdown
no logical-channel 0 shutdown
interface upstream 1/6
no shutdown
no logical-channel 0 shutdown
interface upstream 1/7
no shutdown
no logical-channel 0 shutdown

Casa CMTS Software Configuration Guide

59

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
DHCP and DHCP leasequery
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
Spectrum Management
Load balancing
Casa CMTS Software Configuration Guide

60

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
Casa CMTS Software Configuration Guide

61

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

Casa CMTS Software Configuration Guide

62

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#
Casa CMTS Software Configuration Guide

63

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#

Casa CMTS Software Configuration Guide

64

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


This section covers commands for the following operations:
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]

Casa CMTS Software Configuration Guide

Purpose
Save the current
running-configuration
settings to a storage
location for the
startup-configuration
settings.
65

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


startup-configuration
settings to the
running-configuration
settings.

Casa CMTS Software Configuration Guide

66

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

Casa CMTS Software Configuration Guide

67

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 a file 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>

Specifies the FTP user login ID.

<host-ipaddress>

Specifies the IP address of the FTP


location.

<source-file>

Specifies the name of the file 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: *****
CASA-C10G(config)# copy ftp casa 192.168.8.192
startup-config module 6 nvram
CASA-C10G(config)# copy ftp casa 192.168.8.192
startup-config nvram

Casa CMTS Software Configuration Guide

68

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 source file


to a CMTS location
over TFTP.

copy tftp <host-ipaddress> <source_file> module


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

Specifies the IP address of the TFTP


location.

<source-file>

Specifies the name of the file to be


copied over TFTP 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

Note that the CMTS software supports the loopback interface IP as the source address when
issuing the copy tftp <ip-address> <filename> nvram command.

Casa CMTS Software Configuration Guide

69

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>

Specifies the FTP user login ID.

<host-ipaddress

Specifies the IP address of the FTP


target location.

<source-file>

Specifies the name of the file at the


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: *****
CASA-C10G(config)# copy fdsk2 startup-config
tftp 192.168.8.192 /tmp/startup-config
CASA-C10G(config)# copy fdsk2 startup-config
fdsk2 startup-config.backup

Casa CMTS Software Configuration Guide

70

CASA CMTS

Specifying an MD5 checksum file


The md5 checksum command specifies the name of the checksum file that is used to verify and
compare software image transfer integrity.
Step
1

Command

Purpose

md5 checksum <filename>

Specify the
name of the
MD5
checksum
file.

Where:
Specifies the name of the message digest 5 file.
The file must be present in the CMTS top-level
directory at command execution time.

<filename>

Example:
CASA-C10G> md5 checksum filename

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


running-configuration
settings.

Casa CMTS Software Configuration Guide

71

CASA CMTS

Displaying the system startup configuration


To display the system startup-configuration settings:
Step
1

Command

Purpose

show startup-config

Display the system


startup-configuration
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
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

Casa CMTS Software Configuration Guide

72

CASA CMTS

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>

Purpose
Remove or
delete a file from
the current
directory.

Example:
Remove a file from the directory using the remove command:
CASA-CMTS# remove startup-config
CASA-CMTS# del startup-config

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-file- name>

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.

Casa CMTS Software Configuration Guide

73

CASA CMTS

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 0 to 15, with 0 being the lowest and 15 the highest level. The users with privilege
level 15 are called super users.
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 for the diagnostic mode.
Table 2-1. Privilege levels and capabilities

Privilege
Level
0
1

Group
show commands only
Operator

Capability
Lowest level of operation

Casa CMTS Software Configuration Guide

74

CASA CMTS

2
3
4
5
6

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

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
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.

Assigning commands to user levels


CMTS commands may be assigned to specific user levels using the privilege command. For
example, users at privilege level 6 are able to configure and/or execute the commands that have
been configured at level 6.
Step
1

Command (config)

Purpose

privilege configure all level <number> <command_string>


privilege exec all level <number> <command_string>
privilege exec level <number> <command_string>

Assign CMTS
commands to
configured
user levels.

Where:
<number>

command string

Specifies the user level in the range 0 to 15,


where level 0 includes all show commands
and level 15 is a super user with all
privileges.
Specifies the command string as entered in
the Casa CLI. The string must be enclosed
in quotation marks.

Casa CMTS Software Configuration Guide

75

CASA CMTS

Examples:
Level 2 users can configure any parameters inside the interface docsismac configuration context.
CASA-CMTS(config)#privilege configure all level 2
interface docsis-mac
Level 0 users can execute all show and clear commands.
CASA-CMTS(config)# privilege exec all level 0 "clear"
Level 2 users can execute all show commands, clear cable modem
reset, and ping.
CASA-CMTS(config)# privilege exec level 2 "clear
cable modem reset"
CASA-CMTS(config)# privilege exec all level 2 "ping"

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
1

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

Check the
connected SSH
server (CMTS).

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

Displays hot key


information.

DSA key.

Casa CMTS Software Configuration Guide

76

CASA CMTS

rsa

RSA key.

fingerprint

CMTS ssh server public host key 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
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>]

Casa CMTS Software Configuration Guide

Enable the SSH


server.
77

CASA CMTS

Where:
<2000-65535>

Port number. The default port number is 22.

Example:
5

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

Disable the SSH


server.

Replace the
default keys.

DSA key.
RSA key.

Example:
CASA-CMTS# ssh gen-hostkey {dsa | rsa}

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.

Casa CMTS Software Configuration Guide

78

CASA CMTS

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#

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

Casa CMTS Software Configuration Guide

79

CASA CMTS

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#
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.

Casa CMTS Software Configuration Guide

80

CASA CMTS

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/1


Connection closed by foreign host.
[user@gollum]$

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

Casa CMTS Software Configuration Guide

81

CASA CMTS

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 sessions.
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


minutes in the range 1 to 1440 minutes.

To remove the
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.

Casa CMTS Software Configuration Guide

82

CASA CMTS

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
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
Broadcast Message from root@CASA-CMTS
(/dev/pts/0) at 11:40 ..
Casa CMTS Software Configuration Guide

83

CASA CMTS

System reboot reason: test


2

Cancel a
scheduled
or delayed
reboot.

system reboot cancel


Example:
CASA-CMTS#system reboot cancel
Broadcast Message from root@CASA-CMTS
(/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#

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.
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

Example:
CASA-CMTS(config)#system reboot confirm
Casa CMTS Software Configuration Guide

84

CASA CMTS

prior to reboot.
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#

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
Casa CMTS Software Configuration Guide

85

CASA CMTS

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)
Major rev 3, Minor rev 0
serial_no = UV30B89S0003
CFE version 2.1.5
Module 2 QAM Running (4 ports, 4
channels/port, 1 banks/port, docsis enabled)
Major rev 4, Minor rev 1
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

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.

Casa CMTS Software Configuration Guide

86

CASA CMTS

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
Timezone set to "America/New_York", offset from
UTC is -0400
To show all time zones:
CASA-CMTS(config)# show timezone list

Casa CMTS Software Configuration Guide

87

CASA CMTS

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

Casa CMTS Software Configuration Guide

88

CASA CMTS

Displaying NTP status


For the current NTP status at the CMTS, run the show ntp status command to display the NTP
server address, and NTP polling, delay, offset, and jitter statistics.
Step
1

Command (config)

Purpose

show ntp status

Display
current
NTP
status and
connection
statistics.

Example:
CASA-CMTS(config)# show ntp status

Example
C3000-230(config# show ntp status
remote

refid

st t when poll reach

delay

offset

jitter

==============================================================================
203.248.240.140 .INIT.

16 -

- 1024

0.000

0.000

0.000

Configuring system rate limiting (Rel. 6.0 and later)


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

Specifies rate limiting when the CMTS is


processing Layer 2 destination lookup failure
packets.

multicast

Specifies rate limiting when the CMTS is


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 Software Configuration Guide

89

CASA CMTS

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:
<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 use the route net command. To create
black hole routes for unwanted IPv4 traffic, use the ip route form of the command.
Step
1

Command (config)

Purpose

[no] route net <net-address> /<mask> gw <gw-ip>


[<metric_value>]

Add an entry to the


network routing
table.

[no] ip route <net-address>/mask null0 [<metric_value>]

Use the no form of


the command to
delete the route
entry.

Where:
<net-ip>

Destination network IP address in the


format a.b.c.d.

<mask>

IP network mask entered as 8, 16, 24, 32.

<gw- ip>

Gateway IP address in the format a.b.c.d.

Casa CMTS Software Configuration Guide

90

CASA CMTS

[<metric_value>]

Optional. Preferred routing distance


metric value in the range 1-255 where 1 is
most preferred. The default value is 1.

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:

Use the no form of the


command to delete the
entry from the host table.

<host-ip>

Destination host IP address in the format


a.b.c.d.

<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 use the route6 net command. To create
black hole routes for unwanted IPv6 traffic, use the ipv6 route form of the command.
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.

[no] ipv6 route <net-address>/mask null0 [<metric_value>]


Use the no form of
the command to
delete the IPv6
route.
Casa CMTS Software Configuration Guide

91

CASA CMTS

Where:
<ipv6_subnet_address
/prefix_length>

<ipv6_address>

Specifies the destination IPv6


network address with up to eight
16-bit bytes followed by the prefix
length between 0 and 64.
Specifies the gateway IPv6 network
address containing up to eight 16bit bytes in IPv6 standard address
notation.

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 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 0
eth0
default
192.168.0.1 0.0.0.0
UG 0 0 0 eth0

Displaying IP interface status


The show ip interface brief command displays the current status of all IP interfaces configured
on the CMTS by IP address, including Ethernet (eth), GigE and XGigE, ip-bundle, loopback, and
VLAN. The command has been introduced with Release 6.1.3.
Step
1

Command

Purpose

show ip interface brief

Display the current


status of all IP
interfaces

Example:
Casa CMTS Software Configuration Guide

92

CASA CMTS

C3000-230(config)#show ip interface brief

configured at the
CMTS.

See sample output below.

Example: show ip interface brief


C3000-230(config)#show ip interface brief
Interface
eth 0
loopback0
loopback0
gige 0
gige 0
gige 3
gige 3
vlan 34
vlan 34
vlan 35
vlan 36
vlan 37
vlan 2322
ipbundle1
ipbundle1.1
ipbundle1.1
ipbundle2
ipbundle2

IP-Address
192.168.8.230
88.88.88.230
128:238:238:238::230
192.168.3.230
3000::230
33.33.33.230
4000:238:238:238::230
34.34.34.230
3000:238:238:238::230
35.35.35.230
36.36.36.230
37.37.37.230
12.232.100.230
10.230.1.1
10.10.20.1
10.188.1.1
10.230.20.1
2000:230:1::1

Admin
Status
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up
up

Link
Status
up
up
up
up
up
down
down
down
down
down
down
down
down
up
up
up
down
down

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

Casa CMTS Software Configuration Guide

93

CASA CMTS

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
logged in from 192.168.3.32
[Tue Oct 27 23:46:39 2009]-AL-SYS-1: Module 0
(QAM), is up
[Tue Oct 27 23:46:15 2009]-AL-SYS-1: Module 1
(UPS), is up
[Tue Oct 27 23:45:57 2009]-AL-CLI-1: User root
logged in from 192.168.5.169
[Tue Oct 27 23:45:19 2009]-AL-SYS-1: Module 1
(UPS), in boot state
[Tue Oct 27 23:45:18 2009]-AL-SYS-1: Module 0
(QAM), in boot state

[Wed Oct 28 07:45:09 2009]-AL-CLI-1: Reboot


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.

Casa CMTS Software Configuration Guide

94

CASA CMTS

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

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

Casa CMTS Software Configuration Guide

95

CASA CMTS

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

State

Type

192.168.2.38 00:00:00 00c0.9f24.bfee dynamic


ARPA eth 0
192.168.2.39 00:19:03 000c.f1a6.36e8 dynamic
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

Casa CMTS Software Configuration Guide

96

CASA CMTS

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
the specified time
window.

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.

Use the no form of the


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

Casa CMTS Software Configuration Guide

97

CASA CMTS

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.*.*

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

Casa CMTS Software Configuration Guide

98

CASA CMTS

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

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

Casa CMTS Software Configuration Guide

99

CASA CMTS

To display the IPv6 route table:


Step Command
1

Purpose
Display the IPv6 route
table.

show route6
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 at the active SMM module:
Step
1

Command

Purpose

show cpuinfo

Display CPU usage at


the SMM module.

Example:
CASA-CMTS# show cpuinfo
To display CPU usage associated with a line card module:
Step
1

Command

Purpose

show cpuinfo module <identifier>

Display CPU usage


associated with a line
card module.

Where:
<identifier>

Specifies the module ID from which CPU


information is requested.

Example:
CASA-CMTS# show cpuinfo module 0
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
Casa CMTS Software Configuration Guide

100

CASA CMTS

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 across all modules:
Step
1

Command

Purpose

show cpuinfo all

Display CPU usage over


all modules.

Example:
See example below.

Example: show cpuinfo all


CASA-CMTS# show cpuinfo all
SMM:
cpu model
SiByte SB1 V0.3 FPU V0.3
BogoMIPS
265.42
microsecond timers yes
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
SiByte SB1 V0.3 FPU V0.3
BogoMIPS
532.48
microsecond timers yes
tlb_entries
64
5:28pm up 1:24, 0 users, load average: 0.02, 0.04, 0.00
44 processes: 43 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 2.2% user, 0.9% system, 0.0% nice, 97.0% idle
Mem: 245352K total, 192896K used, 52456K free, 500K buffers
Module 1:
cpu model
SiByte SB1 V0.3 FPU V0.3
BogoMIPS
265.42
microsecond timers yes
tlb_entries
64
5:28pm up 1:24, 0 users, load average: 0.21, 0.31, 0.28
45 processes: 44 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 4.5% user, 2.2% system, 0.0% nice, 93.3% idle
Mem: 245356K total, 140044K used, 105312K free, 504K buffers
To display CPU usage associated with CMTS processes:

Casa CMTS Software Configuration Guide

101

CASA CMTS

Step
1

Command

Purpose

show cpu-process

Display CPU process


usage across the CMTS.

Example:
CASA-CMTS# show cpu-process

Example: show cpu-process


C3000-230# show cpu-process
UID
root
root
root
root
root
root
root
root
root
root
root
root
root

PID
1
2
3
4
5
6
7
8
9
10
11
12
86

PPID
0
0
2
2
2
2
2
2
2
2
2
2
2

LWP
1
2
3
4
5
6
7
8
9
10
11
12
86

C NLWP STIME TTY


0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?
0
1 Nov15 ?

TIME
00:00:15
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:01

CMD
init [3]
[kthreadd]
[ksoftirqd/0]
[events/0]
[khelper]
[kblockd/0]
[kseriod]
[casa_help]
[pdflush]
[pdflush]
[kswapd0]
[aio/0]

To display CPU and memory statistics associated with CMTS processes:


Step
1

Command

Purpose

show cpu-memory process-list [<module_id> | all]

Display CPU and


memory statistics across
a specified module or
across all modules.

Example:
CASA-CMTS# show cpu-memory process-list all

Example: show cpu-memory process-list module 1


C3000-230#show cpu-memory process-list module 1
Module 1 CPU and Memory information:
COMMAND
PID USER
STIME
init
1 root
11:59
kthreadd
2 root
11:59
migration/0
3 root
11:59
ksoftirqd/0
4 root
11:59
migration/1
5 root
11:59
ksoftirqd/1
6 root
11:59
migration/2
7 root
11:59
Casa CMTS Software Configuration Guide

TIME %CPU %MEM


00:00:11 0.6 0.0
00:00:00 0.0 0.0
00:00:00 0.0 0.0
00:00:00 0.0 0.0
00:00:00 0.0 0.0
00:00:00 0.0 0.0
00:00:00 0.0 0.0
102

CASA CMTS

ksoftirqd/2
migration/3
ksoftirqd/3
migration/4
ksoftirqd/4
migration/5
ksoftirqd/5
migration/6
ksoftirqd/6
migration/7
ksoftirqd/7
migration/8
ksoftirqd/8
migration/9

8
9
10
11
12
13
14
15
16
17
18
19
20
21

root
root
root
root
root
root
root
root
root
root
root
root
root
root

11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59
11:59

00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00
00:00:00

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 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>

Display memory usage


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#

Casa CMTS Software Configuration Guide

103

CASA CMTS

To display memory usage of all modules:


Step
1

Command

Purpose

show meminfo all

Display memory usage


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#

Viewing module statistics


The show controller command allows you to display statistics across the installed CMTS
modules.
Step
1

Command

Purpose

show controller

Display statistics across


all modules.

Example:
CASA-CMTS(config)#show controller
See the example output below.

Example: show controller


C3000-230#show controller
Upstream module information:
Interface upstream 4/0.0/0 information:
IfIndex :
5000256
Admin status:
UP
Operating status:
UP
Frequency:
20000000 Hz
Channel Width:
3200000 Hz
Power Level:
0
Modulation profile
2
SNR:
28.2
Statistics:
Received 12 broadcasts, 6 multicasts, 340 unicasts
0 discards, 0 errors, 0 unknown protocol
Casa CMTS Software Configuration Guide

104

CASA CMTS

1247 Unerroreds, 1 Correcteds, 0 Uncorrectables


Req Mslots 337935795, Used Req Mslots 1089
Init Mtn Mslots 3805323, Used Init Mtn Mslots 0
Total Mslots 341756450, Ucast Granted Mslots 15268
Downstream module information:
Interface QAM 0/0
Admin Status: UP
Power level: 450
Channel 0:
IfIndex
: 3000000
Admin Status
: UP
Operating Status
: UP
Frequency
: 549000000
Channel Width
: 6000000
Modulation
: 256QAM
Annex:
: B
Statistics:
Broadcast packets
:
8064
Multicast packets
:
0
Unicast packets
:
59
UCD counts
:
5363
MAP counts
:
2180539
Interface docsis-mac 1 statistics
Ifindex:
2000001
Administrated status:
UP
Operation status:
UP
Mac address:
0017.1080.5e40
DSA Request
:
0/ups;
0/ds
DSA Response
:
0/ups;
0/ds
DSA Acknowledgements :
0/ups;
0/ds
DSA Success
:
0/ups;
0/ds
DSA Fail
:
0/ups;
0/ds
DSC Request
:
0/ups;
0/ds
DSC Response
:
0/ups;
0/ds
DSC Acknowledgements :
0/ups;
0/ds
DSC Success
:
0/ups;
0/ds
DSC Fail
:
0/ups;
0/ds
DSD Request
:
0/ups;
0/ds
DSD Response
:
0/ups;
0/ds
DSD Success
:
0/ups;
0/ds
DSD Fail
:
0/ups;
0/ds
DCC Request
:
0/ups;
0/ds
DCC Response
:
0/ups;
0/ds
DCC Acknowledgements :
0/ups;
0/ds
DCC Success
:
0/ups;
0/ds
DCC Fail
:
0/ups;
0/ds
DCC RSP Depart
:
0/ups;
0/ds
DCC RSP Arrive
:
0/ups;
0/ds
DBC Request
:
0/ups;
0/ds
Casa CMTS Software Configuration Guide

105

CASA CMTS

DBC Response
:
0/ups;
DBC Acknowledgements :
0/ups;
DBC Success
:
0/ups;
DBC Fail
:
0/ups;
DBC Partial Service :
0/ups;
Last clearing of interface stat: never
Interface gige 11 information:
IfIndex:
1000083
interface status
Administratively DOWN
link status
DOWN
auto-negotiation
Enabled
interface speed
1000000000
duplex status
Full
mac address
0017.1000.5e4d
Statistics:
IfInOctets
0
IfInUcastPkts
0
IfInNUcastPkts
0
IfInNUcastDiscards
0
IfInDiscards
0
IfInErrors
0
IfInUnknownProtos
0
IfOutOctets
0
IfOutUcastPkts
0
IfOutNUcastPkts
0
IfOutErrors
0
IfOutNUcastDiscards
0
IfOutDiscards
0
IpForwDatagrams
0
IpInReceives
0
IpInDiscards
0
v6IfInReceives
0
v6IfInDiscards
0
v6IfInErrors
0
v6IfOutForwDatagrams
0
v6IfOutDiscards
0
Last clearing of interface stat: never
SMM xgig interface information:
eth interface information:
Interface eth 0 information:
IfIndex:
1
interface status
UP
interface speed
100000000
mac address
0017.1000.5e40
Statistics:
IfInOctets
28077350
IfInUcastPkts
57667
IfInDiscards
0
IfInErrors
0
Casa CMTS Software Configuration Guide

0/ds
0/ds
0/ds
0/ds
0/ds

106

CASA CMTS

IfOutOctets
IfOutUcastPkts
IfOutErrors
IfOutDiscards
C3000-230#

2285988
49326
0
0

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

Casa CMTS Software Configuration Guide

107

CASA CMTS

Clearing interface statistics


To clear all statistics associated with a specified interface:
Step

Command (config)

Purpose

clear interface {docsis-mac | gige | qam | trunk | upstream


| xgige} <identifier> stat

Clear interface statistics.

Example:
CASA-CMTS(config)# clear interface gige 0 stat
CASA-CMTS(config)#

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

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).

Casa CMTS Software Configuration Guide

108

CASA CMTS

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.
The ping commands can be specified with multiple arguments when quotation marks are entered
at the beginning and end of the argument list.
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# 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
64 bytes from 192.168.8.113: icmp_seq=2 ttl=64
time=0.067 ms
64 bytes from 192.168.8.113: icmp_seq=3 ttl=64
time=0.082 ms
--- 192.168.8.113 ping
3 packets transmitted,
time 2000ms
rtt min/avg/max/mdev =
CASA-CMTS(conf-if-vlan

statistics --3 received, 0% packet loss,


0.067/0.083/0.102/0.017 ms
6/10)#

In the following example, a ping request is sent to an IPv6 address.


CASA-CMTS(conf-if-vlan 6/10)# ping6
2001:0db8:85a3:0000:0000:8a2e:0370:7334

Note that the ping6 command accepts a source interface parameter in the command input using
the I option. Example: ping6 "-I 2003:456::1 2001:730:3800:302::1"

Casa CMTS Software Configuration Guide

109

CASA CMTS

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.
64 bytes from 192.168.3.8: icmp_seq=1 ttl=64
time=0.357 ms
64 bytes from 192.168.3.8: icmp_seq=2 ttl=64
time=0.372 ms
64 bytes from 192.168.3.8: icmp_seq=3 ttl=64
time=0.361 ms

Using the traceroute commands


The traceroute and traceroute6 commands, previously only available in the CMTS diagnostic
mode, now operate 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.
The traceroute commands can be specified with multiple arguments when quotation marks are
entered at the beginning and end of the argument list.
Step
1

Command

Purpose

traceroute <ip_address>
traceroute6 <ipv6_address>

Trace the
number of IP
hops to a
destination IP
device.

traceroute help
traceroute6 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 ]"
traceroute6 "[ -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 ]"
Casa CMTS Software Configuration Guide

110

CASA CMTS

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
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

Casa CMTS Software Configuration Guide

111

CASA CMTS

-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
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
Casa CMTS Software Configuration Guide

112

CASA CMTS

max, 1500 byte packets


1 192.168.8.230 (192.168.8.230)
0.748 ms

1.624 ms

0.943 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

Configuring ICMP packet filtering


To set number of ICMP response packets to accept from the CM and CPE in a configured time
window (in seconds):
Step
1

Command (config)

Purpose

[no] cable icmp filter <number> <seconds>

Set the number of ICMP


packets to accept within
the specified time
window.

Where:
<number>

A value in the range 0 to 255 to specify the


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.

Casa CMTS Software Configuration Guide

Use the no form of the


command to revert to the
default settings.

113

CASA CMTS

<seconds>

The number of seconds in the range 1 to 5


to specify the time window for accepting
ICMP packets from the CM or CPE. The
default is 2 seconds.

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
window (in seconds):
Step
1

Command (config)

Purpose

[no] cable dhcp filter <number> <seconds>

Set the number of DHCP


packets to accept within
the specified time
window.

Where:
<number>

<seconds>

A value in the range 0 to 255 to specify the


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

Use the no form of the


command to revert to the
default settings.

The number of seconds in the range 1 to 5


to specify the time window for accepting
DHCP packets from the CM or CPE. The
default is 2 seconds.

Example:
CASA-CMTS(config)# cable dhcp filter 100 2

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)#
Casa CMTS Software Configuration Guide

114

CASA CMTS

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

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

Casa CMTS Software Configuration Guide

115

CASA CMTS

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
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
3/0.0
3/0.1
3/1.0
3/1.1
3/2.0
3/2.1
3/3.0
3/3.1
3/4.0
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

(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(549000000 Hz)
(555000000 Hz)
(561000000 Hz)
(567000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 Hz)
(20000000 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
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down
down

Casa CMTS Software Configuration Guide

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
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

116

CASA CMTS

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

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

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

show docsis channel utilization

Show the utilization on


upstream channels

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

Example: Display upstream channel utilization


Upstream
Operational Utilization Online Secondary Channel
Slot/Port.Channel
Status
Percentage Modems Modems
Description
------------------------------------------------------------------------------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

Casa CMTS Software Configuration Guide

117

CASA CMTS

4/0.0
4/0.1
4/1.0
4/1.1

(32600000
(34200000
(35800000
(37400000

Hz)
Hz)
Hz)
Hz)

up
up
up
up

0
0
0
0

0
0
0
0

0
0
0
0

Displaying downstream channel utilization


To see the utilization on all downstream channels:
Step
1

Command

Purpose

show docsis channel utilization

Show the utilization on


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
Percentage Modems Modems
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
0/2/3 ( 65000000 Hz)
down
0
0
0
0/3/0 (549000000 Hz)
up
0
0
6
0/3/1 (555000000 Hz)
up
4
20
0
0/3/2 (561000000 Hz)
up
0
0
6
0/3/3 (567000000 Hz)
up
0
0
6
1/0/0 (129000000 Hz)
down
0
0
0
1/0/1 (135000000 Hz)
up
0
0
0
1/0/2 (141000000 Hz)
up
0
0
0
1/0/3 (147000000 Hz)
up
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)
up
0
0
0
testing
1/3/1 (555000000 Hz)
up
0
0
0
1/3/2 (561000000 Hz)
up
0
0
0
1/3/3 (567000000 Hz)
up
0
0
0
casacasa

Casa CMTS Software Configuration Guide

118

CASA CMTS

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
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.

Casa CMTS Software Configuration Guide

119

CASA CMTS

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:
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

Casa CMTS Software Configuration Guide

120

CASA CMTS

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

interface <eth-port>

Enter fast Ethernet


interface mode.

Where:
<eth-port>

Specifies the ethernet port number.

Example:
CASA-CMTS(config)# interface eth 0
2

ip address dhcp
Example:
CASA-CMTS(config)# interface eth 0
CASA-CMTS(config-if-eth 0)# ip address dhcp

Obtain an IP address
from the DHCP server.

Configuring an IP access group on eth0 (C3200 and C10200 only)


To configure an IP access group on eth0:
Step

Command (config)

Purpose

interface <eth-port>

Enter fast Ethernet


interface mode.

Where:
<eth-port>

ethernet port

Example:
CASA-CMTS(config)# interface eth 0

Casa CMTS Software Configuration Guide

121

CASA CMTS

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
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 Software Configuration Guide

122

CASA CMTS

CASA-CMTS(config)# interface gige 1


CASA-CMTS(config-if-gige 1)#
2

Enable the GigE port

no shutdown
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>

Gigabit Ethernet port number in the


range 0 to 11 for C3200/C10200 and 0
to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
[no] auto negotiate
Where:
<port>

Enable or disable autonegotiation mode.

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

Casa CMTS Software Configuration Guide

123

CASA CMTS

Assigning or removing a Gigabit Ethernet port IP address


To assign an IP address to a Gigabit Ethernet port:
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

Gigabit Ethernet port number in the


range 0 to 11 for C3200/C10200 and 0
to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
[no] ip address <ip-address> <subnet-mask>
Where:
<ip-address>
<subnet-mask>

Assign an IP address to
a GigE port.

Text string for standard IP address in


the format a.b.c.d.
Text string for standard subnet mask
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)#

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

interface gige <port>

Enter GigE
interface mode.

Where:
<port>

Gigabit Ethernet port number in the range 0 to


11 for C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#

Casa CMTS Software Configuration Guide

124

CASA CMTS

ip access-group <string>
Where:
<string>

Assign an IP
access group to
a GigE port.

The access group name.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)# ip access-group
my_access_group
Delete the IP access group:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)# no ip access-group

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

interface gige <port>

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:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
[no] ipv6 address <ipv6-address>/<mask_len>
Where:
<ipv6-address>
<mask_len>

Text string for standard IPv6 address format :


xxxx:xxxx:xxxx:...:xxxx

Assign an IPv6
address to a
Gigabit Ethernet
port.

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
Casa CMTS Software Configuration Guide

125

CASA CMTS

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

interface gige <port>

Enter GigE
interface mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:

CASA-CMTS(config)# interface gige 1


CASA-CMTS(config-if-gige 1)#
[no] vlan <vlan-id>
Where:
<port>
<vlan-id>

GigE port number in the range 0 to 11.

Assign a GigE
port to a VLAN
or remove the
assignment.

Specifies the VLAN ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

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

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

interface gige <port>

Enter GigE Ethernet


interface mode.

Where:
<port>

Gigabit Ethernet port number in the range 0 to


11 for C3200/C10200 and 0 to 3 for C2200.

Casa CMTS Software Configuration Guide

126

CASA CMTS

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
[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
CASA-CMTS(config-if-gige 1)#
Disable IGMP client service on Gigabit Ethernet port 1:
CASA-CMTS(config-if-gige 1)# no ip igmp
CASA-CMTS(config-if-gige 1)#
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

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

interface gige <port>

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:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
mtu <1500-1800>

Configure the MTU size


of a GigE port interface

Where:
Casa CMTS Software Configuration Guide

127

CASA CMTS

<1500-1800>

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
no ip pim sparse-mode
interface gige 2
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 3
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 4
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
Casa CMTS Software Configuration Guide

128

CASA CMTS

interface gige 5
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 6
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 7
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 8
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 9
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 10
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode
interface gige 11
no ip igmp
auto negotiate
no shutdown
no ip pim sparse-mode

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.

Casa CMTS Software Configuration Guide

129

CASA CMTS

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
no ip pim sparse-mode
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
no ip pim sparse-mode

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:
<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).

Casa CMTS Software Configuration Guide

130

CASA CMTS

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
IfInTotalPkts
0 packets/second
IfOutOctets
0 bytes/second
IfOutUcastPkts
0 packets/second
IfOutNUcastPkts
0 packets/second
IfOutTotalPkts
0 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

Casa CMTS Software Configuration Guide

131

CASA CMTS

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>

Loopback interface number in the range 0 to 15.

Example:
CASA-CMTS(config)# interface loopback 12
CASA-CMTS(conf-if-lo 12)#

Configuring an IPv6 address on a loopback interface


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.
To specify an IPv6 address on a loopback interface:
Step
1

Command (config)

Purpose

interface loopback <if_id>

Enter interface
loopback mode.

Where:
<if_id>

Loopback interface number in the range 0 to 15.

Example:
CASA-CMTS(config)# interface loopback 4
CASA-CMTS(conf-if-lo 4)#
2

[no] ipv6 address <ipv6-address>/<mask_len>


Where:
<ipv6-address>
<mask_len>

Assign an IPv6
address to a
loopback interface.

Text string for standard IPv6 address in the


format xxxx:xxxx:xxxx:...:xxxx
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 GigE port 4:
Casa CMTS Software Configuration Guide

132

CASA CMTS

CASA-CMTS(config-if-lo 4)# ipv6 address


2000::1000:1/64
Remove the IPv6 address:
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

interface loopback <if_id>

Enter interface loopback


mode.

Where:
<if_id>

Loopback interface ID in the range 0 to 15.

Example:
CASA-CMTS(config)# interface loopback 0
CASA-CMTS(conf-if-lo 0)#
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(config)# interface loopback 0
CASA-CMTS(conf-if-lo 0)#ip address 60.1.2.3
255.255.0.0

Assigning an access group to a loopback interface


To assign an access group to a loopback interface:
Step
1

Command (config)

Purpose

interface loopback <if_id>

Enter interface loopback


mode.

Where:
<if_id>

Loopback interface ID in the range 0 to 15.

Example:
CASA-CMTS(config)# interface loopback 0
CASA-CMTS(conf-if-lo 0)#
[no] ip access-group <string>

Assign an access group


to a loopback interface.

Where:
Casa CMTS Software Configuration Guide

133

CASA CMTS

<string>

The access group name.

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>

Loopback interface ID in the range 0 to 15.

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).
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>

Loopback interface ID in the range 0 to 15.

Example:
CASA-CMTS(config)# ftp-tftp source-interface
loopback 0
Remove the configuration:
CASA-CMTS(config)# no ftp-tftp sourceinterface loopback 0

Casa CMTS Software Configuration Guide

134

CASA CMTS

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

Creating a trunk interface


The Casa CMTS supports up to 12 trunk interfaces:
Step
1

Command (config)

Purpose

[no] interface trunk <number>

Create or remove a trunk


interface.

Where:
<number>

Specifies the trunk interface number in the


range 1 to 12.

Example:
CASA-CMTS(config)# interface trunk 12
Casa CMTS Software Configuration Guide

135

CASA CMTS

CASA-CMTS(conf-if-trunk 12)#
To remove trunk interface 12:
CASA-CMTS(config)# no interface trunk 12

Configuring a trunk description


To configure a text description of a trunk interface, execute the description command under the
interface trunk configuration context.
Step
1

Command (config)

Purpose

[no] interface trunk <number>

Create a numbered
trunk interface and
enter the interface
trunk configuration
context.

Where:
<number>

Specifies the trunk interface number in the range


1 to 12.

Example:

CASA-CMTS(config)#interface trunk 12
C3000-230(conf-if-trunk 12)#
[no] description <string>
Where:
<string>

Specifies the text string to describe the trunk


interface. Up to 64 characters may be specified. If
the string has embedded blank spaces, then the
string must be within quotation marks ( ).

Example:
Enter a text description of trunk interface 12.
CASA-CMTS(config-if-trunk 12)# description This
is a text string within quotation marks.

Casa CMTS Software Configuration Guide

136

CASA CMTS

Assigning an IP address to a trunk interface


To set an IP address to the trunk Interface:
Step
1

Command (config)

Purpose

[no] interface trunk <number>

Create a
numbered
trunk interface
and enter the
interface trunk
configuration
context.

Where:
<number>

Specifies the trunk interface number in the range


1 to 12.

Example:
CASA-CMTS(config)# interface trunk 1
CASA-CMTS(conf-if-trunk 1)#
[no] ip address <address> <mask>
[no] ipv6 address <ipv6-address>/<mask_len>
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:


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 ::

Examples:
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

Casa CMTS Software Configuration Guide

137

CASA CMTS

Enabling/disabling a trunk interface


To enable or disable a trunk interface:
Step
1

Command (config)

Purpose

[no] interface trunk <number>

Create a numbered trunk


interface and enter the
interface trunk
configuration context.

Where:
<number>

Specifies the trunk interface number in the


range 1 to 12.

Example:
CASA-CMTS(config)# interface trunk 1
CASA-CMTS(conf-if-trunk 1#
[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

[no] interface trunk <number>

Create a numbered trunk


interface and enter the
interface trunk
configuration context.

Where:
<number>

Specifies the trunk interface number in the


range 1 to 12.

Example:
CASA-CMTS(config)# interface trunk 1
CASA-CMTS(conf-if-trunk) 1#
[no] gige <port>
Where:
<port>

Add or remove a GigE


port on a trunk interface.

GigE interface port number.

Example:
Casa CMTS Software Configuration Guide

138

CASA CMTS

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 1)# 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

[no] interface trunk <number>

Create a numbered trunk


interface and enter the
interface trunk
configuration context.

Where:
<number>

Specifies the trunk interface number in the


range 1 to 12.

Example:
CASA-CMTS(config)# interface trunk 1
CASA-CMTS(conf-if-trunk 1)#
2

Enable IGMP client


services on a trunk
interface.

[no] ip igmp
Example:
Enable IGMP client services on trunk interface 1:
CASA-CMTS(conf-if-trunk 1# ip igmp
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

[no] interface trunk <number>

Create a numbered trunk


interface and enter the
interface trunk
configuration context.

Where:
<number>

Specifies the trunk interface number in the


range 1 to 12.

Example:
CASA-CMTS(config)# interface trunk 1
Casa CMTS Software Configuration Guide

139

CASA CMTS

CASA-CMTS(conf-if-trunk 1)#
2

[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:
CASA-CMTS(config)# show interface trunk 1
!
interface trunk 1
gige 4 mode active
gige 5 mode active
gige 6 mode active
Casa CMTS Software Configuration Guide

140

CASA CMTS

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

[no] interface trunk <number>

Create a
numbered trunk
interface and enter
the interface trunk
configuration
context.

Where:
<number>

Specifies the trunk interface number in the


range 1 to 12.

Example:
CASA-CMTS(config)# interface trunk 1
CASA-CMTS(conf-if-trunk 1)#
show arp

Display ARP
entries associated
with the current
trunk interface.

Example:
CASA-CMTS(config)# interface trunk 10
CASA-CMTS(conf-if-trunk 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

Casa CMTS Software Configuration Guide

State

Type

dynamic ARPA
dynamic ARPA
dynamic ARPA
dynamic ARPA
static

ARPA

dynamic ARPA
static

ARPA

static

ARPA

static

ARPA

141

CASA CMTS

Configuring DNS
This section covers the Domain Name Server (DNS) configuration at the CMTS. In most cases,
because the GigE CMTS interfaces are in the private network, the source interface for DNS
responses over the public network will be a previously configured loopback interface.
To configure a DNS name server IP address at the CMTS, or to configure a loopback interface as
the source for DNS protocol traffic, use the nameserver command from the configuration mode.
Step
1

Command (config)

Purpose

[no] nameserver <ip_address>

Specify the
source IP
address for DNS
requests and
responses at the
CMTS.

[no] nameserver ipv6 <ip_address>


[no] nameserver source-interface loopb ack <number>
Where:
<ip_address>

Specifies the IPv4 address of the DNS


server in the format in 32-bit notation,
as in xxx.xxx.xxx.xxx.

ipv6 <ip_address>

Specifies the IPv6 address of the DNS


server in 128-bit notation as in
xxxx:xxxx:...:xxxx

<number>

Specifies the previously configured


loopback interface number in the range
0 to 15.

Example:
CASA-CMTS(config)#nameserver 192.168.9.0
CASA-CMTS(config)#nameserver source-interface
loopback 12

Configuring DHCP
This section covers the Dynamic Host Configuration Protocol (DHCP) configuration at the CMTS.
The CMTS uses DHCP to request IP addresses from a DHCP server for cable modem and CPE
devices that are registering with the CMTS. DHCP DISCOVER, OFFER, REQUEST, and
ACKNOWLEDGEMENT messages are exchanged between the CMTS DHCP client and the
DHCP server.
Once a cable modem has an assigned IP address, the CMTS uses TFTP to download the
modem configuration file from the TFTP server to the cable modem. Using the configuration file,
the modem configures itself with the correct parameters to operate with the CMTS.

Casa CMTS Software Configuration Guide

142

CASA CMTS

Using the DHCP insert function


The dhcp-insert command allows users to insert type values in DHCP packets using Option 82
(DHCP Relay Agent) to include information about a cable modem. The DHCP server attempts to
match the received information to determine if the device is a cable modem or a CPE device.
The supported DHCP-insert options are:
downstream-desc-type Inserts the type value for downstream port descriptor into the
received DHCP packets.
enterprise-num Inserts the Casa enterprise number into the received DHCP packets.
host-name-type Inserts the type value for the router host name into the received DHCP
packets.
upstream-desc-type Inserts the type value for upstream port descriptor into the received
DHCP packets.
To configure DHCP Option 82, perform the following steps:
Step
1

Command (config)

Purpose

dhcp-insert downstream-desc-type <value>


dhcp-insert enterprise-num <value>
dhcp-insert host-name-type <value>
dhcp-insert upstream-desc-type <value>

Specifies a type
value to be
inserted into
DHCP packet sent
to DHCP servers.

Where:
downstream-desc-type
<value>

Specifies a downstream port


descriptor type value in the range 1
to 255. The default value is 2.

dhcp-insert enterprisenum <value>

Specifies the Casa enterprise


number type value in the range 1 to
4294967295. The default setting is
20858.

host-name-type <value>

Specifies the host name type value


in the range 1 to 255. The default
setting is 1.

upstream-desc-type
<value>

Specifies an upstream port


descriptor type value in the range 1
to 255. The default value is 1.

Examples:
CASA-CMTS(config)# dhcp-insert downstream-desctype 2
CASA-CMTS(config)# dhcp-insert enterprise-num
20858#
CASA-CMTS(config)# dhcp-insert host-name-type 1
CASA-CMTS(config)# dhcp-insert upstream-desc-type
1
Casa CMTS Software Configuration Guide

143

CASA CMTS

Related DHCP-insert commands


To apply the dhcp-insert settings to a DOCSIS MAC interface, use the following commands
under the interface docsis-mac configuration context.
dhcp-insert downstream-description
dhcp-insert hostname
dhcp-insert upstream-description
Example
C3200-232(config)# interface docsis-mac 1
C3200-232(conf-if-mac 1)# dhcp-insert downstream-description
C3200-232(conf-if-mac 1)# dhcp-insert hostname
C3200-232(conf-if-mac 1)# dhcp-insert upstream-description
C3200-232(conf-if-mac 1)#

DHCP and DHCPv6 Leasequery


Use the dhcp leasequery and the dhcpv6 leasequery commands 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;
Casa CMTS Software Configuration Guide

144

CASA CMTS

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.
Display the
current lease
query setting.

Example:
CASA-CMTS(config)#dhcp leasequery enforce
2

show running-config | i leasequery


Example:
CASA-CMTS(config)#show running-config | i
leasequery
dhcp leasequery enforce

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

Casa CMTS Software Configuration Guide

145

CASA CMTS

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.

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 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:
Step
1

Command (config)
show lacp system-id

Purpose
Display the LACP
system ID.

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

Casa CMTS Software Configuration Guide

146

CASA CMTS

Setting LACP port priority


To configure LACP port priority value:
Step
1

Command (config)

Purpose

interface gige <port>

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:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
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


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

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

Casa CMTS Software Configuration Guide

147

CASA CMTS

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

interface gige <port>

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:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
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:
Step
1

Command (config)

Purpose

interface gige <port>

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:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
Casa CMTS Software Configuration Guide

148

CASA CMTS

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>

GigE port number in the range 0 to 11 for


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

Configuring and displaying LACP trunk interfaces


Step
1

Command (config)

Purpose

[no] interface trunk <num>

Create 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)#
[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
Casa CMTS Software Configuration Guide

149

CASA CMTS

!
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

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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
[no] ip router isis <string>
Where:
<string>

Configure or disable an
IPv4 IS-IS under a GigE
port.

IPv4 routing process tag.

Casa CMTS Software Configuration Guide

150

CASA CMTS

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:
Step
1

Command

Purpose

interface gige <port>

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:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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

interface gige <port>

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:
CASA-CMTS(config)# interface gige 0
Casa CMTS Software Configuration Guide

151

CASA CMTS

CASA-CMTS(config-if-gige 0)#
2

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.

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 circuit-type
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

interface gige <port>

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:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] isis network point-to-point
Example:
CASA-CMTS(config-if-gige 0)#isis network point-topoint

Configure a
point-to-point
link between two
IS-IS devices.

To disable:
CASA-CMTS(config-if-gige 0)#no isis network pointto-point

Casa CMTS Software Configuration Guide

152

CASA CMTS

Configuring the complete sequence number PDU (CSNP) interval


To configure the CSNP interval in seconds:
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE
interface mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] isis csnp-interval <num=0:65535> [(level-1|level-2)]
Where:
<num=0:65535>

Configure or
disable the
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 csnp-interval 40
level-1

Configuring the IS-IS Hello interval


To setup the ISIS Hello interval in seconds
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11


for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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.

Casa CMTS Software Configuration Guide

153

CASA CMTS

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

Configuring the IS-IS Multiplier for Hello holding time


To configure the ISIS Multiplier for the Hello holding time:
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE
interface mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] isis hello-multiplier <num=2:100> [(level-1 | level-2)]
Where:
<num=2:100>

Hello multiplier value.

level-1

Specify hello multiplier for level-1 IIHs

level-2

Specify hello multiplier for level-2 IIHs

Configure or
disable the ISIS
Multiplier for Hello
Holding time

Example:
CASA-CMTS(config-if-gige 0)#isis hello-multiplier 5
level-2
Disable the ISIS multiplier:
CASA-CMTS(config-if-gige 0)#no isis hellomultiplier

Casa CMTS Software Configuration Guide

154

CASA CMTS

Enabling padding on IS-IS Hello packets


To pad Hello packets:
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE
interface mode.

Where:
<port>

GigE port number in the range 0 to 11


for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] isis hello padding

Enable padding
on Hello packets.

Example:
CASA-CMTS(config-if-gige 0)#isis hello padding
CASA-CMTS(config-if-gige 0)#
Disable:
CASA-CMTS(config-if-gige 0)#no isis hello padding
CASA-CMTS(config-if-gige 0)#

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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11


for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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.

Casa CMTS Software Configuration Guide

155

CASA CMTS

level-1

Optional. Applies the specified


metric to Level-1 links.

level-2

Optional. Applies the specified


metric to Level-2 links.

Example:
CASA-CMTS(config-if-gige 0)#isis metric 40
CASA-CMTS(config-if-gige 0)#
To disable the default metric:
CASA-CMTS(config-if-gige 0)#no isis metric
CASA-CMTS(config-if-gige 0)#

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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] isis password <string> [level-1 | level-2]
Where:
<string>

Specifies the password string using up


to 255 characters.

level-1

Optional. Applies the specified


password to Level-1 Hello packets
only.

level-2

Optional. Applies the specified


password to Level-2 Hello packets
only.

Configure or disable
the IS-IS
authentication
password for a GigE
interface.

Example:
CASA-CMTS(config-if-gige 0)#isis password AAA
CASA-CMTS(config-if-gige 0)#
Disable the password:
Casa CMTS Software Configuration Guide

156

CASA CMTS

CASA-CMTS(config-if-gige 0)#no isis password AAA


CASA-CMTS(config-if-gige 0)#

Configuring the IS-IS priority


To setup IS-IS priority:
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE
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:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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

interface gige <port>

Enter GigE
Ethernet
interface mode.

Where:
<port>

Gigabit Ethernet port number. Valid values are 0 to 11


for C3200/C10200, 0 to 7 on the C10g, and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#

Casa CMTS Software Configuration Guide

157

CASA CMTS

[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.

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
Casa CMTS Software Configuration Guide

158

CASA CMTS

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>
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 parameters


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:
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
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]

Casa CMTS Software Configuration Guide

159

CASA CMTS

redistribute {bgp | connected | isis | static} {level-1 | level-2 | level-1-2}


metric <number> metric-type {internal | external} [route-map <name>
redistribute {bgp | connected | isis | static} {level-1 | level-2 | level-1-2}
metric <number> metric-type {internal | external} [route-map <name>
redistribute {bgp | connected | isis | static} {level-1 | level-2 | level-1-2}
route-map <name>
summary-prefix X:X::X:X/M
Where:
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

Optional. Instructs IS-IS to apply a previously-

Casa CMTS Software Configuration Guide

160

CASA CMTS

<name>

configured 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
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 Software Configuration Guide

161

CASA CMTS

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

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

Command (config-router)

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
CASA-CMTS(config-router-isis)#
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.
Casa CMTS Software Configuration Guide

162

CASA CMTS

Step
1

Command (config-router)

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
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
CASA-CMTS(config-router-isis)#
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

Command (config-router)

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
CASA-CMTS(config-router-isis)#
Disable the IS-IS authentication mode:
CASA-CMTS(config-router-isis)#no authentication
send-only

Casa CMTS Software Configuration Guide

163

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

Command (config-router)

Purpose

[no] default-information originate

Generate a
default route
within the IS-IS
routing domain.

Example:
CASA-CMTS(config-router-isis)# default-information
orginate
CASA-CMTS(config-router-isis)#
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

Command (config-router)

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
Casa CMTS Software Configuration Guide

164

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

Command (config-router)

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 local
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

Casa CMTS Software Configuration Guide

165

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

Command (config-router)

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-isis)# lsp-gen-interval
level-1 20
CASA-CMTS(config-router-isis)# lsp-gen-interval
level-2 10
Reset the LSP generation interval to the default setting:
CASA-CMTS(config-router-isis)#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

Command (config-router)

Purpose

[no] lsp-lifetime <seconds>

Configure the
maximum
time in

Casa CMTS Software Configuration Guide

166

CASA CMTS

Where:
<seconds>

Specifies the maximum number of seconds that an


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).

seconds for an
LSP to exist in
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-isis)#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

Command (config-router)

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-isis)# metric-style
transition
Remove the current metric-style setting:
CASA-CMTS(config-router-isis)#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:
Casa CMTS Software Configuration Guide

167

CASA CMTS

47 AFI
0004.0000.0000 area identifier
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

Command (config-router)

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

Command (config-router)

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-isis)#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.
Casa CMTS Software Configuration Guide

168

CASA CMTS

Step
1

Command (config-router)

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-isis)#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.

Casa CMTS Software Configuration Guide

169

CASA CMTS

static

Specifies IS-IS to advertise statically-configured


routes.

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 Level2 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.
Step
1

Command (config-router-isis)

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>
suppress

Specifies the temportary time in seconds to


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

Casa CMTS Software Configuration Guide

170

CASA CMTS

external

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:
CASA-CMTS(config-router-isis)# set-overload-bit
on-startup 10

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

Command (config-router-isis)

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:
<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
Casa CMTS Software Configuration Guide

171

CASA CMTS

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

Command (config-router-isis)

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 summaryaddress prefix setting to Level-2 areas


only.

level-1-2

Optional. Forwards the IPv4 summaryaddress prefix setting to both Level-1


and Level-2 areas.

Use the no form of


the command to
remove the current
setting.

Examples:
CASA-CMTS(config-router-isis)#
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>]
Casa CMTS Software Configuration Guide

172

CASA CMTS

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-2 link state database only.

level-1

Level-1 link state database only.

level-2

Level-2 link state database only.

slot

IS-IS database statistics per specified system slot


number.

verbose

Displays full IS-IS link state database information.


Optional system slot number may be specified.

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 Software Configuration Guide

173

CASA CMTS

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

Displays full IS-IS link state database information.


Optional system slot number may be specified.

l1

Specifies the level-1 link state database only.

l2

Specifies the level-2 link state database only.

level-1

Specifies the level-1 link state database only.

level-2

Specifies the level-2 link state database only.

slot
<number>

Specifies the IS-IS database statistics per specified


system slot number.

verbose

Displays full IS-IS link state database information.


Optional system slot number may be specified.

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

Casa CMTS Software Configuration Guide

174

CASA CMTS

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.

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 ID in the range 1 to


4094. On Casa C3200 CMTS systems,
the supported VLAN range is 1 to 4078.

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(config)#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
Casa CMTS Software Configuration Guide

175

CASA CMTS

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> ]

Displays 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:
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> ]

Shows 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:
Casa CMTS Software Configuration Guide

176

CASA CMTS

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
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)

Casa CMTS Software Configuration Guide

177

CASA CMTS

Enabling PIM-SM on a GigE or loopback interface


To enable PIM-SM on a GigE interface:
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#
[no] ip pim sparse-mode

Enable PIM-SM.

Example:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(conf-if-gige 1)# ip pim sparse-mode

Use the no form of the


command to disable
PIM-SM on a previouslyconfigured GigE
interface.

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:

Casa CMTS Software Configuration Guide

178

CASA CMTS

Step
1

Command (config)

Purpose

[no] ip pim rp-address <ip_address> [access-list <name> |


override]

Specify the static


RP address

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.

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
show ip pim rp [mapping]
show ip pim rp-hash <ip_address>
Where:
<ip_address>

Display the RP
groups and
mappings.

The IP address of the multicast group


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
Info source: 0.0.0.7, via bootstrap, priority 0,
holdtime 1
Uptime: 14677:11:17:52, expires:0
PIMv2 Hash Value (mask 192.168.3.232)

Casa CMTS Software Configuration Guide

179

CASA CMTS

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.

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>

Use the no
form of the
command to
delete the RP
candidate
assignment.

Example:
CASA-CMTS(config)# ip pim rp-candidate gige1 priority
5

Casa CMTS Software Configuration Guide

180

CASA CMTS

show ip pim rp [mapping]


show ip pim rp-hash <ip_address>
Where :
<ip_address>

Display the RP
groups and
mappings.

The IP address of the multicast group


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
Info source: 0.0.0.7, via bootstrap, priority 0,
holdtime 1
Uptime: 14677:11:17:52, expires:0
PIMv2 Hash Value (mask 192.168.3.232)

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>

The GigE or loopback interface number.


Optional: 0 to 32 is the IP hash mask among
the RP candidates. This value specifies the

Casa CMTS Software Configuration Guide

Use the no form of


the command to
delete the BSR
181

CASA CMTS

<priority>

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

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

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:
Step Command (config)
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.

Purpose
Specify the SPT
threshold.
Use the no form of
the command to
delete the configured
SPT threshold.

Example:
Casa CMTS Software Configuration Guide

182

CASA CMTS

CASA-CMTS(config)# ip pim spt-threshold 1500


CASA-CMTA(config)# ip pim spt-threshold infinity
2

show ip pim 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:
Step Command (config)
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

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
Casa CMTS Software Configuration Guide

183

CASA CMTS

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
show ip ospf database
show ip ospf interface
show ip ospf neighbor
show ip ospf route
show ip route

Casa CMTS Software Configuration Guide

184

CASA CMTS

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-ospf)#

Exiting OSPF configuration mode


To exit OSPF Configuration mode:
Step
1

Command (config)

Purpose

end

Exit OSPF configuration


mode.

Example:
CASA-CMTS(config-router-ospf)# 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.
Step Command (config)
Purpose
1

Enter OSPF
configuration mode.

router ospf
Example:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#

[no] area <id> authentication [message-digest]


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.

Enable or disable
OSPF area
authentication.

Example:
Enable authentication for areas 10 of OSPF routing process:
Casa CMTS Software Configuration Guide

185

CASA CMTS

CASA-CMTS(config-router-ospf)# area 10
authentication
CASA-CMTS(config-router-ospf)#
Disable area authentication:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
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-ospf)# area 192.168.3.2
default-cost 35
CASA-CMTS(config-router-ospf)#
Disable a cost:
CASA-CMTS(config-router-ospf)# no area 192.168.3.2
default-cost 35
CASA-CMTS(config-router-ospf)#

Casa CMTS Software Configuration Guide

186

CASA CMTS

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

Example:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] area <id> filter-list prefix {<list-name> in | out}

Enter OSPF
configuration
mode.

Where:
<id>

Configure or
disable the OSPF
area filter list.

Area identifier specified as either a decimal value (04294967295) 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 ospf
CASA-CMTS(config-router-ospf)# area 3 filter-list
prefix area_3 in

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
2

area <id> export-list <list-name>

Casa CMTS Software Configuration Guide

Configure the OSPF


area export list.

187

CASA CMTS

Where:
<id>

<list-name>

Area identifier. It can be specified as either


a decimal value (0-4294967295) or an
IP address (A.B.C.D).
name of an export list.

Example:
Filters prefixes that are sent from all other areas to area 3:
CASA-CMTS(config-router-ospf)# area 3 filterlist prefix area_3 in
Remove or cancel a list:
CASA-CMTS(config-router-ospf)# no area 3
filter-list 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
2

[no] area id import-list <list-name>


Where:
Id

<list-name>

Configure or remove the


OSPF area import list.

Area identifier specified as either a


decimal value (0-4294967295) or an
IP address (A.B.C.D).
Import list name.

Casa CMTS Software Configuration Guide

188

CASA CMTS

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] area <id> nssa [translate-always | translate-candidate |
translate-never] [no-summary]
Where:
<id>

Configure or
remove OSPF
Area NSSA

Area identifier specified as either a


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-ospf)# area 3 nssa
translate-always no-summary
Remove NSSA configuration:
CASA-CMTS(config-router-ospf)# no area 3 nssa
translate-always no-summary

Casa CMTS Software Configuration Guide

189

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[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-ospf)# area 3 range
192.168.2.3/24 cost 20
Disable:
CASA-CMTS(config-router-ospf)# no area 3 range
192.168.2.3/24 cost 20

Casa CMTS Software Configuration Guide

190

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
2

[no] area <id> shortcut {enable | disable | default}


Where:
<id>

Configure or disable the


OSPF area shortcut.

Area identifier specified as either a


decimal value (04294967295) or an
IP address (A.B.C.D).

enable

Enable shortcutting through the area.

disable

Disable shortcutting through the area.

default

Set default shortcutting behavior.

Example:
CASA-CMTS(config-router-ospf)# area 3 SC
enable
Disable:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#

Casa CMTS Software Configuration Guide

191

CASA CMTS

[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.

Example:
Enable stub in area 3:
CASA-CMTS(config-router-ospf)# area 3 stub
Disable:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[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>

Area identifier specified as either a


decimal value (0-4294967295) OR AN
IP address (A.B.C.D).

<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

Casa CMTS Software Configuration Guide

192

CASA CMTS

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.

retransmitinterval <num>

Optional. Time (in seconds) between link


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.

Casa CMTS Software Configuration Guide

193

CASA CMTS

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.

Example:
Establish a virtual link with MD5 authentication:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[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-ospf)# auto-cost
reference-bandwidth 20
Assign cost based only:
CASA-CMTS(config-router-ospf)# 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.
Casa CMTS Software Configuration Guide

194

CASA CMTS

Step
1

Command (config)

Purpose

router ospf

Enter OSPF
configuration mode.

Example:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
2

[no] compatible rfc1583


or
[no] ospf rfc1583compatibility

Enable or disable RFC


1583 compatibility.

Example:
CASA-CMTS(config-router-ospf)# compatible
rfc1583
Disable:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] default-information originate [always] [metric
<metric-value>] [metric-type <type-value>] [route-map
<map-name>]
Where:
always

Configure or disable
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

Casa CMTS Software Configuration Guide

195

CASA CMTS

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.

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-ospf)# defaultinformation 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
2

[no] default-metric <metric-value>


Where:
metric-value

Configure or disable
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-ospf)# default-metric 20

Casa CMTS Software Configuration Guide

196

CASA CMTS

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
distance { <dist0> | ospf {intra-area <dist1> | inter-area <dist2> |
external <dist3> } }
Where:
<dist0>

Configure the
OSPF
administrative
distance.

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-ospf)# distance ospf
external 200

Displaying the OSPF command list


To show the OSFP command list, follow the command provided below.
Step
1

Command (config)

Purpose

router ospf

Enter OSPF
configuration
mode.

Example:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#

Casa CMTS Software Configuration Guide

197

CASA CMTS

list
Example:
Set the external distance to 200:
CASA-C3000(config-router-ospf)# 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 <016777215>
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 (translatecandidate|translate-never|translate-always)
area (A.B.C.D|<0-4294967295>) nssa (translatecandidate|translate-never|translate-always) nosummary
area (A.B.C.D|<0-4294967295>) nssa no-summary
area (A.B.C.D|<0-4294967295>) range A.B.C.D/M
area (A.B.C.D|<0-4294967295>) range A.B.C.D/M
advertise
area (A.B.C.D|<0-4294967295>) range A.B.C.D/M
advertise cost <0-16777215>

Display the
OSFP
command list.

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[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

Casa CMTS Software Configuration Guide

198

CASA CMTS

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-ospf)# 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.

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] network <ip-address>/<mask_prefix> area <area-id>

Enter OSPF
configuration
mode.

Where:
<ip-address/mask>
<area-id>

Configure OSPF
routing on an IP
network.

Specifies the IP address and mask in the


format A.B.C.D/M.
Specifies 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.

Example:
Defines two OSPF areas: 1 and 2. Areas 1 and 2 mask specific
address ranges:
CASA-CMTS(config-router-ospf)# network
10.10.10.0/24 area 1
CASA-CMTS(config-router-ospf)# network
10.10.20.1/24 area 2

Casa CMTS Software Configuration Guide

199

CASA CMTS

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] ospf abr-type [cisco | ibm | shortcut | standard]
Where:
cisco

Configure the OSPF


ABR type.

Alternative ABR in Cisco implementation.

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)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[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)# ospf router-id
192.168.3.20

Casa CMTS Software Configuration Guide

200

CASA CMTS

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
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
A.B.C.D.

Example:
Configure OSPF passive interface ifname with address
10.10.10.3:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] distribute-list <list-name> out { bgp | connected | kernel | rip
| static }
Where:
<list-name>

in

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.
Applies the access list to incoming routing
updates.

Casa CMTS Software Configuration Guide

201

CASA CMTS

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-ospf)# 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
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 route redistribution


This command redistributes routes from other routing protocols over OSPF.
Step

Command (config)

Purpose

router ospf

Example:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
redistribute {bgp | connected | isis | rip | static}

Enter OSPF
configuration
mode.

redistribute bgp [metric | metric-type | route-map | tag]


redistribute bgp tag <number> [metric | metric-type | route-map]
redistribute rip [metric | metric-type | route-map | tag]
redistribute rip tag <number> [metric | metric-type | route-map]

Redistribute
learned routes
from other
protocols to
OSPF
neighbors.

redistribute isis [metric | metric-type | route-map | tag]


redistribute isis tag <number> [metric | metric-type | route-map]
redistribute connected [metric | metric-type | route-map | tag]
redistribute connected tag <number> [metric | metric-type | routemap]
redistribute static [metric | metric-type | route-map | tag]
redistribute static tag <number> [metric | metric-type | route-map]
Where:
Casa CMTS Software Configuration Guide

202

CASA CMTS

bgp

Applies the access list to BGP routes.

connected

Applies the access list to connected routes.

isis

Applies the access list to IS-IS routes.

rip

Applies the access list to RIP routes.

static

Applies the access list to statically-configured


routes.

tag

Optional. RIP route tag in the range 1 to


4294967295.

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 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
<map-name>

Optional. Routing process will generate the default


route if the route map is satisfied.

Example:
Configure OSPF to redistribute routes from static routes:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[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-ospf)# refresh timer 100
Casa CMTS Software Configuration Guide

203

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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] route-id <ip-address>
Where:
<ip-address>

Configure or disable the


OSPF route ID.

Router ID in IP address format.

Example:
CASA-CMTS(config-router-ospf)# 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:
CASA-CMTS(config)# router ospf
CASA-CMTS(config-router-ospf)#
[no] timers spf <delay-time> <hold-time>
Where:
<delay-time>

<hold-time>

Configure or disable the


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:

Casa CMTS Software Configuration Guide

204

CASA CMTS

CASA-CMTS(config-router-ospf)# 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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11


for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
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

Casa CMTS Software Configuration Guide

205

CASA CMTS

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.
Step
1

Command (config)

Purpose

interface gige <port>

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:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] ip ospf authentication-key <password>
Where:
<password>

Configure or disable IP
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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11


for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#

Casa CMTS Software Configuration Guide

206

CASA CMTS

[no] ip ospf cost <if-cost>


Where:
<if-cost>

Configure or disable the


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:
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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] ip ospf dead-interval <num>
Where:
<num>

Configure or disable
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

Casa CMTS Software Configuration Guide

207

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.

interface gige <port>


Where:
<port>

Purpose

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
Casa CMTS Software Configuration Guide

208

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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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)# interface gige 0
CASA-CMTS(config-if-gige 0)# ip ospf retransmitinterval 10

Casa CMTS Software Configuration Guide

209

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

interface gige <port>

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:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[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)
Casa CMTS Software Configuration Guide

210

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
Casa CMTS Software Configuration Guide

211

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.
Step

Command (config)

Purpose

show ip ospf route

Display the OSPF


routing table.

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.

Casa CMTS Software Configuration Guide

212

CASA CMTS

rip

Routing Information Protocol routes.

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
C>* 10.168.3.0/24 is directly connected, bcm1
C>* 10.168.66.0/24 is directly connected, bcm26
CASA-CMTS(config)#

Displaying IPv6 route information


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

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.

supernets-only

Supernets.

Example:
CASA-CMTS(config)# show ipv6 route

Casa CMTS Software Configuration Guide

213

CASA CMTS

Sample OSPF configurations


Example 1:
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.

CASA-CMTS(config)# router ospf


CASA-CMTS(config-router-ospf)#

CASA-CMTS(config-router-ospf)# redistribute
connected

Enter OSPF
configuration mode.
Configure OSPF
redistribute information.

CASA-CMTS(config-router-ospf)# 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.

CASA-CMTS(config)# router ospf


CASA-CMTS(config-router-ospf)#

CASA-CMTS(config-router-ospf)#network
192.168.3.0/24 area 0.0.0.0
CASA-CMTS(config-router-ospf)#network
10.237.1.0/24 area 0.0.0.0
CASA-CMTS(config-router-ospf)#network
10.237.2.0/24 area 0.0.0.0

Enter OSPF
configuration mode.
Configure the network.

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
Casa CMTS Software Configuration Guide

214

CASA CMTS

distribute-list
list
neighbor
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
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-rip)# 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.
Casa CMTS Software Configuration Guide

215

CASA CMTS

Step
1

Command (config)

Purpose

router rip

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
2

[no] default-information originate

Configure or disable RIP


default route.

Example:
Distribute a default route:
CASA-CMTS(config-router-rip)#defaultinformation 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

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
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 rip
CASA-CMTS(config-router-rip)# default-metric
10

Casa CMTS Software Configuration Guide

216

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 :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#

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

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
[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


from other areas.

Casa CMTS Software Configuration Guide

217

CASA CMTS

out

Prefixes advertised out of the specified area


from other areas.

if-name

Optional. Interface name

Example:
Filters prefixes that are sent from all other areas to area 3:
CASA-CMTS(config-router-rip)# 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

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
list

Configure the RIP


command list.

Example:
CASA-CMTS(config-router-rip)# 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

Casa CMTS Software Configuration Guide

218

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

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
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:
CASA-CMTS(config-router-rip)# neighbor
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

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
[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:
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)# network
Casa CMTS Software Configuration Guide

219

CASA CMTS

10.10.10.3/24
CASA-CMTS(config-router-rip)# network
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 :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
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-rip)# offset-list acl2 out
15

Casa CMTS Software Configuration Guide

220

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

Enter RIP configuration


mode.

Example :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
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-rip)# passive
interface default

Redistributing routes over RIP


This command redistributes routes from other routing protocols over RIP.
Step

Command (config)

Purpose

router rip

Example:
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
redistribute {ospf | connected | isis | bgp | static}

Enter RIP
configuration
mode.

redistribute ospf [metric | route-map]


redistribute connected [metric | route-map]
redistribute isis [metric | route-map]
redistribute rip [metric | route-map]
redistribute static [metric | route-map]

Redistribute
learned routes
from other
protocols to RIP
neighbors.

Where:
ospf

Redistributes OSPF routes over RIP.

connected

Redistributes connected routes over RIP.

isis

Redistributes IS-IS routes over RIP.

bgp

Redistributes RIP routes over BGP.

Casa CMTS Software Configuration Guide

221

CASA CMTS

static

Redistributes statically-configured routes over RIP.

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 configuration
command, the default metric value is 1. The value
used is specific to the protocol.

route-map
<map-name>

Optional. Routing process will generate the default


route if the route map is satisfied.

Example:
Configure OSPF to redistribute routes from static routes:
CASA-CMTS(config-router-ospf)# redistribute static

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

Enter RIP configuration


mode.

Example:
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
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-rip)# route
192.168.2.3/24

Casa CMTS Software Configuration Guide

222

CASA CMTS

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
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:
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 :
CASA-CMTS(config)# router rip
CASA-CMTS(config-router-rip)#
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

Casa CMTS Software Configuration Guide

223

CASA CMTS

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-rip)# 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.
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-rip)# version 2

Use the no form of the


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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE t port number in the range 0 to 11 for


C3200/C10200 and 0 to 3 for C2200.

Casa CMTS Software Configuration Guide

224

CASA CMTS

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
2

[no] ip rip authentication key-chain <name>


Where:
<name>

Configure or disable the


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.
Step
1

Command (config)

Purpose

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number in the range 0 to 11


for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] ip rip authentication string <name>
Where:
<name>

Configure or disable the


RIP authentication string.

Authentication string name up to 16 characters.

Example:
Configure authentication string as public:
CASA-CMTS(config-if-gige 0)# ip rip
authentication string public
Disable:
CASA-CMTS(config-if-gige id)# no ip rip
authentication string
Casa CMTS Software Configuration Guide

225

CASA CMTS

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

interface gige <port>

Enter GigE interface


mode.

Where:
<port>

GigE port number. Valid values are 0


to 11 for C3200/C10200 and 0 to 3 for
C2200.

Example:
CASA-CMTS(config)# interface gige 0
CASA-CMTS(config-if-gige 0)#
[no] ip rip authentication mode { text | md5 [auth-length
rfc] }
Where:
text

Text authentication mode.

md5

MD5 authentication mode.

Configure or disable IP
RIP authentication
mode.

Example:
Configure the interface to use MD5 authentication:
CASA-CMTS(config-if-gige 0)# ip rip
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
Casa CMTS Software Configuration Guide

Next Hop
0.0.0.0

226

CASA CMTS

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
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)

Displaying IPv4 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

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.

Casa CMTS Software Configuration Guide

227

CASA CMTS

rip

Routing Information Protocol routes.

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
C>* 10.168.3.0/24 is directly connected, bcm1
C>* 10.168.66.0/24 is directly connected,
bcm26
CASA-CMTS(config)#

Displaying IPv6 route information


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

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.

supernets-only

Supernets.

Example:
CASA-CMTS(config)# show ipv6 route

Casa CMTS Software Configuration Guide

228

CASA CMTS

Configuring the BGP Routing Protocol (Release 5.4 and later)


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

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 instances, as described later in this section.

Step
1

Command (config)

Purpose

[no] router bgp <asn>

Enable or disable BGP


routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#

Casa CMTS Software Configuration Guide

229

CASA CMTS

To specify the router-ID, using the following command:


Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
bgp router-id A.B.C.D

Specify the router-ID.

Example:
CASA-CMTS(config-router-bgp)# bgp router-id
A.B.C.D

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

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
distance bgp <1-255> <1-255> <1-255>
Where:
<1-255>

Specifies the external distance.

<1-255>

Specifies the internal distance.

Casa CMTS Software Configuration Guide

Change the BGP


distance value.

230

CASA CMTS

<1-255>

Specifies the local distance.

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>

Specifies the autonomous system number


(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that BGP
is already running. Respecify the command
using the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
distance <1-255> A.B.C.D/M [name]
Where:
<1-255>

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.

Set a distance
value to a
specified
network.

Example:
CASA-CMTS(config-router-bgp)# distance 5 60.3.4.5/24
list5

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).
Casa CMTS Software Configuration Guide

231

CASA CMTS

Enabling BGP networks


Configuring 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>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
[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.
Use the no form of the
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.

Enabling route aggregation


To specify an aggregate address:
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.

Casa CMTS Software Configuration Guide

232

CASA CMTS

If BGP was previously configured at the


CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
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

Configuring BGP route redistribution


This command redistributes routes from other routing protocols over BGP.
Step
1

Command (config)

Purpose

router bgp <asn>

Enter BGP
configuration
mode.

Where:
<asn>

Specifies the autonomous system number


(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that BGP
is already running. Respecify the command
using the expected AS number.

Example:
CASA-CMTS(config)# router bgp 5
CASA-CMTS(config-router-bgp)#
2

redistribute {ospf | connected | isis | rip | static}


redistribute ospf [metric | route-map]
redistribute connected [metric | route-map]
redistribute isis [metric | route-map]
redistribute rip [metric | route-map]

Casa CMTS Software Configuration Guide

Redistribute
learned routes
from other
protocols to
BGP neighbors.
233

CASA CMTS

redistribute static [metric | route-map]


Where:
ospf

Redistributes OSPF routes over BGP.

connected

Redistributes connected routes over BGP.

isis

Redistributes IS-IS routes over BGP.

rip

Redistributes RIP routes over BGP.

static

Redistributes statically-configured routes over


BGP.

metric
<metricvalue>

Optional. Metric used for generating the default


route in the range 0 to 4294967295. If you do not
specify a value, the default metric value is 0. The
metric value used is specific to the protocol.

route-map
<map-name>

Optional. Routing process will generate the default


route if the route map is satisfied.

Example:
Configure OSPF to redistribute routes from static routes:
CASA-CMTS(config-router-ospf)# 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>

Specifies the autonomous system number


(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that
BGP is already running. Respecify the
command using the expected AS number

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> remote-as <asn>
Where:

Casa CMTS Software Configuration Guide

Creates a new neighbor


whose remote-AS is
ASN. A peer can be an
234

CASA CMTS

<peer_ip-address>

The IP address of the BGP peer.

<asn>

Specifies the autonomous system


number (ASN) in the range 1 to
65535. If BGP was previously
configured at the CMTS, you will
receive a screen message to tell you
that BGP is already running.
Respecify the command using the
expected AS number.

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.
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> password <string>
Where:
<peer_ip-address>
<string>

The IP address of the BGP peer.


The password text string associated
with this BGP peer.

Example:
In this case the router in AS-1 is attempting to peer with AS-2
at 10.0.0.1.
Casa CMTS Software Configuration Guide

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.

235

CASA CMTS

CASA-CMTS(config-router-bgp)# neighbor
10.0.0.1 password

Configuring BGP peers


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>

Specifies the autonomous system number (ASN) in


the range 1 to 65535. If BGP was previously
configured at the CMTS, you will receive a screen
message to tell you that BGP is already running.
Respecify the command using the expected AS
number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[ no] neighbor <peer_ip-address> shutdown
Where:
<peer_ip-address>

IP address of the BGP peer.

Specify shutdown
or no-shutdown of
neighbor-specific
configurations.

Example:
CASA-CMTS(config-router-bgp)# no neighbor
64.10.1.0 shutdown
To allow EBGP neighbors thatare not on directly-connected networks:
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP
routing.

Where:
<asn>

Specifies the autonomous system number


(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that
BGP is already running. Respecify the
command using the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> ebgp-multihop [max-hopcount]

Casa CMTS Software Configuration Guide

EBGP neighbors
not on directly
236

CASA CMTS

Where:
<peer_ip-address>
<max-hop-count>

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
CASA-CMTS(config-router-bgp)# neighbor 63.10.1.0
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>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor peer description <line>

Add a description to a
peer (up to 80 lines):

Example:
CASA-CMTS(config-router-bgp)#[ 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>

Specifies the autonomous system number


(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that BGP
is already running. Respecify the command
using the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
Casa CMTS Software Configuration Guide

237

CASA CMTS

CASA-CMTS(config-router-bgp)#
2

Set up the neighbors


BGP version.

neighbor <peer_ip-address> version <version>


Where:
<peer_ip-address>
<version>

The IP address of the BGP peer.


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 4is similar but the neighbor uses the old
Internet-Draft revision 00s Multiprotocol
Extensions for BGP-4. Some routing
software is still using this version.

Example:
CASA-CMTS(config-router-bgp)#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>

Specifies the autonomous system number (ASN) in the


range 1 to 65535. If BGP was previously configured at
the CMTS, you will receive a screen message to tell you
that BGP is already running. Respecify the command
using the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> interface <ifname>
Where:
<peer_ip-address>
<ifname>

Connect to a BGP
peer over an IPv6
link-local address.

The IP address of the BGP peer.


The interface name specified as a
text string.

Example:
CASA-CMTS(config-router-bgp)#neighbor 192.168.3.4
interface ifname
To specify an announced routes nexthop as being equivalent to the address of the BGP router:
Step

Command (config)

Casa CMTS Software Configuration Guide

Purpose
238

CASA CMTS

Enable BGP routing.

router bgp <asn>


Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> next-hop-self
Where:
<peer_ip-address>

The IP address of the BGP peer.

Specify an announced
routes next hop as being
equivalent to the address
of the BGP router

Example:
CASA-CMTS(config-router-bgp)# neighbor
192.168.3.4 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>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> default-originate
Where:
<peer_ipaddress>

Announce default routes


to the peer.

The IP address of the BGP peer.

Example:
CASA-CMTS(config-router-bgp)#[no] neighbor
192.168.3.4 default-originate
Casa CMTS Software Configuration Guide

239

CASA CMTS

To define the source of routing updates:


Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP
routing.

Where:
<asn>

Specifies the autonomous system number


(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that BGP
is already running. Respecify the command
using the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> update-source <asn>
Where:
<peer_ipaddress>
<asn>

Define the
source of routing
updates

The IP address of the BGP peer.


Specifies the autonomous system number
(ASN) in the range 1 to 65535. If BGP was
previously configured at the CMTS, you will
receive a screen message to tell you that BGP
is already running. Respecify the command
using the expected AS number.

Example:
CASA-CMTS(config-router-bgp)#[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>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
Casa CMTS Software Configuration Guide

240

CASA CMTS

CASA-CMTS(config-router-bgp)#
2

Send community
attributes to this
neighbor.

[no] neighbor <peer_ip-address> send-community


Where:
<peer_ip-address>

Specifies the IP address of the BGP peer.

Example:
CASA-CMTS(config-router-bgp)# neighbor 192.168.3.4
send-community
To specify a default value for the neighbor routes:
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:

CASA-CMTS(config)# router bgp 1


CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> weight <value>
Where:
<peer_ipaddress>
<value>

Specify a default value


for the neighbors routes

The IP address of the BGP peer.


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:


Casa CMTS Software Configuration Guide

241

CASA CMTS

Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
2

[no] neighbor <peer_ip-address> maximum-prefix


<number>

Specify the maximum


number of prefixes
accepted from this peer.

Where:
<peer_ipaddress>

The IP address of the BGP peer.

<number>

The maximum number of prefixes in the


range 1 to 4294967295.

Example:
CASA-CMTS(config-router-bgp)# neighbor
192.168.3.4 maximum-prefix 100

Peer filtering
To 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>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
Casa CMTS Software Configuration Guide

242

CASA CMTS

CASA-CMTS(config)# router bgp 1


CASA-CMTS(config-router-bgp)#
neighbor <peer_ip-address> distribute-list {<name> |
<number> } {in | out}
Where:
<peer_ipaddress>

Specify a distribute-list
for the peer.

The IP address of the BGP 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:
CASA-CMTS(config-router-bgp)# neighbor
192.168.3.4 distribute-list list1 in
To 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 (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
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.

in

Filters inbound updates.

out

Filters outbound updates.

Example:
Casa CMTS Software Configuration Guide

243

CASA CMTS

CASA-CMTS(config-router-bgp)#neighbor peer
prefix-list prefixList1 out
To specify a filter-list for the peer:
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
neighbor <peer_ip-address> filter-list <name> [in | out]

Specify a filer-list for the


peer:

Where:
<peer_ipaddress>

The IP address of the BGP peer.

<name>

The filter list name.

in

Filters inbound updates.

out

Filters outbound updates.

Example:
CASA-CMTS(config-router-bgp)#neighbor peer
filter-list filterList1 in
To apply a route-map to a BGP neighbor:
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
Casa CMTS Software Configuration Guide

244

CASA CMTS

CASA-CMTS(config-router-bgp)#
2

neighbor <peer_ip-address> route-map <name> {in | out}


Where:
<peer_ipaddress>

Apply a route map (5.4


only) to a neighbor.

The IP address of the BGP peer.

<name>

The name of the route-map.

in

Filters inbound updates.

out

Filters outbound updates.

Example:
CASA-CMTS(config-router-bgp)#neighbor peer
route-map <name> [in | out]

Configuring BGP peer groups


To define a new BGP peer group:
Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:

CASA-CMTS(config)# router bgp 1


CASA-CMTS(config-router-bgp)#
neighbor <peer-group_name>

Define a new peer group

Example:
CASA-CMTS(config-router-bgp)#neighbor group1

To bind a specific peer to a peer group:


Casa CMTS Software Configuration Guide

245

CASA CMTS

Step
1

Command (config)

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system


number (ASN) in the range 1 to 65535.
If BGP was previously configured at the
CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using
the expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
neighbor <ip_-address> peer-group <name>

Bind a specific peer to a


named peer group.

Example:
CASA-CMTS(config-router-bgp)# neighbor
192.168.3.4 peer-group peerGroup1

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>

Specifies the autonomous system number


(ASN). If BGP was previously configured at
the CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using the
expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] address-family {ipv4 | ipv6 |} [ unicast]
Where:
ipv4
ipv6

Internet Protocol Version 4; multicast or unicast

Configure a routing
session using
address-family ipv4,
ipv6 or vpnv4.

Internet Protocol Version 6; unicast only

Casa CMTS Software Configuration Guide

246

CASA CMTS

unicast

Optional. Specifies IPv4, IPv6, or vpnv4 unicast


address prefixes. This is the default setting.

Example:
CASA-CMTS(config-router-bgp)# address-family ipv4
unicast

Specifying the BGP IPv6 address family parameters


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

router bgp <asn>

Enable BGP
routing.

Where:
<asn>

Specifies the autonomous system number (ASN).


If BGP was previously configured at the CMTS,
you will receive a screen message to tell you that
BGP is already running. Respecify the command
using the expected AS number.

Example:

CASA-CMTS(config)# router bgp 1


CASA-CMTS(config-router-bgp)#
[no] address-family ipv6 [unicast]
Parameter settings:
aggregate-address < X:X::X:X/M >

Configure the
BGP IPv6
address-family
parameters.

exit-address-family
neighbor {ipv4_address | ipv6_address | peer_group_name}
activate
neighbor {ipv4_address | ipv6_address | peer_group_name}
advertisement-interval <seconds>
neighbor {ipv4_address | ipv6_address | peer_group_name}
allowas-in [occurences_number]
neighbor {ipv4_address | ipv6_address | peer_group_name}
attribute-unchanged [as-path | med | next-hop]
neighbor {ipv4_address | ipv6_address | peer_group_name}
capability orf prefix-list {both | receive | send}
neighbor {ipv4_address | ipv6_address | peer_group_name}
Casa CMTS Software Configuration Guide

247

CASA CMTS

default-originate [route-map <name>]


neighbor {ipv4_address | ipv6_address | peer_group_name}
default-originate [route-map <name>]
neighbor {ipv4_address | ipv6_address | peer_group_name}
distribute-list <name> {in | out}
neighbor {ipv4_address | ipv6_address | peer_group_name}
filter-list <name> {in | out}
neighbor {ipv4_address | ipv6_address | peer_group_name}
maximum-prefix <limit_number> [threshold <number> | warningonly]
neighbor {ipv4_address | ipv6_address | peer_group_name}
next-hop-self
neighbor {ipv4_address | ipv6_address | peer_group_name}
peer-group <name>
neighbor {ipv4_address | ipv6_address | peer_group_name}
prefix-list <name> {in | out}
neighbor {ipv4_address | ipv6_address | peer_group_name}
remove-private-AS
neighbor {ipv4_address | ipv6_address | peer_group_name}
route-map <name> {in | out}
neighbor {ipv4_address | ipv6_address | peer_group_name}
send-community [both | extended | standard]
neighbor {ipv4_address | ipv6_address | peer_group_name}
soft-reconfiguration inbound
neighbor {ipv4_address | ipv6_address | peer_group_name}
unsuppress-map <name>
neighbor {ipv4_address | ipv6_address | peer_group_name}
weight <number>
network ipv6 address [route-map <name>]
redistribute { connected | isis | static} metric <number> [routemap <name>
Where:
ipv6

Internet Protocol Version 6; unicast only

unicast

Optional. Specifies IPv6 unicast address prefixes.

aggregateaddress

Specifies the address-family IPv6 prefix in the


shortened format x:x::x:x/<mask>. The aggregate

Casa CMTS Software Configuration Guide

248

CASA CMTS

address is a public unicast global address that


begins with 2xxx (001) .
exit-addressfamily

Exits the address-family configuration context


(config-router-af) and places the user at the
previous context (config-router-bgp).

neighbor

Specifies the IPv4, IPv6, or the previouslyconfigured BGP peer group name containing one
or more BGP neighbor bindings.
Neighbor options:
activate Enables the address-family for the
this BGP neighbor.
advertisement-interval Sets the time
interval between sending BGP route updates
to the BGP neighbor. The interval is specified
in the range 0 to 600 seconds.
allowas-in Instructs the CMTS to accept
inbound route advertisement s containing
occurrences of the local CMTS routers AS
number. Up to 10 occurrences may be
specified before BGP rejects the inbound route
update as a looping condition.
attribute-unchanged Propogates BGP next
hop attribute as unchanged to the specified
neighbor. This parameter is used for multihop
BGP peering.
capability orf Advertises the prefix-based
outbound route filter (ORF) send and receive
capabilities, or both, to the BGP neighbor in
order to reduce the number route updates that
are exchanged between the BGP peers.
default-originate Instructs the CMTS to
advertise the default route to the specified
BGP neighbor. Optionally, a route-map may be
specified if the route-map contains a matching
IP address with a route that matches an IP
access list.
distribute-list Instructs the CMTS to filter
inbound or outbound BGP route
advertisements associated with a specified
BGP peer or peer group using a named
access-list. This is the access-list created with
the ip access-list command.
Note: Do not apply the neighbor distributelist and the neighbor prefix-list to the same
neighbor or peer group at the same time in any
direction.
filter-list Specifies the IP access-list to apply
to either inbound or outbound BGP route

Casa CMTS Software Configuration Guide

249

CASA CMTS

advertisements associated with the specified


peer or peer-group. This is the access-list
created with the ip as-path access-list
command.
maximum-prefix Specifies the number of
IPv6 prefixes that can received from the
specified BGP peer or peer group. By default,
there is no limit to the numer of IPv6 prefixes.
next-hop-self Configures the specified BGP
router or BGP peer group as the next hop BGP
speaker in networks where BGP neighbors do
not have direct access to other neighbors on
the same IP subnet.
nexthop-local unchanged -- Configures the
outgoing link-local nexthop attribute as
unchanged for the specified next hop BGP
neighbor or peer-group across multihop peer
sessions.
peer-group Adds the specified BGP
neighbor IP address to the specified peer
group. This BGP router inherits the current
configuration settings for this peer group.
prefix-list Instructs the CMTS to filter BGP
inbound or outbound route advertisements
associated with a BGP neighbor or BGP peer
group using a named prefix-list.
Note: Do not apply the neighbor distributelist and the neighbor prefix-list to the same
neighbor or peer group at the same time in any
direction.
remove-private-AS Instructs the CMTS to
remove private autonomous system numbers
in BGP route updates to the specified external
neighbor or BGP peer group. Private AS
numbers are not removed if the AS path
contains the AS number of the BGP peer
router.
route-map Applies the specified route-map
to either inbound route updates from the
specified BGP neighbor or applies the routemap to outbound route updates to the BGP
neighbor.
send-community Specifies whether
standard or extended community attributes,or
both, are sent to this BGP neighbor.
soft-reconfiguration inbound Instructs the
CMTS to store unmodified inbound BGP route
updates from the specified neighbor. Stored
routes are used to generate new inbound route
updates.
unsuppress-map Specifies the name of the
Casa CMTS Software Configuration Guide

250

CASA CMTS

route-map at the CMTS that releases


surpressed routes.
weight Sets the default weight for routes that
originate from this BGP neighbor when
compared to weights associated with other
routes. Routes with higher weight values have
preference over other routes to the same
network.
network

redistribute

Specifies the network IPv6 address and mask to


be advertised by BGP. Optionally, a route-map
may be specified for network filtering. Otherwise,
all networks specified by the network prefix will be
advertised.
Captures routes from other routing protocols. BGP
then advertises these routes to BGP neighbor
routers.
connected -- Instructs BGP to advertise
connected routes from a directly-connected
subnet or host.
isis -- Specifies BGP route distribution to IS-IS
level-1/level-2 routers.
static -- Instructs BGP to advertise staticallyconfigured routes. A level option is not
required.

route-map
<name>

Optional. Instructs BGP to apply a previouslyconfigured route map to control route


advertisements to BGP routers. See the
Configuring Route Maps section of this manual
for information.

Examples:
CASA-CMTS(config-router-bgp)# address-family ipv6
unicast
CASA-CMTS(config-router-af)# exit-address-family
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
activate
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
advertisement-interval 100
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
allowas-in 5
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
attribute-unchanged as-path med next-hop
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
capability orf prefix-list both
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
Casa CMTS Software Configuration Guide

251

CASA CMTS

default-originate route-map map1


CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
distribute-list acl1 in
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
filter-list list1 out
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
maximum-prefix 100 warning-only
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
next-hop-self
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
prefix-list list1 in
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
remove-private-AS
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
route-map map1 in
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
send-community both
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
soft-reconfiguration inbound
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
unsuppress-map map1
CASA-CMTS(config-router-af)# neighbor 2001:1::1:1
weight 600
CASA-CMTS(config-router-af)# network 2001:1::1:1/64
CASA-CMTS(config-router-af)# redistribute connected

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.

Defining the AS path access list


To define new AS path access-list:
Casa CMTS Software Configuration Guide

252

CASA CMTS

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
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

Casa CMTS Software Configuration Guide

253

CASA CMTS

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.

Example:
CASA-CMTS(config)#ip community-list 123 permit
internet

Casa CMTS Software Configuration Guide

254

CASA CMTS

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
ip community-list 80 permit 7675:80 ip community-list 80 deny
ip community-list 90 permit 7675:90 ip community-list 90 deny
!
route-map RMAP permit 10 match community 70
set local-preference 70
!
route-map RMAP permit 20 match community 80
set local-preference 80
!
route-map RMAP permit 30 match community 90
set local-preference 90

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.
router bgp 100 network 10.0.0.0/8
neighbor 192.168.0.2 remote-as 7675
neighbor 192.168.0.2 route-map RMAP out
Casa CMTS Software Configuration Guide

255

CASA CMTS

!
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
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
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
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
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

Example 5

Casa CMTS Software Configuration Guide

256

CASA CMTS

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
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
ip community-list standard DEL permit 100:1 100:2
!
route-map RMAP permit 10
set comm-list DEL delete
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
ip community-list 80 permit 7675:80 ip community-list 80 deny
ip community-list 90 permit 7675:90 ip community-list 90 deny
!
route-map RMAP permit 10 match community 70
set local-preference 70
!
route-map RMAP permit 20 match community 80
set local-preference 80
!
route-map RMAP permit 30 match community 90
set local-preference 90

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 remote-as 7675
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
route-map RMAP permit 10
match ip address acl
set community 7675:80

Example 7
Casa CMTS Software Configuration Guide

257

CASA CMTS

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
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
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
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
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
neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
ip community-list standard DEL permit 100:1 100:2
!
route-map RMAP permit 10
set comm-list DEL delete

Casa CMTS Software Configuration Guide

258

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
To 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.

To 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.

To display path information:


Step
1

Command

Purpose

show ip bgp paths

Display path information.

Example:
CASA-CMTS# show ip bgp paths
To 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
To display the BGP scan status:
Step
1

Command

Purpose

show ip bgp scan

Display the BGP scan


status.

Casa CMTS Software Configuration Guide

259

CASA CMTS

Example:
CASA-CMTS# show ip bgp scan
To 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
To display the BGP attributes:
Step Command
1

show ip bgp attribute-info

Purpose
Display BGP attributes.

Example:
CASA-CMTS# show ip bgp attribute-info
To 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:
Casa CMTS Software Configuration Guide

260

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

Casa CMTS Software Configuration Guide

261

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>

Specifies the autonomous system


number (ASN). If BGP was previously
configured at the CMTS, you will receive
a screen message to tell you that BGP is
already running. Respecify the
command using the expected AS
number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> dont-capabilitynegotiate
Where:
<peer_ipaddress>>

Disable sending the


capability negotiation
OPEN message.

The IP address of the BGP peer.

Example:
CASA-CMTS(config-router-bgp)# neighbor
192.168.3.4 dont-capability-negotiate

Casa CMTS Software Configuration Guide

262

CASA CMTS

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.

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>

Specifies the autonomous system number


(ASN). If BGP was previously configured at
the CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using the
expected AS number.

Example:
CASA-CMTS(config)# router bgp 1
CASA-CMTS(config-router-bgp)#
bgp cluster-id <cluster_id> |
Where:
<cluster_id>

Configure routereflector cluster


identifier.

Router reflector cluster identifier in IP


address format or in the range 1 to
4294967295

Example:
CASA-CMTS(config-router-bgp)# bgp cluster-id 300
Configure a BGP neighbor as a route-reflector:
Step
1

Command

Purpose

router bgp <asn>

Enable BGP routing.

Where:
<asn>

Specifies the autonomous system number


(ASN). If BGP was previously configured at
the CMTS, you will receive a screen
message to tell you that BGP is already
running. Respecify the command using the
expected AS number.

Casa CMTS Software Configuration Guide

263

CASA CMTS

Example:

CASA-CMTS(config)# router bgp 1


CASA-CMTS(config-router-bgp)#
[no] neighbor <peer_ip-address> route-reflector-client
Where:
<peer_ipaddress>>

Configure a BGP
neighbor as a routereflector.

The IP address of the BGP peer.

Example:
CASA-CMTS(config-router-bgp)# [no] neighbor peer
route-reflector-client

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

Casa CMTS Software Configuration Guide

264

CASA CMTS

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

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:
CASA-CMTS(config)# ip access-list telnet_host
CASA-CMTS(conf-acl telnet_host)#
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.
Casa CMTS Software Configuration Guide

265

CASA CMTS

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:
CASA-CMTS(config)# ip access-list telnet_host
CASA-CMTS(conf-acl telnet_host)#
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
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

Casa CMTS Software Configuration Guide

266

CASA CMTS

addresses. IP addresses and masks are


specified in the dotted notation A.B.C.D.
Port numbers are in the range 1 to 65535.
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.

any

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


CASA-CMTS(conf-acl telnet_host)#
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:
CASA-CMTS(conf-acl telnet_host)# no 100
CASA-CMTS(conf-acl telnet_host)#

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:
CASA-CMTS(config)# ip access-list telnet_host
CASA-CMTS(conf-acl telnet_host)#

Casa CMTS Software Configuration Guide

267

CASA CMTS

[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>
details

Name of ACL.
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

Casa CMTS Software Configuration Guide

268

CASA CMTS

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
20 deny telnet any any
To insert another rule between sequences 10 and 20:
CASA-CMTS(conf-acl telnet_host)#
CASA-CMTS(conf-acl telnet_host)#
10 permit telnet 192.168.2.238
15 permit telnet 192.168.2.222
20 deny telnet any any

15 permit telnet 192.168.2.222


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.
CASA-CMTS(conf-acl telnet_host)#
CASA-CMTS(conf-acl telnet_host)#
10 permit telnet 192.168.2.238
20 permit telnet 192.168.2.222
30 deny telnet any any

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
Casa CMTS Software Configuration Guide

269

CASA CMTS

trunk
vlan
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)# interface eth 0
CASA-CMTS(config-if-eth 0)#
ip access-group <acl-name>
Where:
<acl-name>

Apply the ACL.

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:
CASA-CMTS(config)# interface gige 1
CASA-CMTS(config-if-gige 1)#

Casa CMTS Software Configuration Guide

270

CASA CMTS

Apply the ACL.

ip access-group <acl-name>
Where:
<acl-name>

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

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

Casa CMTS Software Configuration Guide

271

CASA CMTS

Where:
<acl-name>

Name of ACL.

Example:
CASA-CMTS(config)# access-class out tftp_host
CASA-CMTS(config)# no access-class out

incoming access
class use the no
command. The
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 :
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.

Note that this command is accessible from diagnostic mode in Rel.5.4 and later releases:
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:
Casa CMTS Software Configuration Guide

272

CASA CMTS

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.

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>
permit

The named route-map up to 128 alphanumeric


characters. The name is case-sensitive.
If the inbound route meets the match criteria,

Casa CMTS Software Configuration Guide

Use the no form


of the command
to delete the
273

CASA CMTS

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
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.

named routemap.

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

Casa CMTS Software Configuration Guide

Use the no form


274

CASA CMTS

which a route passes in order to reach a


destination.
Only one as-path may be specified per routemap.

of the command
to delete the
named as-path
setting.

Example:
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.

Use the no
form of the
command to
delete the
route-map
community.

Perform exact matching on the configured


BGP community attribute list name or
number.

Example:
CASA-CMTS(conf-route-map cmtsNet1)# match community
70
To remove the configured BGP community list:
CASA-CMTS#(conf-route-map cmtsNet1)#
community

Casa CMTS Software Configuration Guide

no match

275

CASA CMTS

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.
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.

Casa CMTS Software Configuration Guide

Use the no form


276

CASA CMTS

Only one metric may be specified per route-map.


Examples:
CASA-CMTS(conf-route-map cmtsNet1)# match metric 5

of the command
to delete the
metric entry.

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

Casa CMTS Software Configuration Guide

277

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

Casa CMTS Software Configuration Guide

278

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.
Casa CMTS Software Configuration Guide

279

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

Use the no form of the


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.

Casa CMTS Software Configuration Guide

Use the no
form of the
command to
delete
community
setting.

280

CASA CMTS

Example:
CASA-CMTS(conf-route-map cmtsNet1)# set community
225:1
To remove the configured community number:
CASA-CMTS(conf-route-map cmtsNet1)# no set
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.

Casa CMTS Software Configuration Guide

281

CASA CMTS

Step
1

Command (config)

Purpose

[no] set local-preference <localPref-value>

Specify the local


preference
metric value

Where:
<localPef-value>

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.

Examples:
CASA-CMTS(conf-route-map cmtsNet1)# set metric 5

Use the no form


of the command
to delete the
metric setting.

To remove the configured metric setting:


CASA-CMTS(conf-route-map cmtsNet1)# no set metric

Casa CMTS Software Configuration Guide

282

CASA CMTS

Modifying route origins


Use the set origin command to modify the path origin attribute, as originally matched by routemap.
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 Software Configuration Guide

Use the no form


of the command
283

CASA CMTS

CASA-CMTS(conf-route-map cmtsNet1)# set originatorid 192.268.3.4

to delete the
originator-id
setting.

To remove the configured metric setting:


CASA-CMTS(conf-route-map cmtsNet1)# no set
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.

To remove the configured metric 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

Casa CMTS Software Configuration Guide

284

CASA CMTS

Configuring a VLAN
To configure a VLAN:
Step
1

Command (config)

Purpose

[no] interface vlan <number>

Create a numbered
VLAN and enter the
interface vlan
configuration
context.

Where:
<number>

Specifies the VLAN ID in the range 1 to 4094. On


Casa C3200 CMTS systems, the supported VLAN
range is 1 to 4078.

Example:
CASA-CMTS(config)#interface vlan 2
CASA-CMTS(config-if-vlan 2)

Configuring a VLAN description


To configure a text description of a VLAN interface, execute the description command under the
interface vlan configuration context.
Step
1

Command (config)

Purpose

[no] interface vlan <number>

Create a numbered
VLAN and enter the
interface vlan
configuration
context.

Where:
<number>

Specifies the VLAN ID in the range 1 to 4094. On


Casa C3200 CMTS systems, the supported VLAN
range is 1 to 4078.

Example:
2

CASA-CMTS(config)#interface vlan 2
[no] description <string>
Where:
<string>

Specifies the text string to describe the VLAN port


interface. Up to 64 characters may be specified. If
the string has embedded blank spaces, then the
string must be within quotation marks ( ).

Example:
Enter a text a description for VLAN interface 10.
CASA-CMTS(config-if-vlan 10)# description This
is a text string within quotation marks.

Casa CMTS Software Configuration Guide

285

CASA CMTS

Configuring up to six VLANs concurrently (Release 5.4 and later)


Step
1

Command (config)

Purpose

[no] interface vlan <num> <num> [<num>] [<num>]


[<num>] [<num>]

Configure up to 5
VLANs. To remove the
VLANs, use the no form
of the command.

Where:
<num>

Specifies the VLAN ID in the range 1 to 4094.


On Casa C3200 CMTS systems, the supported
VLAN range is 1 to 4078.

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 and later)


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

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 ID in the range 1 to 4094.


On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Casa CMTS Software Configuration Guide

286

CASA CMTS

Example:
CASA-CMTS(config)#interface vlan 2
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 ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 256
CASA-CMTS(conf-if-vlan 256)#
gige <port>
Where:
<port>

Specify the GigE


interface port
number.

Specifies the GigE interface port number.

Example:
CASA-CMTS(conf-if-vlan 256)# gige 1

Casa CMTS Software Configuration Guide

287

CASA CMTS

Assigning a 10Gigabit Ethernet port to a VLAN


To assign a 10GigE Ethernet port to a VLAN:
Step
1

Command (config)

Purpose

interface vlan <vlan-id>

Configure the VLAN


interface.

Where:
<vlan-id>

Specifies the VLAN ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 10
CASA-CMTS(conf-if-vlan 6/10)#
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

interface vlan <vlan-id>

Configure the
VLAN interface.

Where:
<vlan-id>

Specifies the VLAN ID in the range 1 to 4094.


On Casa C3200 CMTS systems, the supported
VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 256
CASA-CMTS(conf-if-vlan 256)#
no gige <port>
Where:
<port>

Specify the GigE


interface port
number.

Specifies the GigE interface port number.

Example:
CASA-CMTS(conf-if-vlan 256)# no gige 1

Casa CMTS Software Configuration Guide

288

CASA CMTS

Removing a 10Gigabit Ethernet port from a VLAN


To remove a 10GigE Ethernet port from a VLAN:
Step
1

Command (config)

Purpose

interface vlan <vlan-id>

Configure the
VLAN interface.

Where:
<vlan-id>

Specifies the VLAN ID in the range 1 to 4094.


On Casa C3200 CMTS systems, the supported
VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 10
CASA-CMTS(conf-if-vlan 6/10)#
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

interface vlan <vlan-id>

Configure the VLAN


interface

Where:
<vlan-id>

Specifies the VLAN ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 10
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

Casa CMTS Software Configuration Guide

289

CASA CMTS

[no] ip address <ip-address> <subnet-mask>


Where:
<ip-address>

Assign an IP address to
a VLAN.

Text string for standard IP address in


the format a.b.c.d.
Text string for standard subnet mask
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


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.
To assign a IPv6 address to a VLAN:
Step
1

Command (config)

Purpose

interface vlan <vlan-id>

Configure the VLAN


interface

Where:
<vlan-id>

Specifies the VLAN ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 10
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

[no] ipv6 address <ipv6-address>/<mask_len>


Where:
<ipv6address>
<mask_len>

Assign an IPv6
address to VLAN.

Text string for standard IPv6 address in the


format xxxx:xxxx:xxxx:...:xxxx
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)

Casa CMTS Software Configuration Guide

290

CASA CMTS

One sequence of 20 bit blocks containing only


zeroes can be replaced with ::
Example:
Assign IPv6 address 2000::1000:1/64 to VLAN 10:
CASA-CMTS(config-if-vlan 6/10)# ipv6 address
2000::1000:1/64
Remove the IPv6 address:
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 ID in the range 1 to 4094. On


Casa C3200 CMTS systems, the supported VLAN
range is 1 to 4078.

Example:
CASA-CMTS(config)#interface vlan 10
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(config)# interface vlan 2
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:
Step
1

Command (config)

Purpose

interface qam <module>/<port>

Enter QAM interface


mode.

Casa CMTS Software Configuration Guide

291

CASA CMTS

Where:
<module>
<port>

Module number.
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>

Specifies the VLAN ID in the range 1 to 4094.


On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

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>

Specifies the VLAN ID in the range 1 to 4094.


On Casa C3200 CMTS systems, the supported
VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)#interface vlan 2
[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:
Casa CMTS Software Configuration Guide

292

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>

Enter a VLAN
interface by
specifying the
VLAN ID.

Where:
<vlan_id>

Specifies the VLAN ID in the range 1 to 4094. On


Casa C3200 CMTS systems, the supported VLAN
range is 1 to 4078.

Example:
CASA-CMTS(config)#interface vlan 10
[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(config)# interface trunk 12
CASA-CMTS(conf-if-trunk 12)#
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(config)# interface vlan 10
CASA-CMTS(conf-if-vlan 10)#trunk 10
CASA-CMTS(conf-if-vlan 10)#ip address 192.67.43.1 255.255.0.0

Casa CMTS Software Configuration Guide

293

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 gige 1, vlan 256
interface gige 2, vlan 2
interface gige 3, vlan 2
interface qam 0/0, vlan 2
interface qam 0/1, vlan 256
interface qam 0/2, vlan 2
interface qam 0/3, 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>

Specifies the VLAN ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

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 Software Configuration Guide

294

CASA CMTS

Displaying ARP entries from the current VLAN


To display the ARP entries from the current VLAN:
Step
1

Command (config)

Purpose

interface vlan <vlan-id>

Configure the VLAN


interface.

Where:
<vlan-id>

Specifies the VLAN ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 10
CASA-CMTS(conf-if-vlan 6/10)#
show arp
Example:
CASA-CMTS(config)# interface vlan 10
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

Casa CMTS Software Configuration Guide

State

Type

dynamic ARPA
dynamic ARPA
dynamic ARPA
dynamic ARPA
static

ARPA

dynamic ARPA
static

ARPA

static

ARPA

static

ARPA

295

CASA CMTS

Configuring L2VPN
Casa CMTS supports L2VPN protocol which provides an end-to-end connection to an enterprise
office over an MPLS or IP core network. 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
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 ip pim sparse-mode
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

[no] interface vlan <vlan_id>

Find out the information


about the VPN on the

Casa CMTS Software Configuration Guide

296

CASA CMTS

Where:
<vlan_id>

CMTS.
Specifies the VLAN ID in the range 1 to
4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
CASA-CMTS(config)# interface vlan 400
CASA-CMTS(conf-if-vlan 400)#

Specifying GigE/trunk interfaces on the L2VPN VLAN


Step
1

Command (config)

Purpose

[no] interface vlan <vlan_id>

Enter interface
mode.

Where:
<vlan_id>

VLAN ID. Valid values are 256 to 1000.

Example:
CASA-CMTS(config)# interface vlan 400
CASA-CMTS(conf-if-vlan 400)#
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-traffic-forwarding}

Preventing/permitti
ng station
movement and
local forwarding.

Where:
mac-address-movable

Specifies a change of locations for


MAC addresses attached to a
permitted l2vpn.

Casa CMTS Software Configuration Guide

297

CASA CMTS

local-traffic-forwarding

Traffic destined to local addresses


permitted

Example:
CASA-CMTS(config)# no l2vpn mac-address-movable

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-traffic-forwarding}

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 ID in the range 1 to


4094. On Casa C3200 CMTS systems, the
supported VLAN range is 1 to 4078.

Example:
C10G-203(config)#show l2vpn vlan 10
l2vpn vlan table: vlan_id=10

Casa CMTS Software Configuration Guide

298

CASA CMTS

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


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 TACACS+ host IP address and key
Enabling and disabling TACACS+ password authentication
Configuring and displaying the AAA configuration

Configuring the TACACS host IP


To configure a host IP:
Step
1

Command (config)

Purpose

tacacs-server host <ip_address>

Configure a
TACACS server
host IP
address.

Where:
<ip_address>

Specifies the TACACS host IP address in decimal


format a.b.c.d.

Example:
CASA-CMTS(config)tacacs-server host 192.168.10.1#

Casa CMTS Software Configuration Guide

299

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>

Specifies the case sensitive server access keyword.

Example:
CASA-CMTS(config) tacacs-server key abcd

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

Casa CMTS Software Configuration Guide

300

CASA CMTS

Enabling ASCII clear text authentication


To enable the TACACS+ ASCII clear text authentication:
Step
1

Command (config)

Purpose

[no] aaa authentication ascii

Enable TACACS+
ACSCII clear text
password authentication.

Example:
CASA-CMTS(config)# aaa authentication ascii

Using RADIUS/TACACS+ Server for default server group for AAA


login authentication
Step
1

Command (config)

Purpose

aaa authentication login default group {radius |


tacacsplus}
Where:
radius
tacacsplus

Use RADIUS/TACACS+
server for default server
group for AAA login
authentication.

Use RADIUS server.


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

Casa CMTS Software Configuration Guide

301

CASA CMTS

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

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}

Configure authorization
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)
aaa authorization exec default {if-authenticated group | group |
local group | none group } tacacsplus

Casa CMTS Software Configuration Guide

Purpose
Configure
authorization exec
shell default login
302

CASA CMTS

Where:
if-authenticated

Proceed if authenticated.

local

Use local.

none

No authorization.

group

Server Group.

tacacsplus

Tacacs plus server

Example:
aaa authorization exec default if-authenticated
group tacacsplus

Enabling accounting
To enable accounting:
Step
1

Command (config)

Purpose

aaa accounting

Enable accounting

Command accounting
To perform command accounting:
Step
1

Command (config)

Purpose

aaa accounting commands <num> default {none | start-stop |


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 |

Casa CMTS Software Configuration Guide

Purpose
Configure AAA
303

CASA CMTS

accounting for startstop events.

tacacsplus}
Where:
radius
tacacsplus

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

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.

Casa CMTS Software Configuration Guide

304

CASA CMTS

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

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

Casa CMTS Software Configuration Guide

305

CASA CMTS

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
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.

RPC mode
Auto Multiplex mode

Group-4-port mode

Group-2-port mode

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
Casa CMTS Software Configuration Guide

306

CASA CMTS

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:
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.

Casa CMTS Software Configuration Guide

307

CASA CMTS

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
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.

Casa CMTS Software Configuration Guide

308

CASA CMTS

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:
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)
pppppppp = Assigned program number, 1 to 255
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

Casa CMTS Software Configuration Guide

309

CASA CMTS

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

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.

Casa CMTS Software Configuration Guide

310

CASA CMTS

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
pppppppp = Assigned program number, 1 to 255
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

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.

Casa CMTS Software Configuration Guide

311

CASA CMTS

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)#

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)
end

Purpose
End stream configuration
mode.

Example:
End stream configuration mode:
CASA-CMTS(config-stream)# end
CASA-CMTS(config)#

Casa CMTS Software Configuration Guide

312

CASA CMTS

Setting the stream source IP address


To set stream source IP address:
Step
1

Command (config)

Purpose

[no] stream <stream-id>

Enter or end stream


configuration mode.

Where:
<stream-id>

Stream ID in the range 1 to 9999.

Example:
Enter stream configuration mode. for stream 123:
2

CASA-CMTS(config)# stream 123


[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.

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
CASA-CMTS(config-stream 123)#
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

[no] stream <stream-id>

Enter or end 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)#
2

[no] ip destination address <ip-address>

Set or remove a stream


destination IP address.

Where:
Casa CMTS Software Configuration Guide

313

CASA CMTS

<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
CASA-CMTS(config-stream 123)#
Remove the configured destination IP address for stream 123:
CASA-CMTS(config-stream 123)# no ip
destination address
CASA-CMTS(config-stream 123)#

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>

Stream ID in the range 1 to 9999.

Example:
CASA-CMTS(config)# stream 123
CASA-CMTS(config-stream 123)#
[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
CASA-CMTS(config-stream 123)#
Example:
Remove the configured source UDP port for stream 123:
CASA-CMTS(config-stream 123)# no udp source
port
CASA-CMTS(config-stream 123)#

Casa CMTS Software Configuration Guide

314

CASA CMTS

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>

Stream ID in the range 1 to 9999.

Example:
CASA-CMTS(config)# stream 123
CASA-CMTS(config-stream 123)#
udp destination port <destination-port>
Where:
<destination-port>

Set or remove stream


destination UDP port.

Destination UDP port number in the


range 1 to 9999.

Example:
Set source UDP port for stream 123 to 4321:
CASA-CMTS(config-stream 123)# udp destination
port 4321
CASA-CMTS(config-stream 123)#
Remove the configured destination UDP port for stream 123:
CASA-CMTS(config-stream 123)# no udp
destination port
CASA-CMTS(config-stream 123)#

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
------------------------------------------------Casa CMTS Software Configuration Guide

315

CASA CMTS

ip source address is
ip destination address is
udp source port is
udp destination port is
Dejitter buffer is
millisecond

wildcard
wildcard
wildcard
3014
400

Show the configuration of all configured streams:


CASA-CMTS(config)# show stream config
stream configuration:
stream 1
ip source address is
wildcard
ip destination address is
wildcard
udp source port is
wildcard
udp destination port is
3001
Dejitter buffer is
400
millisecond
stream 2
ip source address is
ip destination address is
udp source port is
udp destination port is
Dejitter buffer is
millisecond

stream 14
ip source address is
ip destination address is
udp source port is
udp destination 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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>

Module number

Casa CMTS Software Configuration Guide

316

CASA CMTS

QAM port number

<port>
Example:

Enter QAM Interface mode for interface on module 0, port 2:

CASA-CMTS(config)# interface qam 0/2


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:
CASA-CMTS(config-if-qam)# channel 1 stream 123
program 100
CASA-CMTS(config-if-qam)#
Bind the MPTS stream 223 to QAM channel 0 on port 0/0:
CASA-CMTS(config-if-qam)# channel 0 stream 223
pass-through
CASA-CMTS(config-if-qam)#
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

Casa CMTS Software Configuration Guide

317

CASA CMTS

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

Command (config)

Purpose

CASA-CMTS(config)# operation mode group-4 port

Enter operation mode.

CASA-CMTS(config)# interface gige 3

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)# interface qam 0/0


CASA-CMTS(config-if-qam0/0)# ip add a.b.c.d
<mask>

Assign an IP address to
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.

Casa CMTS Software Configuration Guide

318

CASA CMTS

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 bandwidth
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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number.
QAM port number.

Example:

Enter QAM Interface mode for interface on module 0, port 0:


CASA-CMTS(config)# interface qam 0/0
CASA-CMTS(config-if-qam)#

Casa CMTS Software Configuration Guide

319

CASA CMTS

Ending QAM interface configuration mode


To end QAM interface mode:
Step
1

Command (config)

Purpose

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number
QAM port number

Example:

Enter QAM Interface mode for interface on module 0, port 0:

CASA-CMTS(config)# interface qam 0/0


CASA-CMTS(config-if-qam)#
end

End QAM interface


mode.

Example:

CASA-CMTS(config-if-qam 0/0)# end


CASA-CMTS(config)#

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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number.
QAM port number.

Example:

Enter QAM Interface mode for interface on module 0, port 0:

CASA-CMTS(config)# interface qam 0/0


CASA-CMTS(config-if-qam)#
no shutdown

Enable a QAM port.

Example:

Enable QAM port 0 on module 0:


CASA-CMTS(config-if-qam)# no shutdown
CASA-CMTS(config-if-qam)#
Casa CMTS Software Configuration Guide

320

CASA CMTS

Disabling QAM output port


To disable a QAM port:
Step
1

Command (config)

Purpose

interface qam <module>/<port>

Enter QAM interface


Mode

Where:
<module>
<port>

Module number.
QAM port number.

Example:

Enter QAM Interface mode for interface on module 0, port 0:

CASA-CMTS(config)# interface qam 0/0


CASA-CMTS(config-if-qam)#
shutdown

Enable a QAM port.

Example:

Enable QAM port 0 on module 0:


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)#
interface qam <module>/<port>
Where:
<module>
<port>

Enter QAM interface


mode.

Module number.
QAM port number.

Example:
Enter QAM Interface mode for interface on module 1, port 3:

CASA-CMTS(config)# interface qam 1/3


CASA-CMTS(config-if-qam 1/3)#
no channel <chan-id> shutdown
Where:
<chan-id>

Enable a QAM channel.

QAM channel number; valid values are 0

Casa CMTS Software Configuration Guide

321

CASA CMTS

through 3.
Example:
Enable QAM channel 1 on module 1, port 3:
CASA-CMTS(config-if-qam 1/3)# no channel 1
shutdown
CASA-CMTS(config-if-qam 1/3)#

Disabling QAM output channels


To disable a QAM channel follow the command below:
Step
1

Command (config)

Purpose

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number.
QAM port number.

Example:
Enter QAM Interface mode for interface on module 0, port 2:
CASA-CMTS(config)# interface qam 0/2
CASA-CMTS(config-if-qam 0/2)#
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
CASA-CMTS(config-if-qam 0/2)#

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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number.
QAM port number.

Casa CMTS Software Configuration Guide

322

CASA CMTS

Example:
Enter QAM Interface mode for interface on module 1, port 2:
CASA-CMTS(config)# interface qam 1/2
CASA-CMTS(config-if-qam 1/2)#
2

[no] ip address <ip-address> <subnet-mask>


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)#
CASA-CMTS(config-if-qam 1/2)# no ip address
CASA-CMTS(config-if-qam 1/2)#

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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number.
QAM port number.

Example:
Enter QAM Interface mode for interface on module 1, port 2:
CASA-CMTS(config)# interface qam 1/2
CASA-CMTS(config-if-qam 1/2)#
2

mac address <mac-address>


Where:
<mac-address>

Set or remove the QAM


port default MAC
address.

MAC address in format xxxx.xxxx.xxxx.

Casa CMTS Software Configuration Guide

323

CASA CMTS

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
CASA-CMTS(config-if-qam)#
Return to the manufacturers built-in MAC
address:
CASA-CMTS(config-if-qam)# no mac address
CASA-CMTS(config-if-qam)#

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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>

Module number.

<port>

QAM port number.

Example:
Enter QAM Interface mode for interface on module 0, port 3:

CASA-CMTS(config)# interface qam 0/3


CASA-CMTS(config-if-qam 0/3)#
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.

Casa CMTS Software Configuration Guide

324

CASA CMTS

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

interface qam <module>/<port>

Enter QAM
interface
mode.

Where:
<module>
<port>

Module number.
QAM port number.

Example:

Enter QAM Interface mode for interface on module 0, port 2:

CASA-CMTS(config)# interface qam 0/2


CASA-CMTS(config-if-qam 0/2)#
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


CASA-CMTS(config-if-qam 0/2)#
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

Casa CMTS Software Configuration Guide

325

CASA CMTS

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
CASA-CMTS(config-if-qam 0/2)#
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.
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

interface qam <module>/<port>

Enter QAM
interface mode

Where:
<module>
<port>

Module number
QAM port number

Example:

Enter QAM Interface mode for interface on module 0, port 3:


CASA-CMTS(config)# interface qam 0/3
CASA-CMTS(config-if-qam 0/3)#
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
Casa CMTS Software Configuration Guide

326

CASA CMTS

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
CASA-CMTS(config-if-qam 0/3)#
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:
Step
1

Command (config)

Purpose

interface qam <module>/<port>

Enter QAM
interface mode.

Where:
<module>
<port>

Module number.
QAM port number

Example:
Enter QAM Interface mode for interface on module 0, port 3:

CASA-CMTS(config)# interface qam 0/3


CASA-CMTS(config-if-qam 0/3)#
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:
Casa CMTS Software Configuration Guide

327

CASA CMTS

Set the output power level for RF port 0/2 to 550:


CASA-CMTS(config-if-qam 0/2)# power 550
CASA-CMTS(config-if-qam 0/2)#
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:
60 dBmV at 1-channel/port
56 dBmV at 2-channels/port
52 dBmV at 4-channels/port
49 dBmv at 8-channels/port
The CMTS configuration allows adjustment and override of QAM power output levels based on
real measurements. Because an actual power level may vary +/- 1dB, the power setting may be
adjusted either higher or lower to compensate for the actual reading. If the actual reading is 1dB
lower, then the QAM power setting in the CLI can be increased by 1dB.
Note: Both DOCSIS and Casa Systems specify the maximum QAM power level for four channels
at 580 (58 dBmV). However, the Casa CMTS allows you to override the setting to 590. This
setting may occasionally cause bit errors or a slight increase in adjacent channel distortion.
Some customers find this an acceptable trade-off if they need to overcome a highly attenuated
cable plant. But unless such an overdrive is necessary, Casa recommends not exceeding
the 580 setting.
In summary, setting the QAM power level higher than 580 is not recommended unless:
1) A measurement shows the actual CMTS output is slightly lower than what is requested in CLI,
or
2) A determination is made that the cable plant is highly attenuated, and the only solution is to
force the CMTS to overdrive its output level (as opposed to removing attenuation in the cable
plant).

Setting the QAM interleave level


To set the interleave level for a QAM channel on a port:
Step
1

Command (config)

Purpose

interface qam <module>/<port>

Enter QAM interface


mode

Where:
<module>

Module number.

Casa CMTS Software Configuration Guide

328

CASA CMTS

<port>

QAM port number.

Example:
Enter QAM Interface mode for interface on module 0, port 3:

CASA-CMTS(config)# interface qam 0/3


CASA-CMTS(config-if-qam 0/3)#
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
CASA-CMTS(config-if-qam)#
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

interface qam <module>/<port>

Enter QAM interface


mode.

Where:
<module>
<port>

Module number.
QAM port number.

Example:
Enter QAM Interface mode for interface on module 0, port 3:
CASA-CMTS(config)# interface qam 0/3
CASA-CMTS(config-if-qam 0/3)#
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 Software Configuration Guide

329

CASA CMTS

CASA-CMTS(config-if-qam 0/3)# no spectral


inversion on

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_slot>/<port> [brief]

Show configurations and


stream status for the
specified QAM port
interface.

Where:
<module_slot>

Module number.

<port>

QAM port number.

[brief]

Optional. Show only the interface


configurations.

Example:
CASA-CMTS(config) show interface qam 2/1 brief

To show the configurations of a QAM channel and the stream bonded to it:
Step
1

Command (config)

Purpose

show interface qam <module_slot>/<port> channel <ch-id>


stream <number>

Show the
configurations of a
QAM channel and
the bonded
stream.

Where:
<module_slot>

Module number.

<port>

QAM port number.

<ch-id>

QAM channel number 0 to 3.

<number>

Stream identifier.

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:
Casa CMTS Software Configuration Guide

330

CASA CMTS

To show the utilization rates of all downstream channels:


Step Command (config)
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


utilization
Downstream Slot/Port/Channel
Utilization (%)
2/0/0
2
2/0/1
2
2/0/2
2
2/0/3
2
2/1/0
0
2/1/1
0
2/1/2
0
2/1/3
0
2/2/0
0
2/2/1
0
2/2/2
0
2/2/3
0
2/3/0
0
2/3/1
0
2/3/2
0
2/3/3
0

Displaying QAM downstream channel sets


To display all downstream channel sets or to display the downstream channel set count:
Step Command (config)
Purpose
1

show downstream channel set [ | count-only /]


Examples:
C10G(config)# show downstream channel set
MAC
Chan Channel
ID
Set
List
1
1 0/0/0
1
2 0/0/1
1
3 0/0/2
1
4 0/0/3
1
5 0/0/4
1
6 0/0/5
1
7 0/0/6
1
8 0/0/7
1
256 0/0/0, 0/0/1, 0/0/2, 0/0/3, 0/0/4
2
1 0/1/8
2
2 0/1/9
2
3 0/1/10

Casa CMTS Software Configuration Guide

Displays
downstream
channel set
details by
MAC ID,
channel set
number, and
channel list.

331

CASA CMTS

2
2
2
2
2
2

4
5
6
7
8
256

0/1/11
0/1/12
0/1/13
0/1/14
0/1/15
0/1/8, 0/1/9, 0/1/10, 0/1/11, 0/1/12

To display the channel set count only:


C10G(config)#show downstream channel set | count-only /
Count Line: 72
C10G(config)#

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.

About upstream interface configurations


When configuring upstream interfaces, each interface is defined using the following information in
the format:
module_slot_number/port_number.physical_channel_number/logical_channel_number
Where:
module slot number Is the number of the CMTS system slot where the upstream module
reside.
port number Is the port number on the upstream module. For example, a 16-port
upstream module on the C10G CMTS platform has port numbers in the range 0 to15.
physical channel number is the physical channel number, where each channel is
comprised of two logical channels, 0 and 1.
The following format applies to the upstream interface in system slot 11, where physical channel
0 is represented by 11/0.0/0 and 11/0.0/1, and physical channel 1 is represented by 11/0.1/0 and
11/0.1/1 . The following CLI session shows the upstream channel format when show upstream
command is executed on a C10G CMTS.
C10G-CMTS(config-if-ups 11/0.1)#show upstream
upstream channel
burst noise rate (events/sec)
11/0.0/0
0.0
11/0.0/1
0.0
11/0.1/0
0.0
11/0.1/1
0.0

Casa CMTS Software Configuration Guide

332

CASA CMTS

Multiple upstream logical channels, dynamic channel width


switching, independent power levels
Release 6.1.3 supports dynamic channel width switching between logical upstream channels (0
and 1) using the same center frequency. This feature allows legacy D1.x modems to transmit
upstream at 3.2 MHz over one logical channel, while the second logical channel is available for
D2.0 (and later) modems to transmit upstream at 6.4 MHz.
Time-division multiplexing provides the switching between the logical channels, with modem
upstream transmission taking place over one logical channel at a time. Supported upstream
channel widths per upstream logical channel are configurable at .2, .4, .8, 1.6, 3.2, and 6.4 MHz.
Depending on the configured upstream channel width, a logical channel provides an SNR
increase for higher QAM modulation, a reduction of integrated noise, and an increase in total
bandwidth for improved efficiency within the same spectrum. For example, by dividing one 6.4
MHz logical channel in half, SNR increases by 3dB.
The follow CLI session shows an example upstream interface configuration with the logical
channels (in bold text) set at frequencies for modems operating on this interface. Logical channel
0 is set 6.4 MHz, and logical channel 1 is set at 3.2 MHz. The CMTS dynamically performs TDM
switching between the logical channels when the CMTS sends upstream transmission grants to
the modems. Channel selection is based on the requirements of the requesting modem.
C10G(config-if-ups 13/0.0)# show interface upstream 13/0
interface upstream 13/0.0
spectrum-rule 35
frequency 5000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
ingress-cancellation 100
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 6400000
logical-channel 0 profile 4
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 4
logical-channel 1 minislot 8
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
logical-channel 1 pre-equalization
Casa CMTS Software Configuration Guide

333

CASA CMTS

logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
no logical-channel 1 shutdown
no shutdown
In addition to the dynamic channel width switching between the logical channels, an upstream
power-offset level setting (relative to the physical channel power) may be configured
independently on each logical channel in the range -10 dBto 10 dB.

Entering the upstream port interface configuration mode


To enter upstream port interface configuration mode:
Step
1

Command

Purpose

config

Enter
configuration
mode.

Example:

CASA-CMTS#config
CASA-CMTS(config)#
interface upstream <module_slot_num>/<port_num>
Where:
<module_slot_num>

<port_num>

Specifies the system slot number


where the upstream module is
installed.

Enter upstream
port interface
configuration
mode.

Specifies the upstream port 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)#
Casa CMTS Software Configuration Guide

334

CASA CMTS

Enabling upstream ports


To enable an upstream port, use the following command:
Step
1

Command (config)

Purpose

interface upstream <module_slot_num>/<port_num>

Enter
upstream port
interface
configuration
mode.

Where:
<module_slot_num>
<port_num>

Specifies the system slot number where the


upstream module is installed.
Specifies the upstream port 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)#
no shutdown

Enable an
upstream port.

Example:
Enable upstream port 7 on module 3:
CASA-CMTS(config-if-ups 3/7)# no shutdown
CASA-CMTS(config-if-ups 3/7)#

Disabling upstream ports


To disable an upstream port:
Step
1

Command (config)

Purpose

interface upstream <module_slot_num>/<port_num>

Enter
upstream port
interface
configuration
mode.

Where:
<module_slot_num>
<port_num>

Specifies the system slot number where the


upstream module is installed.
Specifies the upstream port 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)#
2

shutdown

Casa CMTS Software Configuration Guide

Disable an
upstream port.
335

CASA CMTS

Example:
Disable upstream port 7 on module 3:
CASA-CMTS(config-if-ups 3/7)# shutdown
CASA-CMTS(config-if-ups 3/7)#

Entering an upstream logical interface description


To enter a description of the upstream port interface:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 1 on module 2:
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

description <string>
logical-channel <number> description <string>
Where:
<string>

<number>

Specify a text
description of the
upstream port
interface.

Specifies the text string to describe the


upstream port interface. Up to 64
characters may be specified. If the
string has embedded blank spaces,
then the string must be within quotation
marks ( ).
Specifies the logical channel number,
either 0 or 1, under the current physical
port.

Example:
Enter a text a description of the upstream port interface 11/0.0.
Casa CMTS Software Configuration Guide

336

CASA CMTS

CASA-CMTS(config-if-ups 11/0.0)# description This


is a text string within quotation marks.
CASA-CMTS(config-if-ups 11/0.0)#logical channel 1
description This is a sample string.

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 brief
interface upstream 4/0.0
frequency 20000000
channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
no logical-channel 0 shutdown
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 shutdown
no shutdown
interface upstream 4/0.1
frequency 24000000
channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
no logical-channel 0 shutdown
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 shutdown
no shutdown
interface upstream 4/1.0
frequency 20000000
channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
no logical-channel 0 shutdown
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 shutdown
shutdown

Casa CMTS Software Configuration Guide

337

CASA CMTS

To show configurations of all upstream port interfaces in a module:


Step
1

Command (config)

Purpose

show interface upstream <module_slot_num>

Show
configurations of
all upstream port
interfaces in the
specified module
slot.

Where:
<module_slot_num>

Specified the slot number containing


the upstream module.

Example:

See example below.

Example: Showing upstream port interface configurations


CASA-CMTS# show interface upstream 4
interface upstream 4/0.0
frequency 20000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
no shutdown
interface upstream 4/0.1
frequency 24000000
channel-width 3200000
power-level 0
Casa CMTS Software Configuration Guide

338

CASA CMTS

power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
no shutdown

interface upstream 4/0.1


frequency 24000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
no shutdown
interface upstream 4/1.0
frequency 20000000
Casa CMTS Software Configuration Guide

339

CASA CMTS

channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
shutdown
interface upstream 4/1.1
frequency 20000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
Casa CMTS Software Configuration Guide

340

CASA CMTS

logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
shutdown

Displaying upstream interface status


To show the status of an upstream interface:
Step
1

Command (config)

Purpose

show interface upstream


<module_slot_num>/<port_num>.<physical_channel_num> [brief |
current | port | stat]

Show the
status of an
upstream
interface
with filtering
options.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port number.

<physical_channel_num>

Specifies the physical channel number,


either 0 or 1. The default physical
channel is 0 if not specified.

brief

Optional. Filters the show interface


upstream output to display only critical
statistics.

current

Optional. Filters the show interface


upstream output to display the current
configuration.

stat

Optional. Filter the show interface


upstream output to display upstream
traffic statistics associated with the
specified slot and port number.

Examples:
Display the upstream interface in slot 4, port 0:
CASA-CMTS(config)# show interface upstream 4/0
frequency 20000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
Casa CMTS Software Configuration Guide

341

CASA CMTS

logical-channel 0 channel-width 3200000


logical-channel 0 profile 2
logical-channel 0 minislot 2
logical-channel 0 data-backoff automatic
logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
no shutdown
Display the brief description of upstream slot 4, port 0:
C3000-230(config)#show interface upstream 4/0 brief
interface upstream 4/0.0
frequency 20000000
channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
no logical-channel 0 shutdown
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 shutdown
no shutdown
C3000-230(config)#
Display the current configuration of upstream slot 4, port 0:
C3000-230(config)#show interface upstream 4/0 current
interface upstream 4/0.0
frequency 20000000
channel-width 3200000
power-level 0
power-adjustment continue 2
power-adjustment threshold 1
voice-bw-reserve 75 emergency 0
rate-limit
no ingress-cancellation
logical-channel 0 prov-attr-mask 0x0
logical-channel 0 channel-width 3200000
logical-channel 0 profile 2
logical-channel 0 minislot 2
Casa CMTS Software Configuration Guide

342

CASA CMTS

logical-channel 0 data-backoff automatic


logical-channel 0 ranging-backoff 0 4
no logical-channel 0 pre-equalization
logical-channel 0 power-offset 0
logical-channel 0 ranging-priority 0x0
logical-channel 0 class-id 0x0
no logical-channel 0 shutdown
logical-channel 1 prov-attr-mask 0x0
logical-channel 1 channel-width 3200000
logical-channel 1 profile 2
logical-channel 1 minislot 2
logical-channel 1 data-backoff automatic
logical-channel 1 ranging-backoff 0 4
no logical-channel 1 pre-equalization
logical-channel 1 power-offset 0
logical-channel 1 ranging-priority 0x0
logical-channel 1 class-id 0x0
logical-channel 1 shutdown
no shutdown
C3000-230(config)#
Display upstream slot 4, port 0 traffic statistics.
C3000-230(config)#show interface upstream 4/0 stat
Interface upstream 4/0.0 statistics
Admin status: UP
Received 12 broadcasts, 5 multicasts, 23641
unicasts
0 discards, 2472 errors, 0 unknown protocol
87074 Unerrored, 0 Corrected, 0 Uncorrectables
Total Modems On This Upstream Channel: 2 ,2 active
cm,0 secondary cm
Req Mslots 3499886425, Used Req Mslots 71064
Init Mtn Mslots 281230167, Used Init Mtn Mslots 0
Total Mslots 3782191073, Ucast Granted Mslots
1074417
Avg upstream channel utilization: 0
Channel utilization interval: 1
Last clearing of interface stat: never

Setting the upstream logical channel frequency


Channel frequency is an upstream port parameter. To set the upstream logic channel frequency:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

Casa CMTS Software Configuration Guide

343

CASA CMTS

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 1 on module 2:
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

Set the logicalchannel channelfrequency.

frequency <frequency_num>
Where:
<frequency_num>

Specifies the channel frequency in the


range 5 MHz to 65 MHz. Type the
frequency using the actual units in the
range 5000000 to 65000000.

Example:
Set frequency to 10,000,000 Hz for upstream port 11/0 on logical
port 0:
CASA-CMTS(config-if-ups 11/0.0)# frequency
10000000
CASA-CMTS(config-if-ups 11/0.0)#

Setting the upstream logical channel width


To set the upstream logical channel width
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Casa CMTS Software Configuration Guide

344

CASA CMTS

Example:
Enter upstream interface mode for upstream port 1 on module 2:
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

channel-width <width_in_hertz>
logical-channel <number> channel-width <width_in_hertz>
Where:
<width_in_hertz>

<number>

Set the logicalchannel channelwidth.

Specifies the channel width in hertz. .


Type the channel width using the actual
units. Valid values are 200000, 400000,
800000, 1600000, 3200000, and
6400000, where 6400000 is 6.4 MHz.
Specifies the logical channel number,
either 0 or 1, under the current physical
port.

Example:
Set the channel-width to 3.2 MHz for upstream port 11/0 on logical
port 0:
CASA-CMTS(config-if-ups 11/0.0)# channel-width
3200000
CASA-CMTS(config-if-ups 11/0.0)#

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 <milliseconds>

Change the
upstream MAP
size.

Where:
<milliseconds>

Species the map size in the range 2 to 10


milliseconds. The default is map size is 5 ms.
Casa recommends using the default value.

Example:

Enter upstream
CASA-CMTS(config)# upstream map-size 6

Casa CMTS Software Configuration Guide

345

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:
Step Command (config)
Purpose
1

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>
Where:
<module_slot_num>

Enter upstream
port interface
configuration
mode.

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.

CASA-CMTS(config)# interface upstream 11/0


CASA-CMTS(config-if-ups 11/0.0)#
power-level <level>
Where:
<level>

Set the upstream


input power level.

Specifies the 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 11/0.0:
CASA-CMTS(config-if-ups 11/0.0)# 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
degrade 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
Casa CMTS Software Configuration Guide

346

CASA CMTS

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
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

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

power-adjustment threshold <level>


Where:
<level>

Adjust the
upstream input
power threshold

Specifies the upstream input power adjustment


threshold in dBmV. The default setting is 1 dBmV.
The valid range is 0 to 2 dBmV.

Example:
Set the power adjustment level to 1 dBmV.
CASA-CMTS(config-if-ups 11/0.0)# power-adjustment
threshold 2
CASA-CMTS(config-if-ups 11/0.0)#
Casa CMTS Software Configuration Guide

347

CASA CMTS

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

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

power-adjustment continue <level>


Where:
<level>

Adjust the
upstream input
power level.

Specifies the upstream input power adjustment 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
Casa CMTS Software Configuration Guide

348

CASA CMTS

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
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

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Casa CMTS Software Configuration Guide

349

CASA CMTS

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

[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>

static
<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 lookahead time in MAPs to account for inaccuracies of
the measurement system and internal software
latencies. The max-delay valid range is 200 to 2000
microseconds, with a default of 1000.
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.
The max-delay specifies the maximum round trip
delay between the CMTS and the most-distant
cable modem 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:
CASA-CMTS(config-if-ups 11/0.0)# map-advance dynamic
400
CASA-CMTS(config-if-ups 11/0.0)#
Defaults: Dynamic map-advance with a safety factor of 1000 microseconds and a max-delay of
1800 microseconds.

Casa CMTS Software Configuration Guide

350

CASA CMTS

Enabling the upstream logical-channels


To enable an upstream logical-channel:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter the
upstream port
interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

no logical-channel <number> shutdown


Where:
<number>

Enables the
upstream logical
channels.

Specifies the logical channel number, either 0 or


1, under the current physical port.

Example:
Enable logical-channel 0 under upstream 11/0.0:
CASA-CMTS(config-if-ups 11/0.0)# no logical-channel
0 shutdown

Disabling the upstream logical-channels


To disable an upstream logical-channel:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
Casa CMTS Software Configuration Guide

351

CASA CMTS

<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> shutdown


Where:
<number>

Disable upstream
logical channels.

Specifies the logical channel number, either 0 or


1, under the current physical port.

Example:
Disable logical-channel 0 under upstream 11/0.0:
CASA-CMTS(config-if-ups 2/6)# logical-channel 0
shutdown

Setting upstream channel data and ranging 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 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 backoff values of 4 and 10.

Casa CMTS Software Configuration Guide

352

CASA CMTS

To set data-backoff values, use the following command:


Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> data-backoff {<start_value>


<end_value > | automatic}
Where:
<number>

Set upstream
channel backoff
values.

Specifies the logical channel number, either 0


or 1, under the current physical port.

automatic

Specifies automatic data backoff adjustment

<start_value>

Specifies the data backoff start value in the


range 0 to 15. The default value is 0.

<end_value>

Specifies the data backoff end value in the


range 0 to 15. The default value is 4.

Example:
Set data-backoff range to 2 and 8 for logical channel 0 on interface
11/0.
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
data-backoff 2 8

Casa CMTS Software Configuration Guide

353

CASA CMTS

To set data-backoff values to the default values of 0 and 4:


Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> data-backoff {<start_value>


<end_value > | automatic}
Where:
<number>

Set data-backoff
values to the
default values of 0
and 4.

Specifies the logical channel number, either 0


or 1, under the current physical port.

automatic

Specifies automatic data backoff adjustment

<start_value>

Specifies the data backoff start value in the


range 0 to 15. The default value is 0.

<end_value>

Specifies the data backoff end value in the


range 0 to 15. The default value is 4.

Example:
Set upstream data backoff to default values 0 and 4 for channel 0:
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
data-backoff 0 4

Casa CMTS Software Configuration Guide

354

CASA CMTS

To set ranging-backoff values:


Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> ranging-backoff <start_value>


<end_value>
Where:
<number>

Specifies the logical channel number, either 0 or


1, under the current physical port.

<start_value>

Specifies the ranging backoff start value; valid


values are 0 to 15.

<end_value>

Specifies the ranging backoff end value; valid


values are 0 to 15.

Set rangingbackoff values on


the specified
upstream logical
channel.

Example:
Set ranging-backoff to 4 and 10 (recommended) for logical channel
0 on upstream 11/0:
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
ranging-backoff 4 10
CASA-CMTS(config-if-ups 11/0.0)#
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.
Casa CMTS Software Configuration Guide

355

CASA CMTS

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.

Configuring the ranging hold-off priority bit


To set the ranging hold-off TLV:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> ranging-priority <value>


Where:
<number>
<value>

Specifies the logical channel number, either 0 or


1, under the current physical port.

Set the ranging


hold-off priority
value on the
specified upstream
logical channel.

Specifies the ranging hold-off priority value in the


range 0x0 to 0x0FFFFFFFF. Setting the value to
0x0 disables the ranging hold-off TLV.

Example:
Casa CMTS Software Configuration Guide

356

CASA CMTS

Set ranging-priority to 0x0 on logical channel 0 on upstream 11/0.0:


CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
ranging-backoff 4 10
CASA-CMTS(config-if-ups 11/0.0)#

Setting the upstream channel mini-slot size


To set the upstream minislot size:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> minislot <size>


Where:
<number>
<size>

Set the upstream


channel mini-slot
size.

Specifies the logical channel number, either 0 or 1,


under the current physical port.
Specifies the minislot size in ticks. Value values ae
1, 2, 4, 8, 16, 32, 64, and 128.

Example:
Set the minislot size to 64 ticks for logical channel 0 on module 11,
port 0:
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
minislot 64

Casa CMTS Software Configuration Guide

357

CASA CMTS

Enabling the upstream channel class identifier


The upstream channel class-id parameter enables the ranging hold-off UCD Type-19 TLV.
To specify the upstream logical channel class identifier:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

[no] logical-channel <number> class-id <identifier>


Where:
<number>
<identifier>

Set the logical


channel class
identifier.

Specifies the logical channel number, either 0 or 1,


under the current physical port.
Specifies the UCD Type 19 TLV ranging hold-off bit
field identifier in the range 0x0-0xFFFFFFFF.
Specifing 0x0 disables the identifier.

Example:
To enable the class identifier for logical channel 0 on upstream
channel 11/0.0.
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
class-id 0xFFFFFFFF
CASA-CMTS(config-if-ups 11/0.0)#

Casa CMTS Software Configuration Guide

358

CASA CMTS

Setting the upstream channel S-CDMA frame interval


Synchronous-Code Division Multiple Access (S-CDMA) in DOCSIS 3.0 improves the maximum
upstream bandwidth by allowing the same physical upstream channel to receive multiple burst
simultaneously using a time and code data transmission technique. Multiple modems can send
simultaneously using their own codes in the same upstream time slot without interfering with each
other. Data is sent using up to 128 spreading codes.
To set the Synchronous-Code Division Multiple Access (SCDMA) frame settings on an upstream
port interface:
Step Command (config)
Purpose
1

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>
Where:
<module_slot_num>

Enter upstream
port interface
configuration
mode.

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> frame <interval>


<codes_per_minislot> <active_codes>
Where:
<number>

Set the upstream


channel S-CDMA
frame interval.

Specifies the logical channel


number, either 0 or 1, under the
current physical port.

<interval>

Specifies the maximum number of


spreading intervals per frame in the
range 1 to 32.

<codes_per_minislot>

Specifies the maximum number of


codes per minislot in the range 2 to
32.

<active_codes>

Specifies the maximum number of


active codes in the range 64 to 128.

Casa CMTS Software Configuration Guide

359

CASA CMTS

Example:
Set the upstream channel S-CDMA frame interval on upstream port
interface 11/0.0 :
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
frame 24 12 64

Assigning modulation profiles to an upstream interface


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. Primary and secondary
modulation profiles are supported.
To set the primary and optional secondary modulation profile:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

logical-channel <number> profile <profile_id> secondary-profile


<string>
Where:
<number>

Set the upstream


channel
modulation profile.

Specifies the logical channel number, either 0 or


1, under the current physical port.

<profile_id>

Specifies the primary modulation profile identifier


in the range 1 to 64.

<string>

Specifies the name of the optional secondary


profile. Note that the secondary profile is not

Casa CMTS Software Configuration Guide

360

CASA CMTS

supported on logical channel 1.


Example:
Set modulation-profile to profile 2 on upstream channel 11/0.0/0
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
profile 2
CASA-CMTS(config-if-ups 11/0.0)#
Note: When specifying a secondary profile, both the primary and secondary profiles must match
the upstream channel type. CSM will not change to a mismatched profile. The secondary profile
also has to be less bandwidth-efficient than the primary profile.
When plant signal quality deterioration causes threshold hits, CSM changes to the secondary
modulation profile. The show running-config command will show the transit configuration using
the secondary-profile.
When signal quality satisfies primary profiles SNR plus 3dB (or to the default SNR threshold if
the threshold is not defined in the rule), CSM changes modulation profile back to the primary.

Specifying multiple secondary profiles to an upstream interface


Multiple 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 11/0.0)# 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, and 33 specifies the priority which CSM tries to use the profiles.
3. Lower priority suggests a less bandwidth efficient modulation profile.

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

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration

Casa CMTS Software Configuration Guide

361

CASA CMTS

Where:
<module_slot_num>

mode.
Specifies the system slot number
where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

[no] logical-channel <number> pre-equalization


Where:
<number>

Set the upstream


channel preequalization.

Specifies the logical channel number, either 0 or 1,


under the current physical port.

Example:
To enable pre-equalization for logical channel 0 on upstream
channel 11/0.0/0.
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
pre-equalization
CASA-CMTS(config-if-ups 11/0.0)#
To disable pre-equalization for logical channel 0 on upstream
channel 11/0.0.
CASA-CMTS(config-if-ups 11/0.0)# no logicalchannel 0 pre-equalization
CASA-CMTS(config-if-ups 11/0.0)#

Setting the provisioned attribute mask


DOCSIS 3.0 povisioned attribute masks allow assigning of service flows to channels or channel
bonding groups using binary attributes. These attributes are either user-defined or specificationdefined. The default is 0x0.

Casa CMTS Software Configuration Guide

362

CASA CMTS

To set the provisioned attribute mask on an upstream port interface:


Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.

CASA-CMTS(config)# interface upstream 11/0


CASA-CMTS(config-if-ups 11/0.0)#
logical-channel <number> prov-attr-mask <value>
logical-channel <number> prov-attr-mask [bonding |
highavailability | lowlatency]
Where:
<number>

Set the upstream


channel
provisioned
attribute mask.

Specifies the logical channel


number, either 0 or 1, under the
current physical port.

<value>

Specifies a user-defined provisioned


attribute mask value in the range
0x0-0xFFFFFFFF. The default is
0x0.

<bonding>

Specifies the upstream channel


bonding attribute mask. This bit is 0
for channel interfaces; bit 1 for
channel bonding groups.

<highavailability>

Specifies the highavailability


provisioned attribute mask. The bit
is set to 0 for all channels and is
defined by the user.

<lowlatency>

Specifies the lowlatency provisioned


attribute mask. The bit is set to 0 for
all channels and is defined by the
user.

Casa CMTS Software Configuration Guide

363

CASA CMTS

Example:
Set the provisioning attribute mask on upstream port interface
11/0.0::
CASA-CMTS(config-if-ups 11/0.0)# logical-channel 0
prov-attr-mask

Enabling/disabling ingress noise cancellation


The default state is disabled. To enable ingress noise cancellation follows the command below:
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

[no] ingress-cancellation <interval>


Where:
<interval>

Enable or disable
ingress noise
cancellation.

Specifies the 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)#ingress-cancellation
100

Casa CMTS Software Configuration Guide

364

CASA CMTS

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.
To configure the voice bandwidth reserve percentage:
Step Command (config)
1

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>
Where:
<module_slot_num>

Purpose
Enter upstream
port interface
configuration
mode.

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

voice-bw-reserve <percentage> [emergency <percentage>]


Where:
<percentage>

emergency
<percentage>

Specifies the percentage of total bandwidth on


the current channel that is reserved for voice
calls. The valid range 0 to 100 percent. The
default is setting is 75 percent.
The percentage of total bandwidth on the
current channel that is reserved for emergency
calls. The valid range is 0 to 100 percent. The
default setting is 0 percent.

Specify reserve
bandwidth
percentage for
upstream voice
calls.

Example:
In the following example, 75% of the bandwidth on upstream
interface 11/0.0 is reserved for voice calls, with 10% of that
percentage available for emergency calls. The remaining 25%
Casa CMTS Software Configuration Guide

365

CASA CMTS

bandwidth is available for data and video traffic.


CASA-CMTS(config-if-ups 11/0.0)#voice-bw-reserve
75 emergency 10
CASA-CMTS(config-if-ups 3/6)#

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.

Configuring the QoS traffic bandwidth reserve percentage


To configure the percentage of total available reserved-resource bandwidth dedicated for QoSprofiled traffic on upstream channels, use the qos bw-reserve parameter. When the configured
percentage threshold is reached, no new QoS-profiled traffic is accepted on that channel. Any
unused portion of the configured percentage will be available for data sessions. However, new
QoS calls will assume priority and preempt any data sessions.
If an upstream service flow request exceeds the total bandwidth available, the CMTS will either
accept, reject, or DCC the service flow request.
To configure the QoS-profiled traffic bandwidth reserve percentage:
Step Command (config)
1

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>
Where:
<module_slot_num>

Purpose
Enter upstream
port interface
configuration
mode.

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

qos bw-reserve <percentage>

Casa CMTS Software Configuration Guide

Specify reserve
bandwidth
366

CASA CMTS

Where:
<percentage>

Specifies the percentage of total bandwidth on


the current channel that is reserved for QoS
traffic. The valid range 0 to 99 percent. The
default is setting is 95 percent.

percentage for
QoS-profiled
traffic.

Example:
In the following example, 80% of the bandwidth on upstream
interface 11/0.0 is reserved for QoS traffic.
CASA-CMTS(config-if-ups 11/0.0)#qos bw-reserve 80
CASA-CMTS(config-if-ups 11/0.0)#

Related bandwidth reserve parameters


Reserved bandwidth on both upstream and downstream QAM interfaces can be specified globally
as a percentage with the cable qos bw-reserve command. To override the downstream global
setting on a per-channel basis, specify the percentage with the interface channel <identifier>
qos bw-reserve <percentage>.
Whenever the requested bandwidth is exceeded on either upstream or downstream interfaces,
specify the action (accept, reject, or DCC) using the cable qos bw-reserve exceed parameter.

Applying spectrum rules to upstream channels


To apply a previously-configured spectrum-rule to a service flow over an upstream channel, use
the spectrum-rule command. Refer to the section, Spectrum management, for information on
configuring rules.
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.
Step
1

Command (config)

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream
port interface
configuration
mode.

Casa CMTS Software Configuration Guide

367

CASA CMTS

Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

Specify the
spectrum rule
identifier.

spectrum-rule <identifier>
Where:
<percentage>

Specifies the previously-created spectrum rule


by the rules unique identifier in the range 1 to
40.

Example:
In the following example, spectrum rule 10 is applied to upstream
traffic on port 11/0.0.
CASA-CMTS(config-if-ups 11/0.0)#spectrum-rule 10

Enabling rate limiting


The Casa CMTS enforces the rate limit defined in the modem configuration. This is the default.
To turn off rate limiting:
Step Command (config)
1

Purpose

interface upstream
<module_slot_num>/<port_num>.<physical_channel_num>
Where:
<module_slot_num>

<port_num>

Enter upstream
port interface
configuration
mode.

Specifies the system slot number


where the upstream module is
installed.
Specifies the upstream port
number.

Casa CMTS Software Configuration Guide

368

CASA CMTS

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
Enter upstream interface mode for upstream port 0 on module 11,
physical channel 0.
CASA-CMTS(config)# interface upstream 11/0
CASA-CMTS(config-if-ups 11/0.0)#
2

[no] rate-limit

Enable or disable
rate limiting.

Example:
To enab le rate limiting on the upstream channel:
CASA-CMTS(config-if-ups 11/0.0)# rate-limit
To disable rate limiting on the upstream channel:
CASA-CMTS(config-if-ups 11/0.0)# no 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:
Step
1

Command (config)

Purpose

show docsis upstream channel utilization

Show the utilization rates


of all upstream channels.

Example:
See the sample session below.

Example: Displaying the utilization rates of upstream channels


C3200-232(config-if-ups 11/0.0#show docsis upstream channel utilization
Upstream
Operational Utilization Online Secondary Channel
Slot/Port.Channel
Status
Percentage Modems Modems
Description
----------------------------------------------------------------------------11/0.0 (20000000 Hz)
up
0
0
0
11/0.1 (24000000 Hz)
up
0
0
0
C3200-232(config-if-ups 11/0.0)#

Casa CMTS Software Configuration Guide

369

CASA CMTS

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 signal-quality

Show the
upstream channel
signal quality.

show upstream
<module_slot_num>/<port_num>.<physical_channel_num>
signal-quality
Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
To show the SNR of all the upstream channels:
CASA-CMTS(config)# show upstream signal-quality
upstream port
signal noise
11/0.0/1
42.0
11/0.0/1
42.0
To show the SNR of upstream port 11/0.0:
CASA-CMTS(config-if-ups 11/0.0)#show upstream
11/0.0 signal-quality
upstream channel
signal noise
11/0.0/0
0.0
11/0.0/1
0.0
CASA-CMTS(config-if-ups 11/0.0#

Displaying the upstream channel burst nose


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:

Casa CMTS Software Configuration Guide

370

CASA CMTS

Step
1

Command (config)

Purpose

show upstream burst-noise

Show the
upstream channel
signal quality.

show upstream
<module_slot_num>/<port_num>.<physical_channel_num>
burst-noise
Where:
<module_slot_num>

Specifies the system slot number


where the upstream module is
installed.

<port_num>

Specifies the upstream port


number.

<physical_channel_num>

Specifies the physical channel


number, either 0 or 1. The default
physical channel is 0 if not
specified.

Example:
To show the burst nose statistics of all upstream channels:
CASA-CMTS(config)# show upstream burst-noise
upstream channel
burst noise rate (events/sec)
11/0.0/0
0.0
11/0.0/1
0.0
To show upstream port 11/0.0/0 burst noise:
CASA-CMTS(config-if-ups 11/0.0)#show upstream 11/0.0/0 burstnoise
Burst Noise Stats for Channel 11/0.0/0:
Burst noise event rate:
Percentage of Correctable Burst Events:
Percentage of Uncorrectable Burst Events:
Burst Duration (microseconds)
(in dB)
---------------------------------0 to 1
1 to 3
3 to 10
10 to 50
50 to 500
500 to 2000
2000 to 10000
10000 to 50000
> 50000
C3200-232(config-if-ups 11/0.0)#

Casa CMTS Software Configuration Guide

0.0
0 %
0 %

events/second.

% of Events

Max Power

-----------

-----------

0
0
0
0
0
0
0
0
0

0
0
0
0
0
0
0
0
0

371

CASA CMTS

Displaying upstream channel sets


To display upstream channel sets, use the following commands:
Step Command (config)
1

show upstream channel set


show upstream channel set | <output_modifier>
show upstream channel set id [mac-domain <identifier>]
show upstream channel set mac-domain <identifier>
Where:
<output_modifier>

mac-domain <identifier>

Purpose
Displays
upstream
channel set
details by
MAC ID,
channel set
number, and
channel list.

Specifies the optional output modifier


to filter the show upstream command
output. The supported modifiers are
include, exclude, count-only, count,
and begin.
Specifies the channel set associated
with the specified MAC domain
identifier in the range 1 to 32.

Examples:
C10G(config)# show upstream channel set
MAC
Chan Channel
ID
Set
List
1
1 10/0.0/0
2
1 10/0.1/0
3
1 10/0.2/0
4
1 10/0.3/0
5
1 13/15.0/0
6
1 13/15.1/0
7
1 13/15.2/0
8
1 13/15.3/0
To display the channel set count only:
C10G(config)#show upstream channel set | count-only /
Count Line: 8
C10G(config)#
C10G-CMTS(config-if-ups 5/0.0)#show upstream channel
set mac-domain 1
MAC
Chan Channel
ID
Set
List
1
1 5/0.0/0
1
2 5/0.1/0
1
256 5/0.0/0, 5/0.1/0
C10G-CMTS(config-if-ups 5/0.0)#
Casa CMTS Software Configuration Guide

372

CASA CMTS

Displaying voice information on upstream interfaces


To show the voice information on the upstream interfaces:
Step
1

Command

Purpose

show cable voice summary

Display voice
information.

Example:
C3200-232(config-if-ups 5/0.0)#show cable voice summary
Upstream Slot/Port.Channel Normal Emergency Total
5/0.0
0
0
0
5/0.1
0
0
0
5/1.0
0
0
0
5/1.1
0
0
0
5/2.0
0
0
0
5/2.1
0
0
0
5/3.0
0
0
0
5/3.1
0
0
0
5/4.0
0
0
0
5/4.1
0
0
0
5/5.0
0
0
0
5/5.1
0
0
0
5/6.0
0
0
0
5/6.1
0
0
0
5/7.0
0
0
0
5/7.1
0
0
0
total
0
0
0

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.

Casa CMTS Software Configuration Guide

373

CASA CMTS

Step
1

Command (config)

Purpose

interface ip-bundle <id>

Create or enter the


IP-bundle
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)#

Adding the primary IP interface


To add the primary IP address to IP-bundle interface:
Step
1

Command (config)

Purpose

interface ip-bundle <id>

Create or enter
the IP-bundle
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)#
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

Casa CMTS Software Configuration Guide

374

CASA CMTS

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:
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

interface ip-bundle <id.num>

Create or
enter the IPbundle
Interface.

Where:
Casa CMTS Software Configuration Guide

375

CASA CMTS

<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:
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)#
2

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
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

interface ip-bundle <id.num>

Create or enter
the IP-bundle
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:
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)#
[no] ipv6 address <ipv6-address>/<mask_len> [secondary]
Where:
<ipv6-address>

Text string for standard IPv6 address format:


xxxx:xxxx:xxxx:...:xxxx

Casa CMTS Software Configuration Guide

Assign an IPv6
address to a
primary or
secondary IPbundle interface.
376

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
can be shortened to: 2001::1000:1)
One sequence of 20 bit blocks containing only
zeroes can be replaced with ::

secondary

Specify secondary to indicate a secondary


IPv6 IP bundle 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
Remove the IPv6 address:
CASA-CMTS(ip-bundle 1.155)# no ipv6 address

Specifying the IPv6 local link address


The reserved IPv6 local link address is required for communication within a network segment of
an IPv6 local network or point-to-point host connection. Local link addresses are not forwarded to
neighbor routers. IPv6 local link addresses used the reserved prefix of fe80::/64.
Step
1

Command (config)

Purpose

interface ip-bundle <id.num>

Create or enter
the IP-bundle
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:
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)#
2

[no] ipv6 link-local-address <ipv6-address>


Where:
<ipv6address>

Assign an IPv6
address to a
prim

Specfies the reserved IPv6 local link address in the


format: fe80:xxxx:xxxx:...:xxxx

Example:
Assign IPv6 local link address fe80::217:10ff:fe02:cbcd.
Casa CMTS Software Configuration Guide

377

CASA CMTS

CASA-CMTS(ip-bundle 1.155)# ipv6 link-local-address


fe80::217:10ff:fe02:cbcd
Remove the IPv6 local link address:
CASA-CMTS(ip-bundle 1.155)# no ipv6 link-local
address

Displaying the IPv6 local link address


The reserved IPv6 local link address is required for communication within a network segment of a
local network or point-to-point host connection.
Step
1

Command

Purpose

show ipv6 link-local-address

Show all IPv6


local link
addresses

Example:
CASA-CMTS(config)# interface ip-bundle 1.511
CASA-CMTS(ip-bundle 1.155)# show ipv6 link-localaddress
mac domain 1
fe80::217:10ff:fe02:cbcd
mac domain 2
fe80::217:10ff:fe02:cbce
mac domain 3
fe80::217:10ff:fe02:cbcf
mac domain 4
fe80::217:10ff:fe02:cbd0
mac domain 5
fe80::217:10ff:fe02:cbd1
mac domain 6
fe80::217:10ff:fe02:cbd2
mac domain 7
fe80::217:10ff:fe02:cbd3
mac domain 8
fe80::217:10ff:fe02:cbd4
mac domain 9
fe80::217:10ff:fe02:cbd5
mac domain 10
fe80::217:10ff:fe02:cbd6
.
.
.

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

interface ip-bundle <id>

Create or enter
the IP-bundle
interface

Where:
<id>

IP bundle interface ID. Valid values are 1 to 16.

Casa CMTS Software Configuration Guide

378

CASA CMTS

Example:
Create an IP-bundle interface with ID=2:

CASA-CMTS(config)# interface ip-bundle 2


CASA-CMTS(ip-bundle 2)#
[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: xxxx: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)#

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.
Casa CMTS Software Configuration Guide

379

CASA CMTS

interface ip-bundle 1
ip address 172.18.32.4 255.255.255.0
ip address 192.168.254.254 255.255.255.0 secondary
cable helper-address 172.18.4.239
ip access-group 123
interface ip-bundle 1.1
ip address 10.0.0.3 255.255.255.0
ip address 192.168.54.254 255.255.255.0 secondary
cable helper-address 172.18.4.239
ip access-group 123
interface ip-bundle 1.2
ip address 192.168.5.1 255.255.255.0
ip address 10.110.50.25 255.255.255.0 secondary
cable helper-address 172.18.4.239
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.

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

Casa CMTS Software Configuration Guide

380

CASA CMTS

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
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

Casa CMTS Software Configuration Guide

381

CASA CMTS

Where:
<string>

Specifies the user-defined name of the CPE class


with up to 11 alphanumeric characters.

open and existing


class for editing.

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.
CASA-CMTS(config-if-mac 2)# 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.
Step
1

Command (config)

Purpose

interface ip-bundle <id>

Enter ip-bundle
interface mode.

<id>

IP bundle interface ID. Valid values are 1 to 16.

Example:
CASA-CMTS(config)# interface ip-bundle 1
CASA-CMTS(ip-bundle 1)#
[no] ip rip authentication key-chain <name>
Where:
<name>

Name of the authentication key chain.

Configure or
disable the RIP
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

Casa CMTS Software Configuration Guide

382

CASA CMTS

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

interface ip-bundle <id>

Enter the ipbundle interface


mode.

<id>

IP bundle interface ID. Valid values are 1 to 16.

Example:
CASA-CMTS(config)# interface ip-bundle 1
CASA-CMTS(ip-bundle 1)#
[no] ip rip authentication string <name>
Where:
<name>

Authentication string name up to 16 characters.

Configure or
disable the RIP
authentication
string.

Example:
Configure authentication string as public:
CASA-CMTS(ip-bundle 1)# ip rip authentication
string public
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

interface ip-bundle <id>

Enter the ipbundle interface


mode.

<id>

IP bundle interface ID. Valid values are 1 to 16.

Example:
CASA-CMTS(config)# interface ip-bundle 1
CASA-CMTS(ip-bundle 1)#
[no] ip rip authentication mode { text | md5 [auth-length rfc] }
Where:
text

Text authentication mode.

md5

MD5 authentication mode.

Casa CMTS Software Configuration Guide

Configure or
disable IP RIP
authentication
mode.

383

CASA CMTS

Example:
Configure the interface to use MD5 authentication:
CASA-CMTS(config-if-gige 0)# ip rip 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>

The number of the IP bundle interface in the range


1 to 16.

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 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
ip address 10.232.10.1 255.255.255.0 secondary
ip address 10.232.11.1 255.255.255.0 secondary
ipv6 address 2000:232:1::1/60
ipv6 address 2000:232:2::1/60 secondary
cable helper-address 192.168.3.6
cable helper-ipv6-address 3000::10
CASA-CMTS(config)# show interface ip-bundle 1 stat
ip-bundle:
upstream bytes:
upstream packets:
Casa CMTS Software Configuration Guide

1
144574
2118
384

CASA CMTS

downstream
downstream
downstream
downstream
downstream
downstream

unicast bytes:
multicast bytes:
total bytes:
unicast packets:
multicast packets:
total packets:

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

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)
Casa CMTS Software Configuration Guide

385

CASA CMTS

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

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
interface docsis-mac 1
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
Casa CMTS Software Configuration Guide

386

CASA CMTS

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
downstream 1 interface qam 2/0/0
downstream 2 interface qam 2/0/1
downstream 3 interface qam 2/0/2
downstream 4 interface qam 2/0/3
upstream 1 interface upstream 1/0.0/0
upstream 2 interface upstream 1/0.1/0
upstream 3 interface upstream 1/7.0/0
upstream 4 interface upstream 1/7.1/0
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

[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.

Example:
Create a new MAC domain interface with domain id = 2 or
enter an existing one:

Use the no form to


remove a MAC domain
interface.

CASA-CMTS(config)# interface docsis-mac 2


CASA-CMTS(config-if-mac 2)# end
CASA-CMTS(config)#

Casa CMTS Software Configuration Guide

387

CASA CMTS

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

[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.

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

Binding upstream interfaces


To bind an upstream 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.

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)#
Casa CMTS Software Configuration Guide

388

CASA CMTS

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.)

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

[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.

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)#
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

Casa CMTS Software Configuration Guide

389

CASA CMTS

Binding downstream interfaces


To bind a downstream interface to a MAC domain interface:
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.

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)#
downstream <chan-id> interface qam <x/y/z>
Where:
<chan-id>

Bind downstream
interfaces.

User-defined channel identity in the range 1 to


255 and is unique within a MAC domain.

<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

[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.

Casa CMTS Software Configuration Guide

390

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)#
downstream <chan-id> interface qam <x/y/z> [secondary]
Where:
<chan-id>

Bind secondary
downstream
interfaces

User-defined channel identity in the range 1 to


255 and is unique within a MAC domain.

<x>

Module number.

<y>

Port number.

<z>

Channel number in the range 0 to 3.

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

[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.

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)#
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

Casa CMTS Software Configuration Guide

391

CASA CMTS

Enabling MAC domain interfaces


To enable MAC domain interface 2:
Step
1

Command

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.

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)#
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

[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.

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)#
shutdown

Disable MAC domain


interface

Example:
CASA-CMTS(config-if-mac 2)# shutdown

Casa CMTS Software Configuration Guide

392

CASA CMTS

Setting MAC domain interface IP addresses


To set the IP address for a MAC domain interface:
Step
1

Command (config)

Purpose

[no] interface docsis-mac <domain-id>


Where:
MAC domain number. The valid values
<domain-id>
are 1 to 32.

Create new domain


interfaces or enter
an existing one.

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)#
2

[no] ip address <ip-address> <subnet-mask>


Where:
<ip-address>
<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.

Set the IP address


for a MAC domain
interface
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
CASA-CMTS(config-if-mac 2)#

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

[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.

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)#
Casa CMTS Software Configuration Guide

393

CASA CMTS

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

Removing MAC domain interface IPv6 addresses (Rel. 5.2 and earlier)
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.

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)#
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 Ver. 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.

Casa CMTS Software Configuration Guide

394

CASA CMTS

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.

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)#
[no] cable helper-address <ip_addr> [cable-modem | host | mta]
Where:
<ip_addr>

Set or disable the


helper-address.

The IP address of a DHCP server to which


UDP broadcast packets are sent.

cable-modem

Optional. Specifies that only CM UDP


broadcasts are forwarded.

host

Optional. Specifies that only host UDP


broadcasts are forwarded.

mta

Optional. Specifies that only MTA UDP


broadcasts are forwarded.

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-if-mac 2)# end
CASA-CMTS(config)#
Forward UDP broadcasts from CMs, MTA and CPE devices to
separate DHCP servers:
CASA-CMTS(config-if-mac 2)#
172.23.66.143 host
CASA-CMTS(config-if-mac 2)#
172.23.66.144 cable-modem
CASA-CMTS(config-if-mac 2)#
172.23.66.145 mta
CASA-CMTS(config-if-mac 2)#
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
Casa CMTS Software Configuration Guide

395

CASA CMTS

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:
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.

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)#
[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.

CASA-CMTS(config-if-mac 2)# ip bundle 1

Casa CMTS Software Configuration Guide

396

CASA CMTS

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

[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.

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)#
[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.

Example:
Set the interval for the sync message transmissions to 100 ms:
CASA-CMTS(config-if-mac 2)# sync-interval 100
CASA-CMTS(config-if-mac 2)# end

Specifying the intial technique for moving cable modems to upstream


channels
Specify the ranging technique to be used by D3.0 modems when moving to new upstream
channels associated with the MAC domain interface. The options are broadcast-ranging, direct,
period-ranging, and unicast-ranging. The show interface docsis-mac <id> command displays
the current initial technique setting. The default technique is broadcast-ranging.

Casa CMTS Software Configuration Guide

397

CASA CMTS

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.

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)#
2

initial-tech <broadcast-ranging> | <direct> | <period-ranging> |


<unicast-ranging>
Where:
<broadcastranging>

Instructs D3.0 modems to move to new


channels during broadcast ranging. This is
the default technique.

<direct>

Instructs D3.0 cable modems to move to


new channels directly.

<period-ranging>

Instructs D3.0 modems to move to new


channels during period ranging.

<unicast-ranging>

Instructs D3.0 modems to move to new


channels during unicast ranging.

Specify the initial


technique for
moving cable
modems to new
upstream
channels
associated with
the CMTS MAC
domain interface.

Example:
CASA-CMTS(config-if-mac 2)#initial-tech broadcastranging

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.

Casa CMTS Software Configuration Guide

398

CASA CMTS

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.

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)#
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

Configuring the MDD interval


To configure the MDD interval:
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.

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)#
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.

Casa CMTS Software Configuration Guide

399

CASA CMTS

Example:
Set the minimum insertion interval to 100 ms:
CASA-CMTS(config-if-mac 2)# mdd interval 10
CASA-CMTS(config-if-mac 2)#

Enabling a domain interface gateway IP address


To enable a gateway IP address on a domain interface:
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.

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)#
[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

Casa CMTS Software Configuration Guide

400

CASA CMTS

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

[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.

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)#
[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.
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.

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)#

Casa CMTS Software Configuration Guide

401

CASA CMTS

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.

[no] tftp-enforce
Example:
CASA-CMTS(config-if-mac 2)#tftp-enforce

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

Enabling/disabling IP policies on a domain interface


To enable an IP policy on a domain interface:
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.

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)#
Casa CMTS Software Configuration Guide

402

CASA CMTS

[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

[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.

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)#
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
CASA-CMTS(config-if-mac 2)#
Disable:
CASA-CMTS(config-if-mac 2)# mgmd ipv4 shutdown
CASA-CMTS(config-if-mac 2)#

Casa CMTS Software Configuration Guide

Enable the group


membership discovery
(mgmd) protocol on a
docsis-mac domain
interface.
To disable the mgmd
protocol on a docsis-mac
domain interface,
remove the no command
at the beginning of the
command.

403

CASA CMTS

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

[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.

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)#
[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:
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.

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)#
Casa CMTS Software Configuration Guide

404

CASA CMTS

[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

[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.

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)#
2

[no] multicast-dsid-forward
Example:
CASA-CMTS(config-if-mac 2)# multicast-dsidforward

Casa CMTS Software Configuration Guide

Enable or disable
forwarding of multicast
downstream IDs to cable
modem CPE devices.
Use the no form of the
command to disable
DSID forwarding.

405

CASA CMTS

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

[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.

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-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

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 followparameters are supported in Release 6.1.
enable
cur-hop-limit
life-time
Casa CMTS Software Configuration Guide

406

CASA CMTS

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

[no] interface docsis-mac <domain-id>

Create new
domain
interfaces or
enter an
existing one.

Where:
<domain-id>

MAC domain number in the range 1 to 32.

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)#
[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.

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.

Casa CMTS Software Configuration Guide

407

CASA CMTS

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
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.

Casa CMTS Software Configuration Guide

408

CASA CMTS

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

Configuring BPI+ on a MAC domain interface


To configure KEK and TEK life-time on MAC domain Interfaces.
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 in the range 1 to


32.

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)#
Casa CMTS Software Configuration Guide

409

CASA CMTS

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
CASA-CMTS(config-if-mac 1)#

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:
Step Command (config)
Purpose
1

[no] interface docsis-mac <domain-id>


Where:
<domain-id>

Create new domain


interfaces or enter an
existing one.

MAC domain number. The valid values


are 1 to 32.

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)#
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
Casa CMTS Software Configuration Guide

410

CASA CMTS

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
Ifindex:
77
Administrated status:
UP
Operation status:
UP
Mac address:
0017.1000.2647
DSA Request
:
0/ups;
DSA Response
:
0/ups;
DSA Acknowledgements :
0/ups;
DSA Success
:
0/ups;
DsA Fail
:
0/ups;
DSC Request
:
0/ups;
DSC Response
:
0/ups;
DSC Acknowledgements :
0/ups;
DSC Success
:
0/ups;
DSC Fail
:
0/ups;
DSD Request
:
0/ups;
DSD Response
:
0/ups;
DSD Success
:
0/ups;

Casa CMTS Software Configuration Guide

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

411

CASA CMTS

DSD
DCC
DCC
DCC
DCC
DCC
DCC
DCC
DBC
DBC
DBC
DBC
DBC
DBC

Fail
Request
Response
Acknowledgements
Success
Fail
RSP Depart
RSP Arrive
Request
Response
Acknowledgements
Success
Fail
Partial Service

:
:
:
:
:
:
:
:
:
:
:
:
:
:

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
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
Binding upstream interfaces
Removing upstream interfaces
Binding downstream interfaces
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:
Casa CMTS Software Configuration Guide

To remove a service
group, use the no
form of the
command.

412

CASA CMTS

Create a new service group 2:


CASA-CMTS(config)# service group 2
CASA-CMTS(conf-svc-grp 2)# end
CASA-CMTS(config)#
Remove the service group:
CASA-CMTS(config)# no service group 2
CASA-CMTS(conf-svc-grp 2)# end
CASA-CMTS(config)#

Binding upstream interfaces


To bind an upstream interface to a service group:
Step
1

Command (config)
[no] service group <string>
Where:
<string>

Service group name containing up to 16


characters. Up to 160 service groups are
supported.

Purpose
Create or enter a
new service group
To remove a service
group, use the no
form.

Example:
Create a new service group 2:

CASA-CMTS(config)# service group 2


[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.

Bind upstream
interfaces.
To remove upstream
interface binding,
use the no form of
the command.

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

Casa CMTS Software Configuration Guide

413

CASA CMTS

Binding downstream interfaces


To bind a downstream interface to a service group:
Step
1

Command (config)

Purpose

[no] service group <string>

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:
Create a new service group 2:
CASA-CMTS(config)# service group 2
[no] qam <X/Y/Z>
Where:
<X>

Module number.

<Y>

Port number.

<Z>

Channel number in the range 0 to 3.

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

Casa CMTS Software Configuration Guide

414

CASA CMTS

Displaying service groups


To display the configured service groups:
Step
1

Command (config)

Purpose

show service group [<string>]

Display configured
service groups.

show this
Where:
<string>

Specifies the service group name entered


as a string.

Example:
Display service group 1:
CASA-CMTS(config)# show 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.0
upstream 3/1.0
upstream 3/2.0
upstream 3/3.0
Display service group 4:
CASA-CMTS(config)#service group 4
C10G-CMTS(conf-svc-grp 4)#show this
service group 4
upstream 11/6.0
upstream 11/6.1
upstream 11/6.2
upstream 11/6.3
upstream 11/7.0
upstream 11/7.1
upstream 11/7.2
upstream 11/7.3

Casa CMTS Software Configuration Guide

415

CASA CMTS

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
docsis-mac 1 service-group 2
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:
mac:<num=1:16>
service group <string>

Specify a MAC domain in the


range 1 to 32.
To specify which service group.

Example:
CASA-CMTS#show md-ds-sg mac 1 service-group 1
docsis-mac 1 service-group 1
qam 0/2/0
qam 0/2/1
qam 0/2/2
qam 0/2/3

Casa CMTS Software Configuration Guide

416

CASA CMTS

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


docsis-mac 1 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

MAC domain number in the range 1 to 32.


The named service group string.

Example:

CASA-CMTS#show md-us-sg mac 1 service-group 1


docsis-mac 1 service-group 1
upstream 1/4/0
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.
Casa CMTS Software Configuration Guide

417

CASA CMTS

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
mac-domain 1 group-id 1
CASA-CMTS(bond-ds-mac-1-group-1)#
To create a new upstream bonding group:
Step
1

Command (config)

Purpose

[no] bonding-group upstream mac-domain <mac_id>


group-id <grp_id>

Create or enter a new


upstream bonding group

Where:
<mac_id>

To remove the bonding


group, use the no form
of the command.

<grp_id>

MAC domain ID in the range 1 to 32.


Bonding group ID in the range 1-65535.

Example:

Casa CMTS Software Configuration Guide

418

CASA CMTS

Create a new downstream bonding-group with mac-domain 1


and group ID 1:
CASA-CMTS(config)# bonding-group upstream macdomain 1 group-id 1
CASA-CMTS(bond-ds-mac-1-group-1)#
Remove the group:
CASA-CMTS(config)# no bonding-group upstream
mac-domain 1 group-id 1
CASA-CMTS(bond-ds-mac-1-group-1)#

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>

Create or enter a new


upstream bonding group.

Where:
<md_id>
<grp_id>

MAC domain ID in the range 1 to 32.


Bonding group ID in the range 1 to
65535

Example:
Create a new upstream bonding-group with mac-domain 1
and group ID 1:
CASA-CMTS(config)# bonding-group upstream macdomain 1 group-id 1
CASA-CMTS(bond-ds-mac-1-group-1)#
2

[no] upstream <X/Y.C/Z>


Where:
<X>

Module number.

<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.

Bind upstream interfaces


to a bonding group.
To remove upstream
interface binding from a
bonding group, use the
no form of the
command.

Example:
Bind upstream 1/1.0/0 to bonding-group 1:
Casa CMTS Software Configuration Guide

419

CASA CMTS

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>

Create or enter a new


downstream bonding
group.

Where:
<md_id>
<grp_id>

MAC domain ID in the range 1 to 32.


Bonding group ID in the range 1 to
65535.

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)#
[no] qam <X/Y/Z>
Where:
Module number.
<X>
<Y>

Port number.

<Z>

Channel number in the range 0 to 3.

Example:

Bind a downstream
interface to a bonding
group.
To remove a bound
downstream interface
from a bonding group,
use the no form.

Bind downstream 0/2/1 to binding-group 2:


CASA-CMTS(bond-ds-mac-1-group-1)# qam 0/2/1
Remove the binging:
CASA-CMTS(bond-ds-mac-1-group-1)# no qam 0/2/1

Casa CMTS Software Configuration Guide

420

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>

MAC domain ID in the range 1 to 32.


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)#

Casa CMTS Software Configuration Guide

421

CASA CMTS

Assigning a receive module


To assign a receive module to receive channel configuration:
Step
1

Command (config)

Purpose

[no] rcc mac <mac_id> rcp-id <rcp_id> <cfg_id>

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:

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)#
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


the range 0 to 999000000.

<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

[no] rcc mac <mac_id> rcp-id <rcp_id> <cfg_id>

Set up receive channel


configuration (RCC) for
downstream channel
bonding to the CM.

Where:
<mac_id>

MAC domain ID in the range 1 to 32.

<rcp_id>

Receive channel profile id, in form of

Casa CMTS Software Configuration Guide

422

CASA CMTS

xx:xx:xx:xx:xx
<cfg_id>

rcc cfg id. Value Range: 1-4294967295.

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)#
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>

MAC domain ID in the range 1 to 32.

<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:
Casa CMTS Software Configuration Guide

423

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
rc 2 downstream 2 primary connect 1
rc 3 downstream 3 primary connect 1
rc 4 downstream 4 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
-

Casa CMTS Software Configuration Guide

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
-

424

CASA CMTS

Predefined modulation-profile 2 parameters


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
-

Predefined modulation-profile 3 parameters


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

Predefined modulation-profile 4 parameters


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.
Casa CMTS Software Configuration Guide

425

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

Predefined modulation-profile 5 parameters


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

Casa CMTS Software Configuration Guide

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

426

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>

Profile ID in the range 6 to 64.

Casa CMTS Software Configuration Guide

427

CASA CMTS

Example:
CASA-CMTS(config)#modulation-profile 22
CASA-CMTS(config-mod-prof)#
<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

Casa CMTS Software Configuration Guide

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
428

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>

Profile ID in the range 6 to 64.


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
CASA-CMTS(config-mod-prof)#
Note: The specified modulation type applies only to the burst types a-short and a-long.

Manual mode ATDMA-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>

Profile ID in the range 6 to 64.

Example:
CASA-CMTS(config)#modulation profile 22
CASA-CMTS(config-mod-prof)#
<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:

Casa CMTS Software Configuration Guide

429

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)
4-255 (modulation intervals)
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)# modulation-profile 7
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-mod-prof)# end
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

Casa CMTS Software Configuration Guide

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

430

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>

Profile ID in the range 6 to 64.


Modulation type: qpsk, 16qam, 8qam,
32qam, or 64qam. If omitted, the profile
is the same as predefined modulationprofile 4.

Example:
CASA-CMTS(config)#modulation-profile 22 mtdma qpsk
CASA-CMTS(config-mod-prof)#
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


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.

Casa CMTS Software Configuration Guide

431

CASA CMTS

Step
1

Command (config)

Purpose

modulation-profile <profile>

Select the profile


to configure.

Where:
<profile>

Profile ID in the range 6 to 64.

Example:
CASA-CMTS(config)#modulation-profile 22
CASA-CMTS(config-mod-prof)#
<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)
4-255 (modulation intervals)
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)# modulation-profile 8
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
CASA-CMTS(config-mod-prof)# end
CASA-CMTS(config)#

Casa CMTS Software Configuration Guide

432

CASA CMTS

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 scdma-type modulation profiles, specify the modulation type to automatically set the
attributes 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>

Profile ID in the range 6 to 64.


Modulation type: qpsk, 16qam, 8qam,
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
CASA-CMTS(config-mod-prof)#
Note: The specified modulation type applies only to the burst types a-short and a-long.

Casa CMTS Software Configuration Guide

433

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
modulation-profile 2
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 16qam off 168 6 75 338 7 8 shortened on
long tdma 16qam off 192 8 220 338 0 8 shortened on
modulation-profile 3
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
modulation-profile 4
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
modulation-profile 5
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

Casa CMTS Software Configuration Guide

off
1 off
1 off
on 128 1 on
on 128 1 on

434

CASA CMTS

show modulation-profile, one profile


CASA-CMTS# config
CASA-CMTS(config)# show modulation-profile 1
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

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)#

Upstream burst noise detection and monitoring


Release 6.1.3 provides a set of commands that allow cable operators to monitor upstream burst
noise statistics over 10-second intervals. Burst noise can be displayed per logical channel, or
displayed over all upstream channels. Statistics include:
Burst noise event rate in events per second.
Percentage of correctable and uncorrectable burst events.
Burst duration in microseconds, percentage of events in the duration, and the maximum
upstream power level.
The commands are summarized as follows:
show upstream burst noise Displays brief burst noise statistics for all logical channels.
show upstream [slot/port.channel} burst noise Displays brief burst noise statistics for
both logical channels for the specified physical channel.
Casa CMTS Software Configuration Guide

435

CASA CMTS

show upstream {slot/port.channel/logical-channel} burst noise Displays brief burst


noise statistics for the specified logical channel.
cable upstream burst-noise-detect Enables/disables burst noise detection. Use the no
form of the command to disable upstream burst noise detection.

Examples
C10G(config-if-ups 13/0.0)# show upstream burst-noise
upstream channel
burst noise rate (events/sec)
10/0.0/0
143.0
10/0.0/1
119.7
10/0.1/0
95.2
10/0.1/1
131.1
10/1.0/0
0.0
10/1.0/1
0.0
10/1.1/0
0.0
10/1.1/1
0.0
C10G-181(config-if-ups 13/0.0)#show upstream 10/0.0/0 burst-noise
Burst Noise Stats for Channel 10/0.0/0:
Burst noise event rate:
Percentage of Correctable Burst Events:
Percentage of Uncorrectable Burst Events:
Burst Duration (microseconds)
-----------------------------

% of Events
-----------

0 to 1
1 to 3
3 to 10
10 to 50
50 to 500
500 to 2000
2000 to 10000
10000 to 50000
> 50000

0
65
35
0
0
0
0
0
0

143.5 events/second.
98%
2%
Max Power (in dB)
----------------0
0
0
0
0
0
0
0
0

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
Casa CMTS Software Configuration Guide

436

CASA CMTS

Static multicast configuration


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.

Casa CMTS Software Configuration Guide

437

CASA CMTS

Step
1

Command

Purpose

multicast max channel-util <number>

Enable multicast
authorization
globally.

Where:
<number>

The numerical percentage in the range 1 to


100. The default setting is 60.

Example:
CASA-CMTS(config)# multicast max channel-util 70

Enabling/disabling multicast session authorization


To enable multicast authorization globally, use the following procedure.
Step
1

Command (config)

Purpose

[no] 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

Enabling/disabling the multicast single security association identifier


The multicast single-said command enables a single security security association (SA) identifier
(SAID) to be used for multicast session encryption during mulitcast traffic forwarding on bonded
cable modems. The default setting is disabled. When disabled, each multicast replication is
assigned a different SAID to help prevent cable modems from receiving duplicate traffic. When
enabled, a single SAID is assigned to all multicast replications.
Step
1

Command (config)

Purpose

[no] multicast single-said

Enable the single


SAID.

Example:
CASA-CMTS(config)# multicast single-said
Casa CMTS Software Configuration Guide

438

CASA CMTS

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

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)#
session-rule <rule-id> <accept|deny> [ipv6]
<sourceAddr/mask_len> <groupAddr/mask_len> priority
<number>
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

Casa CMTS Software Configuration Guide

439

CASA CMTS

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.

<number>

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
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

Casa CMTS Software Configuration Guide

440

CASA CMTS

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:
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
Casa CMTS Software Configuration Guide

441

CASA CMTS

multicast authorization enable


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 config 2
multicast group encryption 1 algorithm cmts
multicast group qos 1 IPTV aggregate max-sess 10
app-id 1234
multicast-dsid-forward

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
------ ----------------IPV6 Multicast Groups:
Number Module
Vlan
Multicast
------ -----------------

Group
----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_>

Casa CMTS Software Configuration Guide

Configure the
table entries.

442

CASA CMTS

Where:
<sourceAddr/mask_len>

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
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 1)# source-address
192.168.0.1/32
CASA-CMTS(conf-grp-config 1)# group-address
Casa CMTS Software Configuration Guide

443

CASA CMTS

244.0.0.1/32
CASA-CMTS(conf-grp-config
CASA-CMTS(conf-grp-config
CASA-CMTS(conf-grp-config
CASA-CMTS(conf-grp-config
CASA-CMTS(conf-grp-config
CASA-CMTS(conf-grp-config
CASA-CMTS(conf-grp-config

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
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>

Creates a unique GCR and a


unique GSF for the session. If the

Casa CMTS Software Configuration Guide

444

CASA CMTS

multicast group qos is configured


to be single, a new downstream
service flow will be used for each
session.
<aggregate>

Combines all sessions with


matching criteria 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
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)#
Casa CMTS Software Configuration Guide

445

CASA CMTS

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.

<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 the


range 0 to 65535.

<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

Casa CMTS Software Configuration Guide

446

CASA CMTS

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-traffic-burst
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.
To configure a default service class:
Step Command (config)
1

multicast default grp-service-class <class_name>


Where:
<class_name>

Purpose
Configure the
default service
class.

Default group service-class name


containing up to 15 characters.

Example:
CASA-CMTS(config)# multicast default grp-serviceclass 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 enable
multicast authorization match-profile my-profile1
Casa CMTS Software Configuration Guide

447

CASA CMTS

multicast authorization default-action permit


multicast authorization max-session-num 5
multicast authorization profile 1
multicast group config 1
multicast group config 2
multicast group encryption 1 algorithm cmts
multicast group qos 1 IPTV aggregate max-sess 10
app-id 1234
multicast-dsid-forward

Creating static multicast sessions


To create a static multicast session for any-source-multicast:
Step
1

Command (config)

Purpose

cable igmp static-group <group_address>

Specify the group


address.

Where:
<group_address>

Specified the 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:
Step
1

Command (config)

Purpose

cable igmp static-group <group_address> source <ip_address>

Specify the
group and
source
address.

cable igmp static-group <group_address> source <ip_address>


dsid <number>
cable igmp static-group <group_address> dsid <number>
Where:
<group_address>

Specifies the IP multicast group


address.

<ip_address>

Specifies the source IP address for


the mullticast session.

<number>

Specifies the 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 <slot/port_number/channel_number>

Casa CMTS Software Configuration Guide

Specify the
QAM ID for
448

CASA CMTS

Where:
<slot/port_number/downstream_channel>

Specifies the
downsteam
channel using the
system slot, port
number, and
physical
downstream
channel number.

downstream
binding.

Example:
CASA-CMTS(conf-igmp-static-group 224.0.100.100)# qam
2/0/0
To create a description of the static multicast session for source-specific-multicast:
Step
1

Command (config)

Purpose

cable igmp static-group <group_address> source <ip_address>

Specify the
group and
source
address.

cable igmp static-group <group_address> source <ip_address>


dsid <number>
cable igmp static-group <group_address> dsid <number>
Where:
<group_address>

Specifies the IP multicast group address.

<ip_address>

Specifies the source IP address for the


mullticast session.

<number>

Specifies the 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)#
desc <string>
Where:
<string>

Specify a
description

Specifies the text string to describe multicast session.


Up to 64 characters may be specified. If the string has
embedded blank spaces, then the string must be within
quotation marks ( ).

Example:
CASA-CMTS(conf-igmp-static-group 224.0.100.100)# qam
2/0/0

Casa CMTS Software Configuration Guide

449

CASA CMTS

Configuring redundant downstream multicast


The secondary-source parameter specifies a second and redundant IPv4 or IPv6 downstream
source address for the active source address. When a secondary address is configured, the
switch multicast-source command interactively moves the stream from the active to the
secondary source IP address.
To create a secondary source IP for the active downstream IP and to switch over to the
secondary IP:
Step
1

Command (config)

Purpose

cable igmp static-group <group_address> source <ip_address>

Specify the
group and
source
address.

cable igmp static-group <group_address> source <ip_address>


dsid <number>
cable igmp static-group <group_address> dsid <number>
Where:
<group_address>

Specifies the IP multicast group address.

<ip_address>

Specifies the source IP address for the


mullticast session.

<number>

Specifies the 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)#
secondary-source {<ip_address> | ipv6 <ip_address>}
Where:
<ip_address>

Specifies the redundant secondary multicast


downstream source IP address. The address is
specified as an IPv4 or an IPv6 address using
address conventions.

Configure
the
secondary
multicast
source IP
address.

Example:

CASA-CMTS(conf-igmp-static-group 224.0.100.100)#
secondary-source 224.0.100.200
switch multicast-source
Example:
CASA-CMTS(conf-igmp-static-group 224.0.100.100)#
switch multicast-source

Casa CMTS Software Configuration Guide

Switch over
over to the
redundant
secondary
downstream
IP source.

450

CASA CMTS

Use the show cable igmp static-group switch log command to


display the switchover time and whether the switchover was done
manually using the CLI or initiated automatically by the CMTS.

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>

IP multicast group address.

Example:
CASA-CMTS(config)# no cable igmp static-group
224.0.100.100
To remove a specific static session for source-specific-multicast:
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>
<srcAddr>

IP multicast group address.


The source IP address for SSM session.

Example:
CASA-CMTS(config)# no cable igmp static-group
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 | include igmp

Display the static


multicast
sessions.

Example:
Casa CMTS Software Configuration Guide

451

CASA CMTS

CASA-CMTS(config)# show running-config | include


igmp

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
window (in seconds):
Step
1

Command (config)

Purpose

[no] cable igmp filter <number> <seconds>

Set the number of


IGMP packets to
accept within the
specified time
window.

Where:
<number>

<seconds>

A value in the range 0 to 20 to specify the


maximum number of IGMP response
packets to accept from the CM or CPE within
the specified time window. The default
setting is 4 IGMP packets.
The number of seconds in the range 2 to 5
to specify the time window for accepting
IGMP packets from the CM or CPE. The
default is 2 seconds.

Use the no form


of the command
to revert to the
default settings.

Example:
CASA-CMTS(config)# cable igmp filter 10 2

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)#

Casa CMTS Software Configuration Guide

452

CASA CMTS

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:
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 1234
CASA-CMTS(conf-app-policy 1234) limit replication
CASA-CMTS(conf-app-policy 1234) max iptv channel <num=0:2>

Casa CMTS Software Configuration Guide

453

CASA CMTS

Multicast Listener Discovery (RFC2710)


Release 6.1.2 includes support for the Multicast Listener Discovery (MLD) Versions 1 and 2 for
IPv6 networks. The MLD process running over a CMTS interface discovers multicast listeners (or
receivers) for distribution of multicast traffic.
MLD is comprised of the following three Internet Control Message Protocol (ICMPv6) messages
that are transmitted over a CMTS interface:
Multicast Listener Query The CMTS polling message for multicast groups.
Multicast Listener Report The host response to the Multicast Listener Query
message, or a multicast join message from the host to the CMTS.
Multicast Listener Done - The hos t message to the CMTS when a host drops out of
the multicast group.

Enabling MLD on an interface


MLD is configured on CMTS interfaces. The following CLI session enables MLD on a CMTS GigE
interface (already configured with an IPv6 address).
C3200-232(config)# interface gige 5
C3200-232(config-if-gige 5)# ipv6 mld

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>

Specifies the qos service class index in the


range 1 to 255.

Example:

CASA-CMTS(config)# cable service-class 1


CASA-CMTS(conf-service-class 1)#
name <name>

Name the class.

Where:
Casa CMTS Software Configuration Guide

454

CASA CMTS

<name>

The service class name.

Example:
3

CASA-CMTS(conf-service-class 1)# name my_class


upstream
downstream
Where:
<direction>

Define the
direction.

Upstream or downstream.

Example:
CASA-CMTS(conf-service-class 1)# upstream

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.

Casa CMTS Software Configuration Guide

455

CASA CMTS

activity-timeout
admission-timeout
app-id
attr-aggr-rule-mask
ds-resequencing
dscp-overwrite
forbidden-attr-mask
grant-interval
grant-jitter
grant-size
grants-per-interval
max-buff-size
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

qos service class activity timeout


qos service class admission timeout
qos service class application id
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
maximum buffer size for service-flow
queue,default is 0
qos service class max-concat-burst
qos service class max-latency
qos service class max-outstanding-bytes-persid-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

name
no
peak-traffic-rate
poll-interval
poll-jitter
priority
req-trans-policy
required-attr-mask
sched-type

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

storage-type

qos service class non-volatile or permanent


storage
target or desired buffer size for service-flow
queue,default is 0
qos service class tos mask
physical upstream port binding

tar-buff-size
tos-overwrite
upstream
Example:

CASA-CMTS(conf-service-class 1)#max-traffic-burst
20000000
Casa CMTS Software Configuration Guide

456

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:
Step

Command (config)

Casa CMTS Software Configuration Guide

Purpose

457

CASA CMTS

show cable service-class [<unum=1:255>] [(brief|verbose)]


Where:
No option

Display the
service class
parameters.

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}

Casa CMTS Software Configuration Guide

458

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 1)#
CASA-CMTS(config)#cable service-class 2
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)# min-packet-size 0
CASA-CMTS(conf-service-class 2)# req-trans-policy 0x0
CASA-CMTS(conf-service-class 2)# tos-overwrite 0xFF 0x0
CASA-CMTS(conf-service-class 2)# downstream
CASA-CMTS(conf-service-class 2)# app-id 0
CASA-CMTS(conf-service-class 2)#
CASA-CMTS(config)#cable service-class 3
CASA-CMTS(conf-service-class 3)# name DefD3Down
CASA-CMTS(conf-service-class 3)# min-packet-size 0
CASA-CMTS(conf-service-class 3)# req-trans-policy 0x0
Casa CMTS Software Configuration Guide

459

CASA CMTS

CASA-CMTS(conf-service-class 3)# tos-overwrite 0xFF 0x0


CASA-CMTS(conf-service-class 3)# app-id 0
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 the T1 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
Casa CMTS Software Configuration Guide

460

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

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

Casa CMTS Software Configuration Guide

461

CASA CMTS