cmts_software_config_guide_2_7_13_torelease_6.1.3, 1g.pdf

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

[email protected]

www.casa-systems.com

http://www.casa-systems.com/

CASA CMTS

Casa CMTS Software Configuration Guide 2

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


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


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


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


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


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


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


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


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


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


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



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


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


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


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


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


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


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


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





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


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


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


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


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


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


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


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


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


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


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


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: x C2200 CMTS Hardware Installation Guide x C3200 CMTS Hardware Installation Guide x C10200 CMTS Hardware Installation Guide x C10G CMTS Hardware Installation Guide x C1G CMTS Hardware Installation Guide x 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:

x DOCSIS protocols, including MPEG-2

x IETF protocols, including TCP/IP, RIP, OSPF, BGP, unicast and multicast routing

x 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


- 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


-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


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

RSP 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


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

status.”

Added description of command for configuring ip access group on

eth0.

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

June 1, 2010 Corrected upper range of VLAN interfaces.

Corrected information on using masks instead of wildcards to

exclude modems by type from load balancing.

Updated the cable modem status section.

Corrected information about storage devices and copying software

to flash.

Corrected gige command.

Corrected Table numbering and references.

Added command: debug service group.

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

September 24, 2010 Reformatted document to provide better procedure visibility. Consolidated all debug and diagnostic commands in the Casa CMTS Debugging and Diagnostics Reference Guide.

November 18, 2010 Revised document to support CMTS software up to 5.4.19.9.

December 30, 2010 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.

January 14, 2011 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.

July 15, 2011 Release 6.0.3 availability update. See the Release Notes for information.

September 7, 2011 Added missed 5.4.21 command; software-health-check snmpd

November 14, 2011 December 6, 2011

Release 6.1.1 availability update. See the Release Notes for information.

January 4, 2012 February 9, 2012 March 1, 2012 April 18, 2012 May 22, 2012

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.

September 17, 2012 October 4, 2012

Final updates for Release 6.1.2.

November 20, 2012 December 20, 2012

Release 6.1.3 update.

February 7, 2012 Added the following commands: - [no] cable partial-service dbc - [no] cable ecn 770 - [no] cable sa-des-tlvlen-2

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 Description Boldface font 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.

[x | y | z] Optional alternative keywords are grouped in brackets and separated by vertical bars.

String A non-quoted set of characters. Do not use quotation marks around the string or the string will include the quotation marks.

Screen font Terminal sessions and information the system displays are in screen font.

Boldface screen font Information you must enter is in boldface screen font.

^ The symbol ^ represents the key labeled Control—for 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


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: x� Slot and port numbering x� Completing pre-configuration x� Starting system configuration x� 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.

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.

0 1 2 3

s GigE SFP

CASA CMTS


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

RF Output Burst ReceiverInput

Burst ReceiverInput

Burst ReceiverInput

Slot 0 1 2 3

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.

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: x Casa Systems – C10G CMTS Hardware Installation Guide x Casa Systems – C10200 CMTS Hardware Installation Guide

GigE SFP Port 0 1 2 3 4 5 6 7 8 9 10 11

Line-Card Slot 0 3 1 4 2 5

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


• 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


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


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


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: x show ha configuration x show ha log x 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


becomes preferred method of handling a failure at the affected module. When disabled, automatic recovery is not performed and a failover to the standby SMM will take place. Example: CASA-CMTS(config)# ha software auto-recovery To disable the software auto-recovery to revert to the default setting, use the no form of the command. CASA-CMTS(config)# no ha software auto-recovery

Fan, power, and temperature status on the C10G For C10G platforms, the CLI provides the show envm command to selectively display fan, power, and temperature status. If a specific argument is not specified, the CMTS displays the current status for all arguments.

CASA-C10G# show envm [fan | power | temperature] CASA-C10G# show envm fan [left [0-1]| middle [0-1] | right [0-1]] CASA-C10G# show envm temperature [module <number> | QAM | SMM | UPS] CASA-C10G# show envm power

Example: CASA-C10G# show envm PEM A (-48V) PEM B (-48V) Input 1 : Present Input 1 : Present Input 1 FUSE : Good Input 1 FUSE : Good Input 2 : Present Input 2 : Present Input 2 FUSE : Good Input 2 FUSE : Good Input 3 : Present Input 3 : Present Input 4 FUSE : Good Input 3 FUSE : Good Input 4 : Present Input 4 : Present Input 4 FUSE : Good Input 4 FUSE : Good Temperature : 78 F/26 C Temperature : 80 F/27 C

FAN_Tray Temperature DC_A/DC_B Front/Back Switch Present Fan RPM LEFT** 22C/ 71F -48V/ 0V 2200/2700 ON YES MIDDLE** 23C/ 73F -48V/ 0V 1700/2900 ON YES RIGHT** 23C/ 73F -48V/ 0V 2600/2000 ON YES Module Temperature Status Type 2 86F/ 30C Normal UPS 6 89F/ 32C Normal SMM CASA-C10G(config)#show envm temperature Module Temperature Status Type 1 87F/ 31C Normal QAM

CASA CMTS


5 78F/ 26C Normal QAM 6 89F/ 32C Normal SMM 7 89F/ 32C Normal SMM 8 102F/ 39C Normal UPS 9 105F/ 41C Normal UPS 10 96F/ 36C Normal UPS 13 71F/ 22C Normal 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:

x LEFT — 0 = Front, 1 = Back x MIDDLE — 0 = Front, 1= Back x 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 non-contiguous 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


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


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 1 Ensure that your network supports reliable broadband data transmission.

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

3 Ensure that all other required headend routing and network interface equipment is installed, configured, and operational. This includes: x� All routers, switches, etc. x� Servers (DHCP, TFTP, ToD) x� Network management systems

4 Ensure that the modem firmware can support the features, throughput, and management requirements of the network.

5 Ensure that DHCP and DOCSIS configuration files have been created and pushed to appropriate servers so that each CM, when initialized, can: x� Transmit a DHCP request x� Receive an IP address x� Obtain TFTP and ToD server address x� Download a DOCSIS configuration file

6 Ensure that CPEs and CMs meet requirements for your network and service offerings.

7 Be familiar with your channel plan to assign appropriate frequencies.

After these prerequisites are met, you are ready to configure your Casa CMTS.

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 Example

Auto - Completion Use Tab key Auto - Recognition The CMTS recognizes the

command once enough characters are entered to distinguish it from other commands.

copy run start

Instead of: copy running-config

startup-config

Command history Use arrow keys Display error messages

If command syntax is entered incorrectly

Display commands and arguments

“?” 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.

Shortcuts using the alias command (Rel. 5.4 and later).

To shorten the “show cable modem” command to “scm,” enter: CASA-CMTS: alias scm “show cable modem”

Starting the system configuration This section describes some basic procedures to start your Casa CMTS configuration. It contains following topics: x� Connecting the console x� Starting the system x� Viewing loaded software version x� Viewing the system hardware configuration x� Viewing the system running configuration x� Entering configuration mode x� Configuring CMTS device contact and location strings x� Saving the configuration to NVRAM x� Resetting the IP address x� 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


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 Command Purpose 1 reset-console

Example: CASA-CMTS# reset-console

Reapplies TTY console port default parameters.

Starting the system Follow the steps below to start your system:

Step Command Purpose 1 Toggle the power switch.

Turn on the power.

2 ... ... CASA-CMTS>

Observe the console terminal for boot process. 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.

3 enable Example: CASA-CMTS> enable Password: casa CASA-CMTS#

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.

CASA CMTS


Viewing the loaded software version Use the show version command to view the system software version after entering the enable mode. Step Command Purpose

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

Display the system software version.

Viewing the system hardware configuration Use the following command to view the system hardware configuration after entering the enable mode. Step Command Purpose

1 show system Example: CASA-CMTS# show system

Display the CMTS hardware configuration.

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 Command Purpose 1 show running-config

Example: CASA-CMTS# show running-config

Display a subset of system software configurations and settings.

2 show running-config verbose Example: CASA-CMTS#show running-config verbose

Display all the default values of system software configurations and settings.

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

1 config Example: CASA-CMTS#config CASA-CMTS(config)#

Enter configuration mode (config).

2 end Example: CASA-CMTS(config)#end CASA-CMTS#

Exits configuration mode.

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 Command (config) Purpose 1 device {contact <string> | location <string>}

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”

Specify the CMTS device contact and location information strings. 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


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 Command (config) Purpose 1 [no] secure console

Example: CASA-CMTS(config)# secure-console CASA-CMTS(config)# no secure-console

Configure console security at the CMTS. Use the no form of the command to remove console security.

2 console-password <string> console-password encrypted <string> Where:

<string> Specifies either the normal or encrypted password string using up to 32 alphanumeric characters.

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

Configure either a normal or encrypted password for CMTS console access.

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 Command (config) Purpose 1 [no] console timeout <minutes>

Where:

<minutes> Specifies the number of minutes in the range 1 to 1440.

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

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

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

Step Command Purpose 1 copy running-config startup-config [unconditional]

Save the current running-configuration 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 Command Purpose

1 copy running-config startup-config Example: CASA-CMTS#copy running-config startup-config Note: This command operates at the top level of the CLI while in configuration mode.

Store the configuration or changes to your startup configuration in NVRAM.

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

CASA CMTS


Resetting the IP address To reset the IP address, log in through the console port and perform the following:

Step Command Purpose 1 Login through the console port Reset the eth 0 IP

address requires access through the console port.


Enter configuration mode.

3 Interface eth 0 Example: CASA-CMTS(config)#interface eth 0 CASA-CMTS(conf-if-eth 0)#

Select the eth 0 interface.

4 ip address <ip-address> <mask> Where:

<ip-address> IP address in dotted decimal format A.B.C.D.

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

Reset the system IP address.

Restoring factory defaults To restore the factory defaults, perform the following:

Step Command Purpose 1 Login as root. Root permission is required

to reset all defaults. 2 del startup-config

Example: CASA-CMTS# del startup-config

Delete the current configuration.

3 system reboot Reboot the system so that the default configuration is applied.

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


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


General configuration The following sample configuration includes spectrum management, channel bonding, and load-balancing 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


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


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


2 Configuring and managing the CMTS from the CLI

The CASA CMTS system is managed and configured through Casa’s 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:

x Managing the system Configuration:

x Managing configurations

x Managing NVRAM files

x Updating system software

x Management ports (Fast Ethernet)

x GigE Ethernet, loopback, and trunk interfaces

x DHCP and DHCP leasequery

x LACP

x PIM-SM

x OSPF, RIP, and BGP

x Virtual private networks (VPNs and L2VPNs)

x TACACS+ and RADIUS AAA

x Streams

x Downstream QAM ports and upstream port interfaces

x Logical upstream channels

x MAC domains

x IP bundles

x Service and bonding groups

x Modulation profiles

x Multicast operations

x Cable service classes

x PacketCable

x DSG tunnels and tunnel groups

x DOCSIS BPI/BPI+

x Source Address Verification

x Spectrum Management

x Load balancing

CASA CMTS


x Channel bonding

x Quality of Service (QoS)

x SNMP

x IPDR

x IPsec

x Cable modems

x Subscriber management

x Configuring MPEG-compliant features

x Configuring DVB-compliant Features

x Time zone settings

x IP access lists

x Configuring DOCSIS event notification policy

x Logging commands

Managing the system This section covers commands for the following operations:

x Entering and exiting privileged mode

x Changing passwords for privileged mode

x Resetting passwords from privilege mode to default

x Changing the privileged mode system prompt

x Entering and ending configuration mode.

x Adding user names for Telnet logins

x Displaying Telnet user lists

x Changing Telnet user passwords

x Removing Telnet users

x Displaying the current login user list

x Removing users from the current login session

x Rebooting the system

x Rebooting a specified QAM/Upstream Receiver Module

x Retrieving the system hardware version

x Retrieving the system software version

x Retrieving the system boot device

x Setting the system clock

x Synchronizing the system clock with a network time protocol (NTP) server

x Retrieving the system clock

x Adding an entry to the network routing table

x Removing an entry from the network routing table

CASA CMTS


x Adding an entry to the host routing table

x Removing an entry from the host routing table

x Showing alarm states

x Showing system logs

x Displaying Rapid Spanning Tree Protocol status

x Displaying CPU usage information

x Displaying memory usage information

x 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

1 CASA-CMTS> At initial login, the prompt appears with a > prefix.

2 enable Example: CASA-CMTS> enable

Initiates the privileged mode.

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


1 exit Example: CASA-CMTS# exit

Exits privileged mode.

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

1 password <new_password> Where:

<new_password> New password for entering privileged mode.

Example: CASA-CMTS# password mypassword

Change the password.

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.


1 reset password <new_password> Where:

<new_password> New password for entering privileged mode.

Example: CASA-CMTS# reset password mypassword

Reset the password.

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 Command (config) Purpose

1 [no] service password-encryption Example: CASA-CMTS(config)# service password-encryption CASA-CMTS#

Encrypts MD5 or other passwords.

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

1 hostname <string> Where:

<string> New CLI prompt to be displayed in privileged mode.

Example: CASA-CMTS# hostname host_200

host_200#

Changes the CLI prompt to the specified string.

Setting up a command alias The command can be changed into an alias form in order to facilitate the input. Step Command Purpose

1 [no] alias <command-alias> <original-command> 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#

Enables a command alias.

CASA CMTS


Showing the configured command alias Step Command Purpose

1 show aliases [<command-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.

Shows the configured alias.

Managing configurations and files This section covers commands for the following operations:

x Saving a running configuration to the startup configuration

x Copying a startup configuration to a file

x Restoring the startup configuration to a file in NVRAM

x Restoring the startup configuration to the running configuration

x Displaying the current running configuration

x 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 startup-configuration settings:

Step Command Purpose 1 copy running-config startup-config [unconditional]

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

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 Command Purpose 1 copy nvram startup-config nvram <filename>

Save the current startup-configuration 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 Command Purpose 1 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 Command Purpose 1 copy startup-config running-config Load the stored

startup-configuration settings to the running-configuration settings.

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 Command Purpose 1 copy running-config ftp <userID> <host-ipaddress>

<remote-dir-path> 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: *****

Copy the running configuration to a new location over FTP.

To copy the running configuration to an external location using TFTP:

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

[<dest-filename>] 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

Copy the running configuration to a new location over TFTP.

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 Command Purpose 1 copy ftp <userID> <host-ipaddress> <source_file> fdsk2

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


<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

Copy a file to a new location over FTP.

CASA CMTS


To copy a source file to an external location over TFTP:

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

[<dest-filename>] 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

Copy a source file to a CMTS location over TFTP.

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


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 Command Purpose 1 copy fdsk2 <source_file> ftp <userID> <host-ipaddress>

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


<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

Copy fdsk2 files to a new location over FTP or TFTP, or copy an existing file to a new name under fdsk2.

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 Command Purpose 1 md5 checksum <filename>

Where:

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

Example: CASA-C10G> md5 checksum filename

Specify the name of the MD5 checksum file.

Displaying fdsk2 directory contents

The dir fdsk2 command lists the directories and files on the C10G fdsk2 drive.

Step Command Purpose 1 dir fdsk2

Example: CASA-C10G> dir fdsk2 total 2079 -rw-r--r-- 1 root root 17538 Nov 4 13:19 cdb.log -rw-rw-rw- 1 root root 23822 Oct 5 16:04 docsislogfile -rw-r--r-- 1 root root 1035812 Nov 4 13:30 logfile -rw-r--r-- 1 root root 1048634 Nov 3 15:46 logfile.old -rw-r--r-- 1 root root 1209 Oct 28 15:24 reboot_log CASA-C10G>

Displaying the C10G fdsk2 directory contents.

Displaying the running configuration

To display the current running-configuration settings:

Step Command Purpose 1 show running-config Display the current

running-configuration settings.

CASA CMTS


Displaying the system startup configuration

To display the system startup-configuration settings:

Step Command Purpose 1 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 1 show this

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

Display the system startup-conf

Managing NVRAM Files

This sub-section covers commands for the following operation: x Listing files in directory x Removing a file from the directory x 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 Command Purpose 1 ls | dir List files in a

CASA CMTS


Example: CASA-CMTS# dir Total 9 -rw—r—r-- 1 root 1 root 8455 Aug 7 13:44 startup-config CASA-CMTS#

directory.

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 Command Purpose 1 remove <filename>

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

Remove or delete a file from the current directory.

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 Command Purpose 1 copy nvram <source-file-name> tftp <host-ip> <target-file-

name> copy nvram <source-file-name> ftp <ftp-user-id> <host-ip> <target-file-name> copy nvram <source-file-name> nvram <target-file-name> Where:

<source-filename> Specifies the file name in NVRAM to be copied.

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

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

Copy a file stored in NVRAM to a remote host.

CASA CMTS


Example: Copy startup-config from NVRAM to host 192.168.2.39 as startup-config-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

Group Capability

0 show commands only Lowest level of operation 1 Operator

CASA CMTS


2 Not Used 3 Not used 4 Not used 5 Not used 6 Maintenance Firmware upgrade, clock, management and GigE

interface management, reboot. 7 VIDEO Video stream and downstream configuration. 8 CMTS All upstream, downstream and MAC domain

configuration. 9 VIDEO2 Video and maintenance. 10 CMTS2 CMTS and maintenance. 11 DCTS DCTS. 12 System Admin All of the above. 13 Diagnostics Diagnostics. 14 Not Used 15 Super user 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 Command (config) Purpose

1 privilege configure all level <number> <”command_string”> privilege exec all level <number> <”command_string”> privilege exec level <number> <”command_string”> Where:

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

“command string” Specifies the command string as entered in the Casa CLI. The string must be enclosed in quotation marks.

Assign CMTS commands to configured user levels.

CASA CMTS


Examples: Level 2 users can configure any parameters inside the interface docsis-mac 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 Command Purpose

1 show ssh server Example: CASA-CMTS# show ssh server SSH Server Enabled: version 2, port 22

Show SSH server information.

2 show ssh hostkey fingerprint [rsa | dsa] Where:

dsa DSA key fingerprint. rsa 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

Check the connected SSH server (CMTS).

3 show ssh hostkey {dsa | rsa | fingerprint} Where:

dsa DSA key.

Displays hot key information.

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/0mMp5FLc7L5ka+W6ksOK 45BSrbVwb4Fk2oCyUJFHUgnfFpSKxSdgVLCeT8VfOSyaLxnLZW7r2PnLIJnb4ft+sPtBYQ Tf17uIJ/gE+o4AdqAq3KibUOlf9GyxzF8sVr8LYrsiENltaBLuDdAAAAFQDWg6//lFi6BI KUqaC7QjFsc6UXfwAAAIAjgo4/yRUASQi/sk8jL1wjL+kpeBoKiqMtcsT/6MeTyxfequGf TybeNxiI+YXI3xPWQKnYFEFr44EBj0pHXBe09hyHoHIHRFRYB55JdGJDqk57DXiAS5yFFT NXF2Griv5mPFvuwA2hnHOVJBucrYLfDZL3+YgKBkov65FyYtssmAAAAIEAzhzwHRxVsU+v wgWdTxLnDQEi6//U82ywJdQjVAK6q+daIarwj5I1YIzNFks/cLRj0ZaBSkBtxoqrjNKdXM nQFre0rbbAknFWk2fnt9mrisFKAe/T9O7Y72lqcd5reB54/UiozE1+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" AAAAB3NzaC1yc2EAAAABIwAAAQEArfdT9vRF5UcDc7fyR2Hgt5RxDHqAsIV5AuFxZxZti8 nAdlmcu6pObu1daGQCYRXUQCWHXuy9Ygi1c2tYRMzTCP3I94hC3ha4RaWZT2MpjfyL+5ml 5NlKX7lBz3yhLQaeHVVkMTQyVMB8kIDABykkKP3v44BMCvbWYdKeA6TbjjADneovdbmdHX tix7XQHDZPhEjYp9PD6tTbCOylp7zzjAcNzZGNG29hH7NECCaS7jaBEIhe4qPKCTYIg6+E 2AY7koxmxcU8guXV4Zgvku8BJqDyje59+FYZF8N3jWAPIsR1Cp1Au3ofgtBk2yjQtFcSux 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>]

Enable the SSH server.

CASA CMTS


Where: <2000-65535> Port number. The default port number is 22.

Example: CASA-CMTS# ssh start [port <2000-65535>]

5 ssh stop Example: CASA-CMTS# ssh stop SSH server stopped.

Disable the SSH server.

6 ssh gen-hostkey {dsa | rsa} Where:

dsa DSA key.

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

Replace the default keys.

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 Command (config) Purpose

1 [no] ssh enable Example: CASA-CMTS(config)# ssh enable CASA-CMTS(config)# no ssh enable

Enables or disables SSH sessions to the CMTS.

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



1 adduser <user-name> [privilege <level>] Enter new password: <password> Re-enter new password: <password> Where:

<user-name> 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#

Add Telnet users.

Displaying Telnet and SSH users To see the list of users who are allowed to log in over Telnet or SSH:


1 show user [current] 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

Displays all registered users, or displays the users who are currently logged on to the CMTS.

CASA CMTS


Changing Telnet and SSH user passwords To change a Telnet or SSH user password:


1 user password <user-name> … Enter new password: <password> Re-enter new password: <password> 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#

Change user password for Telnet login.

� Note: All user passwords can be changed including the root password.

Removing Telnet or SSH users To remove a Telnet or SSH user:


1 deluser <username> Where:

<username> The configured user name text string.

Example: CASA-CMTS# deluser operator

CASA-CMTS#

Remove a user from the CMTS login list.

� Note: The default user-name root cannot be removed from the configuration.

CASA CMTS


Removing a logged-in user To remove a user from the currently logged-in list:


1 deluser <user-id> session <term-id> 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]$

Remove a user from the current login list.

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 Command (config) Purpose

1 [no] telnet port <number> Where:

<number> Specifies a user-defined Telnet port number in the range 1 to 65535. The default Telnet port is 23.

Example: CASA-CMTS# config CASA-CMTS(config)# telnet port 23 CASA-CMTS (config)# show telnet port telnet port 23

Set a Telnet port for Telnet sessions to the CMTS. To remove the Telnet port, use the no form.

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

1 line vty <number> 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

Set a maximum number of concurrent Telnet sessions to the CMTS over the configured Telnet port.

Configuring Telnet and SSH timeout periods Termination time for an inactive telnet session is a configurable feature. Default setting is no time out. Step Command (config) Purpose

1 [no] telnet timeout <minute> Where:

<minute> The inactive Telnet or SSH session time in minutes in the range 1 to 1440 minutes.

Example: CASA-CMTS# config CASA-CMTS(config)# telnet timeout 60 CASA-CMTS# config CASA-CMTS(config)# no telnet timeout

Termination time to inactivate the Telnet or SSH session. To remove the termination time, use the no form.

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


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.


1 system reboot [reason <reason-text>] [in <mmm | hhh:mm> [remind <num=1:60>]] 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 0-59 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 ..

Reboot the CMTS.

CASA CMTS


System reboot reason: test

2 system reboot cancel Example: CASA-CMTS#system reboot cancel

Broadcast Message from root@CASA-CMTS

(/dev/pts/0) at 10:00

*** *** ---SHUTDOWN ABORTED---

***

Cancel a scheduled or delayed reboot.

3 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

1 system reboot confirm Example: CASA-CMTS(config)#system reboot confirm

Instructs the CMTS software to present a reminder to save the configuration

CASA CMTS


CASA-CMTS#system reboot System configuration has been modified. Save [yes/no]? yes Proceed with reload? {confirm | no} [Enter]

prior to reboot.

Rebooting a downstream/upstream module To reboot a downstream/upstream module: Step Command Purpose

1 reboot module <module> Where:

<module> QAM/Upstream Receiver module number.

Reboot a downstream/upstream module.

Displaying the system boot device To display system boot device: Step Command Purpose

1 show bootdev Examples: CASA-CMTS# show bootdev System boot device is: flash1 CASA-CMTS#

Show system boot device.

Displaying the system hardware version To display system hardware version:


1 show system 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

Display the system hardware version.

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:


1

show 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

Display the system software version.

Setting and displaying the system clock To set the system clock:


1 system clock <clock> Where:

<clock> System clock in the format: MMDDhhmmYYYY MM – month, DD -- day, hh – hour, mm – minute, YYYY-- year.

Set the system clock.

CASA CMTS


Example: CASA-CMTS(config)# system clock 071621082004 Fri Jul 16 21:08:00 UTC 2004

2 show clock Example: CASA-CMTS# show clock Fri Jul 16 21:08:06 UTC 2004 CASA-CMTS#

Display the system clock.

Setting and displaying the time zone To set the time zone:


1

system timezone <setting> 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

Set the timezone in which the CMTS is located.

2 show timezone [list] Where:

list Optional: Displays the full list of valid 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

Display the configured timezone or the option list of all time zones.

CASA CMTS


Synchronizing the system clock with an NTP server To synchronize the system clock with a Network Time Protocol (NTP) server: Step Command (config) Purpose

1 ntp {server <server-ip> | scheck | sync <server-ip> | source-interface loopback} 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.

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

Synchronize the system clock with an NTP server.

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 Command (config) Purpose

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

Display current NTP status and connection statistics.

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 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 Command (config) Purpose

1 system rate-limit {broadcast | dlf | multicast} <0 to 4294967295> 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:

Configure CMTS rate limiting for specified packet types in number of packets per second.

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 Command (config) Purpose

1 ntp source-interface loopback <interface-number> Where:

<interface-number>

Specifies the NTP loopback interface number in the range 0 to 15.

Example: CASA-CMTS(config)# ntp source-interface loopback 4

Configure the NTP loopback interface. Use the no form of the command to remove the current setting.

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 Command (config) Purpose

1 [no] route net <net-address> /<mask> gw <gw-ip> [<metric_value>] [no] ip route <net-address>/mask null0 [<metric_value>] 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.

Add an entry to the network routing table. Use the no form of the command to delete the route entry.

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:


1 [no] route host <host-ip> gw <gw-ip> Where:

<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

Add an entry to the host routing table. Use the no form of the command to delete the entry from the host table.

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.


1 [no] route6 net <ipv6_subnet_address/prefix_length> gw <ipv6_address> [no] ipv6 route <net-address>/mask null0 [<metric_value>]

Add an IPv6 entry to the network routing table. Use the no form of the command to delete the IPv6 route.

CASA CMTS


Where: <ipv6_subnet_address/prefix_length>

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

<ipv6_address> Specifies the gateway IPv6 network address containing up to eight 16-bit 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:


1 show route show route6 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

Display routing table, either IPv4 or IPv6.

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.


1 show ip interface brief Example:

Display the current status of all IP interfaces

CASA CMTS


C3000-230(config)#show ip interface brief See sample output below.

configured at the CMTS.

Example: show ip interface brief C3000-230(config)#show ip interface brief

Admin Link

Interface IP-Address Status Status

eth 0 192.168.8.230 up up

loopback0 88.88.88.230 up up

loopback0 128:238:238:238::230 up up

gige 0 192.168.3.230 up up

gige 0 3000::230 up up

gige 3 33.33.33.230 up down

gige 3 4000:238:238:238::230 up down

vlan 34 34.34.34.230 up down

vlan 34 3000:238:238:238::230 up down

vlan 35 35.35.35.230 up down

vlan 36 36.36.36.230 up down

vlan 37 37.37.37.230 up down

vlan 2322 12.232.100.230 up down

ipbundle1 10.230.1.1 up up

ipbundle1.1 10.10.20.1 up up

ipbundle1.1 10.188.1.1 up up

ipbundle2 10.230.20.1 up down

ipbundle2 2000:230:1::1 up 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 Command Purpose

1 show alarm Example: CASA-CMTS# show alarm

Display alarm status.

CASA CMTS


Displaying system logs To show logged system messages:


1 show log 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

Display logged system messages.

Configuring a log message source IP address To specify a log message source IP address:


1 logging source-interface loopback <lo_id> Where:

<lo-id> Loopback interface number in the range 0 to 15. Example: CASA-CMTS(config)# logging source-interface loopback <lo_id>

Specify a log message source IP address.

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


To configure the loopback address as the source and a TID:


1 [no] lawful-intercept {source-interface loopback <0-15> | tid stream-id} Where:

source-interface loopback <0-15>

Loopback interface ID number in the range 0 to 15. The default source address is the MAC domain IP address.

tid stream-id 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 source-interface loopback 0

Configure lawful intercept interface and a configurable TID to support different versions of LI software.

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:

x Bridge failure

x Breakdown in a data path within the confines of the available Bridge LAN components

x 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 Command Purpose

1 show rstp bridge Example: CASA-CMTS# show rstp bridge

Display RSTP status on bridge LAN components

CASA CMTS


To display RSTP status on GigE ports: Step Command Purpose

1 show rstp port [<port-id>] 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>]

Display RSTP status on GigE ports.

Displaying ARP entries To display ARP entries in the system:


1 show arp Example: CASA-CMTS# show arp Address Age Hardware Addr State Type Interface 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

Display ARP entries in the system.

CASA CMTS


Configuring the ARP request interval CMTS sends an ARP request to every CM and CPE periodically. To set ARP request period: Step Command (config) Purpose

1 arp request-interval <interval> 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.

Set the ARP request period.

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 Command (config) Purpose

1 [no] cable arp filter <number> <seconds> Where:

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

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

Set the number of ARP packets to accept within the specified time window. Use the no form of the command to revert to the default settings.

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:


1 clear arp-cache {all | <ip-address>} 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.*.*

Clears an entry in the ARP cache.

Displaying the ARP request interval To display ARP request interval at the CMTS: Step Command Purpose

1 show arp request-interval Example: CASA-CMTS# show arp request-interval

Display ARP request interval at the CMTS

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:


1 [no] arp timeout-cm-reset Example: CASA-CMTS(config)# arp timeout-cm-reset

Disable the feature: CASA-CMTS(config)# no arp timeout-cm-reset

Enable or disable CM reset feature.

Displaying IPv6 information To display information about IPv6:


1 show ipv6 route 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

Display information about IPv6.

To display the IPv6 route advertisement table: Step Command Purpose

1 show router-advertisement Example: CASA-CMTS# show router-advertisement

Display the IPv6 route advertisement table.

CASA CMTS


To display the IPv6 route table: Step Command Purpose

1 show route6 Example: CASA-CMTS# show route6

Display the IPv6 route table.

Displaying the ARP timeout reset configuration Step Command Purpose

1 show arp timeout-cm-reset Example: CASA-CMTS# show arp timeout-cm-reset

Display the ARP timeout reset configuration at the CMTS.

Displaying CPU usage To display CPU usage at the active SMM module:


1 show cpuinfo Example: CASA-CMTS# show cpuinfo

Display CPU usage at the SMM module.

To display CPU usage associated with a line card module:


1 show cpuinfo module <identifier> 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

Display CPU usage associated with a line card module.

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:


1 show cpuinfo all Example: See example below.

Display CPU usage over all modules.

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



1 show cpu-process Example: CASA-CMTS# show cpu-process

Display CPU process usage across the CMTS.

Example: show cpu-process C3000-230# show cpu-process UID PID PPID LWP C NLWP STIME TTY TIME CMD

root 1 0 1 0 1 Nov15 ? 00:00:15 init [3]

root 2 0 2 0 1 Nov15 ? 00:00:00 [kthreadd]

root 3 2 3 0 1 Nov15 ? 00:00:00 [ksoftirqd/0]

root 4 2 4 0 1 Nov15 ? 00:00:00 [events/0]

root 5 2 5 0 1 Nov15 ? 00:00:00 [khelper]

root 6 2 6 0 1 Nov15 ? 00:00:00 [kblockd/0]

root 7 2 7 0 1 Nov15 ? 00:00:00 [kseriod]

root 8 2 8 0 1 Nov15 ? 00:00:00 [casa_help]

root 9 2 9 0 1 Nov15 ? 00:00:00 [pdflush]

root 10 2 10 0 1 Nov15 ? 00:00:00 [pdflush]

root 11 2 11 0 1 Nov15 ? 00:00:00 [kswapd0]

root 12 2 12 0 1 Nov15 ? 00:00:00 [aio/0]

root 86 2 86 0 1 Nov15 ? 00:00:01

To display CPU and memory statistics associated with CMTS processes:


1 show cpu-memory process-list [<module_id> | all] Example: CASA-CMTS# show cpu-memory process-list all

Display CPU and memory statistics across a specified module or across all modules.

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 TIME %CPU %MEM

init 1 root 11:59 00:00:11 0.6 0.0

kthreadd 2 root 11:59 00:00:00 0.0 0.0

migration/0 3 root 11:59 00:00:00 0.0 0.0

ksoftirqd/0 4 root 11:59 00:00:00 0.0 0.0

migration/1 5 root 11:59 00:00:00 0.0 0.0

ksoftirqd/1 6 root 11:59 00:00:00 0.0 0.0

migration/2 7 root 11:59 00:00:00 0.0 0.0

CASA CMTS


ksoftirqd/2 8 root 11:59 00:00:00 0.0 0.0

migration/3 9 root 11:59 00:00:00 0.0 0.0

ksoftirqd/3 10 root 11:59 00:00:00 0.0 0.0

migration/4 11 root 11:59 00:00:00 0.0 0.0

ksoftirqd/4 12 root 11:59 00:00:00 0.0 0.0

migration/5 13 root 11:59 00:00:00 0.0 0.0

ksoftirqd/5 14 root 11:59 00:00:00 0.0 0.0

migration/6 15 root 11:59 00:00:00 0.0 0.0

ksoftirqd/6 16 root 11:59 00:00:00 0.0 0.0

migration/7 17 root 11:59 00:00:00 0.0 0.0

ksoftirqd/7 18 root 11:59 00:00:00 0.0 0.0

migration/8 19 root 11:59 00:00:00 0.0 0.0

ksoftirqd/8 20 root 11:59 00:00:00 0.0 0.0

migration/9 21 root 11:59 00:00:00 0.0 0.0

Displaying memory usage To display memory usage at the SMM module:


1 show meminfo Example: CASA-CMTS# show meminfo

Display memory usage at the SMM module

To display memory usage of a line card module:


1 show meminfo module <id> Where:

<id> Module ID for line cards. Example: CASA-CMTS# show meminfo module 0 Module 0: MemTotal: 245352 kB MemFree : 52672 kB CASA-CMTS#

Display memory usage of a line card module

CASA CMTS


To display memory usage of all modules:


1 show meminfo all 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#

Display memory usage of all modules.

Viewing module statistics The show controller command allows you to display statistics across the installed CMTS modules. Step Command Purpose

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

Display statistics across all modules.

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


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


DBC Response : 0/ups; 0/ds

DBC Acknowledgements : 0/ups; 0/ds

DBC Success : 0/ups; 0/ds

DBC Fail : 0/ups; 0/ds

DBC Partial Service : 0/ups; 0/ds

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


IfOutOctets 2285988

IfOutUcastPkts 49326

IfOutErrors 0

IfOutDiscards 0

C3000-230#

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 Command (config) Purpose

1 [no] monitor keepalive Example: CASA-CMTS(config)# monitor keepalive Disable monitoring: CASA-CMTS(config)# no monitor keepalive

Enable or disable line-card monitoring.

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.


1 [no] monitor gige Example: CASA-CMTS(config)# monitor gige Disable monitoring: CASA-CMTS(config)# no monitor gige

Enable GigE monitoring.

CASA CMTS


Clearing interface statistics To clear all statistics associated with a specified interface:


1 clear interface {docsis-mac | gige | qam | trunk | upstream | xgige} <identifier> stat Example: CASA-CMTS(config)# clear interface gige 0 stat CASA-CMTS(config)#

Clear interface statistics.

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.


1 show monitor Example: CASA-CMTS(config)# show monitor Monitor GIG-E activity : Disabled Monitor Keepalive : Disabled Monitor Daemon : Enabled

Display the current monitor status.

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.


1 auto-reboot monitor <ip-address> [retries] Where:

<ip-address> IP address to ping.

[retries] The number of consecutive pings before reboot. The default is 30 (60 seconds).

Enable GigE monitoring.

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.


1 ping ping6 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 statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2000ms rtt min/avg/max/mdev = 0.067/0.083/0.102/0.017 ms CASA-CMTS(conf-if-vlan 6/10)# In the following example, a ping request is sent to an IPv6 address. CASA-CMTS(conf-if-vlan 6/10)# ping6 2001:0db8:85a3:0000:0000:8a2e:0370:7334

Run the extended ping command.

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


Testing connectivity with extended ping The Casa CMTS supports the extended ping command. Enclose Linux arguments in quotations.


1 ping ping6 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

Run the extended ping command.

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

1 traceroute <ip_address> traceroute6 <ipv6_address> 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 ]"

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

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


-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


max, 1500 byte packets 1 192.168.8.230 (192.168.8.230) 1.624 ms 0.943 ms 0.748 ms

Example output: traceroute to verizon.net (206.46.232.39), 30 hops max, 40 byte packets 1 192.168.2.1 (192.168.2.1) 0.564 ms 0.438 ms 0.402 ms 2 192.168.1.1 (192.168.1.1) 1.724 ms 1.482 ms 1.334 ms 3 192.168.0.1 (192.168.0.1) 3.573 ms 3.308 ms 3.400 ms 4 209.101.35.209 (209.101.35.209) 4.334 ms * 4.179 ms 5 208-41-205-1.client.dsl.net (208.41.205.1) 20.577 ms 16.912 ms 19.954 ms 6 ge-2-2-0.c00.nyc.megapath.net (155.229.123.121) 19.863 ms 17.526 ms

19.568 ms 7 ge-6-5.car1.NewYork1.Level3.net (209.246.126.1) 19.946 ms 17.224 ms

19.897 ms 8 vlan69.csw1.NewYork1.Level3.net (4.68.16.62) 19.893 ms 17.967 ms 19.767

ms 9 ae-64-64.ebr4.NewYork1.Level3.net (4.69.134.113) 24.904 ms 22.647 ms * 10 ae-6-6.ebr2.NewYork2.Level3.net (4.69.141.22) 19.224 ms 17.346 ms 19.626

ms 11 ae-2-52.edge2.NewYork2.Level3.net (4.69.138.227) 23.098 ms 17.541 ms ae-

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

xe.newyork2.Level3.net (4.68.110.234) 17.970 ms mci-level3-xe.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-0-3.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 POS6-0.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 Command (config) Purpose

1 [no] cable icmp filter <number> <seconds> 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.

Set the number of ICMP packets to accept within the specified time window. Use the no form of the command to revert to the default settings.

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 Command (config) Purpose

1 [no] cable dhcp filter <number> <seconds> 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 DHCP packets, or no filtering.

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

Set the number of DHCP packets to accept within the specified time window. Use the no form of the command to revert to the default settings.

Displaying all filtering settings in the running configuration To display all filtering settings from the running CMTS configuration: Step Command (config) Purpose

1 show cable filter running-config Example: CASA-C3000(config)#show cable filter running-

config cable arp filter 8 2 cable dhcp filter 100 2 cable icmp filter 0 2 cable igmp filter 4 2 CASA-C3000(config)#

Display the filter settings from the running configuration.

CASA CMTS


Setting channel utilization intervals To set the channel utilization interval (the interval over which the channel utilization information is collected and averaged):


1 channel-utilization-interval <0-86400> 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

Set the channel utilization interval in seconds.

Displaying channel utilization To see the utilization on all channels:


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

Show the utilization on all channels

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


1/0/1 (555000000 Hz) down 0 0 0 1/0/2 (561000000 Hz) down 0 0 0 1/0/3 (567000000 Hz) down 0 0 0 1/1/0 (549000000 Hz) down 0 0 0 1/1/1 (555000000 Hz) down 0 0 0 1/1/2 (561000000 Hz) down 0 0 0 1/1/3 (567000000 Hz) down 0 0 0 1/2/0 (549000000 Hz) down 0 0 0 1/2/1 (555000000 Hz) down 0 0 0 1/2/2 (561000000 Hz) down 0 0 0 1/2/3 (567000000 Hz) down 0 0 0 1/3/0 (549000000 Hz) down 0 0 0 1/3/1 (555000000 Hz) down 0 0 0 1/3/2 (561000000 Hz) down 0 0 0 1/3/3 (567000000 Hz) down 0 0 0 2/0/0 (549000000 Hz) down 0 0 0 2/0/1 (555000000 Hz) down 0 0 0 2/0/2 (561000000 Hz) down 0 0 0 2/0/3 (567000000 Hz) down 0 0 0 2/1/0 (549000000 Hz) down 0 0 0 2/1/1 (555000000 Hz) down 0 0 0 2/1/2 (561000000 Hz) down 0 0 0 2/1/3 (567000000 Hz) down 0 0 0 2/2/0 (549000000 Hz) down 0 0 0 2/2/1 (555000000 Hz) down 0 0 0 2/2/2 (561000000 Hz) down 0 0 0 2/2/3 (567000000 Hz) down 0 0 0 2/3/0 (549000000 Hz) down 0 0 0 2/3/1 (555000000 Hz) down 0 0 0 2/3/2 (561000000 Hz) down 0 0 0 2/3/3 (567000000 Hz) down 0 0 0 3/0.0 (20000000 Hz) down 0 0 0 3/0.1 (20000000 Hz) down 0 0 0 3/1.0 (20000000 Hz) down 0 0 0 3/1.1 (20000000 Hz) down 0 0 0 3/2.0 (20000000 Hz) down 0 0 0 3/2.1 (20000000 Hz) down 0 0 0 3/3.0 (20000000 Hz) down 0 0 0 3/3.1 (20000000 Hz) down 0 0 0 3/4.0 (20000000 Hz) down 0 0 0 3/4.1 (20000000 Hz) down 0 0 0 3/5.0 (20000000 Hz) down 0 0 0 3/5.1 (20000000 Hz) down 0 0 0 3/6.0 (20000000 Hz) down 0 0 0 3/6.1 (20000000 Hz) down 0 0 0 3/7.0 (20000000 Hz) down 0 0 0 3/7.1 (20000000 Hz) down 0 0 0 4/0.0 (20000000 Hz) down 0 0 0 4/0.1 (20000000 Hz) down 0 0 0 4/1.0 (20000000 Hz) down 0 0 0 4/1.1 (20000000 Hz) down 0 0 0 4/2.0 (20000000 Hz) down 0 0 0 4/2.1 (20000000 Hz) down 0 0 0 4/3.0 (20000000 Hz) down 0 0 0 4/3.1 (20000000 Hz) down 0 0 0 4/4.0 (20000000 Hz) down 0 0 0 4/4.1 (20000000 Hz) down 0 0 0 4/5.0 (20000000 Hz) down 0 0 0 4/5.1 (20000000 Hz) down 0 0 0 4/6.0 (20000000 Hz) down 0 0 0 4/6.1 (20000000 Hz) down 0 0 0 4/7.0 (20000000 Hz) down 0 0 0

CASA CMTS


4/7.1 (20000000 Hz) down 0 0 0 5/0.0 (20000000 Hz) down 0 0 0 5/0.1 (20000000 Hz) down 0 0 0 5/1.0 (20000000 Hz) down 0 0 0 5/1.1 (20000000 Hz) down 0 0 0 5/2.0 (20000000 Hz) down 0 0 0 5/2.1 (20000000 Hz) down 0 0 0 5/3.0 (20000000 Hz) down 0 0 0 5/3.1 (20000000 Hz) down 0 0 0 5/4.0 (20000000 Hz) down 0 0 0 5/4.1 (20000000 Hz) down 0 0 0 5/5.0 (20000000 Hz) down 0 0 0 5/5.1 (20000000 Hz) down 0 0 0 5/6.0 (20000000 Hz) down 0 0 0 5/6.1 (20000000 Hz) down 0 0 0 5/7.0 (20000000 Hz) down 0 0 0 5/7.1 (20000000 Hz) down 0 0 0

Displaying upstream channel utilization To display the utilization on all upstream channels:


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

Show the utilization on upstream channels

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


4/0.0 (32600000 Hz) up 0 0 0

4/0.1 (34200000 Hz) up 0 0 0

4/1.0 (35800000 Hz) up 0 0 0

4/1.1 (37400000 Hz) up 0 0 0

Displaying downstream channel utilization To see the utilization on all downstream channels:


1 show docsis channel utilization Example: CMTS(config)# show docsis downstream channel utilization

Show the utilization on all downstream channels

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


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:


1 system monitor <unit> enable | disable Where:

<unit> CPU, fan, memory, power, or temperature Example: CASA-CMTS(config)#system monitor cpu enable

Enable or disable the system monitor.

In addition, the CPU and memory usage thresholds can be defined in each module. To configure the CPU monitor: Step Command (config) Purpose

1 system monitor cpu <num> threshold <pct> Where:

<num> Slot number of the module (enter smm for the Switch and Management module.

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

Configure the CPU monitor.

CASA CMTS


To configure the memory monitor:


1 system monitor memory <num> threshold <amt> Where:

<num> Slot number of the module. Enter smm for the Switch and Management Module.

<amt> Amount of memory used in the range (1 to 512 MB).

Configure the memory monitor.

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. Enter configuration mode. Step 2. Enter fast Ethernet interface mode. Step 3. Set an IP address to the interface. Step 4. 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

1 interface <eth-port> Where:

<ethport> ethernet port Example: CASA-CMTS(config)# interface eth 0

Enter fast Ethernet interface mode.

2 [no] ip address <ip-address> <subnet-mask> Where:

<ip-address> Text string for standard IP address in format a.b.c.d.

<subnet-mask> Text string for standard subnet mask in format p.q.r.s

Set the fast Ethernet port as the management port.

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

3 end Example: CASA-CMTS(config-if-eth 0)# end

Exit the interface mode.

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


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



<eth-port> ethernet port Example: CASA-CMTS(config)# interface eth 0


CASA CMTS


2 ip access-group <string> Where:

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

Configure an IP Access Group on eth0 or delete the group.

Configuring Gigabit Ethernet (GigE) ports This section describes commands for the following operations:

x Enabling a Gigabit Ethernet port

x Disabling a Gigabit Ethernet port

x Enabling Auto-Negotiation Mode on a Gigabit Ethernet port

x Setting the GigE Port IP address and subnet mask

x Assigning an IPv6 address to the GigE port

x Enabling Auto-Negotiation Mode on a Gigabit Ethernet port

x Disabling Auto-Negotiation Mode on a Gigabit Ethernet port

x Enabling/Disabling IGMP Client Service on a Gigabit Ethernet port

x Displaying Gigabit Ethernet interface configuration

x Enabling a Gigabit Ethernet port

To enable a Gigabit Ethernet port (all ports are disabled by default):


1 interface gige [<slot>/]<port> interface xgige <slot>/<port> Where:

<port> Gigabit Ethernet port number in the range 0 to 11 for C3200/C10200 , 0 to 3 for C2200, 0 to 7 on the C10G

<slot> System slot number on C10G; either 6 or 7

Example:

Enter gige Ethernet interface mode.

CASA CMTS


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

2 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

Enable the GigE port

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 Command (config) Purpose

1 interface gige <port> 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)#

Enter GigE Ethernet interface mode.

2 [no] auto negotiate Where: <port> Gigabit Ethernet port number in the range 0 to

11. Example: CASA-CMTS(config-if-gige 1)# auto negotiate Disable mode: CASA-CMTS(config-if-gige 1)# no auto negotiate

Enable or disable auto-negotiation mode.

CASA CMTS


Assigning or removing a Gigabit Ethernet port IP address To assign an IP address to a Gigabit Ethernet port: Step Command (config) Purpose




Enter GigE interface mode.


<ip-address> Text string for standard IP address in the format a.b.c.d.

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

Assign an IP address to a GigE port.

Assigning an IP access group to a Gigabit Ethernet port To assign an IP access group to a Gigabit Ethernet port:






CASA CMTS


2 ip access-group <string> Where:

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

Assign an IP access group to a GigE port.

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.



<port> Gigabit Ethernet port number. Valid values are 0 to 11 for C3200/C10200 and 0 to 3 for C2200.


Enter Gigabit Ethernet interface mode.

2 [no] ipv6 address <ipv6-address>/<mask_len> Where:

<ipv6-address> Text string for standard IPv6 address format : xxxx:xxxx:xxxx:...:xxxx

<mask_len> Standard subnet mask.Usable addresses: 2001:0db8:0100:f101:0210:a4ff:fee3:9566 2001:0000:0000:0000:0000:0000:1000:1 (This can be shortened to: 2001::1000:1) One sequence of 20 bit blocks containing only zeroes can be replaced with “::“

Example: Assign IPv6 address 2000::1000:1/64 to Gigabit Ethernet port 1: CASA-CMTS(config-if-gige 1)# ipv6 address 2000::1000:1/64

Assign an IPv6 address to a Gigabit Ethernet port.

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:



<port> GigE port number in the range 0 to 11 for C3200/C10200 and 0 to 3 for C2200.



2 [no] vlan <vlan-id> Where:

<port> GigE port number in the range 0 to 11.

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

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

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 Command (config) Purpose




CASA CMTS



2 [no] ip igmp 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)#

Enable or disable IGMP client service.

To configure the IGMP version: Step Command (config) Purpose

1 igmp client version <version_number> Where:

<version_number>

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

Configure the IGMP version on the CMTS.

Configuring the MTU size on a Gigabit Ethernet interface (5.4) To configure the MTU size of a GigE port interface: Step Command (config) Purpose





2 mtu <1500-1800> Where:

Configure the MTU size of a GigE port interface

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

1 show interface gige [<port>] 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

Display the GigE interface configuration.

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

1 show interface xgige [<slot>/<port>] Where:

<port> Specifies the 10GigE port number in the range 0 to 1 using the system slot and interface number.

Display the 10 GigE interface configuration.

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:


1 show interface { gige | xgige} <port> {acl-count [details] | brief | lacp status | service-policy-count [details] | stat | throughput [duration <seconds>]} 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.

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

Display the GigE interface statistics.

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:

x Entering interface loopback mode

x Specifying the IP address subnet for a loopback interface

CASA CMTS


Enabling interface loopback mode To enter Interface Loopback mode:


1 interface loopback <if_id> 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)#

Enter interface loopback mode.

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:



<if_id> Loopback interface number in the range 0 to 15. Example: CASA-CMTS(config)# interface loopback 4 CASA-CMTS(conf-if-lo 4)#



<ipv6-address> Text string for standard IPv6 address in the format xxxx:xxxx:xxxx:...:xxxx


Example: Assign IPv6 address 2000::1000:1/64 to GigE port 4:

Assign an IPv6 address to a loopback interface.

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:



<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> Specifies the IPv4 address on this loopback interface in standard decimal format.

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

Specify the IPv4 address subnet for a loopback interface.

Assigning an access group to a loopback interface To assign an access group to a loopback interface:



<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 [no] ip access-group <string> Where:

Assign an access group to a loopback interface.

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:


1 logging source-interface loopback <lo_id> Where:

<loid> Loopback interface ID in the range 0 to 15. Example: CASA-CMTS(config)# logging source-interface loopback 0

Configure the log message source IP address

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 Command (config) Purpose

1 [no] ftp-tftp source-interface loopback <id> 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 source-interface loopback 0

Configure a loopback interface as source IP address on FTP/TFTP.

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 Command (config) Purpose

1 lawful-intercept source-interface loopback <number> Where:

<number> The loopback interface number in the range 0 to 15.

Example: CASA-CMTS(config)# lawful-intercept source-interface loopback 2

Set the source loopback interface number for lawful intercept packets.

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:

x Creating/removing a trunk interface

x Setting/removing an IP Address to/from trunk Interface

x Enabling/disabling a trunk interface

x Adding/removing a Gigabit Interface to/from trunk interface

x Enabling/disabling IGMP on a trunk interface

x Applying/removing an IP-Access list on/from trunk interface

x Displaying a trunk-interface configuration

Creating a trunk interface The Casa CMTS supports up to 12 trunk interfaces:


1 [no] interface trunk <number> Where:

<number> Specifies the trunk interface number in the range 1 to 12.

Example: CASA-CMTS(config)# interface trunk 12

Create or remove a trunk interface.

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 Command (config) Purpose



Example: CASA-CMTS(config)#interface trunk 12 C3000-230(conf-if-trunk 12)#

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

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


Assigning an IP address to a trunk interface To set an IP address to the trunk Interface:




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


2 [no] ip address <address> <mask> [no] ipv6 address <ipv6-address>/<mask_len> Where:

<address> IP address assigned to the trunk interface.

<mask> IP address mask.

<ipv6-address> Text string for standard IPv6 address format: xxxx:xxxx:xxxx:...:xxxx


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

Assign an IP address to a trunk interface.

CASA CMTS


Enabling/disabling a trunk interface To enable or disable a trunk interface:




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


2 [no] shutdown Example: Enable an interface: CASA-CMTS(conf-if-trunk num)# no shutdown

Disable an interface: CASA-CMTS(conf-if-trunk num)# shutdown

Enable or disable a trunk interface. The default is disabled.

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:




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


2 [no] gige <port> Where:

<port> GigE interface port number. Example:

Add or remove a GigE port on a trunk interface.

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:






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

Enable IGMP client services on a trunk interface.

Applying an IP access group to a trunk interface To apply an IP-access group to a trunk interface:






CASA CMTS



2 [no] ip access-group <name> Where:

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

Apply or remove an IP access group on a truck interface.

Displaying a trunk interface configuration To display a trunk interface configuration:


1 show interface trunk [<num>] [acl-count [details] | stat | throughput [duration] | service-policy-count [details] ] Where:

<num> Specifies the trunk interface number in the range 1 to 12.


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



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

Display trunk interface configurations.

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:







2 show arp Example: CASA-CMTS(config)# interface trunk 10

CASA-CMTS(conf-if-trunk 10)# show arp Interface Age Hardware Addr State Type IP Address eth 6/0 00:00:01 0017.1001.5cab dynamic ARPA 192.168.8.1 eth 6/0 00:08:40 0022.0c9a.ea41 dynamic ARPA 192.168.8.12 eth 6/0 00:18:01 bc30.5bd8.0f8e dynamic ARPA 192.168.8.90 eth 6/0 00:00:01 b8ac.6f8f.181f dynamic ARPA 192.168.8.92 eth 6/0 00:00:01 0017.1002.cc40 static ARPA 192.168.8.113 eth 7/0 00:08:24 0022.0c9a.ea41 dynamic ARPA 192.168.8.12 eth 7/0 00:00:01 0017.1002.c4c0 static ARPA 192.168.8.114 CATV-MAC 1 00:00:01 0017.1002.cc4d static ARPA fe80::217:10ff:fe02:cc4d CATV-MAC 2 00:00:01 0017.1002.cc4e static ARPA fe80::217:10ff:fe02:cc4e

Display ARP entries associated with the current trunk interface.

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 Command (config) Purpose 1 [no] nameserver <ip_address>

[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

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

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


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: x downstream-desc-type — Inserts the type value for downstream port descriptor into the

received DHCP packets. x enterprise-num — Inserts the Casa enterprise number into the received DHCP packets. x host-name-type — Inserts the type value for the router host name into the received DHCP

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


1 dhcp-insert downstream-desc-type <value> dhcp-insert enterprise-num <value> dhcp-insert host-name-type <value> dhcp-insert upstream-desc-type <value> 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 enterprise-num <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-desc-type 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

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

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. x dhcp-insert downstream-description x dhcp-insert hostname x 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 IP bundle range option routers 10.10.9.1; <----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


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 Command (config) Purpose 1 dhcp leasequery enforce

dhcpv6 leasequery [enforce] Example: CASA-CMTS(config)#dhcp leasequery enforce

Configure the Casa CMTS to send DHCP lease query requests to the DHCP server.

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

Display the current lease query setting.

This allows IP addresses of the CPE to be verified. The DHCP server will return an acknowledgement message that contains the MAC address of the CPE assigned to this IP address, if there is one. This function will not interfere with valid RF traffic while it prevents users from assigning unauthorized IP addresses to CPE. The default configuration for these commands is off. DHCP authorization must also be enabled in the MAC domain for lease queries to be sent. If dhcpv6 leasequery is set, a leasequery will be sent to the DHCP server when a packet with a source IPv6 address (that is not present in the ARP and local DHCPv6 CPE lease table) is received. If dhcpv6 leasequery enforce is set, a leasequery will be sent when a packet with a source IPv6 address (that is not present in the ARP table) is received.

The messages returned from the server have the following default values: x 30 – query x 31 - unassigned x 32 – unknown x 33 – active

To change the default coding:

Step Command (config) Purpose 1 dhcp leasequery message-coding

Example: CASA-CMTS(config)#dhcp leasequery message-coding

Change the default coding

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:

x LACP Global Configure

x LACP Administrative Key

x LACP Port Priority

x LACP Group Configure and Display

x LACP GigE Interface Configure and Display

x LACP Trunk Interface Configure and Display

Enabling the LACP global configuration To configure or disable the LACP priority:


1 [no] lacp system priority <number> 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

Configure or disable the LACP priority.

To display the LACP system ID:


1 show lacp system-id Example: CASA-CMTS(config)#show lacp system-id

Note: The system ID is the system priority and system MAC.

Display the LACP system ID.

CASA CMTS


Setting LACP port priority To configure LACP port priority value:






2 lacp port-priority <number> Where:

<number> Port priority number in the range 1 to 65535

Example: CASA-CMTS(config-if-gige 1)#lacp port-priority 1

Configure LACP port priority value.

Setting the LACP system port priority To configure LACP system priority:


1 [no] lacp system priority <num=1:65535> Where:

<num=1:65535> Priority range from 1 to 65535. Example: CASA-C2200(config)#lacp system priority 1

Configure LACP system port priority value.

Displaying LACP group information To display the summary information of all the LACP groups:


1 show lacp summary Example: CASA-CMTS#show lacp summary

Display the summary information of all LACP groups.

CASA CMTS


Example: Display LACP summary CASA-CMTS#show lacp summary Flag: A--LACP Activity, B--LACP Timeout, C--Aggregation, D—Synchronization E--Collecting, F--Distributing, G--Defaulted, H—Expired Port Trunk Mode State Priority Flag Receive Send gige1 1 active down 1000 ACG 0 0 gige2 1 active down 2000 ACG 0 0 gige3 1 passive down 3000 CG 0 0

Configuring and displaying LACP port priority on GigE interfaces To configure the port priority in the LACP group:






2 lacp port-priority <number> Where:

<number> Port priority number in the range 1 to 65535

Example: CASA-CMTS(config-if-gige 1)#lacp port-priority 1

Configure LACP Port priority value.

To configure the LACP port priority to default:






CASA CMTS


2 no lacp priority Example: CASA-CMTS(config-if-gige 1)# no lacp priority

Configure the LACP port priority to the default setting.

To display the LACP status of the port defined by the port number:


1 show interface gige <port num> lacp status 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

Display the LACP status of the port defined by the port number.

Example: Displaying LACP status CASA-CMTS# show interface gige 3 lacp status Flag: A--LACP Activity, B--LACP Timeout, C--Aggregation, D—Synchronization E--Collecting, F--Distributing, G--Defaulted, H—Expired 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 Command (config) Purpose

1 [no] interface trunk <num> Where:

<num> Trunk interface number in the range 1 to 12.


Create a trunk interface.

2 [no] gige 1 [mode active] Example: CASA-CMTS(config-if-trunk 1)#gige 1 mode active. . CASA-CMTS# show interface trunk 1

Add or remove a gige port to a channel group.

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:


1 show lacp system-id Example: CASA-C2200(config)#show lacp system-id System ID: 32768,00:17:10:00:13:67

Display LACP system information.

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.






2 [no] ip router isis <string> Where:

<string> IPv4 routing process tag.

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

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:






2 [no] ipv6 router isis <string> Where:

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

Configure or disable an IPv6 ISIS under a GigE port.

Configuring an IS-IS circuit type on a GigE interface To configure circuit type on a GigE Interface:




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


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

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

Configure or disable circuit type for a GigE interface.

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:






2 [no] isis network point-to-point Example: CASA-CMTS(config-if-gige 0)#isis network point-to-point To disable: CASA-CMTS(config-if-gige 0)#no isis network point-to-point

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

CASA CMTS


Configuring the complete sequence number PDU (CSNP) interval To configure the CSNP interval in seconds:






2 [no] isis csnp-interval <num=0:65535> [(level-1|level-2)] Where:

<num=0:65535> 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

Configure or disable the CSNP interval in seconds.

Configuring the IS-IS Hello interval To setup the ISIS Hello interval in seconds






2 [no] isis hello-interval <num=1:65535> [(level-1 | level-2)] Where:

<num=1:65535> Hello interval in seconds.

Setup or disable the ISIS Hello interval in seconds

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 hello-interval 40 level-2 Disable the ISIS Hello interval: CASA-CMTS(config-if-gige 0)#no isis hello-interval 40 level-2

Configuring the IS-IS Multiplier for Hello holding time To configure the ISIS Multiplier for the Hello holding time:






2 [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 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 hello-multiplier

Configure or disable the ISIS Multiplier for Hello Holding time

CASA CMTS


Enabling padding on IS-IS Hello packets To pad Hello packets:






2 [no] isis hello padding 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)#

Enable padding on Hello packets.

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:






2 [no] isis metric <num=1:16777214> [level-1 | level-2] Where:

<num=0:16777214> Sets the default metric for IS-IS circuit in the range 1 to 16777214.

Configure or delete the default IS-IS metric .

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:






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

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

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

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:



<port> Gigabit Ethernet port number. Valid values are 0 to 11 for C3200/C10200 and 0 to 3 for C2200.



2 [no] isis priority <num=0:127> [(level-1|level-2)] Where:

priority <num=0:127> 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

Setup IS-IS priority.

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.



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



CASA CMTS


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


1 [no] router isis <string> 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

Configure the IS-IS router area tag.

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 Command (config-router-isis) Purpose

1 list Example: CASA-CMTS(config-router-isis)# list area-password WORD area-password WORD authenticate snp (send-only|validate) authentication key-chain XXX

Display the IS-IS command list.

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 address-family command to remove the IPv6 setting.


1 [no] router isis <string> 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

Configure the IS-IS router area tag.

2 [no] address-family ipv6 [unicast] Parameter settings: default-information originate exit-address-family multi-topology [level-1 | level-2 | level-1-2 | transition]

Configure the IPv6 parameter for IS-IS.

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.

default-information originate

Generates a default route within the IS-IS routing domain for distribution to other IS-IS neighbors.

exit-address-family

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.

redistribute Captures routes from other routing protocols. IS-IS then advertises these routes to Level-1, Level-2, or both Level-1 and -2 routers.

x bgp -- Specifies IS-IS to advertise Border Gateway Protocol (BGP) routes.

x connected -- Specifies IS-IS to advertise connected routes from a directly-connected subnet or host.

x isis -- Specifies IS-IS level-1/level-2 route distribution.

x static -- Specifies IS-IS to advertise statically-configured 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


<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 Command (config-router) Purpose

1 [no] area-password <password> [authenticate snp {send-only | validate}] 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:

Enter or disable the IS-IS area plain text password setting.

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 Command (config-router) Purpose

1 [no] authentication key-chain <name> [level-1 | level-2] 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 key-chain charlie CASA-CMTS(config-router-isis)# Disable the IS-IS authentication key chain: CASA-CMTS(config-router-isis)#no authentication key-chain CASA-CMTS(config-router-isis)#no authentication key-chain charlie

Specify or delete the IS-IS key chain name for IS-IS authentication.

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 area-password or the domain-password command.

CASA CMTS


Step Command (config-router) Purpose

1 [no] authentication mode md5 [level-1 | level-2] 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

Specify or remove the IS-IS authentication mode setting.

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 Command (config-router) Purpose

1 [no] authentication send-only [level 1 | level-2] Where:

level-1 Optional. Enables authentication of Level 1 packets sent over the IS-IS interface.

level-2 Optional. Enables authentication of Level 2 packets sent over the IS-IS interface.

Example: CASA-CMTS(config-router-isis)# authentication send-only CASA-CMTS(config-router-isis)# Disable the IS-IS authentication mode: CASA-CMTS(config-router-isis)#no authentication send-only

Enable the IS-IS send-only option. Use the no form of the command to disable the send-only option

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 Command (config-router) Purpose

1 [no] default-information originate 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

Generate a default route within the IS-IS routing domain. 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 Command (config-router) Purpose

1 [no] domain-password <password> [authenticate snp {send-only | validate}] 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

Enter or disable the IS-IS domain plain text password setting.

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 link-state database, each router determines the shortest path to other routers. Use the show isis database command to display the current link state statis


1 [no] is-type {level-1 | level-1-2 | level-2-only} 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

Configure the IS-IS routing algorithm.

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 Command (config-router) Purpose

1 [no] lsp-gen-interval {<seconds> | level-1 <seconds> | level-2 <seconds>] 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

Configure the minimum elapsed time in seconds between generated LSPs.

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 router’s 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 Command (config-router) Purpose

1 [no] lsp-lifetime <seconds>

Configure the maximum time in

CASA CMTS


Where: <seconds> Specifies the maximum number of seconds that an

LSP is allowed to exist in the router’s 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).

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

seconds for an LSP to exist in the link state database with being updated.

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 Command (config-router) Purpose

1 [no] metric-style {narrow | transition | wide] 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

Configure the IS-IS route redistribution 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


x 47 – AFI x 0004.0000.0000 – area identifier x 1234.5678.2005 – system identifier x 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 Command (config-router) Purpose

1 [no] net <network-entity-title> Where:

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

Enable or disable the network entity title.

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 Command (config-router) Purpose

1 [no] hostname dynamic Example: CASA-CMTS(config-router-isis)# hostname dynamic Disable the IS-IS dynamic hostname: CASA-CMTS(config-router-isis)#no hostname dynamic

Enable or disable the dynamic hostname capability.

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



1 [no] passive-interface {gige | ip-bundle | loopback | trunk | vlan | xgige} <interface_name> 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

Configure the IS-IS passive interfaces.

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 Command (config router) Purpose

1 redistribute {bgp | connected | isis | rip | static | ospf} {level-1 | level-2 | level-1-2} metric <number> metric-type {internal | external} [route-map <name>] 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.

Configure IS-IS to advertise routes from other protocols to Level-1, Level-2, or Level-1-2 routers.

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 Level-2 routers.

metric <number>

Specifies the metric to be applied to IS-IS route distribution in the range 0 to 4261412864.

metric-type Specifies an internal or external metric type. Internal metrics (less than 64) are generated within the IS-IS domain; external metrics (greater than 64) are generated outside of the IS-IS routing domain or from other protocols. The default metric-type is internal.

route-map <name>

Optional. Instructs IS-IS to apply a previously-configured 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 Command (config-router-isis) Purpose

1 set-overload-bit on-startup <seconds> [suppress external] [interlevel] set-overload-bit on-startup <seconds> [suppress interlevel] [exernal] set-overload-bit suppress external [interlevel] [on-startup <seconds>] set-overload-bit suppress interlevel [external ] [on-startup <seconds>] Where:

on-startup <seconds>

Specifies the temportary time in seconds to advertise the CMTS as overloaded after a system reboot in the range 5 to 86400 seconds.

suppress Specifies that IP prefixes from other protocols not

Configure IS-IS to notify neighbor routers that the CMTS is unavailable to forward packets after a system reboot.

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 Command (config-router-isis) Purpose

1 [no] spf-interval-exp <minimum_delay> <maximum_delay> [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 0-2147483647 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.

Examples: CASA-CMTS(config-router-isis)#spf-interval-exp 50 500 CASA-CMTS(config-router-isis)#spf-interval-exp level-1 50 500

Set the shortest path first (SPF) time interval to elapse between received SPF updates. Use the no form of the command to remove the current setting.

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 Command (config-router-isis) Purpose

1 [no] summary-address <ip_address/netmask> [level-1 | level-2 | level-1-2] Where:

ip_address/netmask Specifies the IPv4 summary address and the network mask to be announced in IS-IS link state packets forwarded to IS-IS 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 summary-address prefix setting to Level-1 areas only.

level-2 Optional. Forwards the IPv4 summary-address prefix setting to Level-2 areas only.

level-1-2 Optional. Forwards the IPv4 summary-address prefix setting to both Level-1 and Level-2 areas.

Examples: CASA-CMTS(config-router-isis)# CASA-CMTS(config-router-isis)#spf-interval-exp level-1 50 500

Set the IPv4 summary prefix to be included in IS-IS advertisements neighbor routers. Use the no form of the command to remove the current setting.

Displaying the IS-IS area configuration To show the IS-IS area configuration:


1 show isis area <tag> database [detail [slot <number>] | l1 | l2 | level-1 | level-2 | slot <number> ] show isis area <tag> neighbors [detail [slot <number>] | slot <number>]

Display the IS-IS area configuration.

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:


1 show isis counter [slot <number>} Where:

slot <number> Specifies the CMTS system slot number over which IS-IS is running.

Example:

Show ISIS route statistics for all configured areas.

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:


1 show isis database [detail [slot <number> ]| l1 | l2 | level-1 | level-2 | slot | verbose [slot <number>] ] 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

Display the IS-IS database.

CASA CMTS


Displaying the IS-IS interface statistics To show the ISIS statistics counters:


1 show isis interface counter [slot <number>]] show isis interface docsis-mac <id> show isis interface gige <slot/port> show isis interface loopback <number> show isis interface trunk <id> show isis interface vlan <slot/vlanId> show 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

Show ISIS route statistics for all configured areas.

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:


1 show isis neighbors [detail [slot <number>] | slot <number> ] Where:

detail Displays full IS-IS neighbor information. Optional system slot number may be specified.

slot <number>

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:

Displays the ISIS neighbor database.

Displaying the IS-IS topology information To show the ISIS routing topology across Level-1 and Level-2 areas:


1 show isis topology [level-1 [slot <number>] | level-2 [slot <number>] | slot <number> ] 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:

Shows the ISIS topology database.

CASA CMTS


Area chris: Area AAA:

Displaying the IPv4 and IPv6 IS-IS routing table To show the IPv4 routing table:


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

Display the IPv4 or IPv6 IS-IS routing table.

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


Enabling PIM-SM on a GigE or loopback interface To enable PIM-SM on a GigE interface:






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

Enable PIM-SM. Use the no form of the command to disable PIM-SM on a previously-configured GigE interface.

Displaying the current PIM-SM interface and neighbor configurations To display the PIM-SM interface and neighbor configurations: Step Command Purpose

1 show ip pim interface show ip pim neighbor Example: CASA-CMTS# show ip pim interface Address Interface Ver Nbr Count DR Prior DR 192.168.6.170 Gige0 v2 2 1 192.168.6.144 170.1.1.1 Lookback1 v2 0 0 0.0.0.0 CASA-CMTS# show ip pim neighbor Neighbor Address Interface Uptime/Expires DR Priority

Display the current PIM-SM configuration.

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



1 [no] ip pim rp-address <ip_address> [access-list <name> | override] Where :

<ip_address> The IP address of the multicast group rendezvous point.

access-list <name>

Optional: The named access-list reference associated with the multicast group.

override Optional: Overrides dynamically learned rendezvous point mappings.

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

Specify the static RP address Use the no form of the command to delete the RP address assignment.

2 show ip pim rp [mapping] show ip pim rp-hash <ip_address> Where:


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)

Display the RP groups and mappings.

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 Command (config) Purpose

1 [no] ip pim rp-candidate {gige <number> | loopback <number>} [group-list <string> | interval <seconds> | priority <range>] Where :

<number> The GigE or loopback interface number.

group-list <string>

Optional: The name or number of the previously-configured multicast access control list.

interval <seconds>

Optional: The time in seconds to elapse between RP candidate advertisements.

priority <range>

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.

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

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

CASA CMTS


2 show ip pim rp [mapping] show ip pim rp-hash <ip_address> Where :


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)

Display the RP groups and mappings.

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:


1 [no] ip pim bsr-candidate {gige <number> | loopback <number>} [<hash_mask> <piority>] Where :

<number> The GigE or loopback interface number.

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

Specify the bootstrap router candidate. Use the no form of the command to delete the BSR

CASA CMTS


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.

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

candidate assignment.

2 show ip pim bsr-router Example : CASA-CMTS(config)#show ip pim bsr-router

This system is the Bootstrap Router (BSR)

BSR address:192.168.3.232

Uptime: 0:0:10:8,BSR Priority:0, Hash mask length:10

Next bootstrap message in 7

Candidate RP: 192.168.3.232(gige 1)

Holdtime 150 seconds

Advertisement interval 60 seconds Next advertisement in 7

Display the BSR router configuration.

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

1 [no] ip pim spt-threshold {<number > | infinity} Where :

<number> The traffic rate in kilobits per second (Kbps) . The valid range is 1 to 4294967.

infinity Prevents PIM sparse mode from switching to a source tree; only shared trees are used when infinity is set.

Example:

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

CASA CMTS


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

2 show ip pim spt-threshold Example : CASA-CMTS(config)#show ip pim spt-threshold

ip pim spt-threshold 1500

Display the SPT threshold setting.

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

1 [no] ip pim ssm {default | range <string>} Where :

default Specifies the group IP address range 232.255.0.0/8.

range <string>

Specifies the group range associated with an ACL name or number to be used with SSM.

Example: CASA-CMTS(config)# ip pim ssm default CASA-CMTA(config)# ip pim ssm range acl1

Specify the SSM group range. Use the no form of the command to remove the SSM setting.

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:

x area authentication

x area default-cost x area filter-list x area export-list x area import-list x area nssa

x area range

x area shortcut

CASA CMTS


x area stub

x area virtual-link

x auto-cost x default-information

x default-metric x distance x distribute-list x list x neighbor x network

x ospf abr-type

x passive-interface x refresh x router-id x timers x ip ospf authentication x ip ospf authentication-key x ip ospf cost x ip ospf hello-interval x ip ospf authentication x ip ospf message-digest-key x ip ospf retransmit-interval x ip ospf transmit-delay x show ip ospf x show ip ospf border-routers x show ip ospf database x show ip ospf interface x show ip ospf neighbor x show ip ospf route x show ip route

CASA CMTS


Entering OSPF configuration mode To enter OSPF configuration mode:


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

Enter OSPF configuration mode.

Exiting OSPF configuration mode To exit OSPF Configuration mode:


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

Exit OSPF configuration mode.

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



2 [no] area <id> authentication [message-digest] Where:

<id> The area identifier specified as either a decimal value (0–4294967295) or an IP address (A.B.C.D).

message-digest Optional. Enables Message Digest 5 (MD5) authentication on the area specified by the area-id argument.

Example: Enable authentication for areas 10 of OSPF routing process:

Enable or disable OSPF area authentication.

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 Command (config) Purpose



2 [no] area <id> default-cost <cost> Where:

<id> Area identifier specified as either a decimal value (0-4294967295) 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.

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

Configure or disable a cost for the default summary route.

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



2 [no] area <id> filter-list prefix {<list-name> in | out} Where:


prefix Keyword to indicate that a prefix list is used.

<list-name>

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

Configure or disable the OSPF area filter list.

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 Command (config) Purpose



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

Configure the OSPF area export list.

CASA CMTS


Where: <id> Area identifier. It can be specified as either

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

<list-name> 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 filter-list 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 Command (config) Purpose



2 [no] area id import-list <list-name> Where:

Id Area identifier specified as either a decimal value (0-4294967295) or an IP address (A.B.C.D).

<list-name> Import list name.

Configure or remove the OSPF area import list.

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.




2 [no] area <id> nssa [translate-always | translate-candidate | translate-never] [no-summary] Where:


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

Configure or remove OSPF Area NSSA

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 Command (config) Purpose



2 [no] area <id> range <ip-address>/<mask> [advertise | not-advertise] [cost <cost>] Where:

<id> Area identifier specified as either a decimal value (0–4294967295) 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

Configure or disable the OSPF area range.

CASA CMTS


Configuring the OSPF area shortcut To configure the area’s shortcutting mode, use the area shortcut command in router configuration mode. To disable this function, use the no form of this command. Step Command (config) Purpose



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


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

Configure or disable the OSPF area shortcut.

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 Command (config) Purpose



CASA CMTS


2 [no] area <id> stub [no-summary] Where:


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

Enable or disable the OSPF area 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



2 [no] area <id> virtual-link <router-id> [authentication [message-digest|null]] [hello-interval <num>] [retransmit-interval <num>] [transmit-delay <num>] [dead-interval <num>] [[authentication-key <key>] | [message-digest-key <key-id> md5 <key>]] 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.

message-digest|null

Optional. Specifies authentication type and if message-digest authentication is used. If NULL, no authentication is used. Overrides password or message digest

Configure or remove the OSPF area virtual link.

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.

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

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


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



2 [no] auto-cost reference-bandwidth <ref-bw> Where:

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

Configure the OSPF interface auto cost.

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





2 [no] compatible rfc1583 or [no] ospf rfc1583compatibility Example: CASA-CMTS(config-router-ospf)# compatible rfc1583 Disable: CASA-CMTS(config-router-ospf)# no compatible rfc1583

Enable or disable RFC 1583 compatibility.

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 Command (config) Purpose



2 [no] default-information originate [always] [metric <metric-value>] [metric-type <type-value>] [route-map <map-name>] Where:

always Optional. Always advertises the default route regardless of whether the software has a default route.

metric <metric-value>

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

Configure or disable OSPF control-distribution default Information.

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

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)# default-information originate metric 50 metric-type 1 Note: Route maps are not supported in Release 5.2.

Configuring the OSPF default metric To set default metric values for the OSPF routing protocol, use the default-metric command. To return to the default setting, use the no form of this command. Step Command (config) Purpose



2 [no] default-metric <metric-value> Where:

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

Configure or disable OSPF default metric

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 Command (config) Purpose



2 distance { <dist0> | ospf {intra-area <dist1> | inter-area <dist2> | external <dist3> } } Where:

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

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

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

external <dist3> Sets the distance for routes from other routing domains, learned by redistribution. Valid values are 1 to 255. The default value is 110.

Example: Set the external distance to 200: CASA-CMTS(config-router-ospf)# distance ospf external 200

Configure the OSPF administrative distance.

Displaying the OSPF command list To show the OSFP command list, follow the command provided below.




CASA CMTS


2 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 <0-16777215> area (A.B.C.D|<0-4294967295>) export-list NAME area (A.B.C.D|<0-4294967295>) filter-list prefix WORD (in|out) area (A.B.C.D|<0-4294967295>) import-list NAME area (A.B.C.D|<0-4294967295>) nssa area (A.B.C.D|<0-4294967295>) nssa (translate-candidate|translate-never|translate-always) area (A.B.C.D|<0-4294967295>) nssa (translate-candidate|translate-never|translate-always) no-summary area (A.B.C.D|<0-4294967295>) nssa no-summary area (A.B.C.D|<0-4294967295>) range A.B.C.D/M 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 Command (config) Purpose



2 [no] neighbor <ip-address> [priority <num>] [poll-interval <num>] Where:

<ip-address> Interface IP address of the neighbor.

priority <num> Optional. A number that indicates the router priority value of the non- broadcast 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

Configure the OSPF neighbor route.

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



2 [no] network <ip-address>/<mask_prefix> area <area-id> Where:

<ip-address/mask> Specifies the IP address and mask in the format A.B.C.D/M.

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

Configure OSPF routing on an IP network.

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



2 [no] ospf abr-type [cisco | ibm | shortcut | standard] Where:

cisco 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

Configure the OSPF ABR type.

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



2 [no] ospf router-id <router_id> Where:

<router_id> OSPF router id in IP address format. Example: CASA-CMTS(config-router-ospf)# ospf router-id 192.168.3.20

Configure or remove the OSPF route ID.

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



2 [no] passive-interface {dmac | gige | vlan} <id> [<ip_address>] Where:

<id> GigE port ID, docsis-mac ID, or VLAN ID

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

Configure or remove the OSPF passive interface command.

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 Command (config) Purpose



2 [no] distribute-list <list-name> out { bgp | connected | kernel | rip | static } Where:

<list-name> Standard IP access list name. The list defines which networks are to be received and which are to be suppressed in routing updates.

in Applies the access list to incoming routing updates.

Configure or disable the OSPF default metric.

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




2 redistribute {bgp | connected | isis | rip | static} 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 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 | route-map] redistribute static [metric | metric-type | route-map | tag] redistribute static tag <number> [metric | metric-type | route-map] Where:

Redistribute learned routes from other protocols to OSPF neighbors.

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.


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.



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



2 [no] refresh timer <num> Where:

<num> Timer value in the range 10 to 1800 seconds. Example: Set OSPF refresh value to 100 : CASA-CMTS(config-router-ospf)# refresh timer 100

Configure the OSPF refresh parameters.

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



2 [no] route-id <ip-address> Where:

<ip-address> Router ID in IP address format.

Example: CASA-CMTS(config-router-ospf)# route-id 192.168.3.20

Configure or disable the OSPF route ID.

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



2 [no] timers spf <delay-time> <hold-time> Where:

<delay-time> Delay between receiving a change to SPF calculation in the range 0 to 4294967295 in milliseconds. The default value is 33 milliseconds.

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

Configure or disable the OSPF routing timer.

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 Command (config) Purpose





2 ip ospf authentication [message-digest | null] Where:

Message-digest Optional. Specifies that message digest authentication will be used.

null 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

Configure or disable IP OSPF Authentication.

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 Command (config) Purpose





2 [no] ip ospf authentication-key <password> Where:

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

Configure or disable IP OSPF password authentication.

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 Command (config) Purpose





CASA CMTS


2 [no] ip ospf cost <if-cost> Where:

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

Configure or disable the IP OSPF cost.

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 Command (config) Purpose





2 [no] ip ospf dead-interval <num> Where:

<num> 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 hello-interval. Example: Set the OSPF dead interval to 33 seconds: CASA-CMTS(config-if-gige 0)# ip ospf dead-interval 33

Configure or disable the IP OSPF dead interval.

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 Command (config) Purpose





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

The default is 10 seconds for Ethernet, or 30 seconds for non-broadcast. Example: Set the interval between hello packets to 26 seconds: CASA-CMTS(config-if-gige 0)# ip ospf hello-interval 26

Configure or disable the IP OSPF Hello interval.

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 Command (config) Purpose





CASA CMTS


2 [no] ip ospf message-digest-key <key-id> md5 <key> Where:

<key-id> An identifier in the range from 1 to 255.

<key> 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 message-digest-key 12 md5 1007

Enable or disable the IP OSPF message digest key.

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 Command (config) Purpose





2 [no] ip ospf retransmit-interval <num> Where:

<num> 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 retransmit-interval 10

Enable or disable the IP OSPF retransmit interval.

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 Command (config) Purpose





2 [no] ip ospf transmit-delay <num> Where:

<num> 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 transmit-delay 10

Enable or disable the IP OSPF transmit delay.

Displaying OSPF general information To display general information about Open Shortest Path First (OSPF) routing processes, use the show ip ospf command. Step Command (config) Purpose

1 show ip ospf 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)

Display OSPF general information.

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 Command (config) Purpose

1 show ip ospf border-routers Example: CASA-CMTS(config)# show ip ospf border-routers

Display the OSPF internal routing table entries.

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 Command (config) Purpose

1 show ip ospf database Example: CASA-CMTS(config)# show ip ospf database

Display the OSPF database for a specified router.

Displaying OSPF interface information To display OSPF related interface information, use the show ip ospf interface command.


1 show ip ospf interface Example: CASA-CMTS(config)# show ip ospf interface

Display OSPF interface information.

CASA CMTS


Displaying OSPF neighbor information To display OSPF neighbor information on a per-interface basis, use the show ip ospf neighbor command. Step Command (config) Purpose

1 show ip ospf neighbor [neighbor-id] [detail] Where:

neighbor-id Optional. Neighbor ID in form of A.B.C.D.

detail Optional. Displays all neighbors in detail.

Display OSPF neighbor information.

Displaying the OSPF routing table To display the current state of the routing table, use the show ip route command. Step Command (config) Purpose

1 show ip ospf route Example: CASA-CMTS(config)# show ip ospf route

Display the OSPF routing table.

Displaying IPv4 route information To display IPv4 route information, use the show ip route command. Step Command (config) Purpose

1 show ip route [a.b.c.d | a.b.c.d/m | connected | kernel | ospf | static | bgp | rip | supernets-only ] Where:

a.b.c.d Internet address in standard format.

m IP mask.

bgp Border Gateway Protocol routes.

connected Connected routes.

kernel Kernel routes.

isis IS-IS routes.

ospf OSPF routes.

static Static routes.

Display IPv4 OSPF routing information.

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 Command (config) Purpose

1 show ipv6 route [a.b.c.d | a.b.c.d/m | connected | kernel | isis | ospf | static | rip | bgp | supernets-only ] Where:


m IP mask.




isis IS-IS routes.

ospf OSPF routes.




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

Display IPv6 OSPF routing information.

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

1 CASA-CMTS# config CASA-CMTS(config)#


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


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

Configure OSPF redistribute information.

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


1 CASA-CMTS# config CASA-CMTS(config)#


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


3 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

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:

x default-information

x default-metric

x distance

CASA CMTS


x distribute-list

x list

x neighbor

x network

x offset-list

x passive-interface

x route

x router-map

x timers

x version

x ip rip authentication key-chain

x ip rip authentication string

x ip rip authentication mode

x show ip rip

x show ip rip status

x show ip rip route

Entering RIP configuration mode To enter RIP configuration mode:


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

Enter RIP configuration mode.

Exiting RIP configuration mode To exit RIP configuration mode:


1 end Example : CASA-CMTS(config-router-rip)# end

Exit RIP configuration mode.

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





2 [no] default-information originate Example: Distribute a default route: CASA-CMTS(config-router-rip)#default-information originate

Configure or disable RIP default route.

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 Command (config) Purpose



2 [no] default-metric <metric-value> Where:

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

Configure or cancel default metric values for RIP.

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



2 [no] distance <value> [<ip-address>/<mask_prefix> [name]] 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

Configure RIP administrative distance.

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 Command (config) Purpose



2 [no] distribute-list {<access-list> | prefix <list> {in | out [if-list] } } Where:

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

Configure the RIP filter list.

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.




2 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

Configure the RIP command list.

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 Command (config) Purpose



2 [no] neighbor <ip-address> Where:

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

Configure RIP neighbor router.

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



2 [no] network {<ip-address>/<mask_prefix> | <if-name> }> Where:


IP address directly connected networks, in the form of A.B.C.D/M.

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

Configure or remove RIP routing on an IP network.

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 Command (config) Purpose



2 [no] offset-list <list-name> {in | out} <metric_value> [if-name] Where:

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

Configure the RIP offset list.

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 Command (config) Purpose



2 [no] passive-interface { <if-name> | default } Where:

<if-name> Name of the interface to become passive.

default All interfaces become passive. Example: CASA-CMTS(config-router-rip)# passive interface default

Configure RIP passive interface or enable sending of route updates.

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


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


2 redistribute {ospf | connected | isis | bgp | static} 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] 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.

Redistribute learned routes from other protocols to RIP neighbors.

CASA CMTS


static Redistributes statically-configured routes over RIP.


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.




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 Command (config) Purpose

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


2 [no] route <ip-address>/<mask_prefix> Where:


IP address and mask in the format A.B.C.D/M.

Example: CASA-CMTS(config-router-rip)# route 192.168.2.3/24

Configure or remove RIP static routes.

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 Command (config) Purpose



2 [no] route-map <map-tag> {in | out <if-name> } Where:

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

Configure or delete the RIP static route map.

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 Command (config) Purpose



2 [no] timers basic <update_timer> <timeout_timer> garbage_col_timer> Where:

<update_timer> Rate (in seconds) at which updates are sent. This is the fundamental timing

Configure RIP routing timers.

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

1 [no] version {1 | 2} Where: 1 - Specifies first RIP Version. 2 -Specifies RIP second Version. Example: CASA-CMTS(config-router-rip)# version 2

Configure the RIP version running on the CMTS. 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 Command (config) Purpose


<port> GigE t port number in the range 0 to 11 for C3200/C10200 and 0 to 3 for C2200.


CASA CMTS



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

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

Configure or disable the 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 Command (config) Purpose





2 [no] ip rip authentication string <name> Where:

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

Configure or disable the RIP authentication string.

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 Command (config) Purpose


<port> GigE port number. Valid values are 0 to 11 for C3200/C10200 and 0 to 3 for C2200.



2 [no] ip rip authentication mode { text | md5 [auth-length rfc] } Where:

text Text authentication mode.

md5 MD5 authentication mode. Example: Configure the interface to use MD5 authentication: CASA-CMTS(config-if-gige 0)# ip rip authentication mode md5 auth-length rfc

Configure or disable IP RIP authentication mode.

Displaying RIP routing information To display routing information about RIP routing processes, use the show ip rip command.


1 show ip rip 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 Next Hop Metric From Tag Time C(i) 192.168.3.0/24 0.0.0.0 1 self 0

Display RIP routing information.

CASA CMTS


Displaying RIP status information To display status information about RIP routing processes, use the show ip rip status command.


1 show ip rip status 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)

Display RIP status information.

Displaying IPv4 route information To display IP route information, use the show ip route command.


1 show ip route [a.b.c.d | a.b.c.d/m | connected | kernel | isis | static | rip | bgp| ospf | supernets-only ] Where:


m IP mask.




isis IS-IS routes.

ospf OSPF routes.


Display IP route information.

CASA CMTS




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.


1 show ipv6 route [a.b.c.d | a.b.c.d/m | connected | kernel | isis | rip | static | bgp| ospf | rip | supernets-only ] Where:


m IP mask.




isis IS-IS routes.

ospf OSPF routes.




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

Display IPv6 route information.

CASA CMTS


Configuring the BGP Routing Protocol (Release 5.4 and later) BGP configuration tasks are discussed in the following sections:

x Enable BGP routing

x BGP decision process

x BGP network

x BGP peers

x BGP address family

x Autonomous system

x BGP communities

x Displaying BGP routes

x Capability negotiation

x 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 Command (config) Purpose

1 [no] 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 5 CASA-CMTS(config-router-bgp)#

Enable or disable BGP routing.

CASA CMTS


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


1 router bgp <asn> Where:



Enable BGP routing.

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

Specify the router-ID.

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 Command (config) Purpose




Enable BGP routing.

2 distance bgp <1-255> <1-255> <1-255> Where:

<1-255> Specifies the external distance. <1-255> Specifies the internal distance.

Change the BGP distance value.

CASA CMTS


<1-255> Specifies the local distance. Example: CASA-CMTS(config-router-bgp)# distance bgp <1-255> <1-255> <1-255>

To set a distance value to a specified network:





Enable BGP routing.

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

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

Set a distance value to a specified network.

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


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 Command (config) Purpose




Enable BGP routing.

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

Announce a network to all neighbors. Use the no form of the command to cancel the announcement.

Enabling route aggregation To specify an aggregate address:



<asn> Specifies the autonomous system number (ASN) in the range 1 to 65535.

Enable BGP routing.

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.


2 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 The network number.

A.B.C.D/M The IP prefix and mask length.

as-set Generate AS set path information.

summary-only

Specify an aggregate address but not announce aggregated routes.

Example: CASA-CMTS(config-router-bbp)# aggregate-address 192.168.6.7/24 as-set summary-only

Enable route aggregation.

Configuring BGP route redistribution This command redistributes routes from other routing protocols over BGP.





Enter BGP configuration mode.

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]

Redistribute learned routes from other protocols to BGP neighbors.

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.


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.




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: “can’t find neighbor A.B.C.D” will appear. To configure a BGP peer: Step Command (config) Purpose


<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


Enable BGP routing.

2 [no] neighbor <peer_ip-address> remote-as <asn> Where:

Creates a new neighbor whose remote-AS is ASN. A peer can be an

CASA CMTS


<peer_ip-address> The IP address of the 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(config-router-bgp)# neighbor 10.0.0.1 remote-as 2

IPv4 address or an IPv6 address. To delete the neighbor configuration use the no form.

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 Command (config) Purpose




Enable BGP routing.

2 [no] neighbor <peer_ip-address> password <string> Where:


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

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.

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 Command (config) Purpose




Enable BGP routing.

2 [ no] neighbor <peer_ip-address> shutdown Where:

<peer_ip-address> IP address of the BGP peer. Example: CASA-CMTS(config-router-bgp)# no neighbor 64.10.1.0 shutdown

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

To allow EBGP neighbors thatare not on directly-connected networks:





Enable BGP routing.

2 [no] neighbor <peer_ip-address> ebgp-multihop [max-hop-count]

EBGP neighbors not on directly

CASA CMTS


Where:

<peer_ip-address> IP address of the BGP peer.

<max-hop-count> 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

connected networks

To add a description to a peer (up to 80 lines):





Enable BGP routing.

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

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

To set up the neighbor’s BGP version, use the following.




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

Enable BGP routing.

CASA CMTS


CASA-CMTS(config-router-bgp)#

2 neighbor <peer_ip-address> version <version> Where:


<version> The version can be 4, 4+ or 4-. BGP version 4 is the default value used for BGP peering. BGP version 4+ means that the neighbor supports Multiprotocol Extensions for BGP-4. BGP version 4- is similar but the neighbor uses the old Internet-Draft revision 00’s 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

Set up the neighbor’s BGP version.

When connecting to a BGP peer over an IPv6 link-local address, specify the ifname of the interface used for the connection: Step Command (config) Purpose




Enable BGP routing.

2 [no] neighbor <peer_ip-address> interface <ifname> Where:


<ifname> The interface name specified as a text string.

Example: CASA-CMTS(config-router-bgp)#neighbor 192.168.3.4 interface ifname

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

To specify an announced route’s nexthop as being equivalent to the address of the BGP router:


CASA CMTS





Enable BGP routing.

2 [no] neighbor <peer_ip-address> next-hop-self Where:

<peer_ip-address> The IP address of the BGP peer. Example: CASA-CMTS(config-router-bgp)# neighbor 192.168.3.4 next-hop-self

Specify an announced route’s next hop as being equivalent to the address of the BGP router

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 Command (config) Purpose




Enable BGP routing.

2 [no] neighbor <peer_ip-address> default-originate Where:

<peer_ip-address>

The IP address of the BGP peer.

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

Announce default routes to the peer.

CASA CMTS


To define the source of routing updates:





Enable BGP routing.

2 [no] neighbor <peer_ip-address> update-source <asn> Where:

<peer_ip-address>



Example: CASA-CMTS(config-router-bgp)#[no] neighbor peer update-source 4

Define the source of routing updates

To send community attributes to this neighbor:





Enable BGP routing.

CASA CMTS



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

Send community attributes to this neighbor.

To specify a default value for the neighbor routes:





Enable BGP routing.

2 [no] neighbor <peer_ip-address> weight <value> Where:

<peer_ip-address>


<value> The default weight value for neighbor routes in the range 0 to 65535.

Example: CASA-CMTS(config)# neighbor 192.168.3.4 weight 5

Specify a default value for the neighbor’s routes

To specify the maximum number of prefixes accepted from this peer:

CASA CMTS






Enable BGP routing.

2 [no] neighbor <peer_ip-address> maximum-prefix <number> Where:

<peer_ip-address>


<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

Specify the maximum number of prefixes accepted from this peer.

Peer filtering To specify a distribute-list for the peer (direct is “in” or “out”):

Step Command (config) Purpose 1 router bgp <asn>

Where:


Example:

Enable BGP routing.

CASA CMTS


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

2 neighbor <peer_ip-address> distribute-list {<name> | <number> } {in | out} Where:

<peer_ip-address>


<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

Specify a distribute-list for the peer.

To specify a prefix-list for the BGP peer:





Enable BGP routing.

2 neighbor <peer_ip-address> prefix-list <name> {in | out} Where:

<peer_ip-address>

Specifies the IP address of the BGP peer.

<name> Specifies the name of the prefix list.


out Filters outbound updates.

Example:

Specify a prefix-list for the peer.

CASA CMTS


CASA-CMTS(config-router-bgp)#neighbor peer prefix-list prefixList1 out

To specify a filter-list for the peer:





Enable BGP routing.

2 neighbor <peer_ip-address> filter-list <name> [in | out] Where:

<peer_ip-address>


<name> The filter list name.


out Filters outbound updates. Example: CASA-CMTS(config-router-bgp)#neighbor peer filter-list filterList1 in

Specify a filer-list for the peer:

To apply a route-map to a BGP neighbor:





Enable BGP routing.

CASA CMTS



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

<peer_ip-address>


<name> The name of the route-map.


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

Apply a route map (5.4 only) to a neighbor.

Configuring BGP peer groups To define a new BGP peer group:





Enable BGP routing.

2 neighbor <peer-group_name> Example: CASA-CMTS(config-router-bgp)#neighbor group1

Define a new peer group

To bind a specific peer to a peer group:

CASA CMTS






Enable BGP routing.

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

Bind a specific peer to a named peer group.

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 Command (config) Purpose


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


Enable BGP routing.

2 [no] address-family {ipv4 | ipv6 |} [ unicast] Where:

ipv4 Internet Protocol Version 4; multicast or unicast


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

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 address-family command to remove the IPv6 setting.





Enable BGP routing.

2 [no] address-family ipv6 [unicast] Parameter settings: aggregate-address < X:X::X:X/M > 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}

Configure the BGP IPv6 address-family parameters.

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> | warning-only] 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> [route-map <name> Where:


unicast Optional. Specifies IPv6 unicast address prefixes.

aggregate-address

Specifies the address-family IPv6 prefix in the shortened format x:x::x:x/<mask>. The aggregate

CASA CMTS


address is a public unicast global address that begins with 2xxx (001) .

exit-address-family

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 previously-configured BGP peer group name containing one or more BGP neighbor bindings. Neighbor options: x activate – Enables the address-family for the

this BGP neighbor. x 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.

x allowas-in – Instructs the CMTS to accept inbound route advertisement s containing occurrences of the local CMTS router’s AS number. Up to 10 occurrences may be specified before BGP rejects the inbound route update as a looping condition.

x attribute-unchanged – Propogates BGP next hop attribute as unchanged to the specified neighbor. This parameter is used for multihop BGP peering.

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

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

x 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 distribute-list and the neighbor prefix-list to the same neighbor or peer group at the same time in any direction.

x filter-list – Specifies the IP access-list to apply to either inbound or outbound BGP route

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.

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

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

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

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

x 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 distribute-list and the neighbor prefix-list to the same neighbor or peer group at the same time in any direction.

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

x route-map – Applies the specified route-map to either inbound route updates from the specified BGP neighbor or applies the route-map to outbound route updates to the BGP neighbor.

x send-community – Specifies whether standard or extended community attributes,or both, are sent to this BGP neighbor.

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

x unsuppress-map – Specifies the name of the

CASA CMTS


route-map at the CMTS that releases surpressed routes.

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

redistribute Captures routes from other routing protocols. BGP then advertises these routes to BGP neighbor routers. x connected -- Instructs BGP to advertise

connected routes from a directly-connected subnet or host.

x isis -- Specifies BGP route distribution to IS-IS level-1/level-2 routers.

x static -- Instructs BGP to advertise statically-configured routes. A level option is not required.

route-map <name>

Optional. Instructs BGP to apply a previously-configured 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


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



1 [no] ip as-path access-list <name> [permit | deny] <string> 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

Define a new AS path access list.

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


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.


1 ip community-list <number> {permit | deny} {<community_number> | internet | no-advertise | local-AS | no-export} 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

Define a new standard community list.

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

1 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 route’s 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


! 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 example’s FILTER. ip community-list standard INTERNET deny 1:1 ip community-list standard INTERNET permit internet

Example 5

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 route’s 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


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 example’s 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


Displaying BGP routes To display information about BGP routes, use the following commands. To list all the BGP attribute information: Step Command Purpose

1 show ip bgp attribute-info Example: CASA-CMTS# show ip bdg attribute-info

List all the BGP attribute information.

To display paths suppressed due to dampening: Step Command Purpose

1 show ip bgp dampened-paths Example: CASA-CMTS# show ip bgp dampened-paths

Display paths suppressed due to dampening.

To display detailed information on TCP and BGP neighbor connections: Step Command Purpose

1 show ip bgp neighbors Example: CASA-CMTS# show ip bgp neighbors

Display detailed information on TCP and BGP neighbor connections.

To display path information:


1 show ip bgp paths Example: CASA-CMTS# show ip bgp paths

Display path information.

To Display information about the route server client:


1 show ip bgp rsclient Example: CASA-CMTS# show ip bgp rsclient

Display information about the route server client.

To display the BGP scan status:


1 show ip bgp scan

Display the BGP scan status.

CASA CMTS


Example: CASA-CMTS# show ip bgp scan

To display a summary of BGP neighbor status:


1 show ip bgp summary Example: CASA-CMTS# show ip bgp summary

Display a summary of BGP neighbor status.

To display the BGP attributes: Step Command Purpose

1 show ip bgp attribute-info Example: CASA-CMTS# show ip bgp attribute-info

Display BGP attributes.

To display path suppressed due to dampening:


1 show ip bgp dampened-paths Example: CASA-CMTS# show ip bgp dampened-paths

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


1 clear ip bgp { * | A.B.C.D | X:X::X:X | <1-65535> | external | peer-group } [ in [prefix-filter] | ipv4 {multicast | unicast} {in [prefix-filter] | out | soft [in [prefix-filter] | out]} | out | rsclient | soft [in[prefix-filter] | out] | vpnv4 unicast {in [prefix-filter] | out | soft [in | out]} ] Where:

Clear the specified BGP route (s) to one or more BGP peers.

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


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 peer’s capability to handle other than IPv4 unicast routes. This version of BGP uses a feature called Capability Negotiation to detect the remote peer’s 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 Command (config) Purpose




Enable BGP routing.

2 [no] neighbor <peer_ip-address> dont-capability-negotiate Where:

<peer_ip-address>>


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

Disable sending the capability negotiation OPEN message.

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:





Enable BGP routing.

2 bgp cluster-id <cluster_id> | Where:

<cluster_id> 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 route-reflector cluster identifier.

Configure a BGP neighbor as a route-reflector:




Enable BGP routing.

CASA CMTS



2 [no] neighbor <peer_ip-address> route-reflector-client Where:

<peer_ip-address>>


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

Configure a BGP neighbor as a route-reflector.

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: x Creating and removing ACLs x Entering and exiting ACL editing mode x Adding and removing control rules x Numbering the control rules x Displaying control rules x Applying and removing an ACL on a specified IP interface x Creating and deleting IP access classes x Displaying access class information

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 Command (config) Purpose 1 [no] ip access-list <acl_name> [resequence]

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

Create an access control list.

Entering and exiting ACL editing mode

To enter ACL editing mode:

Step Command (config) Purpose 1 ip access-list <acl_name>

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)

Enter ACL editing mode.

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


To add ACL rules:

Step Command (config) Purpose 1 ip access-list <acl_name>

Where:

<acl_name> Name of ACL. A maximum of 32 ACLs are allowed.

Example: CASA-CMTS(config)# ip access-list telnet_host


Enter ACL editing mode.

2 [sequence-number] permit[6] | deny[6] <protocol_name>|all [sourceIP sourceMask destIP destMask destPort sourcePort] Where:

[sequence-number] 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

Adds the ACL rule.

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.

any A key word maybe used to specify any IP address and corresponding mask of 255.255.255.255. For example, permit tcp any any is equivalent to permit 6 0.0.0.0 255.255.255.255 0.0.0.0 255.255.255.255.

Example: ACL rule to permit telnet access from host 192.168.2.222:

CASA-CMTS(conf-acl telnet_host)# 100 permit telnet 192.168.2.222 CASA-CMTS(conf-acl telnet_host)#

3 no <sequence-number> Where:

<sequence-number> The sequence number of the rule in the 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)#

Removes the specific rule.

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 Command (config) Purpose 1 ip access-list <acl-name>

Where:

<acl-name> Specifies the name of the ACL. Example: CASA-CMTS(config)# ip access-list telnet_host


Create or open the named ACL.

CASA CMTS


2 [sequence-number] remark <string> Example: To add a remark with the sequence number 10: CASA-CMTS(conf-acl telnet_host)#10 remark “This is a remark.”

To remove a remark by sequence number: CASA-CMTS(conf-acl telnet_host)# no 10

Create or remove an ACL remark statement.

Displaying a control rule in an ACL

To display a control rule:

Step Command (config) Purpose 1 show ip access-list <acl-name> [details]

Where:

<acl-name> Name of ACL.

details Shows the match count. Example: Display control rules specified in ACL telnet_host: CASA-CMTS(config)# show ip access-list telnet_host

10 permit telnet 192.168.2.38 255.255.255.255.254 any

20 deny telnet any any

30 deny icmp 192.168.2.19 255.255.255.255 any

Display the control rules.

Displaying ACL names

To display the names of all access lists in the system:


1 show ip access-list Example: CASA-CMTS(config)# show ip access-list ip access-list telnet_host ip access-list ftp_host ip access-list tftp_host

Displays the names of all access lists in the system.

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)# 15 permit telnet 192.168.2.222 CASA-CMTS(conf-acl telnet_host)# show ip access-list telnet_host 10 permit telnet 192.168.2.238 255.255.255.255 any 15 permit telnet 192.168.2.222 255.255.255.255 any 20 deny telnet any 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)# resequence 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 permit telnet 192.168.2.222 255.255.255.255 any 30 deny telnet any 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: x eth0 x gige x loopback

CASA CMTS


x trunk x vlan x 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 Command (config) Purpose 1 interface eth <eth_int>

Where:

<eth_int> Ethernet management interface.

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

Enter interface configuration mode.

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

<acl-name> Name of ACL. Example: Apply ACL telnet_host to Ethernet management interface: CASA-CMTS(config-if-eth 0)# ip access-group telnet_host

Apply the ACL.

To apply an ACL to a specified gigabit Ethernet interface:

Step Command (config) Purpose 1 interface gige <port-id>

Where:

<port-id> GigE port id.


Enter interface configuration mode.

CASA CMTS


2 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 1)# ip access-group telnet_host

Apply the ACL.

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:


1 [no] access-class in <acl_name> Where:

<acl-name> Name of ACL.

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

Create or delete an incoming access class. To delete an incoming access class use the no command. The access list name is optional.

To create an outgoing access class:

Step Command (config) Purpose 1 [no] access-class out <acl_name>

Create or delete an outgoing access class. To delete an

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 Command Purpose 1 show interface <type> <num> acl-count [details]

Where:

<type> Interface (docsis-mac, eth, gige, ip-bundle, loopback, qam, trunk, vlan upstream).

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

Show the ACL counters.

To list all the interfaces that currently have a specific ACL applied :

Step Command Purpose 1 show ip access-list <string> applications

Where:

<string> Access list name.

List all the interfaces that currently have a specific ACL applied.

Note that this command is accessible from diagnostic mode in Rel.5.4 and later releases:

To show the access list with counters:

Step Command Purpose 1 show ip access-list <string> details

Where:

<string> Access list name.

List the access list with counters.

To show the packets dropped by the access list from the deny rules:

CASA CMTS


Step Command Purpose 1 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 route-map 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: x If matched, the route is then redistributed using the newly-modified settings. x If the route-map does not contain at least one match command, then all routes match. x 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.


1 [no] route-map <routemap-name> [ {permit | deny} <sequence-number>] Where:

<routemap-name>

The named route-map up to 128 alphanumeric characters. The name is case-sensitive.

permit If the inbound route meets the match criteria,

Create a named route-map and sequence number. Use the no form of the command to delete the

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.

<sequence-number>

The line number of the named route map in the range 1 to 65535. The CMTS evaluates route maps in sequence from the lowest number to the highest number. The first match takes precedence. If not specified, the default sequence number is 10.

Example: CASA-CMTS(config)# route-map cmtsNet1 permit 100

To remove a named route-map: CASA-CMTS(config)# no route-map cmtsNet1

named route-map.

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: x as-path x community x ip x metric x origin x 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:


1 [no] match as-path <acl-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

Specify the BGP autonomous system path access-list name. Use the no form

CASA CMTS


which a route passes in order to reach a destination. Only one as-path may be specified per route-map.

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 as-path as10

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

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 Command (config) Purpose

1 [no] match community <BGP-communityList-name> [exact-match] Where:

<BGP-communityList -name>

The BGP community list name or number. If inbound BGP route matches the configured community list name or number in the route-map configuration, the route is either permitted or denied for redistribution. Only one community attributes list may be specified per route-map.

exact-match 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)# no match community

Specify the BGP community list name or number. Use the no form of the command to delete the route-map community.

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

1 [no] match {ip | ipv6} {address | next-hop} <acl-name> 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 route-map.

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

Specify the access-list name associated with a destination or next-hop IP address. Use the no form of the command to delete the match ip entry.

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 Command (config) Purpose

1 [no] match metric <metric-number> Where:

<metric-number>

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.

Specify the route metric to match with an inbound route for redistribution. Use the no form

CASA CMTS


Only one metric may be specified per route-map.

Examples: CASA-CMTS(conf-route-map cmtsNet1)# match metric 5 To remove the configured metric entry: CASA-CMTS(conf-route-map cmtsNet1)# no match metric

of the command to delete the metric entry.

Matching route origins A route with a path origin attribute matching the route-map origin setting are either permitted or denied for redistribution. Step Command (config) Purpose

1 [no] match origin {egp | igp | incomplete} 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.

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

Specify the route origin to match with an inbound route for redistribution. Use the no form of the command to delete the origin entry.

CASA CMTS


Matching peer routes Inbound routes from peer routers matching the peer setting are either permitted or denied for redistribution. Step Command (config) Purpose

1 [no] match peer {<ip-address> | local} Where:

<ip-address> Specifies the IP address of peer router from which routes are received at the CMTS. Only one peer may be specified per route-map.

local Specifies the peer router as a local AS router.

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

Specify the peer router to match with an inbound route for redistribution. Use the no form of the command to delete the peer entry.

Matching route tags Inbound routes matching the tag setting are either permitted or denied for redistribution. Step Command (config) Purpose

1 [no] match tag <0-65535> Where:

<0-65535> Specifies the route tag in the number range 0 to 65535.

Examples: CASA-CMTS(conf-route-map cmtsNet1)# match tag 57 To remove the configured tag entry: CASA-CMTS(conf-route-map cmtsNet1)# no match tag 57

Specify the route tag to match with an inbound route for redistribution. Use the no form of the command to delete the tag entry.

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: x as-path x atomic-aggregate x community x ip x local-preference x metric x origin x originator-id x 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:


1 [no] set as-path prepend <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.

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

Prepend the autonomous system path with the new AS number. Use the no form of the command to delete the prepended as-path setting.

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



1 [no] set atomic-aggregate 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

Enables the atomic-aggregate setting. 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 Command (config) Purpose 1 [no] set community <community-number>

Where:

<community-number>

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.

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

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 Command (config) Purpose

1 [no] set ip next-hop <ip-address> [<ip-address> <ip-address>] 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 next-hop 192.168.3.0 To remove the configured ip next-hop entries: CASA-CMTS(conf-route-map cmtsNet1)# no set ip next-hop

Specify the route-map next-hop IP address(es). Up to three IP addresses may be specified. Use the no form of the command to delete the ip next-hop entry.

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



1 [no] set local-preference <localPref-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.

Examples: CASA-CMTS(conf-route-map cmtsNet1# set local-preference 5 To remove the configured local-preference entry: CASA-CMTS(conf-route-map cmtsNet1# no set local-preference

Specify the local preference metric value Use the no form of the command to delete the local-preference entry.

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 Command (config) Purpose

1 [no] set metric <metric-value> 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 To remove the configured metric setting: CASA-CMTS(conf-route-map cmtsNet1)# no set metric

Specify the metric value for routes advertised to external BGP peers. Use the no form of the command to delete the metric setting.

CASA CMTS


Modifying route origins Use the set origin command to modify the path origin attribute, as originally matched by route-map. Step Command (config) Purpose

1 [no] set origin {egp | igp | incomplete} 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.

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

Modify the route origin, as originally matched by the route-map. Use the no form of the command to delete the set origin entry.

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 Command (config) Purpose

1 [no] set originator-id <ip-address> Where:

<ip-address> The IP address of the router where the route update originated.

Examples:

Specify the IP address of the router where the matched route originated. Use the no form of the command

CASA CMTS


CASA-CMTS(conf-route-map cmtsNet1)# set originator-id 192.268.3.4 To remove the configured metric setting: CASA-CMTS(conf-route-map cmtsNet1)# no set originator-id

to delete the originator-id setting.

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 Command (config) Purpose

1 [no] set weight <weight-value> 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 To remove the configured metric setting: CASA-CMTS(conf-route-map cmtsNet1)# no set weight

Specify the IP weight of a matched route when there is more than one route to a destination. Use the no form of the command to delete the weight setting.

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:

x Assigning a Gigabit Ethernet Port to a VLAN

x Removing a Gigabit Ethernet Port from a VLAN

x Assigning a QAM Port to a VLAN

x Removing a QAM Port from a VLAN

x Displaying VLAN configurations

CASA CMTS


Configuring a VLAN To configure a VLAN:


1 [no] interface vlan <number> 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)

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

Configuring a VLAN description To configure a text description of a VLAN interface, execute the description command under the interface vlan configuration context. Step Command (config) Purpose

1 [no] interface vlan <number> 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

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

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


Configuring up to six VLANs concurrently (Release 5.4 and later) Step Command (config) Purpose

1 [no] interface vlan <num> <num> [<num>] [<num>] [<num>] [<num>] 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

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

Configuring VLANs in a range (Release 5.4 and later) Step Command (config) Purpose

1 [no] interface vlan range <snum> <enum> Where:

<snum> Specifies the beginning of the VLAN range.

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

Configure a VLAN range from the first to last ID.

Configuring the MAC address on each VLAN interface Step Command (config) Purpose

1 [no] interface vlan <vlan-id> Where:


Enter a VLAN interface.

CASA CMTS


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

2 mac address xxxx.xxxx.xxxx Where:

xxxx.xxxx.xxxx Specifies the MAC address of the VLAN interface.

Example: CASA-CMTS(conf-if-vlan 2)#mac address xxxx.xxxx.xxxx

Configure the MAC address.

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:


1 interface vlan <vlan-id> Where:


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

Configure the VLAN interface

2 gige <port> Where:

<port> Specifies the GigE interface port number. Example: CASA-CMTS(conf-if-vlan 256)# gige 1

Specify the GigE interface port number.

CASA CMTS


Assigning a 10Gigabit Ethernet port to a VLAN To assign a 10GigE Ethernet port to a VLAN:




Example: CASA-CMTS(config)# interface vlan 10 CASA-CMTS(conf-if-vlan 6/10)#

Configure the VLAN interface.

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

Example: CASA-CMTS(conf-if-vlan 6/10)# xgige 6/0

Specify the 10GigE interface port number.

Removing a Gigabit Ethernet port from a VLAN To remove a gigabit Ethernet port from a VLAN:






2 no gige <port> Where:

<port> Specifies the GigE interface port number. Example: CASA-CMTS(conf-if-vlan 256)# no gige 1

Specify the GigE interface port number.

CASA CMTS


Removing a 10Gigabit Ethernet port from a VLAN To remove a 10GigE Ethernet port from a VLAN:




Example: CASA-CMTS(config)# interface vlan 10 CASA-CMTS(conf-if-vlan 6/10)#


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

Example: CASA-CMTS(conf-if-vlan 6/10)# no xgige 6/0

Specify the 10GigE interface port number for removal.

Assigning an IPv4 address to a VLAN To assign an IP address to a VLAN: Step Command (config) Purpose



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



<ip-address> Text string for standard IP address in the format a.b.c.d.

<subnet-mask> Text string for standard subnet mask in the format p.q.r.s

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

Assign an IP address to a VLAN.

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:




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



<ipv6-address>

Text string for standard IPv6 address in the 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)

Assign an IPv6 address to VLAN.

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 Command (config) Purpose

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


Enter a VLAN interface by specifying the VLAN ID.

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

Example: CASA-CMTS(config)# interface vlan 2 CASA-CMTS(conf-if-vlan 2)# rate-limit multicast 1500

Configure the number of multicast packets per second.

Assign a QAM port to a VLAN To assign a QAM port to a VLAN:


1 interface qam <module>/<port>

Enter QAM interface mode.

CASA CMTS


Where: <module> Module number.

<port> QAM port number. Example: Enter QAM Interface mode for interface on module 0, port 2: CASA-CMTS(config)# interface qam 0/2 CASA-CMTS(conf-if-qam)#

2 [no] vlan <vlan-id> Where:


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

Assign a QAM port a VLAN. Use the no form of the command to un-assign the QAM port.

Assigning an IP access group to a VLAN interface To assign an IP access group to a VLAN:


1 [no] interface vlan <num> 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.


Enter a VLAN interface.

2 [no] ip access-group <string> Where:

<string> Specifies the access group name. Example: CASA-CMTS(conf-if-vlan)# ip access-group my_access_group Remove the assignment:

Assign an IP access group to a VLAN. Use the no form of the command to remove the assignment.

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:


1 [no] interface vlan <vlan_id> Where:



Enter a VLAN interface by specifying the VLAN ID.

2 [no] trunk <number> Where:

<number> The trunk interface number in the range 1 to 12. CASA-CMTS(conf-if-vlan 10)# trunk 24 Remove the assignment: CASA-CMTS(conf-if-vlan)# no trunk 12

Specify the previously -configured trunk number. Use the no form of the command to remove the trunk from the

Example: Create trunk and add interfaces; add trunk to VLAN. CASA-CMTS(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


Displaying all VLAN configurations To display all configured VLANs:


1 show interface vlan 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.

Display all configured VLANs.

Displaying a VLAN interface (Release 5.4) To display a specific VLAN:


1 show interface vlan [<vlan-id>] [ acl-count [details] | brief | service-policy-count [details] ] Where:


acl-count Indicates the packet drop count from ACL deny rules.

brief Display the specified VLAN in abbreviated form.



Example: CASA-CMTS(config)#show interface vlan interface vlan 2 no ip igmp interface vlan 300 gige 0 no ip igmp

Display a specific VLAN.

CASA CMTS


Displaying ARP entries from the current VLAN To display the ARP entries from the current VLAN:




Example: CASA-CMTS(config)# interface vlan 10

CASA-CMTS(conf-if-vlan 6/10)#


2 show arp Example: CASA-CMTS(config)# interface vlan 10

CASA-CMTS(conf-if-vlan 6/10)# show arp Interface Age Hardware Addr State Type IP Address eth 6/0 00:00:01 0017.1001.5cab dynamic ARPA 192.168.8.1 eth 6/0 00:08:40 0022.0c9a.ea41 dynamic ARPA 192.168.8.12 eth 6/0 00:18:01 bc30.5bd8.0f8e dynamic ARPA 192.168.8.90 eth 6/0 00:00:01 b8ac.6f8f.181f dynamic ARPA 192.168.8.92 eth 6/0 00:00:01 0017.1002.cc40 static ARPA 192.168.8.113 eth 7/0 00:08:24 0022.0c9a.ea41 dynamic ARPA 192.168.8.12 eth 7/0 00:00:01 0017.1002.c4c0 static ARPA 192.168.8.114 CATV-MAC 1 00:00:01 0017.1002.cc4d static ARPA fe80::217:10ff:fe02:cc4d CATV-MAC 2 00:00:01 0017.1002.cc4e static ARPA fe80::217:10ff:fe02:cc4e

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:

x Specify Ports/Interfaces on NSI Side of a L2VPN VLAN

x Specify a Gige/Trunk Interface on a L2VPN VLAN

x Display configured L2VPN

x Prevent/Permit Station Movement/Local Forwarding

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


1 show interface vlan [<vlan_id>] 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

Find out information about the VLAN

Specifying ports/interfaces on the NSI side of the L2VPN VLAN To specify ports/interfaces on the NSI side of the L2VPN VLAN:


1 [no] interface vlan <vlan_id>

Find out the information about the VPN on the

CASA CMTS


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.


CMTS.

Specifying GigE/trunk interfaces on the L2VPN VLAN Step Command (config) Purpose

1 [no] interface vlan <vlan_id> Where:

<vlan_id> VLAN ID. Valid values are 256 to 1000. Example: CASA-CMTS(config)# interface vlan 400 CASA-CMTS(conf-if-vlan 400)#

Enter interface mode.

2 [no] gige <port_num> [no] trunk <trunk_num> Where:

<port_num> GigE port number.

<trunk_num> Trunk interface number. Values are 1 to 16. Note: A L2VPN may have more than one gige and trunk interfaces.

Specify GigE or trunk interface on a L2VPN VLAN.

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

1 [no] l2vpn {mac-address-movable | local-traffic-forwarding} Where:

mac-address-movable Specifies a change of locations for MAC addresses attached to a permitted l2vpn.

Preventing/permitting station movement and local forwarding.

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 Command Purpose 1 show l2vpn {mac-address-movable | local-traffic-forwarding}

Where:

mac-address-movable Specifies a change of locations of MAC addresses attached to a permitted l2vpn.

local-traffic-forwarding Traffic destined to local addresses permitted.

Example: CASA-CMTS# show l2vpn local-traffic-forwarding no l2vpn mac-address-movable no l2vpn local-traffic-forwarding

Display the station movement and local forwarding configuration.

Displaying configured L2VPNs To display configured L2VPN VLANs:


1 show l2vpn vlan [<vlan_id>] Where:


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

Display a configured L2VPN VLAN:

CASA CMTS


Displaying L2VPN statistics on QAM modules To display configured L2VPN VLANs:


1 show l2vpn qam [<module_id>] 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():

Display L2VPN statistics over a specified QAM module.

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

x Configuring the TACACS+ host IP address and key

x Enabling and disabling TACACS+ password authentication

x Configuring and displaying the AAA configuration

Configuring the TACACS host IP To configure a host IP:


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

Configure a TACACS server host IP address.

CASA CMTS


Configuring a TACACS key To configure a TACACS key:


1 tacacs-server key <key> Where:

<key> Specifies the case sensitive server access keyword. Example: CASA-CMTS(config) tacacs-server key abcd

Specify the key.

Enabling password authentication at the TACACS+ server To enable password authentication at the TACACS+ server: Step Command (config) Purpose

1 aaa authentication enable default group {radius | tacacsplus} enable Where:

radius Use RADIUS server.

tacacsplus Use TACACS plus server. Example: CASA-CMTS(config)# aaa authentication enable default group radius

Enable “enable” password authentication at TACACS+ server.

Disabling the TACACS+ authentication password To disable the TACACS+ password authentication:


1 no aaa authentication enable Example: CASA-CMTS(config)# no aaa authentication enable

Disable TACACS+ password authentication.

CASA CMTS


Enabling ASCII clear text authentication To enable the TACACS+ ASCII clear text authentication:


1 [no] aaa authentication ascii Example: CASA-CMTS(config)# aaa authentication ascii

Enable TACACS+ ACSCII clear text password authentication.

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


1 aaa authentication login default group {radius | tacacsplus} Where:

radius Use RADIUS server.

tacacsplus Use TACACS plus server. Example: CASA-CMTS(config)# aaa authentication login default group tacacsplus

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

Configuring the AAA authentication login Step Command (config) Purpose

1 aaa authentication login { local | radius | radius-local | tacacsplus | tacacsplus-local ) Where:

default 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

Setup AAA authentication login.

CASA CMTS


Example: CASA-CMTS(config)# aaa authentication login radius

Configuring AAA authorization To configure the authorization shell command:


1 aaa authorization command <num> default {group | if-authenticated | local | none} 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

Configure authorization shell command.

To configure authorization exec shell default server group by tacacs plus server:


1 aaa authorization exec default group tacacsplus {if-authenticated | local | none} Where:

if-authenticated Go ahead if authenticated.

local Use local.

none No authorization Example: CASA-CMTS(config)# aaa authorization exec default group tacacsplus local

Configure authorization exec shell default server group by tacacs plus server.

To configure the authorization exec shell default login:


1 aaa authorization exec default {if-authenticated group | group | local group | none group } tacacsplus

Configure authorization exec shell default login

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:


1 aaa accounting

Enable accounting

Command accounting To perform command accounting:


1 aaa accounting commands <num> default {none | start-stop | stop-only} 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

Command accounting.

Configuring AAA accounting for start-stop events Step Command (config) Purpose

1 aaa accounting exec default start-stop group {radius | Configure AAA

CASA CMTS


tacacsplus} Where:

radius Use radius protocol.

tacacsplus Use tacacs protocol

accounting for start-stop events.

Configuring AAA RADIUS-source loopback interface configuration To configure AAA RADIUS source loopback interface:


1 aaa radius-source loopback <num=0:15> Where:

<num=0:15> The index number in the range 0 to 15. Example: CASA-CMTS(config)# aaa radius-source loopback 4

Setup AAA radius source loopback interface.

Disabling the AAA RADIUS source Step Command (config) Purpose

1 no aaa radius-source

Disable AAA RADIUS source.

Configuring the RADIUS server Step Command (config) Purpose

1 radius-server {host <string> key <string> <number> | key <string> | retry-max <0-5> | timeout <1-60>} 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.

Configure the RADIUS server.

CASA CMTS


Example: CASA-CMTS(config)# radius server host server1 key 123 7

Disabling a specified RADIUS server or RADIUS encryption key Step Command (config) Purpose

1 no radius-server host<string>/key Where:

host Specify a RADIUS server.

<string> IP address in dotted decimal format.

key Set RADIUS encryption key. Example: CASA-CMTS(config)# no radius server host server1/123

Disable a specified RADIUS server or RADIUS encryption key

Displaying the AAA configuration To display AAA configuration:


1 show aaa 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 TRIGGERSTART-STOP : NO COMMAND ACC TRIGGER FOR OTHER LEVEL(S) : EXEC ACC TRIGGER LOGIN-LOGOUT

Display the AAA configuration.

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

RPC mode Similar to manual mode, but mapping configuration is remotely provisioned from SDV (Switched Digital Video) server.

Auto Multiplex mode The Casa CMTS automatically maps the incoming program using the destination IP address and UDP port number embedded in the incoming program.

Group-4-port mode 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.

Group-2-port mode Similar to auto mode, but with a different mapping scheme. The Casa CMTS system translates 8 (4 for 2-chans/port) incoming programs to 8 (4 for 2-chans/port) QAM output channels of 2 ports in a group. The ports in each group key off the IP address of the first QAM port in each group.

Enabling manual operation mode When the Casa CMTS system is in manual mode, the system maps incoming streams to QAM output channels by using values configured in the object stream, which includes the following fields: x source IP address

x destination IP address

CASA CMTS


x source UDP port number

x 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 Command (config) Purpose

1 operation mode manual [module <id>] Where:

<id> QAM module ID. Example: Enable QAM manual operation mode: CASA-CMTS(config)# operation mode manual CASA-CMTS(config)#

Enable manual operation mode.

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 Command (config) Purpose

1 operation mode rpc [module <id>] Where:

<id> QAM module ID.

Enable RPC mode.

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:

x Enabling auto-multiplex operation mode

x Enabling Group-4-Port operation mode

x Enabling Group-2-Port operation mode

x Enabling manual operation mode

x Setting de-jitter interval time

x Entering stream configuration mode

x Ending stream configuration mode.

x Removing a configured stream

x Setting stream source IP address

x Removing a configured stream source IP address

x Setting stream destination IP address

x Removing a configured stream destination IP address

x Setting stream source UDP port

x Removing a configured stream source UDP port

x Setting stream destination UDP port

x Removing a configured stream destination UDP port

x Showing the configured streams

x Binding a stream with a QAM output channel

x Removing the binding between a stream and a QAM output channel

x 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


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: x qqqqqqqq = QAM channel, 0 to 3 (or 0 to 1 for 2-chans/port) x 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 Command (config) Purpose

1 operation mode auto [module <id>] Where:

<id> QAM module ID. Example: Enable QAM auto-multiplex operation mode: CASA-CMTS(config)# operation mode auto CASA-CMTS(config)#

Enable the auto-multiplex operation mode.

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

1 0/0

2 0/1

CASA CMTS


3 0/2

4 0/3

5 1/0

6 1/1

7 1/2

8 1/3

9 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 Command (config) Purpose

1 operation mode group-4-port [module <id>] Where:

<id> QAM module ID. Example: Enable QAM group-4-port operation mode: CASA-CMTS(config)# operation mode group-4-port CASA-CMTS(config)#

Enable the Group-4-port operation mode.

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


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

Output QAM-Chan <port>/<channel> Destination IP =

QAM-port-0 IP

Destination IP =

QAM-port-2 IP

1 0/0 2/0

2 0/1 2/1

3 0/2 2/2

4 0/3 2/3

5 1/0 3/0

6 1/1 3/1

7 1/2 3/2

8 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 Command (config) Purpose

1 operation mode group-2-port [module <id>] Where:

<id> QAM module ID. Example: Enable QAM group-2-port operation mode: CASA-CMTS(config)# operation mode group-2-port CASA-CMTS(config)#

Enable the Group-2-port operation mode.

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


The de-jitter interval is a global setting; it applies to all streams in the system in either auto-multiplex operation mode or manual mode. Step Command (config) Purpose

1 [no] dejitter interval <size> 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)#

Set de-jitter interval or return de-jitter interval to the default value of 400 milliseconds.

Entering stream configuration mode To enter stream configuration mode:


1 [no] stream <stream-id> 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)#

Enter stream configuration mode.

Ending stream configuration mode To end stream configuration mode:


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

End stream configuration mode.

CASA CMTS


Setting the stream source IP address To set stream source IP address:



<stream-id> Stream ID in the range 1 to 9999. Example: Enter stream configuration mode. for stream 123: CASA-CMTS(config)# stream 123

Enter or end stream configuration mode.

2 [no] ip source address <ip-address> Where:

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

Set or remove a stream source IP address.

Setting the stream destination IP address To set stream destination IP address:



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

Enter or end stream configuration mode.

2 [no] ip destination address <ip-address> Where:

Set or remove a stream destination IP address.

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:


1 stream <id> Where:

<id> Stream ID in the range 1 to 9999. Example: CASA-CMTS(config)# stream 123 CASA-CMTS(config-stream 123)#


2 [no] udp source port <source-port> Where:

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

Set or remove stream source UDP port.

CASA CMTS


Setting the stream destination UDP port To set or remove a stream destination UDP port:


1 stream <id> Where:

<id> Stream ID in the range 1 to 9999. Example: CASA-CMTS(config)# stream 123 CASA-CMTS(config-stream 123)#


2 udp destination port <destination-port> Where:

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

Set or remove stream destination UDP port.

Displaying configured streams To show the current stream configurations:


1 show stream config [<stream-id>] 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 -------------------------------------------------

Show the configured streams.

CASA CMTS


ip source address is wildcard ip destination address is wildcard udp source port is wildcard udp destination port is 3014 Dejitter buffer is 400 millisecond Show the configuration of all configured streams: CASA-CMTS(config)# show stream config stream configuration: stream 1 ip source address is wildcard 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 wildcard ip destination address is wildcard udp source port is wildcard udp destination port is 3002 Dejitter buffer is 400 millisecond … stream 14 ip source address is wildcard ip destination address is wildcard udp source port is wildcard udp destination port is 3014 Dejitter buffer is 400 millisecond CASA-CMTS(config)#

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 Command (config) Purpose

1 interface qam <module>/<port> Where:

<module> Module number


CASA CMTS


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

2 [no] channel <ch-id> stream <st-id> program <pr-id> [pass-through] Where:

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

Bind a stream to a QAM output channel or removes the bind.

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 Command (config) Purpose

1 show module <module-id> stream no-mapping Where

<module-id> Stream with no mapping

Show unmapped streams.

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:


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

Enter operation mode.

2 CASA-CMTS(config)# interface gige 3

Select a gigabit Ethernet port that has no IP address (port 3 in this example).

3 CASA-CMTS(config-if-gige 3)# no shutdown Enable the interface.

4 N/A Connect a cable to the gige port and make sure the link is up.

5 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


Configuring downstream QAM ports This sub-section covers commands for the following operations:

x Entering the QAM interface configuration mode

x Ending the QAM interface configuration mode

x Enabling the QAM output ports

x Disabling the QAM output ports

x Enabling QAM output channels

x Disabling QAM output channels

x Setting the QAM port IP address and subnet mask

x Setting QAM port MAC address

x Setting QAM modulation type

x Setting QAM channel annex

x Setting QAM frequency

x Setting QAM output power

x Setting QAM interleave level

x Setting QAM spectral inversion

x Setting QAM channel bandwidth

x Showing QAM interface configurations

x Showing QAM channel utilization rates

Entering QAM interface configuration mode To enter QAM Interface Configuration mode:



<module> Module number.

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


Ending QAM interface configuration mode To end QAM interface mode:




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


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

End QAM interface mode.

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 Command (config) Purpose





2 no shutdown Example: Enable QAM port 0 on module 0: CASA-CMTS(config-if-qam)# no shutdown CASA-CMTS(config-if-qam)#

Enable a QAM port.

CASA CMTS


Disabling QAM output port To disable a QAM port:





Enter QAM interface Mode

2 shutdown Example: Enable QAM port 0 on module 0: CASA-CMTS(config-if-qam)# shutdown

Enable a QAM port.

Enabling QAM output channels To enable QAM output channels:






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


3 no channel <chan-id> shutdown Where:

<chan-id> QAM channel number; valid values are 0

Enable a QAM channel.

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:






2 channel <channel id> shutdown 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)#

Disable a QAM channel.

Setting the QAM port IP address and subnet mask To set the IP address and subnet mask for a QAM port:




<port> QAM port number.


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


<ip-address> Text string for standard IP address, in format a.b.c.d

<subnet-mask> Text string for standard subnet mask, in format p.q.r.s

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

Set or remove the QAM port IP address and subnet mask.

Setting the QAM port MAC address The Casa CMTS allows users to override the built-in manufacturer’s MAC address. To override the default MAC address on a QAM port, follow the command below: Step Command (config) Purpose





2 mac address <mac-address> Where:

<mac-address> MAC address in format xxxx.xxxx.xxxx.

Set or remove the QAM port default MAC address.

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 manufacturer’s 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:






2 modulation <type> Where:

<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

Set the QAM modulation type.

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


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 Command (config) Purpose





2 annex <type> Where:

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

Set the Annex type.

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

Set the Annex A symbol rate.

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 Command (config) Purpose



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

Enter QAM interface mode

2 channel <channel-id> frequency <freq> Note: The center frequencies for the four channels on the same port are correlated. When any one is set, the others

Set the QAM frequency.

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> QAM channel number; valid values are 0 through 3

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




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


2 power <level> Where:

<level> Downstream power output level in one tenth of dBmV. The range is from 450 to 620. The default setting is 510.

Example:

Set the QAM output power.

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:

x 60 dBmV at 1-channel/port

x 56 dBmV at 2-channels/port

x 52 dBmV at 4-channels/port

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




Enter QAM interface mode

CASA CMTS



2 interleave <level> Where:

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

Set the QAM interleave level.

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 Command (config) Purpose





2 [no] spectral inversion on

Example: CASA-CMTS(config-if-qam 0/3)# spectral inversion on Disable QAM spectral inversion:

Setting or disabling QAM spectral inversion.

CASA CMTS


CASA-CMTS(config-if-qam 0/3)# no spectral inversion on

Displaying QAM interface configurations The following show interface commands include:

x Showing the configurations and stream status of a specified QAM port interface.

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


1 show interface qam <module_slot>/<port> [brief] Where:

<module_slot> Module number.


[brief] Optional. Show only the interface configurations.

Example: CASA-CMTS(config) show interface qam 2/1 brief

Show configurations and stream status for the specified QAM port interface.

To show the configurations of a QAM channel and the stream bonded to it:


1 show interface qam <module_slot>/<port> channel <ch-id> stream <number> Where:

<module_slot> Module number.


<ch-id> QAM channel number 0 to 3.

<number> Stream identifier. Example: CASA-CMTS(config) show interface qam 2/1/0

Show the configurations of a QAM channel and the bonded stream.

Displaying QAM channel counters and utilization rates This command is used to display the utilization rates of all downstream channels:

CASA CMTS


To show the utilization rates of all downstream channels: Step Command (config) Purpose

1 show docsis downstream channel {count | utilization} Example: Show the utilization rates of all the downstream channels in the system: 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

Show the utilization rates of all downstream channels.

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

Displays downstream channel set details by MAC ID, channel set number, and channel list.

CASA CMTS


2 4 0/1/11 2 5 0/1/12 2 6 0/1/13 2 7 0/1/14 2 8 0/1/15 2 256 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 A-TDMA 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:

x module slot number – Is the number of the CMTS system slot where the upstream module reside.

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

x 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


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


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:




2 interface upstream <module_slot_num>/<port_num> Where:

<module_slot_num> Specifies the system slot number where the upstream module is installed.

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

Enter upstream port interface configuration mode.

Ending an upstream port interface configuration session To end an upstream port interface configuration session:


1 end Example: Exit upstream interface mode: CASA-CMTS(config-if-ups 2/0)# end CASA-CMTS(config)#

End an upstream port interface configuration session.

CASA CMTS


Enabling upstream ports To enable an upstream port, use the following command:






2 no shutdown Example: Enable upstream port 7 on module 3: CASA-CMTS(config-if-ups 3/7)# no shutdown CASA-CMTS(config-if-ups 3/7)#

Enable an upstream port.

Disabling upstream ports To disable an upstream port:






2 shutdown

Disable an upstream port.

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:


1 interface upstream <module_slot_num>/<port_num>.<physical_channel_num> Where:


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

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

Specify a text description of the upstream port interface.

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:


1 show interface upstream [brief] 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

Show configurations of all upstream port interfaces.

CASA CMTS


To show configurations of all upstream port interfaces in a module:


1 show interface upstream <module_slot_num> Where:

<module_slot_num> Specified the slot number containing the upstream module.

Example: See example below.

Show configurations of all upstream port interfaces in the specified module slot.

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


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


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


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:


1 show interface upstream <module_slot_num>/<port_num>.<physical_channel_num> [brief | current | port | stat] Where:




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

Show the status of an upstream interface with filtering options.

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


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:





CASA CMTS





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

Set the logical-channel channel-frequency.

Setting the upstream logical channel width To set the upstream logical channel width







CASA CMTS



2 channel-width <width_in_hertz> logical-channel <number> channel-width <width_in_hertz> Where:

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


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

Set the logical-channel channel-width.

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 Command (config) Purpose

1 upstream map size <milliseconds> 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

Change the upstream MAP size.

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 power-level. Power-level is an upstream port parameter. To set the upstream input power-level: Step Command (config) Purpose





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

<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

Set the upstream input power level.

Caution: Increases in the upstream port input power-level will lead to an increase in the CM’s 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


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:








2 power-adjustment threshold <level> Where:

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

Adjust the upstream input power threshold

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 Command config) Purpose







2 power-adjustment continue <level> Where:

<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

Adjust the upstream input power level.

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 Command (config Purpose






CASA CMTS



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>

Enables the dynamic MAP advance algorithm that automatically tunes look-ahead time in MAPs based on the current farthest CM on a particular upstream port. This value controls the amount of extra look-ahead time in MAPs to account for inaccuracies of the measurement system and internal software latencies. The max-delay valid range is 200 to 2000 microseconds, with a default of 1000.

static <max-delay>

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

Set the upstream map-advance.

Defaults: Dynamic map-advance with a safety factor of 1000 microseconds and a max-delay of 1800 microseconds.

CASA CMTS


Enabling the upstream logical-channels To enable an upstream logical-channel:







Enter the upstream port interface configuration mode.

2 no logical-channel <number> shutdown Where:

<number>

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

Enables the upstream logical channels.

Disabling the upstream logical-channels To disable an upstream logical-channel:




CASA CMTS






2 logical-channel <number> shutdown Where:

<number>

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

Disable upstream logical channels.

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


To set data-backoff values, use the following command:








2 logical-channel <number> data-backoff {<start_value> <end_value > | automatic} Where:


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

Set upstream channel backoff values.

CASA CMTS


To set data-backoff values to the default values of 0 and 4:








2 logical-channel <number> data-backoff {<start_value> <end_value > | automatic} Where:


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

Set data-backoff values to the default values of 0 and 4.

CASA CMTS


To set ranging-backoff values:








2 logical-channel <number> ranging-backoff <start_value> <end_value> Where:


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

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

Set ranging-backoff values on the specified upstream logical channel.

The upstream interface reconnection time after a power outage is related to the following factors:

x DHCP, ToD, and TFTP servers often operate well below 1 percent load under normal situations, but can jump to 100 percent after an outage.

x Increasing backoff slows upstream interface reconnection and reduces server load.

CASA CMTS


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

x Large backoffs result in increased recovery time after a large scale service outage.

x There is significant variation in cable interface performance (brand to brand) in upstream interface restart time.

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








2 logical-channel <number> ranging-priority <value> Where:


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

Set the ranging hold-off priority value on the specified upstream logical channel.

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:








2 logical-channel <number> minislot <size> Where:


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

Set the upstream channel mini-slot size.

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:








2 [no] logical-channel <number> class-id <identifier> Where:


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

Set the logical channel class identifier.

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







2 logical-channel <number> frame <interval> <codes_per_minislot> <active_codes> Where:


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

Set the upstream channel S-CDMA frame interval.

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:








2 logical-channel <number> profile <profile_id> secondary-profile <string> Where:


<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

Set the upstream channel modulation profile.

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 profile’s 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 secondary-profile 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:


1 interface upstream <module_slot_num>/<port_num>.<physical_channel_num>

Enter upstream port interface configuration

CASA CMTS


Where: <module_slot_num> Specifies the system slot number

where the upstream module is installed.




mode.

2 [no] logical-channel <number> pre-equalization Where:


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 logical-channel 0 pre-equalization CASA-CMTS(config-if-ups 11/0.0)#

Set the upstream channel pre-equalization.

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 specification-defined. The default is 0x0.

CASA CMTS


To set the provisioned attribute mask on an upstream port interface: Step Command (config) Purpose







2 logical-channel <number> prov-attr-mask <value> logical-channel <number> prov-attr-mask [bonding | highavailability | lowlatency] Where:


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

Set the upstream channel provisioned attribute mask.

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:








2 [no] ingress-cancellation <interval> Where:

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

Enable or disable ingress noise cancellation.

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







2 voice-bw-reserve <percentage> [emergency <percentage>] Where:

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

emergency <percentage>

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.

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%

Specify reserve bandwidth percentage for upstream voice calls.

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 admission-control 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 QoS-profiled 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) Purpose







2 qos bw-reserve <percentage>

Specify reserve bandwidth

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.

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

percentage for QoS-profiled traffic.

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: x Plant noise level exceeds SNR threshold defined explicitly in the commands or by default x Percentage of correctable FEC errors of total packets received on the upstream (during

polling period) exceeds the defined or default threshold x 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 Command (config) Purpose

1 interface upstream <module_slot_num>/<port_num>.<physical_channel_num>


CASA CMTS


Where: <module_slot_num> Specifies the system slot number

where the upstream module is installed.




2 spectrum-rule <identifier> Where:

<percentage> Specifies the previously-created spectrum rule by the rule’s 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

Specify the spectrum rule identifier.

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





CASA CMTS




2 [no] rate-limit 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

Enable or disable rate limiting.

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 Command (config) Purpose

1 show docsis upstream channel utilization Example: See the sample session below.

Show the utilization rates of all upstream channels.

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


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 Command (config) Purpose

1 show upstream signal-quality show upstream <module_slot_num>/<port_num>.<physical_channel_num> signal-quality Where:




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#

Show the upstream channel signal quality.

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



1 show upstream burst-noise show upstream <module_slot_num>/<port_num>.<physical_channel_num> burst-noise Where:




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 burst-noise Burst Noise Stats for Channel 11/0.0/0: Burst noise event rate: 0.0 events/second. Percentage of Correctable Burst Events: 0 % Percentage of Uncorrectable Burst Events: 0 % Burst Duration (microseconds) % of Events Max Power (in dB) ----------------------------- ----------- ----------------- 0 to 1 0 0 1 to 3 0 0 3 to 10 0 0 10 to 50 0 0 50 to 500 0 0 500 to 2000 0 0 2000 to 10000 0 0 10000 to 50000 0 0 > 50000 0 0 C3200-232(config-if-ups 11/0.0)#

Show the upstream channel signal quality.

CASA CMTS


Displaying upstream channel sets To display upstream channel sets, use the following commands: Step Command (config) Purpose

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> Specifies the optional output modifier to filter the show upstream command output. The supported modifiers are include, exclude, count-only, count, and begin.

mac-domain <identifier> 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)#

Displays upstream channel set details by MAC ID, channel set number, and channel list.

CASA CMTS


Displaying voice information on upstream interfaces To show the voice information on the upstream interfaces:


1 show cable voice summary 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

Display voice information.

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:

x Creating the IP-bundle interface

x Adding the primary IP interface

x Adding the secondary IP interface

x Removing the secondary IP interface

x Adding the helper-address

x Configuring an IP-bundle sub interface

x Applying IP bundle interfaces to MAC domains

x 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



1 interface ip-bundle <id> 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)#

Create or enter the IP-bundle interface.

Adding the primary IP interface To add the primary IP address to IP-bundle interface:



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

Create or enter the IP-bundle interface

2 ip address <addr> <mask> Where:

<addr> IP address of the primary sub interface in decimal format.

<mask>

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

Add the primary IP interface.

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 Command (config) Purpose

1 interface ip-bundle <id.num> Where:

<id.num> Specifies the IP bundle interface number and sub-interface 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)#

Create or enter the IP-bundle Interface.

2 ip address <addr> <mask> secondary Where:

<addr> IP address of the primary subinterface in decimal format.

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

Add an IP address to an IP bundle sub-interface.

Remove an IP bundle secondary IP address To remove a secondary IP address from an IP bundle interface:




CASA CMTS


<id.num> Specifies the IP bundle interface number and sub-interface 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> IP address of the primary sub interface, in decimal format.

<mask>

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

Remove a secondary IP interface.

Adding primary and secondary IPv6 interfaces To add primary and secondary IP addresss to IP-bundle interface:




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 address <ipv6-address>/<mask_len> [secondary] Where:

<ipv6-address> Text string for standard IPv6 address format: xxxx:xxxx:xxxx:...:xxxx

Assign an IPv6 address to a primary or secondary IP-bundle interface.

CASA CMTS



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.




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:

<ipv6-address>

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.

Assign an IPv6 address to a prim

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.


1 show ipv6 link-local-address Example: CASA-CMTS(config)# interface ip-bundle 1.511 CASA-CMTS(ip-bundle 1.155)# show ipv6 link-local-address 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 . . .

Show all IPv6 local link addresses

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 helper-addresses can be added in each IP-bundle interface. Step Command (config) Purpose


<id> IP bundle interface ID. Valid values are 1 to 16.

Create or enter the IP-bundle interface

CASA CMTS


Example: Create an IP-bundle interface with ID=2: CASA-CMTS(config)# interface ip-bundle 2 CASA-CMTS(ip-bundle 2)#

2 [no] cable helper-address <ip _addr> [cable-modem | host | mta] [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)#

Add a helper-address.

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 modem’s IP address. In the example below:

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

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

x 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


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:


1 [no] interface docsis-mac <domain-id> 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)#

Create new domain interfaces or enter an existing one.

2 ip bundle <id> Where:

<id>

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

Bind IP-bundle interfaces.

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


1 [no] cpe-class <string>

Create a new CPE class, or

CASA CMTS


Where: <string> Specifies the user-defined name of the CPE class

with up to 11 alphanumeric characters. Example: Create a new cpe-class named “computers.” CASA-CMTS(config)# cpe-class computers CASA-CMTS(conf-cpe-class computers)#

open and existing class for editing.

2 dhcp option 60 <string> Where:

<string>

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

Specify the DHCP option 60 string to match.

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 Command (config) Purpose

1 interface ip-bundle <id>

<id> IP bundle interface ID. Valid values are 1 to 16. Example: CASA-CMTS(config)# interface ip-bundle 1 CASA-CMTS(ip-bundle 1)#

Enter ip-bundle interface mode.

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

<name> Name of the authentication key chain. Example: Applies authentication to the autonomous system named school: CASA-CMTS(ip-bundle 1)# # ip rip authentication key-chain school To disable: CASA-CMTS(ip-bundle 1)# no ip rip authentication key-chain

Configure or disable the RIP authentication Key chain.

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 Command (config) Purpose



Enter the ip-bundle interface mode.

2 [no] ip rip authentication string <name> Where:

<name> Authentication string name up to 16 characters. 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

Configure or disable the 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 Command (config) Purpose



Enter the ip-bundle interface mode.

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

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:


1 show interface ip-bundle [<num>] [acl-count [details] | brief | stat | throughput [duration] | service-policy-count [details] ] Where:

<num> The number of the IP bundle interface in the range 1 to 16.


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



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: 1 upstream bytes: 144574 upstream packets: 2118

Display the IP-bundle configuration and statistics.

CASA CMTS


downstream unicast bytes: 96070 downstream multicast bytes: 0 downstream total bytes: 96070 downstream unicast packets: 446 downstream multicast packets: 0 downstream total packets: 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:

x Displaying domain interface configurations

x Creating new domain interfaces

x Entering domain interface configuration mode

x Ending the domain interface configuration session

x Removing domain interfaces

x Binding IP-bundle interfaces

x Binding upstream interfaces

x Binding downstream interfaces

x Binding secondary downstream interfaces

x Deleting upstream interfaces

x Deleting downstream interfaces

x Enabling MAC domain interfaces

x Disabling MAC domain interfaces

x Setting domain interface IP addresses (5.2 only)

x Setting domain interface IPv6 addresses

x Removing domain interface IPv6 addresses

x Setting the helper-address (5.2 only)

CASA CMTS


x Setting IP bundle interfaces

x Setting the domain sync-interval

x Setting the upstream insertion interval

x Setting the MDD interval

x Enabling/disabling the TFTP proxy on MAC domain interfaces

x Configuring multicast on MAC domain interface

x Enabling/disabling DHCP authorization on MAC domain interface

x Configuring channel bonding on MAC domain interfaces

x Configuring IP-provisioning-mode on MAC domain interfaces

x Displaying MAC domain interface configurations and statistics

Displaying domain interface configurations To show a specified domain interface configuration or all configurations:


1 show interface docsis-mac [brief] or show interface docsis-mac <domain-id> [brief] Where:


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

Show a specified domain interface configuration.

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:




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

Create new domain interfaces or enter an existing one. Use the no form to remove a MAC domain interface.

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:






2 ip bundle <id> Where:

<id>

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

Bind IP-bundle interfaces.

Binding upstream interfaces To bind an upstream interface to a MAC domain:






CASA CMTS


2 upstream <chan-id> interface upstream <X/Y.C/Z> Where:

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

Bind upstream interfaces.

Deleting upstream interface bindings To delete a bond upstream interface from a MAC domain:






2 no upstream <chan-id> Where:

<chan-id> User-defined channel identity. Example: Remove bond upstream 5 from domain 2: CASA-CMTS(config-if-mac 2)# no upstream 5

Delete upstream interface bindings.

CASA CMTS


Binding downstream interfaces To bind a downstream interface to a MAC domain interface:






2 downstream <chan-id> interface qam <x/y/z> Where:


<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

Bind downstream interfaces.

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 Command (config) Purpose




CASA CMTS



2 downstream <chan-id> interface qam <x/y/z> [secondary] Where:


<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

Bind secondary downstream interfaces

Deleting downstream interface bindings To delete a bound downstream interface from a MAC domain:






2 no downstream <chan_id> Where:

<chan_id> User-defined channel identity. Example: Remove bound downstream 3 from domain 2: CASA-CMTS(config-if-mac 2)# no downstream 3

Delete downstream interface bindings.

CASA CMTS


Enabling MAC domain interfaces To enable MAC domain interface 2:






2 no shutdown Example: CASA-CMTS(config-if-mac 2)# no shutdown

Enable MAC domain interfaces.

Disabling MAC domain interfaces To disable MAC domain interface 2:






2 shutdown Example: CASA-CMTS(config-if-mac 2)# shutdown

Disable MAC domain interface

CASA CMTS


Setting MAC domain interface IP addresses To set the IP address for a MAC domain interface:







<ip-address> Text string for standard IP address, in format a.b.c.d

<subnet-mask> Text string for standard subnet mask, in format p.q.r.s.

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

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.

Setting MAC domain interface IPv6 addresses (Rel. 5.2 and earlier) To set the IPv6 address for a MAC domain interface:






CASA CMTS


2 ipv6 address <ipv6-address> <subnet-mask> Where:

<ipv6-address>

Text string for standard IPv6 address in format A.B.C.D

<subnet-mask>

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

Set the IPv6 address for a MAC domain interface

Removing MAC domain interface IPv6 addresses (Rel. 5.2 and earlier) Step Command (config) Purpose



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







2 [no] cable helper-address <ip_addr> [cable-modem | host | mta] Where:

<ip_addr> 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)# helper-address 172.23.66.143 host CASA-CMTS(config-if-mac 2)# helper-address 172.23.66.144 cable-modem CASA-CMTS(config-if-mac 2)# helper-address 172.23.66.145 mta CASA-CMTS(config-if-mac 2)# end CASA-CMTS(config)#

Set or disable the helper-address.

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


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 Command (config) Purpose





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: CASA-CMTS(config-if-mac 2)# ip bundle 1

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


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 Command (config) Purpose





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.

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

Set the domain sync-interval. To return the sync message interval, use the no form.

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


Step Command (config) Purpose 1 [no] interface docsis-mac <domain-id>

Where:




2 initial-tech <broadcast-ranging> | <direct> | <period-ranging> | <unicast-ranging> Where:

<broadcast-ranging>

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.

Example: CASA-CMTS(config-if-mac 2)#initial-tech broadcast-ranging

Specify the initial technique for moving cable modems to new upstream channels associated with the CMTS MAC domain interface.

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







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.

Example: Set the minimum insertion interval to 100 ms: CASA-CMTS(config-if-mac 2)# insertion-interval 10

Set the upstream insertion-interval. To disable upstream insertion-interval, use the no form.

Configuring the MDD interval To configure the MDD interval:






2 mdd interval <num> Where:

<num> Interval between two successive MDD messages in milliseconds. The valid range is 0 to 2000, 0 to disable mdd.

Configure the MDD interval.

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:






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. Example: CASA-CMTS(config-if-mac 2)# dhcp-giaddr-primary

Enable a gateway IP address on a domain interface

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 Command (config) Purpose





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 Command (config) Purpose





CASA CMTS


2 [no] tftp-enforce Example: CASA-CMTS(config-if-mac 2)#tftp-enforce

Enable TFTP-enforce to prevent cable modems from registering with the CMTS until the DOCSIS configuration file is downloaded to the modem via TFTP server.

Displaying modem registrations that have bypassed TFTP Th show cable modem tftp-bypass command displays the cable modems that have registered with the CMTS without using TFTP. When the tftp-enforce setting is disabled (by default), cable modems are allowed to register with the CMTS and come online without first downloading their DOCSIS configuration file from a TFTP server. Step Command (config) Purpose

1 show cable modem tftp-bypass 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

Display cable modems that have bypassed TFTP download of the DOCSIS configuration file and have registered with the CMTS.

Enabling/disabling IP policies on a domain interface To enable an IP policy on a domain interface:






CASA CMTS


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






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

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.

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 Command (config) Purpose





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

Enable DHCP authorization on MAC domain to prevent IP address and mac-address 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 Command (config) Purpose





CASA CMTS


2 [no] {upstream | downstream } 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

Enable or disable 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:






2 [no] multicast-dsid-forward Example: CASA-CMTS(config-if-mac 2)# multicast-dsid-forward

Enable or disable forwarding of multicast downstream IDs to cable modem CPE devices. Use the no form of the command to disable DSID forwarding.

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:






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. Example: Enable dual-stack ip-provisioning-mode on docsis-mac domain 2: CASA-CMTS(config-if-mac 2)# ip-provisioning-mode dual-stack

Configure IP-provisioning-mode to select the IP addressing scheme for a MAC domain interface.

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. x enable x cur-hop-limit x life-time

CASA CMTS


x link-mtu x managed-flag x max-advertising-interval x min-advertising-interval x other-config-flag x prefix x reachable-time x retransmit-time

To configure the router-advertisement parameters:



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


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

Configure router-advertisement parameters.

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.

managed-flag

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

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

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

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.

reachable-time

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

retransmit-timer

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


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 Purpose

1 show router-advertisement 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

Display the IPv6 router advertisement table.

Configuring BPI+ on a MAC domain interface To configure KEK and TEK life-time on MAC domain Interfaces.



<domain-id> MAC domain number in the range 1 to 32.



CASA CMTS


2 privacy {kek | tek } life-time <length> Where:

kek 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 life-time 300 CASA-CMTS(config-if-mac 1)#

Configure BPI+ on a MAC domain interface.

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





2 cm trap cm trap interval <seconds> Where :

<seconds> Specifies the time interval in the range 1 to 86400 seconds.

Example: CASA-CMTS(config-if-mac 2)# cm trap CASA-CMTS(config-if-mac 2)# cm trap interval 20000

Enables cable modem trap notification and sets the minimum time interval between CMTS notifications in seconds.

CASA CMTS


Displaying the MAC domain interface configuration To display the MAC domain configuration:


1 show interface docsis-mac [<num>] Example: CASA-CMTS# show interface docsis-mac 8

Display the MAC domain configuration.

To display the MAC domain statistics:


1 show interface docsis-mac stat Example: See example below.

Display the MAC domain Statistics

Displaying MAC domain statistics

To show MAC domain statistics:


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

CASA CMTS


DSD Fail : 0/ups; 0/ds

DCC Request : 0/ups; 1/ds

DCC Response : 2/ups; 0/ds

DCC Acknowledgements : 0/ups; 1/ds

DCC Success : 0/ups; 1/ds

DCC Fail : 0/ups; 0/ds

DCC RSP Depart : 1/ups; 0/ds

DCC RSP Arrive : 1/ups; 0/ds

DBC Request : 0/ups; 0/ds

DBC Response : 0/ups; 0/ds

DBC Acknowledgements : 0/ups; 0/ds

DBC Success : 0/ups; 0/ds

DBC Fail : 0/ups; 0/ds

DBC Partial Service : 0/ups; 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:

x Creating a new service group

x Entering service group configuration mode

x Ending a service group configuration session

x Removing a service group

x Binding upstream interfaces

x Removing upstream interfaces

x Binding downstream interfaces

x Removing downstream interfaces

x Displaying configured service groups

Creating a new service group To create a new service group:


1 [no] service group <string> Where:

<string> Service group name, up to 16 characters. Up to 160 service groups are supported.

Example:

Create or enter a new service group To remove a service group, use the no form of the command.

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:



<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

Create or enter a new service group To remove a service group, use the no form.

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.

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

Bind upstream interfaces. To remove upstream interface binding, use the no form of the command.

CASA CMTS


Binding downstream interfaces To bind a downstream interface to a service group:



<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

Create or enter a new service group To remove a service group, use the no form of the command.

2 [no] qam <X/Y/Z> Where:

<X> Module number.

<Y> Port number.

<Z> Channel number in the range 0 to 3. 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

Bind downstream interfaces. To remove downstream interface bindings, use the no form of the command.

CASA CMTS


Displaying service groups To display the configured service groups:


1 show service group [<string>] 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

Display configured service groups.

CASA CMTS


Displaying MAC domain downstream service groups (Release 5.4) To display the downstream service groups:


1 show md-ds-sg {mac-domain} [service-group] Where:

mac-domain MAC domain number.

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

Display the downstream service groups.

Displaying specific MAC domain downstream service groups To display a specific downstream service group associated with a MAC domain:


1 show md-ds-sg mac <num=1:32> [service-group <string>] Where:

mac:<num=1:16> Specify a MAC domain in the range 1 to 32.

service group <string> To specify which service group. Example: CASA-CMTS#show md-ds-sg mac 1 service-group 1 docsis-mac 1 service-group 1 qam 0/2/0 qam 0/2/1 qam 0/2/2 qam 0/2/3

Display a specific MAC domain downstream service group.

CASA CMTS


Displaying a specific downstream service group To display a named downstream service group:


1 show md-ds-sg service-group <string> 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

Display a specific downstream service group.

Displaying MAC domain upstream service group information To display MAC domain service group information:


1 show md-us-sg [mac <num=1:32>][service-group <string>] Where:

<mac> MAC domain number in the range 1 to 32.

service-group

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

Display MAC domain upstream service group information.

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


This section describes the commands for bonding-group management. It covers the following:

x Creating a new downstream/upstream bonding group

x Entering downstream/upstream bonding-group configuration mode

x Removing a downstream/upstream bonding group

x Binding downstream/upstream interfaces to a bonding group

x Removing downstream/upstream interfaces from a bonding group

x Displaying configured bonding groups

Creating new downstream/upstream bonding groups To create a new downstream bonding group:


1 [no] bonding-group downstream mac-domain <mac_id> group-id <group_id> Where:

<mac_id> MAC domain ID in the range 1 to 32.

<grp_id> Bonding group ID in the range 1-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)# Remove the group: CASA-CMTS(config)# no bonding-group downstream mac-domain 1 group-id 1 CASA-CMTS(bond-ds-mac-1-group-1)#

Create or enter a new downstream bonding group. To remove the bonding group, use the no form of the command.

To create a new upstream bonding group:


1 [no] bonding-group upstream mac-domain <mac_id> group-id <grp_id> Where:


<grp_id> Bonding group ID in the range 1-65535. Example:

Create or enter a new upstream bonding group To remove the bonding group, use the no form of the command.

CASA CMTS


Create a new downstream bonding-group with mac-domain 1 and group ID 1: CASA-CMTS(config)# bonding-group upstream mac-domain 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:


1 [no] bonding-group upstream mac-domain <mac_id> group-id <group_id> Where:

<md_id> MAC domain ID in the range 1 to 32.

<grp_id> Bonding group ID in the range 1 to 65535

Example: Create a new upstream bonding-group with mac-domain 1 and group ID 1: CASA-CMTS(config)# bonding-group upstream mac-domain 1 group-id 1 CASA-CMTS(bond-ds-mac-1-group-1)#

Create or enter a new upstream bonding group.

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.

Example: Bind upstream 1/1.0/0 to bonding-group 1:

Bind upstream interfaces to a bonding group. To remove upstream interface binding from a bonding group, use the no form of the command.

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:


1 [no] bonding-group downstream mac-domain <mac_id> group-id <group_id> Where:

<md_id> MAC domain ID in the range 1 to 32.

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

Create or enter a new downstream bonding group.

2 [no] qam <X/Y/Z> Where:

<X> Module number.

<Y> Port number.

<Z> Channel number in the range 0 to 3. Example: 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

Bind a downstream interface to a bonding group. To remove a bound downstream interface from a bonding group, use the no form.

CASA CMTS


Displaying bonding groups To display bonding groups:


1 show bonding-group [mac-domain <mac-id>] 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

Display a bonding group.

Setting up the receive channel configuration To set up receive channel configuration (RCC) for downstream channel bonding:


1 [no] rcc mac <mac_id> rcp-id <rcp_id> <cfg_id> Where:


<rcp_id> Receive channel profile ID in the format xx:xx:xx:xx:xx

<cfg_id> rcc cfg id in the range 1 to 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)#

Set up the receive channel configuration (RCC) for downstream channel bonding to the CM. To remove a receive channel, use the no form of the command.

CASA CMTS


Assigning a receive module To assign a receive module to receive channel configuration:



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

Set up receive channel configuration (RCC) for downstream channel bonding to the CM.

2 rm <rm_id> frequency <freq> connect <connect_id> Where:

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

Assign a receive module to receive channel configuration.

Assigning a receive channel To assign a receive channel to receive channel configuration:




<rcp_id> Receive channel profile id, in form of

Set up receive channel configuration (RCC) for downstream channel bonding to the CM.

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

2 rc <rc_id> downstream <downstream_id> primary|secondary connect <rm_id> Where:

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

Assign a receive channel to receive channel configuration.

Displaying the receive channel configuration To display the receive channel configuration (RCC):


1 show rcc [mac <mac_id> [rcp-id <rcp_id> <cfg_id>]] Where:


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

Display the receive channel configuration.

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. x Parameters for predefined modulation profile 1 to 5 x Configuring modulation profiles x Configuring TDMA burst types x Configuring ATDMA burst types x Configuring MTDMA burst types x Configuring SCDMA burst types x 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 request initial station short long a-short a-long modulation-type qpsk qpsk qpsk qpsk qpsk - - diff-encoding off off off off off - - preamble-len 64 640 384 84 96 - - fec-tbytes 0 5 5 6 8 - - fec-kbytes 16 34 34 75 220 - - scrambler-seed 338 338 338 338 338 - - max-burst-size 0 0 0 13 0 - - guard-time 16 48 48 8 8 - - code-word-len fixed fixed fixed fixed fixed - - scrambler-mode on on on on on - - interleave-depth - - - - - - - interleave-block - - - - - - - preamble-type - - - - - - -

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 request initial station short long a-short a-long modulation-type qpsk qpsk qpsk 16qam 16qam - - diff-encoding off off off off off - - preamble-len 64 640 384 168 192 - - fec-tbytes 0 5 5 6 8 - - fec-kbytes 16 34 34 75 220 - - scrambler-seed 338 338 338 338 338 - - max-burst-size 0 0 0 7 0 - - guard-time 16 48 48 8 8 - - code-word-len fixed fixed Fixed fixed fixed - - scrambler-mode on on on on on - - interleave-depth - - - - - - - interleave-block - - - - - - - preamble-type - - - - - - -

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 request initial station short long a-short a-long modulation-type qpsk qpsk qpsk - - 64qam 64qam diff-encoding off off off - - off off preamble-len 64 640 384 - - 104 104 fec-tbytes 0 5 5 - - 12 16 fec-kbytes 16 34 34 - - 75 220 scrambler-seed 338 338 338 - - 338 338 max-burst-size 0 0 0 - - 6 0 guard-time 16 48 48 - - 8 8 code-word-len fixed fixed fixed - - shortened shortened scrambler-mode on on on - - on on interleave-depth 1 1 1 - - 1 1 interleave-block 1536 1536 1536 - - 1536 1536 preamble-type qpsk0 qpsk0 qpsk0 - - qpsk1 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


iuc request initial station short long a-short a-long modulation-type

qpsk qpsk qpsk 16qam 16qam 64qam 64qam

diff-encoding off off off off off off off preamble-len 64 640 384 168 192 104 104 fec-tbytes 0 5 5 6 8 12 16 fec-kbytes 16 34 34 75 220 75 220 scrambler-seed 338 338 338 338 338 338 338 max-burst-size 0 0 0 7 0 6 0 guard-time 16 48 48 8 8 8 8 code-word-len fixed fixed fixed fixed shortened shortened shortened scrambler-mode

on on on on on on on

interleave-depth

1 1 1 1 1 1 1

interleave-block

1536 1536 1536 1536 1536 1536 1536

preamble-type 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 request initial station short long a-short a-long modulation-type qpsk qpsk qpsk - - 128qam 128qam diff-encoding off off off - - off off preamble-len 64 640 512 - - 64 64 fec-tbytes 0 5 5 - - 5 10 fec-kbytes 16 34 34 - - 33 156 scrambler-seed 338 338 338 - - 338 338 max-burst-size 1 0 0 - - 12 0 guard-time 0 0 0 - - 0 0 code-word-len fixed fixed fixed - - shortened shortened scrambler-mode on on on - - on on interleave-depth 0 0 0 - - 0 0 interleave-block 0 0 0 - - 0 0 Preamble-type qpsk0 qpsk0 qpsk0 - - qpsk0 qpsk0 Interleave-step 1 1 1 - - 1 1 spreader on off off - - on on subframe-code 2 2 2 - - 128 128 TCM-encode off off off - - on on

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 Command (config) Purpose 1 modulation-profile <profile> tdma [<mod-type>]

Where:

<profile> Profile ID in the range 6 to 64.

<mod-type> Optional. Modulation type is qpsk or 16qam. Example: CASA-CMTS(config)#modulation profile 22 tdma qpsk CASA-CMTS(config-mod-prof)#

Automatically configure the TDMA-type modulation profile.

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 Command (config) Purpose 1 modulation-profile <profile>

Where:

<profile> Profile ID in the range 6 to 64.

Select the profile to configure.

CASA CMTS


Example: CASA-CMTS(config)#modulation-profile 22 CASA-CMTS(config-mod-prof)#

2 <iuc> tdma <mod-type> <diff-encoding> <preamble-len> <fec-t> <fec-k> <scramble-seed> <bust-size> <guard-time> <cw-len> <scramble-mode> Where:

Example: See below.

<iuc> request, initial, station, short, long

<mod-type> qpsk,16qam <diff-encoding> on, off <preamble-len> 1-1024 (bits) <fec-t> 0-16 <fec-k> 0, 16-253 <scrambler-seed> 15-bit seed (0-32767) <max-burst-size> 0-255 (mini-slots) <guard-time> 4-255 (modulation intervals) <code-word-len> fixed, shortened <scrambler-mode> On, off

Specify the profile parameter values.

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> request initial station short long <mod-type> qpsk qpsk qpsk qpsk qpsk <diff-encoding> off off off off off <preamble-len> 64 128 128 72 80 <fec-t> 0 5 5 6 8 <fec-k> 16 34 34 75 220 <scrambler-seed> 338 338 338 338 338 <max-burst-size> 1 0 0 6 0 <guard-time> 8 48 48 8 8 <code-word-len> fixed fixed fixed fixed fixed <scrambler-mode> on on on on on

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 Command (config) Purpose 1 modulation-profile <profile> atdma [<mod-type>]

Where:

Example: CASA-CMTS(config)#modulation profile 22 atdma qpsk

CASA-CMTS(config-mod-prof)#

<profile> Profile ID in the range 6 to 64. <mod-type> Modulation type: qpsk, 16qam, 8qam,

32qam, or 64qam. If omitted, the profile is the same as predefined modulation-profile 3.

Automatically configure the ATDMA-type modulation profile.

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.


1 modulation-profile <profile> Where:

<profile> Profile ID in the range 6 to 64. Example: CASA-CMTS(config)#modulation profile 22 CASA-CMTS(config-mod-prof)#

Select the profile to configure

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


CASA CMTS


Example: See below.

<iuc> request, initial, station, a-short, a-long <mod-type> qpsk,16qam, 8qam, 32qam, 64qam <diff-encoding> on, off <preamble-len> 1-1536 (bits) <fec-t> = T 0-16 <fec-k> = k 0, 16-253 <scrambler-seed> 15-bit seed (0-32767) <max-burst-size> 0-255 (mini-slots) <guard-time> 4-255 (modulation intervals) <code-word-len> fixed, shortened <scrambler-mode> on, off <intlv-depth> 0 to [2048/(k+2T)] <intlv-block> 2*(k+2T) to 2048 <preamble-type> qpsk0, qpsk1

Configure modulation-profile 7 CASA-CMTS# config CASA-CMTS(config)# modulation-profile 7 CASA-CMTS(config-mod-prof)# request atdma qpsk off 64 0 16 338 1 8 fixed on 1 1536 qpsk0 CASA-CMTS(config-mod-prof)# initial atdma qpsk off 128 5 34 338 0 48 fixed on 1 1536 qpsk0 CASA-CMTS(config-mod-prof)# station atdma qpsk off 128 5 34 338 0 48 fixed on 1 1536 qpsk0 CASA-CMTS(config-mod-prof)# a-shot atdma 16qam off 72 6 75 338 6 8 fixed on 1 1536 qpsk0 CASA-CMTS(config-mod-prof)# a-long atdma 16qam off 80 8 220 338 0 8 fixed on 1 1536 qpsk0 CASA-CMTS(config-mod-prof)# end CASA-CMTS(config)#

The modulation-profile 7 uses the following parameter values:

<iuc> Request initial station a-short a-long <mod-type> Qpsk qpsk qpsk 16qam 16qam <diff-encoding> Off off off off off <preamble-len> 64 128 128 72 80 <fec-t> = T 0 5 5 6 8 <fec-k> = k 16 34 34 75 220 <scrambler-seed> 338 338 338 338 338 <max-burst-size> 1 0 0 6 0 <guard-time> 8 48 48 8 8 <code-word-len> Fixed fixed fixed fixed fixed <scrambler-mode> On on on on on <intlv-depth> 1 1 1 1 1 <intlv-block> 1536 1536 1536 1536 1536 <preamble-type> qpsk0 qpsk0 qpsk0 qpsk0 qpsk0

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 Command (config) Purpose 1 modulation-profile <profile> mtdma [<mod-type>]

Where:

Example: CASA-CMTS(config)#modulation-profile 22 mtdma qpsk CASA-CMTS(config-mod-prof)#


32qam, or 64qam. If omitted, the profile is the same as predefined modulation-profile 4.

Automatically configure the MTDMA-type modulation profile.

Note: The specified modulation type applies to the profile in following way:

Specified mod-type

Burst Type short long a-short a-long

qpsk qpsk qpsk qpsk qpsk 8qam 16qam 16qam 8qam 8qam

16qam 16qam 16qam 16qam 16qam 32qam 16qam 16qam 32qam 32qam 64qam 16qam 16qam 64qam 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


Step Command (config) Purpose 1 modulation-profile <profile>

Where:

<profile> Profile ID in the range 6 to 64. Example: CASA-CMTS(config)#modulation-profile 22 CASA-CMTS(config-mod-prof)#

Select the profile to configure.

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

Example: See below.

<iuc> request, initial, station, a-short, a-long <mod-type> qpsk,16qam, 8qam, 32qam, 64qam <diff-encoding> on, off <preamble-len> 1-1536 (bits) <fec-t> = T 0-16 <fec-k> = k 0, 16-253 <scrambler-seed> 15-bit seed <max-burst-size> 0-255 (mini-slots) <guard-time> 4-255 (modulation intervals) <code-word-len> fixed, shortened <scrambler-mode> on, off <intlv-depth> 0 to [2048/(k+2T)] <intlv-block> 2*(k+2T) to 2048 <preamble-type> qpsk0, qpsk1


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


The modulation-profile 8 Example: uses the following parameter values:

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 Command (config) Purpose 1 modulation-profile <profile> scdma [<mod-type>]

Where:

Example: CASA-CMTS(config)#modulation-profile 22 scdma qpsk CASA-CMTS(config-mod-prof)#


32qam, 64qam or 128qam. If omitted, the profile is the same as predefined modulation-profile 5.

Automatically configure the SCDMA-type modulation profile.

Note: The specified modulation type applies only to the burst types a-short and a-long.

<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 0 5 5 6 8 6 8

<fec-k> = k 16 34 34 75 220 75 220

<scrambler-seed> 338 338 338 338 338 338 338

<max-burst-size> 1 0 0 6 0 6 0

<guard-time> 8 48 48 8 8 8 8

<code-word-len> fixed fixed fixed fixed fixed fixed Fixed

<scrambler-mode> on on on on on on On

<intlv-depth> 1 1 1 1 1 1 1

<intlv-block> 1536 1536 1536 1536 1536 1536 1536

<preamble-type> qpsk0 qpsk0 qpsk0 qpsk0 qpsk0 qpsk0 qpsk0

CASA CMTS


Retrieving configured modulation profiles To retrieve the names of configured modulation profiles:

Step Command (config) Purpose 1 show modulation-profile [<profile>]

Where:

Example: See below.

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

Display the names and details of one or all configured modulation profiles.

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 off initial scdma qpsk off 640 5 34 338 0 0 fixed on qpsk0 off 2 1 off station scdma qpsk off 512 5 34 338 0 0 fixed on qpsk0 off 2 1 off a-short scdma 128qam off 64 5 33 338 12 0 shortened on qpsk0 on 128 1 on a-long scdma 128qam off 64 10 156 338 0 0 shortened on qpsk0 on 128 1 on

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 Command (config) Purpose 1 no modulation-profile <profile>

Where:

Example: CASA-CMTS(config)# no modulation-profile 7 CASA-CMTS(config)#

<profile> ID of configured modulation profile in the range 1 to 64.

Remove the specified modulation profile.

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: x Burst noise event rate in events per second. x Percentage of correctable and uncorrectable burst events. x Burst duration in microseconds, percentage of events in the duration, and the maximum

upstream power level. The commands are summarized as follows:

x show upstream burst noise — Displays brief burst noise statistics for all logical channels.

x show upstream [slot/port.channel} burst noise — Displays brief burst noise statistics for both logical channels for the specified physical channel.

CASA CMTS


x show upstream {slot/port.channel/logical-channel} burst noise — Displays brief burst noise statistics for the specified logical channel.

x 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: 143.5 events/second. Percentage of Correctable Burst Events: 98% Percentage of Uncorrectable Burst Events: 2% Burst Duration (microseconds) % of Events Max Power (in dB) ----------------------------- ----------- ----------------- 0 to 1 0 0 1 to 3 65 0 3 to 10 35 0 10 to 50 0 0 50 to 500 0 0 500 to 2000 0 0 2000 to 10000 0 0 10000 to 50000 0 0 > 50000 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:

x Multicast channel utilization

x Multicast session authorization

x Multicast group configuration

CASA CMTS


x Static multicast configuration

x Multicast management for IPTV In each group, the supported multicast commands are: Multicast Session Authorization

x Enabling/disabling multicast session authorization x Configuring multicast session authorization profile x Configuring multicast session rule x Configuring multicast authorization default action x Configuring multicast authorization maximum sessions x Assigning profile to multicast authorization session x Displaying configurations of multicast authorization

Multicast Group Configuration

x Configuring multicast group configuration table x Configuring multicast group encryption x Configuring multicast group QoS x Configuring multicast group PHS x Configuring multicast group service class x Configuring multicast group default service class x Displaying multicast group configurations

Static Multicast Configuration

x Creating static multicast x Removing static multicast x Displaying Static Multicast Configurations

Multicast Management for IPTV

x 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


Step Command Purpose 1 multicast max channel-util <number>

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

Enable multicast authorization globally.

Enabling/disabling multicast session authorization To enable multicast authorization globally, use the following procedure.

Step Command (config) Purpose 1 [no] multicast authorization enable

Example: CASA-CMTS(config)# multicast authorization enable

Enable multicast authorization globally.

To disable multicast authorization, use the following procedure. The default setting for multicast authorization is disabled.

Step Command (config) Purpose 1 no multicast authorization enable

Example: CASA-CMTS(config)# no multicast authorization enable

Disable multicast authorization globally.

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 Command (config) Purpose 1 [no] multicast single-said

Example: CASA-CMTS(config)# multicast single-said

Enable the single SAID.

CASA CMTS


Configuring a multicast session authorization profile To configure an authorization profile:

Step Command (config) Purpose 1 multicast authorization profile <profile_name>

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

Configure a specified authorization 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 Command (config) Purpose 1 multicast authorization profile <profile_name>

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

Configure a specified authorization profile.

2 session-rule <rule-id> <accept|deny> [ipv6] <sourceAddr/mask_len> <groupAddr/mask_len> priority <number> Where:

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

Configure specific session rules.

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)# session-rule 1 accept 192.168.2.1/24 224.0.100.1/24 priority 1

Session matching rule: x If a multicast join request matches this rule, the request is accepted and the session is

established. x If the “accept” is changed to “deny”, then the request would be denied. x If more than one rule matches the join request, the rule with the highest priority is used. x If a mask_len of zero is configured for the source address, then requests with any source

address will match this rule. x 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 Command (config) Purpose 1 multicast authorization default-action <permit | deny>

Where:

<permit | deny> Change default action to permit or deny.

Example: CASA-CMTS(config)# multicast authorization default-action permit

Change the default behavior for a multicast join request.

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 Command (config) Purpose 1 multicast authorization max-session-num <number>

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 max-session-num 5

Restrict the number of join requests that will be accepted from each cable modem.

Assigning a profile to multicast authorization To specify the name of a profile to be used for multicast authorization:

Step Command (config) Purpose 1 multicast authorization match-profile <name>

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.

Example: CASA-CMTS(config)# multicast authorization match-profile my-profile1 CASA-CMTS(config)# multicast authorization match-profile my-profile2

Name the profile to be used for multicast authorization. To use more than one profile, specify more profile names.

Displaying multicast authorization configurations To display the multicast authorization configurations:

Step Command (config) Purpose 1 show running-config | include multicast

Example: CASA-CMTS(config)#show running-config | include multicast !multicast

Display the multicast group configurations.

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 Command (config) Purpose 1 show igmp client

Example: CASA-CMTS(config)#show igmp client Number Module Vlan Multicast Group ------ ------ ---- --------- ----- IPV6 Multicast Groups: Number Module Vlan Multicast Group ------ ------ ---- --------- -----

Display the multicast sessions.

Configuring a multicast group table To configure a multicast group configuration table:

Step Command (config) Purpose 1 multicast group config <id>

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

Select the multicast group configuration object.

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

Configure the table entries.

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


244.0.0.1/32 CASA-CMTS(conf-grp-config 1)# tos-low 0 CASA-CMTS(conf-grp-config 1)# tos-high 0 CASA-CMTS(conf-grp-config 1)# tos-mask 0 CASA-CMTS(conf-grp-config 1)# qos-id 13 CASA-CMTS(conf-grp-config 1)# encryption-id 0 CASA-CMTS(conf-grp-config 1)# phs-id 0 CASA-CMTS(conf-grp-config 1)# priority 1

Configuring multicast group encryption To configure encryption:

Step Command (config) Purpose 1 multicast group encryption <number> algorithm

<cmts|aes128|des40|des56> Where:

<number> Identifier of instances of the encryption in the range 1 to 65535.

<cmts|aes128|des40|des56>

Defines which encryption algorithm will be used for an SA referenced by this object.

Example: CASA-CMTS(config)# multicast group encryption 1 algorithm cmts

Configure multicast group encryption.

Configuring multicast group QoS To configure QoS:

Step Command (config) Purpose 1 multicast group qos <qos_num> <service-class-name>

<single | aggregate> [max-sess <max_sess_num>] app-id <app_id> 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

Configure multicast group QoS.

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 “max-sess” 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 my-srvs-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 Command (config) Purpose 1 cable service class <class_id>

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

Enter the service class

CASA CMTS


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

Configure the table entries.

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) Purpose 1 multicast default grp-service-class <class_name>

Where:

<class_name> Default group service-class name containing up to 15 characters.

Example: CASA-CMTS(config)# multicast default grp-service-class dgsc1

Configure the default service class.

Displaying multicast group configurations To display the multicast group configurations:

Step Command (config) Purpose 1 show running-config | include multicast

Example: CASA-CMTS(config)#show running-config | include multicast !multicast multicast authorization enable multicast authorization match-profile my-profile1

Display the multicast group configuration.

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 Command (config) Purpose 1 cable igmp static-group <group_address>

Where:

<group_address> Specified the IP multicast group address. Example: CASA-CMTS(config)# cable igmp static-group 224.0.100.100

Specify the group address.

To create a static multicast session for source-specific-multicast:

Step Command (config) Purpose 1 cable igmp static-group <group_address> source <ip_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)#

Specify the group and source address.

2 qam <slot/port_number/channel_number>

Specify the QAM ID for

CASA CMTS


Where: <slot/port_number/downstream_channel> Specifies the

downsteam channel using the system slot, port number, and physical downstream channel number.

Example: CASA-CMTS(conf-igmp-static-group 224.0.100.100)# qam 2/0/0

downstream binding.

To create a description of the static multicast session for source-specific-multicast:








2 desc <string> Where:

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

Specify a description

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:








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

Example: CASA-CMTS(conf-igmp-static-group 224.0.100.100)# secondary-source 224.0.100.200

Configure the secondary multicast source IP address.

3 switch multicast-source Example: CASA-CMTS(conf-igmp-static-group 224.0.100.100)# switch multicast-source

Switch over over to the redundant secondary downstream IP source.

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 Command (config) Purpose 1 no cable igmp static-group

Example: CASA-CMTS(config)# no cable igmp static-group

Remove all static sessions.

To remove a specific static session for any-source-multicast:

Step Command (config) Purpose 1 no cable igmp static-group <grpAddr>

Where:

<grpAddr> IP multicast group address. Example: CASA-CMTS(config)# no cable igmp static-group 224.0.100.100

Remove the static session specified.

To remove a specific static session for source-specific-multicast:

Step Command (config) Purpose 1 no cable igmp static-group <grpAddr> source <srcAddr>

Where:

<grpAddr> IP multicast group address. <srcAddr> 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

Remove the static session for a source-specific multi-cast.

Displaying static multicast sessions To display the static multicast session configurations:

Step Command (config) Purpose 1 show running-config | include igmp

Example:

Display the static multicast sessions.

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


1 [no] cable igmp filter <number> <seconds> Where:

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

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

Example: CASA-CMTS(config)# cable igmp filter 10 2

Set the number of IGMP packets to accept within the specified time window. Use the no form of the command to revert to the default settings.

Displaying all filtering settings in the running configuration To display the IGMP filter setting and all filtering settings from the running CMTS configuration: Step Command (config) Purpose

1 show cable filter running-config Example: CASA-C3000(config)#show cable filter running-

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

Display the filter settings from the running configuration.

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


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:

x Multicast Listener Query —The CMTS polling message for multicast groups.

x Multicast Listener Report — The host response to the Multicast Listener Query message, or a multicast join message from the host to the CMTS.

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

x Create the service class

x 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 Command (config) Purpose 1 cable service-class <index>

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

Initiate the service class

2 name <name> Where:

Name the class.

CASA CMTS


<name> The service class name. Example: CASA-CMTS(conf-service-class 1)# name my_class

3 upstream downstream Where:

<direction> Upstream or downstream. Example: CASA-CMTS(conf-service-class 1)# upstream

Define the direction.

Specifying the cable service class parameters Perform the following steps:

Step Command Purpose 1 <param>

Where: The following parameters are supported.

Service class parameters to be applied.

CASA CMTS


Example: CASA-CMTS(conf-service-class 1)#max-traffic-burst 20000000

activity-timeout qos service class activity timeout admission-timeout qos service class admission timeout app-id qos service class application id attr-aggr-rule-mask qos service class attribute aggregation rule

mask ds-resequencing qos service class ds-resequencing dscp-overwrite qos service class dscp overwrite forbidden-attr-mask qos service class forbidden attribute mask grant-interval qos service class grant-interval grant-jitter qos service class grant-jitter grant-size qos service class grant-size grants-per-interval qos service class grants-per-interval max-buff-size maximum buffer size for service-flow

queue,default is 0 max-concat-burst qos service class max-concat-burst max-latency qos service class max-latency max-outstanding-bytes-per-sid-cluster

qos service class max-outstanding-bytes-per-sid-cluster

max-req-per-sid-cluster

qos service class max-req-per-sid-cluster

max-time-in-sid-cluster

qos service class max-time-in-sid-cluster

max-tot-bytes-req-per-sid-cluster

qos service class max-tot-bytes-req-per-sid-cluster

max-traffic-burst qos service class max traffic burst max-traffic-rate qos service class max traffic rate min-packet-size qos service class min-packet-size min-reserved-rate qos service class min reserved rate multiplier-bytes-req qos service class multiplier-bytes-req multiplier-contention-req-window

qos service class multiplier-contention-req-window

name unique name of qos service class to create no no command peak-traffic-rate qos service class peak-traffic-rate poll-interval qos service class poll-interval poll-jitter qos service class poll-jitter priority set multicast group priority req-trans-policy qos service class request policy required-attr-mask qos service class required attribute mask sched-type qos service class schedule type storage-type qos service class non-volatile or permanent

storage tar-buff-size target or desired buffer size for service-flow

queue,default is 0 tos-overwrite qos service class tos mask upstream physical upstream port binding

CASA CMTS


2 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 0 20000000 0

Exits the service class configuration.

Displaying service class parameters To display the service class parameters:


CASA CMTS


1 show cable service-class [<unum=1:255>] [(brief|verbose)] Where:

No option Displays class parameters of all service classes.

[<unum=1:255>] A specific service class.

[(brief|verbose)] Displays a subset or all parameters of the service class(s).

Example: To display the service class parameters of all service classes: CASA-CMTS(config)#show cable service-class Index Name Dir Sched Prio MaxSusRate MaxBurst MinRsvRate 1 PCMM-US US BE 0 0 24480 0 2 PCMM-DS DS BE 0 512000 3044 0 3 DefD3Down US BE 0 0 3044 0 To display the detailed service class parameters of a specific service class: CASA-CMTS(config)#show cable service-class 1 verbose Index: 1 Name: UP_UGS Direction: Upstream/Downstream Traffic Priority: 0 Maximum Sustained Rate: 0 bits/sec Max Burst: 1522 bytes Minimum Reserved Rate: 0 bits/sec Minimum Packet Size 100 bytes Admitted QoS Timeout 200 seconds Active QoS Timeout 30 seconds Scheduling Type: Unsolicited Grant Service Request/Transmission Policy: 0x1FF Unsolicited Grant Size: 100 bytes Nominal Grant Interval: 20000 usecs Tolerated Grant Jitter: 4000 usecs Grants per Interval: 1 IP ToS Overwrite [AND-mask,OR-mask]: 0xE0,0xA0 Max Latency: 0 usecs Parameter Presence Bitfield: {0xE08, 0xBCC000}

Display the service class parameters.

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 “test-ds ”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


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 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 3044 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: x Configuring PacketCable operations x Configuring RADIUS Accounting for RKS Server x Monitoring and maintaining PacketCable Operations

In each group, the supported commands are: x Configuring PacketCable operations x Enabling/disabling PacketCable x Displaying event messages x Configuring event messages x Configuring the IP address x Configuring FTP users x Configuring FTP user passwords x Configuring the T0 timer x Configuring the T1 timer x Configuring maximum normal calls x Configuring maximum emergency calls x Displaying the PacketCable configuration

Configuring RADIUS accounting for the RKS server x Specifying timeouts for RKS servers x Specifying retry counts for RKS servers x Specifying batch file sendmode x Specifying the time interval for sending the event message batch file to the RKS server

CASA CMTS


x Specifying the max size of the event messages batch file x Specifying the max massages in the event message batch file x Specifying the media alive time for the RKS server x Displaying RKS server information

Monitoring and maintaining PacketCable operations x Displaying summary information for alive gates x Displaying upstream information for a specific gate x Displaying downstream information for a specific gate x Displaying total number of gates x Displaying COPS server information

Enabling PacketCable operation To enable or disable PacketCable operation:

Step Command (config) Purpose 1 [no] packetcable

Example: CASA-CMTS(config)# packetcable

Enable or disable PacketCable operation

Displaying event messages To show event messages:

Step Command (config) Purpose 1 show packetcable log

Example: CASA-CMTS(config)# show packetcable log

Display the PacketCable log.

Enabling DSCP checking To enable checking of the Differentiated Services Code Point (DSCP) level of service setting in IP headers:

Step Command (config) Purpose 1 [no] packetcable dscp check

Example: CASA-CMTS(config)# packetcable dscp check

Configure an event message.

CASA CMTS


Configuring event messages To configure event message:

Step Command (config) Purpose 1 [no] packetcable elemid <ele_id>

Where:

[no] Sets event-message ID to default value 9999

<ele_id> Event-message ID. Values are 1 to 9999 with a default 9999.

Example: CASA-CMTS(config)# packetcable elemid 9996

Configure an event message.

Configuring an IP address To configure an IP address for the CASA CMTS:

Step Command (config) Purpose 1 [no] packetcable myaddress <ip_addr>

Where:

[no] Sets IP address to default value 0.0.0.0.

<ip_addr> IP address of CMTS in decimal form. Default is 0.0.0.0.

Example: CASA-CMTS(config)# packetcable myaddress 1.1.1.1

Configure an IP address.

Configuring an FTP user To configure an FTP user name:

Step Command (config) Purpose 1 [no] packetcable ftp newuser <name>

Where:

[no] If the user is not manually configured, the default is casa. The no form of this command sets user name to default.

<name> FTP user name. Example: CASA-CMTS(config)# packetcable ftp newuser abcd

Configure an FTP user name.

CASA CMTS


Configuring FTP user passwords To configure a password for the current FTP user:

Step Command (config) Purpose 1 [no] packetcable ftp user password <pswd>

Where:

[no] Sets user password to default.

<pswd> User password. The default is casa. Example: CASA-CMTS(config)# packetcable ftp user password mypswd

Configure a password for the current FTP user.

Configuring the T0 timer To configure the t0 timer:

Step Command (config) Purpose 1 [no] packetcable t0 <time>

Where:

[no] Sets t0 timer to default.

<time> Time of t0 timer in seconds, values are 1 to 65535. The default is 30.

Example: CASA-CMTS(config)# packetcable t0 15

Configure the T0 timer.

Configuring the T1 timer To configure the t1 timer:

Step Command (config) Purpose 1 [no] packetcable t1 <time>

Where:

[no] Sets t1 timer to default.

<time> Time of t1 timer in seconds; values are 1 to 65535. The default is 200.

Example: CASA-CMTS(config)# packetcable t1 10

Configure the T0 timer.

CASA CMTS


Configuring network layer signaling (NLS) The packetcable nls command sets Network Layer Signaling (NLS) for transporting Control Point Discovery (CPD) messages, setting the Authentication Group Identifier (AGID), and the CMTS loopback interface for NLS traffic.

Step Command (config) Purpose 1 [no] packetcable nls [agid <number> key <string> | cpd |

source-interface loopback <0 to 15>] Where:

agid <number> key <string>

Specifies the authentication group identifier and key TLV to be carried over NLS authentication message exchanges. The AGID and variable key string must be matched for a successful request and reply exchange.

cpd Specifies Control Point Discovery (CPD) messaging. CPD protocol messages are carried by the NLS protocol to media endpoints (MTAs) to gather the IP addresses of end devices.

source-interface loopback

Specifies the CMTS logical interface for NLS traffic in the range 0 to15.

Example: CASA-CMTS(config)# packetcable nls cpd CASA-CMTS(config)# packetcable nls source-interface loopback 10 CASA-CMTS(config)# packetcable nsl agid 124 key alpha

Configure PacketCable Network Layer Signaling.

Configuring maximum normal calls To configure maximum normal calls for the CMTS:

Step Command (config) Purpose 1 [no] packetcable max normal call <num>

Where:

<num> Number of max normal calls in the range 0 to 8000. The default is 0 (disabled).

Example: CASA-CMTS(config)# packetcable max normal call 5

Configure the maximum normal calls. Use the no form of the comman d to cancel the current setting.

CASA CMTS


Configuring maximum emergency calls To configure max emergency calls for the CMTS:

Step Command (config) Purpose 1 [no] packetcable max emerg call <number>

Where:

<number> Maximum number of max emergency calls; values are 0 to 8000. The default is 0 (disabled).

Example: CASA-CMTS(config)# packetcable max emerg call 100

Configure the maximum emergency calls.

Configuring inactive call aging (Rel. 6.1 and later) The packetcable inactive call aging command controls freeing of packet cable gates when service flows become inactive. Previously, PacketCable gates remained active and calls were not being torn down after a call ended, consuming system resources and bandwidth. This command sets the number of hours to pass before tearing down a call, as well as sets an optional minimum voice downstream throughput threshold (in kilobits) to determine if the call session should be torn down. To configure inactive call aging:

Step Command (config) Purpose 1 packetcable inactive call aging <0-24> [minimum traffic <0-

1000>] Where:

<0-24> Specifies the call aging time in hours 0 to 24. The default setting is 2 hours. Enter 0 to disable the inactive call aging setting.

<0-1000> Specifies the minimum downstream throughput in kilobits before determining if a call should be torn down (if the minimum setting is not met). The default setting is 30 kbps.

Example: CASA-CMTS(config)# packetcable inactive call aging 4 minimum traffic 50

Configure the inactive call aging time in hours and the optional minimum downstream throughput in kilobit before determining call teardown.

CASA CMTS


Enabling PacketCable admission control preempt voice priority To enable or disable PacketCable admission-control preempt voice priority:

Step Command (config) Purpose 1 [no] cable admission-control preempt priority-voice

Where:

[no] Disables admission-control preempt voice priority. Example: CASA-CMTS(config)#cable admission-control preempt priority-voice

Enable or disable PacketCable admission control preempt voice priority.

Enabling PacketCable Multimedia (PCMM) The packetcable multimedia command enables PCMM so that the CMTS generates and responds to PCMM Common Open Policy Service (COPS) commands. Once enabled, the CMTS attempts a COPS connection over a TCP connection to a PCMM policy server.

Step Command (config) Purpose 1 [no] packetcable multimedia [T1 <1 to 1000>]

Where:

[no] Disables PacketCable multimedia.

T1 Specifies the optional T1 timer in seconds. This setting configures the amount of time that PCMM will remain in an authorized state.

Example: CASA-CMTS(config)# packetcable multimedia CASA-CMTS(config)# packetcable multimedia t1 100

Enable or disable PacketCable multimedia.

Enabling Packetcable Multimedia version setup To enable or disable Packetcable Multimedia Version setup:

Step Command (config) Purpose 1 [no] pcmm mmversion major <num=1:10> minor <num=0:10>

Where:

[no] Disables PacketCable multimedia.

<num=1:10> Major number from 1 to 10.

<num=0:10> Minor number from 0 to 10.

Enable or disable PacketCable multimedia version setup.

CASA CMTS


Example: casa-CMTS(config)#pcmm mmversion major 1 minor 10 casa-CMTS(config)# casa-CMTS(config)#no pcmm mmversion major 1 minor 10

Displaying Packetcable Multimedia specifications To show the Packetcable Multimedia specifications:

Step Command (config) Purpose 1 show pcmm gateid <0-0xffffffff> [clsfy | spec | traffic]

Where:

<0-0xffffffff> Gate ID ranged from 0 to 0xffffffff.

[clsfy | spec | traffic] Classifier, Specification, or Traffic Specification.

Example: casa-CMTS(config)#show pcmm gateid 1 clsfy spec Cable Modem: 0015.f2fe.8d6a GateID: 0x40002 PCMM gate state: AUTH Direction: upstream Type: multicast PCMM service-flow: 0 PCMM T1 timer: 200s PCMM T2 timer: 0s PCMM T3 timer: 60s PCMM T4 timer: 0s PCMM classify count: 1 PCMM traffic profile type: 1 PCMM traffic profile: Flow Spec PCMM envelope type: 1 PCMM Time Usage Limit: 0s PCMM Time Usage: 0s PCMM Volume Usage Limit: 0 Kbytes PCMM Volume Usage: 0 Kbytes casa-CMTS(config)#show pcmm gateid 5 spec casa-CMTS(config)#show pcmm gateid 1 traffic spec

Display the selected specification.

CASA CMTS


Setting the cable service flow timeout To set the active service flow timeout for PacketCable implementations where a policy server is not used:

Step Command (config) Purpose 1 [no] cable service-flow active-timeout <seconds>

Where:

[no] Resets the service flow to the default.

<seconds> The number of seconds before the service flow times out. Valid values are 0- 200. The default is 0 (no timeout).

Example: CASA-CMTS(config)# cable service-flow active-timeout 100

Sets the active service flow timeout for PacketCable implementations that do not use a policy server:

Assigning dynamic service flows to downstream channels Use the cable dynamic-service-flow command to assign dynamic service flows to bonded downsteam channels (default), to any one of the downstream channels (non-bonding), or to the modem’s primary downstream channel. For example, to assign VoIP traffic to the modem’s primary downstream channel, use the cable dynamic-service-flow primary command.

Step Command (config) Purpose 1 [no] cable dynamic-service-flow {bonding | non-bonding |

primary} Where:

bonding Assigns dynamic service flows to bonded downstream channels. This is the default setting.

non-bonding Assigns dynamic service flows to any one of the downstream channels.

primary Assigns dynamic service flows to the modem’s primary downstream channel.

Example: CASA-CMTS(config)# cable dynamic service-flow primary

Assigns dynamic service flows to modem downstream channels.

CASA CMTS


Displaying the PCMM policy server To show PCMM policy server:

Step Command (config) Purpose 1 show pcmm ps server

Example: casa-CMTS(config)#show pcmm ps server IP Port PSID

Shows the PCMM policy server.

Displaying PCMM multicast To show PCMM multicast gate summary information to include gateID, subscriberID, and sharedResourceID:

Step Command (config) Purpose 1 show pcmm multicast

Example: casa-CMTS(config)#show pcmm multicast GateID SubscriberID Multicast-Session SharedResourceID

Shows PCMM multicast gate summary information.

Displaying the PacketCable configuration To show the PacketCable configuration:

Step Command (config) Purpose 1 show packetcable global

Example: CASA-CMTS(config)# show packetcable global **********PacketCable Global********** PacketCable: enable Element ID: 9999 MyIPaddr: 0.0.0.0 Gate ID Used: 0 Max Gate: 8000 COPS Server Listen Port: 2126 RKS_Receive_Port: 1813 PCMM Listen Port : 3918 PCMM version: 2.0 T0 Timer: 30 T1 Timer: 200 Max Batch File Size: 65535 Batch File Send Mode: UDP Batch File Send Time: 1

Shows the PacketCable configuration.

CASA CMTS


Batch File Ftp User: casa Normal Calls: 0 Emerg Calls: 0 Max Normal Calls: 1000 Max Emerg Calls: 1000 RKS tries: 3 Media Alive: 00:00 inactive call aging: 2 inactive call mini traffic: 30 no cable admission-control preempt priority-voice **************************************

Specifying a timeout for the RKS server Timeout is the time interval that the router waits for the RKS server to reply before retransmitting. To specify or remove the timeout:

Step Command (config) Purpose 1 [no] packetcable rks timeout <time>

Where:

<time> Time interval for router retransmitting to RKS server, values are 1 to 30. The default is 5.

[no] Removes the timeout setting. Example: CASA-CMTS(config)# packetcable rks timeout 9 CASA-CMTS(config)# no packetcable rks timeout

Set or removes the RKS server timeout.

Specifying a retry count for the RKS server The retry count is the number of times that a RADIUS request is re-sent to a RKS server. To specify or remove the retry count:

Step Command (config) Purpose 1 [no] packetcable rks retry <count>

Where:

<count> Retry count, values are 1 to 10. The default is 3.

[no] Removes the retry count. Example: CASA-CMTS(config)# packetcable rks retry 6 CASA-CMTS(config)# no packetcable rks retry

Set or remove the retry count.

CASA CMTS


Specifying batch file send mode A batchfile can be sent to the RKS server by UDP or FTP. To specify or reset send mode:

Step Command (config) Purpose 1 [no] packetcable rks batchfile sendmode <udp | ftp>

Where:

<udp | ftp> Specifies send mode.

[no] Resets the send mode. Example: CASA-CMTS(config)# packetcable rks batchfile sendmode udp Disable: CASA-CMTS(config)# no packetcable rks batchfile sendmode

Sets or resets the send mode.

Specifying the batch file sending time interval To specify a time interval for sending the batchfile to the RKS server:

Step Command (config) Purpose 1 [no] packetcable rks batchfile time <interval>

Where:

<interval> Time interval of sending the batch file to the RKS server in the range 1 to 200 seconds. The default is 200 seconds.

[no] Removes the time interval. Example: CASA-CMTS(config)# packetcable rks batchfile time 120 CASA-CMTS(config)# no packetcable rks batchfile time

Set or remove the batch file send interval.

CASA CMTS


Specifying the maximum size of the event message batch file To specify the maximum size of the batch file sent to the RKS server:

Step Command (config) Purpose 1 [no] packetcable rks batchfile max size <size>

Where:

<size> The max size of batchfile in the range 1024 to 65535. The default is 65535.

[no] Sets max event messages to default. Example: CASA-CMTS(config)# packetcable rks batchfile max size 4096 Disable: CASA-CMTS(config)# no packetcable rks batchfile max size

Specify the maximum size of the batch file.

Specifying the maximum messages in the batch file To specify maximum number of messages in a batch file:

Step Command (config) Purpose 1 [no] packetcable rks batchfile max msg <num>

Where:

<num> The max messages in batchfile, values are 1 to 20. The default is 20.

[no] Sets max event messages to default. Example: CASA-CMTS(config)# packetcable rks batchfile max msg 10 Disable: CASA-CMTS(config)# no packetcable rks batchfile max msg

Specify the maximum number of messages in a batch file.

CASA CMTS


Specifying the RKS server media alive time Media Alive Time is an EM message. To specify the media alive time:

Step Command (config) Purpose 1 [no] packetcable media alive time <time>

Where:

<time> Media alive time in form hh:mm.

[no] Removes the time setting. Example: CASA-CMTS(config)# packetcable media alive time 10:30 CASA-CMTS(config)# no packetcable media alive

Set or reset the media alive time setting.

Specifying the RKS server maximum gates To specify or reset the RKS server maximum gates:

Step Command (config) Purpose 1 [no] packetcable max gate <number>

Where:

<number> Max gate number from 1 to 8000. The default setting is 8000.

[no] Sets maximum gates to the default setting. Example: CASA-CMTS(config)# packetcable max gate 1000 CASA-CMTS(config)# no packetcable max gate

Specify the maximum gates or reset to default.

Displaying RKS server information To show RKS server information:

Step Command (config) Purpose 1 show packetcable rks server

Example: CASA-CMTS(config)# show packetcable rks server

Display RKS server information.

CASA CMTS


Displaying live gate summary information To show a summary of live gates:

Step Command (config) Purpose 1 show packetcable gate

Example: CASA-CMTS(config)# show packetcable gate GateID SubID State U_stream D_stream RKSIP 1 10.237.2.200 committed enable enable 192.168.0.155

Display live gates summary.

Displaying upstream or downstream gate information To show upstream or downstream information for a specific gate:

Step Command (config) Purpose 1 show packetcable gateid <gate_id> [uspec | dspec]

Where:

<gate_id> Gate ID.

[uspec | dspec] Downstream specifications or upstream specifications.

Example: CASA-CMTS(config)# show packetcable gateid 1 uspec

Display the upstream or downstream information.

Displaying the total gate number To show the total number of gates:

Step Command (config) Purpose 1 show packetcable commit gate

Example: CASA-CMTS(config)# show packetcable commit gate

Display the total number of gates.

CASA CMTS


Displaying COPS server information To show COPS server information:

Step Command (config) Purpose 1 show packetcable cms server

Example: CASA-CMTS(config)# show packetcable cms server

Display the COPS server information.

Configuring DSG The CASA CMTS supports the latest DOCSIS Set-Top Gateway (DSG) specification from CableLabs™. DSG offers substantial support for enhanced DOCSIS implementation in the Broadband Cable environment. This section describes the commands of DSG configuration and provides an example at the end of the section. The commands are organized in 7 groups:

x Configuring a DSG tunnel and classifier x Associating a DSG tunnel with a tunnel-group x Configuring a DSG downstream table x Configuring a DSG client list x Configuring DSG vendor parameters x Configuring a DSG channel list x Configuring DSG timers

The following section describes the DSG configuration commands.

Creating a new DSG tunnel To create a new DSG tunnel, delete a tunnel or enter DSG tunnel configuration mode:

Step Command (config) Purpose 1 [no] dsg tunnel <tunnel-id>

Where:

<tunnel-id> DSG tunnel identifier in the range 1 to 4294967295.

[no] Removes the specified tunnel. Example: CASA-CMTS(config)# dsg tunnel 2 CASA-CMTS(conf-dsg-tunnel-2)# end CASA-CMTS(config)#

Create a new DSG tunnel, delete the tunnel, or enter configuration mode for an existing tunnel.

CASA CMTS


To remove the DSG tunnel: CASA-CMTS(config)# no dsg tunnel 2

Creating a DSG tunnel-group To create a new DSG tunnel-group, or to enter an existing group, perform the following. Note that the maximum number of tunnel groups is 32.

Step Command (config) Purpose 1 [no] dsg tunnel-group <tg-id>

Where:

<tg-id> DSG tunnel-group identifier. The valid values are 1 to 429496729.

[no] Removes a tunnel group. Example: CASA-CMTS(config)# no dsg tunnel-group 2

Create a new tunnel group, delete a group, or enter an existing group.

Associating a DSG tunnel with a tunnel-group To include a configured tunnel with a DSG tunnel-group:


Where:

<tunnel-id> DSG tunnel identifier. The valid values are 1 to 4294967295.

[no] Removes the specified tunnel. Example: CASA-CMTS(config)# dsg tunnel-group 2 CASA-CMTS(conf-dsg-tunnel-grp 2)# To remove the DSG tunnel: CASA-CMTS(config)# no dsg tunnel 2

Create a new DSG tunnel, delete the tunnel, or enter configuration mode for an existing tunnel.

CASA CMTS


2 [no] group <grp_id> Where:

<grp-id> Tunnel-group identifier. Valid values are 1 to 4294967295.

[no] Removes the specified tunnel group association.

Example: CASA-CMTS(conf-dsg-tunnel-2)# group 3 Disable: CASA-CMTS(conf-dsg-tunnel-2)# no group 3

Associates the tunnel with a tunnel group.

Displaying DSG tunnel groups To show DSG tunnel-group settings:

Step Command (config) Purpose 1 show dsg tunnel-group <tg-id>

Where:


Example: CASA-CMTS(config)# show dsg tunnel-group 2 channel 1 qam x/y/z rule-priority 20 vendor-param-id 1 ucid-list 1 channel 2 qam x/y/z rule-priority 30 vendor-param-id 500 ucid-list 2

Display DSG tunnel group settings.

Ending a DSG tunnel-group configuration session To end a DSG tunnel-group configuration session:

Step Command (config) Purpose 1 end

Example: CASA-CMTS(conf-dsg-tunnel-grp-2)# end

End a DSG tunnel-group session.

CASA CMTS


Assigning a destination MAC address to a DSG tunnel To set a MAC address to DSG tunnel:

Step Command Purpose 1 [no] dsg tunnel <tunnel-id>

Where:


[no] Removes the specified tunnel Example: CASA-CMTS(config)# dsg tunnel 2 CASA-CMTS(conf-dsg-tunnel-2)# CASA-CMTS(conf-dsg-tunnel-id)# end CASA-CMTS(config)# To disable: CASA-CMTS(config)# no dsg tunnel 2

Create the new DSG tunnel, delete the tunnel, or enter configuration mode for an existing tunnel.

2 dst_addr <mac_addr> Where:

<mac-address>

DSG tunnel destination MAC address in the format xxxx.xxxx.xxxx.

Example: CASA-CMTS(conf-dsg-tunnel-2)# dst-address 1234.2345.3456

Set a destination MAC address to the tunnel.

Assigning a client list to a DSG tunnel To assign a client-list to a DSG tunnel:


Where:


[no] Removes the specified tunnel Example: CASA-CMTS(config)# dsg tunnel 2 CASA-CMTS(conf-dsg-tunnel-2)# CASA-CMTS(conf-dsg-tunnel-id)# end CASA-CMTS(config)#


CASA CMTS


Disable: CASA-CMTS(config)# no dsg tunnel 2

2 client-list <list_id> Where:

<list_id> DSG client list identifier. Valid values are 1 to 4294967295.

[no] Removes the client list from the tunnel. Example: CASA-CMTS(conf-dsg-tunnel-2)# client-list 123 Disable: CASA-CMTS(conf-dsg-tunnel-2)# no client-list 123

Sets the tunnel with a destination MAC address.

Assigning a service-class to a DSG tunnel To assign a service-class to a DSG tunnel:


Where:


[no] Removes the specified tunnel. Example: CASA-CMTS(config)# dsg tunnel 2 CASA-CMTS(conf-dsg-tunnel-2)# CASA-CMTS(conf-dsg-tunnel-id)# end CASA-CMTS(config)# To disable: CASA-CMTS(config)# no dsg tunnel 2


2 [no] service-class <string> Where:

<string> Service-class name. The max number of the string of service-class name is 16.

[no] Removes the client list from the tunnel. Example: CASA-CMTS(conf-dsg-tunnel-2)# service-class private-class Disable: CASA-CMTS(conf-dsg-tunnel-2)# no service-class private-class

Set the service class to the tunnel.

CASA CMTS


Assigning a classifier to a DSG tunnel To assign a classifier to a DSG tunnel:


Where:


[no] Removes the specified tunnel. Example: CASA-CMTS(config)# dsg tunnel 2 CASA-CMTS(conf-dsg-tunnel-2)# CASA-CMTS(conf-dsg-tunnel-id)# end CASA-CMTS(config)# CASA-CMTS(config)# no dsg tunnel 2


2 classifier [no] <classifier_id> <priority> [ipv6] <src_ip_addr> <dst_ip_addr> [indcd [<src_port> <dst_port>]] [secondary-src-ip <sec_ip_addr>] [primary-gige <pri_gige_port> secondary-gige <sec_gige_port>] Where:

<classifier_id> Classifier identifier. Valid values are 1 to 65535.

<priority> Classifier priority. Valid values are 1 to 255.

[ipv6] Set to ipv6 mode

<src_ip_addr> Source IP address with mask prefix in format of x.x.x.x/n.

<dst_ip_addr> Destination IP address in format of x.x.x.x.

indcd Keyword specifies whether or not the classifier is included in the DCD message.

<src_port> Source TCP/UDT port number.

<dst_port> Destination TCP/UDT port number.

secondary-src-ip <sec_ip_addr>

Secondary source IP address.

primary-gige <pri_gige_port

Primary GigE port number; values are 0 to 11.

secondary-gige <sec_gige_port>]

Secondary GigE port number; values are 0 to 11.

Sets a classifier to the tunnel.

CASA CMTS


[no] Remove a classifier from a DSG tunnel. Example: CASA-CMTS(conf-dsg-tunnel-2)# classifier 1 20 192.168.0.1/24 224.0.0.100 indcd 6666 6667 CASA-CMTS(conf-dsg-tunnel-2)# no classifier 1 20 192.168.0.1/24 224.0.0.100 indcd 6666 6667

Displaying the DSG tunnel configuration (Release 5.4) To display DSG tunnel configuration:

Step Command (config) Purpose 1 show dsg tunnel <tunnel-id>

Where:


Example: CASA-CMTS(config)# show dsg tunnel 2 client-list 123 service-class private-class classifier 1 20 192.168.0.1/24 224.0.0.100 indcd

Display the DSG tunnel configuration.

Displaying the cable DSG tunnel configuration (Release 5.4) To display the cable DSG tunnel configuration:

Step Command (config) Purpose 1 show cable dsg tunnel <num=1:4294967295> [(cfrs | clients |

interface | verbose)] Where:

<num=1:4294967295> DSG tunnel identifier.

cfrs DSG classifier.

clients DSG client.

interface Show DSG interface.

verbose Show detailed DSG information. Example: CASA-CMTS# show cable dsg tunnel 1 cfrs cfr cfr cfr destination ip source ip srcPre d_port d_port id state pri address address length start end

Display the cable DSG tunnel configuration.

CASA CMTS


Associating a downstream channel with a DSG tunnel-group To associate a downstream channel and a tunnel-group:

Step Command (config) Purpose 1 [no] dsg tunnel-group <tg-id>

Where:


[no] Removes a tunnel group. Example: CASA-CMTS(config)# no dsg tunnel-group 2

Create a new tunnel group, delete a group, or enter an existing group.

2 channel [no] <ch_id> qam x/y/z rule-priority <level> [vendor-param-id <vnd_id>] [ucid-list <usid_list>] Where:

<ch_id> User defined channel identity ranges from 1 to 4294967295.

<level> Rule priority level ranges from 0 to 255 with 255 the highest priority.

<vnd_id> DSG vendor parameter group identifier. Valid values are 1 to 4294967295.

<ucid_list> List of upstream channel IDs from which the rule applies. Values are 1 to 255.

[no] Removes the association. Example: CASA-CMTS(conf-dsg-tunnel-grp-2)# channel 1 qam x/y/z rule-priority 20 vendor-param-id 1 ucid-list 1 CASA-CMTS(conf-dsg-tunnel-grp-2)# no channel 1

Associate a downstream channel and a tunnel-group. Use the no form of the command to remove the association.

Displaying the downstream DSG configuration (Release 5.4) Step Command (config) Purpose

1 show dsg downstream [<ds_chan>] [dcd/decoded-dcd] Where:

<ds_chan> Downstream channel ID.

dcd Downstream channel descriptor.

decoded-dcd DSG decoded-dcd TLV information. Example:

Display a downstream DSG configuration.

CASA CMTS


CASA-CMTS(config)#show dsg downstream dcd ds dcd dcd num of dcd num of dcd num of i/f state Tx sent change cnt fragment 0/1/0 dis off 0 0 0 0/1/1 dis off 0 0 0 0/1/2 dis off 0 0 0 0/1/3 dis off 0 0 0

Displaying DSG channel and tunnel group information Step Command (config) Purpose

1 show dsg downstream <ds_chan> tunnel [<num=1:4294967295>] Where:

<ds_chan> Downstream channel ID.

<num=1:4294967295> Tunnel ID range from 1 to 4294967295.

Example: CASA-CMTS(config)#show dsg downstream 1 tunnel 1

Display DSG channel and tunnel group information.

Setting a DSG timer to a downstream channel To set a DSG timer:

Step Command (config) Purpose 1 interface qam <x/y>

Where:

x QAM slot number.

y QAM port number. Example: CASA-CMTS(config)# interface qam 0/1

Enter configuration mode for a specific interface.

2 [no] channel <ch_id> dsg timer-id <tmr_id> Where:

<ch_id> Downstream channel ID, 0 to 3.

<tmr_id > DSG timer ID, 1 to 4294967295.

[no] Removes a DSG timer from a downstream channel.

Set the DSG timer.

CASA CMTS


Example: CASA-CMTS(conf-qam 0/1)# channel 0 dsg timer-id 1

Assigning a DSG vendor-parameter ID to a downstream channel To set a DSG vendor-parameter ID:


Where:

x QAM slot number.



2 [no] channel <ch_id> dsg vendor-param-id <vnd_id> Where:


<vnd_id > DSG vendor-param ID, 1 to 4294967295.

Example: CASA-CMTS(conf-qam 0/1)# channel 0 dsg vendor-param-id 2

Set the DSG vendor-parameter ID. Use the no form of the command to remove the assignment.

Assigning a DSG channel-list to a downstream channel To set the DSG channel list:

Step Command Purpose 1 interface qam <x/y>

Where:

x QAM slot number.



2 [no] channel <ch_id> dsg channel-list <list_id> Where:


Set the DSG channel list. Use the no form of the

CASA CMTS


<list_id > DSG channel list ID, 1 to 4294967295 Example: CASA-CMTS(conf-qam 0/1)# channel 0 dsg channel-list 3 To remove the assignment: CASA-CMTS(conf-qam-id)# no channel 0 dsg channel-list 3

command to remove the assignment.

Assigning DSG DCD ENABLE to a downstream channel To set DSG DCD ENABLE:


Where:

x QAM slot number.



2 [no] channel <ch_id> dsg dcd-enable Where:

<ch_id> Downstream channel ID; 0 to 3. Example: CASA-CMTS(conf-qam 0/1)# channel 0 dsg dcd-enable To disable: CASA-CMTS(conf-qam-id)# no channel 0 dsg dcd-enable

Enable or disable DSG DCD ENABLE.

Setting a DSG time interval on a downstream channel To set a DSG time interval:


Where:

x QAM slot number.



CASA CMTS


2 [no] channel <ch_id> dsg interval <ticks> Where:

<ch_id> Downstream channel ID; 0 to 3.

<ticks> DSG time interval in unit of time ticks from 2 to 10.

Example: CASA-CMTS(conf-qam 0/1)# channel 0 dsg interval 5 Remove: CASA-CMTS(conf-qam 0/1)# no channel 0 dsg interval 5

Set a DSG time interval to a downstream channel.

Displaying the DSG downstream-table settings To show a DSG downstream table:

Step Command (config) Purpose 1 show interface qam <x/y>

Where:

x QAM slot number.

y QAM port number. Example: CASA-CMTS(config)#show interface qam 2/0 interface qam 2/0 no spectral inversion on annex B modulation 256qam interleave 128x1 power 510 channel 0 frequency 549000000 channel 0 dsg channel-list 3 channel 0 dsg timer-id 1 channel 0 dsg vendor-param-id 2 channel 0 dsg interval 5 channel 0 dsg dcd-enable no channel 0 shutdown channel 1 frequency 555000000 no channel 1 shutdown channel 2 frequency 561000000 no channel 2 shutdown channel 3 frequency 567000000 no channel 3 shutdown no shutdown!

Display DSG downstream table settings.

CASA CMTS


Configuring a DSG client list To configure a DSG client list:

Step Command (config) Purpose 1 dsg client-list <list_id> client <client_id> id-type (broadcast |

macAddr | caSysId|appId) id-value <value> vendor-param-id <vp_id> [no] dsg client-list <list_id> client <client_id> Where:

<list_id> Client-list ID. Values are 1 to 4294967295.

<client_id> Client ID. Values are 1 to 4294967295.

broadcast Sets the DSG Client type broadcast identifier with the broadcast-id value.

macAddr The DSG Client type MAC address with mac-addr value.

caSysId The DSG Client type CA system ID, with value provided for sys-id.

appId Sets the index to use for DSG Client ID settings, with index identifier value specified with id. <value>

<vp_id> Sets the vendor parameter index for the vendor-specific parameters, and applied to the specified vendor group. The values are 1 to 4294967295.

Example: CASA-CMTS(config)# dsg client-list 1 client 1 id-type broadcast id-value 2048 vendor-param-id 2 CASA-CMTS(config)# no dsg client-list 1 client 1

Configures the DSG client list. Use the no form of the command to remove the client list.

Displaying DSG client lists To display DSG client lists:

Step Command (config) Purpose 1 show dsg client-list <list_id>

Where:

<list_id> Client-list ID. Values are 1 to 4294967295.

Example: CASA-CMTS(config)# show dsg client-list 1

Display the DSG client list.

CASA CMTS


dsg client-list 1 client 1 id-type broadcast id-value 2048 vendor-param-id 2

Configuring DSG vendor parameters To set DSG vendor parameters:

Step Command (config) Purpose 1 [no] dsg vendor-param-id <vp_id> vendor <vnd_id> oui <oui>

value <value> Where:

<vp_id> Sets the vendor parameter index for the vendor-specific parameters, and applied to the specified vendor group. Values are 1 to 4294967295.

<vnd_id> DSG vendor parameters vendor index setting. Values are 1 to 4294967295.

<oui> DSG vendor parameters vendor OUI. Includes the 0803 <oui> tlv in the VSIF.

<value> DSG vendor parameters vendor value. Example: CASA-CMTS(config)# dsg vendor-param-id 1 vendor 1 oui 01:02:03 value abc CASA-CMTS(config)# no dsg vendor-param-id 1 vendor 1

Set the DSG vendor parameters. Use the no form of the command to remove the vendor parameters.

Displaying DSG vendor parameters To show DSG vendor parameters:

Step Command (config) Purpose 1 show dsg vendor-param-id <vp_id>

Where:

<vp_id> Sets the vendor parameter index for the vendor-specific parameters, and applied to the specified vendor group. Values are 1 to 4294967295.

Example: CASA-CMTS(config)# show dsg vendor-param- 1 dsg vendor-param-id 1 vendor 1 oui 01:02:03 value abc

Display the DSG vendor parameters.

CASA CMTS


Configuring a DSG channel list To configure a DSG channel list:

Step Command (config) Purpose 1 [no] dsg channel-list <ch-list> channel <ch-id> frequency <freq>

Where:

<ch-list> A list of DSG channels that could carry DSG tunnels. Values are 1 to 4294967295.

<ch-id> Downstream channel index. Values are 1 to 4294967295.

<freq> Center frequency of the downstream channel in Hz.

Example: CASA-CMTS(config)# dsg channel-list 1 channel 1 frequency 526000000 CASA-CMTS(config)# no dsg channel-list 1 channel 1

Configure a DSG channel list. Use the no form of the command to remove the channel list.

Displaying a DSG channel list To show a DSG channel list:

Step Command (config) Purpose 1 show dsg channel-list <ch-list>

Where:

<ch-list> A list of DSG channels that could carry DSG tunnels. Values are 1 to 4294967295.

Example: CASA-CMTS(config)# show dsg channel-list 1 dsg channel-list 1 channel 1 frequency 526000000

Displays the DSG channel list.

Configuring DSG timers DSG timer entry is linked with the downstream channel and is encoded into the DCD message. To set DSG timers:

Step Command (config) Purpose 1 [no] dsg timer-id <timer_id> t1 <t1> t2 <t2> t3 <t3> t4 <t4>

Where:

<timer_id> Timer identifier. Values are 1 to 4294967295.

Set the DSG timers. Use the no form of the

CASA CMTS


<t1> DSG initialization timeout. Values are 1 to 65535

<t2> DSG operational timeout. Values are 1 to 65535.

<t3> DSG two-way retry timer. Values are 1 to 65535.

<t4> DSG one-way retry timer. Values are 1 to 65535.

Example: CASA-CMTS(config)# dsg timer-id 1 t1 20 t2 30 t3 40 t4 50 CASA-CMTS(config)# no dsg timer-id 1

command to remove the DSG timer.

Displaying DSG timers To display DSG timers:

Step Command (config) Purpose 1 show dsg timer-id <timer_id>

Where:

<timer_id> Timer identifier. Values are 1 to 4294967295.

Example: CASA-CMTS(config)#show dsg timer 1 dsg timer-id 1 t1 20 t2 30 t3 40 t4 50

Show the timer ID configuration.

Configuring DSG unicast To configure DSG unicast:

Step Command (config) Purpose 1 dsg unicast-port <port_id>

Where:

<port_id> Unicast port ID. Values are 1 to 65535.

Example: CASA-CMTS(config)# dsg unicast-port 1

Configure DSG unicast.

CASA CMTS


Displaying DSG statistics To display DSG statistics:

Step Command (config) Purpose 1 show dsg statistics [(dcd | traffic)]

Example: CASA-CMTS(config)# show dsg statistics dcd

Display the DCD or traffic statistics.

Displaying the DSG running configuration To display the current DSG running configuration:

Step Command (config) Purpose 1 show dsg running-config

Example: CASA-CMTS(config)# show dsg running-config dsg tunnel-group 1 channel 2 qam 0/1/0 rule-priority 1 dsg tunnel 1 group 1 dst-address 0010.5e00.1123 classifier 20 20 10.100.1.10/24 224.0.0.4

dsg client-list 1 client 1 id-type broadcast id-value 1 vendor-param-id 1

dsg vendor-param-id 1 vendor 1 oui 00:11:22 value 1 dsg channel-list 1 channel 1 frequency 640000 dsg timer-id 1 t1 1 t2 2 t3 3 t4 4 dsg server-redundancy enable dsg unicast port : 8888

Display the current DSG running configuration.

Using the DSG feature To use the DSG feature, first complete the basic CMTS configuration and then configure the DSG feature. The following procedure outlines the initial configuration steps.

CASA CMTS


The following procedure summarizes the DSG configuration steps.

Step Purpose Command Example:

1 Enable the IGMP client.

CASA-CMTS(config)#igmp client version 3

2 Enable multicast on the GigE interface.

CASA-CMTS(config)#interface gige 0

CASA-CMTS(conf-if-gige0)#ip igmp

3 Enable IGMP query on the MAC domain.

CASA-CMTS(config)#interface docsis-mac 3

CASA-CMTS(conf-if-mac3)# mgmd ipv4 version 3

CASA-CMTS(conf-if-mac3)# no mgmd ipv4 shutdown

4 Configure the default service class for multicast.

CASA-CMTS(config)# multicast default grp-service-class-name xyz

5 Specify the service class to be used.

CASA-CMTS(conf-service-class1)# name <string>

Step Purpose Command

1 Set up the tunnel group. This defines the mapping between a tunnel to downstream channels and DSG rule-related data.

CASA-CMTS(config)# dsg tunnel-group <grp-id>

CASA-CMTS(conf-dsg-tunnel-grp1)# dsg channel <chan id> qam <x/y/z> rule-priority <pri> [vendor-param-id <vpid>] [ucid-list <string>]

Example: dsg tunnel-group 1

channel 1 qam 0/0/0 rule-priority 20




2 Define the DSG tunnel ID.

CASA-CMTS(config)# dsg tunnel <id>

3 Define the tunnel destination MAC address.

CASA-CMTS(conf-dsg-tunnel 1)# dst-address xxxx.xxxx.xxxxx

4 Define the service class, if any.

CASA-CMTS(conf-dsg-tunnel 1)# service-class <name>

CASA CMTS


Verify DSG DCD message and DSG data forwarding To verify the DSG DCD message and DSG data forwarding, use the following show commands. To show the counters of the DCD messages and DSG data packets sent through each downstream interface: CASA-CMTS# show dsg statistics [dcd | traffic]

5 Define the client list for DCD messages.

CASA-CMTS(conf-dsg-tunnel 1)# client-list <cls id>

6 Define the classifier.

CASA-CMTS(conf-dsg-tunnel 1)# classifier <cls id> <priority> <src ipv4 addr>/<prefixlen> <group addr> [indcd .] dsg tunnel 1

group 1

client-list 1

dst-address 1111.2222.3333

classifier 1 10 192.168.3.6/32 239.1.1.8 indcd

classifier 2 11 0.0.0.0/0 239.100.1.9

indcd

7 Configure the DCD parameters.

The following examples illustrate how to configure the DCD parameters: dsg client-list 1 client 1 id-type macAddr id-value xxxx.xxxx.xxxx vendor-param-id 1 dsg client-list 2 client 2 id-type broadcast id-value 2048 vendor-param-id 1.

CASA-CMTS(config)# dsg vendor-param-id 1 vendor 1 oui 1:1:0 value cj_vid

CASA-CMTS(config)# dsg channel-list 1 channel 1 frequency 567000000 dsg channel-list 1 channel 2 frequency 573000000 dsg channel-list 1 channel 3 frequency 579000000

CASA-CMTS(config)# dsg timer-id 1 t1 20 t2 30 t3 40 t4 50

8 Configure the DSD message configuration and enable it on a QAM interface.

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

CASA-CMTS(conf-if-qam 0/0)# channel 0 dsg channel-list 1

CASA-CMTS(conf-if-qam 0/0)# channel 0 dsg timer-id 1

CASA-CMTS(conf-if-qam 0/0)# channel 0 dsg vendor-param-id 1

CASA-CMTS(conf-if-qam 0/0)# channel 0 dsg interval 5

CASA-CMTS(conf-if-qam 0/0)# channel 0 dsg dcd-enable

CASA CMTS


To show multicast replication in general (DSG replication will be shown as well, if configured): CASA-CMTS# show multicast replication

Configuring DOCSIS BPI/BPI+ Baseline Privacy Interface (BPI) is defined as a set of extended services within the DOCSIS MAC sub-layer. BPI gives subscribers data privacy across the RF network, encrypting traffic flows between the CMTS and CM. This section covers commands for the following operations: x Configuring shared-secret MIC x Adding a privacy certificate x Displaying the privacy certificate x Setting the privacy hotlist x Configuring the encryption algorithm x Managing the revocation certificate x Choosing the Revocation Certificate management method x Setting the CRL method refresh interval x Setting the CRL method URL address x Setting the OCPS client URL address x Setting the OCSP client signature x Displaying the Revocation Certificate method configuration x Displaying the CRL configuration x Displaying the OCSP configuration x Configuring the Source Address Verification rule x Enabling SAV authorization x Displaying the SAV configuration x Enabling the TFTP proxy x Configuring the TFTP proxy x Displaying TFTP proxy status x Configuring the EAE exclusion list x Adding CMs to the EAE exclusion list x Displaying the EAE exclusion List x Displaying BPI information

Configuring shared secrets to protect the modem configuration file Because DOCSIS configuration files from an authorized TFTP server provide critical quality of service (QoS) definitions and other data for cable modems, security measures must be applied to protect the configuration file from unauthorized intercept, theft, substitution, and potential modification.

The DOCSIS specification supports the shared-secret and shared-secondary secret passwords to protect modem configuration files from possible tampering. Once configured, these passwords calculate the CMTS Message Integrity Check (MIC) field that is attached to all DOCSIS configuration files.

CASA CMTS


The shared-secondary-secret provides a second password should a cable modem fail to authenticate with the primary shared-secret. With the secondary secret configured, the cable modem must authenticate using either the primary or secondary password in order for the modem to register and come online. Using a secondary secret allows CMTS operators to frequently revise the primary password without interrupting a currently active and online cable modem with a primary password update.

The CMTS supports a maximum of 198 shared secrets (primary, secondary, and primary/secondary extended), including those shared secrets defined under the interface docsis-mac configuration.

To configure a primary shared-secret:

Step Command (config) Purpose 1 shared-secret {0 | 7} <mic_string> [extend]

Where:

0 Specifies that an unencrypted message (clear text) will follow.

7 Specifies that an encrypted message will follow.

<mic_string> MIC string used to encrypt and decrypt the configuration file. String length is 1 to 32.

extend Sets share-secret MIC for the extend TLVs received from Reg-Req message.

Example: To set the shared-secret for non-encrypted messages or encrypted messages: CASA-CMTS(config)# shared-secret 0 DOCSIS To set share-secret MIC globally: CASA-CMTS(config)# shared-secret DOCSIS To set share-secret MIC for the extend TLVs received from Reg-Req message: CASA-CMTS(config)# shared-secret DOCSIS extend To unset shared-secret MIC: CASA-CMTS(config)# no shared-secret CASA-CMTS(config)# no shared-secret extend

Configure a shared-secret password.

2 show running-config | i secret Example: CASA-CMTS(config)# show running-config | i secret shared-secret 7 d6ab86abb7242b65

Display the configured shared secret.

CASA CMTS


To configure up to two shared-secondary secrets:

Step Command (config) Purpose 1 shared-secondary -secret {1|2} {0|7} <mic_string> [extend]

Where:

{1|2} Specifies the index number of the secondary shared-secret, either 1 or 2. If two secondary secrets are configured, the index determines which secondary secret password is checked first.

0 Specifies that an unencrypted message (clear text) will follow.

7 Specifies that an encrypted message will follow.

<mic_string> MIC string used to encrypt and decrypt the configuration file. String length is 1 to 32.

extend Sets share-secret MIC for the extend TLVs received from Reg-Req message.

Examples: To set the shared-secondary-secret for non-encrypted messages or encrypted messages: CASA-CMTS(config)# shared-secondary-secret 1 0 DOCSIS To set the shared-secondary-secret MIC for the extend TLVs received from Reg-Req message: CASA-CMTS(config)# shared-secondary-secret 1 0 DOCSIS extend To remove shared-secret MIC: CASA-CMTS(config)# no shared-secondary-secret 1 CASA-CMTS(config)# no shared-secondary-secret 2 extend

Configure a shared-secondary secret password.

2 show running-config | i secret Example: CASA-CMTS(config)# show running-config | i secret shared-secondary-secret 1 7 d6ab86abb7242b65

Display the configured shared-secondary secret.

Adding the privacy certificate (DOCSIS 3.0 only) To add a manufacturer or root CA certificate to the list of trusted certificates, use the privacy add-certificate command in global configuration mode. To remove a particular certificate, use the no form of this command.

CASA CMTS


Step Command (config) Purpose 1 [no] cable privacy add-certificate {manufacturer|root} <hex-

data> Where:

Example: Add a manufacturer CA certificate to the CMTS list of trusted certificates: CASA-CMTS(config)# cable privacy add-certificate manufacturer 35c146353431a541463b41337343938333373142 FEF03A8BC7A441313134749A0A592C9C66831412

Add a root CA certificate to the CMTS list of trusted certificates: CASA-CMTS(config)# cable privacy add-certificate root “00908300 00300501 308202A1 3082020A A0030201 02020800 90830000 00000130 0D06092A 864886F7 0D010105 05003081 92310B30 09060355 04061302 4A503110 300E0603 55040A13 07546F73 68696261 310F300D 06035504 0B130644 4F435349 53312730 25060355 040B131E 312D312D 31205368 69626175 7261204D 696E6174 6F2D6B75 20546F6B 796F3137 30350603 55040313 2E546F73 68696261 20436162 6C65204D 6F64656D 20526F6F 74204365 72746966 69636174 65204175 74686F72 69747930 1E170D30 30303331 38303830 3030305A 170D3230 30333138 30383030 30305A30 8192310B 30090603 55040613 024A5031 10300E06 0355040A 1307546F 73686962 61310F30 0D060355 040B1306 444F4353 49533127 30250603 55040B13 1E312D31 2D312053 68696261 75726120 4D696E61 746F2D6B 7520546F 6B796F31 37303506 03550403”

manufacturer <hex-data>

Specifies the hexadecimal data for the manufacturer CA certificate. Enter multiple lines as needed, and use a blank line to terminate the string.

root <hex-data>

Specifies the hexadecimal data for the root CA certificate. Enter multiple lines as needed, and use a blank line to terminate the string.

Add a manufacturer or root CA certificate to the list of trusted certificates.

CASA CMTS


Displaying the privacy certificate configuration (DOCSIS 3.0 only) To show configuration of privacy certification:

Step Command Purpose 1 show cable privacy {manufacturer-cert-list | root-cert-list}

Where:

Example: Display BPI+ certificate information using the show cable privacy command: CASA-CMTS# show cable privacy manufacturer-cert-list Cable Manufacturer certificate chain: <certificate dump> CASA-CMTS# show cable privacy root-cert-list Cable Root certificate chain: <certificate dump>

manufacturer-cert-list

Displays the BPI manufacturer certificate verification list.

root-cert-list Displays the BPI root certificate verification list.

Show the configuration of privacy certification for manufacturer certificates that have been added to the CMTS.

Enforcing BPI and BPI+ The CMTS provides commands that enforce the Baseline Privacy Interface (BPI) and BPI+ security protocols running between the CMTS and the cable modems (CMs). BPI authentication protocols protect cable modem data traffic by preventing upstream and downstream eavesdropping by other users who are connected over the same cable. Traffic between the CMTS and the CMs is encrypted using an encapsulation protocol, as well as a key management protocol called Baseline Privacy Key Management (BKPM) for processing authentication and authorization key exchanges between the CM and CMTS. BPI+ is required on all DOCSIS 1.1 (and later) compliant cable modems. Earlier cable modems use BPI. x bpi-enforce — Enforces BPI-authenticated cable modems and prohibits traffic for non-BPI

authenticated cable modems. Data is not forwarded before a BPI-enabled cable modem completes BPI initialization.

x bpi-plus-enforce — Enforces BPI-plus for DOCSIS 1.1 or later cable modems. When

enabled, cable modems running DOCSIS 1.1 or higher that are not running BPI-plus are rejected.

Both options are disabled by default.

CASA CMTS


To enable BPI and BPI+ enforcement:

Step Command (config) Purpose 1 [no] cable privacy bpi-enforce

[no] cable privacy bpi-plus-enforce Example: To enable BPI and BPI+ enforcement: CASA-CMTS# cable privacy bpi-enforce CASA-CMTS# cable privacy bpi-plus-enforce

Enable enforcement of BPI and BPI plus. Use the no form of the command to disable the current setting.

Changing the security association descriptor TLV length The cable sa-des-tlvlen-2 command sets the security association TLV length to two bytes as required by some BPI-authenticated cable modems. These modems may not be able to register with the CMTS using a one-byte descriptor. Use the no form of the command to reset the two-byte SA descriptor TLV to one byte.

Step Command (config) Purpose 1 [no] cable sa-des-tlvlen-2

Example: To set the SA descriptor TLV to two-bytes: CASA-CMTS# cable sa-des-tlvlen-2 CASA-CMTS#

Sets the security association descriptor TLV length to two bytes. Use the no form of the command to revert the setting to a one-byte SA descriptor TLV.

Setting the privacy hotlist (DOCSIS 3.0 only) To mark a manufacturer's or CM certificate as distrusted and to add the certificate to the CMTS hotlist of invalid certificates to prevent those CMs from registering, use the privacy hotlist command in global configuration mode. To remove a particular CM or manufacturer's certificate from the hotlist, use the no form of this command.

Step Command (config) Purpose 1 [no] privacy hotlist {cm <mac-address> | manufacturer <cert-

serial-number>} Where:

Mark a manufacturer's or CM certificate as distrusted and add them to the CMTS hotlist.

CASA CMTS


Example: Add the CM certificate with the MAC address of 00C0.8345.de51 to the hotlist, so that this particular CM cannot register with the CMTS: CASA-CMTS(config)# privacy hotlist cm 00C08345de51 CASA-CMTS(config)# Add a manufacturer CA certificate into the BPI+ hotlist, so that the CMTS will reject any CM attempting to register with a certificate from that particular manufacturer: CASA-CMTS(config)# privacy hotlist manufacturer 1eabdef39b3f171c2e89c6df1143e40b21e4a1b29acc2d9064a30263167eb001053e419c8742842ab74778f07328f5c842768e3136b1068117a1f9f5c8493c606996fa4d6b362ee87ff403f85c41cfae80d5cc123515c3fe3f1e26f2bef2195f92b25b63516961ebce0e89c9b6277ad98cdf414e0203a031cfb4454738e986af1ba42a0355bf7f21ba34f0567780a800172fa9bd99bcad4afb8909026083ac9a0d638298b8873e3e4c8a6e51d057aa366e53c9917886fc0ac5a31848ca57eae79cdd7d8efb2b0e4e100143fcd126f59acb5891fcba76e497472d08111d84472cbb4a4c6b1d90203010001a326302430120603551d130101ff040830060101ff020100300e0603551d0f0101ff040403020106300d06092a864886f70d010105050003820101009cbca0b3ee06d0ac1198291eef1bde42040cbfb442f7249244866d3e1385365454449ced03b6da62218d0baa59c332ae79288aaba988d457161670eb77ebfd8eb4b7a545f1c8a9cbf6a52b7e2b8d65ad1369ac831ecdc3aec0cc2b24d199f971b0c9add78d6a75cc0e1b04d4c005dcae67543d205be2f39c065150a756555d965cb941d8b5eb92afbc8c0ac9ee880c989f53d0c5f8408a5ca679b0e65b198e33791ca347e30eb373a82243ac63ac8440faa83e1486a59ec991352f4d31e434551a258f6f60564c88e9d91e22917be8557a63472bb8bd2cc8bd0ba36ab826db3e6fc8a572a6c2fbff6c736df5cb970a900b4f6ba4f5a7e53e38b87325c08934ef CASA-CMTS(config)#

cm <mac-address>

Specifies the MAC address for the CM certificate to be added to the hotlist. The mac-address should be specified as a hexadecimal string, without periods or other separators.

manufacturer cert-serial-number

Specifies the serial number for the particular manufacturer CA certificate. The cert-serial-number should be specified as a hexadecimal string up to 32 bytes in length. Enter multiple lines as needed, and use a blank line to terminate the string.

CASA CMTS


Configuring an encryption algorithm Casa CMTS supports three encryption algorithms: 40-bit-des, 56-bit-des, and 128-bit-aes. To force a CM use 40-bit-des algorithm for data traffic encryption, perform the following. Note, if CMs do not support 40-bit-des encryption algorithm, the CMs will not be able to complete BPI.

Step Command (config) Purpose 1 [no] cable privacy 40-bit-des

Example: CASA-CMTS(config)# cable privacy 40-bit-des

Set the cable encryption algorithm to 40-bit-des.

To set encryption algorithms with priorities:

Step Command (config) Purpose 1 cable sec encrypt-alg-priority <alg1> [<alg2> <alg3>]

Where:

Example: CASA-CMTS(config)# cable sec encrypt-alg-priority aes128CbcMode des40CbcMode des56CbcMode

<alg1>, <alg2> and <alg3>

One of the three encryption algorithms: - aes128CbcMode 128 bit AES - des40CbcMode 40 bit DES - des56CbcMode 56 bit DES If more than one algorithm is set, the CMTS will choose the highest priority algorithm which the CM supports for data traffic encryption.

Set the encryption algorithm priority when more than one encryption algorithm is set.

Managing revocation certificates The Casa CMTS provides following CLI commands in managing revocation certificate:

x Choosing the management method for revocation certification

x Setting the CRL method refresh interval

x Setting the CRL method URL address

x Setting the OCPS client URL address

x Setting the OCPS client signature

x Displaying the revocation method configuration

x Displaying the CRL configuration

x Displaying the OCPS configuration

CASA CMTS


Choosing a revocation certificate management method To choose a method:

Step Command (config) Purpose 1 [no] cable sec cert-revocation-method [crl | crlAndOcsp | none | ocsp]

Where: crl Management method for CRL.

crlAndOcsp Management method for CRL and OCSP.

ocsp Management method for OCSP.

none No revocation certificate.

Example: CASA-CMTS(config)# cable sec cert-revocation-method crl

Choose the method.

Setting a CRL method URL address Once the CRL or the crlAndOcsp method is chosen, a URL address should also be set. To set a URL address:

Step Command (config) Purpose 1 [no] cable sec cert-revocation-list url <url_string>

Where:

<url_string> URL address, such as http://www.revo-cert-list.com.

Example: CASA-CMTS(config)# cable sec cert-revocation-list url http://www.cert.com

Set a URL address.

Setting an OCSP client URL address

Once OCSP or the crlAndOcsp method is chosen, a URL address should also be set. To set the URL address:

Step Command (config) Purpose 1 [no] cable sec ocsp protocol-url <url_string>

Where:

<url_string> URL address of ocsp client (usually is CMTS).

Example: CASA-CMTS(config)# cable sec ocsp protocol-url http://www.ocsp.net

Set a URL address

CASA CMTS


Setting an OCSP client signature Once ocsp or crlAndOcsp method is chosen, a client should also be set.

To set client signature:

Step Command (config) Purpose 1 [no] cable sec ocsp signature-bypass

Example: CASA-CMTS(config)# cable sec ocsp signature-bypass

Set a client signature.

Displaying the revocation certificate configuration To show configured revocation certificate method:

Step Command (config) Purpose 1 show cable sec cert—revocation-method

Example: CASA-CMTS(config)# show cable sec cert—revocation-method cable sec cert-revocation-method ocsp

Show configured revocation certificate method.

Displaying the CRL configuration To show the CRL configuration:

Step Command (config) Purpose 1 show cable sec cert-revocation-list [url | refresh-interval]

Example: CASA-CMTS(config)# show cable sec cert-revocation-list cable sec cert-revocation-list url http://www.cert.com cable sec cert-revocation-list refresh-interval 10

Show the CRL configuration.

Displaying the OCSP configuration To display the OCSP configuration:

Step Command (config) Purpose 1 show cable sec ocsp [protocol-url | signature-bypass]

Example: CASA-CMTS(config)# show cable sec ocsp cable sec ocsp protocol-url http://www.ocsp.net no cable sec ocsp signature-bypass

Show the OCSP configuration.

CASA CMTS


Configuring the source address verification rule For more information on source address verification (SAV), see the next section. To set a rule for a SAV (Source Address Verification) group:

Step Command (config) Purpose 1 [no] cable sec sav-cfg-list <group_name> <rule_id>

[<ipv4_address> | <ipv6_address>] Where:

<group_name> SAV group name. String length is 1 to 32 characters.

<rule_id> Rule ID in the range 1 to 4,294,967,295. <ipv4_address> Version 4 IP address in the format

xxx.xxx.xxx.xxx/mask_len.

<ipv6_address> Version 6 IP address in the format xxxx:xxx:..:xxx/mask_len.

Example: CASA-CMTS(config)# cable sec sav-cfg-list OneSubNet 1 10.150.3.1/24 CASA-CMTS(config)# cable sec sav-cfg-list ipv6Exp 1 ipv6 2001:180::1/64

Set a rule for a SAV group.

Enabling SAV authorization To enable or disable SAV authorization globally:

Step Command (config) Purpose 1 [no] cable sec sav-auth-enable

Example: CASA-CMTS(config)# cable sec sav-auth-enable CASA-CMTS(config)# no cable sec sav-auth-enable

Enable SAV authorization globally. Use the no form of the command to disable authorization.

Displaying the SAV configuration To show rules for all SAV groups:

Step Command (config) Purpose 1 show cable sec sav-cfg-list [ <group_name> <rule_id>]

Where:

Show rules of all existing SAV groups. If no options are

CASA CMTS


<group_name> SAV group name. String length is 1 to 32 characters.

<rule_id> Rule ID in the range 1 to 4294967295. Example: CASA-CMTS(config)# show cable sec sav-cfg-list cable sec sav-cfg-list Ipv6Exp 1 ipv6 2001:180:0:0:0:0:0:1/64 cable sec sav-cfg-list OneSubNet 1 10.150.3.1/24

specified, all rules are shown.

Enabling configuration file learning When config-file-learning is enabled, the CMTS will record the CMTS-MIC and CM-MIC from the received configuration file. To enable or disable the config-file-learning:

Step Command (config) Purpose 1 [no] cable sec config-file-learning

Example: CASA-CMTS(config)# cable sec config-file-learning CASA-CMTS(config)# no cable sec config-file-learning

Enable or disable config-file-learning.

Configuring TFTP proxies Once an option for TFTP proxies is configured, the CMTS will add the corresponding address into the TFTP message. To configure TFTP proxy:

Step Command (config) Purpose 1 cable sec tftp-option [both | hw-addr | net-addr | none]

Where:

both Both hardware address and net address will be added.

hw-addr Only hardware address will be added.

net-addr net-addr: only net address will be added.

none Neither hardware address nor net address will be added.

Example: CASA-CMTS(config)# cable sec tftp-option both

Configure TFTP proxy.

CASA CMTS


Displaying config file learning status To display config-file-learning status:

Step Command (config) Purpose 1 show cable sec config-file-learning

Example: CASA-CMTS(config)# show cable sec config-file-learning no cable sec config-file-learning

Display config-file-learning status.

Displaying the TFTP option setting To show the TFTP option setting:

Step Command (config) Purpose 1 show cable sec tftp-option

Example: CASA-CMTS(config)# cable sec tftp-option cable sec tftp-options both

Display TFTP options setting.

Configuring the EAE exclusion list The Casa CMTS supports the capability of excluding individual CMs from EAE enforcement based on their MAC addresses. To add or remove an EAE exclusion list:

Step Command (config) Purpose 1 [no] cable sec eae-exclusion <list_id>

Where:

<list_id> EAE exclusive list ID in the range 1 to 4,294,967,295.

Example: CASA-CMTS(config)# cable sec eae-exclusion 1 0015.f2fe.c904

Add an EAE exclusion list. Use the no form of the command to remove the exclusion list.

Adding cable modems to the EAE exclusion list Once a MAC address is added into the exclusion list, the CMTS will not allow the cable modem at the specified MAC address to perform EAE. To add a MAC address to the existing EAE exclusion list:

CASA CMTS


Step Command (config) Purpose 1 [no] cable sec eae-exclusion <list_id> <mac_addr>

Where:

<list_id> EAE exclusive list ID, values are 1 to 4,294,967,295.

<mac_addr> MAC address of the CM in format xxxx.xxxx.xxxx.

Example: CASA-CMTS(config)#cable sec eae-exclusion 1 0050.f112.b764

Add a MAC address to an existing EAE exclusion list. Use the no form of the command to remove the MAC address from the exclusion list.

Displaying the EAE exclusion list To show the EAE exclusion list:

Step Command (config) Purpose 1 show cable sec eae-exclusion

Example: CASA-CMTS(config)# show cable sec eae-exclusion cable sec eae-exclusion 1 0015.f2fe.c904 ffff.ffff.ffff

Display the EAE exclusion list.

Source Address Verification (SAV) When dhcp-authorization is disabled on a DOCSIS MAC domain, anyone can assign their own IP address. This may cause conflicts and may not be desirable by the service provider. One secure way to allow customers authorized by their ISPs to use static IP addresses is to enable DHCP authorization and use the Source Address Verification (SAV) feature of DOCSIS/CMTS/CM. To do this, the CM receives a configuration file with SAV Group Name Subtype encoded. For example (docsis -d sav_merlin.bin):

Main { NetworkAccess 1; VendorSpecific { VendorIdentifier 0xffffff; GenericTLV TlvCode 7 TlvLength 8 TlvValue 0x01066d65726c696e; } MaxCPE 16; UsServiceFlow { UsServiceFlowRef 1; QosParamSetType 7;

CASA CMTS


SchedulingType 2; } DsServiceFlow { DsServiceFlowRef 2; QosParamSetType 7; } /* CmMic 49b9d8d459f9a9119f43188372a00422; */ /* CmtsMic 0dc1e7ce52cb806a57f13d9eea9c4db8; */ /*EndOfDataMkr*/ )

In the config file above, the TLV value for SAV Group Name Subtype is merlin (in hex format: 6d65726c696e). When the CM registers with the CMTS, the CMTS will note the SAV for the CM. The CMTS must be configured as: CMTS(config)#cable sec sav-cfg-list merlin 1 192.168.7.77/32 192.168.7.77 is the static IP used by the CPE. The 32-bit mask specifies only this IP. Use a mask to allow a contiguous range of IP addresses. The number “1” after the “merlin” string is the SAV Group Name Subtype. By default the dhcp-authorization is enabled. Unauthorized IP addresses are not allowed. The cable modem security configuration will allow authorized IPs behind a given CM. By default, cable sec sav-auth-enable command is enabled. The sav-cfg-list supports up to 2048 entries to match the number of cable modem authorization names. To authorize an individual MAC address without changing the modem config file, use the following command:

Step Command (config) Purpose 1 [no] cable host authorization <mac_address> <ip_address>

Where:

<mac_address> CPE MAC address in the format: xxxx.xxxx.xxxx

<ip_address> CPE IP address in the format: A.B.C.D

Example: CASA-CMTS(config)# cable host authorization 0015.f2fe.c904 67.1.8.23

Authorize individual cpe MAC address.

To authorize an IP address or IP subnet (specified in SAV config list) for a specified CM:

Step Command (config) Purpose 1 [no] cable sec sav-cfg-list <list_name> <rule_id>

<ip_address/netmask> Authorize an IP address or IP

CASA CMTS


[no] cable sec sav-cfg-list <list_name> <rule_id> ipv6 <ipv6_address/netmask> Where:

list_name Specifies the name of the SAV config list. Up to 16 characters may be specified.

rule_id Specifies the config list rule identifier in the range 1 to 4294967295.

<ip_address/netmask> <ipv6_address/netmask>

Specifies the cable modem IPv4 address in the format in 32-bit notation. xxx.xxx.xxx.xxx/netmask. Specifies the IPv6 address of the modem in 128-bit notation. xxxx:xxxx:...:xxxx

Example: CASA-CMTS(config)#cable sec sav-cfg-list host1 1 192.168.9.0/24

subnet (specified in SAV config list) for a specified CM.

Spectrum management Casa Spectrum Management (CSM) allows the Casa CMTS to monitor the quality of upstream paths and automatically perform correcting actions when upstream plant impairments are detected. The monitored upstream plant impairments include Signal to Noise Ratio (SNR), correctable FECs, and uncorrectable FECs. The automatic corrections include frequency hopping, upstream channel-width adjustment, and dynamic upstream modulation profile changes. CSM also provides a means to report the configurations, actions, and some test facilities. This section describes briefly the algorithm of CSM, and then the operation commands. x Creating spectrum rules x Setting the frequency band x Setting hopping periods and priorities x Setting the channel-width adjustment range x Specifying the modulation profile x Setting the FEC threshold x Assigning spectrum rules to upstream interfaces x Setting the monitoring period x Displaying the spectrum map x Displaying the spectrum noise level x Enabling and disabling CM hopping x Displaying and removing CM hopping history

CASA CMTS


CSM algorithm Casa Spectrum manager uses the Fast Fourier Transform (FFT) technique to monitor signal quality on the return path. The FFT screening results, SNR and FEC errors in particular, are the main error events monitored to determine whether plant noise exists and corrective actions are necessary. Corrective action(s) can be one, two or all three of: frequency hopping, channel width adjustment, and dynamic modulation profile change.

Spectrum manager maintains a list of discrete channel frequencies and/or one or more frequency bands for each upstream interface as frequency hopping targets. This is called the spectrum map. CSM scans through the spectrum map to select the cleanest channel. The spectrum map is updated when a hop is performed. CSM uses spectrum rule to manage the corrective actions. A spectrum rule consists of a set of thresholds and a sequential list of actions. An action can be frequency hopping, channel width adjustment, or modulation profile. A FFT procedure is triggered when a monitored indicator to an upstream interface hits a defined or default threshold.

The actions take place in an order defined by the operator in the action commands. If plant signal quality is maintained within the thresholds due to one or more actions, the subsequent actions in a rule will not be performed since it is not necessary.

If the upstream channel signal with corrected modulation and/or adjusted channel width returns to 3 dB above normal, the spectrum manager may roll back the settings to their original channel width or modulation profile setting. The hop back threshold can also be specified in the CLI.

To activate CSM on specified upstream interfaces, spectrum rules need to be defined and assigned to upstream interfaces.

Creating spectrum rules To create a spectrum rule or to enter the spectrum rule setting mode:

Step Command (config) Purpose 1 spectrum rule <id>

Where:

<id> Spectrum rule ID number. Valid values are 1 to 40.

Example: CASA-CMTS(config)# spectrum rule 2 CASA-CMTS(conf-spec-rule 2)#

Create a spectrum rule or enter spectrum rule setting mode.

Exiting spectrum rule mode To exit from spectrum rule setting mode:

CASA CMTS



Where:




2 end Example: CASA-CMTS(config-spec-rule 2)# end CASA-CMTS(config)#

Exit from the spectrum rule setting mode.

Setting a frequency band To set a frequency band:


Where:

<id> Specifies the spectrum rule ID number. Valid values are 1 to 40.



CASA CMTS


2 [no] frequency band <freq1> <freq2> Where:

<freq1> Left edge of the frequency band, unit in Hz.

<freq2> Right edge of the frequency band, unit in Hz. Example: Set two frequency bands, 14-20 and 30-60 MHz, to spectrum rule 2: CASA-CMTS(conf-spec-rule 2)# frequency band 14000000 20000000 CASA-CMTS(conf-spec-rule 2)# frequency band 30000000 60000000 Remove frequency band 30-33 MHz from a defined spectrum group: CASA-CMTS(conf-spec-rule 2)# frequency band 14000000 20000000 CASA-CMTS(conf-spec-rule 2)# frequency band 30000000 60000000 CASA-CMTS(conf-spec-rule 2)# no frequency band 30000000 33000000 CASA-CMTS(conf-spec-rule 2)# show running-config … spectrum rule 2 frequency band 14000000 20000000 frequency band 33000000 60000000 …

Set or remove a frequency band.

Setting a discrete frequency To set a discrete frequency:


Where:

<id> Spectrum rule ID number. Valid values are 1 to 40. Example: CASA-CMTS(config)# spectrum rule 2 CASA-CMTS(conf-spec-rule 2)#


2 frequency <freq> Where:

<freq> Frequency in Hz. Example: CASA-CMTS(conf-spec-rule 2)# frequency 34000000

Set or remove a frequency band.

CASA CMTS


Note: After the spectrum rule is assigned to an upstream interface, the discrete frequency becomes a frequency band with the same width as that of the upstream interface

Setting the hopping period This command sets a time period between two consecutive frequency hops. This period allows new channels to stabilize before making a frequency hopping decision to assign the traffic to cleaner unstream channels. To set the hopping period:

Step Command (config) Purpose 1 hop period <time>

Where:

<time> Specifies the hopping period in seconds. Valid values are 1 to 3,600. The default is 30 seconds.

Example: CASA-CMTS(config)# hop period 100

Specifies the time period to transpire before a frequency hops to a cleaner channel.

Setting the hopping priority This command specifies the order of effort of trying correcting actions (frequency hopping, upstream channel-width adjustment, and dynamic upstream modulation change). There is no default action or default order of actions. The action(s) has to be explicitly specified in the action command. To set the priority:


Where:



2 action frequency modulation channel-width or action modulation frequency channel-width or action frequency channel-width modulation Example: CASA-CMTS(conf-spec-rule 2)# action modulation frequency channel-width

Set the frequency hopping priority.

CASA CMTS


Note: Frequency hopping will not occur if no frequency band is specified to a spectrum rule. Modulation profile change will not occur if the no secondary profile defined in the upstream. Channel-width adjustment will not occur if no channel width range specified.

Setting the channel-width adjustment range To set the channel-width adjustment range:


Where:



2 [no] channel-width <start-width> <end-width> Where:

<start-width> Start channel-width in Hz. Valid values are 400000, 800000, 1600000, 3200000, and 6400000.

<end-width> End channel-width in Hz. Valid values are 200000, 400000, 800000, 1600000, and 3200000, and should also be less or equal to the specified start-width.

Example: CASA-CMTS(conf-spec-rule 2)# channel-width 3200000 1600000

Set the channel-width adjustment range.

Note: If the specified start-width is larger than current effective width, channel-width change starts from start-width. Otherwise, the change starts with current effective width.

Specifying a modulation profile SNR To specify a modulation profile SNR threshold:


Where:

<id> Spectrum rule ID number. Valid values are 1 to 40. Example:


CASA CMTS


CASA-CMTS(config)# spectrum rule 2 CASA-CMTS(conf-spec-rule 2)#

2 [no] profile <id> snr-threshold <tenth-dB> Where:

<id> Modulation profile ID which can be predefined or user defined.

<tenth-dB> SNR threshold number in units of tenth dB. Example: Specify profiles 3 and 4 to spectrum rule 2 with SNR 130 and 200: CASA-CMTS(conf-spec-rule 2)# profile 3 snr-threshold 130 CASA-CMTS(conf-spec-rule 2)# profile 4 snr-threshold 200 To remove a spectrum rule profile: CASA-CMTS(conf-spec-rule 2)# no profile 3

Specify a modulation profile SNR threshold.

Note: 0 or more profiles with an SNR threshold can be specified for a spectrum rule. Casa Spectrum Management (CSM) uses the SNR threshold of a modulation profile for two purposes: 1. One of the three triggers (SNR, correctable FEC and uncorrectable FEC) for possible

corrective actions.

2. As a reference to evaluate a calculated SNR (based on FFT data) is sufficient for a particular modulation profile in an effort of corrective or improvement action.

Specifying a modulation profile SNR threshold If no SNR threshold is specified for a modulation profile in a spectrum rule, it defaults to 0. This means the SNR will not be a trigger for a possible action if an upstream channel is using this modulation profile (number 1 above). Only correctable FEC and uncorrectable FEC are possible triggers to start a corrective action.

To prevent SNR from triggering a possible corrective action for a particular modulation profile, do not specify the SNR threshold for the modulation profile, or use the following command:


Where:




CASA CMTS


2 profile <id> snr-threshold 0 Where:


Example: CASA-CMTS(conf-spec-rule 2)# profile 3 snr-threshold 0

Specify a modulation profile SNR threshold setting to 0.

Specifying the hop-back threshold To set the threshold for hopping back:


Where:




2 profile <id> snr-threshold <first> [<second>] Where:


<first> The threshold for hopping to the next profile.

<second> The threshold for hopping back to the original profile. When <second> is configured, CSM will use <second> as hop-back threshold instead of <first> + 3dB.

Example: CASA-CMTS(config)# spectrum rule 2 CASA-CMTS(conf-spec-rule 2)# profile 1 snr-threshold 100

Set the threshold for hopping back.

CASA CMTS


Default SNR threshold for different modulations CSM has a built-in default SNR threshold for each modulation type and for each modulation profile. The default SNR threshold takes effect for a spectrum rule, if there is no threshold specified in a spectrum rule for a particular modulation profile. CASA-CMTS#show spectrum snr-threshold-default Default SNR threshold per modulation type (tenth dB): Modulation Conservative Addressive QPSK: 130 100 8QAM: 190 160 16QAM: 220 190 32QAM: 250 220 64QAM: 280 250 128QAM: 310 290

Setting the FEC threshold To set the correctable-FEC threshold:


Where:




2 correctable-fec threshold <percentage> Where:

<percentage> Correctable-fec threshold percentage. Valid values are 0 to 100. The default is 3.

Example: CASA-CMTS(conf-spec-rule 2)# correctable-fec

threshold 5

Set the correctable-FEC threshold.

To set the uncorrectable-FEC threshold:


Where:

Create a spectrum rule or enter spectrum rule

CASA CMTS




setting mode.

2 uncorrectable-fec threshold <percentage> Where:

<percentage> Uncorrectable-fec threshold percentage. Valid values are 0 to 30. The default is 1.

Example: CASA-CMTS(conf-spec-rule 2)# uncorrectable-fec threshold 0

Set the uncorrectable-FEC threshold.

Assigning a spectrum rule to an upstream interface To assign a spectrum rule to an upstream interface:








2 spectrum-rule <identifier> Where:

Specify the spectrum rule identifier.

CASA CMTS


<percentage> Specifies the previously-created spectrum rule by the rule’s 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

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: x Plant noise level exceeds SNR threshold defined explicitly in the commands or by default x Percentage of correctable FEC errors of total packets received on the upstream (during

polling period) exceeds the defined or default threshold x 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.

Assigning modulation profiles to an upstream interface To assign modulation profiles to an upstream interface:






Example: Enter upstream interface mode for upstream port 0 on module 11, physical channel 0. CASA-CMTS(config)# interface upstream 11/0


CASA CMTS


CASA-CMTS(config-if-ups 11/0.0)#

2 logical-channel <number> profile <profile_id> secondary-profile <string> Where:


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

Set the upstream channel modulation profile.

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 profile’s 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 (Release 5.4 and later) Multiple (up to 5; 2 in 5.2) secondary profiles can be specified for an upstream interface, so multiple steps can be achieved for dynamic modulation profile change. CASA-CMTS(config-if-ups 1/2)# logical-channel 0 profile 3 secondary-profile 12,20,33 Where:

4. Modulation profile 12, 20 and 33 have compatible channel types. 5. The order of 12, 20, and 33 specifies the priority which CSM tries to use the profiles. 6. Lower priority suggests a less bandwidth efficient modulation profile.

CASA CMTS


Setting the monitoring period CSM monitors the quality of all upstream channels by periodically polling measured parameters of SNR, correctable and uncorrectable FECs. The user can configure this monitoring period. The default setting is 30 seconds.

To configure the polling period:

Step Command (config) Purpose 1 cable monitor-period <seconds>

Where:

<seconds> Polling period in second. Valid values are 1 to 3600.

Example: Set monitoring polling-period to 100 seconds: CASA-CMTS(config)# cable monitor-period 100

Configure the polling period.

Displaying hopping history To display hopping history:

Step Command (config) Purpose 1 show spectrum hop-history [upstream X/Y]

Example: CASA-CMTS# show spectrum hop-history upstream 1/4 Port Action Time Code From To Reason 1/4/0 Mon Oct 26 22:12:26 2009 C 800000 1600000 SNR 283 (220) 1/4/0 Mon Oct 26 22:11:26 2009 C 1600000 800000 SNR 243 (220) cFEC 0 (3) uFEC 3 (1) 1/4/0 Mon Oct 26 21:34:26 2009 C 3200000 1600000 SNR 210 (220) cFEC 90 (3) uFEC 0 (1) 1/4/0 Mon Oct 26 21:33:56 2009 C 800000 3200000 SNR 281 (220) 1/4/0 Mon Oct 26 21:32:56 2009 M 12 22 SNR 285 (220) cFEC 0 (3) uFEC 20 (1) 1/4/0 Mon Oct 26 21:32:26 2009 C 1600000 800000 SNR 252 (250) cFEC 6 (3) uFEC 6 (1) 1/4/0 Mon Oct 26 21:31:56 2009 C 800000 1600000 SNR 288 (250) 1/4/0 Mon Oct 26 21:31:26 2009 C 1600000 800000 SNR 254 (250) cFEC 5 (3) uFEC 0 (1) 1/4/0 Mon Oct 26 21:30:56 2009 C 3200000 1600000 SNR 218 (250) cFEC 113 (3) uFEC 0 (1) 1/4/0 Mon Oct 26 21:30:26 2009 C 800000 3200000 SNR 285 (250) 1/4/0 Mon Oct 26 21:29:56 2009 C 1600000 800000 SNR 247 (250) cFEC 38 (3) uFEC 0 (1)

Displays the hopping history.

CASA CMTS


1/4/0 Mon Oct 26 21:29:26 2009 C 800000 1600000 SNR 282 (250) 1/4/0 Mon Oct 26 21:28:26 2009 C 1600000 800000 SNR 258 (250) cFEC 4 (3) uFEC 0 (1) 1/4/0 Mon Oct 26 21:27:56 2009 C 800000 1600000 SNR 281 (250) 1/4/0 Mon Oct 26 21:26:56 2009 C 1600000 800000 SNR 253 (250) cFEC 13 (3) uFEC 0 (1) 1/4/0 Mon Oct 26 21:26:26 2009 C 6400000 1600000 SNR 192 (250) cFEC 100 (3) uFEC 19 (1) 1/4/0 Mon Oct 26 21:25:56 2009 C 800000 6400000 SNR 288 (250) 1/4/0 Mon Oct 26 21:20:26 2009 M 10 12 SNR 283 (250) cFEC 0 (3) uFEC 25 (1) 1/4/0 Mon Oct 26 21:19:56 2009 M 3 10 SNR 286 (290) cFEC 0 (3) uFEC 3 (1) 1/4/0 Mon Oct 26 21:18:26 2009 C 6400000 800000 SNR 211 (280) cFEC 202 (3) uFEC 0 (1) 1/4/0 Mon Oct 26 21:17:25 2009 M 0 3 Configuration change 1/4/0 Mon Oct 26 21:17:25 2009 C 0 6400000 Configuration change 1/4/0 Mon Oct 26 21:17:25 2009 F 0 17000000 Configuration change

Displaying the spectrum map The spectrum map is a collection of possible frequency slots for the frequency hopping operation to target. The map is dynamic for each upstream channel. It depends on the frequency ranges defined in the rule and the current frequency used by other channels in the same Service Group. The operator does not need to be concerned about frequency overlap in the same Service Group (fiber node). It is recommended to use larger frequency ranges as hopping targets.

To display the spectrum map for an upstream interface:

Step Command (config) Purpose 1 show spectrum-map upstream <X/Y>

Where:

<X/Y> Upstream interface indices. X is module index; Y is port index.

Example: CASA-CMTS(config)# show spectrum-map upstream 1/2 Spectrum Map for interface 1 /2.0 band 0: [18000000, 20000000] ...narrower than current chan-width 3200000 band 1: [22000000, 25400000] band 2: [28600000, 40000000] band 3: [58400000, 61600000] Note: A frequency band narrower than current chan-width of the channel will not be useful in frequency hopping.

Displays the spectrum map.

CASA CMTS


Displaying the spectrum noise level To display the spectrum noise level for all possible upstream frequencies at channel-width 3.2MHz:

Step Command (config) Purpose 1 show spectrum upstream <X/Y> [channel-width <chan_width>]

[raw] Where:

<X/Y> Upstream interface indices. X is module index; Y is port index.

<chan_width> By channel width. Valid values are 200000, 400000, 800000, 1600000, 3200000 and 6400000.

raw In dB. In the 5.4 release, if “raw” is added to the show spectrum upstream command, the result is showed in dB. Without this parameter, the result is displayed in dBmV.

Example: Display spectrum noise levels for upstream interface 2/0: CASA-CMTS(config)# show spectrum upstream 2/0 raw FREQUENCY NOISE-LEVEL at channel-width 3200000 (dBmV) 5000000: -42.1 8200000: -42.1 11400000: -42.1 14600000: -42.1 17800000: -42.1 21000000: -42.1 24200000: -42.1 27400000: -42.1 30600000: -42.1 33800000: -42.1 37000000: -42.1 40200000: -35.1 43400000: -42.1 46600000: -42.1 49800000: -42.1 53000000: -42.1 56200000: -42.1 59400000: -42.1 62600000: -42.1 Display spectrum noise levels for upstream interface 2/0 in dB: CASA-CMTS(config)# show spectrum upstream 2/0 chan-width 6400000 raw FREQUENCY NOISE-LEVEL at channel-width 6400000 (dB) 5000000: 9.5 11400000: 0.0 17800000: 7.8 24200000: 7.8 30600000: 6.0 37000000: 7.0 43400000: 17.2 49800000: 9.5 56200000: 9.5 62600000: 6.0

Displays the spectrum map.

CASA CMTS


Enabling CM hopping When multiple logical channels are configured with different modulation profiles in an upstream physical channel and a cm-hop command is issued, a cable modem can be moved among the channels based on specified thresholds. If the thresholds specified are exceeded for the cable modem, it will move to the next (more reliable) logical channel. To enable or disable CM hopping:

Step Command (config) Purpose 1 spectrum rule <rule_id>

Where:

<rule_id> Specifies the rule identifier in the range 1 to 40.

Example: CASA-CMTS(config)# spectrum rule 1 CASA-CMTS(conf-rule 1)#

Select the spectrum rule.

2 [no] cm-hop Example: CASA-CMTS(conf-rule 1)# correctablefec threshold 5 CASA-CMTS(conf-rule 1)# uncorrectablefec threshold 3 CASA-CMTS(conf-rule 1)# cm-hop CASA-CMTS(conf-rule 1)# interface ups 1/0 CASA-CMTS(conf-rule 1)# no cm-hop

Enable or disable CM hopping.

Displaying CM hopping history To display or remove logged events of CM hopping:

Step Command (config) Purpose 1 spectrum rule <rule_id>

Where:

<rule_id> Specifies the rule identifier in the range 1 to 40.

Example: CASA-CMTS(config)# spectrum rule 1 CASA-CMTS(conf-rule 1)#

Select the spectrum rule.

2 show cm-hop log clear cm-hop log Example: CASA-CMTS(config)# spectrum rule 1 CASA-CMTS(conf-rule 1)# show cm-hop log

Show or remove CM hopping history.

CASA CMTS


Considerations when using CSM 1. Spectrum Map is a collection of frequency ranges where a target frequency can be

selected when performing frequency hopping for an upstream channel. It is dynamic (calculated when it is used) and upstream interface specific. It is calculated based on two factors. First, frequency ranges specified in a given spectrum rule. And second, current frequencies used by other upstream channels in the same service group. The user can give a large frequency range(s) and let CSM take care it without concerns about frequency overlapping.

2. Discrete frequency in a spectrum rule can be viewed as a frequency band with a given center frequency and current channel width.

3. There is no frequency hopping back when a channel’s impairments disappear; only modulation and channel width.

4. Meaningful order of modulation profiles specified for dynamic modulation profile change is the order of bandwidth efficiency (or reliability), most efficient one first (most reliable last).

5. If the configured channel width differs from the start channel width in a spectrum rule, the start channel width in the rule governs. For example, if the configured channel width is 3.2MHz and “chan-width 6400000 800000” is in the rule, then when a channel width adjustment occurs, it will change to 1.6 MHz or lower. When it recovers, it will try from 6.4 MHZ (the high end) first, then the lower widths.

6. The show interface upstream x/y and show running-config commands show configurations, not necessarily the current configuration of an upstream interface. If CSM is in use, use show interface upstream x/y current and show spectrum hop-history upstream x/y.

7. CSM has a built-in default SNR threshold for each modulation type. To view them, use the CLI command “show spectrum snr-threshold-default”. CSM can work without an SNR threshold for a modulation profile specified in a spectrum rule; that is, using the default SNR threshold. However, a corrective action will not take place due to low polled SNR.

8. There can be up to three action command items in the spectrum rule. There is no default action. CSM will attempt a corrective (or improvement) action in the order specified in the command. However, this does not guarantee that the action will take place. It is important to know how the action helps before performing it. If an action does not help, it attempts the next one. The most common reason for an action not helping is that the calculated SNR for that action does not satisfy the SNR threshold for a modulation profile.

9. If the user wants to change configuration based on modulation profile or channel width (whatever the user wants CSM to manage), the user should remove spectrum rule from the channel first, and put the spectrum rule back in the channel list after the configuration change. This will avoid a conflict between the manual change and CSM control.

Frequency hop case study If CSM cannot find a frequency to hop to, it will not hop, even if the current frequency is too noisy to support modems. For example, if there is noise at 31 MHz on interface 5/1/0, then it should perform a frequency hop. However, if the spectrum map is,

CASA CMTS


CASA-CMTS(config)#show spectrum-map upstream 8/1 Spectrum Map for interface 8/1/0 band 0: [28000000, 32800000] band 1: [36000000, 38400000] band 2: [41600000, 42000000]

There is no to hop to avoid the noise. The three bands (0-2) are too narrow to escape the noise. When CSM tries a hop (frequency, modulation, or channel width), it checks if the calculated SNR at the destination (new freq, etc.) is good enough to accommodate the SNR threshold (280, in this case). If so, hopping is performed. Otherwise, it tries the next action. In this example, there is no other action.

However, if the 8/4 frequency is moved to 45MHz (away from 25+1.6=26.6MHz) to give channel 8/1 more room, as in, spectrum rule 2 frequency band 26000000 42000000 action frequency

then move channel 8/1 back to 30MHz (resetting the CSM state machine at channel 8/1), and then apply the rule 2 to upstream 8/1, to acquire: CASA-CMTS(config-if-ups 8/1)#show spectrum-map upstream 8/1 Spectrum Map for interface 8/1/0 band 0: [26000000, 32800000] band 1: [36000000, 38400000] band 2: [41600000, 42000000]

When the CSM poll reaches a threshold, the channel hops to freq 27.6MHz, as indicated by the following debug message: [Wed Dec 2 21:26:18 2009]-DE-CSM-FSM-1: H -> R on 8/1/0.. freq hop 30000000 to 27600000 CASA-CMTS#show spectrum hop-history upstream 8/1 Port Action Time Code From To Reason 8/1/0 Wed Dec 2 21:26:18 2009 F 30000000 27600000 SNR 80 (280) cFEC 2 (3) uFEC 30 (1) 8/1/0 Wed Dec 2 21:20:29 2009 F 0 30000000 Configuration change 8/1/0 Wed Dec 2 20:58:46 2009 F 30000000 29600000 SNR 131 (280) cFEC 0 (3) uFEC 29 (1) 8/1/0 Wed Dec 2 20:54:16 2009 F 0 30000000 Configuration change 8/1/0 Wed Dec 2 20:31:14 2009 F 30000000 29600000 SNR 100 (280) cFEC 1 (3) uFEC 29 (1) 8/1/0 Wed Dec 2 20:29:33 2009 F 29600000 30000000 Back to Configuration 8/1/0 Wed Dec 2 17:08:59 2009 F 30000000 29600000 SNR 106 (280) cFEC 1 (3) uFEC 28 (1) 8/1/0 Wed Dec 2 16:41:45 2009 M 0 10 Configuration change 8/1/0 Wed Dec 2 16:41:45 2009 C 0 3200000 Configuration

CASA CMTS


change 8/1/0 Wed Dec 2 16:41:45 2009 F 0 30000000 Configuration change

CSM configuration example Example: 1: Modulation and channel width spectrum rule 1 channel-width 6400000 800000 action modulation channel-width correctable-fec threshold 3 uncorrectable-fec threshold 1 profile 3 snr-threshold 280 profile 12 snr-threshold 250 profile 22 snr-threshold 220 profile 30 snr-threshold 190 profile 33 snr-threshold 150 interface upstream 1/0 spectrum-rule 1 … logical-channel 0 profile 3 secondary-profile 12,22,30,33

Example: 2: Frequency, channel width, and modulation spectrum rule 20 frequency 60000000 frequency band 5500000 40000000 frequency band 46000000 51200000 channel-width 6400000 800000 action frequency channel-width modulation correctable-fec threshold 3 uncorrectable-fec threshold 0 profile 10 snr-threshold 300 profile 20 snr-threshold 260 interface upstream 2/0.0 spectrum-rule 20 …. logical-channel 0 profile 10 secondary-profile 20

Spectrum measurement (DOCSIS 3.0 only) The Casa CMTS is Spectrum Measurement DOCSIS 3.0 compliant. A CLI command is used to show the measured results. Note that the measurement must be triggered through a MIB setting by creating a table entry for docsIf3CmtsSpectrumAnalysisMeasTable for an upstream channel. You can use a spectrum analysis application to poll the MIB entry docsIf3CmtsSpectrumAnalysisMeasAmplitudeData and to retrieve the spectrum measurement data and to display the data in graph form.

CASA CMTS


Displaying spectrum measurement results To display spectrum measurement results for a specified upstream channel:

Step Command (config) Purpose 1 show spectrum-meas upstream <X/Y>

Where: <x/y> Upstream interface indices. X is module

index; Y is port index. Example: CASA-CMTS(config)# show spectrum-meas upstream 2/0 See below.

Display the spectrum measurement results.

Displaying spectrum measurement results for upstream interface 2/0 CASA-CMTS(config)# show spectrum-meas upstream 2/0 2/0 (0) Spectrum MEAS data (in Hz): chan cnter freq: 8000000 frequency span: 10240000 number of bins: 513 resolution bw: 20000 bin spacing: 20000 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2

CASA CMTS


F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F7 4C F8 DA F7 4C F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2 F4 F2

CASA CMTS


Running spectrum analysis across the entire spectrum With the following CLI command, the Casa CMTS displays full spectrum data in the same MIB entry and same format, which, in turn, can be used for same purpose. Note that this command will always display 40960000, which is the center frequency (chan cnter freq) of the full spectrum.

Step Command (config) Purpose 1 spectrum analysis full-spectrum

Example: CASA-CMTS(config)# show spectrum-meas upstream 2/0 See below.

Select the full spectrum.

Spectrum analysis across the entire spectrum CASA-CMTS(config)# spectrum analysis full-spectrum CASA-CMTS# show spectrum-meas upstream 1/0 1/0 (0) Spectrum MEAS data (in Hz): chan cnter freq: 40960000 frequency span: 81920000 number of bins: 1024 resolution bw: 80000 bin spacing: 80000 FC 66 FE C0 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 52 F6 ……………….

Configuring load balancing The load balancing feature for the Casa CMTS allows system operators to distribute cable modems across radio frequency downstream and upstream channels on the same cable interface line card, or across multiple cable interface line cards in some circumstances. Load balancing maximizes bandwidth and usage of the cable plant. Load balancing supports multiple methods to achieve greater bandwidth availability. These include static and dynamic load balancing schemes, inter-line card and intra-line card support, and in some circumstances, configuration of load balancing groups that entail multiple interfaces, multiple load balancing policies, and the option to configure multiple additional load balancing parameters.

CASA CMTS


A CMTS channel can be load-balanced using two methods:

x Number of cable modems -- Load balancing according to the number of cable modems on the interface.

x Utilization -- Load balancing according to the current percentage of channel utilization. Each of the methods can further be operated in two types: static or dynamic.

x Static -- Static load balancing is done at ranging request time. When a cable modem sends its initial ranging request message, the CMTS responds with a ranging response message that includes either a Downstream Frequency Override or an Upstream Channel ID Override field that instructs the cable modem which channels it should use.

x Dynamic -- This is a form of load balancing in which cable modems are moved among upstream and downstream channels within the same service group after their initial difference between two interfaces exceeds a user-defined percentage. The CMTS will use DCC/UCC messages to move CMs with single upstream/downstream channels and DBC (dynamic bonding change) messages to move CMs with bonding upstream/downstream channels to different bonding groups. For DOCSIS and EuroDOCSIS 3.0 modems, the dynamic load-balancing software generates a downstream channel set with a minimum load to fit the modem’s RCP. This prevents rejection of the new channel set so that load balancing is not canceled when the assigned modem is under load.

The Casa CMTS supports both methods and types to load balance upstream and downstream channels. You can configure a Casa CMTS using static load balancing only, or using static load balancing and dynamic load balancing together.

Because load balancing can only be done to upstream and downstream interfaces sharing the same physical connectivity, the upstream and downstream interfaces have to belong to the same service group. Both channel bonding and non-channel bonding modems can participate in load balancing. Channel bonding modems will count as one CM for each of its channels.

To configure load balancing,

1. Define the MAC domains and the service groups. 2. Define the basic rules and/or the execution rules. 3. Define the load balancing policy and assign the rules to the policy. 4. Apply the policy to a load balancing group, either the default group or a restricted load

balance group. To apply a load balancing policy globally, apply it to the default group. To apply different load balancing policies to different MAC Domain/Service Groups, first define the rules and the policies. Then create a restricted load balance group, and assign it to the MAC Domain/Service group. This section covers commands for the following operations:

CASA CMTS


Enable/disable load balancing

General load balance groups • Enter general load balance group default • Enable or disable load balance function on mac-sg general group • Specify technique to move cable modems • Remove technique • Specify the policy to use for load balancing execution

Load balancing basic rules • Enter a basic rule • Enable or disable this rule • Specify a time period

Load balancing execution rules • Enter a load balance execution rule • Specify minimum time interval between each load balance • Specify minimum time interval between each upstream load balance • Specify minimum time interval to move the same modem • Specify method for load balance calculation • Specify method of upstream load balance for load balance calculation

Load balancing policies • Enter a load balance policy • Add or remove basic rule into a policy • Add/replace or remove execution rule into a policy

Restricted load balancing groups • Enter load balance restricted group • Specify mac domain on a restricted group • Enable or disable load balance function on this restricted group • Specify technique to move cable modems • Remove technique • Add service type ID • Add or remove upstream and downstream channel

Exclusion lists • Add a CM into exclusion list • Remove a CM from exclusion list

Restricted cable modems • Enter to restricted CM configuration • Enter or remove CM mac-address information • Add or remove service type ID • Add or remove reference to a restricted load balance group

CM frequency and channel relocation • Change both upstream and downstream via DCC method • Change downstream via DCC method

CASA CMTS


• Change upstream via DCC method • Change upstream via UCC method • Change bonded CM’s upstream and downstream via DBC method • Change bonded CM’s downstream via DBC method • Change bonded CM’s upstream via DBC method

Displaying load balancing • Show load balance • Clear all load-balance logs

Static CM bonding groups • Add or delete a static downstream CM bonding group • Add or delete a static upstream CM bonding group • Set the provisioned attribute mask • Add or remove upstream channel • Set the DSID re-sequencing wait time • Set the DSID re-sequencing warning threshold

Command default values • Default values for general load-balance group default • Default values for general/restricted load-balance group • Default values for load-balance basic rule • Default values for load-balance execution rule

Enabling and disabling load balancing This command corresponds to MIB docsLoadbal3System. To enable or disable the load balancing function globally:

Step Command (config) Purpose 1 [no] load-balance enable

Example: CASA-CMTS(config)# load-balance enable

CASA-CMTS(config)# no load-balance enable

Enable or disable load balancing.

Disabling upstream load balancing To disable upstream load balancing only, specify upstream load balancing and set the load and enforce values to 0 in the execution rule. See the sections on specifying upstream method and threshold.

CASA CMTS


Enabling load balancing across MAC domains The CMTS supports static load balancing across MAC domains in networks where upstream and downstream channels are on two MAC domains, such as “docsis mac 1” and “docsis mac 2.” Use the load-balance enable across-mac command to specify upstream precedence (default), or specify the downstream option for downstream load balancing precedence. By default, the upstream channel has precedence in load balancing across MAC domains, where the lowest loaded (least busy) upstream channel is selected within the service group. Then, the lowest loaded downstream channel is selected within the MAC domain of the selected upstream channel. If the downstream precedence is configured, then the downstream channel is selected first. The CMTS will use downstream frequency override and the upstream channel ID override in the ranging response message to move modems to a different MAC domain if needed. This applies to all DOCSIS 1.0, 1.1, 2.0 and 3.0 modems. The SID in the ranging response message is 0x3fff. Additionally, the load-balance enable downstream command specifies downstream load balancing preference on channels within a MAC domain.

Step Command (config) Purpose 1 [no] load-balance enable across-mac [downstream]

Example: CASA-CMTS(config)# load-balance enable across-mac

CASA-CMTS(config)# no load-balance enable across-mac

Enable or disable static load balancing across MAC domains.

General load balancing groups The general load balance group default contains the default settings for newly-created general load-balance groups.

Entering the general load balance group default To enter the general load balance group defaults:

Step Command (config) Purpose 1 load-balance general-group default-settings

Example: CASA-CMTS(config)# load-balance general-group

default-settings

CASA-CMTS(load-bal-general-default)#

Enter load balance group default mode.

CASA CMTS


Entering the general load balance group Once docsis mac interfaces and service groups are configured, a General Load Balance Group will form automatically for each MAC Domain Service Group (MD-SG). General Load Balance Group will use the load balancing settings from general load balance default settings. The user can also configure different load balancing settings using the following commands.

To enter the general load balance group to configure load balancing settings:

Step Command (config) Purpose 1 load-balance general-group mac-domain <number> service-group

<string> Where:

<number> MAC domain number in the range 1 to 32.

<string> Service group name. Example: CASA-CMTS(config)# load-balance general-group mac-domain 1 service-group FN_A CASA-CMTS(load-bal-general-mac-1-sg-FN_A)# In the example above, the service-group definition must be configured prior to running this command.

Enter the load balance group.

Enabling the load balance function on a MAC-SG general group To enable or disable the load balance function on a mac-sg general group:


Example: CASA-CMTS(config)# load-balance general-group default-settings CASA-CMTS(load-bal-general-default)#


2 [no] enable Example: CASA-CMTS(load-bal-general-default)# enable CASA-CMTS(load-bal-general-default)# no enable

Enable or disable the load balance function.

Specifying the technique for moving cable modems Only one technique may be specified to move cable modems:

CASA CMTS





2 initial-tech {broadcast-ranging> | direct | period-ranging | reinitialize-mac | unicast-ranging} Where:

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

reinitialize-mac Instructs D3.0 modems to reinitialize the MAC domain.

Example: CASA-CMTS(load-bal-general-default)#initial-tech broadcast-ranging

Enter the move cable modem technique.

Specifying the policy for load balancing execution To specify the policy to use for load balancing execution:




2 policy-id <number> Where:

<number> Specifies the load-balance policy ID in the range 0 to 4,294,967,295.

Example:

Specify the policy for load balancing.

CASA CMTS


CASA-CMTS(load-bal-general-default)# policy-id 2

Load balancing basic rules The DOCS-LOADBAL3-MIB defines the load balance basic rules.

Entering a basic rule configuration To enter a basic rule configuration:

Step Command (config) Purpose 1 load-balance basic-rule <number>

Where:

<number> Specifies the load-balance basic rule ID in the range 1 to 4,294,967,295.

Example: CASA-CMTS(config)# load-balance basic-rule 1

Enter basic rule configuration mode.

Enabling a basic rule To enable or disable this rule:


Where:

<number> Specifies the load-balance basic rule ID; valid values are 1 to 4,294,967,295.

Example: CASA-CMTS(config)# load-balance basic-rule 1


2 [no] enable Example: CASA-CMTS(load-balance basic-rule 1)# enable CASA-CMTS(load-balance basic-rule 1)# no enable

Enable or disable the basic rule.

Specifying a time period on a basic rule to disable a load balance function To specify a time period on a basic rule to a disable load balance function:


Where:


CASA CMTS


<number> Specifies the load-balance basic rule ID; valid values are 1 to 4,294,967,295.

Example: CASA-CMTS(config)# load-balance execution-rule 1 CASA-CMTS(load-bal-exe-rule 1)#

2 suspend-load-balance from <t-start> to <t-end> Where:

<t-start> Specifies the start time for disabling load balancing in the format HH:MM:SS.

<t-end> Specifies the end time for disabling load balancing in the format HH:MM:SS.

Example: Suspend load balancing from 12:00 p.m. to 3:00 p.m. using a 24-hour clock. CASA-CMTS(load-bal-exe-rule 1)#suspend-load-balance from 12:00:00 to 15:00:00

Specify the time period in which load balancing is suspended.

Load balance execution rules Up to 16 load balance execution rules are allowed in the CMTS configuration. Note that an execution rule is always enabled; there is no command to enable or disable it.

Step Command (config) Purpose 1 load-balance execution-rule <number>

Where:

<number> Specifies the execution rule ID in the range 1 to 16. Example: CASA-CMTS(config)# load-balance execution-rule 1

Enter load balance execution rule configuration mode.

CASA CMTS


Specifying a minimum time Interval between each load balance calculation To specify a minimum time interval between each load balance calculation:


Where:

<number> Specifies the execution rule ID in the range 1 to 16. Example: CASA-CMTS(config)# load-balance execution-rule 1 CASA-CMTS(load-bal-exe-rule 1)#


2 interval <number> Where:

<number> Specifies the minimum time interval in seconds in the range 10 to 3600.

Example: CASA-CMTS(load-bal-exe-rule 1)# interval 200

Specify minimum time interval.

Specifying a minimum time interval between upstream load balance calculations To specify a minimum time interval between each upstream load balance calculation, perform the following.

Note: If the upstream-interval is not configured, the interval value applies to both upstream and downstream load balancing. If the upstream-interval is configured, upstream-interval value applies to upstream load balancing; the interval value applies to downstream load balancing.


Where:



CASA CMTS


2 upstream-interval <number> Where:

<number> Specifies the minimum time interval in seconds. The valid range is 10 to 3600 seconds. The default setting is 10 seconds.

Example: CASA-CMTS(load-bal-exe-rule 1)# upstream-interval 30


Specifying the minimum time interval to move the same modem To specify a minimum time interval to move the same modem:


Where:



2 cable modem rebalance-interval <number> Where:

<number> Specifies the minimum rebalance-time interval in seconds; valid values are 60 to 3600. The default is 3600.

Example: CASA-CMTS(load-bal-exe-rule 1)# cable modem rebalance-interval 200


To specify a minimum time interval to move the same modem if previous load-balancing failed for the modem:


Where:



CASA CMTS


2 cable modem retry-interval first <first> second <second> Where:

<first> Specifies the first retry interval time in seconds in the range 60 to 86,400. The default is 86,400 seconds (1 day).

<second> Specifies the second retry interval time in seconds in the range 60 to 432,000. The default is 432,000 seconds (4 days).

Example: CASA-CMTS(load-bal-exe-rule 1)# cable modem retry-interval first 35000 second 87000

Specify the minimum time interval.

Specifying a method for load balance calculations A method can apply to dynamic, static or both types of load balancing. If method dynamic is not configured, the method will apply to both static and dynamic load balance; it is not necessary to specify the dynamic parameters. If method dynamic is configured, the method will only apply to static load balancing while method dynamic will apply to dynamic load balance. To disable static load balancing, set the threshold to 0. To specify the utilization method for load balance calculations:


Where:



2 method utilization [dynamic] Example: CASA-CMTS(load-bal-exe-rul 5)#method utilization

Configure the method of utilization.

To specify the modem for load balance calculation:


Where:

Enter load balance execution

CASA CMTS



rule configuration mode.

2 method modem [dynamic] Example: CASA-CMTS(load-bal-exe-rul 5)#method modem

Configure the method of modem.

Specifying a method for upstream load balance calculations To specify the utilization method for upstream load balance calculations:

Step Command (config) Purpose 1 load-balance execution-rule <num>

Where:


<number> Specifies the execution rule ID in the range 1 to 16.


2 upstream-method utilization [dynamic] Example: CASA-CMTS(load-bal-exe-rul 5)# upstream-method utilization

Configure the upstream method of utilization.

To specify the modem method for upstream load balance calculations:


Where:


<number> Specifies the execution rule ID in the range 1 to 16.


CASA CMTS


2 upstream-method modem [dynamic] Example: CASA-CMTS(load-bal-exe-rul 5)#method modem

Configure the upstream method of modem.

Specifying a utilization method for upstream load balance calculations To specify a method of utilization for upstream load balance calculations:


Where:


<num> Execution rule ID in the range 1 to 16.


2 upstream-threshold load <load_number> [enforce <enforce_number> | minimum <minimum_number> | dynamic minimum <dynamic_number>] Where:

<load_number> Sets the load difference between interfaces to start static load balance. This is the number of modems on the modem method or the utilization percentage on the utilization method. Valid values are 0 to 100. The default is 10.

enforce <enforce_number>

Sets the load difference between interfaces to start dynamic load balance. This is the number of modems on the modem method or the utilization percentage on the utilization method. Valid values are 0 to 100. The default is 10.

<minimum_number> Sets the minimum number of modems on the modem method or the minimum utilization percentage on the utilization method. For static load balance, values are 2 to 500. The default is 10.

dynamic minimum <dynamic_number>]

Sets the minimum number of modems for dynamic load balance. Valid values are 2 to 500. The default is 0.

Set the method of utilization.

CASA CMTS


Example: CASA-CMTS(config)# load-balance execution-rule 5

CASA-CMTS(load-bal-exe-rule 5)# upstream-threshold load350 enforce 50 minimum 50 dynamic minimum 50

To disable upstream load balancing, set the threshold and enforce values to 0.

Load balancing policies To enter a load balance policy:

Step Command (config) Purpose 1 load-balance policy <identifier>

Where:

Example: CASA-CMTS(config)# load-balance policy 5 CASA-CMTS(load-bal-policy 5)#

<identifier> Specifies the load-balance policy ID in the range 1 to 4,294,967,295.

Enter load balance policy mode.

Adding a basic rule Load balance policy can have multiple basic rules. To add or remove a basic rule in a policy:


Where:




2 [no] rule basic <identifier> Where:

<identifier> Specifies the load-balance basic rule ID in the range 1 to 4,294,967,295.

Add or remove a policy basic rule.

CASA CMTS


Example: CASA-CMTS(load-bal-policy 5)# rule basic 10

Adding an execution rule Load balance policies can have only one execution rule. To add, replace, or remove an execution rule:


Where:




2 [no] rule execution <identifier> Where:

Example: CASA-CMTS(load-bal-policy 5)# rule execution 10

<identifier> Specifies the load-balance execution rule ID in the range 1 to 16.

Add or remove a policy execution rule.

Restricted load balance groups Restricted Load Balance Group is very similar to the General Load Balance Group except the user needs to enter the upstream and downstream channel set.

Entering the load balance restricted group To enter load balance restricted group:

Step Command (config) Purpose 1 load-balance restricted-group <group-id>

Where:

Example:

<group-id> Specfies the restricted group ID in the range 1 to 255.

Enter load balance restricted group.

CASA CMTS


CASA-CMTS(config)# load-balance restricted-group 2 CASA-CMTS(load-bal-restrict 2)#

Specifying the MAC domain on a restricted group To specify the mac domain on a restricted group:

Step Command (config) Purpose 1 load-balance restricted-group <group-id>

Where:

Example: CASA-CMTS(config)# load-balance restricted-group 2 CASA-CMTS(load-bal-restrict-group-2)#

<group-id> Specifies the restricted group ID in the range 1 to 255.


2 docsis-mac <number> Where:

Example: CASA-CMTS(load-bal-restrict-2)# docsis-mac 1

<number> Specifies the MAC domain number in the range 1 to 32.

Specify the MAC domain.

Enabling load balancing on a restricted group To enable or disable the load balance function on a restricted group:


1 load-balance restricted-group <group-id> Where:

Example: CASA-CMTS(config)# load-balance restricted-group 2 CASA-CMTS(load-bal-restrict 2)#


Enter the load balance restricted group.

2 docsis-mac <number> Specify the MAC

CASA CMTS


Where:

Example: CASA-CMTS(load-bal-restrict 2)# docsis-mac 1 CASA-CMTS(load-bal-restrict 2)#


domain.

3 [no] enable Example: CASA-CMTS(load-bal-restrict 2)# enable

Enable or disable the load balance function.

Adding the service type ID to a restricted group To add service type ID to a restricted group:












4 service-type-id <string> Where:

Add the service type ID.

CASA CMTS


Example: CASA-CMTS(load-bal-restrict 2)# service-type-id “load balance” CASA-CMTS(load-bal-restrict 2)#

<string> Specifies the service type ID as a text string with up to 16 characters with no blank spaces. If blank spaces are included in the string, surround the string with quotation marks.

Displaying cable modem information by service-type-id To display cable modems using the service-type-id:


1 show cable modem service-type-id [<string>] Where:

Example: CASA-CMTS(config)#show cable modem service-type-id

<string> Specifies the service-type-id as a text string. If the string has embedded spaces, enclose the string within quotation marks.

Display cable modems by service-type-id.

Example: C10G-RC220#show cable modem service-type-id MAC Address IP Address US DS MAC Prim Service-

Type_ID(C/P)

Intf Intf Status Sid

0005.caa3.d5c4 10.220.1.137 11/0.0/0 2/0/7 init(o) 19 -/-

0017.9a60.5c30 10.220.1.146 11/0.0/0 2/0/6 online(pt) 3 -/-

0025.2e06.70ec 10.220.1.129 11/0.0/0 2/0/4* online(pt) 4 -/-

0026.2495.b89c 0.0.0.0 11/7.0/0 1/7/7 offline 0 -/-

0026.5e77.43b3 10.220.1.123 11/0.0/0 2/0/7* online(pt) 1 -/-

C10G-RC220#

Adding an upstream channel to a restricted group To add or remove an upstream channel associated with a restricted group:




CASA CMTS






<number> Specifies the MAC domain number in the range values are 1 to 32.


3 [no] upstream <module_slot_num>/<port_num>.<physical_channel_num>/ <logical_chan_num> Where:




<logical_chan_num> Specifies the logical channel number, either 0 or 1.

Example: CASA-CMTS(load-bal-restrict 2)# upstream 5/0.0/1 CASA-CMTS(load-bal-restrict 2)#

Add or remove an upstream channel on a restricted group.

Adding a downstream channel to a restricted group To add a downstream channel to a restricted group:

Step Command (config)

Purpose


Enter load balance restricted

CASA CMTS


Example: CASA-CMTS(config)# load-balance restricted-group group-id 2 CASA-CMTS(load-bal-restrict-group-2)#


group.


Example: CASA-CMTS(load-bal-restrict-group-2)# docsis-mac 1 CASA-CMTS(load-bal-restrict-mac-id-group-1)#

<number> Specifies the MAC domain number in the range values are 1 to 32.


3 [no] qam <module_slot_num>/<port_num>/<physical_channel_num> Where:

<module_slot_num> Specifies the system slot number where the QAM module is installed.

<port_num> Specifies the QAM port number.

<physical_channel_num> Specifies the QAM downstream channel number supported on the specific CMTS platform being managed.

Example: Add the downstream channel on the QAM in slot 1, port 1, and channel 0 to the load balance restricted group. CASA-CMTS(load-bal-restrict 2)# qam 1/1/0 CASA-CMTS(load-bal-restrict 2)#

Add or remove a downstream channel on a restricted group.

Exclusion lists Cable modems can be set not to move by putting them into an exclusion list.

Adding a CM to an exclusion list To add or remove a CM into an exclusion list:


CASA CMTS


1 load-balance exclusion list Example: CASA-CMTS(config)# load-balance exclusion list CASA-CMTS(load-bal-exclusion-list)#

Enter load balance exclusion list mode.

2 [no] mac addr <mac_address> mask <mask> [static | both] Where:

Example: Exclude all modems with MAC address 0014. CASA-CMTS(config)# load-balance exclusion list CASA-CMTS(load-bal-exclusion-list)# mac addr 0014.0000.0000 mask ffff.0000.0000

<mac_address> Specifies the modem MAC address in 48-bit hexadecimal format.

<mask> Specifies the MAC address mask in decimal format xxxx.xxxx.xxxx. Use the mask to apply the exclusion list to modems from a particular modem vendor.

static both

If neither “static” nor “both” is specified, modems are only excluded from dynamic load balancing. If “static” is specified, modems are only excluded from static load balancing. If “both” is specified, modems are excluded from both static and dynamic load balancing Note that modem types can also be excluded by using a mask.

Add or remove a CM into an exclusion list.

Restricted cable modems

Entering the restricted CM configuration To enter restricted CM configuration:

Step Command (config) Purpose 1 load-balance restricted-cm <identifier>

Where:

Example:

<identifier> Specifies the restricted modem ID in the range 1 to 4,294,967,295.

Enter the restricted CM configuration.

CASA CMTS


CASA-CMTS(config)# load-balance restricted-cm 1 CASA-CMTS(load-bal-restrict-cm 1)#

Entering the CM MAC address To enter CM MAC address:

Step Command (config) Purpose 1 load-balance restricted-cm <identifier>

Where:

Example: CASA-CMTS(config)# load-balance restricted-cm 1 CASA-CMTS(load-bal-restrict-cm 1)#



2 [no] mac addr <mac_address> [mask <mask>] Where:

Example: CASA-CMTS(load-bal-restrict-cm 1)mac addr 0011.e6bb.e3b1 #

<mac_address> Modem MAC address in 48-bit hex format.

<mask> Mask in 48-bit hex format. If omitted, the mask defaults to ffff.ffff.ffff.

[no] Removes the CM MAC address. This sets mac addr = 0 and mask = 0xffffffff.

Enter the cable modem MAC address.

Adding a service type ID To add a service type ID:

Step Command (config) Purpose 1 load-balance restricted-cm <identifer>

Where:




CASA CMTS


3 service-type-id <string>

Where:

Example: CASA-CMTS(load-bal-restrict-cm 1)# service-type-id “load balance” CASA-CMTS(load-bal-restrict-cm 1)#

<string> Specifies the service type ID as a text string with up to 16 characters with no blank spaces. If blank spaces are included in the string, surround the string with quotation marks.

Add the service type ID.

Adding a reference to a restricted load balance group To add or remove a reference to a restricted load balance group:

Step Command (config) Purpose 1 load-balance restricted-cm <identifer>

Where:



Enter restricted CM configuration.

2 [no] restricted-load-balance-group <id> Where:

Example: Add restricted group 3: CASA-CMTS(load-bal-restrict-cm 1)# restricted-load-balance-group 3 Remove reference to restricted group 3: CASA-CMTS(load-bal-restrict-cm 1)# no restricted-load-balance-group

<identifier> Specifies the restricted group ID in the range 1 to 4,294,967,295.

Add or remove a reference to a restricted load balance group.

CASA CMTS


CM frequency and channel relocation The CLI commands provide the capability for a user to move a cable modem to a different downstream frequency or upstream channel.

Changing upstream and downstream channels with the DCC method To change both upstream and downstream with the DCC method:

Step Command (config) Purpose 1 cable modem <mac_address> dcc change-frequency

<frequency_number> upstream <channel_number> initial-tech {reinitialize-mac | broadcast-ranging | unicast-ranging | period-ranging | direct} Where:

<mac-address> Specifies the modem MAC address in 48-bit hex format.

<frequency_number> Specifies the downstream channel frequency in MHz in the range 50000000 to 999000000.

<channel_number> Specifies the upstream channel ID number in the range 1 to 255.






Example: Move CM 0015.f2fe.c904 to new upstream and downstream channels. CASA-CMTS(config)# cable modem 0015.f2fe.c904 dcc change-frequency 593000000 upstream 200 initial-tech reinitialize-mac

Change both upstream and downstream channels using the DCC method.

CASA CMTS


Changing a downstream channel with the DCC method To change a downstream channel with the DCC method:


<frequency_number> initial-tech {reinitialize-mac | broadcast-ranging | unicast-ranging | period-ranging | direct} Where:








Example: Move CM 0015.f2fe.c904 to new downstream channel. CASA-CMTS(config)# cable modem 0015.f2fe.c904 dcc change-frequency 593000000 initial-tech period-ranging

Change downstream channel using the DCC method.

CASA CMTS


Changing an upstream channel with the DCC method To change an upstream using the DCC method:

Step Command (config) Purpose 1 cable modem <mac_address> dcc upstream <channel_number>

initial-tech {reinitialize-mac | broadcast-ranging | unicast-ranging | period-ranging | direct} Where:









Example: Move CM 0015.f2fe.c904 to new upstream and downstream channels. CASA-CMTS(config)# cable modem 0015.f2fe.c904 dcc upstream 200 initial-tech broadcast-ranging

Change upstream channels using the DCC method.

CASA CMTS


Changing the CM to another CMTS with the DCC method To move a CM to another CMTS by overriding the downstream channel frequency using the DCC method, perform the following command.

Note: Currently this function is for CMs without channel bonding only. Do not specify the upstream channel ID here.


<frequency> initial-tech reinitialize-mac Where:

Example: Move CM 0015.f2fe.c904 to another CMTS: CASA-CMTS(config)# cable modem 0015.f2fe.c904 dcc change-frequency 593 initial-tech reinitialize-mac

<mac_address> Modem MAC address in 48-bit hex format.

<frequency> Downstream channel frequency in MHz; valid values are 50000000 to 999000000.

Move the CM.

Setting the upstream channel frequency difference limit on the DCC when the initial technique is direct When this limit is set, if the CMTS needs to move a modem to a new upstream channel with a frequency difference greater than the set limit during dynamic load balancing, it will use the initial technique of broadcast-ranging (1) instead of direct (4). To set the difference limit from 1 MHz to 60MHz (if set to 0, then there is no limit):



Enter general default.

.

CASA CMTS


2 initial-tech direct frequency-limit <number> Where:

Example: CASA-CMTS(load-bal-general-default)# initial-tech direct frequency-limit 40

<number> Specfies the difference limit range in 0 to 60 MHz, where 0 specifies no limit.

Set the difference limit.

Changing an upstream channel with the UCC method To change an upstream channel with the UCC method:

Step Command (config) Purpose 1 cable modem <mac_address> ucc upstream

<channel_number> Where:

Example: CASA-CMTS(load-bal-general-default)# cable modem 0001.0002.0003 ucc upstream 100

<mac_address> Specifies the modem MAC address in 48-bit hex format.


Change upstream via the UCC method.

Changing a bonded CM’s upstream and downstream with the DBC method To change a bonded CM’s upstream and downstream channels via the DBC method:


1 cable modem <mac_address> dbc [rcp-id <rcp_id> rcc-id <rcc_id>] upstream-list <string> initial-tech {reinitialize-mac | broadcast-ranging | unicast-ranging | period-ranging | direct} Where:


<rcp_id> Specifies receive channel profile (RCP) ID in the format xx:xx:xx:xx:xx.

<rcc_id> Specifies the receive channel

Change bonded CM upstream and downstream channels with the DBC method.

CASA CMTS


configuration (RCC) template ID in the range 1 to 255.

<string> Specifies the name of the upstream list as a text string.






Example: C3000-230(config)#cable modem 0001.0002.0003 dbc rcp-id 01:FE:EA:00:04 rcc-id 200 upstream-list 1 initial-tech period-ranging

Changing a bonded CM’s downstream channel with the DBC method To change a bonded CM’s downstream channel with the DBC method:


1 cable modem <mac_address> dbc downstream-list <string> initial-tech {reinitialize-mac | broadcast-ranging | unicast-ranging | period-ranging | direct} Where:


<string> Specifies the name of the downstream list as a text string.





Change bonded CM downstream channels with the DBC method.

CASA CMTS



Example: C3000-230(config)#cable modem 0001.0002.0003 dbc downstream-list 1 initial-tech period-ranging

Changing a bonded CM’s upstream channel via the DBC method To change a bonded cable modem’s upstream channel with the DBC method:


1 cable modem <mac_address> dbc upstream-list <string> initial-tech {reinitialize-mac | broadcast-ranging | unicast-ranging | period-ranging | direct} Where:


<string> Specifies the name of the upstream list as a text string.






Example: C3000-230(config)#cable modem 0001.0002.0003 dbc upstream-list 1 initial-tech period-ranging

Change bonded CM upstream channels with the DBC method.

Sending DBC request messages to cable modems The cable partial-service dbc command instructs the CMTS to send DBC request messages to cable modems when these modems report partial service mode while attempting to acquire affected channels. This functionality is disabled by default. Use this command only with special case modems.

CASA CMTS


Under normal conditions, when the CMTS receives ranging request messages on the unusable upstream channels, the channels are removed from the unusable channel list and the affected modems are no longer considered in partial service mode.


1 [no] cable partial-service dbc Example: CASA(config)#cable partial-service dbc

Enables the CMTS to send DBC request messages to cable modems that are in partial service mode.

Configuring CableLabs Engineering Change Notice 770 The [no] cable ecn 770 command enables the CableLabs Engineering Change Notice 770 to help keep modems from getting into the upstream partial service state when there are a large number of modems attempting to register with the CMTS while the CMTS is assigning and bonding channels to D3.0 modems. This feature is disabled by default. Some cable modems end up in upstream partial service mode if there are collisions followed by no additional attempts to range on the assigned upstream channels. Configuring unicast ranging as the initial technique instead of the default broadcast ranging in the DOCSIS MAC interface using the initial-tech unicast-ranging command will avoid any collisions and help prevent modems from getting into upstream partial service mode. By enabling ECN 770 with the cable ecn 770 command, UCD encodings will be included within the transmit channel configuration (TCC) in the CMTS' registration response to the prevent the partial service problem. However, modems that are already in partial service mode will need to be reset. A complete copy of CableLabs ECN 770 is available for download from the Casa Technical Support FTP site, or directly from CableLabs.


1 [no] cable ecn 770 Example: CASA(config)#cable ecn 770

Enables CableLabs ECN 770. Use the no form of the command to disable ECN 770.

CASA CMTS


Displaying load balancing information To show load balancing statistics:


1 show load-balance (dynamic|static) [begin <b_date> < b_time>] [end <e_date> <e_time>] [(begin | count | count-only | exclude | include) <string>] Where:

Example: CASA-CMTS# show load-balance dynamic See below.

<date> load-balance beginning date in form YYY-MM-DD.

<b_time> load-balance beginning time in form HH:MM:SS.

<e_date> load-balance ending date in form YYY-MM-DD.

<e_time> load-balance ending time in form HH:MM:SS.

begin Begin with the line that matches

count count lines output

count-only Count lines output while suppressing output.

exclude Exclude lines that match

Include Include lines that match.

<string> String to match.

Displays load balancing statistics.

show load-balance dynamic Mac address Mac-id upstream-channel downstream-channel initial_tech cmd status type time 0015.f2fe.c643 0 3 -- 1 dcc WaitToSendMsg GLB 2008-04-06 23:25:17 0015.f2fe.c643 0 2 -- 1 dcc WaitToSendMsg RGLB 2008-04-06 23:28:41 ----------------------------------------------------------------------- total: 2; success:0; other:2 Where type is: BAL -- Balancing done by the system. MLT -- DCC by limit replication multicast. CLI -- Load balancing done manually from the CLI. MIB -- Load balancing done manually from SNMP. CSM -- DCC done by CSM per cable modem. DSA -- DCC done by voice.

CASA CMTS


RSLB -- DCC moved a cable modem into a restricted load-balance group. RGLB -- General load balancing done until registration. SG -- Channel is not in the channel set of the configured service group.

Clearing all load-balance logs To clear all load-balance logs:


1 clear load-balance log Example: CASA-CMTS# clear load-balance log

Clear the load balance logs.

.

Command ordering Because many of the load balancing commands depend on the existence of other objects, the ordering of these commands is critical. For example, load-balance general-group depends on the existence of mac domain, service group, and policy. And policy depends on basic rule and execution rule.

In show run, the command described in this document should come after all the interface configuration commands and follow the order outlined below: service-group …. interface docsis-mac 1 …. interface upstream x/y …. load-balance enable …. load-balance basic-rule …. load-balance execution-rule …. load-balance policy x …. load-balance general-group default-settings …. load-balance general-group mac-domain x service-group y …. load-balance restricted-group group-id y …. load-balance restricted-cm x …. bonding-group downstream mac-domain x group-id y …. bonding-group upstream mac-domain x group-id y

CASA CMTS


Command default values

Default values for general load-balance group default enable initial-tech-none no policy-id

Default values for general/restricted load-balance group The default values for a newly created General Load-Balance Group shall be taken directly from the General Load-Balance Group Default.

Default values for load-balance basic rule

- no enable

Default values for load-balance execution rule interval 10 method modem

threshold load 10 enforce 0 minimum 10

Sample configuration CASA-CMTS# show run ! ! CASA-CMTS system running configuration ! hostname "sada" ! password casa ! ! interface eth 0 ip address 192.168.2.240 255.255.255.0 ! interface ip-bundle 1 ip address 10.248.1.1 255.255.255.0 cable helper-address 192.168.3.8 ! ! interface gige 0 ip address 192.168.3.48 255.255.255.0 ipv6 address 2001:50:1::3/64 no shutdown ! interface gige 1 shutdown ! interface gige 2

CASA CMTS


shutdown ! interface gige 3 shutdown ! ! cable sec tftp-options none no cable sec config-file-learning cable sec cert-revocation-list url cable sec ocsp protocol-url ! ! interface qam 0/0 interleave 128x1 power 540 channel 0 frequency 669000000 no channel 0 shutdown channel 1 frequency 675000000 no channel 1 shutdown channel 2 frequency 681000000 no channel 2 shutdown channel 3 frequency 687000000 no channel 3 shutdown no shutdown interface qam 0/1 interleave 128x1 power 540 channel 0 frequency 549000000 no channel 0 shutdown channel 1 frequency 555000000 no channel 1 shutdown channel 2 frequency 561000000 no channel 2 shutdown channel 3 frequency 567000000 no channel 3 shutdown no shutdown interface qam 0/2 interleave 128x1 channel 0 frequency 549000000 channel 0 shutdown channel 1 frequency 555000000 channel 1 shutdown channel 2 frequency 561000000 channel 2 shutdown channel 3 frequency 567000000 channel 3 shutdown shutdown interface qam 0/3 interleave 128x1 power 450 channel 0 frequency 549000000 no channel 0 shutdown channel 1 frequency 555000000 no channel 1 shutdown

CASA CMTS


channel 2 frequency 561000000 no channel 2 shutdown channel 3 frequency 567000000 no channel 3 shutdown shutdown ! igmp client version 2 ! service group FN_A qam 0/0/0 qam 0/0/1 qam 0/0/2 qam 0/0/3 upstream 1/0 upstream 1/1 service group FN_B qam 0/1/0 qam 0/1/1 qam 0/1/2 qam 0/1/3 upstream 1/2 upstream 1/3 upstream map size 5 interface docsis-mac 1 no shutdown no dhcp-authorization no early-authentication-encryption no multicast-dsid-forward no tftp-proxy 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 ! ! channel-utilization-interval 0 interface upstream 1/0 frequency 8000000 channel-width 3200000 logical-channel 0 profile 2 logical-channel 0 minislot 2 logical-channel 0 pre-equalization

CASA CMTS


no logical-channel 0 shutdown logical-channel 1 profile 5 logical-channel 1 frame 16 8 128 no logical-channel 1 shutdown no shutdown interface upstream 1/1 frequency 12000000 channel-width 3200000 logical-channel 0 profile 2 logical-channel 0 minislot 2 no logical-channel 0 shutdown logical-channel 1 profile 5 logical-channel 1 frame 16 8 128 no logical-channel 1 shutdown no shutdown interface upstream 1/2 frequency 16000000 channel-width 3200000 logical-channel 0 profile 2 logical-channel 0 minislot 2 no logical-channel 0 shutdown logical-channel 1 profile 5 logical-channel 1 frame 16 8 128 no logical-channel 1 shutdown no shutdown interface upstream 1/3 frequency 20000000 channel-width 3200000 logical-channel 0 profile 2 logical-channel 0 minislot 2 no logical-channel 0 shutdown logical-channel 1 profile 5 logical-channel 1 frame 16 8 128 no logical-channel 1 shutdown no shutdown interface upstream 1/4 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 1/5 frequency 28000000 channel-width 3200000 logical-channel 0 profile 2 logical-channel 0 minislot 2 no logical-channel 0 shutdown

CASA CMTS


logical-channel 1 profile 2 logical-channel 1 minislot 2 logical-channel 1 shutdown no shutdown interface upstream 1/6 frequency 32000000 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 1/7 frequency 36000000 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 ! ! ! load balance commands ! load-balance enable load-balance basic-rule 1 enable suspend-load-balance from 13:00:00 to 20:00:00 load-balance basic-rule 2 enable suspend-load-balance from 13:00:00 to 23:00:00 load-balance basic-rule 3 enable suspend-load-balance from 20:00:00 to 01:00:00 load-balance execution-rule 1 enable method modem threshold load 10 enforce 30 minimum 35 load-balance policy 1 rule basic 1 rule basic 3 rule execution 1

CASA CMTS


load-balance general-group default-settings initial-tech unicast-ranging load-balance general-group mac-domain 1 service-group FN_A enable initial-tech direct policy-id 1 load-balance general-group mac-domain 1 service-group FN_B no enable initial-tech direct policy-id 1 load-balance restricted-group group-id 10 enable docsis-mac 1 initial-tech broadcast-ranging policy-id 1 service-type-id restict1 qam 0/1/0 qam 0/1/1 qam 0/1/2 upstream 1/2 upstream 1/3 load-balance restricted-cm 1 mac addr 0018.0123.5678 service-type-id restict1 restricted-load-balance-group 10 load-balance restricted-cm 2 mac addr 0019.0000.0000 mask ffff.0000.0000 service-type-id restict1 restricted-load-balance-group 10 bonding-group downstream mac-domain 1 group-id 1 prov-attr-mask 0x00ff reseq wait-time 1000 reseq warn-thrshld 1200 qam 0/0/0 qam 0/0/1 qam 0/0/2 qam 0/0/3 bonding-group upstream mac-domain 1 group-id 1 prov-attr-mask 0x00ff upstream 1/0/0 upstream 1/1/0 ! ! end of config !

CASA CMTS


Configuring channel bonding operations

In order for the Casa CMTS to operate in channel bonding mode, the docsis-mac interface must be configured, as well as a service group with at least one downstream channel and one upstream channel.

For cable modems that support channel bonding operation, the Casa CMTS automatically creates channel bonding groups with channels that belong to the same service group, and the same docsis-mac interface.

The Casa CMTS supports channel bonding in the same line card module. With Release 6.1.3, the maximum number of downstream channels per QAM module is 32, and the maximum number of upstream channels per upstream DCU module is 32.

Service group configuration

A service group represents the RF topology with at least one upstream channel and one downstream channel to allow channel-bonding operations. A downstream channel and an upstream channel can be associated with multiple service groups. To configure a service group:

Step Command (config) Purpose 1 service group <grp_id>

Where:

<grp_id> Service group ID. Example: CASA-CMTS(config)# service group 1 CASA-CMTS(conf-svc-grp 1)#

Enter the service group configuration mode.

2 [no] qam <slot/port/channel> Where:

<slot/port/channel> Slot, port and channel numbers. Example: CASA-CMTS(conf-svc-grp 1)# qam 0/0/0 Remove: CASA-CMTS(conf-svc-grp 1)#no qam 0/0/0

Add or remove a downstream channel.

CASA CMTS


3 [no] upstream <slot/port.phy_channel> Where:

<slot/port.phy_channel> Slot, port and logical channel numbers.

Example: CASA-CMTS(conf-svc-grp 1)# upstream ? X/Y.C X-slot number, Y-port number, C-physical channel index 0 or 1

CASA-CMTS(conf-svc-grp 1)# upstream 3/0.1 CASA-CMTS(conf-svc-grp 1)# show service group

CASA-CMTS(conf-svc-grp 1)# no upstream 3/0.1

Add or remove an upstream channel.

DOCSIS-MAC interface configuration

For normal DOCSIS operation, a “docsis-mac” interface must be configured. The “docsis-mac” interface creates an association between downstream channels and upstream channels. A downstream channel or an upstream logic-channel can only be associated with one “docsis-mac” interface. The channel id must be unique in a “docsis-mac” interface.

To configure a “docsis-mac” interface:

Step Command (config) Purpose 1 interface docsis-mac <dsm_id>

Where:

<grp_id> DOCSIS MAC ID. Example: CASA-CMTS(config)# interface docsis-mac 1 CASA-CMTS(conf-if-mac 1)#

Enter the docsis-mac configuration mode.

2 [no] downstream <chan_id> interface qam <slot/port/channel> Where:

<chan_id> Channel ID.

<slot/port/channel> Slot, port and channel numbers. Example: CASA-CMTS(conf-if-mac 1)#downstream 1 interface qam 0/0/0

Add or remove a downstream channel.

CASA CMTS


3 [no] upstream <chan_id> interface upstream <slot/port.channel/logical_channel> Where:

<chan_id> Channel ID.

<slot/port/channel> Slot, port and channel numbers.

Examples: CASA-CMTS(conf-if-mac 1)# upstream 1 interface upstream ? X/Y.C/Z X - slot, Y - port (0-7), C - upstream physical channel(0-1), Z - upstream logical channel(0-1 CASA-CMTS(conf-if-mac 1)# upstream 1 interface upstream 4/1.0/0 CASA-CMTS(conf-if-mac 1)# show interface docsis-mac 1

CASA-CMTS(conf-if-mac 1)#no upstream 1 CASA-CMTS(conf-if-mac 1)#

Add or remove an upstream channel.

Channel bonding example

In the following example, one service group is formed with 16 downstream and 8 upstream channels from the same downstream/upstream modules, with two mac domain interfaces created within the service group. Each domain contains 8 downstream and 4 upstream channels. The channel bonding then occurs inside each of the domains, or 8 downstream and 4 upstream channels. CASA-CMTS(config)# service group 1 CASA-CMTS(config-svc-grp 1)# qam 0/0/0 CASA-CMTS(config-svc-grp 1)# qam 0/0/1 CASA-CMTS(config-svc-grp 1)# qam 0/0/2 CASA-CMTS(config-svc-grp 1)# qam 0/0/3 CASA-CMTS(config-svc-grp 1)# qam 0/1/0 CASA-CMTS(config-svc-grp 1)# qam 0/1/1 CASA-CMTS(config-svc-grp 1)# qam 0/1/2 CASA-CMTS(config-svc-grp 1)# qam 0/1/3 CASA-CMTS(config-svc-grp 1)# qam 0/2/0 CASA-CMTS(config-svc-grp 1)# qam 0/2/1 CASA-CMTS(config-svc-grp 1)# qam 0/2/2 CASA-CMTS(config-svc-grp 1)# qam 0/2/3 CASA-CMTS(config-svc-grp 1)# qam 0/3/0 CASA-CMTS(config-svc-grp 1)# qam 0/3/1 CASA-CMTS(config-svc-grp 1)# qam 0/3/2 CASA-CMTS(config-svc-grp 1)# qam 0/3/3 CASA-CMTS(config-svc-grp 1)# upstream 1/0 CASA-CMTS(config-svc-grp 1)# upstream 1/1

CASA CMTS


CASA-CMTS(config-svc-grp 1)# upstream 1/2 CASA-CMTS(config-svc-grp 1)# upstream 1/3 CASA-CMTS(config-svc-grp 1)# upstream 1/4 CASA-CMTS(config-svc-grp 1)# upstream 1/5 CASA-CMTS(config-svc-grp 1)# upstream 1/6 CASA-CMTS(config-svc-grp 1)# upstream 1/7 CASA-CMTS(config-svc-grp 1)# end CASA-CMTS(config)# interface docsis-mac 1 CASA-CMTS(config-if-mac 1)# no shutdown CASA-CMTS(config-if-mac 1)# no dhcp-authorization CASA-CMTS(config-if-mac 1)# no early-authentication-encryption CASA-CMTS(config-if-mac 1)# no tftp-proxy CASA-CMTS(config-if-mac 1)# ip address 10.15.131.1 255.255.255.0 CASA-CMTS(config-if-mac 1)# cable helper-address 192.168.3.6 CASA-CMTS(config-if-mac 1)# downstream 1 interface qam 0/0/0 CASA-CMTS(config-if-mac 1)# downstream 2 interface qam 0/0/1 CASA-CMTS(config-if-mac 1)# downstream 3 interface qam 0/0/2 CASA-CMTS(config-if-mac 1)# downstream 4 interface qam 0/0/3 CASA-CMTS(config-if-mac 1)# downstream 5 interface qam 0/1/0 CASA-CMTS(config-if-mac 1)# downstream 6 interface qam 0/1/1 CASA-CMTS(config-if-mac 1)# downstream 7 interface qam 0/1/2 CASA-CMTS(config-if-mac 1)# downstream 8 interface qam 0/1/3 CASA-CMTS(config-if-mac 1)# upstream 1 interface upstream 1/0/0 CASA-CMTS(config-if-mac 1)# upstream 2 interface upstream 1/1/0 CASA-CMTS(config-if-mac 1)# upstream 3 interface upstream 1/2/0 CASA-CMTS(config-if-mac 1)# upstream 4 interface upstream 1/3/0 CASA-CMTS(config-if-mac 1)# end CASA-CMTS(config)# interface docsis-mac 2 CASA-CMTS(config-if-mac 2)# no shutdown CASA-CMTS(config-if-mac 2)# no dhcp-authorization CASA-CMTS(config-if-mac 2)# no early-authentication-encryption CASA-CMTS(config-if-mac 2)# no tftp-proxy CASA-CMTS(config-if-mac 2)# ip address 10.15.131.2 255.255.255.0 CASA-CMTS(config-if-mac 2)# cable helper-address 192.168.3.6 CASA-CMTS(config-if-mac 2)# downstream 1 interface qam 0/2/0 CASA-CMTS(config-if-mac 2)# downstream 2 interface qam 0/2/1 CASA-CMTS(config-if-mac 2)# downstream 3 interface qam 0/2/2 CASA-CMTS(config-if-mac 2)# downstream 4 interface qam 0/2/3 CASA-CMTS(config-if-mac 2)# downstream 5 interface qam 0/3/0 CASA-CMTS(config-if-mac 2)# downstream 6 interface qam 0/3/1 CASA-CMTS(config-if-mac 2)# downstream 7 interface qam 0/3/2 CASA-CMTS(config-if-mac 2)# downstream 8 interface qam 0/3/3 CASA-CMTS(config-if-mac 2)# upstream 1 interface upstream 1/4/0 CASA-CMTS(config-if-mac 2)# upstream 2 interface upstream 1/5/0 CASA-CMTS(config-if-mac 2)# upstream 3 interface upstream 1/6/0 CASA-CMTS(config-if-mac 2)# upstream 4 interface upstream 1/7/0 CASA-CMTS(config-if-mac 2)# end CASA-CMTS(config)#

Creating static CM bonding groups

The bonding group commands configure the static channel bonding combination that is available in the MAC domain for cable modems. Casa Systems does not recommend the use of static bonding.

CASA CMTS


Adding a static downstream CM bonding group To add or delete a static downstream CM bonding group:

Step Command (config) Purpose 1 [no] bonding-group downstream mac-domain <dmn_id>

group-id <grp_id> Where:

<dmn_id> MAC domain ID in the range 1 to 32.

<grp_id> Bonding group ID in the range 1 to 65,535. Example: CASA-CMTS(config)# bonding-group downstream mac-domain 7 group-id 1 CASA-CMTS(bond-ds-mac-7-group-1)#

Add or delete a static downstream CM bonding group.

Adding a static upstream CM bonding group To add or delete a static upstream CM bonding group:

Step Command (config) Purpose 1 [no] bonding-group upstream mac-domain <dmn_id> group-

id <grp_id> Where:


<grp_id> Bonding group ID in the range 1 to 65,535. Example: CASA-CMTS(config)# bonding-group upstream mac-domain 7 group-id 1 CASA-CMTS(bond-us-mac-7-group-1)#

Add or delete a static upstream CM bonding group.

CASA CMTS


Setting the provisioned attribute mask in an upstream/downstream bonding group

To set the provisioned attribute mask in an upstream bonding group:


id <grp_id> Where:


<grp_id> Bonding group ID in the range 1 to 65,535. Example: CASA-CMTS(config)# bonding-group upstream mac-domain 7 group-id 1 CASA-CMTS(bond-us-mac-7-group-1)#


2 prov-attr-mask <mask> Where:

<mask> Provisioned attribute mask in hex format 0x0 to 0xffffffff.

Set the provisioned attribute mask.

To set the provisioned attribute mask in a downstream bonding group:




<grp_id> Bonding group ID in the range 1 to 65535. Example: CASA-CMTS(config)# bonding-group downstream mac-domain 7 group-id 1 CASA-CMTS(bond-ds-mac-7-group-1)#


2 prov-attr-mask <mask> Where:

<mask> Provisioned attribute mask in hex format 0x0 to 0xffffffff.

Set the provisioned attribute mask.

CASA CMTS


Adding an upstream channel to a bonding group To add or remove the upstream channel to a bonding group:


id <grp_id> Where:


<grp_id> Bonding group ID in the range 1 to 65535. Example: CASA-CMTS(config)# bonding-group upstream mac-domain 7 group-id 1 CASA-CMTS(bond-us-mac-7-group-1)#


2 [no] upstream <x/y.z> Where:

<x/y.z> Upstream channel in form of slot/port/logic-channel.

Add or remove the upstream channel.

Adding a downstream channel to a bonding group To add or remove a downstream channel to a bonding group:






2 [no] qam <x/y/z> Where:

<x/y/z> Downstream channel in form of slot/port/channel.

Add or remove the downstream channel.

CASA CMTS


Setting the DSID re-sequencing wait time in a downstream bonding group

To set the DSID re-sequencing wait time:


1 [no] bonding-group downstream mac-domain <dmn_id> group-id <grp_id> Where:




2 reseq wait-time <value> Where:

<value> Re-sequencing waiting time value; 0 to 255.

Set the DSID re-sequencing wait time.

Setting the DSID re-sequencing warning threshold in a downstream bonding group

To set the DSID warning threshold:






2 reseq warn-threshold <level> Where:

<level> Re-sequencing threshold level; 0 to 255.

Set the DSID warning threshold.

CASA CMTS


QoS support

The C10200 and C3200 provide Quality of Service (QoS) through fine grain, per-flow queuing in the DQM and DCU modules, and class-based strict priority scheduling in the switch fabric and Gigabit interfaces.

QoS support in DQM modules

The DQM module provides QoS support through a two-level hierarchical scheduler. The top level is priority based, and the second level is a fair scheduler based on round robin. Each packet destined for a downstream interface is assigned a service flow through classification by the DOCSIS forwarding engine. The packet scheduler in the DQM module supports minimum guaranteed rate, as well as maximum transmitted rate. Packets are serviced in the order of priority specified by the service flow. Service flow that is within minimum guaranteed rate is served first. Within the same priority, round robin is used to schedule between different service flows. If the service flow has minimum guaranteed rate, and the current rate is within the specified rate, the packet is queued in the guaranteed class, which has the highest priority. The packet is subsequently rate limited through a token bucket to conform to the maximum transmitted rate specified for the service flow. Packets that exceed the maximum transmitted rate are rate-shaped by deferring their transmission. Packets are only dropped if the buffer utilization is high and the buffer usage by the service flow is above the drop threshold.

The packet scheduler is driven by availability of transmission opportunities on the downstream channel. The scheduler can provide millisecond level latency guarantees for high priority traffic through the use of shallow transmit queues. Every time a channel transmit queue becomes available, the scheduler services the service flows in the order of priority until the transmit queue is full or all eligible packets are serviced. For downstream channel bonding operation, the service flow is serviced by each of the channels in the bonding channel set in parallel.

QoS support in DCU modules

In the DCU module, the upstream scheduler handles modem transmission opportunities. In addition to providing minimum guaranteed rate and rate limiting support, it also provides jitter guarantees for jitter-sensitive services, such as unsolicited grant service (UGS). The hierarchical upstream scheduler serves upstream service flows based on priority. Jitter-sensitive service flows are serviced first, followed by service flows that are within its guaranteed rate. Best effort service flows are then serviced in the order of priority. Within each priority, the service flows are serviced by a round robin scheduler. For best effort services, the minimum guaranteed rate is checked first. If the transmission rate of the service flow is within its specified guaranteed rate, the request is placed in the guaranteed

CASA CMTS


queue, which is serviced before other best effort queues. Token bucket is used to rate limit the service flow within its configured maximum transmission rate and maximum burst size. Requests that exceed the maximum transmission rate are deferred. Requests that conform to the maximum transmission rate are placed into the queue determined by the priority of the service flow. Jitter-sensitive service flows are scheduled by the real-time scheduler. To provide jitter guarantees, the transmission opportunities are pre-allocated when the service flow is admitted to prevent overlap. At MAP generation time, the real time scheduler aggregates jitter-sensitive grants into clusters. The best effort grants are then placed into the gaps between the real time grant clusters. If the gap is not big enough, the cluster is allowed to move to increase the gap, as long as jitter guarantees can be met for the real time grants in the cluster. If the gap is still not enough to place the best effort grant, the best effort grant is then fragmented. The scheduler keeps track of the remainder of the fragments and continues to serve the fragments until the request is fulfilled. For service flows that are serviced by upstream channel bonding, the service flow is inserted into multiple queues, one for each of the upstream channels in the bonding channel set. The service flow is serviced by each of the upstream channels until all the outstanding bytes requested are served.

QoS support in switch fabric and Gigabit Ethernet interfaces

The switch fabric connects to the RF modules and Gigabit Ethernet interfaces. Each of the fabric ports supports eight classed-based queues. The scheduler in the switch fabric is straight priority.

For packets entering the switch fabric from the DCU module, the priority is determined by the priority value in the upstream service flow. For packets entering the switch fabric from Gigabit Ethernet interfaces, the priority is from the 802.1p field if the packet is VLAN-tagged. For untagged packets, the DSCP value in the IP header is used to determine the priority. The filtering engine can be used to overwrite the DSCP value using access list. The priority value can also be modified based on access lists. To prevent head-of-line blocking, the switch fabric keeps track of the outstanding buffer count and packet count for each of the ingress ports and each of the classes. When an egress port on the switch fabric becomes congested, a packet is discarded at ingress if the outstanding buffer count or packet count from the ingress port exceeds the discard threshold for the class it belongs to.

Configuring QoS

The Casa CMTS supports quality of services (QoS) as defined by the DOCSIS 1.0, 1.1 specifications. Service classes can be configured through the command-line interface to support the QoS profile number, traffic priority, maximum upstream bandwidth, guaranteed upstream bandwidth, maximum downstream bandwidth, maximum transmit burst length, baseline privacy enable/disable, and type of service (ToS) overwrite byte. This section covers commands for the following operations:

CASA CMTS


x Configuring service classes (DOCSIS 1.1)

x Showing the service class

Configuring the service class (DOCSIS 1.1)

To set parameters for DOCSIS 1.1 cable service class, use the cable service class command in global configuration mode. To delete a service class or to remove a configuration, use the no form of the command.

Step Command (config) Purpose 1 [no] cable service-class class-index

Where:

class-index Specifies the class ID for the class to be modified. Valid range is 1 to 255. Defaults: Values that are not specified are set to their DOCSIS 1.1 defaults, if applicable to the service-class schedule type.

Example: CASA-CMTS(config)# cable service-class 100

Set or delete parameters for DOCSIS 1.1 cable service class.

Showing the service class

To display the parameters for cable service class, use the show cable service class command in privileged mode.

Step Command Purpose 1 show cable service-class [sclass-index] [verbose]

Where:

sclass-index Identifies the index for a service class that has already been defined (1 to 255).

verbose Displays all of the defined attributes for the service class.

Examples: Show the standard and verbose formats of the show cable service class command: CASA-CMTS# show cable service-class Index Name Dir Sched Prio

Display the parameters for cable service class.

CASA CMTS


MaxSusRate MaxBurst MinRsvRate 1 UP_UGS US/DS UGS 0 0 1522 0 2 UP_UGSAD US/DS UGS_AD 0 0 1522 0 3 UP_RTPS US/DS RTPS 0 128000 2000 64000 4 UP_BE US/DS BE 5 128000 2000 0 5 DOWN_BE US/DS BE 5 1000000 3000 0 CASA-CMTS# 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 30 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}

QoS class and policy (C3200, C10200, C10G only)

To specify the QoS parameters, define a class map and assign it to a QoS policy. Then apply the policy to a GigE interface, a trunk interface, a VLAN, and IP bundle, or a MAC domain. To define a class map for QoS:

CASA CMTS


Step Command (config) Purpose 1 [no] class-map <string>

Where:

<string> Class map name.

Define a class map.

Only 'permit' rules are used for policy/class. A total of 128 ACL rules are supported for policy service (set DSCP). ACL rules in the access-group take priority if a packet matches in both the ACL and policy (for DSCP rewrite). To assign an access control list to the class map:

Step Command (config) Purpose 1 [no] match access-group <acl_name>

Where:

<acl_name> Access Control List name.

Assign an access control list.

To define a class action (DSCP overwrite for matched packets):

Step Command (config) Purpose 1 [no] set-dscp <0:63>

Define a class action.

To define a QoS policy (up to eight maps are supported):

Step Command (config) Purpose 1 [no] policy-map <policy-name>

Where:

<policy-name> Policy name.

Define a QoS policy.

To define classes within a policy:

Step Command (config) Purpose 1 [no] class <class-name>

Where:

<class-name> Class name. Up to 16 classes are supported.

Define a class within a policy.

To show information about the QoS class and policy:

Step Command (config) Purpose 1 show class-map <name>

show policy-map <name> Display QoS class and policy

CASA CMTS


Where:

<name> The class or policy name

map information.

To apply a policy to a GigE interface:


1 interface gige <id> Where:

<id> GigE interface ID. Example: CASA-CMTS(config)# interface gige 5


2 service-policy <policy-name> Where:

<policy-name> Policy name. Example: CASA-CMTS(conf-if-gige 5)#service-policy policy1 CASA-CMTS(conf-if-gige 5)#

Specify the service policy.

To apply a policy to a MAC domain interface:


1 interface docsis-mac <id> Where:

<id> The docsis mac ID. Example: CASA-CMTS(config)# interface docsis-mac 1 CASA-CMTS(conf-if-mac 1)#

Enter the interface.

2 service-policy <policy-name> Where:

<policy-name> The policy name. Example: CASA-CMTS(conf-if-mac 1)# service-policy policy1 CASA-CMTS(conf-if-mac 1)#

Apply the policy.

CASA CMTS


To apply a policy to a VLAN interface:


1 interface vlan <id> Where:

<id> VLAN ID.

Enter VLAN interface mode.

2 service-policy <policy_name> Where:

<policy_name> The policy name. Example: CASA-CMTS(conf-if-vlan 1)#service-policy policy1 CASA-CMTS(conf-if-vlan 1)#

Apply the policy.

Configuring SNMP (Enhanced for Rel. 5.4 and later)

Casa CMTS supports SNMP protocol in both CLI and MIB operations. This section covers the CLI commands for the following operations: x Configuring the SNMP engineId

x Enabling SNMP traps

x Setting the SNMP traphost

x Setting the SNMP trap source IP address

x Enabling SNMP Informs

x Setting the SNMP community

x Configuring the access table

x Configuring the community table

x Configuring the notification table

x Configuring the securityToGroup table

x Configuring the TargetAddress table

x Configuring the TargetParameter table

x Configuring the ViewFreeFamily table

x Configuring the user table

x Displaying the SNMP configuration and statistics

The command should be run under configuration mode. The configurations are persistent and a copy running-config to startup-config is not required.

CASA CMTS


Configuring the SNMP engineID

The SNMP engineID is an administrative identifier that is required for SNMP V3, as specified in RFC3411, An Architecture for Describing Simple Network Management Protocol (SNMP) Management Frameworks. SNMP V3 authentication and encryption keys are generated using the engineID and associated passwords. The engineID is expressed as a hexadecimal string (24 characters) in the SNMP configuration. After configuring or changing the SNMP engineID, you will need to reconfigure any SNMP V3 users, as the keys will based on the prior engineID setting.

Step Command (config) Purpose 1 [no] snmp engineid <hexadecimal-string>

Where:

<hexadecimal-string>> Specifies the 24-character SNMP engine identifier.

Example: CASA-CMTS(config)# snmp engineid 112233445566778899001112 CASA-CMTS(config)# no snmp engineid

Configure the SNMP engineID. Use the no form of the command to remove the engineID.

Enabling SNMP traps

To enable SNMP traps (the default is all versions of traps are enabled):

Step Command (config) Purpose 1 [no] snmp trap version <version>

Where:

<version> Trap version; values are 1, 2 or 3 Example: Enable SNMP v2 trap CASA-CMTS (config)# snmp trap version 2 Disable SNMP v2 trap: CASA-CMTS (config)# no snmp trap version 2

Enable or disable SNMP traps.

2 show running-config | i “no snmp trap” Example: CMTS#config)#show running-config | i syslog no snmp trap version 1 In the examples above, SNMP version 1 traps are turned off; versions 2 and 3 are allowed are valid for a trap host configuration.

Check for traps that are turned off.

CASA CMTS


Setting an SNMP traphost

To set an SNMP traphost:


1 snmp traphost <host-ip> community <community-string> version <version> Where:

<host-ip> Host server IP address in the format a.b.c.d.

<version> Trap version; values are 1 or 2

<community-string>

SNMP community name.

Example: Set SNMP trap with host IP address 192.168.6.10, community string as public, and trap version of 1: CASA-CMTS (config)# snmp traphost 192.168.6.10 community public version 1

Set the SNMP traphost.

Configuring SNMP server contact and location strings

To specify SNMP contact and location information:


1 snmp-server {contact <string> | location <string>} Where:

<string> Specifies location and contact information associated with the SNMP server. The text string can have up to 32 alphanumeric characters. If blank spaces are necessary, enclose the string in quotation marks (“ “).

Example: CASA-CMTS (config)# snmp-server location bostonOffice CASA-CMTS (config)# snmp-server contact “Fred Gamble at 978-123-4567”

Specify the SNMP contact and location information strings. Use the no form of the command to delete the current entries.

CASA CMTS


Configuring the SNMP trap source IP address

To specify the SNMP trap source IP address:


1 snmp trap-source loopback <lo_id> Where:

<lo_id> Loopback interface ID’; values are 0 to 15. Example: CASA-CMTS (config)# snmp trap-source loopback 6

Specify the SNMP trap source IP address.

Enabling SNMP inform requests

To enable or disable SNMP inform requests. By default, v2 and v3 informs are enabled:

Step Command (config) Purpose 1 [no] snmp inform version <version>

Where:

<version> Inform version; values are 2 or 3 Example: Enable SNMP v2 inform CASA-CMTS (config)# snmp inform version 2 CASA-CMTS (config)# Disable SNMP v2 inform CASA-CMTS (config)# no snmp inform version 2 CASA-CMTS (config)#

Enable or disable SNMP informs.

2 show running-config | i “no snmp inform” Example: CMTS#config)#show running-config | i “no snmp inform” no snmp inform version 2 In the examples above, SNMP version 2 inform requests are turned off; version 3 inform requests are enabled by default.

Check the current SNMP inform setting.

CASA CMTS


Setting the SNMP community

To set SNMP community:


1 snmp community <community_string> { ro | rw } Where:

<community_string> Text string for SNMP community.

ro Read only privilege.

rw Read and write privilege.

Example: Set SNMP community string to “local” with read-only privileges. CASA-CMTS(config)# snmp community local ro CASA-CMTS(config)# show snmp community Community name: local Community Index: local Community SecurityName: rotesting Community StorageType: 3 Community Status: active

Set SNMP community.

Disabling default SNMP public and private community

To disable the default SNMP public or private community:


1 no snmp comm-tbl public | private Example: CASA-CMTS(config)# no snmp comm-tbl public CASA-CMTS(config)# show snmp community

Disable the default SNMP public or private community.

Configuring the SNMP access table

To configure the SNMP access table:


1 snmp access <group> <context> (snmpv1 | snmpv2c | usm) (no-auth | auth-no-priv | auth-priv) (exact | prefix) <read> <write> <notify> (other | volatile | non-volatile | permanent | read-only) (mod) Where:

<group> group name in string form

Configure the SNMP access table.

CASA CMTS


<context> context prefix in string form snmpv1 snmp version 1 snmpv2c snmp version 2c usm usm no-auth no authentication no privacy auth-no-priv authentication no privacy auth-priv authentication and privacy exact exact context match prefix prefix context match <read> read view name in string form <write> write view name in string form <notify> notify view name in string form other storage other volatile storage volatile non-volatile storage non-volatile permanent storage permanent read-only storage read-only mod modify an entry

Deleting the SNMP access table

To delete the SNMP access table:

Step Command (config) Purpose 1 no snmp access <group> <context> (snmpv1 | snmpv2c |

usm) (no-auth | auth-no-priv | auth-priv) Where:

<group>: group name in string form <context> : context prefix in string form snmpv1: snmp version 1 snmpv2c: snmp version 2c usm: usm no-auth: no authentication no privacy auth-no-priv:

authentication no privacy

auth-priv: authentication and privacy

Delete the SNMP access table.

CASA CMTS


Configuring the community table

To configure the SNMP community table:

Step Command Purpose 1 snmp comm-tbl <comm_index> <comm_name> <sec_name>

<context_id> <context_name> <tag> (other | volatile | non-volatile | permanent | read-only) [mod] Where:

<comm_index>: community table index in string form <comm_name> : community name in string form <sec_name>: community security name in string form <context_id>: context engine ID in string form <context_name>: context name in string form <tag>: tag value in string form other: storage other volatile: storage volatile non-volatile: storage non-volatile permanent: storage permanent read-only: storage read-only mod: modify an entry

Configure the SNMP access table.

Deleting the SNMP community table

To delete the SNMP community table:

Step Command Purpose 1 no snmp comm-tbl <comm_index>

Where:

<comm_index> community table index in string form

Delete the SNMP access table.

Configuring the notification table

To configure the SNMP notification table:

Step Command Purpose 1 snmp notify <name> <tag> (trap | inform) (other | volatile |

non-volatile | permanent | read-only) [mod] Where:

<name>: notify name in string form <tag> : notify tag in string form

Configure the SNMP notification table.

CASA CMTS


trap: notify trap inform: notify inform other: storage other volatile: storage volatile non-volatile: storage non volatile permanent: storage permanent read-only: storage read-only mod: modify an entry

Example: CASA-CMTS(config)#snmp notify InformV2cSNMPv2cNotifyTagList InformV2cSNMPv2cNotifyTagList inform n on-volatile CASA-CMTS(config) show snmp

Deleting the notification table

To delete the SNMP notification table:


1 no snmp notify <name> Where:

<name>: notify name in string form

Delete the SNMP notification table.

Configuring the securityToGroup table

To configure the securityToGroup table:


1 snmp security (snmpv1 | snmpv2c | usm) <sec_name> <group_name> (other | volatile | non-volatile | permanent | read-only) (mod) Where:

snmpv1: SNMP version 1 snmpv2c: SNMP version 2c usm: usm <sec_name>: Security name in string form <group_name>: Group name in string form other: Storage other volatile: Storage volatile

Configure the securityToGroup table.

CASA CMTS


non-volatile: Storage non-volatile permanent: Storage permanent read-only: Storage read-only mod: Modify an entry

Example: CASA-CMTS(config)#snmp security snmpv1 rotesting rotesting non-volatile CASA-CMTS(config) show snmp

Configuring the TargetAddress table

To configure the TargetAddress table:


1 snmp tgt-addr <tgt_addr> snmpUDPDomain <td_addr> <time_out_num> <retry_num> <tag_list> <param> (other | volatile | non-volatile | permanent | read-only) <mask_value> <num> [mod] Where:

<tgt_addr>: Target address in string form snmpUDPDomain:

td UDP domain

<td_addr>:<port> td address and port in dotted decimal notation.

<time_out_num>: time-out value <retry_num>: Number of retries <tag_list>: Tag list in string form <param>: Parameters in string form other: Storage other volatile: Storage volatile non-volatile: Storage non-volatile permanent: Storage permanent read-only Storage read-only <mask_value> Mask value in string form <num> MMS integer range 484 to 65535 Mod Modify an entry

Example: CASA-CMTS(config)# snmp tgt-addr anywhere snmpUDPDomain 192.168.8.232:162 500 1 anywhereTag none non-volatile 255.255.0.0:162 500 CASA-CMTS(config) show snmp

Configure the security TargetAddress table.

CASA CMTS


Deleting the TargetAddress table

To delete the TargetAddress table:

Step Command (config) Purpose 1 no snmp tgt-addr <addr>

Where:

<addr> The target address in string form

Delete the TargetAddress table.

Configuring the TargetParameter table

To configure the TargetParameter table:


1 snmp tgt-param <param> (0 | 1 | 3) (snmpv1 | snmpv2c | usm) <sec_name> (no-auth | auth-no-priv | priv) (other | volatile | non-volatile | permanent | read-only) [mod] Where:

<param>: Target parameter in string form 0 snmpv1 processing 1 snmpv2c processing 3 snmpv3 processing snmpv1 snmp v1 model snmpv2c snmp v2c model usm usm model <sec_name> security name in string form no-auth no auth auth-no-priv auth, no priv priv priv other storage other volatile storage volatile non-volatile storage non-volatile permanent storage permanent read-only storage read-only mod modify an entry

Example: CASA-CMTS(config)# snmp tgt-param InformV3SNMPv3Notify 3 snmpv2c noAuthNoPrivUser no-auth non-volatile CASA-CMTS(config) show snmp

Configure the TargetParameter table.

CASA CMTS


Deleting the TargetParameter table To delete the TargetParameter table:


1 no snmp tgt-param <param> Where:

<param>: Target parameter in string form.

Delete the TargetParameter table.

Configure the ViewTreeFamily table

To configure the ViewTreeFamily table:


1 snmp tree-family <view> <subtree> <mask> (include | exclude) (other | volatile | non-volatile | permanent | read-only) [mod] Where:

<view>: view name in string form <subtree>: subtree name in string form <mask>: mask name in string form include include exclude exclude other storage other volatile storage volatile non-volatile storage non volatile permanent storage permanent read-only storage read-only mod modify an entry

Example: CASA-CMTS(config)# snmp tree-family docsisManagerView 1.3.6.1.4.1.9.9 252 exclude non-volatile CASA-CMTS(config) show snmp

Configure the ViewFreeFamily table.

CASA CMTS


Deleting the ViewTreeFamily table

To delete the ViewTreeFamily table:


1 no snmp tree-family <view> <subtree> Where:

<view>: View name in string form <subtree>: Subtree name in string form

Delete the ViewFreeFamily table.

Configuring the SNMP user table

To configure the User table


1 snmp user <engine_id> <user_name> (no-auth | md5 | sha) (0 | 1) <auth_pswd> (no-priv | des | aes) (0 | 1) <priv_pswd> (other | volatile | non-volatile | permanent | read-only) <target_string> [mod] Where:

<engine_id> local use engine id in string form

<user_name> user name in ASCII format no-auth no authentication md5 MD5 authentication sha SHA authentication 0 use clear authentication

password as input 1 use encrypted authentication

password as input <auth_pswd> authentication password, use

- if no password no-priv no privilege des use DES aes use AES 0 use clear privilege password

as input 1 use encrypted privilege

password as input <priv_pswd> privilege password, use - if no

password Other storage other volatile storage volatile

Configure the SNMP user table.

CASA CMTS


non-volatile storage non volatile permanent storage permanent read-only storage read-only <target_string> target string, use - if no string Mod modify an entry

Example: CASA-CMTS(config)#snmp user AuthPrivMD5User user1 md5 1 zYtNm no-priv 1 - non-volatile anyWhereTag CASA-CMTS(config) show snmp

Deleting the SNMP user table

To delete the SNMP user table:


1 no snmp user <engine_id> <user_name> Where:

<engine_id> User engine id. <user_name> User name in ASCII format

Delete the SNMP User table.

Displaying the SNMP configuration and statistics

To show the SNMP configuration and statistics:


1 show snmp Example: See example below.

Show the SNMP configuration and statistics.

Example: show snmp CASA-CMTS (config)# show snmp SNMP community information Community name: private Community Index: private Community SecurityName: rwtesting Community StorageType: 3 Community Status: active

CASA CMTS


Community name: public Community Index: public Community SecurityName: rotesting Community StorageType: 3 Community Status: active Community name: rotesting Community Index: rocablelabs Community SecurityName: rotesting Community StorageType: 3 Community Status: active Community name: rwtesting Community Index: rwcablelabs Community SecurityName: rwtesting Community StorageType: 3 Community Status: active Community name: testcom Community Index: testcom Community SecurityName: rotesting Community StorageType: 3 Community Status: active SNMP server hosts Host address : 192.168.0.222 Security model: SNMPv2c Security Name : rotesting SNMP agent statistics snmpInPkts: 11 snmpOutPkts: 2 snmpInBadVersions: 0 snmpInBadCommunityNames: 9 snmpInBadCommunityUses: 0 snmpInASNParseErrs: 0 snmpInTooBigs: 0 snmpInNoSuchNames: 0 snmpInBadValues: 0 snmpInReadOnlys: 0 snmpInGenErrs: 0 snmpInTotalReqVars: 1 snmpInTotalSetVars: 0 snmpInGetRequests: 0 snmpInGetNexts: 1 snmpInSetRequests: 0 snmpInGetResponses: 0 snmpInTraps: 0 snmpOutTooBigs: 0 snmpOutNoSuchNames: 0 snmpOutBadValues: 0 snmpOutGenErrs: 0 snmpOutGetRequests: 0

CASA CMTS


snmpOutGetNexts: 0 snmpOutSetRequests: 0 snmpOutGetResponses: 0 snmpOutTraps: 0 snmpEnableAuthenTraps: 1 snmpSilentDrops: 0 snmpProxyDrops: 0 snmp user - root no-auth - no-priv - non-volatile active anywhereTag snmp user - tapuser md5 - no-priv - non-volatile active tapUserTagList snmp user - rotesting no-auth - no-priv - non-volatile active

anywhereTag snmp user - rwtesting no-auth - no-priv - non-volatile active

anywhereTag snmp user - AuthPrivMD5User md5 - - non-volatile active anywhereTag snmp user - AuthPrivSHAUser sha - - non-volatile active anywhereTag snmp user - noAuthNoPrivUser no-auth - no-priv - non-volatile active

anywhereTag snmp user - AuthNoPrivMD5User md5 - no-priv - non-volatile active

anywhereTag snmp user - AuthNoPrivSHAUser sha - no-priv - non-volatile active

anywhereTag snmp security snmpv1 rotesting rotesting non-volatile active snmp security snmpv1 rwtesting rwtesting non-volatile active snmp security snmpv2c rotesting rwtesting non-volatile active snmp security snmpv2c rwtesting rwtesting non-volatile active snmp security usm root root non-volatile active snmp security usm tapuser tapUserGroup non-volatile active snmp security usm AuthPrivMD5User AuthPrivMD5User non-volatile active snmp security usm AuthPrivSHAUser AuthPrivSHAUser non-volatile active snmp security usm noAuthNoPrivUser noAuthNoPrivUser non-volatile active snmp security usm AuthNoPrivMD5User AuthNoPrivMD5User non-volatile

active snmp security usm AuthNoPrivSHAUser AuthNoPrivSHAUser non-volatile

active snmp access root usm no-auth exact SNMPv3View SNMPv3View SNMPv3View

non-volatile active snmp access rotesting snmpv1 no-auth exact docsisManagerView

docsisManagerView non-volatile active snmp access rotesting snmpv2c no-auth exact docsisManagerView

docsisManagerView non-volatile active snmp access rwtesting snmpv1 no-auth exact docsisManagerView

docsisManagerView docsisManagerView non-volatile active snmp access rwtesting snmpv2c no-auth exact docsisManagerView

docsisManagerView docsisManagerView non-volatile active snmp access tapUserGroup usm auth-no-priv exact TapView TapView

TapView non-volatile active snmp access AuthPrivMD5User usm auth-priv exact SNMPv3View SNMPv3View

SNMPv3View non-volatile active snmp access AuthPrivSHAUser usm auth-priv exact SNMPv3View SNMPv3View

SNMPv3View non-volatile active snmp access noAuthNoPrivUser usm no-auth exact SNMPv3View SNMPv3View

SNMPv3View non-volatile active snmp access AuthNoPrivMD5User usm auth-no-priv exact SNMPv3View

SNMPv3View SNMPv3View non-volatile active

CASA CMTS


snmp access AuthNoPrivSHAUser usm auth-no-priv exact SNMPv3View SNMPv3View SNMPv3View non-volatile active

snmp notify InformV2cSNMPv2cNotifyTagList InformV2cSNMPv2cNotifyTagList inform non-volatile active

snmp notify InformV3SNMPv3NotifyTagList InformV3SNMPv3NotifyTagList inform non-volatile active

snmp notify TrapV1SNMPv1TrapsTagList TrapV1SNMPv1TrapsTagList trap non-volatile active

snmp notify TrapV2cSNMPv2cTrapsTagList TrapV2cSNMPv2cTrapsTagList trap non-volatile active

snmp notify TrapV2cSNMPv3TrapsTagList TrapV2cSNMPv3TrapsTagList trap non-volatile active

snmp notify tapUserTrapTagList tapUserTrapTagList trap non-volatile active

snmp tgt-addr V1SNMPv1Traps snmpUDPDomain 192.168.0.222:162 500 1 V1SNMPv1TrapsTagList V1SNMPv1Traps other active

snmp tgt-param InformV2cSNMPv2cNotify 1 2 rotesting 1 non-volatile active

snmp tgt-param InformV3SNMPv3Notify 3 3 noAuthNoPrivUser 1 non-volatile active

snmp tgt-param TrapV1SNMPv1Traps 0 1 rotesting 1 non-volatile active snmp tgt-param TrapV2cSNMPv2cTraps 1 2 rotesting 1 non-volatile active snmp tgt-param TrapV2cSNMPv3Traps 3 3 noAuthNoPrivUser 1 non-volatile

active snmp tgt-param tapUserTrapTag 3 3 tapuser 2 non-volatile active snmp tree-family TapView 1.3.6.1 - excluded non-volatile active snmp tree-family TapView 1.3.6.1.4.1.9.9.252 - included non-volatile

active snmp tree-family TapView 1.3.6.1.4.1.9.9.394 - included non-volatile



active snmp tree-family TapView 1.3.6.1.4.1.20858.10.19 - included non-

volatile active snmp tree-family TapView 1.3.6.1.4.1.4491.2.2.9.1.1 - included non-

volatile active snmp tree-family TapView 1.3.6.1.4.1.4491.2.2.9.1.2 - included non-

volatile active snmp tree-family SNMPv3View 1.3.6.1 - included non-volatile active snmp tree-family SNMPv3View 1.3.6.1.4.1.9.9.252 - excluded non-volatile

active snmp tree-family SNMPv3View 1.3.6.1.4.1.9.9.394 - excluded non-volatile



active snmp tree-family SNMPv3View 1.3.6.1.4.1.20858.10.19 - excluded non-

volatile active snmp tree-family SNMPv3View 1.3.6.1.4.1.4491.2.2.9.1.1 - excluded non-

volatile active snmp tree-family SNMPv3View 1.3.6.1.4.1.4491.2.2.9.1.2 - excluded non-

volatile active

CASA CMTS


snmp tree-family docsisManagerView 1.3.6.1 - included non-volatile active

snmp tree-family docsisManagerView 1.3.6.1.4.1.9.9.252 - excluded non-volatile active





snmp tree-family docsisManagerView 1.3.6.1.6.3.16.1.5.2 - excluded non-volatile active

snmp tree-family docsisManagerView 1.3.6.1.4.1.4491.2.2.9.1.1 - excluded non-volatile active

snmp tree-family docsisManagerView 1.3.6.1.4.1.4491.2.2.9.1.2 - excluded non-volatile active

Monitoring the SNMP process at the CMTS To monitor and restart the SNMP process whenever an unknown SNMP failure occurs, enable the software-health-check snmpd setting in the CMTS configuration mode. The default setting is disabled.


1 [no] software-health-check snmpd Example: To enable monitoring of the SNMP process: CASA-CMTS(config)#software-health-check snmpd To disable monitoring of the SNMP process: CASA-CMTS(config)# no software-health-check snmpd

Enable or disable monitoring and restarting of the SNMP process after an SNMP failure.

Configuring IPDR

CASA CMTS supports IP Detail Record (IPDR). IPDR is an open, vendor-independent standard defined in the Network Data Management, and provides billing interface and record-keeping for any type of services that can be delivered over an IP-based network.

The IPDR server should be set to the default port 4737.

This section describes the CLI commands for the following IPDR operations:

CASA CMTS


x Displaying the IPDR connection x Displaying IPDR sessions x Restarting/Stopping the IPDR daemon x Configuring IPDR collector masterships x Enabling IPDR service types x Configuring the IPDR keepalive interval x Configuring the IPDR ACK sequence interval x Configuring the IPDR ACK interval x Configuring the IPDR collector interval x Configuring the IPDR spectrum measurement interval x Setting the IPDR connection primary

Displaying IPDR connections

To display current IPDR connections:


1 show ipdr connection [<channel_name>] Where:

<channel_name> Connection channel name in string form. Example: CASA-CMTS(config)#show ipdr connection DISPLAYING CONNECTION INFORMATION OF THE IPDR COLLECTORS No IPDR Collector is connected at current time.

Display current IPDR connections.

Displaying IPDR sessions

To display current IPDR sessions:


1 show ipdr session Example: CASA-CMTS(config)#show ipdr session

Display current IPDR sessions.

Example: show ipdr session C3000-230(config)#show ipdr session

Session: 1

Session Name : DOCSIS-SAMIS-TYPE-1

CASA CMTS


Schema Name : DOCSIS-SAMIS-TYPE-1_3.5.1-A.1.xsd

Schema version : 3.5.1-A.1

Collection Interval: 60 (seconds)

Streaming status : Other

Collector IpAddr : N/A

Session Type : TIME INTERVAL

Session enabled : TRUE

Session: 2

Session Name : DOCSIS-SAMIS-TYPE-2

Schema Name : DOCSIS-SAMIS-TYPE-2_3.5.1-A.1.xsd

Schema version : 3.5.1-A.1

Collection Interval: 17 (seconds)

Streaming status : Other

Collector IpAddr : N/A

Session Type : TIME INTERVAL

Session enabled : TRUE

Displaying IPDR statistics from the running configuration To display current IPDR statistics, including keepalive, IPDR acksequence, IPDR acktimeInterval, and IPDR master settings, execute the show running-config command with the include ipdr filter option.


1 show running-config | include ipdr Example: CASA-CMTS(config)#show running-config | include ipdr

Display current IPDR sessions.

Restarting and stopping the IPDR daemon

To stop or restart the IPDR daemon:


1 ipdr stop ipdr restart Example: CASA-CMTS# ipdr stop CASA-CMTS# ipdr restart

Stop or restart the IPDR daemon.

CASA CMTS


Configuring IPDR collector mastership

To configure an IPDR server as a master collector:


1 ipdr collector <conn_index> (primary | secondary) Where:

<conn_index> Specifies the connection index of the collection from the show command.

primary Specifies the primary collector.

secondary Specifies the secondary collector.

Configure an IPDR server.

Enabling IPDR service types

To enable IPDR service types:


1 ipdr enable {all | cm-status | cpe | cpe-adhoc | cpe-event | diaglog | logdetail | logevent | samis1 | samis2 | sm | topo | us-status] Where:

all Specifies enabling of all IPDR services.

cm-status Specifies cable modem registration status.

cpe Specifies customer premises equipment status records.

cpe-adhoc Specifies customer premises equipment ad-hoc session status. Ad-hoc sessions are created by the CMTS to enable data streaming and export, and then closed by the CMTS upon completion.

cpe-event Specifies customer premises equipment event-based session status. Event-based sessions allow the CMTS to enable data streaming and export as long as the session remains open.

diaglog Specifies diagnostic log records.

logdetail Specifies log detail records.

logevent Specifies log event records.

samis1 Specifies DOCSIS Subscriber Accounting Management Interface Specification for DOCSIS 3.0 (SAMIS, Type 1) records

Enable IPDR service type.

CASA CMTS


samis2 Specifies DOCSIS Subscriber Accounting Management Interface Specification for DOCSIS 3.0 (SAMIS, Type 2 ) records.

sm Specifies spectrum measurement records.

topo Specifies network topology records.

us-status Specified upstream status records. Example: CASA-CMTS(config)# ipdr enable all CASA-CMTS(config)#

Configuring the IPDR keepalive time interval

To configure the IPDR keepalive time interval:


1 [no] ipdr keepalive <interval> Where:

<interval> Specifies the keepalive time interval in seconds; values are 1 to 600.

Configure the IPDR keepalive time interval.

Configuring the IPDR acknowledge sequence interval

To configure the IPDR acknowledge sequence interval:

Step Command (config) Purpose 1 [no] ipdr acksequence <interval>

Where:

<interval> Specified the acknowledgement sequence interval in seconds.

Configure the IPDR acknowledge sequence interval.

Configuring the IPDR ACK interval

To configure the IPDR acknowledge time interval:


1 [no] ipdr ackTimeInterval <interval> Where:

<interval> Specifies the acknowledgement time interval in seconds.

Configure the IPDR acknowledge time interval.

CASA CMTS


Configuring the IPDR spectrum measurement interval

To configure the IPDR spectrum measurement interval:


1 [no] ipdr sminterval <interval> Where:

<interval> Specifies the spectrum measurement collection interval in seconds.

Configure the IPDR spectrum measurement interval.

Configuring the IPDR connection to be primary

To configure the IPDR connection to be primary:


1 ipdr master <ipaddr> Where:

<ipaddr> Specifies the connection IP address.

Configure the IPDR connection to be primary.

Configuring the IPDR loopback interface

To configure the internal CMTS loopback interface for IPDR traffic:


1 [no] ipdr source-interface loopback <number> Where:

<number> Specifies the IPDR loopback interface in the range 0 to 15.

Example: CASA-CMTS(config# ipdr source-interface loopback 10

Configure the IPDR source interface for IPDR traffic.

CASA CMTS


Configuring IPsec

This section describes the CLI commands for IPsec operations currently supported by the Casa CMTS. The supported operations are:

x Enabling IPsec services x Configuring the IPsec PreKey x Deleting the IPsec PreKey x Displaying IPsec PreKey x Configuring IPsec Phase 1 x Configuring IPsec Phase 2 x Displaying the IPsec information x Deleting the IPsec configuration x Adding the IPsec security policy x Removing the IPsec security policy x Displaying the IPsec security policy database

Steps to configure IPsec are:

1. Set the pre-shared key. 2. Configure the phase1 parameters. 3. Configure the phase2 parameters. 4. Configure the SPD.

Enabling and disabling the IPsec service

To enable or disable the IPsec service, use the following commands. Note that this command is not executed in config mode; end the config session first.

IPsec will automatically start when all parameters are correctly configured the first time.

Step Command (config) Purpose 1 ipsec start

ipsec stop Example: CASA-CMTS# ipsec start CASA-CMTS# ipsec stop To verify that IPsec is running: CASA-CMTS# show ipsec info IKE status: running Phase I: Phase II:

Enable or disable IPsec. All established SAs will be cleared after ipsec stop.

CASA CMTS


Configuring the IPsec PreKey

To configure or delete the IPsec prekey:


1 [no] ipsec <ip_addr> <prekey> Where:

<ip_addr> Remote IP address in dotted decimal format A.B.C.D. This is the IPsec tunnel peer.

<prekey> Prekey in string format. Example: CASA-CMTS(config)# ipsec 192.168.2.125 PACKETCABLE CASA-CMTS(config)# show ipsec prekey 192.168.2.125 PACKETCABLE

To delete:

CASA-CMTS(config)# no ipsec 192.168.2.125 prekey CASA-CMTS(config)#

Configure or delete the IPsec PreKey.

Displaying the IPsec PreKey

To show the IPsec PreKey:


1 show ipsec prekey Example: CASA-CMTS(config)# ipsec 192.168.2.125 PACKETCABLE CASA-CMTS(config)# show ipsec prekey 192.168.2.125 PACKETCABLE

Show the IPsec prekey.

Configuring IPsec Phase 1

To configure IPsec phase 1:


1 ipsec phase1 <policy_name> <ip_addr> <lifetime> <dhgroup> <encry-algorith> <auth-algorith> <use-prekey> <mode> Where:

<policy_name>: Policy name in string format. 'all' is reserved, do not use it

Configure IPsec phase 1.

CASA CMTS


<ip_addr>: Remote IP address in dotted format A.B.C.D, - for any

<lifetime>: Llifetime in unit of minutes. <dhgroup>: diffie-hellman group, 1 or 2 <encry-algorith>:

Encryption algorithm, 3des or des

<auth-algorith>: Authentication algorithm,md5 or sha <use-prekey>: Use pre-shared key or not. <mode>: Main or aggressive

Example: CASA-CMTS(config)# ipsec phase1 test 10.170.1.1 60 1 3des md5 psk aggressive To verify Phase 1 settings: CASA-CMTS(config)# show ipsec info

IKE status: running phase I:

policy name : test

IP address : 10.170.1.1

exchange mode: aggressive

lifetime : 60

proposal : encryption : tripple DES

hash : MD5

auth-method: pre-shared key

dh-group : 1

Configuring IPsec Phase 2

To configure IPsec phase 2:


1 ipsec phase2 <policy_name> <src_ip_addr> <dst_ip_addr> <group> <lifetime> <encry-algorith> <auth-algorith> deflate Where:

<policy_name> Policy name, 'all' is reserved, please do not use it

<src_ip_addr> Source ip address; for any, then destination IP will not take effect

<dst_ip_addr> Destination IP address in dotted format A.B.C.D

<group> diffie-hellman group, 0 refers to a group not specified, 1 refers to PFS group 1

<lifetime> Interval for re-key in unit of minutes.

Configure IPsec phase 2.

CASA CMTS


<encry-algorith>

Encryption algorithm, 3des or des

<auth-algorith> Authentication algorithm. deflate Deflate compression.

Example: CASA-CMTS(config)# ipsec phase2 test 10.170.1.1 10.170.2.1 0 60 des md5 deflate To verify Phase 2 settings: CASA-CMTS(config)# show ipsec info

IKE status: running

phase II:

policy name : test

IP address source : 10.170.1.1

IP address remote : 10.170.2.1

lifetime : 60

encryption : des

hash : MD5

compression-method: deflate

Displaying IPsec information

To show IPsec information:


1 show ipsec info Example: CASA-CMTS# show ipsec info IKE status: running phase I: policy name : test IP address : 10.170.1.1 exchange mode: aggressive lifetime : 60 proposal : encryption : triple DES hash : MD5 auth-method: pre-shared key dh-group : 1 phase II: policy name : test IP address source : 10.170.1.1 IP address remote : 10.170.2.1 lifetime : 60 encryption : des hash : MD5 compression-method: deflate

Show IPsec information.

CASA CMTS


Deleting the IPsec configuration

To delete IPsec configuration:


1 no ipsec <phase_num> <policy_name> Where:

<phase_num>: Phase1or phase2 <policy_name>: Policy name in string format or all for all

policies. Example: CASA-CMTS(config)# no ipsec phase1 192.168.2.125server CASA-CMTS# show ipsec info IKE status: running phase I: phase II: policy name : 192.168.2.125server IP address source : 192.168.2.247 IP address remote : 192.168.2.125 lifetime : 5 encryption : 3des hash : SHA

Delete IPsec configuration.

Adding an IPsec security policy

To add or remove an IPsec security policy:


1 [no] ipsec spd <local_ip_addr> <local_port_num> <remote_ip_addr> <remote_port_num > (in | out) Where:

spd: SPD command. <local_ip_addr>: Local IP address in dotted format. <local_port_num>: Local udp port number, 0 for all traffic. <remote_ip_addr>: Remote IP address in dotted decimal

format. <remote_port_num>: UDP port number, 0 for all traffic in: Direction incoming. out: Direction outgoing. [no] Remove the IPsec security policy.

Add or remove an IPsec security policy.

CASA CMTS


Displaying the IPsec security policy database

To display the security policy database:


1 show ipsec spd [detail] Examples: CASA-CMTS(config)#show ipsec spd IPsec SPD configuration: remote ip address: 192.168.2.125 local ip address : 192.168.2.247 protocol : any direction : in ipsec mode : ESP local ip address : 192.168.2.247 remote ip address: 192.168.2.125 protocol : any direction : out ipsec mode : ESP

CASA-CMTS(config)# show ipsec spd detail 192.168.2.125 192.168.2.247 esp mode=transport spi=52611555(0x0322c9e3) reqid=0(0x00000000) E: 3des-cbc 55ae1807 339b4a01 01a8f8a9 9c988f29 7f9cf461 d343cd21 A: hmac-sha1 bb6f05b7 06c68b44 15bab266 3ff302d1 09d4d374 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Jun 30 14:11:09 2008 current: Jun 30 14:11:12 2008 diff: 3(s) hard: 300(s) soft: 240(s) last: Jun 30 14:11:09 2008 hard: 0(s) soft: 0(s) current: 128(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 2 hard: 0 soft: 0 sadb_seq=1 pid=924 refcnt=0 192.168.2.247 192.168.2.125 esp mode=transport spi=4055512964(0xf1ba3784) reqid=0(0x00000000) E: 3des-cbc e87c92e6 f13102d3 50840db3 d3f42dc9 5efce445 efe14f97 A: hmac-sha1 784a8db4 0386eede 8423adc9 281ddcf5 1fd49c84 seq=0x00000000 replay=4 flags=0x00000000 state=mature created: Jun 30 14:11:09 2008 current: Jun 30 14:11:12 2008 diff: 3(s) hard: 300(s) soft: 240(s)

Display the security policy database. The detail view shows all SAs currently existing in the system.

CASA CMTS


last: Jun 30 14:11:09 2008 hard: 0(s) soft: 0(s) current: 240(bytes) hard: 0(bytes) soft: 0(bytes) allocated: 2 hard: 0 soft: 0 sadb_seq=0 pid=924 refcnt=0

Managing cable modems

The Casa CMTS allows users to manage how cable modems operate in the HFC network. This section covers commands for the following operations: x Showing cable modem status

x Showing the cable modem CPEs

x Showing the registered cable modems

x Showing the cable modem flap list

x Showing the cable modem summary

x Showing the cable modem remote-query

x Configuring the cable modem access-group

x Changing the cable modem frequency

x Setting the cable modem max-CPE

x Setting the cable modem QoS profile

x Enabling cable modem authentication

x Clearing cable modem counts

x Clearing the cable modem offline

x Clearing the cable modem reset

Displaying cable modem status

To display information for the registered and unregistered CMs, use the show cable-modem command in privileged mode. The output is sorted by cable interface and the CM MAC address.

Step Command Purpose 1 show cable modem [<ip-address> | <ipv6-address | mac-

address] [verbose] Where:

ip-address ipv6-address

Identifies the IP address of a specific CM to be displayed. If you specify the IP address for a CPE device behind a CM, information for that CM is displayed.

Show cable modem status.

CASA CMTS


Example: Show the default display for individual CMs. CASA-CMTS# show cable modem MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf Status Sid (dB) Offset CPEs Enb 0011.8078.1950 0.0.0.0 3/2/0 0/1/2 offline 0 0.0 0 0 no 0011.e6bb.e3b1 10.190.1.98 3/3/0 0/1/1 online 3 0.0 1971 0 no 0014.6cb9.ffbb 10.190.1.99 3/0/0 0/1/0* online 4 -0.5 1989 1 no 0015.f2fe.cef5 0.0.0.0 3/0/0 0/1/3 init(rc) 6 0.0 2079 0 no online cm 2 ; offline cm 1 ; ranging cm 1

mac-address Identifies the MAC address of a specific CM to be displayed. You can also specify the MAC address for a CPE device behind a CM, and information for that CM will be displayed.

verbose Displays detailed information for the CMs.

Example: show cable modem command Show the default output for the cable modem with the specified mac-address. CASA-CMTS# show cable modem 0011.8078.1950 MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf Status Sid (dB) Offset CPEs Enb 0011.8078.1950 10.237.1.102 3/2/0 0/1/2 online 5 0.0 1906 1 yes online cm 1 ; offline cm 0 ; ranging cm 0

See Table 3 for a description of the MAC status field.

Table 3. MAC status fields

MAC State Value Description of registration and status conditions

init(r1) Initial ranging request sent by cable modem (CM) to CMTS.

init(r2) The CMTS received an initial ranging rquest from the CM. The CMTS has responded and returned RF power information, timing offset, and frequency adjustments to the CM. The CM and CMTS link is still in the ranging state, and ranging is not complete. Check the RF attenuations if initial ranging remains stuck. Use the debug cable ranging command for information.

init(ov) CMTS is static load balancing and is using the upstream channel ID override and/or downstream frequency override to move the modem to new channel.

CASA CMTS


Check the modem power if stuck in this state.

init(rc) CM ranging to the CMTS has completed. Check the cable helper address configuration and IP connectivity to the DHCP server. Use debug cable dhcp command for information. Note: It is also possible that the upstream is at capacity and has no additional bandwidth for the CM to finish registration and come online. If this is the case make sure load balancing is enabled.

init(ua) Upstream channel adjustment (for DOCSIS 3.0 modems).

init(d) CMTS has received the DHCP discover message; first IP broadcast packet has been received from the CM.

init(i) The CM has received the DHCPOFFER reply from the DHCP server, but the CM has not yet replied with a DHCPREQUEST message, nor has it sent an IP packet with its assigned IP address. It is possible that the CM has received the DHCPOFFER reply from the DHCP server, but the reply might have invalid options for that particular CM.

init(e) Early authentication and encryption started (3.0 modems). Check the modem certificate if stuck in this state.

init(t) Configuration file download complete; time-of-day (TOD) exchange started.

init(r) CMTS received register-request from cm,but has not received reg-ack yet. If stuck, check the modem config file. Use debug cable registration to debug registration request received.

init(bpi) Start baseline privacy. If stuck in this state, check the modem certificate and ensure that the CM is synchronized with the BPI server.

resetting The CM is being reset; registration process restarting.

Non-error Status Conditions cc(r1) The CM had previously registered and was online, but the CMTS has sent a

Downstream Channel Change (DCC) or Upstream Channel Change (UCC) request message to the CM. The CM has started moving to the new channel, sending an initial ranging request on the new downstream or upstream channel to the CMTS. At the MAC layer, the CM is not yet passing traffic on the new channel and is considered in the offline state. This state does not trigger the flap-list counters.

cc(r2) This state normally follows cc(r1) and indicates that the CM has finished its initial ranging on the new channel, and is currently performing continuous ranging on the new channel. At the MAC layer, the CM is not yet passing traffic on the new channel and is considered in the offline state. This state does not trigger the flap-list counters.

offline The CM is detected as offline, disconnected, or powered off.

online The CM has registered; modem is ready to pass data on the network.

online(d) The CM is registered. However, network access for CPE devices using this CM has been disabled by the DOCSIS configuration file. The CMTS continues to communicate with the CM using DOCSIS messages and IP traffic (such as SNMP) but the CM does not forward traffic to or from the CPE devices,

CASA CMTS


Note: If BPI was enabled in the DOCSIS configuration file sent to the CM, the CM is using BPI encryption unless other messages indicate that the BPI negotiation and key assignments have failed.

online(pkd) The CM has registered with the CMTS. However, network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. BPI is enabled and the key-encrypting key (KEK) is assigned.

online(pt) The CM has registered with the CMTS. BPI is enabled and traffic-encrypting key (TEK) is assigned. BPI encryption is now being performed.

online(ptd) The CM has registered with the CMTS. However, network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. BPI is enabled and traffic-encrypting key (TEK) is assigned. BPI encryption is now being performed. This state is equivalent to the online(d) and online(pt) states.

online(pk) The CM has registered with the CMTS. BPI is enabled and the key-encrypting key (KEK) is assigned.

expire(pk) The CM has registered. BPI is enabled and the KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value

expire(pke) The CM has registered. However, network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. BPI is enabled and the KEK was assigned, but the current KEK expired before the CM could successfully renew a new KEK value. This state is equivalent to the online(d) and expire(pk) states

expire(pt) The CM has registered. BPI is enabled and the TEK was assigned. The current TEK expired before the CM could successfully renew a new KEK value.

expire(ptd) The CM has registered. However, network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. BPI is enabled and traffic-encrypting key (TEK) was assigned, but the current TEK expired before the CM could successfully renew a new KEK value. This state is equivalent to the online(d) and expire(pt) states.

Error status conditions reject(pk) The KEK assignment is rejected and BPI encryption has not been established.

reject(pkd) The CM has registereed. However, network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. BPI encryption was not established because KEK assignment was rejected. This state is equivalent to the online(d) and reject(pk) states.

reject(pt) The TEK assignment is rejected and BPI encryption has not been established.

reject(ptd) The CM has registered. However, network access for CPE devices using this CM has been disabled through the DOCSIS configuration file. BPI encryption was not established because TEK assignment was rejected. This state is equivalent to the online(d) and reject(pt) states.

Example: show sample cable modem verbose CASA-CMTS# show cable modem 0050.f112.b764 verbose MAC Address :0026.5e77.43b3

CASA CMTS


IP Address :10.248.1.103 Prim Sid :8 MAC Domain :1 Upstream Channel Set :1/0/0, 1/1/0, 1/4/0, 1/5/0 Downstream Channel Set :0/1/0, 0/1/1, 0/1/2, 0/1/3 Unusable channel list : Timing Offset :2030 Initial Timing Offset :2026 Received Power :0 dBmV MAC Version :DOC3.0 Qos Provisioned Mode :DOC1.1 Enable DOCSIS2.0 Mode :Y Initial Ranging Message :B-INIT-RNG-REQ Registration Request Message :REG-REQ-MP Phy Operating Mode :atdma Capabilities :{Frag=Y, Concat=Y, PHS=Y, Priv=BPI} Optional Filtering Support :{802.1P=N, 802.1Q=N} Number of CPE IPs :0 CFG Max-CPE :16 Errors :0 CRCs,0 HCSes Stn Mtn Failures :0 aborts,0 exhausted Total US Flows :1 Total DS Flows :1 Total US Data :128 packets,9074 bytes Total US Throughput :0 kbits/sec,0 packets/sec Total DS Data :6 packets,1039 bytes Total DS Throughput :0 kbits/sec,0 packets/sec Upstream Dropped Packets :0 Active Classifiers :0 DSA/DSX messages :permit all Total Time Online :0 d, 0 h, 58 m, 39 s sysDescr :Cisco EPC3212 DOCSIS 3.0 2-PORT EMTA <<HW_REV: 1.0; VENDOR: Cisco; BOOTR: 2.3.0_R1; SW_REV: epc3212-E10-5-v302r12901-100121c-ZIG; MODEL: EPC3212>>z<AC>

Table 4. show cable modem fields

Field Description

MAC Address The MAC address of the CM.

IP Address The IP address assigned by the DHCP server to the CM.

Prim Sid The primary SID assigned to this CM.

MAC Domain MAC domain ID.

Upstream The line card/port/channel providing the upstream for this CM.

Downstream The line card/port/channel providing the downstream for this CM.

Upstream Channel Set

The set of upstream channels assigned to this modem for bonding (3.0 modems).

Downstream Channel Set

The set of downstream channels assigned to this modem for bonding (3.0 modems).

Unusable channel list

List of assigned channels that are not usable by the modem.

MAC State The current state of the MAC layer.

Received Power

The power level (in dB) received by the CM.

CASA CMTS


Timing Offset The timing offset for the CM, in ticks, as recognized by the CMTS. (A tick is 6.25/64 microseconds.) This is the delay between when a particular cable modem is scheduled to make a transmission and when the CMTS actually receives it. Note: The timing offset shown here is typically smaller than the TX Time Offset value shown by the show cable modem remote-query command, since the latter value is the offset as recognized on the CM (which will include any internal delay between when the CM software begins the transmission and when the bits actually appear on the local cable interface).

Initial Timing Offset

The initial timing offset for the CM, in ticks, as recognized by the CMTS (see above).

Num CPEs, CFG Max-CPE

Indicates the number of CPE devices for which the CM is providing services.

Number of CPE IPs

Indicates the maximum number of IP addresses assigned to CPE devices behind this CM, as configured by the cable max-hosts command.

Ver, MAC Version

Displays the maximum supported version of DOCSIS that the CM supports (DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0, DOCSIS 3.0).

QoS Prov, QoS Provisioned Mode

Displays the version of DOCSIS that the CM currently is provisioned for (DOCSIS 1.0, DOCSIS 1.1, DOCSIS 2.0).

Enable DOCSIS 2.0 Mode

Indicates whether the CM is capable of DOCSIS 2.0 (ATDMA) operation, as determined by the presence and value of the Enable 2.0 Mode (TLV39) field in the CM's Registration Request message or in the DOCSIS configuration file. The valid values are: • Y = TLV 39 was set to 1, indicating that the CM has enabled DOCSIS 2.0 mode. The CM could still be registered for DOCSIS 1.1 operations, however, on DOCSIS 1.X interfaces. • N = Either the TLV 39 field was not present in the CM's Registration Request message, indicating that the CM is not capable of DOCSIS 2.0 operations, or the TLV 39 field was set to 0 in the DOCSIS configuration file, preventing the CM from using the DOCSIS 2.0 mode.

Initial Ranging Message

Initial ranging message that the CM sends: RNG-REQ for DOCSIS 1.0/1.1/2.0 CMs, B-INIT-RNG-REQ for DOCSIS 3.0 CM.

Registration Request Message

Registration request message that the CM sends: REG-REQ for DOCSIS 1.0/1.1/2.0 CMs, REG-REQ-MP for DOCSIS 3.0 CM.

Phy Operating Mode

Indicates the type of PHY-layer modulation that the CM is using: tdma or atdma.

BPI Enbld Indicates whether Baseline Privacy Interface (BPI) or BPI Plus (BPI+) encryption is enabled for the CM.

CASA CMTS


Capabilities Indicates what the CM reported as its capabilities in its Registration Request message: DOCSIS fragmentation, concatenation, packet header suppression (PHS), and BPI encryption.

Optional Filtering Support

Indicates whether 802.1P or 802.1Q packet filtering is enabled for this CM.

Transmit Equalizer Support

Number of taps used for transmit equalization.

Errors Number of frame CRC and HCS errors reported for this CM.

Sn Mtn Failures

Number of station maintenance failures (aborts and retries).

Total US Flows Total number of upstream service flows, with the number of active service flows within the parentheses.

Total DS Flows Total number of downstream service flows, with the number of active service flows within the parentheses.

Total US Data Total data this CM has transmitted on the upstream, in packets and bytes.

Total US Throughput

Calculated throughput for this CM on the upstream, if available.

Total DS Data Total data this CM has received on the downstream, in packets and bytes.

Total DS Throughput

Calculated throughput for this CM on the downstream, if available.

Upstream Dropped Packets

Number of packets dropped on the upstream interface.

Active Classifiers

Current number of active classifiers for this CM, with the maximum number of allowable classifiers for this CM within the parentheses.

DSA/DSX messages

Indicates whether dynamic service changes (DSX) from the cable modem are permitted (permit all) or disallowed (reject all).

Dynamic Secret

Dynamically-generated shared secret (a 16-byte hexadecimal value) that was used in the cable modem's previous registration cycle. If the cable modem is currently offline, this field shows all zeroes. Note: This field displays a value only when the cable dynamic-secret command has been used on the CMTS interface.

Total Time Online

Amount of time in days, hours, and minutes that this CM has been continuously online since it last registered with the CMTS. This field begins incrementing whenever the CM enters one of the online(x) MAC states, and is reset to 0 whenever the CM enters any other MAC state.

sysDescr Cable modem information.

CASA CMTS


Displaying cable modem CPE devices

To display the CPE devices accessing the cable interface through a particular CM, use the show cable modem cpe command in privileged mode.


1 show cable modem [<ip-address> |<ipv6-address> | mac-address] cpe Where:

Example: List the CPE devices by their MAC and IP addresses: CASA-CMTS# show cable modem 0050.bfb9.021d cpe CPE IP Address Method CPE MAC Address CM IP Address CM MAC Address 10.190.1.143 static 0064.0102.0101 10.190.1.7 0050.bfb9.021d


Identifies the IP address of a specific CM to be displayed. If you specify the IP address for a CPE device behind a CM, information for that CM is displayed.

mac-address Identifies the MAC address of a specific CM to be displayed. You can also specify the MAC address for a CPE device behind a CM, and information for that CM will be displayed.

Display CPE devices behind a specified cable modem.

Displaying cable modems by state

To display a list of the CMs by state, use the show cable modem {init | offline | online} command in privileged mode:


1 show cable modem [init | offline | online] Example: See examples below.

Display the CMs by state.

Example: Show cable modems by state Show sample output for the default form of the show cable modem init command.

CASA CMTS


CASA-CMTS# show cable modem init MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf Status Sid (dB) Offset CPEs Enb 0005.ca6d.0120 0.0.0.0 3/2.0/0 0/1/0 init(i) 402 -0.2 2487 0 no 0024.d18e.b1cf 0.0.0.0 3/0.0/0 0/0/2 init(d) 401 0.0 2245 0 no total cm 2

Show sample output for the default form of the show cable modem online command. CASA-CMTS# show cable modem online Interface MAC Address Prim Previous Online Rx RX SM Sid State Time Power SNR Exhaust Count 3/0/0 0015.f2fe.bf1a 6 online Tue May 12 08:56:31 2009 0.0 42.1 0 3/0/0 0050.bfb9.021d 7 online Tue May 12 08:56:30 2009 0.2 42.1 0

Cable modem summary information

The show cable modem command has the following options:

<ipAddress> Cable modem IPv4 address; A.B.C.D

<mac_addr> Cable modem MAC address; xxxx.xxxx.xxxx

<ipv6_address> Cable modem IPv6 address; xxxx:xxxx:...:xxxx

authorization Display trusted cable modem configurations

bonding Display cable modem bonding

calls Display total number of calls that have been processed at this cable modem.

cm-status Display the cable modem status log

counters Display cable modem upstream and downstream counter information in bytes.

cpe Display customer premises equipment and the associated IP and MAC addresses.

deny Display cable modems that are denied registration at the CMTS.

docsis-device-class

Display DOCSIS device class information.

docsis-mac Display cable modems per MAC domain.

downstream Display cable modem statistics on CMTS downstream interfaces.

dropped-packets Display dropped packet counts on upstream and downstream interfaces.

errors Display upstream and downstream CRC and HCS errors.

init Display total cable ip modems that have initialized and are in the init state.

ip-address Display IPv4 and IPv6 cable modem addresses.

CASA CMTS


mac Display cable modem MAC information.

maintenance Display cable modem active time statistics per interface.

non-bonding Display cable modem non-bonding (modems capable of bonding but have only 1 channel assigned

offline Display previously-registered cable modems that are now offline.

online Display the current list of cable modems that have a MAC status of online.

phy Display cable modem physical information statistics, such as transmission and signal-to-noise reduction data.

qos Display quality-of-service statistics including transmission and throughput rates.

remote-query Display cable modem performance statistics immediately, or at the specified upstream or downstream module.

rogue Display cable modems spoofing statistics during ranging.

summary Display cable modem summary information, including total modem counts, active and offline modems, modems that have registered, and secondary modems.

tftp-bypass Display cables that have bypassed TFTP and have not uploaded a modem configuration file.

upstream Display cable modems per the specified system upstream slot, port number, physical channel number, and upstream logical channel.

vendor Display cable modem vendor-specific information, or filtered vendor information using the all, config, default, or summary options.

verbose Displays the extended version of the show cable modem command output by including all statistics.

In addition, the following information can be displayed about each cable modem by specifying the MAC or IP address: show cable modem [<mac-address> | <ip-address> | < ipv6-address>]:

classifiers Displays downstream classifiers information.

calls Display total number of calls that have been processed at this cable modem.

counters Display cable modem upstream and downstream counter information in bytes.

cpe Display customer premises equipment and the associated IP and MAC addresses.

docsis-device-class Display DOCSIS device class information.

dropped-packets Display dropped packet counts on upstream and downstream interfaces.

errors Display upstream and downstream CRC and HCS errors.

CASA CMTS


mac Display cable modem MAC information.

maintenance Display cable modem active time statistics per interface.

multicast-session Display multicast session information.

mask Display remote query statistics

online Display the current list of cable modems that have a MAC status of online.

phy Display cable modem physical information statistics, such as transmission and signal-to-noise reduction data.

qos Display quality-of-service statistics including transmission and throughput rates.

remote-query Display cable modem performance statistics immediately, or at the specified upstream or downstream module.

vendor Display cable modem vendor-specific information, or filtered vendor information using the all, config, default, or summary options.

verbose Displays the extended version of the show cable modem command output by including all statistics.

Configuring the cable modem flap list

The Casa CMTS has a flap-list command that can be used for detecting abnormal CM(s) in the network. It provides a list of malfunctioning CM(s), and assists the user in identifying the problem. The user can define several parameters for determining which modems are put in the flap list. These parameters are:

x Set the flap-list insertion time

x Set the flap-list power-adjust threshold

x Set the flap-list miss threshold

x Set the flap list aging

x Configure the flap-list check interval

x Configure the flap-list size

Setting the flap list insertion time

During a certain period, if the CM constantly sends out initial ranging requests, then it will be put into flap-list table for observation. The default value is 60 seconds. This command can be disabled by a "no" form of this command:

CASA CMTS


Example: Set the flap-list insertion-time to 5 seconds: CASA (config)# cable flap-list insertion-time 5

Example: Recover flap-list insertion-time default value: CASA(config)# cable flap-list insertion-time default

Example: Cancel flap-list insertion-time configuration: CASA(config)# no cable flap-list insertion-time

Setting the flap list power adjust threshold

After the CMs come online and the status is stable, if the power adjustment from the CMTS to the CMs is greater than a certain unit of dB, the CMs will be moved to the flap-list table for observation. This command can be disabled by the "no" form of the command:

Example: Set up flap-list power-adjust threshold as 5: CASA(config)# cable flap-list power-adjust threshold 5

Example: Recover flap-list power adjust default value: CASA(config)# cable flap-list power-adjust threshold default

Example: Cancel flap-list power adjust: CASA(config)# no cable flap-list power-adjust threshold

Configuring the flap list miss threshold

When the CMs do not reply to the maintenance message sent from the CMTS after a certain number of times, they will be put into the flap-list table for observation. The default value is 6 times. The command can be canceled using the "no" form of this command.

Example: Set up flap-list miss threshold as 5: CASA(config)# cable flap-list miss threshold 5

Example: Recover flap-list miss threshold default value: CASA(config)# cable flap-list miss threshold default

Example: Cancel flap-list miss threshold: CASA(config)# no cable flap-list miss threshold

Configuring flap list aging

Configure the period which the CMs will be maintained in the flap-list table. If the time limit is reached, the CMs will be removed from the flap-list table. After the CM is removed, the user cannot get flap-list information about this CM. The default value is 10,080 minutes (one week).

Example: Configure the flap-list aging as 120 minutes: CASA(config)# cable flap-list aging 120

Example: Recover flap-list aging default value:

CASA CMTS


CASA(config)# cable flap-list aging default

Configuring the flap list check interval

Set up the interval for the CMTS to scan the flap-list table. If the CMTS finds any CM that has reached the aging limit, the CMTS will remove it from the flap-list table. When the CM is removed, the user cannot check the CM's flap-list information. The default value is 120 minutes.

Example: Configure the flap-list check-interval as 20 minutes: CASA(config)# cable flap-list check-interval 20

Example: Recover flap-list check-interval default value: CASA(config)# cable flap-list check-interval default

Showing the cable modem flap-list

To display the CMs that are flapping on one or more cable interfaces, use the show cable flap-list command in privileged mode. The command will display up to 100 records by default. The command has several arguments that allow the user to display specific information about the modems:

Example: show cable flap-list Display all CM records in the flap-list: CASA> show cable flap-list

Display specified CM record by MAC address: CASA> show cable flap-list ****.****.****

Display specified CM record by MAC address and subnet mask: CASA> show cable flap-list ****.****.**** mask ****.****.****

Display specified CM record by upstream physical channel: CASA> show cable flap-list upstream x/y

Display specified CM record by upstream logical channel: CASA> show cable flap-list upstream x/y/z

Display CM record of specified downstream channel: CASA> show cable flap-list downstream x/y/z

Sort the displayed results by sequence of the latest offline: CASA> show cable flap-list sort-time

CASA> show cable flap-list downstream x/y/z sort-time

Sequence the displayed results by the latest upstream logical channel order:

CASA CMTS


CASA> show cable flap-list sort-int

CASA> show cable flap-list downstream x/y/z sort-int

Order the displayed results by flap value: CASA> show cable flap-list sort-flap

CASA> show cable flap-list downstream x/y/z sort-flap

Sequence the results by CM MAC address: CASA> show cable flap-list sort-mac

CASA> show cable flap-list downstream x/y/z sort-mac

Display detailed flap-list of CMs with specified MAC address: CASA> show cable flap-list ****.****.**** detail

Example: Show the modem flap list output Start Time Hit Miss(%) CRC P-Adj ARP-TO States Offline Time -- 1938 768 (28.4%) 0 0 0 online 2009-08-23,21:51:20 2009-08-24,16:39:28 1291 342 (20.9%) 0 0 0 init(r2) 2009-08-24,20:20:35 2009-08-25,15:28:56 1210 175 (12.6%) 0 0 0 init(r2) 2009-08-25,18:53:52

Showing the cable modem summary

To display a summary of CMs on one or more cable interfaces, use the show cable modem command in privileged mode.


1 show cable modem summary [total] Where:

total Displays the totals for each column.

Example: See examples below.

Display a summary of CMs on one or more cable interfaces.

Example: show cable modem summary Default form of the show cable modem summary command: CASA-CMTS# show cable modem summary Upstream Total Active Registered Interface Modems Modems Modems 1/0/0 2 2 2 1/0/1 0 0 0

CASA CMTS


1/1/0 0 0 0 1/1/1 0 0 0 1/2/0 0 0 0 1/2/1 0 0 0 1/3/0 2 1 1 1/3/1 0 0 0

Example: Show cable modem summary command with the total option: CASA-CMTS# show cable modem summary total CASA#show ca mo summary total Upstream Total Active Registered Secondary Offline Channel Interface Modems Modems Modems Modems Modems Description 1/0.0/0 0 0 0 0 0 1/0.1/0 1 1 1 0 0 1/1.0/0 0 0 0 0 0 1/1.1/0 0 0 0 0 0 1/2.0/0 0 0 0 0 0 1/2.1/0 0 0 0 0 0 1/3.0/0 0 0 0 0 0 1/3.1/0 0 0 0 0 0 1/4.0/0 0 0 0 0 0 1/4.1/0 0 0 0 0 0 1/5.0/0 0 0 0 0 0 1/5.1/0 0 0 0 0 0 1/6.0/0 0 0 0 0 0 1/6.1/0 0 0 0 0 0 1/7.0/0 0 0 0 0 0 1/7.1/0 0 0 0 0 0 Total: 1 1 1 0 0

Displaying the cable modem summary (Release 5.4)

To display a summary of CMs on one or more cable interfaces, use the show cable modem command in privileged mode.


1 show cable modem summary [total] Where:

total The totals for each column. Example: See examples below.

Display a summary of CMs on one or more cable interfaces.

Example: show cable modem summary Default form of the show cable modem summary command: CASA-CMTS# show cable modem summary tot

CASA CMTS


Upstream Total Active Registered Secondary Offline Description Interface Modems Modems Modems Modems Modems 1/0.0/0 0 0 0 0 0 WC-02322 1/0.1/0 0 0 0 0 0 WC-02323 1/1.0/0 0 0 0 0 0 WC-02324 Total: 0 0 0 0 0

Displaying the cable modem on downstream channels

To show all the cable modem on downstream channel:

Step Command Purpose 1 show cable modem downstream {< X/Y/Z> | summary}

Where:

<x> line card slot number. <y> port number. <z> channel number for downstream module. summary: display cable modem summary

information. Example: See examples below.

Show all the cable modem on a downstream channel.

Example: show cable modem on downstream channels CASA-CMTS>show cable modem downstream summary Downstream Total Active Registered Interface Modems Modems Modems 2/0/0 6 6 6 2/0/1 6 6 6 2/0/2 7 6 6 2/0/3 7 7 7 2/1/0 0 0 0 2/1/1 0 0 0 2/1/2 0 0 0 2/1/3 0 0 0 2/2/0 0 0 0 2/2/1 0 0 0 2/2/2 0 0 0 2/2/3 0 0 0 2/3/0 0 0 0 2/3/1 0 0 0 2/3/2 0 0 0 2/3/3 0 0 0

CASA CMTS


Example: show cable modem on downstream channel 2/0/0 CASA-CMTS#show cable modem downstream 2/0/0 MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf Status Sid (dB) Offset CPEs Enb 0015.f2fe.9160 10.170.1.9 1/7.0/0 2/0/0 online 282 0.7 2404 0 no 0015.f2fe.98a4 10.170.1.22 1/0.0/0 2/0/0 online 269 -0.5 2404 0 no 0015.f2fe.9ad5 10.170.1.27 1/0.0/0 2/0/0 online 288 1.0 2405 0 no 0015.f2fe.9ad8 10.170.1.31 1/0.0/0 2/0/0 online 279 0.5 2404 0 no 0015.f2fe.ba88 10.170.1.23 1/7.1/0 2/0/0 online 274 0.0 2405 0 no 0015.f2fe.ce86 10.170.1.10 1/0.1/0 2/0/0 online 257 0.5 2405 0 no

Displaying cable modem physical information

To show all the cable modem physical information on all upstream and downstream channels, as well as signal-to-noise ratios:

Step Command Purpose 1 show cable modem phy


Show all the cable modem physical information.

Example: show cable modem physical information CASA-CMTS#show cable modem phy MAC Address US IF DS IF Sid USPwr(dB) USSNR Timing MicroReflec DSPwr DSSNR Mode TX RX (dB) Offset (dBc) (dB) (dB) 0018.4de7.3d2a 11/0.0/0 1/0/0 1 - -0.5 30.8 - - - - tdma c446.199d.fee8 11/0.0/0 1/0/0 5 - 0.7 27.4 - - - - tdma

Showing the cable modem remote-query

To show all the cable modem remote-query information:


1 show cable modem [ mac-address> | <ip-address> | <ipv6-address] remote-query [ verbose ] [ immediate [ community-string <string> ] ] Where:

<mac-address> CM MAC address. <ip-address> <ipv6-address>

CM IPv4 or IPv6 address.

<verbose> Provides detailed information. <immediate> Obtains remote query info directly

from the cable modem when background remote query feature is turned on.

Show all the cable modem remote-query information.

CASA CMTS


<string> SNMP community string to poll the CMs.

To show the cable modem remote information according to the specific upstream:

Step Command Purpose 1 show cable modem remote-query upstream (<x/y> | <x/y/z>)

Where:

<x> Line card slot number. <y> Port number. <z> Channel number for downstream module or logical

channel number for upstream module.

Show the cable modem remote information according to the specific upstream

To show the cable modem remote information according to the specific downstream:

Step Command Purpose 1 show cable modem remote-query downstream (<x/y> |

<x/y/z>) Where:

<x> Line card slot number. <y> Port number. <z> Channel number for downstream module or logical

channel number for upstream module.

Show the cable modem remote information according to the specific downstream.

The commands get all the CM’s MAC-addresses from DDM, and then get the IP-addresses from the CM MAC-addresses, and finally access the CM’s remote information through SNMP communication.

Example: show cable modem remote-query CASA-CMTS>show cable modem remote-query MAC Address IP Address S/N US DS TX Time Micro(dB) Modem Ratio Power Power Offset Reflection State 0015.f2fe.c643 10.160.1.9 36.2 42.4 5.5 2435 7 online

Configuring the remote-query polling interval

To set the remote query polling interval:


1 cable modem remote-query <num=30:1800> [ <string> ] Where:

<num> Number of seconds from 30-1800 seconds (0 = turn off polling).

<string> SNMP community string to poll the CMs

Set the remote query polling interval.

CASA CMTS


Example: Change the community interval to be 1000: CASA-CMTS(config)# cable modem remote-query 1000

Configuring the remote-query loopback interface

To configure the loopback interface as the source IP address to be used with cable modem remote-query functionality, specify the CMTS’ loopback interface number in the range 0 to 15.

To set the remote query CMTS loopback interface:


1 cable modem remote-query loopback <number: 0-15> Where:

<number> Specifies the CMTS internal loopback interface in the range 0 to 15.

Example: Set the CMTS loopback interface for remote query to 10: CASA-CMTS(config)# cable modem remote-query loopback 10

Specify the CMTS loopback interface as the source IP address for remote query.

Displaying the cable modem remote-query with a specified MAC address To show remote information with a specified MAC address:


1 show cable modem <mac_addr> remote-query {(upstream | downstream)(<x/y> | <x/y/z>)} Where:

<mac_addr> MAC address. <x> Line card slot number. <y> Port number.

<z> Channel number for downstream module or logical channel number for upstream module.

Show remote information with a specified MAC address.

CASA CMTS


Example: show cable modem remote-query with a specified MAC Address CASA-C2200(config)#cable modem remote-query 30 CASA-C2200(config)#show cable modem 0015.* remote-query MAC Address IP Address S/N US DS TX Time Micro(dB) Modem Ratio Power Power Offset Reflection State 0015.f2fe.9247 10.160.1.241 39.6 41.1 3.4 2434 11 online 0015.f2fe.baac 10.160.1.223 37.1 38.4 3.1 2436 9 online CASA-C2200(config)#show cable modem 0015.* remote-query upstream 1/1/0 MAC Address IP Address S/N US DS TX Time Micro(dB) Modem Ratio Power Power Offset Reflection State 0015.f2fe.baac 10.160.1.223 37.1 38.4 3.1 2436 9 online

Showing the cable modem remote-query with a specified IP address

To show remote information with a specified IP address:

Step Command Purpose 1 show cable modem <ip_addr> [mask <mask >] remote-query

Where:

<ip_addr> IP address. <mask> Optional mask of IP address.

Show remote information with a specified IP address.

Example: show cable modem remote-query with a specified IP address CASA-CMTS# show cable modem 10.160.1.9 mask 255.255.255.255 remote-query MAC Address IP Address S/N US DS TX Time Micro(dB) Modem Ratio Power Power Offset Reflection State 0015.f2fe.c643 10.160.1.9 36.2 42.4 5.5 2435 7 online

Setting the cable modem flap-list aging interval

Step Command (config) Purpose 1 cable flap-list aging {<num=15:86400> | default}

Where:

<num=15:86400> Period ranged from 15 minutes to 86-400 minutes (60 days). This is the length of period the cable modem can remain in the flap list table.

default Default value of 10-800 minutes (180 hours).

Example: CASA-CMTS(config)# cable flap-list aging 15

Set the cable flap-list aging interval.

CASA CMTS


Accelerating cable modem registration

Sometimes when cable modems come on line slowly, the system will trigger a lot of DOCSIS-events (docsis-log/syslog/trap). These DOCSIS-logs will consume CPU usage and slow modem registration even further. Use the following commands to drop the log messages and reduce CPU usage: CASA-CMTS(config)#cable event priority warning 0x00 0x00 CASA-CMTS(config)#cable event priority notice 0x00 0x00 CASA-CMTS(config)#show cable event notification-policy priority flash-log mem-log traps syslog ------------------------------------------------- emergency yes no yes yes alert yes no yes yes critical yes no yes yes error yes no yes yes warning no no no no notice no no no no informational yes no yes yes debug yes no yes yes

This configuration can be saved to the startup configuration. To turn the messages back on: CASA-CMTS(config)#cable event priority warning <hex> CASA-CMTS(config)#cable event priority notice <hex>

Where <hex>:

0x80 equals messages reported to the local log

0xA0 equals messages reported to the local log and SYSLOG servers

0xC0 equals messages reported to the local log and trap receivers

0xE0 equals messages reported to the local log, SYSLOG servers and trap

Registration can also be accelerated by changing the ranging back off values from the default (0 4) to 4 10. This is especially helpful on channels with 200 or more cable modems.

Registering DOCSIS 2.0 bonding modems

Some DOCSIS 2.0 cable modems will not register if TCC is included in the ranging response. To turn TCC on or off for these modems:


1 [no] cable tcc us-bonding disable Example: CASA-CMTS(config)# cable tcc us-bonding disable CASA-CMTS(config)# no cable tcc us-bonding disable

Turn TCC on or off. The default is off.

CASA CMTS


Enabling the cable modem flap-list trap (Release 5.2)

To enable and disable the cable modem flap-list trap:

Step Command (config) Purpose 1 cable flap-list trap [(enabled | disabled)]

Where:

enabled Enable the cable modem flap list trap.

disabled Disable the cable modem flap list trap. Example: CASA-CMTS(config)#cable flap-list trap enabled

Enable or disable the cable modem flap list.

Enabling the cable modem flap-list trap (Release 5.4)

To enable and disable the cable modem flap-list trap:

Step Command (config) Purpose 1 [no] cable flap-list trap

Example: CASA-CMTS(config)#cable flap-list trap CASA-CMTS(config)#no cable flap-list trap

Enable or disable the cable modem flap list trap.

Configuring a cable modem deny list

Up to 512 cable modems can be specified in a list that denies certain modems from registering with the CMTS. Specify each modem to be denied by the cable modem’s MAC address using the cable modem deny command as follows:

Step Command (config) Purpose 1 [no] cable modem deny <mac_address>

Where:

<mac-address> Specifies the cable modem by MAC address.

Example: CASA-CMTS(config)#cable modem deny 0015.f2fe.cef2

Setup or disable a cable modem deny list.

CASA CMTS


Enabling PacketCable admission control preempt voice priority To enable or disable PacketCable admission-control preempt voice priority:

Step Command (config) Purpose 1 [no] cable admission-control preempt priority-voice

Where:

[no] Disables admission-control preempt voice priority. Example: CASA-CMTS(config)#cable admission-control preempt priority-voice

Enable or disable PacketCable admission control preempt voice priority.

Setting global QoS bandwidth over upstream and downstream interfaces

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>. On upstream interfaces, use the qos bw-reserve command on the upstream port interface. Whenever the requested bandwidth for a service flow is exceeded on either upstream or downstream interfaces, specify the action (accept, reject, or DCC) using the cable qos bw-reserve exceed parameter. To configure the global QoS-profiled traffic bandwidth reserve percentage on upstream and downstream interfaces: Step Command (config) Purpose

1 cable qos bw-reserve <percentage> [upstream | downstream ] cable qos bw-reserve exceed {accept | reject | dcc} Where:

<percentage> Specifies the global 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.

accept Forces the CMTS to accept the QoS-profiled traffic over an upstream or downstream interface, or both, when the reserved bandwidth has been exceeded.

reject Instructs the CMTS to reject the QoS-profiled traffic over an upstream or downstream

Specify global reserve bandwidth percentage for QoS-profiled traffic on upstream and downstream interfaces.

CASA CMTS


interface, or both, when the reserved bandwidth has been exceeded

dcc Instructs the CMTS to perform a DOCSIS channel change (DCC) when the QoS-proficle traffic over an upstream or downstream interface, or both, has exceeded the reserved bandwidth.

Example: In the following example, 80% of the bandwidth on upstream interfaces is globally reserved for QoS-profiled traffic. CASA-CMTS(config)#cable qos bw-reserve 80 upstream

Configuring QoS temporary upstream service flows The cable qos temp-us-sf allows operators to specify and match a temporary upstream service flow using a pre-configured service class (by name) with QoS-defined settings before a cable modem registers with the CMTS. Using the defined service class, this command enables certain cable modems to come online with highest priority during high upstream traffic periods. Step Command (config) Purpose

1 [no] cable qos temp-us-sf <service_class_name> Where:

<service_class_name> Specifies a previously configured service class name.

Example: In the following example, all traffic matching the named service class will be granted a temporary upstream service flow. CASA-CMTS(config)#cable qos temp-us-sf classname

Enable a temporary upstream service flow to allow for high priority cable modems to come online when upstream channels are busy.

See the section “Configuring cable service classes” for additional information.

Enabling cable DSX authorization

When enabled, the CMTS will check all DSX messages (DSA, DSC and DSD) for a valid gate ID authorization value. If the DSX message is invalid, the CMTS rejects the message. Use the no form of the command to disable checking of DSX messages.

CASA CMTS


Step Command (config) Purpose 1 [no] cable dsx authorization

Where:

[no] Disable checking of DSX messages. Example: CASA-CMTS(config)#cable dsx authorization CASA-CMTS(config)#no cable dsx authorization

Enable or disable checking of DSX messages.

Enabling Receive Channel Profile (RCP) fragment support

When enabled, the CMTS will inform registered cable modems that it supports fragmented RCC/RCP TLV packet transmissions if the RCP length exceeds 255. The default setting is disabled (no RCP fragment support). This command operates at the top level of the CLI and in configuration mode.

Step Command (config) Purpose 1 [no] cable mdd rcp fragment support

Where:

[no] Disables RCP fragment support notifications. Example: CASA-CMTS(config)#cable mdd rcp fragment support CASA-CMTS(config)#no cable mdd fragment support

Enable or disable RCP fragment support notifications to registered cable modems.

Controlling CMTS upstream power levels (Rel. 6.1 and later)

The cable mdd extended tx-power support command configures the CMTS to support extended transmission power over upstream channels. Specify 1 to support extended power levels; specify 0 (default) to disable the extended transmission power support feature. This command operates at the CLI top level and in the CMTS configuration mode.

Step Command Purpose 1 [no] cable mdd extended tx-power support [0 | 1]

Where:

0 Disables extended transmission power support. This is the default setting.

1 Enables extended transmission power support.

Enable or disable extended upstream transmission power support at the CMTS.

CASA CMTS


Examples: CASA-CMTS#cable mdd extended tx-power support 0 CASA-CMTS#cable mdd extended tx-power 1

Adjusting modem upstream power levels (Rel. 6.1 and later)

The cable upstream hi-power command sets the cable modem output level to a higher upstream power level specified in decibels per millivolt (dBmV). Specify a value in the range 0 to 6, where 0 (default) specifies the optimum upstream power level, and 6 specifies an increase of 6dB. This command operates in the CMTS configuration mode.

Step Command (config) Purpose 1 [no] cable upstream hi-power <number>

Where:

<number> Specifies the upstream power level in the range 0 to 6 dB, where 0 indicates the optimum power level and 6 indicates a power level increase of 6dB. The default setting is 0.

Examples: Increase upstream modem power by 3dB. CASA-CMTS(config)#cable upstream hi-power 3

Configure modem upstream power level in decibels per millivolt.

Setting the SNR averaging interval The cable upstream snr-interval command sets the time interval for the re-averaging of SNR graphing statistics when there are excessive upstream SNR fluctuations over certain time periods. The CMTS will perform the SNR averaging at the specified time interval in seconds. SNR is observed with the show cable modem phy command. To set the SNR averaging interval:

Step Command (config) Purpose 1 [no] cable upstream snr-interval <seconds>

Where:

<seconds> Specifies the number of seconds to elapse before the CMTS re-averages upstream SNR statistics. Specify a value in the range 0 to 600 seconds.

Configure upstream SNR interval in seconds.

CASA CMTS


Example: To re-average SNR statistics every 60 seconds: CASA-CMTS(config)#cable upstream snr-interval 60

Resetting cable modems and clearing cable modem counters

The clear cable modem command allows you to reset the cable modem upstream and downstream counters to zero, or to reset cable modems using the modem IP or MAC address.


1 clear cable modem <mac_address> counters [downstream | upstream]

clear cable modem <mac_address> reset

clear cable modem <ip_address> reset

clear cable modem <ipv6_address> reset

Where: <mac_address> Specifies the 48-bit hardware address

(MAC address) of an individual CM, or of any CPE devices or hosts behind that CM. If the optional downstream or upstream parameter is specified, then the downstream or upstream counts will be reset respectively.

<ip_address> Specifies the IPv4 address of the modem in 32-bit dotted decimal notation. A.B.C.D

<ipv6_address> Specifies the IPv6 address of the modem in 128-bit notation. xxxx:xxxx:...:xxxx

downstream Specifies clearing of downstream counters only.

upstream Specifies clearing of upstream counters only.

reset Resets the specified cable modem Example: CASA-CMTS(config)#clear cable modem 015.f2fe.cef2

Reset the CM flap-list counters to zero.

If no options are specified, all CM counters will be reset. If a mac-address is specified, only the counters for that cable modem will be reset.

CASA CMTS


Example: clear cable modem counters Clear the counters for the CM at MAC address 0014. 6cb9.ff9f: CASA-CMTS# show cable modem counters MAC Address US Packets US Bytes DS Packets DS Bytes 0004.bd02.5050 9 1582 3 406 0011.e360.5655 0 0 0 0 0011.e62b.6c0f 0 0 0 0 0013.115d.25a2 0 0 0 0 0014.6cb9.ff9f 9 1495 4 927 0015.e9a0.b8c6 44 4480 0 0 0016.ce88.8ab2 0 0 0 0 0017.9a5f.dcf9 0 0 0 0 CASA-CMTS# CASA-CMTS# clear cable modem 0014.6cb9.ff9f counters CASA-CMTS# show cable modem counters MAC Address US Packets US Bytes DS Packets DS Bytes 0004.bd02.5050 9 1582 3 406 0011.e360.5655 0 0 0 0 0011.e62b.6c0f 0 0 0 0 0013.115d.25a2 0 0 0 0 0014.6cb9.ff9f 0 0 0 0 0015.e9a0.b8c6 44 4480 0 0 0016.ce88.8ab2 0 0 0 0 0017.9a5f.dcf9 0 0 0 0 CASA-CMTS#

Clearing offline cable modems immediately

To remove all offline CMs from the show cable modem list, use the clear cable modem offline command:


1 clear cable modem offline Example: CASA-CMTS# clear cable modem offline

Remove all offline CMs from the show cable modem list.

Clearing offline cable modems after aging

The cable modem offline aging command allows you to clear modems that have previously registered with the CMTS but have been offline for a specified number of hours. If set to 0 (default), the modem will maintain an offline state indefinitely and will not be cleared. If set to a value in the range 1 to 8760 hours (1 year), the CMTS will clear all modems that have been offline for the specified number of hours.

CASA CMTS



1 cable modem offline aging <hours> Where:

<hours> 1 to 8760 hours (1 hour to 1 year). Example: CASA-CMTS# cable modem offline aging 10

Remove all offline CMs after the specified aging period.

In the above example, registered cable modems that have been in the offline for 10 hours will be cleared by the CMTS and will reregister with the CMTS when they become available. Use the show cable modem offline command to display the previous modem state and the total time duration of the modem (s) being offline. CASA(config)# show cable modem offline MAC Address US DS Prim Previous Offline Rx RX SM Intf Intf Sid State Time Power SNR Exh.Cnt 0008.0e41.5664 0/3.1/0 1/3/3 61 online 2010-11-13,03:02:30 -0.5 40.4 16 0015.f2fe.9a7e 0/0.0/0 1/2/2 57 online 2010-11-13,03:02:30 -0.5 40.4 16 0015.f2fe.b9fb 0/3.0/0 1/3/2 67 online 2010-11-13,03:02:29 0.0 42.1 16 0015.f2fe.ba58 0/3.1/0 1/2/3 62 online 2010-11-13,03:02:35 0.0 45.1 16 0015.f2fe.c643 0/2.0/0 1/3/0 52 online 2010-11-13,03:02:32 0.2 35.6 16 0015.f2fe.ceb9 0/3.0/0 1/3/1 51 online 2010-11-13,03:02:34 0.0 42.1 16 0022.102b.c609 0/0.1/0 1/2/1 50 online 2010-11-13,03:02:27 0.0 45.1 16 0022.3ace.d9b9 0/0.0/0 1/3/0 54 online 2010-11-13,03:02:35 -0.2 39.1 16 0026.5e77.4463 0/0.1/0 1/3/0 60 online 2010-11-13,03:02:34 0.0 40.4 16 0026.5e77.446c 0/0.1/0 1/2/1 58 online 2010-11-13,03:02:30 0.0 39.1 16

Displaying cable modem vendors

To display up to 512 cable modem vendors:


1 show cable modem [<ip-address> | ipv6-address | <mac-address>] vendor Example: See examples below.

Display cable modem vendor information.

Example: show cable modem vendor CASA-CMTS# show cable modem vendor summary Vendor OUI Cable Modem Total Registered Unregistered Offline ZDT 00:15:f2 1 1 0 0 Motorola 00:20:40 28 28 0 0

Show cable modem vendor details.

CASA CMTS


CASA-CMTS# show cable modem vendor Vendor MAC Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf State Sid (db) Offset CPEs Enb Motorola 0011.802c.43fe 3/4/0 1/0/0 online 2 -2.0 889 0 no Motorola 0013.7163.0f92 3/4/0 1/0/0 online 9 -2.0 882 0 no Motorola 0013.7163.3ea2 3/0/0 1/0/0 online 1 -3.2 840 0 no Motorola 0013.7163.6980 3/4/0 1/0/0 online 24 -1.7 895 0 no Motorola 0013.716c.e0de 3/4/0 1/0/0 online 61 -1.7 838 0 no Motorola 0013.716c.f33e 3/4/0 1/0/0 online 19 -1.5 876 0 no Motorola 0013.716d.72a6 3/0/0 1/0/0 online 7 -2.7 878 0 no Motorola 0013.7176.d8f4 3/4/0 1/0/0 online 5 -2.0 871 0 no Motorola 0013.7176.ef86 3/4/0 1/0/0 online 62 -1.2 850 0 no Motorola 0013.7176.f8e6 3/4/0 1/0/0 online 63 -1.5 885 0 no Motorola 0013.7178.0812 3/4/0 1/0/0 online 25 -1.2 877 0 no

Displaying vendor-specific information on cable modems

To display vendor information of a specific cable modem:


1 show cable modem [<mac_address> | <ip_address> | ipv6_address] vendor Where:

<mac_address> Cable modem MAC address in the format xxxx.xxxx.xxxx.

<ip_address> <ipv6_address>

IPv4 or IPv6 cable modem address.


Display cable modem vendor information.

Example: show vendor information CASA-CMTS#show cable modem 0015.f2fe.c904 vendor Vendor MAC Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf State Sid (db) Offset CPEs Enb ZDT 0015.f2fe.c904 1/6/0 0/2/0 online 10 1.7 2180 0 no

CASA CMTS


Adding and modifying cable modem vendor information

To add user-defined cable modem vendor information or to modify the system default CM vendor:


1 cable modem vendor <vendor_id> <string> Where:

<vendor_id> Organizational Unique Identifier. xx:xx:xx

<string> Vendor-name. If spaces are included in the vendor name, enclose the string in quotation marks (“”).

Example: CASA-CMTS# cable modem vendor 00:00:00 ABC

Add a user defined cable modem vendor information.

Deleting cable modem vendor information

To delete a user defined cable modem vendor:

Step Command (config) Purpose 1 no cable modem vendor <vendor_id>

Where:

<vendor_id> Organizational Unique Identifier. xx:xx:xx Example: CASA-CMTS(config)# no cable modem vendor 0:00:00

Delete a user defined cable modem vendor.

Displaying vendor OUI information

To show the vendor OUI information:


1 show cable modem vendor [config | all | default | summary] Where:

config Show the user config OUI information.

all Show all OUI information.

default Show the default OUI database.

summary Show abbreviated information only. Example:

Show the vendor OUI information.

CASA CMTS


CASA-CMTS#show cable modem vendor all system default cm vendor database: cable modem vendor 00:0f:9f "Motorola" cable modem vendor 00:11:1a "Motorola" cable modem vendor 00:11:80 "Motorola" cable modem vendor 00:12:25 "Motorola" cable modem vendor 00:13:71 "Motorola" cable modem vendor 00:14:e8 "Motorola" cable modem vendor 00:18:c0 "Motorola" cable modem vendor 00:1a:ad "Motorola" cable modem vendor 00:1b:dd "Motorola" cable modem vendor 00:0f:21 "Sci Atl" cable modem vendor 00:11:e6 "Sci Atl" cable modem vendor 00:14:f8 "Sci Atl" cable modem vendor 00:16:92 "Sci Atl" cable modem vendor 00:18:68 "Sci Atl" cable modem vendor 00:19:47 "Sci Atl" cable modem vendor 00:1c:ea "Sci Atl" user config cm vendor: cable modem vendor 00:26:5e "Ubee" cable modem vendor 00:20:40 "Moto"

Example: show cable modem vendor summary CASA-CMTS# show cable modem vendor summary Vendor OUI Cable Modem Total Registered Unregistered Offline ZDT 00:15:f2 1 1 0 0 Motorola 00:20:40 28 28 0 0

Setting the default cable modem vendor

To set the system default vendor to default value after modifying them:

Step Command (config) Purpose 1 default cable modem vendor <vendor_id>

Where:

<vendor_id> Organizational Unique Identifier. xx:xx:xx

Example: Set 00:0f:9f to default value after modifying it CASA-CMTS(config)#show cable modem vendor default cable modem vendor 00:0f:9f "Motorola" cable modem vendor 00:11:1a "Motorola" cable modem vendor 00:11:80 "Motorola" CASA-CMTS(config)#cable modem vendor 00:0f:9f ABC CASA-CMTS(config)#show cable modem vendor all system default cm vendor database:

Set the system default vendor to default value.

CASA CMTS


cable modem vendor 00:0f:9f "Motorola" cable modem vendor 00:11:1a "Motorola" user config cm vendor: cable modem vendor 00:0f:9f "ABC" CASA-CMTS(config)#default cable modem vendor 00:0f:9f CASA-CMTS(config)#show cable modem vendor all system default cm vendor database: cable modem vendor 00:0f:9f "Motorola" cable modem vendor 00:11:1a "Motorola" cable modem vendor 00:11:80 "Motorola”

Displaying cable modem classifiers

To show classifiers in the configuration file that the CM is using:

Step Command Purpose 1 show cable modem [<mac-address> | <ip_address> | <ipv6-

address>] classifiers Where:

<mac-address> Specifies the cable modem MAC address in the format xxxx.xxxx.xxxx.

<ip_address> Specifies the cable modem IPv4 or IPv6 address.


Show classifiers in the config file.

Example: show cable modem classifiers CASA-CMTS# show cable modem 0050.f112.b764 classifiers CM Mac Address: 0050.f112.b764 Classifier ID: 3 ServiceFlow ID: 514 Direction: Upstream Rule Priority: 20 Activation State: Active IP classifiers: ToS: 0x00 0x00 0x00 Protocol: 17 Source Address: 0.0.0.0 Source Mask: 255.255.255.255 Destination Address: 0.0.0.0 Destination Mask: 255.255.255.255 Source Port Start: 0 Source Port End: 65535 Destination Port Start: 0 Destination Port End: 65535 LLC classifiers: Destination Mac Address: 0000.0000.0000 Destination Mac Mask: 0000.0000.0000

CASA CMTS


Source Mac Mask: 0000.0000.0000 Ether Type: 0x00 User Priority Low: 0x0 User Priority High: 0x0 Vlan ID: 0x0 Bit Map: 0xb CM Interface Mask: 0x00.00.00.00 Classifier ID: 2 ServiceFlow ID: 639 Direction: Upstream Rule Priority: 10 Activation State: Active IP classifiers: ToS: 0x00 0x00 0x00 Protocol: 256 Source Address: 0.0.0.0 Source Mask: 255.255.255.255 Destination Address: 0.0.0.0 Destination Mask: 255.255.255.255 Source Port Start: 0 Source Port End: 65535 Destination Port Start: 0 Destination Port End: 65535 LLC classifiers: Destination Mac Address: 0000.0000.0000 Destination Mac Mask: 0000.0000.0000 Source Mac Mask: 0000.0000.0000 Ether Type: 0x00 User Priority Low: 0x0 User Priority High: 0x0 Vlan ID: 0x0 Bit Map: 0xb CM Interface Mask: 0x00.00.00.00 Classifier ID: 5 ServiceFlow ID: 641 Direction: Down Rule Priority: 20 Activation State: Active IP classifiers: ToS: 0x00 0x00 0x00 Protocol: 17 Source Address: 0.0.0.0 Source Mask: 255.255.255.255 Destination Address: 0.0.0.0 Destination Mask: 255.255.255.255 Source Port Start: 0 Source Port End: 65535 Destination Port Start: 0 Destination Port End: 65535 LLC classifiers: Destination Mac Address: 0000.0000.0000 Destination Mac Mask: 0000.0000.0000 Source Mac Mask: 0000.0000.0000 Ether Type: 0x00 User Priority Low: 0x0

CASA CMTS


User Priority High: 0x0 Vlan ID: 0x0 Bit Map: 0xb Classifier ID: 4 ServiceFlow ID: 767 Direction: Down Rule Priority: 10 Activation State: Active IP classifiers: ToS: 0x00 0x00 0x00 Protocol: 256 Source Address: 0.0.0.0 Source Mask: 255.255.255.255 Destination Address: 0.0.0.0 Destination Mask: 255.255.255.255 Source Port Start: 0 Source Port End: 65535 Destination Port Start: 0 Destination Port End: 65535 LLC classifiers: Destination Mac Address: 0000.0000.0000 Destination Mac Mask: 0000.0000.0000 Source Mac Mask: 0000.0000.0000 Ether Type: 0x00 User Priority Low: 0x0 User Priority High: 0x0 Vlan ID: 0x0 Bit Map: 0xb

Showing cable modem errors

To show cable modem error information, such as CRC and HCS:

Step Command Purpose 1 show cable modem [<mac_addrress> | <ip_address> | <ipv6-

address>] errors Where:

<mac-address> Cable modem MAC address in the format xxxx.xxxx.xxxx

<ip_address> Cable modem IP address in the format A.B.C.D.

Example: See sample output below.

Show cable modem errors in the config file.

CASA CMTS


Example: showing cable modem errors C2800#show cable modem errors MAC Address US Intf DS Intf CRC HCS 0008.0d55.da42 1/3/0 0/0/1 0 0 0015.f2fe.bea2 1/3/0 0/0/3 0 0 0050.f112.b764 1/3/0 0/0/1 0 0

Displaying cable modem MAC information

To show cable modem MAC information, such as the version number:

Step Command Purpose 1 show cable modem [<mac_address> | <ip_address> |

ipv6_address>] mac

Where: <mac_address> Cable modem MAC address in the format

xxxx.xxxx.xxxx

<ip_address> Cable modem IPv4 or IPv6 address Example: See example below.

Display cable modem MAC information.

Example: show cable modem mac information CASA-C3000(config)#show cable modem upstream 4/1.1/0 mac MAC Address MAC Prim Ver QoS Frag Concat PHS Priv DS US State Sid Prov Saids Sids 0004.bd04.c1d8 online 17 DOC1.1 DOC1.1 YES YES YES BPI 0 1 0005.caa3.d65c online 22 DOC3.0 DOC1.1 YES YES YES BPI 0 1 000e.5c69.0188 online 6 DOC1.1 DOC1.1 YES YES YES BPI 0 1 0011.8054.3af2 online 9 DOC2.0 DOC1.1 YES YES YES BPI 0 1 0012.c99f.700a online 10 DOC2.0 DOC1.1 YES YES YES BPI 0 1 0026.5e77.43ba online 27 DOC3.0 DOC1.1 YES YES YES BPI 0 1 0026.5e77.43ce online 24 DOC3.0 DOC1.1 YES YES YES BPI 0 1 0026.5e77.446e online 21 DOC3.0 DOC1.1 YES YES YES BPI 0 1 CASA-C3000(config)#

CASA CMTS


Displaying cable modem spoof information

To show spoof information of the cable modem during ranging.


upstream < X/Y.C/Z>] rogue

Where: <mac_address> Cable modem MAC address in the format

xxxx.xxxx.xxxx

<ip_address> Cable modem IP address in the format A.B.C.D.

< X/Y.C/Z > X - slot, Y - port (0-7), C - upstream physical channel(0-1), Z - upstream logical channel(0-1)

Example: See sample output below.

Show spoof information of the cable modem during ranging.

Example: show cable modem spoof information CASA-CMTS#show cable modem rogue MAC Address Vendor US Intf Ds Intf Spoof Count Dynamic Secret 0011.8078.1950 - 3/0/0 0/0/0 4 ba052c3991df6a933fa2c857f9654104 0013.7192.5b04 - 3/2/0 0/0/0 5 ba052c3991df6a933fa2c857f9654104

Displaying cable modem maintenance ranging information

To show CM maintenance ranging information:


ipv6_address] maintenance Where:

<mac_address> Cable modem MAC address in the format xxxx.xxxx.xxxx.

<ip_address> <ipv6_address>

Cable modem IPv4 or IPv6 address.


Show CM maintenance ranging information.

CASA CMTS


Example: show cable modem maintenance ranging information CASA-CMTS#show cable modem maintenance MAC Address US Intf Ds Intf Prim SM Fail Active-Time Sid Count Count 0015.f2fe.c763 1/0/0 0/1/0 2 42 0 2009-06-30,16:16:00 0015.f2fe.cee6 1/0/0 0/1/1 1 43 0 2009-06-30,16:15:58 0015.f2fe.cef2 1/2/0 0/1/1 3 44 0 2009-06-30,16:16:02

Displaying denied cable modem

To show CM that are added to the deny list.

Step Command Purpose 1 show cable modem deny

Example: CASA-CMTS# show cable modem deny cable modem deny 0015.f2fe.cee6

Show CM that are added to the deny list.

Displaying the cable modem MAC summary

To show CM MAC layer information summary:

Step Command Purpose 1 show cable modem mac [downstream] summary


Show CM Mac layer information summary.

Example: show cable modem mac summary CASA-CMTS# show cable modem mac downstream summary Mac Version QoS Provision Mode Interface Total DOC3.0 DOC2.0 DOC1.1 DOC1.0 Register DOC2.0 DOC1.1 DOC1.0 0/0/0 0 0 0 0 0 0 0 0 0 0/0/1 0 0 0 0 0 0 0 0 0 0/0/2 0 0 0 0 0 0 0 0 0 0/0/3 0 0 0 0 0 0 0 0 0 0/1/0 0 0 0 0 0 0 0 0 0 0/1/1 0 0 0 0 0 0 0 0 0 0/1/2 0 0 0 0 0 0 0 0 0 0/1/3 0 0 0 0 0 0 0 0 0 0/2/0 1 0 1 0 0 1 0 1 0 0/2/1 0 0 0 0 0 0 0 0 0

CASA CMTS


0/2/2 0 0 0 0 0 0 0 0 0 0/2/3 0 0 0 0 0 0 0 0 0 0/3/0 0 0 0 0 0 0 0 0 0 0/3/1 0 0 0 0 0 0 0 0 0 0/3/2 0 0 0 0 0 0 0 0 0 0/3/3 0 0 0 0 0 0 0 0 0 Total: 1 0 1 0 0 1 0 1 0

Displaying the cable modem status event report

To show the CM status event report for each DOCSIS-MAC interface, first enter DOCSIS-MAC config mode and define the event:

Step Command (config) Purpose 1 interface docsis-mac <dsm_id>

Where:

<grp_id> Docsis-mac ID Example: CASA-CMTS(config)# interface docsis-mac 1 CASA-CMTS(conf-if-mac 1)#

Enter docsis-mac configuration mode.

2 cable cm-status event <a> max-timer <b> max-number <c> Where:

<a> Specifies the event code; valid values are 1-10

<b> Maximum Event Holdoff Timer

<c> Timer value units in 20 milliseconds; valid values are 0-255.

Define the event.

3 cable cm-status report event-list <string> Where:

<string>

The list of events in the format: 1,2,3 . . . ; valid values are 1-10.

Run the report.

4 show interface docsis-mac <id> Example: CASA-CMTS(config)# show interface docsis-mac 1 cable cm-status report event-list 5 cable cm-status event 1 max-timer 1500 max-number 35

Check configured cm-status.

CASA CMTS


Displaying cable modem quality-of-service (QOS)

The show cable modem qos command displays quality-of- service (QOS) information associated with one or more cable modems. For QOS information relating to a specific cable modem, specify the IP or the MAC address. Use the show cable modem qos command to display the average number of service ID (SIDs) per cable modem.


1 show cable modem [<ip-address> | ipv6-address | <mac-address>] qos [verbose] Where:

mac-address Optional. Specifies the MAC address of the target cable modem.


Optional. Specifies the IP address of the target cable modem.

verbose Optional. Provides detailed information associated with each cable modem service flow.

Example: CASA-CMTS(config)#show cable modem qos

Display QOS information associated with the specified cable modem, or all cable modems.

Example: show cable modem qos CASA-CMTS> show cable modem qos

Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput

State Type (kbps) (kbps) (kbps)

Mac Addr : 0012.c99f.700a

Mac Addr : 0050.f112.b329

383 US act 1 BE 0 0 3044 0 0

511 DS act N/A UNDEF 0 0 3044 0 0

To display the total number of SIDs currently in use, enter the show cable modem qos command with the count-only output modifier.

Example: show cable modem qos | count-only <string> CASA-C3000> show cable modem qos | count-only "us act"

Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst MinRsvRate Throughput

State Type (kbps) (kbps) (kbps)

Count Line: 9854

CASA CMTS


Displaying the cable modem docsis-mac summary

The show cable modem docsis-mac command displays the cable modems belonging to the specified DOCSIS MAC interface.


1 show cable modem docsis-mac <domain-id> Where:

<domain-id> Specifies the MACdomain ID in the range 1 to 32.

Example: CASA-CMTS(config)#show cable modem docsis-mac 1

Display cable modem information associated with the specified DOCSIS MAC interface at the CMTS.

Example: show cable modem docsis-mac

CASA-CMTS> show cable modem docsis-mac 1

MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI

Intf Intf Status Sid (dB) Offset CPEs Enb

0012.c99f.700a 0.0.0.0 5/1.1/0 0/0/1 offline 0 0.0 0 0 no

0050.f112.b329 10.230.1.145 5/1.0/0* 0/0/0* online(pt) 1 0.0 2442 0 yes

c0cb.38d3.6e74 0.0.0.0 5/1.0/0 0/0/0 init(r2) 206 6.2 2391 0 no

CASA-C3000>

To display the total number of SIDs currently in use over the specified MAC domain, enter the show cable modem docsis-mac ommand with the count-only output modifier.

Example: show cable modem docsis-mac <id> | count-only <string> CASA-CMTS> show cable modem docsis-mac 1 | count-only online

MAC Address IP Address US DS MAC Prim RxPwr

Timing Num BPI

Intf Intf Status Sid (dB)

Offset CPEs Enb

Count Line: 515

CASA CMTS


Enabling/disabling cable modem host authorization

To enable or disable cable modem host authorization:

Step Command (config) Purpose 1 [no] cable host authorization <mac_address> <ip_address>

Where:

<mac_address> CPE MAC address in the format xxxx.xxxx.xxxx.

<ip_address> IP address in the format A.B.C.D. Example: CASA-CMTS(config)# cable host authorization 0015.f2fe.8d6a 10.160.1.40 CASA-CMTS(config)# Disable cable modem host authorization: CASA-CMTS(config)# no cable host authorization 0015.f2fe.8d6a 10.160.1.40 CASA-CMTS(config)#

Enable or disable cable modem host authorization.

Displaying the cable host authorization

To show trusted host configuration:

Step Command Purpose 1 show cable host authorization

Example: CASA-CMTS(config)#show cable host authorization cable host authorization 0015.f2fe.8d6a 10.160.1.40

Show the cable host configuration.

Subscriber management

Casa CMTS supports Subscriber Management features defined in DOCSIS 3.0. This section describes how to use CLI commands to configure those features. It covers the following operations:

CM controls (Rel. 6.0.3 and earlier) x Enabling subscriber management. x Setting a mode for the CM to learn the CPE IP address without DHCP. x Setting maximum ipv4 CPEs behind the CM. x Setting maximum ipv6 CPEs behind the CM. x Removing all CPEs behind the CM.

CASA CMTS


Default settings x Default settings if cable modem configuration file does not specify otherwise

Filters x Setting filter rule x Removing all IP and TCP-UDP filters

Enabling subscriber management

To enable subscriber management on a CM after it is registered:


1 docsis submgt cm-control cm <cm_id> active true docsis submgt cm-control cm <cm_id> active false Where:

<cm_id> CM ID as defined and distributed by the CMTS as an identifier. Use the show cable modem and then use the show qos ds cm qam command with the cm_id modifier. The identifier can also be retrieved by walking the MIB entry docsIfCmtsCmStatusMacAddress

Example: CASA-CMTS(config)#docsis submgt cm-control cm 1 active true

Enable or disable subscriber management on a CM.

Example: Enabling subscriber management CASA-CMTS# show cable modem MAC Address IP Address US DS MAC Prim RxPwr Timing Num BPI Intf Intf Status Sid (dB) Offset CPEs Enb 0005.caa3.c38c 10.160.1.250 1/1/0* 2/0/1* online 40 0.5 2443 0 yes 0015.f2fe.9247 10.160.1.241 1/2/0 2/0/0 online 36 0.2 2432 0 yes 0015.f2fe.baac 10.160.1.223 1/2/0 2/0/2 online 37 0.2 2437 0 yes 0020.4058.c984 10.160.1.251 1/3/0 2/0/3 online 39 0.0 1674 0 yes 0026.5e77.43aa 10.160.1.252 1/1/0* 2/0/2* online 38 0.0 2392 0 yes online cm 5 ; offline cm 0 ; ranging cm 0 CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.252 | i cm_id nx=0 ty= 1 lc= 2 mc=0000 pcnt= 6 ir=1 0 0 10.160.1.252 00265e7743aa cm_id=5 cid=2 cm_tbl_idx= 16 cm_id=5 cid= 2 psid=38 v=3 00265e7743aa tek=02af3628 CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.251 | i cm_id nx=0 ty= 1 lc= 2 mc=0000 pcnt= 10 ir=1 0 0 10.160.1.251 00204058c984 cm_id=4 cid=3 cm_tbl_idx= 17 cm_id=4 cid= 3 psid=39 v=0 00204058c984 tek=00000000 CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.223 | i cm_id nx=0 ty= 1 lc= 2 mc=0000 pcnt= 4 ir=1 0 0 10.160.1.223 0015f2febaac cm_id=3 cid=2 cm_tbl_idx= 15 cm_id=3 cid= 2 psid=37 v=0 0015f2febaac tek=02af36a8 CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.241 | i cm_id nx=0 ty= 1 lc= 2 mc=0000 pcnt= 4 ir=1 0 0 10.160.1.241 0015f2fe9247 cm_id=6 cid=0 cm_tbl_idx= 14 cm_id=6 cid= 0 psid=36 v=0 0015f2fe9247 tek=02af36e8

CASA CMTS


CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.250 | i cm_id nx=0 ty= 1 lc= 2 mc=0000 pcnt= 4 ir=1 0 0 10.160.1.250 0005caa3c38c cm_id=1 cid=1 cm_tbl_idx= 18 cm_id=1 cid= 1 psid=40 v=3 0005caa3c38c tek=02af3668 CASA-CMTS(config)#docsis submgt cm-control cm 1 active true CASA-C2200#show qos ds cm qam 2 ip address 10.160.1.250 | i cm_id nx=0 ty= 1 lc= 2 mc=0000 pcnt= 4 ir=1 0 0 10.160.1.250 0005caa3c38c cm_id=1 cid=1 cm_tbl_idx= 18 cm_id=1 cid= 1 psid=40 v=3 0005caa3c38c tek=02af3668 CASA-C2200(config)#show docsis submgt cm 1 module 2 Submgt Active = 1 Submgt Learnable = 1 Submgt Max IP = 10 Downstream Filter Entry 0 = 0 Upstream Filter Entry 0 = 0 Downstream Filter Entry 1 = 0 Upstream Filter Entry 1 = 0 Downstream Filter Entry 2 = 0 Upstream Filter Entry 2 = 0 Downstream Filter Entry 3 = 0 Upstream Filter Entry 3 = 0 Downstream Filter Entry 4 = 0 Upstream Filter Entry 4 = 0

Setting the mode for a CM to learn the CPE IP address without DHCP (Rel. 6.0.3 and earlier) To set or unset the mode for a CM to learn the CPE IP address:

Step Command (config) Purpose 1 docsis submgt cm-control cm <cm_id> learnable true

docsis submgt cm-control cm <cm_id> learnable false Where:

<cm_id> CM ID as defined and distributed by the CMTS as an identifier. Use the show cable modem and then use the show qos ds cm qam command with the cm_id modifier. The identifier can also be retrieved by walking the MIB entry docsIfCmtsCmStatusMacAddress.

Example: CASA-CMTS(config)#docsis submgt cm-control cm 1 learnable true

Set or unset the mode for a CM to learn the CPE IP address.

Setting maximum IPv4 CPEs behind a CM (Rel. 6.0.3 and earlier)

To set maximum IPv4 CPEs:

Step Command (config) Purpose 1 docsis submgt cm-control cm <cm_id> max-cpe-ip <num>

Where:

Set maximum IPv4 CPEs.

CASA CMTS


<num> Maximum number of IPv4 CPEs behind the cable modem in the range 0 to 1023.

Example: CASA-CMTS(config)#docsis submgt cm-control cm 1 max-cpe-ip 10

Setting maximum IPv6 CPEs behind a CM (Rel. 6.0.3 and earlier)

To set max ipv6 CPEs:

Step Command (config) Purpose 1 docsis submgt cm-control cm <cm_id> max-cpe-ipv6-prefix

<num> Where:

<num> Maximum number of IPv6 CPEs behind a CM; values are 0 to 1023.

Example: CASA-CMTS(config)#docsis submgt cm-control cm 1 max-cpe-ipv6-prefix 10

Set maximum IPv6 CPEs.

Resetting IP addresses of all CPEs behind a CM (Rel. 6.0.3 and earlier) To reset learnable IP addresses of CPEs behind a CM:

Step Command (config) Purpose 1 docsis submgt cm-control cm <cm_id> reset

Where:


Reset learnable IP addresses of CPEs behind a CM.

Using the subscriber management default settings

Each cable modem will receive subscriber management default settings from the CMTS if the modem configuration file does not specify otherwise.

CASA CMTS


CASA-CMTS(config)#docsis submgt default active [on|off] CASA-CMTS(config)#docsis submgt default learnable [on|off] CASA-CMTS(config)#docsis submgt default max-ip <0-1023> CASA-CMTS(config)#docsis submgt default max-ipv6-prefix <0-1023> CASA-CMTS(config)#docsis submgt default cm-filter-downstream <0-65535> CASA-CMTS(config)#docsis submgt default cm-filter-upstream <0-65535> CASA-CMTS(config)#docsis submgt default cpe-filter-downstream <0-65535> CASA-CMTS(config)#docsis submgt default cpe-filter-upstream <0-65535> CASA-CMTS(config)#docsis submgt default mta-filter-downstream <0-65535> CASA-CMTS(config)#docsis submgt default mta-filter-upstream <0-65535> CASA-CMTS(config)#docsis submgt default stb-filter-downstream <0-65535> CASA-CMTS(config)#docsis submgt default stb-filter-upstream <0-65535> CASA-CMTS(config)#docsis submgt default ps-filter-downstream <0-65535> CASA-CMTS(config)#docsis submgt default ps-filter-upstream <0-65535> To specify the DOCSIS subscriber management defaults:


1 docsis submgt default <option> Where <option> is one of the following:

active Turns DOCSIS subscriber management either ON or OFF. The default is OFF.

learnable Allows the cable modem to learn its IP address. The default is ON.

max-ip Sets the maximum number of customer premises equipment (CPE) IP addresses that can be allowed for each cable modem connected to the CMTS. Enter a number in the range 0 to 1023. The default setting is 16 IP addresses to indicate a maximum of 16 CPE devices connected to each modem.

max-ipv6-prefix Sets the maximum number of IPV6 prefixes that can be allowed for each cable modem connected to the CMTS. Enter a number in the range 0 to 1023. The default setting is 16 prefixes.

cm-filter-downstream

Specifies the packet filter group ID to be applied to CM downstream traffic in the range 0 to 65535. The default setting is 0.

cm-filter-upstream Specifies the packet filter group ID to be applied to CM upstream traffic in the range 0 to 65535. The default setting is 0.

cpe-filter-upstream Specifies the packet filter group ID to be applied to upstream traffic from customer premise equipment (CPE) devices in the range 0 to 65535. The default setting is 0.

cpe-filter-downstream

Specifies the packet filter group ID to be applied to downstream traffic to CPE

Configures subscriber management default settings to be sent to registered cable modems.

CASA CMTS


devices in the range 0 to 65535. The default setting is 0.

mta-filter-upstream Specifies the packet filter group ID to be applied to upstream traffic from multimedia terminal adapter (MTA) devices in the range 0 to 65535. The default setting is 0.

mta-filter-downstream

Specifies the packet filter group ID to be applied to downstream traffic to MTA devices in the range 0 to 65535. The default setting is 0.

stb-filter-upstream Specifies the packet filter group ID to be applied to upstream traffic from set-top box (STB) devices in the range 0 to 65535. The default setting is 0.

stb-filter-downstream

Specifies the packet filter group ID to be applied to downstream traffic to STB devices in the range 0 to 65535. The default setting is 0.

ps-filter-upstream Specifies the packet filter group ID to be applied to upstream traffic from portal server (PS) devices in the range 0 to 65535. The default setting is 0.

ps-filter-downstream Specifies the packet filter group ID to be applied to downstream traffic to PS devices in the range 0 to 65535. The default setting is 0.

Displaying the DOCSIS subscriber management defaults

To display the DOCSIS subscriber management defaults:

Step Command Purpose 1 show docsis submgt default

Example: CASA-CMTS (config) #show docsis submgt default docsis submgt default active on docsis submgt default max-ip 16 docsis submgt default max-ipv6-prefix 16 docsis submgt default learnable on docsis submgt default cm-filter-downstream 0 docsis submgt default cm-filter-upstream 0 docsis submgt default cpe-filter-downstream 0 docsis submgt default cpe-filter-upstream 0 docsis submgt default ps-filter-downstream 0 docsis submgt default ps-filter-upstream 0 docsis submgt default mta-filter-downstream 0 docsis submgt default mta-filter-upstream 0 docsis submgt default stb-filter-downstream 0 docsis submgt default stb-filter-upstream 0

Display DOCSIS subscriber management defaults.

CASA CMTS


Setting a filter rule

To enter a filter rule:


1 docsis submgt ip-filter <filter_group> <filter_index> [accept | deny] [src-ip <ip_address> <ip_mask>] [dst-ip <ip_addr> <ip_mask>] [tos <tos_high> <tos_low> <tos_mask>] [ protocol <0-257>] [src-port <0-65535>] [dst-port <0-65535>] [cm-intf-mask <bitmap>] Where:

<filter_group> Filter group, 1-65535 <filter_index> Filter index, 1-65535 <bitmap> bitmask, 0-ffffff

Enter a filter rule.

Removing all IP and TCP-UDP filters

To remove all IP and TCP-UDP filters in the system:


1 docsis submgt filters clear-all Removes all IP and TCP-UDP filters.

Displaying IP filters

To display IP filters:

Step Command Purpose 1 show docsis submgt ip-filter [<cm_id>]

Where:

<cm_id> Cable modem ID as defined and distributed by the CMTS as an identifier. Use the show cable modem and then use the show qos ds cm qam command with the cm_id modifier. The identifier can also be retrieved by walking the MIB entry docsIfCmtsCmStatusMacAddress

Display the IP filter.

Example: Displaying the IP filter CASA-CMTS#show docsis submgt ip-filter Group Index Accept Src Ip Mask Dst Ip Mask UIP TOSlo TOShi TOSMask Hit Cnt 1 1 1 0.0.0.0 0.0.0.0 10.200.3.5 255.255.255.255 10 0 255 0 0

CASA CMTS


Displaying cable modem information (Rel. 6.0.3 and earlier)

To display cable modem information under subscriber management:


1 show docsis submgt cm <cm_id> module <module_num> Where:


<module_num> CMTS module slot location Example: CASA-CMTS# show docsis submgt cm 1 module 2 Submgt Active = 0 Submgt Learnable = 1 Submgt Max IP = 16 Downstream Filter Entry 0 = 0 Upstream Filter Entry 0 = 0 Downstream Filter Entry 1 = 0 Upstream Filter Entry 1 = 0 Downstream Filter Entry 2 = 0 Upstream Filter Entry 2 = 0 Downstream Filter Entry 3 = 0 Upstream Filter Entry 3 = 0 Downstream Filter Entry 4 = 0 Upstream Filter Entry 4 = 0

Display cable modem information under subscriber management.

Displaying the cable modem control table (Rel. 6.0.3 and earlier)

To display cable modem control table:

Step Command Purpose 1 show docsis submgt cm-control cm <cm_id>

Where:


Example: CASA-CMTS# show docsis submgt cm-control cm 1 cm=1 maxCpe IPv4=16 IPv6=16 active=false learnable=true reset=0 numOfCpeIp=0

Display the cable modem control table.

CASA CMTS


Displaying CPE information (Rel. 6.0.3 and earlier)

To display CPE information behind a modem under subscriber management:

Step Command Purpose 1 show docsis submgt cm-cpe-ip cm <cm_id>

Where:


Example: CASA-CMTS#show docsis submgt cm-cpe-ip cm 3

Display CPE information behind a modem under subscriber management.

Configuring MPEG Compliant Features

The MPEG standard requires that the Casa CMTS system generate Program Association Tables (PAT) and Program Mapping Tables (PMT), and then insert them into MPEG transport streams. This section covers commands for the following PAT and PMT operations: x Setting the PAT insertion interval x Setting the PMT insertion interval

Setting the PAT insertion interval

To set the PAT insertion interval:

Step Command (config) Purpose 1 pat interval <time>

Where:

<time> PAT insertion interval in the range 100 to 1000 ms. Default value is 250.

Example: Set the PAT insertion interval to 500 ms: CASA-CMTS(config)# pat interval 500 CASA-CMTS# show running-config | i pat pat interval 500

Set and verify the PAT insertion interval.

CASA CMTS


Setting the PMT insertion interval

To set the PAT insertion interval:

Step Command (config) Purpose 1 pmt interval <time>

Where:

<time> PMT insertion interval in the range 100 to 1000 ms. Default value is 250.

Example: Set the PMT insertion interval to 500 ms: CASA-CMTS(config)# pmt interval 500 CASA-CMTS# show running-config | i pmt pmt interval 500

Set and verify the PMT insertion interval.

Configuring DVB-compliant features

The Casa CMTS supports the DVB standard. The DVB standard requires the generation of Service Information (SI) tables and insertion of them into MPEG transport streams. This section covers commands for the following SI table operations: x Enabling/disabling SI table generation and insertion

x Setting the network ID

x Setting the channel transport stream ID

Enabling SI table generation and insertion

The SI table contains four sub-tables: EIT (Event Information Table), NIT (Network Information Table), SDT (Service Description Table), and TDT (Time of Day Table). Each of the four tables can be turned on or off individually. The default setting is disabled for each of four tables.

SI table generation and insertion setting is chassis based. When enabled, it applies to all QAM downstream channels on the chassis.

CASA CMTS


To enable or disable EIT:

Step Command (config) Purpose 1 [no] si generator eit

Example: CASA-CMTS(config)# si generator eit CASA-CMTS(config)# no si generator eit To check the configured generator: CASA-CMTS(config)# show running-config | i generator

Enable or disable EIT.

To enable or disable NIT:

Step Command (config) Purpose 1 [no] si generator nit

Example: CASA-CMTS(config)# si generator nit CASA-CMTS(config)# no si generator nit To check the configured generator: CASA-CMTS(config)# show running-config | i generator

Enable or disable NIT.

To enable or disable SDT:

Step Command (config) Purpose 1 [no] si generator sdt

Example: CASA-CMTS(config)# si generator sdt CASA-CMTS(config)# no si generator sdt To check the configured generator: CASA-CMTS(config)# show running-config | i generator

Enable or disable SDT.

CASA CMTS


To enable or disable TDT:

Step Command (config) Purpose 1 [no] si generator tdt

Example: CASA-CMTS(config)# si generator tdt CASA-CMTS(config)# no si generator tdt To check the configured generator: CASA-CMTS(config)# show running-config | i generator

Enable or disable TDT.

To enable or disable TOT:

Step Command (config) Purpose 1 [no] si generator tot

Example: CASA-CMTS(config)# si generator tdt CASA-CMTS(config)# no si generator tdt To check the configured generator: CASA-CMTS(config)# show running-config | i generator

Enable or disable TOT.

Setting the network ID

The Network ID is needed in SI table generation. The network ID setting is based on the QAM downstream channel. To set a network ID:


Where:

<x/y> x=QAM module number; y=QAM port number Example: CASA-CMTS(config)# interface qam 0/4 CASA-CMTS(config-if-qam)#

Specifies the QAM module number and port.

2 channel <ch-id> network id <net-id> Where:

<ch-id> QAM channel number in the range 0 to 3. <net-id> Network ID number in the range 0 to 65535. The

default setting is 0.

Set and verify the network ID.

CASA CMTS


Example: Set network ID to 16 for channel 2 of QAM port 4: CASA-CMTS(config-if-qam)# channel 2 network id 16 CASA-CMTS(config-if-qam)# show interface qam 2/0 brief interface qam 2/0 interleave 128x1 channel 0 frequency 549000000 no channel 0 shutdown channel 1 frequency 555000000 no channel 1 shutdown channel 2 frequency 561000000 channel 2 transport stream id 500 channel 2 network id 16 no channel 2 shutdown channel 3 frequency 567000000 no channel 3 shutdown no shutdown

Setting the channel transport stream ID

The channel transport stream ID is needed in SI table generation. The setting is QAM downstream channel based. To set a channel transport stream ID:


Where:

<x/y> x=QAM module number; y=QAM port number Example: CASA-CMTS(config)# interface qam 0/4 CASA-CMTS(config-if-qam)#

Specifies the QAM interface.

CASA CMTS


2 channel <ch-id> transport stream id <ts-id> Where:

<ch-id> QAM downstream channel number. Valid values are 0 to 3. <net-id> QAM channel transport-stream ID in the range 0 to 65535.

The default setting is 0. Example: Set transport stream ID to 500 for channel 2 of QAM port 4: CASA-CMTS(config-if-qam)# channel 2 transport stream id 500 CASA-CMTS(config-if-qam)# show interface qam 2/0 brief interface qam 2/0 interleave 128x1 channel 0 frequency 549000000 no channel 0 shutdown channel 1 frequency 555000000 no channel 1 shutdown channel 2 frequency 561000000 channel 2 transport stream id 500 channel 2 network id 16 no channel 2 shutdown channel 3 frequency 567000000 no channel 3 shutdown no shutdown

Set a channel transport stream ID.

Configuring the Time Offset Table

The Time Offset Table (TOT) carries the UTC-time and date information as well as the local time offset. It is transmitted in TS packets with a PID value of 0x0014 and a table ID of 0x73. This section covers commands for the following TOT configurations: x Setting Time Zone x Setting Time Offset x Setting Daylight Saving Time (US only)

CASA CMTS


Setting the time zone

To set the time zone (not to be used for EuroDOCSIS):

Step Command (config) Purpose 1 si generator tot country-code <string> region-id <0-60>

Where:

<string> 3-character country identifier. When the country-code is set to “cet” the time is adjusted to daylight saving time (CEST) and readjusted to CET automatically.

<0-60> Time zone: 0 for none, 1 for the most eastern region, and so on. To display a list of time zones: CASA-CMTS# show timezone list

Example: Set the time zone to the Central European Time: CASA-CMTS(config)# si generator tot country-code cet region-id 0

To verify the time zone setting: CASA-CMTS(config)#show running-config | i tot si generator tot country-code cet region-id 0 si generator tot offset-hours 5 offset-minutes 30 si generator tot dst begin month 4 week 1 time 2 si generator tot dst end month 10 week 5 time 2

Set and verify the time zone.

Setting the time offset

The time offset is relative to the Universal Time Coordinated (UTC) time. To set the time offset:

Step Command (config) Purpose 1 si generator tot offset-hours <-12 to 13> offset-minutes <0, 30,

45> Where:

<-12 to 13> Offset hours to UTC-time. Valid values are –12 to 13.

<0, 30, 45> Minute part of the offset. Valid values are 0, 30, and 45.

Example: If the offset in a time zone is 5 hours and 30 minutes (such as in India), the command is:

Set and verify the time offset.

CASA CMTS


CASA-CMTS(config)# si generator tot offset-hours 5 offset-minutes 30 To verify the time offset: CASA-CMTS(config)# show running-config | i tot

Setting daylight saving time (US only)

To configure daylight saving time (DST) use the following pair of commands. Both the beginning and the end of DST need to be specified to complete the DST configuration.

Step Command (config) Purpose 1 si generator tot dst begin month <1-12> week (1-5> time <0-3>

si generator tot dst end month <1-12> week (1-5> time <0-3> Where:

<1-12> Month number, January to December. <1-5> First to fourth; enter 5 for last Sunday of month. <0-3> 0 for 12 a.m. midnight to 3 a.m. after midnight.

Example: Set daylight saving time beginning in the first Sunday of April at 2am: CASA-CMTS(config)# si generator tot dst begin month 4 week 1 time 2 Set daylight saving time ending in the last Sunday of October at 2am: CASA-CMTS(config)# si generator tot dst end month 10 week 5 time 2 To verify the DST setting: CASA-CMTS(config)# show running-config | i tot

Set and verify the DST setting. Both the beginning and the end of DST are required in the configuration

Configuring the DOCSIS event notification policy This section covers commands for the following operations: x Enabling cable event reporting x Configuring event reporting by unique identifier x Configuring the event reporting flags for DOCSIS event messages x Enabling logging of DOCSIS event messages to a SYSLOG server

CASA CMTS


x Configuring TRAP/INFORM and SYSLOG throttling and limiting attribute x Specifying the throttle interval x Specifying the throttle threshold

Enabling DOCSIS cable event reporting The [no] cable event command enables and disables the generation and dispatching of DOCSIS cable event message notifications. This function is enabled by default. Use the show cable event running-config command to display the list of cable event IDs. Note: The local CMTS log file is not affected by cable events that have been disabled with the cable event command.


1 [no] cable event Example: CASA-C10G(config)# cable event CASA-C10G(config)# no cable event

Enables or disables dispatching of DOCSIS cable events.

Configuring event reporting by unique identifier The cable event <identifier> command controls the dispatching of DOCIS cable event messages by event ID. By default, all cable event messages except 82010100 and 82010400 are enabled. Use the show cable event running-config command to display the list of cable event IDs. Use the no form of the command to disable any cable events using a valid identifier. Note: The local CMTS log file is not affected by cable events that have been disabled with the cable event command.


1 [no] cable event <number> Where:

<number> Specifies a valid cable ID value in the range 1-4294967295. Use the show cable event running-config command to display the valid cable event identifiers.

Example: CASA-C10G(config)# no cable event 83020203 CASA-C10G(config)# show cable event running-config . .

Controls dispatching of cable events by event identifier.

CASA CMTS


cable event 83020103 cable event 83020200 cable event 83020201 cable event 83020202 no cable event 83020203

Displaying the cable event identifiers Use the show cable event running-config command to display the list of valid cable event IDs, as well as those IDs that have been disabled for dispatch with the no cable event command.


1 show cable event running-config [brief] Where:

brief Specifies the shortened version of the cable event identifier list.

Example: CASA-C10G(config)# show cable event running-config . . . cable event 83020103 cable event 83020200 cable event 83020201 cable event 83020202 no cable event 83020203

Displays the cable event identifiers from the CMTS running configuration.

Configure the event reporting flags for DOCSIS event messages

To configure the event reporting flags for DOCSIS event messages, which determines how the CMTS reports these events, use the cable event priority command in global configuration mode. To return to the default settings found in the DOCS-CABLE-DEVICE-MIB, use the no form of this command:


1 [no] cable event priority {emergency | alert | critical | error | warning | notice | informational | debug} flags Where:

<flags> See Table 5 below.

Configure event priority reporting flags.

CASA CMTS


Table 5. DOCSIS event priority and flags Keyword Description

emergency Sets the event reporting flag for emergency system error messages. (Emergency messages indicate that the system has become unusable and requires immediate attention. This problem might also be affecting other parts of the network.)

alert Sets the event reporting flag for alert system error messages. (Alert messages indicate that some type of system or connection failure has occurred and requires immediate attention.)

critical Sets the event reporting flag for critical system error messages. (Critical messages indicate that an error occurred which requires immediate attention to avoid system or connection failure.).

error Sets the event reporting flag for error system error messages. (Error messages indicate that an error condition occurred that requires attention to resolve. Failure to address this problem will result in some type of system or connection failure in the near future.).

warning Sets the event reporting flag for warning system error messages. (Warning messages indicate that a condition occurred that indicates attention is needed in near future to avoid potential problems. Failure to address this problem could result in some type of system or connection failure later on.) .

notice Sets the event reporting flag for notice system error messages. (Notice messages indicate that a situation occurred that is normal but is significant enough that system administrators might want to notice.)

informational Sets the event reporting flag for informational system error messages. (Informational messages might or might not be significant to the system administrators.).

debug Sets the event reporting flag for debug system error messages. (Debug messages appear only when debugging has been enabled.).

flags Sets the event reporting flags value, in hex, which specifies how this particular type of event message should be reported. The valid values are shown below: • 0x00 DOCSIS messages are not reported. • 0x80 DOCSIS messages are saved in a local log on the CMTS. • 0xA0 DOCSIS messages are reported to the local log and SYSLOG

servers • 0xC0 DOCSIS messages are reported to the local log and trap receivers • 0xE0 DOCSIS messages are reported to the local log, SYSLOG servers

and trap receivers

CASA CMTS


Displaying the current priority and flags for cable event logging

To show the event reporting flags for cable event messages:


1 show cable event notification-policy Example: CASA-CMTS#config)#show cable event notification-policy priority flash-log mem-log traps syslog ------------------------------------------------- emergency yes no no no alert yes no no no critical yes no yes yes error yes no yes yes warning no yes yes yes notice no yes yes yes informational no no no no debug no no no no

Display current cable event logging priority and flags

Enabling logging of DOCSIS event messages to a SYSLOG server

To enable logging of DOCSIS event messages to a SYSLOG server, use the cable event syslog-server command in global configuration mode. To disable the logging of a DOCSIS syslog server, use the no form of this command.

Step Command (config) Purpose 1 [no] cable event syslog-server <ip_address>

Where:

<ip_address> The DOCSIS server address.

Enable or disable the logging of a DOCSIS syslog server.

2 show running-config | i syslog Example: CMTS#config)#show running-config | i syslog !syslog server for DOCSIS events: cable event syslog-server 192.168.0.163

Verify the current syslog server for DOCSIS events.

CASA CMTS


Configuring the TRAP/INFORM and SYSLOG throttling and limiting attribute To configure how the CMTS throttles the SNMP traps and SYSLOG messages it generates for DOCSIS event messages, use the cable event throttle-adminStatus command in global configuration mode. To restore the default behavior, use the no form of this command.

Step Command (config) Purpose 1 [no] cable event throttle-adminStatus {inhibited |

maintainBelowThreshold | stopAtThreshold | unconstrained} Where:

unconstrained(1) Causes traps and syslog messages to be transmitted without regard to the threshold settings.

maintainBelowThreshold(2) Causes trap transmission and syslog messages to be suppressed if the number of traps would otherwise exceed the threshold.

stopAtThreshold(3) Causes trap transmission to cease at the threshold, and not resume until directed to do so.

inhibited(4) Causes all trap transmission and syslog messages to be suppressed.

Configures how the CMTS throttles the SNMP traps and SYSLOG messages.

2 show running-config | i throttle-adminStatus Example: CMTS#config)#show running-config | i throttle-adminStatus cable event throttle-adminStatus stopAtThreshold

Verify the current throttle- admin Status setting

Specifying the throttle interval

To specify the throttle interval, which controls how often the CMTS generates SNMP traps and SYSLOG messages for DOCSIS event messages, use the cable event throttle-interval command in global configuration mode. To restore the default behavior, use the no form of this command.

Step Command (config) Purpose 1 [no] cable event throttle-interval <num>

Where:

<num> Throttle interval in unit of seconds. Valid values are from 1-2147483647.

Specify the throttle interval.

CASA CMTS


Specifying the throttle threshold

To set the maximum number of SNMP traps and SYSLOG messages that the CMTS can generate for DOCSIS event messages during the throttle interval, use the cable event throttle-threshold command in global configuration mode. To restore the default number, use the no form of this command.


1 [no] cable event throttle-threshold <num> Where:

<num> Throttle threshold in unit of seconds. Valid values are from 1-2147483647.

Specify the throttle threshold

2 show running-config | i throttle-threshold Example: CMTS#config)#show running-config | i throttle-threshold cable event throttle-threshold 1000

Verify the current throttle-threshold setting

Using the logging commands

By default, the Casa CMTS saves logging messages (debugging output) to local flash as a logfile. To redirect logging messages to a destination other than local flash, use the logging command. Possible destinations include the console, virtual terminals, and hosts running a Syslog server. Logging levels determine the severity of the information that is collected in the log file. The user can set the logging levels as needed. Table 6 lists and briefly describes the logging levels and corresponding keywords used to set the logging levels for these types of messages. Level 0, emergencies, is the highest level and logs only the most serious errors. Level 7, debugging, is the lowest level. Level 7 logs include the most messages because Level 7 logs include messages from all levels. Table 6. Message logging keywords and levels

Level Keyword Description Syslog definition

0 Emergencies System is unusable. LOG_EMERG

1 Alerts Immediate action is needed. LOG_ALERT

2 Critical Critical conditions exist. LOG_CRIT

3 Errors Error conditions exist. LOG_ERR

4 Warnings Warning conditions exist. LOG_WARNING

CASA CMTS


5 Notification Normal, but significant, conditions exist.

LOG_NOTICE

6 Informational Informational messages. LOG_INFO

7 Debugging Debugging messages. LOG_DEBUG

This sub-section explains how to use logging commands to redirect and limit the types of logging messages.

x Configuring the logging target destinations and levels x Excluding user log-in messages from the log file x Display the current logging settings

Configuring logging targets and levels

The logging command allows you to direct messages processed by the CMTS to a specified target destination. The target can be a remote syslog host, the system console display, volatile or non-volatile memory, or a loopback interface. For each logging target, you need to specify the type of message based on a severity level, as listed in Table 6.

CASA CMTS


Step Command Purpose 1 [no] logging {host <ip-address> | non-volatile | source-interface

loopback <number>| syslog | system | volatile} <level> Where:

host IP address of the syslog host. A maximum of 8 hosts can be configured.

non-volatile Logging level on non-volatile memory (flash memory)

source-interface loopback

The port number of the loopback interface in the range 0 to 15.

syslog Logging level for the syslog hosts, as configured with the host <ip-address> option.

system Logging level to system console display.

volatile Logging level for local log on volatile memory (RAM FS)

<level> alerts, critical, debugging, emergencies, errors, informational, notifications, warnings

Example: Set the level of messages displayed on monitors to notification: CASA-CMTS(config)# logging system notifications

Send alert messages to two syslog hosts: CASA-CMTS(config)#logging host 192.168.8.123 CASA-CMTS(config)#logging host 192.168.8.145 CASA-CMTS(config)#logging syslog alerts

Set the logging target and level. Use the no form of the command to remove any previous logging settings.

Excluding user messages from the log file by severity level

To disable all logging for specific users (up to 16) or to selectively disable certain logs for a user, first create an exclusion list, and then enter a maximum severity level. Messages associated with the specified log level (and all lower severity levels) for the specified user are disabled and will not be logged. Specifying the highest severity level (alert) disables logging of all messages for the specified user. This is useful when users log in regularly to run a process, for example. Each log-in and log-out creates an entry in the log file. This can fill the log file with entries that are not useful.

CASA CMTS


To create the exclusion list, enter config mode:

Step Command (config) Purpose 1 user log exclusion-list

Example: CASA-CMTS(config)#user log exclusion-list

CASA-CMTS(user-log-exclusive-list)#

Enter user log configuration mode.

2 user <name> <level>

Where: <name> User name <level> Logging level (use alert for log-in entries):

x alert -- severity level 1 (alert and below)

x critical – severity level 2 (critical and below)

x error – severity level 3 (error and below)

x warning – severity level 4 (warning and below)

x notification – severity level 5 (notification and below)

x information – severity level 6 (information and below)

x debugging – severity level 7 (debugging)

Example: Exclude all logging messages associated with user test1 from the log file: CASA-CMTS(user-log-exclusive-list)# user test1 alert Example: Exclude all error, warning, notification, information, and debugging messages associated with user test1 from the log file. All alert and critical messages associated with user test1 will continue to be logged. CASA-CMTS(user-log-exclusive-list)# user test1 error

Add the user name and specify alert to exclude log-ins by this user from the log file.

CASA CMTS


Displaying the current logging settings To display the logging settings associated with all configured logging targets:

Step Command (config) Purpose 1 show logging all

Example: CASA-CMTS(config)#show logging all /dev/console : notifications system log level : notifications non-volatile log level : warnings volatile log level : errors syslog level : warnings syslog host: 192.168.8.123 192.168.8.145

Display all current logging settings

cmts_software_config_guide_2_7_13_torelease_6.1.3, 1g.pdf

Documents

casa systems

software releases

port numbering

licensed software products

c2200 slot

c3200 slot

c10g slot

table of contents version