Survey
* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project
Download Arris Cadant C4
Document related concepts
no text concepts found
Transcript
C4® CMTS Release 8.3
User Guide
STANDARD Revision 1.0
November 2016
C4/C4c CMTS Release 8.3 User Guide
ARRIS Standard Software License Terms and Warranty Table
Unless your company has executed a separate agreement which contains terms and conditions for software licensing of
ARRIS products, you must agree to the below terms and conditions to receive download and support. ARRIS products, both
Hardware and Software, contain proprietary information and trade secrets that are confidential information of ARRIS.
ARRIS reserves the right to audit the use of Customer’s Hardware and Software.
Definitions and Interpretation
Within this document the following terms are defined as follows:
“ARRIS” means ARRIS Solutions, Inc., a wholly owned subsidiary of ARRIS Enterprises, Inc. and/or its designated affiliates.
“Customer” means the person or entity however constituted to whom the Products or Services are provided.
“Hardware” means equipment designed and manufactured by ARRIS, or other manufacturer's equipment offered for sale
by ARRIS to Customer.
“Software” means ARRIS-licensed software, including updates, and any other enhancements, modifications, and bug fixes
thereto, in object code form only, and any full or partial copies thereof. Software is licensed by ARRIS separately or as part
of a Product sale.
Provided that the Customer has paid all applicable license fees to ARRIS, and assuming that the Customer has not
negotiated a separate specific agreement or been granted a third-party license with the Software, then ARRIS grants to
Customer a limited, royalty-free, nonexclusive and nontransferable, non-sublicensable license limited solely to the use of
the Software’s application with the Hardware, if applicable, sold in conjunction with the Software for its intended
purposes, which purposes preclude Customer’s provision of any product or service to a third party that would alleviate any
third party from the obligation or need to obtain a separate license to the Software. All rights, title to and ownership of all
applicable intellectual property rights in the Software, including but not limited to patents, copyrights and trade secrets
remain with ARRIS and its licensors. Customer shall not attempt to acquire any other rights or transfer any ownership
rights in the Software in contravention to ARRIS’ rights. ARRIS’ rights extend to any accompanying printed materials and
online or electronic documentation, and any authorized copies of the above materials. The Software as used herein
includes unpublished software, trade secret and confidential or proprietary information of ARRIS or its licensors and is
developed at private expense. Customer may use third-party software products or modules supplied by ARRIS solely with
the Products, unless the licensing terms of the third-party software specify otherwise.
Customer shall not modify, create derivative works, reverse engineer, decompile, disassemble or in any manner attempt to
derive the source code from the Software, in whole or in part, except and only to the extent that such activity is expressly
permitted by applicable law. Customer is entitled to make a single copy of the Software solely for backup or archival
purposes and all title, trademark, copyright, restricted rights or any other proprietary notices shall be reproduced in such
copy. Unless otherwise agreed to in writing, Customer shall not otherwise use, copy, modify, lend, share, lease, rent,
assign, sub-license, provide service bureau, hosting or subscriptions services, or distribute or transfer the Software or any
copies thereof, in whole or in part, except as expressly provided in these terms and conditions. Customer further agrees
not to publish or disclose any benchmark tests run on the Software. Customer shall not remove, obscure or alter any
notice of copyright, patent, trade secret, trademark or other proprietary right or disclaimer appearing in or on any
Software Products or accompanying materials. All rights not expressly granted hereunder are reserved by ARRIS.
The Software may contain embedded third-party software (“Embedded Third-party Software). The licensors of such
Embedded Third-party Software shall be third party beneficiaries entitled to enforce all rights and obtain all benefits which
relate to such licensors under these terms and conditions. The licensors of such Embedded Third-party Software shall not
be liable or responsible for any of ARRIS’ covenants or obligations under these terms and conditions, and Customer’s rights
or remedies with respect to any Embedded Third-party Software under these terms and conditions shall be against ARRIS.
Customer shall not directly access or use any embedded third-party software independently of the Software unless
Customer obtains appropriate licenses. Under certain circumstances, ARRIS will advise that Customer needs to obtain a
license for other third-party software (“Third-party Software”) for use in conjunction with the Software. Customer agrees
that the terms and conditions agreed to between Customer and such Third-party Software vendor, including but not
limited to warranties, indemnification and support, shall be solely between Customer and the Third-party Software vendor,
and ARRIS shall not have any responsibility or liability for such Third-party Software. ARRIS Products may contain Open
Source software. If Open Source is used, upon written request from an ARRIS customer, ARRIS will make available the
appropriate Open Source software as per the applicable GPL.
ARRIS C4® CMTS and E6000®Converged Edge Router Warranty
Warranty Period from Shipment Date
ARRIS Product Categories
Domestic U.S.
All ARRIS CMTS products including WiDOX CMTS, C3, C4, C4c, D5
Hardware—one (1) Year
UEQ and E6000 CER; and EGT Encoder Solutions: Encore and Quartet Software—ninety (90) days
Encoders, VIPr Video Transcoder and System Solutions, and HEMi
Headend Micro Solutions.
Outside of U.S.
Hardware—one (1) Year
Software—ninety (90) days
Copyright and Trademark Information
E6000® Converged Edge Router
©ARRIS Enterprises, Inc. 2016 All rights reserved. No part of this publication may be reproduced in any form or by any
means or used to make any derivative work (such as translation, transformation, or adaptation) without written
permission from ARRIS Enterprises, Inc. (“ARRIS”). ARRIS reserves the right to revise this publication and to make changes
in content from time to time without obligation on the part of ARRIS to provide notification of such revision or change.
ARRIS and the ARRIS logo are all trademarks of ARRIS Enterprises, Inc. Other trademarks and trade names may be used in
this document to refer to either the entities claiming the marks and the names of their products. ARRIS disclaims
proprietary interest in the marks and names of others.
ARRIS provides this guide without warranty of any kind, implied or expressed, including, but not limited to, the implied
warranties of merchantability and fitness for a particular purpose. ARRIS may make improvements or changes in the
product(s) described in this manual at any time.
The capabilities, system requirements and/or compatibility with third-party products described herein are subject to
change without notice.
ARRIS C4® Cable Modem Termination System (CMTS)
ARRIS C4® Cable Modem Termination System
ARRIS C4c™ Cable Modem Termination System
ARRIS DOCSIS® 3.0 C4® CMTS
The capabilities, system requirements and/or compatibility with third-party products described herein are subject to
change without notice. ARRIS, the ARRIS logo, Auspice®, BigBand Networks®, BigBand Networks and Design®, BME®, BME
50®, BMR®, BMR100®, BMR1200®, C3™, C4®, C4c™, C-COR®, CHP Max5000®, ConvergeMedia™, Cornerstone®,
CORWave™, CXM™, D5®, Digicon®, E6000®, ENCORE®, EventAssure™, Flex Max®, FTTMax™, HEMi®, MONARCH®, MOXI®,
n5®, nABLE®, nVision®, OpsLogic®, OpsLogic® Service Visibility Portal™, Opti Max™, PLEXiS®, PowerSense™, QUARTET®,
Rateshaping®, Regal®, ServAssure™, Service Visibility Portal™, TeleWire Supply®, TLX®, Touchstone®, Trans Max™, VIPr™,
VSM™, and WorkAssure™ are all trademarks of ARRIS Enterprises, Inc. Other trademarks and trade names may be used in
this document to refer to either the entities claiming the marks and the names of their products. ARRIS disclaims
proprietary interest in the marks and names of others. Copyright 2016 ARRIS Enterprises, Inc. — All Rights Reserved.
Reproduction in any manner whatsoever without the express written permission of ARRIS Enterprises, Inc. is strictly
forbidden. For more information, contact ARRIS.
Metaswitch® is a registered trademark of Metaswitch Networks in the US and other countries.
Portions of the IPDR software were authored by IPDR.org.
The Regular Expression Source Code and its use is covered by the GNU LESSER GENERAL PUBLIC LICENSE version 3, June
29, 2007.
This product includes software developed by the Apache Software Foundation, http://www.apache.org/ .
Patent Information
The ARRIS C4® Cable Modem Termination System (CMTS) and E6000® Converged Edge Router are protected by U.S. and
international patents including:
6,449,249
6,457,978
6,636,482
6,637,033
6,662,368
6,769,132
6,898,182
7,002,914
7,047,553
7,272,144
7,480,237
7,480,241
7,570,127
7,593,495
7,606,870
7,660,250
7,698,461
7,701,956
7,953,144
7,958,260
7,974,303
8,136,141
8,218,438
8,332,911
8,548,457
8,819,606
8,861,366
8,923,319
8,959,408
8,971,184
8,995,460
9,065,735
9,088,358
Additional ARRIS Enterprises, Inc. patents pending. Copyright (c) 2002-2016 ARRIS Enterprises, Inc. — All Rights Reserved.
Table 1. Revision History
Revision
Date
Reason for Change
Rel. 8.3 Preliminary, Issue 1.0
August 2015
Rel. 8.3 Standard, Issue 1.0
November 2016
Meet Field Soak Ready (FSR) requirements.
Reissued for General Availability.
Table of Contents
1. Introduction ........................................................................................................................................... 45
Overview ............................................................................................................................................................. 45
Intended Audience.............................................................................................................................................. 45
Prerequisite Skill and Knowledge ....................................................................................................................... 45
Purpose ............................................................................................................................................................... 46
Textual Conventions ........................................................................................................................................... 46
Admonishments .................................................................................................................................................. 47
2. C4/C4c CMTS Features ............................................................................................................................ 48
DOCSIS 2.0 Compliance....................................................................................................................................... 48
DOCSIS 3.0 Compliance....................................................................................................................................... 49
Fault Detection and Recovery ............................................................................................................................. 50
Interfaces and Protocols ..................................................................................................................................... 50
Security Features ................................................................................................................................................ 50
Baseline Features and Early Releases ................................................................................................................. 51
Release 3.0 Features .................................................................................................................................. 51
Release 3.3 Features .................................................................................................................................. 52
Release 4.0 Features .................................................................................................................................. 52
Release 4.1 Features .................................................................................................................................. 54
Release 4.2 Features .................................................................................................................................. 54
Release 5.0 Features .................................................................................................................................. 55
Release 5.1.x Features ............................................................................................................................... 57
Release 7.0.x Features ............................................................................................................................... 59
Release 7.1.x Features ............................................................................................................................... 59
Release 7.2.x Features ............................................................................................................................... 60
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
7
Release 7.3.x Features................................................................................................................................ 60
Release 7.4.x Features................................................................................................................................ 62
Release 8.0.x Features................................................................................................................................ 63
Release 8.1.x Features................................................................................................................................ 64
Release 8.1.5 -- Small Feature Release ...................................................................................................... 65
Release 8.2 Features .................................................................................................................................. 66
Release 8.2.5 Features ............................................................................................................................... 69
Release 8.3 Features .................................................................................................................................. 71
3. C4/C4c CMTS Specifications .................................................................................................................... 74
Overview ............................................................................................................................................................. 74
Network Diagram ................................................................................................................................................ 75
C4 CMTS .............................................................................................................................................................. 76
C4c CMTS ............................................................................................................................................................ 76
Slot Numbering Scheme ............................................................................................................................. 77
Limited Support for the 2Dx12U CAM in the C4c CMTS ............................................................................ 78
C4/C4c CMTS Specifications................................................................................................................................ 78
Physical ....................................................................................................................................................... 78
Power ......................................................................................................................................................... 79
Safety .......................................................................................................................................................... 79
Electromagnetic Compatibility ................................................................................................................... 80
Environmental ............................................................................................................................................ 80
WEEE (Waste Electrical and Electronic Equipment) .................................................................................. 81
RF Electrical Specifications .................................................................................................................................. 82
Network Interfaces..................................................................................................................................... 84
Scalability ............................................................................................................................................................ 85
C4 CMTS Chassis ......................................................................................................................................... 85
C4c CMTS Chassis ....................................................................................................................................... 86
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
8
VoIP Call Capacities ............................................................................................................................................. 87
4. C4 CMTS General Installation Requirements ........................................................................................... 91
Overview ............................................................................................................................................................. 92
Safety Precautions .............................................................................................................................................. 92
Lifting Safety............................................................................................................................................... 92
Electrical Equipment Guidelines ......................................................................................................................... 94
Electrostatic Discharge (ESD) .............................................................................................................................. 94
C4 CMTS Installation Checklist............................................................................................................................ 95
Tools Required ........................................................................................................................................... 96
Torque Values ............................................................................................................................................ 96
Items Not Supplied ..................................................................................................................................... 97
Unpacking the C4 CMTS ...................................................................................................................................... 97
Module Protection ..................................................................................................................................... 99
Installation Considerations ................................................................................................................................. 99
Rack Mounting ........................................................................................................................................... 99
Power Requirements................................................................................................................................ 100
Cooling Requirements .............................................................................................................................. 100
Rack Mounting the C4 CMTS ............................................................................................................................ 102
Grounding the Chassis ............................................................................................................................. 103
Main Hardware Components ........................................................................................................................... 104
Module Types and Chassis Slots—Front View ......................................................................................... 105
Chassis — Rear View ................................................................................................................................ 106
Installing Modules in the C4 CMTS ................................................................................................................... 108
Module Installation Overview .................................................................................................................. 108
Installation Diagram ................................................................................................................................. 109
Ejector Levers ........................................................................................................................................... 110
Fan Trays ........................................................................................................................................................... 110
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
9
High Speed Fan Trays ............................................................................................................................... 111
Air Filter .................................................................................................................................................... 112
Power Conditioning Module and Cabling ......................................................................................................... 113
Power Requirements................................................................................................................................ 114
Front Panel Access ................................................................................................................................... 116
Power Protection Description .................................................................................................................. 118
Chassis Maintenance ........................................................................................................................................ 123
Cleaning the Chassis ................................................................................................................................. 123
Air Filters .................................................................................................................................................. 123
Replacing the C4 CMTS Chassis......................................................................................................................... 123
5. C4c CMTS Installation Requirements ..................................................................................................... 125
Safety Precautions ............................................................................................................................................ 126
Lifting Safety ............................................................................................................................................. 126
Electrical Equipment Guidelines .............................................................................................................. 128
Electrostatic Discharge (ESD) ............................................................................................................................ 129
Installation Checklist ......................................................................................................................................... 130
Tools Required ......................................................................................................................................... 131
Torque Values .......................................................................................................................................... 131
Items Not Supplied ................................................................................................................................... 131
Unpacking the C4c CMTS .................................................................................................................................. 132
Module Protection ................................................................................................................................... 133
Installation Considerations ............................................................................................................................... 134
Rack Mounting ......................................................................................................................................... 134
Power Requirements ................................................................................................................................ 135
Cooling Requirements .............................................................................................................................. 135
Rack Mounting the C4c CMTS ........................................................................................................................... 137
Grounding the Chassis.............................................................................................................................. 138
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
10
Main Hardware Components ........................................................................................................................... 139
Chassis Configuration ............................................................................................................................... 139
Module Types and Chassis Slots—Front View ......................................................................................... 140
Chassis — Rear View ................................................................................................................................ 143
Installing Modules in the C4c CMTS ......................................................................................................... 144
Fan Tray Module ...................................................................................................................................... 147
Power Module and Cabling............................................................................................................................... 151
Power Requirements................................................................................................................................ 154
Front Panel Access ................................................................................................................................... 158
Power Protection Description........................................................................................................................... 159
A and B Power Feeds................................................................................................................................ 159
Internal Branch Protection ....................................................................................................................... 160
Automatic Card Recovery for DC Voltage ................................................................................................ 161
C4c CMTS Chassis Maintenance ....................................................................................................................... 162
Cleaning the Chassis ................................................................................................................................. 162
Air Filters .................................................................................................................................................. 162
Replacing the C4c CMTS Chassis ....................................................................................................................... 162
6. System Control Module (SCM) .............................................................................................................. 165
SCM Overview ................................................................................................................................................... 165
SCM/SCM II Ethernet Interfaces .............................................................................................................. 167
SCM 3 Ethernet Interfaces ....................................................................................................................... 167
Installation................................................................................................................................................ 172
SCM Replacement ............................................................................................................................................. 177
SCM Upgrade to 1GB RAM (SCM II EM)............................................................................................................ 181
Virtual System Controller ......................................................................................................................... 186
SCM II EM (U) .................................................................................................................................................... 187
SCM 3 ................................................................................................................................................................ 187
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
11
SCM 3 Operational Interaction ................................................................................................................ 188
Out-of-Band Management on the SCM 3 ................................................................................................ 188
Upgrading a C4 CMTS to an SCM 3 .......................................................................................................... 189
Compact Flash ................................................................................................................................................... 195
Physical Dimensions ................................................................................................................................. 195
Replacing the Compact Flash ................................................................................................................... 196
Compact Flash Disk Partitions .................................................................................................................. 200
File System Administration ...................................................................................................................... 204
File Transfers ............................................................................................................................................ 206
7. Router Control Module (RCM) ............................................................................................................... 208
RCM Overview................................................................................................................................................... 208
Primary Software Functions .............................................................................................................................. 210
RCM Hardware .................................................................................................................................................. 210
LED Status Indicators ................................................................................................................................ 211
RCM Crossover Connector ....................................................................................................................... 211
SFP and XFP Ethernet Interfaces .............................................................................................................. 214
Fiber Optic SFP and XFP Modules ............................................................................................................ 214
8. Downstream Cable Access Modules (DCAMs) ........................................................................................ 219
Overview ........................................................................................................................................................... 219
16D Cable Access Module (16D CAM) .............................................................................................................. 219
Primary Software Function ...................................................................................................................... 222
Downstream Test Port on 16D CAM Faceplate ....................................................................................... 223
LED Status ................................................................................................................................................. 224
Downstream Interleaver Settings ............................................................................................................ 224
QAM Modulation Order and Port Requirements..................................................................................... 225
Spectrum Windows and Downstream Frequency Spacing ...................................................................... 225
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
12
Restrictions............................................................................................................................................... 227
QAM Output Power ................................................................................................................................. 227
16D Physical Interface Cards (PICs) .......................................................................................................... 228
XD Cable Access Module (XD CAM) .................................................................................................................. 229
Types of Downstream CAMs .................................................................................................................... 230
Operational Considerations for the XD CAM ........................................................................................... 230
RF Power Monitoring and Recovery ........................................................................................................ 240
Physical Interface Cards (PICs) ................................................................................................................. 241
Downstream Parameters .................................................................................................................................. 242
Annex ....................................................................................................................................................... 242
Downstream Frequency Range ................................................................................................................ 248
XD CAM Field Software Upgrade ...................................................................................................................... 249
Overview .................................................................................................................................................. 249
Operational Concerns .............................................................................................................................. 250
Sample XD CAM Provisioning ................................................................................................................... 251
Sample Script for 32D CAM Provisioning ................................................................................................. 256
9. Upstream Cable Access Modules (UCAMs) ............................................................................................ 267
Overview ........................................................................................................................................................... 268
Guidelines................................................................................................................................................. 268
12U Cable Access Module (12U CAM) .............................................................................................................. 268
Primary Software Function ...................................................................................................................... 271
LED Status................................................................................................................................................. 271
Upstream Receive Power Levels .............................................................................................................. 272
Basic Command Set for Bringing Up a 12U CAM .............................................................................................. 274
24U Cable Access Module (24U CAM) .............................................................................................................. 277
Primary Software Function ...................................................................................................................... 279
LED Status................................................................................................................................................. 279
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
13
Shuffle Network ....................................................................................................................................... 280
Rules and Restrictions for 12U/24U CAM Configuration .................................................................................. 281
Slot Provisioning ....................................................................................................................................... 281
Annex........................................................................................................................................................ 282
Upstream (US) Channel to Physical Connector Mapping......................................................................... 282
24U CAM Upstream Power Level Groups ......................................................................................................... 282
Default Admin States ............................................................................................................................... 286
Basic Command Set for Bringing Up a 24U CAM .............................................................................................. 286
Measuring SNR in the 12U/24U CAM ............................................................................................................... 289
Channel SNR Calculations......................................................................................................................... 289
Modem SNR Calculation........................................................................................................................... 291
Modulation Profiles .......................................................................................................................................... 292
Default Modulation Profile ...................................................................................................................... 292
Valid Center Frequencies ......................................................................................................................... 294
Setting the Rx Power Levels ..................................................................................................................... 295
Adjusting Channel Settings in Response to Increased CM Scaling ................................................................... 298
Explanation of Upstream Parameters............................................................................................................... 299
Modulation Profile Values........................................................................................................................ 300
12U/24U Ingress Noise Cancellation ........................................................................................................ 308
Notes on DOCSIS 3.0 Upstream Frequency Range................................................................................... 308
Modulation Profiles: Default and User-defined................................................................................................ 309
Displaying Modulation Profiles ................................................................................................................ 311
Optimizing a Modulation Profile ....................................................................................................................... 311
Noise and SNR versus Modulation Symbol Rate ...................................................................................... 312
10. Control Complex Redundancy ............................................................................................................... 322
Overview ........................................................................................................................................................... 322
Add Control Complex ........................................................................................................................................ 323
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
14
11. Basic Bring-up Procedure for the C4 CMTS............................................................................................. 325
Introduction ...................................................................................................................................................... 325
Chassis Installation and Powering ............................................................................................................ 326
HFC Network Connectivity ....................................................................................................................... 326
IP Network Plan ........................................................................................................................................ 328
Configuration of Back Office Servers ....................................................................................................... 328
1. Install Cards, Rear PICs, Filler Panels, PCMs, and Fans ........................................................................ 331
2. Set Up Console Cable ........................................................................................................................... 332
3. Power Up the Chassis ........................................................................................................................... 333
4. Configure Slots ..................................................................................................................................... 333
5. Configure RCM Ethernet Connections ................................................................................................. 333
6. Configure MAC Domains ...................................................................................................................... 333
7. Configure Downstream Parameters .................................................................................................... 334
8. Configure Upstream Parameters ......................................................................................................... 335
9. Configure Fiber Node and Topology .................................................................................................... 337
10. Configure a Dynamic Bonding Group ................................................................................................. 337
11. Configure RCC Management .............................................................................................................. 337
12. Local Authentication .......................................................................................................................... 338
13. Managing the C4 CMTS ...................................................................................................................... 338
14. Configure the SNMP ........................................................................................................................... 339
15. Configure Clock .................................................................................................................................. 340
16. Save the Configuration ....................................................................................................................... 340
Verification Steps .............................................................................................................................................. 340
17. Cable CAMs and RCM ......................................................................................................................... 340
18. Configure/Verify Back Office Systems ............................................................................................... 341
19. Verify the C4 CMTS Configuration ..................................................................................................... 341
20. Verify Modem Registration ................................................................................................................ 343
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
15
IP Address Prefixes and Subnets ....................................................................................................................... 348
12. Basic Bring-up Procedure for a C4c CMTS .............................................................................................. 351
Introduction ...................................................................................................................................................... 351
Before You Begin............................................................................................................................................... 352
Chassis Installation and Powering ............................................................................................................ 352
HFC Network Connectivity ....................................................................................................................... 352
IP Network Plan ........................................................................................................................................ 354
Configuration of Provisioning and Back Office Servers ............................................................................ 354
Bring-up Procedures ......................................................................................................................................... 355
Install Front Cards, PICs, Filler Panels, PMs, and Fan Tray Module ......................................................... 356
Set Up Console Cable ............................................................................................................................... 357
Power Up the Chassis ............................................................................................................................... 358
Basic Bring-up Procedure .................................................................................................................................. 358
Configure Slots ......................................................................................................................................... 358
Configure RCM Ethernet Connections ..................................................................................................... 358
Configure MAC Domains .......................................................................................................................... 359
Configure Downstream Parameters......................................................................................................... 359
Configure Upstream Parameters ............................................................................................................. 360
Configure Fiber Node and Topology ........................................................................................................ 361
Configure Bonding Group Management .................................................................................................. 362
Configure RCC Management .................................................................................................................... 362
Save the Configuration ............................................................................................................................. 363
Local Authentication ................................................................................................................................ 363
Managing the CMTS ................................................................................................................................. 364
In-band Management............................................................................................................................... 364
Out-of-band Management ....................................................................................................................... 364
Configure the SNMP ................................................................................................................................. 365
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
16
Configure Clock ........................................................................................................................................ 366
Verification Steps .............................................................................................................................................. 366
Cable CAMs and RCM ............................................................................................................................... 366
Configure/Verify Back Office Systems ..................................................................................................... 366
Verify the CMTS Configuration ................................................................................................................ 366
Verify Modem Registration ...................................................................................................................... 370
IPv6 Configuration (Optional) ........................................................................................................................... 372
IP Address Prefixes and Subnets .............................................................................................................. 373
13. CAM Sparing ......................................................................................................................................... 375
FlexCAM™ Hitless CAM Sparing ........................................................................................................................ 375
Benefits of Hitless CAM Sparing ............................................................................................................... 376
CAM Sparing PIC LEDs .............................................................................................................................. 376
Definitions ................................................................................................................................................ 376
Size of Hitless CAM Spare-groups ............................................................................................................ 376
Signal Loss during Failover ....................................................................................................................... 377
Guidelines for CAM Spare Groups .................................................................................................................... 377
Guidelines for Upstream Spare Groups ................................................................................................... 378
Guidelines for Downstream Spare Groups .............................................................................................. 378
Calculating Signal Loss During Failover .................................................................................................... 378
Configuration Example...................................................................................................................................... 378
Create CAM Spare Groups ....................................................................................................................... 382
Fail Back Manually.................................................................................................................................... 383
Deleting a CAM Spare-group ............................................................................................................................ 384
14. Cable-side Configuration ....................................................................................................................... 386
Overview ........................................................................................................................................................... 386
MAC Domains ................................................................................................................................................... 387
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
17
DOCSIS Functions ..................................................................................................................................... 387
DOCSIS 3 Terminology .............................................................................................................................. 388
Specifications ........................................................................................................................................... 391
MAC Domain Configuration ..................................................................................................................... 391
Upstream to Downstream Channel Association ............................................................................................... 405
Upstream Channel Descriptor Messages ................................................................................................. 405
Supervision ............................................................................................................................................... 405
Cable Plant Topology and Fiber Nodes ............................................................................................................. 411
Fiber Node Configuration ......................................................................................................................... 412
Channel to Fiber Node Configuration ...................................................................................................... 413
Cable Modem Timing, Supervision, and Messaging ................................................................................ 415
Service Group Determination and Display........................................................................................................ 416
MAC Domain ............................................................................................................................................ 416
Channel Sets ...................................................................................................................................................... 418
Show CLI Commands ................................................................................................................................ 418
Receive Channel Configurations and Bonding Groups ..................................................................................... 427
15. Interface IP Configuration ..................................................................................................................... 428
Overview ........................................................................................................................................................... 428
Subinterfaces (Multiple VRIs per VRF) for IPv4................................................................................................. 428
Rules of Operation and Guidelines for Subinterfaces .............................................................................. 429
Network ACLs ........................................................................................................................................... 430
Interface Configuration ..................................................................................................................................... 431
Common Interface Configuring Commands ............................................................................................. 431
Monitoring Interfaces .............................................................................................................................. 433
802.1Q VLAN Tagging (Q-tags) .......................................................................................................................... 435
One Q-tag per Network Interface ............................................................................................................ 437
Loopback Interfaces for Routing Protocols ....................................................................................................... 438
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
18
Characteristics of the Loopback Interface ............................................................................................... 438
Configuring IP Static Routes.............................................................................................................................. 441
Multiple VRFs .................................................................................................................................................... 441
Overview .................................................................................................................................................. 441
Overview of the Sample Procedure ......................................................................................................... 443
Example of Setting Up Five VRFs.............................................................................................................. 444
Link Aggregation ............................................................................................................................................... 446
Provisioning .............................................................................................................................................. 446
LACP Forwarding ...................................................................................................................................... 447
Feature Interactions ................................................................................................................................. 448
Link Overload Protection ......................................................................................................................... 448
BSoD ......................................................................................................................................................... 448
Command Line Interface .......................................................................................................................... 448
Configuring Link Aggregation ................................................................................................................... 455
16. Dynamic Routing Protocols ................................................................................................................... 457
Overview of Dynamic Routing .......................................................................................................................... 457
Border Gateway Protocol ................................................................................................................................. 458
BGP Version 4 ........................................................................................................................................... 458
Intermediate System-Intermediate System ..................................................................................................... 468
Overview .................................................................................................................................................. 468
CLNP Addressing/NSAP Address Format ................................................................................................. 469
IS-IS Network Topology, Unique Level 1 Areas ........................................................................................ 470
Dynamic Hostname Support .................................................................................................................... 472
IS-IS Network Topology — Multi-homing ................................................................................................ 473
Packet Flow Between IS-IS Systems ......................................................................................................... 473
Designated Intermediate System (DIS) and Reliable Flooding of LSPs .................................................... 474
IS-IS Point-to-Point ................................................................................................................................... 475
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
19
Multiple Topology IS-IS ..................................................................................................................................... 478
Multiple Topology IS-IS Overview ............................................................................................................ 478
Overcoming Single SPF Limitation............................................................................................................ 478
Adjacencies............................................................................................................................................... 479
Broadcast Interface Adjacencies .............................................................................................................. 480
Advertising MT Reachable Intermediate Systems in LSPs ....................................................................... 480
MT IP Forwarding ..................................................................................................................................... 480
Configuring MT IS-IS on the C4/c CMTS ................................................................................................... 482
Enable MT IS-IS ......................................................................................................................................... 482
Disable MT IS-IS ........................................................................................................................................ 482
Modify the Default Metric ....................................................................................................................... 483
Sample Configuration ............................................................................................................................... 483
Example Show Commands ....................................................................................................................... 484
CLI Commands for ISIS.............................................................................................................................. 487
Open Shortest Path First Version 2 ................................................................................................................... 495
Link State Routing Protocol Description .................................................................................................. 495
Routing Metrics ........................................................................................................................................ 495
Equal Cost MultiPath Routes.................................................................................................................... 496
Configuring OSPF ...................................................................................................................................... 496
Enable OSPF.............................................................................................................................................. 497
Disable OSPF for an Interface................................................................................................................... 499
Disable OSPF on the C4/c CMTS ............................................................................................................... 499
CLI Commands for OSPF ........................................................................................................................... 500
Open Shortest Path First Version 3 ................................................................................................................... 502
Comparison of OSPFv3 and OSPFv2 ......................................................................................................... 503
Discovering Neighboring Routers............................................................................................................. 503
Hello Packets ............................................................................................................................................ 504
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
20
Equal Cost Multipath................................................................................................................................ 505
Neighbors ................................................................................................................................................. 506
Adjacency ................................................................................................................................................. 507
Router Types ............................................................................................................................................ 507
Areas ........................................................................................................................................................ 509
Link-State Advertisement......................................................................................................................... 510
Stub Area .................................................................................................................................................. 512
Not-So-Stubby Area ................................................................................................................................. 512
Route Summarization............................................................................................................................... 512
Configuring OSPFv3 for IPv6 .................................................................................................................... 513
Configure OSPFv3 with Cable-side Interfaces as Passive Interfaces........................................................ 514
Summary of CLI Commands for OSPFv3 .................................................................................................. 516
Routing Information Protocol ........................................................................................................................... 521
RIP version 2 ............................................................................................................................................. 521
Hop Count ................................................................................................................................................ 521
Routing Update Management ................................................................................................................. 522
RIP Enable and Disable ............................................................................................................................. 522
RIP Passive Mode Operation .................................................................................................................... 524
Default Route Processing ......................................................................................................................... 525
Plain Text Authentication ......................................................................................................................... 526
MD5 Digest Authentication...................................................................................................................... 527
Enable Single Key Authentication ............................................................................................................ 529
Enable Multiple Key Authentication (i.e., Key Chains)............................................................................. 530
Route Redistribution for IPv4 Addresses .......................................................................................................... 532
BGP Route Maps ...................................................................................................................................... 532
Route Redistribution CLI Commands ....................................................................................................... 534
IP Route Filtering ...................................................................................................................................... 537
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
21
Policy-Based Routing (PBR) ............................................................................................................................... 545
Configuring PBR ........................................................................................................................................ 545
CLI Commands for PBR ............................................................................................................................. 553
17. IP Packet Filters, Subscriber Management ............................................................................................. 560
Overview ........................................................................................................................................................... 560
IP Packet Filtering.............................................................................................................................................. 560
IP Packet Filter .......................................................................................................................................... 561
IP Filter Groups ......................................................................................................................................... 561
Drop Packet By Flow Label or IP Version ................................................................................................. 566
IPv4 and IPv6 Drop/Accept Packet Command Examples ......................................................................... 567
Port Filters ................................................................................................................................................ 568
IP Protocol Filters ..................................................................................................................................... 570
Type of Service and Match Action Filtering ............................................................................................. 573
Effect of IP Packet Filtering / Subscriber Management on IP Address Limits .......................................... 574
Per-Interface Configuration ..................................................................................................................... 575
Default Subscriber Management Settings ............................................................................................... 577
C4 CMTS Debug IP Packet Capture .......................................................................................................... 578
IP Filter Related CLI Commands ............................................................................................................... 580
IP Packet Filtering Configuration Example ............................................................................................... 581
Upstream Drop Classifiers................................................................................................................................. 583
Provisioning .............................................................................................................................................. 583
US Drop Classifier Commands .................................................................................................................. 583
18. Baseline Privacy Interface (BPI) ............................................................................................................. 585
Baseline Privacy Overview ................................................................................................................................ 585
BPI Operations.......................................................................................................................................... 586
Baseline Privacy Key Management (BPKM) ............................................................................................. 586
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
22
Packet Data Encryption ............................................................................................................................ 586
Baseline Privacy Operational Overview ................................................................................................... 586
Baseline Privacy Setup ...................................................................................................................................... 588
Initial CER Base Table Setup ..................................................................................................................... 588
Baseline Privacy Cable Modem Configuration File Settings .................................................................... 593
BPI Initialized State Configuration Settings.............................................................................................. 595
Digital Certificates (BPI+ Only) ................................................................................................................. 596
Provisioning BPI X.509 Certificates Using Import/Export Commands ..................................................... 597
Provisioning X.509 Certificates ......................................................................................................................... 599
CA Certificates .......................................................................................................................................... 599
To Review or Confirm CA Certificates ...................................................................................................... 600
CM Certificates ......................................................................................................................................... 600
Baseline Privacy Debugging .............................................................................................................................. 601
Registration Debugging ............................................................................................................................ 601
Explanation of the QoS Parameter .......................................................................................................... 602
Initialization State Debugging .................................................................................................................. 602
Baseline Privacy MIB Debugging .............................................................................................................. 604
Baseline Privacy Trap Codes ............................................................................................................................. 604
Baseline Privacy: CLI Commands ...................................................................................................................... 608
Configure Cable Commands ..................................................................................................................... 608
Show Cable Command ............................................................................................................................. 609
Configure Interface Cable-mac ................................................................................................................ 610
BPI Hybrid Mode Operation.............................................................................................................................. 611
Overview .................................................................................................................................................. 611
BPI+ Enforce ...................................................................................................................................................... 613
CLI Commands .......................................................................................................................................... 614
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
23
19. DOCSIS Set-top Gateway Configuration ................................................................................................. 616
Overview ........................................................................................................................................................... 616
Logical Devices in a DSG System .............................................................................................................. 616
Definitions ................................................................................................................................................ 617
DSG 3.0 .............................................................................................................................................................. 619
DSG 3.0 Operational Considerations ........................................................................................................ 619
Determining DSID to Tunnel Associations ............................................................................................... 620
DSG Configuration Overview ............................................................................................................................ 622
Reset DSG Configuration to Null .............................................................................................................. 623
Configuring Interfaces to Carry Tunnel Traffic ......................................................................................... 623
Enabling Upstream Filters ........................................................................................................................ 625
DSG Configuration .................................................................................................................................... 626
Sample DSG Configuration Scenarios ............................................................................................................... 637
Initial Setup for DSG ................................................................................................................................. 637
DSG Configuration Only ........................................................................................................................... 638
Multicast Destination IP to RFC1112 DSG Tunnel MAC ........................................................................... 639
Multicast Destination IP to non-RFC1112 DSG Tunnel MAC ................................................................... 641
20. CPE Device Classes ................................................................................................................................ 644
Overview ........................................................................................................................................................... 644
Types of Device Classes..................................................................................................................................... 644
Functionality ............................................................................................................................................. 645
IPv6 VoIP Support ..................................................................................................................................... 645
Considerations.......................................................................................................................................... 645
Dynamic Host Configuration Protocol (DHCP) .................................................................................................. 646
DHCP Client .............................................................................................................................................. 646
DHCP Server ............................................................................................................................................. 646
DHCP Relay Agent .................................................................................................................................... 647
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
24
DHCP Options ........................................................................................................................................... 647
Rapid Commit ........................................................................................................................................... 649
DHCP Helper Address Provisioning .......................................................................................................... 649
Assigning Secondary Interfaces Based on Device Class ........................................................................... 650
Filter Groups Based on Device Class ................................................................................................................. 651
Filter Group Assignment .......................................................................................................................... 652
DOCSIS Subscriber Management MIB...................................................................................................... 652
CPE Device Filtering Related Commands ................................................................................................. 653
21. Integrated Upstream Agility .................................................................................................................. 660
Overview ........................................................................................................................................................... 660
Monitoring Upstream Agility State Machines.......................................................................................... 661
Limitations ................................................................................................................................................ 662
Examples of Upstream Agility State Machines ................................................................................................. 663
Example 1 (Unique State)......................................................................................................................... 664
Using Tables Instead of Diagrams ............................................................................................................ 667
Trigger Precedence .................................................................................................................................. 669
Example 2 (Periodic) ................................................................................................................................ 670
Example 3 (Time-of-Day).......................................................................................................................... 672
Example to Configure a Sample Upstream Agility Application ................................................................ 673
Related CLI Commands ..................................................................................................................................... 674
Defining Triggers ...................................................................................................................................... 676
Show Commands .............................................................................................................................................. 679
Example of Modifying a State Machine ................................................................................................... 682
State Machine Crosschecks .............................................................................................................................. 683
22. Channel Bonding................................................................................................................................... 685
Channel Assignment ......................................................................................................................................... 685
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
25
CM Channel Selection .............................................................................................................................. 686
Service Flow Channel Selection................................................................................................................ 689
Downstream Channel Bonding (DSCB) ............................................................................................................. 690
RCP/RCC ................................................................................................................................................... 694
Configuration Examples for Static RCC .................................................................................................... 697
Configuring Channel Bonding Groups ...................................................................................................... 699
Per-packet Channel Selection for Bonding Groups .................................................................................. 700
Upstream Channel Bonding (USCB) .................................................................................................................. 700
Enhanced USCB Scaling ............................................................................................................................ 701
TCS Optimization for Static US Bonding Groups ...................................................................................... 702
TCS Reduction Enhancement ................................................................................................................... 702
Upstream Graceful TCS Reduction ........................................................................................................... 703
Selective Enabling of USCB within a MAC Domain ........................................................................................... 703
Non-Primary Channel Acquisition for Upstream Channel Bonding .................................................................. 705
Partial Service Handling .................................................................................................................................... 706
Upstream Impairment Detection and Recovery ...................................................................................... 706
Partial Service Enhancement ................................................................................................................... 707
Ranging Timing Offset .............................................................................................................................. 708
Downstream Impairment Detection and Recovery ................................................................................. 708
Sequence Out of Range Recovery ............................................................................................................ 709
CM Channel Reassignment for AC Power Loss ........................................................................................ 710
CM-STATUS Message ............................................................................................................................... 711
Related CLI Commands ............................................................................................................................ 711
Observability ..................................................................................................................................................... 712
23. IPv6 ...................................................................................................................................................... 715
Overview .................................................................................................................................................. 715
MDF .......................................................................................................................................................... 716
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
26
GMAC Explicit Mode ................................................................................................................................ 716
IPv6 Packet Structure ........................................................................................................................................ 716
IPv6 Addressing Architecture............................................................................................................................ 717
Address Notation ..................................................................................................................................... 717
Types and Scope of Addresses ................................................................................................................. 717
Interface Assignment ............................................................................................................................... 718
General Limits for IP Addresses ............................................................................................................... 719
Link-Local Addresses ................................................................................................................................ 719
Neighbor Discovery Proxy for CPE Traffic ................................................................................................ 720
IPv6 over Ethernet ................................................................................................................................... 721
Well-Known Multicast Addresses ............................................................................................................ 721
C4/c CMTS Security Features for IPv6 .............................................................................................................. 723
IPv6 Configure Commands................................................................................................................................ 724
Neighbor Discovery Commands ............................................................................................................... 725
Router Advertisements for IPv6 ............................................................................................................... 727
DHCPv6 Relay Agent ................................................................................................................................ 727
Basic Configuration Script ........................................................................................................................ 727
Ping and Traceroute Commands .............................................................................................................. 728
IPv6 Show Commands .............................................................................................................................. 729
IPv6 Show Cable Modem Commands ...................................................................................................... 730
Proxy Duplicate Address Detection.......................................................................................................... 731
DHCPv6 PDRI and Bulk Lease Query ................................................................................................................. 731
Prefix Delegation ...................................................................................................................................... 732
CLI Commands for PDRI ........................................................................................................................... 733
Bulk Lease Query ...................................................................................................................................... 735
Examples of Show Commands ................................................................................................................. 736
IPv6 Prefix Stability ........................................................................................................................................... 739
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
27
Using Prefix-Stability ................................................................................................................................ 739
Configuring Prefix Stability Using IS-IS ..................................................................................................... 740
Configuring Prefix Stability Using OSPF.................................................................................................... 742
Operational Concerns .............................................................................................................................. 747
IPv6 Distribute Lists ........................................................................................................................................... 748
Sample Distribute List for OSPFv3 PD Routes .......................................................................................... 748
24. IP Video ................................................................................................................................................ 750
Overview ........................................................................................................................................................... 750
IP Video Functionality ....................................................................................................................................... 752
Video CPE ................................................................................................................................................. 753
Video Management .................................................................................................................................. 753
Video Access ............................................................................................................................................. 753
Valid Multicast Address Ranges ............................................................................................................... 754
ASM Architecture .............................................................................................................................................. 754
ASM Components..................................................................................................................................... 755
SSM Architecture .............................................................................................................................................. 756
SSM Components ..................................................................................................................................... 757
IP Video Provisioning ........................................................................................................................................ 758
ASM Configuration ................................................................................................................................... 758
PIM-SM Configuration .............................................................................................................................. 762
Additional Configuration References ....................................................................................................... 763
IP Video Visibility............................................................................................................................................... 764
Verifying the Configuration ...................................................................................................................... 764
IP Video Monitoring and Management ............................................................................................................ 771
Current Hour Results ................................................................................................................................ 772
CLI Commands for IP Video ............................................................................................................................... 774
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
28
25. Multicast .............................................................................................................................................. 776
Overview ........................................................................................................................................................... 776
IP Multicast ....................................................................................................................................................... 777
What is IP Multicast? ............................................................................................................................... 777
Multicast Traffic ................................................................................................................................................ 777
MDF .......................................................................................................................................................... 777
Multicast Routing ..................................................................................................................................... 778
Valid Multicast Address Ranges ............................................................................................................... 778
IGMP Implementation ...................................................................................................................................... 779
Source-Specific Multicast ......................................................................................................................... 779
Multicast Routing Configurations ..................................................................................................................... 780
ASM/SSM Configurations ......................................................................................................................... 781
IGMP Visibility .......................................................................................................................................... 783
Static IGMP Joins ...................................................................................................................................... 787
Forced Downstream Replication of Multicast Traffic ....................................................................................... 789
Operational Guidelines ..................................................................................................................................... 790
Effects of Enabling MDF on the MAC Domain .................................................................................................. 791
CLI Commands .................................................................................................................................................. 792
26. Connection Admission Control .............................................................................................................. 796
Overview ........................................................................................................................................................... 796
General CAC Description ................................................................................................................................... 797
Reserved Bandwidth ................................................................................................................................ 797
PacketCable CAC Description............................................................................................................................ 797
Multicast CAC Description ................................................................................................................................ 798
Guidelines for CAC Thresholds in Non-converged System ...................................................................... 799
Guidelines for CAC Thresholds in Converged System .............................................................................. 800
Configuring CAC ................................................................................................................................................ 800
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
29
Show Commands .............................................................................................................................................. 801
Preemption of Normal Calls by Emergency Calls ..................................................................................... 803
Data Consistency Checks................................................................................................................................... 803
Load Balancing of Voice Bearer Flows .............................................................................................................. 804
27. Converged Services (Voice and Data)..................................................................................................... 806
Overview ........................................................................................................................................................... 806
QoS Levels ......................................................................................................................................................... 806
Ensuring QoS in a Converged Services Environment ............................................................................... 806
Overload Conditions ................................................................................................................................. 808
28. PacketCable™ Services and Voice Applications ...................................................................................... 810
PacketCable Overview ...................................................................................................................................... 810
PacketCable Multimedia Overview ................................................................................................................... 813
Compliance with PCMM Standards.......................................................................................................... 816
PCMM Classification for Remotely Connected Subnets .......................................................................... 817
PCMM Configuration Procedures ............................................................................................................ 820
PacketCable Settings ................................................................................................................................ 821
DSx DQoS VoIP ......................................................................................................................................... 830
29. Security ................................................................................................................................................ 832
AAA Overview ................................................................................................................................................... 832
The AAA Model ........................................................................................................................................ 833
Line Interfaces .......................................................................................................................................... 834
AAA Functions Supported by the C4/c CMTS........................................................................................... 835
Local Authentication ......................................................................................................................................... 836
RADIUS Authentication ..................................................................................................................................... 837
RADIUS Servers and Server Groups.......................................................................................................... 837
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
30
RADIUS Access Challenge ......................................................................................................................... 840
TACACS+ ............................................................................................................................................................ 843
TACACS+ Description................................................................................................................................ 843
TACACS+ Servers and Server Groups ....................................................................................................... 844
Authentication Method Lists.................................................................................................................... 845
Authorization Method Lists...................................................................................................................... 845
Accounting Method Lists.......................................................................................................................... 846
Common CLI Commands for AAA Using TACACS ..................................................................................... 846
Enable TACACS Authentication ................................................................................................................ 848
Configuring the C4/c CMTS to Enable Password ..................................................................................... 848
TACACS+ Source Interface ................................................................................................................................ 852
Operational Concerns .............................................................................................................................. 852
Feature Interactions ................................................................................................................................. 853
Configuring TACACS+ Source Interface .................................................................................................... 853
Sample Show Commands ......................................................................................................................... 854
SSH2 .................................................................................................................................................................. 855
SSH2 Description ...................................................................................................................................... 855
Server Management................................................................................................................................. 856
Configure Commands ............................................................................................................................... 857
Show Commands...................................................................................................................................... 860
Routing to a Null Interface ................................................................................................................................ 861
CLI Commands for Routing to a Null Interface ........................................................................................ 861
Source Verification of Cable-side IP Addresses ................................................................................................ 862
For IPv6..................................................................................................................................................... 862
CLI Commands for Source Verification .................................................................................................... 863
CPE Host Authorization ..................................................................................................................................... 864
CLI Commands .......................................................................................................................................... 865
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
31
Advanced CM Configuration File Verification ................................................................................................... 866
TFTP Enforcement .................................................................................................................................... 867
Dynamic Shared Secret Verification ......................................................................................................... 867
Log Messages ........................................................................................................................................... 870
TFTP Relay Agent and the Upgrade Server TLV ....................................................................................... 870
Option 125, Sub-option 2 ......................................................................................................................... 871
DHCPv6 Servers Address—Option 32 ...................................................................................................... 871
Dual Shared Secret ................................................................................................................................... 871
Cable Modem MAC Deny List................................................................................................................... 873
30. Unified Electronic Surveillance .............................................................................................................. 875
UES Overview .................................................................................................................................................... 875
CALEA ................................................................................................................................................................ 875
Electronic Surveillance Configuration ...................................................................................................... 877
Electronic Surveillance Logging Messages ............................................................................................... 877
Legal Intercept .................................................................................................................................................. 878
Feature Operation .................................................................................................................................... 880
Chassis Configuration ............................................................................................................................... 881
CLI Commands .......................................................................................................................................... 881
Sample Configuration for Secure Access and Tap .................................................................................... 881
Create or Delete an LI tap on IPv6 Modem .............................................................................................. 883
Data Management and Maintenance ...................................................................................................... 884
PC 2.0 Lawfully Authorized Electronic Surveillance .......................................................................................... 884
Additional Guidelines ............................................................................................................................... 885
Configuring PC 2.0 LAES ........................................................................................................................... 886
Configuration Guidelines.......................................................................................................................... 886
Configure SNMPv3 User View .................................................................................................................. 888
Configure Intercept Source Interface....................................................................................................... 889
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
32
31. Load Balancing...................................................................................................................................... 890
Overview ........................................................................................................................................................... 891
Load Balancing Groups ..................................................................................................................................... 891
General Load Balancing Group (GLBG) .................................................................................................... 891
Restricted Load Balancing Group (RLBG) ................................................................................................. 892
Load Balancing Methods................................................................................................................................... 893
Load Balancing Types ........................................................................................................................................ 893
Interactions with Older Cable Modems ................................................................................................... 894
Load Balancing Policy ........................................................................................................................................ 895
Load Balancing Rules ........................................................................................................................................ 895
Relative Weighting ................................................................................................................................... 897
Using Multiple Rules ................................................................................................................................ 897
Global Load Balance Settings ............................................................................................................................ 898
Load Balance Thresholds .................................................................................................................................. 899
Default Configuration ....................................................................................................................................... 900
Example Configuration...................................................................................................................................... 902
Verify the Configuration ........................................................................................................................... 903
Load Balance Modem Steering ......................................................................................................................... 905
Rule-based Modem Steering.................................................................................................................... 905
Steering to RLBG ...................................................................................................................................... 908
Service-type Modem Steering.................................................................................................................. 909
Load Balance Actions ........................................................................................................................................ 912
Ranging Time Load Balance Actions......................................................................................................... 912
Registration Time Load Balance Actions .................................................................................................. 913
Periodic Load Balancing Actions .............................................................................................................. 915
Load Balancing Bonded DS and US Modems via DBC .............................................................................. 917
Load Balancing Bonded Modems via DCC ............................................................................................... 919
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
33
Cross-MAC Domain Dynamic Load Balancing .......................................................................................... 919
Statistics ................................................................................................................................................... 920
Failed List Operation ......................................................................................................................................... 921
Exclude List Operation.............................................................................................................................. 923
Movable and Non-movable Modems ............................................................................................................... 923
DCC Movable Checks ................................................................................................................................ 923
DBC Movable Checks ................................................................................................................................ 924
Movable CLI Commands ................................................................................................................................... 925
Manual Modem Moves ..................................................................................................................................... 926
CLI Modem Move via DCC ........................................................................................................................ 926
CLI Modem Move via DBC ........................................................................................................................ 927
CLI Modem Move via Range Response .................................................................................................... 927
CLI Modem Move via DCC Using MIBs ..................................................................................................... 928
32. Packet Throttling .................................................................................................................................. 930
Overview ........................................................................................................................................................... 930
RCM Protocol Policing ....................................................................................................................................... 931
Maintaining Performance During Excessive Traffic ................................................................................. 931
RCM Protocol CLI Commands................................................................................................................... 931
Upstream Cable Protocol Throttling ................................................................................................................. 933
IPv6 Neighborhood Discovery .................................................................................................................. 934
ARP/ND Monitoring ................................................................................................................................. 934
Cable Protocol Throttling Configuration .................................................................................................. 935
Throttling Configuration Clear and Show Commands ............................................................................. 935
Cable Throttling Command Examples ...................................................................................................... 936
ARP/ICMP Throttling ......................................................................................................................................... 940
Configure ARP Throttling Commands ...................................................................................................... 940
Default Configuration for ARP Throttling ................................................................................................. 942
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
34
Quality of Service Mechanisms ......................................................................................................................... 943
Statistical Multiplexing ............................................................................................................................. 943
Weighted Random Early Detection and Traffic Policing .......................................................................... 943
Traffic Shaping .......................................................................................................................................... 943
Traffic Shaping CLI Commands ......................................................................................................................... 945
Set Peak Traffic Rate for DOCSIS 1.1 COS ................................................................................................ 945
Set Peak Traffic Rate for QOS................................................................................................................... 946
Power Boost Cap ............................................................................................................................................... 946
Peak and Maximum Rates ........................................................................................................................ 946
Enable/Disable Peak Rate Service Flow ................................................................................................... 946
Service Flow Information ......................................................................................................................... 946
Upstream Tpeak ....................................................................................................................................... 947
33. Access Control Lists ............................................................................................................................... 948
Overview ........................................................................................................................................................... 948
Named Access Lists .................................................................................................................................. 949
Data Plane Filter IP ACLs ................................................................................................................................... 950
IPv4 CLI Commands .................................................................................................................................. 950
Match Counts ........................................................................................................................................... 952
In-band Management ....................................................................................................................................... 953
Provision In-band Management............................................................................................................... 953
SNMP ACL ................................................................................................................................................. 954
IGMP ACLs ......................................................................................................................................................... 954
Example 1 ................................................................................................................................................. 955
Example 2 ................................................................................................................................................. 955
IPv6 ACLs ........................................................................................................................................................... 955
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
35
34. Internet Protocol Detail Record ............................................................................................................. 957
Overview ........................................................................................................................................................... 957
Exporter Services .............................................................................................................................................. 958
IPDR Session Methods.............................................................................................................................. 958
IPDR Records ............................................................................................................................................ 958
Method and Record Usage....................................................................................................................... 959
Sequence of Records ................................................................................................................................ 959
Exporter Address ...................................................................................................................................... 960
Collector Connectivity ....................................................................................................................................... 960
Redundancy .............................................................................................................................................. 960
Simultaneous Sessions ............................................................................................................................. 961
Inter-Operations ............................................................................................................................................... 961
Data Acknowledgment ............................................................................................................................. 961
Keep Alive ................................................................................................................................................. 962
Missed Interval ......................................................................................................................................... 962
Surveillance ....................................................................................................................................................... 962
Connection Logs ....................................................................................................................................... 962
Session Logs.............................................................................................................................................. 963
SNMP Traps .............................................................................................................................................. 963
Configuration .................................................................................................................................................... 963
Parameters ............................................................................................................................................... 963
IPDR CLI Commands ................................................................................................................................. 965
35. Host Names, User IDs, and Password Recovery ..................................................................................... 970
How to Administer the Host Name and User IDs ............................................................................................. 970
Configure a Host Name ............................................................................................................................ 970
Syslog Server IPAddress ........................................................................................................................... 971
How to Add and Delete Users ........................................................................................................................... 971
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
36
Add or Delete Users ................................................................................................................................. 971
Passwords in show running-config .......................................................................................................... 972
Configuring Privilege Levels and Local Authentication ..................................................................................... 972
User Profiles ...................................................................................................................................................... 973
Creating a Global User Profile .................................................................................................................. 973
Creating a User Profile ............................................................................................................................. 974
Password Recovery ........................................................................................................................................... 975
Enabling Password Recovery Using the Application Dialog ..................................................................... 975
Sample Bootloader Dialog for Password Recovery .................................................................................. 976
36. Clock Synchronization Protocol ............................................................................................................. 980
Overview ........................................................................................................................................................... 980
Local (Internal) Clock ........................................................................................................................................ 980
Clock Commands ...................................................................................................................................... 981
Setting the Internal Clock ......................................................................................................................... 984
Network Time Protocol ..................................................................................................................................... 985
NTP Server Commands............................................................................................................................. 985
Configure NTP Client ................................................................................................................................ 986
Secure NTP ........................................................................................................................................................ 989
37. Service Class Names .............................................................................................................................. 991
Overview ........................................................................................................................................................... 991
Service Class Name Details ............................................................................................................................... 992
Service Flows ............................................................................................................................................ 992
Major Functions ....................................................................................................................................... 992
Quality of Service Parameters MIB .......................................................................................................... 993
Service Class Name Configuration ........................................................................................................... 996
Service Classes .................................................................................................................................................. 996
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
37
Gold Service Class Example ...................................................................................................................... 996
Silver Service Class Example ..................................................................................................................... 997
Bronze Service Class Example .................................................................................................................. 997
Tiered Service Examples ........................................................................................................................... 997
Additional Service Flows .......................................................................................................................... 998
Commands for Adding Service Class Names ..................................................................................................... 999
Integrated Service Class Agility (ISCA) ............................................................................................................ 1001
Operational Considerations for ISCA .............................................................................................................. 1001
Calculating Average Usage .............................................................................................................................. 1003
Feature Interactions........................................................................................................................................ 1003
CLI Commands Used for ISCA .......................................................................................................................... 1004
Dynamic Service Class Modifications .............................................................................................................. 1007
Operational Considerations for Dynamic Service Class Modifications .................................................. 1007
CLI for Dynamic Service Class Modifications .......................................................................................... 1008
Sample Show Commands ....................................................................................................................... 1009
DSCP Marking for Downstream Subscriber Traffic ......................................................................................... 1010
38. Per-Subscriber Throughput ................................................................................................................. 1012
Overview ......................................................................................................................................................... 1012
Throughput ..................................................................................................................................................... 1012
Class and Quality of Service ................................................................................................................... 1013
Determining Throughput ....................................................................................................................... 1013
Configuration File ................................................................................................................................... 1013
Displaying Throughput ........................................................................................................................... 1013
Two Display Formats ....................................................................................................................................... 1013
Display Basic CM QoS Output ................................................................................................................ 1014
Display Verbose CM QoS Output ........................................................................................................... 1015
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
38
39. Additional Classifier Support ............................................................................................................... 1018
Overview ......................................................................................................................................................... 1018
Description ...................................................................................................................................................... 1018
Operation ........................................................................................................................................................ 1020
Multiple Grants Per Interval (MGPI) ...................................................................................................... 1021
Maximum Active Call Capacity ............................................................................................................... 1021
Dynamic Tmin and Tmax ........................................................................................................................ 1021
40. Diagnostics ......................................................................................................................................... 1022
Overview ......................................................................................................................................................... 1022
Problem Isolation ............................................................................................................................................ 1023
Module Replacement and Repair .......................................................................................................... 1023
Applicable Modules................................................................................................................................ 1023
Diagnostic Rules ..................................................................................................................................... 1023
Service-Affecting Protection .................................................................................................................. 1024
System Log ............................................................................................................................................. 1024
Take Module Out-of-Service ........................................................................................................................... 1024
Diagnosing Modules ....................................................................................................................................... 1025
To Diagnose Modules ............................................................................................................................. 1025
Diagnostic Logging .......................................................................................................................................... 1028
Diagnostic Failure and Recovery ..................................................................................................................... 1029
Diagnostic Failure ................................................................................................................................... 1029
Recovery ................................................................................................................................................. 1030
41. Logging ............................................................................................................................................... 1031
Overview ......................................................................................................................................................... 1031
Event Messages .............................................................................................................................................. 1032
Asynchronous Notification Management .............................................................................................. 1032
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
39
Event Management Subsystems ............................................................................................................ 1032
History Buffer ......................................................................................................................................... 1033
System Consoles ..................................................................................................................................... 1033
Monitor .................................................................................................................................................. 1034
Local Log (Volatile and Non-Volatile) ..................................................................................................... 1034
Syslog Server .......................................................................................................................................... 1034
SNMP Management Station ................................................................................................................... 1034
Event Message Routing ................................................................................................................................... 1034
Priority-Based Event Routing ................................................................................................................. 1035
Event Routing Sequence ........................................................................................................................ 1035
Logging History Buffer..................................................................................................................................... 1036
Restrictions and Defaults for Logging History Buffer ............................................................................. 1036
Basic Log Commands .............................................................................................................................. 1036
Change Message Number ...................................................................................................................... 1038
Enable Debug Facility Notification ......................................................................................................... 1039
Disable Debug Facility Notification ........................................................................................................ 1039
Override Priority Settings ....................................................................................................................... 1039
Assign Priority to CLI Access Level.......................................................................................................... 1039
List Available Show Commands .............................................................................................................. 1040
Display Event Management Subsystems ............................................................................................... 1040
Display Debug Information .................................................................................................................... 1042
Display Logging History (Last Number of Events) .................................................................................. 1043
Display Logging History (Slot Number) .................................................................................................. 1044
Display Event Logging Overrides ............................................................................................................ 1045
Display CLI Access Levels and Priority .................................................................................................... 1045
Display Proprietary Logging Status ........................................................................................................ 1046
System Console ............................................................................................................................................... 1046
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
40
Asynchronous Terminal Connection ...................................................................................................... 1047
Display Monitor Priority ......................................................................................................................... 1047
System Console Session ......................................................................................................................... 1047
Event Display on System Console .......................................................................................................... 1047
System Console Log Commands ............................................................................................................ 1047
Configure Console Logging ..................................................................................................................... 1048
Eliminate Console Logging ..................................................................................................................... 1048
Monitor (Telnet or Secure Shell) .................................................................................................................... 1048
Telnet ..................................................................................................................................................... 1049
Secure Shell ............................................................................................................................................ 1049
Secure Shell-2 ......................................................................................................................................... 1049
Monitor Log Commands......................................................................................................................... 1049
Configure Monitor Logging .................................................................................................................... 1050
Eliminate Monitor Logging ..................................................................................................................... 1050
Display Console Priority ......................................................................................................................... 1050
Local Log (Volatile) .......................................................................................................................................... 1050
Syslog Server and SNMP Management Station ..................................................................................... 1051
Local Volatile Log Commands ................................................................................................................ 1051
Configure Local Logging Level ................................................................................................................ 1052
Disable Specific Local Logging Level ....................................................................................................... 1052
Configure Local Log Size ......................................................................................................................... 1052
Display Local Log Priority ....................................................................................................................... 1053
Syslog Server ................................................................................................................................................... 1053
Standard Protocol .................................................................................................................................. 1053
Multiple Syslog Servers .......................................................................................................................... 1053
Event Priorities ....................................................................................................................................... 1054
Syslog Facilities ....................................................................................................................................... 1054
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
41
Syslog Host IP Address ........................................................................................................................... 1055
Syslog Server Commands ....................................................................................................................... 1055
Send All Messages to Specific Server ..................................................................................................... 1056
Add Syslog Server ................................................................................................................................... 1056
Remove Syslog Server ............................................................................................................................ 1056
Send All Informational Messages to Syslog ........................................................................................... 1056
Disable Informational Messages to Syslog ............................................................................................. 1056
Inhibit Events to Syslog .......................................................................................................................... 1057
Display Syslog Statistics and Server(s) ................................................................................................... 1057
Simple Network Management Protocol Management Station ...................................................................... 1057
Traps ....................................................................................................................................................... 1057
Event Priorities ....................................................................................................................................... 1058
SNMP Management Station Host IP Address ........................................................................................ 1058
SNMP Host Commands .......................................................................................................................... 1058
Generate Trap for Priority 7 ................................................................................................................... 1059
Disable Trap for Priority 7 ...................................................................................................................... 1059
Configure SNMP Server to Existing Network ......................................................................................... 1059
Display SNMP Utilization Statistics ........................................................................................................ 1060
SNMP Trap Control Commands ............................................................................................................. 1060
SNMP Configuration with CLI ................................................................................................................. 1061
Throttle Control of Event Messages....................................................................................................... 1066
42. Fully-Qualified Domain Name (FQDN) ................................................................................................. 1070
Overview ......................................................................................................................................................... 1070
Limited Support for FQDN Feature ........................................................................................................ 1071
Operational Concerns ..................................................................................................................................... 1071
CLI Commands................................................................................................................................................. 1073
FQDN Rejection Scenarios .............................................................................................................................. 1075
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
42
43. BSoD L2VPN........................................................................................................................................ 1076
BSoD L2VPN Configuration via CLI .................................................................................................................. 1087
44. Standard and Enterprise MIBs ............................................................................................................. 1090
Overview ................................................................................................................................................ 1090
SNMP MIB Variable Descriptions .................................................................................................................... 1090
Enterprise MIBs............................................................................................................................................... 1094
45. CLI Overview....................................................................................................................................... 1099
Overview ................................................................................................................................................ 1099
Access Levels and Modes ................................................................................................................................ 1099
User EXEC ............................................................................................................................................... 1100
Privileged EXEC ....................................................................................................................................... 1100
CLI Command Modes ............................................................................................................................. 1100
Designating MAC addresses and IP addresses ....................................................................................... 1104
Keyboard Shortcuts......................................................................................................................................... 1105
CLI Command Features ................................................................................................................................... 1106
CLI Help Feature ..................................................................................................................................... 1107
Configuring Passwords and Privileges.................................................................................................... 1110
CLI Filtering ..................................................................................................................................................... 1115
Basic Searching ....................................................................................................................................... 1115
How to Use CLI Filtering ......................................................................................................................... 1115
Show Cable Modem Column Feature ............................................................................................................. 1123
Command Parameters ........................................................................................................................... 1123
Help Enhancements ............................................................................................................................... 1125
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
43
46. Command Line Descriptions ................................................................................................................ 1127
47. Alphabetical List of CLI Commands ...................................................................................................... 3085
48. Abbreviations ..................................................................................................................................... 3171
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
44
Chapter 1
Introduction
Overview
As of early 2008 ARRIS has deployed more than 4600 C4 CMTSs supporting over millions of subscribers. Beginning with
Software Release 7.1 ARRIS introduced the C4c CMTS which was based on the larger C4 CMTS.
The C4c CMTS is a compact version of the full-sized C4 CMTS. Because it measures only 7 rack units (RUs) — half the height
of the C4 CMTS, it is ideal for headends with space or environmental limitations. It is meant for MSOs or headends that do
not need to support as many subscribers as the C4 CMTS. The C4c CMTS is based on the same field-proven DOCSIS 3.0
hardware and software that goes into the C4 CMTS.
The C4c CMTS has been designed to meet the needs of the Multiple System Operator (MSO) in terms of system density,
wire-speed performance, and reliability. Like the C4 CMTS, the C4c CMTS enables MSOs to bundle high-speed data, voice,
full-motion video, and other multimedia content to residential and business customers.
Intended Audience
This document is intended for MSO technical support personnel who are responsible for integrating, operating, and
maintaining the CMTS.
Prerequisite Skill and Knowledge
This document serves as an introduction to the CMTS for all administrators and users of cable modem termination
systems. Ideally, users of this documentation and equipment should have a basic knowledge of the following:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
45
Chapter 1: Introduction
RF measuring equipment
Provisioning servers
Command Line Interface (CLI) commands
RF cable plant and operating methods.
Purpose
To provide a comprehensive overview of the C4 and C4c CMTS including reference and procedural information required to
manage and control the C4 and C4c CMTS.
Conventions Used in this Document
This section presents the textual conventions used in this documentation set.
Textual Conventions
The conventions used in this guide are shown in the following table:
Table 2. Examples of Textual Conventions
Type of text
Description
Example
CLI commands and other user input
Monospaced bold
configure slot <17-18> type RCM
Names of chapters and manuals
Italicized text
chapter 1, About This Manual
Menu selections
Plain-faced text
From the File>Set-up menu choose…
System responses and screen display Monospaced font
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Time since the CMTS was last booted:
12 days, 2: 8: 14 <hr:min:sec>
C4® CMTS Release 8.3 User Guide
46
Chapter 1: Introduction
Admonishments
There are three levels of admonishments used in this documentation. The first is a simple note.
Note: Notes are intended to highlight additional references or general information related to a procedure, product, or
system.
The international symbols, Caution and Warning, appear in this book to indicate actions involving risk.
Caution indicates a risk of dropping traffic, losing data, or disrupting the equipment. Read the accompanying instructions
and proceed with caution.
WARNING The warning symbol represents a risk of bodily injury or serious damage to the equipment. Before you work on
any equipment, be aware of the hazards involved with electrical circuitry and fiber optics and follow standard procedures
for preventing accidents and serious damage.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
47
Chapter 2
C4/C4c CMTS Features
This chapter contains the C4/C4c CMTS descriptive and reference information along with the Features list.
DOCSIS 2.0 Compliance ...................................................................... 48
DOCSIS 3.0 Compliance ...................................................................... 49
Fault Detection and Recovery ............................................................ 50
Interfaces and Protocols .................................................................... 50
Security Features ............................................................................... 50
Baseline Features and Early Releases ................................................ 51
DOCSIS 2.0 Compliance
In December, 2004, the C4 Cable Modem Termination System (CMTS) received DOCSIS® 2.0 requalification by CableLabs®
with the new software upgrade designed to support DOCSIS Set-top Gateway (DSG) technology. With this qualification, the
C4 CMTS, configured with the higher density 2Dx12U CAM provided the most reliable and scalable C4 CMTS solution
available.
The C4 CMTS supports DOCSIS Set-Top Gateway (DSG), allowing operators to transition the signaling, provisioning, and
control of advanced set-top boxes from proprietary to standards-based protocols. This transition of all services to IP-based
standards is expected to streamline operations and lower capital costs for cable operators.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
48
Chapter 2: C4/C4c CMTS Features
The DOCSIS 2.0 standard greatly improves performance in the upstream path of the cable network. The growing demand
for peer-to-peer file sharing, interactive gaming, and voice over IP telephony increases the need for upstream bandwidth.
The following enhancements are available to CMTSs and CMs that comply with the 2.0 standard while maintaining all the
DOCSIS 1.1 and 1.0 functionality:
Enhanced upstream capacity
Greater maximum upstream throughput — up to 30.72 mbps per channel
Greater upstream channel width — up to 6.4 Mhz
New upstream channel modulation rates: 8QAM, 32QAM, and 64QAM
Longer preamble to facilitate synchronization — up to 1536 bits
Higher powered preamble — QPSK-1
Enhanced noise cancelation and error correction
Synchronous-Code-Division Multiple Access (SCDMA) operation along with the standard TDMA and ATDMA techniques
for combining CM signals onto a given upstream channel.
DOCSIS 3.0 Compliance
In May 2008, the C4 CMTS received DOCSIS® 3.0 Bronze-level requalification by CableLabs®in Certification Wave 58.
The following features were added to the ARRIS C4 CMTS as part of the DOCSIS 3.0 initiative while maintaining total
compatibility with deployed pre-3.0 DOCSIS devices:
Independent Scalability of Upstream and Downstream Channels
Management of Multiple Upstream and Downstream Channels per MAC Domain
Enhanced Cable Plant Infrastructure Management
Cable Modem Topology Resolution
Downstream Channel Bonding
IPv6 Management of CMs and Forwarding of CPE Traffic
Enhanced Operations Support System Interface.
The ARRIS C4c CMTS is a compact DOCSIS 3.0 CMTS based on the proven hardware and software of the larger C4 CMTS
solution.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
49
Chapter 2: C4/C4c CMTS Features
Fault Detection and Recovery
The C4/C4c CMTS employs:
Advanced data-path integrity checks (parity, CRC, loopbacks, pings)
Continuous system audits
Multiple levels of error detection.
Fault recovery on the C4/C4c CMTS:
Rapidly isolates faults
Decreases diagnostic and repair time
Reduces the probability of fault propagation
Minimizes impact on subscriber services.
Interfaces and Protocols
Open interfaces and protocols allow seamless integration with existing network management infrastructures. The primary
protocols supported by the C4/C4c CMTS include the following:
Simple Network Management Protocol (SNMP) — v1, v2c, and v3
DOCSIS 1.1, DOCSIS 2.0, DOCSIS 3.0 (Bronze), and Cadant MIBS
Command Line Interface (CLI)
File Transfer Protocol (FTP)
Telnet
Routing Information Protocol (RIPv2)
Open Shortest Path First (OSPFv2)
Open Shortest Path First (OSPFv3)
Security Features
Unique security measures ensure plant and subscriber integrity through:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
50
Chapter 2: C4/C4c CMTS Features
DOCSIS 1.1 BPI+ encryption
Administrative isolation by means of a separate physical interface
Packet filtering
Proxy ARP
Password and key authentication for RIP and OSPF
Secure Shell version 2 (SSH2)
Secure Shell (SSH)
Access Control Lists (ACLs)
Multi-stage Denial of Service throttling mechanisms in hardware and software
TACACS+
Protocol throttling
SNMP Security.
Baseline Features and Early Releases
The ARRIS C4/C4c CMTS Release 8.3 aggregated Feature Set is comprised of the Baseline Feature Set, plus the features of
software Releases 3.0, 3.3, 4.0, 4.1, 4.2, 5.0, 7.0, 7.1, 7.2, 7.3, 7.4, 8.0, 8.1, the Small Feature Release 8.1.5, 8.2, 8.2.5, and
8.3.
Release 3.0 Features
The following features were added with Release 3.0:
GigE Network Access Module (Gig-E NAM)
Authentication using RADIUS
SNMP Security
In-Band Management and Access Control Lists (ACLs)
Upstream Load Balancing (ULB)
Multiple syslog servers.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
51
Chapter 2: C4/C4c CMTS Features
Release 3.3 Features
The following features or improvements have been added for release 3.3:
PacketCable Qualification
Increased subscriber limits per chassis: 24K CM
Increased VoIP Call Capacities
Improved Password Recovery
Loopback Interface
Multiple Subinterfaces per VRF
Loopback Interfaces for routing protocols
Number of filters in group increased to 31
Support for Authentication, Authorization, and Accounting (AAA) [RADIUS & TACACS+]
In-Band Management: Access to the SCM via the loopback IP address
Support for Packet Cable
Automatic System Backup during Upgrade
Improved Baseline Privacy Interface (BPI)
Domain Name System (DNS) Support for Telnet, Traceroute, and Ping.
CLI Improvements:
extended ping command
show ip interface brief
show temperature
reset all CMs
traceroute CLI command
configure authorization
COS and 1.0 Modems
configure logging priority
configure privilege exec level.
Release 4.0 Features
The following features or improvements have been added for release 4.0:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
52
Chapter 2: C4/C4c CMTS Features
2Dx12U CAM — full DOCSIS 2.0 (A-TDMA and S-CDMA)
Proprietary automatic ingress noise cancellation
Flash disk re-partitioning
Graceful restart with OSPFv2
Real-time FFT of upstream (compatible with C3 CMTS MIBs)
NAM IP interface bundling
Increased subscriber limits per chassis: 32,000 CMs per chassis, and 3,000 CMs per downstream (500 per upstream in
1x6 operation)
Preemption of normal calls by new emergency calls when BW is limited
Additional audits: FCM, file system, 2Dx12U
CM reset clear trap
Flap List enhancements:
percent of station maintenance ranging opportunities that receive a range request
number of power adjustments exceeding a threshold
Number of CRC errors per CM (2D only)
Number of bytes dropped per CM (congestion and policing)
Virtual System Controller
CLI Improvements:
show/copy running-config
show cable qos profile
assign and display an output name or description for each interface.
To look up syntax and parameters for individual CLI commands, see Command Line Descriptions (page 1127). Each entry in
the alphabetical list of commands is hyperlinked to the appropriate page in the manual.
Automatic fan speed control
Encryption of MD5 shared secret for routing protocols in CLI output
Disabled ICMP Unreachables
OSPF "point-to-point" interface support
Increased AC/DC power solution
Voice call requirements:
At least 1,000 MTAs (Multimedia Terminal Adapters) per downstream
At least 5,000 BHCAs with completion rate of 99.5%
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
53
Chapter 2: C4/C4c CMTS Features
At least 260 half-calls per downstream.
Note: The voice call requirements are reduced by one-half in a mixed voice and data environment.
Release 4.1 Features
The following features or improvements have been added for release 4.1:
Committed Access Rate
Global Traffic Shaping for TCP Traffic
Remote Query of Cable Modems
Release 4.2 Features
The following features or improvements have been added for release 4.2:
DOCSIS Set-top Gateway (DSG) Agent
Associate ACL with SNMP Community String
Advanced CM Config File Verification
Scalability — 52K CMs per chassis
Modify overload control to ensure older CMs range/register in reasonable time through overload conditions (chassis
reboot, CAM insertion, etc.)
"Debug" IP Filter Packet Capture capability (ability to capture packet headers that match IP filters or similar
functionality)
PacketCable Multimedia
Network side ACLs
Support for 16 telnet sessions
Clear the IP filter counters through the CLI
Hitless software update
PacketCable 1.x Voice call requirements
MTAs /downstream (1D)
MTAs/downstream (2D)
MTAs/C4
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1000
1500
20000
C4® CMTS Release 8.3 User Guide
54
Chapter 2: C4/C4c CMTS Features
Lines/downstream
1800
Lines/C4
24000
BHCA/downstream
5000
BHCA/C4
66600
Simultaneous half calls/downstream
260
Programmable unicast request opportunity polling interval.
Note: The voice call requirements specifically assume that only GNAMs are used. If the system contains any FastENAMs,
the per-chassis line and MTA limits must be reduced to 1000.
Certain features may impact software upgrade procedures. For more information related to upgrades or for nonconformance issues, see the Cadant® C4®CMTS Software Upgrade Notes. This file is included on the software CD.
In addition to the previously described features and functionality, the following section describes the C4 CMTS feature set
for Release 5.0. This includes:
Release 5.0 Features
The following is a list of the new features included in Software Release 5.0.x:
FlexPath®
Dynamic Load Balancing
Legal Intercept
PIM-SSM
IGMP ACLs
Secure NTP
DHCP Test Injection
Named Access-List
Additional Modem States
Integrated Upstream Agility
Clear cable host/modem (MAC DB)
ARP Throttling
Number of supported VRFs increased to 32
Downstream center frequency step size is now 125 kHz (formerly 250)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
55
Chapter 2: C4/C4c CMTS Features
DOCSIS 1.1 DSx/DQOS and PacketCable 1.x Voice Scalability Improvements with Respect to Release 4.2:
MTAs/downstream (1D)
1,000 (no change)
MTAs/downstream (2D)
1,500 (no change)
MTAs/C4 equipped w/GNAMs
26,666
Lines/downstream
1,800 (no change)
Lines/C4
32,000
BHCA/downstream
5,000 (no change)
BHCA/C4
90,000
Simultaneous half calls/downstream
260 (no change)
Connections/second per chassis
25
Cable Modem Deny List
CPE Host Authorization
Configure Cable Modem Vendor OUI
Show Cable Modem Columns.
Note: These call capacities assume that the C4 CMTS is equipped with GNAMs. If the chassis is equipped with Ethernet
NAMs, the number of MTAs supported is only 10,000.
Dynamic Load Balancing — The Dynamic Load Balancing feature automatically moves modems from one upstream
channel to another, or from one downstream to another (including from one 2Dx12U CAM to another). Requires 2Dx12U
CAMs.
Legal Intercept — Legal Intercept provides the MSOs a mechanism for meeting legal requirements to intercept all IP data
and voice traffic originated or sent to subscribers on the cable network. Legal Intercept is based on Cisco’s implementation
described in RFC 3924. The C4 CMTS interprets SNMP SET/GETs to enable/clear/display subscriber taps and send
intercepted packets to the Mediation Device.
PIM-SSM — PIM-SSM (Source Specific Multicast) provides the capability to request multicast traffic from a single source
and build a source path tree (SPT) from the edge router back to the source of the multicast stream. It also contains
requirements to provide SSM multicast data plane counts.
IGMP ACLs — IGMP ACLs provide the ability to limit what multicast groups can be joined on an interface by using a
standard ACL to indicate what groups are allowed to be joined.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
56
Chapter 2: C4/C4c CMTS Features
Secure NTP — A mechanism is provided for authentication of NTP messages. For MSOs who require NTPv4 functionality,
including server or peer authorization, the C4 CMTS will only support the NTPv4 symmetric key MD5 secure hash
authentication method.
DHCP Text Injection — DHCP Text Injection will allow the operator to distinguish which upstream channels DHCP packets
originated from as they are forwarded to the DHCP server. The upstream will be identified in the circuit ID sub-option of
the DHCP relay agent option (option 82).
Named Access List — By allowing the use of a description name to identify an access list rather than a number, full
modification to an existing access-list (e.g., delete, append and insert new entries) by using the ACL name is now available.
Also, we are adding the ability to allow multiple remarks per access-list entry.
Additional Modem States — One additional cable modem state indicating the status of the Network Access Control for a
registered CM has been added. The CM’s Network Access Control state is provided via the modem configuration file. This
variable indicates whether or not CPE devices are allowed to access the network through the CM even though the CM is
registered.
Integrated Upstream Agility — This provides the ability to enable or disable an Upstream Agility state machine for an
upstream channel. The state machine includes permissible upstream channel frequencies and operating characteristics
(e.g., channel width, modulation profile) along with rules to change from one operating characteristic to another.
Clear Cable Host/Modem — Enabled the ability to remove cable modems and CPEs from the system including removing
them from the MACDB and C4 CMTS MIB tables.
ARP Throttling — Provides the ability to control the number of ARPS and ICMP packets that are generated due to traffic
transmitted to IP addresses that do not have a valid (active or inactive) entry in the ARP cache.
Configure Cable Modem Vendor OUI — This feature provides the ability to configure a cable modem vendor name with
the vendor’s Organizational Unique Identifier (OUI). The OUI is the first three bytes of the six byte CM MAC address.
Show Cable Modem Column — This new command will now allow you to create your own output by specifying exactly
which columns you wish to see, thus maximizing your screen space and run-time.
Release 5.1.x Features
The following is a list of the new features included in Software Release 5.1.x:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
57
Chapter 2: C4/C4c CMTS Features
FlexPath DOCSIS 3.0-based Channel Bonding Enhancements
Enhanced Query Modem Counts on a per Upstream Basis
DOCSIS Set-top Gateway Configuration Simplification
Source IP Configuration for CM Remote Query
DHCP Lease Query Feature Configurability
Automatic Gain Control
The 5.1 enhancements to the FlexPath channel bonding solution include the following:
3 bonded downstreams x 3 traffic-bearing unbonded upstreams
2 bonded downstreams x 2 traffic-bearing unbonded upstreams
4 bonded downstreams x 1 traffic-bearing unbonded upstream plus 3 non-traffic-bearing upstreams for return
path of DOCSIS management messages
Optional designation of upstream channels as FlexPath only
The Enhanced Query Modem Counts feature provides a CLI command--show cable modem summary brief--that offers
modem totals on a per-upstream basis. The total number of modems calculated per upstream includes registered,
unregistered, and offline modems.
DOCSIS Set-top Gateway (DSG) Configuration Simplification performs the automatic insertion of static multicast group
memberships and the automatic insertion of multicast MAC/IP bindings when configuring DSG tunnels.
Source IP Configuration for CM Remote Query allows the user to configure the IP address used for remote SNMP to get
queries to any valid C4 IP address.
DHCP Lease Query Feature Configurability adds a source IP address verification phase to the IP address learning process of
the C4 CMTS. This configurable Cable Source Verify feature is intended to eliminate host- initiated corruption of the layer 2
and layer 3 address spaces on the cable network.
Automatic Gain Control uses an improved downstream power calibration algorithm on the 2Dx12U in order to maintain
accurate downstream power levels in environments subject to fluctuating temperatures.
Note: QAM128 and Trellis Code Modulation (TCM) are not supported in Release 5.1. SCDMA is supported.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
58
Chapter 2: C4/C4c CMTS Features
Release 7.0.x Features
The Release 7.0 C4 CMTS is an integrated DOCSIS 3.0 solution in that it contains both downstream and upstream modules
and all associated CMTS components in a single chassis. The following is a list of the new features included in Software
Release 7.0.x:
Support for new hardware modules:
Router Control Module (RCM)
16D CAM
12U CAM (a repurposed 2Dx12U CAM configured in software to be a 12-upstream only CAM)
Upstream spectrum support as follows:
US
5-42 MHz
Japan
5-55 MHz
Europe
5-65 MHz
DOCSIS 3.0 DS Channel Bonding
DOCSIS 3.0 Topology/Infrastructure
DOCSIS 3.0 NMS support
IPv6 support on all interfaces
IPv6 for CM Management
New Hardware supported
Release 7.1.x Features
The following new features are included in Software Release 7.1.x:
Multiple Virtual Routing and Forwarding (VRF) instances
Full support of OSPF in five VRFs
Limited routing protocol support for 11 VRFs (Rel. 7.1.2 and later)
Cable Modem Steering — based on Service Type TLV (Rel. 7.1.2 and later)
Layer 3 802.1Q VLAN Tagging
Service Independent Intercept (SII) for Legal Intercept
DOCSIS 2.0-compliant IP Detail Record/Streaming Protocol (IPDR/SP)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
59
Chapter 2: C4/C4c CMTS Features
Compatibility with the Intelligent Channel Optimizer (ICO) (requires an updated version of ICO software, licensed
separately)
64 QAM Downstream Modulation
Increased Maximum Concatenated Burst Size
Baseline Privacy Interface (BPI) / DOCSIS 1.1 Hybrid Mode operation
DOCSIS 1.0+ Operation
Note: The DOCSIS 1.0+ Operation feature is not documented in this user manual; instead, it is described in an individual
feature sheet.
Release 7.2.x Features
The following new features are included in Software Release 7.2.x:
Upstream Channel Bonding
BGP
IS-IS Support in IPv4 Networks
ARP Abuse Counts
Dynamic MIC/TFTP Enforce
Per Subscriber Throughput
Secure NTP
Global User Profile
TACACS+
DOCSIS Ping
DNS Client (IPv4)
Enhancements to BGP
Mixed Annex Support
Modem Steering
SSH
Release 7.3.x Features
The following is a list of the new features included in Software Release 7.3.x:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
60
Chapter 2: C4/C4c CMTS Features
Business Services over DOCSIS (BSoD) L2 VPN
IPv6 Support (Phase 2)
Encryption Support with MTCM
Load Balancing Enhancements
Integrated Upstream Agility
BPI+ Enforce
Turbo Button Support
D3.0 IPDR Elements
D3.0 Partial Service Support
Bonding Support for 8 Downstreams
Device Classes
Subset of PacketCable PCMM version I04 Support
PCMM Classification for Remotely Connected Subnets
Cable Modem MAC Deny list increase — up to 1,000 addresses
Table 3. Summary of Support Capability for CAM Types
Capability
Supports IPv6 CMs
2D12U
X
Supports IPv6 CPEs
Supports IPv6 CM DS traffic
X
Supports IPv6 CM US traffic
X
12U
X
X
X
X
X
X
Supports IPv6 CPE DS traffic
X
Supports IPv6 CPE US traffic
X
Supports dual stack CPE
X
Support CM DS filtering traffic IPv4
X
Support CM US filtering traffic IPv4
X
Support CPE DS filtering traffic IPv4
X
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
16D
X
X
X
X
C4® CMTS Release 8.3 User Guide
61
Chapter 2: C4/C4c CMTS Features
Capability
Support CPE US filtering traffic IPv4
Support CM DS filtering traffic IPv6
2D12U
X
12U
16D
X
X
Support CM US filtering traffic IPv6
Support CPE DS filtering traffic IPv6
X
Support CPE US filtering traffic IPv6
Release 7.4.x Features
The following is a list of the new features in Software Release 7.4.x:
DHCP Prefix Delegation with Route Injection (PDRI)
IP Address Scaling per Chassis
OSPFv3
Cable Source Verify with DHCP Lease Query
DHCP Bulk Lease Query
Duplicate Address Detection Proxy
Subscriber Management Filters
Protocol Throttling
IPv6 Lawful Intercept Support (SII)
IPv6 CPE Support with DOCSIS 2.0+ IPv6 Cable Modems
Enhanced Density Downstream CAM
Mixed TDMA/ATDMA Channel Support for Load Balancing
Load Balancing Weighting toward Upstream Utilization
Cross-MAC Domain Dynamic Load Balancing
Cable Modem Move Enhancement
DSID Addition and Deletion
Counts-based US Load Balancing With Weighting
Modem Steering via Attribute Mask
Policy-Based Routing
12U Scaling Enhancement
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
62
Chapter 2: C4/C4c CMTS Features
SCDMA
IGMPv3-Controlled DOCSIS 3.0 IP Video
Release 8.0.x Features
The following is a list of the new features in Software Release 8.0.x:
24U CAM
IS-IS Multi-topology (MT) support
TFTP Enforce for IPv6-addressed Cable Modems
FQDN Support for IGMP Static Joins
Control of CM Resets due to CPE NAKs
Multicast CAC support for IP Video
Logical Channel Reduction
Enhanced Utilization Monitoring
The 24U CAM represents a new design using the latest DOCSIS 3.0 PHY and MAC silicon and enhanced ARRIS FPGAs for
high performance. The Upstream PICs have not changed from those used with the 12U CAM, so customers can deploy the
24U CAM with a minimum of cabling interruptions and allows the 24 upstream receivers to be shared across the eight
available F-connectors. The 2Dx12U CAM is not supported in Rel. 8.0.
Any F-connector can have between zero and 12 receivers assigned. The sum total of the receivers assigned to the evennumbered F-connectors (0,2,4,6) cannot exceed 12, and the sum total of the receivers assigned to the odd-numbered Fconnectors (1,3,5,7) cannot exceed 12. Also, upstreams 0 to 11 must be on even-numbered connectors, and upstreams 12
to 23 must be on odd-numbered connectors.
Some other features of the 24U CAM with Release 8.0 include:
Up to 6,600 total subscriber devices per CAM
Up to 9+1 hitless RF sparing
All 24 channels support bonding (up to four channels per bonding group)
IS-IS Multi-topology (MT) provides independent topologies for IS-IS routing and is particularly useful when IS-IS is being
used both for IPv4 routing and for migration to IPv6 routing. In this software release, the C4 CMTS supports MT #0 (IPv4
unicast) and MT #2 (IPv6 unicast) as described in RFC 5120.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
63
Chapter 2: C4/C4c CMTS Features
TFTP Enforce for IPv6-addressed Cable Modems provides modem security for devices addressed via IPv6, identical to the
existing C4 CMTS functionality for IPv4 modems. The intent of this feature is to reduce or prevent occurrences in which an
IPv6-addressed modem has an incorrect or modified configuration file.
Fully Qualified Domain Name (FQDN) Support for IGMP Static Joins allows the IGMP join command in the C4 CLI to accept
an FQDN as the IP multicast source address, instead of requiring an IP multicast address. The DNS must then contain the
FQDN to IP address entry so that the CMTS can obtain the corresponding IP address from the FQDN parameter. Should the
source IP multicast address have to change, the MSO would change it on the DNS and the C4 CMTS will then resolve the
new address via DNS and re-initiate IGMP joins as needed.
Multicast CAC for IP Video (Phase 1) extends the existing voice-oriented Connection Admission Control function to
multicast service flows (intended for IP Video applications). Independent CAC control is provided for multicast flows, and
parameters for reserving bandwidth for multicast and for limiting the total bandwidth utilized by multicast are included.
Enhanced Processor Monitoring reports the utilization levels of the various microprocessors within the C4 CMTS modules
(the control plane). There is a new SNMP notification as part of the processor monitoring feature that will send traps when
the overload status of a card or the system changes.
Release 8.1.x Features
The following is a list of the new features in Software Release 8.1.x:
DSG 3.0
IPv6 Route Scaling Expansion – Phase 2
SCM 3
PacketCable 2.0 LAES
Syslog Support for IUA State Changes
D3.0 Load Balancing of Voice Bearer FLows Enhancement
Radius Authentication
ARP Reduction
DSG 3.0 adds support for the DOCSIS 3.0-based revisions to the DOCSIS Set-top Gateway (DSG) functionality that is
described in CM-SP-DSG-I19-111117. The C4 CMTS will tag DSG multicast tunnels with the appropriate DSID when
multicast DSID forwarding (MDF) is enabled.
IPv6 Route Scaling Expansion – Phase 2 adds additional capacity for PDRI.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
64
Chapter 2: C4/C4c CMTS Features
SCM 3 is being introduced to improve capacity, performance, and materially extend the operation lifespan of the current
C4 CMTS. The SCM 3 will not coexist with previous versions of the SCM, SCM II, SCM II EM, or the SCM II EM (U).
PacketCable 2.0 LAES supports lawful intercept as specified int he PacketCable 2.0 LAES specification. This includes the
capability to intercept traffic specific to a particular IP address (or subnet) including the IP address or subnet of a particular
CPE behind a cable modem. Intercepts will function for both IPv4 and IPv6 addressed target devices.
Syslog Support for IUA State Changes will report IUA state changes via syslog. The C4 CMTS will indicate in the syslog each
occurrence of an IUA state change by including a timestamp and a description of the change incorporating both the
current state and the prior state. The syslog will also indicate the cable-mac and US channel where the state change took
place.
D3.0 Load Balancing of Voice Bearer Flows Enhancement provides a capability for load balancing of voice bearer traffic.
This encompasses distributing voice bearer traffic for DOCSIS 3.0 devices across available RF channels in both the
downstream and upstream. The voice traffic load balancing function will operate even if the existing downstream load
balancing of bonded modems is disabled.
Radius Authentication functionality will be implemented as part of the AAA feature.
ARP Reduction is being implemented to reduce the volume of IPv4 broadcast ARP messages and IPv6 multicast NS
messages issued by the C4 CMTS towards CMs. This will apply to both IPv4 broadcast ARP messages and IPv6 multicast NS
messages.
Release 8.1.5 -- Small Feature Release
The following is a list of the new features in the Small Feature Release 8.1.5:
32D Annex A Support
IS-IS Point-to-Point Links
IPv6 Security Enhancements
Support for Cable Modem Status for Out-of-Range
Downstream Output Power Loss- Detection and Recovery
24 Downstream Channel Bonding
Upstream-Only Cable Modem Move
Piggyback Support on RTP Flows
Show-tech-support brief
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
65
Chapter 2: C4/C4c CMTS Features
Provisionable Number of Upstream Equalizer Taps
Operation Mode to Not Store Bad BPI Certificates
32D Annex A Support provides the ability for the XD CAM to operate in a mode where it can support 32 Annex A (8 MHz)
EuroDocsis 3.0-capable downstreams.
IS-IS Point-to-Point Adjacency or point-to-point links simplify the shortest path found (SPF) calculation and reduces both
the network convergence times and size of the topography database.
Support for Cable Modem Status for Out of Range provides a recovery mechanism for downstream bonded flows that
encounter an error in the sequence numbers of the flows which are out-of-sync in the CMTS. The Downstream Service ID is
reset on the DCAM, toggling the sequence change count and resetting the sequence number to zero.
Downstream Output Power Loss Detection and Recovery provides for logging and/or recovering of the DCAM depending
on the threshold reached and how the feature is configured.
24 Downstream Channel Bonding provides support for up to 24 downstream channels, including supporting dynamic
bonding groups when verbose Receive Channel Profiles (RCPs) are enabled.
Upstream-Only Cable Modem Move allows for a CM with downstream bonding enabled and a single upstream that has
not been assigned a Transmit Channel Configuration (TCC) during registration to use any type of initialize technique
identified in the command.
Piggyback Support on RTP Flows allows CMs to register with a modem config file that has an upstream service flow with
both a scheduling type "Real-Time Polling Service" and a Request/Transmission Policy with bit 4 disabled.
Show tech-support brief provides an additional parameter to the show tech-support command to reduce both the time
for the command to run and the volume of the output.
Provisionable Number of Upstream Equalizer Taps allows for selecting the number of taps in the receiver’s equalizer that
is set on a logical channel basis. The new CLI command supports either a five (5) or 24 tap setting.
Operation Mode to Not Store Bad BPI Certificates provides a mode that inhibits storing bad certificates, which can
prevent valid certificates from being added to the database, possibly blocking good modems from registering properly.
Release 8.2 Features
The following is a list of the new features in Release 8.2:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
66
Chapter 2: C4/C4c CMTS Features
Ethernet Link Aggregation (IEEE 802.1ax)
Support for Increased Modem Transmit Power (USCB)
Dual Shared Secret
Enhanced Scaling with Upstream Channel Bonding
Integrated Service Class Agility (ISCA)
Dynamic Service Class Modifications
IPv6 PCMM Support for Voice
Automatic Card Recovery for DC Voltage
Upstream Drop Classifier (UDC) Support
Support for Modem Loss of AC Power (reduce to 1x1)
Improved Partial Services (USCB primary upstream)
Policy-Based Routing (PBR) Recursive Next Hop
Any Source Multicast (ASM) with IGMPv3 on the Cable Side
DSG Reset to Null
TACACS+ Source Interfaces
TCS Optimization for Static Upstream Bonding Groups
Voice Service Flow Load Balancing by CAC Capacity
Subscriber Management Filter Expansion
Ethernet Link Aggregation (IEEE 802.1ax) will allow eight GigE links per link aggregation group (LAG).
Support for Increased Modem Transmit Power (USCB) will implement the extended upstream transmit power CM
capability ECNs which will enable a cable modem that is bonding upstream channels to transmit at a higher power level, if
the cable modem supports that capability.
Dual Shared Secret will allow configuration of a secondary (in addition to the primary) shared secret. Authentication of the
cable modem configuration file will attempt to use the secondary shared secret if a failure occurs during registration using
the normal primary shared secret string. If a match is found using the secondary (or alternate) shared secret, the modem
will be allowed by the C4 CMTS.
Enhanced Scaling with Upstream Channel Bonding will implement measures to reduce C4 CMTS system resources
consumed by modems using multiple upstreams (MTCM) so that the per-CAM scaling of upstream-bonding modems is
increased.
Integrated Service Class Agility (ISCA) will be provided to permit a system operator to enable or disable a state machine
for each eligible upstream channel.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
67
Chapter 2: C4/C4c CMTS Features
Dynamic Service Class Modifications will provide a capability to hitlessly and dynamically change the downstream or
upstream service class parameters in use by a modem by reassigning the updated service class parameters to the modem
via a CLI command.
IPv6 PCMM Support for Voice will allow the use of IPv6 in PCMM (i.e. SIP-based) voice applications.
Automatic Card Recovery for DC Voltage adds a second set of thresholds for each voltage monitor point on the XD, 12U,
and 24U CAMs. This second set of thresholds, which indicates that the voltage is further out of specification that the
existing thresholds, will be used to initiate recovery if the recovery action has been enabled for the monitor point.
Upstream Drop Classifier (UDC) Support will allow a modem to use UDCs. The UDC would be configured strictly via TLV in
the modem configuration file.
Support for Modem Loss of AC Power (reduce to 1x1) will provide functionality to reduce an MxN bonded modem to a
1x1 configuration upon receipt of the "loss of AC power" CM Status message from that modem. It will also restore the
modem to the MxN configuration upon receipt of the "AC power restored" CM Status message from a given modem. This
feature will not apply, however, if at least one voice call is active on the modem.
Improved Partial Services (USCB primary upstream) will prevent a modem from re-ranging or re-registering (i.e. flapping)
when the primary upstream channel of a bonded modem becomes impaired provided that the modem is able to range on
another (non-primary) channel.
Policy-Based Routing (PBR) Recursive Next Hop will enhance the existing PBR feature to support configuration of a next
hop address which is not directly connected to the C4 CMTS. A recursive route look-up will be supported to obtain the
next-hop IP address. The RCM will forward the packet using the IP address obtained via look-up instead of the Destination
IP in the packet.
Any Source Multicast (ASM) with IGMPv3 on the Cable Side will accept ASM (*.G) joins on the cable side interfaces while
operating in IGMPv3 mode. IGMP Proxy will be used on the NSI side.
DSG Reset to Null will provide a single command to delete all DSG configuration information in the C4 CMTS without
affecting the DSG Service Class Name (SCN).
TACACS+ Source Interfaces will allow a non-loopback interface (which is currently used by default) to be configured as the
source IP address for TACACS+ AAA packets originating on the C4 CMTS. Other configuration defaults existing today (prior
to Release 8.2) for TACACS+ AAA will not be changed.
TCS Optimization for Static Upstream Bonding Groups will support optimization of a modem’s Transmit Channel Set (TCS)
such that the TCS contains only the channels defined in the static bonding group(s) assigned to the modem rather than all
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
68
Chapter 2: C4/C4c CMTS Features
channels available on the fiber node if the modem first ranges on a channel in that static bonding group. It will add a
system operation mode to limit the size of the TCS based on the number of upstream channels the modem is using for its
service flows.
Voice Service Flow Load Balancing by CAC Capacity will give preference to channels that have the lightest overall
utilization.
Subscriber Management Filter Expansion will increase the filter entries per Subscriber Management Filter group from 31
to 63 filter entries.
Release 8.2.5 Features
The following is a list of the new features in Release 8.2.5:
Annex A Mixed Modulation (Q64 / Q256) per F-connector (blocks of 4 channels)
Intelligent RCS Assignment/Balancing Control
Differential Services Code Point (DSCP) Marking for DHCP Packets
PCMM IPv4/IPv6 Classifiers and gates ECN Support (MM-N-13.0697-1)
Differential Services Code Point (DSCP) Marking for Downstream Subscriber Traffic
RADIUS Password Challenge
Support for Multi-Tuner Cable Modems
Bonding of Eight Upstream Channels (24U CAM)
Improved Partial Service
IPv6 VoIP Support
Intelligent TCS Assignment
5-85 MHz Support
Multi-protocol BGP Support with IPv6 Address Family
TCS Reduction Enhancement
Ping Stats
Automatic Gain Control (AGC) Correction with Enable/Disable Control
BSoD L2 VPN Configuration via CLI
Configure cable global CLI Commands
Annex A Mixed Modulation (Q64 / Q256) per F-connector (blocks of 4 channels) will support simultaneous use of 256
QAM modulation and 64 QAM modulation on a single F-connector from the XD-CAM. This functionality is required for
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
69
Chapter 2: C4/C4c CMTS Features
Annex A only. The C4 CMTS will support four (4) channels at 64 QAM and four (4) channels at 256 QAM on each of the four
(4) F-connector outputs of the XD-CAM. The four (4) 64 QAM channels on each F-connector may be set at a power level 6
dB below that of the 256 QAM channels. All the channels on the F-connector can be in the same MAC domain and could be
channel-bonded together.
Intelligent RCS Assignment/Balancing Control provides the capability such that automatic intelligent assignment of the
Receive Channel Set (RCS) used by a modem results in the assignment of the modem to the least loaded downstream
channels that meet the required service flow attributes at registration.
DSCP Marking for DHCP Packets provides the ability to mark the TOS byte or DSCP for DHCP and DHCPv6 packets leaving
the C4 CMTS after being processed by the DHCP relay agent. DHCP renew packets that bypass the relay agent will not be
marked.
PCMM IPv4/IPv6 Classifiers and gates ECN Support (MM-N-13.0697-1) provides support so that a single PCMM gate for
an upstream or a downstream flow can simultaneously use both an IPv4 and an IPv6 classifier.
DSCP Marking for Downstream Subscriber Traffic The CMTS currently can mark the DSCP for upstream subscriber traffic
but not for downstream. This new feature will extend this capability to the downstream in order to create a greater level
of control over the prioritization of traffic.
RADIUS Password Challenge will support a Password Challenge function for RADIUS Authentication by adding support for
the Access Challenge message.
Support for Multi-Tuner Cable Modems provides support for multi-tuner CMs without resorting to static RCCs which can
be difficult to configure, such as:
Two tuners per modem
Four channels per tuner
Other permutations of numbers of tuners and channels may be supported (i.e. M tuners, N channels per tuner where
M/N is an integer and M>1).
Bonding of Eight Upstream Channels (24U CAM) supports bonding of eight (8) upstream channels with the 24U CAM
(Note: bonding of five, six, and seven upstream channels will also be supported. The current support for bonding of
channels of varying widths or modulation profiles is maintained.
Improved Partial Service supports the capability to recover any upstream channels that were placed into an impaired state
when the channel was reported as impaired via the REG-ACK or DBC-RSP messaging mechanism. This feature is disabled by
default. When enabled, the C4 CMTS will continue to send unicast ranging opportunities for any upstream channels that
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
70
Chapter 2: C4/C4c CMTS Features
are reported to be impaired via a REG-ACK or DBC-RSP. Regardless of whether this feature is enabled or disabled, the
behavior will only impact newly registered modems; currently registered modems are unaffected.
IPv6 VoIP Support supports the IPv6 address family for IP addressing to DOCSIS 3.0 MTAs or DOCSIS 3.0 embedded Digital
Voice Adapters (eDVAs). It will not perform IPv6 classification using the source IP address of IPv6 MTAs or eDVAs.
Intelligent TCS Assignment supports the capability to assign the Transmit Channel Set (TCS) used by a modem such that
the modem will be assigned to the most lightly-loaded upstream channels that meet the required service flow attributes at
registration time. The ability to control the intelligent TCS assignment/balancing mode of operation will be separately
configurable from the ability to enable and disable periodic dynamic load balancing.
5-85 MHz Support supports using the extended upstream frequency range (5 to 85 MHz) CM capability TLV when
evaluating TCS selection and potential CM movement from several mechanisms: upstream channel override in the RNGRSP message, or DCC.
Multi-protocol BGP Support with IPv6 Address Family adds support for IPv4 and IPv6 BGP operation. The C4 CMTS will
advertise and learn IPv4 and IPv6 prefixes and allow regular community tagging based on route-maps for IPv4 and IPv6.
TCS Reduction Enhancement allows user to specify the maximum size of a modem’s transmit channel set (TCS).
Ping Stats provides support for including round-trip delay statistics with the output of the ping CLI command. Output of
the ping command will now return minimum, maximum, and average round trip delay.
Automatic Gain Control (AGC) Correction with Enable/Disable Control -- adds an operational mode to limit the maximum
adjustment to the originally intended value (3.0), but will default to the extended value (4.3).
BSoD L2 VPN Configuration via CLI implements CLI functionality in the C4 CMTS to allow a modem to be assigned to a
specified BSoD L2 VPN without putting the L2VPN TLVs in the modem configuration file.
Configure cable global CLI Commands This new family of commands is meant to improve CLI usability by reducing the
number of options directly under the configure cable command.
Release 8.3 Features
The following is a list of the new features in Release 8.3:
Hitless Dynamic DS and US Bonded Modem Load Balancing
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
71
Chapter 2: C4/C4c CMTS Features
Hitless Bonded Modem Movement
Energy Management ECN (MULPI v3.0-N-23.1071.10)
Additional OSSIv3 IPDR Schemas
DHCP Option 82.9 Support for MSO Defined Text
Upstream Channel Bonding (USCB) Graceful Reduction
Filter Group Text Descriptions
Repeat CLI Command
Per Flow Downstream Latency Support
Hitless Dynamic DS and US Bonded Modem load balancing — supports dynamic load balancing of bonded modems
without intrusive techniques such as reinit mac. There is no support for this feature on a 12U CAM card.
See Load Balancing chapter.
Hitless Bonded Modem Movement — enhances modem move capability to hitlessly operate with a bonded modem.
There is no support for this feature on a 12U CAM card.
See Load Balancing chapter.
Energy Management ECN (MULPI v3.0-N-12.1071-10) — implements "Energy Management 1 x 1 Mode" per ECN
MULPIv3.0-N-12.1071.10. With this feature, modems monitor bandwidth usage and sends request to CMTS to reconfigure
to 1 x 1 when data usage falls below thresholds established by the operator. ECN includes definition of thresholds for
modem to make decision.
See Energy Management 1x1 Mode in the Channel Bonding chapter.
Additional OSSIv3 IPDR Schemas — supports the use of the OSSIv3 IPDR schemas on the SCM II and SCM 3 families.
See Configure Sessions (page 966) in the Internet Protocol Detail Record chapter.
DHCP Option 82.9 Support for MSO Defined Text — This feature supports the capability for MSOs to define a custom text
string (more specifically referred to as MSO Defined Text) that will be added into DHCP Option 82.9 for those broadcast
DHCP messages that get relayed by the CMTS to a DHCP server. The source of the broadcast DHCP messages is a modem or
CPE on the cable side of the CMTS. The destination of the broadcast DHCP messages is the DHCP server reached through a
Network Side Interface (NSI).
See DHCP Options (page 647) in the CPE Device Class chapter.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
72
Chapter 2: C4/C4c CMTS Features
Upstream Channel Bonding (USCB) Graceful Reduction — supports a graceful fallback from any number of channels
greater than two USCB to two USCB and then to a single channel.
See TCS Reduction Enhancement (page 702) in the Channel Bonding chapter.
Filter Group Text Descriptions — allows a text description to be configured for each Subscriber Management Filter group.
Doing so does not reduce the number of indexes for filters allowable per group. This feature will support a text string of at
least 32 characters for the description.
See Text Description Parameter (page 572) in the IP Packet Filters, Subscriber Management chapter.
Repeat CLI Command — provides a single command to allow users to repeat a show command multiple times with an
optional delay between shows.
See CLI Repeat Command (page 1121) in the CLI Overview chapter.
Per Flow Downstream Latency Support — introduces some provisioning options to provide some control over the latency
of DOCSIS downstream service flows. For voice service flows, an option is provided to enable and disable shaping on those
service flows. For non-voice service flows, this feature will implement a latency-based random packet discard where the
latency thresholds and probability of drop will be provisionable.
See Per Downstream Latency in the Packet Throttling chapter.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
73
Chapter 3
C4/C4c CMTS Specifications
Overview ............................................................................................74
Network Diagram ...............................................................................75
C4 CMTS .............................................................................................76
C4c CMTS ............................................................................................76
C4/C4c CMTS Specifications ...............................................................78
RF Electrical Specifications .................................................................82
Scalability............................................................................................85
VoIP Call Capacities ............................................................................87
Application-related Specifications .....................................................89
Overview
This chapter will introduce the features and functionality for both the C4 CMTS and the C4c CMTS. This chapter contains
the following topics:
Descriptive and reference information
Physical design information
Power and electrical requirements
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
74
Chapter 3: C4/C4c CMTS Specifications
Network Diagram
A cable network system consists of cable modems (CMs) at subscriber premises, a C4/C4c CMTS at the cable plant
operations area, a data-over-cable management software suite integrated with the operator's other management systems,
and the Hybrid Fiber Coaxial (HFC) cabling that connects it all.
DOCSIS defines the standard for communication among these elements. The C4/C4c CMTS provides data switching
functions as well as the radio frequency (RF) interface to and from the cable plant. It also provides ethernet interfaces to
the Internet Service Provider(s).
The data-over-cable management system provides both the end-to-end network management solution and the support for
subscriber provisioning. The figure below shows a typical cable network architecture.
Figure 1: Typical Cable Network Architecture
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
75
Chapter 3: C4/C4c CMTS Specifications
C4 CMTS
The following graphic displays the front view of the C4 CMTS. There are a total of twenty-one slots for modules. There are
four main types of modules used to equip the slots in the front. These are sometimes referred to as front cards. Smaller
modules, called Physical Interface Cards, or PICs, are inserted in each slot from the rear of the chassis. The PICs provide
physical connectors for terminating cable. Between the front and back slots is the midplane of the chassis. Three C4 CMTS
chassis can be mounted in a single 19-inch wide, seven-foot standard rack.
Figure 2: The C4 CMTS (front view)
C4c CMTS
The figure below illustrates the front view of the C4c CMTS. There are a total of eight slots for modules. There are four
main types of modules used to equip the slots in the front. These are sometimes referred to as front cards. Smaller
modules, called Physical Interface Cards, or PICs, are inserted in each slot from the rear of the chassis. The PICs provide
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
76
Chapter 3: C4/C4c CMTS Specifications
physical connectors for terminating cables from the subscriber. Between the front and back slots is the midplane of the
chassis.
Figure 3: The C4c CMTS (front view)
Slot Numbering Scheme
The eight slots from top to bottom are numbered and populated as follows:
Slot 15
Slot 14
Slot 13
Slot 12
Slot 11
Slot 10
Slot 19
Slot 17
16D or XD CAM
12U or 16D or XD CAM
12U or 16D or XD CAM
12U or 16D or XD CAM
12U or 16D or XD CAM
12U CAM
SCM
RCM
The slot numbering scheme makes the C4c CMTS compatible with C4 CMTS software. Without this numbering scheme the
software would return provisioning errors for cards used in the wrong slots.
The CAMs, RCM, SCM, power modules, and Fan Tray Module plus filter are hot-swappable and field-replaceable units.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
77
Chapter 3: C4/C4c CMTS Specifications
Limited Support for the 2Dx12U CAM in the C4c CMTS
The C4c CMTS has limited support for the 2Dx12U CAM:
Up to a maximum of six (6) 2Dx12U CAMs per C4c chassis
If 2Dx12Us are used, then no 16D, XD or 12U CAMs can be used in the same chassis
The 2Dx12U can be used in any CAM slot (i.e., slots 10-15)
The 2Dx12U CAMs can be used for voice or data
The 2Dx12U CAM does not support channel bonding.
Note: The C4c CMTS does not support CAM sparing.
C4/C4c CMTS Specifications
This section is a summary of the CMTS physical characteristics, operating specifications, and information on compliance
with regulatory standards.
Physical
C4 CMTS
C4c CMTS
19- or 23-inch rack, or stand-alone
19- or 23-inch rack, or stand-alone
Height
24.5" (622 mm)
12.25" (311 mm)
Width
17.4" (422 mm)
17.45" (433 mm)
Depth
20.0" (508 mm)
22.5" (572 mm)
Mounting
Dimensions:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
78
Chapter 3: C4/C4c CMTS Specifications
178 pounds (80.9 Kg)
105 pounds (47.6 Kg)
Operating voltage:
Nominal -48V DC, range -44 to -72V DC
Nominal -48V DC, range -44 to -72V DC
Start-up voltage:
-44 to -67.5 V DC
-44 to -67.5V DC
Chassis Weight (fully equipped)
Power
Power
Operating voltage
C4 CMTS
C4c CMTS
Nominal -48V DC, Range -44 to -72V DC
Nominal -48V DC, Range -44 to -72V
DC
115V AC, Range 100V to 240V, 47 to
63 Hz
Note: Once powered up, the C4 and C4c CMTS will continue to operate if within this range.
Start-up voltage range
-44 to -67.5V DC
-44 to -67.5V DC
Note: If powered down, the C4 and C4c CMTS will not restart successfully if the voltage is not in the range of -44 to 67.5V DC. This offset from the operating range provides a cushion against multiple possible power cycles. Attempted
start-ups at the voltage extremes are subject ot power fluctuations that could result in multiple power cycles and
damage to the equipment. The -44 V guaranteed operating limit translates to a maximum current draw of 64A at
2800W.
Chassis power consumption
2800 W maximum
1200 W maximum using DC power
1350 W maximum using AC power
Safety
The C4/C4c CMTSs meet the following safety standards:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
79
Chapter 3: C4/C4c CMTS Specifications
UL60950 (1999) Third Edition
CAN/CSA-C22.2, No. 950-95
IEC60950-1 (2001), First Edition
Electromagnetic Compatibility
The C4/C4c CMTSs meet the following:
GR-1089-CORE, Issue 3 (FCC - Part 15, Class A)
EN 300 386 v1.3.1 (CISPR 22, Class A)
Environmental
Mechanical —
NEBS GR-63-CORE
ETS 300 019
In-use (Class3.1E)
Storage (Class 1.2)
Transportation (Class 2.3)
Thermal — The C4 CMTS meets the following environmental standards:
NEBS GR-63-CORE, ETS 300 019
Operating temperature
Short term1 :
Long term:
Non-operating temperature:
Operating humidity
Short term:
Long term:
Non-operating humidity:
-5 to +55ºC
+5 to +40ºC
-40 to +70ºC
5 to 90%, non-condensing
5 to 85%
5 to 95%, non-condensing
Other —
NEBS Level 3 Criteria (SR-3580)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
80
Chapter 3: C4/C4c CMTS Specifications
Acoustic Noise Criteria:
NEBS (GR-63-CORE)
ETSI (ETS 300 753)
Altitude Criteria (NEBS GR-63-CORE)
Illumination Criteria (NEBS GR-63-CORE)
1
Short term refers to a period of not more than 96 consecutive hours and a total of not more than 15 days in one year.
(This equals of total of 360 hours in a given year, but no more than 15 occurrences in that one-year period. (Telcordia, GR63-CORE, Section 4.1.2, Issue 2, April 2002)
WARNING: This product may contain chemical(s) known to the State of California to cause cancer, birth defects, or other
reproductive harm.
WEEE (Waste Electrical and Electronic Equipment)
As indicated by the symbol below, disposal of this product in participating European Community member states is
governed by Directive 2002/96/EC of the European Parliament and of the Council on waste electrical and electronic
equipment (WEEE). WEEE could potentially prove harmful to the environment; as such, upon disposal of the C4 CMTS and
its components, the Directive requires that this product must not be disposed as unsorted municipal waste, but rather
collected separately and disposed of in accordance with local WEEE ordinances.
Figure 4: WEEE Symbol
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
81
Chapter 3: C4/C4c CMTS Specifications
RF Electrical Specifications
The following table lists the downstream RF electrical specifications for the C4 and C4c CMTSs.
Table 4. Downstream RF Electrical Specifications
Specification
16D or XD CAM
Center frequency range supported:
57 - 999 MHza
Frequency step size:
125 kHzb
Modulation types
64QAM, 256QAM
Downstream channel width:
North America (Annex B)
Europe (Annex A)
Europe (using Annex B)
6 MHz
8 MHz
6 MHz with 6 or 8 MHz channel spacing
Annex B symbol rates in Msym/sec
64QAM:
256QAM:
Annex A symbol rate in Msym/sec
64QAM or 256QAM:
Raw Bit Rate
Annex B:
Annex A:
64QAM
256QAM
30.342 Mbps
42.884 Mbps
64QAM
256QAM
41.712 Mbps
55.616 Mbps
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
5.056941
5.360537
6.952
C4® CMTS Release 8.3 User Guide
82
Chapter 3: C4/C4c CMTS Specifications
Specification
16D or XD CAM
RF output level
Overall: 41-60 dBmV
Channels used per connectorc :
1: 41-60 dBmV
5: 41-51 dBmV
2: 41-56 dBmV
6: 41-50 dBmV
3: 41-54 dBmV
7: 41-49 dBmV
4: 41-52 dBmV
8: 41-49 dBmV
Return loss
> 14 dB in-band
Output impedance
75 Ohms
a
Note: The 16D hardware supports DS center frequencies up to 999 MHz, but for the best performance, it is advisable
to go no higher than 960 MHz. If the 999 MHz is attempted, the downstream maximum frequency must be set
appropriately using the configure freq-ds-max command.
b
For the XD CAM, see Spectrum Window and Frequency Grid for Channels on the Same F-connector.
c
The 16D CAM supports 1-4 channels per connector. The XD CAM in Annex B supports 1-4 channels per connector.
The XD CAM in Annex A supports 1-8 channels on connectors 0 and 2; 1-4 channels on connectors 1 and 3.
The following table lists the upstream RF electrical specifications.
Table 5. Upstream RF Electrical Specifications
Specification
12U/24U
Frequency Range
5 - 65 MHz
RF channel frequency resolution
<1 kHz
Modulation types
Type 4 TLV: QPSK, 16QAM
Type 5 TLV: QPSK, 8QAM, 16QAM, 32QAM, and 64QAM
Raw bit rate (Max.)
30.72 Mbps
RF Input Level (dBmV)
-16 to 29
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
83
Chapter 3: C4/C4c CMTS Specifications
Specification
12U/24U
Forward error correction
Reed-Solomon (T = 1-16)
The following is a list of receiver input levels for upstream channels:
Table 6. Receiver Input Levels for Upstream Channels
Channel Width
(kHz)
Symbol Rate
(ksym/sec)
Input Power Range (dBmV)
12U or 24U CAM
200
160
-16 to +14
400
320
-13 to +17
800
640
-13 to +20
1600
1280
-13 to +23
3200
2560
-10 to +26
6400
5120
-7 to +29
Note: It is not recommended that upstream ranges go beyond +23 dBmV. (See the tables in 24U CAM Upstream Power
Level Groups ("24U CAM Upstream Power Level Groups" page 282) for more details on the Upstream Power Level Groups.)
Network Interfaces
The C4 and C4c CMTSs support the following network interfaces:
10 Base-T (SCM Maintenance Port)
SFP Modules (10 per RCM):
10/100/1000Base-T
1000Base-SX
1000Base-LX
1000Base-LX10
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
84
Chapter 3: C4/C4c CMTS Specifications
1000Base-ZX
XFP Modules (1 per RCM):
10GBase-SR
10GBase-LR
10GBase-ER
10GBase-ZR
Note: To order ARRIS-supported SFP and XFP interface connectors, contact your ARRIS Sales Team Representative.
Scalability
ARRIS offers a number of combinations of downstream to upstream channel ratios to improve scalability. With the ability
to accommodate many configurations, the C4 CMTS can grow to meet evolving subscriber traffic considerations along with
reducing inter-shelf cabling. This leads to lower cost for installation, operations, and maintenance.
C4 CMTS Chassis
A fully equipped C4 CMTS chassis offering basic service will provide reasonable performance up to the following suggested
subscriber limits:
128,000 ARP cache entries
24,000 subscribers per chassis
1,000 subscribers per 12U CAM
6,600 subscribers per 24U CAM
16,000 subscribers per 16D and XD CAMs
2,000 subscribers per 16D downstream channel
50 simultaneous PacketCable CALEA taps
32,800 downstream service flows
32,800 upstream service flows
32,800 downstreams classifiers
320 simultaneous Service Independent Intercept (SII) taps
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
85
Chapter 3: C4/C4c CMTS Specifications
40,000 subscribers per chassis with the SCM II EM/EM (U) and SCM 3 board
The maximum number of modems/eMTAs is 30,000; the remaining devices must be STBs
51,000 downstream service flows
51,000 upstream service flows
51,000 downstreams classifiers
32,000 downstream service flows per 16D or XD CAM
13,200 upstream service flows per 24U CAM
9,000 upstream service flows per 12U CAM
4,500 subscribers per 12U CAM
6,600 subscribers per 24U CAM
16,000 subscribers per 16D and XD CAMs
320 simultaneous Service Independent Intercept (SII) taps
C4c CMTS Chassis
A fully equipped C4c CMTS chassis offering basic service will provide reasonable performance up to the following
suggested subscriber limits:
Chassis scaling
Numbers depend on how many cards are configured in the chassis and the number of subscribers per UCAM or
DCAM.
Component scaling
1,000 subscribers per 12U CAM
6,600 subscribers per 24U CAM
16,000 subscribers per 16D and XD CAMs
2,000 subscribers per 16D downstream channel
50 simultaneous PacketCable CALEA taps
32,800 downstream service flows
32,800 upstream service flows
32,800 downstreams classifiers
320 simultaneous Service Independent Intercept (SII) taps
Chassis with the SCM II EM/EM (U) and SCM 3 board
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
86
Chapter 3: C4/C4c CMTS Specifications
The maximum number of modems/eMTAs is 30,000; the remaining devices must be STBs
51,000 downstream service flows
51,000 upstream service flows
51,000 downstreams classifiers
32,000 downstream service flows per 16D or XD CAM
13,200 upstream service flows per 24U CAM
9,000 upstream service flows per 12U CAM
4,500 subscribers per 12U CAM
6,600 subscribers per 24U CAM
16,000 subscribers per 16D and XD CAMs
320 simultaneous Service Independent Intercept (SII) taps
The number of IPv4 and IPv6 supported routes by the C4 and C4c CMTSs are:
Table 7. IPv4 and IPv6 Supported Routes
Total
IPv4
32,000
IPV6[1]
28,000[2]
PDRI
Dynamic
Static
16,000
10,000[3]
2,000
1. The IPv6 routes are in addition to the IPv4 total.
2. The total of IPv6 routes allowed is the sum total of the PDRI, Dynamic, and Static routes.
3. The total number of IPv6 dynamic routes is a combination of OSPFv5 and IS-IS IPv6 routes.
VoIP Call Capacities
The following Voice over Internet Protocol hardware and call limits apply to both the C4 and C4c CMTSs configured for
DSx/DQoS VoIP or PacketCable voice.
The Multimedia Terminal Adapter (MTA) is a telephony modem:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
87
Chapter 3: C4/C4c CMTS Specifications
MTAs per C4/C4c CMTS
MTAs per downstream channel
12,000
1,000
Maximum per 16D CAM
MTAs per upstream channel
Lines per downstream channel
Lines per upstream
Lines per C4 CMTS
8,000
250
1,200
300
14,400
Busy Hour Call Attempts (peak 60-minute call loads supported):
BHCA per C4/C4c CMTS
39,600
BHCA per downstream channel
3,348
Maximum per 16D/XD CAM
BHCA per upstream channel
26,640
828
Maximum per 24U CAM (C4 CMTS only)
Simultaneous half-calls/downstream channel
Simultaneous half-calls/upstream channel
Connections per second per chassis
16,500
67
42
11
Call load performance is based on the following assumptions:
Lines per subscriber
1.2
Hold time
180 seconds
Call Completion Rate
99.5%
These limits also depend on the following:
MTAs/lines are distributed evenly across 4 upstream channels per downstream channel
256QAM downstream channel
16QAM upstream channel
3.2 MHz upstream channel width
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
88
Chapter 3: C4/C4c CMTS Specifications
Application-related Specifications
Table 8. DOCSIS-related Specifications Compliance
Standard
Status
Notes
DOCSIS
1.1 Qualified, Cert-wave 25
2.0 Qualified, Cert-wave 32
3.0 Bronze Qualified, Cert-wave 56
2.0 implies DOCSIS 1.1 qualification also.
EuroDOCSIS
2.0 Qualified, ECW 18x
PacketCable
1.0 Qualified, Cert-wave 25
(1.1 Compliant)
PacketCable
Multimedia
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
PacketCable™ Dynamic Quality-of-Service Specification,
PKT-SP-DQOS-I07-030815, also I08, I09, I10, and I11
PacketCable™ Event Messages Specification,
PKT-SP-EM-I08-040113, also I08, I09, I10, and I11; as well as EM-N04.0198-2
PacketCable™ Security Specification,
PKT-SP-SEC-I09-030728, also I10, and I11
PacketCable™ Electronic Surveillance Specification,
PKT-SP-ESP-I01-991229, also I03 and I04
Complies with the following subset of PacketCable Multimedia
Specification,
PKT-SP-MM-I03-051221:
PCMM Gate Control
State Synchronization
Versioning
All traffic profile formats
DOCSIS Parameters
IKE/IPSec
C4® CMTS Release 8.3 User Guide
89
Chapter 3: C4/C4c CMTS Specifications
Standard
Status
Notes
Complies with the following subset of PacketCable Multimedia
Specification,
PKT-SP-MM-I04-080522:
Support for Bonded Unicast Flows
Attribute-based Channel Selection
Support for User Identifier
Addition of Max Concatenated Burst to the BE Traffic Profiles
Handling of DOCSIS 3.0 Peak Rate TLV
DOCSIS 3.0 Additions of Sequence and Segment Numbers
Packet Cable Update of Major/Minor Version for I04
Traffic Profile: Upstream Drop
DOCSIS Set-top
Gateway (DSG)
DOCSIS 2.0 qualification at Certwave 32 includes DSG
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
90
Chapter 4
C4 CMTS General Installation Requirements
Overview ............................................................................................ 92
Safety Precautions.............................................................................. 92
Electrical Equipment Guidelines ........................................................ 94
Electrostatic Discharge (ESD) ............................................................. 94
C4 CMTS Installation Checklist ........................................................... 95
Unpacking the C4 CMTS ..................................................................... 97
Installation Considerations................................................................. 99
Rack Mounting the C4 CMTS ............................................................ 102
Main Hardware Components ........................................................... 104
Installing Modules in the C4 CMTS .................................................. 108
Fan Trays .......................................................................................... 110
Power Conditioning Module and Cabling ........................................ 113
Chassis Maintenance........................................................................ 123
Replacing the C4 CMTS Chassis ........................................................ 123
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
91
Chapter 4: C4 CMTS General Installation Requirements
Overview
This chapter provides the operating precautions and installation requirements for the C4 CMTS.
Note: Do not make any mechanical or electrical modifications to either the C4 CMTS equipment. If modified, the C4 CMTS
may no longer comply with regulatory standards.
Safety Precautions
This section provides safety precautions for installing the C4 CMTS. When setting up the equipment, please observe the
following:
Install the C4 CMTS only in restricted access areas for reasons of security and safety.
Follow all warnings and instructions marked on the equipment.
Ensure that the voltage and frequency of your power source meets or exceeds the voltage and frequency listed on the
equipment’s electrical rating label.
Never force objects of any kind through openings in the equipment because dangerous voltages may be present.
Foreign objects may produce a short circuit resulting in fire, electric shock, or damage to the C4 CMTS and other
equipment.
Connect the C4 CMTS chassis to protective earth ground in compliance with U.S. and International Safety standards.
See see "Grounding the Chassis (page 103).
Lifting Safety
A fully-equipped C4 CMTS weighs approximately 178 lbs. (80.9 kg). The chassis is not intended to be moved frequently.
Before installing the C4 CMTS, ensure that your site is properly prepared.
When lifting the chassis or any heavy object, follow these guidelines:
Disconnect all external cable before lifting or moving the chassis.
Do not attempt to lift the chassis by yourself: have at least one other person assist you.
Ensure that your footing is solid and that you balance the weight of the object between your feet.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
92
Chapter 4: C4 CMTS General Installation Requirements
To lift the chassis, use two people (one on each side). With on hand, grasp a front handle, and with the other hand,
grasp a back handle or grasp the underside of the chassis and lift slowly. Do not twist your body as you lift.
Figure 5: C4 CMTS Chassis Handles
Keep your back straight and lift with your legs, not your back. If you must bend down to lift the chassis, bend at the
waist to reduce the strain on your lower back muscles.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
93
Chapter 4: C4 CMTS General Installation Requirements
Electrical Equipment Guidelines
Follow these basic guidelines when working with any electrical equipment:
Know where the emergency power-off switch is located for the room in which you are working.
Disconnect all power and external cables before moving the chassis.
Do not work alone if potentially hazardous conditions exist.
Never assume that power has been disconnected; always check.
Do not perform any action that makes the equipment unsafe or might create a potential danger to people.
Examine your work area for possible hazards such as ungrounded power extension cables, missing safety grounds, or
wet floors.
CAUTION: Be sure to connect the chassis to protective earth ground before applying power or inserting modules. An
ungrounded chassis may damage components.
CAUTION: The ports of the C4/C4c CMTS chassis are suitable for connection to intra-building or unexposed wiring or
cabling only. The ports of the chassis MUST NOT be metallically connected to interfaces which connect to outside plant
(OSP) or its wiring. These interfaces are designed for use as intra-building interfaces only, requiring isolation from the
exposed OSP cabling. They are Type 2 or Type 4 ports as described in GR-1089-CORE, Issue 4. Finally, the addition of
Primary Protectors is not sufficient protection from electrical shock in order to connect these interfaces metallically to OSP
wiring.
Electrostatic Discharge (ESD)
Electrostatic Discharge (ESD) can damage equipment and impair electrical circuitry. ESD occurs when printed circuit
modules are improperly handled. It may result in module failure or intermittent problems.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
94
Chapter 4: C4 CMTS General Installation Requirements
The C4 CMTS contains replaceable printed circuit modules. Modules are equipped with a metal faceplate that features
Electromagnetic Interference (EMI) shielding and lever-action latches. Handle the modules by their latches and avoid
touching the printed circuit board and connector pins.
Although the metal faceplate helps to protect the printed circuit modules from ESD, wear an antistatic wrist or ankle strap
whenever handling the modules. Ensure that the anti-ESD device makes good skin contact. The chassis is equipped with
four sockets in which you can ground plug-in wrist straps.
C4 CMTS Installation Checklist
Installation involves mounting the unit in a rack, populating slots with client1 and system modules and Physical Interface
Cards (PICs), attaching cables, and configuring software. Follow the instructions in this section when installing the C4 CMTS
for the first time.
Table 9. Installation Checklist
Completed (X)
Task Description
Become familiar with component descriptions
Unpack the C4 CMTS according to the instructions in see "Unpacking the C4 CMTS (page 97)
Obtain any necessary items not supplied to install the C4 CMTS in your configuration
Prepare the site for installation in accordance with placement and electrical considerations
Install C4 CMTS in rack
Attach the chassis grounding cable
Connect yourself to the chassis ground
Install the three Fan Trays
Install the two Power Conditioning Modules
Install the Physical Interface Modules (PICs)
Install the front cards (i.e., system and client modules1)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
95
Chapter 4: C4 CMTS General Installation Requirements
Completed (X)
Task Description
Attach to DC power (See see "Power (page 79))
Attach cables
Connect an operator console
Power up the C4 CMTS
Configure the C4 CMTS according to the instructions in Basic Bring-up Procedure for the C4 CMTS (page
325)
1
CAMs are client modules; the SCM and RCM are system modules.
Tools Required
The following tools are required for installation:
#3 Phillips screwdriver for large bolts
#2 Phillips screwdriver
Digital volt meter
Torque wrench
Torque Values
The following table lists the recommended torque values for selected screws and fasteners of the C4 CMTS.
Table 10. Recommended Torque Values in Inch-pounds
Fasteners
Torque
Screws for grounding cable
10.0 +/- 0.5 in-lbs.
Captive fasteners of PCMs
5.0 +/- 0.5 in-lbs.
Captive fasteners of Fan Trays
5.0 +/- 0.5 in-lbs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
96
Chapter 4: C4 CMTS General Installation Requirements
Captive fasteners of Crossover Connector for RCMs
5.0 +/- 5 in-lbs.
F-connectors of PICs
20.0 +/- 0.5 in.lbs.
If used only for F-connectors, torque wrench should be self limiting to 20 in-lbs.
Items Not Supplied
The following items are not included with the C4 CMTS. Obtain these items before installation:
Appropriate network cables
Operator console or PC with built-in asynchronous terminal emulation
Coaxial cables
48 VDC power supply
The CMTS requires one Router Control Module (RCM). To use the RCM, customers must order an Ethernet interface. You
may choose either a Small Form-factor Pluggable (SFP) or a 10G Small Form-factor Pluggable (XFP) to be used with the
RCM. For more information, see SFP and SFP Ethernet interfaces. If you plan to operate the C4 CMTS in duplex mode
(redundant control complexes), you must purchase one (1) C4 CMTS Router Control Module Crossover Connector (Part
Number 722891) along with the two RCMs and two SCMs.
Unpacking the C4 CMTS
CAUTION: Installation requires more than one person.
When unpacking the C4 CMTS, use the following steps and checklist:
Inspect the shipping crate before removing the unit. If there is evidence of damage to the crate upon receipt, request
an agent of the carrier to be present before removing the C4 CMTS.
Ensure the crate is right side up. Open crate and carefully remove the packaged unit inside. Then remove the
protective foam from the unit. Do not discard any optional items, which are typically packed in small boxes set in the
packing foam.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
97
Chapter 4: C4 CMTS General Installation Requirements
Remove the remaining contents of the crate. Front and rear modules are shipped in separate cartons, unless you
ordered a configured chassis. In a configured chassis modules are shipped in their slots.
Check the packing slip and verify its contents. If an entire C4 CMTS is ordered, it typically ships with the following
items. Use the checklist provided below to verify that the required items are present.
Table 11.
(X)
Hardware Shipment Checklist
Required Items
One C4 CMTS chassis
One (1) chassis ground cable (green, 4 gauge, approx. 24 inches)
Two Power Conditioning Modules
Two (2) power cables: one for each power feed (A & B) and each containing two 6 gauge wires
(one red and one white), approx. 50 ft.
Modules for basic configuration (minimal requirement):
One System Control Module (SCM) and associated physical interface card (PIC)
One Router Control Module (RCM)
One downstream Cable Access Module (CAM) and PIC
One upstream Cable Access Module (CAM) and PIC
Seventeen (17) front filler panels
Eighteen (18) rear filler panels (there is no PIC for the RCM)
Three (3) Fan Trays
One (1) air filter (installed)
One (1) hardware installation kit
One (1) ESD Wrist Strap
One (1) C4 CMTS Serial Cable and adapter for connecting a console to the SCM serial port
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
98
Chapter 4: C4 CMTS General Installation Requirements
(X)
Required Items
Documentation package (zip-lock plastic bag in shipping crate):
One (1) paper copy of the licensing agreement
One (1) copy of the pre-printed packing list
Module Protection
All spare modules are shipped in reusable antistatic shielding bags. If modules are not immediately installed, keep them in
these antistatic bags. Do not remove modules from the antistatic bags unless properly grounded.
Do not place these bags on exposed electrical contacts or else the modules may short circuit.
Installation Considerations
Rack Mounting
The C4 CMTS is designed to be mounted in a standard 7-foot by 19-inch equipment rack, compliant with EIA RS-310. A
total of three chassis can be installed in this equipment rack.
Uneven mechanical loading of an equipment rack can be hazardous. Plan the installation so that the weight of the
equipment is evenly distributed across the vertical height of the rack. Depending on the number of modules supported,
some C4 CMTS configurations are heavier than others. Place the heaviest units toward the bottom of the rack.
Chassis Placement
Select an appropriate installation area that is dry, relatively dust free, well-ventilated, and air conditioned. Be sure the
floor is capable of supporting the combined weight of the rack with the installed equipment.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
99
Chapter 4: C4 CMTS General Installation Requirements
CAUTION: The C4 CMTS generates a significant amount of heat. Allow enough space around the C4 CMTS for adequate
ventilation and do not block the air vents. Inadequate ventilation could cause the system to overheat.
Clearance
Allow sufficient clearance around the rack for maintenance. If the rack is mobile (not recommended), place the C4 CMTS
near a wall or cabinet for normal operation and pull it out for maintenance (installing or moving port adapters, connecting
cables, and replacing or upgrading components). Be sure there is enough cable length available to pull the C4 CMTS out for
repairs or adjustments if necessary.
Power Requirements
The C4 CMTS uses dual redundant -48V power feeds to supply electrical power to the system. The system is capable of
operating from a single feed in case one of the feeds fails.
The system consumes a maximum of 2800W of power when equipped with the maximum number (16) of CAMs.
The supply voltage should be a nominal -48V. The operating range is -44 to -72V. The system will shut down if the voltage
is outside these limits.
The -44V guaranteed operating limit translates to a maximum current draw of 64A at 2800W. Circuit breakers on the
power feeds should be sized accordingly. The Power Conditioning Modules in the C4 CMTS will limit the startup current to
prevent false tripping of the circuit breakers.
Cooling Requirements
The C4 CMTS should be installed in a location with adequate ventilation. It is designed for long-term operation at ambient
air temperatures ranging from 5-40C and an area that is between 5 to 95 percent relative humidity, non-condensing.
To determine cooling requirements, assume 2800W for worst-case power dissipation. These values assume the worst-case
cooling requirements when the maximum number of CAMs (16) is used.
The C4 CMTS draws cooling air in through the front, sides, and back at the bottom of the unit and expels it out the sides
and back at the top of the unit. Clear airflow must be maintained in these areas to ensure adequate ventilation. If the C4
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
100
Chapter 4: C4 CMTS General Installation Requirements
CMTS is installed in a closed or multi-unit rack assembly, the inlet air temperature could exceed the room ambient air
temperature and/or the air flow may be reduced. In these cases, the C4 CMTS requires a colder room temperature be
maintained to compensate for this type of installation.
CAUTION: As with all electrical equipment, operation at excessive temperature accelerates the deterioration of
components and adversely effects performance. Prevent excessive heat buildup in the rack.
Temperature Monitoring
The C4 CMTS monitors module temperatures at approximately 90-second intervals. If the temperature of a front module
falls below, or rises above its operating range, a TempOutOfRangeNotification SNMP trap is generated for that module. If
the temperature continues to rise to the module’s thermal limit, the card is powered down and a card
TempOverHeatNotification SNMP trap is generated.
The temperature value read during the last 90-second poll is accessible via both the CLI and SNMP. The show
environment CLI command will display the current temperature of modules in equipped slots. The card Temperature
object in the cardTable table in the cadEquipmentMib MIB module contains the current temperature of the associated
slot.
As shown the figure below, the Fan Trays circulate the air that cools the chassis. Air is drawn in through the intake vent at
the bottom of the chassis It then moves across the internal components, cooling them as it passes. The warm air is
exhausted through the vent at the top rear of the chassis.
To ensure the proper air flow, make sure blank filler panels are installed in unoccupied front and rear chassis slots. It is also
important to change the fan filter at least every three months, and more often if the air at the site is dusty.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
101
Chapter 4: C4 CMTS General Installation Requirements
CAUTION: Fan filters cannot be cleaned and re-used.
Figure 6: Internal Air Flow (side view)
CAUTION: Care should be taken when dressing RF cables such that they do not obstruct the grillwork at the top rear of the
chassis. This grill is the primary heat vent for the chassis. Blocking it can cause overheating and card failure. Allow sufficient
clearance for airflow around the chassis.
Rack Mounting the C4 CMTS
The following steps outline how to rack mount the C4 CMTS.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
102
Chapter 4: C4 CMTS General Installation Requirements
WARNING: Ensure that the rack is stable and properly bolted to the floor so that weight of the chassis does not make it
unstable.
How to Rack Mount the C4 CMTS
1. Attach the supplied green protective earth ground cable to either the side or rear termination point of the chassis
prior to placing the chassis in the rack. The other end of the protective earth ground cable should extend to the back.
See see "Grounding the Chassis (page 103).
The attachment screws for this cable are shipped pre-installed in the chassis. Remove the attachment screws from the
desired ground cable location on the chassis and reattach. The recommended torque for these screws is 10.0 ±0.5 inchpounds.
2. If using telco type racks, be sure to bolt the rack to the floor.
3. Position the C4 CMTS in rack.
4. Install rack bolts to secure the C4 CMTS in position.
5. Secure the loose end of protective earth ground cable to a suitable protective earth ground termination point within
the building installation. If attaching this cable to the frame, ensure that the attachment point is bare metal and that
the frame is bonded to a suitable protective earth ground.
Grounding the Chassis
The C4 CMTS chassis must be properly connected to protective earth ground for safety compliance. There are two places
you can connect the protective earth ground wire to the chassis. One is located on the side of the chassis; the other is
located on the rear of the chassis between the PCMs (refer to the figure below). Install the chassis termination end of the
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
103
Chapter 4: C4 CMTS General Installation Requirements
protective earth ground wire to either of these locations before installing the chassis in the rack. See the procedure above
for details on attaching the earth ground cable to the chassis.
Figure 7: Location of Grounding Terminals
Main Hardware Components
The C4 CMTS base system contains the following components:
C4 CMTS chassis
Two Power Conditioning Modules (PCMs) – Power Feeds A & B
Cable Access Module (CAMs) and associated Physical Interface Cards (PICs)
Router Control Module (RCM)
System Control Module and associated PIC
Three Fan Trays which are numbered 0, 1, and 2 (Each Fan Tray contains two fans, marked front and rear.)
Air filter (factory installed)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
104
Chapter 4: C4 CMTS General Installation Requirements
Module Types and Chassis Slots—Front View
The C4 CMTS chassis front contains twenty-one vertical slots labeled 0-20 (from left to right). These slots are equipped for
the following modules (sometimes referred to as front cards):
One or two System Control Modules
One or two Router Control Modules
One to sixteen Cable Access Modules (mix of upstream and downstream CAMs)
Following is an illustration of the front of the chassis.
Figure 8: Front View of C4 CMTS
The chassis example shown in the figure above is equipped with:
Nine 12U (shown) or 24U (not shown) CAMS located in slots 0-8
Seven XD or 16D CAMS located in slots 9-15
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
105
Chapter 4: C4 CMTS General Installation Requirements
Slot 16 is equipped with a front filler panel
Two RCMs in slots 17 and 18 (these slots can be equipped only with RCMs; slot 17 must be the first equipped.) A
Crossover Connector is in place to connect them.
Two SCMs in slots 19 and 20 (these slots can be equipped only with SCMs; slot 19 must be the first equipped.)
Chassis — Rear View
Physical Interface Cards (PICs)
Smaller modules, called Physical Interface Cards, or PICs, are inserted in each slot from the rear of the chassis. The PICs
provide physical connectors for terminating cables from the subscriber network and enable the CAMs to be replaced
without having to remove cables.
The figure below shows an example of a rear view of a chassis configured with 12U and 16D CAMs to show their
connectors:
Slots 16-18 are equipped with filler panels
Slot 15 is equipped with a 16D Spare PIC.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
106
Chapter 4: C4 CMTS General Installation Requirements
Slot 0 is equipped with a 12U Spare PIC
Figure 9: C4 CMTS Chassis (rear view)
Midplane
Between the front and back slots is the midplane of the chassis. The midplane connects the front modules to the rear
modules. The midplane is a necessary point of communication for all modules inserted in the C4 CMTS. The midplane is
used as follows:
By the power conditioning modules to provide power to the rest of the system
By the SCMs and RCMs to exchange control information and packets
By the CAMs (client modules) to pass packets to the RCM
By the RCMs to pass packets to the CAMs and SCMs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
107
Chapter 4: C4 CMTS General Installation Requirements
Filler Panels
The C4 CMTS has two types of filler panels:
Front filler panels — used for any unequipped front module slot
Rear filler panels — used for any unequipped rear PIC slot.
All unused module slots, front and rear, must be equipped with filler panels. Filler panels are required for proper EMC
emission levels and sufficient airflow to properly cool the C4 CMTS system. Failure to cover empty slots reduces the air
flow through the chassis and could result in overheating.
Storing Modules
1. Retain the packaging in which each module was shipped and follow these guidelines for storing modules to avoid
damage:
2. Store each module in a separate antistatic bag. Ideally, store the item in its antistatic bag within the protective
packaging or padded box in which the item was shipped.
Installing Modules in the C4 CMTS
CAUTION: Before removing or replacing any C4 CMTS modules, obtain and attach an antistatic grounding wrist or ankle
strap to protect against damage to components resulting from static electricity.
Use extreme care when inserting or removing modules from the C4 CMTS chassis.
Module Installation Overview
Each module is installed in three basic steps:
1. Use proper ESD precautions before handling modules.
2. Align and insert module into proper slot. Lock ejector levers before proceeding to the next module: red buttons will
click audibly if module is completely seated in the slot and ejector levers are closed.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
108
Chapter 4: C4 CMTS General Installation Requirements
3. Install proper PIC or filler panel in the corresponding rear slot of the chassis. (The RCM does not have a PIC; use a filler
panel instead.)
Note: If you meet strong resistance when attempting to seat the module, PIC or filler panel, remove it from the chassis and
try reinserting it. Be sure that you have aligned the top and bottom edges in the correct matching tracks.
Installation Diagram
Although the figure below shows the SCM, the ejector levers are the same for all modules and PICs.
Figure 10: Installing the System Control Module
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
109
Chapter 4: C4 CMTS General Installation Requirements
Ejector Levers
The figure below illustrates the ejector levers on the module faceplates. Once installed, the module is locked in place. The
red button must be pushed in on each ejector lever mechanism before it will release the module. Always operate both (top
and bottom) ejector levers at the same time when seating or releasing the module.
Figure 11: Ejector Levers
Fan Trays
The C4 CMTS contains three Fan Trays (also called modules) numbered 0, 1, and 2. Each tray contains a front and rear fan.
A failing fan is easily identified by the Fan Status LED on the Fan Tray. Maintenance personnel can replace the failed Fan
Tray without shutting down the entire system.
These fans cool the system components by forcing air from the lower portion of the chassis through all system modules
and exhausting it through the upper rear portion of the chassis.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
110
Chapter 4: C4 CMTS General Installation Requirements
High Speed Fan Trays
All Release 8.x chassis require high-speed Fan Trays. These trays are labeled "High Speed" on their front plates.
Figure 12: Example of High Speed Fan Tray
WARNING: To prevent unnecessary equipment damage, the Fan Tray should be installed only in a chassis that is securely
mounted in a frame or rack. You should rack-mount the chassis first and then install the Fan Trays.
How to Install the Fan Trays
1. Perform the following steps to install Fan Trays. Refer to the figure below to identify the location of the Fan Trays.
2. Align the Fan Tray on the rails and slide firmly into chassis.
3. Hand tighten the captive fastener at the bottom of the tray. If using a tool, care should be exercised not to overtighten. The recommended torque for this fastener is 5.0 ±0.5 inch-pounds.
4. Repeat steps 1 and 2 for the remaining Fan Trays.
5. Once the fans reach operational speed verify that the Fan Status LEDs are green.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
111
Chapter 4: C4 CMTS General Installation Requirements
CAUTION: Be careful when dressing RF cables so that they do not obstruct the grillwork at the top rear of the chassis. This
grill is the primary heat vent for the chassis. Blocking it can cause overheating and card failure.
Figure 13: Installing a Fan Tray
Air Filter
The C4 CMTS comes equipped with an air filter mounted horizontally just above the fan assemblies and just below the
chassis slots. It is important to change the fan filter at least every three months, depending on the air quality on site.
CAUTION: Dirty air filters cannot be cleaned and reused.
Replacement filters may be ordered from ARRIS in kits of four — normally a year’s supply for one chassis. For ordering
information contact your ARRIS sales representative.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
112
Chapter 4: C4 CMTS General Installation Requirements
Power Conditioning Module and Cabling
The C4 CMTS requires two -48V power feeds, A and B, for redundancy. The source can be an external battery plant or
independent AC/DC power supply. In the event that one feed fails or is removed from service for maintenance, the other
feed continues to supply power to the C4 CMTS with no interruption in service.
Note: Review the total current consumption of all equipment on the same line before supplying power to the C4 CMTS.
Avoid sharing a power source that requires large currents.
Power is filtered and conditioned by a Power Conditioning Module (PCM) for each feed. The PCM contains the power input
connector, main breaker, and all active circuitry for power distribution of a power bus.
The PCM:
Soft starts the chassis on power up
Filters noise and power disturbances from the power feeds
Monitors the power draw of the chassis and shuts down a branch circuit in the event of a power fault
Each PCM is removable and can be replaced without interrupting power to the C4 CMTS in a duplex power configuration.
Figure 14: Installing a PCM
CAUTION: Do not connect the cables to a PCM that is not in a chassis.
Be sure to shut the breaker off for the unit and disconnect the -48V power cable before removing the PCM from the
chassis.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
113
Chapter 4: C4 CMTS General Installation Requirements
How to Install the PCM
1. Be sure you are wearing an Electrostatic Discharge (ESD) strap when handling modules.
2. Ensure that no DC power cable is connected to the PCM.
3. Align the PCM on the rails in the rear of the chassis and slide firmly into place. From the rear, the PCM can be inserted
into either the left or right:
a. The PCM on the right side of the chassis is named PCM A. It corresponds to the Bus A power panel LEDs and control
switch located on the front of the chassis.
b. The PCM on the left side of the chassis is named PCM B. It corresponds to the Bus B power panel LEDs and control
switch located on the front of the chassis.
4. Hand tighten the three captive fasteners on each of the PCMs. If the captive fasteners are tightened using a tool, care
should be exercised not to over-tighten. The recommended torque for these fasteners is 5.0 ±0.5 inch-pounds.
Power Requirements
The C4 CMTS must be connected to a protected DC power source that meets the following current requirements:
Input voltage: A and B feed from –44V to -72V
Maximum required current for each feed: 65 amps
Figure 15: Cabling the PCM
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
114
Chapter 4: C4 CMTS General Installation Requirements
How to Cable the PCM
1. Refer to the figure above and follow the steps below to cable the PCM.
2. Two cables, one red and one blue (each containing two 6 gauge wires, one red and one white) are included with the C4
CMTS. One end of each cable is connectorized and keyed for the power connector on the rear of the chassis.
a. Make sure the breaker is in the OFF position before plugging in the power feed cables.
b. Using the connectorized end of the red cable, plug it directly into the PCM Power Feed A.
c. Using the connectorized end of the blue cable, plug it directly into the PCM Power Feed B.
CAUTION: You must ensure the power connections maintain the proper polarity. Your power source cables might be
labeled (+) and (-) to indicate their polarity. There is no standard color coding for DC power cables. The color coding used
by the external DC power source at your site determines how the ARRIS CMTS power cables are connected.
3. Each cable contains two 6-gauge wires (one red and one white) that must be hard-wired to the DC source by a
qualified service electrician.
a. Connect the red wire to the negative (—) side of the -48V supply.
b. Connect the white wire to the positive (+) or return side of the -48V supply.
CAUTION: Do not connect the cables to a PCM that is not in a chassis.
Be sure to shut the breaker off for the unit and disconnect the -48V power cable before removing the PCM from the
chassis.
Replacing a PCM
Follow the steps below to replace a PCM:
1. Be sure you are wearing an ESD strap when handling PCMs.
2. Confirm that you have approximately 7 inches of clearance from the rear of the PCM and any RF cabling in order to
remove the module. If removal of RF cabling is required for clearance, be sure to label the cables appropriately first.
3. Confirm that the other PCM and its power feed is currently functioning. Flip up the hinged front panel at the top of the
chassis and verify that the corresponding set of Bus Branch LEDs are green.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
115
Chapter 4: C4 CMTS General Installation Requirements
4. On the front power status panel, turn the PCM (to be replaced) off for the appropriate power branch by pushing and
holding its power button down. There is an approximate 2-second delay on the power down to avoid accidental
shutdowns.
5. At the rear of the chassis, power off the BUS A or B FEED (the feed of the PCM to be replaced) on the PCM by turning
the MAIN breaker to the OFF position.
6. Remove the power cable.
7. Unscrew the three captive fasteners on the rear of the PCM.
8. Remove the PCM and insert the replacement PCM.
9. Tighten the captive fasteners by hand. If the captive fasteners are tightened using a tool, care should be exercised not
to over-tighten. The recommended torque for these fasteners is 5.0 ±0.5 inch-pounds.
10. Insert the power cable.
11. Power the MAIN breaker switch back ON.
12. Confirm the PCM and power feeds are functioning properly by verifying all four of the replaced BUS (A or B) branch
LEDs are green.
Front Panel Access
Protective panels mounted on the front of the chassis flip open, as illustrated in the figure below.
The top single panel flips up to reveal the power panel and power LEDs.
The mid and lower matching panels flip open to allow access to the ejector clips for the front modules.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
116
Chapter 4: C4 CMTS General Installation Requirements
Another small panel is found beneath the lower matching panel. The chassis slot numbers are printed on it; it flips
down to allow access to the air filter.
Figure 16: C4 CMTS Front Access Panels
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
117
Chapter 4: C4 CMTS General Installation Requirements
The figure below shows the LEDs and power switches for Buses A and B. The system alarm and power indicator LEDs are in
the middle of this panel.
Figure 17: LED and Power Bus Switches
Power Protection Description
The C4 CMTS chassis power configuration consists of three levels of protection:
A and B power feeds controlled by circuit breaker in the PCM
Internal chassis branch fuses and electronic circuit breakers located in the PCM
Fuses located on the front modules (These fuses are not field replaceable)
The C4 CMTS must be installed only by trained service personnel who are familiar with the precautions required when
working in a –48V DC power delivery environment. Power requirements are listed in see "Power (page 79).
A and B Power Feeds
Power is supplied to the C4 CMTS via A and B feeds located at the rear of the unit. The C4 CMTS chassis is protected by two
70-amp breakers located on the rear of the chassis, shown in the figure below. This is the first level of protection.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
118
Chapter 4: C4 CMTS General Installation Requirements
They also serve as the master power switch for the unit. The breakers protect the cables within the C4 CMTS which carry
high current and the power connectors located at the rear of the unit.
Figure 18: C4 CMTS Power Feeds (chassis rear)
Internal Branch Protection
Each A and B power feed is further divided into four internal chassis distribution branches, A through D. Each of these
branches is protected by both an electronic circuit breaker and a 20-amp fuse located in the PCM. These fuses constitute
the second level of protection. They are not field replaceable, nor can they be reset.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
119
Chapter 4: C4 CMTS General Installation Requirements
These feeds supply power to the C4 CMTS midplane and to all circuit modules. Power is distributed to the twenty-one slots
by the four branches as shown in the figure below.
Figure 19: Second Level — Internal Branch Fusing
If, for example, a damaged module or bent pin causes an electrical short, the fuses and overcurrent circuits protect the
power distribution wiring and midplane circuitry from damage.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
120
Chapter 4: C4 CMTS General Installation Requirements
The entire feed for a side is turned on and off by pressing the power control button (the figure blow) on the power panel.
Each push of the button should be held approximately two seconds and will toggle the power from that feed (e.g., one
push turns it off, the next push turns it on). This is a delayed switch to prevent accidental activation.
Figure 20: Power Control Button
In the event of a power fault on a branch:
The electronic breaker for that branch detects the failure and removes power from that branch.
A system power alarm is generated.
The green power OK LED for that branch is turned off and the corresponding branch’s red power fault LED is turned on.
Module (Board-level) Fuses
The third level of protection is at the module level.
Each front module (CAM, RCM, or SCM) has two fuses that protect its internal circuitry.
One fuse is located on the circuit powered by the A bus; and the other on the circuit powered by the B bus.
These on-board module fuses are not field replaceable: if the fuse blows the module must be returned for repair.
Automatic Card Recovery for DC Voltage
Each front module of the C4 CMTS contains multiple DC-to-DC converters to supply the variety of voltages required by
module components. This capability functions independently for each front module and any voltage planes that fall out of
specification can trigger subtle and misleading faults.
In many cases, a voltage measurement that is only slightly out of specification in the High or Low Warning Level Threshold
will not affect the performance of a module and should be considered only as a warning to the operator to take action in
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
121
Chapter 4: C4 CMTS General Installation Requirements
the near future. Voltage planes that are far out of specification can cause the module to stop functioning properly. The
improper function is detected by maintenance and the card is taken out of service (configuration dependent).
Note: By default, logging is enabled but recovery is disabled. To enable recovery or disable logging, contact an ARRIS Tech
Support representative.
Proper operation is ensured by adding support for tiered DC voltage thresholds. The new High and Low Warning
Thresholds are used to trigger log messages for operator notifications (enabled by default). The new High and Low Error
Thresholds are used to trigger card recovery actions (disabled by default). These actions are indicated in the following
figure:
Figure 21: DC Voltage Thresholds
Voltage monitors on the cards continuously measure a multitude of card voltage levels. Maintenance software then
compares these measurements with the threshold values and takes the above actions when voltage levels fall outside of
the specified ranges.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
122
Chapter 4: C4 CMTS General Installation Requirements
If recovery is enabled and the C4 CMTS voltage High or Low Error Threshold level is crossed, normal card recovery action
will occur. On the third Low or High Error Threshold level recovery attempt within a 24-hour period, the C4 CMTS will place
the CAM in an OOS-FLT state until a manual action occurs. If that occurs, the operator must shut/no shut the slot of that
card in order to restore it to service. If an SCM or RCM has three High or Low Error Threshold level recovery attempts in a
24-hour period, then the SCM or RCM goes into a fault state but will continue to try to recover on its own.
Chassis Maintenance
Cleaning the Chassis
Since some cleaners could be dangerous or cause damage to the finish of the chassis, ARRIS recommends only Isopropyl
Alcohol wipes be used.
Air Filters
Dirty air filters cannot be cleaned and reused.
Replacement filters may be ordered from ARRIS in kits of four — normally a year’s supply for one chassis. For ordering
information contact your ARRIS sales representative.
Replacing the C4 CMTS Chassis
How to Replace the Chassis
In the event of a chassis failure in which a replacement is deemed necessary, perform the following steps:
1. Before you begin:
a. Make sure all cables are labeled.
b. Tag each module with the current slot number and be sure modules are returned to same slot.
c. Verify that the new chassis has arrived in good condition. For a fully loaded chassis you will need 40 antistatic bags.
Note: Ensure your ESD strap is in place before handling any C4 CMTS component, modules, or other hardware.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
123
Chapter 4: C4 CMTS General Installation Requirements
2. Enter the write mem command and save the running configuration to a local file and any other relevant information
pertaining to modem counts (this will be referenced after the chassis swap).
3. Use Secure FTP (SFTP) or FTP to transfer the backed-up running-configuration to a system or machine other than the
C4 CMTS.
4. Power the C4 CMTS down.
5. Remove the power feed from the rear of the chassis.
6. Remove cables from the CAM PICs and group them with a tie wrap for ease of identification.
7. Remove all other cables from the SCMs and their PICs after placing identification or labeling on each cable.
8. Remove power supplies from the chassis.
9. Remove active front modules from right to left and put each module into an antistatic bag with an identification tag
indicating which slot it came from.
10. Remove PICs from the chassis rear from right to left. Put each module into an antistatic bag with an identification tag
indicating which slot it came from.
11. Remove the three Fan Trays prior to chassis dismount.
12. Disconnect the chassis ground as a final step prior to chassis dismount. The current chassis can now be swapped with
the new chassis.
13. Reconnect the chassis ground once the new chassis is installed.
14. Install the three Fan Trays following chassis grounding.
15. Insert the power supply modules, restore power supply feeds, and power up the C4 CMTS.
16. Reload the front and rear modules.
17. Begin to re-cable the rear PICs until all cables have been restored.
18. Have a laptop or access to a console port.
19. Power up the C4 CMTS.
20. Monitor linecard status and port status once all cards are active.
21. Verify modems are registering on all CAMs.
22. Ensure the area is clean.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
124
Chapter 5
C4c CMTS Installation Requirements
This chapter provides the operating precautions and installation requirements and procedures for the C4c CMTS.
Note: Do not make any mechanical or electrical modifications to the C4c CMTS equipment. If modified, the C4c CMTS may
no longer comply with regulatory standards.
Safety Precautions ........................................................................... 126
Electrostatic Discharge (ESD) ........................................................... 129
Installation Checklist ........................................................................ 130
Unpacking the C4c CMTS ................................................................. 132
Installation Considerations .............................................................. 134
Rack Mounting the C4c CMTS .......................................................... 137
Main Hardware Components .......................................................... 139
Power Module and Cabling.............................................................. 151
Power Protection Description.......................................................... 159
C4c CMTS Chassis Maintenance ...................................................... 162
Replacing the C4c CMTS Chassis ...................................................... 162
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
125
Chapter 5: C4c CMTS Installation Requirements
Safety Precautions
This section provides safety precautions for installing the C4c CMTS. When setting up the equipment, please observe the
following:
Install the C4c CMTS only in restricted access areas for reasons of security and safety.
Follow all warnings and instructions marked on the equipment.
Ensure that the voltage and frequency of your power source meets or exceeds the voltage and frequency listed on the
equipment’s electrical rating label.
Never force objects of any kind through openings in the equipment because dangerous voltages may be present.
Foreign objects may produce a short circuit resulting in fire, electric shock, or damage to the C4c CMTS and other
equipment.
Connect the C4c CMTS chassis to protective earth ground in compliance with U.S. and International Safety standards.
See see "Grounding the Chassis (page 138).
Lifting Safety
A fully-equipped C4c CMTS weighs approximately 105 lbs. (47.6 Kg). The chassis is not intended to be moved frequently.
Before installing the C4c CMTS, ensure that your site is properly prepared.
When lifting the chassis or any heavy object, follow these guidelines:
Disconnect all external cables before lifting or moving the chassis.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
126
Chapter 5: C4c CMTS Installation Requirements
Do not attempt to lift the chassis by yourself: have at least one other person assist you.
Figure 22: Lifting Hazard Warning
Ensure that your footing is solid and that you balance the weight of the object between your feet.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
127
Chapter 5: C4c CMTS Installation Requirements
To lift the chassis: use two people (one on each side). With one hand grasp the underside of the chassis front at the
recess and with the other hand grasp a back handle and lift slowly. Do not twist your body as you lift.
Figure 23: C4c CMTS Chassis Handles
Keep your back straight and lift with your legs, not your back. If you must bend down to lift the chassis, bend at the
knees, not at the waist, to reduce the strain on your lower back muscles.
Electrical Equipment Guidelines
Follow these basic guidelines when working with any electrical equipment:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
128
Chapter 5: C4c CMTS Installation Requirements
Know where the emergency power-off switch is located for the room in which you are working.
Disconnect all power and external cables before moving the chassis.
Do not work alone if potentially hazardous conditions exist.
Never assume that power has been disconnected; always check.
Do not perform any action that makes the equipment unsafe or might create a potential danger to people.
Examine your work area for possible hazards such as ungrounded power extension cables, missing safety grounds, or
wet floors.
CAUTION: Be sure to connect the chassis to protective earth ground before applying power or inserting modules. An
ungrounded chassis may damage components.
CAUTION: The ports of the C4c CMTS chassis are suitable for connection to intra-building or unexposed wiring or cabling
only. The ports of the chassis MUST NOT be metallically connected to interfaces which connect to outside plant (OSP) or its
wiring. These interfaces are designed for use as intra-building interfaces only, requiring isolation from the exposed OSP
cabling. They are Type 2 or Type 4 ports as described in GR-1089-CORE, Issue 4. Finally, the addition of Primary Protectors
is not sufficient protection from electrical shock in order to connect these interfaces metallically to OSP wiring.
Electrostatic Discharge (ESD)
Preventing Electrostatic Discharge Damage
Electrostatic Discharge (ESD) can damage equipment and impair electrical circuitry. ESD occurs when printed circuit
modules are improperly handled. It may result in module failure or intermittent problems.
The C4c CMTS contains replaceable printed circuit modules. Modules are equipped with a metal faceplate that features
Electromagnetic Interference (EMI) shielding and lever-action latches. Handle the modules by their latches and avoid
touching the printed circuit board and connector pins.
Although the metal faceplate helps to protect the printed circuit modules from ESD, wear an antistatic wrist or ankle strap
whenever handling the modules. Ensure that the anti-ESD device makes good skin contact. The chassis is equipped with
four sockets in which you can ground plug-in wrist straps.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
129
Chapter 5: C4c CMTS Installation Requirements
Installation Checklist
Installation involves mounting the unit in a rack, populating slots with the SCM and RCM, and the client Modules (CAMs),
and Physical Interface Cards (PICs). Then the all the cables must be attached. Finally, the system must be properly
configured using the CLI. Follow the instructions in this section when installing the C4c CMTS for the first time.
Table 12. Installation Checklist
Completed (X)
Task Description
Become familiar with component descriptions
Unpack the C4c CMTS according to the instructions in Unpacking the C4c CMTS (page 132)
Obtain any necessary items not supplied to install the C4c CMTS in your configuration
Prepare the site for installation in accordance with placement and electrical considerations
Install C4c CMTS in rack
Attach the chassis grounding cable
Connect yourself to the chassis ground
Install the Fan Tray Module
Install the one or two Power Modules
Install the Physical Interface Modules (PICs)
Install the front cards (i.e., system and client modules)
Attach to power (DC or AC)
Attach cables
Attach to an operator console
Power up the C4c CMTS
Configure the C4c CMTS according to the instructions in Basic Bring-up Procedure for a C4c CMTS.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
130
Chapter 5: C4c CMTS Installation Requirements
Tools Required
The following tools are required for installation:
#3 Phillips screwdriver for large bolts
#2 Phillips screwdriver
Digital volt meter
Torque wrench (See see "Torque Values (page 131). If used only for F-connectors, torque wrench should be selflimiting to 20 in-lbs.)
Torque Values
The following table lists the recommended torque values for selected screws and fasteners of the C4c CMTS:
Table 13. Recommended Torque Values in Inch-pounds
Fasteners
Torque
Screws for grounding cable
10.0 ±0.5 in-lbs
Captive fasteners of PMs
5.0 ±0.5 in-lbs
F-connectors of PICs
20.0 ±0.5 in-lbs
Items Not Supplied
The following items are not included with the C4c CMTS. Obtain these items before installation:
Appropriate network cables
Operator console or PC with built-in asynchronous terminal emulation
Coaxial cables
48 VDC power supply and/or AC power source
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
131
Chapter 5: C4c CMTS Installation Requirements
Note: The C4c CMTS requires one Router Control Module (RCM). To use the RCM customers must order an ethernet
interface. You may choose either a Small Form-factor Pluggable (SFP) or a 10G Small Form-factor Pluggable (XFP) to be
used with the RCM. For more information, see SFP and XFP Ethernet Interfaces.
Unpacking the C4c CMTS
CAUTION: Installation requires more than one person.
When unpacking the C4c CMTS, use the following steps and checklist:
Inspect the shipping crate before removing the unit. If there is evidence of damage to the crate upon receipt, request
an agent of the carrier to be present before removing the C4c CMTS.
Ensure the crate is right side up. Open crate and carefully remove the packaged unit inside. Then remove the
protective foam from the unit. Do not discard any optional items which are typically packed in small boxes set in the
packing foam.
Remove the remaining contents of the crate. Front and rear modules are shipped in separate cartons, unless you
ordered a configured chassis. In a configured chassis modules are shipped in their slots.
Check the packing slip and verify its contents. If an entire C4c CMTS is ordered, it typically ships with the following
items. Use the checklist provided below to verify that the required items are present.
Table 14.
(X)
Hardware Shipment Checklist
Required Items
One C4c CMTS chassis
One (1) chassis ground cable (green, 4 gauge, approx. 24 inches)
One or two Power Modules (AC, DC, AC/DC, AC/AC or DC/DC)
One DC power cable (red or blue, 10 gauge, approx. 50 ft) for each DC power module
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
132
Chapter 5: C4c CMTS Installation Requirements
(X)
Required Items
Modules for basic configuration (minimal requirement):
One System Control Module II (SCM) and associated physical interface card (PIC)
One Router Control Module (RCM)
One downstream Cable Access Module (CAM) and PIC
One upstream Cable Access Module (CAM) and PIC
Five (5) front filler panels. Must be Type III. Type III filler panels are made specifically for the C4c CMTS; they are
stiffer.
Five (5) rear filler panels (there is no PIC for the RCM)
One (1) Fan Tray Module
One (1) air filter (installed in Fan Tray Module)
One (1) hardware installation kit
One (1) ESD Wrist Strap
One (1) C4c CMTS Serial Cable and adapter for connecting a console to the SCM serial port
Documentation package (zip-lock plastic bag in shipping crate):
One (1) paper copy of the licensing agreement
One (1) copy of the pre-printed packing list
Module Protection
All uninstalled modules are shipped in reusable antistatic shielding bags. If modules are not immediately installed, keep them in
these antistatic bags. Do not remove modules from the antistatic bags unless properly grounded.
Do not place these bags on exposed electrical contacts or else the modules may short circuit.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
133
Chapter 5: C4c CMTS Installation Requirements
Installation Considerations
Rack Mounting
The C4c CMTS is designed to be mounted in a standard 7-foot by 19-inch equipment rack, compliant with EIA RS-310. Ensure
that the rack does not block the airflow vents on either side of the chassis.
Uneven mechanical loading of an equipment rack can be hazardous. Plan the installation so that the weight of the equipment is
evenly distributed across the vertical height of the rack. Depending on the number of modules supported, some C4c CMTS
configurations are heavier than others. Place the heaviest units toward the bottom of the rack.
Note: A half-inch of space is required under the lowest C4c CMTS chassis installed in the frame. Additional chassis can be
mounted directly above the lowest C4c chassis.
Chassis Placement
Select an appropriate installation area that is dry, relatively dust free, well-ventilated, and air conditioned. Be sure the
floor is capable of supporting the combined weight of the rack with the installed equipment.
CAUTION: The C4c CMTS generates a significant amount of heat. Allow enough space around the C4c CMTS for adequate
ventilation and do not block the air vents. Inadequate ventilation could cause the system to overheat.
Clearance
Allow sufficient clearance around the rack for maintenance. If the rack is mobile (not recommended), place the C4c CMTS
near a wall or cabinet for normal operation and pull it out for maintenance (installing or moving port adapters, connecting
cables, and replacing or upgrading components). Be sure there is enough cable length available to pull the C4c CMTS out
for repairs or adjustments if necessary.
Note: Route any front cables to the left side (when facing the system) of the C4c chassis to avoid interference with the Fan
Tray Module.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
134
Chapter 5: C4c CMTS Installation Requirements
Power Requirements
The C4c CMTS uses dual redundant power feeds to supply electrical power to the system. The system is capable of
operating from a single feed in case one of the feeds fails. The supply voltage can be either DC or AC. The C4c CMTS must
be connected to a protected power source. The system consumes a maximum of 1200W of power for DC voltage and
1350W maximum for AC voltage.
The operating range for 115Vac is 100 to 240 Vac, 47 to 63 Hz. The system will shut down if the voltage is outside of these
limits.
When operating on -44VDC and using 1200W, the C4c CMTS draws a maximum of 27.3A. Circuit breakers on the power
feeds should be sized accordingly. The Power Modules in the C4c CMTS will limit the startup current to prevent false
tripping of the circuit breakers.
Cooling Requirements
The C4c CMTS should be installed in a location with adequate ventilation. It is designed for long-term operation at ambient
air temperatures ranging from 41-104°F (5-40°C) and an area that is between 5 to 85 percent relative humidity, noncondensing.
To determine cooling requirements, assume 1350W for worst-case power dissipation. These values assume the worst-case
cooling requirements when the maximum number of CAMs (6) is used.
The C4c CMTS draws cooling air in through the right side of the unit (when facing the front of the chassis) and expels it out
the left side of the unit. Clear airflow must be maintained to ensure adequate ventilation. A closed unit rack assembly is
not recommended.
CAUTION: As with all electrical equipment, operation at excessive temperature accelerates the deterioration of
components and adversely effects performance. Prevent excessive heat buildup in the rack.
Temperature Monitoring
The C4c CMTS monitors module temperatures at approximately 90-second intervals. If the temperature of a front module
falls below, or rises above its operating range, a TempOutOfRangeNotification SNMP trap is generated for that module. If
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
135
Chapter 5: C4c CMTS Installation Requirements
the temperature continues to rise to the module’s thermal limit, the card is powered down and a card
TempOverHeatNotification SNMP trap is generated.
The temperature value read during the last 90-second poll is accessible via both the CLI and SNMP. The show
environment CLI command will display the current temperature of modules in equipped slots. The card Temperature
object in the cardTable table in the cadEquipmentMib MIB module contains the current temperature of the associated
slot.
As shown in figure below, the Fan Tray Module circulates the air that cools the chassis. Air is drawn in through the intake
vent on the right side of the chassis (when facing the front) and moves across the internal components, cooling them as it
passes. The warm air is exhausted through the vents on the left side of the chassis.
To ensure the proper air flow, make sure filler panels are installed in unoccupied chassis slots. It is also important to
change the fan filter at least every three months, and more often if the air at the site is dusty.
CAUTION: Fan filters cannot be cleaned and re-used.
CAUTION: Due to the heat generated by the C4c CMTS, it is critical that preparations are made in advance to change the
fan filter. The fan filter replacement must be completed within a 60-second window or damage may occur to the chassis
and/or the boards.
Note: The diamond-shaped mesh side of the air filter should face toward the modules and away from the fans.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
136
Chapter 5: C4c CMTS Installation Requirements
Figure 24: Internal Air Flow (side view)
CAUTION: Allow sufficient clearance for airflow around the chassis.
Rack Mounting the C4c CMTS
The following steps outline how to rack mount the C4c CMTS.
WARNING: Ensure that the rack is stable and properly bolted to the floor so that weight of the chassis does not make it
unstable.
How to Rack Mount the C4c CMTS
1. Attach the supplied green protective earth ground cable to either the front or rear termination point of the chassis, as
illustrated in the figure above, prior to placing the chassis in the rack. The other end of the protective earth ground
cable should extend to the back. See see "Grounding the Chassis (page 138).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
137
Chapter 5: C4c CMTS Installation Requirements
The attachment screws for this cable are shipped pre-installed in the chassis. Remove the attachment screws from the
desired ground cable location on the chassis and reattach. The recommended torque for these screws is 10.0 ±0.5 inchpounds.
If using telco type racks, be sure to bolt the rack to the floor.
2. Position the C4c CMTS in rack.
3. Install rack bolts to secure the C4c CMTS in position.
4. Secure the loose end of protective earth ground cable to a suitable protective earth ground termination point within
the building installation. If attaching this cable to the frame, ensure that the attachment point is bare metal and that
the frame is bonded to a suitable protective earth ground.
Grounding the Chassis
The C4c CMTS chassis must be properly connected to protective earth ground for safety compliance. You can connect the
protective earth ground wire on the front of the chassis. Install the chassis termination end of the protective earth ground
wire to this location before installing the chassis in the rack. See the procedure above for details on attaching the earth
ground cable to the chassis.
Figure 25: Location of Grounding Terminals
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
138
Chapter 5: C4c CMTS Installation Requirements
Main Hardware Components
The C4c CMTS base system contains the following components:
C4c CMTS chassis
One or two Power Modules (PMs) – Power Feeds A & B
Cable Access Modules (CAMs) and associated Physical Interface Cards (PICs)
Router Control Module (RCM)
System Control Module and associated PIC
One Fan Tray Module containing six fans
Air filter (factory installed)
Chassis Configuration
There are various ways to equip a chassis. CAM configurations are dependent on the configuration of the cable plant of the
subscriber network. The module faceplate in each slot includes a label stating the module type and multiple LEDs to
indicate the module’s status.
Design of the C4c CMTS
The C4c CMTS operates in simplex mode. It does not support Control Complex Redundancy (CCR). A fully equipped C4c
CMTS can support up to 10,000 customer premise devices.
This chassis is equipped with dual redundant power supplies. These can be either AC or DC, or one of each. The chassis can
continue to operate if one of the two power supplies fails. There is one Fan Tray Module which contains six fans and the air
filter.
The client and system modules1 of the C4c CMTS are the same modules that are used by the C4c CMTS. The system and
client modules, the Fan Tray Module, and the Power Modules are all field replaceable.
A fully loaded C4c CMTS is equipped with a total of eight modules, two power modules, and a fan tray module:
One (1) System Control Module (SCM)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
139
Chapter 5: C4c CMTS Installation Requirements
One (1) Router Control Module (RCM)
From one to five 16D or XD CAMs and one to five 12U CAMs in the following combinations:
Table 15. DS and US CAM Combinations in the C4c CMTS
CAMs
Channels
US:DS Ratio
12U
16D or XD
US
DS
1
1
12
16
.75 to 1 (3 : 4)
5
1
60
16
3.75 to 1 (15 : 4)
4
2
48
32
1.5 to 1 (3 : 2)
3
3
36
48
.75 to 1 (3 : 4)
2
4
24
64
.375 to 1 (3:8)
1
5
12
80
.15 to 1 (3 : 20)
Module Types and Chassis Slots—Front View
The C4c CMTS chassis contains eight horizontal slots. These slots are equipped for the following modules (sometimes
referred to as front cards).
One Router Control Module (Slot 17)
One System Control Module (Slot 19)
One to six Cable Access Modules (in a mix of upstream and downstream CAMs) (Slots 10 thru 15)
Note: The slot numbering on the C4c CMTS is not the logical slot order of one through eight but is numbered to
correspond to the C4 CMTS slots. This will help to maintain consistency with CLI command functionality as well as helping
in the case of a chassis upgrade from a C4c to a C4 CMTS.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
140
Chapter 5: C4c CMTS Installation Requirements
The following two illustrations, line art and graphical, show the front of the chassis.
Figure 26: Front View of C4c CMTS
Figure 27: Line Drawing Showing Slot Numbering (front view)
The chassis example shown in the above figure is equipped with:
Three 16D or XD CAMS located in slots 13, 14, and 15
Three 12U or 24U CAMS located in slots 10, 11, and 12
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
141
Chapter 5: C4c CMTS Installation Requirements
One SCM in slot 19
One RCM in slot 17
Slot Numbering Scheme
The eight slots from top to bottom are numbered and populated as follows:
Slot 15
Slot 14
Slot 13
Slot 12
Slot 11
Slot 10
Slot 19
Slot 17
16D or XD CAM
12U or 16D or XD CAM
12U or 16D or XD CAM
12U or 16D or XD CAM
12U or 16D or XD CAM
12U CAM
SCM
RCM
The slot numbering scheme makes the C4c CMTS compatible with C4 CMTS software. Without this numbering scheme the
software would return provisioning errors for cards used in the wrong slots.
The CAMs, RCM, SCM, power modules, and Fan Tray Module plus filter are hot-swappable and field-replaceable units.
Limited Support for the 2Dx12U CAM in the C4c CMTS
The C4c CMTS has limited support for the 2Dx12U CAM:
Up to a maximum of six (6) 2Dx12U CAMs per C4c chassis
If 2Dx12Us are used, then no 16D, XD or 12U CAMs can be used in the same chassis
The 2Dx12U can be used in any CAM slot (i.e., slots 10-15)
The 2Dx12U CAMs can be used for voice or data
The 2Dx12U CAM does not support channel bonding.
Note: The C4c CMTS does not support CAM sparing.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
142
Chapter 5: C4c CMTS Installation Requirements
Chassis — Rear View
Physical Interface Cards (PICs)
Smaller modules, called Physical Interface Cards, or PICs, are inserted in each slot from the rear of the chassis. The PICs
provide physical connectors for terminating cables from the subscriber network and enable the CAMs to be replaced
without having to remove cables.
The figure below shows an example of a rear view of a chassis configured with 12U and 16D CAMs to show their
connectors.
Slots 10-15 are equipped with CAM PICs
Slot 19 is equipped with an SCM PIC
There is no rear slot 17 and the RCM has no PIC.
Figure 28: C4c CMTS Chassis (rear view)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
143
Chapter 5: C4c CMTS Installation Requirements
Midplane
Between the front and back slots is the midplane of the chassis. The midplane connects the front modules to the rear
modules. The midplane is a necessary point of communication for all modules inserted in the C4c CMTS. The midplane is
used as follows:
By the power modules to provide power to the rest of the system
By the SCM and RCM to exchange control information and packets
By the CAMs (client modules) to pass packets to the RCM
By the RCM to pass packets to the CAMs and SCM.
Filler Panels
The C4c CMTS has three types of filler panels:
Front filler panels — used for any unequipped front module slot.
Rear filler panels — used for any unequipped rear PIC slot.
Power Module filler panel - used for an unequipped power module.
All unused module slots, front and rear, must be equipped with filler panels. Filler panels are required for proper EMC
emission levels and sufficient airflow to properly cool the C4c CMTS system. Failure to cover empty slots reduces the air
flow through the chassis and could result in overheating.
Storing Modules
Retain the packaging in which each module was shipped and follow these guidelines for storing modules to avoid damage:
Store each module in a separate antistatic bag. Ideally, store the item in its antistatic bag within the protective
packaging or padded box in which the item was shipped.
Installing Modules in the C4c CMTS
CAUTION: Before removing or replacing any C4c CMTS modules, obtain and attach an antistatic grounding wrist or ankle
strap to protect against damage to components resulting from static electricity.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
144
Chapter 5: C4c CMTS Installation Requirements
CAUTION: Use extreme care when inserting or removing modules from the C4c CMTS chassis. Some components may be
scraped off the bottom of the Printed Wiring Board (PWB).
Module Installation Overview
Each module is installed in three basic steps:
1. Use proper ESD precautions before handling modules.
2. Align and insert module into proper slot. Lock ejector levers before proceeding to the next module: red buttons will
click audibly if module is completely seated in the slot and ejector levers are closed.
3. Install proper PIC or filler panel in the corresponding rear slot of the chassis. (The RCM does not have a PIC.)
Note: If you meet strong resistance when attempting to seat the module, PIC or filler panel, remove it from the chassis and
try reinserting it. Be sure that you have aligned the left and right edges in the correct matching tracks.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
145
Chapter 5: C4c CMTS Installation Requirements
Installation Diagram
Although the figure below shows the SCM, the side ejector lever is the same for all modules and PICs.
Figure 29: Installing the System Control Module
Ejector Levers
The figure below illustrates the ejector lever mechanism on the module faceplates. Once installed the module is locked in
place. The red button in each lever must be pushed before the ejector levers can be operated to release the module.
Always operate both (left and right) ejector levers at the same time when seating or releasing the module.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
146
Chapter 5: C4c CMTS Installation Requirements
Figure 30: Ejector Levers
Fan Tray Module
The C4c CMTS contains one Fan Tray module. When a fan fails, it is easily identified by the Fan LED on the Control and
Display cover on the front of the chassis. Maintenance personnel can replace the failed Fan Tray Module (also called fan
tray) without shutting down the entire system. The chassis can operate even if one of the six fans in the Fan Tray Module
fails.
These fans cool the system components by forcing air from the right side of the chassis through all front modules and out
the left side of the chassis.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
147
Chapter 5: C4c CMTS Installation Requirements
WARNING: To prevent unnecessary damage, the Fan Tray Module should be installed only in a chassis that is securely
mounted in a frame or rack. You should rack-mount the chassis first and then install the Fan Tray Module.
CAUTION: Due to the heat generated by the C4c CMTS system, it is critical that preparations are made in advance to
change the fan filter. The fan filter replacement must be completed within a 60-second window or damage may occur to
the chassis and/or the boards.
How to Install the Fan Tray Module
Perform the following steps to install the Fan Tray Module. Refer to the figure below to identify the location of the Fan
Tray Module.
1. Make sure that the fans are properly seated in the Fan Tray Module so that they do not prevent the Fan Tray Module
from seating properly.
2. Align the Fan Tray on the rails and slide firmly into chassis.
3. With the ejector levers fully open, slide the Fan Tray Module all the way into the slot. Press firmly with equal pressure
top and bottom to align the fan tray in the slot.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
148
Chapter 5: C4c CMTS Installation Requirements
4. Flip the ejector levers toward each other to close and lock the Fan Tray Module in the slot. The teeth of the ejector
levers engage the seating rails and the ejectors click into place if the module is seated correctly.
Figure 31: Installing the Fan Tray Module
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
149
Chapter 5: C4c CMTS Installation Requirements
Air Filter
The C4c CMTS comes equipped with an air filter mounted on the inside of the Fan Tray Module. It is important to change
the fan filter at least every three months, depending on the air quality on site. The figure below shows where the air filter
is located and how it is removed for replacement.
Figure 32: Replacing the Air Filter
CAUTION: Dirty air filters cannot be cleaned and reused.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
150
Chapter 5: C4c CMTS Installation Requirements
To Replace the Air Filter
CAUTION: Due to the heat generated by the C4c CMTS system, it is critical that preparations are made in advance to
change the fan filter. The fan filter replacement must be completed within a 60-second window or damage may occur to
the chassis and/or the boards.
1. Be sure you are wearing an ESD strap when handling any modules.
2. Open the right side panel to access the Fan Tray Module.
3. Flip open the ejector levers away from each other to open and unlock the Fan Tray Module from the slot. Carefully
slide the module out of the seating rails.
4. Quickly remove the air filter by sliding it up and out of the Fan Tray Module. Replace it with a new filter. Ensure that
the diamond-shaped mesh is facing toward the modules and away from the fans.
5. Carefully align the Fan Tray Module on the rails and with the ejector levers open, slide the module firmly all the way
into the slot. Apply equal pressure to the top and bottom of the Fan Tray Module.
6. Flip the ejector levers toward each other to close and lock the Fan Tray Module in place. As the teeth of the levers
engage the seating rails, the Fan Tray Module clicks into place if seated correctly.
CAUTION: The air filter can be incorrectly positioned and cause interference when inserting or removing the Fan Tray
Module.
Note: The diamond-shaped mesh side of the air filter should face toward the modules, away from the fans.
Replacement filters may be ordered from ARRIS in kits of four — normally a year’s supply for one chassis. For ordering
information contact your ARRIS sales representative.
Power Module and Cabling
The C4c CMTS can operate on a single -48V DC or a 115V AC power source, but requires two -48V power feeds, A and B, for
redundancy. In the event that one feed fails or is removed from service for maintenance, the other feed continues to
supply power to the C4c CMTS with no interruption in service.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
151
Chapter 5: C4c CMTS Installation Requirements
The source can be an external battery plant or independent AC or DC power supply. The C4c CMTS chassis can have a DC,
AC, AC/DC, DC/DC, or AC/AC Power Module configuration.
The PM contains the power input connector, main breaker, and all active circuitry for power distribution of a power bus.
The Power Module:
Soft starts the chassis on power up
Filters noise and power disturbances from the power feeds
Monitors the power draw of the chassis and shuts down a branch circuit in the event of a power fault
Note: Review the total current consumption of all equipment on the same line before supplying power to the C4c CMTS.
Avoid sharing a power source that requires large currents.
Each PM is removable and can be replaced without interrupting power to the C4c CMTS in a duplex power configuration.
Figure 33: Installing the PM
How to Install the PMs
Refer to the above figure and follow these steps to install the PMs:
1. Be sure you are wearing an Electrostatic Discharge (ESD) strap when handling modules.
2. Ensure that no power cables are attached to the PMs.
3. Align the PM on the rails in the rear of the chassis and slide firmly into place. From the rear, the PM can be inserted
into either the left or right:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
152
Chapter 5: C4c CMTS Installation Requirements
a. The PM on the right side of the chassis is named PM A. It corresponds to the Bus A power panel LEDs and control
switch located on the front of the chassis.
b. The PM on the left side of the chassis is named PM B. It corresponds to the Bus B power panel LEDs and control
switch located on the front of the chassis.
4. Hand tighten the two captive fasteners on each of the PMs. If the captive fasteners are tightened using a tool, care
should be exercised not to over-tighten. The recommended torque for these fasteners is 5.0 ±0.5 inch-pounds.
5. Connect the appropriate power cable.
The C4c CMTS can operate on a single -48V DC or a 115V AC power source, but requires two -48V power feeds, A and B, for
redundancy. In the event that one feed fails or is removed from service for maintenance, the other feed continues to
supply power to the C4c CMTS with no interruption in service.
The source can be an external battery plant or independent AC or DC power supply. The C4c CMTS chassis can have a DC,
AC, AC/DC, DC/DC, or AC/AC Power Module configuration.
The PM contains the power input connector, main breaker, and all active circuitry for power distribution of a power bus.
The Power Module:
Soft starts the chassis on power up
Filters noise and power disturbances from the power feeds
Monitors the power draw of the chassis and shuts down a branch circuit in the event of a power fault
Note: Review the total current consumption of all equipment on the same line before supplying power to the C4c CMTS.
Avoid sharing a power source that requires large currents.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
153
Chapter 5: C4c CMTS Installation Requirements
Each PM is removable and can be replaced without interrupting power to the C4c CMTS in a duplex power configuration.
Figure 34: Installing the PM
How to Install the PMs
Refer to the above figure and follow these steps to install the PMs:
1. Be sure you are wearing an Electrostatic Discharge (ESD) strap when handling modules.
2. Ensure that no power cables are attached to the PMs.
3. Align the PM on the rails in the rear of the chassis and slide firmly into place. From the rear, the PM can be inserted
into either the left or right:
a. The PM on the right side of the chassis is named PM A. It corresponds to the Bus A power panel LEDs and control
switch located on the front of the chassis.
b. The PM on the left side of the chassis is named PM B. It corresponds to the Bus B power panel LEDs and control
switch located on the front of the chassis.
4. Hand tighten the two captive fasteners on each of the PMs. If the captive fasteners are tightened using a tool, care
should be exercised not to over-tighten. The recommended torque for these fasteners is 5.0 ±0.5 inch-pounds.
5. Connect the appropriate power cable.
Power Requirements
The C4c CMTS must be connected to a protected power source that meets the following current requirements:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
154
Chapter 5: C4c CMTS Installation Requirements
AC Power at 115 Volts AC
Input voltage: 100 to 240 Volts AC
Power consumption: 1000 W nominal and 1350 W maximum
DC Power at -48 Volts DC
Input voltage: -44 to -72 Volts DC
Power consumption: 900 W nominal and 1200 W maximum
Note: The C4c CMTS can be configured with either one or two Power Modules; therefore, the number of cables shipped
with your system depends on the configuration.
Figure 35: Applying Power to the DC PM
How to Cable the DC Power Module
Refer to the figure above and follow the steps below to cable the PM.
1. One or two cables (one red and/or one blue) are included with the C4c CMTS. One end of each cable is connectorized
and keyed for the power connector on the rear of the DC Power Module.
a. Make sure the breaker is in the OFF position before plugging in the power feed cables.
b. Use the connectorized end of the red cable and plug it directly into the PM Power Feed A. If only one PM is
configured, a red or blue cable will be included.
c. If there are two PMs, use the connectorized end of the blue cable and plug it directly into the PM Power Feed B.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
155
Chapter 5: C4c CMTS Installation Requirements
CAUTION: You must ensure the power connections maintain proper polarity. Your power source cables might be labeled
(+) and (-) to indicate their polarity. There is no standard color coding for DC power cables. The color coding used by the
external DC power source at your site determines how the ARRIS CMTS power cables are connected.
2. Each supplied cable contains two 10-gauge wires (one red and one white) that must be hard-wired to the DC source by
a qualified service electrician
a. Connect the red wire to the negative (—) side of the -48V supply.
b. Connect the white wire to the positive (+) or return side of the -48V supply.
CAUTION: Do not connect the cables to a PM that is not in a chassis.
Be sure to shut off the breaker for the unit and disconnect the -48V DC or 115V AC power cable before removing the PM
from the chassis.
Figure 36: Applying Power to the AC PM
How to Cable the AC Power Module
Refer to the figure above and follow the steps below to cable the PM.
1. One or two power cords are included with the C4c CMTS. One end of each cord has an IEC 60320 C19 connector that
attaches to the C20 connection on the rear of the AC Power Module.
2. Make sure the breaker is in the OFF position before plugging in the power feed cables.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
156
Chapter 5: C4c CMTS Installation Requirements
3. Plug the C19 connector into the AC Power Module. Secure the connector by tightening the connector clamp. We
recommend installing two tie straps (as shown below) as supplemental strain relief.
Figure 37: Tie Strap Installation
4. If a redundant AC PM is supplied, repeat step 3 for the redundant PM.
Replacing a Power Module
Follow the steps below to replace a PM:
1. Be sure you are wearing an ESD strap when handling PMs.
2. Confirm that you have approximately seven inches of clearance from the rear of the PM and any RF cabling in order to
remove the module. If removal of RF cabling is required for clearance, be sure to label the cables appropriately first.
CAUTION: If no redundant PM is installed, replacing a PM will interrupt service.
3. Confirm the other PM and power feed is currently functioning. Flip down the hinged front panel at the bottom of the
chassis and ensure that both its LEDs are green.
4. At the rear of the chassis, power off the PM to be replaced by pushing the Main breaker to the off position.
5. Remove the power cable and unscrew the two captive fasteners on the rear of the PM.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
157
Chapter 5: C4c CMTS Installation Requirements
6. Remove the PM and insert the replacement PM.
7. Tighten the captive fasteners by hand. If you are using a tool, tighten according to How to Install the PMs, and insert
the power cable.
8. Power the MAIN breaker back ON.
9. Confirm the PM and power feeds are functioning properly by verifying both of its branch LEDs are green.
Front Panel Access
Protective panels mounted on the front of the chassis flip open, as illustrated in the figure below SFP and XFP Ethernet
Interfaces (page 214).
The bottom single panel flips down to reveal the power panel and power LEDs.
The side panels flip open to allow access to the ejector clips for the front modules.
Figure 38: C4c Front Access Panel
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
158
Chapter 5: C4c CMTS Installation Requirements
The figure below shows the LEDs and power for Buses A and B. The system power indicator and fan status LED is in the
middle of this panel.
Figure 39: LED and Power Bus Status
Power Protection Description
The C4c CMTS chassis power configuration consists of three levels of protection:
A and B power feeds controlled by circuit breaker in the PM
Internal chassis branch fuses located in the PM
Fuses located on the front modules (These fuses are not field replaceable).
The C4c CMTS must be installed only by trained service personnel who are familiar with the precautions required when
working in a –48V DC or 115V AC power delivery environment. Power requirements are listed in Power Requirements.
A and B Power Feeds
Power is supplied to the C4c CMTS via A and B feeds located at the rear of the unit. The power feeds are protected by two
30-amp breakers located on the rear of the chassis, shown in Power Requirements (DC PM) and Power Requirements (AC
PM). This is the first level of protection.
They also serve as the master disconnect switch for the unit. The breakers protect the cables within the CMTS which carry
high current and the power connectors located at the rear of the unit.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
159
Chapter 5: C4c CMTS Installation Requirements
Internal Branch Protection
Each A and B power feed is further divided into two internal chassis distribution branches, A and B. Each of these external
power feeds is protected by both an electronic circuit breaker and a 20-amp fuse located in the PM. These fuses constitute
the second level of protection. They are not field replaceable, nor can they be reset.
These feeds supply power to the C4c CMTS midplane and to all circuit modules. Power is distributed to the eight slots and
the Fan Tray Module by the two branches as shown below.
Figure 40: Second Level — Internal Branch Fusing
If, for example, a damaged module or bent pin causes an electrical short, the fuses protect the power distribution wiring
and midplane circuitry from damage.
The entire feed for a side is turned on and off by pressing the power control button on the power panel as shown in the
figure below. Each push of the button toggles the power from that feed (one push turns it off, the next push turns it on).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
160
Chapter 5: C4c CMTS Installation Requirements
In the event of a power fault on a branch:
The electronic breaker for that branch detects the failure and removes power from that branch.
A system power alarm is generated.
The green power OK LED for that branch is turned off and the corresponding branch’s red power fault LED is turned on.
Figure 41: Power Control Buttons
Automatic Card Recovery for DC Voltage
Each front module of the C4c CMTS contains multiple DC-to-DC converters to supply various required voltages to devices
on the modules. There are also multiple voltage measurement devices that continuously measure the voltage levels while
the maintenance software generates log messages for voltage levels that are outside the specified range for each
measurement point.
In many cases, a voltage measurement that is only slightly out of specification will not affect the performance of a module
and should be considered only as a warning to the operator to take action in the near future. In this case, a failover to a
standby module might cause more issues than remaining on the current active module even though it has a voltage plane
that is slightly out of specification. On the other hand, voltage planes that are far out of specification can cause the module
to stop functioning properly. In this case, sometimes the improper function is detected by maintenance and the card is
taken out of service. There are some cases in which a voltage plane can fail causing the module to stop functioning
properly without an automatic recovery.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
161
Chapter 5: C4c CMTS Installation Requirements
We have taken a two-tiered approach to these problems and a second set of thresholds has been added for each voltage
monitor point on the XD, 12U and 24U CAMs. If the operation event is enabled and the monitored voltage is further out
than the second set of thresholds, then the logging and/or recovery action will be initiated.
The logging and/or recovery functionality can be enabled or disabled by executing the following command:
configure operation event <event id> logging <enable | disable> recovery <enable | disable>
The default states for logging is on or "enabled" and recovery is off or "disabled".
If voltage monitoring on an upstream or downstream CAM reveals three voltage errors within a 24-hour period, then the
C4c CMTS places that client card in an OOS-FLT state. If that occurs, the operator must shut/no shut the slot of that card in
order to restore it to service. If an SCM or RCM has three voltage errors in a 24-hour period, then the SCM or RCM goes
into a fault state but will continue to try to recover on its own.
C4c CMTS Chassis Maintenance
Cleaning the Chassis
Since some cleaners could be dangerous or cause damage to the finish of the chassis, ARRIS recommends only Isopropyl
Alcohol wipes be used.
Air Filters
Dirty air filters cannot be cleaned and reused.
Replacement filters may be ordered from ARRIS in kits of four — normally a year’s supply for one chassis. For ordering
information contact your ARRIS sales representative.
Replacing the C4c CMTS Chassis
How to Replace the Chassis
In the event of a chassis failure in which a replacement is deemed necessary, perform the following steps:
1. Before you begin:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
162
Chapter 5: C4c CMTS Installation Requirements
a. Make sure all cables are labeled.
b. Tag each module with the current slot number and be sure modules are returned to same slot.
c. Verify that the new chassis has arrived in good condition. For a fully loaded chassis you will need 18 static bags for
eight front cards, seven PICs, two PMs, and one Fan Tray Module.
Note: Ensure your ESD strap is in place before handling any C4c CMTS component, modules, or other hardware.
2. Enter the write mem command and save the running configuration to a local file and any other relevant information
pertaining to modem counts (this will be referenced after the chassis swap).
3. FTP the backed-up running-configuration to a system or machine other than the C4c CMTS.
4. Power down the C4c CMTS by turning the breakers to the off position on the Power Modules. (This applies to either AC
or DC power.)
5. Remove the power feed(s) from the rear of the chassis.
6. Remove cables from rear CAM PICs and group them with a tie wrap for ease of identification.
7. Remove all other cables from SCM, RCM, and PICs after each cable has been identified and labeled.
8. Remove power modules from the chassis.
9. Remove active front modules from top to bottom and put each module into a static bag with an identification tag
indicating which slot it came from.
10. Remove PICs from the chassis rear from top to bottom and put each module into a static bag with an identification tag
indicating which slot it came from.
11. Remove the Fan Tray Module prior to chassis dismount.
12. Disconnect the chassis ground as a final step prior to chassis dismount. The current chassis can now be swapped with
the new chassis.
13. Reconnect the chassis ground once the new chassis is installed.
14. Install the Fan Tray Module.
15. Insert the power modules, restore power supply feeds, and power up the C4c CMTS.
16. Reload the front and rear modules. Be sure to route front cables to the left side (when facing the system) of the C4c
chassis to avoid interference with the Fan Tray Module.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
163
Chapter 5: C4c CMTS Installation Requirements
CAUTION: Use extreme care when inserting or removing modules from the C4c chassis. Some components may scrape off
from the bottom of the Printed Wiring Board (PWB).
17. Begin to re-cable the rear PICs until all cables have been restored.
18. Have a laptop or access to a console (serial) port.
19. Monitor linecard status and port status once all cards are active.
20. Verify modems are registering on all CAMs.
21. Ensure the area is clean.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
164
Chapter 6
System Control Module (SCM)
SCM Overview .................................................................................. 165
SCM Replacement ............................................................................ 177
SCM Upgrade to 1GB RAM (SCM II EM) ........................................... 181
SCM II EM (U) ................................................................................... 187
SCM 3 ............................................................................................... 187
Compact Flash .................................................................................. 195
SCM Overview
The System Control Module (SCM) supports:
Two maintenance ports
One maintenance RS-232 interface which supports Baud rate speeds of 9600, 19200, 38400, 57600, 115200
One maintenance Ethernet interface
One bi-directional fabric port
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
165
Chapter 6: System Control Module (SCM)
A system maintenance processor
Figure 42: System Control Module and Physical Interface Card
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
166
Chapter 6: System Control Module (SCM)
SCM/SCM II Ethernet Interfaces
The Ethernet connection must be at least a 10 baseT and half duplex connection. There is only one port but it can be
reached through either one of two RJ45 connectors — one in front and one in back. Only one of these maintenance
Ethernet interfaces on the SCM/SCM IIs may be used at a time.
SCM 3 Ethernet Interfaces
While the SCM 3 Ethernet interfaces are in the same location as those of the SCM and SCM II, the implementation is
different. As on the prior SCMs, the Link/Activity LED’s reside on the SCM 3 front panel. For the SCM 3, however, these
Link/Activity LEDs only reflect the status of the front panel ethernet interface. The SCM PIC-resident ethernet interface
does not have Link/Activity LEDs.
The software will support:
One of the SCM 3 physical ethernet interfaces as active/operational at a time and they will share the SCM MAC address
between them.
The SCM 3 will provide the ability to select either the front or the rear Ethernet port as the active/operational port.
The selection of the (front/rear) port will happen at boot time using the same "menu" as the Ethernet port IP address,
subnet, and gateway.
The setting of the active/operational Ethernet port (front/rear) is printed to the console port during boot, stored in the
SCM PIC (with fan controller), and is persistent across reboots.
A single Ethernet port directional setting applies to both SCM 3s if the system is a duplex system.
For newly manufactured SCM PICs (with fan controllers), the default orientation will have the rear Ethernet port being
active/operational.
Legacy/existing SCM PICs will also have the default orientation of the rear Ethernet port active/operational.
Slots 19 and 20 are reserved for the SCM cards on the C4 CMTS and Slot 19 for the C4c CMTS.
Removing the SCM in a simplex configuration (one SCM) will shut down the CMTS. The SCM provides the ON/OFF power
control for all client modules (CAMs) in the CMTS. If the simplex SCM is removed, then the power converters on all client
modules are shut off.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
167
Chapter 6: System Control Module (SCM)
Primary Software Functions
The primary software functions on the SCMs include:
Persistent store management
System maintenance control
Monitoring all client modules
SNMP agent
System wide data distribution
Alarms monitoring and management
Overload control
Audit control
Billing and measurement data
Common Operation Administration Maintenance and Provisioning (OAM&P) and infrastructure software functions
Telnet processing
SSH processing
FTP processing
RADIUS authentication
TACACS+ processing
PacketCable Common Open Policy Server (COPS)
PacketCable IPSec processing
PacketCable/VoIP Connection Management
PacketCable Gate Control.
LED Status
The LED status descriptions for all SCMs are listed in the following table:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
168
Chapter 6: System Control Module (SCM)
Table 16. LED Status Descriptions—System Control Module
LEDs
Ethernet
Power
Active
Out of
Service
System
Alarm
Off
Off
Off
Slot not powered
On
Off
Off
Powered, in-service, but standby
On
Off
On
Off
Powered but out of service and not active
On
Off
On
On
Powered, initializing, or running tests (not passing
traffic) and not active, or system-level fault
detected.
On
On
Off
Link
Activity
Module Status
Powered, functional, and in service (normal
operational state)
On (green)a
Layer 2 connectivity established
On
Active traffic being passed
(amber)b
a
For the SCM 3, this LED is only available on the front of the module.
b
For the SCM 3, the LED is only available on the front of the module.
LED Test Button
The SCM provides an LED Test button in order to verify the functionality of all active LEDs in the chassis. Testing the LED
functionality on a chassis should be performed upon initialization, and then on a regularly scheduled basis in order to
ensure that all LEDs are functional.
The SCM LED Test Button is recessed. You will need something small and thin, such as a paper clip, to press it.
The following table lists the types of SCMs currently in the field. It includes the size of memory included and ordering codes
for each hardware type.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
169
Chapter 6: System Control Module (SCM)
Table 17. Types of System Control Modules (SCMs)
Short
name
Full name
Vendor ID
RAM
Introduced Memor
y
Flash
Disk
SCM
System Control
Module
SCM00440W
2002
512 MB
SCM II
System Control
Module II w/ Rel 5.x
SCM02440W
2003
SCM II
System Control
Module II w/ Rel 7.x
SCM02440W
SCM II
System Control
Module II w/ Rel 7.x
for C4c
SCM II EM
SCM II EM
(U)
SCM 3
a
Latest
HW
Rev
Ordering
Code
320 MB
ARCT00641
Full-size
G05
708368
512 MB
512 MB
ARCT00638
Full-size
B10
718100
2003
512 MB
512 MB
ARCT00638
Full-size
B10
785108
SCM02440W
2003
512 MB
512 MB
ARCT00638
Full-size
B10
785169
SCM II Enhanced
Memory
SCM02441W
2009
1 GB
512 MB
ARCT01940
Full-size
B02
780263
SCM II Enhanced
Memory (Updated)
SCM02441W
1 GB
4 GB
Compac ARCT02671
t
E03
793931
System Control
Module 3
SCM03441W
2 GB
4 GB
Compac ARCT0502
t
A05
799087
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
2011
2012
Agile p/n
ARRIS only
C4® CMTS Release 8.3 User Guide
170
Chapter 6: System Control Module (SCM)
SCM Faceplate Designation
The following figure displays the various SCM faceplate designations.
Figure 43: SCM Faceplate Designations
SCM PIC Considerations
The SCM PIC in slot 19 comes equipped with a MAC address and a printed label. This MAC serves as the basis for all
generated MAC addresses in the chassis. The slot 19 SCM PIC is also equipped with a fan controller. The fan controller is a
daughter board that is only visible when the PIC is removed from the slot. The SCM PIC used in slot 20 has neither the fan
controller nor the printed MAC address.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
171
Chapter 6: System Control Module (SCM)
Installation
How to Install an SCM
Perform the following steps to install an SCM:
1. Wearing an antistatic wrist strap (or foot strap), connect the strap to one of the ESD points on the chassis.
2. If a filler panel is installed in the front module slot, remove the panel.
3. Grasp the front of the module with both hands and align the module between the guides in slot 19.
4. With the ejector levers fully open, slide the module all the way into the slot. Press firmly with equal pressure top and
bottom to align the module with the midplane connector.
5. Flip the ejector levers toward each other to close and lock the module in the slot. The teeth of the ejector levers will
engage the seating rails and the module will click into place if it is seated correctly. Repeat Steps 3-6 if it does not.
6. For a duplex configuration, insert a second SCM in slot 20.
Due to hardware enhancements, the SCM 3 is not backwards compatible with previous software releases.
7. When ready to attach the console management cables, refer to How to Cable the SCM.
How to Install the SCM PIC
There are two types of SCM PIC (one labeled (O) for the odd slot and one labeled (E) for the even slot). One is equipped
with a daughter board for the fan controller and is labeled PIC SCM (O) and must be installed in slot 19 whether the
configuration is simplex or duplex. The other SCM PIC is labeled PIC SCM (E) and should be installed in slot 20.
Perform the following steps to install the SCM PIC:
1. If a filler panel is installed in the rear PIC slot, remove the panel.
2. Grasp the front of the module with both hands and align the PIC between the guides in the corresponding slot in the
rear of the chassis.
3. To ensure proper seating of the ejector levers, move them to an outward position slightly less than perpendicular to
the faceplate before seating the module in the slot.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
172
Chapter 6: System Control Module (SCM)
4. Slide the PIC all the way into the slot, pressing firmly with equal pressure top and bottom to align the module with the
midplane connector
5. Flip the ejector levers toward each other to close and lock the module in the slot. The module will click into place if it is
seated correctly. Repeat Steps 2-5 if it does not.
Connecting the Operator (System) Console
This section gives a detailed description of the cabling for the operator console. The operator console is necessary to
initially power up and configure the CMTS. Use an asynchronous terminal or a PC with asynchronous terminal emulation
software.
The front panel connector on the SCM (in slot 19) is designed to connect directly to a host device with the supplied cable
and adapter. Do not attach the console to any other network interface.
The pinouts for the asynchronous serial console port, the RJ-45–to–RJ-45 Serial Cable, and the RJ-45–to–DB-9 female DTE
adapter is shown in below as follows:
Table 18. Cabling and Console Port Signaling Using a DB-9 Adapter
Console Port (DTE)
RJ-45–to–RJ-45 Serial Cablea
RJ-45–to–DB-9
Terminal Adapter Console Device
Signal
RJ-45 Pin
RJ-45 Pin
DB-9 Pin
Signal
RTS (Request to Send)
Pin 1b
Pin 8
Pin 8
CTS (Clear to Send)
DTR (Data Terminal Ready) Pin 2
Pin 7
Pin 6
DSR (Data Set Ready)
TxD (Transmit Data)
Pin 3
Pin 6
Pin 2
RxD (Receive Data)
GND System Ground)
Pin 4
Pin 5
Pin 5
GND System Ground)
GND (System Ground)
Pin 5
Pin 4
Pin 5
GND (System Ground)
RxD (Receive Data)
Pin 6
Pin 3
Pin 3
TxD (Transmit Data)
DSR (Data Set Ready)
Pin 7
Pin 2
Pin 4
DTR (Data Terminal Ready)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
173
Chapter 6: System Control Module (SCM)
Console Port (DTE)
RJ-45–to–RJ-45 Serial Cablea
RJ-45–to–DB-9
Terminal Adapter Console Device
Signal
RJ-45 Pin
RJ-45 Pin
DB-9 Pin
Signal
CTS (Clear to Send)
Pin 8b
Pin 1
Pin 7
RTS (Request to Send)
a
Pin 1 is on the left when the RJ-45 connector tab is facing down as shown in the following graphic:
Figure 44: View of Pin-out of Serial Cable
How to Cable the SCM
Perform the following steps to cable the operator console.
1. Locate the supplied 8-foot shielded Ethernet, 10 BaseT, RJ-45–to–RJ-45 Serial Cable and RJ-45–to–DB-9 female
connector.
2. Using the supplied Serial Cable, plug the RJ-45 end into the RS-232 connection on the front of the SCM.
3. Plug the other end of the RJ-45 cable into the RJ-45–to–DB-9 adapter.
4. Plug the adapter into your operator console.
5. When you are ready to begin configuring the CMTS, power on the chassis and boot the software using the procedures
in Replacing the C4 CMTS Chassis. Perform initial setup by entering CLI commands on the operator console.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
174
Chapter 6: System Control Module (SCM)
The following figure illustrates a console port connection:
Figure 45: Connecting the Console Port to a PC
CMTS Base Configuration
The CMTS ships with a configuration database that contains all data required to initialize the CMTS. The base configuration
database is present in the SCM persistent memory — the flash disk.
The base configuration is the minimum data needed to initialize and configure the CMTS. When the CMTS initializes from
the base configuration database, the SCM and Router Control Module (RCM) become active. Configuration procedures
begin once the SCM and RCM are active.
The next section of this chapter contains the procedure for initially setting the system clock, the SCM’s IP address, and
other parameters to customize the CMTS for use in your LAN and time zone. After this procedure is completed, technical
support personnel will be able to administer the CMTS using either the ethernet (telnet) port or serial port of the SCM.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
175
Chapter 6: System Control Module (SCM)
Local and Remote Access to the SCM
The SCM serial port is necessary for the initial configuration of the system. After that, a system administrator can access
the SCM through the ethernet port from any locally connected host. Remote management from any Internet-connected
host is supported once In-Band Management is enabled.
When management through a Router Control Module (RCM) interface is enabled, system administrators can manage the
CMTS remotely, accessing the SCM through any RCM interface. If users choose to enable remote management, they
should also enable Access Control Lists (ACLs) for security. If the ACL feature is enabled, all packets to the SCM are
dropped except those whose source IPs are approved by the ACL.
Local access to the SCM is restricted to any host on the local subnet associated with the SCM ethernet interface. System
administrators who are connected through a local network router will no longer be able to access the SCM through the
SCM ethernet port.
How to Set Up the Terminal Emulator
The following procedure outlines how to set up a command window using a terminal emulator application such as
TeraTerm or Microsoft’s HyperTerm. For help with the emulator of your choice, please consult the vendor-specific
documentation. After setting the IP addresses through the serial port of the SCM, you can telnet into the CMTS system via
the SCM ethernet port.
How to Open the Terminal Emulator Session
Perform the following steps in their proper sequence.
1. Connect the supplied Serial Cable from a serial port of a PC (COM1 or COM2) to the lower connector (type RS232) on
the faceplate of the SCM. The upper connector, type RJ45, is an ethernet port. The two ports are clearly labeled on the
faceplate.
2. Open the terminal emulator application. You may be asked to give the session a name, for example, c4link.
3. Specify a serial port (usually COM1 or COM2) to be used in this connection.
4. Configure the serial port using these settings:
Bits per second
9600 baud (default)
Data bits
8
Parity
None
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
176
Chapter 6: System Control Module (SCM)
Stop bits
Flow control
1
None
Figure 46: Opening a Terminal Session on the CMTS
The PCs at your site may be equipped with operating systems and application software different from the ones chosen
here as examples. Locations of files may also differ.
The CMTS is already set to echo entries. If your emulator gives you the option to echo typed characters locally, turn it
off.
5. Save your terminal emulator.
SCM Replacement
The following procedure should be used when replacing the SCMs in a duplex control complex.
How to Replace an SCM in a Duplex Chassis
Follow the steps below to replace a System Control Module (SCM).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
177
Chapter 6: System Control Module (SCM)
1. Be sure you are wearing an ESD strap when handling the SCM.
2. If you have made any changes to the CMTS configuration since the last write memory command was entered, execute
the write memory command again.
3. Back up the existing configuration of the SCM by performing the following steps:
Enter copy running-config BKUPMMDDYY.cfg
Use Secure FTP (SFTP) or FTP to transfer the backed-up configuration from the CMTS to another system (your PC,
for example).
Verify which SCM is running standby by executing the show linecard status command or by checking the LED status
on the front of the modules. The active SCM will display green Power and Active LEDs. The standby SCM will only
have a green Power LED.
Refer to the following example output for the status of the SCM:
show linecard status
Chassis Type: C4
Slot Description
0
1
2
3
4
8
9
10
11
12
13
15
17
18
19
20
17
18
19
20
12UCAM Spare
CAM (0D, 12U)
CAM (0D, 12U)
24UCAM Spare
CAM (0D, 24U)
CAM (16D, 0U)
CAM (16D, 0U)
CAM (16D, 0U)
CAM (16D, 0U)
CAM (16D, 0U)
CAM (16D, 0U)
16DCAM Spare
RCM A
RCM B
SCM A
SCM B
RCM A
RCM B
SCM A
SCM B
Admin
State
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Up
Oper
State
IS
OOS-FLT
IS
OOS-FLT
IS
IS
IS
IS
IS
OOS-FLT
OOS-FLT
IS
IS
IS
IS
IS
IS
IS
IS
IS
Duplex
State
Standby
Serial
HW Version
Number
07243CMD0029 CAM-01122W/K03
Active
10293CMD0033 CAM-01122W/K05
Active
Simplex
Active
Active
Active
11283CTU0011
12413CXD0278
10063CSD0082
12463CXD0049
10043CSD0155
CAM-01240W/C07
CAM-40032W/G04
CAM-20032W/G04
CAM-40032W/G04
CAM-20032W/G04
Standby
Active
Standby
Active
Standby
Standby
Active
Standby
Active
10053CSD0053
09523RCM0054
10113RCM0001
07023CBM0084
07303CBM0104
10283RCM0013
10273RCM0043
11123CBM0009
11123CBM0006
CAM-20032W/G04
RCM-01000W/E03
RCM-01000W/F03
SCM-02440W/B06
SCM-02440W/B07
RCM-01000W/E04
RCM-01000W/E04
SCM-02441W/E03
SCM-02441W/E03
Prov/Det
Type
CAM/CAM
CAM/CAM/CAM
CAM/CAM/CAM
DMM/DMM
DMM/DMM
DMM/DMM
DMM/DMM
DMM/DMM/DMM/DMM
RCM/RCM
RCM/RCM
SCM/SCM
SCM/SCM
RCM/RCM
RCM/RCM
SCM/SCM
SCM/SCM
4. Unplug the standby SCM card and plug in the replacement SCM. You must use a compatible SCM (see note below).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
178
Chapter 6: System Control Module (SCM)
The SCM 3 can only be operated in software Release 8.1 or later. Also, the SCM 3 is not compatible with SCMs or SCM IIs in
duplex systems.
5. Allow the CMTS to return to duplex. Confirm by executing the show linecard status command. The standby SCM will
display IS Standby.
6. Depending on the current firmware version of the new SCM, the system may require a reload commit. Log into the
standby SCM and enter the following command:
show version detail
Using the system output, verify that the FPGA versions show TRANSIENT.
If they do not show TRANSIENT continue to next step.
If they do show TRANSIENT then perform a reload commit from the active SCM. The reload
take up to 40 minutes to complete.
commit command can
Example of FPGA firmware in TRANSIENT state:
FPGA Versions:
sandm
= 08.04.00[TRANSIENT]
Boot Versions:
boot0
= CMTS_BOOT0_V00.00.85
boot1
= CMTS_BOOT1_V00.09.62
boot2
= CMTS_BOOT1_V00.09.62
7. Perform a soft-switch to switch the active pair over to standby by entering the following command:
configure interface system-controller xx soft-switch
Where:
xx = active SCM slot
If using telnet for access to the CMTS, the telnet session will be disconnected during the soft-switch and will require the
user to telnet back in.
8. Allow system to return to duplex. Confirm by executing the show linecard status command. The standby SCM card
should show IS Standby.
9. Unplug the standby SCM and plug in the replacement SCM.
10. Allow the system to return to duplex. This can be confirmed by executing the show linecard status command. The
standby SCM should show IS Standby.
11. Depending on the current firmware version of the new SCM, the system may require a reload commit. Log into the
standby SCM card and enter:
show version detail
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
179
Chapter 6: System Control Module (SCM)
Check the FPGA versions for the standby SCM slot and validate if any of the FPGA versions show TRANSIENT.
If they do not show TRANSIENT continue to next step.
If they do show TRANSIENT then a reload commit should be performed from the active SCM. The reload commit
command can take up to 40 minutes to complete.
Example of FPGA versions showing TRANSIENT
FPGA Versions:
sandm
= 08.04.00[TRANSIENT]
Boot Versions:
boot0
= CMTS_BOOT0_V00.00.85
boot1
= CMTS_BOOT1_V00.09.62
boot2
= CMTS_BOOT1_V00.09.62
After the reload commit has completed perform a soft-switch from the active copy over to standby:
configure interface system-controller <slot> soft-switch
Where:
xx = active SCM slot
If using telnet for access to the CMTS, the telnet session will be disconnected during the soft-switch and will require the
user to telnet back in.
12. Allow system to return to duplex. This can be confirmed by executing the show linecard status command. The
standby SCM should show IS Standby.
13. Check system for normal operation.
How to Replace an SCM in a C4c CMTS or a Simplex Chassis
Follow the steps below to replace a System Control Module (SCM) in a simplex system.
1. This procedure requires out-of-band management. Verify that you have a working console connection from your PC to
the serial port at the bottom of the faceplate of the SCM. See How to Cable the SCM for more information.
2. If you have made any changes to the CMTS configuration since the last write memory command was entered, execute
the write memory command again.
3. Back up the existing configuration of the SCM by performing the following steps:
Enter copy running-config BKUPMMDDYY.cfg
where BKUPMMDDYY is the name of your backup configuration file.
Use Secure FTP (SFTP) or FTP to transfer the backed-up configuration from the CMTS to your PC.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
180
Chapter 6: System Control Module (SCM)
Open the BKUPMMDDYY.cfg file to make sure that this step succeeded.
4. Power down the C4c CMTS (or simplex chassis).
5. Be sure you are wearing an ESD strap when handling SCMs. Remove your existing SCM and insert the spare SCM.
6. Connect your cable to the SCM that you just installed.
7. Power on the C4c CMTS or simplex chassis.
8. Open the backup config file you FTP’d to your PC.
9. On your PC open a console window (terminal emulator). See How to Open the Terminal Emulator Session if you need
help with this.
10. Start a capture file in case you encounter problems and need help from Tech Support.
11. Copy portions of the backup config file and paste it into the console window. Watch the commands for success or
failure responses.
12. Repeat step as necessary until you have pasted the rest of the backup config file into your console window.
13. Do a show version in order to verify that the version of the software loaded on the flash disk of the new SCM is the
one you want to use. If not, you’ll have to do a software upgrade.
Once you have finished restoring the configuration, do a
write memory
command to save your changes.
Backing up the Existing Configuration of the SCM
1. Enter the following command:
copy running-config verbose /system/cfgfiles/BKUPMMDDYY.cfg
2. Use Secure FTP (SFTP) or FTP to transfer the backed-up configuration from the CMTS to another system (your PC, for
example).
SCM Upgrade to 1GB RAM (SCM II EM)
The CMTS supported 24,000 devices in Release 7.x with no hardware changes to the SCM. The SCM II with Enhanced
Memory (SCM II EM) contains a one gigabit Dual-In-line Memory Module (DIMM) RAM and supports 40,000 devices.
The CMTS must be running software version 7.1.x or later in order to perform this upgrade.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
181
Chapter 6: System Control Module (SCM)
Upgrading the SCM to 1 GB — Duplex System
Perform the following steps to upgrade the SCM in a duplex system:
Be sure that you are wearing an ESD strap and use ESD precaution when handling the SCM card(s) and DIMM modules.
1. Shutdown the SCM intended for upgrade by using the command:
configure slot <X> shutdown
2. Remove the SCM from the CMTS chassis and place on a flat, grounded antistatic mat with the components facing up.
3. Remove the DIMM from the connector by prying outward on the ejector latches located at both ends of the connector.
See the figure below. (In the event of an upgrade failure, temporarily retain the 512MB DIMM module in the staticproof bag in which the 1GB DIMM was shipped.)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
182
Chapter 6: System Control Module (SCM)
Figure 47: Removing the DIMM
1. Replace the removed DIMM module with the new 1GB DIMM shipped in the Upgrade Kit. The label must face upward
and the DIMM must be centered with the connector. Press firmly against the back edge of the DIMM module using
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
183
Chapter 6: System Control Module (SCM)
your thumbs. See next figure. Slide the DIMM into the connector until the latches at both ends snap into the locking
notches on the DIMM module.
Figure 48: Replacing the DIMM Module
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
184
Chapter 6: System Control Module (SCM)
2. Apply the new front panel label supplied in the Upgrade Kit over the top of the existing label in the concave area as
shown in the following figure.
Figure 49: Labeling the SCM
3. Reinsert the upgraded SCM into the CMTS chassis and enable the SCM by entering:
configure slot <x> no shutdown
4. Allow the SCM to boot up in the CMTS chassis. If it fails to boot, remove the SCM from the chassis, remove and reseat
the DIMM module. Then reinsert the SCM into the chassis.
5. If the SCM fails to boot a second time, obtain the serial port output and contact technical support at ARRIS.
6. Once the upgraded SCM has booted, enter:
show version detail <slot>
The output should indicate that the SDRAM has 1024 MB.
7. To ensure that all modules are in-service (IS), enter:
show linecard status
8. Once all cards are in-service, a softswitch can be executed to force the newly upgraded SCM to ACTIVE and force the
other SCM to STBY. Enter:
configure interface <slot> soft-switch
9. Once the system is running duplex, repeat steps 1 - 9 to upgrade the memory in the standby SCM.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
185
Chapter 6: System Control Module (SCM)
Upgrading the SCM to 1 GB — Simplex System
Perform the following steps to upgrade the SCM in a C4c CMTS or a simplex system:
Be sure that you are wearing an ESD strap and use ESD precaution when handling the SCM card(s) and DIMM modules.
1. Power down the CMTS.
2. Remove the SCM from the CMTS chassis, and place onto a flat, grounded antistatic mat with the component side up.
3. Remove the DIMM from the connector by prying outward on the ejector latches located at both ends of the connector.
Temporarily retain the 512 MB DIMM module in the static-proof bag in which the 1GB DIMM was shipped in the event
of an upgrade failure.
4. Replace the removed DIMM module with the new DIMM shipped with the Upgrade Kit. The label must face upward
and the DIMM must be centered in the connector. Press firmly against the back edge of the DIMM module using your
thumbs.
Slide the DIMM into the connector until the latches at both ends snap into the locking notches on the DIMM module.
5. Reinsert the upgraded SCM into the CMTS chassis.
6. Apply the new front label supplied in the Upgrade Kit by placing it over the top of the existing label in the concave
area.
7. Allow the SM to boot up in the CMTS chassis. If the SCM fails to boot, remove the SCM from the chassis, then remove
and reseat the SDRAM DIMM module. Then reinsert the SCM into the chassis.
8. If the SCM fails to boot a second time, obtain the serial port output and contact technical support at ARRIS.
9. Once the upgraded SCM had booted, enter:
show version detail <slot>
The output should indicate that the SDRAM is 1024MB.
Virtual System Controller
The Virtual System Controller feature offers the operator the ability to direct the console port on either SCM to the active
or standby SCM. This takes place once the SCMs are in service.
Use the following command if you want the console port to be always redirected to the active SCM (this is the default
setting):
configure line console 0 1 connect active
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
186
Chapter 6: System Control Module (SCM)
Use the following command to redirect the console port to the SCM that you plugged into:
configure line console 0 1 connect local
When using the local method your authentication will be local only on the standby SCM.
SCM II EM (U)
The System Control Module (SCM) has been in production since 2002. The SCM II EM (U) was implemented in Release
7.3.2.2 to extend its production life due to the replacement of some end-of-life (EOL) components. Since some of these
components are not software compatible, new software drivers were required to use the SCM II EM (U).
Due to hardware enhancements, the SCM II EM (U) is not backwards compatible with previous software releases. Because
of this incompatibility, the SCM II EM (U) will have a new product code to differentiate it from the existing SCM. Refer to
Types of System Control Modules (SCMs) for the comprehensive list of SCMs.
The SCM II EM (U) will include the 4 GB Enhanced Memory compact flash disk and replaces existing SCM hardware. With
updated software, any combination of existing SCM and SCM II EM (U) modules may be used in a duplex C4 CMTS chassis.
SCM 3
Beginning in Release 8.1, the SCM 3 processor complex including its RAM memory has been replaced in order to increase
performance. The SCM 3 maintains the same standards compliance as the SCM and SCM II.
Due to hardware enhancements, the SCM 3 is not backwards compatible with previous software releases. Because of this
incompatibility, the SCM 3 has a new product code to differentiate it from the existing SCM. Refer to Types of System
Control Modules (SCMs) for the comprehensive list of SCMs.
The SCM 3 includes the 4 GB Enhanced Memory compact flash disk and replaces existing SCM hardware. The SCM 3 can be
operated only in software Release 8.1 or later. Also, the SCM 3 is not compatible with SCMs or SCM IIs in duplex systems.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
187
Chapter 6: System Control Module (SCM)
SCM 3 Operational Interaction
When an SCM 3 and a prior-version SCM (SCM or SCM II (EM)) are plugged into the same chassis running Release 8.1,
there will be no undesirable physical interaction but one of the following scenarios will happen:
Scenario 1 — When a C4 CMTS is operating with a single, prior-version SCM and an SCM 3 is then inserted, the system will
continue normal operation in single SCM mode with the prior-version SCM active but will ignore the SCM 3. Any attempts
to bring the SCM 3 into an operational state will be rejected and the SCM3 modules will remain OOS. In addition, the active
SCM will generate a log at the ERROR level declaring that the clone cannot be made duplex operational.
Scenario 2 — When a C4 CMTS is operating with a single SCM 3 and a prior-version SCM is inserted, the system will
continue normal operation in single SCM mode with the SCM 3. The system will ignore the prior-version SCM and any
attempts to bring the prior-version SCM into an operational state will be rejected and the prior version SCM will remain
OOS. The active SCM will generate a log at the ERROR level declaring the SCM vintage mismatch cannot be made duplex
operational.
Scenario 3 — If the C4 CMTS powers up or the system resets with a mismatched control complex (one SCM 3 and one
prior-version SCM), which SCM is selected as the active SCM is indeterminate, but historically will favor slot 19. Since the
control complex is mismatched, the SCM not chosen will remain out-of-service (OOS). If the SCM 3 is active, it will generate
a log at the ERROR level declaring that the clone cannot be made duplex operational because it is not an SCM 3. If the nonSCM 3 is active, then it will generate a log at the ERROR level declaring that the clone cannot be made duplex operational.
In this case it is not possible for the non-SCM 3 to determine why.
Out-of-Band Management on the SCM 3
For the SCM 3, the SCM PIC ethernet interface will support and advertise the following speeds:
10baseT (portType eport10BaseT(3)) and
100baseT (portType eport100BaseT(4)), full duplex
1000baseT is not supported with the current SCM PIC.
The default active/operational interface for the SCM 3 is the rear PIC ethernet. The front port can be made
active/operational using the serial control interface boot dialog. As with prior version SCMs, Link/Activity LEDs only reside
on the SCM 3 front panel. For the SCM 3, however, these Link/Activity LEDs only reflect the status of the front panel
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
188
Chapter 6: System Control Module (SCM)
ethernet interface. The SCM PIC-resident ethernet interface has no Link/Activity LEDs. If running a duplex system, any
changes made to one SCM will also affect the other SCM.
The front panel Ethernet interface will support and advertise the following speeds;
10baseT (portType eport10BaseT(3)),
100baseT (portType eport100BaseT(4)), and
1000baseT (portType eport1000BaseT(4)), full duplex
Upgrading a C4 CMTS to an SCM 3
Due to hardware incompatibilities, SCM 3s cannot become fully operational in the same chassis with prior-version SCMs.
This makes a hitless chassis upgrade impossible: all upgrade scenarios will involve the chassis being down for some amount
of time.
The SCM 3 Compact Flash will work with the SCM II EM(U) but it is not compatible with any other prior-version SCM.
Assumptions:
The C4 CMTS is running with SCM II, SCM II EM and SCM II EM(U) active/standby and running SW version 8.2.
The SCM 3 flash disk is pre-programmed at the factory with at least:
the Release 8.1.x (or later) image
null config file (skeleton database)
SCM 3 Upgrade Procedures
There are four possible scenarios, covered by the following procedures, to use when upgrading to an SCM 3:
Upgrade to an SCM 3 with the Compact Flash from an SCM II EM(U)
Upgrade to an SCM 3 Using the Serial Console Port (RS 232) Only
Upgrade to an SCM 3 Using the OOBM Ethernet Interface (via rear port of the SCM PIC)
Upgrade to an SCM 3 Using the OOBM Ethernet Interface (via front port of the SCM 3 Module)
"OOBM" is an abbreviation for out-of-band management.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
189
Chapter 6: System Control Module (SCM)
Upgrade to an SCM 3 with the Compact Flash from an SCM II EM(U)
1. Perform a write memory to save the existing configuration. Make sure the chassis is running the 8.x.x.x software load.
Once you have verified that you are on the 8.x software load, execute a reload commit.
2. Back up the existing configuration with the following command:
copy running-config verbose /system/cfgfiles/backupMMDDYY.cfg
3.
4.
5.
6.
Use Secure FTP (SFTP) or FTP to transfer the configuration off the CMTS and save it on a local machine/server.
Power down the C4 CMTS.
Remove the SCM or SCM-II cards from the chassis.
Remove the flash disks from the two SCM II EM(U) cards that you removed and place them in the two SCM 3 cards. See
Replacing the Compact Flash Disk on a Duplex System.
7. Insert the two SCM 3 modules in slots 19 and 20.
8. If the previous SCMs had RS-232 serial or ethernet cables connected to the front of the card, then reconnect those
cables.
Note: By default, the SCM 3 out-of-band Ethernet cable connection defaults to the rear PIC connector. Either move the
out-of-band Ethernet cable to the rear PIC connector, or follow Upgrade to an SCM 3 Using the OOBM Ethernet Interface
(via front port of the SCM 3 Module) to use the front Ethernet connector.
9. Verify that all modules are in-service and that modems have registered.
10. Execute the following command:
reload commit
Upgrade to an SCM 3 Using the Serial Console Port (RS 232) Only
Note: This procedure is meant for sites using in-band management with no out-of-band Ethernet access.
1. Perform a write memory to save the existing configuration. Make sure the chassis is running the 8.x.x.x software load.
Once you have verified that you are on the 8.x.x.x software load, execute a reload commit.
2. Back up the existing configuration with the following command:
copy running-config verbose /system/cfgfiles/backupMMDDYY.cfg
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
190
Chapter 6: System Control Module (SCM)
3. Use Secure FTP (SFTP) or FTP to transfer the configuration off the CMTS and save it on a local machine/server. The
configuration will be required later.
4. Power down the C4 CMTS.
5. Remove the SCM or SCM-II cards from the chassis.
6. Insert the SCM 3 modules in Slots 19 (and 20 if duplex).
7. Reconnect the serial port console cable(s).
8. Power up the chassis with both SCM 3 cards inserted.
9. Wait for the RCM and SCM 3 modules to go into Active/Standby state on the Release 8.x image.
10. Using the serial port, re-populate the configuration by cutting and pasting the previously saved configuration (from
step above). You should paste a small portion of the configuration file at a time and verify after each paste that no
errors have occurred.
Note: For large configuration files, time can be saved by using only the serial port to configure the network interfaces,
routing protocols, inband access, ACLs, users, authentication (local, TACACS, RADIUS), vtys, and telnet or SSH access. Then
configure ftp-server and ftp the backup configuration onto the CMTS. Then perform the following command: exc file
backupMMDDYY.cfg.
11. Save your configuration:
write memory
12. Verify CMs register.
13. Commit the software image to all client cards:
reload commit
The C4 CMTS is now operating with SCM 3s and its configuration file is back\-upMMDDYY.cfg. It is running on Release
8.x.x.x software, which has been committed. If the image currently on the SCM cards is not the desired load, then upgrade
to the desired load using the normal upgrade procedure. Refer to the Release Notes for more information.
Upgrade to an SCM 3 Using the OOBM Ethernet Interface (via rear port of the SCM PIC)
1. Perform a write memory to save the existing configuration. Make sure the chassis is running the 8.x.x.x software load.
Once you have verified that you are on the 8.x.x.x software load, execute a reload commit.
2. Back up the existing configuration with the following command:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
191
Chapter 6: System Control Module (SCM)
copy running-config verbose /system/cfgfiles/backupMMDDYY.cfg
3. Use Secure FTP (SFTP) or FTP to transfer the configuration off the CMTS and save it on a local machine/server. The
configuration will be required later.
4. Power down the C4 CMTS.
5. Remove the SCM or SCM-II cards from the chassis.
6. Insert the SCM 3 cards in slots 19 (and 20 in a duplex chassis).
7. If previously installed, reconnect the RS-232 serial console cable(s) to the front of the SCM 3 card(s).
8. Power up the C4 CMTS.
9. Wait for SCM 3 to go Active/Standby on 8.x.x.x image shipped from the factory.
10. Enable FTP protocol using the following command:
configure ftp-server
11. FTP the backupMMDDYY.cfg file to /system/cfgfiles.
12. Execute the backup configuration file:
exc file /system/cfgfiles/backupMMDDYY.cfg
13. Save your configuration:
write memory
14. Verify that CMs register.
15. Commit the software image to all client cards:
reload commit
The C4 CMTS is now operating with SCM 3s and its configuration file is backupMMDDYY.cfg. It is running on Release 8.x.x.x
software, which has been committed. If the image currently on the SCM cards is not the desired load, then upgrade to the
desired load using the normal upgrade procedure. Refer to the Release Notes for more information.
Note: By default, the SCM 3 out-of-band Ethernet cable connection defaults to using the rear PIC connection.
Upgrade to an SCM 3 Using the OOBM Ethernet Interface (via front port of the SCM 3 Module)
1. Perform a write memory to save the existing configuration. Make sure the chassis is running the 8.x.x.x software load.
Once you have verified that you are on the 8.x.x.x software load, execute a reload commit.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
192
Chapter 6: System Control Module (SCM)
2. Back-up the existing configuration with the following command:
copy running-config verbose /system/cfgfiles/backupMMDDYY.cfg
3.
4.
5.
6.
FTP the configuration off the CMTS and save it on a local machine / server. The configuration will be required later.
Power down the C4 CMTS.
Remove the SCM or SCM-II cards from the chassis.
If out-of-band access is used and the Ethernet cables were connected to the front of the old SCM, reconnect them to
the front of the new SCM 3 (or reconnect them to the rear PIC because the SCM 3 will use the rear SCM PIC port for
OOB by default).
7. Out-of-band SCM Ethernet access defaults to the rear SCM PIC. Depending on your environment, you can choose to
connect to the rear SCM PIC or use step below to use the front Ethernet connector. If you choose to move the cables
to the rear SCM PIC, go to step . If Ethernet cables are used and will remain connected to the front port, continue with
step 8.
8. Insert the SCM 3 card in slot 19 and connect serial console cable and the front Ethernet cable.
9. To change the default operation to use the front port, power up the chassis with the SCM 3 card in slot 19. See the
sample bootloader script below. Using the example below, respond as instructed.
Example of Bootloader Script
The bootloader script allows you to reconfigure default parameters.
#####################################################################
To change any of this, press <m> and <RETURN> key within 2 seconds
#####################################################################
Type m followed by the RETURN key within two seconds. If you miss the prompt and fail to enter
Modify mode, then reseat the card to restart the bootloader script.
PASSWORD:
Enable Password Recovery ?[No]
Hit the RETURN key.
REAR ETHERNET INTERFACE PARAMETERS:
Enable the System Controller's ethernet port ? [Yes]
Hit RETURN.
Select ethernet port: 0-Front 1-Rear:[1]
Type 0 followed by the RETURN
key to use the front ethernet port.
IP address for the System Controller ethernet port?[10.44.108.1]
Use a subnet mask for the ethernet port interface?[Yes]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Hit RETURN.
Hit RETURN.
C4® CMTS Release 8.3 User Guide
193
Chapter 6: System Control Module (SCM)
Subnet mask for the above IP address?[255.255.255.248]
Do you want to specify a default gateway router?[Yes]
IP address for the default gateway router?[10.44.108.6]
to boot).
Hit RETURN.
Hit RETURN.
Hit RETURN (the SCM 3 continues
#####################################################################
To change any of this, press <m> and <RETURN> key within 2 seconds
#####################################################################
(M)odify any of this or (C)ontinue?
Type C followed by the RETURN key.
While the bootloader continues, you should plug in the SCM 3 in slot 20 if your chassis is
duplex. This is the next step below. Let the rest of the bootloader script run until you see the
login prompt.
•
•
•
connecting to SCM 19
======================================================================
Login:
1. (If duplex) Insert an SCM 3 in slot 20 as the SCM 3 in slot 19 is finishing its boot-up process. If the SCM/RCM pair in
slots 19/17 have already come up and are in simplex mode, then reseat both slots 19 and 20 to bring the system up in
duplex mode.
2. Power up the chassis with both SCM 3 cards inserted (if not previously done).
3. Wait until the SCM 3 cards and RCM cards go Active/Standby state on the image shipped from the factory.
4. Enable FTP protocol using the following command:
configure ftp-server
5. FTP the backupMMDDYY.cfg file to /system/cfgfiles.
6. Execute the backup configuration file:
exc file /system/cfgfiles/backupMMDDYY.cfg
7. Save your configuration:
write memory
8. Verify that CMs register.
9. Commit the software image to all client cards:
reload commit
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
194
Chapter 6: System Control Module (SCM)
The C4 CMTS is now operating with SCM 3s and its configuration file is backupMMDDYY.cfg. It is running on Release 8.x.x.x
software, which has been committed. If the image currently on the SCM cards is not the desired load, then upgrade to the
desired load using the normal upgrade procedure. Refer to the Release Notes for more information.
Compact Flash
CAUTION: Flash disks from Rev. B SCMs are not compatible with the flash drives of Rev. E and later SCMs, and vice versa.
The older SCMs use a disk with a 70-pin connector; newer SCMs use a disk with a 50-pin connector. Also, the two types of
disk do not have the same physical dimensions. If you attempt to insert the removable flash disk from one type into the
flash drive of the other, you can damage the module and render it unusable.
The flash disk drive of the SCM II EM (U) and SCM 3 changes to a new physical format. The following description covers the
4GB compact flash disk for the SCM II EM (U) and higher models only.
Physical Dimensions
The compact flash disk has a standard 50 pin connector consisting of two rows of female contacts as illustrated in the
following graphic.
Figure 50: Pin-out of 4GB Flash Disk Connector
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
195
Chapter 6: System Control Module (SCM)
CAUTION: Be careful when removing /inserting the 4 GB compact flash disk. The retainer latch is delicate and can be
damaged or broken.
Replacing the Compact Flash
Replacing the Compact Flash Disk on a Duplex System
Follow the steps below to replace a compact flash disk on an SCM.
Be sure you are wearing an ESD strap when handling the SCM and the compact flash disk.
1. Verify that the SCM whose flash disk needs to be replaced is currently the standby SCM. If not, perform a soft switch.
2. Shutdown the standby SCM, whose flash disk is going to be replaced, using the command:
configure slot <X> shutdown
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
196
Chapter 6: System Control Module (SCM)
3. Remove the SCM from the CMTS chassis and place on a flat, grounded antistatic mat with the components facing up.
The following figure shows the location of the compact flash disk on the SCM II EM (U) and SCM 3.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
197
Chapter 6: System Control Module (SCM)
4. Remove the compact flash disk from the SCM by moving the spring-loaded retainer latch 90° to the right and then
pushing up. This action will release the compact flash disk from the socket and you can then pull it out using the yellow
"pull tab". See below.
5. Insert the replacement compact flash disk. The label must face upward and the retainer latch should again be moved
90° to the right. Now move the compact flash into the slot and slide it forward until you hear a "click" and the retainer
latch snap back into the locked position. See below.
6. Reinsert the upgraded SCM into the chassis and reconnect the serial port and ethernet cables, if used.
7. Enable the SCM by entering:
configure slot <x> no shutdown
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
198
Chapter 6: System Control Module (SCM)
8. Allow the SCM to boot up in the CMTS chassis. If it fails to boot, remove the SCM from the chassis and then reinsert the
SCM into the chassis.
9. If the SCM fails to boot a second time, obtain the serial port output and contact technical support at ARRIS.
10. Once the upgraded SCM has booted, enter:
show version detail <slot>
The output should indicate the proper flash disk size.
11. To ensure that all modules are in-service (IS), enter:
show linecard status
12. Save your configuration:
write memory
13. Commit the software image to all client cards:
reload commit
Replacing the Compact Flash Disk on a Simplex System
Perform this procedure to replace the compact flash disk on an SCM in a simplex system.
Be sure that you are wearing an ESD strap and use ESD precaution when handling the SCM card(s) and DIMM modules.
1. Perform a write memory to save the existing configuration.
2. Back up the existing configuration with the following command:
copy running-config verbose /system/cfgfiles/backupMMDDYY.cfg
3.
4.
5.
6.
Use Secure FTP (SFTP) or FTP to transfer the configuration off the CMTS and save it on a local machine/server.
Power down the C4 CMTS.
Remove the SCM from the CMTS chassis and place on a flat, grounded antistatic mat with the components facing up.
Remove the compact flash disk from the SCM by moving the spring-loaded retainer latch 90° to the right and then
pushing up. This action will release the compact flash disk from the socket and you can then pull it out using the yellow
"pull tab".
7. Insert the replacement compact flash disk. The label must face upward and the retainer latch should again be moved
90° to the right. Now move the compact flash into the slot and slide it forward until you hear a "click" and the retainer
latch snap back into the locked position.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
199
Chapter 6: System Control Module (SCM)
8. Reinsert the upgraded SCM into the chassis and reconnect the serial port and ethernet cables, if used.
9. Power up the chassis.
10. Verify that the SCM and RCM modules are in-service.
11. Using the serial port, repopulate the configuration by cutting and pasting the previously saved configuration (from step
above). You should paste a small portion of the configuration file at a time and verify after each paste that no errors
have occurred.
If you are using out-of-band management, then instead of using the serial port, you can use the ethernet port to reload
your configuration. To do this configure ftp-server and ftp the backup configuration onto the CMTS. Then perform the
following command: exc file backupMMDDYY.cfg.
12. Save your configuration:
write memory
13. Verify that the CMs register.
14. Commit the software image to all client cards:
reload commit
The C4 CMTS is now operating with the replacement flash disk and its configuration file is backupMMDDYY.cfg. If the
image currently on the SCM card is not the desired load, then upgrade to the desired load using the normal upgrade
procedure. Refer to the Release Notes for more information.
Compact Flash Disk Partitions
The flash disk contains three partitions: active, update, and system. The flash disk cannot be repartitioned in the field.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
200
Chapter 6: System Control Module (SCM)
The following figure shows the structure of the disk and its partitions.
Figure 51: Flash Disk Partition Structure
Show Commands
Use the following command to display the flash disk capacity on either Slot 19 or 20:
show version detail 19
Sample output:
Chassis Type: C4
Time since the CMTS was last booted: 1 days,
Slot: 19
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
2:58:03 (hr:min:sec)
C4® CMTS Release 8.3 User Guide
201
Chapter 6: System Control Module (SCM)
Type:
Model Number:
Model Version:
Serial Number:
Agile Revision:
Man Deviation:
CPU Type:
CPU Speed:
Bus Speed:
RAM Size:
Flash Size:
Flash Disk Size:
CPLD Versions:
PIC Version:
PIC Serial Number:
PIC Agile Revision:
PIC Man Deviation:
FPGA Versions:
Boot Versions:
Last Boot Version:
Reason Last Booted:
Software Version:
Uptime:
SCM
SCM-02440W
B06
07023CBM0084
AD
0000
IBM 750L (3.2)
396 MHz
99.900 MHz
512 MB
8 MB
488 MB format / 488 MB physical
P302 C600
PICS-00440W/D02
03121RMO0029
sandm
= 06.21.00
boot0
= CMTS_BOOT0_V00.00.85
boot1
= CMTS_BOOT1_V00.09.68
boot2
= CMTS_BOOT1_V00.09.68
CMTS_BOOT1_V00.09.68 [1]
Manual Reset
CMTS_V08.03.00.170
0 days 23:38:19
To display the amount of space remaining on the flash disk, use the following command:
df detail
Sample output:
Device Name
system
update
active
File System
/system
/update
/active
Used Blocks
5044
3792
158048
Free Blocks
96476
480560
255816
Total User Avail
101520
484352
413864
Utilization (%)
4 %
0 %
38 %
clone/system
clone/update
clone/active
/system
/update
/active
5040
1680
158048
96480
482672
255816
101520
484352
413864
4 %
0 %
38 %
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
202
Chapter 6: System Control Module (SCM)
Active Partition
This partition holds the current committed software image. During a reload commit a second image is copied to this
partition. The CMTS always boots from this partition following a normal system reset or power-cycle.
System Image — A system image is a single file containing all CMTS firmware and software components. The system
image is identified by its embedded name (visible through the show image command) which represents the release
number of all components.
Only a committed boot image will remain in the active partition.
Write Memory Command and Backups
A write memory operation first forces the MIB data out to disk, and then initiates a backup operation on the active SCM of
the CMTS. The write memory command causes all files in the following directories of the active SCM to be copied onto
the standby:
/alias
/certs
/cfgfiles (these are not CM configuration files)
/sec
/time
/cmts/sw/config
Once the backup is completed, the backup archive file is copied to the standby side. Once on the standby, it is un-bundled
and the critical files of the active and standby SCM flash disks are synchronized.
As part of a write memory action, critical files in the system partition are backed up to the following directory:
/update/backup/systembkup.arc. The contents of the following /system directories are included in the backup archive:
/alias
/certs
/cfgfiles (these are not CM configuration files)
/sec
/time
/cmts/sw/config
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
203
Chapter 6: System Control Module (SCM)
The following directory is found on the flash disk of a simplex system:
/cmts/sw/mib/data
Update Partition
The update partition contains non-critical, expendable, or dynamic files. This partition is read-write and contains one or
more tran\-sient system images, log files, dump files, and backup files. These can be stored in subdirectories. The CMTS
boots from this partition in response to the reload /update/<imagename>.img command.
System Partition
The system partition is read-write and contains critical configuration information. These files are static — they rarely
change. They include the MIB tables, time-zone data, user and modulation profiles, and encryption keys.
Standby SCM Update Partition for PMDs
The /clone/update/dumps directory allows access to core files (PMDs) on the standby processor.
Disk Check and Recovery
Whenever an SCM initializes, the flash disk is checked for errors. If errors are found, the SCM attempts to recover the disk.
This may result in reformatting the affected partition or the entire disk in a duplex chassis. If the /system partition is
reformatted, it is automatically restored using the backup archive in the /update partition. If the entire disk is found to be
corrupted, the SCM can boot from the redundant SCM and then rebuild its disk.
In a simplex configuration, single partition errors are automatically recovered, but a complete disk corruption can be
corrected only with human intervention.
File System Administration
The commands in this appendix are often associated with system upgrades and disk maintenance procedures. File
transfers to the flash disk usually require connectivity via either TFTP or FTP to a file server, where the files exist. In the
case of an upgrade this would be the server where the new software image exists.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
204
Chapter 6: System Control Module (SCM)
File System Administration CLI Commands
There are several CLI commands that are useful when performing a system backup. These commands and their
functionality are described in the following table.
Table 19.
File System Administration CLI Commands
Use This Command…
To…
cd
change working directory
copy
copy files specified
delete
delete specified files
dir
list files and directories
df
display disk usage
mkdir
make a new directory
pwd
display present working directory
rmdir
remove a specified directory
Reload Commands
The reload command comes in five versions—reload, reload
reload status. Each is explained below.
update, reload retain-patches, reload commit, and show
Table 20. Reload Command Formats
Purpose
CLI Command
Boot the system from system image that resides inreload
the Active
partition.
Reboot the system from the file specified in the Update partition.a reload /update/filename
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
205
Chapter 6: System Control Module (SCM)
Purpose
Reboot the system from the file specified in the Update partition
without first removing existing patch files from the disk.
CLI Command
reload /update/filename retainpatches
1) Copy version of code currently running to the Active partition of
the flash disk.
reload commit
2) Cause HW modules to write transient bootloader and FPGA
versions to hardware.
3) Create backup of system configuration.
Displays the software image information details.
show image
Displays the status during a reload operation if one is in progress.
show reload-status
Note: Committing to a new image and new firmware can take up to 40 minutes to complete. The commit process runs in
the background and does not impact service.
Note: If you replace any modules, run the show version detail command. If any FPGA or bootloader versions are still in
the transient state, execute a reload commit command to ensure that they are written to hardware.
File Transfers
File Transfer Protocols
The procedures in this chapter commonly identify a protocol to use while transferring files. Use Secure FTP (SFTP), File
Transfer Protocol (FTP), or Trivial File Transfer Protocol (TFTP) to transfer files to and from the CMTS.
System files may be uploaded from any partition to a network server using either protocol. Image files may also be
downloaded from a network server to the update partition.
Copy Command Syntax
The copy command is commonly used for file transfers.
Use the following command syntax format to initiate an image upload or download:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
206
Chapter 6: System Control Module (SCM)
copy <source> <destination>
Copy Command Examples
Use the following command examples to initiate an image upload or download. The commands that use FTP assume that
the FTP login and password are properly configured. See the configure ftp-server command for more information.
To copy a backup file from the CMTS to an external FTP server:
copy /system/cfgfiles/backupMMDDYY.cfg ftp://login:password@ftpserverip/backupMMDDYY.cfg
To copy a CMTS image from an external FTP server to the CMTS:
copy ftp://login:password@ftpserverip/CMTS_V08.03.00.40.img /update/CMTS_V08.03.00.40.img
To copy a backup file from the CMTS to an external TFTP server:
copy /system/cfgfiles/backupMMDDYY.cfg tftp://tftpserverip/backupMMDDYY.cfg
To copy a CMTS backup from an external TFTP server to the CMTS:
copy tftp://tftpserverip/backupMMDDYY.cfg /system/cfgfiles/backupMMDDYY.cfg
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
207
Chapter 7
Router Control Module (RCM)
RCM Overview ..................................................................................208
Primary Software Functions .............................................................210
RCM Hardware .................................................................................210
RCM Overview
The Router Control Module (RCM) provides the forwarding capability for the C4/C4c CMTS. Its centralized capabilities
include: layer 3 routing, layer 2 switching, tunneling support, DOCSIS 3 functionality, and the Network Side Interfaces
(NSIs). It is responsible for the control plane and for traffic management in the data plane. IPv4 and IPv6 are both
supported. A duplex C4 CMTS chassis employs dual RCMs for full Control Complex Redundancy (CCR). High-speed
backplane data links interconnect the RCMs with the client cards.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
208
Chapter 7: Router Control Module (RCM)
Figure 52: Router Control Module and Rear Filler Panel
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
209
Chapter 7: Router Control Module (RCM)
Primary Software Functions
The primary software functions of the RCM include:
Forwarding downstream packets to the 16D or XD CAMs and upstream packets received from the 12U or 24U CAMs
Priority-based output scheduling and congestion management using the Quality of Service (QoS) parameter set.
Bandwidth allocation to each client (CAM) card slot for subscriber, management, video, and control traffic
External I/O connectivity and bandwidth via one (1) ten-gigabit Ethernet and ten (10) one-gigabit Ethernet interfaces.
Support for multiple, simultaneous Ethernet interfaces when two RCMs are configured
Hardware support for Access Control Lists (ACLs)
Supporting routing protocols and DHCP
Supporting control plane software.
RCM Hardware
The RCM cards are located in slots 17 and 18 in the C4 CMTS chassis. In the C4c CMTS or simplex mode, slot 17 must be
used.
The RCM is designed to be used without a Physical Interface Card (PIC); therefore, the connectors for all interfaces are on
the front panel. A filler panel is added to the back of the chassis in the corresponding slot. Front-panel LEDs indicate
whether the card is powered, active or standby, and whether the ports and crossover link are connected or are actively
passing traffic. See LED Status Indicators (page 211).
The adaptive link or A-link protocol is used on the ARRIS CMTS midplane. The A-links provide the higher data rates needed
to support the client cards. These cards include:
16D CAM
XD CAM
12U CAM
24U CAM
The A-links provide the upstream and downstream data paths between the RCM and the client cards.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
210
Chapter 7: Router Control Module (RCM)
LED Status Indicators
The following is a table of LED states and the conditions they represent. All of these LEDs are found on the front panel of
the RCM.
Table 21. RCM Status Descriptions
LED
Power
Active
SFP Ports
XFP Ports
Crossover Link Indicator
State of LED
Significance
Solid Green
Power is on
Blinking Green
Power is turned off by software.
Solid Green
Active RCM
Off
Standby RCM
Red
RCM is OOS and initializing
Solid Green
Connectivity established
Amber
Active traffic being passed
Solid Green
Connectivity established
Amber
Active traffic being passed
Solid Green
Link is active
RCM Crossover Connector
If you plan to run in duplex mode (applicable to C4 CMTS only), you must purchase one (1) CMTS Router Control ModuleCrossover Connector (Part Number 722891).
The crossover connection provides the RCM-to-RCM inter-card data transport. These are the important operating
characteristics:
The traffic over the Ethernet interfaces of the two cards functions in an active-active mode, meaning that both cards
simultaneously forward traffic over their respective Ethernet interfaces.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
211
Chapter 7: Router Control Module (RCM)
If there is a problem with the crossover connection, you will lose the standby Ethernet ports even though the card is in
service.
If the standby RCM fails, you will lose the standby Ethernet ports during the time that the standby card is coming back
in service.
Figure 53: RCM Crossover Connector
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
212
Chapter 7: Router Control Module (RCM)
To Install the RCM Crossover Connector
1. First ground yourself properly with an electrostatic discharge (ESD) strap, then install the second RCM.
Figure 54: Installing the RCM Crossover Connector
2. Align the pins on the RCM crossover connector as shown in the figure above.
3. Push in and hand tighten the four supplied captive fasteners. Do not over-tighten. The recommended torque for these
is 5.0 ±0.5 inch-pounds.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
213
Chapter 7: Router Control Module (RCM)
Caution: The crossover connector must be removed before attempting to reseat or remove an RCM card.
SFP and XFP Ethernet Interfaces
The RCM supports the following Ethernet interfaces:
One 10Gbps Ethernet 10G Small Form-factor Pluggable (XFP) optical interface located in port 10
Ten 10/100/1000 Mbps Ethernet Small Form-factor Pluggable (SFP) electrical or optical interfaces located in ports 0
through 9
SFP and XFP ports are Multi-Source Agreement (MSA) compliant
Fiber Optic SFP and XFP Modules
The SFP transceiver is a hot-swappable device that can be plugged into one of the Gigabit Ethernet ports on the front of
the RCM module to link with fiber optic networks. The XFP transceiver module is required for the 10G Ethernet port.
Figure 55: Examples of an Optical XFP, Optical SFP, and Copper SFP
SFP modules come in different forms from different manufacturers. The CMTS does not come with SFP or XFP modules.
Note: Neither SFPs nor XFPs are included with the RCM order; they must be ordered separately.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
214
Chapter 7: Router Control Module (RCM)
Note: The SFP and XFP modules are compliant with the SFP and XFP MSAs, respectively; however, only the approved
1000 Base-TX modules are guaranteed to operate correctly in the 10/100/1000 mode of operation. Contact your ARRIS
Sales or Technical Representative for more information on approved modules.
See the following table for the IEEE specified minimum length limits for the various modules and fiber types.
Table 22. Overview of IEEE SFP and XFP Types and Specifications
Connection Type
Wavelength
Fiber Type
Max.
Distance
SFP GbE Fiber Modules
850nm
62.5/125 multi-mode, 160MHz
62.5/125 multi-mode, 200MHz
50/125 multi-mode, 400MHz
50/125 multi-mode, 500MHz
220m
275m
500m
550m
1000Base-LX10
1310nm
62.5/125 multi-mode, 500MHz
50/125 multi-mode, 400MHz
50/125 multi-mode, 500MHz
9/125 single mode
550m
550m
550m
5km
1000Base-EX
1310nm
9/125 single mode
10km
1000Base-ZX
(not IEEE spec)
1550nm
9/125 single mode
70km
62.5/125 multi-mode, 160MHz
62.5/125 multi-mode, 200MHz
50/125 multi-mode, 400MHz
50/125 multi-mode, 500MHz
50/125 multi-mode, 2000MHz
26m
33m
66m
82m
300m
1000Base-SX
XFP 10GbE Fiber Modules
10GBase-SR
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
850nm
C4® CMTS Release 8.3 User Guide
215
Chapter 7: Router Control Module (RCM)
Connection Type
Wavelength
Fiber Type
Max.
Distance
10GBase-LR
1310nm
9/125 single mode
10km
10GBase-ER
1550nm
9/125 single mode
40km
10GBase-ZR
(not IEEE spec)
1550nm
9/125 single mode
80km
Cat5 Ethernet (or better)
100m
SFP 1000BT Copper Electrical Modules
1000Base-T
Install the SFPs after the RCM is installed. Installation procedures for all SFPs and XFPs are the same. The standard fiber
connector for the SFP and XFP is the LC connector style.
Installing Fiber Optic XFPs or SFPs Into the RCM Ports
Note: Ground yourself properly with an electrostatic discharge (ESD) strap.
CAUTION: Do not remove the plugs from the fiber-optic module port or the rubber caps from the fiber-optic cable until
you are ready to connect the cable.
WARNING: Do not look directly into fiber optic cables or ports. The laser radiation used in these facilities is not visible and
may cause permanent damage, especially to the eye.
1. Open the latch on the module.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
216
Chapter 7: Router Control Module (RCM)
2. Grip the sides of the XFP or SFP with your thumb and forefinger and insert it into the selected RCM port and push
firmly until it seats.
Figure 56: Installing the XFPs and SFPs
CAUTION: Do not install or remove fiber-optic modules with the cables attached. It will damage the housing. Disconnect
all cables before removing or installing an XFP or SFP module.
3. Lock the XFP or SFP into place by moving the latch to the right into the locked position. The latch is properly closed
when access to the connector is not obstructed.
4. Remove the protective caps from the connectors on the fiber-optic cable and save them for future use.
5. Plug the appropriate fiber-optic cable into the connector on the XFP or SFP until it clicks in place.
6. Install Copper SFP Into GigE Ports
To install the Copper SFP option perform the following steps:
1. Ground yourself properly with an electrostatic discharge (ESD) strap.
2. Open the latch on the module.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
217
Chapter 7: Router Control Module (RCM)
3. Grip the sides of the SFP with your thumb and forefinger and insert the copper SFP into the selected RCM port and
push firmly into the port until it seats.
4. Lock the SFP into place by closing the latch in the up or locked position. The latch is properly closed when access to the
connector is not obstructed.
5. Insert the copper Ethernet connector until it clicks in place.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
218
Chapter 8
Downstream Cable Access Modules (DCAMs)
Overview .......................................................................................... 219
16D Cable Access Module (16D CAM) ............................................. 219
XD Cable Access Module (XD CAM) ................................................. 229
Downstream Parameters ................................................................. 242
XD CAM Field Software Upgrade ..................................................... 249
Overview
This chapter provides information on the 16D Cable Access Module (CAM) and the eXtended Downstream Cable Access
Module (XD CAM). The 2Dx12U CAM is not supported by this software release.
The CAMs can be configured in slots 0 through 15, but it is recommended to use the lower-numbered slots for 12U or 24U
CAMs and use higher-numbered slots for the 16D or XD CAMs. Slot 16 is not used.
16D Cable Access Module (16D CAM)
The 16D Cable Access Module (16D CAM) provides downstream channels for as few as one or as many as sixteen different
MAC domains. Each upstream in the MAC domain must be paired with one or more downstream channels of the same
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
219
Chapter 8: Downstream Cable Access Modules (DCAMs)
MAC domain. All of the downstream channels in a MAC domain must be from the same 16D or XD CAM. All of the
upstream channels in a given MAC domain must be from the same 12U or 24U CAM.
The model numbers for the 16D CAM are:
CAM-20016W (Classic 16D CAM)
CAM-40016W (Optimized 16D CAM)
Caution: Optimized 16D CAMs will not work in releases prior to Release 7.4.
Classic Downstream CAMs — name for the original designs of the 16D and XD CAMs.
Optimized Downstream CAMs — has the same functionality and performance (with slightly lower power consumption) as
the Classic Downstream CAM when installed in a CMTS operating Release 7.4 software or later.
Note: Refer to table Downstream CAM Hardware Versions in XD Cable Access Module (XD CAM) (page 229) for the
minimum software for operation of all Downstream CAMs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
220
Chapter 8: Downstream Cable Access Modules (DCAMs)
Figure 57: 16D CAM and Rear Physical Interface Cards (PICs)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
221
Chapter 8: Downstream Cable Access Modules (DCAMs)
Note: Each MAC domain must consist of channels from exactly one 16D CAM or one XD CAM and exactly one 12U or 24U
CAM. In other words, the MAC domain cannot include ports from more than one downstream CAM or from more than one
upstream CAM.
The 16D CAM hardware supports:
Sixteen 40 or 55 Mbps downstream channels (numbered 0-15 within the card)
For supported frequency ranges see Downstream Frequency Range (page 248).
Note: The 16D hardware supports downstream center frequencies up to 999 MHz, but for the best performance it is
advisable to go no higher than 960 MHz. The downstream maximum frequency must be set appropriately using the
following command:
configure cable freq-dsmax
Four RF block upconverters (numbered 0-3). The process of combining multiple carriers digitally and then upconverting
with a single block upconverter is referred to as RF block upconversion, and the group of carriers that is block
upconverted is referred to as an RF block upconverter group. Each RF block upconverter can support up to four
channels simultaneously.
Four downstream physical connectors (numbered 0-3) which are hard-wired to correspond to one RF block
upconverter each.
Primary Software Function
The primary software functions of the 16D CAM include:
Packetization, queueing, and scheduling of all downstream packets
Downstream channel bonding of flows
Creation of DOCSIS downstream SYNC messages
Combining of the digital representation of four single channels into a single wideband channel suitable for
upconversion
Conversion of the wideband digital signal into an analog signal and placement of this at a selected point in the CATV RF
spectrum
Support of a configurable modulation depth (64QAM and 256QAM) per RF block upconverter
Support for interleaver depth selection on a per port, block upconverter, F-connector or channel basis. (This applies to
Annex B only; Annex A has a fixed interleaver.)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
222
Chapter 8: Downstream Cable Access Modules (DCAMs)
Support of independent adjustment of RF power on a per block upconverter basis
Support of the individual muting of channels within an RF block upconverter group to -50dBc
Automatic Gain Control (AGC) is always enabled on the 16D CAM.
Downstream Test Port on 16D CAM Faceplate
The 16D CAM faceplate test port is meant to verify the presence of a downstream signal. It provides a power level that is
approximately 30 dB less than the configured downstream signal strength. This test port is not meant to be used for signal
calibration, detecting signal spurs, or to be used for precise RF quality measurements. When the test port is not in use, a
75 Ohm terminator should be in place.
A single RF test port is located on the 16D CAM front panel. An LED is lit to reflect which of the 4 upconverters is selected.
These four LEDs are labeled D 0-3, D 4-7, D 8-11, and D 12-15.
A push button allows you to choose which of the four RF block upconverter sources you wish to test. As the push button is
pressed, the next RF output port LED is selected and the associated LED is lit. It then cycles back to the first port after the
last port was selected. See the following figure.
Figure 58: 16D CAM Downstream Test Port
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
223
Chapter 8: Downstream Cable Access Modules (DCAMs)
LED Status
The LED status descriptions for the 16D CAM are listed in the following table:
Table 23. 16D CAM Power and Out of Service LED Descriptions
Front LEDs
Out of
Service
Power
Module Status
On
Off
Powered and in normal service state
Flashing
On
Flashing = 1.6 second period. Module power is off: either slot is not provisioned
or module has been disabled.
Persistent Fast
Flashing
On
Fast flashing = 6 times/second. Normal when card is first powered or restored. If
fast flashing persists for more than 2 seconds, there is a serious power problem.
On
On
Powered and out of service.
On
Flashing
Off
Off
Downloading data from SCM, initializing or running diagnostics.
The slot has no power.
Downstream Interleaver Settings
In Annex B, the 16D CAM now supports the following DS interleaver settings (taps, increment): (8,16), (16,8), (32,4), (64,2),
and (128,1). The DS interleaver settings that were added by the DRFI Specification beyond what was required as part of
DOCSIS 2.0 were added specifically to support IPTV applications.
For Annex A, the 16D CAM uses the standard single DS interleaver setting of (12,17) (taps, increment). See also Interleaver
Settings (page 245).
For Annex B, the 16D CAM supports one unique interleaver setting per F-connector on the 16D CAM PIC.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
224
Chapter 8: Downstream Cable Access Modules (DCAMs)
QAM Modulation Order and Port Requirements
The 16D CAM supports:
64QAM and 256QAM operation
A unique setting of 64QAM or 256QAM per F-connector on the 16D CAM PIC.
Each F-connector of the 16D CAM PIC is able to set to 64QAM or 256QAM mode independent of the other Fconnectors. Any change to the modulation changes the modulation of all channels on that F-connector.
Spectrum Windows and Downstream Frequency Spacing
All of the downstream channels assigned to a given F-connector on the 16D PIC must be arranged on an evenly spaced
frequency grid. For example, a 6 MHz grid would be used (in most cases) for an Annex B card. The size of the spectrum
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
225
Chapter 8: Downstream Cable Access Modules (DCAMs)
window is limited to a maximum of 80 MHz by the passband of the analog filters used in the RF upconverters; in the case
of the 16D cards, this is 80 MHz. This is illustrated in the following diagram:
Figure 59: Example of Spectrum Window for Annex B Using a 6 MHz Frequency Grid
The frequency grid for the 16D CAM has a resolution or step size of 125 kHz. This means that the frequency of the first
channel selected per F-connector must be a multiple of 125 kHz within the frequency range for that annex. All other
channels on the same F-connector are offset by an integer multiple of 6 MHz or 8 MHz, all within a range of 80 MHz edgeto-edge.
Note: An 8 MHz grid is permitted for Annex B, but is required for Annex A.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
226
Chapter 8: Downstream Cable Access Modules (DCAMs)
Restrictions
When operating in Annex A, all of the 1-4 16D CAM channels assigned to a given F-connector must be grouped in a
spectrum window of 80 MHz. The center frequencies of Annex A channels must be separated by integer multiples of 8
MHz. There is no requirement that the channels be in the same frequency order as their channel numbers.
Note: The spectrum window is a hardware limitation; the RF circuitry contains a bandpass filter which limits how far apart
the channels on an F-connector may be.
QAM Output Power
The 16D CAM with 16 downstreams will support up to 52 dBmV for four QAM channels per port. If the power is changed
on one channel, it will change the power on all channels on that F-connector.
The CLI will enforce the DRFI maximum power level for the number of included channels on an F-connector. The table
below shows the ranges which will be enforced.
Table 24. 16D CAM Maximum Power Level for Included Channels
Included
Channels
DRFI Required Power
Range (dBmV)
Default Power
(dBmV)
CLI Power Range
(dBmV)
1
52-60
52
44-60
2
48-56
52
44-56
3
46-54
52
44-54
4
44-52
52
44-52
Note: The maximum per-channel power level is determined by the number of channels assigned to a cable MAC on the
same F-connector. The following factors do not determine the per-channel power levels:
the administrative or operational state of the channels
the frequency of the channels (even 0 MHz)
muting the channel.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
227
Chapter 8: Downstream Cable Access Modules (DCAMs)
For example, if the power level is set to 60 dBmV, and if you try to add a second channel to the same F-connector, then the
CLI will allow this second channel to be added to the same F-connector as long as it has not been added to a cable-mac.
But the command to add this second channel to a cable-mac will fail because 60dBmV is not a valid power level for two
channels on the same connector. If the power level for the first channel has been set to 60 dBmV and the second channel
has already been assigned to a cable-mac, then the CLI will reject the command to assign this second channel to the 60
dBmV F-connector.
Other operational notes:
If the power level is changed for one channel, the power level for all other channels associated with the same Fconnector is also changed.
The command to reconfigure the power level fails if the chosen power level is outside of the range shown in the table
above.
16D Physical Interface Cards (PICs)
There are two types of 16D CAM PIC. The normal 16D CAM PIC is equipped with four F-connectors, each labeled for the
appropriate DS channels it carries. Each connector is capable of carrying up to four downstream channels. The 16D CAM
sparing PIC does not have any F-connectors. The chassis back slot of the downstream CAM sparing group leader must be
equipped with a sparing PIC. In a 16D sparing group, the sparing CAM PIC is to the left of the 16D CAM PICs for which it
provides redundancy, as seen from the rear of the chassis.
16D CAM PIC LED Status
Each F-connector of the 16D CAM PIC has an LED next to it. The LED status descriptions for the 16D CAM PIC are listed in
the following table:
Table 25. CAM PIC LED Descriptions
If CAM PIC LED Is…
Then F-Connector Is Supporting…
On (green)
At least one active downstream channel.
Off
No active channels on this connector.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
228
Chapter 8: Downstream Cable Access Modules (DCAMs)
CAM Sparing PIC LED Status
The two types of CAM PICs are equipped with a sparing LED at the bottom of the faceplate. Under normal conditions all
sparing LEDs are off. When a CAM in a sparing group fails, traffic is transferred to its sparing group leader. In this case, the
sparing LEDs of the failed CAM PIC and of the sparing group leader CAM PIC are on.
Note: For sparing to work properly, there must be 16D CAM PICs in all the rear slots of the 16D CAM sparing group even if
one or more front slots of the group are not equipped with CAMs. If, for example, CAM 15 is sparing for the 16D CAMs in
slots 9-14, and front slot 11 is not equipped with a CAM, you must still have a normal 16D PIC in rear slot 11. If slot 11 is
not equipped with a PIC, then the traffic carried by the CAM in slot 9 or 10 cannot transfer to the sparing group leader in
case of a failover because it has no path through the backplane.
XD Cable Access Module (XD CAM)
The XD CAM provides an upgrade path to convert an existing 16D CAM module into an XD CAM supports 32 Annex A or B
DOCSIS 3.0-capable downstreams (DSs).
The model numbers for the XD CAM are:
CAM-20032W (Classic XD CAM)
CAM-40032W (Optimized XD CAM)
The Downstream CAM hardware version shown in the CMTS CLI and SNMP is dependent on whether the CAM is Optimized
or Classic, 16D or XD. The following table lists the hardware version shown in the CLI and SNMP along with the minimum
software for operation for each of the Downstream CAMs.
Table 26. Downstream CAM Hardware Versions
HW Version Shown
in CLI/SNMP
Minimum Software
for Operation
Optimized 16D
CAM
CAM-40016W
Release 7.4
Optimized XD CAM
CAM-40032W
Release 7.4
Product
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
229
Chapter 8: Downstream Cable Access Modules (DCAMs)
Product
HW Version Shown
in CLI/SNMP
Minimum Software
for Operation
Classic 16D CAM
CAM-20016W
Release 7.1
Classic XD CAM
CAM-20032W
Release 7.4 for XD operation
Release 7.1 for 16D operation
Note: The Optimized 16D and XD CAMs will not work in releases prior to Release 7.4. XD CAMs will work in releases prior
to 7.4 but will only configure as a 16D, and the hardware version will appear as a CAM-20016W.
Note: The C4 CMTS does not support both 16D CAMs and XD CAMs operating at the same time. The downstream CAMs in
the chassis should be either all 16D or all XD CAMs.
Types of Downstream CAMs
Classic Downstream CAM — This CAM is available today as a 16D CAM. Field software upgrades are available to convert
16D or Optimized 16D CAMs to XD CAMs.
Optimized Downstream CAM — This module has the same functionality and performance as the Classic Downstream
CAM. Software Release 7.4 or later is required for the Optimized DS CAM.
XD CAM — For both Annex A and Annex B operation, the XD CAM supports up to 32 downstream channels. It can also be
configured to operate as a 16D CAM.
Maximum number of downstreams per Annex:
Annex B
32 downstreams, 6 MHz wide, DOCSIS 3.0
Annex A
32 downstreams, 8 MHz wide, EuroDOCSIS 3.0
Note: Each XD CAM will operate in either Annex B or Annex A mode but a mixed annex mode within an XD CAM is not
supported.
Operational Considerations for the XD CAM
Operators using the XD CAM should be aware of the following:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
230
Chapter 8: Downstream Cable Access Modules (DCAMs)
Beginning with Release 8.1.5 the XD CAM supports 32 channels in both Annex A and Annex B.
The XD CAM is supported by both the C4 and C4c CMTS chassis.
Although the C4/C4c CMTS chassis can support both Annex A and Annex B simultaneously, an individual XD CAM must
be configured for either Annex A or B. It cannot support both annexes at the same time.
Hitless sparing is supported by spare groups up to 8 + 1 in size (eight active XD CAMs plus one spare).
Non-hitless sparing is supported up to 9 + 1, (nine active XD CAMs plus one spare).
Note: For optimal per-CAM throughput, no more than eight (8) active XD CAMs should be provisioned in a C4 CMTS
chassis.
Sparing groups must be homogeneous: they must not mix Annex A and Annex B CAMs or 16D CAMs with XD CAMs.
Only slots 0-15 can be provisioned for the XD CAM; slot 16 is not used.
The XD CAM uses the 16D PIC.
32 channel operation at full line rate is only possible for Annex B due to bandwidth limitations in the system.
Annex A XD CAMs support only one interleaver depth setting, 12. This is in keeping with the EuroDOCSIS specifications.
As stated on see "Downstream Interleaver Settings (page 224), Annex B XD CAMs can support two different interleaver
depth settings, but all the channels on a given RF connector must have the same setting. Changing the setting for one
channel changes it for all of the channels of that RF connector. See also Interleaver Settings (page 245).
The Enhanced Power Mode feature is available only to Annex A XD CAMs. The command to enable [disable] Enhanced
Power is configure cable downstream-enhanced-power [no].
The C4/C4c CMTS permits Annex A channels to be configured with center frequencies from 85-999 MHz.
When operating in Annex A, all of the 1-8 XD CAM channels assigned to a given RF connector must be grouped in a
spectrum window of 80 MHz. The center frequencies of Annex A channels must be separated by 8 MHz or an integral
multiple of 8 MHz.
The step size of the spectrum window is 125 kHz for both Annex A and Annex B.
The channels in the spectrum window must be arranged on an evenly spaced grid. This means that once you pick the
first channel frequency on a multiple of 125 kHz, then all other channels on the same RF connector must have
frequencies separated by exact multiples 8 or 6 MHz, depending on whether Annex A or B is used. Once the first
channel is selected, the remaining channels in the spectrum window can be added using higher or lower frequencies.
See see "Spectrum Window and Frequency Grid for Channels on the Same F-connector (page 237).
The XD CAM supports the 56-bit DES encryption algorithm.
The CLI command configure slot <> type 24DCAM-A results in a slot provisioned for a 32DCAM-A. The CLI
keyword 24DCAM-A is deprecated: it will be accepted but will not appear in the output of this command or in those of
the show commands. It is translated to 32DCAM-A by the CLI.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
231
Chapter 8: Downstream Cable Access Modules (DCAMs)
Annex A channels must be assigned to RF connectors as follows:
Channels
RF Connector
0-7
0
8-11 and 24-27
1
12-19
2
20-23 and 28-31
3
Although this channel numbering scheme is not contiguous, it does not force operators who have been using 24DCAM-A cards
to reconfigure their cabling.
Note: Because the 16D PIC is used for all XD CAMs, the port numbering on the PIC faceplate will be incorrect when the PIC
is used for the XD CAM.
Annex B channels must be assigned to RF connectors as follows:
Channels
RF Connector
0-7
0
8-15
1
16-23
2
24-31
3
An XD CAM can support from 1-16 MAC domains. A single XD CAM can also support one MAC domain containing all 32
of its channels. Each MAC domain contains from 1-32 downstream channels from an XD CAM and one or more
upstream channels from a 12U or 24U CAM.
By default the XD CAM is licensed for 16 channels. An additional license must be purchased to activate the remaining
channels up to a total of 32. In other words, the XD CAM ships with 16 channels enabled and a license can be
purchased to activate the remaining 16 for a total of 32 downstreams.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
232
Chapter 8: Downstream Cable Access Modules (DCAMs)
Figure 60: XD Cable Access Module (CAM) and Rear Physical Interface Cards (PICs)
Port Designation on Faceplate
The XD CAM upgrade kit contains a decal (XD) which should be applied to the front of the faceplate to identify upgraded
CAMs as XD CAMs. However, they do not contain a decal to cover the port designations. Hence, if you are running a 16D
CAM or have upgraded a 16D CAM to an XD CAM, the ports on the faceplate will be shown as D0-3, D4-7, D8-11, and D12-
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
233
Chapter 8: Downstream Cable Access Modules (DCAMs)
15. If you have purchased a new XD CAM Module, it will show the new port designations: Mode 0, Mode 1, Mode 2, and
Mode 3.
Maximum Number of XD CAMs per C4 CMTS
With a single 10 gigabitEthernet interface on an RCM, the C4 CMTS is limited to a maximum of 10 Gbps of traffic upstream
and downstream. A maximum of eight XD CAMs running at full capacity can be supported. More than eight active XD CAMs
is permitted, but because of the 10 Gbps limit of a simplex RCM, they will not reach their maximum combined throughput.
On a duplex C4 CMTS there are two RCMs connected by a cross-over cable. In duplex mode the ports on both RCMs are
active, and it is possible to use both 10 gigE interfaces with the proper routing configuration.
Note: Each MAC domain must consist of channels from exactly one XD CAM or 16D CAM and exactly one 12U or 24U CAM.
In other words, the MAC domain cannot include ports from more than one downstream or from more than one upstream
CAM.
The XD CAM hardware supports:
Up to thirty-two channels numbered 0-31:
If configured for Annex B, the downstream channels use the frequency range of 57 to 999 MHz and carry 40 Mbps per
channel.
If configured for Annex A, the downstream channels use the frequency range of 85 to 999 MHz and carry 55 Mbps per
channel.
Four RF block upconverters (numbered 0-3). The process of combining multiple carriers digitally and then upconverting
with a single block upconverter is referred to as RF block upconversion, and the group of carriers that is block
upconverted is referred to as an RF block upconverter group. Each RF block upconverter can support up to eight
channels simultaneously.
Four downstream physical connectors (numbered 0-3) which are hard-wired to correspond to one RF block
upconverter each. These are located on the PIC.
Note: The XD hardware supports downstream center frequencies up to 999 MHz, but for the best performance it is
advisable to go no higher than 960 MHz. The downstream maximum center frequency must be set appropriately using the
following command:
configure cable freq-ds-max
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
234
Chapter 8: Downstream Cable Access Modules (DCAMs)
Primary Software Function
The primary software functions of the XD CAM include:
Packetization, queueing, and scheduling of all downstream packets
Downstream channel bonding of flows
Creation of DOCSIS downstream SYNC messages
Combining the digital representation of up to eight single channels into a single wideband channel, suitable for
upconversion
Conversion of the wideband digital signal into an analog signal and placement of this at a selected point in the CATV RF
spectrum
Support of a configurable modulation type (64QAM and 256QAM) per RF block upconverter
Support for interleaver depth selection on a per F-connector basis (This applies to Annex B only: Annex A has a fixed
interleaver.)
Support of independent adjustment of RF power on a per block upconverter basis
Support of the individual muting of channels within an RF block upconverter group to -50dBc
Automatic Gain Control (AGC) is always enabled on the XD CAM.
Downstream Test Port on XD CAM Faceplate
The test port on the XD CAM faceplate is meant to verify the presence of a downstream signal. It provides a power level
that is approximately 30 dB less than the configured downstream signal strength. This test port is not meant to be used for
signal calibration, detecting signal spurs, or to be used for precise RF quality measurements. When the test port is not in
use, a 75 Ohm terminator should be in place.
A single RF test port is located on the XD CAM front panel. An LED is lit to reflect which of the four upconverters is
selected. These four LEDs on an XD CAM are labeled Port 0, Port 1, Port 2 and Port 3 (or D 0-3, D 4-7, D 8-11 and D 12-15
on a 16D CAM front panel which has been upgraded to an XD CAM).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
235
Chapter 8: Downstream Cable Access Modules (DCAMs)
A push button allows you to choose which of the four RF block upconverter sources you wish to test. As the push button is
pressed, the next RF output port LED is selected and the associated LED is lit. It then cycles back to the first port after the
last port was selected. See the following figure.
Figure 61: XD CAM Downstream Test Port
Front LED Status
A description of the front LED status on the CAM modules are listed in the following table:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
236
Chapter 8: Downstream Cable Access Modules (DCAMs)
Table 27. XD Cable Access Module LED Descriptions
Front LEDs
Power
Out of
Service
Module Status
On
Off
Powered and in normal service state
Flashing
On
Flashing = 1.6 second period. Module power is off: either slot is not provisioned or
module has been disabled.
Persistent
Fast
Flashing
On
Fast flashing = 6 times/second. Normal when card is first powered or restored. If fast
flashing persists for more than 2 seconds, there is a serious power problem.
On
On
Powered and out of service.
On
Flashing
Downloading data from SCM, initializing or running diagnostics.
Off
Off
The slot has no power.
QAM Modulation Order and Port Requirements
The XD CAM supports:
64QAM and 256QAM operation
A unique setting of 64QAM or 256QAM per F-connector of the 16D CAM PIC.
Each F-connector of the 16D CAM PIC can be set to 64QAM or 256QAM mode independent of the other F-connectors.
Any change to the modulation will change the modulation of all channels on that F-connector.
Spectrum Window and Frequency Grid for Channels on the Same F-connector
Downstream channel frequencies assigned to the same F-connector are required to occupy a limited number of slots of a
frequency grid. For example, a 6 MHz grid would be used (in most cases) for an Annex B card. The size of the spectrum
window (i.e. the total number of slots) is limited by the passband of the analog filters used in the RF upconverters; in the
case of the 16D and XD CAM cards, this is 80 MHz. This is illustrated in the figure below.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
237
Chapter 8: Downstream Cable Access Modules (DCAMs)
The channels in the spectrum window must be arranged on an evenly spaced grid. This means that once you pick the first
channel frequency on a multiple of 125 kHz, then all other channels on the same RF connector must have frequencies
separated by a multiple of 8 or 6 MHz, depending on whether Annex A or B is being used. Once the first channel is
selected, the remaining channels in the window spectrum can be added using higher or lower frequencies.
When the XD CAM is operating in Annex B, up to eight channels can be placed in a spectrum window having 13 slots that
are 6 MHz wide spaced over a total of 78 MHz, or in a spectrum window having 10 slots that are 8 MHz wide and spaced
over a total of 80 MHz. In both cases these Annex B channels are 6 MHz wide.
Figure 62: Example of Spectrum Window with Annex B 6 MHz Frequency Grid
When operating in Annex A, all of the 1-8 XD CAM channels assigned to a given F-connector must be grouped in a
spectrum window of 80 MHz. The center frequencies of Annex A channels must be separated by integer multiples of 8
MHz. There is no requirement that the channels be in the same frequency order as their channel numbers.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
238
Chapter 8: Downstream Cable Access Modules (DCAMs)
Note: The spectrum window for both Annex A and Annex B is based on a hardware limitation: the RF circuitry contains a
bandpass filter which limits how far the channels on a given F-connector can be spread.
QAM Output Power
The XD CAM with 32 downstreams will support up to 52 dBmV for four QAM channels per F-connector and up to 49 dBmV
for eight QAM channels per F-connector. If the power is changed on one channel, it will change the power on all channels
on that F-connector.
The C4/C4c CMTS enforces the DRFI maximum power level for the number of included channels on an F-connector.
The table below shows the ranges which will be enforced.
Table 28. Maximum Power Level for Included Channels
Included
Channels
DRFI Required
Power Range
(dBmV)
Default
Power
(dBmV)
CLI Power Range (dBmV)
1
52-60
49
41-60
2
48-56
49
41-56
3
46-54
49
41-54
4
44-52
49
41-52
5
43-51
49
41-51
6
42-50
49
41-50 (51) (see note below)
7
41-49
49
41-49 (51) (see note below)
8
41-49
49
41-49 (51) (see note below)
Note: The upper limit of 51 dBmV is allowed on Annex A XD CAMs when enhanced
power is enabled.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
239
Chapter 8: Downstream Cable Access Modules (DCAMs)
The maximum per-channel power level is determined by the number of channels assigned to a cable MAC on the same Fconnector. The following factors do not determine the per-channel power levels:
the administrative or operational state of the channels
the frequency of the channels (even 0 MHz)
muting the channel.
For example, if the power level is set to 60 dBmV, and if you try to add a second channel to the same F-connector, then
the CLI will allow this second channel to be added to the same F-connector as long as it has not been added to a cablemac. But the command to add this second channel to a cable-mac will fail because 60dBmV is not a valid power level
for two channels on the same connector. If the power level for the first channel has been set to 60 dBmV and the
second channel has already been assigned to a cable-mac, then the CLI will reject the command to assign this second
channel to the 60 dBmV F-connector.
Other operational notes:
If the power level is changed for one channel, the power level for all other channels associated with the same Fconnector is also changed.
The command to reconfigure the power level fails if the chosen power level is outside of the range shown in the table
above.
Enhanced power for Annex A XD CAMs can be enabled using the CLI command configure cable downstreamenhanced-power.
Note: RF performance may be degraded at the higher output power permitted in the enhanced power mode.
RF Power Monitoring and Recovery
The 16D and XD CAMs monitor the out-of-tolerance power loss on in-service channels. This is accomplished by logging an
event when the actual RF output power deviates either positively or negatively from the provisioned values. A warning is
logged when the monitoring identifies a deviation of +/- 3 dBmV. A recovery, or failover mode, occurs after an RF power
deviation of +/- 6 dBmV.
When recovery is enabled, if the RF power output exceeds the configured recovery value, then the XD CAM automatically
attempts to recover and may go into failover mode.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
240
Chapter 8: Downstream Cable Access Modules (DCAMs)
Operational Considerations
The following items highlight this functionality:
The warning/logging operations is on or enabled by default.
The CAM recovery is off by default.
The monitoring (via logging) and the card recovery can each be turned on or off independently, as well as on a per-slot
basis.
If no spare XD CAM is available when the recovery threshold is exceeded, the card is left in service after attempted
resets.
The CLI command that controls this feature is:
configure operation event <0x0fcad01f> [slot <slot>] recovery <enable|disable> logging
<enable|disable>
Physical Interface Cards (PICs)
The 16D CAM PIC and the 16D CAM PIC (SPARE) are compatible and should be used with the XD CAM.
Note: The four F-Connectors on the 16D CAM PIC are labeled with the downstream channel numbers for the 16D CAM (03, 4-7, 8-11, and 12-15, respectively), so the labeling on the 16D CAM PIC will not be consistent with the XD CAM channel
numbering.
There are two types of 16D CAM PICs. The normal 16D CAM PIC contains four F-connectors, each labeled with the
appropriate DS channels carried. Each connector is capable of carrying up to eight downstream channels with the XD CAM.
The 16D CAM sparing PIC provides sparing for XD CAMs. In an XD CAM sparing group, the sparing 16D CAM PIC is to the
left of the 16D CAM PICs for which it provides redundancy, as seen from the rear of the chassis.
CAM PIC LED Status
Each F-connector of the CAM PIC has an LED next to it. The LED status descriptions for the CAM PIC are listed in the table
below:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
241
Chapter 8: Downstream Cable Access Modules (DCAMs)
Table 29. CAM PIC LED Descriptions
If CAM PIC LED Is…
Then the F-Connector is Supporting…
On (green)
At least one active downstream channel
Off
No active channels on this connector.
CAM Sparing PIC LED Status
The two types of CAM PICs are equipped with a sparing LED at the bottom of the faceplate. Under normal conditions all
sparing LEDs will be off. When a CAM in a sparing group fails, traffic is transferred to its sparing group leader. In this case,
the sparing LEDs of the failed CAM PIC and of the sparing group leader CAM PIC are on.
Note: There must be 16D CAM PICs in all the rear slots of the XD CAM sparing group even if one or more front slots of the
group are not equipped with CAMs. If, for example, CAM 15 is sparing for the XD CAMs in slots 9-14, and front slot 11 is
not equipped with a CAM, you must still have a 16D PIC in rear slot 11. If slot 11 is not equipped with a 16D PIC, then the
traffic carried by the XD CAMs in slot 9 or 10 cannot transfer to the sparing group leader in case of a failover because it has
no path through the backplane.
Downstream Parameters
Annex
The annex setting defines the global annex setting for all the CAMs in the chassis, but it is possible to assign a different
annex to one or more CAMs using the Mixed Annex feature. Changing the global annex affects only new cable-macs on
16D CAMs; the annex for XD CAMs is fixed by the slot type. If you want to change the annex on an existing cable-mac use
How to Change the Local Annex on a 16D CAM (page 243).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
242
Chapter 8: Downstream Cable Access Modules (DCAMs)
Mixed Annex Support
All of the cable-macs on a given CAM must be configured with the same annex. In other words one CAM may be
configured for Annex A and another may be configured for Annex B, but annexes cannot be mixed on the same CAM. If the
cable-macs of a given CAM are configured with different annexes, then this CAM will not go into service.
CAUTION: Changing the annex is service affecting.
If Using Reconfiguration Scripts or Making Multiple RF Parameter Changes
When using provisioning scripts or making extensive changes to downstream or upstream RF parameters or channel
configurations, users should observe the following guidelines:
1. Cable-macs should be shut down before shutting down the up or downstream channels. Shut down each cable-mac
(MAC domain) individually and have the system wait 60 seconds to give the RSM time to process the information. For
example:
configure interface cable-mac 1 shutdown
wait 60
configure interface cable-mac 2 shutdown
wait 60
(Repeat as needed for other cable-macs.)
2. Change the RF parameters or configurations.
3. Restore the up or downstream channels to service before restoring the cable-macs.
4. Restore the cable-macs to service.
How to Change the Local Annex on a 16D CAM
Note: Because the XD CAM slot type determines the annex, this procedure will not work for an XD CAM.
Perform the following steps to change the local annex setting on a MAC domain. If you have multiple mac-domains on
a card, you must repeat steps 2-5 for each mac-domain, before proceeding to steps 6-9:
1. Shut down the CAM(s).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
243
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure slot <x> shutdown
2. Shut down the cable-mac interface.
configure interface cable-mac <int> shutdown
3. Change the annex:
configure interface cable-mac <int> cable annex <A | B>
Note: An improper configuration results in an error message and the annex change is aborted.
4. Change the downstream center frequency if necessary.
configure interface cable-downstream <slot/port> cable frequency <freq>
At this time, a number of values will change and checks will occur. For example, the downstream and upstream
frequency spectrum is checked to insure that there is no overlap in the fiber nodes.
5. Change interleavers for all channels in the cable-mac. Note that changing the interleaver on one channel on an RFconnector changes it for all channels on that connector.
6. Save your changes:
write memory
7. Restore the cable-mac to service.
configure interface cable-mac <int> no shutdown
8. Restore the CAM(s) to service:
configure slot <x> no shutdown
Where x represents the slot number of the CAM. The command must be performed for each provisioned CAM. The CAMs
reset and come back in service with the new annex setting.
9. To display the annex setting use the following command:
show interface cable-mac
Channel Width
The channel width settings for each annex are unchanged for DOCSIS 3.0. The CMTS defaults to Annex B and 6 MHz, just as
it did in previous software releases.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
244
Chapter 8: Downstream Cable Access Modules (DCAMs)
Interleaver Settings
The downstream interleaver helps protect against noise bursts. By interleaving the data, only small pieces of several data
frames are lost as opposed to a larger portion of a single data frame. Reducing the amount of contiguous errors results in a
higher probability that the FEC can correct the losses due to bursts of noise. The more interleaved that the data actually is,
the smaller the amount of data that is lost in any particular data frame; however, increasing the interleaving also increases
the amount of the delay in the transmission of the data.
The table below provides examples of the effects of various interleave depth settings. Taps can be thought of as different
sources of information. The increment determines how much information is taken from each tap; it varies inversely with
the number of taps. The interleaver works with a total of 128 symbols in one group. If there are 128 taps, then each tap
takes one symbol. If there are 16 taps then each one takes 8 symbols. Burst protection values refer to the maximum size in
microseconds of a burst that can be corrected.
Five different versions of the downstream interleaver are available to DOCSIS® CMTS operators. The following table shows
the different interleavers that are available, the length of a noise burst that they can protect against and the delay in the
data transmission. Default = 32 taps.
Table 30. Annex B Downstream Interleavers
64 QAM
Increment
Taps
Burst Protection
(mSec)
256 QAM
Burst Protection
Latency (mSec) (mSec)
Latency (mSec)
8
16
5.9
0.22
4.1
0.15
16
8
12
0.48
8.2
0.33
32
4
24
0.98
16
0.68
64
2
47
2.0
33
1.4
128
1
95
4.0
66
2.8
Note: Burst protection is measured in microseconds; latency is measured in milliseconds.
For the EURO-DOCSIS specification, there is only one downstream interleaver setting that is allowed.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
245
Chapter 8: Downstream Cable Access Modules (DCAMs)
Table 31. Annex A Downstream Interleavers
64 QAM
Taps
Increment
12
17
Burst Protection
(Sec)a
18
256 QAM
Burst Protection
Latency (mSec) (Sec)
Latency (mSec)
0.43
32
14
Note: Burst protection is measured in microseconds; latency is measured in milliseconds.
Max round trip delay
This defines the maximum amount of time in microseconds allowed for round trip delay in microseconds that it would take
a cable modem to send a message, such as a broadcast ranging attempt, to the CMTS and to receive a response. This
parameter is used to determine the amount of time that must be given to a cable modem to transmit a broadcast ranging
message. The parameter is also used to determine the needed Map Ahead Timer for DOCSIS® Map messages. The default
time is 1600 microseconds, which is roughly enough time for a cable modem up to 100 miles from the CMTS to send a
message and receive the response. The CMTS allows values in the range of 200 to 1600.
Automatic Gain Control (AGC)
The 16D and XD CAMs support the power accuracy specification as defined in the CableLabs Downstream RF Interface
Specification. AGC is always enabled on the 16D and XD CAMs.
Modulation
The following are the operational notes and constraints regarding QAM modulation settings:
Changing the modulation of any downstream channel also changes the modulation of all the other channels associated
with the same connector.
The modulation of a channel can be changed whether the channel is in the up or down administrative state.
Default: 256 QAM
If there is an upstream using SCDMA, then all the downstream channels providing supervision to that upstream
channel must all use the same modulation.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
246
Chapter 8: Downstream Cable Access Modules (DCAMs)
CAUTION: Changing the modulation of any channel can be service affecting to all channels associated with the same 16D
or XD CAM connector.
Power
All downstream channels associated with a given RF connector must have the same power setting. If a single channel is
configured to an RF connector, it can be configured for output power in the range of 41-60 dBmV for the XD CAM or 44-60
dBmV for the 16D CAM. If other channels are configured to that connector, the allowed maximum power level decreases
with each additional channel regardless of the administrative states of the added channels. See the table found in QAM
Output Power (page 239).
Assigning a DS Channel Frequency outside the 80MHz Range for Its Connector
1. Choose one of the associated frequencies to be the first one to change to the new frequency outside the 80 MHz
range.
2. Set the admin state of the other associated downstream channels on that RF connector to down.
3. Reassign those admin down DS channels to a frequency of 0 MHz.
4. A 16D channel must be administratively down in order to set the frequency to zero. The 0 Hz frequency acts as an
enabler: it does not violate the 80 MHz constraint.
5. Reassign the only DS channel that is in the admin up state to the desired frequency.
6. Assign new frequencies to the DS channels that you set to the admin down state. The new frequencies must all be
within the 80 MHz edge-to-edge range and must not overlap.
7. Bring up the other channels that are admin down.
The channel frequencies assigned to the channels of the four RF connectors are not required to be in any order. The
channel frequencies associated with RF connector DS2, for example, can be lower than those of DS0 and higher than
those of DS3.
The downstream frequency step size is 125 KHz.
The default downstream frequencyis 0 Hz.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
247
Chapter 8: Downstream Cable Access Modules (DCAMs)
Downstream Frequency Range
The 16D and XD CAMs support the DOCSIS/EuroDOCSIS 3.0 extended frequency range of 85-999 MHz for Annex A and of
57-999 MHz for Annex B.
Note: The 16D hardware supports downstream center frequencies up to 999 MHz, but for the best performance, it is
advisable to go no higher than 960 MHz.
The following command sets the minimum downstream center frequency for all channels within the chassis:
configure cable freq-ds-min {57 | 85 | 91 | 112} [no]
The following command sets the maximum downstream center frequency for all channels within the chassis:
configure cable freq-ds-max {858 | 867 | 999} [no]
Table 32. Downstream Center Frequency Ranges Per Annex
Annex
A
B
Range
Minimum
Maximum
Standard
112
858
Extended
85
999
Standard
91
867
Extended
57
999
The standard values shown in bold in the table above are the defaults.
If the no parameter is included in these commands, it sets the downstream center frequency range to the default values
based on the current annex.
The configure cable freq-ds-min and configure cable freq-ds-max commands do not permit an overlap with the current
upstream frequency range.
To display the downstream center frequency range, use the following command:
show cable global-settings
Sample system output:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
248
Chapter 8: Downstream Cable Access Modules (DCAMs)
Annex:
Downstream Frequency Range:
Upstream Frequency Range:
Allow piggybacking data req on polling US SFs:
Load Balance:
CM registration request Timeout:
Maximum QoS Active Timeout:
Maximum QoS Admitted Timeout:
Concatenation for DOCSIS 1.0 CM:
Fragmentation for DOCSIS 1.0 CM:
Max traffic burst for 1.1 CM:
Peak traffic rate for 1.1 CM:
Percent increase for DS SF rate:
CMs required to detect US lockup:
LO1 leak detect:
Interval to collect utilization data:
Modifying primary DS chan in RCC of Reg-Rsp-Mp:
Send 46.1RefID only in first TCC frag:
Allow CM service group ambiguity override:
Unicast non-primary US channel acquisition:
TFTP Enforce and Dynamic Shared Secret:
Drop Bad BPI Certificates:
annex B
57-999
5-42
Disabled
Enabled
30
0
200
Off
On
128000
0
1
10
Disabled
0
Enabled
False
Disabled
Disabled
Enabled
Disabled
XD CAM Field Software Upgrade
Overview
The C4/C4c CMTSs support an upgraded version of the 16D CAM. It is known as the eXtended Downstream (XD) CAM, and
supports 32 downstreams when configured for Annex A or Annex B. Customers can upgrade existing DOCSIS 3.0 16D CAMs
to XD CAMs in order to support these higher densities. The high density XD CAM allows operators to deploy more
downstream channels per service group and per C4/C4c CMTS.
This document contains the following procedures:
1. SFP and XFP Ethernet Interfaces (page 214)
2. SFP and XFP Ethernet Interfaces (page 214)
3. SFP and XFP Ethernet Interfaces (page 214)
4. SFP and XFP Ethernet Interfaces (page 214)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
249
Chapter 8: Downstream Cable Access Modules (DCAMs)
5. SFP and XFP Ethernet Interfaces (page 214)
The first procedure is simply a precaution. The third and last procedures are the actual upgrades. The second and fourth
procedures listed above are used to create the scripts that you will need to reconfigure (provision) the XD CAMs or the
chassis after upgrading the downstream CAMs. Scripting the provisioning and configuration ahead of time minimizes
subscriber downtime by enabling additional downstreams through the upgrade of the 16D CAMs to XD CAMs.
Operational Concerns
Operators and users of the C4/C4c CMTS should be aware of the following:
Software Release 7.4 or later is required for this upgrade.
An XD license key for each 16D CAM to be upgraded is required to enable XD operation. This key is a text string and is
stored in non-volatile memory on the XD CAM itself; thus it migrates with the XD CAM.
The XD CAMs use the same active and spare Physical Interface Cards (PICs) as the 16D CAMs.
The hardware version of an upgraded Classic CAM will be shown in MIBs and in CLI output as CAM-20032W or as
CAM-40032W for Optimized XD CAMs. This is true whether the upgraded CAM is used as a 16 or 32D downstream
CAM.
If the CMTS is running with Software Release 7.3 or lower, it will support an XD CAM but will recognize and operate it
as a 16D CAM. This chassis will show XD CAMs as hardware version CAM-20016W—the same hardware version as a
16D CAM.
For hitless XD CAM sparing, the C4 CMTS supports a maximum of nine (9) XD CAMs per sparing group (eight active and
one spare).
A chassis running Software Rel. 8.1.5 can support 16D or XD CAMs. If XD CAMs are added to a chassis running Software
Rel. 7.4 or above and using 16D CAMs, they must be configured as 16D CAMs using the configure slot type command.
Note: If the operator attempts to use the saved configuration of the 16D on the XD CAM, then several of the commands in
the script will fail, because the 16D and XD CAMs do not have the same port-to-connector mapping.
Ordering CAMs
Use an ordering code provided by your ARRIS account representative. Each license key provided is stored on the XD CAM
and remains with it.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
250
Chapter 8: Downstream Cable Access Modules (DCAMs)
Note: The license key is related to the serial number of the CAM and cannot be transferred to another CAM.
An upgraded XD CAM has the same warranty as the original 16D CAM. If the 16D CAM is still under warranty, then the
upgraded XD CAM will be under warranty. This upgrade does not extend the existing warranty.
Sample XD CAM Provisioning
Create a Backup Copy of the Running Configuration
Before performing either of the upgrade procedures below, it is recommended that you execute the following commands
in order to preserve a snapshot of your current configuration.
1. Display the show-tech information and log it:
show tech-support
2. Copy the running config and ftp it to a different device:
copy running-config bkup_mmddyy
3. FTP this backup file off the CMTS and to another machine.
Create a Script to Provision XD CAMs
Before upgrading your 16D CAMs in the following procedure after this one (Convert All 16D CAMs in the Chassis to XD
CAMs by Reprovisioning the Downstream Cards Only (page 252)), you will need to create a script or file to be used to
provision the XD CAMs. Here are the basic steps for creating an XD CAM provisioning script. This example uses 32D
CAMs. To create this script you must first perform a copy running-config verbose <filename>. You must then edit this
file to remove the lines that are not related to downstreams or to the downstream CAMs, or are not applicable to the
re-growth procedure. The script you create using this procedure should resemble the see "Sample Script for 32D CAM
Provisioning (page 256).
1. Copy and save the original 16D running-config as 2 separate files:
copy running-config verbose orig_16D.cfg
copy running-config verbose new_32D_prov.cfg
Where orig_16D.cfg is the filename of the original configuration (16D) and new_32D_prov.cfg is the filename of the
new configuration (32D).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
251
Chapter 8: Downstream Cable Access Modules (DCAMs)
2. FTP both files off of the C4/C4c CMTS.
3. Edit the new_32D_prov.cfg file to reflect the desired 32D configuration:
a. Remove configuration lines not related to downstreams or the downstream CAMs
b. Modify the downstream port information to reflect the new 32D DS port-to-connector mapping
c. Add and configure the additional 16 downstreams as appropriate
d. Configure US supervision as appropriate
e. Configure 32D Sparing as appropriate
f. Add commands to this script to enable DSG, static bonding, or other features as necessary to your operation.
4. FTP the new_32D_prov.cfg back to the C4/C4c CMTS.
5. Execute the new_32D_prov.cfg script when called for in the upgrade procedure. In the following procedure this is step
8.
Convert All 16D CAMs in the Chassis to XD CAMs by Reprovisioning the Downstream Cards Only
This procedure assumes that you have ordered upgrade kits and have received the license keys for all 16D CAMs to be
upgraded, and that you have upgraded the chassis to Release 7.4 or later. It also assumes that all 16D CAMs will be
upgraded and that you have created a script for provisioning the upgraded CAMs as in the previous procedure.
1. Assign license keys to all 16D CAMs:
configure slot <slot_number> change-type 16DCAM to XDCAM key <16 hex digit key>
CAUTION: You must perform step 2 and wait for it to successfully complete before proceeding to the step 3. For more
information, see AFB-12-0203.
2. Confirm the license key installation:
show linecard status
Use the system response to verify that the upgraded Classic CAMs have model number CAM-20032W (or CAM40032W for Optimized XD CAMs). This number is displayed for both Annex A and Annex B XD CAMs. The output below
is an excerpt from an example:
11
12
CAM (16D, 0U)
CAM (16D, 0U)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Up
Up
IS
IS
Simplex
Simplex
10063CSD0082 CAM-20032W/G04
10033CSD0119 CAM-20032W/G04
DMM/DMM
DMM/DMM
C4® CMTS Release 8.3 User Guide
252
Chapter 8: Downstream Cable Access Modules (DCAMs)
13
14
CAM (16D, 0U)
CAM (16D, 0U)
Up
Up
IS
IS
Active
Standby
10043CSD0155 CAM-20032W/G04
08423CSD0060 CAM-20032W/G02
DMM/DMM
DMM/DMM
3. Shutdown all cable-macs associated with the 16D CAMs:
configure interface cable-mac <cable-mac> shutdown
4. Shutdown all 16D CAMs using this command for each downstream CAM:
configure slot <slot> shutdown
5. Shut down all of the 12U or 24U CAMs using the following command:
configure slot <slot> shutdown
Where <slot> is the slot number of each slot populated by a 12U or 24U CAM.
6. Remove the downstream CAM sparing group:
configure slot 15 spare-group no
Where slot 15 is assumed to be the spare group leader.
7. Deprovision all 16D CAM slots using this command for each downstream CAM:
configure slot <slot> no
8. Execute the provisioning file you created in the previous procedure (Create a Script to Provision XD CAMs (page 251)):
exc file new_32D_prov.cfg
9. Bring all the 12U or 24U CAMs back into service:
configure slot <slot> no shutdown
Where <slot> is the slot number of each slot populated by a 12U or 24U CAM.
10. Save configuration changes and write to non-volatile memory:
write memory
11. Confirm that all desired cards and ports are in service.
12. The upgrade kits contain decals to identify the upgraded CAMs as XD CAMs; they are applied as in the figure below
titled Upgraded CAMs with XD Decals. Before applying the decal, check to see if this part of the faceplate of the
upgraded CAM is clean. If necessary, clean with an alcohol wipe and allow to dry. Press the decal firmly in place to
ensure it adheres properly.
Create a Script to Reconfigure the Chassis after Upgrading the CAMs
Here are the basic steps for creating a script to reconfigure the chassis after upgrading all 16D CAMs to XD CAMs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
253
Chapter 8: Downstream Cable Access Modules (DCAMs)
1. Copy and save original 16D running-config as 2 separate files
copy running-config verbose orig_16D.cfg
copy running-config verbose 32D_chassis.cfg
Where orig_16D.cfg is the filename of the original configuration (16D) and 32D_chassis.cfg is the filename of the new
configuration.
2. FTP both files off of the C4/C4c CMTS.
3. Edit the 32D_chassis.cfg file to reflect the desired 32D configuration for your chassis:
a. Modify the downstream port information to reflect the new 32D DS port-to-connector mapping
b. Add and configure the additional 16 downstreams per CAM
c. Configure US supervision as appropriate
d. Configure 32D Sparing as appropriate
e. Add commands to this script to enable DSG, static bonding, or other features as necessary to your operation.
4. FTP the 32D_chassis.cfg script back to the C4/C4c CMTS.
5. Execute 32D_chassis.cfg script when called for in the upgrade procedure. In the following procedure this is step 6.
Upgrading All 16D CAMs in the Chassis to XD CAMs by Reprovisioning the Entire Chassis
This procedure assumes that you have ordered the upgrade kits and have received your XD CAM license keys for all the
16D CAMs in the chassis. It also assumes that you have prepared a complete running-config file that will redefine this
chassis for use with XD CAMs. For this procedure you will need serial port access.
1. Upgrade the C4 or C4c CMTS to the software release.
2. Assign license keys to all 16D CAMs:
configure slot <slot> change-type 16DCAM to XDCAM key <16 hex digit key>
CAUTION: You must perform step 2 and wait for it to successfully complete before proceeding to the step 3. For more
information, see AFB-12-0203.
3. Confirm the license key installation:
show linecard status
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
254
Chapter 8: Downstream Cable Access Modules (DCAMs)
Use the system response to verify that the upgraded Classic CAM has model number CAM-20032W (or CAM-40032W
for Optimized XD CAMs). This number is displayed for both Annex A and Annex B XD CAMs. The output below is an
example:
11
12
13
14
15
CAM
CAM
CAM
CAM
CAM
(16D,
(16D,
(16D,
(16D,
(16D,
0U)
0U)
0U)
0U)
0U)
Up
Up
Up
Up
Up
IS
IS
IS
IS
IS
Active
Active
Active
Active
Active
08413CSD0003
08413CSD0004
08413CSD0005
08413CSD0006
08413CSD0007
CAM-20032W/G02
CAM-20032W/G02
CAM-20032W/G02
CAM-20032W/G02
CAM-20032W/G02
DMM/DMM
DMM/DMM
DMM/DMM
DMM/DMM
DMM/DMM
4. Restore the default chassis configuration:
erase nvram
5. Reset the system:
configure reset system
In a duplex chassis wait for the spare Control Complex to come into service before executing the next step.
6. Apply the new running configuration that you created in the previous procedure.
exc file 32D_chassis.cfg
7. Save configuration changes and write to non-volatile memory:
write memory
8. Confirm that all desired cards and ports are in service.
9. The upgrade kits contain decals to identify the upgraded CAMs as XD CAMs; they are applied as in the following figure.
Before applying the decal, check to see if this part of the faceplate of the upgraded CAM is clean. If necessary, clean
with an alcohol wipe and allow to dry. Press the decal firmly in place to ensure it adheres properly.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
255
Chapter 8: Downstream Cable Access Modules (DCAMs)
Figure 63: Upgraded CAMs with XD Decals
Sample Script for 32D CAM Provisioning
The following script is an example of the provisioning commands needed to activate a 32D CAM after it has been upgraded
to an XD CAM. In this example slot 14 is used for the active CAM. Slot 15 is also an XD CAM and is the spare group leader.
This example presumes Annex B is being used: the downstream channels are 6 MHz wide.
# Change card types from 16D CAM to 32D CAM (Annex B.)
configure slot 14 type 32DCAM-B name "CAM (32D)"
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
256
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure slot 15 type 32DCAM-B name "CAM (32D)"
# CAM sparing information left unchanged
configure slot 15 spare-group 15 manual
configure slot 14 spare-group 15
# Configure downstreams into appropriate cable-mac
# - The original 16D CAM configuration had 4 DS per cable-mac
# - This example for new 32D CAM configuration has 8 DS per cable-mac
configure interface cable-downstream 14/0 cable cable-mac 1
configure interface cable-downstream 14/0 cable channel-id 1
configure interface cable-downstream 14/0 cable frequency 525000000
configure interface cable-downstream 14/0 no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/1
14/1
14/1
14/1
cable cable-mac 1
cable channel-id 2
cable frequency 531000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/2
14/2
14/2
14/2
cable cable-mac 1
cable channel-id 3
cable frequency 537000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/3
14/3
14/3
14/3
cable cable-mac 1
cable channel-id 4
cable frequency 543000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/4
14/4
14/4
14/4
cable cable-mac 1
cable channel-id 5
cable frequency 549000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/5
14/5
14/5
14/5
cable cable-mac 1
cable channel-id 6
cable frequency 555000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/6
14/6
14/6
14/6
cable cable-mac 1
cable channel-id 7
cable frequency 561000000
no shutdown
configure interface cable-downstream 14/7 cable cable-mac 1
configure interface cable-downstream 14/7 cable channel-id 8
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
257
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure interface cable-downstream 14/7 cable frequency 567000000
configure interface cable-downstream 14/7 no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/8
14/8
14/8
14/8
cable cable-mac 2
cable channel-id 1
cable frequency 525000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/9
14/9
14/9
14/9
cable cable-mac 2
cable channel-id 2
cable frequency 531000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/10
14/10
14/10
14/10
cable cable-mac 2
cable channel-id 3
cable frequency 537000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/11
14/11
14/11
14/11
cable cable-mac 2
cable channel-id 4
cable frequency 543000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/12
14/12
14/12
14/12
cable cable-mac 2
cable channel-id 5
cable frequency 549000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/13
14/13
14/13
14/13
cable cable-mac 2
cable channel-id 6
cable frequency 555000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/14
14/14
14/14
14/14
cable cable-mac 2
cable channel-id 7
cable frequency 561000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/15
14/15
14/15
14/15
cable cable-mac 2
cable channel-id 8
cable frequency 567000000
no shutdown
# Add DS information for the additional 16 downstreams
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
258
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/16
14/16
14/16
14/16
cable cable-mac 3
cable channel-id 1
cable frequency 525000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/17
14/17
14/17
14/17
cable cable-mac 3
cable channel-id 2
cable frequency 531000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/18
14/18
14/18
14/18
cable cable-mac 3
cable channel-id 3
cable frequency 537000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/19
14/19
14/19
14/19
cable cable-mac 3
cable channel-id 4
cable frequency 543000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/20
14/20
14/20
14/20
cable cable-mac 3
cable channel-id 5
cable frequency 549000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/21
14/21
14/21
14/21
cable cable-mac 3
cable channel-id 6
cable frequency 555000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/22
14/22
14/22
14/22
cable cable-mac 3
cable channel-id 7
cable frequency 561000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/23
14/23
14/23
14/23
cable cable-mac 3
cable channel-id 8
cable frequency 567000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/24
14/24
14/24
14/24
cable cable-mac 4
cable channel-id 1
cable frequency 525000000
no shutdown
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
259
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/25
14/25
14/25
14/25
cable cable-mac 4
cable channel-id 2
cable frequency 531000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/26
14/26
14/26
14/26
cable cable-mac 4
cable channel-id 3
cable frequency 537000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/27
14/27
14/27
14/27
cable cable-mac 4
cable channel-id 4
cable frequency 543000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/28
14/28
14/28
14/28
cable cable-mac 4
cable channel-id 5
cable frequency 549000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/29
14/29
14/29
14/29
cable cable-mac 4
cable channel-id 6
cable frequency 555000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/30
14/30
14/30
14/30
cable cable-mac 4
cable channel-id 7
cable frequency 561000000
no shutdown
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/31
14/31
14/31
14/31
cable cable-mac 4
cable channel-id 8
cable frequency 567000000
no shutdown
# Configure upstream cable supervision
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
configure interface cable-upstream 1/0
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
as appropriate
cable supervision
cable supervision
cable supervision
cable supervision
cable supervision
cable supervision
cable supervision
cable supervision
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
C4® CMTS Release 8.3 User Guide
260
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/1
1/1
1/1
1/1
1/1
1/1
1/1
1/1
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/2
1/2
1/2
1/2
1/2
1/2
1/2
1/2
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/3
1/3
1/3
1/3
1/3
1/3
1/3
1/3
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/4
1/4
1/4
1/4
1/4
1/4
1/4
1/4
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/8
14/9
14/10
14/11
14/12
14/13
14/14
14/15
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/5
1/5
1/5
1/5
1/5
1/5
1/5
1/5
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/8
14/9
14/10
14/11
14/12
14/13
14/14
14/15
configure interface cable-upstream 1/6 cable supervision 14/8
configure interface cable-upstream 1/6 cable supervision 14/9
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
261
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/6
1/6
1/6
1/6
1/6
1/6
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
14/10
14/11
14/12
14/13
14/14
14/15
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/7
1/7
1/7
1/7
1/7
1/7
1/7
1/7
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/8
14/9
14/10
14/11
14/12
14/13
14/14
14/15
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/8
1/8
1/8
1/8
1/8
1/8
1/8
1/8
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/16
14/17
14/18
14/19
14/20
14/21
14/22
14/23
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/9 cable supervision 14/16
1/9 cable supervision 14/17
1/9 cable supervision 14/18
1/9 cable supervision 14/19
1/9 cable supervision 14/20
1/9 cable supervision 14/21
1/9 cable supervision 14/22
1/9 cable supervision 14/23
1/10 cable supervision 14/16
1/10 cable supervision 14/17
1/10 cable supervision 14/18
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/10
1/10
1/10
1/10
1/10
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
14/19
14/20
14/21
14/22
14/23
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/11
1/11
1/11
1/11
cable
cable
cable
cable
supervision
supervision
supervision
supervision
14/16
14/17
14/18
14/19
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
262
Chapter 8: Downstream Cable Access Modules (DCAMs)
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/11
1/11
1/11
1/11
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
2/0
2/0
2/0
2/0
2/0
2/0
2/0
2/0
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/24
14/25
14/26
14/27
14/28
14/29
14/30
14/31
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
2/1
2/1
2/1
2/1
2/1
2/1
2/1
2/1
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/24
14/25
14/26
14/27
14/28
14/29
14/30
14/31
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
2/2
2/2
2/2
2/2
2/2
2/2
2/2
2/2
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/24
14/25
14/26
14/27
14/28
14/29
14/30
14/31
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
2/3
2/3
2/3
2/3
2/3
2/3
2/3
2/3
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/24
14/25
14/26
14/27
14/28
14/29
14/30
14/31
# Re-enable DS cable-macs
configure interface cable-mac
configure interface cable-mac
configure interface cable-mac
configure interface cable-mac
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1
2
3
4
no
no
no
no
cable
cable
cable
cable
supervision
supervision
supervision
supervision
14/20
14/21
14/22
14/23
shutdown
shutdown
shutdown
shutdown
C4® CMTS Release 8.3 User Guide
263
Chapter 8: Downstream Cable Access Modules (DCAMs)
Configuring Cable Fiber Nodes for the XD CAM
The mapping of ports to F-connectors is different for Annex A and for Annex B. Choose the correct set of commands below.
Annex A
# Configure cable fiber-nodes as appropriate (based on 32D CAM downstream port-to-connector mapping
for Annex A)
configure cable fiber-node "1" cable-downstream 14/0 14/1 14/2 14/3 14/4 14/5 14/6 14/7
configure cable fiber-node "2" cable-downstream 14/8 14/9 14/10 14/11 14/24 14/25 14/26 14/27
configure cable fiber-node "3" cable-downstream 14/12 14/13 14/14 14/15 14/16 14/17 14/18 14/19
configure cable fiber-node "4" cable-downstream 14/20 14/21 14/22 14/23 14/28 14/29 14/30 14/31
Annex B
# Configure cable fiber-nodes as appropriate (based on 32D CAM downstream port-to-connector mapping
for Annex B)
configure cable fiber-node "1" cable-downstream 14/0 14/1 14/2 14/3 14/4 14/5 14/6 14/7
configure cable fiber-node "2" cable-downstream 14/8 14/9 14/10 14/11 14/12 14/13 14/14 14/15
configure cable fiber-node "3" cable-downstream 14/16 14/17 14/18 14/19 14/20 14/21 14/22 14/23
configure cable fiber-node "4" cable-downstream 14/24 14/25 14/26 14/27 14/28 14/29 14/30 14/31
# Restore the 32D CAM slots
configure slot 14 no shutdown
configure slot 15 no shutdown
Annex A Mixed Modulation per F-connector
This feature is intended for certain operators who because of noise in the physical plant cannot always use 256-QAM and
who because of space or fiscal concerns are reluctant to add more XD CAMs or CMTSs in their headends. This feature gives
such customers greater flexibility.
Restrictions and Clarifications
MSOs and operators should be aware of the following aspects of this feature:
This feature applies only to the XD-CAM.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
264
Chapter 8: Downstream Cable Access Modules (DCAMs)
This feature is supported only by Annex A; it cannot be used by Annex B customers. This is because in Annex B 64-QAM
and 256-QAM run at different symbol rates. The XD-CAM cannot generate different symbol rates for different channels
on the same port.
Mixed modulation is not enabled or disabled: it is configured on a per-port basis.
A port enters mixed modulation mode when a modulation type is configured for an unused channel that differs
from the modulation used by the channels that are already configured.
If the last remaining mixed modulation channel is unconfigured or removed from the cable-mac, then this port is
no longer in mixed modulation mode.
There are four F-connectors (ports) on the XD-CAM. The following restrictions apply when mixed modulation is used on
a given connector (port):
From 1-4 DS channels can be 64-QAM and 1-4 can be 256-QAM
The lowest 4 numbered channels on a connector must all use the same modulation; the highest 4 numbered
channels on a connector must all use the same modulation.
On a 32D XD-CAM in Annex A the channel numbering is shown in the table below:
Table 33. Channel Numbering per Connector on the Annex A XD CAM
Connector
Lower Four Channels
Upper Four Channels
0
0-3
4-7
1
8-11
24-27
2
12-15
16-19
3
20-23
28-31
This feature causes no frequency agility restrictions: any channel of either modulation type may be assigned to any
available 8 MHz slot in the port’s frequency window.
Impact on RF Power Levels
Operators using this feature should be aware that this feature affects RF power levels as follows:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
265
Chapter 8: Downstream Cable Access Modules (DCAMs)
This feature ensures that on a mixed mode port the 64-QAM channels operate at an RF power level that is 6 dB lower
than that of the 256-QAM channels on the same port.
When a port enters mixed modulation mode, the CMTS issues a notice to the user that 64-QAM channels are operating
at 6 dB less than the stated level.
If a port having only 64-QAM channels becomes a mixed modulation port by the addition of a 256-QAM channel,
whether that channel is added to the existing channels or is a 64-QAM channel reconfigured to be a 256-QAM channel,
then the RF power level of the existing 64-QAM channels is unchanged but the RF power level of the newly added 256QAM channels is that of the 64-QAM channels plus 6 dB.
If a port having only 256-QAM channels is converted to mixed modulation mode by adding a new 64-QAM channel or
by converting an existing channel to 64-QAM, then the RF power level of the existing 256-QAM channels on that port
remains unchanged and the RF power level of the 64-QAM channel(s) is 6 dB less than that of the 256-QAM channels.
If a port ceases to be in mixed modulation mode and all the remaining channels are using 64-QAM modulation, then
the power level of these 64-QAM channels does not change.
If a port ceases to be in mixed modulation mode and all remaining channels are using 256-QAM modulation, then the
power level of these channels does not change.
This feature does not violate the power level requirements of the DRFI Spec, which states that the highest channel
power on a port is used as the reference level against which all parameters are specified.
NOTE: power levels measured by the C4 CMTS are specified to be within 2 dB of the stated level.
Also, there are no new or modified CLI configure or show commands for this feature (Annex A Mixed Modulation per Fconnector).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
266
Chapter 9
Upstream Cable Access Modules (UCAMs)
Overview .......................................................................................... 268
12U Cable Access Module (12U CAM) ............................................. 268
Basic Command Set for Bringing Up a 12U CAM ............................. 274
24U Cable Access Module (24U CAM) ............................................. 277
Rules and Restrictions for 12U/24U CAM Configuration ................. 281
24U CAM Upstream Power Level Groups ........................................ 282
Basic Command Set for Bringing Up a 24U CAM ............................. 286
Measuring SNR in the 12U/24U CAM .............................................. 289
Modulation Profiles .......................................................................... 292
Adjusting Channel Settings in Response to Increased CM
Scaling .............................................................................................. 298
Explanation of Upstream Parameters .............................................. 299
Modulation Profiles: Default and User-defined ............................... 309
Optimizing a Modulation Profile ...................................................... 311
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
267
Chapter 9: Upstream Cable Access Modules (UCAMs)
Overview
This section provides guidelines and procedures specific to the 12U and 24U Cable Access Module (UCAMs).
It also provides basic examples of slot equipage and CAM configuration, as well as examples of procedures for migrating to
denser configurations.
CAMs can be configured in slots 0 through 15, but it is recommended to use the lower-numbered slots for 12U or 24U
CAMs and use higher-numbered slots for the 16D or XD CAMs. Slot 16 is not used.
Guidelines
The following list of items will not be supported in Release 8.0:
2Dx12U CAM
QAM 128
Trellis Code Modulation (TCM)
Multiple logical channels
Channel widths of 200,000, 400,000, and 800,000 Hz.
Note: The terms upstream (US) port, upstream (US) channel, and upstream (US) receiver may be used synonymously in
this document.
12U Cable Access Module (12U CAM)
The 12U CAM provides full DOCSIS 2.0 functionality and supports the following:
Eight upstream physical connectors (numbered 0-7)
Up to twelve 02.56-30.72 Mbps physical upstream channels (numbered 0-11).
The supported channel types are: SCDMA, TDMA, ATDMA, and TDMA & ATDMA.
Range of upstream frequencies configurable for North America, Japan, or Europe:
5-42 MHz (DOCSIS)
5-55 MHz (Japan)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
268
Chapter 9: Upstream Cable Access Modules (UCAMs)
5-65 MHz (EuroDOCSIS)
Extended frequency range to 85 MHz is supported for all three options, depending on modem capability
Note: Extended Upstream frequency ranges are available to modems that support the extended frequencies. The
maximum upstream frequency can be set independent of the Annex or region of operation. Refer to see "Notes on DOCSIS
3.0 Upstream Frequency Range (page 308) for more information on changing the maximum allowable center frequencies.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
269
Chapter 9: Upstream Cable Access Modules (UCAMs)
Figure 64: 12U Cable Access Module (CAM) and the Three Types of Upstream Physical Interface Cards (PICs)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
270
Chapter 9: Upstream Cable Access Modules (UCAMs)
Primary Software Function
The primary software function on the 12U CAM includes:
CM Ranging and Registration
MAC Address Learning
DOCSIS functions: Packet Classification, Service Flows, Dynamic Services (DSx), BPI+, CM Upstream Bandwidth
Scheduling (MAPs), Payload Header Suppression (PHS), Packet defragmentation, packet de-concatenation, and counts
collection
Upstream Policing
Operations, Administration, Maintenance & Provisioning (OAM&P) including initialization and fault recovery code
PacketCable DSx processing.
LED Status
The LED status descriptions for the 12U CAM are listed in the table below:
Table 34. 12U CAM LED Descriptions
Front LEDs
Power
Out of Service
Module Status
On
Off
Powered and in normal service state.
Flashing
On
Flashing = 1.6 second period. Module power is off: either slot is not provisioned or
module has been disabled.
Persistent
Fast Flashing
On
Fast flashing = 6 times/second. Normal when card is first powered or restored. If fast
flashing persists for more than 2 seconds, there is a serious power problem.
On
On
Powered and out of service.
On
Flashing
Downloading data from SCM, initializing or running diagnostics.
Off
Off
The slot has no power.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
271
Chapter 9: Upstream Cable Access Modules (UCAMs)
Upstream Receive Power Levels
Upstream channels connected to a single physical connector may vary in channel width and power levels as long as the
variance falls within a user-configured power level group. The tables below describe the three power level groups. All of
the power levels for all of the channels connected to a single physical connector must fall within the same table.
Table 35. US Receiver Power Level Group 1
1.6 MHz
3.2 MHz
6.4 MHz
-13
-10
-7
-12
-9
-6
-11
-9
-5
-10
-8
-4
-9
-7
-3
-8
-6
-2
Note: All upstream Rx (receive) values are measured in dBmV. Power after attenuation may vary slightly from one CAM to
another. Power Level Group 1 supports a total input power of 29 dBmV.
Table 36. US Receiver Power Level Group 2
1.6 MHz
3.2 MHz
6.4 MHz
-7
-4
-1
-6
-3
0
-5
-2
1
-4
-1
2
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
272
Chapter 9: Upstream Cable Access Modules (UCAMs)
1.6 MHz
3.2 MHz
6.4 MHz
-3
0
3
-2
1
4
-1
2
5
0
3
6
1
4
7
2
5
8
3
6
9
4
7
10
5
8
11
6
9
12
7
10
13
8
11
14
Table 37. US Receiver Power Level Group 3
1.6 MHz
3.2 MHz
6.4 MHz
9
12
15
10
13
16
11
14
17
12
15
18
13
16
19
14
17
20
15
18
21
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
273
Chapter 9: Upstream Cable Access Modules (UCAMs)
1.6 MHz
3.2 MHz
6.4 MHz
16
19
22
17
20
23
18
21
24
19
22
25
20
23
26
21
24
27
22
25
28
23
26
29
Basic Command Set for Bringing Up a 12U CAM
The set of commands provided in the table below is the bare minimum for bring up a 12U CAM in a given slot. The values
chosen for these commands are meant to be examples. Actual values will vary.
Table 38. Example of Basic Command Sequence for Configuring a 12U in Slot 3
Purpose
CLI Command
Configure the Upstream Parameters
Provision slot 3 as a 12U slot.
configure slot 3 type 12UCAM
Restore 12U in slot 3.
configure slot 3 no shutdown
Assign MAC domain
configure interface cable-mac 1
Restore cable-mac 1
configure interface cable-mac 1 no shutdown
Assign a channel to cable-mac 1
configure interface cable-upstream 3/0 cable
cable-mac 1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
274
Chapter 9: Upstream Cable Access Modules (UCAMs)
Purpose
CLI Command
Configure the Upstream Frequencies and Connectors
Assign upstream channel 0 of CAM 3, to connector 0.
configure interface cable-upstream 3/0 cable
connector 0
Configure upstream channel 0 of CAM 3, to use frequency 12
MHz.
configure interface cable-upstream 3/0 cable
frequency 12000000
Specify that DS channel 14/0 carries the supervision for
channel 3/0.
configure interface cable-upstream 3/0 cable
supervision 14/0
Put CAM in Service
Restore upstream channel 0 of CAM 3 to service.
configure interface cable-upstream 3/0 no
shutdown
Restore the logical channel to service.
configure interface cable-upstream 3/0.0 no
shutdown
Confirm channel settings for slot 3.
show interface cable-upstream 3
To view the channel settings resulting from configuring the 12U CAM (note that this example shows that a downstream
was previously configured), enter:
show interface cable-upstream 3/0
Upstream Port 3/0
------------Port state:
Connector:
Cable-Mac:
Downstream Supervision Ports:
Frequency (Hz):
Channel width (Hz):
Equalizer Coefficient State:
Power (dBmV):
Max Power Adj Per Range Resp (1/4 dBmV):
Ranging Power Thresh For Success (1/4 dBmV):
Load Balance Group Id:
Max Allowable Normal Voice BW (%):
Reserved Normal Voice BW (%):
Max Allowable Emergency Voice BW (%):
Reserved Emergency Voice BW (%):
Max Allowed Total (Emergency + Normal) (%):
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
IS
0
1
14/0
12000000
3200000
off
0
24
24
16779264
50
0
70
0
70
C4® CMTS Release 8.3 User Guide
275
Chapter 9: Upstream Cable Access Modules (UCAMs)
Ingress Cancellation Interval:
Ingress Cancellation Size:
Map Size (800 microsecond ticks):
0
0
1
Logical Channel:
0
1
------------------------------------------------------------Channel State
IS
OOS
Channel-ID:
1
25
Channel Type:
tdma
tdma
Modulation profile id:
2
2
Ranging backoff range:
2 - 7
2 - 7
Data backoff range:
2 - 8
2 - 8
Slot Size (6.25 microsecond ticks):
2
2
SCDMA active codes:
SCDMA codes per slot:
SCDMA frame size:
SCDMA hopping seed:
Spectrum Group ID:
Spectrum Group State:
Attribute Mask:
0x00000000 0x00000000
Number of Equalizer Taps:
24
24
The table below shows the commands to restore default values for a number of upstream and downstream parameters.
These are the settings which most users will choose for basic configuration. In each command the default values can be
replaced as needed.
Table 39. Accepting Default Parameters for Cable Upstream Channels of a 12U CAM
Purpose
CLI Command
Accept default modulation profile. Default = 2.
configure interface cable-upstream <slot/port> cable
modulation-profile 2
Accept default channel width. Default = 3.2 MHz.
configure interface cable-upstream <slot/port> cable
channel-width 3200000
Accept default upstream power level. Default = 0.
Power range varies with channel width selection.
Range = -4 to 3 dBmV if channel width is 3.2 MHz for
upstream receive power levels).
configure interface cable-upstream <slot/port> cable
power-level 0
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
276
Chapter 9: Upstream Cable Access Modules (UCAMs)
24U Cable Access Module (24U CAM)
The 24U CAM provides full DOCSIS 3.0 functionality and supports the following:
Uses of the same PIC as the 2D12U and 12U CAM with eight upstream RF physical connectors (numbered 0-7) giving an
average of three upstreams per connector.
Up to twenty-four 2.56-30.72 Mbps physical upstream channels (numbered 0-23).
The supported channel types are: SCDMA, TDMA, ATDMA, and TDMA & ATDMA.
Range of upstream frequencies configurable for North America, Japan, or Europe:
5-42 MHz (DOCSIS)
5-55 MHz (Japan)
5-65 MHz (EuroDOCSIS)
Extended frequency range to 85 MHz is supported for all three options, depending on modem capability.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
277
Chapter 9: Upstream Cable Access Modules (UCAMs)
Note: Extended Upstream frequency ranges are available to modems that support the extended frequencies. The
maximum upstream frequency can be set independent of the Annex or region of operation. Refer to Notes on DOCSIS 3.0
Upstream Frequency Range (page 308) for more information on changing the maximum allowable center frequencies.
Figure 65: 24U Cable Access Module (CAM) and the Three Types of Upstream Physical Interface Cards (PICs)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
278
Chapter 9: Upstream Cable Access Modules (UCAMs)
Note: Any unused connectors (either downstream or upstream) should have a 75 Ohm termination in place.
Primary Software Function
The primary software function on the 24U CAM includes:
CM Ranging and Registration
MAC Address Learning
DOCSIS functions: Packet Classification, Service Flows, Dynamic Services (DSx), BPI+, CM Upstream Bandwidth
Scheduling (MAPs), Payload Header Suppression (PHS), Packet defragmentation, packet de-concatenation, and counts
collection
Upstream Policing
Operations, Administration, Maintenance & Provisioning (OAM&P) including initialization and fault recovery code
PacketCable DSx processing.
LED Status
The LED status descriptions for the 24U CAM are listed in the table below:
Table 40. 24U CAM LED Descriptions
Front LEDs
Power
Out of Service
Module Status
On
Off
Powered and in normal service state.
Flashing
On
Flashing = 1.6 second period. Module power is off: either slot is not
provisioned or module has been disabled.
Persistent
Fast Flashing
On
Fast flashing = 6 times/second. Normal when card is first powered or
restored. If fast flashing persists for more than 2 seconds, there is a
serious power problem.
On
On
Powered and out of service.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
279
Chapter 9: Upstream Cable Access Modules (UCAMs)
Front LEDs
Power
Out of Service
Module Status
On
Flashing
Downloading data from SCM, initializing or running diagnostics.
Off
Off
The slot has no power.
Shuffle Network
The Shuffle network spreads upstream channels across multiple PHY chips as the MSO populates the RF connectors in
order from top to bottom. When fewer than eight F-connectors are wired (e.g. connectors 0 through 3), the shuffle
network will enable the operator to access all 24 upstreams.
The 24U CAM will support 24 upstream channels using eight connectors through the current 12U PIC.
With the Shuffle network, connectors 0, 2, 4, 6 are connected to the first chip (upstream receivers 0 through 11) and
connectors 1, 3, 5, 7 will be connected to the second chip (upstream receivers 12 through 23) as shown in the figure below.
Figure 66: Illustration of the Shuffle Network
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
280
Chapter 9: Upstream Cable Access Modules (UCAMs)
ARRIS designed the 24U CAM with a Shuffle network so that operators can populate cables onto the 24U CAM connectors
in order from top to bottom and still easily utilize up to all 24 upstreams available on the CAM.
To assign US channels (receiver) to connectors, use the following command:
configure interface cable-upstream <slot/us_port> cable connector <number> [no]
Where: us_port = The upstream port. Valid range is 0-23
number = The upstream connector on the PIC. Valid range is 0-7.
The [no] version of the command will unassign (decouple) the US channel (receiver) from the connector.
The following table specifies the valid US channels (receiver) / connector combinations.
Table 41. Valid US Channels/Connector
Upstream Channel
Receiver
Connector
0-11 (first receiver)
0, 2, 4, 6
12-23 (second receiver)
1, 3, 5, 7
Rules and Restrictions for 12U/24U CAM Configuration
Before growing and configuring a 12U/24U CAM with its upstreams, you should review the following rules and restrictions.
Slot Provisioning
The 12U CAM must be grown in a CAM slot provisioned for a 12U CAM and the 24U CAM must be grown in a CAM slot
provisioned for a 24U CAM. CAM sparing can only be done by like cards: a 12U can spare only for a group consisting of
12Us and a 24U can spare only for a group consisting of 24Us. All the CAMs in a sparing group must be of the same type.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
281
Chapter 9: Upstream Cable Access Modules (UCAMs)
Annex
The CMTS supports multiple annexes in one system. See Mixed Annex Support (page 243).
Upstream (US) Channel to Physical Connector Mapping
Guidelines for mapping upstream channels to physical connectors:
There must be no frequency overlap among the upstream channels using the same connector.
The CMTS displays the following error message when the user attempts to change an upstream power level or channel
width to a value that is not valid for that power level group:
Upstream channel power level conflict with another channel using the same connector.
If you receive the above message, the power level and channel width will remain unchanged.
The following guidelines are specific to the 12U CAM:
There are 8 physical connectors and 12 upstream channels on the 12U CAM. If all channels are enabled then at least
one physical connector will receive more than one upstream channel.
Any upstream or all of the upstreams can be connected to any one of the physical upstream connectors.
The following guidelines are specific to the 24U CAM:
There are 8 physical connectors and 24 upstream channels on the 24U CAM. When all upstreams are active, at least
two connectors will be in use.
Upstream channels 0-11 are connected to connectors 0, 2, 4 and 6 while upstream channels 12-23 are connected to
connectors 1, 3, 5 and 7.
Upstream channels connected to a single physical connector may vary in channel width and power levels as long as the
variance falls within a user-configured power level group. The tables below describe the upstream receiver power level
groups. All of the power levels for all of the channels connected to a single physical connector must fall within the
same table.
24U CAM Upstream Power Level Groups
All upstream Rx (receive) values are measured in dBmV. Power after attenuation may vary slightly from one CAM to
another.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
282
Chapter 9: Upstream Cable Access Modules (UCAMs)
Table 42. US Receiver Power Level Group 1
1.6 MHz
3.2 MHz
6.4 MHz
-13
-10
-7
-12
-9
-6
-11
-8
-5
-10
-7
-4
-9
-6
-3
-8
-5
-2
Table 43. US Receiver Power Level Group 2
1.6 MHz
3.2 MHz
6.4 MHz
-7
-4
-1
-6
-3
0
-5
-2
1
-4
-1
2
-3
0
3
-2
1
4
-1
2
5
0
3
6
Table 44. US Receiver Power Level Group 3
1.6 MHz
1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
3.2 MHz
4
6.4 MHz
7
C4® CMTS Release 8.3 User Guide
283
Chapter 9: Upstream Cable Access Modules (UCAMs)
1.6 MHz
3.2 MHz
6.4 MHz
2
5
8
3
6
9
4
7
10
5
8
11
6
9
12
7
10
13
8
11
14
Table 45. US Receiver Power Level Group 4
1.6 MHz
3.2 MHz
6.4 MHz
9
12
15
10
13
16
11
14
17
12
15
18
13
16
19
14
17
20
15
18
21
16
19
22
17
20
23
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
284
Chapter 9: Upstream Cable Access Modules (UCAMs)
Table 46. US Receiver Power Level Group 5
1.6 MHz
3.2 MHz
6.4 MHz
18
21
24
19
22
25
20
23
26
21
24
27
22
25
28
23
26
29
Before Changing the Receive Power Level Settings of the 24U CAM
If there are multiple upstream channels on a single 24U CAM connector and the user is trying to change the receive power
level setting on one or more US channels and the new setting causes a change in the power level group (see Tables above),
then the user must complete the following steps:
1. Unassign (decouple) the corresponding connector (for all upstream channels that are on that connector).
2. Set the receive power level for all upstream channels on that connector.
3. Add the connector back for all upstream channels on that connector.
Note: The above procedure will not apply when the user changes receive power level setting on one or more upstream
channels on the same connector and the new setting does not cause a change in the amplifier attenuation settings. That is,
the new and old receive power level settings occur within the same amplifier attenuation setting (per the tables listed in
the see "24U CAM Upstream Power Level Groups (page 282)).
The following is an example of setting the upstream channels receive power level (attenuation) that will cause a change in
the amplifier attenuation settings. Upstream channels 3/0 and 3/1 have the following initial power and channel width
settings (3.2 and 6.4 MHz and power level 0):
configure interface cable-upstream 3/0 shutdown
configure interface cable-upstream 3/1 shutdown
configure interface cable-upstream 3/0 cable connector no
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
285
Chapter 9: Upstream Cable Access Modules (UCAMs)
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/1
3/0
3/1
3/0
3/1
3/0
3/1
cable connector no
cable power-level 10
cable power-level 10
cable connector 0
cable connector 0
shutdown no
shutdown no
Note: Before using configuration scripts or making extensive changes to RF parameters, see If Using Reconfiguration
Scripts or Making Multiple RF Parameter Changes (page 243).
Default Admin States
The default administrative states for the slot/port (receiver) on the 12U CAN and the 24U CAM is UP.
Note: If an upstream channel is configured for ATDMA or SCDMA, then only DOCSIS 2.0 and 3.0 modems will register on
those channels.
Basic Command Set for Bringing Up a 24U CAM
The set of commands provided in the table below is the bare minimum for turning up a 24U CAM in a given slot. The values
chosen for these commands are meant to be examples. Actual values will vary.
Table 47. Example of Basic Command Sequence for Configuring a 24U in Slot 5
Purpose
CLI Command
Configure the Upstream Parameters
Provision slot 5 as a 24U slot.
configure slot 5 type 24UCAM
Restore 24U in slot 5.
configure slot 5 no shutdown
Assign MAC domain
configure interface cable-mac 1
Restore cable-mac 1
configure interface cable-mac 1 no shutdown
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
286
Chapter 9: Upstream Cable Access Modules (UCAMs)
Purpose
CLI Command
configure interface cable-upstream 5/0 cable cablemac 1
Assign a channel to cable-mac 1
Configure the Upstream Frequencies and Connectors
Assign upstream channel 0 of CAM 5, to connector 0.
configure interface cable-upstream 5/0 cable
connector 0
Configure upstream channel 0 of CAM 5, to use frequency 12
MHz.
configure interface cable-upstream 5/0 cable
frequency 12000000
Specify that DS channel 14/0 carries the supervision for channel
5/0.
configure interface cable-upstream 5/0 cable
supervision 14/0
Put CAM in Service
Restore upstream channel 0 of CAM 5 to service.
configure interface cable-upstream 5/0 no shutdown
Restore the logical channel to service.
configure interface cable-upstream 5/0.0 no
shutdown
Confirm channel settings for slot 5.
show interface cable-upstream 5
To view the channel settings resulting from configuring the 24U CAM (note that this example shows that a downstream
was previously configured), enter:
show interface cable-upstream 5
Upstream Port 5/0
------------Port state:
Connector:
Cable-Mac:
Downstream Supervision Ports:
Frequency (Hz):
Channel width (Hz):
Equalizer Coefficient State:
Power (dBmV):
Max Power Adj Per Range Resp (1/4 dBmV):
Ranging Power Thresh For Success (1/4 dBmV):
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
IS
0
1
14/0
12000000
3200000
off
0
24
24
C4® CMTS Release 8.3 User Guide
287
Chapter 9: Upstream Cable Access Modules (UCAMs)
Load Balance Group Id:
16781312
Max Allowable Normal Voice BW (%):
50
Reserved Normal Voice BW (%):
0
Max Allowable Emergency Voice BW (%):
70
Reserved Emergency Voice BW (%):
0
Max Allowed Total (Emergency + Normal) (%): 70
Ingress Cancellation Interval:
0
Ingress Cancellation Size:
0
Map Size (800 microsecond ticks):
4
Logical Channel:
0
1
------------------------------------------------------------Channel State
IS
OOS
Channel-ID:
1
25
Channel Type:
tdma
tdma
Modulation profile id:
2
2
Ranging backoff range:
2 - 7
2 - 7
Data backoff range:
2 - 8
2 - 8
Slot Size (6.25 microsecond ticks):
4
4
SCDMA active codes:
SCDMA codes per slot:
SCDMA frame size:
SCDMA hopping seed:
Spectrum Group ID:
Spectrum Group State:
Attribute Mask:
Number of Equalizer Taps:
0x00000000
24
0x00000000
24
The table below shows the commands to restore default values for a number of upstream and downstream parameters.
These are the settings which most users will choose for basic configuration. In each command the default values can be
replaced as needed.
Table 48. Accepting Default Parameters for Cable Upstream Channels of a 24U CAM
Purpose
CLI Command
Accept default modulation profile.
Default = 2.
configure interface cable-upstream <slot/port> cable
modulation-profile 2
Accept default channel width. Default = 3.2
MHz.
configure interface cable-upstream <slot/port> cable
channel-width 3200000
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
288
Chapter 9: Upstream Cable Access Modules (UCAMs)
Purpose
Accept default upstream power level. Default
= 0.
Power range varies with channel width
selection.
Range = -10 to 26 dBmV if channel width is
3.2 MHz
CLI Command
configure interface cable-upstream <slot/port> cable powerlevel 0
Measuring SNR in the 12U/24U CAM
For the upstream channel Signal-to-Noise Ratio (SNR) in the C4 CMTS, there are two types of SNR: Channel SNR and
Modem SNR. Channel SNR is calculated on a upstream channel basis and the per Modem SNR is calculated from the
primary upstream service flow (primary SID) of the modem. TDMA and SCDMA Long Term Slicer Error Power is also used
for calculation of the logical channel SNR. If the current Channel SNR is 0 (no traffic on the upstream), the SNR algorithm
uses Long Term SNR calculation based from PHY Slicer error which is based upon all IUCs including contention IUCs (i.e. 1
and 3).
Two pieces of information are used in calculating SNR: symbol errors and burst counts. The SNR calculation is performed
once the burst count is greater than a certain threshold. The threshold varies depending on whether it occurs in the initial
ranging period or during data traffic. The SNR reading is 0.0dB when:
The logical upstream channel is not in service (IS state) or
No modem is registered on the upstream channel
Channel SNR Calculations
In normal operations, SNR readings reflect upstream channel conditions. The SNR readings will decrease as noise level goes
up. In an ideal condition, when noise is not present or very low, the SNR value in decibels is in the high 30’s.
Two SNR calculations are performed in the CAM for Channel SNR. SNR based from MAC (IUC4 plus all data IUCs) does not
include contention Interval Usage Codes (IUCs) such as 1 and 3. The second SNR calculation is based on all IUCs including
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
289
Chapter 9: Upstream Cable Access Modules (UCAMs)
IUC1 and IUC3. The two SNR values can be obtained with show cable noise cable-upstream slot/uport
command. The show cable noise CLI command outputs only the SNR without the contention IUCs.
detail
CLI
The channel SNR calculation is the same between the 12U and 24U CAM. The SNR is based on the MAC (IUC4 + all data
IUCs) excluding contention IUC1 and IUC3. A burst count threshold of 100 packets is used in the calculation and the MIB
attribute for this SNR is docsIfSigQSignalNoise. The show cable noise CLI command outputs this SNR whereas the show
cable noise cable upstream slot/uport detail CLI command outputs additional SNR calculations based from the PHY
chips where the SNR calculation includes all IUCs including contention IUCs.
Besides the SNR measurement, the CMTS uses FEC counters to provide additional information to describe the condition of
an upstream channel.
The CLI command show
cable noise
outputs the SNR from IUC4 + all data IUCs and FEC counts as shown below:
Upstream Cable
Port
Mac
SNR(dB) MicroReflection FEC_Unerrored FEC_Corrected FEC_Uncorrected Codewords In Error(%)
-------------------------------------------------------------------------------------------------------------3/0
1
38.6
0
4229
0
0
0.00e+00
3/1
1
38.5
0
3000
0
0
0.00e+00
3/12
1
44.2
0
7757
0
0
0.00e+00
3/13
1
41.6
0
8537
0
0
0.00e+00
Note: The MicroReflection column is shown in the table, but is not supported in any release. As SNR values decreases, the
probability of FEC Corrected and FEC Uncorrected increases.
CLI commands show cable noise cable-upstream
Channel SNR is output as shown below:
slot/port detail
shows both calculated SNR values. For 12U CAM,
show cable noise cable-upstream 3/0 detail
CAM/US: 3/0 Cable-Mac: 1
SNR from MAC BCM3214, IUC4 + all data IUCs
SNR from PHY BCM3140, TDMA all IUCs
:
:
37.9
37.7
:
:
38.7
37.9
For 24U CAM, Channel SNR is output as shown below:
show cable noise cable-upstream 3/0 detail
CAM/US: 3/0
Cable-Mac: 2
SNR from BCM3142, IUC4 + all data IUCs
SNR from BCM3142, TDMA all IUCs
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
290
Chapter 9: Upstream Cable Access Modules (UCAMs)
Modem SNR Calculation
Modem SNR calculation between 12U and 24U CAM has some variation, as the table below shows:
Table 49. SNR Calculations for Modem SNR
Card Type
12U Channel SNR
Initial Ranging Period
24U Channel SNR
CLI command show
During Traffic/Idle
Calculation is based on IUC4 (station maintenance)
reading only.
Burst counts threshold is 5 packets
CLI show cable modem noise
MIBs attribute:
docsIf3CmtsCmUsStatusSignalNoise
MIB attribute is based on the primary flow SNR.
Calculation is based on all IUCs except IUC1 and IUC3.
Burst counts threshold is 5 packets
CLI show cable modem noise
MIBs attribute:
docsIf3CmtsCmUsStatus Signal Noise
MIB attribute is based on the primary flow SNR.
Calculation is based on all IUCs except IUC1 and
IUC3.
Burst counts threshold is 50 packets
CLI show cable modem noise
MIBs attribute:
docsIf3CmtsCmUsStatusSignalNoise
MIB attribute is based on the primary flow SNR.
Calculation is based on all IUCs except IUC1 and
IUC3.
Burst counts threshold is 50 packets
CLI show cable modem noise
MIBs attribute:
docsIf3CmtsCmUsStatusSignalNoise
MIB attribute is based on the primary flow SNR.
cable modem noise outputs as below
UChan
Interface
USSNR
CM MAC address (DS-US)
(db)
--------------- ------------- -----0015.cf9a.4c01 14/0-3/13
38.2
+0015.cf9a.4c01 14/0-3/0
38.6
+0015.cf9a.4c01 14/0-3/1
38.9
+0015.cf9a.4c01 14/0-3/12
38.1
0015.d187.3b7d 14/2-3/12
38.6
+0015.d187.3b7d 14/2-3/0
38.5
+0015.d187.3b7d 14/2-3/1
38.5
+0015.d187.3b7d 14/2-3/13
38.5
0015.cfb7.c5a1 14/2-3/13
38.0
0015.cfb7.c5e3 14/3-3/12
38.6
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
UChan FEC
Unerrored
Codewords
--------1064
1058
1056
1059
494
493
492
492
834
498
UChan FEC
Corrected
Codewords
--------0
0
0
0
0
0
0
0
0
0
UChan FEC
Uncorrect
Codewords
--------0
0
0
0
0
0
0
0
0
0
UChan FEC
% Uncorrected
Codewords
-------------0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
C4® CMTS Release 8.3 User Guide
291
Chapter 9: Upstream Cable Access Modules (UCAMs)
0015.d0a1.a0f3
0015.cfb7.c394
0015.d002.e6f6
+0015.d002.e6f6
0015.d002.e6f6
+0015.d002.e6f6
NOTE: the plus
14/4-3/0
39.2
1598
0
14/5-3/13
38.1
895
0
14/6-3/12
38.2
503
0
14/6-3/0
38.5
500
0
14/6-3/1
38.2
502
0
14/6-3/13
38.1
496
0
sign "+" indicates a non-primary channel
0
0
0
0
0
0
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
0.00e+00
Modulation Profiles
The pre-defined modulation profiles discussed in this section are used as a means to define the values of the several
parameters needed to configure an upstream (US) channel. These modulation profiles are each given an ID number. They
can be modified or used as a starting point to create other modulation profiles for upstream channel definitions that better
suit the customers’ applications and environments.
Default Modulation Profile
The Modulation Profile ID 2 uses QPSK and TDMA, and it is the default profile. The following sections show you how to
define a new modulation profile.
Note: Modulation profile ID 2 can be modified but it cannot be deleted.
How to Create and Apply a Modulation Profile to an US Port
This procedure can be used to modify existing modulation profiles or to add new ones. Modulation profiles must be
created and then associated with specified upstream ports.
Table 50. Existing or New Modulation Profile
If you specify an …
Then the procedure will …
existing modulation profile ID
change an existing modulation
profile.
unused modulation profile ID
add a new modulation profile.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
292
Chapter 9: Upstream Cable Access Modules (UCAMs)
1. The default modulation profile ID is 2. Use one of the following commands to create a new one modulation profile:
a. The command below creates a modulation profile that contains all of the needed IUCs with the default values,
which are recommended.
configure cable modulation-profile <id> <tdma|atdma|scdma|tdma-atdma> <qpsk | qam-8 | qam-16 |
qam-32 | qam-64>
b. The following command creates a new modulation profile if the ID number specified has not been used. This new
modulation profile contains only the IUC value specified. Before this modulation profile can be used, all of the
necessary IUCs must be added to it.
configure cable modulation-profile <id> <iuc <type>>
Where:
id= The number of the modulation-profile
type = IUC Type (see following note)
Note: Default values for the various modulation profile parameters may change according to the IUC selected. See
Modulation Profile Values (page 300) for a complete listing.
Each of the two commands above can be used to modify an existing modulation profile. The first command changes all
of the values of the modulation profile to the default values. The second command changes only the values that are
specified in the command line.
2. Use the following command to apply an existing modulation profile to an upstream port. Do not enter a range of ports;
the command must be repeated for each upstream port.
configure interface cable-upstream <slot>/<port> cable modulation-profile <id>
3. Verify the parameters of the new (modified) modulation profile:
show cable modulation-profile <id>
The system response is similar to the following output:
Modulation profile 2
Interval
Chan Mod
Pre Dif FEC FEC Scr
Max Guar L Scr ---Atdma--- Prea -----Scdma----Usage
Type Type
Len Enc
CW amb
Bur Time C amb Int
Int
mble TCM Int Sp Sub
Code
En
Len Seed Siz Size S En Depth Block Type En Size En Cod
-----------------------------------------------------------------------------------------------1 request tdma qpsk
56
F
0 16
338
0
8 F
T
- 3 initial tdma qk
640
F
5 34
338
0
48 F
T
- 4 station tdma qppssk 384
F
5 34
338
0
48 F
T
- 5
short tdma qpsk
84
F
6 78
338 45
8 T
T
- -
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
293
Chapter 9: Upstream Cable Access Modules (UCAMs)
6
long
tdma qpsk
96
F
8 220
338
0
8 T
T
-
-
-
-
-
-
-
How to Configure an Upstream (US) Channel
Perform the following procedures for US channel 0 and repeat as necessary for all channels on this CAM. The valid
range for US channels is 0–11 (12U CAM) or 0-23 (24U CAM). Some steps are optional. By not executing the optional
steps, default settings are applied.
Valid Center Frequencies
In the first step, set the center frequency of the upstream channel. The range of valid center frequencies varies according
to the channel width selected. The overall upstream bandwidth in North America is from 5–65 MHz. The first valid center
frequency in Hertz is 5,000,000 plus ½ of the channel width. The last valid frequency is 65,000,000 minus ½ of the channel
width. Thus, 5-65 MHz is the overall upstream range.
To calculate valid upstream center frequencies, refer to the table below.
Note: The CLI supplies meaningful error messages for some but not all invalid combinations of channel width and
frequency. If the CLI has no error message to give, a generic SNMP-level message is displayed.
Table 51. Range of Valid Center Frequencies for Upstream Channels in North America
If channel width is…
Then first valid center frequency is…
And the last valid center frequency is…
1600000
5800000
64200000
3200000
6600000
63400000
6400000
8800000
61800000
1. (Required) Set the center frequency of the US port in Hertz:
configure interface cable-upstream <slot>/<port> cable frequency <5100000-64900000>
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
294
Chapter 9: Upstream Cable Access Modules (UCAMs)
Refer to Notes on DOCSIS 3.0 Upstream Frequency Range (page 308) for more information on changing the maximum
allowable center frequencies.
2. If desired, set US channel width in Hertz (default = 3200000):
configure interface cable-upstream <slot>/<port> cable channel-width {200000 | 400000 | 800000 |
1600000 | 3200000 | 6400000}
Where 1600000, 3200000, and 6400000 represent the currently supported values for channel bandwidth in Hertz.
Setting the Rx Power Levels
The default receive power level of the CMTS is 0 dBmV.
1. If desired, change the input Rx power level. As shown in the table below the valid range varies according to the
upstream bandwidth.
configure interface cable-upstream <slot>/<port> cable power-level <-13 to 29>
2. If the width of a channel is changed and the receive power level is no longer valid, the CMTS automatically adjusts the
receive power to the nearest valid value.
US Channel Width in Hz
Valid Rx Power Range (dBmV)
1600000
-13 to +23
3200000
-10 to +26
6400000
-7 to +29
* Note that setting the power levels above 23dBmV is not
recommended.
Note: Resetting the receive power level in a single step from minimum to maximum in a given power range may
prevent CM range requests from being received. For example, if the US channel bandwidth is 3200000 Hz and the
power level is reset from -10 to 26 dBmV, then the CMs might not remain registered. The CMTS avoids this by
resetting the power in one or more steps according to the max-power-adj parameter found in the CMTS cable
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
295
Chapter 9: Upstream Cable Access Modules (UCAMs)
upstream provisioning. Refer to the tables in see "24U CAM Upstream Power Level Groups (page 282), to make
sure your settings fall within the proper table.
1. If desired, change the maximum power adjustment parameter using the following command (range = 1–48; default =
24 units, which equals 6 dBmV):
configure interface cable-upstream <slot>/<port> cable max-power-adj <power adjustment>
Where: <power adjustment> = Maximum size of the CMTS range , and response power adjustments in units of 0.25
dBmV.
2. If desired, set the start and end values for databackoff parameter (default = 2-8):
configure interface cable-upstream <slot>/<port> cable databackoff <0-16>-<0-16>
Where: the first <0-16> is the valid range for the start value, the second <0-16> is the valid range for the end value,
and the start value must be less than or equal to the end value.
3. If desired, enable or disable the sending of pre-equalization coefficients to the CMs:
configure interface cable-upstream <slot>/<port> cable pre-eq-enable <true|false>
Where true = enabled and false = disabled.
4. If desired, select modulation profile ID (default = 2):
configure interface cable-upstream <slot>/<port> cable modulation-profile <profile id>
Where: <profile ID> = the modulation profile numeric identifier
5. If desired, set the start and end values for range backoff parameter (default = 2-7):
You must enter the start and end values separated by a dash.
configure interface cable-upstream <slot>/<port> cable rangebackoff <0-16>-<0-16>
Where: the first <0-16> is the valid range for the start value, the second <0-16> is the valid range for the end value, and
the start value must be less than or equal to the end value.
6. If desired, put US port in service:
configure interface cable-upstream <slot>/<port> no shutdown
7. If desired, put US logical channel in service:
configure interface cable-upstream <slot>/<port[.0]> no shutdown
8. If desired, modify some or all of the following parameters for this US channel:
configure interface cable-upstream <slot/port> cable ?
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
296
Chapter 9: Upstream Cable Access Modules (UCAMs)
attribute-mask
cable-mac
channel-id
channel-width
connector
databackoff
docsis-mode
frequency
ingress-cancellation
load-balance
map-size
max-power-adj
mini-slot-size
modulation-profile
num-equalizer-taps
power-level
pre-eq-enable
rangebackoff
relay-agent-option
scdma
show
spectrum-group
supervision
threshold-power-offset
voice-limits
-
Configure attributes for this channel for channel assignment
Assign an upstream to a specific cable mac
Provision the channel identifier for the upstream
Provision the channel-width for an upstream
Provision the connector for an upstream
databackoff <WORD>
Provision the docsis mode for an upstream
Provision the frequency for an upstream
Upstream ingress cancellation properties
Turn on/off dynamic load balancing for the upstream channel
Provision the map size for an upstream
Provision the max power adjust for an upstream
Provision the mini slot size for an upstream
Provision the modulation profile for an upstream
Set the number of taps in the receiver’s equalizer
Provision the power level for an upstream
Use pre-equalization technique to reduce upstream signal distortion
rangebackoff <WORD>
Relay agent circuit ID sub-option
Upstream SCDMA properties
Display the upstream configuration
Enables frequency agility on this port
Provision the supervisory downstream for this upstream.
Provision the power offset threshold for an upstream
Set voice data limits
9. Refer to the Command Line Descriptions (page 1127) for additional information on this command.
10. Repeat this procedure as needed for the remaining US ports, 0–11 (12U CAM) or 0-23 (24U CAM), on this CAM.
Putting Cards and Ports into Service
This procedure assumes that the US and DS channels have already been configured. This example is for a 24U CAM:
1. The following command brings the CAM online:
configure slot <slot> no shutdown
Where: slot = the number of the slot, 0-15.
2. Bring up the upstream channel:
configure interface cable-upstream <slot>/<port> no shutdown
3. Bring up the logical channel:
configure interface cable-upstream <slot>/<port[.0]> no shutdown
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
297
Chapter 9: Upstream Cable Access Modules (UCAMs)
4. Repeat steps 2 and 3 as needed for additional upstream channels.
5. Restore the mac-port:
configure interface cable-mac <num> no shutdown
How to Take a CAM Out of Service and Delete Its Slot
This procedure is used to remove a CAM and the slot in which it resides out of service.
1. If the CAM to be taken out of service is part of a spare group, first remove the card from the spare group.
configure slot <slot> spare-group <int> no
2. Take the CAM out of service:
configure slot <slot> shutdown
Where: slot = the number of the slot, 0-15.
3. Verify module status:
show linecard status
The system response should confirm that the module is out of service.
4. Deprovision the slot:
configure no slot <slot>
Where: slot = the number of the slot, 0-15.
5. Save your changes:
write memory
Adjusting Channel Settings in Response to Increased CM Scaling
The table below presents recommendations for channel parameters with respect to cable modem scaling and feature loads.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
298
Chapter 9: Upstream Cable Access Modules (UCAMs)
Table 52. Recommended Settings as Cable Modem Scaling Increases
Ranging
Backoff
Insertion
Interval
Centisecs
Ranging
Interval
Centisecs
Up to 1000 (b)
2-5
10-40
1000-2000 (c)
3-7
2000-4500 (12U only)
2000-660024U only)
5-9
CMs per CAM
BPI ?
CAM
Sparing
Service Flow
US Priority
Bandwidth
Data Rate
Restrictions
2400
OK
Yes
Any
None
20-40
1500-2400
OK
Yes
Any
None
20-40
1500
OK
Yes
Any
None
(a) If CAM Sparing is not configured, the Ranging Interval can be left at the default value of 2400 centiseconds.
Reducing the Ranging Interval is done for the purpose of improving CAM Sparing results on larger scale systems.
(b) If BPI+ is enabled on modems, use 40 centisecond insertion interval when supporting 500-1000 modems.
(c) If BPI+ is enabled on modems, use 40 centisecond insertion interval.
Explanation of Upstream Parameters
Modulation profiles are pre-defined sets of upstream channel parameters which make it easier to configure or reconfigure
upstream channels. This document describes the parameters used in modulation profiles. Where possible, it lists the
default values of these parameters. For greater technical detail on these parameters and their functions, see the DOCSIS
Radio Frequency Interface Specification.
In order to understand all of the parameters used in modulation profiles, some terms must be defined:
IE — Information Element — portions of the allocation MAP used to define transmission opportunities for cable modems.
Each IE is a 32-bit quantity, of which the most significant 14 bits represent the Service ID (SID), the middle 4 bits represent
the Interval Usage Code (IUC), and the low-order 14 bits represent the minislot offset.
SID — Service ID. SIDs are assigned to upstream Service Flows. The CMTS allocates upstream bandwidth to SIDs, therefore
to the cable modems served by the SIDs. SIDs are also used in Quality of Service functions. Certain values of SIDs are
defined in the RFI specification and convey specific meanings for the service flows they represent:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
299
Chapter 9: Upstream Cable Access Modules (UCAMs)
0x3FFF
implies all CMs (broadcast)
0x3FFx
where x is a value of 0x1 to 0xE used to indicate that a data message must fit in x number of minislots. This
can only be used in the Request/Data IE (broadcast).
0x3Exx
This can only be used in the Request IE to allow different priorities to use the request region (broadcast).
If
If
If
If
If
If
If
If
bit
bit
bit
bit
bit
bit
bit
bit
0x01
0x02
0x04
0x08
0x10
0x20
0x40
0x80
is
is
is
is
is
is
is
is
set,
set,
set,
set,
set,
set,
set,
set,
priority
priority
priority
priority
priority
priority
priority
priority
0
1
2
3
4
5
6
7
can
can
can
can
can
can
can
can
request
request
request
request
request
request
request
request
The following SID values have special meaning for 12U or 24U CAMs:
0x1FFF
0x1FFE
used for FFT (fast Fourier Transform) measurements
used for ingress cancellation
Redefining the values of an upstream modulation profile affects all the upstream channels that are using that modulation
profile. To display what upstream modulation profile is used on an upstream channel, use one of the following CLI
commands:
show controllers cable-upstream <slot>/<port>
configure interface cable-upstream <slot>/<port> cable show
The system response contains a line similar to the following:
Modulation profile id: 2
To redefine the values of an upstream modulation profile, use the following CLI command:
configure cable modulation-profile <id> iuc <interval usage code> [mod <qpsk |qam8
|qam16|qam32|qam64|qam128>] [pre-len <preamble len>] [diff <true|false>] [fec-tbytes <no of
bytes>] [fec-len <FEC code word length>] [seed <scrambler seed>] [burst-len <max burst len>]
[last-cw <true|false>] [scrambler <true|false>] [guard-time-size <0|8–96|no>] [int-depth <depth>]
[int-blocksize <blocksize>] [pre-type <preamble type>] [tcm <on|off>] [int-stepsize <stepsize>]
[spreader <on |off>] [subframe-code <subframe size>] [docsis-mode <tdma | atdma | scdma |
tdma-atdma>]
Modulation Profile Values
Default values for the various modulation profile parameters may change according to the IUC selected. To display the
values associated with a modulation profile number 2, for example, use the following command:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
300
Chapter 9: Upstream Cable Access Modules (UCAMs)
show cable modulation-profile 2
Sample output:
Modulation profile 2
Interval
Chan Mod
Pre Dif FEC FEC Scr
Max Guar L Scr ---Atdma--- Prea
Usage
Type Type
Len Enc
CW amb
Bur Time C amb Int
Int
mble
Code
En
Len Seed Siz Size S En Depth Block Type
--------------------------------------------------------------------------------1 request tdma qpsk
56
F
0 16
338
0
8 F
T
3 initial tdma qpsk
640
F
5 34
338
0
48 F
T
4 station tdma qpsk
384
F
5 34
338
0
48 F
T
5
short tdma qpsk
84
F
6 78
338 45
8 T
T
6
long tdma qpsk
96
F
8 220
338
0
8 T
T
-
Table 53. Modulation Profile Parameters
Parameter
ID
Description
Identifier. The number of the modulation profile. The CMTS supports a range of up to two billion modulation profile
IDs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
301
Chapter 9: Upstream Cable Access Modules (UCAMs)
Parameter
IUC
Description
Interval Usage Code. The IUC typically has an assigned numeric value. It defines what kind of Information Element
(IE) is being sent from the CMTS to the cable modems:
• 1 =Request
• 2 =Request/Data
• 3 =Initial Ranging
• 9 =Advanced PHY Short Data Grant
• 4 =Periodic Ranging
• 10 =Advanced PHY Long Data Grant
• 5 =Short Data Grants
• 11 =Advanced PHY Unsolicited Grant
• 6 =Long Data Grants
1 Request This portion of the upstream map interval is used by cable modems to request bandwidth for data
transmission. If the class of the SID associated with the request IE is broadcast, then cable modems must contend
with each other for upstream bandwidth. If the class of the SID associated with the request IE is unicast, then this is
an opportunity for a single cable modem to request additional bandwidth.
2 Request/Data Either data requests or short data messages can be sent in this portion of the upstream map
interval. A multicast SID must be used to indicate the size of the data message that can be sent. This IE is not used by
the CMTS map algorithm and as such changes made to this IE will have no affect on upstream data transmissions.
3 Initial Ranging (Also called Initial Maintenance). This IE allows cable modems a method to adjust their timing,
frequency, and transmit power so that they can reliably communicate with the CMTS. The timing adjustments allow
for the round trip delay of the fiber optic/coax plant plus the time to transmit the range request message. A DOCSIS
1.X cable modem can send a range request message only during this IE. A DOCSIS 2.0 cable modem can send a range
request message or an initial range request message depending upon the type of the upstream channel. Normally,
range request messages are sent in this IE when it contains a broadcast SID, meaning cable modems must contend
with each other when transmitting. An initial range request message can be sent either with a broadcast SID or with
a unicast SID depending upon the situation.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
302
Chapter 9: Upstream Cable Access Modules (UCAMs)
Parameter
Description
4 Periodic Ranging (Also called Station Maintenance). Cable modems use this IE to perform station maintenance.
This IE is unicast. Only the range request message — no other data — can be sent using this IE.
5 Short Data Grants This unicast IE gives permission to a specific cable modem to transmit one or more Protocol
Data Units (PDUs). The cable modem uses this region in the upstream map interval if the number of minislots
required to send the message is less than or equal to the maximum burst interval specified for a short data grant in
the Upstream Channel Descriptor (UCD) message. The reason that grants can be split into short and long data grants
is for the sake of FEC encoding. Short data grants are used only when a cable modem is transmitting via an upstream
channel that is compatible with DOCSIS 1.X.
6 Long Data Grants This unicast IE gives permission to a specific cable modem to transmit one or more PDUs. The
cable modem uses this region in the upstream map interval if the number of minislots required to send the message
is greater than the maximum burst interval for a short data grant in the Upstream Channel Descriptor (UCD)
message. The reason that grants can be split into short and long data grants is for the sake of FEC encoding. Long
data grants are used only when a cable modem is transmitting via an upstream channel that is compatible with
DOCSIS 1.X.
Note: The following Advanced PHY types are provided for channels carrying combined DOCSIS 1.x and DOCSIS 2.0
bursts and also for channels carrying DOCSIS 2.0 bursts.
9 Advanced PHY Short This IE is the same as a short data grant except that it is used when the cable modem is
communicating via an upstream channel that is DOCSIS 2.0 compatible.
10 Advanced PHY Long This IE is the same as a long data grant except that it is used when the cable modem is
communicating via an upstream channel that is DOCSIS 2.0 compatible.
11 Advanced PHY UGS This IE is new with DOCSIS 2.0. It allows parameters to be optimized for UGS flows, which
normally carry VoIP.
diff
Differential Encoding True = enabled; False = disabled.
mod
Modulation type Values 3–6 must not be used when the upstream channel is only DOCSIS 1.X compatible. A DOCSIS
1.X only compatible channel is signified in the UCD message with a descriptor encoded with a type 4 TLV. A type 5
TLV signifies that the channel is DOCSIS 2.0 compatible.
1 = QPSK
3 = 8QAM
5 = 64QAM
2 = 16QAM
4 = 32QAM
6 = 128QAM (not currently supported)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
303
Chapter 9: Upstream Cable Access Modules (UCAMs)
Parameter
Description
fec-tbytes Forward Error Correction (T) The number of bytes with errors that can be corrected with FEC in the size specified in
the codeword information byte length. A value of zero indicates that FEC is disabled. For each byte that can be
corrected there are two additional FEC parity bytes that are added to the FEC codeword. The FEC codeword contains
both the FEC information bytes and the FEC parity bytes. The number of codeword parity bytes is 2 x T, where T =
0-10 for a DOCSIS 1.x upstream channel and 0-16 for a DOCSIS 2.0 upstream channel.
fec-len
Forward Error Correction, Length of Codeword (K) The number of bytes in the information bytes of the FEC
codeword. Assuming that FEC is enabled, the FEC codeword can contain from 16 to 253 information bytes. The FEC
codeword contains both the FEC information bytes and the FEC parity bytes and can be between 18 and 255 bytes. A
shorter codeword will increase the amount of overhead but allow for more errors to be corrected in the total data
frame.
pre-len
Preamble Length The preamble serves to put the FEC and randomizer (also called the scrambler) into known states
before the data is transmitted. The preamble also helps the receiver to receive an upstream burst accurately. DOCSIS
1.X (type 4 TLV in the UCD) requires the preamble length to be between 0 and 1024 bits. DOCSIS 2.0 (type 5 TLV in
the UCD) requires the preamble length to be between 0 and 1536 bits.
12U or 24U CAM
• For a TDMA or tdma-atdma upstream channel, IUCs of 3 and 4 with 16 QAM must have a preamble length in the
range of 208 to 768.
• All other cases for IUCs of 3 and 4 must have a preamble length in the range of 104 to 768.
• For a TDMA or tdma-atdma upstream channel, IUCs of 1, 5 and 6 with 16 QAM must have a preamble length in the
range of 72 to 256.
• All other cases for IUCs of 1, 5 and 6 must have a preamble length in the range of 36 to 256.
• For IUCs 9, 10 and 11, the preamble length must be in the range of 36 to 512.
Note: Even with the above guidelines, it is possible to choose parameters such that the Preamble Superstring which
contains the preamble strings for all the different IUCs does not fit within either the 1024 or the 1536 bit limits.
Contact technical support for further assistance if experiencing these problems.
seed
The 15-bit seed value for the scrambler polynomial. The pseudo-random generator (randomizer) is used so that the
data stream will not produce a long string of either 1's or 0's. Changing the seed for the pseudo-random generator
will cause the generator to produce a different pattern of ones and zeroes if the same input data is sent to the
pseudo-random generator. Some seeds will work better than others for producing a good distribution of 1's and 0's
without a contiguous string of either 1's or 0's. The range of possible values is from 0-32767.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
304
Chapter 9: Upstream Cable Access Modules (UCAMs)
Parameter
Description
burst-len
Burst length The maximum number of minislots that can be used by the IE. For both short data and advanced PHY
short data grant IEs, this field must be present and must contain a non-zero value. In general, a zero value implies
that the IE is not limited. Range = 0–255.
guardtimesize
Guard Time This is the amount of time measured in symbols that must exist between successive frames. This field is
required for non-SCDMA channels and according to the RFI specification must contain a value of at least 5 symbols.
This value may be derivable from other network and architectural parameters. Range = 8–96 symbols.
last-cw
Last Codeword This indicates whether the last FEC codeword is of a fixed length or shortened.
True = shortened; False = fixed length.
scrambler
This field indicates whether the scrambler or randomizer is enabled or not. True = enabled; False = disabled.
int-depth
ATDMA Byte Interleaver Depth This parameter must be present for all IUCs with an ATDMA upstream channel or
IUCs 9, 10 and 11 with a tdma-atdma upstream channel. For all other cases, this parameter must not be present.
There are three different states for the ATDMA Byte Interleaver signified by the values: 0 = dynamic mode, 1 = off, 2floor(2048/(K + 2T)) = fixed mode. In fixed mode, there is one FEC codeword per row and the depth is the number of
rows in the interleaving matrix. In dynamic mode, the system chooses the row and column sizes of the interleaving
matrix to obtain optimum burst noise robustness.
intblocksize
ATDMA Byte Interleaver Block Size This parameter must be present for all IUCs with an ATDMA upstream channel
or IUCs 9, 10 and 11 with a tdma-atdma upstream channel. For all other cases, this parameter must not be present.
This parameter represents the number of bytes that can be used by the ATDMA interleaver when in the dynamic
mode of operation. Range = 2*(K+2T) – 2048. To obtain optimum benefit of the ATDMA interleaver, use a value of
2048.
pre-type
Preamble Type For DOCSIS 2.0 upstream channels, there are two possible constellation patterns that can be used
for the QPSK preamble: qpsk0 and qpsk1. With qpsk1 the preamble’s constellation is at a higher power level when
compared to qpsk0. DOCSIS 1.x channels must use the qpsk0 constellation pattern.
tcm
Trellis Coded Modulation TCM must only be used with an SCDMA upstream channel. TCM causes one bit in the
symbol to be used for encoding purposes. This bit acts like a parity bit for decoding the rest of the bits in the symbol.
Since one bit is removed from the symbol for encoding purposes, the data throughput is similar to what is received if
the next lower value for the modulation type is used. TCM values are either on or off. (TCM is not currently
supported.)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
305
Chapter 9: Upstream Cable Access Modules (UCAMs)
Parameter
Description
intstepsize
SCDMA Interleaver Step Size In an SCDMA upstream channel, interleaving is performed on a sub-frame basis. The
interleaver step size determines the manner in which symbols are interleaved within the sub-frame. This option
must be present for a SCDMA channel and must not be present for all other upstream channel types. Range = 1–31.
spreader
SCDMA Spreader In an SCDMA upstream channel, there are two modes of spreader operation: on and off.
According to the RFI specification, IUC 3 must use spreader off, and IUCs 1, 9, 10 and 11 must use spreader on. And
IUC 4 can use either on or off. However, the CMTS only supports the usage of spreader off for IUC 4. This option
must be present for an SCDMA channel and must not be present for all other upstream channel types.
subframecode
SCDMA Codes per Sub-Frame In an SCDMA upstream channel, interleaving is performed on a sub-frame basis. The
codes per sub-frame define the size of the sub-frame. A sub-frame can vary in size from 1 code up to the total
number of active codes. This option must be present for an SCDMA channel and must not be present for all other
upstream channel types.
docsismode
Upstream DOCSIS-Mode This parameter contains the type of the upstream channel which must correspond to one
of the following values:
• tdma (default)
• atdma
• tdma-atdma
According to the DOCSIS RFI Specification, another value that is typically associated with upstream modulation profiles is
the preamble offset start value. It indicates where in the possible string of the preamble bits the actual preamble actually
starts. This value is determined by the CMTS. The string of possible preamble bits is included in the UCD message.
Once you have equipped the CMTS with CAMs and put them in service, the upstream channels have to be configured. Use
the following command to choose the desired modulation profile and other parameters that determine the upstream
channel’s characteristics:
configure interface cable-upstream <slot/port> cable <parameter>
Note: Logical channels are sometimes called subinterfaces. When changing the following upstream parameters, if no
logical channel (n.0) is specified, then the command syntax assumes logical channel 0.
• Modulation profile ID
• SCDMA active codes
• Ranging backoff range
• SCDMA frame size
• Data backoff range
• SCDMA hopping seed
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
306
Chapter 9: Upstream Cable Access Modules (UCAMs)
• Map size (in 800 microsecond ticks)
• Slot size (in 6.25 microsecond ticks)
• SCDMA codes per slot
For all other upstream parameters, if you do not specify a logical channel, then the CLI code will apply the change to the
physical interface. In other words, both logical channels of the upstream will be affected.
For example, the following command does not specify a logical channel, and it affects the entire upstream:
configure interface cable-upstream 5/0 no shutdown
The following command brings up only logical channel 0:
configure interface cable-upstream 5/0.0 no shutdown
The following command assigns modulation profile 3 to upstream channel 5/0:
configure interface cable-upstream 5/0 cable modulation-profile 3
4 Periodic Ranging (Also called Station Maintenance). Cable modems use this IE to perform station maintenance. This IE is
unicast. Only the range request message — no other data — can be sent using this IE.
5 Short Data Grants This unicast IE gives permission to a specific cable modem to transmit one or more Protocol Data
Units (PDUs). The cable modem uses this region in the upstream map interval if the number of minislots required to send
the message is less than or equal to the maximum burst interval specified for a short data grant in the Upstream Channel
Descriptor (UCD) message. The reason that grants can be split into short and long data grants is for the sake of FEC
encoding. Short data grants are used only when a cable modem is transmitting via an upstream channel that is compatible
with DOCSIS 1.X.
6 Long Data Grants This unicast IE gives permission to a specific cable modem to transmit one or more PDUs. The cable
modem uses this region in the upstream map interval if the number of minislots required to send the message is greater
than the maximum burst interval for a short data grant in the Upstream Channel Descriptor (UCD) message. The reason
that grants can be split into short and long data grants is for the sake of FEC encoding. Long data grants are used only when
a cable modem is transmitting via an upstream channel that is compatible with DOCSIS 1.X.
Note: The following Advanced PHY types are provided for channels carrying combined DOCSIS 1.x and DOCSIS 2.0 bursts
and also for channels carrying DOCSIS 2.0 bursts.
9 Advanced PHY Short This IE is the same as a short data grant except that it is used when the cable modem is
communicating via an upstream channel that is DOCSIS 2.0 compatible.
10 Advanced PHY Long This IE is the same as a long data grant except that it is used when the cable modem is
communicating via an upstream channel that is DOCSIS 2.0 compatible.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
307
Chapter 9: Upstream Cable Access Modules (UCAMs)
11 Advanced PHY UGS This IE is new with DOCSIS 2.0. It allows parameters to be optimized for UGS flows, which normally
carry VoIP.
12U/24U Ingress Noise Cancellation
The following CLI command is used to enable ingress cancellation:
configure interface cable-upstream <x>/<y> cable ingress-cancellation [interval <int>] [size
<int>]
The recommended values for the interval and size parameters are as follows:
Interval100
Size
0
Notes on DOCSIS 3.0 Upstream Frequency Range
DOCSIS 3.0 (North America) provides for an extended upstream frequency range of 42 – 85 MHz.
The 12U CAM supports an upstream range of 5 – 65 MHz: it is limited by hardware constraints to a maximum of 65 MHz. The
24U CAM hardware has been designed to support a range of 5-85 MHz, but currently the software will only support a range of
5-65 MHz.
Use the following command to set the maximum upstream frequency for all channels (global) within the chassis:
configure cable freq-us-max {42 | 55 | 65 |85} [no]
The default maximum upstream frequency for global Annex A is 65 MHz; for Annex B it is 42. The maximum upstream
frequency of 55 MHz must be explicitly set.
The no parameter sets the upstream frequency range to the default value specified by the current Annex.
Use the following command to set the maximum upstream frequency for a specific cable-mac within the chassis:
configure interface cable-mac <x> cable freq-us-max {42 | 55 | 65 | 85}
To display the global upstream frequency range, use the following command:
show cable global-settings
To display the upstream frequency range on a specific cable-mac (which takes precedence over the global setting), use the
following command:
show interface cable-mac <x> | include upstream
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
308
Chapter 9: Upstream Cable Access Modules (UCAMs)
Modulation Profiles: Default and User-defined
Modulation profiles define the following parameters:
Modulation Type (QPSK, 8QAM, 16QAM, 32QAM, 64QAM, 128QAM)
Differential Encoding On/Off
Preamble Length
Reed-Solomon FEC Correctable Bytes (T)
Reed-Solomon FEC Information Bytes per Codeword (k)
Scrambler SEED
Maximum Burst Size
Guard Time Size
Shortened Last Codeword On/Off
Scrambler On/Off
ATDMA Reed-Solomon Interleaver Depth (Ir= 0 for Dynamic Mode, = 1 for off, = 2 through floor (2048/(k+2T)) for Fixed
Mode
ATDMA Reed-Solomon Interleaver Block Size
(Br= 2*(k+2T) through 2048)
Preamble Type
SCDMA Spreader On/Off (default = off for IUCs 3 and 4, on others)
SCDMA Framer Codes Per Subframe (selected so that the Subframe holds 1 FEC codeword)
SCDMA Framer Interleaver Step Size (default =3)
Trellis Coded Modulation (TCM) On/Off (default = Off)
In the CMTS there is a default modulation profile that is automatically created for the user: modulation profile 2.
Modulation profile 1 supported a previous version of the upstream CAM and is no longer available. CMTS users are free to
create user-defined modulation profiles.
User-defined modulation profiles provide a shortcut method for a user to easily create modulation profiles just by
specifying the desired channel type and modulation rate. User-defined modulation profiles can be assigned to any number
from 3–n to create a new profile. (It is recommended that you do not use 2; otherwise you will overwrite the default). If
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
309
Chapter 9: Upstream Cable Access Modules (UCAMs)
you choose a number that is already in use, then the existing modulation profile will be overwritten by the new one. There
is almost no limit to the number you can create.
Each user-defined modulation profile is defined by a channel type, such as tdma, and a modulation type, such as 16QAM.
The user-defined profile defines most of the parameters for that modulation and channel type. For example, if you want to
use the user-defined profile for TDMA and 16QAM to create modulation profile 20, enter the following command:
configure cable modulation-profile 20 tdma qam-16
Modulation profile 20 as defined by the above command:
Interval
Chan Mod Pre Dif FEC FEC Scr
Max Guar L Scr ---Atdma--- Prea -----Scdma----Usage
Type Type Len Enc
CW amb
Bur Time C amb Int
Int
mble TCM Int Sp Sub
Code
En
Len Seed Siz Size S En Depth Block Type En Size En Cod
--------------------------------------------------------------------------------------------1 request tdma qpsk
56
F
0 16
338
0
8 F
T
- 3 initial tdma qpsk 640
F
5 34
338
0
48 F
T
- 4 station tdma qpsk 384
F
5 34
338
0
48 F
T
- 5
short tdma q16 168
F
6 78
338 23
8 T
T
- 6
long tdma q16 192
F
8 220
338
0
8 T
T
- -
Basically, user-defined modulation profiles allow the user to specify the channel type and the modulation rate for the data
IUCs and the rest of the information for the modulation profile is filled in with recommended values. These recommended
values are generic values that should work across a wide variety of plants. Users may want to optimize these values to the
specific needs of their cable plant.
The following channel types are currently supported:
atdma
scdma
tdma
tdma-atdma
- Use preconfigured ATDMA
- Use preconfigured SCDMA
- Use preconfigured
- Use preconfigured
modulation profile
modulation profile
12U CAM TDMA modulation profile
TDMA-ATDMA modulation profile
These user-defined modulation profiles are controlled by the CMTS software. These modulation profiles may evolve and
change slightly with different software versions.
configure cable modulation-profile 100 ?
atdma
- Use preconfigured ATDMA modulation profile
iuc
- IUC type
scdma
- Use preconfigured SCDMA modulation profile
tdma
- Use preconfigured CAM TDMA modulation profile
tdma-atdma
- Use preconfigured TDMA-ATDMA modulation profile
configure cable modulation-profile 100 atdma ?
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
310
Chapter 9: Upstream Cable Access Modules (UCAMs)
qam-8
- Default ATDMA
qam-16
- Default ATDMA
qam-32
- Default ATDMA
qam-64
- Default ATDMA
qpsk
- Default ATDMA
configure cable modulation-profile
QAM-8 modulation profile
QAM-16 modulation profile
QAM-32 modulation profile
QAM-64 modulation profile
QPSK modulation profile
100 scdma ?
qam-8
- Default SCDMA
qam-16
- Default SCDMA
qam-32
- Default SCDMA
qam-64
- Default SCDMA
qpsk
- Default SCDMA
configure cable modulation-profile
QAM-8 modulation profile
QAM-16 modulation profile
QAM-32 modulation profile
QAM-64 modulation profile
QPSK modulation profile
100 tdma ?
qam-16
- Default TDMA QAM-16 profile
qpsk
- Default TDMA QPSK modulation profile
configure cable modulation-profile 100 tdma-atdma ?
qpsk
qam-8
qam-16
qam-32
qam-64
-
Default
Default
Default
Default
Default
TDMA-ATDMA QPSK modulation profile
TDMA - QPSK for data IUCs and ATDMA - QAM8 for data IUCs
TDMA - QAM16 for data IUCs and ATDMA - QAM16 for data IUCs
TDMA - QAM16 for data IUCs and ATDMA - QAM32 for data IUCs
TDMA - QAM16 for data IUCs and ATDMA - QAM64 for data IUCs
Displaying Modulation Profiles
Use the following command to view a modulation profile:
show cable modulation-profile n
Where n = the number of the desired profile.
Optimizing a Modulation Profile
This section is meant to serve as a guide to some of the issues that are involved in optimizing a modulation profile.
Optimizing a modulation profile involves many factors; this document does not claim to explain them all.
What you are really trying to do is to optimize throughput in the upstream channel connected to the CMTS and still
maintain an acceptable packet error rate. This distinction is important because noise on the upstream channel plays a big
role in determining the best modulation profile to use. Additionally, noise on an upstream channel is not consistent over
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
311
Chapter 9: Upstream Cable Access Modules (UCAMs)
time. Because of this if a single modulation profile is used, then this modulation profile must be able to handle the worst
case noise that is expected on the upstream channel and still achieve a reasonable level of performance.
Noise and SNR versus Modulation Symbol Rate
Unfortunately, different types of noise are typically seen on an upstream channel, and each type has a different effect on
the upstream channel. There is the Average White Gaussian Noise (AWGN) that is always present and is typically referred
to as the noise floor. There may be impulse and ingress noise, both of which may cause the noise floor to spike.
Note: Impulse noise is a spike in the time domain and ingress noise results in a spike in the frequency domain.
There are various techniques that can be used to reduce the effects of each of these types of noise. For example, having all
the cable modems transmit at a higher power level (assuming there is enough power headroom) gives a better Signal to
Noise Ratio (SNR) because the modem’s bursts are at a higher power level while the AWGN remains at about the same
level. Forward Error Correction (FEC), Ingress Cancellation Block (ICB), and interleaving can be used to correct ingress and
impulse noise.
Noise affects the SNR. The SNR is the primary indicator of what modulation rate can be used on the upstream channel. If
one assumes that an upstream channel has no ingress or impulse noise, then theoretically the following modulation rates
would work as long as the SNR of the upstream channel is higher than the stated threshold shown in the table below.
The table below is based on theory. In the real world the thresholds shown here would be too low. The amount of margin
that needs to be added is dependant upon the types of noise present in the plant and how that noise varies over time.
Even in a clean plant, we would recommend a margin of at least 4 dB. For a plant with a high noise level, the margin should
be increased. Additionally, the CMTS is effective in eliminating AWGN, less effective for impulse noise, and still less
effective for ingress noise. Therefore, the amount of SNR margin may also be varied depending upon the type of noise that
is present in the system.
Table 54. Minimum SNR Thresholds under Lab Conditions
If the Modulation Rate Is…
Then the SNR Threshold Must Be at Least:
64 QAM
21 dB
32 QAM
18 dB
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
312
Chapter 9: Upstream Cable Access Modules (UCAMs)
If the Modulation Rate Is…
Then the SNR Threshold Must Be at Least:
16 QAM
15 dB
8 QAM
12 dB
QPSK
9 dB
FEC
Forward Error Correction (FEC) can correct errors that occur in the upstream channel; however, this comes with a cost of
additional overhead. FEC is typically expressed in terms of two parameters, T and k. T is used to represent the number of
byte errors that can be corrected. The k parameter is used to specify the number of bytes over which the T number of byte
errors can be corrected and is called the codeword length.
The cost of correcting up to T byte errors in k data bytes is that there is an additional 2 * T bytes of overhead. Note, the
values for T are shown in the FEC column in the show cable modulation-profile CLI command. The values for k are shown in
the FEC CW Len column in the show cable modulation-profile CLI command.
show cable modulation-profile 6
Typical output:
Modulation profile 6
Interval
Chan Mod Pre Dif FEC FEC Scr
Max Guar L Scr ---Atdma--- Prea -----Scdma----Usage
Type Type Len Enc
CW amb
Bur Time C amb Int
Int
mble TCM Int Sp Sub
Code
En
Len Seed Siz Size S En Depth Block Type En Size En Cod
--------------------------------------------------------------------------------------------1 request tdma qpsk
56
F
0 16
338
0
8 F
T
- 3 initial tdma qpsk 640
F
5 34
338
0
48 F
T
- 4 station tdma qpsk 384
F
5 34
338
0
48 F
T
- 5
short tdma q16 168
F
6 75
338
7
8 T
T
- 6
long tdma q16 192
F 10 220
338
0
8 T
T
- -
The figure below illustrates the relation between code words and the packet, and between the T and k parameters. For
more information, see the DOCSIS RFI Specification, version 2.0. (CM-SP-RFIv2.0-C02-090422).
For DOCSIS 3.0, see CM-SP-PHYv3.0-I10-111117.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
313
Chapter 9: Upstream Cable Access Modules (UCAMs)
Figure 67: Relation of FEC Codewords to Data Packet
A slight decrease in SNR can cause a large increase in the Packet Error Rate (PER). There comes a point where simply
adding additional FEC to attempt to correct for the upstream errors is no longer efficient. Once this point is reached, it is
more efficient to use a lower modulation rate with less FEC overhead than to continue to increase the FEC protection.
The figure below, obtained using the ICO tool, illustrates that it can be more efficient to use a lower FEC setting and a
lesser modulation rate. Ideally the channel will operate as far towards the upper left of this chart as possible. The Shannon
curve displays what is theoretically possible. The curves for the different modulation rates show the effect of increasing
the value of T for the FEC for each of the different modulation rates for the specified modulation profile parameters.
Because the lab chassis used to obtain the data in the figure below was provisioned with a very short cable plant, these
numbers approach the theoretical values listed above for SNR. They do not reflect real-world noise levels. In the 64 QAM
modulation profile, if the SNR of the plant is about 20 dB, then a high T value is required to limit the Packet Error Rate
(PER) to 0.1%. The highest bit rate one can achieve is about 8 Mbps. However, if we reduce the modulation to 32 QAM and
decrease the FEC T value, the bit rate goes up to 12 Mbps under the same conditions.
For practical reasons the minimum value of k must be at least 16. Because of this, if there are not 16 data bytes either to
be sent or remaining to be sent, then the modem must pad out this data to be 16 bytes. This especially comes into play for
IUC 1 where the request frame is 6 bytes. Therefore, to have even the minimal values for FEC of T = 1 and k = 16 for IUC 1,
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
314
Chapter 9: Upstream Cable Access Modules (UCAMs)
would mean that there must be 18 total bytes (k + 2T) required to transmit 6 bytes of data. Given this amount of overhead,
it is normally better to use a low order of modulation such as QPSK and no FEC for IUC 1, assuming the noise on the plant
allows this to work.
Figure 68: Maximum ATDMA Data Rate vs. SNR
The type of traffic that is sent in the upstream direction can affect the optimal FEC values also. For example, assuming
there is a lot of ACKs and small packets (i.e. 64-byte packets), then the FEC codeword length should be set so that there is
no need to pad out the remaining 16 bytes. Assuming a 6-byte MAC header, it would take 70 bytes to send the 64-byte
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
315
Chapter 9: Upstream Cable Access Modules (UCAMs)
packet. Also assuming BPI is enabled then there is an additional 5-byte extended header such that it would take 75 bytes
to send a 64-byte packet. Note, that the preamble is not included in FEC and should not be included in these calculations.
In general, the predominant packet size plus the associated overhead determines that the k value should not be a value
between 1 and 15; otherwise there is additional overhead in padding of the codeword.
In the case of a DOCSIS 2.0 upstream, the modulation profile will include an IUC 11. The IUC 11 is used for UGS data flows.
The thing that most commonly uses UGS data flows is VoIP. There are several different codecs that are used in the
industry; however, typically there is only one codec with one sampling period (5, 10 or 20 milliseconds) on a given cable
plant. This tends to cause all of the upstream UGS data packets to be of the same size. Knowing the size of these UGS data
packets, the value of k for the FEC should be such that no additional padding is required for FEC.
Preamble Lengths
The preamble length is something that is displayed in the show cable modulation-profile CLI command in the Pre Len
column. This value represents the number of bits that are in the preamble.
In general the preamble is transmitted as a QPSK symbol no matter what the modulation type for the IUC actually is. One
exception to this is that a 16 QAM TDMA upstream channel will use 16 QAM symbols or 4 bits per symbol.
The preamble length is used by the upstream receiver to decode the upstream burst even if the upstream burst is not
perfectly aligned with the proper spot in the upstream spectrum. The preamble helps to recognize where an upstream
burst actually begins, and is also used to perform equalization on the upstream burst, provided that the preamble is long
enough.
In general a longer preamble is desired for IUC 3, Initial Ranging, since this is the first time that the CMTS has heard from
this modem. Additionally, the extra equalization also helps in IUC3. The amount of gain for equalization does not normally
warrant the additional overhead in terms of length of the preamble especially in IUCs other than the ranging IUCs (IUCs 3
and 4).
The point where the PHY chip switches from simply recognizing the start of the preamble and making sure that it has the
correct pattern to recognizing when extra symbols are used for equalization depends upon several parameters. Some of
these parameters are not currently configurable and require very detailed knowledge of how the PHY chip operates. As
such, this paper will not explain all of the details behind the following numbers. The point where equalization begins for
preambles using QPSK on IUCs 3 and 4 is currently after 136 bits. For IUCs 3 and 4 when 16 QAM is used, equalization
begins after 272 bits. For non-ranging IUCs (any IUC except IUCs 3 and 4) for preambles using QPSK, equalization begins
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
316
Chapter 9: Upstream Cable Access Modules (UCAMs)
after 132 bits. For non-ranging IUCs (any IUC except 3 and 4) for preambles using 16 QAM, equalization begins after 264
bits.
If there is a lot of impulse noise in the upstream channel, then it is probably worth using shorter preambles to lower the
probability that an impulse will actually hit a preamble. Note that if an impulse actually hits a preamble that most likely the
entire frame will be discarded because of a bad preamble. Part of the reason behind this is that the preamble is not
protected with FEC. As such with a lot of impulse noise on the upstream channel, the preamble lengths should be
shortened.
Because of the way that the PHY receiver works in the CMTS, for an SCDMA channel type, there is a slight benefit that can
be gained if the preamble length is a multiple of the SCDMA frame size in symbols. The default value for the SCDMA frame
size is sixteen symbols. Since the preamble for SCDMA is always QPSK, which is two bits per symbol, there is a slight benefit
if the preamble is a multiple of 32.
Differential Encoding
Differential encoding can be enabled since it is a feature in the DOCSIS RFI specifications; however, there is no real gain to
be had in doing this. This mode is rarely used in the field; therefore we recommend that you leave Differential Encoding
disabled. (For more information, see Cable Modem Specifications.)
Scrambler Seeds
This is a value that tends to be tied to the PHY hardware. These values have already been optimized by the PHY
manufacturer. Therefore, do not change the values that come with the default modulation profiles for the scrambler seed.
Maximum Burst Size
This value is contained is something that is displayed in the show cable modulation-profile CLI command in the
Max(imum) Bur(st) Size column. This value is in terms of maximum number of minislots that may be used by the associated
IUC. A value of 0 for the maximum burst size means that there is no limitation on the size at least in the modulation profile.
Note: The short data grant (IUC 5) and the advanced PHY short data grant (IUC 9) must have non-zero values.
It is important to understand the type of traffic that is to be sent upstream and the relative priority of that traffic when
adjusting this parameter. For example, if there is VoIP traffic on an upstream that uses a TDMA channel type, then the VoIP
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
317
Chapter 9: Upstream Cable Access Modules (UCAMs)
traffic should be given a higher priority in terms of FEC protection. Assuming that there is more FEC associated with a short
data grant (IUC 5) than with a long data grant (IUC 6), then the maximum burst size should be set such that the higher
priority traffic, in this case VoIP, uses the IUC with the higher level of FEC protection.
When the modulation profile is for an ATDMA or an SCDMA channel, the modulation profile will contain the UGS IUC 11.
The VoIP traffic will tend to use this IUC on a DOCSIS 2.0 upstream channel. In this case make sure you do not include the
UGS data packets into the process of determining the best value for the maximum burst size.
Guard Time Size
The guard time size is given in the Guard Time Size column in the show cable modulation-profile CLI command. The
guard time size is related to processing delays with a non-SCDMA upstream channel and is defined to be zero for an
SCDMA upstream channel. The times for non-SCDMA channels are already optimized based upon the hardware to be as
small as possible without losing data. If the numbers are increased, then upstream bandwidth is lost without any additional
gains. Changing the default is not recommended.
Shortened Last Codeword
A codeword is specified by the k parameter for FEC. Assuming the data packet is not an even multiple of k, then the last
codeword used to transmit a data packet will have less than k bytes to send. This parameter controls the format of that
last codeword. The last codeword must always contain at least 16 bytes whether shortened or not. This parameter control
whether or not the last codeword must contain k bytes or if it can contain between 16 and k bytes. If the last codeword
can contain between 16 and k bytes, the last codeword is allowed to be shortened and this parameter has a values of true
(T). If the last codeword must be padded out to contain k bytes, then the shortened last codeword value is set to false (F).
The shortened last codeword is displayed in the LCS (Last Codeword Shortened) field in the show cable modulationprofile CLI command.
In general having the shortened last codeword set to true will improve upstream efficiency in that there is less overhead
associated with the additional padding in the last codeword. The default modulation profiles in general for IUCs 1, 3 and 4
do not have this set to true, simply because the messages sent on IUCs 1, 3 and 4 are of a fixed length and the values for k
are already optimized for this length. As such there is no benefit to turning on shortened last codeword with the default
modulation profiles unless the value of k is changed for these modulation profiles to a non-optimal value.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
318
Chapter 9: Upstream Cable Access Modules (UCAMs)
Scrambler Enable
The scrambler enable is shown in the show cable modulation-profile CLI command in the Scramb En column. The
scrambler might be better called a randomizer. Having this field set to true enables hardware that randomizes the bit
stream to avoid a long pattern of either zeroes or ones. This helps in the overall transmission efficiency of the entire
system. In general this should always be set to true (T).
ATDMA Interleaver Depth
With an ATDMA upstream channel, there is the capability of using an interleaver that is not available in the DOCSIS 1.X
version of TDMA. This interleaver works on a byte basis. When enabled, the interleaver will change the order in which
bytes are transmitted. This has a side effect of causing additional latency in the upstream direction. The benefit is the
additional protection against impulse noise. In general an impulse will corrupt some number of bytes that are transmitted
consecutively with time. If the bytes are all from the same FEC codeword, and if FEC is not able to correct for this problem,
then the data is lost. However, by ordering the transmission of bytes such that bytes from multiple FEC codewords are
intermixed, the same impulse will hit fewer bytes from the same FEC codeword giving a better chance that FEC will be able
to recover the corrupted data.
The ATDMA interleaver depth is shown in the show cable modulation-profile CLI command in the Atdma Int Depth column.
This value controls how this interleaver works. A value of 0, puts the interleaver into a dynamic mode such that the
interleaver adjusts the way that it interleaves the data based upon the size of the data to transmit. A value of 1, turns off
this interleaver. Any other value directly controls how many FEC codewords are interleaved together. When directly
controlling how many FEC codewords are interleaved together, the value has a range from 2 to the floor (2048 / (k + 2T))
where k and T are the FEC parameters described in the FEC section of this document.
The default modulation profiles use the dynamic mode of operation in order to get as much protection from impulse noise
as possible. If a system has extremely tight restrictions in terms of upstream latency, then the amount of interleaving may
be changed to either be off or of a lesser amount. This comes at the cost of reduced impulse noise immunity.
ATDMA Interleaver Block Size
This is another control for the ATDMA byte interleaver and is shown in the show cable modulation-profile CLI command in
the Atdma Int Block field. According to the DOCSIS 2.0 RFI specification, both the CMTS and a cable modem must contain
2048 bytes of memory to perform the ATDMA byte interleaving. This parameter controls how much of that memory is
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
319
Chapter 9: Upstream Cable Access Modules (UCAMs)
used. The parameter can vary from 2 * (k + 2T) up to 2048 where k and T are the FEC parameters described in the FEC
section.
When the ATDMA byte interleaver is in the dynamic mode of operation, this parameter should really be left at the 2048
value; otherwise, the byte interleaver will perform sub-optimally. Note, the dynamic mode of operation and a block size of
2048 are used in the default modulation profiles.
Preamble Type
An upstream channel using either ATDMA or SCDMA, has the capability to change the power level at which the preamble is
transmitted. This is displayed in the show cable modulation-profile CLI command in the Preamble Type column. There are
two different values that are possible for the preamble power levels. The first value is QPSK0 which corresponds to the
transmit levels that are used by a DOCSIS 1.x upstream channel. The second value is QPSK1, which uses a higher power
level. For actual differences in the power levels, see the RFI specification for DOCSIS 2.0 or later.
By transmitting at a higher power level, there are times when a preamble of type QPSK1 will be heard when the QPSK0
preamble type would not be heard. Therefore QPSK1 is used for the default modulation profiles.
SCDMA TCM Enable
SCDMA upstream channels can use Trellis Coded Modulation (TCM). The Scdma Tcm En column of the show cable
modulation-profile command shows whether it is enabled. Theoretically there is a slight gain to be had by using TCM.
However, in practice there are sometimes problems with TCM. There are cases where TCM will actually compound
problems and cause more errors than it solves. Consequently, these issues tend to offset the possible gain. TCM is not
enabled in the default modulation profiles.
SCDMA Interleaver Step Size
This parameter controls how the interleaver actually interleaves symbols in an SCDMA frame. It appears in the show cable
modulation-profile command in the Scdma Int Size column. According to the DOCSIS RFI specification, this parameter
has a value from 1 to 31. The PHY chip that is used places an additional restriction in the value must be at least 1 and has a
maximum of SCDMA frame size minus 1. The SCDMA frame size is also called the SCDMA spreading interval.
In general increasing this number will helps reduce impulse noise. The cost associated with increasing this value is
additional latency. The default modulation profiles have a value of 5 for this parameter.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
320
Chapter 9: Upstream Cable Access Modules (UCAMs)
SCDMA Spreader Enable
According to the DOCSIS RFI specification, if SCDMA is enabled, IUC 3 must have the spreader off and the IUCs 1, 9, 10 and
11 must have the spreader on. This only leaves IUC 4. The specification states that it can have the spreader on or off.
However, the current version of the software only supports spreader off for IUC 4. Therefore, all of the values for the
spreader must remain the same as what is currently in the default modulation profiles. This is shown in the show cable
modulation-profile command in the Scdma Sp En column.
SCDMA Codes Per Subframe
This parameter is used in with the SCDMA interleaver step size to determine how data is interleaved with SCDMA. This
parameter is shown in the show cable modulation-profile command in the Scdma Sub Code column.
When interleaving with SCDMA, preamble and TCM-encoded symbols are interleaved in one way and non-TCM-encoded
symbols are interleaved in another. This parameter has the greatest effect on the preamble and TCM-encoded symbols.
Since in general TCM is not recommended, this simply leaves the preamble symbols. As such this parameter does not tend
to have much effect on the overall performance of the system.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
321
Chapter 10
Control Complex Redundancy
Overview
A control complex consists of one SCM and its associated RCM. The SCM in slot 19 and the RCM in slot 17 make up the
control complex in a simplex system. In order to have control complex redundancy (CCR) the C4/c CMTS must be a duplex
system. In a duplex CMTS both control complexes are equipped; one is active the other is standby.
CCR ensures high reliability for system-wide Operations Administration Maintenance and Provisioning (OAM&P), switching,
and routing. The control complex redundancy feature provides 1+1 active/standby redundancy between two pairs of
SCM/RCM modules. The failure of an active SCM/RCM pair immediately causes a failover to the standby SCM/RCM pair.
Key characteristics of control complex redundancy include:
Reduced customer impact on any SCM or RCM failure (hardware or software)
Hot standby SCM/RCM pair with complete replication of configuration and customer data
Fault correlation between active and standby SCM/RCM pairs
Software infrastructure support for replication of software components between active and standby SCM/RCM pairs
Note: Routing protocols restart after a control complex failover. Convergence time varies based upon the specific
configuration.
For a summary of the types of SCM cards, see System Control Module (SCM) (page 165).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
322
Chapter 10: Control Complex Redundancy
Add Control Complex
Use the following procedure to add a redundant control complex. This procedure assumes that the original control
complex (i.e. the SCM in slot 19 and the RCM in slot 17) are in service.
To add a Control Complex (Change from Simplex to Duplex)
Note: Ensure that your system is committed before starting this procedure. Use the reload commit command if
necessary.
Caution: Do not insert the SCM 20 or RCM 18 modules until instructed to do so later in this procedure.
1. Configure a second SCM slot:
configure slot 20 type SCM
2. Configure a second RCM slot:
configure slot 18 type RCM
3. Put slots 20 and 18 in the administrative up state:
configure slot 20 no shutdown
configure slot 18 no shutdown
4. (Optional) If using out-of-band management, configure the IP address of the second SCM in slot 20:
configure interface ethernet 20/0 ip address <ip address> <subnet mask>
In the next step you assign the out-of-band ethernet active IP address (19/0 and 20/0). It remains the active IP even
after a failover.
Note: If you are currently using telnet to access the SCM 19, you will be disconnected and have to log back in to the
system.
5. (Optional) If SCM 19 does not have an active IP address, assign one using the following command:
configure interface ethernet 19/0 active ip <address> [<subnet mask>]
Where: valid slot number = 19 or 20, either can be used to set the active IP.
In this case use slot 19 because the SCM is not yet present in slot 20.
If the IP mask is not provided, it defaults to the mask of the SCM interface ip address.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
323
Chapter 10: Control Complex Redundancy
6. Save the duplex configuration to memory:
write memory
7. Reset the chassis:
configure reset system
8. Wait for slots 17 and 19 to go in-service.
9. Insert an SCM card in slot 20 and the associated Even SCM Physical Interface Card (PIC) at the rear of the chassis.
(Optional) If applicable to your configuration, add the Ethernet cable to either the front of the SCM card or at the rear
of the chassis.
10. Insert an RCM card in slot 18.
The SCM and RCM cards in slots 20 and 18 respectively are initialized automatically and come into service when they
are inserted.
11. Install the crossover connector between the RCMs. See the Router Control Module (RCM) chapter for more details.
Note: It may take up to 20 minutes for the CMTS to synchronize the active and the standby SCM.
12. Verify that new SCM and RCM are standby:
show linecard status
13. Save your configuration changes by entering:
write memory
14. To establish the current image as the active image, enter:
reload commit
Caution: If you wish to revert to a simplex chassis from duplex, first contact ARRIS Technical Support.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
324
Chapter 11
Basic Bring-up Procedure for the C4 CMTS
Introduction ..................................................................................... 325
Before You Begin .............................................................................. 326
Bring-up Procedures......................................................................... 330
Verification Steps ............................................................................. 340
IPv6 Configuration (Optional) .......................................................... 348
IP Address Prefixes and Subnets ...................................................... 348
Introduction
This chapter provides the basic procedure to bring up a C4 CMTS system for Release 8.x. This is not a software upgrade
procedure: it assumes that the chassis is not yet in service. Installing the chassis, modules, and cards and configuring the
system are addressed in this chapter. It is advisable to read through this information and become familiar with the order of
operation before you begin.
This chapter is based on a minimal configuration for a duplex system. The minimal configuration and examples used in this
chapter will consist of two System Control Modules (SCMs), two Router Control Modules (RCMs), two 24U Cable Access
Modules (CAMs) and two 32D CAMs.
Most systems will be configured in redundant mode which means that each of the boards will have a spare or be part of a
sparing group. See Control Complex Redundancy (page 322) and CAM Sparing for more information.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
325
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Before You Begin
In order to properly set up the C4 CMTS for Release 8.0, several items are required to make the installation run smoothly.
These include:
1. Chassis installation and powering
2. Hybrid Fiber Coax (HFC) network connectivity
3. The IP network plan for this C4 CMTS
4. Set up of the provisioning environment for the new C4 CMTS
Chassis Installation and Powering
It is assumed that the C4 CMTS has been mounted in a rack in the head-end and cabled for power prior to starting the
Release 8.x C4 CMTS installation. Do not power up the chassis until told to do so in the procedure.
DC Power — For additional information on power on the system, refer to the C4 CMTS User Guide chapter on
"Installing/Replacing Modules and Initial System Configuration."
HFC Network Connectivity
A useful tool for planning the C4 CMTS configuration is the Network Connectivity Plan, as shown in the figure below. This
plan details the physical connections needed for the C4 CMTS to reach the HFC plant as well as how the C4 CMTS will be
connected to the Operator Network for Internet Access and provisioning, monitoring, and control.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
326
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Figure 69: Network Connectivity Diagram
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
327
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
IP Network Plan
A network diagram is used to illustrate and document your specific network. The figure below is an example of a basic
network with sample IP addresses displayed. The IP addresses shown here are also used in subsequent examples in this
chapter. (See the blank form for actual use at the end of this section.)
Figure 70: Network Diagram Example
Configuration of Back Office Servers
The following servers must be correctly provisioned to support the DOCSIS and non-DOCSIS devices and services.
DHCP Server — A Dynamic Host Configuration Protocol (DHCP) server is needed to provide IP addresses to the modems
and Customer Premise Equipment (CPE).
The following options are required for registering modems:
Option 2 — time offset
Option 3 — router (IP address of CAM primary address)
Option 4 — time server (IP address of the time server)
Option 66 — boot server host name (IP address of the TFTP server)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
328
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Option 67 — bootfile name (name of the modem configuration file)
TFTP Server — This server is required to send the modem configuration file to the modem.
Time of Day Server — This server provides the time of day to the modems.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
329
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Bring-up Procedures
The following is a high-level list of the steps of this procedure:
see "1. Install Cards, Rear PICs, Filler Panels, PCMs, and Fans (page 331)
see "2. Set Up Console Cable (page 332)
see "3. Power Up the Chassis (page 333)
see "4. Configure Slots (page 333)
see "5. Configure RCM Ethernet Connections (page 333)
see "6. Configure MAC Domains (page 333)
see "7. Configure Downstream Parameters (page 334)
see "8. Configure Upstream Parameters (page 335)
see "9. Configure Fiber Node and Topology (page 337)
see "10. Configure a Dynamic Bonding Group (page 337)
see "11. Configure RCC Management (page 337)
see "12. Local Authentication (page 338)
see "13. Managing the C4 CMTS (page 338)
see "14. Configure the SNMP (page 339)
see "15. Configure Clock (page 340)
see "16. Save the Configuration (page 340)
see "17. Cable CAMs and RCM (page 340)
see "18. Configure/Verify Back Office Systems (page 341)
see "19. Verify the C4 CMTS Configuration (page 341)
see "20. Verify Modem Registration (page 343)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
330
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
see "IPv6 Configuration (Optional) (page 348)
A C4 CMTS with one 32D CAM, one 24U CAM, one RCM, and one SCM is configured to serve a set of 4 optical nodes. Both
DOCSIS 2.0 and 3.0 CMs will be put into service. The DOCSIS 3.0 CMs are provisioned with IPv6 addresses, while the
DOCSIS 2.0 CMs obtain IPv4 addresses. All CPE are provisioned as IPv4 devices.
1. Install Cards, Rear PICs, Filler Panels, PCMs, and Fans
The C4 CMTS chassis hardware is configured as follows:
The chassis has 21 slots that can be filled with various modules
Slots are numbered from 0-20 counting from left to right
Slots 19 and 20 are reserved for SCMs
Slots 17 and 18 are reserved for RCMs
The 32D CAM provides downstream channels for as few as one or as many as sixteen different MAC domains.The 32D CAM
is designed to run in the client-card slots to the right side of the chassis, beginning with slot 15, then 14, and so on working
to the left. It is advisable to begin with slot 14, reserving slot 15 for later use as a spare 32D CAM.
The 24U CAM is responsible for upstream RF reception.
The 24U CAMs are designed to be installed from left to right in the chassis, beginning with slot 0.
For this configuration example, an SCM is installed in Slot 19, and RCM in slot 17, and a 32D CAM will be installed in slot 14.
A 24U CAM will be installed in slot 1. In this example, blank slots are available for additional cards. Refer to the figure
below to view the sample configuration.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
331
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
The spare Physical Interface Cards (PICs) for the 24U and 32D CAMs are different and are not interchangeable.
Figure 71: C4 CMTS Slot Diagram
2. Set Up Console Cable
The operator console is necessary for the initial power up and configuring of the C4 CMTS. You may use an asynchronous
terminal or a PC with asynchronous terminal emulation software, such as HyperTerm or Teraterm.
The C4 CMTS is shipped with a black roll-over cable that has a 9-pin connector on one end and an RJ-45 connector on the
other. The RJ-45 end plugs into the front of the SCM card into the RS-232 port. The other end plugs into a computer or
terminal server.
The default connection settings for the computer COM port are:
9600 Baud rate
8 data bits
No parity
1-stop bit
Flow control Xon/Xoff
Once a successful connection is made, you should get a login prompt.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
332
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
3. Power Up the Chassis
At this point, power up the chassis. The SCM and RCM are configured automatically and come into service. As the C4 CMTS
is coming up, the system output displays the system activity.
4. Configure Slots
Use the following commands for basic slot configuration:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
slot
slot
slot
slot
slot
slot
slot
slot
slot
slot
slot
slot
14 type 32DCAM-B
15 type 32DCAM-B
0 type 24UCAM
1 type 24UCAM
0 spare-group 0 auto
1 spare-group 0
15 spare-group 15 auto
14 spare-group 15
14 no shutdown
15 no shutdown
0 no shutdown
1 no shutdown
5. Configure RCM Ethernet Connections
Enter the following CLI commands to configure the RCM ethernet ports:
configure
configure
configure
configure
interface
interface
interface
interface
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
17/0
17/0
18/0
18/0
ip
no
ip
no
address 192.168.176.2 255.255.255.0
shutdown
address 192.168.177.2 255.255.255.0
shutdown
This example uses static routing. To apply a default route to the RCMs enter the following commands:
configure ip route 0.0.0.0 0.0.0.0 192.168.176.1
configure ip route 0.0.0.0 0.0.0.0 192.168.177.1
6. Configure MAC Domains
This section configures the MAC Domain on your system.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
333
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Note: Each MAC domain must consist of channels from exactly one 32D CAM and exactly one 24U CAM. In other words,
the MAC domain cannot include ports from more than one 32D CAM or from more than one 24U CAM.
Configure and assign the MAC domain:
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
1
1
1
1
1
description Mac1
cable cm-ip-prov-mode ipv4only
ip address 192.168.180.1 255.255.255.0
cable helper-address 10.43.210.1
no shutdown
CAUTION: If an IPv4 or IPv6 address on a cable interface is changed or removed, or if a subnet mask on a cable interface is
changed, then be well aware that all cable modems and CPEs using addresses on the changed/removed IPv4/IPv6 subnet
will be stranded. They will have no communication with other cable modems or CPEs. The stranded cable modems and
CPEs will remain stranded until they acquire IPv4/IPv6 addresses on a subnet of that interface. Also, CPEs behind a cable
modem that is stranded that attempt to acquire an IP address using DHCP will not have access to the DHCP server. This
modification or removal includes any IPv4/IPv6 address on a cable interface, either primary or secondary. When an IPv4 or
IPv6 address or subnet mask is modified or removed from a cable interface, all IPv4/IPv6 cable modems on that subnet
should be reset.
7. Configure Downstream Parameters
This section configures a single 32D CAM in slot 14. The 32D has the following characteristics:
4 physical connectors: each one can output 8 downstream channels
The downstream channel frequencies are grouped eight per connector. For each connector there is an 80 MHz
frequency range available for those four channels.
DS carriers 0-7 are associated with connector D0
DS carriers 8-15 are associated with connector D1
DS carriers 16-23 are associated with connector D2
DS carriers 24-31 are associated with connector D3
To configure the downstream interfaces, enter:
configure interface cable-downstream 14/0 cable cable-mac 1
configure interface cable-downstream 14/1 cable cable-mac 1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
334
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/2
14/3
14/4
14/5
14/6
14/7
cable
cable
cable
cable
cable
cable
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
1
1
1
1
1
1
To configure the 32D CAM downstream interfaces to the cable-mac, enter:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
cable frequency
cable frequency
cable frequency
cable frequency
cable frequency
cable frequency
cable frequency
cable frequency
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
no shutdown
321000000
327000000
333000000
339000000
345000000
351000000
357000000
363000000
8. Configure Upstream Parameters
This section provides a procedure to configure four upstream channels that are connected to the four nodes. Each
upstream in this example is configured with the same frequency and modulation profile. Each upstream has a unique
upstream channel id and is supervised by all four downstream channels.
Note: On the 24U CAM, upstreams 0 - 11 must be assigned to even connectors; upstreams 12 - 23 must be assigned to odd
connectors.
To configure the upstream channels, enter:
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/0
1/1
1/2
1/3
1/0
1/1
1/2
1/3
cable
cable
cable
cable
cable
cable
cable
cable
cable-mac
cable-mac
cable-mac
cable-mac
connector
connector
connector
connector
1
1
1
1
0
0
0
0
C4® CMTS Release 8.3 User Guide
335
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/0 cable frequency 10000000
1/1 cable frequency 20000000
1/2 cable frequency 30000000
1/3 cable frequency 40000000
1/0 cable supervision 14/0
1/0 cable supervision 14/1
1/0 cable supervision 14/2
1/0 cable supervision 14/3
1/0 cable supervision 14/4
1/0 cable supervision 14/5
1/0 cable supervision 14/6
1/0 cable supervision 14/7
1/1 cable supervision 14/0
1/1 cable supervision 14/1
1/1 cable supervision 14/2
1/1 cable supervision 14/3
1/1 cable supervision 14/4
1/1 cable supervision 14/5
1/1 cable supervision 14/6
1/1 cable supervision 14/7
1/2 cable supervision 14/0
1/2 cable supervision 14/1
1/2 cable supervision 14/2
1/2 cable supervision 14/3
1/2 cable supervision 14/4
1/2 cable supervision 14/5
1/2 cable supervision 14/6}
1/2 cable supervision 14/7
1/3 cable supervision 14/0
1/3 cable supervision 14/1
1/3 cable supervision 14/2
1/3 cable supervision 14/3
1/3 cable supervision 14/4
1/3 cable supervision 14/5
1/3 cable supervision 14/6
1/3 cable supervision 14/7
1/0 no shutdown
1/1 no shutdown
1/2 no shutdown
1/3 no shutdown
1/0.0 no shutdown
1/1.0 no shutdown
1/2.0 no shutdown
1/3.0 no shutdown
C4® CMTS Release 8.3 User Guide
336
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
9. Configure Fiber Node and Topology
This section provides commands to configure the fiber node data and assign the channels that were defined in the
previous procedures to those fiber nodes.
Configure fiber node 1:
configure cable fiber-node FN1
configure cable fiber-node FN1 cable-upstream 1/0 1/1 1/2 1/3
configure cable fiber-node FN1 cable-downstream 14/0 14/1 14/2 14/3 14/4 14/5 14/6 14/7
10. Configure a Dynamic Bonding Group
This section is provides the commands to create the bonding groups. There are two ways to configure bonding groups:
dynamic and static. This example uses only dynamic. (See Channel Bonding (page 685) for more information.) Note that
the RCC is configured here as well.
Dynamically configure the downstream bonding group by entering:
configure interface cable-mac 1 cable downstream-bonding-group dynamic enable
configure interface cable-mac 1 cable dynamic-rcc
configure interface cable-mac 1 cable verbose-cm-rcp
To dynamically configure the upstream bonding group, enter:
configure interface cable-mac 1 cable upstream-bonding-group dynamic enable
configure interface cable-mac 1 cable mult-tx-chl-mode
11. Configure RCC Management
In this Basic Bring-up, the RCC configuration is created while configuring bonding groups in the procedure above.
DOCSIS 3.0 allows for two methods of configuring the CM Receive Channel Configuration (RCC). Like bonding group
configurations, there can be static and dynamic RCC configurations in Release 7.x and later.
The Static method consists of explicitly defining all the different combinations that could occur on any given node with
specific downstream channels. For an example of static RCC configuration, see Configuration Examples for Static RCC (page
697).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
337
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
12. Local Authentication
To create a new user on the system, enter:
configure username tempuser password <password>
Use the default method list (local database) by entering:
configure
configure
configure
configure
enable password <password>
authentication default local
line vty 0 15 authentication default login-authentication
line vty 0 15 authentication default enable-authentication
13. Managing the C4 CMTS
Managing consists of various system administration tasks, including those related to accounting, security, and
configuration. This is accomplished through in-band or out-of-band management or both. Management functions can use
telnet, SSH, SNMP, and other protocols.
Among the other management protocols are TOD, IPDR, DNS, TACACS, RADIUS, Syslog, NTP, and Event Messaging and
COPS for PacketCable.
In-band Management — This means that the telnet/ssh/snmp sessions are carried through the Ethernet interfaces on the
RCM line card.
Pro: Access Control Lists (ACLs) can be applied to increase security
Con: In-band management uses the same interfaces as all the modem traffic.
To provision in-band management, permit and define a standard ACL by entering:
configure access-list 1 permit any
configure interface gigabitEthernet 17/0 ip scm access-group 1
configure ip scm access
Out-of-band Management — This means that the telnet/snmp sessions are carried through the Ethernet interfaces on the
SCM card, so that management traffic is not being carried on the same channels as data traffic.
Pro: The IPs can be put on a private network and only management traffic is carried on these links
Con: ACLs can not be applied to these interfaces. The interface is 10MBPS and half duplex. The C4 CMTS requires a reboot
if these need to be changed.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
338
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
To provision out-of-band management, enter the following commands:
To configure SCM slot 19 IP address and subnet mask:
configure interface ethernet 19/0 ip address 10.44.101.1 255.255.255.248
To configure the active SCM IP address and subnet mask for SCM 19:
configure interface ethernet 19/0 active ip 10.44.101.3 255.255.255.248
To configure SCM slot 20 IP address and subnet mask:
configure interface ethernet 20/0 ip address 10.44.101.2 255.255.255.248
To configure the active SCM IP address and subnet mask for SCM 20:
configure interface ethernet 20/0 active ip 10.44.101.3 255.255.255.248
To configure the SCM default gateway:
configure ip route vrf management 0.0.0.0 0.0.0.0 10.44.101.6
To save the configuration, enter the write memory command.
Note: The chassis reboot in the following step is only required only if you are using the Out-of-Band Management
configuration and changing the IPs.
Save the changes and reboot the system (if Out-of-Band management is configured) by entering:
write memory
configure reset system
14. Configure the SNMP
The following command sequence enables the Simple Network Management Protocol (SNMP) to work. You should change
community strings for security purposes.
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
community public security rotesting
community private security rwtesting
user rotesting rotesting v1
user rwtesting rwtesting v1
user rotesting rotesting v2c
user rwtesting rwtesting v2c
context ""
group rotesting v1 read docsisManagerView
group rwtesting v1 read docsisManagerView write docsisManagerView
group rotesting v2c read docsisManagerView notify docsisManagerView
group rwtesting v2c read docsisManagerView write docsisManagerView
C4® CMTS Release 8.3 User Guide
339
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
configure snmp-server view docsisManagerView 1.3.6.1 included
configure snmp-server group rotesting v2c notify docsisManagerView
configure snmp-server group rotesting v1 notify docsisManagerView
15. Configure Clock
To set the network timing synchronization protocol, enter the following commands:
configure ntp server 10.44.101.9
configure clock timezone America/Chicago
configure clock network ntp
For more information on the purpose and syntax of these commands, refer to the Command Line Descriptions (page 1127)
to find the command reference page for each command.
16. Save the Configuration
Write the configuration to memory to save the configurations:
write memory
Verification Steps
This section provides the procedures to complete the bring-up of your system.
17. Cable CAMs and RCM
In this step, the Operator needs to connect the cables to the CAMs, RCM, and SCM if out of band management is
configured. In this example, a single cable from the 16D PIC connected to connector 1 will be cabled to provide service to
nodes 1-4. Another 4 cables will be connected to the first four connectors on the 12U PIC on the rear of the chassis. These
individual upstreams will then be connected individually to the four nodes per the network diagram on IP Network Plan
(page 328).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
340
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
18. Configure/Verify Back Office Systems
The provisioning servers and other Back Office servers and data collectors should be configured to allow for the first
modem to receive IP and CM configurations.
Since different offices use various provisioning servers and environments, this procedure is customer-specific and sitedependent.
19. Verify the C4 CMTS Configuration
A number of commands can be used to verify the installation and configuration of the system at this point.
Verify the slot provisioning by entering the following command to show the slot provisioning:
show linecard status
The following is an example of the output:
show linecard status
Chassis Type: C4
Slot Description
0
1
14
15
17
18
19
20
CAM
CAM
CAM
CAM
RCM
RCM
SCM
SCM
(0D, 24U)
(0D, 24U)
(32D, 0U)
(32D, 0U)
A
B
A
B
Admin
State
Up
Up
Up
Up
Up
Up
Up
Up
Oper
State
IS
IS
IS
IS
IS
IS
IS
IS
Duplex
State
Standby
Simplex
Simplex
Standby
Standby
Active
Standby
Active
Serial
Number
11283CTU0029
11283CTU0034
08113CSD0005
08113CSD0023
08133RCM0021
09433RCM0040
06483CBM0093
06063CBM0071
HW Version
CAM-01240W/C04
CAM-01240W/C04
CAM-20032W/E02
CAM-20032W/E02
RCM-01000W/D02
RCM-01000W/E02
SCM-02440W/B06
SCM-02440W/B06
Prov/Det
Type
CAM/CAM
CAM/CAM
DMM/DMM
DMM/DMM
RCM/RCM
RCM/RCM
SCM/SCM
SCM/SCM
Show the fiber node database and the topology information:
show cable fiber-node <name>
The following is an example of the output:
show cable fiber-node
Cable
Fiber Node
MAC
mCMsg
---------------- ----- ----FN1
1
2
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
mDSsg/
mUSsg
-----D1
Ports
-------------------14/0
14/1 14/2
14/3
14/4
14/5
14/6
14/7
C4® CMTS Release 8.3 User Guide
341
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
FN1
1
2
U1
1/0
1/1
1/2
1/3
* Indicates that downstream channel is not primary-capable.
Verify the MAC Domain configuration:
show interface cable-mac <mac>
What follows is an example of the show interface cable-mac 1 output:
show interface cable-mac 1 brief
Cable-mac 1
=============
Cable
Oper
DS Port Mac Conn State
14/0
1
0
IS
14/1
1
0
IS
14/2
1
0
IS
14/3
1
0
IS
14/4
1
0
IS
14/5
1
0
IS
14/6
1
0
IS
14/7
1
0
IS
US PORT
1/0
1/1
1/2
1/3
Cable
Oper
Mac Conn State
1
0
IS
1
0
IS
1
0
IS
1
0
IS
Annex
B(US)
B(US)
B(US)
B(US)
B(US)
B(US)
B(US)
B(US)
Freq(Hz)
321000000
327000000
333000000
339000000
345000000
351000000
357000000
363000000
Chan
Type
tdma
tdma
tdma
tdma
Freq(Hz)
10000000
20000000
30000000
40000000
Mod Power
Type (.1dBmV)
q256
490
q256
490
q256
490
q256
490
q256
490
q256
490
q256
490
q256
490
Channel
Width
3200000
3200000
3200000
3200000
Mini
Slot
4
4
4
4
Spare
Group
-
LBal
Group
16781312
16781312
16781312
16781312
16781312
16781312
16781312
16781312
Mod Power Spare
Prof (dBmV) Group
2
0
2
0
2
0
2
0
-
LBal
Group
16781312
16781312
16781312
16781312
If you desire more detailed information on the cable-mac, use show interface cable-mac <number> instead.
To display the supervisory downstream for the upstream, enter:
show cable supervision
An example of the show interface cable supervision output:
show cable supervision
MAC
-----
US
-------
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
DS
-----
Method
-----------
C4® CMTS Release 8.3 User Guide
342
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1/0
1/0
1/0
1/0
1/0
1/0
1/0
1/0
1/1
1/1
1/1
1/1
1/1
1/1
1/1
1/1
1/2
1/2
1/2
1/2
1/2
1/2
1/2
1/2
1/3
1/3
1/3
1/3
1/3
1/3
1/3
1/3
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
14/0
14/1
14/2
14/3
14/4
14/5
14/6
14/7
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
20. Verify Modem Registration
For status on a specific cable modem, enter:
show cable modem detail <mac address>
An example of output for the show
cable modem detail command:
show cable modem detail 001d.cdf9.35f8
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
343
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
14/7-1/1
CM 001d.cdf9.35f8 (Arris) D3.0 State=Operational D1.1/tdma PrimSID=8192
Cable-Mac= 1, mCMsg = 2
mDSsg = 1
mUSsg = 1 RCP_ID= 0x0010000008 RCC_Stat= 1,
RCS=0x01000001 TCS=0x01000001
Timing Offset=770
Rec Power= 0.00 dBmV Proto-Throttle=Normal dsPartialServMask=0x00000000
usPartialServMask=0x00000000
Uptime= 0 days 12:37:18 IPv4=192.168.180.9
cfg=basic.bin
LB Policy=0 LB Group=16781312
Filter-Group CM-Down:0
CM-Up:0
Privacy=Ready Ver=BPI Plus Authorized
DES56 Primary SAId=8192 Seq=2
MDF Capability= GMAC Promiscuous(2) MDF Mode= MDF Disabled(0)
u/d
SFID
SID State Sched
Tmin
Tmax
DFrms
DBytes
CRC
HCS Slot/Ports
uB
3
8192 Activ BE
0
2000000
2077
241735
0
0
1/0,1,2,3
dB
4
*2 Activ
0
2000000
1568
157631
14/0,1,2,3,4,5,6,7
L2VPN per CM: (Disabled)
Current CPE=1, IPv4 Addr=1, IPv6 Addr=0
Max CPE=16, IPv4 Addr=32, IPv6 Addr=64
CPE
001d.cdf9.35fa Filter-Group:Up=0 Down=0 Proto-Throttle=Normal IPv4=192.168.180.10
To display the status of the bonding group for a given MAC address, enter:
show cable bonding-group-status
An example of the show cable bonding-group-status output:
show cable bonding-group-status
Cable
mDSsg/
-mac chSetId
mUSsg
CfgId
----- ---------- ------- ------1 0x01000001
D1
dynamic
1 0x01000001
U1
dynamic
AttrMask
--------------
An example of the show cable rcc-status output:
show cable rcc-status verbose
Cable
-mac
1
RCP-id
0010000008
Module: 1
CM-chan
1
2
3
4
5
6
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Stat
RCC ID
ChanSetId
dyn
1 0x1000001
MinCFreq:321000000
Downstream Frequency
14/7
363000000
14/0
321000000
14/1
327000000
14/2
333000000
14/3
339000000
14/4
345000000
RCC-Status
Valid
ModConnID:0
Primary
Primary
Capable
Capable
Capable
Capable
Capable
C4® CMTS Release 8.3 User Guide
344
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
7
8
14/5
14/6
351000000
357000000
Capable
Capable
For a more detailed report, use the show cable rcc-status verbose command:
show cable rcc-status verbose
Cable
-mac
1
RCP-id
0010000004
Module: 1
CM-chan
1
2
3
4
Stat
RCC ID
ChanSetId RCC-Status
dyn
36 0x1000002 Valid
MinCFreq:621000000
ModConnID:0
Downstream Frequency Primary
14/2
633000000 Primary
14/0
621000000 Capable
14/1
627000000 Capable
14/3
639000000 Capable
For overall status of cable modems, enter:
show cable modem summary
Here is an example of the show cable modem summary output:
show cable modem summary
S/P
Mac Conn
Total
Oper Disable
Init Offline
---------------------------------------------------------------1/U0
1
0
27
27
0
0
0
1/U1
1
0
11
11
0
0
0
1/U2
1
0
13
13
0
0
0
1/U3
1
0
9
9
0
0
0
---------------------------------------------------------------Mac 1
Total
48
48
0
0
0
Slot 1
Total
48
48
0
0
0
---------------------------------------------------------------14/D0
1
0
14
14
0
0
0
14/D1
1
0
15
15
0
0
0
14/D2
1
0
6
6
0
0
0
14/D3
1
0
5
5
0
0
0
14/D4
1
0
4
4
0
0
0
14/D5
1
0
4
4
0
0
0
14/D6
1
0
4
4
0
0
0
14/D7
1
0
8
8
0
0
0
----------------------------------------------------------------
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
%Oper
----100%
100%
100%
100%
----100%
100%
----100%
100%
100%
100%
100%
100%
100%
100%
-----
Description
---------
--------BigMac
---------
---------
C4® CMTS Release 8.3 User Guide
345
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Mac 1
Total
48
48
0
0
0 100% BigMac
Slot 14
Total
48
48
0
0
0 100%
---------------------------------------------------------------- ----- ------------------------------------------------------------------------ ----- --------Total
48
48
0
0
0 100%
For the status of the cable modems, enter:
show cable modem
An example of the show cable modem output:
show cable modem
Sep 30 14:49:16
Interface
(DS-US)
---------------14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/0-1/0
14/1-1/0
14/1-1/0
14/1-1/0
14/1-1/0
14/1-1/1
14/1-1/1
14/1-1/1
14/1-1/1
14/1-1/1
14/1-1/2
14/1-1/2
14/1-1/2
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
DOC
Mac
Bonded State
SIS
Qos
CPE
----- ------ ----------- --- ------------- ---
MAC address
IP Address
--------------- -------------------
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
0015.a463.15b3
0015.a463.20ab
0015.a463.2129
0015.a464.e69b
0015.a464.ec5c
0015.ce64.3a08
0015.ce64.3a74
0015.ce64.3cab
0015.ce64.3d1a
0015.ce64.3d2f
0015.ce64.3d35
0015.ce64.3e10
0015.ce64.3e61
0015.ce64.3e64
0015.ce64.39d2
0015.ce64.3bc7
0015.ce64.3ca2
0015.ce64.3e4c
0015.a463.15c8
0015.a464.e46a
0015.ce64.3c7b
0015.ce64.3cd8
0015.ce64.3df5
0015.a463.140c
0015.ce64.3cde
0015.ce64.3cf6
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
192.168.180.177
192.168.180.158
192.168.180.175
192.168.180.37
192.168.180.35
192.168.180.38
192.168.180.163
192.168.180.168
192.168.180.187
192.168.180.167
192.168.180.162
192.168.180.189
192.168.180.165
192.168.180.176
192.168.180.23
192.168.180.171
192.168.180.192
192.168.180.172
192.168.180.173
192.168.180.36
192.168.180.190
192.168.180.22
192.168.180.179
192.168.180.159
192.168.180.170
192.168.180.169
C4® CMTS Release 8.3 User Guide
346
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
14/1-1/2
14/1-1/3
14/1-1/3
14/2-1/0
14/2-1/0
14/2-1/0
14/2-1/2
14/2-1/3
14/3-1/0
14/3-1/0
14/3-1/0
14/3-1/1
14/3-1/2
14/6-1/0
14/7-1/0
14/7-1/0
14/7-1/1
14/7-1/2
14/7-1/2
14/7-1/2
14/7-1/3
14/7-1/3
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
Operational
4x4
4x4
4x4
4x4
2.0
2.0
2.0
3.0
3.0
3.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
3.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2.0
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
2000/2000
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0015.ce64.417f
0015.ce64.3e46
0015.ce64.3e5e
0015.cfee.4c13
0015.cfee.4c2f
0015.cfee.4cbb
0015.ce64.3de9
0015.ce64.3fb1
0015.a463.2429
0015.a464.efe3
0015.ce64.3b55
0015.ce64.3c96
0015.ce64.39d5
0015.cfee.4ccb
0015.a464.eab8
0015.ce64.3fa8
0015.ce64.3f00
0015.ce64.3b13
0015.ce64.3dbc
0015.ce64.3f45
0015.ce64.3639
0015.ce64.3f30
192.168.180.40
192.168.180.97
192.168.180.191
192.168.180.11
192.168.180.43
192.168.180.6
192.168.180.166
192.168.180.7
192.168.180.157
192.168.180.34
192.168.180.164
192.168.180.41
192.168.180.186
192.168.180.12
192.168.180.39
192.168.180.199
192.168.180.194
192.168.180.198
192.168.180.195
192.168.180.197
192.168.180.200
192.168.180.196
Total
Oper Disable
Init Offline
--------------------------------------------------------Total
48
48
0
0
0
To display the service groups, enter:
show cable service-group
An example of the show cable service-group output:
show cable service-group
Cable
MAC
--1
mCMsg
----2
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
mDSsg
----1
mUSsg
----1
C4® CMTS Release 8.3 User Guide
347
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
IPv6 Configuration (Optional)
This section assigns the IPv4 subnets and IPv6 prefixes that will be configured in the C4 CMTS. In Release 7.x, the setup of
IP subnets and prefixes has been augmented with support for IPv6. This allows the operator to run either IPv4 or IPv6 or
both protocols in a chassis.
Release 7.x enhancements and changes to the configuration include:
For installations with 16D CAMs and 12Us, the IPv4 and IPv6 addresses are assigned on a per-MAC domain basis or
bundled across multiple MAC Domains.
IPv6 addresses cannot be assigned to the SCM ports in Release 8.x.
The C4 CMTS can be configured to prefer IPv6 addressing of DOCSIS 3.0 CMs and DOCSIS 2.0 CMs that have support for
IPv6 and still provide IPv4 services to pre-DOCSIS 3.0 CMs.
To complete this configuration:
The IPv4 and IPv6 addresses must be assigned to both the RCM interface ports as well as the RF/MAC Domains/CAMs
as described above
The back office servers used to support the DOCSIS devices as well as CPE must be configured to support both IPv4 and
IPv6 operation
Enter the following CLI commands to configure the RCM Ethernet ports:
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
17/0 no shutdown
17/0.0 ip address 10.58.0.2 255.255.255.0
17/0.0 ipv6 enable
17/0.0 ipv6 address FE80::/10 EUI-64 link-local
17/0.0 ipv6 address 2001:db8:C408:1700::2/64
17/0.0 ip igmp
17/0.0 ipv6 no nd ra suppress
IP Address Prefixes and Subnets
When the C4 CMTS is configured for service, the back office systems that support the installation must also be configured
and properly setup to support the DOCSIS and non-DOCSIS devices services by the C4 CMTS. This means that if the C4
CMTS is operating with both IPv4 and IPv6 devices, the time servers, provisioning servers (DHCP and tftp) and NMS devices
are all capable of operating with either IPv4 or IPv6.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
348
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
Also, the DHCP servers need to be configured with the proper IPv4 and IPv6 address information and the correct DHCP
options for both legacy DOCSIS, and DOCSIS 3.0 devices.
Note: In configuring the MAC domain in the procedure above, the IP Provisioning Mode was set to IPv6 only. To support
legacy DOCSIS 2.0 CMs on the same channels in the MAC domain, IPv4 addresses must also be configured.
Configure the IPv6 on the RF:
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
1.0
1.0
1.0
1.0
1.0
ip address 10.108.0.1 255.255.224.0
ipv6 enable
ip address 10.108.32.1 255.255.224.0 secondary
ipv6 address 2001:db8:C408:C001::1/64
cable helper-address 10.50.8.3
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
1.0
1.0
1.0
1.0
1.0
ip igmp
ipv6 dhcp relay destination 2001:db8:C408:ED00::3
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
ipv6 no nd ra suppress
To display a brief summary of the IPv6 status and configuration for each interface, enter command:
show ipv6 interface brief
An example of the output in brief format:
Interface
Admin
State
Oper
State
Primary IP
cable-mac 1.0
cable-mac 1.0
gigabitEthernet 17/0.0
gigabitEthernet 17/0.0
Up
Up
Up
Up
IS
IS
IS
IS
FE80::201:5CFF:FE23:5A81/10
2001:db8:C408:C001::1/64
FE80::201:5CFF:FE23:5A40/10
2001:db8:C408:1700::2/64
The following is an example of the output returned by the system when the ping command is used to test connectivity:
ping ipv6 2001:db8:C408:C001::1
Sending IP ping to: 2001:db8:C408:C001::1
ping (2001:db8:C408:C001::1): 100 data bytes
!!!!!
5 packets transmitted, 5 packets received
To display the contents of the IPv6 route table entries for the IPv6 address, enter:
show ipv6 route
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
349
Chapter 11: Basic Bring-up Procedure for the C4 CMTS
An example of the output:
Dist/
IPv6 Route Dest / mask
=========================
::/0
2001:db8:C408:1700::/64
2001:db8:C408:C001::/64
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Act
===
Yes
Yes
Yes
PSt
===
IS
IS
IS
Next Hop
==============================
2001:db8:C408:1700::1
2001:db8:C408:1700::2
2001:db8:C408:C001::1
Metric Protocol Interface
======= ========= =============
1/0
netmgmt
gigE 17/0.0
0/0
local
gigE 17/0.0
0/0
local
cMac 1.0
C4® CMTS Release 8.3 User Guide
350
Chapter 12
Basic Bring-up Procedure for a C4c CMTS
Introduction ..................................................................................... 351
Before You Begin .............................................................................. 352
Bring-up Procedures......................................................................... 355
Basic Bring-up Procedure ................................................................. 358
Verification Steps ............................................................................. 366
IPv6 Configuration (Optional) .......................................................... 372
Introduction
This chapter provides the basic procedure to bring up a C4c CMTS system. This is not a software upgrade procedure: it
assumes that the chassis is not yet in service. Installing the chassis, modules, and cards and configuring the system are
addressed in this condensed reference. It is advisable to read through this information and become familiar with the order
of operation before you begin.
This chapter describes a minimal system configuration to be used for basic bring-up. The minimal configuration consists of
one System Control Module (SCM), one Router Control Module (RCM), one 12U Cable Access Module (CAM) and 16D/XD
CAM.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
351
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Before You Begin
In order to properly set up and install the C4c CMTS, several items are required. These include:
1. Chassis installation and powering
2. Hybrid Fiber Coax (HFC) Network Connectivity
3. The IP network plan for this CMTS
4. Set up of the provisioning environment for the new CMTS
Chassis Installation and Powering
It is assumed that the CMTS has been mounted in a rack in the headend and cabled for power prior to starting the
software installation. Do not power up the chassis until told to do so in the procedure.
For additional information on powering the system, refer to the Power Requirements (page 135) section.
HFC Network Connectivity
A useful tool for planning the CMTS configuration is the Network Connectivity Plan, as shown in the figure below. This plan
details the physical connections needed for the CMTS to reach the HFC plant as well as how the CMTS will be connected to
the Operator Network for Internet Access and provisioning, monitoring, and control.
Blank worksheets for configuring your network connectivity plan are located at the end of this chapter.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
352
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Figure 72: Network Connectivity Diagram
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
353
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
IP Network Plan
A network diagram is used to illustrate and document your specific network. The figure below is an example of a basic
network with sample IP addresses displayed. The IP addresses shown here are also used in subsequent examples in this
chapter. (See the blank form for actual use at the end of this section.)
Figure 73: Network Diagram Example
Configuration of Provisioning and Back Office Servers
The following servers must be provisioned and correctly set up to support the DOCSIS and non-DOCSIS devices and
services.
DHCP Server — A Dynamic Host Configuration Protocol (DHCP) server is needed to provide IP addresses to the modems
and Customer Premise Equipment (CPE).
The following options are required for registering modems:
Option 2 — time offset
Option 3 — router (IP address of CAM primary address)
Option 4 — time server (IP address of the time server)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
354
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Option 66 — boot server host name (IP address of the TFTP server)
Option 67 — boot file name (name of the modem configuration file)
TFTP Server — This server is required to send the modem configuration file to the modem.
Time of Day Server — This server provides the time of day to the modems.
Bring-up Procedures
The following is a high-level list of the steps of this procedure:
1. Install Front Cards, PICs, Filler Panels, PMs, and Fan Tray Module
2. Set Up Console Cable
3. Power Up the Chassis
4. Configure Slots
5. Configure RCM Ethernet Connections
6. Configure MAC Domains
7. Configure Downstream Parameters
8. Configure Upstream Parameters
9. Configure Fiber Node and Topology
10. Configure Bonding Group Management
11. Configure RCC Management
12. Save the Configuration
13. Local Authentication
14. Managing the CMTS
15. Configure the SNMP
16. Configure Clock
17. Cable CAMs and RCM
18. Configure/Verify Back Office Systems
19. Verify the CMTS Configuration
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
355
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
20. Verify Modem Registration
For the sake of consistency the following procedures reuse the example configuration used with the Frequency Space
Diagram and Network plan.
A C4c CMTS with one 16D CAM, one 12U CAM, one RCM and one SCM is configured to serve a set of 4 optical nodes. Both
DOCSIS 2.0 and 3.0 CMs will be put into service. The DOCSIS 3.0 CMs are provisioned with IPv6 addresses, while the
DOCSIS 2.0 CMs obtain IPv4 addresses. All CPE are provisioned as IPv4 devices.
Install Front Cards, PICs, Filler Panels, PMs, and Fan Tray Module
The C4c CMTS chassis has 8 slots that can be filled from top to bottom as follows:
Slot 15 (topmost slot) is provisioned for a 16D or an XD CAM
Slots 14 through 11 can be provisioned for 16D/XD or 12U CAMs (If slot 15 is a 16D, all other downstream CAMs must
be 16Ds; if slot 15 is an XD CAM, then all other downstream CAMs must be XDs.)
Slot 10 is provisioned for a 12U CAM
Slot 19 must be provisioned for an SCM
Slot 17 (bottom slot) must be provisioned for an RCM.
Note: The C4c CMTS can be equipped with all 2Dx12U CAMs, but does not support the use of 2Dx12U CAMs with any other
type of CAM in the same chassis. A mix of 16D and XD CAMs in the same chassis is not supported.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
356
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Figure 74: C4c CMTS Slot Diagram
For this configuration example, an SCM is installed in Slot 19 and an RCM in slot 17. Two CAMs are installed: a 16D CAM in
slot 15 and a 12U CAM in slot 10. Slots 14-11 can be used for 16D or 12U CAMs.
Note: If the operator chooses to use this C4c CMTS for DOCSIS 2.0 service only, slots 10-15 could all be equipped with
2Dx12U CAMs. If only 2Dx12U CAMs are being used, the slots can be equipped in any order.
Set Up Console Cable
The operator console is necessary to do the initial power up and configuring of the CMTS. An asynchronous terminal or a
PC with asynchronous terminal emulation software, such as HyperTerm or Teraterm, serves this purpose.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
357
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
The C4c CMTS is shipped with a black roll-over cable that has a 9-pin connector on one end and an RJ-45 connector on the
other. The RJ-45 end plugs into the front of the SCM card into the RS-232 port. The other end plugs into a computer or
terminal server.
The default connection settings for the computer COM port are:
9600 Baud rate
8 data bits
No parity
1-stop bit
Flow control Xon/Xoff
Once a successful connection is made, you should get a login prompt.
Power Up the Chassis
At this point, power on the chassis.
The SCM and RCM are configured automatically and come into service. As the CMTS is coming up, you can observe output
being sent to the console to provide a status of the activity.
Basic Bring-up Procedure
Configure Slots
This section provides steps to configure and provision the slots with the different CAM card types.
Enter the following commands:
configure
configure
configure
configure
slot
slot
slot
slot
15
10
15
10
type 16DCAM
type 12UCAM
no shutdown
no shutdown
Configure RCM Ethernet Connections
This section configures the RCM Ethernet port.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
358
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Enter the following CLI commands to configure the RCM:
configure interface gigabitEthernet 17/0 ip address 192.168.176.2 255.255.255.0
configure interface gigabitEthernet 17/0 no shutdown
This example assumes that static routing is used. To apply a default route, enter:
configure ip route 0.0.0.0 0.0.0.0 192.168.176.1
Configure MAC Domains
This section configures the MAC Domain on your system.
Note: If you are using 16D and 12U CAMs, then each MAC domain must consist of channels from exactly one 16D CAM and
exactly one 12U CAM. In other words, the MAC domain cannot include ports from more than one 16D CAM or from more
than one 12U CAM.
Configure and assign the MAC domain:
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
1
1
1
1
1
description Mac1
cable cm-ip-prov-mode ipv4only
ip address 192.168.180.1 255.255.255.0
cable helper-address 10.43.210.1
no shutdown
Configure Downstream Parameters
This section configures a single 16D CAM in slot 15. The 16D has the following characteristics:
4 physical connectors, each of which can output 4 downstream channels
The downstream channel frequencies are grouped four per connector. For each connector there is an 80 MHz
frequency range available for those four channels.
DS carriers 0-3 are associated with connector D0
DS carriers 4-7 are associated with connector D1
DS carriers 8-11 are associated with connector D2
DS carriers 12-15 are associated with connector D3
To configure the downstream interfaces to the cable-mac, enter:
configure interface cable-downstream 15/0 cable cable-mac 1
configure interface cable-downstream 15/1 cable cable-mac 1
configure interface cable-downstream 15/2 cable cable-mac 1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
359
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
configure interface cable-downstream 15/3 cable cable-mac 1
To configure the 16D CAM downstream frequencies enter:
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
15/0
15/1
15/2
15/3
cable
cable
cable
cable
configure
configure
configure
configure
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
15/0
15/1
15/2
15/3
no
no
no
no
frequency
frequency
frequency
frequency
621000000
627000000
633000000
639000000
shutdown
shutdown
shutdown
shutdown
Configure Upstream Parameters
This section provides a procedure to configure four upstream channels that are connected to the four nodes. Each
upstream in this example is configured with the same frequency and modulation profile. Each upstream has a unique
upstream channel id and is supervised by all four downstream channels.
To configure the upstream channels, enter:
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/0
10/1
10/2
10/3
cable
cable
cable
cable
cable-mac
cable-mac
cable-mac
cable-mac
1
1
1
1
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/0
10/1
10/2
10/3
cable
cable
cable
cable
connector
connector
connector
connector
0
1
2
3
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/0
10/1
10/2
10/3
cable
cable
cable
cable
frequency
frequency
frequency
frequency
10000000
20000000
30000000
40000000
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/0
10/0
10/0
10/0
cable
cable
cable
cable
supervision
supervision
supervision
supervision
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
15/0
15/1
15/2
15/3
C4® CMTS Release 8.3 User Guide
360
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/1
10/1
10/1
10/1
cable
cable
cable
cable
supervision
supervision
supervision
supervision
15/0
15/1
15/2
15/3
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/2
10/2
10/2
10/2
cable
cable
cable
cable
supervision
supervision
supervision
supervision
15/0
15/1
15/2
15/3
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/3
10/3
10/3
10/3
cable
cable
cable
cable
supervision
supervision
supervision
supervision
15/0
15/1
15/2
15/3
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/0
10/1
10/2
10/3
no
no
no
no
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
10/0.0
10/1.0
10/2.0
10/3.0
shutdown
shutdown
shutdown
shutdown
no
no
no
no
shutdown
shutdown
shutdown
shutdown
Note: If the system has been cabled, then legacy modems 1.0, 1.1, and 2.0 will register at this point in the procedure.
Configure Fiber Node and Topology
This section provides commands to configure the fiber node data and assign the channels that were defined in the
previous procedures to those fiber nodes.
Configure fiber nodes 1-4:
configure cable fiber-node FN1
configure cable fiber-node FN1 cable-downstream 15/0 15/1 15/2 15/3
configure cable fiber-node FN1 cable-upstream 10/0
configure cable fiber-node FN2
configure cable fiber-node FN2 cable-downstream 15/0 15/1 15/2 15/3
configure cable fiber-node FN2 cable-upstream 10/1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
361
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
configure cable fiber-node FN3
configure cable fiber-node FN3 cable-downstream 15/0 15/1 15/2 15/3
configure cable fiber-node FN3 cable-upstream 10/2
configure cable fiber-node FN4
configure cable fiber-node FN4 cable-downstream 15/0 15/1 15/2 15/3
configure cable fiber-node FN4 cable-upstream 10/3
Configure Bonding Group Management
This section deals with bonding groups. One method to build a bonding group is to dynamically configure it. This method is
preferred. Use the following command to create dynamic bonding groups:
configure interface cable-mac 1 cable downstream-bonding-group dynamic enable
The second method is Static Configuration: in this method each bonding group is specifically assigned to downstream
channels which will comprise the group. Enter the following commands:
configure interface cable-mac 1
cable downstream-bonding-group 1 cable-downstream
cable downstream-bonding-group 2 cable-downstream
15/0
15/0
15/1
15/1
15/2
15/2
15/3
Configure RCC Management
DOCSIS 3.0 allows for two methods of configuring the CM Receive Channel Configuration (RCC). Like the bonding group
configuration above, there can be dynamic and static RCC configurations.
To enable dynamic RCC configuration creation, use the following command:
configure interface cable-mac 1 cable dynamic-rcc
The Static method is shown below. It consists of explicitly defining all the different combinations that could occur on any
given node with specific downstream channels. Create a sample static RCC by entering the following commands:
configure interface cable-mac
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
cable rcp-id 0010000003 rcc 1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1
description "CLAB-6M-003"
module 1 min-center-frequency 621000000
module 1 connected-module 0
cm-channel 1 cable-downstream 15/0
cm-channel 1 module 1
cm-channel 1 primary-channel
cm-channel 2 cable-downstream 15/1
cm-channel 2 module 1
C4® CMTS Release 8.3 User Guide
362
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
cable
cable
cable
cable
rcp-id
rcp-id
rcp-id
rcp-id
0010000003
0010000003
0010000003
0010000003
rcc
rcc
rcc
rcc
1
1
1
1
cm-channel
cm-channel
cm-channel
cm-channel
2
3
3
3
primary-channel no
cable-downstream 15/2
module 1
primary-channel no
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
0010183381
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
2
2
2
2
2
2
2
2
2
2
2
2
description "BROADCOM-A"
module 1 min-center-frequency 621000000
module 1 connected-module 0
cm-channel 1 cable-downstream 15/0
cm-channel 1 module 1
cm-channel 1 primary-channel
cm-channel 2 cable-downstream 15/1
cm-channel 2 module 1
cm-channel 2 primary-channel no
cm-channel 3 cable-downstream 15/2
cm-channel 3 module 1
cm-channel 3 primary-channel no
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
rcp-id
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
0010000004
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
rcc
3
3
3
3
3
3
3
3
3
3
3
3
3
3
3
description "CLAB-6M-004"
module 1 min-center-frequency 621000000
module 1 connected-module 0
cm-channel 1 cable-downstream 15/0
cm-channel 1 module 1
cm-channel 1 primary-channel
cm-channel 2 cable-downstream 15/1
cm-channel 2 module 1
cm-channel 2 primary-channel no
cm-channel 3 cable-downstream 15/2
cm-channel 3 module 1
cm-channel 3 primary-channel no
cm-channel 4 cable-downstream 15/3
cm-channel 4 module 1
cm-channel 4 primary-channel no
Save the Configuration
Write the configuration to memory to save the configurations:
write memory
Local Authentication
To create a new user on the system, enter:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
363
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
configure username tempuser password <password>
Use the default method list (local database) by entering:
configure
configure
configure
configure
enable password <password>
authentication default local
line vty 0 15 authentication default login-authentication
line vty 0 15 authentication default enable-authentication
Managing the CMTS
Managing consists of various system administration tasks, including those related to accounting, security, and
configuration. This is accomplished through in-band or out-of-band management or both. Management functions can use
telnet, SSH, SNMP, and other protocols.
In-band Management
This means that the telnet/ssh/snmp sessions are carried through the Ethernet interfaces on the RCM line card.
Pro: Access Control Lists (ACLs) can be applied to increase security
Con: In-band management uses the same interfaces as all the modem traffic.
To provision in-band management, permit and define a standard ACL by entering:
configure access-list 1 permit any
configure interface gigabitEthernet 17/0 ip scm access-group 1
configure ip scm access
Out-of-band Management
This means that the telnet/snmp sessions are carried through the Ethernet interfaces on the SCM card, so that
management traffic is not being carried on the same channels as data traffic.
Pro: The IPs can be put on a private network and only management traffic is carried on these links
Con: ACLs can not be applied to these interfaces. The interface is 10MBPS and half duplex. The C4c CMTS requires a reboot
if these parameters need to be changed.
To provision out-of-band management, enter the following commands:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
364
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
To configure SCM slot 19 IP address and subnet mask:
configure interface ethernet 19/0 ip address 10.44.101.1 255.255.255.248
To configure the active SCM IP address and subnet mask for SCM 19:
configure interface ethernet 19/0 active ip 10.44.101.3 255.255.255.248
To configure the SCM default gateway:
configure ip route vrf management 0.0.0.0 0.0.0.0 10.44.101.6
To save the configuration, enter the write memory command.
Note: The chassis reboot in the following step is only required only if you are using the Out-of-Band Management
configuration and changing the IPs.
Save the changes and reboot the system (if Out-of-Band management is configured) by entering:
write memory
configure reset system
Configure the SNMP
The following command sequence enables the Simple Network Management Protocol (SNMP) to work. You should change
community strings for security purposes.
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
snmp-server
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
community public security rotesting
community private security rwtesting
user rotesting rotesting v1
user rwtesting rwtesting v1
user rotesting rotesting v2c
user rwtesting rwtesting v2c
context ""
group rotesting v1 read docsisManagerView
group rwtesting v1 read docsisManagerView write docsisManagerView
group rotesting v2c read docsisManagerView notify docsisManagerView
group rwtesting v2c read docsisManagerView write docsisManagerView
view docsisManagerView 1.3.6.1 included
group rotesting v2c notify docsisManagerView
group rotesting v1 notify docsisManagerView
C4® CMTS Release 8.3 User Guide
365
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Configure Clock
To set the network timing synchronization protocol, enter the following commands. This is a sample; change the IP address
and time zone as necessary.
configure ntp server 10.44.101.9
configure clock timezone America/Chicago
configure clock network ntp
Verification Steps
This section provides the procedures to complete the bring-up of your system.
Cable CAMs and RCM
In this step, the Operator needs to connect the cables to the CAMs, RCM, and SCM if out of band management is
configured. In this example, a single cable from the 16D PIC connected to connector 1 will be cabled to provide service to
nodes 1-4. Another 4 cables will be connected to the first four connectors on the 12U PIC on the rear of the chassis. These
individual upstreams will then be connected individually to four nodes.
Configure/Verify Back Office Systems
The provisioning servers and other Back Office servers and data collectors should be configured to allow for the first
modem to receive IP and CM configurations.
Since different offices use various provisioning servers and environments, this procedure is specific for each customer and
is site dependent.
Verify the CMTS Configuration
A number of commands can be used to verify the installation and configuration of the system at this point.
Verify the slot provisioning by entering the following command to show the slot provisioning:
show linecard status
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
366
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
The following is an example of the output:
C4# show linecard status
Slot Description
10
15
17
19
CAM
CAM
RCM
SCM
(0D, 12U)
(16D, 0U)
A
A
Admin Oper
State State
Up
IS
Up
IS
Up
IS
Up
IS
Duplex
State
Active
Active
Active
Active
Serial
Number
05453CMD0022
08113CSD0005
08143RCM0005
06063CBM0071
HW Version
CAM-01122W/F09
CAM-20016W/E02
RCM-01000W/D02
SCM-02440W/B06
Prov/Det
Type
CAM/CAM
DMM/DMM
RCM/RCM
SCM/SCM
Show the fiber node database and the topology information:
show cable fiber-node <name>
The following is an example of the output:
C4# show cable fiber-node
Cable
mDSsg/
Fiber Node
MAC
mCMsg mUSsg
Ports
---------------- ----- ----- ------------------------FN1
1
2 D1
15/0
15/1
FN1
1
2 U1
10/0.0
* Indicates that downstream channel is not primary-capable.
15/2
15/3
Verify the MAC Domain configuration:
show interface cable-mac <mac>
An example of the show
interface cable-mac
output:
Cable-mac 1
=============
Cable
Oper
Mod Power
Spare
LBal
DS Port Mac Conn State Annex Freq(Hz) Type (.1dBmV) Group
15/0
1
0
IS B(US) 621000000 q64
500
16785408
15/1
1
0
IS B(US) 627000000 q64
500
16785408
15/2
1
0
IS B(US) 633000000 q64
500
16785408
15/3
1
0
IS B(US) 639000000 q64
500
16785408
Cable
US PORT
10/0.0
Oper Chan
Mac Conn State Type
1
0
IS tdma
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Group
- 16779264, 16781312, 16783360,
- 16779264, 16781312, 16783360,
- 16779264, 16781312, 16783360,
- 16779264, 16781312, 16783360,
Channel Mini Mod Power
LBal
Freq(Hz) Width
Slot Prof (dBmV)
10000000 3200000 4
2
0
Group
16781312
C4® CMTS Release 8.3 User Guide
367
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
10/1.0
10/2.0
10/3.0
1
1
1
1
2
3
IS tdma
IS tdma
IS tdma
20000000 3200000 4
30000000 3200000 4
40000000 3200000 4
2
2
2
0
0
0
16779264
16783360
16785408
cable-mac 1.0, VRF: default, IP Address: 192.168.180.1/24
Secondary IP Address(es):
No Secondary Addresses
Physical Address: 0001.5c22.1041
MTU is 1500
DHCP Policy mode is disabled (primary mode)
DHCP Server Helper Address(es):
10.43.210.1 for Traffic Type "any"
Directed Broadcast is disabled
ICMP unreachables are always sent
Multicast reserved groups joined: None
Source-verify is disabled
InOctets
=
4290913
OutOctets
=
2310365
InUcastPkts=
12977
OutUcastPkts=
13222
InDiscards =
0
OutDiscards =
0
InErrors
=
0
OutErrors
=
0
InMulticastPkts=
0
OutMulticastPkts=
0
Cable Privacy
authkey default-life-time
tek default-life-time
default-cert-trust
chk-validity-period
604800
43200
untrusted
false
IGMP interface cable-mac 1:
IGMP host configured version is 2
IGMP host version 1 querier timer is 0h0m0s
IGMP host version 2 querier timer is 0h0m0s
IGMP host robustness is 2
Multicast groups joined by this system:
224.0.0.22
No IRDP entries found.
Subscriber
default-sub-grp-down
default-sub-grp-up
default-cm-grp-down
default-cm-grp-up
Dynamic-RCC:
0
0
0
0
enabled
Ranging interval (centiseconds):
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
2400
C4® CMTS Release 8.3 User Guide
368
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Sync interval (milliseconds):
UCD interval (milliseconds):
Ranging Cycles Int (centiseconds):
TFTP Enforcement:
Dynamic Secret:
Insertion interval (centiseconds):
Invited ranging attempts:
10
1600
120
disabled
disabled
40
16
Fibernode(s): FN1, FN2, FN3, FN4
RCP-id: 0010000005 RCC: dyn
Module: 1
MinCFreq:621000000 ModConnID:0
CM-chan Downstream Frequency Primary
1
15/0
621000000 Primary
2
15/1
627000000 Capable
3
15/2
633000000 Capable
4
15/3
639000000 Capable
To display the supervisory downstream for the upstream channels, enter:
show cable supervision
An example of the show interface cable supervision output:
C4# show cable supervision
MAC
----1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
US
DS
------10/0.0
10/0.0
10/0.0
10/0.0
10/1.0
10/1.0
10/1.0
10/1.0
10/2.0
10/2.0
10/2.0
10/2.0
10/3.0
10/3.0
10/3.0
10/3.0
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
----15/0
15/1
15/2
15/3
15/0
15/1
15/2
15/3
15/0
15/1
15/2
15/3
15/0
15/1
15/2
15/3
Method
----------Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
C4® CMTS Release 8.3 User Guide
369
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Verify Modem Registration
For status on a specific cable modem, enter the following command:
show cable modem detail <mac address>
An example of output for the show cable modem detail command for 0015.a4a4.573e:
C4# show cable modem detail 0015.a4a4.573e
15/0- 10/1.0
CM 0015.a4a4.573e (Arris) D3.0 State=Operational D1.1/tdma PrimSID=353
Cable-Mac= 1, mCMsg = 2
mDSsg = 1
mUSsg = 1 RCP_ID= 0x0010000004 RCC_Stat= 1
Timing Offset=1978
Rec Power= 0.00 dBmV Proto-Throttle=Normal dsPartialServMask=0x0000
Uptime= 0 days 0:06:29 IPv4=192.168.180.49 cfg=tput.bin noLoadBal=0x00
Privacy=Disabled
u/d SFID
u
705
dB
706
SID State Sched
Tmin
Tmax DFrms DBytes MFrms MBytes
CRC
HCS
353 Activ BE
0
0
47
3657
0
0
*353 Activ
0
0
DSID: 0x0161 ChanSetId: 0x01000002 dsBondingMask: 0x000f
DCIDs
Slot/Port
1
15/0
2
15/1
3
15/2
4
15/3
Current CPE=1 Max CPE=16
CPE 0003.471f.b386 IP=192.168.180.65 Filter-Group:Up=0 Down=0 Proto-Throttle=Normal
To display the status of the bonding group for a given MAC address, enter:
show cable bonding-group-status
An example of the show cable bonding-group-status output:
C4# show cable bonding-group-status
Cable
-mac
----1
1
chSetId
---------0x01000001
0x01000002
mDSsg/
mUSsg
------D1
D1
An example of the show
CfgId
------1
2
cable rcc-status
AttrMask
---------0x80000000
0x80000000
output:
C4# show cable rcc-status
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
370
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
Cable
Stat
-mac RCP-id
RCC ID ChanSetId RCC-Status
1 0010000004 dyn 36 0x1000002 Valid
For a more detailed report, use the show
cable rcc-status verbose
command:
C4# show cable rcc-status verbose
Cable
-mac
1
RCP-id
0010000004
Module: 1
CM-chan
1
2
3
4
Stat
RCC ID
ChanSetId RCC-Status
dyn
36 0x1000002 Valid
MinCFreq:621000000
ModConnID:0
Downstream Frequency Primary
15/2
633000000 Primary
15/0
621000000 Capable
15/1
627000000 Capable
15/3
639000000 Capable
For overall status of cable modems, enter:
show cable modem summary
An example of the show cable modem summary output:
C4# show cable modem summary
S/P
Mac Conn
Total
Oper Disable
Init Offline %Oper Description
---------------------------------------------------------------- ----- ------------------10/U0
1
0
5
5
0
0
0 100%
10/U1
1
1
0
0
0
0
0
0%
10/U2
1
2
0
0
0
0
0
0%
10/U3
1
3
0
0
0
0
0
0%
---------------------------------------------------------------- ----- ------------------Mac 1
Total
5
5
0
0
0 100% Mac1
Card 10
Total
5
5
0
0
0 100%
---------------------------------------------------------------- ----- ------------------15/D0
1
0
2
2
0
0
0 100%
15/D1
1
0
1
1
0
0
0 100%
15/D2
1
0
2
2
0
0
0 100%
15/D3
1
0
3
3
0
0
0 100%
---------------------------------------------------------------- ----- ------------------Mac 1
Total
5
5
0
0
0 100% Mac1
Card 15
Total
5
5
0
0
0 100%
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
371
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
---------------------------------------------------------------- ----- ---------------------------------------------------------------------------------- ----- ------------------Total
5
5
0
0
0 100%
For the status of the cable modems, enter:
show cable modem
An example of the show cable modem output:
C4# show cable modem
Sep 30 14:49:16
Interface
DOC
(DS-US)
Mac
Bonded State
SIS
Qos
CPE
------------- ----- ------ ----------- --- ------------- --15/0-10/0
1
Operational 2.0
0/0
0
15/0-10/0
1
Operational 2.0
0/0
0
15/0-10/0
1
4x1
Operational 3.0
0/0
0
15/1-10/0
1
Operational 2.0
0/0
0
15/2-10/0
1
Operational 2.0
0/0
0
15/3-10/0
1
Operational 2.0
0/0
0
15/3-10/0
1
Operational 2.0
0/0
0
Total
Oper Disable
Init Offline
--------------------------------------------------------Total
7
7
0
0
0
MAC address
IP Address
--------------- ---------------------0015.a463.22e8
0015.ce64.3e28
0015.ce92.d1cc
0015.ce64.3999
0015.a463.2135
0015.a463.240e
0015.ce64.3e6a
192.168.180.85
192.168.180.88
192.168.180.205
192.168.180.110
192.168.180.86
192.168.180.98
192.168.180.102
To display the service groups, enter:
show cable service-group
An example of the show cable service-group output:
show cable service-group
Cable
MAC
--1
mCMsg
----2
mDSsg
----1
mUSsg
----1
IPv6 Configuration (Optional)
This section assigns the IPv4 subnets and IPv6 prefixes that will be configured in the CMTS. IP subnets and prefixes can be
configured to use IPv6. This allows the operator to run either IPv4 or IPv6 or both protocols simultaneously in a chassis.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
372
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
For installations with 16D CAMs and 12Us, the IPv4 and IPv6 addresses are assigned on a per-MAC domain basis or
bundled across multiple MAC Domains.
IPv6 addresses cannot be assigned to the SCM ports in Release 7.x.
The CMTS can be configured to prefer IPv6 addressing of DOCSIS 3.0 CMs and DOCSIS 2.0 CMs that have support for IPv6
and still provide IPv4 services to pre-DOCSIS 3.0 CMs.
To complete this configuration:
The IPv4 and IPv6 addresses must be assigned to both the RCM interface ports as well as the RF/MAC Domains/CAMs
as described above
The back office servers used to support the DOCSIS devices as well as CPE must be configured to support both IPv4 and
IPv6 operation
Enter the following CLI commands to configure the RCM Ethernet ports:
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
17/0 no shutdown
17/0.0 ip address 10.58.0.2 255.255.255.0
17/0.0 ipv6 enable
17/0.0 ipv6 address FE80::/10 EUI-64 link-local
17/0.0 ipv6 address FC00:CADA:C408:1700::2/64
17/0.0 ip igmp
17/0.0 ipv6 no nd ra suppress
IP Address Prefixes and Subnets
When the CMTS is configured for service, the back office systems that support the installation must also be configured and
properly setup to support the DOCSIS and non-DOCSIS devices services by the CMTS. This means that if the CMTS is
operating with both IPv4 and IPv6 devices, the time servers, provisioning servers (DHCP and tftp) and NMS devices are all
capable of operating with either IPv4 or IPv6.
Also, the DHCP servers need to be configured with the proper IPv4 and IPv6 address information and the correct DHCP
options for both legacy DOCSIS, and DOCSIS 3.0 devices.
Note: In configuring the MAC domain in the procedure above, the IP Provisioning Mode was set to IPv6 only. To support
legacy DOCSIS 2.0 CMs on the same channels in the MAC domain, IPv4 addresses must also be configured.
Configure the IPv6 on the RF:
configure interface cable-mac 1.0 ip address 10.108.0.1 255.255.224.0
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
373
Chapter 12: Basic Bring-up Procedure for a C4c CMTS
configure
configure
configure
configure
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
1.0
1.0
1.0
1.0
ipv6 enable
ip address 10.108.32.1 255.255.224.0 secondary
ipv6 address FC00:CADA:C408:C001::1/64
cable helper-address 10.50.8.3
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
cable-mac
1.0
1.0
1.0
1.0
1.0
ip igmp
ipv6 dhcp relay destination FC00:CADA:C408:ED00::3
ipv6 nd managed-config-flag
ipv6 nd other-config-flag
ipv6 no nd ra suppress
To display a brief summary of the IPv6 status and configuration for each interface, enter the following command:
show ipv6 interface brief
An example of the output in brief format:
C4# show ipv6 interface brief
Interface
Admin
State
Oper
State
Primary IP
cable-mac 1.0
cable-mac 1.0
gigabitEthernet 17/0.0
gigabitEthernet 17/0.0
Up
Up
Up
Up
IS
IS
IS
IS
FE80::201:5CFF:FE23:5A81/10
FC00:CADA:C408:C001::1/64
FE80::201:5CFF:FE23:5A40/10
FC00:CADA:C408:1700::2/64
The following is an example of the output returned by the system:
C4# ping ipv6 FC00:CADA:C408:C001::1
Sending IP ping to: FC00:CADA:C408:C001::1
ping (FC00:CADA:C408:C001::1): 100 data bytes
!!!!!
5 packets transmitted, 5 packets received
To display the contents of the IPv6 route table entries for the IPv6 address, enter:
show ipv6 route
An example of the output:
Dist/
IPv6 Route Dest / mask
=========================
::/0
FC00:CADA:C408:1700::/64
FC00:CADA:C408:C001::/64
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Act
===
Yes
Yes
Yes
PSt
===
IS
IS
IS
Next Hop
==============================
FC00:CADA:C408:1700::1
FC00:CADA:C408:1700::2
FC00:CADA:C408:C001::1
Metric Protocol Interface
======= ========= =============
1/0
netmgmt
gigE 17/0.0
0/0
local
gigE 17/0.0
0/0
local
cMac 1.0
C4® CMTS Release 8.3 User Guide
374
Chapter 13
CAM Sparing
FlexCAM™ Hitless CAM Sparing ....................................................... 375
Guidelines for CAM Spare Groups ................................................... 377
Configuration Example ..................................................................... 378
Deleting a CAM Spare-group ............................................................ 384
FlexCAM™ Hitless CAM Sparing
CAM sparing minimizes traffic loss and customer impact in case of a hardware or software failure. When an active CAM in
a spare-group fails, the spare CAM automatically takes over. The cable modems that were connected to the upstream and
downstream channels on the failed CAM are immediately connected to the spare CAM. This includes configuration of
downstream and upstream channels and port administrative status. Cable modems do not have to re-register, and they
incur minimal data loss. Failback from the spare CAM to a recovered CAM can be set to take place automatically or
manually.
When a failover occurs, the CMTS automatically reconfigures the spare CAM to take over the functions of the failed
module. This includes configuration of downstream and upstream channels and port administrative status. Depending on
how you configure the CMTS, the spare CAM remains the active module or automatically switches back to the original
active CAM once that CAM comes back online.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
375
Chapter 13: CAM Sparing
Benefits of Hitless CAM Sparing
CAM sparing is an important element of system reliability. The benefits of hitless CAM sparing include:
Uninterrupted service to the subscriber if a CAM goes down in the middle of a session where the end user is sending or
receiving data
System administrators can take active CAMs out of service without serious impact
The spare CAM is used until the failed module is diagnosed, repaired, or replaced, or until there is a software recovery.
The goal of CAM sparing is to preserve data flows such as voice calls, video, best effort, and other subscriber services.
CAM Sparing PIC LEDs
The spare-group leader CAMs are equipped with sparing PICs. Other CAM slots are equipped with regular PICs. All CAM
PICs have a sparing indicator LED. The LED indicates if the CAM is being spared for (in the case of a regular CAM PIC) or if
the spare CAM is actively sparing for a member of the spare group (in the case of a spare CAM PIC). In normal conditions
all sparing LEDs are off. When a CAM in a spare-group fails, traffic is transferred to its spare-group leader. In this case, the
sparing LEDs of the failed CAM PIC and of the spare-group leader CAM PIC are on.
Definitions
Failover — An active CAM fails and the spare CAM takes over
Failback— The recovered CAM becomes active again, taking over for the spare.
Size of Hitless CAM Spare-groups
The C4 CMTS supports CAM sparing within the following limits:
XD CAM Up to 8:1
16D CAM Up to 8:1
12U CAM Up to 11:1
24U CAM Up to 9:1
For example, the CMTS supports 8:1 CAM sparing for the 16D CAM. In other words, the largest possible 16D CAM sparegroup has eight active CAMs and one spare.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
376
Chapter 13: CAM Sparing
Signal Loss during Failover
When failover occurs the RF signal to/from the failed CAM is rerouted from the PIC of the failed CAM through the
intervening PICs and backplane to the PIC of the now-active spare CAM. This longer path produces some signal loss.
Although station maintenance begins immediately and compensates for the upstream loss, there is a period of at least a
few seconds, depending on the number of modems supported, that the signal is weakened.
Guidelines for CAM Spare Groups
A spare-group consists of one spare CAM (the spare-group leader) and one or more active CAMs protected by the sparegroup leader.
CAMs are not required to be part of a spare-group.
A chassis may have several spare-groups, depending on how many slots are used as spares and on the size of the spare
groups.
Any CAM can be used as spare-group leader, but it must be the first CAM added to the group.
The spare-group must be homogenous: the group leader and all of the members of the spare-group must be the same
type of CAM.
CAMs from two different spare-groups cannot be interspersed. If slot 8 has been added to spare-group 0, then CAMs 17 cannot belong to any CAM spare-group except 0. In the same way, if slot 9 has been added to spare-group 15, then
slots10-14 can only be added to spare-group 15.
There can be an unspared CAM or an unpopulated front slot within a spare-group, but the rear slot must have the
correct PIC in it. For example, slot 0 can be the upstream spare-group leader for slots 1, 2, 3, 4, and 6, with slot 5 being
either unpopulated or not added to any spare-group. In this case in which slot 5 is unpopulated, rear slot 5 must be
equipped with an upstream non-spare PIC. If it is not, a failover from CAM 6 to the spare-group leader in slot 0 would
not succeed because traffic on CAM 6 could not be re-routed through the backplane from slot 6 to slot 0.
The spare-group leader must have a special Physical Interface Card called a sparing PIC. The upstream sparing PIC is a
different card than the downstream sparing PIC.
If you decide to turn a sparing leader slot into an active one, you may use the same CAM but you must replace the
sparing PIC with a non-sparing PIC.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
377
Chapter 13: CAM Sparing
Guidelines for Upstream Spare Groups
An upstream spare-group must be homogenous: a 12U CAM can spare only for other 12U CAMs; a 24U CAM can spare
only for other 24U CAMs.
Upstream CAM spare-groups are designated by the lowest-numbered slot in the group. The spare-group leader of an
upstream spare-group is always the lowest-numbered slot in that group.
Guidelines for Downstream Spare Groups
An downstream spare-group must be homogenous: a 16D CAM can spare only for other 16D CAMs; an XD CAM can
spare only for other XD CAMs. All the XD CAM slots in a spare-group must also be provisioned for the same annex.
Downstream CAM spare-groups are named for the highest-numbered slot. The group leader of a downstream sparegroup is always the highest-numbered slot in that group.
Calculating Signal Loss During Failover
When failover occurs the RF signal to the failed CAM is rerouted from the PIC of the failed CAM through the intervening
PICs and backplane to the PIC of the now-active spare CAM. This longer path produces some signal loss. Although station
maintenance begins immediately and compensates for the upstream loss, there is a period of at least a few seconds,
depending on the number of modems supported, that the signal is weakened.
Configuration Example
The figure below provides an example of a chassis equipped with 24U and XD CAMs arranged in spare-groups. Note that
the 24U CAM spare-group builds from left to right: its spare is the lowest-numbered CAM in the group. The XD spare-group
builds from right to left: its spare is the highest-numbered CAM in the group.
For the CAM sparing shown in Figure 11-1 you would need seven non-spare upstream CAM PICs, six non-spare
downstream CAM PICs, and two sparing PICs. The five different types of CAM PICs are listed below.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
378
Chapter 13: CAM Sparing
Type of PIC
Faceplate Label
Downstream sparing PIC:
PIC-CAM 16D (SPARE)
Downstream PIC:
PIC-CAM 16D
Upstream sparing PIC:
PIC-CAM (SPARE)
Upstream odd slot:
PIC-CAM (O)
Upstream even slot:
PIC-CAM (E)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
379
Chapter 13: CAM Sparing
The Odd and Even upstream CAM PICs are functionally identical but their connectors are offset to make cabling easier. The
upstream and downstream sparing PICs are not interchangeable.
Figure 75: Example of 24U and XD Spare groups (front view)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
380
Chapter 13: CAM Sparing
Figure 76: Example of CAM Sparing PICs (chassis rear view)
To configure the spare-groups shown in the examples, use the commands shown in the procedure below.
If using the following procedure for 12U CAMs, enter the CAM slot type 12UCAM instead of 24UCAM. If using 16D CAMs
for the downstream, the CAM slot should be 16DCAM instead of 32DCAM-B (Annex B) or 24DCAM-A (Annex A).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
381
Chapter 13: CAM Sparing
Create CAM Spare Groups
Automatic failback can reduce exposure to traffic loss because the spare CAM is restored to the standby state as soon as
the faulty CAM comes back up. Manual allows you to defer the failback to a more convenient time, such as a maintenance
window.
1. Provision the 24U CAM slots:
configure
configure
configure
configure
configure
configure
configure
configure
configure
slot
slot
slot
slot
slot
slot
slot
slot
slot
0
1
2
3
4
5
6
7
8
type
type
type
type
type
type
type
type
type
24UCAM
24UCAM
24UCAM
24UCAM
24UCAM
24UCAM
24UCAM
24UCAM
24UCAM
2. Configure spare-group 0 for the 24U CAMs:
configure
configure
configure
configure
configure
configure
configure
configure
configure
slot
slot
slot
slot
slot
slot
slot
slot
slot
0
1
2
3
4
5
6
7
8
spare-group
spare-group
spare-group
spare-group
spare-group
spare-group
spare-group
spare-group
spare-group
0 manual
0
0
0
0
0
0
0
0
3. Provision the XD slots. In this example we are provisioning the slots for 32D CAMs and for Annex B:
configure
configure
configure
configure
configure
configure
configure
slot
slot
slot
slot
slot
slot
slot
9 type 32DCAM-B
10 type 32DCAM-B
11 type 32DCAM-B
12 type 32DCAM-B
13 type 32DCAM-B
14 type 32DCAM-B
15 type 32DCAM-B
4. Configure spare-group 15 for the XD CAMs. The spare-group leader is found in the highest-numbered slot of the 32D
sparegroup:
configure
configure
configure
configure
slot 15 spare-group 15 manual
slot 9 spare-group 15
slot 10 spare-group 15
slot 11 spare-group 15
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
382
Chapter 13: CAM Sparing
configure slot 12 spare-group 15
configure slot 13 spare-group 15
configure slot 14 spare-group 15
5. Confirm that the spare-groups have been created:
show spare-group
Slot
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
Leader Slot
0
0
0
0
0
0
0
0
0
15
15
15
15
15
15
15
Mode
manual
manual
Fail Back Manually
If you have configured a CAM spare-group for manual failback, user traffic is handled by the spare CAM until it is manually
forced back to the original CAM by doing a shutdown / no shutdown on the spare-group leader.
1. (If necessary) Display the CAM spare-groups:
show spare-group
Example output:
Slot
0
1
2.
Leader Slot
0
0
Mode
manual
Verify the status of the spare-group leader and original CAM:
show linecard status
The original CAM must be in-service (IS) and Protected. The spare-group leader after a failover is marked IS and Active.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
383
Chapter 13: CAM Sparing
Sample output:
0 CAM (24U) Up IS Active 11073CTU0009 CAM-01240W/B06 CAM/CAM
1 CAM (24U) Up IS Protected 11153CTU0012 CAM-01240W/B06 CAM/CAM
3. Force user traffic back to the original CAM by shutting down the spare-group leader:
configure slot <slot> shutdown
Where: slot = the slot number of the spare-group leader
4. Restore the CAM sparing leader to service:
configure slot <slot> no shutdown
Where: slot = the slot number of the spare-group leader
5. Verify the status of the spare-group leader and original CAM:
show linecard status
The status of the spare-group leader should again be IS and Standby.
Deleting a CAM Spare-group
The CAM spare-group cannot be deleted if one of its CAMs has failed over to the sparing leader.
1. Delete a member of the spare-group:
configure slot <member slot> spare-group <leader slot> no
Repeat this command for each of the remaining CAMs in the spare-group.
2. Take the spare-group leader out of service:
configure slot <leader slot> shutdown
3. Delete the spare-group leader:
configure slot <leader slot> spare-group <leader slot> no
4. Display the spare-groups to confirm the deletion of the desired group:
show spare-group
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
384
Chapter 13: CAM Sparing
Note: The CAM spare-group cannot be deleted if one of its CAMs has failed over to the sparing leader. If a CAM has
failed over to the sparing CAM, the C4/c CMTS does not accept the command to remove the failed CAM from the sparegroup. You must first fail back to the original CAM, then you can remove it from the spare-group.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
385
Chapter 14
Cable-side Configuration
Overview ..........................................................................................386
MAC Domains ...................................................................................387
Upstream to Downstream Channel Association ..............................405
Cable Plant Topology and Fiber Nodes ............................................411
Service Group Determination and Display .......................................416
Channel Sets .....................................................................................418
Receive Channel Configurations and Bonding Groups.....................427
Overview
This chapter discusses the configuration of the logical components that allow the C4/c CMTS to provide service to the
subscriber side of the system.
Once the Cable Access Modules (CAMs) and their channels have been configured, the C4/c CMTS must then be configured
to use these channels.
Note: For cable-side configuration to begin, it is assumed that the slots for all the operational CAMs have previously been
configured. If not, refer to Bring-up Procedures for specifics. Additional information on provisioning the CAM cards can be
found in the Downstream Cable Access Module (DCAM) and Upstream Cable Access Module (UCAM) chapters.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
386
Chapter 14: Cable-side Configuration
MAC Domains
The MAC domain is a logical subcomponent of the C4/c CMTS that provides data forwarding services to a set of
downstream and upstream channels. In DOCSIS, the MAC domain is the set of CMs that use a common set of upstream and
downstream channels (at least 1 of each) linked together through a MAC forwarding entity of the C4/c CMTS.
A C4/c CMTS can support multiple MAC domains; however, each downstream and each upstream channel of the C4/c
CMTS can belong to only one MAC domain.
DOCSIS Functions
The concept of a MAC domain has been formalized in DOCSIS 3.0 to be an, "C4/c CMTS subcomponent object responsible
for all DOCSIS functions on a set of Downstream Channels and Upstream Channels."
These DOCSIS functions include:
DOCSIS downstream packet data transmission services provided to an C4/c CMTS forwarder including:
Service flow classification
Subscriber management filtering
Packet scheduling among one or more downstream channels to a CM
Downstream channel bonding
Downstream load balancing.
DOCSIS upstream packet data reception services provided to cable modems including:
Generation and distribution of bandwidth allocation messages (MAPs) and upstream channel descriptors (UCDs)
for each upstream channel of the MAC domain associated with the downstream channels of the MAC domain. This
is known as upstream supervision in the C4/c CMTS.
Cable modem ranging
Upstream channel bonding
Upstream load balancing
CM Event reporting.
DOCSIS MAC Management message exchanges with CMs
Before a chassis can achieve DOCSIS operation, the MAC domain itself must be provisioned, including:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
387
Chapter 14: Cable-side Configuration
Several parameters of the MAC domain.
The association of each downstream and each logical upstream to the MAC domain.
DOCSIS 3 Terminology
Terminology that is common to DOCSIS 3.0 is defined in the following table:
Table 55. DOCSIS 3.0 Terms
Term
Definition
A service group may contain channels from multiple C4/c CMTSs, and therefore the SG
may contain portions of multiple CM-SGs. The CM-SG is the portion of a service group’s
Cable Modem Service channels that is managed from a single C4/c CMTS.
Group (CM-SG)
The CM-SG is also an important DOCSIS 3.0 concept, but it is not directly used or
represented in the C4/c CMTS provisioning.
Fiber Node (FN)
A Fiber Node can terminate one or more downstream carrier paths from the head-end
and originates one or more upstream reverse carrier paths to the head-end. The FN
connects the upstream and downstream signals from the fiber onto numerous coaxial
cable segments. a
MAC Domain
All upstream and downstream channels of an C4/c CMTS must be assigned to the C4/c
CMTS logical subcomponent called the MAC domain. A MAC domain manages both a
group of channels, and the types of service that are carried on the channels.
A service group may contain channels from multiple MAC domains to allow separate
channels for different services. For example, residential data versus business data.
A cable modem uses channels from and communicates with only one MAC domain at a
time.
MAC Domain Cable
Modem Service
Group (MD-CM-SG)
A cable modem can only operate on channels that are part of the same MAC Domain. The
subset of a CM-SG’s channels which are confined to a single MAC domain is called a MAC
domain cable modem service group (MD-CM-SG).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
388
Chapter 14: Cable-side Configuration
Term
Definition
An MD-CM-SG differs from a CM-SG only if multiple MAC domains are represented in the
same CM-SG. The C4/c CMTS will attempt to identify the MD-CM-SG identifier for each
cable modem as it initializes.
MD-CM-SGs are calculated automatically by the C4/c CMTS based on the channel-to-fibernode and channel-to-MAC-domain provisioning.
MAC Domain
Downstream Service
Group (MD-DS-SG)
The subset of downstream channels from an MD-CM-SG is a MAC domain downstream
service group (MD-DS-SG). The downstream channels of a MD-DS-SG may be replicated
(via RF splitter devices) across multiple MD-CM-SGs. In this case the MD-DS-SG is said to
be a part of multiple MD-CM-SGs.
The determination of the MD-DS-SG by the cable modem during a CM initialization is an
important part of identifying the MD-CM-SG of a CM.
MD-DS-SGs are calculated automatically by the C4/c CMTS based on the channel-to-fibernode and channel-to-MAC-domain provisioning.
MAC Domain
Upstream Service
Group (MD-US-SG)
The subset of upstream channels from an MD-CM-SG is known as a MAC domain
upstream service group (MD-US-SG).
The upstream channels of a MD-US-SG may be shared (via RF combiner devices) across
multiple MD-CM-SGs. In this case the MD-US-SG is said to be a part of multiple MD-CMSGs.
The determination of the MD-US-SG by the C4/c CMTS during a CM initialization is an
important part of identifying the MD-CM-SG of a CM. MD-US-SGs are calculated (as readonly data) by the C4/c CMTS from the channel-to-fiber-node and channel-to-MAC-domain
provisioning.
Once the sets of downstream channels and logical upstream channels that reach each
MD-CM-SG have been determined, the C4/c CMTS will use this information to assign the
proper channels to each cable modem.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
389
Chapter 14: Cable-side Configuration
Term
Definition
Service Group (SG)
The set of upstream and downstream RF channels that connect to the fiber node is known
as the SG.
An SG is the set of upstream and downstream RF channels that can provide service to a
single subscriber device. This could include channels from different DOCSIS MAC domains
and even different C4/c CMTSs as well as video EQAMs.
The SG is an important DOCSIS 3.0 concept, but it is not directly used or represented in
the C4/c CMTS provisioning.
Upstream Channel
Supervision
The DOCSIS protocol has always employed the use of a downstream channel to carry the
channel access control information for each upstream channel. This control information is
carried in two messages:
The first is the Upstream Channel Descriptor, which contains information about the
physical properties of an upstream channel.
The second is the MAP, a message which allocates upstream minislot transmission
opportunities to individual cable modem requests.
For any upstream channel, these two types of control messages are always transmitted on
the same downstream channel. The C4/c CMTS CLI refers to the set of UCD and MAP
messages sent to an upstream channel as upstream channel supervision.
In order to receive the upstream channel supervision for one upstream channel, a DOCSIS
3.0 CM locates the supervision on one of the downstream channels to which it is tuned
and monitors that one downstream channel for the complete set of MAP and UCD
messages. The DOCSIS 3.0 CM repeats this process for each of the upstream channels that
have been assigned.
The CM may find the supervision for different US channels on different DS channels. The
CM may also find duplicate supervision for the same US on multiple DS channels. In such a
case the CM chooses only one DS channel as the source of the supervision for that
particular US channel.
The C4/c CMTS allows the operator to provision any downstream channel to provide
supervision for an upstream channel.
a. Information source is CableLabs® CM-SP-MULPIv3.0-I15-110210 Specifications.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
390
Chapter 14: Cable-side Configuration
Specifications
The following MAC domain specifications apply to the C4/c CMTS:
MAC domains operate independently of one another. A direct result is that the scope of channel bonding is limited to
the MAC domain
Each CM will utilize channels from only one MAC domain at a time.
Each downstream or upstream channel of a C4/c CMTS can be associated with exactly one MAC Domain.
The DCAM can support up to 8 MAC domains.
The UCAM can support up to 24 MAC domains.
A MAC domain must reside on a single UCAM and a single DCAM.
MAC Domain Configuration
The C4/c CMTS allows the creation of a MAC domain with more flexibility in terms of the allowed upstream and
downstream channel mix.
Note: There are several new DOCSIS 3.0 configuration items for these MAC domains. Many of these will impact the way
that DOCSIS 3.0 CMs will initialize.
MAC domains require upstream channels from a UCAM and downstream channels from a DCAM. These MAC domains may
be created and removed by means of CLI commands. See the table below for a summary view of the applicable commands.
For more information and additional commands, see Command Line Descriptions.
Table 56. MAC Domain Configuration Commands
Description
Command
This command configures a MAC domain
interface to be used with channels from a
UCAM or DCAM.
Use the [no] option to remove the cable-mac
interface for the specified MAC ID.
configure interface cable-mac <mac> cable description <text>
[no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Example commands:
configure
configure
configure
configure
interface
interface
interface
interface
cable-mac
cable-mac
cable-mac
cable-mac
1
2
3
4
description
description
description
description
"MAC-DOMAIN
"MAC-DOMAIN
"MAC-DOMAIN
"MAC-DOMAIN
1"
2"
3"
4"
C4® CMTS Release 8.3 User Guide
391
Chapter 14: Cable-side Configuration
Description
Command
This command configures the IP protocol mode
to be used by the cable modems served by this
MAC domain.
Use the [no] option to remove the specified
cable modem IP provisioning
configure interface cable-mac <mac> cable cm-ip-prov-mode
[<apm> | <ipv6only> | <ipv4only>][no]
This command enables cable modem status
event reporting by the cable modems served
by the MAC domain.
Use the [no] option to disable the signaling of
the CM-Status Event reporting mechanism,
configure interface cable-mac <mac> cable cm-status enabled
[no]
This command enables the C4/c CMTS to use IP
Multicast DSID-based Forwarding (MDF) to
cable modems in the MAC domain.
Use the [no] option to disable IP MDF on the
specified cable-mac,
configure interface cable-mac <mac> cable mcast-fwd-by-dsid
[no]
This command configures the interval (in
milliseconds) between successive
transmissions of the MAC domain descriptor
message (MDD) within the MAC domain.
Use the [no] option to remove the insertion
interval.
configure interface cable-mac <mac> cable mdd-interval <int>
[no]
Example command:
configure interface cable-mac 3 cable cm-ip-prov-mode apm
Example command:
configure interface cable-mac 3 cable cm-status enabled
Example command:
configure interface cable-mac 3 cable mcast-fwd-by-dsid
Example command:
configure interface cable-mac 3 cable mdd-interval 150
This command enables the CMs to operate on configure interface cable-mac <mac> cable mult-rx-chl-mode [no]
multiple downstreams within the MAC domain. Example command:
configure interface cable-mac 3 cable mult-rx-chl-mode
This is called multiple receive channel mode.
Note: Multiple receive channel mode must
be enabled before multiple transmit channel
mode may be enabled.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
392
Chapter 14: Cable-side Configuration
Description
Command
Use the [no] option to prevent CMs from
operating on multiple downstreams within the
MAC domain.
This command configures CMs to operate on
multiple upstreams within the MAC domain.
Use the [no] option to disable CMs from
operating on multiple upstreams within the
MAC domain.
configure interface cable-mac <mac> cable mult-tx-chl-mode [no]
Example command:
configure interface cable-mac 3 cable mult-tx-chl-mode
This command configures an override value (in configure interface cable-mac <mac> cable reg-rsp-timer-t6
<time> [no]
seconds) for the T6 timer in the CM that runs
Example command:
while awaiting a response to a registration
configure
interface cable-mac 3 cable mult-tx-chl-mode
request. TheC4/c CMTS also uses this timer
when multiple downstream channel mode is
enabled, but not multiple transmit channel
mode. Use the [no] option to return to the
default setting.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
393
Chapter 14: Cable-side Configuration
Channel to MAC Domain Association
Channels in the CMTS must be assigned to a MAC domain in order to provide service. The MAC domain uses the channels
to transport signaling and data to the CMs.
The commands in this section bind a logical upstream or downstream channel with a MAC Domain. The ARRIS CMTS will
assign a default channel ID for each channel but the user may provision a channel ID (DCID or UCID) to the channel for use
in channel signaling.
These commands associate a downstream channel from an XD CAM or a logical upstream channel from a 12U or 24U CAM
to a logical MAC domain. See example below.
configure interface cable-downstream <WORD> cable cable-mac <mac> [no]
configure interface cable-upstream <WORD> cable cable-mac <mac> [no]
Example of associating XD CAM downstreams to 12U or 24U upstreams:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-downstream 14/0 cable cable-mac 1
cable-downstream 14/1 cable cable-mac 1
cable-downstream 14/2 cable cable-mac 1
cable-downstream 14/3 cable cable-mac 1
cable-downstream 14/4 cable cable-mac 2
cable-downstream 14/5 cable cable-mac 2
cable-downstream 14/6 cable cable-mac 2
cable-downstream 14/7 cable cable-mac 2
cable-downstream 14/8 cable cable-mac 3
cable-downstream 14/9 cable cable-mac 3
cable-downstream 14/10 cable cable-mac 3
cable-downstream 14/11 cable cable-mac 3
cable-downstream 14/12 cable cable-mac 4
cable-downstream 14/13 cable cable-mac 4
cable-downstream 14/14 cable cable-mac 4
cable-downstream 14/15 cable cable-mac 4
cable-upstream 1/0.0 cable cable-mac 1
cable-upstream 1/1.0 cable cable-mac 1
cable-upstream 1/2.0 cable cable-mac 1
cable-upstream 1/3.0 cable cable-mac 2
cable-upstream 1/4.0 cable cable-mac 2
cable-upstream 1/5.0 cable cable-mac 2
cable-upstream 1/6.0 cable cable-mac 3
cable-upstream 1/7.0 cable cable-mac 3
cable-upstream 1/8.0 cable cable-mac 3
cable-upstream 1/9.0 cable cable-mac 4
cable-upstream 1/10.0 cable cable-mac 4
cable-upstream 1/11.0 cable cable-mac 4
C4® CMTS Release 8.3 User Guide
394
Chapter 14: Cable-side Configuration
Note: Channels may not be removed from a MAC domain while they are in the administrative up state.
These commands assign a user-provisioned channel ID to a downstream or logical upstream channel that has already been
added to a logical MAC domain. If you do not execute this command, the CMTS assigns the default channel IDs.
configure interface cable-downstream <WORD> cable channel-id <INT>
configure interface cable-upstream <WORD> cable channel-id <INT>
The following commands use the default channel IDs:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
cable-downstream 14/0 cable channel-id 1
cable-downstream 14/1 cable channel-id 2
cable-downstream 14/2 cable channel-id 3
cable-downstream 14/3 cable channel-id 4
cable-downstream 14/4 cable channel-id 1
cable-downstream 14/5 cable channel-id 2
cable-downstream 14/6 cable channel-id 3
cable-downstream 14/7 cable channel-id 4
cable-downstream 14/8 cable channel-id 1
cable-downstream 14/9 cable channel-id 2
cable-downstream 14/10 cable channel-id 3
cable-downstream 14/11 cable channel-id 4
cable-downstream 14/12 cable channel-id 1
cable-downstream 14/13 cable channel-id 2
cable-downstream 14/14 cable channel-id 3
cable-downstream 14/15 cable channel-id 4
cable-upstream 1/0.0 cable channel-id 1
cable-upstream 1/1.0 cable channel-id 2
cable-upstream 1/2.0 cable channel-id 3
cable-upstream 1/3.0 cable channel-id 4
cable-upstream 1/4.0 cable channel-id 5
cable-upstream 1/5.0 cable channel-id 6
cable-upstream 1/6.0 cable channel-id 7
cable-upstream 1/7.0 cable channel-id 8
cable-upstream 1/8.0 cable channel-id 9
cable-upstream 1/9.0 cable channel-id 10
cable-upstream 1/10.0 cable channel-id 11
cable-upstream 1/11.0 cable channel-id 12
Note: An assigned upstream channel ID (UCID) must not be assigned to any other logical channel on the 12U or 24U CAM
or MAC domain. An assigned downstream channel ID (DCID) must not be assigned to any other channel in the MAC
domain.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
395
Chapter 14: Cable-side Configuration
CAM Channel Mapping
The table below provides a view of the UCAM and DCAM as regards to MAC Domains and the following:
Default and purchased licensed channels.
UCAM connector groups.
DCAM physical connectors.
Table 57. MAC Domain CAM Channel Mapping
MAC
Domains
UCAM
Channels
1
4
2
UCAM
Connector Group
DCAM
Annex B
DCAM
Connector
24
32
0
4
24
32
1
3
4
24(a)
32
2
4
4
24
32(b)
3
5
4
24
32
4
6
4
24
32
5
7
4
24
32
6
8
4
24
32
7
9
4
24
32
0
10
4
24
32
1
11
4
24(a)
32
2
12
4(c)
24
32(b)
3
13
4
24
32
4
14
4
24
32
5
15
4
24
32
6
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
0
DCAM
Annex A
1
2
3
4
C4® CMTS Release 8.3 User Guide
396
Chapter 14: Cable-side Configuration
MAC
Domains
UCAM
Channels
16
4
17
UCAM
Connector Group
5
DCAM
Annex A
DCAM
Annex B
DCAM
Connector
24
32
7
4
24
32
0
18
4
24
32
1
19
4
24(a)
32
2
20
4
24
32(b)
3
21
4
24
32
4
22
4
24
32
5
23
4
24
32
6
24
4
24
32
7
6
7
(a) An Annex A DCAM by default is provided with 48 operational channels. An additional 144 channels (up to a total of
192 DOCSIS channels) may be activated through the purchase of license keys.
(b) An Annex B DCAM by default is provided with 64 operational channels. An additional 192 channels (up to a total of
256 DOCSIS channels) may be activated through the purchase of license keys.
(c) A UCAM by default is provided with 48 operational channels (connector groups 0-3). An additional 48 channels (up to
a total of 96) may be activated through the purchase of license keys.
MAC Domain CLI Commands
The commands in the table below bind a logical upstream or downstream channel with a MAC Domain.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
397
Chapter 14: Cable-side Configuration
Table 58. MAC Domain Channel Association
Description
Command
This command serves as follows:
Sets the downstream channel type.
Associates a downstream channel
from a DCAM with a logical MAC
domain.
configure interface cable-downstream <slot>/<connector>/<dport>
[type <port_type>] [cable-mac <mac>]
Use the [no] option to remove a
downstream channel from a specific
cable-mac (MAC Domain).
configure interface cable-downstream <slot>/<connector>/<dport> no
Example commands:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
cable-downstream
12/0/0 cable cable-mac 1
12/0/1 cable cable-mac 1
12/0/2 cable cable-mac 1
12/0/3 cable cable-mac 1
12/0/8 cable cable-mac 1
12/0/9 cable cable-mac 1
12/0/10 cable cable-mac 1
12/0/11 cable cable-mac 1
12/0/12 cable cable-mac 1
12/0/13 cable cable-mac 1
12/0/14 cable cable-mac 1
12/0/15 cable cable-mac 1
Example command:
configure interface cable-downstream 12/0/0 no
Note: It will also be necessary to
shutdown the downstream channel first
before it can be removed from the MAC
domain.
configure interface cable-upstream <slot>/<connector-group>/<uport>
This command associates an upstream
cable cable-mac <mac>
channel from a UCAM with a logical MAC
Example commands:
domain.
configure
configure
configure
configure
configure
configure
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/0/0 cable cable-mac 1
3/0/1 cable cable-mac 1
3/0/2 cable cable-mac 1
3/0/3 cable cable-mac 1
3/0/10 cable cable-mac 1
3/0/11 cable cable-mac 1
C4® CMTS Release 8.3 User Guide
398
Chapter 14: Cable-side Configuration
Description
Command
Use the [no] option to remove an
upstream channel from a specific cablemac (MAC Domain).
configure interface cable-upstream <slot>/<connector>/<uport> cable
cable-mac no
Note: It will also be necessary to
shutdown the upstream channel first
before it can be removed from the MAC
domain.
This command can be used to assign a
user-provisioned channel ID to an
upstream channel. If this command is not
used, the system assigns a default
channel ID to each upstream channel.
See also.
Example command:
configure interface cable-upstream 3/0/0 cable cable-mac no
configure interface cable-upstream <slot>/<connector-group>/<uport>
cable channel-id <int>
Example commands:
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/0/0 cable channel-id 1
3/0/1 cable channel-id 2
3/0/10 cable channel-id 11
3/0/11 cable channel-id 12
Note: The channel ID can only be in
the range 1-255
An assigned upstream channel ID must
not be assigned to any other logical
channel on the UCAM. The C4/c CMTS
will automatically do this.
This command can be used to assign a
user-provisioned channel ID to an
downstream channel. If this command is
not used, the system assigns a default
channel ID to each downstream channel.
See Channel Assignment Considerations
(page 400) for more information.
Note: The channel ID can only be in
the range 1-255
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
configure interface cable-downstream <slot>/<connector>/<dport>
cable channel-id <int>
Example commands:
configure interface cable-downstream
configure interface cable-downstream
.
.
.
configure interface cable-downstream
configure interface cable-downstream
12/0/0 cable channel-id 97
12/0/1 cable channel-id 98
12/0/14 cable channel-id 111
12/0/15 cable channel-id 112
C4® CMTS Release 8.3 User Guide
399
Chapter 14: Cable-side Configuration
Description
Command
An assigned downstream channel ID
must not be assigned to any other logical
channel on the DCAM. The C4/c CMTS
does this automatically .
Channel Assignment Considerations
Prior to assigning a channel ID the following needs to be considered:
1. Before assigning a channel ID, the upstream or downstream channel, as well as the MAC domain must be shutdown.
2. The shutdowns would be accomplished by the commands shown in the following example:
Note:
To change the channel ID of an upstream, the upstream's logical channel 0 (<slot>/<connectorgroup>/<uport>.0) must be shutdown, as shown in the example.
configure
configure
configure
configure
interface
interface
interface
interface
cable-upstream 3/0/0.0 shutdown
cable-mac 1 shutdown
cable-downstream 12/0/0 shutdown
cable-mac 1 shutdown
3. The channel ID can now be changed.
Example Commands
The following list of commands is meant as a sample configuration. This is not a script to follow since each site and
application is different.
configure
configure
configure
configure
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-downstream
cable-downstream
cable-downstream
cable-downstream
14/0
14/1
14/2
14/3
cable
cable
cable
cable
cable-mac
cable-mac
cable-mac
cable-mac
1
1
1
1
C4® CMTS Release 8.3 User Guide
400
Chapter 14: Cable-side Configuration
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-downstream 14/4 cable cable-mac 2
cable-downstream 14/5 cable cable-mac 2
cable-downstream 14/6 cable cable-mac 2
cable-downstream 14/7 cable cable-mac 2
cable-downstream 14/8 cable cable-mac 3
cable-downstream 14/9 cable cable-mac 3
cable-downstream 14/10 cable cable-mac 3
cable-downstream 14/11 cable cable-mac 3
cable-downstream 14/12 cable cable-mac 4
cable-downstream 14/13 cable cable-mac 4
cable-downstream 14/14 cable cable-mac 4
cable-downstream 14/15 cable cable-mac 4
cable-upstream 1/0 cable cable-mac 1
cable-upstream 1/1 cable cable-mac 1
cable-upstream 1/2 cable cable-mac 1
cable-upstream 1/3 cable cable-mac 2
cable-upstream 1/4 cable cable-mac 2
cable-upstream 1/5 cable cable-mac 2
cable-upstream 1/6 cable cable-mac 3
cable-upstream 1/7 cable cable-mac 3
cable-upstream 1/8 cable cable-mac 3
cable-upstream 1/9 cable cable-mac 4
cable-upstream 1/10 cable cable-mac 4
cable-upstream 1/11 cable cable-mac 4
C4® CMTS Release 8.3 User Guide
401
Chapter 14: Cable-side Configuration
Related CLI Commands
For more information on commands see Command Line Descriptions (page 1127).
configure interface cable-mac <mac> cable …
annex
Configures the MAC MPEG framing format. Annex A (EuroDOCSIS) is used
primarily in Europe; Annex B (DOCSIS) is used primarily in North America and
Japan.
bundle
Configures a cable interface bundle group.
cm-ip-prov-mode
Configures the CM IP provisioning for the interface.
cm-status enabled
Enables signaling of CM-status event reporting mechanism.
dhcp-giaddr
Configures DHCP giaddr mode.
downstream-bonding-group
Configures static downstream bonding group for the system.
dynamic-rcc
Enables/disables the autonomous creation of dynamic RCCs.
dynamic secret
Configures the dynamic secret for tftp enforcement.
freq-ds-max
Configures maximum downstream center frequency
freq-ds-min
Configures minimum downstream center frequency.
freq-us-max
Configures maximum upstream center frequency.
helper-address
DHCP server IP address.
insertion-interval
Provisions the cable MAC insertion interval.
invited-ranging-attempts
load-balance
Provisions the cable MAC invited ranging attempts.
Creates a restricted load-balance group for DOCSIS 3.0 interfaces.
mcast-fwd-by-dsid
Enables the CMTS to use IP Multicast DSID Forwarding (MDF)
mdd-interval
Configures the interval for the insertion of MDD messages.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
402
Chapter 14: Cable-side Configuration
mult-rx-chl-modE
Enables downstream channel bonding.
mult-tx-chl-mode
Enables Multiple Transmit Channel (MTC) mode.
privacy
Configures BPI channel parameters.
range-cycle-interval
Provisions the interval between ranging cycles.
ranging-interval
Provisions the cable MAC station maintenance interval.
rcp-ip
Adds the Receive Channel Profile Identifier.
reg-rep-timer-t6
Overrides the default value of the T6 timer in the CM.
source-verify
Enables (disables) verification of source IP addresses for all packets at this interface.
submgmt
Subscriber Management provisioning per cable mac.
sync-interval
Provisions the interval between sync messages.
tftp-enforce
Configures TFTP enforcement.
ucd-interval
Provisions the interval between UCD messages.
upstream-bonding-group
Configures static upstream bonding group for the system.
us-freq-range
Sets the upper band edge of the upstream frequency in MDD messages.
verbose-cm-cp
Cable modems MUST provide verbose reporting of Receive Channel Profiles.
MDD Upstream Ambiguity List Reduction
The C4/c CMTS places all of the upstream channels in the cable mac on the ambiguity list, which enables modems to
perform initial ranging on any upstream channel in the cable mac. However, when there are more than 16 upstream
channels in the cable mac, the ambiguity list also contains more than 16 channels, which is not supported by some D3.0
modems. In this case, those modems will not be able to register or may register as non-bonded.
When the upstream ambiguity list reduction feature is enabled, because the list will be limited to contain no more than 16
upstream channels, multiple fiber nodes that are configured within the cable mac will contain an equal number of
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
403
Chapter 14: Cable-side Configuration
channels from each fiber node in the ambiguity list. The method to determine how many channels, and which of those
channels will be selected for the ambiguity list, is as follows:
Divide 16 by the number of fiber nodes in the cable mac. Round down to the nearest whole number.
For example:
If there are 4 fiber nodes, then 16 / 4 = 4 channels from each fiber node added to the ambiguity list.
If there are 6 fiber nodes, then 16 / 6 = 2.67, which is rounded down to 2 channels from each fiber node added to the
ambiguity list.
The C4/c CMTS selects each channel with the lowest channel ID to be added to the ambiguity list, as configured by the
command:
configure interface cable-upstream <s/cg/ch[.0]> cable channel-id <1-255>
Note 1: An individual US Channel can only belong to a single MD-US-SG.
Note 2: The customer must ensure that supervision for the channels selected for the ambiguity list have supervision
configured for at least one primary capable downstream channel in the fiber nodes associated with each upstream
channel. It is recommended that supervision is configured on all primary downstream channels for each upstream channel
in the ambiguity list.
Table 59. MDD Upstream Ambiguity List Reduction CLI Commands
Purpose
CLI Command
configure
cable-upstream <s/cg/ch[.0]> cable channel-id <1-255>
Configures the cable
channel IDinterface
for
the interface cable-upstream.
configure operation
mode USAmbiguityListReduction
Enables/Disables USAmbiguity
list
configure operation mode USAmbiguityListReduction no
reduction mode.
Note 3: When enabling or disabling this feature, each upstream CAM must be reset for the feature to take effect. If
upstream CAM redundancy is supported, a fail over and back will cause the feature to take effect.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
404
Chapter 14: Cable-side Configuration
Upstream to Downstream Channel Association
For each logical upstream channel, DOCSIS requires that certain signaling information be carried downstream to the CM
population.
Upstream Channel Descriptor Messages
This signaling consists of Upstream Channel Descriptor (UCD) messages that contain:
Parameters that help the CMs to find and utilize the channel.
Bandwidth allocation (MAP) messages that tell a CM when it can transmit upstream.
Together, for the purposes of provisioning, these two types of signaling are referred to as supervision.
Supervision
Supervision for each upstream channel in the MAC domain must be carried on one or more downstream channels in the
MAC Domain.
Provisioning
Supervision can be either provisioned by the operator or it will be automatically inserted on primary-capable downstreams
by the E6000 CER. If you want to be certain that all legacy cable modems can register on all downstream-upstream
combinations, then you must manually provision cable supervision.
Note: ARRIS recommends that you manually provision all cable supervision.
Guidelines
The following supervision guidelines apply:
Removing the last supervision assignment for a logical upstream channel will result in the upstream going to the
administrative "down" state.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
405
Chapter 14: Cable-side Configuration
For an upstream channel to be in-service, there must be at least one downstream channel in-service that is providing it
with supervision.
Caution: The supervision for at least one upstream channel that is associated with a fiber node must be carried on at least
one primary-capable downstream channel that is also associated with that fiber node. Otherwise, CMs cannot initialize at
the fiber node. Fiber nodes with this problem will show up on the show cable fiber-node not-valid output.
Supervision CLI Commands
The commands in the table below configure supervision, and display slot and channel supervision information. Examples
are found in the following sections.
Table 60. Supervision Related Commands
Description
Command
This command controls the assignment of supervision from
a logical upstream channel to a downstream channel.
At least one, and as many as 16 downstream channels can
be assigned to carry the supervision for 12 individual
upstream channels. For minimum redundancy at least two
downstream channels should be assigned.
Use the [no] option to disable supervision on the specified
downstream port.
configure interface cable-upstream <slot>/<uport>
cable supervision <slot>/<dport> [no]
Show all supervision assignments in the system.
show cable supervision
Show only the supervision associated with one MAC
domain.
show cable supervision cable-mac <mac-id>
Show only supervision associated with one slot.
show cable supervision slot <slot-num>
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
406
Chapter 14: Cable-side Configuration
Supervision Configuration
The following command examples depict the configured channel supervision relationship between a UCAM in slot 3 and a
fully licensed DCAM in slot 12:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/0/0
3/0/0
3/0/0
3/0/0
3/0/1
3/0/1
3/0/1
3/0/1
3/0/2
3/0/2
3/0/2
3/0/2
3/0/3
3/0/3
3/0/3
3/0/3
3/0/4
3/0/4
3/0/4
3/0/4
3/0/5
3/0/5
3/0/5
3/0/5
3/0/6
3/0/6
3/0/6
3/0/6
3/0/7
3/0/7
3/0/7
3/0/7
3/0/8
3/0/8
3/0/8
3/0/8
3/0/8
3/0/8
3/0/8
3/0/8
3/0/9
3/0/9
3/0/9
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
12/0/0
12/0/1
12/0/2
12/0/3
12/0/0
12/0/1
12/0/2
12/0/3
12/0/0
12/0/1
12/0/2
12/0/3
12/0/0
12/0/1
12/0/2
12/0/3
12/0/4
12/0/5
12/0/6
12/0/7
12/0/4
12/0/5
12/0/6
12/0/7
12/0/4
12/0/5
12/0/6
12/0/7
12/0/4
12/0/5
12/0/6
12/0/7
12/0/8
12/0/9
12/0/10
12/0/11
12/0/12
12/0/13
12/0/14
12/0/15
12/0/8
12/0/9
12/0/10
C4® CMTS Release 8.3 User Guide
407
Chapter 14: Cable-side Configuration
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/0/9 cable supervision 12/0/11
3/0/9 cable supervision 12/0/12
3/0/9 cable supervision 12/0/13
3/0/9 cable supervision 12/0/14
3/0/9 cable supervision 12/0/15
3/0/10 cable supervision 12/0/8
3/0/10 cable supervision 12/0/9
3/0/10 cable supervision 12/0/10
3/0/10 cable supervision 12/0/11
3/0/10 cable supervision 12/0/12
3/0/10 cable supervision 12/0/13
3/0/10 cable supervision 12/0/14
3/0/10 cable supervision 12/0/15
3/0/11 cable supervision 12/0/8
3/0/11 cable supervision 12/0/9
3/0/11 cable supervision 12/0/10
3/0/11 cable supervision 12/0/11
3/0/11 cable supervision 12/0/12
3/0/11 cable supervision 12/0/13
3/0/11 cable supervision 12/0/14
3/0/11 cable supervision 12/0/15
3/1/0 cable supervision 12/1/0
3/1/0 cable supervision 12/1/1
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
•
•
•
configure
configure
configure
configure
configure
configure
configure
configure
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
12/7/8
12/7/9
12/7/10
12/7/11
12/7/12
12/7/13
12/7/14
12/7/15
Example of Configuration
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/0.0
1/0.0
1/0.0
1/0.0
1/1.0
1/1.0
1/1.0
1/1.0
1/2.0
1/2.0
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
supervision
14/0
14/1
14/2
14/3
14/0
14/1
14/2
14/3
14/0
14/1
C4® CMTS Release 8.3 User Guide
408
Chapter 14: Cable-side Configuration
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
1/2.0 cable supervision 14/2
1/2.0 cable supervision 14/3
1/3.0 cable supervision 14/4
1/3.0 cable supervision 14/5
1/3.0 cable supervision 14/6
1/3.0 cable supervision 14/7
1/4.0 cable supervision 14/4
1/4.0 cable supervision 14/5
1/4.0 cable supervision 14/6
1/4.0 cable supervision 14/7
1/5.0 cable supervision 14/4
1/5.0 cable supervision 14/5
1/5.0 cable supervision 14/6
1/5.0 cable supervision 14/7
1/6.0 cable supervision 14/8
1/6.0 cable supervision 14/9
1/6.0 cable supervision 14/10
1/6.0 cable supervision 14/11
1/7.0 cable supervision 14/8
1/7.0 cable supervision 14/9
1/7.0 cable supervision 14/10
1/7.0 cable supervision 14/11
1/8.0 cable supervision 14/8
1/8.0 cable supervision 14/9
1/8.0 cable supervision 14/10
1/8.0 cable supervision 14/11
1/9.0 cable supervision 14/12
1/9.0 cable supervision 14/13
1/9.0 cable supervision 14/14
1/9.0 cable supervision 14/15
1/10.0 cable supervision 14/12
1/10.0 cable supervision 14/13
1/10.0 cable supervision 14/14
1/10.0 cable supervision 14/15
1/11.0 cable supervision 14/12
1/11.0 cable supervision 14/13
1/11.0 cable supervision 14/14
1/11.0 cable supervision 14/15
Display System Supervision
The following command example displays a view of cable supervision regarding the whole system:
show cable supervision
An output similar to the following example will result:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
409
Chapter 14: Cable-side Configuration
MAC
----1
1
1
1
US
------1/0.0
1/0.0
1/0.0
1/0.0
4
4
4
4
4
4
•
•
1/10.0
1/10.0
1/11.0
1/11.0
1/11.0
1/11.0
DS
----14/0
14/1
14/2
14/3
Method
----------Provisioned
Provisioned
Provisioned
Provisioned
14/14
14/15
14/12
14/13
14/14
14/15
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
•
Display Supervision for One MAC Domain
The following command example displays a view of cable supervision for one MAC domain:
show cable supervision cable-mac 1
An output similar to the following example would result:
MAC
----1
1
1
1
1
1
1
1
1
1
1
1
US
------1/0.0
1/0.0
1/0.0
1/0.0
1/1.0
1/1.0
1/1.0
1/1.0
1/2.0
1/2.0
1/2.0
1/2.0
DS
----14/0
14/1
14/2
14/3
14/0
14/1
14/2
14/3
14/0
14/1
14/2
14/3
Method
----------Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Display Supervision for One Slot
The following command example displays a view of cable supervision for one chassis slot:
show cable supervision slot 12
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
410
Chapter 14: Cable-side Configuration
An output similar to the following example would result:
MAC
----1
1
1
1
1
1
1
1
1
1
US
---------3/0/0
3/0/0
3/0/0
3/0/0
3/0/1
3/0/1
3/0/1
3/0/1
3/0/2
3/0/2
DS
-------12/0/0
12/0/1
12/0/2
12/0/3
12/0/0
12/0/1
12/0/2
12/0/3
12/0/0
12/0/1
Method
----------Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
3/7/11
12/7/8
12/7/9
12/7/10
12/7/11
12/7/12
12/7/13
12/7/14
12/7/15
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
Provisioned
•
•
•
8
8
8
8
8
8
8
8
Note: The output provided for command execution on slot 3 would be the same.
Cable Plant Topology and Fiber Nodes
The C4/c CMTS is responsible for assigning an upstream Transmit Channel Configuration (TCC) and a downstream Receive
Channel Configuration (RCC) to each cable modem that is capable of supporting them. DOCSIS 3.0 provides for the flexible
assignment of multiple upstream or downstream channels to carry a single packet flow.
As a result, the C4/c CMTS is required to provide enhanced tracking of the cable plant topology than was previously
necessary for earlier DOCSIS phases. Specifically, the C4/c CMTS must be aware of which upstream and downstream
channels reach each cable modem.
The following steps are necessary to achieve this tracking functionality:
Provisioning of fiber nodes in the cable plant
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
411
Chapter 14: Cable-side Configuration
Provisioning of channels to MAC domains
Provisioned assignment of upstream and downstream channels to fiber nodes
Assignment of primary capability to downstream channels.
Fiber Node Configuration
A fiber node in an HFC plant is a point of media conversion between a fiber trunk and the coaxial distribution. In terms of
network topology, it is the common point of aggregation of all of the coaxial branches. In other words, it is the equipment
at which all CMs associated with the fiber node will receive the same set of downstream frequencies and will be able to
transmit on the same set of upstream frequencies.
It is convenient when setting up an HFC network to plan the channel allocation from an C4/c CMTS to a fiber node in a
fiber node combining (and splitting) plan.
Note: Some operators may combine two or more nodes so that both are all connected to the same set of upstream and
downstream channels. In this case, you only need to enter in one fiber-node command on the C4/c CMTS, since the two
nodes share the same interfaces.
The following sections provide commands and examples for managing fiber nodes names and descriptions.
Create/Remove Fiber Node Name
To assign a name to a fiber node:
configure cable fiber-node <fn-name> [no]
Use the [no] option to remove a fiber node with no associated channels. If there are associated channels, this command
will fail.
The following command example creates a fiber node named FN1:
configure cable fiber-node FN1
The following command example is used to remove a fiber node named FN1:
configure cable fiber-node FN1 no
Add/Remove Fiber Node Name Description
To provide a textual description of a fiber node:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
412
Chapter 14: Cable-side Configuration
configure cable fiber-node <fn_name> description <fn_description> [no]
The following command example adds a description to a fiber node named FN1:
configure cable fiber-node FN1 description "Fiber-Node 1"
The following command example removes the description from a fiber node named FN1:
configure cable fiber-node FN1 description no
Force Removal of Fiber Node
The following command disassociates all channels from a fiber node, and then forces the removal of the fiber node itself:
configure cable fiber-node FN1 force no
Channel to Fiber Node Configuration
Once a fiber node has been created, the physical channels assigned to the fiber node must be configured so that the C4/c
CMTS has an accurate understanding of the channels that may be used by each CM.
Channel to Fiber Node Commands
The commands in the table below provide channel to fiber node configuration. See Command Line Descriptions for more
information.
Table 61. Channel to Fiber Node Configuration Commands
Description
Command
This command assigns downstream channels to the
fiber node.
Use the [no] option to remove a downstream channel
from the fiber node.
configure cable fiber-node <fn_name> cabledownstream <slot/connector[/ds port]> [no]
This command assigns upstream channels to the fiber
node.
configure cable fiber-node <fn_name> cable-upstream
<slot>/<uport> [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
413
Chapter 14: Cable-side Configuration
Description
Command
Use the [no] option to remove an upstream channel
from the fiber node.
Assign Upstream Channels to Fiber Node
The following command examples assign upstream channels to a fiber node:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
fiber-node
FN1
FN1
FN1
FN2
FN2
FN2
FN3
FN3
FN3
FN4
FN4
FN4
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
cable-upstream
3/0
3/1
3/2
3/3
3/4
3/5
3/6
3/7
3/8
3/9
3/10
3/11
It is not necessary to use a separate command for each channel that you assign to a fiber node. You can add several
channels on one command line, shown as follows:
configure cable fiber-node FN3 cable-upstream 3/6-8
configure cable fiber-node FN4 cable-upstream 3/9,11
Assign Downstream Channels to Fiber Node
The following command examples assign downstream channels to a fiber node:
configure cable fiber-node FN1 cable-downstream 12/0 12/1 12/2 12/3
configure
configure
configure
configure
cable
cable
cable
cable
fiber-node
fiber-node
fiber-node
fiber-node
FN1
FN1
FN1
FN2
cable-downstream
cable-downstream
cable-downstream
cable-downstream
12/4
12/5
12/6
12/7
configure
configure
configure
configure
cable
cable
cable
cable
fiber-node
fiber-node
fiber-node
fiber-node
FN2
FN2
FN3
FN3
cable-downstream
cable-downstream
cable-downstream
cable-downstream
12/8
12/9
12/10
12/11
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
414
Chapter 14: Cable-side Configuration
configure
configure
configure
configure
cable
cable
cable
cable
fiber-node
fiber-node
fiber-node
fiber-node
FN4
FN4
FN4
FN4
cable-downstream
cable-downstream
cable-downstream
cable-downstream
12/12
12/13
12/14
12/15
It is not necessary to use a separate command for each channel that you assign to a fiber node. You can add several
channels on one command line, shown as follows:
configure cable fiber-node FN4 cable-downstream 12/12-15
configure cable fiber-node FN5 cable-downstream 12/9,11
Cable Modem Timing, Supervision, and Messaging
Before it can initialize, each cable modem (of any DOCSIS version) requires a downstream channel that carries the
following:
SYNC messages (for system timing)
Supervision information for at least one upstream channel
In addition, a DOCSIS 3.0 CM requires the following, in order to register with multiple receive channel mode:
Detailed (lengthy) MDD messages
MAP messages and UCD messages for all upstream channels which will be used in ambiguity resolution
Primary-Capable Downstream Channel
A downstream channel that provides all of the aforementioned timing, supervision, and messaging information is known as
a primary-capable downstream channel. Such a downstream channel is capable of becoming a cable modem’s single
primary downstream channel which it will use to derive all timing for system access in the upstream direction.
Because primary-capable downstream channels are the only downstream channels that carry timing information, they are
also the only downstream channels that pre-3.0 DOCSIS cable modems can use for service. Therefore, primary-capable
downstream channels can be expected to carry slightly more overhead traffic than non-primary-capable downstream
channels.
Note: The MSO should ensure that it has configured enough primary-capable channels to support legacy CMs.
Each MD-DS-SG must contain at least one primary-capable downstream channel so that CMs can register and operate. The
MSO may also wish to configure more than one DS to be primary-capable if there is a large number of pre-3.0 CMs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
415
Chapter 14: Cable-side Configuration
However, all DOCSIS 3.0 CMs are capable of using non-primary-capable downstreams for any type of data service that they
can provide.
Configure Primary Capability
To configure a downstream channel as primary capable, enter:
configure interface cable-downstream <s/p> cable primary-capable [no]
An example of the command:
configure interface cable-downstream 12/0 cable primary-capable
Service Group Determination and Display
Once channels have been assigned to both the MAC Domain and the fiber nodes, the C4/c CMTS can automatically assign
group IDs to channels based upon common HFC plant connection topology.
MAC Domain
Each MAC domain independently defines its own:
MD-CM-SGs
MD-DS-SGs
MD-US-SGs
As a result, different MAC Domains that reach the same set of fiber nodes may have channels that are split/combined in a
manner such that the channel grouping boundaries do not match up. These groupings can then be used by the C4/c CMTS
to determine the channels that are available for each fiber node (and ultimately each CM) to use.
Modem and Service Group Association
A modem is associated with a MD-CM-SG at the time of initial modem ranging. The modem stores the MD-CM-SG-ID as
well as the fiber node's name that is associated with the MD-CM-SG. The ID and name are included in the show cable
modem detail output. A modem’s MD-CM-SG-ID (which is shown as mCMsg in CLI outputs) is also the fiber node’s MD-CMSG-ID when the modem registers.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
416
Chapter 14: Cable-side Configuration
When a topology change occurs where the MD-CM-SG-ID changes for the fiber node, the MD-CM-SG-ID will be updated for
each modem associated with the fiber node via the fiber node name.
The MD-CM-SG-ID will be zero when the fiber node configuration for the fiber node associated with the modem is no
longer valid. It will be restored when the fiber node is restored to a valid configuration.
Note: Only channels that are operationally in service will be considered for the modem’s RCS and TCS at modem
registration or for DBC load balancing or AC power restoral.
Topology changes that may impact the MD-CM-SG-ID for a fiber node include:
Shutting down or restoring channels in its service group
Adding or removing channels to its service group (fiber node)
Adding or removing channels to a MAC domain
Removing the service group (deleting the fiber node)
Recommended Procedures for Topology Changes
The following procedures and guidelines are suggested when making various changes to topology:
Channel Set Changes within the Fiber Node
When only the channel sets within fiber nodes are changing and the fiber node names are maintained, modify the
existing fiber nodes without deleting the fiber nodes.
This allows the modems that are already registered within the effected fiber nodes to properly select from the
modified MD-CM-SG for DBC load balancing and AC power restoral. (See CM Channel Reassignment for AC Power Loss
for more information.)
Fiber Node Name Changes or Fiber Node Moves
When the fiber node names change for existing fiber nodes, the fiber nodes must be deleted and re-entered with the
new channel sets.
When fiber nodes are moved to a set of channels that are no longer accessible by the modems that were associated
with the fiber node, the fiber nodes must be deleted and re-entered with new channel sets.
When fiber nodes are deleted, the registered modems are no longer able to recover from AC power loss, nor are they
able to be DBC load balanced until the modems are reset.
One of the following options should be considered when changing the fiber node’s name if DBC load balancing or the
AC Power Loss feature is enabled:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
417
Chapter 14: Cable-side Configuration
Shutdown the MAC domains before the changes are made and no shut the MAC domain after the changes are
made. When the modems register, they will be associated with a fiber node and will be able to recover from AC
power loss and be dynamically load balanced.
Shutdown and restore the MAC domains at a later time during a Maintenance window to re-register the modems.
Reset the modems by hand for those that need to be load balanced or recovered from AC power loss.
Note that these three options ensure that the modems will be able to load balance and be restored from AC power loss
after the changes are complete and the modem is reset.
Removing a Channel from a MAC Domain
When a channel is removed from a MAC domain, all the modems containing that channel in either its Transmit Channel
Set (TCS) or Receive Channel Set (RCS) are reset.
Note that removing channels from MAC domains should only be done during a Maintenance window.
Channel Sets
DOCSIS 3.0 provides a construct called a channel set to denote groupings of channels in the same direction from the same
MAC domain. These channel sets consist of a MAC-domain-unique channel set identifier and a list of either Upstream
Channel IDs (UCIDs) or Downstream Channel IDs (DCIDs), depending on the direction of the channels.
A channel set may be referenced by many different application contexts that require the grouping all at once. If a channel
set contains only one channel ID, then the channel ID is used as the channel set ID.
As the C4/c CMTS determines the service groups (MD-DS-SG, MD-US-SG, and MD-CM-SG), it creates and assigns a channel
set for the channels that comprise the service group.
The C4/c CMTS automatically creates and destroys channel sets as needed.
Show CLI Commands
The following are examples of the commands that display the various views for fiber nodes and service group related
information. For more information on these CLI commands see Command Line Descriptions.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
418
Chapter 14: Cable-side Configuration
Display All System Channel Sets
The following command example displays all system channel sets:
show cable channel-sets
An output similar to the following example will occur:
Cable
-mac
----1
1
2
2
3
3
4
4
chSetId
---------0x00000100
0x00000100
0x00000101
0x00000101
0x00000102
0x00000102
0x00000103
0x00000103
DS/US Channel Set
----- ----------------------------------------------DS
14/0
14/1
14/2
14/3
US
1/0.0
1/1.0
1/2.0
DS
14/4
14/5
14/6
14/7
US
1/3.0
1/4.0
1/5.0
DS
14/8
14/9
14/10
14/11
US
1/6.0
1/7.0
1/8.0
DS
14/12
14/13
14/14
14/15
US
1/9.0
1/10.0 1/11.0
Display Downstream Channel Sets
The following command example displays all downstream channel sets:
show cable channel-sets ds
An output similar to the following example will occur:
Cable
-mac
----1
2
3
3
4
4
5
5
6
6
chSetId
---------0x00000100
0x00000100
0x00000100
0x01000002
0x00000100
0x01000001
0x00000100
0x01000001
0x00000100
0x01000002
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
DS/US
----DS
DS
DS
DS
DS
DS
DS
DS
DS
DS
Channel Set
----------------------------------------------13/0
13/1
13/2
13/3
12/0
12/1
12/2
12/3
11/0
11/1
11/2
11/3
11/0
11/1
11/2
11/3
10/0
10/1
10/2
10/3
10/0
10/1
10/2
10/3
9/0
9/1
9/2
9/3
9/0
9/1
9/2
9/3
8/0
8/1
8/2
8/3
8/0
8/1
8/2
8/3
C4® CMTS Release 8.3 User Guide
419
Chapter 14: Cable-side Configuration
Display Upstream Channel Sets
The following command example displays all upstream channel sets:
show cable channel-sets us
An output similar to the following example will occur:
Cable
-mac
----1
2
3
3
4
4
5
5
6
6
chSetId
---------0x00000100
0x00000100
0x00000100
0x01000002
0x00000100
0x01000001
0x00000100
0x01000001
0x00000100
0x01000002
DS/US
----US
US
US
US
US
US
US
US
US
US
Channel Set
---------------------------------------1/4
1/5
1/6
1/7
1/8
1/9
1/10
1/11
2/0
2/1
2/2
2/3
2/0
2/1
2/2
2/3
2/4
2/5
2/6
2/7
2/4
2/5
2/6
2/7
2/8
2/9
2/10
2/11
2/8
2/9
2/10
2/11
4/0
4/1
4/2
4/3
4/0
4/1
4/2
4/3
Display Specific MAC Domain Channel Sets
The following command example displays a specific MAC domain channel set:
show cable channel-sets cable-mac 1
An output similar to the following example will occur:
Cable
-mac
----1
1
chSetId
--------0x00000100
0x00000100
DS/US
-------DS
US
Channel Set
----------------------------------------------13/0
13/1
13/2
13/3
1/4
1/5
1/6
1/7
Display Specific Channel Set ID
The following command example displays a specific channel set ID:
show cable channel-sets channel-set-id 0x01000001
An output similar to the following example will occur:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
420
Chapter 14: Cable-side Configuration
Cable
-mac chSetId
DS/US
Channel Set
----- ---------- ----- ----------------------------------------------1 0x01000001 DS
10/0
10/1
10/2
10/3
1 0x01000001 US
2/4
2/5
2/6
2/7
5 0x01000001 DS
9/0
9/1
9/2
9/3
5 0x01000001 US
2/8
2/9
2/10
2/11
Display All Channel Set Configuration Values
The following command example displays all configuration values, including single channel sets:
show cable channel-sets full
An output similar to the following example will occur:
cable
-mac
----1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
1
.
.
.
6
6
6
6
chSetId
DS/US Channel Set
---------- ----- -----------------------0x00000002 DS
13/1
0x00000003 DS
12/2
0x00000004 DS
12/3
0x00000005 DS
12/4
0x00000006 DS
12/5
0x00000007 DS
12/6
0x00000008 DS
12/7
0x00000009 DS
12/8
0x0000000a DS
12/9
0x0000000b DS
12/10
0x0000000c DS
12/11
0x0000000d DS
12/12
0x0000000e DS
12/13
0x0000000f DS
12/14
0x00000010 DS
12/15
0x00000100 DS
12/0
12/1
12/2
12/3
0x00000101 DS
12/4
12/5
12/6
12/7
0x00000102 DS
12/8
12/9
12/10
12/11
0x00000101
0x01000001
0x01000002
0x01000003
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
US
US
US
US
3/4
3/8
3/0
3/4
3/5
3/9
3/1
3/5
3/6
3/10
3/2
3/6
3/7
3/11
3/3
3/7
C4® CMTS Release 8.3 User Guide
421
Chapter 14: Cable-side Configuration
Display All System Fiber Nodes
The following command example displays all system fiber nodes and their associated service groups and ports:
show cable fiber-node
An output similar to the following example will occur:
Fiber Node
-----------FN1
FN1
FN2
FN2
FN3
FN3
FN4
FN4
Cable
MAC
mCMsg
--------1
2
1
2
2
3
2
3
3
4
3
4
4
5
4
5
mDSsg/
mUSsg
----D1
U1
D1
U1
D1
U1
D1
U1
Ports
-------------------------14/0
14/1
14/2
14/3
1/0.0 1/1.0
1/2.0
14/4
14/5
14/6
14/7
1/3.0 1/4.0
1/5.0
14/8
14/9
14/10
14/11
1/6.0 1/7.0
1/8.0
14/12 14/13
14/14 1 4/15
1/9.0 1/10.0 1/11.0
* Indicates that downstream channel is not primary-capable.
Display Specific Fiber Node
The following command example displays a specific fiber node and its associated service groups and ports:
show cable fiber-node FN1
An output similar to the following example will occur:
Cable
Fiber Node
MAC
mCMsg
---------------- ----- ----FN1
1
1
FN1
1
1
mDSsg/
mUSsg
-----U1
D1
Ports
-------------------3/4-7
13/0-3
* Indicates that downstream channel is not primary-capable.
Display All System Fiber Nodes (Detail)
The following command example displays detailed information regarding all system fiber nodes and their associated
service groups and ports:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
422
Chapter 14: Cable-side Configuration
show cable fiber-node detail
An output similar to the following example will occur:
Fiber Node
------------FN1
FN1
FN2
FN2
FN3
FN3
FN4
FN4
Cable
MAC
----1
1
2
2
3
3
4
4
mDSsg/
mCMsg mUSsg
----- -----2
U1
2
D1
3
U1
3
D1
4
U1
4
D1
5
U1
5
D1
Ports
-------------------1/0.0
1/1.0
1/2.0
14/0
14/1
14/2
14/3
1/3.0
1/4.0
1/5.0
14/4
14/5
14/6
14/7
1/6.0
1/7.0
1/8.0
14/8
14/9
14/10
14/11
1/9.0
1/10.0 1/11.0
14/12
14/13
14/14
14/15
* Indicates that downstream channel is not primary-capable.
Display Specific MAC Domain Fiber Nodes
The following command example displays detailed information regarding specific MAC domain fiber nodes and their
associated service groups and ports:
show cable fiber-node cable-mac 1
An output similar to the following example will occur:
Cable
Fiber Node
MAC
mCMsg
---------------- ----- ----FN1
1
1
FN1
1
1
mDSsg/
mUSsg
-----U1
D1
Ports
--------------------------------------3/0
3/1
3/2
3/3
12/0
12/1
12/2
12/3
* Indicates that downstream channel is not primary-capable.
Display Specific MD-CM-SG Fiber Nodes
The following command example displays detailed information regarding specific MAC domain CM signaling group fiber
nodes and their associated service groups and ports:
show cable fiber-node
mCMsg 1
An output similar to the following example will occur:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
423
Chapter 14: Cable-side Configuration
Cable
Fiber Node
MAC
mCMsg
---------------- ----- ----FN1
1
1
FN1
1
1
FN2
2
1
FN2
2
1
FN3
3
1
FN3
3
1
FN4
4
1
FN4
4
1
FN5
5
1
FN5
5
1
mDSsg/
mUSsg
-----U1
D1
D1
U1
D1
U1
D1
U1
D1
U1
Channels
--------------------------------------13/0-3
1/4-7
12/0-3
1/8-11
1/0-3
2/0-3
10/0-3
2/4-7
9/0-3
2/8-11
* Indicates that downstream channel is not primary-capable.
Display Specific MD-DS-SG Fiber Nodes
The following command example displays detailed information regarding specific MAC domain downstream signaling
group fiber nodes and their associated service groups and ports:
show cable fiber-node
mDSsg 1
An output similar to the following example will occur:
Cable
Fiber Node
MAC
mCMsg
---------------- ----- ----FN1
1
1
FN1
1
1
FN2
2
1
FN2
2
1
FN3
3
1
FN3
3
1
FN4
4
1
FN4
4
1
FN5
5
1
FN5
5
1
FN6
6
1
FN6
6
1
mDSsg/
mUSsg
-----U1
D1
D1
U1
D1
U1
D1
U1
D1
U1
D1
U1
Channels
---------------------------------------13/0-3
1/4-7
12/0-3
1/8-11
11/0-3
2/0-3
10/0-3
2/4-7
9/0-3
2/8-11
8/0-3
4/0-3
* Indicates that downstream channel is not primary-capable.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
424
Chapter 14: Cable-side Configuration
Display Specific MD-US-SG Fiber Nodes
The following command example displays detailed information regarding specific MAC domain upstream signaling group
fiber nodes and their associated service groups and ports:
show cable fiber-node
mUSsg 1
An output similar to the following example will occur:
Cable
Fiber Node
MAC
mCMsg
---------------- ----- ----FN1
1
1
FN1
1
1
FN2
2
1
FN2
2
1
FN3
3
1
FN3
3
1
FN4
4
1
FN4
4
1
FN5
5
1
FN5
5
1
FN6
6
1
FN6
6
1
mDSsg/
mUSsg
-----U1
D1
D1
U1
D1
U1
D1
U1
D1
U1
D1
U1
Channels
----------------------------------------13/0-3
1/4-7
12/0-3
1/8-11
11/0-3
2/0-3
10/0-3
2/4-7
9/0-3
2/8-11
8/0-3
4/0-3
* Indicates that downstream channel is not primary-capable.
Display All Cable-mac Service Groups
The following command example displays all system cable-macs and associated service groups:
show cable service-group
An output similar to the following will occur:
Cable
MAC
--1
2
3
4
5
6
mCMsg
----1
1
1
1
1
1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
mDSsg
----1
1
1
1
1
1
mUSsg
----1
1
1
1
1
1
C4® CMTS Release 8.3 User Guide
425
Chapter 14: Cable-side Configuration
Display Specific Cable-mac and Service Groups
The following command example displays a specific cable-mac and its associated service groups:
show cable service-group cable-mac 9
An output similar to the following will occur:
Cable
MAC
--9
mCMsg
----1
mDSsg
----1
mUSsg
----1
Display Specific MD-CM-SG Service Group
The following command example displays a specific MD-CM-SG:
show cable service-group mcmsg 1
An output similar to the following will occur:
Cable
MAC
--1
2
3
4
5
6
mCMsg
----1
1
1
1
1
1
mDSsg
----1
1
1
1
1
1
mUSsg
----1
1
1
1
1
1
Display Specific MD-DS-SG Service Group
The following command example displays a specific MD-DS-SG:
show cable service-group mdssg 1
An output similar to the following will occur:
Cable
MAC
--1
2
3
mCMsg
----1
1
1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
mDSsg
----1
1
1
mUSsg
----1
1
1
C4® CMTS Release 8.3 User Guide
426
Chapter 14: Cable-side Configuration
4
5
6
1
1
1
1
1
1
1
1
1
Display Specific MD-US-SG Service Group
The following command example displays a specific MD-US-SG:
show cable service-group mussg 1
An output similar to the following will occur:
Cable
MAC
--1
2
3
4
5
6
mCMsg
----1
1
1
1
1
1
mDSsg
----1
1
1
1
1
1
mUSsg
----1
1
1
1
1
1
Receive Channel Configurations and Bonding Groups
See the Channel Bonding (page 685) chapter for the configuration of RCCs and Bonding Groups.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
427
Chapter 15
Interface IP Configuration
Overview ..........................................................................................428
Subinterfaces (Multiple VRIs per VRF) for IPv4 ................................428
Interface Configuration ....................................................................431
802.1Q VLAN Tagging (Q-tags) .........................................................435
Loopback Interfaces for Routing Protocols ......................................438
Configuring IP Static Routes .............................................................441
Multiple VRFs ...................................................................................441
Link Aggregation ...............................................................................446
Overview
This section outlines the basic configuration tasks required to implement routing (layer 3) functionality in the C4/c CMTS.
Subinterfaces (Multiple VRIs per VRF) for IPv4
A subinterface is a Virtual Router Interface (VRI), a logical layer 3 interface. Multiple subinterfaces may be defined on a
single interface and associated with the same VRF.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
428
Chapter 15: Interface IP Configuration
Multiple subinterfaces may be defined per physical port and associated with the same VRF, such that there is a many-toone relationship between subinterfaces and VRFs, per cable-side physical interface. The C4/c CMTS system administrator
must also be allowed to change the association between a subinterface and a VRF.
The default VRF is the global VRF that is always present in the C4/c CMTS. It can neither be created nor destroyed. Note
that upon creation of a subinterface, it is implicitly associated with the default VRF.
The relationship of a subinterface to a VRF is many-to-one when viewed from the perspective of a single CAM physical
interface or cable bundle. Each ingress cable-side IP packet must classify to one and only one subinterface. This
classification to a subinterface will be based solely on the source IP address and source physical port of the packet. For
broadcast DHCP packets that have a source IP address of 0.0.0.0, the following rules apply:
If the DHCP packet is sourced from a CM, then the packet will classify to the lowest numbered subinterface that has a
DHCP-Server defined.
If the DHCP packet is sourced from a CPE, then the packet must be classified to the subinterface of the CPE’s associated
CM.
Rules of Operation and Guidelines for Subinterfaces
The C4/c CMTS supports up to 150 IPv4 interfaces (both interfaces and subinterfaces count towards the total of 150).
A subinterface is associated with the default VRF upon creation.
The sum of all subinterface IP addresses may not exceed the total C4/c CMTS system limitation of 1000 IPv4 interfaces.
This limit represents all primary and secondary IP addresses associated with each subinterface.
The following items may be provisioned per subinterface:
IP addresses, both primary and secondary
DHCP Relay Agent including: primary/policy mode selection, secondary dhcp-giaddr identification, DHCP Lease
Query (cable source verify) functionality and DHCP Server IP address definitions
IP filter groups
Directed broadcast support
RIP and OSPF
IGMP
IRDP (ICMP Router Discovery Protocol)
SCM access
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
429
Chapter 15: Interface IP Configuration
Per interface cable source-verify
VRF forwarding
Device classification
The DHCP Relay Agent supports the definition of 10 DHCP Server IP addresses per subinterface.
The DHCP Relay Agent classifies ingress CM DHCP packets to the lowest numbered subinterface associated for each
unique DHCP Server IP address.
When the DHCP Relay Agent is forwarding a packet originating from a CPE, it will forward the packet using as its giaddr
the primary or a secondary address, depending on the dhcp-giaddr mode of the subinterface, that is, of the
subinterface associated with the CM that the CPE is behind. The packet will be forwarded to each unique DHCP server
IP address for CPEs provisioned on that subinterface.
If there are no DHCP servers for CPEs defined for the subinterface associated with the CM that a CPE is behind, then
the DHCP Relay Agent will forward a packet originating from a CPE to each unique DHCP server IP address for CPEs
using as its giaddr the primary address or a secondary address, depending on the dhcp-giaddr mode of the
subinterface, in other words, the lowest numbered subinterface provisioned with that server address.
This allows MSOs to provide a service where different CPEs behind a single cable modem could be serviced by different
ISPs on different subinterfaces. It would require the C4/c CMTS to be provisioned such that the CMs and CPE would be
on different subinterfaces. In addition, it provides a mechanism where different giaddrs could be sent to different
DHCP servers by defining those DHCP servers on different subinterfaces.
The subinterfaces for CMs would be provisioned with DHCP servers marked for use with CMs only, and the
subinterfaces for CPEs would be provisioned with DHCP servers marked for use with CPEs only (although DHCP server
addresses could be the same values).
Subinterfaces cannot be defined for SCM ports.
Network ACLs
For information on configuring network ACLs, see the see "Data Plane Filter IP ACLs (page 950) chapter.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
430
Chapter 15: Interface IP Configuration
Interface Configuration
Common Interface Configuring Commands
This section describes common interface commands which support IP address and helper syntaxes in the C4/c CMTS.
Configure an IP Address on the CAM Interface
The following command is accepted only for provisioned CAM slot/port combinations in the system. This command assigns
an IP address to the CAM interface and determines its DHCP policy:
configure interface cable-mac <mac> ip address <ipAddr> <mask> [secondary] [dhcp-giaddr]
Secondary IP addresses become candidates for the dhcp-giaddr field if and only if the keywords secondary and dhcp-giaddr
are both used.
The command in the example below assigns an IP address of 10.10.1.1 to the specified CAM interface. It enables DHCP
policy for this interface — secondary IP addresses are candidates for the dhcp-giaddr field:
configure interface cable-mac 1 ip address 10.10.1.1 255.255.255.0 secondary dhcp-giaddr
Configure the Helper (DHCP) Addresses
The following command defines the cable-helper information for a CAM slot/port. This command assumes the default
route table:
configure interface cable-mac <mac> cable helper-address <DHCP Server Ip Addr>
[cable-modem|host|any]
If no host type is specified, this command defaults to a value of any.
Configure DHCP Relay Agent Mode for a Cable-mac
The DHCP Relay Agent needs to be enabled for each cable-mac as follows:
config interface cable-mac <mac> cable dhcp-giaddr {primary | policy}
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
431
Chapter 15: Interface IP Configuration
Primary Operation — When the DHCP Relay Agent is defined for Primary operation on a specific CAM subinterface, the
Primary IP address of the interface is used to populate the gi_addr field of all DHCP messages originating from either CMs
or Hosts (CPEs).
Policy Operation — When the DHCP Relay Agent is defined for Policy operation on a specific CAM subinterface, the
Primary IP address of the interface is used to populate the gi_addr field with all DHCP messages originating from CMs. For
Hosts (CPEs), a designated secondary IP address of the interface is used. If multiple secondary IP addresses are defined for
dhcp-giaddr support, then the DHCP Relay Agent uses round-robin selection based on device class, choosing the next entry
in the list with each new DHCP transaction.
Device Classes for DHCP-GIADDR
Device classes may be configured for the DHCP GIADDR:
For example:
configure interface cable-mac 1 ip address 10.10.10.1 255.255.255.0 secondary dhcp-giaddr ?
cpe...Regular CPE device secondary DHCP giaddr
mta
MTA device secondary DHCP giaddr
ps....CableHome PS device secondary DHCP giaddr
stb
DSG STB device secondary DHCP giaddr
Where:
CPE =
MTA =
PS =
STB =
Customer Premise Equipment
Multimedia Terminal Adapter (PacketCable)
Portal Server (CableHome)
Set-top Box (sometimes called DOCSIS Set-top Gateway, or DSG.
Device Classes for the Helper Address
Device classes may be configured for the DHCP helper address. For example:
configure interface cable-mac 1 ip helper-address 10.10.10.1 ?
cable-modem
host
cpe
mta
ps
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Cable modem traffic
All CPE host types traffic
Regular CPE device secondary DHCP giaddr
MTA device secondary DHCP giaddr
CableHome PS device secondary DHCP giaddr
C4® CMTS Release 8.3 User Guide
432
Chapter 15: Interface IP Configuration
stb
any
DSG STB device secondary DHCP giaddr
All types
Monitoring Interfaces
After configuring the C4/c CMTS interfaces, the system is ready to route traffic. Once traffic is generated, you may view the
counters for these interfaces by using the procedures in this section.
How to Monitor Interfaces
Execute the following steps from the SCM prompt to verify traffic is being routed through the C4/c CMTS.
1. Display information about the virtual interfaces in the system, including data counts:
show ip interface
The output will look similar to the following (only a portion of output is shown):
cable-mac 1.0, VRF: default, IP Address: 10.131.0.1/19
Secondary IP Address(es):
*10.181.253.1/24
Physical Address: 0001.5c61.3a46
MTU is 1500
DHCP Policy mode is enabled
DHCP Server Helper Address(es):
10.44.249.46 for Traffic Type "mta"
10.50.31.3 for Traffic Type "cm"
10.50.31.3 for Traffic Type "cpe"
Directed Broadcast is disabled
ICMP unreachables are always sent
Multicast reserved groups joined: None
Source-verify is disabled
InOctets
=
1899028
OutOctets
=
InUcastPkts =
7423
OutUcastPkts=
InDiscards =
0
OutDiscards =
InErrors
=
0
OutErrors
=
InMcastPkts =
0
OutMcastPkts=
loopback 0, VRF: default, IP Address: 10.44.31.200/32
Secondary IP Address(es):
937137
4661
0
0
2
2. Display all interface information about the physical ports in the system, including byte and packet counts:
show interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
433
Chapter 15: Interface IP Configuration
The counts displayed will be the same as those described below except that each count represents the data for one
physical interface (only a portion of output is shown):
cable-mac 1
AdminState:Up
Description: md1
Physical Address: 0001.5c61.3a46
MTU is 1500
Inbound access list is not set
Outbound access list is not set
InOctets
=
230912507
InUcastPkts =
156657
InDiscards =
0
InErrors
=
0
InFiltered =
0
InMcastPkts =
23
OperState:IS
Type:
OutOctets
=
OutUcastPkts=
OutDiscards =
OutErrors
=
231032941
156388
0
0
OutMcastPkts=
23
3. Display information about active and inactive routes:
show ip route detail
Sample output (partial):
VRF Name: default
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
VRF Name: default
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
VRF Name: default
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
VRF Name: default
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
0.0.0.0/0
10.58.10.1
Active-IS
1/0
netmgmt
0 days 00:03:25
tenGigabitEthernet 17/10.0
0.0.0.0/0
10.58.138.1
Active-IS
1/0
netmgmt
0 days 00:03:25
tenGigabitEthernet 18/10.0
10.0.1.9/32
10.58.10.1
Active-IS
110/20
ospf(E2) external type-2
0 days 00:02:30
tenGigabitEthernet 17/10.0
C4® CMTS Release 8.3 User Guide
434
Chapter 15: Interface IP Configuration
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
•
•
VRF Name: default
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
VRF Name: default
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
VRF Name: default
IPv4 Route Dest:
Next Hop:
Active:
Dist/Metric:
Protocol:
Route Age:
Interface:
10.0.1.9/32
10.58.138.1
Active-IS
110/20
ospf(E2) external type-2
0 days 00:02:30
tenGigabitEthernet 18/10.0
200.31.62.0/24
10.58.10.1
Active-IS
115/20
isis(L1) internal level-1
0 days 00:00:07
tenGigabitEthernet 17/10.0
200.31.63.0/24
10.58.10.1
Active-IS
115/20
isis(L1) internal level-1
0 days 00:00:07
tenGigabitEthernet 17/10.0
204.16.96.81/32
10.58.10.1
Active-IS
119/20
ospf(E2) external type-2
0 days 00:00:03
tenGigabitEthernet 17/10.0
802.1Q VLAN Tagging (Q-tags)
MSOs often deploy Layer 3 Virtual Private Networks (VPNs) for commercial customers or other Internet Service Providers
(ISPs). They also use VPNs to segregate their VoIP traffic from their data traffic for traffic engineering purposes. The C4/c
CMTS serves as the Provider Edge (PE) access router. It is required to segregate VPN traffic within the C4/c CMTS domain
using subinterfaces and Virtual Route Forwarders (VRFs). It must signal the VPN association to the adjacent northbound
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
435
Chapter 15: Interface IP Configuration
Provider (P) router. The C4/c CMTS does this using a layer 2 virtual circuit (VC) mechanism with 802.1Q Virtual LAN (VLAN)
tags embedded in the traffic. This allows a single physical network interface to host multiple logical subinterfaces identified
by Q-tags, thereby multiplexing traffic from multiple VPNs over a single physical link.
Normally subinterfaces in the C4/c CMTS segregate packets by source IP address (SIP) prefix only. This works well on the
cable side, but not on the network side. Network subinterfaces typically have incoming SIPs that belong to remote subnets
not hosted by the C4/c CMTS.
The Q-tag feature extends the existing network subinterface function to include layer 2 VCs based on the presence of a Qtag containing a VLANid in the ethernet header, as in the figure below:
Figure 77: Difference between Standard IP and Q-tag Encapsulation
In this case subinterface traffic that arrives or leaves the RCM port is encapsulated in an ethernet frame that has a Q-tag
ethertype (0x8100, as in the figure below) positioned in front of a native ARP or IP ethertype (0x0806 or 0x0800
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
436
Chapter 15: Interface IP Configuration
respectively). Each physical network interface may have from 0 to 255 subinterfaces defined. Each encapsulated
subinterface then behaves like a separate physical interface with the Q-tag as the VC identifier:
Figure 78: IEEE 802.1Q/p Tag Format
Note: This feature does not provide true VLAN support as defined by IEEE 802.1Q for switching tagged ethernet frames
between ports. It merely uses the Q-tag as a means to multiplex multiple ethernet VCs onto a single physical ethernet link.
Q-tags also carry the IEEE 802.1p priority (p-bits). The network subinterface can assign either a fixed priority value to the pbits for all egress Q-tags or a dynamic bi-directional mapping between the IP TOS precedence bits and the Q-tag p-bits for
ingress and egress IP frames. Otherwise, the egress p-bits are set to zero by default and ingress p-bits are ignored.
IP TOS precedence bits, IP Differentiated Services Code Point (DSCP) bits, Class Selector (CS) bits, and 802.1p priority bits
are all defined identically and therefore may be interchanged without any conversion. This capability makes it possible for
intervening layer 2 switches to give the appropriate Quality of Service (QoS) treatment to ethernet frames being switched
between adjacent routers. Also, the DOCSIS 2.0 service flow TOS overwrite capability may be used to impose a TOS byte on
IP frames forwarded by cable modems to the C4/c CMTS based on flow classification rules. Thus, dynamic IP TOS
precedence bit mapping to Q-tag p-bits at the network subinterfaces allows DOCSIS priorities to be propagated through
the adjacent network side layer 2 switches.
For more information, see IEEE standard 802.1Q, Virtual Bridged Local Area Networks, at
http://standards.ieee.org/getieee802/802.1.html.
One Q-tag per Network Interface
This feature supports only the static configuration of one Q-tag per network subinterface. To avoid fragmentation, only
one Q-tag (adding only 32 bits) will be imposed on the egress frame by the RCM port creating a maximum ether frame size
of 1522 octets when a Q-tag is present.
Note: The ARRIS Q-tag feature provides Virtual Circuit (VC) identity to the RCM ports. It does not support VLAN switching
between RCM ports or CAM ports.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
437
Chapter 15: Interface IP Configuration
Loopback Interfaces for Routing Protocols
This section deals with the RSM loopback interface that may be used by OSPF. This interface has all the characteristics of a
physical interface IP address, including packet counts, admin provisioning, socket-layer accessibility, and so on. This new
interface type has a presence on the SCM when in-band management is enabled.
Automatic import of the loopback interface into the SCM protocol stack is consistent with existing in-band management
functionality. Currently, all RSM-based interface IP addresses are imported into the SCM to allow SCM-based applications
to process traffic destined for one of the C4/c CMTS interface IP addresses. Packet redirection from the RCM to the SCM is
a hardware decision based on the IP packet type.
Characteristics of the Loopback Interface
Observe the following guidelines when configuring and administering loopback interfaces:
The C4/c CMTS supports 64 unique loopback interfaces, ranging from 0-63.
The subnet mask must be /32; this implies a host address.
Upon creation of a loopback interface, it will be associated with the default VRF.
If the loopback is taken down, no physical interface is taken out of service (OOS).
If OSPF is enabled on the loopback interface, the network associated with the loopback address must be advertised in a
router LSA. The existing OSPF command must be used:
network <ip address> <mask> area <areaId>
Like physical interfaces, a loopback may reside in only one area.
Routing protocols (RIPv2, ISIS, OSPFv2, or BGP) will not advertise the active IP address.
The active IP address will not have a presence on the RCM.
When in-band management is enabled, loopback interfaces associated with the default VRF are imported into the
SCM’s protocol stack.
If multiple loopback interfaces exist, the lowest value loopback interface is used as the source IP address for SCMoriginated IP datagrams.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
438
Chapter 15: Interface IP Configuration
Table 62. CLI Commands for Active and Loopback Interface
Command
Purpose
configure interface mgmt 6/0 active ip <address> [<netmask>]
Defines the active IP address on the SCM. Valid slot numbers are 6 and 7; either one
may be used to define the active IP address. If the IP mask is not provided, then it
defaults to the mask of the RSM interface ip address.
configure interface mgmt 6/0 no active ip [<address> [<netmask>]]
Removes the active IP address associated with the SCM management port. The IP
address and mask are not required.
configure interface loopback <0…13> [ ip address <address> <netmask> ] [shutdown]
[no]
Defines the syntax to assign an IP address to a loopback interface and admin state
(shutdown or restored to service).
configure interface loopback <loopback number> ip vrf forwarding <vrf_name>
Moves a loopback interface to the VRF specified.
configure interface loopback <0…15> ip ospf cost <metric>
Defines the OSPF cost to reach the loopback interface. No other OSPF parameters are
configurable.
To configure ports for in-band management see 5. Configure RSM Ethernet Connections.
To configure ports for out-of-band management see 6. Out-of-Band Management (Optional).
The figure below depicts a network configuration where a loopback interface is defined for in-band management. In this
figure the active IP address is used for out-of-band management.
This network topology shows the loopback interface used as the "forwarding address" of OSPF Type-7 LSAs that advertise
CAM-side prefixes. Since the loopback interface IP address was previously announced in a Router LSA and is part of the
OSPF AS, ECMP is available, from the switch to the C4/c CMTS, for packets destined for RIP advertised networks.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
439
Chapter 15: Interface IP Configuration
Figure 79: Example of Packet Flow Using Loopback Interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
440
Chapter 15: Interface IP Configuration
Configuring IP Static Routes
How to Add/Delete/View a Static IP Route
1. To add an IP Route:
configure ip route <dest route prefix> <dest route mask> <next-hop ip addr> [metric <0-255>]
Where the value assigned to the metric parameter defines the weight or cost of the route.
2. To delete an IP Route:
configure no ip route <dest route prefix> <dest route mask> <next-hop ip addr>
3. To display the IP Routes:
show ip route
Multiple VRFs
Overview
The Multiple Virtual Routing and Forwarding (Multiple VRFs) feature was developed to support separation of traffic for
different classes of users or for different services. It also allows MSOs to offer multiple service providers. Virtual routing is
a form of policy routing that allows the administrator to assign subscribers to an ISP via simple IP interface configuration
on the C4/c CMTS. The administrator is responsible for programming the DHCP server to assign the proper IP addresses to
the subscriber CMs and CPEs. However, the C4/c CMTS must allow for multiple network configurations, including DHCP
servers that vary in location and number. Separate routing tables are maintained for each VRF. Each data packet routed
through the C4/c CMTS is associated with a VRF and is routed using the corresponding route table. This functionality is
similar to that of BGP/MPLS Layer 3 VPNs.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
441
Chapter 15: Interface IP Configuration
Multiple VRF Functionality
Both cable and network side interfaces can be configured and assigned to a VRF instance.
Network side interfaces must use QTAGs to create logical subinterfaces which may be assigned to a VRF. Cable side
interfaces use the SIP of the ingress packets to associate a logical subinterface with a VRF instance.
Note: For IPv6, ingress link local packets on cable-mac interfaces are handled differently than packets with globally
scoped SIPs.
All ingress IPv6 packets with a SIP and DIP that use a link local address are mapped to the lowest sub-interface
associated with the cable-mac with the following exceptions:
Neighbor Solicitations and Neighbor Advertisements with a destination address or a target address that is globally
scoped are mapped to the sub-interface and VRF of the globally scoped IP address prefix.
Router Solicitations are fanned out to all sub-interfaces associated with the cable-mac.
Multiple instances of VRFs can be created, each with its own route table, interfaces, protocol instances, and so on.
A default VRF instance is always automatically created. This VRF includes all of the interfaces not explicitly assigned to
other VRFs.
The default VRF has a special property that enables it to route traffic to any directly connected subnet in any other
VRF for which the auto-import property is enabled.
Data traffic is isolated by VRF.
Data traffic between two devices within the same VRF scope will be routed within the C4/c CMTS. Data traffic between
two devices in separate VRF scopes will not be routed within the C4/c CMTS unless explicitly configured.
The VRF feature supports IPv4 and IPv6.
There are limits to the number of VRFs and the number of configured routing protocol instances. See Operational
Guidelines (page 443). Contact ARRIS Tech Support when using this feature.
Note: When using multiple VRFs, a default route must exist in the default VRF. If not, the Multiple VRF feature will not
function correctly.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
442
Chapter 15: Interface IP Configuration
Operational Guidelines
The C4/c CMTS can support multiple VRFs with the following restrictions:
Static routing is supported in all 11 VRFs
OSPFv2 can be supported in up to 5 VRFs
OSPFv3 can be supported in up to 5 VRFs
IS-IS can be supported in up to 5 VRFs
RIPv2 can be supported in up to 5 VRFs
BGP is supported in the default VRF.
Multiple protocols can operate in the same VRF (e.g., a common example is to have RIPv2 and OSPFv2 operate in the
same VRF with RIP being redistributed into OSPFv2).
Even though the CLI may allow for configurations beyond the restrictions described here (e.g., more than 11 VRFs),
those configurations are not supported.
Note: Up to a maximum of 64 VRFs are supported if MPLS L3VPN is used and if auto-import is disabled. If not, then a
maximum of only 32 VRFs is supported.
Overview of the Sample Procedure
The configuration example that follows is for demonstration purposes. Such a configuration is not likely to be encountered
in the field, but it serves to show what commands are available.
In the example below we use the default VRF and create four additional ones.
This sample procedure has RIP being redistributed into OSPF and OSPF being redistributed into RIP in every VRF. This is
not a recommended configuration. MSOs might configure one VRF with RIP into OSPF and another VRF with OSPF into
RIP, but in most cases you will see only RIP redistributed into OSPF.
This procedure also has one RCM interface and one cable-mac in each VRF. You can have multiple interfaces (RCM or
cable-macs) in a VRF. One VRF does not have to match the other VRFs in terms of the number of interfaces. The default
VRF, for example, could have three RCM ports and four cable-macs. VRF1 could have only one RCM port and three
cable-macs, and so on.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
443
Chapter 15: Interface IP Configuration
Example of Setting Up Five VRFs
In this procedure you will add four non-default VRFs to the existing default VRF. This procedure assumes that the following
interfaces are using these IP addresses:
Type
GigE
GigE
GigE
GigE
GigE
Cable-mac
Cable-mac
Cable-mac
Cable-mac
Cable-mac
Interface
17/1.0
17/1.1
17/1.2
18/1.1
18/1.2
1
2
3
4
5
Address/subnet
10.0.0.1/24
20.0.0.1/24
30.0.0.1/24
40.0.0.1/24
50.0.0.1/24
110.0.0.1/24
120.0.0.1/24
130.0.0.1/24
140.0.0.1/24
150.0.0.1/24
1. These are the commands you would use to define the interfaces listed above:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
interface
interface
gigabitEthernet 17/1.0
gigabitEthernet 17/1.1
gigabitEthernet 17/1.2
gigabitEthernet 18/1.1
gigabitEthernet 18/1.2
cable-mac 1 ip address
cable-mac 2 ip address
cable-mac 3 ip address
cable-mac 4 ip address
cable-mac 5 ip address
ip address 10.0.0.1 255.255.255.0
ip address 20.0.0.1 255.255.255.0
ip address 30.0.0.1 255.255.255.0
ip address 40.0.0.1 255.255.255.0
ip address 50.0.0.1 255.255.255.0
110.0.0.1 255.255.255.0
120.0.0.1 255.255.255.0
130.0.0.1 255.255.255.0
140.0.0.1 255.255.255.0
150.0.0.1 255.255.255.0
2. Create the VRFs:
configure
configure
configure
configure
ip
ip
ip
ip
vrf
vrf
vrf
vrf
vrf1
vrf2
vrf3
vrf4
3. The purpose of this step is to associate the interfaces with VRFs.
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
gigabitEthernet 17/1.0 ip vrf forwarding
gigabitEthernet 17/1.1 ip vrf forwarding
gigabitEthernet 17/1.2 ip vrf forwarding
gigabitEthernet 18/1.1 ip vrf forwarding
gigabitEthernet 18/1.2 ip vrf forwarding
cable-mac 1 ip vrf forwarding default
cable-mac 2 ip vrf forwarding vrf1
cable-mac 3 ip vrf forwarding vrf2
default
vrf1
vrf2
vrf3
vrf4
C4® CMTS Release 8.3 User Guide
444
Chapter 15: Interface IP Configuration
configure interface cable-mac 4 ip vrf
configure interface cable-mac 5 ip vrf
forwarding vrf3
forwarding vrf4
4. The use of sub-interfaces requires q-tags. Assign Q-tags to the sub-interfaces:
configure
configure
configure
configure
interface
interface
interface
interface
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
17/1.1
17/1.2
18/1.1
18/1.2
encapsulation
encapsulation
encapsulation
encapsulation
dot1q
dot1q
dot1q
dot1q
100
101
102
103
5. (Optional) Enable RIP on one or more of the VRFs:
configure
configure
configure
configure
configure
router
router
router
router
router
rip
rip
rip
rip
rip
vrf
vrf
vrf
vrf
vrf
default enable
vrf1 enable
vrf2 enable
vrf3 enable
vrf4 enable
6. (Optional) Configure the interfaces to which RIP runs:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
router
router
router
router
rip
rip
rip
rip
rip
rip
rip
rip
rip
rip
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
default network 10.0.0.0
vrf1 network 20.0.0.0
vrf2 network 30.0.0.0
vrf3 network 40.0.0.0
vrf4 network 50.0.0.0
default network 110.0.0.0
vrf1 network 120.0.0.0
vrf2 network 130.0.0.0
vrf3 network 140.0.0.0
vrf4 network 150.0.0.0
7. (Optional) Configure the router ID for the OSPF instances:
configure
configure
configure
configure
configure
router
router
router
router
router
ospf
ospf
ospf
ospf
ospf
vrf
vrf
vrf
vrf
vrf
default router-id 10.0.0.1
vrf1 router-id 20.0.0.1
vrf2 router-id 30.0.0.1
vrf3 router-id 40.0.0.1
vrf4 router-id 50.0.0.1
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
vrf
default network 10.0.0.0 0.0.0.255 area 0.0.0.0
vrf1 network 20.0.0.0 0.0.0.255 area 0.0.0.0
vrf2 network 30.0.0.0 0.0.0.255 area 0.0.0.0
vrf3 network 40.0.0.0 0.0.0.255 area 0.0.0.0
vrf4 network 50.0.0.0 0.0.0.255 area 0.0.0.0
default network 110.0.0.0 0.0.0.255 area 0.0.0.0
vrf1 network 120.0.0.0 0.0.0.255 area 0.0.0.0
vrf2 network 130.0.0.0 0.0.0.255 area 0.0.0.0
vrf3 network 140.0.0.0 0.0.0.255 area 0.0.0.0
vrf4 network 150.0.0.0 0.0.0.255 area 0.0.0.0
8. Create the OSPF areas:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
router
router
router
router
ospf
ospf
ospf
ospf
ospf
ospf
ospf
ospf
ospf
ospf
9. (Optional) Enable OSPF on all five VRFs:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
445
Chapter 15: Interface IP Configuration
configure
configure
configure
configure
configure
router
router
router
router
router
ospf
ospf
ospf
ospf
ospf
vrf
vrf
vrf
vrf
vrf
default enable
vrf1 enable
vrf2 enable
vrf3 enable
vrf4 enable
10. (Optional) Redistribute RIP into OSPF:
configure
configure
configure
configure
configure
router
router
router
router
router
ospf
ospf
ospf
ospf
ospf
vrf
vrf
vrf
vrf
vrf
default redistribute rip
vrf1 redistribute rip
vrf2 redistribute rip
vrf3 redistribute rip
vrf4 redistribute rip
Link Aggregation
Link aggregation provides a method for aggregating two or more 1 Gigabit ethernet links into a single logical link known as
a Link Aggregation Group (LAG):
Benefiting from larger capacity links without the costs of 10 Gigabit interfaces
Reducing the number of IP/IPv6 addresses required per chassis
Reducing the number of interfaces to be configured.
LAGs can also help operators manage their data networks. They do this by:
Dynamically bringing down a link-aggregate if the number of its operational ports falls below a certain level as defined
by the min-links configuration
Using Link-Aggregation Control Protocol (LACP) to detect bad configurations between the C4/c CMTS and its neighbors
Increase fault tolerance by allowing the bundling of interfaces from both RCMs.
Provisioning
Operators provisioning ports and configuring LAGs should be aware of the following:
The C4/c CMTS does not support dynamic formation of LAGs; they must be manually provisioned by the operator.
All member ports of a link-aggregate must be connected to the same partner (remote) system.
TenGigabit interfaces are not allowed to be members of a LAG.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
446
Chapter 15: Interface IP Configuration
The LAG must be shut down before adding or removing any ports. Shutting down the link aggregate will bring down
the operational state of all ports included in the LAG; however, the admin state of ports is not affected by changing the
admin state of the link-aggregate port.
SFP+ transceivers — ARRIS does not support LAGs whose member ports use different types of SFPs. Because
performance of member ports using different types of SFPs is unpredictable, ARRIS supports having the same type of
SFP for all member ports of a LAG. See SFP Interfaces for a description of SFP models supported by the C4/c CMTS.
It is possible to change the admin state of an individual port that is a member of a LAG.
All IP/IPv6 (including access-lists) configuration must be removed from all sub-interfaces on a port before the port can
be added to a link-aggregate.
Link-Aggregate ports can be configured Static or LACP:
Static configuration is simply the configuration of a LAG without enabling LACP. Users opting for static
configuration should perform manual checks to ensure their LAGs are connected correctly. Static ports are
considered operational once the physical link is operational.
An LACP port is considered operational once the physical link is operational and the port has finished negotiating
via LACP with its peer.
The pre-defined minimum number of ports must be operational (min-links) before the link aggregate is considered
operational. If the number of operational links on the C4/c CMTS falls below the min-links requirement, then the LAG is
taken out of service.
If one or more ports of the LAG go out of service and the minimum links requirement is violated, then the LAG will be
taken out of service. If the operational state of the one or more OOS ports changes to in-service and the min-links
requirement is once again met, then the link-aggregate is restored to service.
Note: Both the C4/c CMTS and remote (i.e. partner) side must be configured with minimum links functionality enabled and
with the same number of minimum links for this requirement to be fully operational. For example, a LAG on the C4/c CMTS
may continue to receive traffic from a north-bound router even when the min-links requirement is violated locally.
LACP Forwarding
A LAG is said to be LACP forwarding when data traffic is being received and transmitted. A link can cease to be LACP
forwarding for a number of reasons including:
The link has been configured to be administratively down.
The link has been physically disconnected, e.g., the cable has been unplugged.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
447
Chapter 15: Interface IP Configuration
The partner side is not LACP forwarding.
An LACP timeout occurs, indicating that the partner is LACP out-of-sync.
Feature Interactions
It should be stressed that LAG works with all the supported routing protocols; however, the purpose of this section is to
note unexpected effects on other supported features.
Link Overload Protection
If Equal Cost Multipath (ECMP) is being utilized with LAGs, and links in a particular LAG go down, traffic will continue to be
sent on the remaining link(s); however, a point may be reached where the remaining link(s) become overloaded. The
Minimum Number of Links feature helps prevent overloading of the remaining links by setting the number of links that can
be lost before ECMP reroutes using a different LAG.
BSoD
Performance of the BSoD feature is enhanced with link aggregation. Without LAGs, a primary and a secondary (backup) 1G
link are used for BSoD, one on each RCM. All traffic goes in and out the primary link. If the primary side RCM goes down, a
side switch occurs and the former backup link then becomes primary. However, there is no immediate notification to the
northbound router that a shift has occurred. The router first needs to detect "link down" on the old primary link before it
can shift traffic to send to the new primary link of the C4/c CMTS. This traffic shift is therefore delayed.
Using a LAG that spans RCMs eliminates the need for a BSoD backup link because all data is passed by means of the LAG. If
an RCM goes down, only a portion of the links are impacted in the LAG, and it is still operational with the same capacity as
the previous primary link. Because the northbound router is communicating over just the one LAG for all traffic, if an RCM
goes down there is no need to shift traffic. Therefore there is no delay.
Command Line Interface
CLI commands related to specific functions unique to LAG configuration and usage are provided in the table below. For
additional details concerning these commands refer to Command Line Descriptions.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
448
Chapter 15: Interface IP Configuration
Table 63. Basic Configuration Commands
Purpose or Description
Command
configure interface link-aggregate <0-9> min-links <1-8>
Create link aggregate group <0-9> and define the
[no]
minimum number of links required for this LAG to
remain operational. The C4/c CMTS rejects this
command if the LAG is administratively up. The [no]
option returns the LAG to the default minimum of
one link.
Configure LAG <0-9> to use LACP
Configure LAG <0-9> to run in static mode.
The LAG must be administratively down in order to
change this parameter.
configure interface link-aggregate <0-9> lacp enable
configure interface link-aggregate <0-9> lacp disable
Configure LAG <0-9> to initiate messaging (active
mode)
Configure LAG <0-9> to respond to incoming
messaging (passive).
The default mode is active.
configure interface link-aggregate <0-9> lacp mode active
configure interface link-aggregate <0-9> lacp mode passive
Define rate at which the C4/c CMTS expects to
receive LACP messages:
Slow is one message every 30 seconds, with a
timeout of 90 seconds. Fast is one message every
second, with a timeout of three seconds. The LAG
does not need to be administratively down to
change this parameter. The [no] option returns the
LAG to the default of slow.
NOTE: because the C4/c CMTS always matches the
advertised rate of the remote partner, this
parameter does not determine the rate at which
the CMTS transmits LACP messages.
configure interface link-aggregate <0-9> lacp timeout
<fast|slow> [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
449
Chapter 15: Interface IP Configuration
Purpose or Description
Command
Add or remove an NSI port to/from a LAG. The RCM
slots are 17 and 18 in the C4/c CMTS chassis.
If no LAG exists when this command is entered,
then a LAG with that lag-number is internally
created with default values. However, deleting the
membership of this gigabitEthernet port in that LAG
will not auto-delete the LAG (i.e., the "no" version
of this command), even if this is the last port in the
LAG.
Only gigabitEthernet links (ports 0-9) can be added
to a LAG. If a gigabitEthernet port is already
assigned to a different LAG, the command is
rejected. If the LAG is administratively IS, the
command is rejected.
Ports cannot be directly moved from one LAG to
another; they are deleted from the first LAG and
then assigned to the second LAG.
The [no] version removes the gigabitEthernet port
from the LAG.
configure interface gigabitEthernet <rcm slot>/<rcm port>
link-aggregate <lag-number>
configure interface gigabitEthernet <rcm slot>/<rcm port>
link-aggregate [<lag-number>] [no]
These commands assign the specified IPv4 or IPv6
address to the specified LAG. The same rules used
for gigabitEthernet link IP address configuration
apply to LAGs:
An IPv4 primary address must be configured
before configuring a secondary address.
Both IPv4 and IPv6 addresses may be assigned
to the same LAG.
Multiple IPv6 and secondary IPv4 addresses are
allowed.
An address must be configured before the LAG
goes operationally into service.
configure interface link-aggregate <lag number> ip address
<ipv4 address> <ipv4 mask> [secondary] [description] [no]
configure interface link-aggregate <lag number> ipv6 address
<ipv6 address/prefix> [eui-64] [link-local] [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
450
Chapter 15: Interface IP Configuration
Purpose or Description
Command
If the [no] version is used with an IP address, it
deletes just that address, leaving the LAG still in
existence. The [no] version without an address
deletes the entire LAG.
Bring up the LAG:
configure interface link-aggregate * shutdown no
Table 64. Other CLI Commands Related to Link Aggregation
Purpose or Description
Command
Clear the counts for a LAG:
clear counters link-aggregate <WORD>
Clear the IPv6 neighbor counts for a LAG:
clear ipv6 neighbors link-aggregate <WORD> [<ipv6-address>]
Set the threshold for the number of LACP
messages:
configure slot <RCM slot: 17 or 18> proto-throttle-rate <> lacp
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
451
Chapter 15: Interface IP Configuration
Purpose or Description
Command
show lacp [gigabitEthernet <slot>/<port>] [{counters | internal
Display minimum information about the LACP
| partner | sys-id}]
protocol. (Shows protocol settings, counts, and
status for one or all gigabit Ethernet ports.) For
each gigabitEthernet link running LACP, the show
lacp counters command shows:
LACP PDUs sent
LACP PDUs received
LACP PDU errors
For each gigabitEthernet link running LACP, the
show lacp internal and show lacp
partner commands show the following for the
local actor and for the partner, respectively:
LACP flags (fast/slow, active/passive)
LACP state
Port priority
Port Operational state
Port ID
Port state
Display routing information for the LAG port:
show interface link-aggregate <>
show ip igmp groups detail link-aggregate <WORD>
show ip igmp groups host link-aggregate <WORD>
show ip igmp interfaces link-aggregate <WORD>
show ip interface [brief] link-aggregate [<WORD>]
show ipv6 interface [brief] link-aggregate [<WORD>]
show ipv6 neighbors link-aggregate <WORD>
show ipv6 ospf interface [brief] link-aggregate [<WORD>]
show ipv6 ospf neighbor [detail] link-aggregate <WORD>
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
452
Chapter 15: Interface IP Configuration
Purpose or Description
Command
show ipv6 route [vrf <WORD>] [include-inactive] [detail] linkaggregate <WORD>
Indicate that the gigabitEthernet link is in a LAG
show interface gigabitEthernet <>
show port status <>
Indicate that the gigabitEthernet link is in a LAG
show port status network
In addition to showing membership in a LAG, the show ip interface gigabitEthernet <>
output shows whether or not the dataplane is
passing traffic (i.e., some sort of LACP summary
state).
In addition to showing membership in a LAG, the show ipv6 interface gigabitEthernet <>
output of this command shows whether or not
the dataplane is passing traffic (i.e., some sort of
LACP summary state).
The CLI includes the LACP throttle value and the
LACP packets received and packets dropped
counts to the output for this command.
show proto-throttle-rate
The CLI includes a new ipv6 ping command that
will specify the LAG.
ping ipv6 <WORD> [repeat-count <INT>] [source <WORD>] [timeout
<INT>] [size <INT>] [tos <INT>] [ttl <INT>] [payload <WORD>]
[validate] output-interface link-aggregate <WORD>
Sample Show Commands
Sample outputs of the most commonly used show commands will be provided.
show interface link-aggregate 1
link-aggregate 1
AdminState:Up
LACP: Enabled
Min-links: 1
Member Ports:
17/2 17/3 17/4 17/5
Description:
Physical Address: 0001.5c24.8e82
MTU is 1500
Inbound access list is not set
Outbound access list is not set
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
OperState:IS
C4® CMTS Release 8.3 User Guide
453
Chapter 15: Interface IP Configuration
InOctets
=
1460
InUcastPkts =
0
InDiscards =
0
InErrors
=
0
InMcastPkts =
14
Outbound access list is not set
OutOctets
=
OutUcastPkts=
OutDiscards =
OutErrors
=
OutMcastPkts=
1276
0
0
0
12
S - Port Suspended State, D - Port Down State
In the output above Suspended State identifies a port which is link up but has not completed LACP negotiations. Down
State identifies a port which is down.
show lacp summary
---- LAG ---Admin
Oper
LAG Num
LACP
State
State
Member Ports
===============================================================================
1
Enabled
Up
IS
17/2 17/3 17/4 17/5
S - Port Suspended State, D - Port Down State
show lacp sys-id
0000,0001.5c24.8e80
show lacp counters
Link
LACPDUs
Interface
Agg
Sent
Recv
Error
================================================================
gigabitEthernet 17/2
1
26
315
0
gigabitEthernet 17/3
1
27
290
0
gigabitEthernet 17/4
1
27
260
0
gigabitEthernet 17/5
1
27
222
0
show lacp local
-------------------- Port ------------------- ------- LAG ------Link
LACP
Admin
Link
Admin Oper
Oper
Admin Oper
Min
Interface
Agg
State
State
State Id (0x)
Key
Key
State State State Links LACP Flags
=======================================================================================================================
gigabitEthernet 17/2
1
Bndl
Up
IS
0000,0003 0x2
0x2
0x3f
Up
IS
1
Fast/Active
gigabitEthernet 17/3
1
Bndl
Up
IS
0000,0004 0x2
0x2
0x3f
Up
IS
1
Fast/Active
gigabitEthernet 17/4
1
Bndl
Up
IS
0000,0005 0x2
0x2
0x3f
Up
IS
1
Fast/Active
gigabitEthernet 17/5
1
Bndl
Up
IS
0000,0006 0x2
0x2
0x3f
Up
IS
1
Fast/Active
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
454
Chapter 15: Interface IP Configuration
show lacp partner --- Local --- ----------------------------- Partner's Info --------------------------Link
LACP
LACP
Port
Port
Port
Port
Interface
Agg
State
Flags
System ID
Id (0x)
AdminKey OperKey State
================================================================================================================
gigabitEthernet 17/2
1
Bndl
Slow/Active
8000,30e4.db0e.9d80 8000,0104
0x0
0x1
0x3d
gigabitEthernet 17/3
1
Bndl
Slow/Active
8000,30e4.db0e.9d80 8000,0105
0x0
0x1
0x3d
gigabitEthernet 17/4
1
Bndl
Slow/Active
8000,30e4.db0e.9d80 8000,0106
0x0
0x1
0x3d
gigabitEthernet 17/5
1
Bndl
Slow/Active
8000,30e4.db0e.9d80 8000,0107
0x0
0x1
0x3d
Configuring Link Aggregation
The following procedure is a basic configuration script that results in the creation of LAG number 1, with LACP enabled and
set to active mode and fast messaging and timeout. This link aggregate group includes four ports from each RCM.
Note: The values chosen for steps 1 through 4 are the defaults. If this is a new LAG, skip to step 5. It will create the LAG
with the defaults shown in steps 1 through 4.
1. Create LAG number 1:
configure interface link-aggregate 1
min-links 1
2. Enable LACP for LAG 1:
configure interface link-aggregate 1
lacp enable
3. Configure active mode for LACP messaging:
configure interface link-aggregate 1
lacp mode active
4. Set the lacp message rate and timeout to slow:
configure interface link-aggregate 1
lacp timeout slow
5. Assign an IPv4 address to LAG 1:
configure interface link-aggregate 1
[description]
ip address <ipv4 address> <ipv4 mask> [secondary]
6. Assign an IPv6 address to LAG 1:
configure interface link-aggregate 1
ipV6 address <ipv6 address/prefix> <eui-64> [link-local]
7. Add the following ports to LAG 1:
configure
configure
configure
configure
interface
interface
interface
interface
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
17/1
17/2
17/3
17/4
link-aggregate
link-aggregate
link-aggregate
link-aggregate
1
1
1
1
configure
configure
configure
configure
interface
interface
interface
interface
gigabitEthernet
gigabitEthernet
gigabitEthernet
gigabitEthernet
18/1
18/2
18/3
18/4
link-aggregate
link-aggregate
link-aggregate
link-aggregate
1
1
1
1
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
455
Chapter 15: Interface IP Configuration
8. Put the LAG in service:
configure interface link-aggregate * shutdown no
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
456
Chapter 16
Dynamic Routing Protocols
Overview of Dynamic Routing .......................................................... 457
Border Gateway Protocol ................................................................. 458
Intermediate System-Intermediate System ..................................... 468
Multiple Topology IS-IS .................................................................... 478
Open Shortest Path First Version 2 .................................................. 495
Open Shortest Path First Version 3 .................................................. 502
Routing Information Protocol .......................................................... 521
Route Redistribution for IPv4 Addresses ......................................... 532
Policy-Based Routing (PBR) .............................................................. 545
Overview of Dynamic Routing
This chapter describes the various routing protocols currently supported in the C4/c CMTS.
Note: For more information regarding routing protocol event messages, see Logging (page 1031).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
457
Chapter 16: Dynamic Routing Protocols
Border Gateway Protocol
Border Gateway Protocol (BGP) is the routing protocol used to exchange routing information across the Internet.
BGP was developed to allow interconnection between Internet Service Providers (ISPs), and to allow end-users to connect
to more than one ISP. BGP is a solution that can accommodate the vast expanse of the Internet, and also handle multiple
connections to unrelated routing domains.
BGP Version 4
BGP Version 4 (BGP-4) is the most widely deployed version of BGP.
BGP-4 provides the mechanisms for supporting Classless Inter-Domain Routing (CIDR). These mechanisms include:
Support for advertising a set of destinations as an IP prefix.
Eliminating the concept of network "class" within BGP.
BGP-4 also introduces mechanisms that allow aggregation of routes, including aggregation of Autonomous System (AS)
paths.
BGP-4 Implementation
The following points summarize BGP-4 implementation on the C4/c CMTS:
BGP-4 complies with RFC 1771 and the MIB RFC 1657.
If the C4/c CMTS is used in either an eBGP or iBGP configuration, it must be for an MSO’s internal network only. Given
the size of the C4/c CMTS hardware routing table, approximately 32K routes, the C4/c CMTS must not be defined as an
AS-border router running either eBGP or iBGP to the internet.
The C4/c CMTS supports a single instance of BGP, and it must be on the default VRF.
iBGP routes have a default administrative distance of 200.
eBGP routes have a default administrative distance of 20.
BGP-4 supports Autonomous System Confederations. This feature is useful in reducing full mesh configurations in iBGP.
A BGP AS is split into multiple sub-ASs. Within a sub-AS, there is a full mesh of iBGP.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
458
Chapter 16: Dynamic Routing Protocols
BGP-4 supports Equal Cost Multi-Path (ECMP). In addition to being supported for eBGP, ECMP must be supported
when multiple next-hops exist for a prefix within an AS. This implies that ECMP is available for iBGP configurations. The
allowable range for ECMP is 1–4 routes. A value of 1 implies that ECMP is disabled.
BGP-4 supports Route Reflection. This is an alternative to full mesh iBGP. A route reflector is responsible for readvertising routes to an entire AS, but a route reflector client requires no additional functionality beyond the original
BGP specification.
BGP-4 supports the Communities Attribute. This allows similar routes to be grouped for the same policy treatment.
BGP-4 sends BGP Updates on card/port maintenance state changes. For example, if port maintenance indicates a state
change in a CAM subnet, this change triggers a BGP update to all peers indicating the reachability of the CAM-side
subnets.
BGP-4 supports Route-Refresh. This feature allows the C4/c CMTS to dynamically request a re-advertisement of the
Adj-RIB-Out from a BGP peer.
BGP-4 supports Capabilities Advertisement. This feature is required to advertise BGP capabilities to peers, such as
route refresh. When VPN extensions are available and two BGP speakers wish to exchange labeled VPN-IPv4 NLRI, they
must use BGP Capabilities Advertisement to ensure both peers are capable of processing such NLRI.
The C4/c CMTS, acting as a BGP Server, allows for a socket bind to any provisioned C4/c CMTS IP interface, including
loopback interfaces. For iBGP connections, loopback interfaces are the preferred IP address when establishing
connections since they represent the router itself and not any particular interface that is subject to state changes.
Additionally, the C4/c CMTS supports binding to a "wildcard" address. A "wildcard" address is assumed if the "update
source" parameter is not defined during the creation of a BGP instance.
BGP supports Route Reflector Client (RRC) and Confederation, but does not support peer groups or route filtering. In
the anticipated use of the C4/c CMTS as an RRC, there will be only a handful of routers north of the C4/c CMTS.
Therefore, the neighbor commands contain the IP addresses of the neighbors, but not of peer groups.
The C4/c CMTS supports BGP route filtering via route maps, which is required for C4/c CMTS peers with multiple ISPs
and is recommended in confederations. Without this filtering, the C4/c CMTS could advertise routes received from one
peer to another peer, becoming an unintentional transit router.
The C4/c CMTS permits system administrators to redistribute static, connected, RIP, or OSPF routes into BGP.
The C4/c CMTS supports BGP Route Aggregation.
Interior and Exterior BGP
The C4/c CMTS supports a full complement of features associated with Interior BGP (iBGP) and Exterior BGP (eBGP), with a
few noted exceptions.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
459
Chapter 16: Dynamic Routing Protocols
Some MSOs use BGP as the protocol of choice for advertising C4/c CMTS CAM-side IP prefixes. In such an application iBGP
is used throughout their regional networks with a full mesh of interconnected peering routers.
The C4/c CMTS in this environment is required to run iBGP peering sessions with various routers in a particular Regional
Area Network (RAN). iBGP peers typically communicate using loopback interfaces.
Loopback interfaces are not assigned to any particular interface; therefore, a particular BGP session is not interrupted by
an interface failure. Interface IP addresses may also be changed without impacting BGP sessions.
Typically, iBGP networks require the following:
BGP Autonomous System: A routing domain in which all routers are associated with the same AS. iBGP peering
sessions occur within an AS.
BGP Route Reflector: A route reflector supports the readvertisement of routes between iBGP peers.
BGP Route Reflector Client: Depends on a route reflector to advertise its routes to the entire BGP AS
Since iBGP full mesh topologies scale at a rate of N(N-1)/2, two methods have been developed to reduce the number of
BGP peering sessions:
AS confederations
Route reflectors
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
460
Chapter 16: Dynamic Routing Protocols
AS confederations break the AS down into smaller entities. The figure below depicts a BGP autonomous system that is
broken down into sub-ASs.
Figure 80: iBGP with Confederations to Reduce Full Mesh Peering
Within each sub-AS, a full mesh exists between all peers; however, a single eBGP peering session is sufficient for
interconnection between sub-ASs.
Note: From the perspective of ASs outside of the confederation, the original AS does not appear any different. That is, the
sub-AS configuration is contained within the original AS.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
461
Chapter 16: Dynamic Routing Protocols
Route Reflectors
Route reflectors are commonly used to reduce the number of peering groups. In the figure below, the C4/c CMTS acts as a
route reflector client, and shows a complete RAN running iBGP with route reflection.
Figure 81: BGP Network Topology with Route Reflections and an OSPF Overlay
In the example above, each region is defined as a RAN with a single OSPF area. OSPF summarization occurs at each area
border router, and therefore OSPF SPF calculations occur for each RAN.
Scalability Benefit
This network topology provides a substantial scalability benefit to the C4/c CMTS in that it does not need to establish a
peering session with each BGP enabled router in the RAN.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
462
Chapter 16: Dynamic Routing Protocols
Loopback Interfaces
To allow BGP sessions to be established between peering routers via loopback interfaces, the routers must communicate
the reachability of the various loopback interfaces. Typically, these interfaces have a network mask of /32. Advertisement
of loopback interfaces is accomplished using an overlay OSPF network.
Multiprotocol BGP (MP-BGP)
BGP was initially developed for IPv4 Internet Classless Inter-Domain Routing (CIDR). Thus, by default, BGP carries IPv4
routing information (via Network Layer Reachability Information (NLRI) together with a number of specific path attributes
like ORIGIN, AS_PATH, NEXT_HOP (as an IPv4 address), etc.
MP-BPG extensions, as described in RFC4760, will enable BGP to carry routes for other Network Layer protocols or Address
Families (AF) like IPv6, VPN IPv4, VPN IPv6, L2VPN, etc. MP-BGP also introduces two new attributes: Multiprotocol
Reachable NLRI (MP_REACH_NLRI) and Multiprotocol Unreachable NLRI (MP_UNREACH_NLRI).
The introduction of MP-BGP will allow for IPv6 BGP peers along with the sharing of IPv6 NLRI information. The introduction
of IPv6 will change BGP behavior in the cases of Prefix Lists, Route Maps, Peer Addressability and General Setup.
Transport Network Layer Address
BGP is based on sessions between peers and uses TCP for transport. The TCP session is formed between two BGP systems
(usually routers) and the two systems would be called BGP Peers or BGP Neighbors. The two systems must be reachable
via IP so, unless they are locally inter-connected, an IGP must run to provide the base for IP connectivity for BGP. The BGP
peers can be internal (IBGP) when the peering session is between two systems within the same ASN, or external (EBGP),
when a router inter-connects with other AS on the Internet.
A BGP router (or speaker) is always identified by a 4 byte integer number, the BGP Identifier. It identifies a BGP speaker
and is the same for every peer and on any interface. The BGP ID has to be unique within an ASN, and it also cannot overlap
with any other BGP speaker within an AS. This is why one of the IP addresses of the BGP system is usually assigned as a
BGP ID.
A BGP speaker also needs a transport IP address to establish BGP peering sessions. This address can be different for each
peer or interface. However, for simplicity and reliability, it is usually recommended that the transport address is the same
for all peers and is set to the IP address of the loopback interface of the BGP speaker. This way, the state of the BGP
speaker is not dependent on the state of an interface and is always up.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
463
Chapter 16: Dynamic Routing Protocols
Consequently, the underlying network protocol can be either IPv4 or IPv6. It is also possible to have two sessions between
two peers concurrently, one over IPv4 and one over IPv6.
The network layer transport protocol is important because it will determine the type of network layer transport address or
source address the BGP speaker will use (IPv4 or IPv6). When a route is originally advertised by a BGP speaker, the
NEXT_HOP attribute (or the next hop field in the MP_REACH_NLRI attribute) is set, by default, to the BGP speaker’s
network layer transport address. Thus, when the transport network layer address is an IPv4 address, the NEXT_HOP will
have to be an IPv4 address. Similarly, if the BGP source address is IPv6, then the NEXT_HOP will have to be an IPv6 address.
MP-BGP Implementation
The C4/c CMTS previously only supported BGP for IPv4 only. Starting in Release 8.2.5, the C4/c CMTS will support BGP for
IPv6 by implementing MP-BGP. The following points summarize MP-BGP implementation:
Multi Protocol BGP (MP-BGP) is originally defined in RFC 2283
MP-BGP is a framework that extends the original IPv4 BGP to be able to carry other address families.
MP-BGP introduces the concept of Address Family Indicators (AFI) and Sub-address Family Indicator (SAFI)
Some of the address families MP-BGP supports is:
IPv4 (AFI=1) --> Unicast (SAFI=1), Multicast (SAFI=2), VPNv4 (SAFI=128)
IPv6 (AFI=2) --> Unicast (SAFI=1), Multicast (SAFI=2), VPNv6 (SAFI=128)
Release 1.1 will support two address families:
AFI=1, SAFI=1 and AFI=2, SAFI=1
MP-BGP for IPv6 is used the same way we use BGP for IPv4
All addresses involved are IPv6
Router-ID for MP-BGP (IPv4 or IPv6) in default VRF only
The C4/c CMTS can be configured to run:
MP-BGP for IPv4 only
MP-BGP for IPv6 only
MP-BGP for IPv4 and IPv6
IPv4 routes will be advertised using MP-BGP for IPv4 only (not using IPv6 BGP Neighbor)
IPv6 routes will be advertised using MP-BGP for IPv6 only (not using IPv4 BGP Neighbor)
MP-BGP uses same message types as BGP
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
464
Chapter 16: Dynamic Routing Protocols
Open
Update
Keep Alive
Notifications
Route Refresh
Open Message has been modified in MP-BGP to communicate what address families this BGP Router supports (a.k.a.
Capabilities)
Update Message has been modified to support encoding advertisements for different address families.
The C4/c CMTS IPv6 address family will support all comparable IPv4 BGP features along with the following BGP features for
the IPv6 Address family:
IPv6 Address Family route redistribution with optional filtering from:
Connected
Static
OSPFv3
ISIS
IPv6 PD
Peer activation/deactivation configuration
Peer maximum prefix and maximum prefix warning configuration
Peer route update filtering (inbound and outbound)
Peer next-hop-self
Peer route reflector client
Aggregate address advertisements
The C4/c CMTS will support 10,000 BGP learned IPv6 routes in the data plane Forwarding Information Base (FIB).
BGP CLI Show Commands
To get the complete list of supported BGP and MP-BGP CLI commands, use the following command syntax:
show all-commands | include bgp
show all-commands | include route-map
show all-commands | include prefix-list
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
465
Chapter 16: Dynamic Routing Protocols
The above commands will also list all the show commands. For more information on these CLI commands, see the
Command Line Descriptions.
Sample Configuration Commands for BGP
The following three configurations are meant as examples only. They provide the command sequences for configuring BGP
on the C4/c CMTS for operation with two neighbors. MSOs should customize BGP configuration to suit their own network
environments and applications.
Basic Configuration for IPv4
The following commands show the basic configuration for IPv4:
#configure BGP router instance
configure router bgp 65005 bgp router-id 10.44.5.200
configure router bgp 65005 no shutdown
#configure IPv4 neighbor
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
bgp
bgp
bgp
bgp
bgp
bgp
neighbor 10.55.3.1 remote-as 65005
neighbor 10.55.3.1 update-source loopback 0
neighbor 10.55.3.1. password 096bdb4d8816f52675a7b615b54e529 hidden
65005 address-family ipv4 neighbor 10.55.3.1 next-hop-self
65005 address-family ipv4 neighbor 10.55.3.1 activate
neighbor 10.55.3.1 no shutdown
#configure IPv4 route redistribution for this BGP instance.
configure router bgp 65005 address-family ipv4 redistribute connected
configure router bgp 65005 address-family ipv4 redistribute rip
Basic Configuration for IPv6
The following commands show the basic configuration for IPv6:
#configure BGP router instance
configure router bgp 65005 bgp router-id 10.44.5.200
configure router bgp 65005 no shutdown
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
466
Chapter 16: Dynamic Routing Protocols
#configure IPv6 neighbor
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
bgp
bgp
bgp
bgp
bgp
bgp
neighbor fc00:cada:c405:603::1 remote as 65005
neighbor fc00:cada:c405:603::1 update-source loopback 0
neighbor fc00:cada:c405:603::1 password 096bdb4d8816f52675a7b615b54e529 hidden
65005 address-family ipv6 neighbor fc00:cada:c405:603::1 next-hop-self
65005 address-family ipv6 neighbor fc00:cada:c405:603::1 1 activate
neighbor fc00:cada:c405:603::1 no shutdown
#configure IPv6 route redistribution for this BGP instance
configure router bgp 65005 address-family ipv6 redistribute connected
configure router bgp 65005 address-family ipv6 redistribute pd
Basic Configuration for IPv4 and IPV6 (simultaneously)
The following commands show the basic configuration for IPv4 and IPv6
#configure BGP router instance
configure router bgp 65005 bgp router-id 10.44.5.200
configure router bgp 65005 no shutdown
#configure IPv4 router redistribution for this BGP instance
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
bgp
bgp
bgp
bgp
bgp
bgp
neighbor 10.55.3.1 remote-as 65005
neighbor 10.55.3.1 update-source loopback 0
neighbor 10.55.3.1 password 096bdb4d8816f52675a7b615b54e529 hidden
65005 address-family ipv4 neighbor 10.55.3.1 next-hop-self
65005 address-family ipv4 neighbor 10.55.3.1 activate
neighbor 10.55.3.1 no shutdown
#configure IPv6 neighbor
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
bgp
bgp
bgp
bgp
bgp
bgp
neighbor fc00:cada:c405:603::1 remote as 65005
neighbor fc00:cada:c405:603::1 update source loopback 0
neighbor fc00:cada:c405:603::1 password 096bdb4d8816f52675a7b615b54e529 hidden
65005 address-family ipv6 neighbor fc00:cada:c405:603::1 next-hop-self
65005 address-family ipv6 neighbor fc00:cada:c405:603::1 1 activate
neighbor fc00:cada:c405:603::1 no shutdown
#configure IPv6 route redistribute for this BGP instance
configure router bgp 65005 address-family ipv6 redistribute connected
configure router bgp 65005 address-family ipv6 redistribute pd
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
467
Chapter 16: Dynamic Routing Protocols
Examples of BGP Route Policy
The following commands show an example of a BGP Route Policy.
#using route-map on redistributes
configure route-map comcon permit 10 set community 0:9999
configure router bgp 65001 address-family ipv4 redistribute connected route-map comcon
#using distribute-list (using access-list) to redistribute routes
configure access-list 99 permit any
configure router bgp address-family ipv4 distribute-list 99 out connected
#configure prefix list to use in route-map to be applied on neighbor
configure
configure
configure
configure
configure
configure
ip prefix-list PL1 permit 1.2.3.4/32
route-map MPBGP permit 10 match community regexp 9999
route-map MPBGP permit 20 match ip address prefix-list PL1
route-map MPBGP permit 20 set metric 20
router bgp neighbor 10.70.3.1 route-map MPBGP in
router bgp neighbor 10.70.3.1 route-map MPBGP out
Intermediate System-Intermediate System
Overview
Intermediate System-Intermediate System (IS-IS) is a routing protocol developed by the International Standards
Organization (ISO). In this link-state protocol, IS routers exchange routing information based on a single metric to
determine network topology. It is similar to Open Shortest Path First (OSPF) in the TCP/IP network.
The C4/c CMTS supports:
Both IPv4 and IPv6 protocols.
Q-tags with IS-IS traffic for both IPv4 and IPv6.
The maximum number of IP routes shown in the following table.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
468
Chapter 16: Dynamic Routing Protocols
Table 65. Number of IPv4 and IPv6 Routes Supported by the C4/c CMTS
Protocol Type
Total
Prefix Delegation and Route Injection (PDRI)
Dynamic
Static
IPv4
32,000
n/a
n/a
n/a
IPv6a
28,000b
16,000
10,000c
2,000
a. The IPv6 routes are in addition to the IPv4 total.
b. The total of IPv6 routes allowed is the sum total of the PDRI, Dynamic, and Static routes.
c. The total number of IPv6 dynamic routes is a combination of MP-BGP, OSPFv3 or IS-IS IPv6 routes.
Note: IS-IS runs only on the default VRF.
CLNP Addressing/NSAP Address Format
CLNP is an abbreviation of Connectionless Network Protocol. NSAP stands for Network Service Access Point. The CLNP
node-based addressing scheme is one of the concepts retained for use in advertising IP networks. CLNP network
addressing is mandatory on IP routers and therefore both CLNP and IP addresses need to be provisioned on the C4/c
CMTS.
CLNP Address
The CLNP address is analogous to an IP loopback interface in so far as it is node-based versus interface-based. As such, a
single CLNP address suffices per IS-IS node, within a specific IS-IS area.
NSAP Address
Each CLNP (NSAP) address is composed of three parts:
An area identifier (area ID) prefix
A system identifier (SysID)
An N-selector
A group of routers within a specific area shares the same area ID.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
469
Chapter 16: Dynamic Routing Protocols
IS-IS Routers
IS-IS routers may be multi-homed, implying they reside in multiple Level 1 areas (or Level 2 backbone) and therefore
require multiple NSAP addresses. Since IS-IS is an IGP, the NSAP addressing scheme need not be globally unique and
private IP addresses may be defined within an AS.
IS-IS Network Topology, Unique Level 1 Areas
IS-IS defines a multi-layered hierarchy called Level 1 and Level 2 routing.
Level 1 Routers
Level 1 routers belong to a common area and are engaged in level one routing. These routers are aware of their local
topology only and require Level 2 routers to communicate inter-area routing information.
Level 2 Routers
In practice, most Level 2 routers are also Level 1 routers; that is, they serve a local area and connect to the IS-IS backbone.
Two-Level Network Topology
The figure below depicts an IS-IS two-level network topology with both NSAP and IP addressing. NSAP addresses are based
on the defined IP loopback addresses and must be manually provisioned as such.
Note: In this example IP hosts are not assigned NSAP addresses and do not in any way participate in IS-IS routing.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
470
Chapter 16: Dynamic Routing Protocols
Each router in a Level 1 area builds an area unique LSP database with its peers. Disjointed Level 1 areas must be joined
together via a Level 2 (backbone) area.
Figure 82: IS-IS Level 1 and 2 Routing
By default, Level 1 areas are considered "stub" areas because they rely on a default route to forward traffic out of the area.
However, route leaking from Level 2 and Level 1 areas allows for more intelligent inter-area routing.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
471
Chapter 16: Dynamic Routing Protocols
Adjacencies
Adjacencies formed are based on interface circuit-type (either Level 1, Level 2, or both) and the provisioned area ID in the
NSAP address.
Note: The circuit-type is encoded in the Intermediate System to Intermediate System Hello (IIH) packet.
The figure above defines the following adjacencies:
Router R1: Circuits are Level 2 only since the router resides completely in a Level 2 area. R1 will form Level 2
adjacencies with R2 and R3.
Routers R2 and R3: These routers are considered Border routers since north-bound circuits are defined as Level 2, and
south-bound circuits are defined as Level 1. R2 defines adjacencies with R1 and R5 while R3 defines adjacencies with
R1 and R4.
Routers R4 and R5: Circuits may be defined as Level 1 only since these are edge routers connected to the IS-IS
backbone.
Dynamic Hostname Support
The C4/c CMTS will support use of the dynamic hostname in IS-IS link state packets (LSPs). The C4/c CMTS will support the
use of TLV 137 to communicate its hostname and receive hostname updates from peer routers.
In the IS-IS routing domain, a system ID is used to represent each router. The system ID is part of the network entity title
that is configured for each IS-IS router.
The dynamic hostname mechanism uses link-state protocol (LSP) flooding to distribute the router-name-to-system-ID
mapping information across the entire network. Every router on the network will try to install the system ID-to-router
name mapping information in its routing table.
To enable the C4/c CMTS to send dynamic hostname Type-Length-Value (TLV) for IS-IS routes, use the following command:
configure router isis hostname dynamic
The default value is enabled and will persist across a system reboot. To turn off dynamic hostname TLV sending, use the
following command:
configure router isis hostname dynamic no
Note: Receiving, decoding, and processing Dynamic Hostname TLVs from peer routers is always on.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
472
Chapter 16: Dynamic Routing Protocols
Dynamic Host Mapping Table
If a router that has been advertising the dynamic name Type-Length-Value (TLV) on the network suddenly stops the
advertisement, the mapping information last received will remain in the dynamic host mapping table for up to one hour.
This allows the network administrator to display the entries in the mapping entry during a time when the network
experiences problems.
Entering the following command, displays the entries in the system-ID-to-router-name mapping table:
show isis hostname
IS-IS Network Topology — Multi-homing
Multi-homing provides the capability to define multiple NSAP addresses, one per area.
Primary Purpose
The primary purpose of IS-IS multi-homing is to merge otherwise disparate, Level 1 areas into one large unified area. The
LSP database thus becomes unified across the individual Level 1 areas.
Note: IS-IS multi-homing is not analogous to the IP concept of sub-interfaces with multiple secondary IP addresses. IP
multi-homing implies that multiple logical subnets can be defined on the same physical link.
Additional Benefit
Multi-homing provides the benefit of not having to take down an IS-IS network during:
NSAP address renumbering.
IS-IS area merging.
IS-IS splitting.
Packet Flow Between IS-IS Systems
IS-IS defines three packet type categories, similar to that defined in OSPF:
Hello packets.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
473
Chapter 16: Dynamic Routing Protocols
Link State Packets (LSPs).
Sequence number packets.
Hello Packets — As is the case with OSPF, Hello packets are used to establish and maintain adjacencies between directly
connected IS-IS neighbors.
Link State Packets — Link state packets are used to distribute the actual IP routing information.
Sequence Number Packets — Sequence number packets control the distribution of LSPs to allow for correct
synchronization of the Link State database.
Designated Intermediate System (DIS) and Reliable Flooding of LSPs
The DIS is sometime referred to as the Pseudonode, which is an abstraction for representing broadcast links as network
nodes. This reduces the amount of router-to-router communications on a broadcast network and as a consequence,
reduces the amount of information (IS-IS PDUs) that is exchanged when multiple nodes interconnect on a LAN.
The election of the DIS is based on interface priority and, as a tie breaker, the MAC address used to encapsulate the Hello
packet. As is the case with OSPF, the DIS plays the critical role of LSP flooding; however it should be noted that unlike
OSPF, there does not exist the concept of a backup DIS (known in OSPF nomenclature as a BDR).
If the DIS becomes unavailable, then DIS election must be restarted.
To help mitigate a DIS outage, the hello interval for DIS routers is set at three times the rate of non-DIS routers. This
scheme allows for quick detection of DIS failures and replacement.
In addition to flooding responsibilities, the DIS will advertise a pseudonode LSP, which represents the broadcast link itself.
This LSP has a zero cost and allows for communication on the broadcast link between individual non-DIS routers.
The DIS router is not guaranteed to remain the DIS if a new router with a higher priority shows up on the LAN; likewise,
there is no mechanism for making a router ineligible for DIS operation.
IS-IS peers are said to be adjacent after Hello packets are exchanged, but before the LSP database synchronization is
complete. This differs from OSPF, and may cause transient routing problems when adjacent routers do not have a
complete forwarding table representing routes within the IS-IS domain.
Use of the LSP overload bit can help solve this issue by informing adjacent routers that traffic should not be sent to a
router whose LSP overload bit is set.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
474
Chapter 16: Dynamic Routing Protocols
On broadcast links, periodic flooding by all IS-IS nodes is used to ensure that adjacent peers maintain a consistent view of
the LSP database for a particular IS-IS Domain. That is, all IS-IS nodes broadcast their LSPs to all attached devices. These
flooded LSPs are not acknowledged and require support from the DIS to maintain a consistent view of the LSP database.
To help support reliable flooding of LSPs, the DIS periodically sends out a CSNP that contains a summary of every known
LSP within the IS-IS domain.
To purge a LSP from the IS-IS domain, the remaining lifetime field is set to 0, and the LSP is flooded throughout the
network. Only the originator of the LSP may purge it from the domain.
IS-IS Point-to-Point
With the implementation of IS-IS point-to-point adjacencies, also referred to as point-to-point links, Broadcast links will
continue to be supported as the default configuration, with a point-to-point link being an optional configuration on an
interface or subinterface basis. IS-IS point-to-point links simplify the Shortest Path Found (SPF) calculation and reduce both
the network convergence times and the size of the topology database.
The C4/c CMTS still supports the existing IS-IS for IPv4/IPv6 and Multi-Topology as previously implemented.
Point-to-Point and Broadcast
Point-to-point and broadcast are the two predominant circuit types used by link state routing protocols such as IS-IS and
OSPF.
The most important difference between point-to-point and broadcast is that broadcast circuits utilize the concept of a
designated router, and are represented topologically as virtual nodes in the network topology graph.
From a functional aspect the IS-IS and OSPF routing protocols are treated differently with respect to:
Establishing neighbor adjacencies.
Flooding link state information.
Representing the topology.
Calculating the Shortest Path First (SPF) and protocol packets.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
475
Chapter 16: Dynamic Routing Protocols
Point-to-Point Advantages
Compared with broadcast circuits, point-to-point circuits afford more straightforward IGP operation. Specifically, there is
no designated router involved, and there is no representation of the pseudonode or network Link State Advertisement
(LSA) in the link state database.
For IS-IS, there also is no periodic database synchronization which results in improved network convergence performance.
Conversely, if there are more than two routers on the LAN media, the traditional view of the broadcast circuit will reduce
the routing information in the network. When there are only two routers on the LAN, it makes more sense to treat the
connection between the two routers as a point-to-point circuit.
Maintaining IS-IS Point-to-Point Adjacency
The C4/c CMTS maintains IS-IS point-to-point adjacency by supporting both:
IS-IS Point-to-Point Operation over LAN in Link State Routing Protocols (RFC 5309).
Three-Way Handshake for IS-IS Point-to-Point Adjacencies (RFC 5303).
Point-to-Point Operation over LAN — IS-IS Point-to-Point operation over LAN circuit extension is mainly concerned with
pure IP routing and forwarding. Because the circuit physically is broadcast, the IS-IS protocol packets need to have MAC
addresses. From a link-layer point of view, those packets are IS-IS LAN packets.
IS-IS uses Level 1 Hello packet (PDU type 15) and Level 2 Hello packet (PDU type 16) when it is configured for a LAN
environment. However, the protocol uses only Point-to-Point Hello packet (PDU type 17) for both Level 1 and Level 2
adjacencies.
With the Point-to-Point over-LAN extension, the difference between a LAN and a point-to-point circuit can be made purely
by configuration. The C4/c CMTS implements the mechanisms for early detection of misconfiguration. Specifically:
If the circuit is configured as the point-to-point type and receives LAN Hello packets, the router must discard the
incoming packets.
If the circuit is a LAN type and receives point-to-point hello packets, it must discard the incoming packets.
If the system ID or the router ID of an incoming hello packet does not match the system ID or the router ID for an
established adjacency over a Point-to-Point over-LAN circuit, the packet must be discarded.
Both routers on a LAN must support the Point-to-Point over-LAN extension and both must have the LAN segment
configured as a Point-to-Point over-LAN circuit for successful operation. The C4/c CMTS must form adjacency and exchange
routes when both the C4/c CMTS and remote router are configured for Point-to-Point.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
476
Chapter 16: Dynamic Routing Protocols
Three-Way Handshake — Previously, only a two-way handshaking mechanism was provided when establishing adjacencies
on point-to-point links. The basic mechanism for this operation is that each side declares the other side to be reachable if a
Hello packet is detected. Once this occurs, each side then sends a Complete Sequence Number PDU (CSNP) to trigger
database synchronization.
This mechanism is not reliable, and is alleviated with the implementation of three-way handshake for point-to-point
adjacency. This is accomplished by providing an optional mechanism (TLV 240) that allows each system to report its
adjacency three-way state, thus allowing a system to only declare an adjacency to be up if it knows that the other system is
receiving its IS-IS Hello (IIH) packets.
Point-to-Point Adjacencies for IS-IS Multi-Topology
Adjacencies on point-to-point interfaces are formed with IS-IS routers not implementing MT extensions. If a local router
does not participate in certain MTs, it will not advertise those MT IDs in its IIHs and thus will not include that neighbor
within its LSPs.
On the other hand, if an MT ID is not detected in the remote side's IIHs, the local router is not allowed to include that
neighbor within its LSPs. The local router is not allowed to form an adjacency if they don't have at least one common MT
over the interface.
Configuring IS-IS Point-to-Point
The following CLI commands are provided to configure a circuit as point-to-point:
configure interface gigabitethernet <WORD> isis network point-to-point [no]
configure interface tengigabitethernet <WORD> isis network point-to-point [no]
A user must shut down the IS-IS protocol on the circuit first before enabling or disabling IS-IS Point-to-Point.
Related MIB — The Point-to-Point command populates the
isisCircPtToPtOverLAN MIB of the IsisCircEntry MIB table with either TRUE (1) or FALSE (2).
Related Show Command — With this feature, the output of the
seen in the following output example:
show isis interface
command has been updated, as
tenGigabitEthernet 17/2.0 is Up, line protocol is Up
CLNS/IS-IS protocol processing enabled
MTU 1500
Circuit Type: level-1 point-to-point
Interface Number 0x1000012f (268435759), local circuit ID 0x0
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
477
Chapter 16: Dynamic Routing Protocols
Circuit Admin State: enabled, Oper State: Up
Level-1
Metric: 10, Wide-metric: 10, Priority: 64, Circuit Id: E6-22.00
Hello Timer: 3000msec, Hello Multiplier: 10, DRHello Timer:
1000msec
LSP Throttle: 30msec, LSP Retransmit Interval: 5sec
Number of active level-1 adjacencies: 1
Multiple Topology IS-IS
Multiple Topology IS-IS Overview
The C4/c CMTS software supports two topologies for IS-IS:
IPv4
IPv6
IS-IS could be configured as IPv4 only, IPv6 only, or IPv4-IPv6 only, but only a single Shortest Path First (SPF) would run per
level for IPv4 or IPv6.
Overcoming Single SPF Limitation
To overcome the single SPF limitation, Multiple Topology IS-IS (MT IS-IS) is implemented in the C4/c CMTS.
When MT IS-IS is enabled, the C4/c CMTS will maintain multiple instances of the IS-IS routing tree and will run two
separate SPFs:
One for standard topology IPv4
The other for IPv6 topology
In the example of the figure below, Router B in Area 1 is IPv4 only, and all other routers are IPv4-IPv6.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
478
Chapter 16: Dynamic Routing Protocols
Figure 83: Example of IS-IS and MT IS-IS Topologies
MT IS-IS Not Enabled
If MT IS-IS is not enabled, the best path from A to D is: A –> B –> C –> D
However, any IPv6 traffic from A –> D would be lost in Router B.
MT IS-IS Enabled
When MT IS-IS is enabled, two separate SPFs will run and maintain the two separate topologies, IPv4 and IPv6.
As a result:
The best IPv4 path from A to D is: A –> B –> C –> D
The best IPv6 path from A to D is: A –> E –> F –> C –> D
Adjacencies
Users need to know what they are running, IPv4 or IPv6, in order for the adjacency to be included in the correct topology.
If the interface only supports the IPv4 topology, the C4/c CMTS will not use the new MT TLV in the IS-IS Hello packet, and it
will not be advertised in the new TLV. Thus, the exclusion of MT TLV in the IIH implies that this interface is only part of the
IPv4 topology.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
479
Chapter 16: Dynamic Routing Protocols
Broadcast Interface Adjacencies
All the routers on a LAN that implement the MT extension may advertise their MT capability TLV in their IIHs. If there is at
least one adjacency on the LAN interface that belongs to this MT capable router, the corresponding MT IS Reachable TLV
will be included in its LSP.
Establishing Adjacency
Adjacency will always be established between two routers on a LAN whether they have a common MT or not. This
guarantees that all the routers on the LAN can correctly elect the same DIS.
Unsupported MT
If the C4/c CMTS receives an LSP from another router with an unsupported MT, the LSP will be installed into the database
but no routes will be calculated using that LSP.
Advertising MT Reachable Intermediate Systems in LSPs
The C4/c CMTS will include within its LSPs (in the Reachable Intermediate TLV-only) adjacent nodes that are participating in
the corresponding topology and advertise such TLVs only if it participates itself in the corresponding topology. There is no
change to the pseudo-node LSP construction.
Note: The Standard Reachable Intermediate Systems TLV is acting here as MT IPv4 (ID #0), the equivalent of the newly
introduced MT Reachable Intermediate Systems TLV.
Acknowledging MT IS TLV
A router must announce the MT IS TLV when there is at least one adjacency on the interface that belongs to this MT,
otherwise it may announce the MT IS TLV of an adjacency for a given MT if this interface participates in the LAN.
MT IP Forwarding
The C4/c CMTS supports MT IPv4 (ID #0) and MT IPv6 (ID #2) on the same interface.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
480
Chapter 16: Dynamic Routing Protocols
Routing Information Base
Each MT belongs to a Distinct Address Family and routes learned within that topology are installed in a separate Routing
Information Base (RIB). The RIB associated with MT IPv4 (ID#0) is the default IPv4 VRF.
Displaying Active IPv4 Routes
To display all active IPv4 routes in this RIB, use the following command:
show ip route isis
Note: Be aware this can be an extremely large output.
The C4/c CMTS displays an output similar to the following:
Codes:
(L1) internal level-1, (L2) internal level-2, (eL1) external level-1, (eL2) external level-2
(S) summary,
(IA) internal area,
(E1) external type-1,
(E2) external type-2
(I) internal,
(E) external
VRF Name
IP Route Dest.
Act PSt Next Hop
Metric Protocol
Dist Route Age
Interface
=============== ================== === === =============== ====== ========
==== ============ =============
default
4.4.4.0/24
Yes IS 10.85.9.1
30
isis(L1)
115
0 00:11:39 gigE
17/9.0
default
3.3.3.0/24
Yes IS 10.85.9.1
30
isis(L1)
115
0 00:11:39 gigE
17/9.0
Displaying Active IPv6 Routes
To display all active IPv6 routes in the RIB associated with the IPv6 (MT#2), use the following command:
show ipv6 route isis
Note: Be aware this can be an extremely large output.
The C4/c CMTS displays an output similar to the following:
Codes:
(L1) internal level-1,
(eL2) external level-2
(E1) external type-1,
(E) external
ACT Active-IS,
(L2) internal level-2,
(S) summary,
(E2) external type-2,
(eL1) external level-1,
(IA) inter-area,
(I) internal,
OOS Inactive-OOS
Dist/
IPv6 Route Dest / mask Act Next Hop
Metric
Protocol
====================== === ============================= ======= =========
2001:1111:2222:3333/64 ACT fe80::20b:45ff:feb6:100
115/20 isis(L1)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
IS Inactive-IS,
RouteAge
========
00:10:52
Interface
===========
gigE 17/9.0
C4® CMTS Release 8.3 User Guide
481
Chapter 16: Dynamic Routing Protocols
2001:1234:0:3::/64
ACT fe80::20b:45ff:feb6:100
2001:1234:0:4::/64
ACT fe80::20b:45ff:feb6:100
2002:2001:3001:3002/64 ACT fe80::20b:45ff:feb6:100
y
116/10
116/10
115/20
isis(L2)
isis(L2)
isis(L1)
00:08:07
00:08:07
00:10:52
gigE
gigE
gigE
17/9.0
17/9.0
17/9.0
Configuring MT IS-IS on the C4/c CMTS
Configuration tasks associated with MT IS-IS are accomplished by means of:
An enable procedure
A disable procedure
A default metric modification procedure.
Enable MT IS-IS
Use this procedure to enable MT IS-IS on the C4/c CMTS.
Note: IS-IS must be disabled at the system level before enabling MT.
1. Disable IS-IS at the system level with the following command:
configure router isis shutdown
2. Enable MT IS-IS on the C4/c CMTS:
configure router isis address-family ipv6 multi-topology
3. Once MT IS-IS has been enabled, IS-IS can once again be enabled with the following command:
configure router isis shutdown no
Disable MT IS-IS
Use this procedure to disable MT IS-IS on the C4/c CMTS.
Note: IS-IS must be disabled at the system level before disabling MT.
1. Disable IS-IS at the system level with the following command:
configure router isis shutdown
2. Disable MT IS-IS using the following command:
configure router isis address-family ipv6 multi-topology no
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
482
Chapter 16: Dynamic Routing Protocols
3. Once MT IS-IS has been disabled, IS-IS can once again be enabled with the following command:
configure router isis shutdown no
Modify the Default Metric
Use this procedure to modify the MT IS-IS default metric on the C4/c CMTS.
1. Use the following command only if the default metric needs to be changed.
configure interface gigabitethernet <slot/port> isis ipv6 metric <1-16777215> [level-1 | level-2]
[no]
2. To return to the default metric of 10, use the [no] parameter.
Sample Configuration
The following sample configuration shows a C4/c CMTS directly connected to another router.
The following information is from the C4/c CMTS:
show running-config verbose interface gigabitethernet 17/9
configure
configure
configure
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
interface
interface
interface
gigabitethernet
gigabitethernet
gigabitethernet
gigabitethernet
gigabitethernet
gigabitethernet
gigabitethernet
gigabitethernet
17/9 no shutdown
17/9.0 ip address 10.85.0.2 255.255.255.0
17/9.0 ipv6 enable
17/9.0 ipv6 address fc00:cada:c435:600::2/64
17/9.0 ip router isis
17/9.0 ipv6 router isis
17/9.0 isis protocol no shutdown
17/9.0 ipv6 no nd ra suppress
The following information is also from the C4/c CMTS:
show running-config verbose | begin router isis
configure
configure
configure
configure
configure
configure
configure
router
router
router
router
router
router
router
isis
isis
isis
isis
isis
isis
isis
net 47.0001.0100.8500.9002.00
metric-style wide level-1-2
address-family ipv4 enable
address-family ipv6 multi-topology
address-family ipv6 redistribute connected level-2
address-family ipv6 enable
no shutdown
The following information is from the next-hop router:
show running-config interface gigabitethernet 2/20
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
483
Chapter 16: Dynamic Routing Protocols
Building configuration...
Current configuration : 282 bytes
!
interface GigabitEthernet 2/20
description C4-35,port 17/9
ip address 10.85.9.1 255.255.255.0
ip router isis
ipv6 address 2001:db8:C435:1709::1/64
ipv6 router isis
end
The following information is also useful:
show running-config | router isis
router isis
net 47.0001.0100.8500.9001.00
metric-style wide
no hello padding
log-adjacency-changes
redistribute connected
redistribute static ip
!
address-family ipv6
multi-topology
redistribute static
exit-address-family
!
Example Show Commands
The following section contains a group of commands most commonly used to display MT IS-IS information.
Displaying Current IS-IS Configuration
To display the current IS-IS configuration, use the following command:
show isis database detail
To display the IS-IS neighbor output including the remote router’s MT setting, use the following command:
show isis neighbor
The system output would look similar to the following:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
484
Chapter 16: Dynamic Routing Protocols
System ID
-------------0100.8500.9001
0100.8500.9001
Interface
---------------------gigabitEthernet 17/9.0
gigabitEthernet 17/9.0
SNPA
--------------000b.45b6.0100
000b.45b6.0100
State
----Up
Up
Sys
Hold
----9
9
Adj
Type
---L1/2
L1/2
Type
---L1
L2
Circuit Id
Protocol
------------------- -------TR11.01
M-ISIS
TR11.01
M-ISIS
Note: If the connected router does not support MT IS-IS, the protocol will display IS-IS in the above output. If the neighbor
row says ‘IS-IS’, it only indicates that the remote IS is using regular IS-IS TLVs on that interface. The C4/c CMTS can still send
MT TLVs based on its own system/interface configuration. The C4/c CMTS's MT support can be verified using the show
isis protocol command. If you are not seeing IPv6 routes and you think you should, then an inconsistent configuration
between the C4/c CMTS and the northern router may be the cause.
To display the multi-topology system status, use the following command:
show isis protocol
The system display will look similar to the following:
IS-IS Router: default
IS-IS routing Enabled
IS-IS multi-topology Enabled
System ID: 0100.6000.0002
IS-Type: level-1
Max LSP Lifetime: 1200 seconds
Max time to delay after LSP event: 5000 milliseconds
Override the routing calculation delay when the number of updates reach: infinite
Routing calculation is to be paused: 10000 times
Manual area address(es):
47.0001
Interfaces supported by IS-IS:
gigabitEthernet 17/0 - IP - IPv6 level-L1
gigabitEthernet 18/0 - IP - IPv6 level-L1
Administrative distances:
Internal level-1: 115
Internal level-2: 116
External level-1: 117
External level-2: 118
Metrics:
Level-1 generates: wide
Level-1 accepts:
wide
Level-2 generates: wide
Level-2 accepts:
wide
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
485
Chapter 16: Dynamic Routing Protocols
To display the IS-IS neighbor detail output which includes both the remote router’s protocol (M-ISIS or IS-IS) and the
remote router’s topologies (IPv4 and IPv6), use the following command:
show isis neighbor detail
The system output would look similar to the following:
System ID
Interface
SNPA
State Hold Type Type
Circuit Id
-------------- --------------------- ------------- ----- ---- ---- ---- ---------------0100.8500.9001 gigabitEthernet 17/9 000b.45b6.0100
Up
9 L1/2 L1
TR11.01
Area Address(es): 47.0001
IP Address(es): 10.60.0.1
IPv6 Address(es): fe80::215:15ff:fe15:1177
Uptime: 0 days 00:49:52
Priority: 64
Support restart signalling: Yes
Restart state: Not Restarting
Adjacency suppressed: N
Topology: IPv4, IPv6
Protocol
--------M-ISIS
Note: If the only "IS-IS" is displayed in the Protocol column above, this command will not display the Topology.
Using the command show isis database detail <word> (where <word> in this example is the LSP PDU identifier
"TR11.00-06") to display the IS-IS database detail, including the MT extensions, use the following command:
show isis database detail TR11.00-06
The system output would look similar to the following:
IS-IS Level-2 Link State Database
LSPID
LSP Seq Num
-----------------------------TR11.00-06
0x000001BF
Metric: 0
IPv6 (MT-IPv6)
Metric: 0
IPv6 (MT-IPv6)
Metric: 0
IPv6 (MT-IPv6)
Metric: 10
IPv6 (MT-IPv6)
LSP Checksum LSP Holdtime
------------ -----------0xF0E8
602
2001:1111:2222:3333:/64
2001:1234:0:3:/64
2001:1234:0:4:/64
2002:2001:3001:3002:/64
ATT/P/OL
-------0/0/0
To display the IPv4 IS-IS route information, use the following command:
show ip route isis
The system output would look similar to the following:
Codes:
(L1) internal level-1,
(S) summary,
(I) internal,
(L2) internal level-2,
(IA) internal area,
(E) external
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
(eL1) external level-1,
(E1) external type-1,
(eL2) external level-2
(E2) external type-2
C4® CMTS Release 8.3 User Guide
486
Chapter 16: Dynamic Routing Protocols
VRF Name
===============
default
default
IP Route Dest.
==================
4.4.4.0/24
3.3.3.0/24
Act
===
Yes
Yes
PSt
===
IS
IS
Next Hop
===============
10.85.9.1
10.85.9.1
Metric
======
30
30
Protocol
========
isis(L1)
isis(L1)
Dist Route Age
==== ============
115
0 00:11:39
115
0 00:11:39
Interface
=============
gigE
17/9.0
gigE
17/9.0
By adding the "ipv6" parameter to the command, the IPv6 IS-IS route information will be displayed:
show ipv6 route isis
The system output would look similar to the following:
Codes:
(L1) internal level-1,
(eL2) external level-2
(E1) external type-1,
(E) external
ACT Active-IS,
(L2) internal level-2,
(S) summary,
(E2) external type-2,
(eL1) external level-1,
(IA) inter-area,
(I) internal,
IS Inactive-IS,
OOS Inactive-OOS
Dist/
IPv6 Route Dest / mask Act Next Hop
Metric
Protocol
====================== === ============================= ======= =========
2001:1111:2222:3333/64 ACT fe80::20b:45ff:feb6:100
115/20 isis(L1)
2001:1234:0:3::/64
ACT fe80::20b:45ff:feb6:100
116/10 isis(L2)
2001:1234:0:4::/64
ACT fe80::20b:45ff:feb6:100
116/10 isis(L2)
2002:2001:3001:3002/64 ACT fe80::20b:45ff:feb6:100
y
115/20 isis(L1)
RouteAge
========
00:10:52
00:08:07
00:08:07
00:10:52
Interface
===========
gigE 17/9.0
gigE 17/9.0
gigE 17/9.0
gigE 17/9.0
CLI Commands for ISIS
The following table lists many of the CLI commands that are used in configuring and managing both MT IPv4 (ID #0) and
MT IPv6 (ID #2) routing.
For more information on these CLI commands see Command Line Descriptions.
Table 66. List of Commands Related to IS-IS and MT IS-IS
Purpose
Command
Clears the IS-IS counters.
clear isis counters
Enables [disables] IS-IS routing for IPv4 / IPv6
on the specified interface.
Note: the loopback interface is always passive.
configure
configure
configure
configure
configure
configure
configure
configure
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
interface
interface
interface
interface
interface
interface
interface
interface
cable <WORD> ip router isis [no]
cable <WORD> ipv6 router isis [no]
cable-mac <WORD> ip router isis [no]
cable-mac <WORD> ipv6 router isis [no]
loopback <INT> ip router isis [no]
loopback <INT> ipv6 router isis [no]
gigabitethernet <WORD> ip router isis [no]
gigabitethernet <WORD> ipv6 router isis [no]
C4® CMTS Release 8.3 User Guide
487
Chapter 16: Dynamic Routing Protocols
Purpose
Command
configure interface tengigabitethernet <WORD> ip router isis
[no]
configure interface tengigabitethernet <WORD> ipv6 router isis
[no]
Configures the IS-IS authentication for LSPs.
configure interface cable <WORD> isis authentication key-chain
[no]
configure interface cable-mac <WORD> isis authentication
key-chain [no]
configure interface gigabitethernet <WORD> isis authentication
key-chain [no]
configure interface tengigabitethernet <WORD> isis
authentication key-chain [no]
Configures the IS-IS authentication mode for
LSPs.
configure interface
configure interface
[no]
configure interface
mode [no]
configure interface
authentication mode
cable <WORD> isis authentication mode [no]
cable-mac <WORD> isis authentication mode
gigabitethernet <WORD> isis authentication
tengigabitethernet <WORD> isis
[no]
Configures the level of adjacency for the
specified interface. The Level 1 adjacency may
be established if there is at least one area
address in common between this system and
its neighbors.
configure
configure
configure
[no]
configure
[no]
interface cable <WORD> isis circuit-type [no]
interface cable-mac <WORD> isis circuit-type [no]
interface gigabitethernet <WORD> isis circuit-type
Configures the complete sequence number
PDUs (CSNPs) interval for the specified
interface. This command only applies to the
designated router on the specified interface.
configure
configure
configure
[no]
configure
[no]
interface cable <WORD> isis csnp-interval [no]
interface cable-mac <WORD> isis csnp-interval [no]
interface gigabitethernet <WORD> isis csnp-interval
Configures the length of time in milliseconds
between hello packets for the specified
interface when it is DIS.
configure interface cable <WORD> isis ds-hello-interval [no]
configure interface cable-mac <WORD> isis ds-hello-interval [no]
configure interface gigabitethernet <WORD> isis
ds-hello-interval [no]
configure interface tengigabitethernet <WORD> isis
ds-hello-interval [no]
Computes the hello interval based on the hello
multiplier so that the resulting hold time is 1
second.
configure interface cable <WORD> isis hello-interval [no]
configure interface cable-mac <WORD> isis hello-interval [no]
configure interface gigabitethernet <WORD> isis hello-interval
[no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
interface tengigabitethernet <WORD> isis circuit-type
interface tengigabitethernet <WORD> isis csnp-interval
C4® CMTS Release 8.3 User Guide
488
Chapter 16: Dynamic Routing Protocols
Purpose
Command
configure interface tengigabitethernet <WORD> isis
hello-interval [no]
Computes the hello interval based on the hello
multiplier so that the resulting hold time is 1
second.
configure interface cable <WORD> isis hello-interval minimal
configure interface cable-mac <WORD> isis hello-interval minimal
configure interface gigabitethernet <WORD> isis hello-interval
minimal
configure interface tengigabitethernet <WORD> isis
hello-interval minimal
Configures the number of IS-IS hello packets a
neighbor must miss before the router declares
the neighbor to be down on the specified
interface. This time determines how quickly a
failed neighbor is detected so that routes can
be recalculated.
configure interface cable <WORD> isis hello-multiplier [no]
configure interface cable-mac <WORD> isis hello-multiplier [no]
configure interface gigabitethernet <WORD> isis hello-multiplier
[no]
configure interface tengigabitethernet <WORD> isis
hello-multiplier [no]
Configures the time delay between successive
LSPs for the specified interface.
configure
configure
configure
[no]
configure
[no]
interface cable <WORD> isis lsp-interval [no]
interface cable-mac <WORD> isis lsp-interval [no]
interface gigabitethernet <WORD> isis lsp-interval
Configures the maximum packet size of LSPs
for the specified interface.
configure
configure
configure
configure
interface
interface
interface
interface
cable <WORD> isis lsp-mtu [no]
cable-mac <WORD> isis lsp-mtu [no]
gigabitethernet <WORD> isis lsp-mtu [no]
tengigabitethernet <WORD> isis lsp-mtu [no]
Configures the default metric for the specified
interface.
Note: the loopback interface is always passive.
configure
configure
configure
configure
configure
interface
interface
interface
interface
interface
cable <WORD> isis metric [no]
cable-mac <WORD> isis metric [no]
loopback <INT> isis metric [no]
gigabitethernet <WORD> isis metric [no]
tengigabitethernet <WORD> isis metric [no]
Configures the metric for the MT #2 IPv6
topology.
configure interface gigabitethernet <WORD> isis ipv6 metric
<metric> [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
interface tengigabitethernet <WORD> isis lsp-interval
C4® CMTS Release 8.3 User Guide
489
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Configures the priority of the designated
routers for the specified interface. The priority
is used to determine which router on a LAN
will be the designated router. The priorities are
advertised in the hello packets. The router
with the highest priority will become the
Designated Intermediate System (DIS). In the
case of equal priorities, the highest MAC
address breaks the tie.
configure
configure
configure
configure
interface
interface
interface
interface
cable <WORD> isis priority [no]
cable-mac <WORD> isis priority [no]
gigabitethernet <WORD> isis priority [no]
tengigabitethernet <WORD> isis priority [no]
Disables [enables] the administrative state of
IS-IS on the specified interface.
Note: the loopback interface is always passive.
configure interface
configure interface
configure interface
configure interface
shutdown [no]
configure interface
shutdown [no]
cable <WORD> isis protocol shutdown [no]
cable-mac <WORD> isis protocol shutdown [no]
loopback <INT> isis protocol shutdown [no]
gigabitethernet <WORD> isis protocol
Configures the maximum rate between LSP
retransmissions for the specified interface.
This command is useful in very large networks
with many LSPs and many interfaces to control
LSP retransmission traffic. This command
controls the rate at which LSPs can be resent
on the interface.
configure interface
configure interface
[no]
configure interface
retransmit-interval
configure interface
retransmit-interval
cable <WORD> isis retransmit-interval [no]
cable-mac <WORD> isis retransmit-interval
Allows unpadded small hello packets for the
specified interface.
configure
configure
configure
configure
[no]
cable <WORD> isis small-hello [no]
cable-mac <WORD> isis small-hello [no]
gigabitethernet <WORD> isis small-hello [no]
tengigabitethernet <WORD> isis small-hello
interface
interface
interface
interface
tengigabitethernet <WORD> isis protocol
gigabitethernet <WORD> isis
[no]
tengigabitethernet <WORD> isis
[no]
Allows wide metrics for the specified interface. configure interface cable <WORD> isis wide-metric <INT> [no]
configure interface cable-mac <WORD> isis wide-metric <INT> [no]
Note: the loopback interface is always passive. configure interface loopback <INT> isis wide-metric [no]
configure interface gigabitethernet <WORD> isis wide-metric [no]
configure interface tengigabitethernet <WORD> isis wide-metric
[no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
490
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Configure filtering for outbound BGP routes on configure router bgp [<INT>] distribute-list <1-99> out isis
the specified VRF for the ISIS routing process.
Configure redistribution of routes from IS-IS
routing processes into a BGP autonomous
system.
configure router bgp [<int>] redistribute isis
Places the system into an intermediate mode. configure router isis [no]
NOTE: Use the NO command to remove all the
IS-IS configuration.
Allows user to enter CLI address family IPv4
mode.
configure router isis address-family ipv4
Enables IS-IS routing for IP on the router level
configure router isis address-family ipv4 enable [no]
Allows user to enter CLI address family IPv6
mode.
configure router isis address-family ipv6
Enables IS-IS routing for IPv6 on the router
level.
configure router isis address-family ipv6 enable [no]
Configures the router IS-IS authentication keychain.
configure router isis authentication key-chain [no]
Configures the router IS-IS authentication
mode.
configure router isis authentication mode [no]
Configures administrative distance for IS-IS
routes.
configure router isis distance [no]
Configures administrative distance for subsets
of the IS-IS routes in the same VRF.
configure router isis distance isis [no]
Configure filtering for outbound IS-IS routes in
the same VRF.
configure router isis distribute-list <num> out [no]
Configures the number of equal costs routes.
configure router isis ecmp [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
491
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Modifies the graceful-restart parameters for
IS-IS to help the peer to restart.
configure router isis graceful-restart help-peer [no]
Modifies the graceful-restart parameters for
IS-IS to wait the specified time to establish
adjacencies before completing the
start/restart. Use the second command to
negate the wait time.
configure router isis graceful-restart interface wait <INT>
configure router isis graceful-restart interface [no]
Modifies the graceful-restart parameters for
IS-IS for the maximum time before completing
the restart procedures.
configure router isis graceful-restart t3 <INT> [no]
Configures the routing level.
configure router isis is-type [no]
Configures the generation rate of the LSPs.
configure router isis lsp-gen-interval [no]
Configures the link-state-packet (LSP) refresh
interval.
configure router isis lsp-refresh-interval [no]
Configures the maximum time that link-statepackets (LSPs) can remain in a router’s
database without being refreshed.
configure router isis max-lsp-lifetime [no]
Configures the type of metric the C4/c CMTS
will generate or accept.
configure router isis metric-style <narrow | transition | wide>
Configures an IS-IS network entity title (NET).
NETs define the area addresses for the IS-IS
area and the system ID of the router.
configure router isis net [no]
Suppresses routing updates on the specified
interface.
configure router
configure router
configure router
configure router
[no]
configure router
<WORD> [no]
Note: the loopback interface is always passive.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
isis
isis
isis
isis
passive-interface
passive-interface
passive-interface
passive-interface
cable <WORD> [no]
cable-mac <WORD> [no]
loopback <INT> [no]
gigabitethernet <WORD>
isis passive-interface tengigabitethernet
C4® CMTS Release 8.3 User Guide
492
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Redistribute BGP routes into IS-IS.
configure router isis redistribute bgp [no]
Redistribute connected routes into IS-IS.
configure router isis redistribute connected [no]
Redistribute connected IPv6 routes into IS-IS.
configure router isis address-family ipv6 redistribute connected
[no]
Redistribute OSPF routes into IS-IS.
configure router isis redistribute ospf [no]
Redistribute RIP routes into IS-IS.
configure router isis redistribute rip [no]
Redistribute static routes into IS-IS.
configure router isis redistribute static [no]
Redistribute IPv6 static routes into IS-IS.
configure router isis address-family ipv6 redistribute static
[no]
Turns on [off] Multi-topology IS-IS.
configure router isis multi-topology [no]
To configure the router to signal other routers
not to use it as an intermediate hop in their
shortest path first (SPF) calculations, use the
set-overload-bit command in router
configuration mode. It will cause to originate
LSPs with the Overload bit set. This bit will be
set if the level-1 or level-2 database is running
short of a resource such as memory.
configure router isis set-overload-bit
Disables the administrative state of IS-IS.
configure router isis shutdown
Configures the IS-IS throttling of shortest path
first (SPF) calculations.
configure router isis spf-interval [no]
Change aggregate addresses for the VRF.
configure router isis summary-address [no]
Change aggregate IPv6 addresses for the VRF.
configure router isis address-family ipv6 summary-prefix [no]
Configure filtering for outbound OSPF routes
on the specified VRF for the IS-IS routing
process.
configure router ospf [vrf <name>] distribute-list <WORD> out
isis [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
493
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Configure redistribution routes from
Intermediate System-to-Intermediate System
(IS-IS) routing processes into OSPF.
configure router ospf [vrf <name>] redistribute isis [no]
Configure filtering for outbound RIP routes on
the specified VRF for the IS-IS routing process.
configure router rip [vrf <name>] distribute list <WORD> out
isis [no]
Configure redistribution routes from IS-IS
routing processes into RIP.
configure router rip [<int>] [vrf <name>] redistribute isis [no]
Display the IS-IS redistribution information.
show distribute-list
Displays the IS-IS redistribution information.
show ip isis
show ipv6 isis
Displays the IPv4 / IPv6 IS-IS route information. show ip route isis
show ipv6 route isis
Displays IS-IS link state database for the
specified VRF.
show isis database
Displays IS-IS interface status and
configuration for the specified VRF.
show isis interface
Displays IS-IS events specific to a circuit and
level for the specified VRF.
show isis interface events
Displays CLNS neighbor adjacencies for the
specified VRF.
show isis neighbor [detail]
Displays CLNS protocol information for the
specified VRF.
show isis protocol
Displays IS-IS protocol statistics for the
specified VRF.
show isis traffic
Enables tracing of IS-IS router events to the
logging history.
trace logging router isis [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
494
Chapter 16: Dynamic Routing Protocols
Open Shortest Path First Version 2
Open Shortest Path First (OSPF) is a dynamic link state routing protocol developed by the Internet Engineering Task Force
(IETF) that:
Supports Classless Inter-Domain Routing (CIDR)
Provides for routing update authentication, both simple and MD5
Uses IP multicast when sending/receiving the updates
Responds quickly to topology changes with a smaller amount of routing protocol traffic.
The OSPF specification is published as Request For Comments (RFC) 2328.
Link State Routing Protocol Description
The OSPF routing protocol maintains a link state database of all subnets available on the network. This includes details
about which routers are attached to the links.
If a link goes down, the router that is directly attached to it immediately sends a Link State Advertisement (LSA) to its
neighbor routers. Information about the link state propagates throughout the network. Each router reviews its database
and re-calculates the routing table independently.
Routing Metrics
A router learns multiple paths to a particular destination network, and chooses the path with the best metric in its routing
table.
Types of Metrics
Different routing protocols use different types of metrics:
Link States — Rather than counting the number of hops as a metric, OSPF bases its path descriptions on link states that
take into account additional network information.
Cost Metrics — OSPF also lets the user assign cost metrics to each interface so that some paths are given preference.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
495
Chapter 16: Dynamic Routing Protocols
User-Defined Cost — OSPF uses a user-defined cost for each interface. This cost is added together for each hop when
calculating the cost of a route. This metric could be the same as number of hops if each interface along the route uses
a cost of 1.
Equal Cost MultiPath Routes
OSPF also has the concept of Equal Cost MultiPath (ECMP) routes. These are routes to the same DIP (destination IP
address) and prefix which use different next hop IPs but the same cost.
The C4/c CMTS can distribute packets across at most four ECMP routes. ECMP routes can also be used with static routes.
The C4/c CMTS bases its choice of best route on the following order of criteria:
1. Longest prefix
2. Route type (local, netmgmt, OSPF, RIP)
3. Route cost
Configuring OSPF
This section outlines the tasks required to configure a network and C4/c CMTS for OSPF. The procedures and commands in
this section assume that IP addresses have already been configured for the network and OSPF interfaces. The sequence
includes:
1. Reviewing a network diagram for interface information and architecture.
2. Enabling OSPF globally.
3. Configuring the network according to standard configuration parameters: set router id, hello timer, dead timer,
network type (broadcast, point-to-point, virtual link), and authentication.
4. Verifying OSPF is running as configured.
It is beyond the scope of this document to supply recommendations for reviewing network architecture for all OSPF
configuration possibilities; however, the following sections identify the CLI commands required for basic OSPF
configuration on the C4/c CMTS.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
496
Chapter 16: Dynamic Routing Protocols
Enable OSPF
The following procedure is used to enable OSPF on the C4/c CMTS.
To enable OSPF:
1. Enter the following command to give the default router an identification number:
configure router ospf vrf default router-id 1.1.1.1
Where:
1.1.1.1 is the router ID
2. By default, OSPF is disabled for all interfaces. Enabling OSPF for an interface does not affect the global enable/disable
state on the C4/c CMTS. Enter the following command to enable OSPF for an interface:
configure router ospf [vrf <VRF>] network <ip-address> <inverse mask> area <area-id>
Network address and area-id can be specified as either a decimal value or as an IP address. The inverse mask is also
called the wildcard mask.
3. Enter the following command to advertise routes for the locally connected interfaces (i.e. CAMs) and to redistribute
the default ospf route based on metric-types, tags, and subnets:
configure router ospf [vrf <VRF>] redistribute connected [metric {<0-16777215> | transparent}]
[metric-type <1 | 2>] [tag <1-4294967295>]
Where:
metric (optional) is the metric used for redistributed route. Values 1-4294967295. Default is 1.
metric-type (optional) is the external link type associated with the default route advertised into the OSPF
routing domain. Values are 1 (internal route) or 2 (external route). Default is 2.
tag (optional) is the 32 bit decimal value that OSPF attaches to the external route. Default is 0.
4. By default, OSPF is disabled on the C4/c CMTS. Enter the following command to enable OSPF:
configure router ospf vrf default no shutdown
There is no system response if the command is successful. This is a "silent success" command.
5. Validate OSPF status:
show ip ospf
The output should indicate as follows:
Router VRF default with ID 1.1.1.1
Only cost is used when choosing among multiple AS-external-LSAs
Exit overflow interval 0 seconds
Number of external LSA 0. Checksum 0x0
Number of new originated LSAs 2
Number of received LSAs 5
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
497
Chapter 16: Dynamic Routing Protocols
6. Confirm that OSPF is enabled for the interface:
show ip ospf interface
Sample output:
gigabitethernet 17/0 Router Virtual Interface of Virtual Router: default
Internet Address is 192.168.176.2 / 255.255.255.0
Internet Secondary Address(es):
No Secondary Addresses
Area ID: 0.0.0.0
Network type:
Point-to-point
Cost:
1
Transmit delay:
1
Admin state:
Enabled
Interface state:
Point-to-point
Priority:
1
Designated router: 0.0.0.0
Backup designated
router:
0.0.0.0
Not a graceful-restart helper
Timer intervals (in seconds):
Hello:
1
Retransmit:
5
Dead:
4
Poll:
120
Counts:
Events: 1
LSAs:
0
Authentication Type: None
gigabitethernet 17/1 Router Virtual Interface of Virtual Router: default
Internet Address is 192.168.177.2 / 255.255.255.0
Internet Secondary Address(es):
No Secondary Addresses
Area ID: 0.0.0.0
Network type:
Point-to-point
Cost:
1
Transmit delay:
1
Admin state:
Enabled
Interface state:
Point-to-point
Priority:
1
Designated router: 0.0.0.0
Backup designated
router:
0.0.0.0
Not a graceful-restart helper
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Timer intervals (in seconds):
Hello:
1
Retransmit:
5
Dead:
4
Poll:
120
Counts:
Events: 1
LSAs:
0
Authentication Type: None
C4® CMTS Release 8.3 User Guide
498
Chapter 16: Dynamic Routing Protocols
Disable OSPF for an Interface
Caution: Care should be exercised when using the following command, because the OSPF network command can be used
to enable OSPF on one, some, or all network interfaces. Most instances of OSPF in the field will have a network command
for each interface, but some sites will use network commands for multiple interfaces to save time and reduce commands.
Be sure that your "ospf no network" command matches the mask and area of the network interface(s) on which you wish
to disable OSPF.
To disable OSPF for an interface:
1. Enter the following command to disable OSPF for an interface or interfaces:
configure router ospf no network <ip-address> <wildcard-mask> area <area-id>
Where:
ip-address is the IP prefix of the desired network interface.
wildcard-mask is the IP address type mask that includes "don’t care bits".
area-id is the area that is to be associated with the OSPF address range.
2. Confirm that OSPF is disabled for the network:
show ip ospf interface
Disable OSPF on the C4/c CMTS
The following procedure is used to disable OSPF.
To disable OSPF on the C4/c CMTS:
1. Enter the following commands to disable OSPF:
configure router ospf [vrf <VRF>] shutdown
2. Validate OSPF status:
show ip ospf
The output should include the following line:
Router VRF default with ID 1.1.1.1 (disabled)
3. Validate vrf status:
show ip vrf
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
499
Chapter 16: Dynamic Routing Protocols
Sample output:
Virtual Router Details:
Name
Index
===============
==========
default
1
vrf_a
2
OSPF
====
no
no
RIP
===
no
no
ISIS
====
no
--
BGP
===
no
--
ICMP-TIME-EXCEEDED
==================
no
no
CLI Commands for OSPF
The following list is meant as summary of the OSPF-related commands. They do not have to be performed in the order
listed and not all commands will pertain to your plant and application.
For more information on these CLI commands see the Command Line Descriptions.
Table 67. List of Commands Related to OSPF
Purpose
Command
Defines an OSPF area as a stub area. External
routes can not be imported into these areas.
configure router ospf [vrf default] area <area-id> stub [no]
configure router ospf [vrf default] area <area-id> nssa [no]
Configures an area as a not so stubby area
(NSSA). This area allows for generation of type-7
LSAs.
Sets up a virtual link between two routers.
configure router ospf [vrf default] area <area-id) virtuallink <router-id> [no]
Suppresses routing updates on the specified
interface.
configure router ospf [vrf default] passive-interface cablemac <mac> [no]
configure router ospf [vrf default] passive-interface
gigabitethernet <slot>/<port> [no]
configure router ospf [vrf default] passive-interface
tengigabitethernet <slot>/<port> [no]
Configures the time between an OSPF event and configure router ospf [vrf default] timer delay-spf <seconds>
[no]
the SPF calculation. Valid range is 0-255
seconds. Default = 5.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
500
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Assigns a password to be used by neighboring
routers that are using the OSPF simile password
authentication.
configure interface cable-mac <mac> ip ospf authentication-key
<password> [no]
configure interface gigabitethernet <slot>/<port> ip ospf
authentication-key <password> [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
authentication-key <password> [no]
Specifies the set of keys that can be used on the configure interface cable-mac <mac> ip ospf authentication
key-chain <name> [no]
specified interface.
configure interface gigabitethernet <slot>/<port> ip ospf
authentication key-chain <name> [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
authentication key-chain <name> [no]
Configures the OSPF md5 key chain.
configure interface cable-mac <mac> ip ospf message-digest-key
<INT> md5 [<WORD>] [no]
configure interface gigabitethernet <WORD> ip ospf messagedigest-key <INT> md5 [<WORD>] [no]
configure interface tengigabitethernet <WORD> ip ospf messagedigest-key <INT> md5 [<WORD>] [no]
Specifies the interval between hello packets
that the software sends on the interface.The
valid range in seconds = 1-65535 and the
default is set at 10 seconds.
configure interface cable-mac <mac> ip ospf hello-interval
<interval> [no]
configure interface gigabitethernet <slot>/<port> ip ospf
hello-interval <interval> [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
hello-interval <interval> [no]
Sets the interval at which hello packets must
not be seen before neighbors declare the router
down. The dead interval must be greater than
the hello interval. It is recommended that the
dead interval be set to a value greater than two
times the hello interval.
configure interface cable-mac <mac> ip ospf dead-interval
<interval> [no]
configure interface gigabitethernet <slot>/<port> ip ospf
dead-interval <interval> [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
dead-interval <interval> [no]
Automatically deletes the neighbors when
adjacency is lost.
configure interface cable-mac <mac> ip ospf auto-deleteneighbor [no]
configure interface gigabitethernet <slot>/<port> ip ospf
auto-delete-neighbor [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
auto-delete-neighbor [no]
Specifies the cost of sending a packet on the
interface.
configure interface cable-mac <mac> ip ospf cost <metric> [no]
configure interface gigabitethernet <slot>/<port> ip ospf cost
<metric> [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
501
Chapter 16: Dynamic Routing Protocols
Purpose
Command
configure interface tengigabitethernet <slot>/<port> ip ospf
cost <metric> [no]
Configures the OSPF network type to either a
broadcast or point-to-point network.
Note: You must shutdown OSPF before
changing network types.
configure interface cable-mac <mac> ip ospf network <type>
[no]
configure interface gigabitethernet <slot>/<port> ip ospf
network <type> [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
network <type> [no]
Sets the router priority.
configure interface
<priority> [no]
configure interface
priority <priority>
configure interface
priority <priority>
cable-mac <mac> ip ospf priority
Specifies the time between link-state
advertisement (LSA) retransmissions for
adjacencies belonging to the interface.
configure interface
interval <interval>
configure interface
retransmit interval
configure interface
retransmit interval
cable-mac <mac> ip ospf retransmit
[no]
gigabitethernet <slot>/<port> ip ospf
<interval> [no]
tengigabitethernet <slot>/<port> ip ospf
<interval> [no]
Sets the estimated time it takes to transmit a
link state update.
configure interface cable-mac <mac> ip ospf transmit-delay
<delay time> [no]
configure interface gigabitethernet <slot>/<port> ip ospf
transmit-delay <delay time> [no]
configure interface tengigabitethernet <slot>/<port> ip ospf
transmit-delay <delay time> [no]
Displays the OSPF interface information.
show ip ospf interface
gigabitethernet <slot>/<port> ip ospf
[no]
tengigabitethernet <slot>/<port> ip ospf
[no]
Open Shortest Path First Version 3
Open Shortest Path First version 3 (OSPFv3) is an IETF link-state protocol specifically for IPv6 routers.
Note: OSPFv3 is described in RFC 5340.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
502
Chapter 16: Dynamic Routing Protocols
Comparison of OSPFv3 and OSPFv2
Much of the OSPFv3 protocol is the same as in OSPFv2. The key differences between the OSPFv3 and OSPFv2 protocols are
as follows:
OSPFv3 only provides support for IPv6 routing prefixes and will handle the larger size IPv6 addresses. OSPFv2 only
supports IPv4 routing.
LSAs in OSPFv3 are expressed as prefix and prefix length. OSPFv2 uses address and mask.
The router ID and area ID are 32-bit numbers, which is the same as in OSPFv2, with no relationship to IPv6 addresses.
OSPFv3 uses link-local IPv6 addresses for neighbor discovery and other features.
OSPFv3 uses IPSec for authentication and OSPFv2 uses MD5.
OSPFv3 redefines LSA types.
The C4/c CMTS supports running both OSPFv2 and OSPFv3 at the same time, including running the protocols on the same
interface. It will also support passive interfaces on the:
Cable side.
Network side.
Loopback interfaces.
OSPFv3 on the C4/c CMTS supports point-to-point links, but does not support point to multipoint links.
Discovering Neighboring Routers
An OSPFv3 router sends a special message, called a Hello packet, out each OSPF-enabled interface to discover other
OSPFv3 neighbor routers. Once a neighbor is discovered, the two routers compare information in the Hello packet to
determine if the routers have compatible configurations.
Establishing Adjacency
The neighboring routers attempt to establish adjacency, which means that the routers synchronize their Link-State
Databases (LSDBs) to ensure that they have identical OSPFv3 routing information.
Link-State Advertisements
Adjacent routers share Link-State Advertisements (LSAs) that include information about:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
503
Chapter 16: Dynamic Routing Protocols
The operational state of each link.
The cost of the link.
Any other neighbor information.
The routers then flood these received LSAs out every OSPF-enabled interface so that all OSPFv3 routers eventually have
identical LSDBs.
When all OSPFv3 routers have identical LSDBs, the network is converged. Each router then uses Dijkstra's Shortest Path
First (SPF) algorithm to build its route table.
Note: OSPFv3 networks can be divided into separate areas which helps reduce the CPU and memory requirements for an
OSPF-enabled router because routers send most LSAs only within one area.
Hello Packets
OSPFv3 routers periodically send Hello packets on every OSPF-enabled interface. The Hello interval determines how
frequently the router sends these Hello packets, and is configured per interface.
Determining Compatibility
An OSPFv3 interface that receives Hello packets determines if the settings are compatible with the receiving interface
settings. Compatible interfaces are considered neighbors, and are added to the neighbor table.
Tasks
OSPFv3 uses Hello packets for the following tasks:
Neighbor discovery
"Keepalive" messages
Bidirectional communications
Designated router election.
Packet Contents
The Hello packet contains information about the:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
504
Chapter 16: Dynamic Routing Protocols
Originating OSPFv3 interface and router.
Instance ID and interface ID.
Hello interval.
Optional capabilities of the originating router.
Hello packets also include a list of router IDs for the routers that the originating interface has communicated with. If the
receiving interface sees its own router ID in this list, then bidirectional communication has been established between the
two interfaces.
Keepalive Message
OSPFv3 uses Hello packets as a "keepalive" message to determine if a neighbor is still communicating. If a router does not
receive a Hello packet by the configured dead interval (usually a multiple of the Hello interval), then the neighbor is
removed from the local neighbor table.
Fast Hello Packets for OSPFv2 and v3
Both OSPV2 and OSPFv3 support Fast Hello Pa ckets in the C4/ c CMTS implementation. Operators can configure the sendi ng of Hello pa ckets in intervals of less tha n one second. S uch a configuration will result in faster converge nce in a n OSPF netw ork.
Interval Settings
Setting the dead interval to one second will turn on the Fast Hello feature with the default value of 5 for the Hello
multiplier (200 ms Hello interval). The Hello multiplier is not configurable for OSPFv3.
Equal Cost Multipath
Routing protocols can use equal cost multipath (ECMP) to share traffic across multiple paths. When a router learns
multiple routes to a specific network, it installs the route with the lowest administrative distance in the routing table.
If the router receives and installs multiple paths with the same administrative distance and cost to a destination, ECMP can
occur.
Path Number Limit
The number of paths used is limited by the number of entries that the routing protocol puts in the routing table. The C4/c
CMTS supports up to a maximum of four equal cost routes.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
505
Chapter 16: Dynamic Routing Protocols
Best Choice Route
The C4/c CMTS bases its choice of best route based on the following order of criteria:
1. Longest prefix
2. Administrative Distance based on route type (for example, connected, static, ISIS, BGP)
3. Route cost.
Neighbors
An OSPFv3 interface must have a compatible configuration with a remote interface before the two can be considered
neighbors.
Compatibility Match
The two OSPFv3 interfaces must match the following criteria:
Hello interval
Dead interval
Area ID
Authentication
Instance ID
Optional capabilities
If there is a match, the following information is entered into the neighbor table:
Neighbor ID — The router ID of the neighbor router.
Priority — Priority of the neighbor router. The priority is used for designated router.
State — Indication of whether the neighbor has just been heard from, is in the process of setting up bidirectional
communications, is sharing the link-state information, or has achieved full adjacency.
Dead Time — Indication of how long since the last Hello packet was received from this neighbor.
Link-local IPv6 Address — The link-local IPv6 address of the neighbor.
Designated Router — Indication of whether the neighbor has been declared the designated router or backup
designated router.
Local Interface — The local interface that received the Hello packet for this neighbor.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
506
Chapter 16: Dynamic Routing Protocols
State Sequence
For a better understanding of this section, see RFC 2178 (http://www.rfc-base.org/txt/rfc-2178.txt), Section 10.1, Neighbor
States, and Section 10.3, the Neighbor state machine, in order to understand state changes. When the first Hello packet is
received from a new neighbor:
1. The neighbor is entered into the neighbor table in the init state.
2. When bidirectional communication is established, the neighbor state becomes two-way as the two interfaces exchange
their link-state databases.
3. Finally, the neighbor moves into the full state, signifying full adjacency.
If the C4/c CMTS fails to receive any Hello packets from a neighbor for the length of the dead-interval, that adjacency is
broken and considered down.
Adjacency
Not all neighbors establish adjacency. Depending on the network type and designated router establishment, some
neighbors become fully adjacent and share LSAs with all their neighbors, while other neighbors do not.
Adjacency is established using:
Database Description Packets — The Database Description packet includes just the LSA headers from the link-state
database of the neighbor. The local router compares these headers with its own link-state database and determines
which LSAs are new or updated.
Link State Request Packets — The local router sends a Link State Request packet for each LSA for which it needs new
or updated information.
Link State Update Packets — The neighbor responds with a Link State Update packet. This exchange continues until
both routers have the same link-state information.
Router Types
Networks with multiple routers present a unique situation for OSPFv3. If every router floods the network with LSAs, the
same link-state information will be sent from multiple sources.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
507
Chapter 16: Dynamic Routing Protocols
Designated Router
Depending on the type of network, OSPFv3 might use a single router, the Designated Router (DR), to control the LSA floods
and represent the network to the rest of the OSPFv3 area.
DRs are based on a router interface. A router might be the DR for one network and not for another network on a different
interface.
Backup Designated Router
If the DR fails, OSPFv3 will promote the Backup Designated Router (BDR) to DR.
Network Types
Network types are as follows:
Point-to-point — A network that exists only between two routers. All neighbors on a point-to-point network establish
adjacency and there is no DR.
Broadcast — A network with multiple routers that can communicate over a shared medium that allows broadcast
traffic such as Ethernet. OSPFv3 routers establish a DR and BDR that controls LSA flooding on the network. OSPFv3 uses
the well-known IPv6 multicast addresses, FF02::5, and a MAC address of 33:33:00:00:00:05 to communicate with
neighbors.
Router Selection
The DR and BDR are selected based on the information in the Hello packet. When an interface sends a Hello packet, it sets
the priority field and the DR and BDR field if, it can identify the DR and BDR.
To accomplish this, the routers follow an election procedure based on which the routers declare themselves in the
following:
The DR and BDR fields
The priority field of the Hello packet.
As a final alternative, OSPFv3 chooses the highest router IDs as the DR and BDR.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
508
Chapter 16: Dynamic Routing Protocols
All other routers establish adjacency with the DR and the BDR and use the IPv6 multicast address FF02::6 and MAC address
33:33:00:00:00:06 to send LSA updates to the DR and BDR.
Designated Router Configuration
It is recommended that the following command is issued on each interface with an OSPFv3 broadcast network type. By
setting the priority to 0, as shown in the example, the C4/c CMTS will not participate in DR elections:
configure interface gigabitethernet <slot>/<port> ipv6 ospf priority 0
Note: ARRIS recommends that the C4/c CMTS not be configured as a designated router by means of this command.
Areas
An area is a logical division of routers and links within an OSPFv3 domain that creates separate subdomains. By dividing an
OSPFv3 network into areas and limiting the numbers of LSAs per area, the CPU and memory requirements can be reduced.
LSA Flooding
LSA flooding is contained within an area, and the link-state database is limited to links within the area.
Area ID
You can assign an area ID to the interfaces within the defined area. The area ID is a 32-bit value that can be expressed as a
number or in a dotted decimal notation, such as 10.2.3.1.
Backbone Area
If you define more than one area in an OSPFv3 network, you must also define the backbone area, which has the reserved
area ID of 0. The backbone area sends summarized information about one area to another area.
Area Border Routers
If you have more than one area, then one or more routers become Area Border Routers (ABRs). An ABR connects to both
the backbone area and at least one other defined area.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
509
Chapter 16: Dynamic Routing Protocols
The ABR has a separate link-state database for each area to which it connects. The ABR sends Inter-Area Prefix (type 3)
LSAs from one connected area to the backbone area.
Autonomous System Boundary Router
OSPFv3 defines one other router type: the Autonomous System Boundary Router (ASBR). This router connects an OSPFv3
area to another Autonomous System (AS).
An AS is a network controlled by a single technical administration entity. OSPFv3 can redistribute its routing information
into another AS or receive redistributed routes from another AS.
Link-State Advertisement
OSPFv3 uses link-state advertisements (LSAs) to build its routing table.
LSA Types
The following tables contains the various LSA Types.
Table 68. LSA Types
Name
Description
Router LSA
LSA sent by every router. This LSA includes state and cost of all links. Does not include prefix information.
Router LSAa trigger an SPF recalculation. Router LSAs are flooded to the local OSPFv3 area.
Network LSA
LSA sent by the DR. Lists all routers in the multi-access network. This LSA does not include prefix
information. Network LSAs trigger an SPF recalculation.
Inter-Area Prefix
LSA
LSA sent by the area border router to an external area for each destination in local area. This LSA includes
the link cost from area the border router to the local destination.
Inter-Area Router
LSA
LSA sent by the area border router to an external area. This LSA advertises the link cost to the ASBR only.
AS External LSA
LSA generated by the ASBR. This LSA includes the link cost to an external autonomous system destination.
AS External LSAs are flooded throughout the autonomous system.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
510
Chapter 16: Dynamic Routing Protocols
Name
Description
Type-7 LSA
LSA generated by the ASBR within an NSSA. This LSA includes the link cost to an external autonomous
system destination. Type-7 LSAs are flooded only within the local NSSA.
Link LSA
LSA sent by every router, using a link-local flooding. This LSA includes the link-local address and IPv6
prefixes for this link.
Intra-Area Prefix
LSA
LSA sent by every router. This LSA includes any prefix or link state changes within an area. Intra-Area
Prefix LSAs are flooded to the local OSPFv3 area. This LSA does not trigger an SPF recalculation.
Link Cost
Each OSPFv3 interface is assigned a link cost. The link cost is:
An arbitrary number. By default, the C4/c CMTS assigns a cost of one to each interface.
Configurable by the user.
Carried in the LSA updates for each link.
Displaying Cost of Route
The cost of the route is the sum of the interface costs which can be displayed by the following command:
show ipv6 route
Flooding
OSPFv3 floods LSA updates to different sections of the network depending on the LSA type. OSPFv3 uses the following
flooding scopes:
Link-local — LSA is flooded only on the local link, and no further. Used for Link LSAs and Grace LSAs.
Area-local — LSA is flooded throughout a single OSPF area only. Used for Router LSAs, Network LSAs, Inter-Area-Prefix
LSAs, Inter-Area-Router LSAs, and Intra-Area-Prefix LSAs.
AS scope — LSA is flooded throughout the routing domain. Used for AS External LSAs.
LSA flooding guarantees that all routers in the network have identical routing information. LSA flooding depends on the
OSPFv3 area configuration. The LSAs are flooded based on the link-state refresh time (every 30 minutes by default). Each
LSA has its own link-state refresh time.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
511
Chapter 16: Dynamic Routing Protocols
Link-State Database
Each router maintains a link-state database for the OSPFv3 network. This database contains all the collected LSAs, and
includes information on all the routes through the network. OSPFv3 uses this information to calculate the best path to
each destination and populates the routing table with these best paths.
LSAs are removed from the link-state database if no LSA update has been received within a set interval, called the MaxAge.
Routers flood a repeat of the LSA every 30 minutes to prevent accurate link-state information from being aged out.
VRF Requirements
OSPFv3 only runs in the default VRF on the C4/c CMTS.
Stub Area
The amount of external routing information that floods an area can be limited by making it a stub area. A stub area is an
area that does not allow AS External (type 5) LSAs. These LSAs are usually flooded throughout the local AS to propagate
external route information.
Not-So-Stubby Area
A Not-So-Stubby Area (NSSA) is similar to the stub area, except that an NSSA allows you to import autonomous system
external routes within an NSSA using redistribution.
Note: The backbone Area 0 cannot be an NSSA.
Route Summarization
Because OSPFv3 shares all learned routes with every OSPFv3-enabled router, route summarization can be used to reduce
the number of unique routes that are flooded to every OSPFv3-enabled router.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
512
Chapter 16: Dynamic Routing Protocols
Simplified Routing Tables
Route summarization simplifies routing tables by replacing more-specific addresses with an address that represents all the
specific addresses. For example, you can replace 2010:11:22:0:1000::1 and 2010:11:22:0:2000:679:1 with one summary
address, 2010:11:22::/32.
Guidelines
Typically, you would summarize at the boundaries of Area Border Routers (ABRs). Although, it is acceptable to configure
summarization between any two areas, it is better to summarize in the direction of the backbone so that the backbone
receives all the aggregate addresses and injects them, already summarized, into other areas.
Inter-Area Route Summarization
Inter-area route summarization summarizes routes on ABRs between areas in the autonomous system. To take advantage
of summarization, network numbers should be assigned in areas in a contiguous way to be able to lump these addresses
into one range.
External Route Summarization
External route summarization is specific to external routes that are injected into OSPFv3 using route redistribution. Ensure
that external ranges that are being summarized are contiguous.
Note: Summarizing overlapping ranges from two different routers could cause packets to be sent to the wrong destination.
Safeguard
When a summary address is configured, the C4/c CMTS automatically configures a discard route for the summary address
to prevent routing black holes and route loops.
Configuring OSPFv3 for IPv6
OSPFv3 for IPv6 is enabled by specifying an OSPFv3 router ID and an area at the interface configuration level. The
configuration process includes:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
513
Chapter 16: Dynamic Routing Protocols
Configure the OSPFv3 router-id.
Enabling OSPFv3 globally.
Configuring the network according to standard configuration parameters: set router id, hello timer, dead timer, and
network type (broadcast, point-to-point, virtual link).
Verifying OSPFv3 is running as configured.
Note: It is beyond the scope of this User Guide to supply recommendations for reviewing network architecture for all
OSPFv3 configuration possibilities.
Passive Interface Configuration
Cable-side interfaces are advertised in OSPFv3 by configuring these interfaces as passive interfaces in order to suppress the
unnecessary hellos that would be sent on the downstream. This could also reduce the number of LSAs needed to advertise
all the cable-side interface addressees.
Configure OSPFv3 with Cable-side Interfaces as Passive Interfaces
OSPFv3 requires the user to define the router ID and will not allow OSPFv3 to come into service until then.
To enable OSPFv3 as a passive interface on the C4/c CMTS:
1. Enter the following command to configure the router ID:
configure ipv6 router ospf router-id 1.1.1.1
Where:
1.1.1.1 is the unique router id
Note: If the router-id is not provisioned, OSPFv3 will not be allowed to come into service.
2. Enter the following command to enable OSPFv3 for an specified interface:
configure interface {cable-mac <mac> | loopback <0-15> | gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>} ipv6 ospf area <word>
Where:
cable-mac <mac>
is the MAC identifier
loopback <0-63>
is the loopback interface number
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
514
Chapter 16: Dynamic Routing Protocols
gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>
is the RCM slot number/port number of the specified
interface
area <word>
is the area ID. It can be specified as either an IP address or
decimal value
3. Whenever a user enables a cable-side interface, the user should also configure the interface as a passive interface:
configure ipv6 router ospf passive-interface {cable-mac <mac> | loopback <0-15> | gigabitethernet
<slot>/<port> | tengigabitethernet <slot>/<port>}
Note: The cable-mac and loopback interfaces are generally configured as passive interfaces to suppress hello packets
that would otherwise be sent on the downstream.
4. By default, OSPFv3 is disabled on the C4/c CMTS. Enabling OSPFv3 for an interface does not affect the global
enable/disable state on the C4/c CMTS. Enter the following command to enable OSPFv3:
configure ipv6 router ospf no shutdown
There is no system response if the command is successful. This is a "silent success" command.
Note: To again disable OSPFv3 the same command form is entered as follows:
configure ipv6 router ospf shutdown
5. Confirm that OSPFv3 is enabled for the interface:
show ipv6 ospf interface
Sample output:
gigabitethernet 17/0.0
Link-local address
Global unicast address(es)
Area ID: 0.0.0.0
Network type:
Cost:
Transit delay:
Admin state:
Interface state:
Priority:
Designated router:
Backup designated
router:
Broadcast
1
1
Enabled
UP
1
0.0.0.0
: FE80::201:5CFF:FE22:9420/10
: 2001::201:5CFF:FE22:9420
Timer intervals (in seconds):
Hello:
10
Retransmit:
5
Dead:
40
Poll:
120
Counts:
Events: 0
LSAs: 0
0.0.0.0
6. Enter the following command to disable OSPFv3 for an specific interface or interfaces:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
515
Chapter 16: Dynamic Routing Protocols
configure interface {cable-mac <mac> | loopback <0-15> | gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>} ipv6 ospf no
Where:
cable-mac <mac>
is the MAC identifier
loopback <0-63>
is the loopback interface number
gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>
is the RCM slot number/port number of the specified
interface
7. Confirm that OSPFv3 is disabled for the interface:
show ipv6 ospf interface
Summary of CLI Commands for OSPFv3
Below is a table listing many of the CLI commands that you will use in configuring and using OSPFv3.
For more information on these CLI commands see Command Line Descriptions.
Table 69. List of Commands Related to OSPFv3
Purpose
Command
Global commands:
To enable [disable] OSPFv3.
configure ipv6 router ospf [vrf <VRF>] shutdown [no]
Configures router ID.
configure ipv6 router ospf [vrf <VRF>] router-id
<a.b.c.d> [no]
Defines this router as an autonomous border router.
configure ipv6 router ospf [vrf <VRF>] as-border-router
[no]
configure ipv6 router ospf [vrf <VRF>] distance <int>
Configures the administrative distance for OSPFv3 routes. [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
516
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Configures the administrative distance for external
OSPFv3 routes.
configure ipv6 router ospf [vrf <VRF>] distance <int>
ospf external <int>
Suppresses sending OSPFv3 packets on the specified
interface.
configure ipv6 router ospf [vrf <VRF>] passiveinterface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
[no]
Area Commands:
To configure an OSPFv3 area
configure ipv6 router ospf [vrf <VRF>] area <word> [no]
To configure the default cost for an area.
configure ipv6 router ospf [vrf <VRF>] area defaultcost [no]
To configure an area as a not-so-stubby area (NSSA)
configure ipv6 router ospf [vrf <VRF>] area <word> nssa
[no-summary] [no]
configure ipv6 router ospf [vrf <VRF>] area <word>
Consolidates and summarizes routes at an area boundary. range <word> [no]
Sets the address range status to advertise and generates a configure ipv6 router ospf [vrf <VRF>] area <word>
range <word> advertise [no]
Type 3 summary LSA.
Sets the address range status to DoNotAdvertise. Type 3
summary LSAs are suppressed.
configure ipv6 router ospf [vrf <VRF>] area <word>
range <word> not-advertise [no]
Defines an area as a stub area.
configure ipv6 router ospf [vrf <VRF>] area <word> stub
[no-summary] [no]
Interface Commands:
Configures an OSPFv3 area on the specified interface.
configure interface {cable <word> | cable-mac <word> |
loopback <int> | gigabitethernet <word> |
tengigabitethernet <word>} ipv6 ospf area <word>
[instance <int>] [no]
Configures the cost of sending a packet on the specified
interface for the OSPFv3 router process.
configure interface {cable <word> | cable-mac <word> |
loopback <int> | gigabitethernet <word> |
tengigabitethernet <word>} ipv6 ospf cost [<int>] [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
517
Chapter 16: Dynamic Routing Protocols
Purpose
Configures the interval after which a neighbor is declared
dead when no hello packets are seen on the specified
interface.
Command
configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
ipv6 ospf dead-interval [<int>] [no]
Configures the interval between hello packets sent on the configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
specified interface.
ipv6 ospf hello-interval [<int>] [no]
Configures whether the OSPFv3 router process checks if
neighbors are using the same maximum transmission unit configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
(MTU) on the specified interface when exchanging data
ipv6 ospf mtu-ignore [no]
base descriptor (DBD) packets.
Configures the OSPF network type to a type other than
the default for a given media. Current supported type is
broadcast or point-to-point.
configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
ipv6 ospf network <list> [no]
Configures the router priority on the specified OSPFv3
interface.
configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
ipv6 ospf priority <int> [no]
Configures the time between link-state advertisement
(LSA) retransmissions for adjacencies belonging to the
specified OSPFv3 interface.
configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
ipv6 ospf retransmit-interval <int> [no]
Configures the estimated time required to send a linkstate update packet on the specified OSPFv3 interface.
configure interface {cable <word> | cable-mac <word> |
gigabitethernet <word> | tengigabitethernet <word>}
ipv6 ospf transmit-interval <int> [no]
Show Commands:
Displays the route redistributions.
show ipv6 ospf <word>
Displays the OSPF area information.
show ipv6 ospf area
Displays the OSPF database information.
show ipv6 ospf database
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
518
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Displays the OSPF database information filtered by the
Advertising Router [as an IP address].
show ipv6 ospf database adv-router <a.b.c.d>
Displays the OSPF database external link states by link
state ID or IPv6 prefix.
show ipv6 ospf database external {<0-4292967295> |
<X:X:X:X::X/<0-128>}
Displays the OSPF database external link states filtered by show ipv6 ospf database external {<0-4292967295> |
<X:X:X:X::X/<0-128>} adv-router <a.b.c.d>
the Advertising Router (as an IP address).
Displays the OSPF database inter-area prefix link states by show ipv6 ospf database inter-area prefix {<04292967295> | <X:X:X:X::X/<0-128>}
link state ID or IPv6 prefix.
Displays the OSPF database inter-area prefix link states
filtered by the Advertising Router (as an IP address).
show ipv6 ospf database inter-area prefix {<04292967295> | <X:X:X:X::X/<0-128>} adv-router <a.b.c.d>
Displays the OSPF database inter-area router link states
by link state ID.
show ipv6 ospf database inter-area router {<04292967295> | <X:X:X:X::X/<0-128>}
Displays the OSPF database inter-area router link states
filtered by the Advertising Router (as an IP address).
show ipv6 ospf database inter-area router {<04292967295> | <X:X:X:X::X/<0-128>} adv-router <a.b.c.d>
Displays the OSPF database link by link state ID.
show ipv6 ospf database link [<0-4292967295>]
Displays the OSPF database link filtered by the Advertising show ipv6 ospf database link [<0-4292967295>] advrouter <a.b.c.d>
Router (as an IP address).
Displays the OSPF network link by link state ID.
show ipv6 ospf database network [<0-4292967295>]
Displays the OSPF network link filtered by the Advertising
Router (as an IP address).
show ipv6 ospf database network [<0-4292967295>] advrouter <a.b.c.d>
Displays the OSPF database nssa-external link states by
link state ID or IPv6 prefix.
show ipv6 ospf database nssa-external {<0-4292967295> |
<X:X:X:X::X/<0-128>}
Displays the OSPF database nssa-external link states
filtered by the Advertising Router (as an IP address).
show ipv6 ospf database nssa-external {<0-4292967295> |
<X:X:X:X::X/<0-128>} adv-router <a.b.c.d>
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
519
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Displays the OSPF database prefix link by link state ID.
show ipv6 ospf database prefix [<0-4292967295>]
Displays the OSPF database prefix link filtered by the
Advertising Router (as an IP address).
show ipv6 ospf database prefix [<0-4292967295>] advrouter <a.b.c.d>
Displays the OSPF database router link by link state ID.
show ipv6 ospf database router [<0-4292967295>]
Displays the OSPF database router link filtered by the
Advertising Router (as an IP address).
show ipv6 ospf database router [<0-4292967295>] advrouter <a.b.c.d>
Displays a summary of OSPF database.
show ipv6 ospf database summary
Displays the OSPF interface information.
show ipv6 ospf interface [brief]
Displays only the specified cable OSPF interface
information.
show ipv6 ospf interface [brief] cable [<word>]
Displays only the specified cable-mac OSPF interface
information.
show ipv6 ospf interface [brief] cable-mac [<word>]
Displays only the specified loopback OSPF interface
information.
show ipv6 ospf interface [brief] loopback [<int>]
Displays only the specified ethernet OSPF interface
information.
show ipv6 ospf interface [brief] gigabitethernet
<word> | tengigabitethernet <word>
Displays the OSPF neighbor information by either the
neighbor ID or detail of all neighbors.
show ipv6 ospf neighbor [<a.b.c.d>] [detail]
Displays the OSPF neighbor information via the specified
ethernet interface.
show ipv6 ospf neighbor [detail] gigabitethernet
<word> | tengigabitethernet <word>
Displays the OSPF route table entries.
show ipv6 route ospf [vrf <vrf-name>] [includeinactive] [detail] ospf
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
520
Chapter 16: Dynamic Routing Protocols
Purpose
Command
Logging
Enables/disables detailed logging.
This command creates extensive protocol message
logging.
trace logging router ospfv3 [no]
Routing Information Protocol
Routing Information Protocol (RIP) is a distance vector routing protocol. Because it learns routes dynamically without
provisioning, RIP requires little overhead and is easy to implement. It remains a popular routing protocol, especially for
small networks.
Note: The C4/c CMTS does not support RIP version 1 (RIPv1). If the C4/c CMTS is connected to a router that supports only
RIPv1, problems result because the C4/c CMTS is unable to decipher the information that is communicated by a RIPv1
router. RIP supports only IPv4.
RIP version 2
RIP version 2 (RIPv2) is compatible with the C4/c CMTS. Unlike RIPv1 it supports subnet masks and Message Digest 5 (MD5)
authentication. For more information on this standard, see RFCs 2453 and 1058.
Hop Count
RIP uses a single criterion (hop count) for determining the best available route. Each route in a RIP routing table is assigned
a hop count of 1–16.
A value of 15 hops is the longest route permitted; once the hop count value reaches 16 the route is considered
unreachable.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
521
Chapter 16: Dynamic Routing Protocols
Routing Update Management
The following applies as regards to the management of routing updates:
Entries in the RIP routing tables are dynamically updated as needed.
As the topology of a network changes, some routes will become invalid.
RIP uses "aging" algorithms to eliminate invalid routes from its tables.
RIP Enable and Disable
The following RIP-related enable and disable tasks, along with their associated commands, are grouped for convenience.
This is not intended to be a step-by-step procedure.
Enabling RIP on the C4/c CMTS
By default, RIP is disabled on the C4/c CMTS.
Enter the following command to enable RIP:
configure router rip shutdown no
The system will respond:
RIP has been enabled
Validate RIP status:
show ip vrf
Virtual Router Details:
Name
Index
===============
==========
default
1
OSPF
====
no
RIP
===
yes
ISIS
====
no
BGP
===
no
ICMP-TIME-EXCEEDED
==================
no
Disabling RIP on the C4/c CMTS
Use the following command to disable RIP:
configure router rip shutdown
The system will respond:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
522
Chapter 16: Dynamic Routing Protocols
RIP has been disabled
Enabling RIP for a Network
By default, RIP is disabled for all networks. Enabling RIP for a network does not affect the global enable/disable state on
the C4/c CMTS.
To enable RIP for a network, enter the following command:
configure router rip network <network address>
Where: network address is the IP prefix of the desired network.
Confirm that RIP is enabled for the network:
show ip rip
The output should look something like the following:
RIP Interfaces
Interface
VRF
Df Met
Auth Mode
State
10.71.0.2
default
1
disabled
active
10.71.64.2
default
1
disabled
disabled
In this instance, an interface with an IP address 10.71.0.2 is actively running RIP. This interface is part of a network which
was enabled (10.71.0.0, for example).
Note: Secondary interfaces on RIP-enabled primary interfaces are automatically set to passive.
Disabling RIP for a Network
Use the following command to disable RIP for the default VRF network:
configure router rip network <network address> no
Confirm that RIP is disabled for the network. Following the command is a sample system response:
show ip rip
The output should look something like the following:
VRF
Status
default
enabled
RIP Interfaces
Interface
VRF
10.41.1.2
default
RIP Timers
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Df Met
0
Auth Mode
disabled
State
active
C4® CMTS Release 8.3 User Guide
523
Chapter 16: Dynamic Routing Protocols
VRF default: Update interval is set to 30 seconds.
VRF default: Route invalidation interval is set to 180 seconds.
VRF default: Route flush interval is set to 120 seconds.
In this instance, an interface with an IP address 10.71.0.2 is not running RIP. This interface is part of a network which was
disabled (10.71.0.0 for example).
RIP Passive Mode Operation
In order for an interface to receive and process RIP messages, but not advertise its routes, system administrators can
enable passive RIP mode operation. By the same token, this passive RIP mode of operation can be disabled.
The following RIP passive mode related enable and disable tasks, along with their associated commands are grouped for
convenience. This is not intended to be a step-by-step procedure.
Enabling RIP Passive Mode
To enable RIP passive mode on an interface, enter the following command:
configure router rip [vrf <name>] passive-interface {cable-mac <mac> | default | gigabitethernet
<slot>/<port> | tengigabitethernet <slot>/<port>}
Where:
cable-mac <mac>
is the MAC identifier
default
sets all RIP enabled interfaces to be passive
gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>
is the RCM slot number/port number of the specified
interface
Confirm that RIP is running in passive mode on an interface:
show ip rip
The output should look similar to the following:
RIP Interfaces
Interface
VRF
10.71.0.2
default
10.71.64.2
default
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Df Met
1
1
Auth Mode
disabled
disabled
State
passive
disabled
C4® CMTS Release 8.3 User Guide
524
Chapter 16: Dynamic Routing Protocols
In this instance, an interface with an IP address 10.71.0.2 is running RIP in passive mode.
Disabling RIP Passive Mode
Use the following command to disable the RIP passive mode previously set on an interface:
configure router rip passive-interface {cable-mac <mac> | default | gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>} no
The system will respond:
RIP interface disabled
Default Route Processing
By default, each interface running RIP advertises an available default route, static or learned via RIP, with a metric of 1.
Because default route propagation must be controlled carefully, system administrators can set the metric to be used for
default route advertisements on a per interface basis. If the default route metric is set to 0, the default route is not
advertised.
The following default route metric tasks, along with their associated commands are grouped for convenience. This is not
intended to be a step-by-step procedure.
Setting Default Route Metric
Use the following command to set the default route metric:
configure interface {cable-mac <mac> | default | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip default-metric <0-15>
Where:
cable-mac <mac>
is the MAC identifier
default
sets all RIP enabled interfaces to be passive
gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>
is the RCM slot number/port number of the specified
interface
0–15
are available default metrics; the original default metric is 0
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
525
Chapter 16: Dynamic Routing Protocols
Verify that the default metric is changed to match the value entered:
show ip rip
The output should look similar to the following:
VRF
Status
default
enabled
RIP Interfaces
Interface
VRF
10.62.1.2
default
RIP
VRF
VRF
VRF
Df Met
0
Auth Mode
text
State
active
Timers
default: Update interval is set to 30 seconds.
default: Route invalidation interval is set to 180 seconds.
default: Route flush interval is set to 120 seconds.
Plain Text Authentication
Plain text authentication may be enabled for each active or passive interface running RIP in order to add security to RIP
communication. By default it is disabled on each interface.
The following plain text authentication tasks, along with their associated commands are grouped for convenience. This is
not intended to be a step-by-step procedure.
Enabling Plain Text Authentication
Enter the following command to enable plain text authentication for a given interface:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication mode text
Where:
cable-mac <mac>
is the MAC identifier
gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>
is the RCM slot number/port number of the specified
interface
The system will respond:
Authentication mode is plain text
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
526
Chapter 16: Dynamic Routing Protocols
Creating Plain Text Key
Enter the following command to set authentication:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication key <testkey1>
Where:
testkey1
is a 1–16 character text string used for authentication.
Note: The key can be up to 16 characters long. Every RIP message sent on this interface contains this key and every
incoming message’s validation is dependent on its having this key.
Confirm that the interface is set up to do plain text authentication:
show ip rip
The output should look similar to the following:
VRF
Status
default
enabled
RIP Interfaces
Interface
VRF
10.62.1.2
default
RIP
VRF
VRF
VRF
Df Met
0
Auth Mode
text
State
active
Timers
default: Update interval is set to 30 seconds.
default: Route invalidation interval is set to 180 seconds.
default: Route flush interval is set to 120 seconds.
MD5 Digest Authentication
Message Digest 5 (MD5) authentication may be enabled for each active or passive interface running RIP in order to add
security to RIP communication. By default it is disabled on each interface.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
527
Chapter 16: Dynamic Routing Protocols
Encrypted Packets
Message Digest 5 (MD5) authentication allows a System Administrator to encrypt RIPv2 packets based on an interfacespecific key. This key is used to generate an MD5 hash which is appended to all outgoing RIP packets originating from the
C4/c CMTS.
Routers that receive these encrypted RIPv2 packets must have the same key associated with the incoming interface. The
key is used to verify the MD5 of each encrypted packet.
Similarly, all RIPv2 packets that are received by the C4/c CMTS interfaces for which MD5 is enabled must have the key
associated with that interface applied to all RIPv2 packets. These encrypted packets allow the C4/c CMTS to communicate
securely with other routers in the network.
Invalid Encryption
If a router or host attempts to provide the C4/c CMTS with RIP information and it does not have the correct MD5 hash, the
packet is dropped and an error message is logged.
Time-of-Day
The RIP protocol requires a sequence number to increase monotonically based on the time-of-day. This key is used to
generate an MD5 hash over the entire RIP message plus the concatenated plain-text key which is appended to all outgoing
RIP packets originating from the C4/c CMTS.
Any out-of-sequence number violates the monotonic sequence rule and the packet will be discarded. The C4/c CMTS uses
its system time as the MD5 message sequence number. As a result, exercise caution when changing the system time to an
earlier time.
If the C4/c CMTS is running RIPv2 with MD5 authentication and the system time is changed to an earlier time,
communication with peer routes cease until either the system time reaches it previous point, or all the RIP routes age out
of the routing tables on the C4/c CMTS.
Time-Out Limit
RIP routes sent by the C4/c CMTS to adjacent peer routers age out (time-out) five minutes after the last authenticated RIP
message was received.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
528
Chapter 16: Dynamic Routing Protocols
Single or Multiple Keys
For RIP with MD5 to interoperate with other routers, the external router must be set up to send and receive either using
one key or multiple keys.
Single Key Authentication
For single key MD5 authentication, the system administrator can define a single key for a specified physical interface. This
interface uses an infinite send and receive lifetime key and, therefore, never ages out.
In this configuration, the key ID associated with the key must be set to 0 on all peer routers. If a router receives a RIP
message with a non-matching key, it identifies the authentication mismatch and drops the message.
Enable Single Key Authentication
Use the following procedure to configure single key MD5 authentication.
To Enable Single Key Authentication
1. Set the single key authentication node on the physical interface:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication mode md5
Where:
cable-mac <mac>
is the MAC identifier
gigabitethernet <slot>/<port> |
tengigabitethernet <slot>/<port>
is the RCM slot number/port number of the specified
interface
The system will respond:
Authentication mode is keyed MD5 digest
2. Create the MD5 key:
configure interface {cable-mac <mac> | gigabitethernet <slot> | tengigabitethernet <slot>} ip rip
authentication key <key>
Where:
<key>
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
is a text string 1–16 characters long used for the key id.
C4® CMTS Release 8.3 User Guide
529
Chapter 16: Dynamic Routing Protocols
Note: The key can be up to 16 characters long. Every RIP message sent on this interface contains a digest and every
incoming message received is validated based on its digest.
3. Confirm that the interface is set up to do MD5 digest authentication:
show ip rip
The output should look similar to the following:
VRF
Status
default
enabled
RIP Interfaces
Interface
VRF
10.62.1.2
default
RIP
VRF
VRF
VRF
Df Met
0
Auth Mode
text
State
active
Timers
default: Update interval is set to 30 seconds.
default: Route invalidation interval is set to 180 seconds.
default: Route flush interval is set to 120 seconds.
Multiple Key Authentication
For multiple key authentication you need only assign a key chain that has been configured with more than one key.
Otherwise the MD5 functionality works as described in the single key mode.
For MD5 to interoperate, the keys and key IDs in the C4/c CMTS key chain must match the keys in the external router.
Enable Multiple Key Authentication (i.e., Key Chains)
Use this procedure to enable multiple key authentication.
To Enable Multiple Key Authentication
1. Create a key chain and key:
configure key chain <key chain name> key <key id> key-string <key>
Where:
key chain name is a text string up to 16 characters long.
key id
is a number between 0 and 255.
key
is a text string up to 16 characters long.
Both the key ID and the key defined on the C4/c CMTS must be the same as the key ID and key defined on the other
router. The key chain name used on the C4/c CMTS does not have to match that of the other router.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
530
Chapter 16: Dynamic Routing Protocols
To remove a key chain and all its keys:
configure key chain <key chain name> no
2. Enable MD5 digest authentication with multiple keys for a given interface:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication mode md5
3. Enable the key chain (created in step 1) on the same interface:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication key-chain <keychain1>
Where:
keychain1 is the name of the key chain to use.
Note: The key chain can be up to 16 characters long and determines which key is used for sending and receiving.
4. Confirm that the interface is set-up for MD5 digest authentication:
show ip rip
The output should look similar to the following:
VRF
Status
default
enabled
RIP Interfaces
Interface
VRF
10.62.1.2
default
RIP
VRF
VRF
VRF
Df Met
0
Auth Mode
text
State
active
Timers
default: Update interval is set to 30 seconds.
default: Route invalidation interval is set to 180 seconds.
default: Route flush interval is set to 120 seconds.
5. If desired, remove the keychain/interface assignment:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication key-chain <keychain1> no
6. If desired, disable MD5 authentication:
configure interface {cable-mac <mac> | gigabitethernet <slot>/<port> | tengigabitethernet
<slot>/<port>} ip rip authentication mode md5 no
Note: If you configure both single key and key chain authentication, only the key chain is used. Because of this, only the
key chain CLI command will appear in the running-config output.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
531
Chapter 16: Dynamic Routing Protocols
Route Redistribution for IPv4 Addresses
Route redistribution is defined as the ability to import and export IP routing information from one routing protocol domain
to another. In addition, Local (C4/c CMTS interface networks) and Static (Net Management) routes may be imported into a
protocol domain. The dynamic routing protocols RIPv2 and OSPF may be run at the same time.
The Route Table Manager (RTM) is responsible for choosing the best group of routes provided by each routing protocol. Its
choice is based on the administrative distance assigned to each protocol group. It should be noted this approach requires
that the administrative distance of each protocol entity, including static and connected routes, must be unique.
This feature supports route redistribution at the following levels:
From static to RIPv2 and OSPF
From connected (local) to RIPv2 and OSPF
From RIP to OSPF
From OSPF to RIPv2
This feature supports different types of distribution lists (filtering):
RIP input (per interface or global)
RIP output (per interface or global)
Route redistribution RIPv2 to OSPF
BGP Route Maps
For BGP, route-maps can be used to control the redistribution of IP routes from BGP into another protocol (match
functionality) or to redistribute routes from another protocol into BGP (set functionality).
Distribute-Lists for Route Redistribution within the Default VRF
Distribute-lists rely on standard ACLs to filter on a destination IP prefix. Because support for the BGP routing protocol
requires more complicated filtering of routes, this type of filtering is beyond the syntactic definition of distribute-lists.
The following is an example of default VRF distribute list commands:
configure router bgp 65500 redistribute connected
configure router bgp 65500 distribute-list 77 out connected
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
532
Chapter 16: Dynamic Routing Protocols
The command filters routes that are redistributed from various routing protocols (such as static, connected, ISIS, OSPF and
RIPv2) into BGP IPv4 AF.
Route Redistribution Filtering
MIB support built into the routing protocol software allows for the following BGP filtering to be used for route
redistribution (in addition to destination IP address filtering):
Next-Hop — Allows route redistribution to be controlled based on the advertising router (next-hop). May also be used
with other routing protocols
BGP Community Number (match or set) — 4 byte value identifying a BGP community
BGP Extended Community Number (match or set) — 8 byte value identifying a BGP community
BGP Origin (set) — Allows the origin attribute to be set for routes redistributed into BGP
Multi-Exist-Discriminator (set) — Allows a MED attribute value to be set for routes redistributed into BGP.
Local Pref — Allows a Local Preference attribute to be set for routes redistributed into BGP.
Update Message Attributes
The attributes that are applied to the complete group of routes in the BGP Update message are listed as follows:
Origin — Indicates how the IP prefixes became known to BGP.
IGP — Prefix was learned from an interior gateway protocol (e.g. OSPF).
EGP — Prefix was learned via EGP.
Incomplete — Protocol was learned from a source other than IGP/EGP. For example, static or local routes.
AS-Path — A list of ASs the group of routes has passed through.
Next-Hop — Identifies the next hop for the group of routes. This could be a third-party next-hop.
Multi-Exit-Discriminator — Allows for choosing the optimal link for a group of routes when more than one connection
exists between two ASs.
Local-Pref — Allows for choosing the optimal link for a group of routes when multiple connections exists to different
intermediate ASs.
Aggregator — Identifies the AS that performed route aggregation.
Communities — Ability to associate a unique identifier with a route. The following well-known communities are
supported:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
533
Chapter 16: Dynamic Routing Protocols
No-Export — The route must stay local to the AS.
No-Advertise — The route must stay local to the router.
No-Export-Subconfed — The route must stay local to a sub-AS.
Extended Communities — Needed for route targets on VPN-IPv4 routes.
MP-(Un)Reach-NLRI — Multi-protocol attribute needed for carrying VPN-IPv4 routes.
Capabilities — Used to advertise capabilities of the router. Needed for route refresh and VPN extensions.
Route Redistribution CLI Commands
The C4/c CMTS supports route redistribution between all protocols with filtering (see IP Route Filtering (page 537)) based
on distribute-lists. For more information on these CLI commands see the Command Line Descriptions.
RIP Redistribution Commands
The CLI supports the following RIP redistribute commands:
configure router rip
configure router rip
configure router rip
[no]
configure router rip
[metric <int>] [no]
configure router rip
[vrf <name>] redistribute bgp [metric <int>] [no]
[vrf <name>] redistribute connected [metric <int>] [no]
[vrf <name>] redistribute isis [<level1 | level-2 | level-1-2>] [metric <int>]
[vrf <name>] redistribute ospf [match <internal | external1 | external2>]
[vrf <name>] redistribute static [metric <int>] [no]
OSPF Redistribution Commands
The C4/c CMTS CLI supports the redistribution of static, connected, RIP, BGP, and IS-IS routes using the following OSPF
redistribute commands:
configure router ospf [vrf <VRF>] redistribute bgp [metric {<0-16777215> | transparent}] [metrictype <1 | 2>] [tag <1-4294967295>] [no]
configure router ospf [vrf <VRF>] redistribute connected [metric {<0-16777215> | transparent}]
[metric-type <1 | 2>] [tag <1-4294967295>] [no]
configure router ospf [vrf <VRF>] redistribute isis [{level1 | level-2 | level-1-2}] [metric <016777215>] [tag <1-4294967295>] [no]
configure router ospf [vrf <VRF>] redistribute rip [metric {<0-16777215> | transparent}] [metrictype <1 | 2>] [tag <1-4294967295>] [no]
configure router ospf [vrf <VRF>] redistribute static [metric {<0-16777215> } transparent}] [metrictype <1 | 2>] [tag <1-4294967295] [no]
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
534
Chapter 16: Dynamic Routing Protocols
BGP Redistribution Commands
The C4/c CMTS supports the redistribution of static, connected, RIP, OSPF, and IS-IS routes using the following BGP
redistribute commands:
configure router bgp [<int>] redistribute
configure router bgp [<int>] redistribute
[route-map <int>] [no]
configure router bgp [<int>] redistribute
<int>] [route-map <int>] [no]
configure router bgp [<int>] redistribute
configure router bgp [<int>] redistribute
connected [metric <int>] [route-map <int>] [no]
isis [<level1 | level-1-2 | level-2>] [metric <int>]
ospf [match <internal | external1 | external2>] [metric
rip [metric <int>] [route-map <int>] [no]
static [metric <int>] [route-map <int>] [no]
Route maps applied by the previous commands are limited to the following four commands:
configure route-map
[internet]
configure route-map
configure route-map
configure route-map
<word> set community [<WORD>] [none] [local-AS] [no-advertise] [no-export]
<word> set local-preference <INT>
<word> set metric <INT>
<word> set origin {igp | egp | incomplete}
Where: word is the name of the route map
Route maps may contain other commands, but these commands will not be applied to route redistribution.
The C4/c CMTS filtering commands that support VRF-aware distribute lists for route redistribution from non-default VRFs
include:
configure vrf <vrf_name> address-family ipv4 distribute-list <ipv4_std_acl> out static [no]
configure vrf <vrf_name> address-family ipv4 distribute-list <ipv4_std_acl> out connected [no]
configure vrf <vrf_name> address-family ipv4 distribute-list <ipv4_std_acl> out rip [no]
Where: vrf <vrf_name> is the VRF routing table to which the distribute list applies
<ipv4_std_acl> is a standard IPv4 access list
Note that these VRF-context distribute-list commands are similar in functionality and syntax to the other IPv4 BGP
distribute-list commands.
IS-IS Redistribution Commands
The C4/c CMTS supports the redistribution of static, connected, RIP, OSPF, and BGP routes using the following IS-IS
redistribute commands:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
535
Chapter 16: Dynamic Routing Protocols
configure router isis redistribute static {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
configure router isis redistribute connected {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
configure router isis redistribute rip {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
configure router isis redistribute ospf {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [match {internal | external1 | external2}] [no]
configure router isis redistribute bgp {level-1 | level-2 | level-1-2} [metric <int>]
[metric-type {internal | external}] [no]
IS-IS Redistribution Commands (IPv4)
The C4/c CMTS supports the redistribution of IPv4 address family connected, OSPF, PD and static routes using the
following IS-IS redistribute commands
configure router isis address-family ipv4 redistribute bgp {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
configure router isis address-family ipv4 redistribute connected {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
configure router isis address-family ipv4 redistribute ospf {level-1 | level-2} [match <internal |
external1 | external2>] [metric <int>] [metric-type {internal | external}] [no]
configure router isis address-family ipv4 redistribute static {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] no
configure router isis address-family ipv4 redistribute static {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
IS-IS Redistribution Commands (IPv6)
The C4/c CMTS supports the redistribution of IPv6 address family connected, OSPF, PD and static routes using the
following IS-IS redistribute commands:
configure router isis address-family ipv6 redistribute connected {level-1 | level-2} [metric <int>]
metric-type {internal | external}] [no]
configure router isis address-family ipv6 redistribute ospf {level-1 | level-2} [match <internal |
external1 | external2>] [metric <int>] metric-type {internal | external}] [no]
configure router isis address-family ipv6 redistribute pd {level-1 | level-2} [metric <int>]
metric-type {internal | external}] no
configure router isis address-family ipv6 redistribute static {level-1 | level-2} [metric <int>]
[metric-type {internal | external}] [no]
OSPFv3 Redistribution Commands
The C4/c CMTS supports redistribution of static, connected and PD routes using the following OPFv3 commands:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
536
Chapter 16: Dynamic Routing Protocols
configure ipv6 router ospf [vrf <VRF>] redistribute connected [metric <WORD>] [metric-type <INT>]
[tag <INT>]
configure ipv6 router ospf [vrf <VRF>] redistribute pd [metric <WORD>] [metric-type <INT>] [tag
<INT>]
configure ipv6 router ospf [vrf <VRF>] redistribute static [metric <WORD>] [metric-type <INT>] [tag
<INT>]
IP Route Filtering
Although not specifically associated with route redistribution, the C4/c CMTS supports the filtering of IP routes based on
an egress interface. The CadPolicyAclTable MIB must be used when creating an ACL. The ACL defined must be a standard
ACL (range 0-99).
Execution of this command will create an entry in the cadDistListOutTable. If the corresponding route redistribution
command has already been executed, then each entry in the ACL table will create an entry in the rtmRedistTable.
There must also be a wildcard match entry in the rtmRedistTable for either the permit_all or deny_all ACL case, with the
rtmRedistFlag set to AMB_TRUE or AMB_FALSE. The priority (rtmRedistPriority) must be set to a value greater than
(implies lower priority) the more specific matches.
Distribute-lists also control RIP route advertisement per physical interface.
For example:
configure access-list 10 deny 130.10.0.0 0.0.255.255
configure access-list 10 permit 0.0.0.0 255.255.255.255
configure router rip distribute-list 10 out ospf
Distribute List Out Configure Commands
To filter redistributed RIP routes, use the following commands:
configure router rip [no] distribute-list
tengigabitethernet} slot/port
configure router rip [no] distribute-list
configure router rip [no] distribute-list
configure router rip [no] distribute-list
configure router rip [no] distribute-list
configure router rip [no] distribute-list
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
ACL-NUM out {cable-mac | gigabitethernet |
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
out
out
out
out
out
static
connected
ospf
bgp
isis
C4® CMTS Release 8.3 User Guide
537
Chapter 16: Dynamic Routing Protocols
Filtering RIP Routes
To filter RIP routes on an ingress interface, use the following command:
configure router rip [no] distribute-list <access_list_number> in {cable | gigabitethernet |
tengigabitethernet} SLOT/PORT
The C4/c CMTS applies filtering to the destination IP prefixes of RIPv2 updates based on the ingress interface. The ACL
defined is a standard ACL (range 0-99).
The C4/c CMTS CLI supports filtering inbound rip updates with the following syntax:
configure router rip [no] distribute-list <access_list_number> in
The C4/c CMTS processes inbound RIP updates with the following rules:
1. Extract the next network from the inbound update.
2. Check the interface on which it entered.
3. Is there a distribute list applied to that interface?
Yes: Is the network denied by that list?
If the network is denied by that list or does not make it to the routing table; return to step 1.
If the network is allowed; then continue to step 4.
No, there is no list. Then go to step 4.
4. Is there a global distribute list?
Yes: Is the network denied by that list?
Yes: the network does not make it to the routing table; return to step 1.
No: the network makes it to the routing table; return to step 1.
No: The network makes it to the routing table; return to step 1.
Filtering Redistributed OSPF Routes
To filter redistributed OSPF routes, use the following commands:
configure
configure
configure
configure
configure
router
router
router
router
router
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
ospf
ospf
ospf
ospf
ospf
[vrf
[vrf
[vrf
[vrf
[vrf
<VRF>]
<VRF>]
<VRF>]
<VRF>]
<VRF>]
[no]
[no]
[no]
[no]
[no]
distribute-list
distribute-list
distribute-list
distribute-list
distribute-list
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
out
out
out
out
out
static
connected
rip
bgp
isis
C4® CMTS Release 8.3 User Guide
538
Chapter 16: Dynamic Routing Protocols
The C4/c CMTS continues to support distribute-lists for filtering RIP IP prefixes that are redistributed into OSPF. The
CadPolicyAclTable MIB must be used when creating an ACL. The ACL defined must be a standard ACL (range 0-99).
Execution of this command will create an entry in the cadDistListOutTable. If the corresponding route redistribution
command has already been executed, then each entry in the ACL table will create an entry in the rtmRedistTable.
There must also be a "wildcard" match entry in the rtmRedistTable for either the "permit_all" or "deny_all" ACL case, with
the rtmRedistFlag set to AMB_TRUE or AMB_FALSE.
Note: The priority (rtmRedistPriority) must be set to a value greater than (implies lower priority) the more specific
matches.
For example:
configure access-list 10 deny 130.10.0.0 0.0.255.255
configure access-list 10 permit 0.0.0.0 255.255.255.255
configure router ospf [vrf <VRF>] distribute-list 10 out rip
Filtering Redistributed BGP Routes
To filter redistributed BGP routes, use the following commands:
configure
configure
configure
configure
configure
router
router
router
router
router
bgp
bgp
bgp
bgp
bgp
[no]
[no]
[no]
[no]
[no]
distribute-list
distribute-list
distribute-list
distribute-list
distribute-list
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
out
out
out
out
out
static
connected
rip
ospf
isis
Although not specifically associated with route redistribution, the C4/c CMTS continues to support filtering IP routes based
on an egress interface. The existing CadPolicyAclTable MIB must be used when creating an ACL. The ACL defined must be a
standard ACL (range 0-99).
Execution of this command will create an entry in the cadDistListOutTable. If the corresponding route redistribution
command has already been executed, then each entry in the ACL table will create an entry in the rtmRedistTable.
There must also be a "wildcard" match entry in the rtmRedistTable for either the "permit_all" or "deny_all" ACL case, with
the rtmRedistFlag set to AMB_TRUE or AMB_FALSE.
Note: The priority (rtmRedistPriority) must be set to a value greater than (implies lower priority) the more specific
matches.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
539
Chapter 16: Dynamic Routing Protocols
For example:
configure
configure
configure
configure
access-list 10 deny any
access-list 10 permit 0.0.0.0 255.255.255.255
router bgp
router bgp 1 distribute-list 10 out ospf
Filtering Redistributed ISIS Routes
To filter redistributed IS-IS routes, use the following commands:
configure
configure
configure
configure
configure
router
router
router
router
router
isis
isis
isis
isis
isis
[no]
[no]
[no]
[no]
[no]
distribute-list
distribute-list
distribute-list
distribute-list
distribute-list
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
ACL-NUM
out
out
out
out
out
static
connected
rip
ospf
bgp
The existing CadPolicyAclTable MIB must be used when creating an ACL. The ACL defined must be a standard ACL (range 099).
Execution of this command will create an entry in the cadDistListOutTable. If the corresponding route redistribution
command has already been executed, then each entry in the ACL table will create an entry in the rtmRedistTable.
There must also be a "wildcard" match entry in the rtmRedistTable for either the "permit_all" or "deny_all" ACL case, with
the rtmRedistFlag set to AMB_TRUE or AMB_FALSE.
Note: The priority (rtmRedistPriority) must be set to a value greater than (implies lower priority) the more specific
matches.
For example:
configure
configure
configure
configure
access-list 10 deny 130.10.0.0 0.0.255.255
access-list 10 permit 0.0.0.0 255.255.255.255
router isis
router isis 1 distribute-list 10 out ospf
Filtering Outbound RIP Updates
To filter outbound rip updates originating at the C4/c CMTS, use the following commands:
configure router rip [no] distribute-list <access_list_number> out
The C4/c CMTS processes outbound RIP updates with the following rules:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
540
Chapter 16: Dynamic Routing Protocols
1. Select the next network to receive an outbound update.
2. Check which interface it is being sent out on.
3. Is there a distribute list applied to that interface?
Yes: Is the network denied by that list?
o Yes: the network does not go out; return to step 1.
o No: the network goes out; continue to step 4.
No: Go to step 4.
4. Check the routing process from which we derive the route.
5. Is there a distribute list applied to that process?
Yes: Is the network denied by that list?
o Yes: the network does not go out; return to step 1.
o No: the network goes out; continue to step 6.
No: Go to step 6.
6. Is there a global distribute list?
Yes: Is the network denied by that list?
o Yes: the network does not go out; return to step 1.
o No: the network goes out; return to step 1.
No: The network makes it; go to step 1.
Distance Configure Commands
To change the static route administrative distance, use the following commands:
configure router static distance <int>
configure router static no distance
Where: int
is an integer 1-255 = administrative distance range
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
541
Chapter 16: Dynamic Routing Protocols
The distance must be validated to ensure that it is unique among all the protocols. If the user attempts to start a protocol
whose administrative distance conflicts with a protocol that is already running, the attempt will fail until the user corrects
the problem.
To change the RIP route administrative distance, use the following command:
configure router rip distance <int>
configure router rip no distance
Where: int
is an integer 1-255 = administrative distance range
The distance must be validated to ensure that it is unique among all the protocols. If the user attempts to start a protocol
whose administrative distance conflicts with a protocol that is already running, the attempt will fail until the user corrects
the problem.
To change the OSPF route administrative distance, use the following command:
configure router ospf [vrf <VRF>] distance <int> ospf external external-value
configure router ospf [vrf <VRF>] no distance
Where: int
is an integer 1-255 = administrative distance range
To set the administrative distance for both internal and external (type 5, 7 LSA) OSPF routes, use the following command:
configure router ospf [vrf <VRF>] distance <int> ospf external <int2>
Where: int
int2
is an integer 1-255 = internal distance range
is an integer 1-255 = external distance range
To change the BGP administrative distance for both internal (iBGP) and external (eBGP) routes, use the following
command:
configure router bgp distance bgp <int>
Where: int
is an integer 1-255 = administrative distance range
To change the IS-IS route administrative distance, use the following commands:
configure router
configure router
[internal-level1
configure router
Where: int
isis distance <int>
isis distance <1-255> isis [external-level1 <int>] [external-level2 <int>]
<int>] [internal-level2 <int>]
isis no distance
is an integer 1-255 = administrative distance range
The C4/c CMTS sets the administrative distance for internal ISIS routes and external level-1 and level-2 routes.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
542
Chapter 16: Dynamic Routing Protocols
Specific distances (if supplied) override the value supplied by IS-IS-VALUE.
For example:
configure router isis
configure router isis distance 100
Displaying Route Information
To display redistribution settings, use the following command:
show ip {rip | isis | bgp | ospf}
show ipv6 {isis | ospf}
To display redistributed route information for all protocols, use the following command:
show ip protocols
An output similar to the following occurs:
Routing Protocol is "ospf default"
Redistribution: ON
static, admin distance: 1
connected, admin distance: 0
Routing for Networks:
22.22.22.22/32
192.168.202.2/32
192.168.203.2/32
Routing Information Sources:
Gateway
Last Update
192.168.202.1
0 days 0:19:16
192.168.202.2
0 days 0:27:58
Default Distance:
Internal: 30
External: 110
To display the distribute-lists for each protocol:
show distribute-list [rip | ospf | bgp | isis]
The output is similar to the distribute-list portion of the show running config command.
To display the administrative distance for each route:
show ip route
In the sample output that follows, the Metric column is the metric value or cost of a specific route, and the Dist column is
the administrative distance for a particular routing protocol such as OSPF:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
543
Chapter 16: Dynamic Routing Protocols
Codes:
(L1) internal level-1,
(S) summary,
(I) internal,
VRF Name
===============
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
default
(L2) internal level-2,
(IA) internal area,
(E) external
(eL1) external level-1,
(E1) external type-1,
IP Route Dest.
Act PSt Next Hop
================== === === ===============
0.0.0.0/0
Yes IS 192.168.202.1
0.0.0.0/0
Yes IS 192.168.203.1
22.22.22.22/32
Yes IS 22.22.22.22
192.168.129.0/24
Yes IS 192.168.202.1
192.168.129.0/24
Yes IS 192.168.203.1
192.168.136.0/24
Yes IS 192.168.202.1
192.168.136.0/24
Yes IS 192.168.203.1
192.168.145.0/24
Yes IS 192.168.202.1
192.168.145.0/24
Yes IS 192.168.203.1
192.168.176.0/24
Yes IS 192.168.202.1
192.168.176.0/24
Yes IS 192.168.203.1
192.168.177.0/24
Yes IS 192.168.202.1
192.168.177.0/24
Yes IS 192.168.203.1
192.168.190.0/24
Yes IS 192.168.202.1
192.168.190.0/24
Yes IS 192.168.203.1
192.168.196.0/24
Yes IS 192.168.202.1
192.168.196.0/24
Yes IS 192.168.203.1
192.168.197.0/24
Yes IS 192.168.202.1
192.168.197.0/24
Yes IS 192.168.203.1
192.168.202.0/24
Yes IS 192.168.202.2
192.168.203.0/24
Yes IS 192.168.203.2
192.168.205.0/24 Yes IS 192.168.205.1
Metric
======
1
1
0
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
20
0
0
0
Protocol
========
ospf(E2)
ospf(E2)
local
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
ospf(E2)
local
local
local
(eL2) external level-2
(E2) external type-2
Dist Route Age
==== ============
110
0 02:00:23
110
0 02:00:23
0
0 02:12:13
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
110
0 02:00:24
0
0 02:12:08
0
0 02:01:09
0
0 02:10:25
Interface
=========
TenGg 18/10.0
TenGg 18/10.0
loop 0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
TenGg 18/10.0
cMac 1.0
To display the total number of all routes:
show ip route summary
An output similar to the following is returned:
IP routing table name is default(1)
Route Source
Routes
============
======
Local
4
OSPF Type 2 External
17
OSPF Total
17
VR Total
21
IP routing table name is tag70(2)
Route Source
Routes
============
======
Local
4
VR Total
4
Total
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
25
C4® CMTS Release 8.3 User Guide
544
Chapter 16: Dynamic Routing Protocols
Policy-Based Routing (PBR)
IP packets are normally directed by routing protocols and route tables, which make forwarding decisions based on the
destination IP addresses of packets. Policy-based Routing (PBR) enables network engineers to create policies for packets
with matching criteria, causing them to take paths that differ from the next-hop path specified by the route table. To
enable PBR, the user must configure a route map and apply it to an interface. PBR is then applied to all incoming packets
arriving at that interface.
The principal benefits of PBR include the following:
Forwarding is based not on destination IP address but on packet attributes such as source IP or packet type.
Route maps can improve service by enforcing Quality of Service (QOS) sorting at the edge router.
Cost-savings can be achieved by segregating slow bulky traffic from time-sensitive traffic.
Traffic can be separated according to desired characteristics and load balanced across multiple and unequal paths.
Note: The route maps used by the BGP routing protocol are part of a separate feature and are not affected by commands
to create or configure policy-based route maps.
Configuring PBR
Configuring PBR involves creating a route map with match and set commands and then applying the route map to an
interface.
Route Map Statements
Route map statements can result in a permit or deny action on matching packets
Deny means that normal destination-based routing will be used to forward the packet;
Permit means that some set command will be used to route the packet.
Route maps are given unique names (map-tags in CLI) and can have up to ten statements. Each statement is assigned a
sequence number. Because the C4/c CMTS supports a maximum of 2,048 route map statements, if each route map
contains a maximum of ten statements, the C4/c CMTS could support a maximum of 204 route maps.
Types of PBR commands:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
545
Chapter 16: Dynamic Routing Protocols
match ip address
set ip tos
set ip precedence
set ip next-hop
set ip backup-next-hop
set ip interface null 0
Operational Guidelines
The user should be aware of the following:
PBR is also applied to packets destined to IP addresses of the C4/c CMTS. A misconfigured policy could cause the C4/c
CMTS not to receive packets that it should receive.
The C4/c CMTS supports PBR for IPv4 unicast packets only.
The C4/c CMTS does not support PBR for IPv6 packets.
PBR cannot be used on packets coming in from the SCM management 19/0 and 20/0 interfaces.
If a route map matches a packet to an ACL that contains a deny keyword, then the effect of that deny is to cause the
packet to be forwarded using destination-based (not policy-based) routing.
A route map cannot be changed from permit to deny, or from deny to permit. To make such a change you must first
remove the route map, make the change, and add it.
If the same sequence number is used in two route map commands in the same route map, then the first one is
overwritten by the second.
A route map can be created that references an ACL before the ACL is defined. If the route map is used before the ACL is
defined, then the packet will be routed normally.
The only set interface statement supported is set interface null 0, which is used to drop packets.
PBR can work in conjunction with multiple VRFs. PBR is configured on a sub-interface which may be assigned to a VRF
also. If a next-hop is used in the route-map command, the next-hop IP needs to be in the same VRF (or the default VRF)
as the ingress interface. If no next-hop is specified for the route-map (e.g., a set IP ToS is used without a set next-hop),
the packet is routed using the normal VRF routing mechanism.
Counts
The C4/c CMTS keeps packet and byte counts for the following events:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
546
Chapter 16: Dynamic Routing Protocols
The ACL counter will be incremented when the packet matches the ACL specification. This ACL check is done before the
PBR set action is evaluated.
A PBR match occurs and the PBR match count is incremented when a packet arrives at a PBR-enabled interface and all
of the set commands of the route map work.
Packets that match at least one match statement, but then had one or more set statements fail are counted by the PBR
failed counter. In practice this means that either the set next-hop or set backup-next-hop failed.
Match Statements
The following guidelines should be observed when creating match statements:
This implementation of PBR can use standard access control lists to match source IP addresses or extended ACLs to
specify match criteria for source and destination IP, application, protocol type, or ToS.
In any one sequence number (map entry) only one ACL can be specified for the match IP address command. However,
multiple match IP address ACLs can be concatenated into the one ACL specified by the sequence number.
If the route map is applied to a packet and no match is found, the packet is not dropped; instead, it is forwarded using
destination-based routing.
If a route map is created with no match criteria, then it will be applied to all packets that come in to the specified
interface. All set operations will be performed on all packets (unless the set fails).
Only one match statement is allowed for each sequence number. When a packet matches the match statement with
the lowest sequence number, only the corresponding set statements in that route-map will be processed. If the set
statements fail, then the packet will fall back to normal destination-based routing. The packet will not be checked for
additional matches.
Set IP ToS
The configure route-map-policy *
are used (one of the bits is reserved).
permit * set ip tos
command is used to set the 5 ToS bits; values 0, 1, 2, 4, and 8
Table 70. Setting ToS Values
ToS Value | name
Description
0 | normal
Sets the normal ToS
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
547
Chapter 16: Dynamic Routing Protocols
ToS Value | name
Description
1 | min-monetary-cost
Sets the min-monetary-cost ToS
2 | max-reliability
Sets the max reliable ToS
4 | max-throughput
Sets the max throughput ToS
8 | min-delay
Sets the min delay ToS
The ToS value for DOCSIS classification is not supported.
Set IP Precedence Values
The configure route-map-policy * permit * set ip precedence [number | name] route map configuration
command enables you to set the three IP precedence bits in the IP packet header. With three bits, you have eight possible
values for the IP precedence; values 0 through 7 are defined.
Table 71. Setting IP Precedence Values
Precedence Value| name
Description
0 | routine
Sets the routine precedence
1 | priority
Sets the priority precedence
2 | immediate
Sets the immediate precedence
3 | flash
Sets the flash precedence
4 | flash-override
Sets the Flash override precedence
5 | critical
Sets the critical precedence
6 | internet
Sets the internetwork control
precedence
7 | network
Sets the network precedence
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
548
Chapter 16: Dynamic Routing Protocols
The C4/c CMTS does not use the new precedence value for DOCSIS classification, but if it is included it can be used in
routers or devices north of the C4/c CMTS.
Set IP DSCP
The configure route-map-policy * permit * set ip dscp is used to overwrite the six Differentiated Services
Codepoint (DSCP) bits in the Type of Service (ToS) byte with the keywords (see table below) or with a numeric value (0 63). Valid keywords are those listed in the Value column below. The DSCP values include Assured Forwarding (AF), Class
Selector (CS), and Expedited Forwarding (EF).
Table 72. Setting IP DSCP Value
Value
Overwrite the DSCP field with...
<0-63>
the specified codepoint value
af11
AF11 dscp (0b001010)
af12
AF12 dscp (0b001100)
af13
AF13 dscp (0b001110)
af21
AF21 dscp (0b010010)
af22
AF22 dscp (0b010100)
af23
AF23 dscp (0b010110)
af31
AF31 dscp (0b011010)
af32
AF32 dscp (0b011100)
af33
AF33 dscp (0b011110)
af41
AF41 dscp (0b100010)
af42
AF42 dscp (0b100100)
af43
AF43 dscp (0b100110)
cs1
CS1 (precedence 1) dscp (0b001000)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
549
Chapter 16: Dynamic Routing Protocols
Value
Overwrite the DSCP field with...
cs2
CS2 (precedence 2) dscp (0b010000)
cs3
CS3 (precedence 3) dscp (0b011000)
cs4
CS4 (precedence 4) dscp (0b100000)
cs5
CS5 (precedence 5) dscp (0b101000)
cs6
CS6 (precedence 6) dscp (0b110000)
cs7
CS7 (precedence 7) dscp (0b111000)
default
default dscp (0b000000)
ef
EF dscp (0b101110)
Set IP Next-hop
The configure route-map-policy * permit * set IP next-hop command specifies the IP address of the adjacent nexthop router in the path toward the packet's destination. The IP address must be the address of an adjacent router. The
address must be in the same subnet as the C4/c CMTS interface address, but not be the same as the C4/c CMTS interface
address or the subnet broadcast address. With the set ip next-hop command, the routing table is checked only to
determine whether the next hop can be reached, not whether the ultimate destination is reachable. Use the NO version of
the command to delete it from a route map. For an illustration see the flowchart in the figure below.
Note: Upstream packets which are forwarded by Policy Based Routing (PBR) using 'ip nexthop' or 'ip backup nexthop' may
be sent twice or dropped. This is caused by the unsynchronized ARP aging activity in the multiple forwarding engines. To
avoid this problem, add static arp entries for 'ip nexthop' or 'ip backup nexthop'.
Set IP Backup Next-hop
The set IP backup next-hop command provisions a backup next-hop IP address. If the next-hop IP address is unreachable,
then the C4/c CMTS uses the backup next-hop address. If it is not provisioned or if the backup-next-hop is unreachable,
then the C4/c CMTS resorts to normal destination-based routing. Use the NO version of the command to delete it from a
route map. For an illustration see the flowchart in the figure below.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
550
Chapter 16: Dynamic Routing Protocols
Set IP Recursive Next Hop
The configure route-map-policy * permit * set ip recursive-next-hop command permits the configuration of a
recursive next-hop IP address that is used in conjunction with PBR. The recursive next-hop IP address that is specified is
used as the Destination IP Address (DIP) to perform a route lookup to resolve the next-hop address. For an illustration see
the flowchart in the figure above.
The C4/c CMTS uses this IP address as the DIP instead of the DIP in the packet to forward the packet.
The following items apply to the configuration of the recursive next hop feature:
The configuration of IP recursive next-hop and IP next-hop are mutually exclusive. An attempt to configure both in the
same route map will be rejected.
The specified recursive-next-hop IP address can be any valid routable, unicast IP address that is not a C4/c CMTS
interface address.
A command configuration attempt to assign a C4/c CMTS interface address as a recursive-next-hop IP address causes
the command to be rejected as explained in the accompanying failure message.
The IP address does not have to be directly connected, and feature performance is actually optimal when the IP
address is not directly connected, because this allows normal ECMP and normal redundancy to be used to route the
packet.
If the recursive next-hop route lookup is successful:
The packet is sent using the new IP address as the DIP in the route table lookup. Note that the DIP in the packet is not
changed.
If the subnet is directly connected, the ARP entry of the recursive next-hop is used (or learned, then used).
If the subnet is remote (not directly connected), one of the ECMP route next-hop ARP entries is used (or learned, then
used).
If the C4/c CMTS fails to find a route using the recursive next hop IP, the packet is dropped and an ICMP network
"unreachable" message is sent back to the sender.
Set IP Interface Null 0
The set IP interface null 0 command is a way to drop packets. By routing undesired packets to the null interface, the C4/c
CMTS drops them and prevents them from going to a default route and possibly causing a routing loop.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
551
Chapter 16: Dynamic Routing Protocols
Figure 84: Flowchart Representing Decision Path for PBR or Normal Routing
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
552
Chapter 16: Dynamic Routing Protocols
Local PBR
The C4/c CMTS supports local PBR to apply policies to packets sourced from the In-band Management port of the SCM. Inband Management (also called SCM access) is enabled by the configure ip scm access command.
Policies are applied to all IPv4 protocol packets.
CLI Commands for PBR
The following table is a listing of the common PBR commands.
Table 73. PBR CLI Commands
Purpose
CLI Command
The first command configures a route map named ReRoute
which matches on access list number 10.
The second command overwrites the first and sets the
ReRoute map to match on ACL 20.
configure route-map-policy ReRoute permit 100 match ip address 10
configure route-map-policy ReRoute permit 100 match ip address 20
The first command configures route map named ReRoute to
match to set the next-hop ip address to 1.2.3.4.
The second command overwrites sequence number 100 and
sets the next-hop ip address to 5.6.7.8.
configure route-map-policy ReRoute permit 100 set ip next-hop 1.2.3.4
configure route-map-policy ReRoute permit 100 set ip next-hop 5.6.7.8
This command configures a route map name ReRoute which
matches on access list number 30. The packets which match
the ACL are forwarded using destination-based (not policybased) routing because the route map type is deny.
configure route-map-policy ReRoute deny 200 match ip address 30
Deletes the route map named ReRoute.
configure no route-map-policy ReRoute
Deletes only sequence number 30 from the route map named
ReRoute.
configure no route-map-policy ReRoute 30
Configures a local policy route map named my_route_map.
configure ip local policy route-map-policy my_route_map
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
553
Chapter 16: Dynamic Routing Protocols
Purpose
CLI Command
Specifies the IP address of the adjacent next-hop router in the
path toward the packet's destination.
configure route-map-policy my_route_map permit 10 set ip next-hop
10.69.1.1
Provisions a backup next-hop IP address.
configure route-map-policy my_route_map permit 10 set ip backup-nexthop 10.69.2.1
Provisions an IP null interface for packets that you wish to
drop.
configure route-map-policy my_route_map permit 10 set ip interface null
0
Apply the route map to a cable mac.
configure interface cable-mac 1.1 ip policy route-map-policy
my_route_map
Clears the counters that pertain to the specified route map.
If no route map is specified, the second command clears
counters for all route maps.
clear route-map-policy counters my_route_map
clear route-map-policy counters
Displays the match and set clauses for each sequence entry of
each route map. It also displays matching packet and byte
counts and failed packets and byte counts for each map entry.
show route-map-policy
Displays interfaces for which PBR is enabled and the route
maps that are assigned to each of those interfaces.
show ip policy
Displays address, VRF, protocol, and policy configuration for
the specified interface.
show ip interface cable-mac 1.1
Examples showing the use of various PBR CLI commands:
configure
configure
configure
configure
configure
configure
configure
access-list 199 permit tcp any eq 3918 any
access-list 199 permit tcp any eq 2126 any
route-map-policy pbrlocal permit match ip address 199
route-map-policy pbrlocal set ip precedence critical
route-map-policy pbrlocal set ip next-hop 10.63.0.1
route-map-policy pbrlocal set ip backup-next-hop 10.63.128.1
ip local policy route-map-policy pbrlocal
PBR Script Setup – Apply Route Map
This sample script applies a route map named testroutemap to interface cable-mac 1. If the packets entering the C4/c
CMTS from interface cable-mac 1 match ACL 155, they are sent to the interface connected to a router with the IP address
67.59.234.169.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
554
Chapter 16: Dynamic Routing Protocols
1. Create an extended ACL 155 to match packets with destination IP address in the 11.0.0.0/8 or 14.0.0.0/8 subnets and
the precedence value set as routine:
configure access-list 155 permit ip any 11.0.0.0 0.255.255.255 precedence routine
configure access-list 155 permit ip any 14.0.0.0 0.255.255.255 precedence routine
2. Configure route map named testroutemap and sequence number 10 to match ACL 155:
configure route-map-policy testroutemap permit 10 match ip address 155
3. Set the next hop address to 67.59.234.169:
configure route-map-policy testroutemap permit 10 set ip next-hop 67.59.234.169
4. Apply the route map named testroutemap to interface cable-mac 1:
configure interface cable-mac 1 ip policy route-map-policy testroutemap
5. Run the following show commands to confirm your configuration:
show
show
show
show
access-list
ip interface cable-mac 1
route-map-policy
ip policy
PBR Script Setup – IP Next-Hop
The following script is offered as an example of an implementation of PBR. PBR can be applied to one or more C4/c CMTS
interfaces. The two chosen in the following procedure are meant as examples.
1. Create standard access lists 20, 30 & 40:
configure access-list 20 permit 10.10.20.0 0.0.0.255
configure access-list 30 permit 10.10.30.0 0.0.0.255
configure access-list 40 permit 10.10.40.0 0.0.0.255
2. Configure route map named routemap1 and sequence number 10 to match ACL 20; set the next-hop to 10.69.1.1; and
set the backup next-hop to 10.69.2.1:
configure route-map-policy routemap1 permit 10 match ip address 20
configure route-map-policy routemap1 permit 10 set ip next-hop 10.69.1.1
configure route-map-policy routemap1 permit 10 set ip backup-next-hop 10.69.2.1
3. Configure routemap1, sequence number 20, to match ACL 30; set the next-hop to 10.69.3.1; and set the backup nexthop to 10.69.4.1; and set the ToS to normal:
configure
configure
configure
configure
route-map-policy
route-map-policy
route-map-policy
route-map-policy
routemap1
routemap1
routemap1
routemap1
permit
permit
permit
permit
20
20
20
20
match ip address 30
set ip next-hop 10.69.3.1
set ip backup-next-hop 10.69.4.1
set ip tos normal
4. Configure routemap1, sequence number 30, to drop all packets:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
555
Chapter 16: Dynamic Routing Protocols
configure route-map-policy routemap1 permit 30 set ip interface null 0
5. Configure route map named routemap2, sequence number 20, to match ACL 40 and set the next-hop to 10.69.5.1:
configure route-map-policy routemap2 permit 20 match ip address 40
configure route-map-policy routemap2 permit 20 set ip next-hop 10.69.5.1
6. Apply routemap1 to interface cable-mac 1.1:
configure interface cable-mac 1.0 ip policy route-map-policy routemap1
7. Apply routemap2 to the interface gigabitethernet 17/0.0:
configure interface gigabitethernet 17/0.0 ip policy route-map-policy routemap2
8. Apply routemap2 to local policy (packets from the SCM):
configure ip local policy route-map-policy routemap2
9. Run the following show commands to confirm your configuration:
show
show
show
show
route-map-policy
ip policy
ip interface cable-mac 1
ip interface gigabitethernet 17/0.0
PBR Script Setup – IP Recursive Next-Hop
PBR can be applied to one or more C4/c CMTS interfaces. The following script is offered as an example of an
implementation of PBR using IP recursive next hop:
1. Create standard access list 99:
configure access-list 99 permit 10.113.0.50
2. Configure route-map-policy PBR to match ACL 99:
configure route-map-policy pbr permit match ip address 99
3. Set the recursive next-hop to 10.10.10.100 for route map policy PBR:
configure route-map-policy pbr set ip recursive-next-hop 10.10.10.100
4. Apply route-map-policy PBR to cable-mac 1:
configure interface cable-mac 1.0 ip policy route-map-policy pbr
See see "Show Commands (page 556) below for sample system responses to these show commands.
Show Commands
Below are examples of show commands to be used with PBR followed by sample system responses:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
556
Chapter 16: Dynamic Routing Protocols
show route-map-policy
Sample output:
Route-map routemap1, permit, sequence 10
Match clauses:
ip address (access-lists): 20
Set clauses:
ip next-hop
10.69.1.1
ip backup-next-hop 10.69.2.1
Policy routing matches: 0 packets, 0 bytes
Policy routing failed : 0 packets, 0 bytes
permit, sequence 20
Match clauses:
ip address (access-lists): 30
Set clauses:
ip next-hop
10.69.3.1
ip backup-next-hop 10.69.4.1
ip tos
normal
Policy routing matches: 0 packets, 0 bytes
Policy routing failed : 0 packets, 0 bytes
permit, sequence 30
Match clauses:
Set clauses:
ip interface null
Policy routing matches: 0 packets, 0 bytes
Policy routing failed : 0 packets, 0 bytes
Route-map routemap2, permit, sequence 20
Match clauses:
ip address (access-lists): 40
Set clauses:
ip next-hop
10.69.5.1
Policy routing matches: 0 packets, 0 bytes
Policy routing failed : 0 packets, 0 bytes
show access-list
Sample output:
Extended IP access list 155
10 permit ip any 11.0.0.0 0.255.255.255
20 permit ip any 14.0.0.0 0.255.255.255
show ip policy
precedence routine
precedence routine
(0 matches)
(0 matches)
Sample output:
Interface
--------------------------------------STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
Route map
--------C4® CMTS Release 8.3 User Guide
557
Chapter 16: Dynamic Routing Protocols
Local
gigabitethernet 17/0.
cable-mac 1.0
show ip interface cable-mac 1
routemap2
routemap2
routemap1
Sample output:
cable-mac 1.0, VRF: default, IP Address: 10.142.0.1/19
Secondary IP Address(es):
*10.242.224.1/19
10.253.42.1/25
Physical Address: 0001.5c61.1e46
MTU is 1500
DHCP Policy mode is enabled
DHCP Server Helper Address(es):
10.44.249.46 for Traffic Type "mta"
10.50.42.3 for Traffic Type "cm"
Directed Broadcast is disabled
ICMP unreachables are always sent
Multicast reserved groups joined: None
Source-verify is disabled
InOctets
=
3939375
OutOctets
=
InUcastPkts =
12346
OutUcastPkts=
InDiscards =
0
OutDiscards =
InErrors
=
0
OutErrors
=
InMcastPkts =
94
OutMcastPkts=
show ip interface gigabitethernet 17/0.0
1904501
8322
0
0
4
Sample output:
gigabitethernet 17/0.0, VRF: default, IP Address: 10.92.128.2/24
Secondary IP Address(es):
No Secondary Addresses
Physical Address: 0001.5c61.1e23
MTU is 1500
DHCP Policy mode is disabled (primary mode)
DHCP Server Helper Address(es):
No Helper Addresses
Directed Broadcast is disabled
ICMP unreachables are always sent
Multicast reserved groups joined: None
Policy routing is disabled
InOctets
=
1214300
OutOctets
=
InUcastPkts =
4031
OutUcastPkts=
InDiscards =
0
OutDiscards =
InErrors
=
0
OutErrors
=
InMcastPkts =
0
OutMcastPkts=
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
1936336
7450
0
0
2
C4® CMTS Release 8.3 User Guide
558
Chapter 16: Dynamic Routing Protocols
Caution: Care should be exercised when using the set ip next-hop and set ip backup-next-hop commands in policies.
DHCP and other messaging critical to modem registration may have the wrong next hop applied, leading to unintended
results. When setting ipnext-hop and ip backup-next-hop in a PBR policy, it is recommended that extended ACLs be
used to match only the specified protocol.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
559
Chapter 17
IP Packet Filters, Subscriber Management
Overview ..........................................................................................560
IP Packet Filtering .............................................................................560
Upstream Drop Classifiers ................................................................583
Overview
Filtering out packets destined for infrastructure components allows an MSO to reduce the risk of outside break-ins, such as
denial-of-service attacks. Separate configuration files referencing different filter groups could be used as part of a multiple
Internet Service Provider (ISP) application.
IP Packet Filtering
IP packet filtering provides a way for the network administrator to precisely define how incoming IP traffic is managed. IP
packet filtering is an important element in maintaining the integrity of C4/c CMTS traffic. The IP Packet Filtering feature is
based on DOCSIS Subscriber Management Filtering.
Note: Downstream traffic cannot be filtered by matching on IP destinations for the host address 255.255.255.255
(broadcast) or the 224.0.0.0/4 range (multicast).
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
560
Chapter 17: IP Packet Filters, Subscriber Management
IP Packet Filter
An IP packet filter is a provisionable mechanism that examines the header of each IP packet and looks to match the
contents of any or all of the following data fields:
Source IPv4 address
Source IPv4 mask
Destination IPv4 address
Destination IPv4 mask
Source IPv6 address
Source IPv6 prefix
Destination IPv6 address
Destination IPv6 prefix
Type of service
IP Version
IPv6 Flow Label
Source port
Destination port
IP Protocol
When a match condition occurs, one of the following filter actions can be taken:
Drop
Accept
Note: Optional IP packet filters can be provisioned to match these fields.
IP Filter Groups
IP filters are configured in groups. The filters in each group are kept in an ordered list and applied in sequence.
The first IP filter in the sequence to satisfy the matching requirements is used as the one and only match. When an IP filter
encounters a packet that matches, the match count for this IP filter is incremented and the packet is accepted or dropped
depending on the action programmed for this IP filter. If no rules match then the packet is accepted.
A packet matches a filter if all of the values of the filter fields match the values in the corresponding packet fields.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
561
Chapter 17: IP Packet Filters, Subscriber Management
If there is a match, the C4/c CMTS increments the count for this filter and (depending on how the filter is configured):
Accepts the packet
Accepts and logs the accepted packet
Drops the packet
Drops and logs the dropped packet
Note: The logging of all allowed packets and dropped packets will cause a considerable load on the C4/c CMTS. The CMTS
automatically disables logging after reaching a limit of 1,000 packets.
Cable Modem Registration
When a cable modem registers, filter groups for upstream and downstream packets are assigned to it. Also, each modem is
assigned additional filter groups that will be used for CPEs behind that cable modem. These filter groups are based on the
device classes of the CPEs. See Filter Groups Based on Device Class (page 651).
Additionally, three sets of data are used to determine if IP packet filtering is to be applied to the modem:
First, the modem configuration file can include TLVs that instruct the C4/c CMTS to set up IP packet filtering for that
modem and the CPEs behind it.
Then, if these TLVs are not present, the C4/c CMTS checks if defaults are provisioned for the subinterface the CM or
CPE is on.
Finally, if neither of these are present, then the system-wide parameters specifying default filter groups are applied.
For the filter parameters to take effect:
The Subscriber Management feature must be enabled (default = active)
The desired filters must be configured
Cable modems must register or re-register in order to use their filters
Individual filters can be modified with new rules applied dynamically.
If a filter group has been applied to a registered modem and a new filter index is added to that group, the modem does not
have to re-register for that filter index to be enabled.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
562
Chapter 17: IP Packet Filters, Subscriber Management
Filter Group Rules
Every rule in a filter group is identified by a number from 1- 63. This number is called its index in the CLI and is necessary to
add, delete, or modify an individual filter of a filter group. The index numbers also specify the order in which the filters of a
filter group are applied, starting with index number one and ending with number 63.
Calculating Filter Groups
The CLI allows for the creation of up to 1,023 groups and also allows up to 63 rules (indexes) in any filter group. However,
the C4/c CMTS supports a maximum of 16,384 rules. So if all 1,023 groups are configured, they could average only 15 rules.
For example, 260 filter groups could be created, each containing the maximum 63 rules and be within the 16,384 C4/c
CMTS rule limit (16384/63 = 260 filter groups)
Note that protocol types 256 and 257 use more resources than others. Each rule with a match action for type 256 counts
as three rules toward the total of 16,384. Each rule with a match action for type 257 counts as two towards the total.
For this example, if each filter group contained 63 rules, including one type 256 and one type 257, then the maximum
number of filter groups that could be created would be 248 groups. This is derived by adding one extra rule for type 257
and two extra rules for type 256 which equals 66 rules that are divided into the 16,384 maximum. (16384/66 = 248 filter
groups)
Note: A value of 0 indicates that no filter group applies.
Drop Packets Log Data
The following command examples drop packets for filter group 4, indices 1 through 5:
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
group
group
group
group
group
group
group
group
group
group
group
group
4
4
4
4
4
4
4
4
4
4
4
4
index
index
index
index
index
index
index
index
index
index
index
index
1
1
1
1
1
1
1
1
1
1
2
2
ip-version ipv4
src-ip 0.0.0.0
src-mask 0.0.0.0
src-port 65536
dest-ip 0.0.0.0
dest-mask 0.0.0.0
dest-port 135
ip-proto 257
match-action drop
ip-tos 0x0 0x0
ip-version ipv4
src-ip 0.0.0.0
C4® CMTS Release 8.3 User Guide
563
Chapter 17: IP Packet Filters, Subscriber Management
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
filter
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
group
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
4
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
index
2
2
2
2
2
2
2
2
3
3
3
3
3
3
3
3
3
3
4
4
4
4
4
4
4
4
4
4
5
5
5
5
5
5
5
5
5
5
src-mask 0.0.0.0
src-port 65536
dest-ip 0.0.0.0
dest-mask 0.0.0.0
dest-port 137
ip-proto 257
match-action drop
ip-tos 0x0 0x0
ip-version ipv4
src-ip 0.0.0.0
src-mask 0.0.0.0
src-port 65536
dest-ip 0.0.0.0
dest-mask 0.0.0.0
dest-port 138
ip-proto 257
match-action drop
ip-tos 0x0 0x0
ip-version ipv4
src-ip 0.0.0.0
src-mask 0.0.0.0
src-port 65536
dest-ip 0.0.0.0
dest-mask 0.0.0.0
dest-port 139
ip-proto 257
match-action drop
ip-tos 0x0 0x0
ip-version ipv4
src-ip 0.0.0.0
src-mask 0.0.0.0
src-port 65536
dest-ip 0.0.0.0
dest-mask 0.0.0.0
dest-port 445
ip-proto 257
match-action drop
ip-tos 0x0 0x0
Show Cable Filter Command
To display the configured information for all filter groups in the C4/c CMTS, use the following command:
show cable filter
An output similar to the following example will occur:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
564
Chapter 17: IP Packet Filters, Subscriber Management
Ip
TOS
V6-Flow
Grp Idx Prot Mask/Val Label
---- --- ---- -------- ------4
1 257
4
2 257
4
3 257
4
4 257
4
5 257
-
Source Dest
Port
Port
------ -----135
137
138
139
445
Action
-----drop
drop
drop
drop
drop
IP
Src/
Capture Matched
Type Dest
-------- ---------- ---- ---Enabled
0 ipv4 Enabled
54 ipv4 Enabled
16 ipv4 Enabled
3 ipv4 Enabled
3 ipv4 -
Address
--------------
To Enable Logging
Once packet logging is enabled it does not get sent to the log by default, the following two commands are used to enable
logging:
configure logging debug ip packet brief
configure logging debug ip packet detail
To disable logging, enter the following command:
clear logging debug
Show Operation Mode Command
The following command can be used to identify the current state of the IP Protocol operation mode, as regards to UDP and
TCP filtering:
show operation mode
An output similar to the following example will occur:
Enabled
Enabled
Enabled
Disabled
Enabled
Enabled
Disabled
Disabled
Disabled
Enabled
Disabled
Disabled
Disabled
Disabled
Disabled
Disabled
Enabled
Disabled
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
:
(dqossf10cms) Allow 1.0 CMs in DocsQosServiceFlowEntry
(adjrxpwrctl) Allow adjustment of rx power control by mod type
(enbudptcpfltr) Allow combining of Udp and Tcp messages in same filter <------(DSPeakTrafficRateTLV2516) Use old MULPI spec (TLV 25.16) for DS Peak Traf Rate instead of new spec (TLV 25.27)
(cpeNacksForceCmReset) Force CM reset upon receiving 3 consecutive CPE NACKs
(LBalDynUnbondUcast) Enable load balancing of new dynamic unbonded unicast US and DS flows for a multi-channel CM
(upDownTrapIfDescr) Allow linkUp/linkDown SNMP traps to include ifDescr
(ofdmSparingCleanup) CM on an OFDM channel will automatically reset after a DCAM failover/failback
(upstreamRngRspFreqLimit) Limit Modem's US range response to 42 MHz (pre-registration only)
(cmstatusoperational) Allow modem status at the CMTS to reach operational(8)
(USIngressNoiseMitigation) Upstream receiver settings designed to mitigate large ingressors
(docsis20test) DOCSIS 2.0 Testing
(showCmFormatCV) Force alternative output of "show cable modem"
(docsis10plus) Docsis 1.0+ support
(downstreamOverride) Downstream Frequency Override
(suppress-dcd) Supression of DCD messages
(virtualCm) Allow Virtual cable modems
(bpiHybrid) Allow upgraded DOCSIS 1.0 modems to operate using BPI+
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
565
Chapter 17: IP Packet Filters, Subscriber Management
Show Logging History Command
To display log output with logging enabled:
show logging history
An output containing information similar to the following occurs. (Note that this output has been significantly shortened.)
20:51:53 06 notc: CLI command:a:10.43.130.79:show running-config full verbose | include subm
20:52:41 01 debg: Debug:ip.packet.brief:(4/2 US-2) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:42 01 debg: Debug:ip.packet.brief:(4/2 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:42 01 debg: Debug:ip.packet.brief:(4/2 US-2) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:42 01 debg: Debug:ip.packet.brief:(4/2 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:42 01 debg: Debug:ip.packet.brief:(4/2 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:43 01 debg: Debug:ip.packet.brief:(4/2 US-1) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:43 01 debg: Debug:ip.packet.brief:(4/2 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:52:54 01 debg: Debug:ip.packet.brief:(4/2 US-0) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
< Additional lines of output displayed >
20:53:19 06 notc: CLI command:a:10.43.130.79:show cable filter
20:53:22 01 debg: Debug:ip.packet.brief:(4/3 US-0) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:23 01 debg: Debug:ip.packet.brief:(4/3 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:24 06 notc: CHMON: setting fan speed to level 11 (3137 RPM), previous level 10 (3078 RPM) - auto
20:53:24 01 debg: Debug:ip.packet.brief:(4/3 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:25 01 debg: Debug:ip.packet.brief:(4/3 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
220:53:22 01 debg: Debug:ip.packet.brief:(4/3 US-0) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:23 01 debg: Debug:ip.packet.brief:(4/3 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:24 06 notc: CHMON: setting fan speed to level 11 (3137 RPM), previous level 10 (3078 RPM) - auto
20:53:24 01 debg: Debug:ip.packet.brief:(4/3 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:25 01 debg: Debug:ip.packet.brief:(4/3 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=138, destport=138
20:53:26 01 debg: Debug:ip.packet.brief:(4/2 US-3) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Pkt Type: IPV4, sip=10.44.121.67, dip=10.44.121.95, ulp=UDP, tos=0, flowid=0, srcport=137, destport=137
20:53:27 01 debg: Debug:ip.packet.brief:(4/2 US-1) Smac: 0011.2513.e249, Dmac: ffff.ffff.ffff
Drop Packet By Flow Label or IP Version
Packets can be dropped by means of filtering on the following:
IPv6 flow label (v6-flow-label) in the range 0-1048575.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
566
Chapter 17: IP Packet Filters, Subscriber Management
IP version (ip-version) which can be ipv6, ipv4, or unknown.
IPv4 and IPv6 Drop/Accept Packet Command Examples
This section provides drop and accept examples pertaining to IPv4 and IPv6 filter group commands.
The following example command drops packets with an IPv4 source address (src-ip) of 10.119.30.255, and with an IPv4
source address mask (src-mask) of 255.255.255.0:
configure cable filter group 10 index 1 src-ip 10.119.30.255 src-mask 255.255.255.0 match-action
drop
The following example command accepts packets with an IPv4 destination address of 10.119.31.255, and with an IPv4
destination address mask of 255.255.255.0:
configure cable filter group 10 index 2 dest-ip 10.119.31.255 dest-mask 255.255.255.0 matchaction accept
The following example command drops packets with an IPv6 source address (v6-src-address) of
2001:db8:c426:c001:0:0:0:1011, and with an IPv6 source address prefix length (v6-src-pfxlen) of 128:
configure cable filter group 20 index 1 v6-src-address 2001:db8:c426:c001:0:0:0:1011 v6-srcpfxlen 128 match-action drop
The following example command accepts packets with an IPv6 destination address (v6-dest-address) of
2001:db8:c426:c001:0:0:0:1012 and with an IPv6 destination address prefix length (v6-dest-pfxlen) of 128:
configure cable filter group 20 index 2 v6-dest-address 2001:db8:c426:c001:0:0:0:1012 v6-destpfxlen 128 match-action accept
The following command example drops all IPv6 packets with a flow label of 10:
configure cable filter group 20 index 1 v6-flow-label 10 match-action drop
Drop Packet by IP Version
The following command example drops all IPv6 packets:
configure cable filter group 20 index 1 ip-version ipv6 match-action drop
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
567
Chapter 17: IP Packet Filters, Subscriber Management
Default IP Filters in the C4/c CMTS
This function configures the data packet logging operation that the CMTS performs when a match occurs on a packet.
Use the following command to enable/disable a specific IP filter to capture packets and send them to the capture buffer:
configure [no] cable filter group <group> index <index> log [parameter name <value>]
To disable packet capture on all filters, use the following command:
configure no cable filter log
This example drops packets with an IP: 10.119.30.255 with mask 255.255.255.0, but also logs data to the CMTS output:
configure cable filter group 10 index 1 log src-ip 10.119.30.255 src-mask 255.255.255.0 matchaction drop
The logging of captured packets to the CMTS output is turned on/off with the following commands:
configure [no] logging debug ip packet brief [slot < slot>]
The command above uses the brief option. It logs the interface on which the packet was received, including the direction,
if appropriate. It also logs the source of the capture, i.e., IP filter group/index, as well as the SIP, DIP, and protocol.
The second version of the command, which corresponds to the detail option, logs the contents of the packet, limited to the
length that the hardware supports in the capture buffer.
configure [no] logging debug ip packet detail [slot < slot>]
If neither brief nor detail log option is enabled, the captured packets information is still collected but discarded. The
captured buffer data is sent to the logging or syslog output of the CMTS.
To display the captured packets:
show logging history
Port Filters
Port filters perform IP packet header filtering on the source or destination port.
Port Value Ranges
The following port source and destination values apply:
UDP source port. Range is 0-65536.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
568
Chapter 17: IP Packet Filters, Subscriber Management
UDP destination port. Range is 0-65536.
The source and destination port fields of a filter can be given the value of 65536, which acts as a match-all or wildcard. If
the source port field of the filter is set to 65536, then any value in a source port field of the packets is considered a match.
Common Port Values
Some common port values are shown in the table below.
Table 74. Common Port Values
Port
Description
23
telnet
25
SMTP
67
bootpc
68
bootps
69
tftp
137
Microsoft SMB (NetBIOS Name Service)
138
Microsoft SMB (NetBIOS Datagram Service)
139
Microsoft SMB (NetBIOS Session Service)
206
Apple Ethertalk
2301
Compaq Insight Manager
65536
Any port
All ports
Listed in /etc/services on any UNIX system
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
569
Chapter 17: IP Packet Filters, Subscriber Management
Port Filter Drop Command Examples
The following are drop examples pertaining to source and destination port filter group commands.
A command example to filter drops UDP packets for a destination port of 50,000:
configure cable filter group 11 index 1 ip-proto 17 dest-port 50000 action drop
A command example to filter drops all TCP packets from a given source port to a given destination port:
configure cable filter group 20 index 2 ip-proto 6 src-port 2101 dest-port 10122 action drop
The filters created by the following two commands will cause the C4/c CMTS to drop all telnet packets:
configure cable filter group 10 index 1 src-port 23 match-action drop
configure cable filter group 10 index 2 dest-port 23 match-action drop
IP Protocol Filters
IP packet header filtering can be configured for IP protocols.
IP Source and Destination Filters
These filters are used to pass, drop, or log matching IPv4 or IPv6 source and destination addresses:
dest-ip
dest-mask
src-ip
src-mask
v6-dest-address
v6-dest-pfxlen
v6-src-address
v6-src-pfxlen
IPv4 destination address
IPv4 source address mask
IPv4 source address
IPv4 source address mask
IPv6 destination address
IPv6 destination address prefix length
IPv6 source address
IPv6 source address prefix length
IP Protocol Values
The match-all value for the IP protocol (ip-proto) field is 256. If the ip-proto field in the command is set to 256, then all IP
packet protocol values are considered a match.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
570
Chapter 17: IP Packet Filters, Subscriber Management
The value range for IP protocols is 0-257.
Common Protocol Values
Some common protocol values are provided in the table below.
Table 75. Common Protocol Values
IP Protocol
Description
1
ICMP
6
TCP
17
UDP
256
Any protocol
257
UDP and TCP (See note)
All protocols
Listed in /etc/protocols on any UNIX system
Note: If the operation mode is set to enbudptcpfltr (see UDP and TCP Filtering in Same Filter (page 572)), and the ipproto value is set to 257, then combined UDP and TCP filtering is enabled. If the operation mode enbudptcpfltr is reset,
then the ip-proto value cannot be set to 257 and combined UDP and TCP filtering is disabled.
IP Protocol Filter Command Examples
These commands provide drop examples pertaining to IP protocol Filter commands.
The following command example filter drops all ICMP packets:
configure cable filter group 20 index 1 ip-proto 1 match-action drop
The following command example filter drops all TCP packets originating at a specific source port and meant for a specific
destination port:
configure cable filter group 20 index 2 ip-proto 6 src-port mmm dest-port nnn action drop
Where: mmm and nnn are the numbers of the ports.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
571
Chapter 17: IP Packet Filters, Subscriber Management
The following command example filter drops all UDP packets meant for a given destination port:
configure cable filter group 20 index 3 ip-proto 17 dest-port nnn action drop
Where: nnn is the number of a port.
Text Description Parameter
Description — Beginning in Release 8.3, a text description can be added to an existing or configured subscriber
management filter group. Doing so will not reduce the number of indexes or filters allowable per group. If a filter group
has not been defined, you will receive an error message stating that a filter group does not exist.
configure cable filter group <groupID> description <text> [no]
Where:
— The subscriber management filter group number.
— A textual description of the filter group (up to 32 characters). The description text may be
optionally enclosed in quotes.
<groupID>
<text>
The [no] form of the command will remove just the description text.
To display the filter group description, use the following command:
show cable filter [group <number>] [index <index-number>] [verbose]
Note: If a description was not configured for a filter group, the delimiter "description" will be displayed with no
corresponding description text after it.
The [verbose] option will display the description in list form along with the other filter information.
UDP and TCP Filtering in Same Filter
To enable both UDP and TCP filtering requires the use of the configure
command examples:
operation mode
command. The following are
Note: UDP and TCP filtering is enabled by default.
To enable UDP and TCP filtering:
configure operation mode enbudptcpfltr
To disable both UDP and TCP filtering in the same filter:
configure operation mode enbudptcpfltr no
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
572
Chapter 17: IP Packet Filters, Subscriber Management
Type of Service and Match Action Filtering
IP packet filtering can also be configured based on the:
Type of Service (TOS)
Match action
TOS Filtering
The mask is entered against the value of the TOS byte in hexadecimal. The TOS byte is depicted as follows:
0
1
2
Precedence
3
4
5
D
T
R
6
7
Unused
The 0 equates to the Most Significant Bit and the 7 equates to the Least Significant Bit.
Precedence Bits — The three precedence bits have a value from 0 to 7 and are used to indicate the importance of a
datagram. The default is 0. The higher the binary number, the better the TOS as shown in the following table.
Table 76. Precedence Bits
Bits
TOS
111
Network Control
110
Internetwork Control
101
CRITIC/ECP
100
Flash Override
011
Flash
010
Immediate
001
Priority
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
573
Chapter 17: IP Packet Filters, Subscriber Management
Bits
TOS
000
Routine
Remaining Bits — Bits 3, 4, and 5 represent the following:
D (requests low delay)
T (requests high throughput)
R (requests high reliability)
Bits 6 and 7 are unused.
A drop or accept action can be configured for a packet when a match occurs.
TOS Filtering Command Example
The following TOS Filtering command example drops all priority packets:
configure cable filter group 20 index 1 ip-tos <mask> <value> match-action drop
Where: mask = Mask against TOS value. The byte must be in hex (0x0-0xFF)
value = the TOS value, byte in hex (0x0 - 0xFF)
Match Action Command Examples
The following command example accepts all packets that match the filter for IPv4:
configure cable filter group 20 index 2 ip-version ipv4 match-action accept
The following command example drops all packets that match the filter for IPv6:
configure cable filter group 20 index 3 ip-version ipv6 match-action drop
Effect of IP Packet Filtering / Subscriber Management on IP Address Limits
The IP Packet Filtering / Subscriber Management feature affects the maximum number of IP addresses behind a CM that
the C4/c CMTS can learn. The following are the guidelines to be followed when enabling or disabling this feature.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
574
Chapter 17: IP Packet Filters, Subscriber Management
Subscriber Management Off
If IP Packet Filtering / Subscriber Management is turned off, then a single CM can have the following maximums:
64 total CPE IPv6 addresses
32 total CPE IPv4 addresses
The user cannot reconfigure these limits if Subscriber Management is disabled. The show cable modem detail command
output will show "IPv4 Addr=32, IPv6 Addr=64". See a sample system output in the Show Logging History Command (page
566) section.
Subscriber Management On
If IP Packet Filtering / Subscriber Management is turned on, then a single CM can have the following default maximums:
16 total CPE IPv6 addresses
16 total CPE IPv4 addresses
The user can reconfigure these limits in the CLI or in the CM configuration file. To change the default maximums, use the
following commands:
For IPv6:
configure cable submgmt default v6-max-cpe <0-64>
For IPv4:
configure cable submgmt default max-cpe <0-32>
Per-Interface Configuration
Per-interface IP packet filtering configuration applies only to IPv4 packets. It can be used to set packet filters for modems
and CPEs based on the IP address or VRF that references the IPv4 address space for the modem or device.
Default Filter Groups
When a cable modem or CPE is assigned an IPv4 address, the C4/c CMTS determines default IP filter groups in the
following order:
1. First, the modem configuration file can have TLVs for that modem and its CPE device types that instruct the C4/c CMTS
to set up IP packet filtering.
2. If these TLVs are not present, then the C4/c CMTS checks to see if per-interface IP packet filters have been configured.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
575
Chapter 17: IP Packet Filters, Subscriber Management
3. Finally, if there are no TLV or per-interface IP packet filters configured, the system-wide parameters specifying default
filter groups are applied.
Multiple Subinterface Environment
In a multiple subinterface environment, modems on each subinterface could be assigned modem configuration files that
specify filter groups that are specific for that subinterface.
This capability exists today in any system compliant with DOCSIS® 1.1. The provisioning system determines on which
subinterface each modem resides, a necessary step for assigning the IP address. It then uses the modem to which the CPE
is attached to determine the CPE’s subinterface.
The ability to assign default IP filter groups based on the subinterface and derived from the IP address of the CM or CPE is
an enhancement of the per-subinterface IP packet filtering feature. If per-subinterface filter groups have been assigned,
they are used in place of the system-wide default filter groups. However, the per-subinterface filter groups are not used if
filter groups are assigned in the modem configuration file.
For CPEs, the assignment of these new subinterface level filter group parameters would take place when an IP address is
assigned by DHCP, in addition to when the CPE is learned, since CPE assignment to a subinterface would take place when it
gets its IP address. If a CPE doesn't have an IP address when it is first learned (i.e., it is doing DHCP), it initially uses the CPE
filters associated with the modem's subinterface. Once it obtains an IP address, the CPE's filter group will change if the CPE
is in a different subinterface than the modem and that subinterface has default values that are different from the
modem’s.
Recommendations for Using Per-Subinterface Filter Groups
blah blah
Default Filter CLI Examples
The following CLI commands assign default filters for a subinterface:
configure
configure
configure
configure
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-mac
cable-mac
cable-mac
cable-mac
1.0
1.0
1.0
1.0
cable
cable
cable
cable
submgmt
submgmt
submgmt
submgmt
default
default
default
default
filter-group
filter-group
filter-group
filter-group
cm downstream <group>
cm upstream <group>
host downstream <group>
host upstream <group>
C4® CMTS Release 8.3 User Guide
576
Chapter 17: IP Packet Filters, Subscriber Management
Default Subscriber Management Settings
Default filter groups and other subscriber management defaults are used when no groups or other specific subscriber
management parameters are specified in the cable modem config file. Defaults apply to the parameters unless otherwise
specified in the cable modem config file.
Subscriber management control must be enabled for default parameters to have an effect. Once enabled, filters are
applied to modems when they register or re-register. Modems registered prior to default parameter configuration will not
be affected.
Enable/Disable CLI Example
Use the following command to enable or disable subscriber management control:
configure [no] cable submgmt default active
Set Default CLI Examples
Use the following command form to set default values for registering modems:
configure cable submgmt default <parameter>
Example:
configure cable submgmt default ?
active
filter-group
learnable
max-cpe
v6-max-cpe
-
CPE Control for Subscriber Management Filtering
Configure filter groups
Filter group provisioning is learned from CM/eSAFE device
Provision the maximum number of IP addresses behind a CM.
Provision the maximum number of IPv6 addresses behind a CM
Note: Parameters referring to IPv6 in the CLI syntax specifically refer to version 6. For example, "v6-max-cpe". IP related
parameters that do not specifically refer to IPv6 are IPv4. For example, "max-cpe" refers to IPv4 addresses.
Example:
configure
configure
configure
configure
configure
cable
cable
cable
cable
cable
submgmt
submgmt
submgmt
submgmt
submgmt
default
default
default
default
default
active
filter-group host upstream 10
filter-group host downstream 10
learnable
max-cpe 16
Where: the range of max-cpe is 0-32, and 0 means "Do not allow any."
configure cable submgmt default v6-max-cpe 16
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
577
Chapter 17: IP Packet Filters, Subscriber Management
Where: the range of v6-max-cpe is 0-64, and 0 means "Do not allow any."
C4 CMTS Debug IP Packet Capture
The IP Packet Capture feature allows the user to select an existing IP filter and add an option to capture information about
incoming frames that match this particular filter. If the appropriate IP filter is not currently in the filter group, then a new
one can be added which will capture the desired packets. If the first filter in a group satisfies the matching conditions, then
it is the only one to match and the CMTS does not search any further. Functionality is identical for both US and DS IP filters.
Exercise caution when adding new IP filters: they may affect the actions of existing IP filters. When a new IP filter with a
lower index value is added to the group, it has priority over the filters with a higher index value. Therefore, whenever a
packet matches the new filter, the action of that filter will override the actions of those behind it. Likewise, if a filter is
added to the end of the list, i.e. it has a higher index value in a group, it can only match and take action if none of the filters
above it find a match.
Any number of IP filters can be set to capture information about the frames they are matching. All of the frame
information from all of the IP filters set to collect information is aggregated in the capture buffer. If too many IP filters are
enabled to capture frame data and there is heavy traffic load, some of the capture data is discarded.
The capturing of frame data occurs whenever an IP filter matches and its debug capture flag is set. This is true regardless of
how the IP filter’s Drop/Pass action is set.
The information captured by hardware and stored in a First In First Out (FIFO) buffer for each packet is called a capture
entry. A capture entry contains the following:
A capture entry header containing some information specific to this packet
Up to the first 100 Bytes of the captured packet.
This capture entry is read out of the FIFO by software so it can be parsed and reformatted to display as much or as little of
the gathered information as desired. Capturing the first 100 bytes of a packet provides sufficient information about
sources, destinations, and protocols. The capture entry header reveals where the match physically occurred, and can be
used to reference count information associated with the IP filter and group that matched. It also provides trigger function
type, channel ID, and other pertinent information.
There is no software limit to the number of IP filters that can be enabled for packet capture. All IP filters could be triggering
packet captures. There is however a practical limit as to how many flows can be monitored and how much traffic can be
passed from the hardware up to the software. This limit is difficult to define since it is based on several variables.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
578
Chapter 17: IP Packet Filters, Subscriber Management
The Debug IP Packet Capture utility has been designed to be non-interfering. Though it is possible to configure IP filters
that capture huge numbers of packets, the hardware and software that gather the packets only allow as many through as
can currently be processed. System performance and throughput will not suffer even if IP filters capture too many packets.
If a filter matches so many packets that the hardware and software cannot process them, then these packets will be
dropped from the log. The log keeps a counter that shows how many packets were dropped from the log. This does not
mean that the packets were prevented from reaching their destinations; it simply means that these packet captures were
not included in the log.
Filter Logging in the C4/c CMTS
This function configures the data packet logging operation that the CMTS performs when a match occurs on a packet.
Use the following command to enable/disable a specific IP filter to capture packets and send them to the capture buffer:
configure [no] cable filter group <group> index <index> log [parameter name <value>]
To disable packet capture on all filters, use the following command:
configure no cable filter log
This example drops packets with an IP: 10.119.30.255 with mask 255.255.255.0, but also logs data to the CMTS output:
configure cable filter group 10 index 1 log src-ip 10.119.30.255 src-mask 255.255.255.0 matchaction drop
The logging of captured packets to the CMTS output is turned on/off with the following commands:
configure [no] logging debug ip packet brief [slot < slot>]
The command above uses the brief option. It logs the interface on which the packet was received, including the direction,
if appropriate. It also logs the source of the capture, i.e., IP filter group/index, as well as the SIP, DIP, and protocol.
The second version of the command, which corresponds to the detail option, logs the contents of the packet, limited to the
length that the hardware supports in the capture buffer.
configure [no] logging debug ip packet detail [slot < slot>]
If neither brief nor detail log option is enabled, the captured packets information is still collected but discarded. The
captured buffer data is sent to the logging or syslog output of the CMTS.
To display the captured packets:
show logging history
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
579
Chapter 17: IP Packet Filters, Subscriber Management
IP Filter Related CLI Commands
The CLI commands associated with filtering are provided in the table below. Additional information is located in Command
Line Descriptions.
Table 77. Filter Group Related CLI Commands
Purpose
Command
To clear the filter match counters
clear cable filter group <group> [index
<index>] counters
To configure the IP packet filtering parameters for the specified
packet filter
configure cable filter group <group number>
index <index number> [parameter name <value>]
[no]
To configure the IP Type of Service (TOS) settings, and (optionally)
the IP packet filtering parameters for the specified packet filter.
configure cable filter group <group number>
index <index number> ip-tos <mask> <tos value>
[parameter name <value>]
To configure the IP Protocol operation mode to enable both UDP
and TCP filtering in the same filter.
The [no] option disables the IP Protocol operation mode.
configure operation mode <operation mode> [no]
To provision the subscriber management for the specified filter
group.
The [no] option deletes a specific filter group.
configure interface cable-mac <mac> cable
submgmt default filter-group <{cm | host | cpe
| mta | ps | stb }> <{upstream | downstream}>
<group ID> [no]
Note: The specific operation mode that is applicable is
enbudptcpfltr.
For more information, also see Filter Groups Based on
Device Class (page 651).
To configure the data packet logging operation that the system
performs when a match occurs on a packet.
The [no] option disables logging of the packet filter(s)
configure cable filter group <group> index
<index> log [parameter name <value>] [no]
To display the cable IP filter information
show cable filter [group <group number>
[verbose] [clearmatches]
To display the captured packet’s history
show logging history
To display the IP Protocol operation mode status
show operation mode
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
580
Chapter 17: IP Packet Filters, Subscriber Management
Purpose
Command
This command displays general information on functionality and
display options for all cable modems registered or attempting to
register.
show cable modem
IP Packet Filtering Configuration Example
This scenario assumes that the CAM is in-service and that its RF parameters have been set. Use the following sequence of
commands (or script) as an example of filter group configuration:
The series of commands below creates a filter designed to drop netbios traffic and allow all other traffic from a CPE.
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
configure
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
cable
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
submgmt default filter-group cm downstream 1
submgmt default filter-group cm upstream 2
submgmt default filter-group cpe downstream 3
submgmt default filter-group cpe upstream 4
submgmt default active
filter group 4 index 1 ip-version ipv4
filter group 4 index 1 src-port 65536
filter group 4 index 1 dest-port 135
filter group 4 index 1 ip-proto 257
filter group 4 index 1 match-action drop
filter group 4 index 1 ip-tos 0x0 0x0
filter group 4 index 2 ip-version ipv4
filter group 4 index 2 src-port 65536
filter group 4 index 2 dest-port 137
filter group 4 index 2 ip-proto 257
filter group 4 index 2 match-action drop
filter group 4 index 2 ip-tos 0x0 0x0
filter group 4 index 3 ip-version ipv4
filter group 4 index 3 src-port 65536
filter group 4 index 3 dest-port 138
filter group 4 index 3 ip-proto 257
filter group 4 index 3 match-action drop
filter group 4 index 3 ip-tos 0x0 0x0
filter group 4 index 4 ip-version ipv4
filter group 4 index 4 src-port 65536
filter group 4 index 4 dest-port 139
filter group 4 index 4 ip-proto 257
filter group 4 index 4 match-action drop
filter group 4 index 4 ip-tos 0x0 0x0
filter group 4 index 5 ip-version ipv4
filter group 4 index 5 src-port 65536
C4® CMTS Release 8.3 User Guide
581
Chapter 17: IP Packet Filters, Subscriber Management
configure
configure
configure
configure
cable
cable
cable
cable
filter
filter
filter
filter
group
group
group
group
4
4
4
4
index
index
index
index
5
5
5
5
dest-port 445
ip-proto 257
match-action drop
ip-tos 0x0 0x0
Confirm your results with the following command:
show cable filter group 4
Sample system response:
Ip
TOS
V6-Flow
Grp Idx Prot Mask/Val Label
---- --- ---- -------- ------4
1 257 00/00
4
2 257 00/00
4
3 257 00/00
4
4 257 00/00
4
5 257 00/00
-
Source Dest
Port
Port
------ -----135
137
138
139
445
Action
-----drop
drop
drop
drop
drop
Capture Matched
-------- ---------Disabled
0
Disabled
0
Disabled
0
Disabled
0
Disabled
0
IP
Type
---ipv4
ipv4
ipv4
ipv4
ipv4
Src/
Dest
----
Address
--------------
The following command displays the settings for filter index 1 of group 2 in verbose mode:
show cable filter group 2 index 1 verbose
An example of the system response:
IP Filter Group For Group 2 Index 1
IP Type:
ipv4
Source address:
-Source mask:
-Destination address:
-Destination mask:
-IP Protocol:
257
TOS:
00
TOS Mask:
00
Action:
drop
Source Port:
-Destination Port:
135
Capture:
Disabled
Number of times rule was matched: 0
Last Cleared on:
Mon Dec 3 12:27:19 2012
Use the following command to display which filters are being applied to the CM with a given MAC address and to the CPEs
behind it:
show cable modem detail CM 001d.cf1e.492c
A sample of the system response:
12/0/9-1/2/0
CM 001d.cf1e.492c (Arris) D3.0 State=Operational D1.1/atdma PrimSID=8198 FiberNode= FN1
Cable-Mac= 101, mCMsg = 1
mDSsg = 1
mUSsg = 1 RCP_ID= 0x0010001005 RCC_Stat= 3, RCS=0x01000005 TCS=0x01000005
Timing Offset=11776
Rec Power= 0.00 dBmV Proto-Throttle=Normal dsPartialServMask=0x00000000 usPartialServMask=0x00000000
Uptime= 0 days 4:39:48 IPv4=10.129.31.247
reconstructed cfg=cw_basic_30.bin FreqRng=STD
LB Policy=0 LB Group=855640064
Filter-Group CM-Down:0
CM-Up:0
Privacy=Disabled
MDF Capability= GMAC Promiscuous(2) MDF Mode= MDF Enabled(1)
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
582
Chapter 17: IP Packet Filters, Subscriber Management
u/d
SFID
SID State Sched
Tmin
uB
55
8198 Activ BE
0
dB
56
7 Activ
0
L2VPN per CM: (Disabled)
Current CPE=0, IPv4 Addr=0, IPv6 Addr=0
Tmax
0
0
DFrms
0
0
DBytes
0
0
CRC
0
HCS
0
Slot/Ports
1/2/0-3
12/0/8-11
Max CPE=16, IPv4 Addr=32, IPv6 Addr=64
Upstream Drop Classifiers
The CM can perform Upstream IP protocol filtering (as defined in the DOCS-CABLE-DEVICE-MIB) using either IP filters or
Upstream Drop Classifiers. DOCSIS 3.0 expanded the concept of classifiers to encompass the filtering of upstream traffic in
CM. The legacy IP filtering in the CM did not support IPv6 filtering. An Upstream Drop Classifier is a Classifier provisioned in
the CM configuration file to filter upstream traffic that is either IPv4 or IPv6. If a packet matches the specified packet
matching criteria of an Upstream Drop Classifier, it is then dropped.
The mandatory part of Upstream Drop Classifiers is supported, specifically the enabling and disabling by the C4/c CMTS of
statically provisioned Upstream Drop Classifiers in the CM configuration file at registration time.
Note: The C4/c CMTS does not support sending of the Upstream Drop Classifiers configuration to the CM based on the
Upstream Drop Classifiers Group IDs sent to the system during registration. Also, the C4/c CMTS does not support
dynamically modifying Upstream Drop Classifiers on the CM via DSC messages.
Provisioning
When Upstream Drop Classifiers are provisioned in the CM configuration file, in order for the CM to use them, the C4/c
CMTS must also be configured to allow their use.
If the capability is disabled on the C4/c CMTS, during registration the C4/c CMTS will signal to the CM that Upstream Drop
Classifiers cannot be used, and legacy IP filters will be used instead. The CM can only use legacy IP filters or Upstream Drop
Classifiers, but not both at the same time to filter IPv4 traffic only.
US Drop Classifier Commands
The following command is used to enable/disable Upstream Drop Classifier operation:
configure interface cable-mac <mac-id> [no] cable upstream-drop-classifiers enable
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
583
Chapter 17: IP Packet Filters, Subscriber Management
The following show command can be used to determine whether Upstream Drop Classifier operation is enabled or
disabled:
show interface cable-mac 1 detail | include Upstream Drop Classifiers
The following is an example of the output:
Upstream Drop Classifiers:
disabled
The following show command example can also be used to view the status:
show running-config verbose | include upstream-drop-classifiers enable
An output similar to the following example occurs:
configure
configure
configure
configure
interface
interface
interface
interface
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
cable-mac
cable-mac
cable-mac
cable-mac
1
2
3
4
cable
cable
cable
cable
upstream-drop-classifiers
upstream-drop-classifiers
upstream-drop-classifiers
upstream-drop-classifiers
enable
enable
enable
enable
C4® CMTS Release 8.3 User Guide
584
Chapter 18
Baseline Privacy Interface (BPI)
Baseline Privacy Overview ............................................................... 585
Baseline Privacy Setup ..................................................................... 588
Provisioning X.509 Certificates......................................................... 599
Baseline Privacy Debugging ............................................................. 601
Baseline Privacy Trap Codes ............................................................. 604
Baseline Privacy: CLI Commands ...................................................... 608
BPI Hybrid Mode Operation ............................................................. 611
BPI+ Enforce ..................................................................................... 613
Baseline Privacy Overview
Baseline Privacy (BP) provides cable modem users with data privacy across the cable network equal to or better than that
provided by dedicated line network services. It does this by encrypting traffic flows on the RF link between the CM and
C4/c CMTS Baseline Privacy also provides cable operators with protection from theft of data services.
Baseline Privacy Plus Interface (BPI+) is an extension of the Baseline Privacy Interface (BPI); it further strengthens the BP
specification by adding cable modem authentication through the use of X.509 digital certificates. BPI+ is entirely backward
compatible with the earlier BPI specification. The Baseline Privacy portion of the DOCSIS CMTS is compatible with cable
modems operating in either BPI or BPI+ mode.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
585
Chapter 18: Baseline Privacy Interface (BPI)
Further information can be obtained from CableLabs® in the latest versions of the DOCSIS Baseline Privacy and Baseline
Privacy Plus Interface specifications.
BPI Operations
Baseline Privacy is comprised of two separate but interrelated protocols. The first is Baseline Privacy Key Management
(BPKM), the second is the packet data encryption on the RF link.
Baseline Privacy Key Management (BPKM)
The CM and C4/c CMTS use the BPKM protocol to determine authorization status and transfer of traffic encrypted data.
Through this key management protocol, the CM and C4/c CMTS synchronize keying information. BPKM follows a
client/server model where the CM, the client, requests encryption data and the C4/c CMTS, the server, responds to those
requests. BPKM uses DOCSIS MAC Management messaging in the request/reply operations of the BPKM protocol. Baseline
Privacy uses public-key cryptography to establish symmetric traffic keys between the CM and C4/c CMTS.
Packet Data Encryption
Packet data encryption is an extended service within the DOCSIS® MAC sublayer. When encrypting packet data, only the
frame’s packet data is encrypted; the frame’s header is not encrypted. To indicate the proper encryption/decryption key to
use, a special Baseline Privacy Extended Header is included in the MAC frame header. This special extended header
indicates encryption information related to the current MAC frame. Currently the C4/c CMTS supports 56-bit DES
operating in cipher block chaining (CBC) mode.
Note: To reduce confusion in MIB tables and the Baseline Privacy Specification, a Security Association ID (SAId) can be
thought of as the key ID for a traffic flow. It is just a number and should not be confused with the SID which is the service
ID of an upstream service flow.
Baseline Privacy Operational Overview
The operation between the CM and C4/c CMTS is conducted in three main steps:
Registration
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
586
Chapter 18: Baseline Privacy Interface (BPI)
Initialization
Reauthorization and rekeying.
Registration
At registration, the modem receives operational parameters from the CM’s configuration file. The C4/c CMTS verifies that
these parameters, if present in the CM’s registration request message, are in range.
There is one specific message TLV, type 17, which contains the Baseline Privacy operational parameters. The progression of
registration is the same for BPI and BPI+, but BPI+ has different requirements.
Caution: BPI operation requires ALL type 17 BPI parameters to exist and be within range for registration to complete and
accept the BPI portion of registration.
Note: BPI+ is much less restrictive: some, all, or no type 17 parameters need to exist for the BPI portion of registration to
complete. For BPI+ registration, any values that are not specifically defined in the configuration file are defaulted to the
values defined in the BPI+ Specification, Appendix A, in the Recommended Operational Ranges for BPI Configuration
Parameters table.
Initialization
After registration is complete, and Baseline Privacy is enabled, the second operational step of Baseline Privacy initialization
begins. It begins by authorizing the CM to use specific flows and is then followed by the transferring of traffic key
information for each specific flow.
BPI+ performs the same BPKM sequence as BPI with the addition of an initial digital certificate information message which
is used in modem authentication.
A successful initialization sequence proceeds as follows:
1. The CM authorizes with the C4/c CMTS through the use of BPKM authorization messages.
The first message that a CM sends is an authentication information message to the C4/c CMTS. (BPI+ only)
The second message is the Authorization Request.
The third message is the Authorization Reply from the C4/c CMTS.
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
587
Chapter 18: Baseline Privacy Interface (BPI)
2. The CM is granted traffic keys through the use of Traffic Encryption Key (TEK) BPKM messages.
The first message is the Key Request message.
The second message is the Key Reply message.
Reauthorization and Rekeying
The third operational step of reauthorization and rekeying is accomplished at predetermined lifetimes using the messages
in the respective sequence above.
Baseline Privacy Setup
A MIB browser or CLI commands may be used to directly configure BPI parameters. Since there are many different MIB
browsers, only the CLI commands are described.
Note: The CLI commands shown in this chapter that have a no parameter reset other parameters to their default values
when the no parameter is used.
This section describes Baseline Privacy basic setup procedures. BPI basic configuration is divided into four main topics:
1. Initial CER Base Table Setup
2. Configuration files
3. Multicast
4. Digital certificates
Initial CER Base Table Setup
(UCAM) Use the following command form for a MAC ID:
show interface cable-mac <mac> cable privacy base
Example:
show interface cable-mac 1 cable privacy base
The following sample output from this command shows the defaults:
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
588
Chapter 18: Baseline Privacy Interface (BPI)
Cable Privacy Base for cable-mac 1
---------------------------------------------DefaultAuthLifetime
: 604800
DefaultTEKLifetime
: 43200
DefaultSelfSignedManufCertTrust : Untrusted
CertValidityPeriods
: FALSE
BPI Mandatory
: none
docsBpi2CmtsAuthentInfos
: 6
AuthRequests
: 18
AuthReplies
: 18
AuthRejects
: 0
AuthInvalids
: 0
SAMapRequests
: 0
SAMapReplies
: 0
SAMapRejects
: 0
Default Auth Lifetime
The value of this object is the default lifetime, in seconds, that the C4/c CMTS assigns to an initial cable modem’s
authorization key:
Recommended range:
86,400-6,048,000
Default (per DOCSIS®):604,800
The default value is acceptable for normal operation. Using less than the minimum recommended value can degrade
system performance.
(UCAM) Use the following command to configure DefaultAuthLifetime.
configure interface cable-mac <cm-id> cable privacy kek life-time <seconds> [no]
Example:
configure interface cable-mac 1 cable privacy kek life-time 604800
Default TEK Lifetime
The value of this object is the default lifetime, in seconds, that the C4/c CMTS assigns to an initial cable modem’s traffic key
(TEK):
Recommended range:
1,800-604,800
Default (per DOCSIS®):43,200
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
589
Chapter 18: Baseline Privacy Interface (BPI)
The default value is acceptable for normal operation. Using less than the minimum recommended value can degrade
system performance.
Caution: The TEK lifetime must be more than twice as large as the largest TEK CM grace time to prevent denied CM
registration.
(UCAM) Use the following command to configure the default TEK lifetime:
configure interface cable-mac <cm-id> cable privacy tek life-time <seconds> [no]
Example:
configure interface cable-mac 1 cable privacy tek life-time 43000
Default SelfSigned ManufCertTrust (BPI+Certificates)
This object determines the default trust of self-signed manufacturer certificate entries, contained in
docsBpi2CmtsCACertTable, created after setting the object:
Valid values:
Default:
trusted|untrusted
untrusted
Caution: Self-signed certificates are a security risk. As a general rule, do not trust them.
Note: Valid self-signed certificates are marked trusted or untrusted depending on this MIB variable. If the default trust
value is set to untrusted and CA Certificates are learned, then these CA Certificates are considered untrusted and stored.
This is a one-time determination which is never re-evaluated unless the certificate is deleted and relearned.
Setting the trust value for default self-signed back to trusted does not automatically change the trust of previously learned
self-signed CA Certificates. To change the trust of previously learned self-signed CA Certificates, you must manually edit
the current certificate’s trust state or delete the certificate entry so that the certificate will be relearned.
(UCAM) Use the following command to configure the DefaultSelfSignedManufCertTrust:
configure interface cable-mac <mac> cable privacy default-cert-trust <value> [no]
Example:
configure interface cable-mac 1 cable privacy default-cert-trust untrusted
STANDARD Revision 1.0
© 2016 ARRIS Enterprises LLC. All Rights Reserved.
C4® CMTS Release 8.3 User Guide
590
Chapter 18: Baseline Privacy Interface (BPI)
Drop Invalid CA Certificates
The user may find through inspection of the CA Certificate MIB table, untrusted and/or invalid (bad) certificates.
Although these bad certificates are stored (by default) in accordance with the Baseline Privacy DOCSIS specification, there
is no adverse effect with leaving these bad certificates out of the CA Certificate MIB table. On the other hand, if there are a
large number of these bad certificates in the CA Certificate MIB table, their presence in the table can prevent valid
certificates from being put into the table, which can block good modems from completing BPI+ authentication properly.
Previously, to remove these deficient entries, a time consuming manual maintenance procedure needed to be performed.
In this case, using the "Drop Invalid CA Certificates" feature, the learning of bad CA certificate entries can be prevented
eliminating the necessity of customer maintenance.
Feature Objectives — When this feature is enabled:
The drop operation only works on learned CA certificates during the period of modem BPI+ initialization.
The drop operation only applies to newly learned certificates, not existing certificates already stored in the CA
Certificate MIB table.
The provisioning of valid, or bad certificates can still be performed manually.
Possible issues that can be alleviated by this feature are:
Modems stuck in a BPI init (some cases) identified in a log entry, as follows:
No certificates found to chain to CM certificate. CM Certificate invalid.
Greater than 100 entries in the CA Certificate MIB table identified in a log entry, as follows:
Cannot store CA Certificate, mib index overflow. Recover CA Certificate MIB entries.
If any of these conditions currently exist in the CA Certificate MIB table, this feature can be enabled and the bad
certificates can be removed ensuring no future recu
