Page 1
C4® CMTS Release 8.3 User Guide STANDARD Revision 1.0 November 2016...
Page 2
“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.
Page 3
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.
Page 5
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.
Page 6
Table 1. Revision History Revision Date Reason for Change Rel. 8.3 Preliminary, Issue 1.0 August 2015 Meet Field Soak Ready (FSR) requirements. Rel. 8.3 Standard, Issue 1.0 November 2016 Reissued for General Availability.
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 ..........................
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...
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.
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.
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.
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 C4® CMTS Release 8.3 User Guide...
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 ...
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.
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...
Page 56
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).
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.
Page 58
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.
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:...
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.
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.
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).
Page 67
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.
Page 68
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.
Page 70
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.
(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.
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 ...
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.
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.
Slot 19 Slot 17 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.
Start-up voltage range 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.
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 term -5 to +55ºC Long term: +5 to +40ºC...
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.
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 MHz...
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) ...
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 ...
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.
Page 88
3,348 Maximum per 16D/XD CAM 26,640 BHCA per upstream channel Maximum per 24U CAM (C4 CMTS only) 16,500 Simultaneous half-calls/downstream channel Simultaneous half-calls/upstream channel Connections per second per chassis Call load performance is based on the following assumptions: Lines per subscriber ...
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 ...
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.
Page 93
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.
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.
Installation involves mounting the unit in a rack, populating slots with client 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.
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.
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.
Page 98
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.
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.
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...
Page 101
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.
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 C4® CMTS Release 8.3 User Guide...
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).
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 ...
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 ...
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 ...
Page 107
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...
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.
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.
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.
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.
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.
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.
Page 114
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 ...
Page 115
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.
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.
Page 117
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...
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.
Page 119
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.
Page 120
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.
Page 121
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.
Page 122
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.
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.
Page 124
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.
Page 140
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.
Page 142
Slot 19 Slot 17 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.
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.
Page 156
(+) 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.
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 ...
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.
Page 174
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 C4®...
Page 185
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>...
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>...
Page 187
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.
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.
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. ...
Page 191
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.
Page 192
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.
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.
Page 199
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 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.
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.
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.
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 Module- Crossover Connector (Part Number 722891). The crossover connection provides the RCM-to-RCM inter-card data transport. These are the important operating...
Page 215
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.
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.
Page 231
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.
Page 234
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.
Page 239
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.
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.
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 ...
Page 252
Chapter 8: Downstream Cable Access Modules (DCAMs) 2. FTP both files off of the C4/C4c CMTS. 3. Edit the file to reflect the desired 32D configuration: new_32D_prov.cfg 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.
Page 254
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>...
Page 266
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 F- connector).
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.
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.
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.
Page 324
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 C4® CMTS Release 8.3 User Guide...
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.
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.
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.
Page 329
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.
Page 330
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: "1. Install Cards, Rear PICs, Filler Panels, PCMs, and Fans (page 331) "2. Set Up Console Cable (page 332) "3.
(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.
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.
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.
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.
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.
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.
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...
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...
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.
Page 342
Chapter 11: Basic Bring-up Procedure for the C4 CMTS * 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 output: show interface cable-mac 1 show interface cable-mac 1 brief...
Page 345
Chapter 11: Basic Bring-up Procedure for the C4 CMTS 14/5 351000000 Capable 14/6 357000000 Capable For a more detailed report, use the command: show cable rcc-status verbose show cable rcc-status verbose Cable Stat -mac RCP-id ChanSetId RCC-Status 0010000004 0x1000002 Valid...
Page 346
Chapter 11: Basic Bring-up Procedure for the C4 CMTS Total 100% BigMac Slot 14 Total 100% ---------------------------------------------------------------- ----- --------- ---------------------------------------------------------------- ----- --------- Total 100% For the status of the cable modems, enter: show cable modem An example of the show cable modem output:...
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.
Page 349
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.
Page 350
Chapter 11: Basic Bring-up Procedure for the C4 CMTS An example of the output: Dist/ IPv6 Route Dest / mask Act PSt Next Hop Metric Protocol Interface ========================= === === ============================== ======= ========= ============= ::/0 Yes IS 2001:db8:C408:1700::1 netmgmt gigE 17/0.0...
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 ...
Page 385
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 spare- group.
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.
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.
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.
Page 389
MD-CM-SGs. In this case the MD-US-SG is said to be a part of multiple MD-CM- SGs. MAC Domain The determination of the MD-US-SG by the C4/c CMTS during a CM initialization is an Upstream Service important part of identifying the MD-CM-SG of a CM. MD-US-SGs are calculated (as read-...
Page 390
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.
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.
Page 392
Use the [no] option to disable the signaling of configure interface cable-mac 3 cable cm-status enabled the CM-Status Event reporting mechanism, configure interface cable-mac <mac> cable mcast-fwd-by-dsid This command enables the C4/c CMTS to use IP [no] Multicast DSID-based Forwarding (MDF) to Example command: cable modems in the MAC domain.
Page 394
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.
Page 399
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. configure interface cable-downstream <slot>/<connector>/<dport> This command can be used to assign a cable channel-id <int>...
Page 400
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.
Page 403
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...
Page 404
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>...
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 ...
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.
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.
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.
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.
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.
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.
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.
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.
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>...
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.
(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).
Page 436
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.
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.
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.
Page 439
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 C4®...
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.
Page 442
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.
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 ...
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.
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.
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.
Page 449
Configure LAG <0-9> to respond to incoming messaging (passive). The default mode is active. configure interface link-aggregate <0-9> lacp timeout Define rate at which the C4/c CMTS expects to <fast|slow> [no] receive LACP messages: Slow is one message every 30 seconds, with a timeout of 90 seconds.
Page 450
<rcm slot>/<rcm port> Add or remove an NSI port to/from a LAG. The RCM link-aggregate <lag-number> slots are 17 and 18 in the C4/c CMTS chassis. configure interface gigabitEthernet <rcm slot>/<rcm port> link-aggregate [<lag-number>] [no] If no LAG exists when this command is entered, then a LAG with that lag-number is internally created with default values.
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).
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.
Page 459
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.
Page 460
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.
Page 462
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.
Page 464
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 ...
Page 465
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: ...
Page 466
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.
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.
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.
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.
Page 476
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.
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 ...
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.
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.
Page 481
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,...
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.
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.
Page 485
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.
Page 492
(LSPs) can remain in a router’s database without being refreshed. configure router isis metric-style <narrow | transition | wide> Configures the type of metric the C4/c CMTS will generate or accept. configure router isis net [no] Configures an IS-IS network entity title (NET).
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.
(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.
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.
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. ...
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.
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.
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.
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.
Page 511
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.
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.
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.
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: ...
Page 515
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.
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.
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...
Page 528
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.
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.
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.
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).
Page 538
[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).
Page 539
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).
Page 540
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...
Page 542
Where: int 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 C4® CMTS Release 8.3 User Guide...
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.
Page 546
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.
Page 549
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 is used to overwrite the six Differentiated Services...
Page 550
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.
Page 551
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.
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. In- band Management (also called SCM access) is enabled by the command. configure ip scm access Policies are applied to all IPv4 protocol packets.
Page 554
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.
Page 555
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.
Page 556
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.
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.
Page 562
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 ...
Page 563
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.
Page 564
4 index 5 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...
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 <...
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...
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 C4®...
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.
Page 582
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...
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.
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.
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.
Page 587
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.
Page 589
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...
Setting this object to TRUE causes all chained and root certificates in the chain to have their validity periods checked against the current time of day, when the C4/c CMTS receives an Authorization Request or authentication information from the CM. A FALSE setting causes all certificates in the chain not to have their validity periods checked against the...
(page 599). docsBpi2CmtsAuthCmLifetime The value of this object is the lifetime in seconds that the C4/c CMTS assigns to an authorization key for this CM. The no value of this command sets the value to default: 604800. (UCAM) Use the following command to set the authorization key lifetime: configure interface cable-mac <mac>...
1 cable privacy kek-cm-reset 1122.3344.5566 send-auth-invalid docsBpi2CmtsTEKLifetime (UCAM) The value of this object is the lifetime, in seconds, the C4/c CMTS assigns to keys for the respective TEK. The no value of this command defaults to 43200.
ASCII format. 1. FTP to the C4/c CMTS. 2. Copy the CA certificates to the certs directory on the C4/c CMTS flash disk by issuing the following CLI command: copy cacert-config <path/filename>...
Page 598
Use this procedure to export provisioned CM certificate entries from the docsBpi2CmtsProvisionedCmCertEntry MIB table. The exported file contains all the certificates in this table in ASCII format. 1. Copy the CM certificates to the certs directory on the C4/c CMTS flash disk by issuing the following CLI command: copy provcmcert-config <path/filename>...
MIB browser or CLI command. If an authorization request is received and a CM Certificate identical to the CM certificate received from the CM has been provisioned for that MAC address, the C4/c CMTS disregards the CM certificate provided in the auth request and use the trust value associated with the provisioned CM certificate for validation.
Baseline Privacy Debugging Note: All Privileged Mode CLI debug commands are reserved to ARRIS Tech Support personnel. Do not enable CLI debug logging without specific instructions from ARRIS Tech Support. This section describes the debugging sequence for Baseline Privacy on the CER.
Page 603
CM has completed, failed, or not completed. There are three states Baseline Privacy may be in: Disabled — The config file has instructed the C4/c CMTS to disable privacy for this modem. Initialized — The modem is registering BPI configuration data. Privacy mode is not known.
(UCAM) Use the following command to display privacy traffic key (TEK) for a given cable-mac group registered on a UCAM: show interface cable-mac <mac> cable privacy tek <SAId> Baseline Privacy Trap Codes The table below lists the Baseline Privacy traps furnished by the C4/c CMTS and the recommended user action for each one. See Baseline Privacy Interface (BPI) (page 585) for more information.
Page 605
Problem: The respective modem’s authorization request has been rejected. Action: The internal C4/c CMTS reason for the reject will be displayed in the modem’s respective auth reject error string MIB table entry. If the reason can be corrected, fix and reboot the modem.
Page 606
Problem: The time of day is needed to check the validity period of the digital certificates. If there is no TOD server or the C4/c CMTS has cannot collect the time of day, the certificate validity period cannot be tested and this failure will result.
Page 607
Problem: There are encryption algorithms that the CM can support that the C4/c CMTS does not. Action: There is no corrective action that can be taken. As long as the CM and C4/c CMTS support at least one common algorithm, the system will operate properly. If the Devices in the system are certified, this will not be an issue.
3COM 3CR29221 Caution: This feature is not meant for general release. The C4/c CMTS does not normally support hybrid mode operation. Turning on this feature without prior testing and approval from ARRIS will lead to unpredictable results and may cause modems to reset or fail to register.
Page 612
: (virtualCm) Allow Virtual cable modems Disabled : (bpiHybrid) Allow upgraded DOCSIS 1.0 modems to operate using BPI+ Disabled : (ignore1D8UCmDsMaxTrafBurst) CMs will use the C4's DSMaxTrafBurst value regardless of CM config file on a 1D8U (DOCSIS 1.1 CMs only)
It does not enhance the BPI+ standard, it defines what level of BPI functionality a modem must have before the C4/c CMTS will permit it to register. BPI is a required level of Baseline Privacy but the operator may choose BPI+.
For more information, see Static IGMP Joins (page 787). The following configurations are not supported in C4 CMTS Release 8.2: DSG SSM with IGMPv2 ASM IP Video on the same MAC Domain DSG ASM with IGMPv3 SSM IP Video on the same MAC Domain ...
Page 635
DSG tunnel defaults to 2.048 Mbps. Note: Even though a default maximum traffic rate is applied if no SCN association is explicitly made, ARRIS strongly recommends association of an appropriately provisioned service class name to each DSG tunnel. This ensures enforcement not only of an appropriate maximum traffic rate, but also of an appropriate traffic priority.
Overview The high-level goal of this feature is to allow the C4/c CMTS user to classify Customer Premise Equipment (CPE) into a number of distinct device classes. Device classes are the names that are given to CPE devices based on the specialized function that the CPE device performs.
Note: This feature does not support IPv6 CPE device classes. Such CPE devices are treated as generic CPE devices. For CPE devices using a dual mode IPv4/IPv6 stack, the C4/c CMTS will recognize only the device class that can be determined from the IPv4 Dynamic Host Configuration Protocol (DHCP) Relay Agent.
DHCP Options DHCP consists of various options determined and defined by CableLab™ for different functionality in a system. Three of the options that impact the C4/c CMTS are as follows: Option 43 Option 60 ...
Subsequent executions of this command overwrites previous provisioning. If none of the CPE types are specified, then the C4/c CMTS treats the secondary DHCP giaddr like a host, that is, all CPEs.
Some rules for applying filter groups based on device class are as follows: You may only provision one device type per command. There is no any but there is a host. If all cpe types are provisioned they will collapse to host in the C4/c CMTS configuration.
(page 654) for examples of how this command can be used. configure [no] cable submgmt default active This command allows the C4/c CMTS to set default values for the DOCSIS Subscriber Management MIB. Use the option to disable CPE management.
State Machine Crosschecks .............. 683 Overview The Upstream Agility feature is integrated into the C4/c CMTS; it permits a system operator to enable or disable a state machine for each eligible upstream channel. Upstream Agility defines which upstream channels are eligible, which frequencies and operating characteristics are defined for each state machine, and, finally, what rules or triggers are used to cause a channel to transition or hop to another set of upstream characteristics.
(page 679). The C4/c CMTS indicates in the syslog each occurrence of an Upstream Agility state change. In each case, the syslog includes a timestamp, a description of the change (incorporating both the current state and the prior state), and indicates the cable-mac and upstream channel where the state change took place.
Time-of-day triggers are activated by the C4/c CMTS at specific times of the day or on specified days of the week. Periodic triggers can be set to operate at the end of a certain period of time, for example, every 14,400 seconds (four hours).
Page 675
Upstream Agility timers. If the sampling period is set smaller, then better resolution is possible. If it is set larger, then the C4/c CMTS uses fewer system resources. In the CLI syntax it is called sample-period.
30 sec, Change ID: 0b:00:0004, ChannelWidth 6400000->3200000 The C4/c CMTS maintains a separate history of changes for each upstream channel with an active Upstream Agility state machine. Each upstream channel history holds up to 100 entries. After 100 entries are stored, each new entry overwrites the oldest entry.
(lowest numbered state) that does not fail a SCM crosscheck. State Machine Crosschecks The C4/c CMTS performs crosschecks to prevent the Upstream Agility feature from introducing inconsistencies and conflicts that would have a negative impact on performance. These system crosschecks are carried out by the SCM and form a set of operational rules.
(page 695)). The C4/c CMTS attempts to match candidate RCCs for that RCP-ID to the Channels that are found in the MD-DS-SG. These RCCs may either be individually provisioned by the operator or they may be automatically determined by the chassis, if it is provisioned to do so.
Page 687
Dynamic RCC Candidates If so provisioned, the C4/c CMTS might also create dynamic RCC candidates for known RCPs. To do so, the C4/c CMTS searches for combinations of channels within the MD-CM-SG which satisfy the constraints of the RCP. At least one downstream channel of each RCC candidate must be primary capable.
Page 688
The C4/c CMTS selects an RCC that provides the largest bonding group channel set that satisfies the attribute masks of the bonded service flows in the CM’s configuration file.
Here are two ways to set the forbidden bit in the attribute mask: 1. Define a service class with a key Service Class Name (SCN) on the C4/c CMTS with the bits set in the forbidden mask, then define flows that use that SCN. This can be done using the CM config file, or by using PacketCable Multimedia (PCMM) traffic profile type 2 for a dynamic flow.
In the downstream direction, the C4/c CMTS distributes the packets that are destined to the same CM or group of CMs over the multiple channels of a downstream bonding group. DOCSIS 3.0 downstream service flows may be bonded or unbonded depending upon the type of service and the attributes that are attached to the request.
Page 695
The C4/c CMTS processes these RCPs and selects one that will be used to configure the cable modem. A Receive Channel Configuration (RCC) is communicated from the C4/c CMTS to the CM to inform the CM how it is to configure its Receive Channels (RCs) and Receive Modules (RMs) to communicate with the CER.
Page 696
1 must be removed from consideration for the RCC. If no channels are found that meet the restrictions of the attribute masks, DOCSIS allows the C4/c CMTS to select one or more channels to provide service arbitrarily, in which case an error is logged. This algorithm suggests choosing a single channel to provide service.
As shown in the table below, MxN RCP architectures (receive channels x receive modules) are not supported by dynamic RCC creation: they must have RCCs that are statically configured. C4/c CMTS users should know that in such cases the number of static RCC configuration permutations can be unpleasantly large. The C4/c CMTS does not impose limitations on static RCC configurations because to do so would limit MSO flexibility.
Default = enabled Note: If the modem does not support ECN 690, it may flap if the C4/c CMTS changes the primary downstream in the Reg- Rsp-MP. The modem should be upgraded to support ECN 690. For more information on this ECN, see CableLabs specification CM-SP-MULPIv3.0-I09-090121.
No configuration is necessary for this feature. Note: Due to the use of the rolling utilization average distribution algorithm, the C4/c CMTS may send 2 or 3 packets in a row on the same channel. This is normal operation; therefore, you should not expect perfect distribution of downstream packets.
TCS selection at registration, and possible CM movement due to US channel overrides in the RNG-RSP message or Dynamic Channel Changing (DCC). The C4 CMTS will not attempt to move a CM or assign an US channel to a CM using the extended US frequency range unless the CM supports the extended range.
Page 704
2. Enable Multiple Transmit Channel mode: configure interface cable-mac <mac> cable mult-tx-chl-mode 3. Enable the C4/c CMTS to create upstream bonding groups dynamically: configure interface cable-mac <mac> cable upstream-bonding-group dynamic enable Note: When mtcm-conditional-override is set, only CMs that have the bonding bit set in the SfRequiredAttributeMask to the hex string in the step below will be given MTCM (USCB) consideration on the CER.
Partial service is a term used to indicate that service to a particular bonding-capable modem is in a degraded state, such that data cannot or should not be transmitted across some of the channels associated with the modem. The C4/c CMTS provides mechanisms for detecting, reporting, and recovering from some common partial service conditions.
Chapter 22: Channel Bonding channel. In order to provide for recovery of the channel, the C4/c CMTS will provide each modem in this state with one ranging opportunity during every ranging interval for every channel that was determined to be impaired. When the modem responds to that ranging opportunity and successfully completes ranging on that channel, the C4/c CMTS will then begin providing transmit opportunities to that modem on that channel again.
If at a later point in time the modem acquires one or more of the impaired downstream channels, the modem will send a CM-STATUS message to the C4/c CMTS with a report of STANDARD Revision 1.0 C4®...
This feature provides a recovery mechanism for downstream bonded flows that encounter an error whereby the sequence numbers of the flows are out of sync with the C4/c CMTS. By resetting the Downstream Service ID (DSID) on the Downstream CAM, the sequence change count is toggled and the sequence number resets to zero. This will cause the CM to recover from the sequence number out-of- range condition.
C4/c CMTS initiates a battery-saving action which includes reducing the number of channels that the CM uses. If the feature is enabled, the C4/c CMTS places the CM into a 1x1 (US/DS) channel mode to conserve CM battery power, resulting in a partial service condition.
Power Restore Reports Once the C4/c CMTS receives an AC Power Restored report from a CM, the C4/c CMTS treats the CM similarly to when the CM first registers. This includes but is not limited to: New channel set and assignments are determined as in normal bonded modem registration ...
Init Offline --------------------------------------------------------- Total Observability The C4/c CMTS provides visibility to modems which have not fully registered on all channels for which the topology would allow. Use the following commands: show cable modem detail show cable modem bonded-impaired Logging —...
Page 713
14:00:56 13 debg: Debug:cm-status.msgs.expected:CM-STATUS from MAC=00:00:ca:d4:db:33, Transaction=1: Report: QAM/FEC - lock recovery for Downstream Chan ID=2 The C4/c CMTS will generate notice-level logging when disruption in modem ranging occurs on a non-primary channel. For example: 12:26:25 13 notc: MAC=00:15:a4:a4:58:1f; Upstream portNumber 3; SMRanger - Ranging opportunities exceeded on non-primary upstream.
Page 715
IPv6 Distribute Lists ................748 Overview The C4/c CMTS IPv6 Host and Routing feature adds standards-compliant routing of IPv6-conformant packets and an IPv6 host stack to the C4/c CMTS for management applications. IPv6 is defined by a relatively large number of RFCs and Internet Drafts. The requirements on both host stacks and routers are substantially more complex than those for IPv4, partly because many desirable features that are common in IPv4 deployments (but are not part of the basic IPv4 protocol) have been folded into the basic definition of the IPv6 protocol.
GMAC-Promiscuous mode for the specified cable-mac: configure interface cable-mac <mac> cable mcast-fwd-by-dsid GMAC Explicit Mode The C4/c CMTS supports DOCSIS 2.0+ IPv6 modems that are Multicast DSID-based Forwarding (MDF) incapable, as well as modems that are MDF Enabled GMAC Explicit. IPv6 Packet Structure The structure of an IPv6 packet header is defined in RFC-2460: IPv6 Protocol Specification.
In IPv6, addresses are assigned to interfaces, not to nodes. A single interface may be assigned any number of IPv6 addresses of any kind. The C4/c CMTS supports the assignment of only one link-local scope address to each physical interface. This address is typically assigned automatically and is unique over all interfaces in the C4/c CMTS.
General Limits for IP Addresses Users of the C4/c CMTS should observe the following limits and guidelines that pertain to IP addresses: A cable modem (CM) may be assigned only one IP address. It may be either IPv4 or IPv6. If it is assigned an IPv6 ...
64 in its SIPv6 link-local address, the SMAC of packets must match its MAC address in packets it sends. (EUI-64 is trademarked by the IEEE. “EUI” stands for “Extended Unique Identifier”.) The C4/c CMTS verifies that a link-local address being used by a cable-side host (CM or CPE) is not being used by any ...
Link-local traffic, that is traffic from devices on cable interfaces with an IPv6 link-local destination address is never forwarded by the C4/c CMTS. All link-local traffic from devices on cable interfaces received by the C4/c CMTS is terminated at the C4/c CMTS.
Page 722
This feature supports the well-known IPv6 multicast addresses and their equivalent ethernet MAC addresses in the table below. Note that packets with link-local scope multicast addresses will be consumed by the control plane and will not be reflected back to cable interfaces. The C4/c CMTS supports only link-local multicast. Table 92. IPv6 Well Known Multicast Groups...
Network Infrastructure Service C4/c CMTS Security Features for IPv6 The C4/c CMTS provides a number of features to resist various IPv6 Denial of Service (DoS) or spoofing attacks. Here is a summary: 1. Since DHCPv6 and ND/RD packets are targeted to the C4/c CMTS host processor, there is a potential for a malicious subscriber to bombard the C4/c CMTS with a large amount of these packets.
IPv6 Configure Commands The following section provides a list of commands used to configure and enable IPv6 routing on the C4/c CMTS. Note: The IPv6 configuration commands do not support subinterfaces. To configure the IPv6 IP address for the specified interface: configure interface gigabitethernet <slot>[/port.[.subif]] ipv6 address <addr>...
To set the lifetime for the router advertisement on the specified interface: configure interface cable-mac <mac> ipv6 nd ra lifetime {0 | <4-9000>} [no] Where: 0 indicates that the C4/c CMTS is not the default router and 4-9000 is the range in seconds of the lifetime value. DHCPv6 Relay Agent To configure the DHCP relay destination for IPv6 on the specified interface.
When a CPE or client requests an address duplication check using a Neighbor Solicitation (NS) message, the C4/c CMTS checks the Neighbor Discovery (ND) cache to see if the target address is being used. The C4/c CMTS is called a proxy in this case because it responds for the client that already has the requested address.
Address and Interface Specification. The DHCPv6 relay agent within the C4/c CMTS relays the DHCPv6 messages between the DHCPv6 server(s) and all directly connected CPEs and CPE routers on the cable side of the C4/c CMTS. The relay agent processes the PD options within the DHCPv6 messages, extracts the prefixes (routes), and adds them to the route table.
Chapter 23: IPv6 This process of adding PD routes to the C4/c CMTS route table is referred to as Route Injection, which is needed to route traffic destined to IPv6 clients behind CPE routers. The C4/c CMTS marks injected routes as having protocol type PD. Their admin distance is configurable.
(See RFC 5460, DHCPv6 Bulk Lease Query). The C4/c CMTS issues a query of this type whenever a cable-mac virtual router interface (vri), in other words, a layer 3 interface, becomes operational. This approach keeps the PD database up to date.
Page 737
- Displays IPv6 routes for tenGigabiEthernett (sub)interface - VRF name The following are examples of system responses to various show commands from a C4/c CMTS that has learned a single PD route. The highlighted line shows that Prefix Delegation has been enabled on this interface.
IPv6 Prefix Stability feature is an enhancement to the existing Prefix Delegation and Route Injection (PDRI) feature. The PDRI feature allows the C4/c CMTS to learn IPv6 PD type routes as they are given via DHCPv6 to requesting IPv6 gateways.
Figure 92: Scenario for Prefix Stability The setup in the figure above shows two C4/c CMTSs connected to one northbound router (NBR). In this scenario the cable modem is initially connected to the first one but then is moved to the second one as a result of node split.
Page 741
6. The following command line must be identical on all participating C4/c CMTSs. In particular, the metric type and metric value in this command must be exactly the same for all C4/c CMTSs configured to handle the route collisions that result from moving the commercial customers from one C4/c CMTS to another.
6. The following command line must be identical on all participating C4/c CMTSs. In particular, the metric type and metric value in this command must be exactly the same for all C4/c CMTSs configured to handle the route collisions that result from moving the commercial customers from one C4/c CMTS to another.
Page 743
To Configure OSPF on SYS-2 The second part of this procedure begins here. It serves to configure the second C4/c CMTS in this example of Prefix Stability with OSPF. STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide...
Page 744
6. The following configuration line must be identical on all participating C4/c CMTSs. In particular, the metric type and metric value in this command must be exactly the same for all C4/c CMTSs configured to handle the route collisions that result from moving the commercial customers from one C4/c CMTS to another.
Page 745
This collision is detected by both C4/c CMTSs while processing the IGP packets because both C4/c CMTSs are redistributing these PD routes into IGP. When the collision is detected, both C4/c CMTSs check to see if the modem is online. SYS-1 finds that modem is offline and purges the PD route for this prefix.
Page 747
moved from or to this C4/c CMTS, then the two C4/c CMTSs will not detect the collision. The collision can be detected only by IGP protocol packets generated as result of redistributing the PD routes. Make sure the participating C4/c CMTSs are configured to redistribute the PDs that are expected to move.
Route snooping provides an automatic mechanism to clean up previously established PDRI routes that subsequently have been moved to a different C4/c CMTS. When a routing protocol indicates that a route from such a prefix is listed in the routing tables of two C4/c CMTSs, then the C4/c CMTSs establish which one has a connected cable modem using that route.
Page 751
Chapter 24: IP Video The IP Video over DOCSIS approach uses the C4/c CMTS to send managed IP video packets over a DOCSIS delivery system via the Hybrid Fiber Coax (HFC) network. This is the way that IP packets are transported from the head-end to the home.
Video server — Provides the long-term and short-term storage of video content that is available to subscribers. C4/c CMTS — Acts as the interface between the headend and the HFC network. It intelligently manages the flow of IP video streams onto the dedicated IP Video DOCSIS channels of the HFC plant. It also provides routing functions into and out of the "last mile"...
IP multicast group at address G from any multicast source. The notation used to describe this is (*,G). This is known as Any Source Multicast (ASM). On the C4/c CMTS, ASM is supported on the network-side interface via the IGMPv2 or IGMPv3 host protocol and IGMP proxy with IGMPv3 router/querier configured on the cable-side interface.
IP address S. The notation used to describe this is (S, G). On the C4/c CMTS SSM is supported on the network-side interface via the PIM-SSM protocol. SSM requires support of Multicast DSID-based Forwarding (MDF) which means that the C4/c CMTS and the CM must both be MDF-enabled.
IP Video Provisioning Several C4/c CMTS elements must be provisioned for the IP Video feature. Some of these are explained in greater detail in other chapters, including Multicast Chapter and PacketCable Services and Voice Applications Chapter. The following is a general list of what needs to be provisioned: Multicast DSID-based Forwarding (MDF) must be configured for each cable-mac in use.
Page 759
However, the bit-level encoding of an attribute mask is not specified by the DOCSIS 3.0 standard and is left to be defined by the MSO user. Because of this, the C4/c CMTS must be told which bit or bits in an attribute mask indicate an IP video capability.
Page 761
If a multiple downstream CM registers at a fiber node that carries more channels than the CM can support at one time, then the C4/c CMTS must make a choice as to which channels to assign the CM to use for its downstream channel set. As opposed to statically configured service flows, the C4/c CMTS does not know which channels a CM may need for any dynamically created (for PCMM or IGMP, for example) service flows at the time that the CM registers.
The previous section provided an example of setting up an IGMPv2 ASM configuration. IGMPv3 ASM clients are also supported. The following section contains procedures that summarize the C4/c CMTS routing configuration part of the IP Video provisioning process for the IGMPv3 cable-macs and PIM-SM using MDF-enabled.
IP Video Monitoring and Management To monitor service, activity, and quality, metrics may be collected for the service group and stored internally on the C4/c CMTS. These counts are collected to help monitor trends over a long period of time. These metrics are collected on an hourly basis on the hour.
Effects of Enabling MDF on the MAC Domain........791 CLI Commands .................. 792 Overview This chapter provides information on Multicast and the Internet Group Management Protocol (IGMP) technology for C4/c CMTS applications. STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide...
Chapter 25: Multicast IP Multicast This section describes the C4/c CMTS implementation of multicasting as it relates to the handling and forwarding of IP multicast traffic. What is IP Multicast? IP Multicast is an Internet technology that permits a sender to send data (either clear or encrypted) simultaneously to many hosts.
Note: The cable-mac must first be shut down for this change to complete. Multicast Routing Two forms of multicast are supported on the C4/c CMTS: ASM — Any Source Multicast (ASM) denoted as (*,G) ASM is a multicast control technique where clients join a selected multicast group (G) without specifying the source of the multicast traffic.
IGMP is an Internet protocol (IP) for managing multicast groups on the Internet and for the IP Video feature. For an overview of standards related to IGMP, see RFCs 2236, 2933, 3376, 4601, 4607, and 5790. The C4/c CMTS supports IGMP version 2 for host and router functionality and IGMP version 3 for router functionality. ®...
This routing table search yields the RPF next-hop and ingress router interface for the SSM channel. Multicast Routing Configurations The C4/c CMTS Multicast routing supports the following configurations: ASM Configuration — IGMPv2 multicast clients on C4/c CMTS cable-side interfaces and IGMP proxy on the network-side interfaces. For ASM, the following configuration is supported: IGMPv2 or IGMPv3 host on the network side ...
IGMPv3 ASM) or SSM Multicast (IGMPv3) using MDF-enabled. This describes how to configure the C4/c CMTS to track IGMP membership from CPEs on a cable interface. Traffic from a multicast group (or group and specific multicast source) is requested using either IGMP Proxy or SSM. The multicast traffic received by the C4/c CMTS on the network-side interfaces is forwarded to the appropriate cable-side interfaces.
convey to DOCSIS 3.0 CMs the DSID(s) associated with user-joined multicast. With this feature enabled, multicast traffic is treated by the C4/c CMTS as a global default multicast flow with regard to QoS handling in the same way that a statically provisioned multicast session is handled.
Page 794
Display the source memberships status for each group membership. configure interface cable-mac <mac> cable mcast-fwd-by-dsid [no] Allow the C4/c CMTS to use IP Multicast for MDF-disabled mode. PIM-Related Commands configure interface <int> ip pim dr-priority <priority>...
Video and DOCSIS Set-Top Gateway or DSG) for the CAC feature. The C4/c CMTS provides the capability for partitioning the available bandwidth on a per channel basis between telephony (Voice Over IP or VoIP), IP Video, and High Speed Data (HSD) services. The data portion of the channel bandwidth is still allowed to be over-subscribed.
Chapter 26: Connection Admission Control General CAC Description CAC is a C4/c CMTS feature used to determine if adequate resources (specifically, channel bandwidth) are available to permit a new service flow to be established. The CAC feature tracks allocated bandwidth based on the minimum throughput (MinSFRerserved) value of the service flow, and tracks the total allocated bandwidth on a new per channel basis.
SIP/PCMM VoIP calls using voice flows are also handled this way. The PCMM specification defines eight levels of priority. On the C4/c CMTS, these eight levels are mapped to only two priority levels used for PacketCable DQoS calls. One is for normal calls and the other is for emergency calls.
Page 801
<%bw> - Minimum% US and/or DS channel bandwidth reserved for normal voice use After changing a voice limit that applies to all downstream or upstream channels, use the following command to propagate default global voice limits for PacketCable to all channels in the C4/c CMTS: configure packetcable voice-limits set-all To set the Tmin for CAC to track the allocated bandwidth, enter: configure qos-sc name <service class name>...
CMTS randomly searches for an existing normal call on that channel to preempt. If a normal call to preempt is found, the C4/c CMTS simultaneously initiates a tear-down of that normal call while allowing the emergency call to be set up.
ARRIS recommends the utilization of some of these DOCSIS parameters in association with each of the applications that might potentially run on the C4/c CMTS. Keep in mind that other settings can be used, as long as the relative priority of the various applications is set as desired.
Page 807
Notes Priority UPSTREAM Upstream Voice Bearer The C4/c CMTS guarantees service to UGS flows, per the DOCSIS specification; Traffic: UGS and UGS/AD therefore, this flow type is always higher priority than any other. Upstream Voice and Video ARRIS strongly recommends upstream signaling traffic be handled at traffic priority Signaling Traffic 6 to ensure service set up even in the presence of high speed data overload.
(for HSD) or via SCN (for DSG). Overload Conditions ARRIS recommends the following for adjusting SfMinReservedRate (tmin) and SfMaxTrafficRate (tmax) as shown in the table below whenever there is a desire to maintain toll grade performance under data overload conditions: Table 100.
(QoS). PacketCable services on the C4/c CMTS provide the ability to place enhanced-QoS telephone calls over an existing DOCSIS cable data access network. To provide this capability, the C4/c CMTS must communicate with several other specialized servers over a managed IP network that is capable of providing enhanced QoS from end-to-end.
Page 811
(CMS), the Record Keeping Server (RKS), and the Delivery Function (DF) for various portions of signaling information. Note: The IP addresses and ports for RKS and DF are configured on the CMS, not on the C4/c CMTS. STANDARD Revision 1.0 C4®...
Page 812
Call Management Server (CMS) Provides call control and signaling services for the MTA, C4/c CMTS, and PSTN gateways; typically performs both Call Agent (handles call state) and Gate-Controller (authorization) functions as well.
Higher subscriber satisfaction because subscribers are paying for the services they want. The ARRIS implementation of PCMM is based on the C4/c CMTS's carrier class redundancy, high-speed architecture, and DOCSIS QoS capabilities, which are described elsewhere in this document.
Page 814
Once the AM grants a request to access a service, it sends a request for bandwidth to the Policy Server. Policy Server (PS) — A system that primarily acts as an intermediary between Application Manager(s) and C4/c CMTS(s). It applies network policies to Application Manager requests and proxies messages between the Application Manager and C4/c CMTS.
Page 815
Acts as a COPS Policy Enforcement Point (PEP) with respect to the AM Acts as a COPS Policy Decision Point (PDP) with respect to the C4/c CMTS Communicates with one or more AMs and one or more C4/c CMTS ...
Chapter 28: PacketCable™ Services and Voice Applications Figure 100: Network Diagram of PCMM Implementation Compliance with PCMM Standards For a listing of the PacketCable Multimedia specifications that the C4/c CMTS complies with, refer to the Specifications chapter. Future releases of the C4/c CMTS will support: STANDARD Revision 1.0...
HFC topology changes. If an operator uses this solution, the CPE IP address is regarded by the C4/c CMTS as a remotely connected subnet because the CM acts as a router. If the operator needs to provide PCMM-based service(s) to the CPEs, the C4/c CMTS must support PCMM for these remotely connected subnets in order to provide the service.
Page 819
PCMM CLI Commands The C4/c CMTS supports multiple routing tables using the VRF feature. To prevent confusion that could occur if the same subscriber ID existed in two different VRFs, the C4/c CMTS allows only one VRF to support remote subscriber IDs for PCMM.
Where: <IP address> is the IPv4 or IPv6 address of the CM or CPE. PCMM Configuration Procedures Procedure Guidelines To configure the C4/c CMTS for PacketCable services, the following steps must be taken: Configure and bring in-service all cards in a system ...
Note: Control Complex Redundancy does not apply to the C4c CMTS. PC1.x and PCMM are designed to coexist on the C4/c CMTS. Either one or both can be enabled. Either can be disabled without impairing the function of the other.
Page 822
Look for TCP connections with a state of ESTABLISHED at ports 2126, 1813, and 3918 on the CMTS. The C4/c CMTS generates an output similar to the following: show packetcable cops servers Proto...
Page 823
When PacketCable services transition from enabled to disabled, all PacketCable calls in progress are aborted and signaling links to all C4/c CMTSs are torn down. If PCMM is shut down, all associated PacketCable gates are torn down and all signaling links to the PSs are torn down.
Page 824
When PacketCable services transition from enabled to disabled, then all PacketCable calls in progress are aborted and signaling links to all C4/c CMTSs are torn down. If PCMM is shut down, all associated PacketCable gates are torn down and all signaling links to the PSs are torn down.
Page 825
This timer has a range of 1 to 600 seconds. Timer T7 — The value of Timer T7 is determined by the CMS and is sent to the C4/c CMTS in a Gate-Set message along with the rest of the authorization parameters of a call. Timer T7 corresponds to the DOCSIS 1.1 parameter, which is known as the Timeout for Admitted QoS Parameters for the service flow.
Page 826
Chapter 28: PacketCable™ Services and Voice Applications be modified through the use of CLI commands. To set the threshold value of a particular timer of the C4/c CMTS, issue the CLI command: configure packetcable pcmm timer t1 <value> Where: <value> is the time, in deciseconds. Default = 300 deciseconds.
Page 827
Service Flow, and stops timers T2 and T3 if they are running. If the C4/c CMTS detects that the flow is unused for a time in excess of the T3 timer, the C4/c CMTS notifies the Policy Server that the service-flow associated with the gate has been unused, starts the T4 timer, and transitions the Gate to the Committed-Recovery state.
Page 829
QoS for telephony. One of the ways to do this is to use the DiffServ protocol. This protocol uses a field in the IP header to determine the quality of service level to be used for each network hop. The C4/c CMTS marks all upstream voice packets with the DiffServ code point that is provided by the CMS in the Gate-Set message.
Event Messaging Element Identifier — The Event Messaging element Identifier is a number that is assigned to the C4/c CMTS and is included in all event messages from the C4/c CMTS. This number is used by the RKS so that it knows that the event message came from this particular C4/c CMTS.
Page 831
(CMs or MTAs, for example) to utilize or expect packetcable gates. The following CLI command can be used to alter timers on the C4/c CMTS: configure cable global max-qos-admitted-timeout <timeout in seconds>...
Advanced CM Configuration File Verification ........866 AAA Overview The AAA feature enhances the authentication, authorization, and accounting capabilities of the C4/c CMTS by means of the Terminal Access Controller Access Control System Plus (TACACS+) protocol. This protocol not only standardizes the interface to a network element’s AAA capabilities, it also enables centralized administration of security policies across a...
Cisco’s line interface model is included as part of this feature. A line is any point of origin for a CLI session. The C4/c CMTS currently supports two types of lines: console lines and vty (virtual terminal) lines. A console line is a CLI session over the RPIC’s console port, while a vty line is a CLI session over a virtual terminal.
AAA Functions Supported by the C4/c CMTS Since the C4/c CMTS does not support network-based services such as Point-to-Point Protocol (PPP) or Serial Line IP (SLIP), only login and enable services are considered for authorization. Only command services are considered for authorization for similar reasons.
It supports only MD5-based encryption of transmitted passwords. Note: The Radius security protocol of the C4/c CMTS does not support accounting. The Access-Challenge response is not supported. If one is received, it is treated as an Access-Reject response.
Page 838
[no] { group string host ipAddress | host ipAddress key string [hidden] [auth-port integer] [timeout integer] [retransmit integer] } Configure the source interface that the C4/c CMTS will use for all RADIUS packets that are sent to the RADIUS server: STANDARD Revision 1.0 C4®...
Attributes in the Access-Request Packet If the associated line from the CER is configured for authentication, then the C4/c CMTS prompts the user for a user ID and password. The responses are transmitted in the User Name and Password attributes.
Page 841
The C4/c CMTS also supports the inclusion of Session-Timeout and Idle-Timeout attributes in the Access-Accept packet. The C4/c CMTS outputs all Reply-Message attributes received in Access-Accept packets to the originating line, up to a maximum of 8 attributes. Multiple Reply-Message attributes are displayed in the same order as they appear in the packet.
Page 842
A single State attribute, or none - The State attribute is sent by the RADIUS Server to the NAS client (the C4/c CMTS in this case). The client will include the State attribute unchanged in the Access-Request reply packet.
RADIUS or TACACS+ groups listed within an AAA method, if a rejection is received for an authentication request for the first group in the list, the C4/c CMTS attempts to authenticate against the next group in the method list. This same behavior occurs when a rejection is received as a result of a RADIUS challenge response.
Other architectures may require independent TACACS+ servers (or server clusters) for each AAA function. The C4/c CMTS supports six independently configurable TACACS+ servers. The current implementation of TACACS+ has the following characteristics: Configuration information will include the server’s IP addresses, port number, shared secret, and timeout value.
This ordered list of methods is referred to as an authentication method list. The C4/c CMTS supports six (6) independently configurable authentication method lists. The system is capable of maintaining unique parameter values for at least six authentication method lists.
Accounting Method Lists Accounting may be assigned to one or more TACACS+ server groups or to the local logging function of the C4/c CMTS. As with authentication and authorization, accounting may be assigned to multiple methods in order of preference such that method n+1 is employed if method n is is not available.
5. Select Use Separate Password 6. Enter and confirm the user password. Configuring the C4/c CMTS to Enable Password To Configure the C4/c CMTS to Enable Password 1. Enter the following command to set up the local enable password: configure enable password <password>...
Page 849
[login | enable] <authenticationList>] [authorization <authorizationList>] [accounting {shell | command <integer>} [stop-only] <accountingList>] [no] Since the C4/c CMTS currently supports a single console port and up to sixteen remote sessions, the commands shown in the table below are possible: STANDARD Revision 1.0 C4®...
Page 851
Description Default Value Port TACACS server’s TCP port number Time in seconds that the C4/c CMTS waits for a response from the TACACS Timeout server before aborting a TACACS transaction. If true, indicates that the server supports multiplexing multiple TACACS+...
TACACS+ server. Operators of the C4 CMTS are already capable of specifying the IPv4 source addresses for SYSLOG, SNMP TRAPs, and Remote Query. The feature forces the C4 CMTS to use a TCP socket for communicating to the TACACS+ server that is locally bound to the primary IPv4 address associated with the specified interface.
Page 853
on that interface is used as the source IP address. If an IPv4 address is not configured on the TACACS+ source interface, the C4 CMTS falls back to the default behavior until a valid IPv4 address is configured on the respective interface.
SSH2 SSH2 Description The C4/c CMTS Secure Shell Protocol version 2 (SSH2) server provides a secure in-band management connection from a remote client to manage the C4/c CMTS. The system management tools available with SSH services are: Terminal service for interactive CLI and single-command execution ...
In the SSH-UserAuth layer, the client user is authenticated with the server using password and/or public key authentication. The server only supports DSA PEM-formatted and DSA SSH2-formatted (aka, IETF SECSH, IETF RFC-4716, Standard) user key types. Password authentication is performed by the C4/c CMTS CLI user authentication service, which includes local password and TACACS+ authentication.
The C4/c CMTS provides a CLI command to generate the server key pair. If the system administrator prefers to generate the key pair offline, a CLI command is available to import these. Remember, the server key pair must be DSA PEM- formatted.
Page 858
Note: If the server is running, this command also stops the server. Configure User Keys There are no specific commands to configure user public keys. User public key files must be transferred into the C4/c CMTS/usr directory. The filename formats are: <username>.pem for DSA PEM-formatted key type...
Access Control List (ACL) since a single entry in the routing table applies to all ingress interfaces. With this feature enabled, the C4/c CMTS system administrator can define a route in the C4/c CMTS routing table to a null interface.
Source Verify via DHCP Server — This facility allows the C4/c CMTS to query a DHCP server for the CM MAC address associated with a given SIP when that SIP is not present in the MAC DB of the C4/c CMTS. It does this using a DHCP LEASEQUERY message.
IPv6 Address Learning and Invalid IPv6 Prefixes — If Cable Source Verify is enabled, then any IPv6 source address using an expired prefix will not be learned. If any IPv6 prefix expires or is deleted, the C4/c CMTS removes all of the learned IPv6 source addresses using that prefix from the MAC database and from the CAMs.
IP address to a MAC address. If the request satisfies all the checks, the new learned information is added to internal databases of the C4/c CMTS and copied into the CAM hardware. Note: CPE Host Authorization is not supported for IPv6 addresses.
Page 865
IP address. If the same IP address is already used, the new creation is rejected. The C4/c CMTS supports a maximum of 1000 MIB entries in the Host Authorization table and up to 32 entries for a single CPE/MAC address.
TFTP Enforcement to ensure that modems are using the configuration files downloaded from the proper server, and Dynamic Shared Secret Verification, which uses a MIC modified by the C4/c CMTS to verify that these files have not been altered.
CMTS verifies the MIC by dynamically creating a secret key when the cable modem is registering, and using this key to create a new MIC which only the C4/c CMTS can verify. This secret key is valid only for that particular session with that particular cable modem.
Option 125, Sub-option 2 This applies only when the C4/c CMTS is acting as a TFTP relay agent when the TFTP Enforce feature or the Dynamic Secret feature is enabled. This option uses the Vendor Identifying Vendor-Specific (TLV 125) for CableLabs (OID enterprise 4491) and is called the DHCPv4 TFTP Servers Option.
Page 872
Chapter 29: Security request to the C4/c CMTS, the system uses the shared secret, which only it and the configuration server know, to calculate the MIC value. If this value is the same as the one sent by the registering modem, then the modem is allowed to register.
When MSOs detect the same MACs on multiple systems, they can add them to the deny list on the C4/c CMTSs where those MACs do not belong. If a malicious user is detected by the C4/c CMTS, their modem can be added to the MAC Deny list.
Each of these electronic surveillance features may operate simultaneously and independently. CALEA The C4/c CMTS supports PacketCable Electronic Surveillance (ES), versions I01, I02, I03, and I04, which includes Communications Assistance for Law Enforcement Act (CALEA) Call Data and CALEA Call Content. PacketCable Electronic Surveillance makes it possible for MSOs that implement PacketCable specifications to support lawfully authorized STANDARD Revision 1.0...
Page 876
When a surveillance request has been associated with a subscriber on the CMS and the subject under surveillance is involved in a call, an Electronic Surveillance object is sent to the C4/c CMTS within the Gate-Set message sent to the C4/c CMTS from the CMS.
The C4/c CMTS dynamically determines the electronic surveillance version from the syntax of the electronic surveillance object sent to the C4/c CMTS from the CMS. The C4/c CMTS can be connected to multiple CMSs, each of which might support a different version of electronic surveillance. The C4/c CMTS forwards surveillance information in a format compliant with the version related to the surveillance request in question.
The C4/c CMTS allows an LI tap against a single modem, each session directed to a unique MD IP address. In the C4/c CMTS, the only data stream specification that is supported in the cTapMIB is the current layer 2 (aka an 802 stream) "subscriber interface"...
Page 879
For a modem that is being tapped, the C4/c CMTS will encapsulate both IPv4 and IPv6 traffic. The encapsulation header will be an IPv4 header, but the data encapsulated can be either an IPv4 or IPv6 packet. This means the C4/c CMTS will replicate and encapsulate all traffic with an ethertype of either 0x0800 or 0x86dd.
Configuration of secure access The Legal Intercept request can be configured directly using the C4/c CMTS and the configure cable intercept command. It can also be configured by setting the cTapMIB entries using SNMPv3. The CLI and the SNMPv3 agent have simultaneous access to the same underlying cTapMIB object. Therefore, the operator must manage simultaneous access appropriately.
Page 882
4. Use the following command to set the source interface for the SNMPv3 messages and the UDP/IP encapsulated intercept traffic. If you do not use this command to set the source interface for LI, then the C4/c CMTS uses the same source interface value that is used for SNMP traps.
JohnDoe Password: TopSecret Configuring the intercept source interface specifies the source IPv4 address used by the C4/c CMTS. 10. To confirm the status of the tap sessions for a specific subscriber or all tap sessions: show cable intercept [subscriber <CM MAC address>] [userid <string>] [password <string>] If you include the keyword subscriber this command displays tap session status for that subscriber only.
There are differences between the other electronic surveillance methods, including LI and legacy CALEA. They include: PC 2.0 LAES depends solely on the TAP-MIB interface for the MD to remotely control tap sessions at the C4/c CMTS LI requires CLI commands to configure individual taps ...
Additional Guidelines The following items should be considered with regard to the PC 2.0 LAES feature: The C4/c CMTS does not support filtering on type of service, flow ID, or virtual router function (VRF). Therefore, the following corresponding pktcESTapStreamEntry MIB objects are accepted but have no impact on the packets selected for intercept: ...
The parameter can either be extended or reduced as necessary. If a new timeout value is in the past, the active tap session will be immediately terminated by the C4 CMTS. STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide...
Page 887
notifications and may result in: The C4 CMTS may initially accept a new tap stream, returning a successful SNMP response message, but will later fail to enable the tap stream. A pktESTapMediationDebug notification is the only mechanism for the MD/operator to be notified that the tap operation failed.
0 Configure SNMPv3 User View The following procedure configures the C4/c CMTS to allow communication with the MD via the SNMPv3 user view. The examples use arbitrary parameter names in the commands. To Configure an SNMPv3 User View for PC 2.0 LAES ...
Page 891
MAC Domain may be used simultaneously. General load balancing groups are calculated by the C4/c CMTS when the fiber node command is entered with MAC Domain channels. The C4/c CMTS will automatically create a general load balancing group for each MAC Domain-Cable Modem-Service Group (MD-CM-SG).
(page 903) section of this chapter. Using Multiple Rules It is possible to configure a policy with more than one load balancing rule. In such cases, the C4/c CMTS uses the following algorithm to determine which load balancing rules to follow: STANDARD Revision 1.0...
Chapter 31: Load Balancing If one rule is disabled and another enabled at any given time, the C4/c CMTS uses the types, method and threshold parameters from the rule that is enabled. If all rules are disabled, there is no load balancing.
Page 907
These may or may not be D2.0-capable channels. When tcs-load-balance is disabled, the TCS calculated by the C4/c CMTS (if all US channels have acceptable US power levels) is chosen from lowest to highest channel-id. In this case, it is recommended that any D2.0 capable US channels (ATDMA) in the mac-domain be configured such that they are the lowest numbered channels in the cable-mac.
RLBG. The following factors will prevent a cable modem from being steered to an RLBG: Dynamic Load Balancing is disabled at the C4/c CMTS. Dynamic Load Balancing is disabled for the load balancing group to which the modem belongs.
If there is a match between the service-type ID of the restricted load balancing group and the service-type ID defined in the modem’s config file or associated with its MAC address or OUI, then the C4/c STANDARD Revision 1.0...
Page 911
Add the TLV to the CM config file. This will set TLV 43.11 in the CM config file. When the CM registers, it will be steered to the US/DS pair in group 100 as shown in the following figure. (Notice that this view is from the Arris PacketACE tool.)
-------------- ---------- ------------------ ---------- --------------- ---------- 000f.9f7a.eaf8 Note: If a CM config file and the C4/c CMTS provisioning specify different service-type IDs, the C4/c CMTS provisioned value takes precedence. In this partial example, the C4/c CMTS service type takes precedence over the CM provisioning. The CM provisioned service type, xyz, is in parentheses to indicate that it is not being used.
When a CM sends a bonded registration request and the CM is in an MD-CM-SG that corresponds to an enabled load balance group, the C4/c CMTS will attempt to assign a Receive Channel Set (RCS) that includes the least loaded downstreams in the MD-CM-SG.
Page 914
TCS load balancing is enabled. With TCS load balancing enabled, the C4/c CMTS supports distributing D3.0 modems to the least loaded primary and non- primary channels even if periodic dynamic load balancing is disabled. Related CLI Commands Use the following CLI command to globally control enabling of TCS load balancing: configure cable load-balance tcs-load-balance <enable|disable>...
D2.0 or D3.0 rule-based modem steering (see Rule-based Modem Steering (page 905)) Steering to an RLBG based on the modem’s group defined in the CM config file or configured at the C4/c CMTS (see Steering to RLBG (page 908))
Page 918
DCC. Note that the C4/c CMTS considers whether the CM supports the 5-85 MHz extended upstream frequency range when choosing a new channel set. If the CM does not support the extended range, any new channel set will not include an upstream frequency in the extended range.
Extended Upstream Frequency Range Extended upstream frequency ranges (5 - 85 MHz) are supported with recent releases. The C4/c CMTS uses the modem capability when evaluating TCS selection and potential modem movement via DCC or DBC. A modem will not be assigned to an US channel, nor will a CM be moved to an US channel using the extended upstream frequency range if the CM does not support the extended range.
Failed List Operation The C4/c CMTS maintains lists of CMs which have failed to load balance, either because of a failed DCC or a failed DBC. A separate list is maintained for each type of move.
Chapter 31: Load Balancing Time is taken from the C4/c CMTS's internal clock. It does not automatically adjust for calendar changes such as daylight savings time. To confirm the aging-out setting, use the following command: show cable load-balance Following a period of RF issues on a given fiber-node, it is recommended that the failed list be cleared to give the load balancing software a larger pool of modems from which to choose so that the load balancing software is more effective.
This version of the manual modem move command supports moving a CM to a different channel that may or may not be on the same C4/c CMTS. If issued with only the us-channel-id parameter, but without the downstream frequency identified, the CM is moved within the same platform.
Page 929
A downstream must exist and match the docsLoadbal3ChgOverGroupdownFrquency. The upstream channel ID must exist on the C4/c CMTS on the specified Mac Domain. The command will be rejected with an error message if any of these items are invalid when a ChgOverGroupCommit is attempted.
Power Boost Cap ................946 Overview The C4/c CMTS provides several methods for regulating the flow of packets in the network. These methods include: Throttling of excessive upstream packets Monitoring and controlling cable modems (CMs) and Customer Premise Equipment (CPEs) that are generating ...
Chapter 32: Packet Throttling RCM Protocol Policing This feature allows the C4/c CMTS to select and police packets destined for the RSM_RCM processor according to packet protocol type. Note: This feature is also known as Improved Denial-of-Service Attack Protection. Maintaining Performance During Excessive Traffic By selectively throttling protocol packets, the C4/c CMTS can continue to function as a router during periods of excessive traffic.
The C4/c CMTS uses three leaky buckets to throttle packets. One bucket collectively throttles al IPv4 ARP and IPv6 ND type packets, and a second bucket throttles all IPv4 and IPv6 DHCP packets, and a third throttles IGMP packets.
IP addresses that do not have an active entry in the ARP and ND caches. Configure ARP Throttling Commands Various commands are used to configure and manage ARP throttling for the C4/c CMTS and are described in the table below.
Traffic Shaping Traffic shaping is another QoS mechanism used with the C4/c CMTS. In general, traffic shaping and traffic policing both accomplish very similar goals. Both mechanisms change the handling of packet streams in a particular service flow to better match the service for which the customer subscribed.
Packets that must be held more than two seconds in order to conform to the shaping norms are dropped. Disabling policing on the C4/c CMTS also disables traffic shaping on the DCAM because policing determines whether a flow is conforming or not.
<scn> peak-tr-rate 10000000 This command sets the Tpeak for the SCN. When modems register, they get the Tpeak from the C4/c CMTS. Be sure to set the Tpeak value larger than the value of the upstream Tmax.
ACL. The use of ACLs within the C4/c CMTS, and within any router for that matter, is considered a fundamental capability. ACLs are used in conjunction with one or more ACL applications. It is the ACL application that initiates a packet classification search in a particular ACL and takes action on the packet based on whether the matched ACL entry was a permit or deny.
Extended access lists are supported for IPv4 and for IPv6. These lists have a range of 100-199. The C4/c CMTS supports a total of 2048 access list entries and up to 1024 entries per access list.
RCM or cable-side interfaces. Packets can be selectively passed or dropped based on the configuration of the entries within either IPv4 or IPv6 ACLs. It enables the MSO to limit access through the C4/c CMTS to network services such as administrative and billing systems to a subset of authorized users.
Chapter 33: Access Control Lists In-band Management The ARRIS C4/c CMTS offers enhanced in-band network management with controlled access to the SCM via standard Access Control Lists (ACLs) for C4/c CMTS administrators. Note: The SCM Access feature does not support IPv6 ACLs.
IGMP ACLs The C4/c CMTS does allow the IGMP default multicast group IP filter behavior to be overridden by applying an ACL to the IGMP configured interface. Because the application of an ACL to an IGMP configured interface will override all of the default IGMP group membership filters, an ACL rule must exist for any multicast sessions that the C4/c CMTS is expected to permit or deny.
IPv6 ACLs Note: IPv6 ACLs are limited to include entries with Source IP only. The C4/c CMTS does not support IPv6 ACL entries with any other match criteria. IPv6 Access Control Lists can only be configured with an access list name. An ACL number cannot be used to configure an IPv6 ACL.
SESSION-STOP message. The next interval begins immediately. Adhoc — The C4/c CMTS exporter opens a session interval as soon as a collector sends the FLOW-START message. The C4/c CMTS Exporter streams all records (queried and event-triggered) until queried records are finished, then closes the interval with the SESSION-STOP message.
Redundancy The IPDR SP specification supports the use of multiple collectors for backup redundancy. The C4/c CMTS exporter imposes a maximum of five collectors. A priority is assigned to each collector. The highest priority collector is considered the primary collector;...
Simultaneous Sessions In DOCSIS 3.0 mode, the C4/c CMTS exporter can support up to four simultaneous IPDR sessions over multiple TCP connections with a collector. For example, a collector can manage four simultaneous sessions over a single TCP connection or over four TCP connections with each carrying one session.
Keep Alive is when the collector sends KEEP-ALIVE messages to the exporter after a certain period (not to exceed the Keep Alive Interval parameter). This parameter is configurable at the C4/c CMTS and is communicated to the collector when it connects.
This section presents DOCSIS 3.0 IPDR configuration. Refer to Command Line Descriptions for further explanation of the DOCSIS 2.0 commands. Parameters The C4/c CMTS exporter parameters are broken into specific service parameters and global common parameters. STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide...
Page 964
Collector — IP address and redundancy priority of each collector The C4/c CMTS IPDR Fully Qualified Domain Name (FQDN) is included in each exported IPDR record. The IPDR FQDN is statically configured using the C4/c CMTS CLI. The IPDR FQDN is composed of the: Hostname ...
Before configuring the modules, remaining equipment, and interfaces, configure the hostname and syslog server for your C4/c CMTS. Configure a Host Name The host name is used in command prompts and system messages. Configure a hostname for the C4/c CMTS using the following command: configure hostname <name>...
IPv4 address of the syslog server. How to Add and Delete Users Each user must have a unique system login account in order to gain access to the C4/c CMTS and to the command line interface (CLI). This is for the purpose of local authentication.
The output of the show running-config command will not display the actual password. It will be encrypted and shown as an alphanumeric string. Because the passwords are encrypted, an operator can use the running configuration of one C4/c CMTS to populate the passwords and CLI command access levels of another chassis without compromising the passwords.
The filename of this global profile is .profile. Creating a Global User Profile Use the procedure below to make a sample script that executes each time someone logs in to the C4/c CMTS. To create a global user profile script, use the following example: ...
Creating a User Profile To create a script that executes each time you log in to the C4/c CMTS, use the following example: 1. On a personal computer, create a text file of each of the desired commands, on a separate line, using the filename: .profile.<...
Sample Bootloader Dialog for Password Recovery The bootloader dialog below is an example. It may vary depending on the hardware and software versions of the C4 CMTS. The text below presumes that the user has allowed the bootloader to run once. The example below is what he or she will see when the bootloader runs a second time in order to reset his or her password.
Page 977
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.9.6] Copyright (C) ARRIS Enterprises, Inc. 2015 All rights reserved. STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide...
To synchronize the C4/c CMTS to a network time server, you must choose Network Time Protocol (NTP) as your synchronization protocol. If preferred, you may operate the C4/c CMTS on the local (internal) clock of the C4/c CMTS without synchronizing it to a network; however, if you intend to enable PacketCable, you must use NTP.
Chapter 36: Clock Synchronization Protocol Clock Commands The table below and the paragraphs that follow provide the CLI commands that are used to configure and manage the C4/c CMTS internal clock. For more information on these CLI commands see CLI Overview.
Page 983
2012 December 13 07:14:20 America/Chicago (STD) Network time sync protocol is NTP 10.50.42.3 server unicast burst=off prefer=on minpoll=4 maxpoll=10 ver=4 key=0 C4/c CMTS (client) default values: minpoll=6 maxpoll=7 ver=4 auth=on Show Clock Greenwich Mean Time The following command displays the GMT:...
Setting the Internal Clock The purpose of the procedure that follows is to manually set the internal clock of the C4/c CMTS. Note: If there is an active NTP server, you must first disable the NTP server before manually adjusting the internal clock.
Used to configure an NTP unicast client of the remote server <0-65534>] [prefer] at the specified IP address. The remote server distributes time [minpoll <4-11>] [maxpoll <4-11>] [version <2 | sync to the C4/c CMTS, but does not synchronize itself to the 4>] [no] C4/c CMTS. See also Configure NTP Client (page 986).
Chapter 36: Clock Synchronization Protocol Configure NTP Client The purpose of the procedure that follows is to configure the C4/c CMTS as an NTP client. This means that the C4/c CMTS clock is synchronized to the NTP server. To Configure the NTP Client ...
Page 987
PacketCable requires that the maximum interval between consecutive attempts to synchronize the C4/c CMTS local time of day clock must not exceed one hour. Therefore, NTP.MAXPOLL must not exceed 11 (that is 211 or 2048 seconds, which equals approximately 34 minutes). The CLI command configure ntp maxpoll <4 … 11> has a default value of 7.
Page 988
When a GMT offset is given, the local TZ is set accordingly, but no DST adjustments are made when local time is displayed or logged. 5. Configure the C4/c CMTS to use NTP network synchronization: STANDARD Revision 1.0 C4® CMTS Release 8.3 User Guide...
NTPv4 provides a mechanism for optional authentication of NTP messages. The PacketCable standard does not require the C4/c CMTS to support this mechanism, but some MSOs do require NTPv4 functionality including authentication. The following CLI commands control whether NTP authentication mode is active or disabled:...
DSCP Marking for Downstream Subscriber Traffic ......1010 Overview Service Class Names (SCNs) designate Quality of Service (QoS) parameter sets that are stored in the C4/c CMTS and are used to simplify configuration. SCNs are intended to be visible to external Operations Support Systems (OSSs).
Note: If there are parameters defined in the config file that are also defined in an SCN referenced by that config file, the config file parameters override those found in the SCN. If you define an SCN in a config file but do not define it on the C4/c CMTS, you will receive an error and registration will be denied.
(SCN) name> the SCN. This name is case sensitive; maximum length = 15 characters. Allows service flows to be given priority for delay and buffering. The C4/c CMTS Priority [priority <priority>] uses this field to assign traffic priorities, which are implemented using a queuing system.
Page 994
Specifies the maximum duration resources remain unused on an active Service [active-tmout ActiveTimeout Flow. If there is no activity on the Service Flow within this time interval, the C4/c <value>] CMTS MUST change the active and admitted QoS Parameter Sets to null.
Page 995
UGS Flow via the Dynamic Service Change mechanism, without negatively impacting existing sessions. TosAndMask [and-mask <value>] IP Type of Service overwrite. Enables C4/c CMTS to overwrite original Type of TosOrMask [or-mask <value>] Service (ToS) byte with new value.
Service Class Name Configuration Typically SCNs are configured using CLI, but they may also be configured in the C4/c CMTS via SNMP using a Cable Modem (CM) management system. This CM management system would define SCNs and define CM configurations as part of a service-level definition process.
This table compares typical throughputs of sample service classes. Each advertised subscriber service should have a corresponding SCN. These SCNs are called on by the configuration files used to register CMs and by the C4/c CMTS to build SFs for subscribers.
Need help?
Do you have a question about the C4 and is the answer not in the manual?
Questions and answers