Rel Notes 7.2.4.2 Build59e9 PDF

CMTS
Release Notes
Version 7.2.4.2
DOC-3004-01
Document Revision 07.02.04.02_B59e9
October 10, 2017
© 2017 Casa Systems, Inc.
All rights reserved. Licensed software products are owned by Casa Systems or its suppliers and are
protected by United States copyright laws and international treaty provisions.
The information regarding the product in this manual is subject to change without notice. All
statements, information, and recommendations in this manual are believed to be accurate but are
presented without warranty of any kind, express of implied. Users must take full responsibility for
their application of the product.
In no event shall Casa or its suppliers be liable for any indirect, special, consequential, or incidental
damages, including, without limitation, lost profits or loss or damage to data arising out of the use or
inability to use this manual, even if Casa or its suppliers have been advised of the possibility of such
damages.
iii
Contents
Casa CMTS Release Notes, Version 7.2.4.2

About this document ......................................................................................... 1-1 .
Contacting Casa ............................................................................................... 1-4

.
Corporate facility ......................................................................................... 1-4

.
Technical support ........................................................................................ 1-4 .
Technical documentation .................................................................................. 1-4 .
Release note revision history ...................................................................... 1-5 .
Major features in Release 7.2 ........................................................................... 1-5 .
QAM 8x192 downstream module enhancements ....................................... 1-6 .
Implementation notes .............................................................................1-7

Unsupported functionality in Release 7.2 ...............................................1-7
QAM 8x192 broadcast video (MPTS pass-through) ................................ 1-7 .
QAM 8x192 redundancy requirements for OFDM ...................................... 1-8 .
Support for two OFDM downstream channels in R7.2 ................................ 1-8 .
Configuration steps .................................................................................. 1-9 .
Reverting to one OFDM channel ..........................................................1-10

Remaining configuration steps .............................................................. 1-10 .
Dynamic modulation profile change on OFDM channels .......................... 1-10 .
Orthogonal Frequency Division Multiple Access (OFDMA) .......................1-11 .
Low-density parity-check (LDPC) code support in OFDMA ....................1-11 .
TaFDM between OFDMA and TDMA channels ......................................1-11 .
TaFDM configuration ............................................................................1-12

TaFDM restrictions ...............................................................................1-12
Configuration example .........................................................................1-12
TaFDM guardband ...............................................................................1-13
Casa Systems CMTS

iv Release Notes
Contents
Multiple IUC TLV support ....................................................................... 1-16 .
Monitoring OFDMA in SNMP ................................................................. 1-18 .
IPv6 Provider Edge routers (6PE) in BGP ................................................ 1-18 .
NetFlow V9 traffic flow monitoring ............................................................. 1-18 .
CMTS Release 7.2.4.2 software installation ................................................... 1-19 .
Version 7.2.4.2 distribution image ............................................................. 1-19 .
Software update procedures ..................................................................... 1-20 .
Verify any previously-installed software patches ................................... 1-20 .
Verifying the minimum boot loader firmware images ............................. 1-20 .
For Release 7.2 ....................................................................................1-21

Preserving the current software image .................................................. 1-21 .
Updating the application image ............................................................. 1-22 .
Reverting a previously-installed software patch .................................... 1-23 .
Resolved issues and changes in Version 7.2 ................................................. 1-24 .
Table 1. Release 7.2.4.2 Build 59e9 changes and applied fixes..... 1-24
Table 2. Release 7.2.4.2 Build 58b9 changes and applied fixes..... 1-24
Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes..... 1-25
Table 5. Release 7.2.4.1 Build 555c changes and applied fixes ..... 1-32
Table 6. Release 7.2.4.1 Build 54da changes and applied fixes..... 1-32
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes ..... 1-33
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes ..... 1-42
Table 10. Release 7.2.3.2 Build 55fa changes and applied fixes...... 1-79
Table 13. Release 7.2.3.2 Build 4cb3 changes and applied fixes ..... 1-82
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes..... 1-86
Table 15. Release 7.2.1.0 Build 482c changes and applied fixes ... 1-102
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes... 1-103
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes... 1-122
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes... 1-131
Known problems and restrictions in Release 7.2 .......................................... 1-183 .
Possible modem flaps with recovery after editing QAM

channels (ID 78669) ............................................................................ 1-183 .
Casa Systems CMTS Release Ver. 7.2.4.2

Release Notes v
Contents
Observed error message with in-service patch

apply/revert (ID 77833) ........................................................................1-183 .
DVB Simulcrypt over QAM 8x96 shared and narrowcast

channels (ID 72651) .............................................................................1-183 .
SNMP process restarts under certain conditions (ID 79183) ...............1-183 .
LDP session establishment issue (ID 77793) ......................................1-183 .
OFDM channel entries in CLI and SNMP (ID 78054) ..........................1-184 .
QAM 8x192 module restart with switchover (ID 73300) .......................1-184 .
RFoG with TaFDM partial service issue (ID 72475) .............................1-184 .
Modems reporting OFDM MER decrease (ID 71187) ..........................1-184 .
Per-channel and per-port power issue in 2-OFDM mode (ID 72434) ..1-184 .
QAM module redundancy issue with shared channels

enabled (ID 66397) ..............................................................................1-184 .
Enabling OFDMA probe may increase error rate (ID 61757) ...............1-185 .
QAM configuration modify issue (ID 66408) ........................................1-185 .
OFDMA upstream channel utilization incorrect (ID 66350) ..................1-185 .
MPLS traffic handling during SMM switchover (ID 59247) ...................1-185 .
Upstream partial-service issue with certain modulation

profiles (ID 59187) ...............................................................................1-185.
Single carrier 25 kHz spacing in OFDMA (ID 61617) ...........................1-185 .
show datapath-config dhcp-lease-tree command (ID 64537) ..............1-186 .
Operational information .................................................................................1-186

.
Resolutions to security vulnerabilities addressed in Release 7.2.4.1 ..1-186 .
OpenSSL library updates .....................................................................1-186 .
“Broadcast FIFO error” detection .........................................................1-187 .
Extended taps on UPS 16x8 upstream channels ................................1-187 .
Recommended modulation profile over ATDMA with 64QAM ..............1-187 .
Reverting to Release 7.1 (and prior) from Release 7.2 .......................1-188 .
OFDM — QAM 8x192 redundancy limitation (by design) ....................1-189 .
OFDMA — UPS 16x8 redundancy limitation (by design) .....................1-189 .
Enabling DVB Simulcrypt channels .....................................................1-189 .
Forwarding of clear multicast traffic .....................................................1-189 .
Upstream 16x8 channel width limitation ..............................................1-190 .
Casa Systems CMTS

vi Release Notes
Contents
QAM replication limit on QAM 8x96 and QAM 8x192 .......................... 1-190 .
Baseline Privacy Interface (BPI) and BPI-plus modems ..................... 1-192 .
Restricted load balancing groups ........................................................ 1-192 .
Rapid Spanning Tree Protocol ............................................................. 1-192 .
Open Shortest Path First Protocol ....................................................... 1-192 .
Reverting to a prior software release ............................................................ 1-193

.
SNMP MIB objects and OIDs in Release 7.2 ................................................ 1-194 .
SNMP management using the Casa MIBs ................................................... 1-195 .
Appendix A. CLI changes in Release 7.2 ...................................................... 1-196 .
Table 19. CLI additions and changes in Release 7.2 ...................... 1-196

1-1
Casa CMTS
Release Notes, Version 7.2.4.2
About this document

This notice covers Release 7.2 software versions for the Casa C10G, C40G, and
C100G platforms. It includes instructions on installing and upgrading the system
software, information on resolved issues from prior releases, known issues, and
operational considerations. Casa Systems updates and reissues this document anytime
a new version of software becomes available.
Topic Page
Contacting Casa 1-4

Corporate facility 1-4
Technical support 1-4
Technical documentation 1-4
Release note revision history 1-5
Major features in Release 7.2 1-5
QAM 8x192 downstream module enhancements 1-6
Implementation notes 1-7
Unsupported functionality in Release 7.2 1-7
QAM 8x192 broadcast video (MPTS pass-through) 1-7
QAM 8x192 redundancy requirements for OFDM 1-8
Support for two OFDM downstream channels in R7.2 1-8
Configuration steps 1-9
Reverting to one OFDM channel 1-10
Casa Systems CMTS

1-2 Release Notes
About this document
Topic Page
Remaining configuration steps 1-10

Dynamic modulation profile change on OFDM channels 1-10
Orthogonal Frequency Division Multiple Access (OFDMA) 1-11
Low-density parity-check (LDPC) code support in OFDMA 1-11
TaFDM between OFDMA and TDMA channels 1-11
Multiple IUC TLV support 1-16
Monitoring OFDMA in SNMP 1-18
IPv6 Provider Edge routers (6PE) in BGP 1-18
NetFlow V9 traffic flow monitoring 1-18
CMTS Release 7.2.4.2 software installation 1-19
Version 7.2.4.2 distribution image 1-19
Software update procedures 1-20
Verify any previously-installed software patches 1-20
Verifying the minimum boot loader firmware images 1-20
Preserving the current software image 1-21
Updating the application image 1-20
Reverting a previously-installed software patch 1-23
Resolved issues and changes in Version 7.2 1-24
Known problems and restrictions in Release 7.2 1-183
Possible modem flaps with recovery after editing QAM channels (ID 78669) 1-183
Observed error message with in-service patch apply/revert (ID 77833) 1-183
DVB Simulcrypt over QAM 8x96 shared and narrowcast channels (ID 1-183
72651)
SNMP process restarts under certain conditions (ID 79183) 1-183
LDP session establishment issue (ID 77793) 1-183
OFDM channel entries in CLI and SNMP (ID 78054) 1-184
QAM 8x192 module restart with switchover (ID 73300) 1-184
RFoG with TaFDM partial service issue (ID 72475) 1-184
Modems reporting OFDM MER decrease (ID 71187) 1-184
Per-channel and per-port power issue in 2-OFDM mode (ID 72434) 1-184
QAM module redundancy issue with shared channels enabled (ID 66397) 1-184

Casa CMTS Release Notes, Version 7.2.4.2 1-3
About this document
Topic Page
QAM configuration modify issue (ID 66408) 1-185

OFDMA upstream channel utilization incorrect (ID 66350) 1-185
MPLS traffic handling during SMM switchover (ID 59247) 1-185
Upstream partial-service issue with certain modulation profiles (ID 59187) 1-185
Single carrier 25 kHz spacing in OFDMA (ID 61617) 1-185
show datapath-config dhcp-lease-tree command (ID 64537) 1-186
Operational information 1-186
Resolutions to security vulnerabilities addressed in Release 7.2.4.1 1-186
OpenSSL library updates 1-186
“Broadcast FIFO error” detection 1-187
Extended taps on UPS 16x8 upstream channels 1-187
Recommended modulation profile over ATDMA with 64QAM 1-187
Reverting to Release 7.1 (and prior) from Release 7.2 1-188
OFDM — QAM 8x192 redundancy limitation (by design) 1-189
OFDMA — UPS 16x8 redundancy limitation (by design) 1-189
Enabling DVB Simulcrypt channels 1-189
Forwarding of clear multicast traffic 1-189
Upstream 16x8 channel width limitation 1-190
QAM replication limit on QAM 8x96 and QAM 8x192 1-190
Baseline Privacy Interface (BPI) and BPI-plus modems 1-192
Restricted load balancing groups 1-192
Rapid Spanning Tree Protocol 1-192
Open Shortest Path First Protocol 1-192
Reverting to a prior software release 1-193
SNMP MIB objects and OIDs in Release 7.2 1-194
SNMP management using the Casa MIBs 1-195
Appendix A. CLI changes in Release 7.2 1-196

1-4 Release Notes
Contacting Casa
Contacting Casa
Corporate facility
Casa Systems, Inc.
100 Old River Road
Andover, MA 01810
Tel.: 978-688-6706
World Wide Web: www.casa-systems.com
Technical support
In the United States: Tel: 978-699-3045
Email: support@casa-systems.com
Technical documentation
Casa Systems provides the following documentation set in PDF format, viewable
using Adobe Reader 5.0 or later. These PDF files are available from the Casa FTP site
at ftp://support.casa-systems.com.
• Casa Systems – C10G CMTS Quick Installation
• Casa Systems – C10G CMTS Hardware Installation Guide
• Casa Systems – C100G CMTS Quick Installation
• Casa Systems – CMTS Operations and Administration Guide
• Casa Systems – NSI Configuration Guide and Command Reference
• Casa Systems – RF Cable Configuration Guide and Command Reference
• Casa Systems – CCAP Video Edge User Guide
• Casa Systems – CMTS Network Solutions Guide
• Casa Systems – SNMP MIBs and Traps Reference
• Casa Systems – CMTS Troubleshooting and Diagnostics Guide

Major features in Release 7.2
• Casa Systems – CMTS Release 7.2 Features Guide

• Casa Systems – CMTS Release Notes (this document)
Casa Systems provides updates to the manuals on a regular basis. Log on to the Casa
Systems Web site at www.casa-systems.com for the latest files in PDF format. Select
customer login and enter your username and password. If you do not have a
Casa-assigned username and password, send e-mail to support@casa-systems.com.
Effective September 1, 2013, technical documentation CD-ROMs are no longer

shipped with Casa CMTS hardware.
Release note revision history

• 7.2.4.2 — October 2017
Note: If you are upgrading to Release 7.2 from Release 6.1.3 or earlier, and if
you would like to review of all product changes that have been implemented
since you last upgraded your CMTS software, contact Casa Technical Support
for specific versions of the Casa Systems – CMTS Release Notes.
Release 7.2 software is not supported on Casa C1G, C10200, C3200, and
C2200 systems.

This section covers the major features that have been implemented in Release 7.2. For
complete information on all features introduced in Release 7.2, including information
on how to configure new Release 7.2 features, see the Casa Systems – CMTS Release
7.2 Features Guide.
For a brief summary of the features and enhancements that have been implemented in
this latest version, see “Resolved issues and changes in Version 7.2” in this release
notice.
Detailed configuration information can be found in the following manuals to be

published for Release 7.2:
• Casa Systems – NSI Configuration Guide and Command Reference

• Casa Systems – RF Cable Configuration Guide and Command Reference

1-6 Release Notes
• Casa Systems – CMTS Troubleshooting and Diagnostics Guide

• Casa Systems – CCAP Video Edge User Guide
• Casa Systems – SNMP MIBs and Traps Reference
QAM 8x192 downstream module enhancements

Release 7.2 introduces support for multi-port shared channels for broadcast video on
the QAM 8x192 module for the Casa C100G and C40G platforms.
The QAM 8x192 also supports migration to the DOCSIS 3.1 Orthogonal Frequency
Division Multiplexing (OFDM) channel modulation over 10 Gbps downstream and
Orthogonal Frequency Division Multiple Access (OFDMA) 1 Gbps upstream service
flows. See the next section, “Orthogonal Frequency Division Multiple Access
(OFDMA)” for information on the initial OFDMA support in Release 7.2.
The following capabilities have been implemented on the QAM 8x192 downstream
module:
• Combined 64 multi-port shared channels (broadcast) and 64 narrowcast channels

per port: 128
• Maximum multi-port shared channels per module: 128
• Up to 80 narrowcast channels (0 to 79) for DOCSIS, SDV, VOD. (All 128
multi-port shared channels must be narrowcast with no shared broadcast.
• Maximum multi-port shared (broadcast) channels: 64
• Up to 24 Annex A, B, and C channels per port operating in DVB Simulcrypt
encryption mode. These 24 channels must be configured at the upper channel
range, such as 48 to 63. All multi-port shared channels support DVB Simulcrypt.
• Up to two downstream OFDM channels using channel 0 and channel 1, and one
upstream OFDMA channel.
See the following sections for more information:
• “Support for two OFDM downstream channels in R7.2”
• “Orthogonal Frequency Division Multiple Access (OFDMA)”

Implementation notes
• To use the maximum number of narrowcast channels per port (>64), use the video
channel-id-offset command introduced in Release 7.1 so that the number of
narrowcast video channels per port is less than or equal to 64.
The command excludes DOCSIS channels from the video channel numbering
space. The specified offset indicates the number of reserved DOCSIS channels;
video channel numbering begins following the offset, with the first video channel
number beginning at 0.
• Multi-port shared channels are for broadcast video purposes and can only be
configured with the Casa CLI. Therefore, table mode VOD or EDIS/GQI-based
session creation should not be used over the multi-port shared channels.
Unsupported functionality in Release 7.2
• On the QAM 8x192 module, when enabling DVB Simulcrypt on any QAM
channel within an 8-channel block, all remaining channels within that block are
unavailable as DOCSIS channels. All channels within the block must be DVB
Simulcrypt video channels.
• The QAM 8x192 module is NOT supported on the Casa C10G platform.
QAM 8x192 broadcast video (MPTS pass-through)
Release 7.2 supports broadcast video (MPTS pass-through processing) over QAM
8x192 ports 0 to 7 where one input MPTS can be output to one QAM multi-port
shared channel. Note that PID replacement (drop and add) is supported with broadcast
video.

1-8 Release Notes
QAM 8x192 redundancy requirements for OFDM

This section covers the redundant QAM 8x192 requirements when multiple modules
are installed in the C100G.
Active module Redundant module I/O module SMM usage
QAM 8x192 QAM 8x192 8-port I/O SMM 8x10G or SMM

2x10G
One OFDM channel One OFDM channel
64 SC-QAM channels 64 SC-QAM channels Release 7.2.2 or greater
(note that this
configuration is also
supported in the previous
R7.2.1 release).
QAM 8x192 QAM 8x192 8-port I/O SMM 8x10G or SMM
2x10G
Two OFDM channels Two OFDM channels
32 SC-QAM channels 32 SC-QAM channels Release 7.2.2 or greater
Support for two OFDM downstream channels in R7.2

QAM 8x192 module support for up to two downstream OFDM channels has been
revised in R7.2.4.1 on the QAM 8x192 module with the following supported channel
capacities per module:
• One OFDM channel (0); 64 SC-QAM channels per port, and 128 shared channels
as either narrowcast video (VOD or SDV) or multi-port broadcast channels per
module. When the 128 channels are used as narrowcast, up to 80 narrowcast
channels are supported per port, as follows:
— Channels 0 to 31 are available for DOCSIS.
— Channels 0 to 79 are available for video.
— Channels 40 to 79 are available for DVB Simulcrypt.
A maximum of 64 broadcast channels per port is supported.

• Two OFDM channels (0 and 1); 32 SC-QAM channels per port, and 256 shared
channels per module as either narrowcast video (VOD or SDV) or broadcast
channels. When the 256 channels are used as narrowcast, up to 64 narrowcast
channels are supported per port, as follows:
— Channels 0 to 31 are available for DOCSIS.
— Channels 32-63 are available for video.
A maximum of 64 broadcast channels per port is supported.
Note: When configuring two OFDM channels per QAM 8x192 port, DVB
Simulcrypt capabilities are NOT presently supported.
Configuration steps
Perform the following steps to enable two OFDM channels (and 32 SC-QAM
channels) in Release 7.2.3:
1. Issue the module <number> ofdm-channels command in the CLI configuration

mode.
Example
CASA(config)# module 4 ofdm-channels 2
Need to reboot module 4 to apply the change.
Note: The command is NOT required for one OFDM channel and 64 SC-QAM
channels (by default).
2. Reset the module using the reboot module <number> command.
Example
CASA(config)# reboot module 4
3. Repeat steps 1 and 2 for the redundant module to ensure a matching OFDM
configuration between the active and standby QAM8x192 modules.

1-10 Release Notes
Reverting to one OFDM channel
To undo the 2-channel OFDM configuration and revert to one OFDM channel and 64
SC-QAM channels, perform the following steps:
1. Issue the module <number> ofdm-channels command in the CLI configuration

mode:
Example
2. Reset the module using the reboot module <number> command.
Example
CASA(config)# reboot module 4
3. Repeat steps 1 and 2 for the redundant module to ensure a matching OFDM
configuration between the active and standby QAM8x192 modules.
Remaining configuration steps

Perform the follow steps to complete the OFDM configuration.
1. Enable DOCSIS 3.1 using the cable docsis version 31 command in the CLI
configuration mode.
2. Configure the OFDM channels. See the Casa Systems – RF Cable Configuration
Guide and Command Reference for Release 7.2 for complete information on
OFDM.
3. Save the configuration using the copy running-config startup-config command.
Dynamic modulation profile change on OFDM channels

Release 7.2 supports dynamic modulation profile changes on OFDM channels. In
situations where the modem modulation error ratio (MER) on an OFDM channel can
no longer support the highest-rate profile, the software will automatically change to a
profile with a lower modulation rate.
During modem registration, the CMTS will select the appropriate OFDM channels
and the highest-rate profile according to the modem’s capability. Once the modem

returns a registration acknowledgment, the CMTS will then request the Rx MER from
the modem to determine if the error rate is too high to support the current modulation
profile. The software will maintain the highest-rate profile and only move to a
lower-rate modulation profile if necessary.
Once the modem comes online with the CMTS, the software will switch between
modulation profiles (if requested by the modem) to ensure that the highest-rate profile
is being applied to modems on the OFDM channel.
Orthogonal Frequency Division Multiple Access (OFDMA)

OFDMA is the multi-user version of OFDM where many users can transmit and
receive over a single channel simultaneously. OFDMA uses distributed subcarriers
among users to enable multiple user transmissions over one channel. DOCSIS Version
3.1-specific modems are necessary to support OFDMA in the cable network. DOCSIS
3.0 and earlier modems are not supported.
The OFDMA upstream channel capability is available for the UPS 16x8 line card on
the C100G and C40G platforms and is based on the DOCSIS 3.1 specifications from
CableLabs. One OFDMA upstream channel is supported on Release 7.2.
Backward compatibility and interoperability with legacy QAM and UPS channels
coexists with both OFDM (downstream) and OFDMA (upstream) implementations.
Low-density parity-check (LDPC) code support in OFDMA

The low-density parity-check (LDPC) error-correcting code is now supported with
OFDMA transmissions. The LDCP implementation is compliant with the DOCSIS
3.1 specification. There is no configuration requirement with this functionality.
TaFDM between OFDMA and TDMA channels

Time and Frequency Division Multiplexing (TaFDM) allows the upstream frequency
spectrum to be shared between the two types of channels, where one OFDMA channel
overlaps one or more TDMA channels. This feature allows users to transition from the
traditional TDMA scheme to the OFDMA scheme.
With multi-access to shared spectrum resources using the TaFDM scheme, spectrum
resources are divided up into time and frequency dimensions which are then allocated

1-12 Release Notes
to one channel or another. The upstream scheduler determines which area will be used
for TDMA or OFDMA transmissions.
Guardband will be inserted on the boundary between TDMA and OFDMA channels
both in frequency and time dimensions.
TaFDM configuration
Presently, there are no new CLI commands for the TaFDM feature.
In order for the upstream scheduler to run in TaFDM mode, the overlapping channels
must be configured into the same OFDMA subcarrier Service Group.
TaFDM restrictions
There are no restrictions on how the frequency overlap can occur. For example, an
OFDMA channel can
• Cover the entirety of all TDMA channels,

• Cover a portion of the TDMA channels on one side, and
• Reside inside the TDMA spectrum area.
Configuration example
CASA(config)# interface upstream 11/1.0
CASA(config-if-ups 11/1.0)# frequency 22000000
CASA(config-if-ups 11/1.0)# channel-width 6400000




CASA(config)# ofdma exclusion-band 1

CASA(conf-ofdma-exclusion-band 1)# exclusion-sc-group 1 5000000
7000000
CASA(config)# interface ofdma 11/1.0

CASA(conf-ofdma-channel 11/1.0)# lower-freq 5000000 upper-freq
85000000
CASA(conf-ofdma-channel 11/1.0)# prov-attrib-mask 0x0
CASA(conf-ofdma-channel 11/1.0)# sc-spacing 50
CASA(conf-ofdma-channel 11/1.0)# symbols-per-frame 16
CASA(conf-ofdma-channel 11/1.0)# data-backoff automatic
CASA(conf-ofdma-channel 11/1.0)# ranging-backoff 0 4
CASA(conf-ofdma-channel 11/1.0)# voice-bw-reserve 75 emergency 0
CASA(conf-ofdma-channel 11/1.0)# power-level 0
CASA(conf-ofdma-channel 11/1.0)# power-adjust continue 4
CASA(conf-ofdma-channel 11/1.0)# power-adjust threshold 1
CASA# show docsis upstream channel utilization

Upstream Total-BW Utilization Online Secondary Channel
Slot/Port.Channel (Mb/Sec) Percentage Modems Modems Description
-----------------------------------------------------------------------------
11/1.0 (22000000 Hz) 30.7 80 1 2
11/1.1 (28400000 Hz) 30.7 79 0 3
11/1.2 (34800000 Hz) 30.7 80 0 3
11/1.3 (39600000 Hz) 15.4 65 1 2
11/1.0w ( 5M- 85M Hz) 580.6 55 1 1 ofdma
TaFDM guardband
With Time Division Multiple Access (TDMA) and Orthogonal Frequency Division
Multiple Access (OFDMA) channels both enabled on upstream ports, RF interference
may occur between the TDMA and OFDMA channels which can degrade the overall
throughput of all the channels. To address this situation, a guardband of up to 2 MHz
has been applied between the channels (a region not used for transmission) to
safeguard against RF interference (Figure 1).

1-14 Release Notes
Figure 1. TaFMA guardband
Note: There are no added configuration commands to support TaFDM

guardband. The guardband, which supports up to a 2 MHz frequency width, is
handled internally in the software.
With OFDMA mode enabled on a UPS 16x8 line card, each port supports up to one
OFDMA channel and four TDMA single-carrier channels. The OFDMA channels are
between 5 and 101 MHz, while the ATDMA channels can have a center frequency
between 5 and 100 MHz. If the non-overlapping area between the OFDMA and
TDMA edge frequencies is less than 2 MHz, the chances of RF interference can
increase.
An algorithm has been applied to insert a guardband of a specific size automatically

between the OFDMA and single-carrier frequencies based on the signal-to-noise ratio
(SNR) to guarantee error-free transmission. The guardband can be placed at either the
high or low frequency of the OFDMA spectrum based on where the TDMA spectrum
is located.
The SNR value determines the size of the guardband. The guardband ranges are in
increments of 0.25 MHz from 0.25 MHz through 2.0 MHz. For example, with an SNR
measured at 4 dB, a guardband of 0.25 MHz is imposed, whereas an SNR of 20 dB
imposes a larger guardband of 2.0 MHz. The system does this automatically and
requires no user input. The frequency modulation rate also has an effect on the
guardband size. Lower modulation rates (at a smaller bit rate) are less sensitive to

SNR, in which case a smaller guardband can be applied. For example, a high
modulation rate at QAM1024 requires a higher SNR (35.5 dB, translated to 9.5 dB by
the guardband algorithm), requiring a higher guardband size.
The system imposes certain fixed filter sizes for the OFDMA band with the guardband
in effect, in 5-MHz intervals starting at 10 MHz and extending to 95 MHz. The 95
MHz filter is used if no combined OFDMA and TDMA traffic is enabled. The other
10 filters are used when overlapping occurs inside the OFDMA band. With combined
traffic, the narrowest filter that completely covers the overlapping area is selected. For
example, with a 20–40 MHz OFDMA band and a 6.4 MHz TDMA band at 22 MHz,
with both sets of channels operating, a 15 MHz filter is selected for the OFDMA band.
With the guardband in effect, the OFDMA band typically has a 70–80% utilization
rate with OFDMA and TDMA transmitting simultaneously.
Note: To disable the system from adding a guardband automatically, an exclu-

sion zone between the OFDMA and TDMA channels can be configured. How-
ever, the size of the exclusion zone must be calculated to be sufficiently large
to safeguard against overlaps.
Example
The following shows a guardband assignment based on changing a TDMA upstream
interface frequency.
CASA(config-if-ups 12/0.0)# show this
interface upstream 12/0.0

frequency 20000000
channel-width 6400000
power-adjustment continue 4
logical-channel 0 profile 7
logical-channel 0 minislot 2
no logical-channel 0 shutdown
logical-channel 1 shutdown
no shutdown
CASA(config-if-ups 12/0.0)# show interface ofdma 12/0.0
interface ofdma 12/0.0

lower-freq 20000000 upper-freq 55000000
no voice-bw-reserve

1-16 Release Notes
power-adjust continue 4
rolloff-period 64
iuc-profile 1
no shutdown
CASA(config-if-ups 12/0.0)# show cable modem fec

MAC Address US IF USSNR Unerrored Corrected Uncorrectable
6814.01f0.3e67 12/0.0/0 42.1 75 0 0
6814.01f0.3e67 12/0.0w 42.1 11483944 12745 8
e448.c7c0.dc1a 12/0.0/0 42.1 7834606 0 0
After the frequency adjustment from 20 to 21 MHz, the OFDMA wide filter selected
is 40 MHz (centered at 37.55 MHz) while the narrow filter selected is 35 MHz
(centered at 41.95 MHz). The guardband is set at 0.25 MHz. The ensuing signal
quality during mixed mode transmission then has a 0.1% correctable forward error
correction (FEC) rate.
Multiple IUC TLV support

Multiple Internal Usage Code (IUC) TLV 46.11 is now sent by the CMTS with the
REG-RSP-MP messages to D3.1 cable modems supporting multiple IUCs over
OFDMA channels.
When the CMTS assigns multiple OFDMA Upstream Data Profile (OUDP) IUCs to
the original OFDMA channel, the CMTS includes TCC Encoding TLV 46.11 with
action "change" for the OFDMA channel in the REG-RSP message to the cable
modem. After the modem registers with the TLV, the CMTS select the best IUC to
use on the channel based on codeword error rate and channel SNR.
IUC 13 (lower modulation) is the default which is used if an OFDMA channel is

ranged after the modem has registered. If the SNR is satisfactory for the other IUC's
modulation, then the CMTS will switch the channel to the other IUC with the higher
modulation. If the uncorrected error rate is then higher than the acceptable packet drop
threshold, the CMTS switches the channel back to the lower modulation with IUC 13.
If the SNR and FEC values are both high, possibly causing "flapping" between
modulation rates, a 15-minute switching delay period is built in to allow the SNR to
resolve itself before making (or not making) a switching change.
The multiple-iuc command has been introduced in the CLI OFDMA context to
enable the multiple IUC configuration.

Example
CASA(conf-ofdma-channel 11/1.0)# multiple-iuc ?
<cr>
err-threshold uncorrectable packet rate threshold to switching
iuc to lower modulation
interval multiple iuc switching interval
max-retry max attempt number of switching between iuc
The following command enables the CMTS to send multiple Internal Usage Code
(IUC) TLV 46.11 REG-RSP-MP messages to D3.1 cable modems supporting multiple
IUCs over OFDMA channels. Apply the no form of the command disable the
multiple-iuc setting. The multiple-iuc setting is disabled by default.
Example
CASA(conf-ofdma-channel 11/1.0)# multiple-iuc
CASA(conf-ofdma-channel 11/1.0)# no multiple-iuc
The optional multiple-iuc parameters are as follows:
err-threshold <1:999> — Specifies the uncorrectable packet rate threshold to trigger

switching the IUC to a lower modulation rate, specified in 0.1 percent intervals (to
provide granularity at lower percentages). The default is 20, or 2%.
interval <1:200> — Specifies the number of recurring IUC ranging intervals to wait
before making the next considered IUC change. Each ranging interval is a 10-second
period. The default setting is 6 switching intervals, or 60 seconds before making the
IUC change to another modulation profile. Setting the interval parameter to a higher
setting will result in less frequent IUC changes. The regular 10-second ranging
interval checking resumes after the completing the last IUC change. The next IUC
change being considered restarts the waiting period (i.e., the configured number of
intervals) before completing the IUC change.
max-retry {<2:200> | unlimited>} — Maximum IUC switching retry attempts before

making a dynamic bonding change (DBC) to substitute another data-iuc contained in
the iuc-profile defined for the OFDMA interface. The default setting is unlimited
retry attempts.
Example
CASA(config)# interface ofdma 11/1.0
CASA(conf-ofdma-channel 11/1.0)# multiple-iuc err-threshold 100
CASA(conf-ofdma-channel 11/1.0)#

1-18 Release Notes
Monitoring OFDMA in SNMP

Release 7.2 supports OFDMA in the DOCS-IF31-MIB. See the Casa Systems –
SNMP MIBs and Traps Reference for information.
IPv6 Provider Edge routers (6PE) in BGP

Support has been added for IPv6 Provider Edge Routers (6PE) in BGP routes, as
defined in RFC4698. 6PE routers are dual stack in order to connect to IPv6 islands and
to the MPLS core, which is only required to run IPv4 MPLS. The 6PE routers
exchange the IPv6 reachability information transparently over the core using the
Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4.
The implementation allows for a single 6PE Autonomous System (AS) and supports
prefix delegation for IPv6 address assignment.
The following commands and functions support 6PE:
• address-family ipv6 labeled-unicast

• [no] address-family ipv6 labeled-unicast
• show ipv6 bgp labeled-unicast
• show ipv6 bgp labeled-unicast summary
• show ipv6 bgp labeled-unicast XX::XX/len
• show ip bgp neighbors A.B.C.D
NetFlow V9 traffic flow monitoring

Support has been added for NetFlow V9 network traffic flow monitoring. NetFlow
provides the ability to collect IP network traffic as it enters or exits an interface. By
analyzing the data, a network administrator can determine such things as the source
and destination of traffic, class of service, and the causes of congestion. A network
flow is a unidirectional stream of packets identified as the combination of factors. Any
one of the following factors being different defines the flow as unique:
• Source and destination IP address

• IP protocol
• Source and destination port number

CMTS Release 7.2.4.2 software installation
• Type of service (ToS)

• Ingress interface (SNMP IfIndex).
The Casa NetFlow implementation is based on NetFlow Version 9, described in RFCs
7011 and 7012. Version 9 is template-based and complies with IPv6 as well as IPv4
addressing. NetFlow information collection is turned on and off on individual IP
bundle interfaces only.
One sampler MAP and one exporter map are supported per CMTS, with one data
template each for IPv4 and IPv6. Each line card is both an observation domain and an
export device. Only UDP transport is supported. NetFlow depends on a sampling rate.
The Casa minimum sampling rate is defined as one packet out of one thousand
packets.
The following commands have been added to support NetFlow monitoring:
• [no] flow exporter-map <name> — Source loopback and destination addresses

and port definitions, template timeouts, and transport definitions, with
accompanying show command.
• [no] flow monitor-map <name> — Protocol, exporter name, and cache timeout
definitions, with accompanying show command.
• [no] flow sampler-map <name> — Sampler rate definition, minimum one per
thousand packets, default 1024, maximum 10000 packets, with accompanying
show command.
• Flow ingress and flow egress definitions applied to the IP bundle interface.

Version 7.2.4.2 distribution image
The following CMTS software images for Release 7.2.4.2 are available from the Casa
Systems FTP site.
Release image: ccsi.gz.rel7.2.4.2_build59e9 — (For C10G, C40G, and C100G

systems running the QAM 8x96 module.)
MD5 checksum: 572455128cd07553c1f06ff2101907d6

1-20 Release Notes
From your Web browser, log on to the site using your Casa Systems-assigned
customer user name and password at ftp://support.casa-systems.com.
From Unix or Linux systems, run FTP and log in to casa-systems.com.
SNMP MIB archive: mibs-rel7242b5861-20170815.tar
Software update procedures

This section covers the procedures for updating the CMTS application image with
Release 7.2.
Verify any previously-installed software patches

Use the show patch command to determine if any patches have been applied on the
system. Perform the following steps:
1. Execute the show patch command to verify that a patch has been applied and running
at the CMTS.
Example
CASA# show patch
Size Created on Status Patch name
--------- ------------------------ -------- ------------------------------------
3544158 Mon Dec 7 11:48:06 2015 active p####.tgz
PEER SMM VERSION:

--------- ------------------------ -------- -----------------------------------
3544158 Mon Dec 7 11:48:10 2015 active p####.tgz
2. If a software patch is present, proceed to verify the boot loader image versions and
then install the Release 7.2.4.2 software image. After successfully installing R7.2.4.2,
remove the software patch as covered in the section, “Reverting a previously-installed
software patch.”
Verifying the minimum boot loader firmware images

Use the show system command to verify the minimum boot loader firmware revisions
for the C10G, C40G, and C100G hardware modules. The boot loader images are
reported by the CFE version in the show system command output.

For Release 7.2
• SMM 8x10G — CFE Version 12.4.11

• SMM 2x10G — CFE Version 12.4.11
• QAM 8x192 — CFE Version 2.2.5
• UPS 16x4 — CFE Version 12.4.11
• UPS 16x8 — CFE Version 12.9.13
If the show system command reveals that you are running an earlier CFE version for
any one of the listed modules, contact Casa Technical Support for assistance in
updating one or more boot loader images to the current version.
Preserving the current software image

Prior to performing an upgrade to a new R7.2 software image, Casa recommends
copying the existing startup configuration file (prior to R7.2) to a separate file for
future use in situations where reverting to R7.1 (or prior release) may be necessary.
This will allow the system to boot up to the earlier image without having to
reconfigure the software.
Perform the following steps:
1. Before upgrading to a new release, copy the startup-config file to a separate file to
preserve the software image.
Example
CASA# copy nvram startup-config nvram <filename>
2. Perform the software upgrade to R7.2, as covered in the next section, “Updating
the application image.”
Note that this is also a general procedure which can be applied to all software releases.
See the section, “Reverting to a prior software release” for information on rolling back
software versions.

1-22 Release Notes
Updating the application image

To update the application image, first download the image from the Casa FTP server
to the TFTP server. The supported C10G/C100G storage device is nvram
(non-volatile RAM).
1. To perform an update from the TFTP server:

CASA-CMTS# copy tftp <host-ip> <image> <device>
Where:
• <host-ip> is the IP address of the host where the update image is stored.
• <image> is the name of the software image stored on the remote system.
• <device> is the software storage device. On the C10G and C100G platforms,
the storage device is nvram.
Example
CASA-CMTS# copy tftp 192.168.3.10 ccsi.gz.rel7.2.4.2_build59e9
nvram
2. Save the running configuration using the copy running-config startup-config

command.
Example
CASA-CMTS# copy running-config startup-config
3. Execute the md5 checksum command to verify that the software image
transferred to the system successfully and without error. The MD string must
match the string associated with this software release.
CASA-CMTS# md5 checksum ccsi.gz.rel7.2.4.2_build59e9
572455128cd07553c1f06ff2101907d6 ccsi.gz.rel7.2.4.2_build59e9
4. Next, set the boot device and then reboot the system. When the CMTS completes
the series of boot-up processes, execute the show version command to verify the
new software installation.
Example
On the C10G, C40G, or C100G, update the application image
ccsi.gz.rel7.2.4.2_build59e9 file from host 192.168.3.10 to NVRAM:
CASA-CMTS# system bootdev nvram ccsi.gz.rel7.2.4.2_build59e9
CASA-CMTS# system reboot

CASA-CMTS# show version

Running Image: SMM_8x10G Rel 7.2.4, Ver #,build####, Fri Sep 22
17:19:36 EDT 2014,(relmgr)
Configured boot device: nvram
Image booted from: nvram, File name: ccsi.gz.rel7.2.4.#_build####
Casa RMI_BootLdr: Major ##, Minor # Build ##
Note: If a software rollback is necessary, see the section “Reverting to a prior

software release.” If the rollback software version involves a patch installation,
refer to the specific Casa-supplied instructions provided with original patch
release for patch re-installation.
Reverting a previously-installed software patch

Perform the following steps to revert any previously-installed software patches:
1. Execute the show patch command to verify that a patch is present on the system and
in the “disabled” state.
Example
CASA# show patch
--------- ------------------------ -------- ------------------------------------
3544158 Mon Dec 7 11:48:06 2015 disabled p####.tgz
PEER SMM VERSION:

--------- ------------------------ -------- -----------------------------------
3544158 Mon Dec 7 11:48:10 2015 disabled p####.tgz
2. Revert the previously-installed patch file using the system patch revert command.
Example
CASA# system patch revert
Reverting slot 0..1..2..3..4..5..6..7..8..9..10..11..12..13..
The patch is removed.
Note: Once R7.2.4.2 is confirmed for service, delete the patch file from the
system using the remove patch command. This can be done at any time.
Leaving the inactive patch file on the system does not impede the system in
any way.
Example:
CASA# remove patch p###.tgz

1-24 Release Notes
Resolved issues and changes in Version 7.2

The following tables provide the Casa tracking IDs and descriptions of the product
changes, enhancements, and fixed issues that have been applied in recent Version 7.2
software builds. For the complete listing and descriptions of all new features and
enhancements, see the Casa Systems – CMTS Release 7.2 Features Guide.
Table 1. Release 7.2.4.2 Build 59e9 changes and applied fixes
Tracking Service impact Description

ID (Risk level)
81356 Defect: A software fix has been applied to correct an issue where authentication key
Possible service strings from prior releases which used a certain null pattern were not being
impact properly decoded in Release 7.2.4.
(Medium)
81296 Defect: A software change has been applied to ensure that certain specific D3.0
Possible service modems which are susceptible to malformed packets are able to complete
impact registration with the CMTS. Modem flaps were previously observed and the
(Medium) affected modems were not able to come online.
Table 2. Release 7.2.4.2 Build 58b9 changes and applied fixes

ID (Risk level)
78287 Defect: A fix has been applied to correct a previously documented issue where
Possible service changing the QAM channel configuration could result in modems unable to
impact maintain lock on the affected channels with modems going offline or into
(Medium) downstream partial service. Channels would recover after performing channel
or port shutdown/no shutdown. The problem was isolated to an issue with
the reset logic between the MPEG engine and the Annex encoder.
78731 Defect: A problem which was causing the interface logical channel description to be
No service dropped after an SMM switchover has been fixed. Previously, the console print
impact error log message “ER-CFG-1: smm6: if_data_entry_set():3137: pid = 6140,
(None) tid = 6140, err = no such entry” was observed.
79185 Defect: An issue was observed where the QAM 8x96 module did not recover after
Possible service being rebooted. A timing race condition which resulted in a stale state
impact detection at the time of the recovery was the cause of the problem. A
(Low) correction has been applied to ensure detection of the proper state when the
module is recovering after a reboot.

Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes

ID (Risk level)
71937 Defect: There was an issue during module startup which could result in an incorrect
Possible service PCR clock value. This problem has been fixed.
impact
(Medium)
77176 Enhancement: The casaModuleDataCpuUtilizationTable has been added to the
SNMP CASA-ENTITY-MIB to allow SNMP users to query QAM or UPS utilization
(Low) statistics for all CPU processes running on the specified line card.
New MIB objects:
casaModuleDataCpuUtilizationTable (.1.2)
casaModuleDataCpuUtilizationEntry (.1.2.1)
casaModuleDataCpuUtilizationMin (.1.2.1.1)
casaModuleDataCpuUtilizationAvg (.1.2.1.2)
casaModuleDataCpuUtilizationMax (.1.2.1.3)
Example:
***** SNMP QUERY STARTED *****
1: casaModuleDataCpuUtilizationMin.302 (gauge) 0
2: casaModuleDataCpuUtilizationMin.1102 (gauge) 0
3: casaModuleDataCpuUtilizationAvg.302 (gauge) 0
4: casaModuleDataCpuUtilizationAvg.1102 (gauge) 21
5: casaModuleDataCpuUtilizationMax.302 (gauge) 0
6: casaModuleDataCpuUtilizationMax.1102 (gauge) 410
***** SNMP QUERY FINISHED *****

1-26 Release Notes
Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes (continued)

ID (Risk level)
77227 Enhancement: The show cpuinfo module <number> command has been revised to retrieve
CLI, SNMP QAM or UPS utilization statistics for all CPU processes running on the
Informational specified line card. CPU utilization statistics are reported as minimum,
average, and maximum percentages.
The equivalent objects in the CASA-ENTITY-EXT-MIB are:
• casaModuleDataCpuUtilizationTable
• casaModuleDataCpuUtilizationEntry
• casaModuleDataCpuUtilizationMin
• casaModuleDataCpuUtilizationAvg
• casaModuleDataCpuUtilizationMax
Example:
CASA> show cpuinfo module 12
Module 12:
cpu model XLS616 Rev B1 V0.3
BogoMIPS 134.52
microsecond timers yes
tlb_entries 64
00:45:15 up 2 days, 5:26, 0 users, load average: 16.18,

16.13, 16.09
115 processes: 114 sleeping, 1 running, 0 zombie, 0
stopped
CPU states: 0.0% user, 0.4% system, 0.0% nice,
99.6% idle
D-CPU utilization(Min/Avg/Max) (13%/68%/95%)
Mem: 949336K total, 434516K used, 514820K free,
82772K buffers
77237 Defect: Traceroute elapsed time calculations have been reinstated in the software to
No service ensure that an issued traceroute is able to time out successfully. The fix
impact corrects a problem which was causing traceroute to run continuously and not
(Low) terminate without user intervention.


ID (Risk level)
77247 Defect: After a redundancy switchover to SMM7, loopback interfaces on the C100G
Possible service were no longer reachable. The problem was traced to an issue which was
impact causing the next hop router to incorrectly install an ARP address instead of the
(Medium) C100G loopback address. A software change has been applied to ensure
consistent behavior between the active and standby SMM interfaces where the
sender IP field in ARP packets is the outgoing interface IP address.
77297 Defect: An internal FIFO buffer allocation issue which could cause the upstream
Possible service process to lock up under certain conditions has been fixed.
impact
(Medium)
77322 Defect: A channel count calculation logic error in the QAM 8x96 which was affecting
Possible service video streams in certain frequency ranges with lower than expected channel
impact power has been fixed.
(Medium)
77487 Defect: An IPDR issue has been observed where the ds-util-stats template "DsChId"
No service field is being set to 0 indicating that secondary downstream channel ID
impact information is not being passed to QAM. A software fix has been applied to
(Low) ensure fetching of the channel ID for the downstream secondary channels in
IPDR records.
77502 Defect: A software change has been applied to ensure broadcast of RIPv1 and RIPv2
Possible service unicast packets from the CMTS to the IP bundle secondary IP addresses. The
impact change corrects a reported problem where CPE devices could not receive
(Low) RIPv1 update packets from the CMTS.
77546 Defect: A problem which was preventing IGMPv3 multicast join sessions on the
Possible service upstream in situations where the number of multicast sources drops to 0 has
impact been fixed.
(medium(
77559 Defect: A series of code changes have been implemented to enhance the reliability of
Possible service the in-service patch capability for CMTS platforms. Previously reported issues
impact associated with applying and reverting software patches have been addressed
(Medium) in Release 7.2.4.2. The prior issues include correct reporting of patch status,
unexpected module switchovers, and overall performance improvements to
reduce patch installation time.
77560 Defect: Checks have been implemented in the software to ensure that configured
Possible service shared channel transport stream IDs are properly reset when the number of
impact narrowcast channels has been changed. Previously, the message “Error: tsid
(Low) <number> has already been configured in qam channel slot/port/channel” was
observed after increasing the number of narrowcast channels on the QAM
port.

1-28 Release Notes

ID (Risk level)
77575 Enhancement. The dva parameter has been added to the interface ip-bundle
Operational, CLI cable-helper-ipv6-address command to enable forwarding Digital Voice
(Low) Adapter (DVA) broadcasts only.
DHCPv6 packets which contain device type suboption(2) EDVA or EMTA

device will be forwarded to specified server, if present.
Example:
CASA(ip-bundle 1.1)# cable helper-ipv6-address
2001:20:158::6 dva
77621 Defect: A software change has been applied to ensure compatibility with the CVEX
Possible service EDIS SRM. Previously, the CVEX was rejecting the Casa video configuration
impact file export due to an incompatible “Modulation='QAM-256'” parameter. When
(Low) the EDIS SRM type configuration is set to bbnd-cvx, the correct
“Modulation=256” parameter will now be applied in the video export
configuration file.
77813 Enhancement. The maximum number of supported DSG vendor parameter IDs has been
Operational increased to 48 to support customer requirements. Previously, the CMTS
(None) configuration supported a maximum of 32 DSG vendor parameter IDs.
Example:
CASA(config-if-qam 0/0)# channel 1 dsg vendor-param-id 48
78001 Defect: A possible race condition at line card startup which was preventing the ability
Possible service to perform subsequent module switchovers has been fixed. The problem was
impact traced to a process flag which was incorrectly being dropped while the line
(Medium) card was coming up.
78025 Enhancement: The configured Privacy Mode Encryption (PME) device ID and password have
CLI been added to the show running-config command output.
(None)
Example:
CASA(config)# video pme device-id pme password pme
CASA(config)# show run | in device-id
video pme device-id 2 c67b1a0a29a72bca password 2
c67b1a0a29a72bca
78147 Defect: A case was reported where duplicate/stale VPWS labels were observed in
Possible service show mpls vpws and show ldp command output after performing an SMM
impact switchover. A software fix has been applied to ensure that LDP allocates new
(Medium) labels with no label overlaps after an SMM switchover.


ID (Risk level)
78164 Defect: After an SMM switchover initiated with ha module 6 protect command, an
Possible service SNMP user’s MD5 authentication string and the no-priv value were incorrectly
impact changed. A fix has been applied to ensure that the original settings are
(Medium) preserved with an SMM switchover.
78203, Defect: A software change has been implemented to correct a problem which could
78207 Possible service result in some modems dropping off line after interactively editing certain QAM
impact 8x192 configurations. The software change ensures that QAM configuration
(Medium) changes are correctly applied.

ID (Risk level)
68330 Defect: FPGA overflow messages have been observed after re-configuring QAM
Possible service 8x192 parameter settings, and in some cases, after adding QAM 8x192
impact channels. A fix has been implemented and the previous workaround is not
(Medium) longer necessary.

1-30 Release Notes

ID (Risk level)
72721 Defect: A problem which was causing SDV service outages due to abnormal PCRs in
Possible service video streams has been addressed in this software build.
impact
(Medium) PCR abnormal value detection has been added to the health check logic in the
QAM process to detect differences between FPGA PCR values. Detected
differences of 100 and larger over 45 KHz will result in an abnormal PCR with
a resulting QAM auto switchover, if so configured. This feature applies to the
QAM 8x96 and QAM 8x192 modules.
When auto switchover is not enabled, check the video volatile log for
messages pointing to FPGA PCR mismatches.
To turn on the recovery (auto switchover) for a detected PCR timing error on
the QAM 8x96 module, add 400 to the first bitmap.
Example:
CASA(config)# ha hardware qam8x96 recovery ef0004e7
self-recover e80000a7
CASA(config)# show ha config

ha hardware qam8x96 recovery ef0004e7 self-recover
e80000a7
ha hardware qam8x192 recovery ef0000e7 self-recover
e80000a7
To check the configuration, issue the following CLI command:
CASA# show ha hardware qam8x96 recovery

Bit Recovery Self-recover HW Error Condition
-------- -------- ------------ -------------------
00000001 On On DUC FIFO UNDERRUN
00000002 On On DUC FIFO OVERRUN
00000004 On On DUC/DAC PARITY ERROR
00000008 Off Off DUC/DAC LOCK ERROR
00000010 Off Off SEU UNCORRECTABLE_ERROR
00000020 On On FPGA 128MHZ LOCK ERROR
00000040 On Off DUC SPI ERROR
00000080 On On FPGA DDR PARITY ERROR
00000100 Off Off SEU CORRECTABLE ERROR
00000200 Off Off SEU CONTROLLER HEARTBEATERROR
00000400 On Off PCR CLOCKING ERROR


ID (Risk level)
76030 Defect: A fix has been applied to avoid a possible race condition and resulting IPDR
Possible ser- failure when IPDR exits at system reboot.
vice impact
(Medium)
76520 Defect: A software logic error which could cause the SMM to switch over, or reboot (in
Possible service the case of no SMM redundancy protection) during concurrent processing of
impact upstream and downstream DBC has been fixed. The issue was caused by a
(Medium) timing error when the QAM module returns the DBC response later than UPS
module.
76522 Defect: An error in the software logic which could affect the recovery of multiple
Possible service processes at the time of an SMM switchover has been fixed. A correction has
impact been made to prevent a possible looping condition as multiple processes
(Medium) recover. The console log message “soft_timer_control_tick: (mac timer)
detected corrupted timer (xxxxxxx)” indicates the error.
76568 Defect: An error in the IPDR connection logic which resulted in an IPDR process
No service restart and SMM switchover with no impact to service has been fixed. The
impact problem occurred in a situation when IPDR was closing an existing connection
(Low) between the collector and the CMTS.
76580 Defect: A software logic error was causing the ACL rule deny6 sunrpc to incorrectly
Possible service match legitimate IPv6 packets. This issue resulted in routed packets being
impact blocked when establishing the CMTS connection with the peer router. This
(Medium) problem has been fixed.
76664 Defect: An error in the software logic which could cause VPWS CP/VP label entries
Possible service between the active and standby SMMs to go out of synchronization has been
impact fixed. The problem was resulting in missing VPWS entries on the standby
(Medium) SMM. Logic checks have been implemented in the software to ensure
synchronization when VPWS entries are added and deleted.
77039 Defect: Handling of emergency 911 call types has been revised for proper
No service classification in downstream service flows for PacketCable voice. The software
impact change now gets the 911 call type for admission control into PacketCable
(Low) flows.
77040 Defect: A problem which could prevent D3.0/D3.1 modems from completing
Possible service registration and coming online in situations where the downstream channel is
impact changed (via DBC) while modems are registering with the CMTS has been
(Low) fixed. Handling of the transmit channel configuration (TCC) has been revised
so that modems complete ranging and come online with the CMTS on the
original downstream channel.

1-32 Release Notes

ID (Risk level)
77071 Defect: Calculation of the CLI-provisioned QAM port power and the actual power at the
Possible service port egress has been revised so that detected power losses (greater than
impact 6 dB) in the QAM module’s RF path do not result in a QAM module reboot.
(Medium) Previously, the message "QAM LINE CARD POWER LEVEL ERROR” was
observed in certain QAM 8x96 configurations where the module would go into
a rebooting loop after performing a no shutdown on a QAM channel.
77072 Defect: A problem which was causing SAMIS-1 IPDR sessions between the CMTS
No service and a certain IPDR collector to get stuck due to uninitialized service flows has
impact been fixed. The problem was traced to a discrepancy between the SAMIS-1
(Low) session creation time and the IPDR collection period.
77084 Defect: A QAM channel reference count has been observed as a negative value with
No service the show interface qam xx/nn block command. The count error could occur
impact after a QAM module reboots where the reference count incorrectly changed to
(Low) 0 before completing the startup configuration. This problem has been fixed.
Table 5. Release 7.2.4.1 Build 555c changes and applied fixes

ID (Risk level)
71862 Defect: A problem which could prevent a D3.1 modem from ranging and coming online
Possible service with the CMTS over an OFDMA/TaFDM channel has been fixed. The problem
impact was caused by an error in the software logic which resulted in an incorrect
(Medium) initial ranging timing offset for the modem.
Table 6. Release 7.2.4.1 Build 54da changes and applied fixes

ID (Risk level)
68400 Defect: An error in the FPGA logic which could result in a timing calibration issue after
Possible service a system or module boot-up has been fixed. The problem could result in an
impact occasional service interruption over QAM 8x192 video streams across shared
(Medium) channels.

Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes

ID (Risk level)
67145 Defect: A problem was observed in earlier R7.1 releases where enabling a
Possible service QAM 8x192 OFDM channel resulted in a power drop of approximately 3 dB
impact per SC-QAM channel on the QAM port. This problem has been fixed.
(Low)
67545 Defect: Large timing offsets have been observed on OFDMA upstream bonded
No service channels after recovery from the partial service state. The problem was
impact caused by OFDMA incorrectly using the SC-QAM channel timing offset instead
(Low) of the OFDMA channel timing offset calculation. This issue has been fixed.
67894 Defect: An error in the software logic which could prevent downstream bonding-groups
Possible service from being configured successfully has been fixed.
impact
(Low)
68910 Defect: A software fix has been applied to correct possible duplication of program
Possible service identifiers (PIDs) in multi-source SDV input streams.
impact
(Low)
68923 Defect: A software fix has been applied to address a problem where high priority LACP
Possible service packets were contending with lower priority control traffic. To correct the
impact problem, all control packets sent from the standby SMM to the active SMM will
(Medium) now retain their initial priority derived on the standby SMM.
Before this change, all non-queue 0 (Best effort) control packets would be
mapped to queue 7 when sent to the active SMM. This caused all priority
levels to have contention when sent to the CPU on the active SMM. For
example, LACP packets (queue 6) will now be mapped to queue 6 on the
active SMM regardless of whether the packets are initially received on the
standby SMM or active SMM.
68929 Defect: An issue with the PCR drift correction logic which caused the output PCR to be
Possible service out of the range has been fixed.
impact
(Low)
69014 Defect: A software change now enables the CMTS to check the length of MPLS
Possible service encoding TLVs from the modem configuration file in registration request
impact packets. A problem where a modem attempted to register and come online an
(Medium) incorrect MPLS peer TLV length caused an SMM switchover to the redundant
standby. Registration requests containing MPLS TLVs of incorrect length are
now ignored.

1-34 Release Notes
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)

ID (Risk level)
69194 Defect: A coding error which could cause D3.0 modems to go into the partial-service
Possible service state and D2.0 modems to drop offline and not re-register with the CMTS has
impact been fixed. The problem was observed after re-assigning channel frequencies
(Medium) on the UPS 16x4 module where the affected channels became unusable.
Resetting the UPS 16x4 module allowed D3.0 modems to recover from the
partial-service condition, with D2.0 modems registering and coming online.
69200 Defect: A software fix has been applied to correct a problem where transport stream ID
Possible service (TSID) was not being configured correctly for channels 36 to 47 on the QAM
impact 8x96.
(Medium)
69257 Defect: A software fix has been applied to correct an inconsistency between the active
Possible service and standby SMMs where IPv6 xGigE interfaces were being enabled on the
impact standby SMM and not the active SMM. The fix ensures that IPv6 interfaces on
(Low) both the active and standby SMMs are enabled with the configured link-local
address.
69259 Defect: A software change has been implemented to address situation where
Possible service increased memory consumption under certain conditions could cause a line
impact card module to reboot. A problem was observed where the UPS 16x4 module
(Low) in a non-redundant line card configuration rebooted during processing and
collection of statistics. The software change increases the available memory to
prevent the line card reset.
69479 Defect: A software issue which could result in a BGP failure after deleting the VRF
Possible service route distinguisher (RD) has been fixed. The problem was caused by a pointer
impact which continued to make attempts to access the route table associated with
(Low) the deleted RD.
69551 Defect: Support for the “all” protocol option has been reinstated in ACL permit and
Possible service deny rules in the configuration.
impact
(Low)


ID (Risk level)
69633 Feature: The symbols-per-frame command has been added to Casa CLI in the
No service interface ofdma configuration context to warn users if the configured symbol
impact per frame or number of init/fine ranging subcarriers is too small.
(Low)
The following recommended OFDMA ranging slot settings are based on
symbol rate. Ranging slots settings in number of subcarriers can be changed
in ofdma iuc profile.
Note that the number of fine ranging carriers larger than 64 not be used as it
may cause fine ranging failures. This also means symbol per frame number
less than 10 should NOT be used.
Recommended settings:
Symbol Initial Fine

per frame Ranging Ranging
6 64 192
7 64 192
8 64 96
9 64 96
10 64 64
11 64 64
12 32 64
13 32 64
14 32 64
15 32 64
16 32 32
Example:
symbol per frame 6 requires at least 16 initial ranging
minislots in IUC profile
warning: symbol per frame is too small

1-36 Release Notes

ID (Risk level)
69673 Enhancement: The cable modem deny list capacity has been increased to 2048 cable modem
CLI, Operational MAC address entries. Previously, the maximum number of supported entries in
(Low) the list was 512. The cable modem deny command specifies the MAC
address of a cable modem which is prohibited from registering with the CMTS.
Example:
CASA(config)# cable modem deny 0001.0001.2043
set black cm to database failed!
CASA(config)#
CASA(config)# show running-config | count-only "modem

deny"
Wed Mar 8 03:59:58 UTC 2017
Count Line: 2048
CASA(config)#
69685 Defect: A memory leak issue which could prevent CPEs from joining multicast
Possible service sessions has been fixed. The problem was caused by an error in the software
impact logic which was preventing DBC information for the modem from being freed
(Low) where DBC counts were not decreasing.
69831 Enhancement: Support has been implemented to enable PacketCable and PCMM to run over
Operational, CLI multiple VRF instances. Previously, the CLI would only allow one VRF instance
(Low) to handle all PacketCable and PCMM connections. Multiple named VRFs can
now be created under the packetcable configuration in the CLI to allow users
to separate voice and PCMM multicast traffic.
69837 Enhancement: A timing delay has been applied when recovering channels in partial service to
Operational prevent modems from reporting CM-STATUS failure/recovery events. The
(Low) partial service update now occurs after the CM-STATUS message indicates a
recovery.
If the modem reports a failure across all profiles on an OFDM channel, the
channel is now marked as unusable instead of using Profile A.


ID (Risk level)
69890 Defect: A problem which was causing the ACL rule deny sunrpc any any to block
Possible service OSPF adjacency packets has been fixed. The software now checks the ACL
impact rule for the source/destination port. If the source/destination port is present,
(Medium) non TCP/UDP packets will not be blocked.
70676 Defect: Improved signaling between the QAM module and the SMM has been
Possible service implemented to prevent possible video session timeouts when performing a
impact QAM module switchover. The SMM will now signal the QAM process when the
(Medium) QAM switchover has completed for resumed handling of the video stream and
to avoid possible video session timeouts.
70786 Defect: A software fix has been applied to ensure correct reporting of the “Server Last
No service Time Up” statistic presented with the show video simulcrypt ecmg
impact command. Previously, incorrect time statistics were present in the output
(Low) before an ECMG connection with the CMTS was ever established. The output
now reports N/A in this case.
70798 Defect: An error in the SNMP process logic which could corrupt the resulting OID
No service string size and cause an SNMP failure to decode excessively long OID strings
impact at the time of an SNMP query has been fixed.
(Low)
70834 Defect: A software fix has been applied to ensure correct reporting of OFDMA traffic
No service and channel utilization statistics in SNMP queries. Previously, SNMP queries
impact to the ifHCInOctets object were reporting statistics which were lower than the
(Low) actual number of octets received on the OFDMA interface.
70888 Enhancement: The show bonding-group utilization command now provides the application
No service class child identifier in the App-Class-Id column. Child IDs are in the format
impact #.#, as shown in the partial sample output below:
(Low)
Example:
CMTS(config)# show bonding-group utilization
Mac GroupID App-Class-Id Total BW(kbps) Used BW(kbps).
2 - 1.1 102865 0 0
2 - 1.2 102865 0 0
2 - 1.3 102865 0 0
2 - 1 102865 0 0
71062 Defect: When operating the QAM 8x192 with two OFDM channels, a difference was
Possible service observed in spectrum output levels between D3.0 (SC-QAM) and D3.1
impact (OFDM) channels when using the same RF configuration on the DS
(Medium) connectors. This issue has been fixed.

1-38 Release Notes

ID (Risk level)
71195 Defect: After performing an SMM switchover, cable flap-list traps were being
No service forwarded to the trap host even when the traps were disabled in the
impact configuration. The problem was traced to an incorrect pointer in the software.
(Low) The problem has been fixed.
71196 Enhancement: The number of supported PacketCable COPS servers has been increased
No service from 64 to a maximum of 128.
impact
(Low)
71261 Defect: A problem was reported where RADIUS authenticated users were not being
No service granted sufficient command privileges at the CMTS with a valid AAA
impact configuration. The problem has been fixed.
(Low)
71529 Defect: A high latency issue has been observed with Best Effort (BE) service flows in
Possible service RFoG mode when channel utilization is high, but with channels not being fully
impact saturated and with cable modems not being able to use the remaining
(Low) bandwidth on the channel.
A software change has been applied to the upstream RFoG scheduler which
now scales the grant size using the number of channels on the RFoG group so
the outstanding bytes will fill all granted space on the upstream channel.
71604 Defect: On the QAM 8x8 module with channel frequencies greater than 300 MHz, DS
Possible service frequencies greater than 860 MHz in the configuration were being reverted
impact back to the channel frequency default setting on some QAM ports after
(Low) performing a system reboot. This problem has been fixed.
71605 Defect: When configuring a QAM 8x192 downstream port from 16 channels to 32
Possible service channels, DS power level per port was being decreased by 3dB. This problem
impact has been fixed.
(Low)
71621 Defect: An SNMP issue was observed with the show snmp statistics command
No service output where the expected snmpOutPkts and snmpOutTraps statistics were
impact not increasing. A fix has applied to ensure that counts increase correctly.
(Low)
71629 Defect: After performing an SMM switchover, and if the router ID was not configured,
Possible service connected routes for video interfaces inside a VRF were sometimes not being
impact redistributed. This problem has been fixed.
(Low)


ID (Risk level)
71919 Defect: Missing PMTs associated with pre-encrypted MPTS video broadcast
Possible service pass-through streams have been observed. A software change made to
impact correct this problem and also the default behavior is changed so that ghost-pid
(Low) and reserve-pid are not dropped for pass-through sessions.
71961 Defect: When the OFDM profile-modulation is configured to 1024 QAM or 2048 QAM
No service modulation, the throughput reported in SNMP queries to the IF-MIB
impact ifHCOutOctets is lower than expected on OFDM channels. This problem has
(Low) been fixed.
71964 Enhancement: The casaInetCidrRouteTable object has been implemented in the
SNMP CASA-IP-FORWARD-MIB to support IPv4 and IPv6 reporting of subnet and
(Low) VRF route statistics in SNMP queries.
71974 Defect: Missing or inaccessible next hop VRF routes have been observed after a
Possible service performing a system reboot or SMM switchover where BGP next hop lookups
impact are deemed invalid, with BGP unable to select the next hop in the BGP path
(Medium) selection with eventual lost routes.
71982 Defect: The casaDevSoftwareMib has been removed from the SNMP MIB archive in
No service Release 7.2.4.1 to prevent possible security vulnerabilities at the CMTS.
impact
(Medium)

1-40 Release Notes

ID (Risk level)
72066 Feature: SNMP traps are now generated at the Casa C40G platform when the system
CLI, SNMP fan tray is removed or installed.
(Low)
The fanTrayInsertion and fanTrayRemoval MIB objects have been added to
theCasaSysMonNotificationType trap in the CASA-SYS-MON MIB file.
Example: CLI
CASA# show log
[Mon Apr 18 10:08:23 2016]-AL-SYS-1: smm2: Fan tray
(right) is inserted
[Mon Apr 18 10:07:40 2016]-AL-SYS-1: smm2: Fan tray
(right) is pulled out
Example: SNMP:
Binding #7: casaLogMessage.92 *** (octets) Fan tray
(right) is pulled out
[46.61.6E.20.74.72.61.79.20.28.72.69.67.68.74.29.20.69.73
.20.70.75.6C.6C.65.64.20.6F.75.74 (hex)]
Binding #7: casaLogMessage.93 *** (octets) Fan tray

(right) is inserted
[46.61.6E.20.74.72.61.79.20.28.72.69.67.68.74.29.20.69.73
.20.69.6E.73.65.72.74.65.64 (hex)]
72145 Defect: A fix has been implemented to address a possible security vulnerability at the
No service CMTS. Additionally, encryption algorithm updates to the OpenSSL library have
impact been applied to close security vulnerabilities. OpenSSL Version 1.0.2d is
(Medium) presently implemented in Release 7.2.4.2.
72160 Defect: Software and timing changes have been applied to the QAM switchover
Possible service processes to prevent situations where modems could possibly lose lock on
impact OFDM channels during a QAM 8x192 module switchover. A problem was
(Low) observed where some modems on OFDM channels would go into
partial-service and remain locked on SC-QAM channels after the switchover.


ID (Risk level)
65444 Defect: A software error which affected handling of the 32-port numbering scheme on
Possible service the UPS 16x8 with the 32-port I/O module has been fixed. The error resulted in
impact some of UPS ports being unavailable for modems to register and come online
(Low) with the CMTS while other ports were unaffected.
67558 Defect: On QAM 8x192 ports which have OFDM channels configured, performing a no
Possible service shutdown to enable a port which was already enabled incorrectly caused the
impact port to shutdown. A software change has been applied to check the current
(Low) port configuration before applying a configuration change. In this case,
performing a no shutdown on an already-enabled port will have no effect.
67611 Enhancement. The [no] l2vpn local-traffic-forwarding and [no] l2vpn
No service mac-address-movable commands have been reinstated in the Casa CLI to
impact enhance local forwarding of L2VPN MPLS packets.
(Low)
• The local-traffic-forwarding property allows local traffic forwarding to
local addresses.
• The mac-address-movable property allows location changes for MAC
addresses attached to the L2VPN.
The two properties had been applied to the interface vlan configuration and to
the global L2VPN setting, which takes precedence over the interface vlan
configuration.
Example:
CASA(config)# l2vpn local-traffic-forwarding
CASA(config)# l2vpn mac-address-movable
CASA(conf-if-vlan 1)# l2vpn local-traffic-forwarding

CASA(conf-if-vlan 1)# l2vpn mac-address-movable
67784 Defect: After performing a QAM 8x8 module switchover and then reverting the module
Possible service back, modems on certain ports could drop off and not come back online. This
impact problem has been fixed.
(Medium)

1-42 Release Notes
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes

ID (Risk level)
21131 Enhancement: The show mirror command has been introduced in the Casa CLI diag mode
Operational, CLI to display the current mirror state defined by the mirror cm traffic
(Low) <ip_address> command.
Example:
CASA# show mirror
Mirroring CM e4.48.c7.b4.a8.cc to host IP 0xc0a8059a
46573 Defect: A timing issue in the software which was causing the show {cable | docsis}
No service downstream channel utilization command to report 0 utilization has been
impact fixed. The problem existed on the QAM 8x8 module only.
(Low)
50975 Defect: Timing and buffer size adjustments have been applied to ensure that the line
Possible service cards have sufficient time to process the configuration from the SMM after a
impact line card switches over to the redundant card. Previously, an intermittent
(Medium) problem was observed where a line card was unable to complete initialization
from the SMM. The fix reduces the processing time for the line card FPGA
configuration and eliminates unnecessary and time-consuming power
adjustment routines.

Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)

ID (Risk level)
51448 Enhancement. The maximum number of QAM modes on QAM 8x196 has been increased
Operational, CLI from two to three on a per-port basis to include up to two unicast modes and
(Low) one broadcast mode. Only one QAM mode may be applied to an 8-channel
block.
The show module <slot> qam-mode [summary] command has been

introduced in the Casa CLI to display detailed QAM mode statistics for all
ports. There can be up to three QAM modes for a QAM 8x192 module, two for
unicast and one for broadcast (the one with the positive ref_cnt). The second
broadcast mode (bc_mode 2) is used only in per channel interleave mode
where all the module channels have the same annex, modulation, and symbol
rates, and vary only between two interleave values.
Specify the summary option to display the same output in table format.
Example:
CASA# show module 1 qam-mode
Module 1:
uc_mode 1: annex A modulation 256qam interleave 12
symbol_rate 6952 ref_cnt 24
bc_mode 1: annex A modulation 256qam interleave 12
bc_mode 2: annex B modulation 256qam interleave 128x1
Port 0:
admin status: UP
total channel up: 28
number uchan up: 24
number bchan up: 4
uchan in mode 1: 12
uchan in mode 2: 12
bchan in mode 1: 4
bchan in mode 2: 0
default mode: annex A modulation 256qam interleave 12
symbol_rate 6952
other mode: annex B modulation 256qam interleave 128x1
symbol rate 0

1-44 Release Notes

ID (Risk level)
51839 Enhancement: The show run verbose command now displays the default values for various
51889 Operational, CLI L2VPN, DHCP, and cable ARP settings.
(Low)
52896 Defect: The show interface video stat command now correctly updates the running
No service status of the associated GigeE or XGigE interface.
impact
(Low) Example:
CASA(config)# show interface video 1
interface video 1 …
xgige 7/0
CASA(config)# interface gige 7/0

CASA(config-if-gige 7/0)# shutdown
CASA(config-if-gige 7/0)# end
CASA(config)# interface video 1

CASA(conf-if-video 1)# gige 7/0
CASA(config-if-video 1)# show interface video stat
interface video 1 status: Down…
52904 Defect: When performing a manual UPS switchover with the ha module <number>
Possible service protect command, D3.1 modems connected over OFDMA could go offline and
impact not recover during ranging attempts with the CMTS. The problem has been
(Medium) fixed.
55223 Defect: The show spectrum upstream command would show “No spectrum data
No service received” due to Casa Spectrum Management (CSM) listening on UDP port
impact 0xCACA (51914), which is in the local port range which could belong to
(Low) another application. The CSM UDP port has been changed to 61100 to correct
the problem.


ID (Risk level)
57358 Enhancement: The Pmax value has been added to show cable modem verbose command
Operational, CLI output as part of DOCSIS 3.1. Pmax is the maximum total transmit power that
(Low) the cable modem can support. The default and lowest possible value is 65
dBmV.
Example:
CASA(config)# show cable modem verbose
…
Reported Max Total Power Output (dBmV) :65.0
Timing Offset :2478
Initial Timing Offset :2478
Received Power :0 dBmV
…
58479 Defect: A problem which was causing recalibration of the FPGA-to-FPGA connection
Possible service at the time of a QAM 8x192 module reset has been fixed. The recalibration
impact caused existing values to be overwritten. A "no signal" condition was observed
(Medium) on some QAM 8x192 narrowcast/shared channels.
58847 Defect: Checks have been implemented in the software to ensure proper handling of
Possible service video encryption start times sent from the SRM. Specifically, the software
impact change addresses the invalid combination of “start_immediate 0” and
(Low) “start_time 0” which was resulting in a failure to start encryption of the video
stream.

1-46 Release Notes

ID (Risk level)
58971 Feature. OFDMA Upstream Data Profile (OUDP) Interval Usage Code (IUC) changes
58972 Operational, CLI for the Upstream Channel Set now allow the ability to send a dynamic bonding
(Low) change (DBC) of a changing IUC set to the modem and use multiple IUCs for
secondary bonding of OFDMA channels in the IUC profile (iuc-profile).
Changes are now reported in the show cable modem <mac-address> ver-
bose command output. IUCs (up to two) are reported in parentheses, with the
leftmost value reflecting the IUC presently in use. IUC 13 will always be pres-
ent as the default.
Example:
CASA(config)# show cable modem 6814.01f0.3e47 verbose
MAC Address :6814.01f0.3e47
IP Address :10.64.1.158
MAC Status :online
CM-ID :1
Prim Sid :11
MAC Domain :2
Service-Group :G1
Upstream Channel Set :12/0.0/0, 12/0.1/0, 12/0.2/0,
12/0.3/0, 12/0.0w(10,13)
Downstream Channel Set :1/0/29, 1/0/1, 1/0/2, 1/0/3,
1/0/4, 1/0/5, 1/0/6, 1/0/7,
1/0/8, 1/0/9, 1/0/10, 1/0/11,
1/0/12, 1/0/13, 1/0/14,
1/0/15, 1/0/16, 1/0/17,
1/0/18, 1/0/19, 1/0/20,
1/0/21, 1/0/22, 1/0/23,
1/0/24, 1/0/25, 1/0/26,
1/0/27, 1/0/28, 1/0/0, 1/0/30,
1/0/31
Unusable channel list :
Upstream Channel :12/0.0/0 12/0.1/0
12/0.2/0 12/0.3/0 12/0.0w
Ranging Status :RNG_SUCCESS RNG_SUCCESS
RNG_SUCCESS RNG_SUCCESS
RNG_SUCCESS
59182 Defect: A revision has been applied to the software patch installation process to pre-
Possible service vent a possible rebooting loop at the standby SMM. The rebooting loop was
impact observed in a situation where the standby SMM was not at the same base
(Medium) release level as the active SMM during the patch installation.


ID (Risk level)
59245 Defect: Fixes have been applied to the IP Detail Record (IPDR) collection timers to
Possible service correct a problem where the CMTS was attempting to re-enable timers which
impact were already in the enabled or disabled state during an SMM switchover.
(Medium) Checks to the IPDR timer have been implemented in the software to ensure
the current state of the timer before the CMTS makes an attempt to disable it.
59358 Enhancement: Forward Error Correction (FEC) results can now be derived specifically for
Operational, CLI OFDMA upstream channels in the Casa CLI using the show upstream fec
(Low) ofdma <slot>/<port>.<chan> command. The upstream FEC counters can
also be cleared specifically for OFDMA channels using the clear upstream
fec counters ofdma <slot>/<port>.<chan> command.
Example:
CASA(config)# show upstream fec ofdma 12/0.0
US chan frequency status cFEC uFEC
12/0.0w - UP 2226783 1565
CASA# clear upstream fec counters ofdma 12/0.0

59386 Enhancement: The downstream OFDM channel power now appears in show cable modem
Operational, CLI remote-query [immediate] command output. It was previously omitted if the
(Low) OFDM channel was the first channel bonded.
Example:
CASA(config)# show cable modem 6814.01f0.3ea1 remote-query
ofdm 12/3/0
MAC Address IP Address
S/N US DS TX Time Micro(dB) Modem
Ratio Power Power Offset Reflection State
6814.01f0.3ea1 0.0.0.0
-- 34.3 7.4 2704 -- online(pt)
2001:0:168:24:e885:c04:f3a0:1a93
59740 Defect: When editing the QAM 8x192 channel interleave setting under the interface
Possible service qam <slot/port> configuration, applying interleave 64 or interleave 128 was
impact rendering a single-carrier channel unusable. This problem has been fixed.
(Low)

1-48 Release Notes

ID (Risk level)
59789 Defect: With multi-Annex mode enabled on the QAM 8x192 module, the RF output
Possible service power level has been observed at approximately 4dB higher than the
impact. configuration value after a QAM 8x192 redundancy switch over. The problem
(Medium) was due to incorrect gain values in Annex C.
A change has been applied to the gain calibration table to ensure the
redundancy gain level as a function of frequency and to be within DOCSIS
DFRI specifications.
59934 Enhancement: The debug cable igmp command has been introduced in the Casa CLI to log
CLI Internet Group Management Protocol (IGMP) event messages.
Operational
(Low) Example:
CASA# debug cable igmp
59948 Defect: In a configuration where a different channel width value is configured on the
Possible service same port (such as 3.2 MHz & 6.4 MHz) and depending on modem type,
impact partial service could possibly occur on some upstream channels. This problem
(Medium) has been fixed.


ID (Risk level)
59968, Enhancement: The DOCS-IF31-MIB has been updated to the latest version of the CableLabs
59970 SNMP, DOCS-IF31-MIB-2016-08-18. The docsIf31DocsisBaseCapability of 4
Operational (DOCSIS 3.0) is maintained for management system compatibility.
(Low)
docsIf31DocsisBaseCapability OBJECT-TYPE
SYNTAX ClabsDocsisVersion
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This attribute reports the DOCSIS capability of the device.
A CMTS reports its highest supported DOCSIS version while a CM
reports its supported DOCSIS version.
This attribute replaces docsIfDocsisBaseCapability defined in RFC

4546."
::= { docsIf31MibObjects 1 }
Other changes to the DOCS-IF31-MIB:
1. docsIf31CmtsCmDsOfdmProfileTotalCodewords — Removed.
2. docsIf31CmUsOfdmaChanTxPower — Changed tenthBmv to
Unsigned32.
3. docsIf31CmUsOfdmaChanChannelId — Added.
4. docsIf31CmtsDsOfdmProfileStatsProfileId — Changed Index to ID.
5. docsIf31CmtsDsOfdmProfileStatsProfileId — Removed.
6. docsIf31CmtsUsOfdmaChanId — Changed CHID to Integer32
7. docsIf31CmEmDlsCfgExitBitrateThrshld — Changed
docsIf31CmEmDlsCfgEntryBitrateThrshld.
8. docsIf31CmEmDlsCfgEntryBitrateThrshld — Changed
docsIf31CmEmDlsCfgExitBitrateThrshld.
60080 Defect: A problem which caused the CMTS to send BGP notification packets to a BGP
Possible service peer router when a SAFI OPEN capability message was received at the CMTS
impact has been fixed. This issue caused the BGP peer session to disconnect. BGP
(Low) will now ignore the SAFI OPEN capability update message; notification
packets will not be sent.

1-50 Release Notes

ID (Risk level)
60141 Enhancement: The cumulative debug levels from 5 through 7 were added to the debug
Operational, CLI config qam flag command in diagnostic mode. The modes currently are
(Low) defined as:
• 0 – All off
• 1 – Debug
• 2 – BQAM
• 3 – QCC
• 4 – Mode
• 5 – Power
• 6 – DVB
• 7 – All on
Example:
CASA(diag)# debug config qam flag 7
CASA(diag)# show debug config qam flag
Qam config debug flag:
debug_flag=1
debug_bqam=1
debug_qcc=1
debug_mode=1
debug_power=1
debug_dvb=1
60336 Defect: A timer processing issue which caused accumulated time drifts (in seconds) at
No service IPDR data collection intervals has been fixed. The software fix implements an
impact optimized timer to minimize drift after each collection interval.
(Low)
60348 Enhancement: The maximum number of channels per DSG tunnel-group has been increased
Operational, CLI to 2560 with a maximum of 5120 DSG channels across all tunnel groups
(Low) system wide. Previously, the software supported up to 1280 DSG channels per
tunnel-group and 2560 DSG channels across all tunnel groups.
Example:
CASA(conf-dsg-tunnel-grp 21)# channel 1 qam 1/0/0
maximum channel limit in all dsg tunnel-groups has been
reached: 5120 ! !


ID (Risk level)
60387 Enhancement: The casaCmtsUSModemTable in the CASA-CABLE-CMCPE-MIB file has

SNMP been updated to include OFDMA channels in responses to SNMP queries.
(Low)
60432 Defect: A problem was observed where cable modem vendor names containing blank
No service spaces would be dropped from the running configuration after performing a
impact system reboot. A fix has been applied to ensure that vendor strings
(Medium) comprising blank spaces are preserved in the configuration with enclosed
quotation marks (“”) to comply with standard conventions.
60465 Defect: High ping latency was observed at some modems during peak traffic periods.
No service A software change to improve processing of CPE-to-CPE traffic entries has
impact been applied to correct the latency issue.
(Low)
60494 Defect: A synchronization issue between a software driver and the FPGA which was
Possible service preventing upstream burst noise detection from working properly has been
impact fixed. Burst noise detection can now be enabled where systems can now
(Medium) detect the burst noise along with the duration and magnitude of the burst
noise.
Previously in some networks, enabling upstream burst noise detection caused

degraded SNR and modem upstream partial service.
60557 Defect: A fix has been applied to ensure that processing of VOD sessions does not
Possible service begin until the CMTS completes a full system reboot and with FPGAs
impact configured and ready. The problem resulted in a session queue overflow state
(Medium) on some channels with subscribers reporting a “black screen” condition.
Performing a QAM module switchover provided a workaround to the problem.
60569 Enhancement: The message "This is the standby SMM. Please log into the system from the
Operational active SMM!" will now be presented if a newly configured user with level 0 to
(Low) 14 access privileges attempts to login over the console port at the SMM
standby. Console logins to the system are only supported at the active SMM.
60625 Enhancement: Certain modems sending repeated multicast join requests with extended time
Performance periods were not be able to establish service flows with the CMTS. The
(Low) problem was observed in a test environment and has been fixed.

1-52 Release Notes

ID (Risk level)
60722 Enhancement: Up to sixteen video interfaces (1 to 16) can now be configured on a single
Operational GigE or xGigE port, with each port having a unique IP address. The previously
(Low) supported number of video interfaces per port was four.
Example:
CASA(config)# show interface video
interface video 1
ip address 192.168.18.200 255.255.255.0
ip igmp
input-port-id 1
bandwidth 10000000
gige 6/0
.
.
interface video 16
ip address 192.168.18.215 255.255.255.0
ip igmp
input-port-id 1
bandwidth 10000000
gige 6/0
60751 Defect: In the OFDMA/TaFDM frequency scheme, the 5 MHz guard band, which is
No service inserted on the boundary between TDMA and OFDMA channels both in
impact frequency and time dimensions will now be removed if the OFDMA frequency
(Low) edge is covered with the exclusion band. The guard band is maintained when
no exclusion band is present on the channel.
60807 Defect: The CMTS measured cable modem timing offset displayed with the show
No service cable modem command was changing over time due to a calculation error.
impact The actual timing offset to the CM did not change. The timing offset reported
(Low) by the CM with show cable modem phy remained correct. This was a display
issue.
60839 Defect: When load balancing traffic between two ECMGs, a problem was reported
Possible service where the software was creating duplicate connections to the same
impact Conditional Access System (CAS), resulting in encrypted video being dropped.
(Medium) This problem has been fixed.


ID (Risk level)
60896 Enhancement. The show multicast client stat command was added in the Casa CLI to dis-
Operational, play multicast client statistics, including forwarded, filtered and dropped
CLI, (Low) reports, and rate limit drops.
The show multicast client summary command was also enhanced with
IGMP statistics, including total joins and the number of total reports for IPv4
and IPv6.
Example:
CASA(config)# show multicast client stat
|Forwarded Reports |Filtered Reports
module|total |rate/min |acl |submgt
3 |67 |10 |4 |0
|Dropped Reports
|group mismatch |invalid
|3 |13
|Rate Limit Drops
|per cm |per module
|16 |13
…
CASA(config)# show multicast client summary

MD Static/Dynamic Last Reporter Multicast Session
1 0 /2 10.94.0.180 <226.94.2.0, 0.0.0.0>
1 0 /2 10.94.0.180 <226.94.2.1, 0.0.0.0>
…
MD Total Joins (v4/v6) Active Groups (v4/v6) Total
Reports (v4/v6) Rate/Min (v4/v6)
1 2/0 2/0
3 1/1 1/1
…
60929 Defect: There was a logic error on RFoG scheduler on a TDMA channel where the
Possible service RFoG group was not properly added on the line card. The logic error has been
impact fixed.
(Medium)

1-54 Release Notes

ID (Risk level)
61004 Defect: Under a rare condition when the active SMM is rebooted or is manually pulled,
Possible service or if an SMM switchover is initiated, a CPU2FPGA XAUI TIMEOUT error has
impact been reported with a resulting QAM module switchover. There was a small
(Medium) timing window which could cause this condition when the SMM and the
QAM8x192 module establish communication with each other. Software logic,
which controls the SMM transmissions to the QAM line cards, has been
applied to ensure that communication is properly established between the
modules to prevent the problem.
61006 Defect: Management link status detection has been implemented in the software to
Possible service ensure that the management GigE interface is brought back up if detected in
impact the link down state following an SMM switchover to the standby SMM.
(Medium)
Previously, in cases where the SMM switches over to the standby, some QAM
8x192 modules would switch over to the standby QAM if the link down state
with reported “NO KEEPALIVE” continued to be detected.
61037 Defect: A problem was reported where the clear cable flap-list delete command
Possible service would fail to delete all entries in the flap list. This problem has been fixed.
impact
(Low)


ID (Risk level)
61048 Feature: The QAM 8x192 module with two OFDM channels now allows pre-binded
61947 Operational, CLI narrowcast DOCSIS channels in the shared channel range 32–63 as
(Low) secondary channels. These channels can be configured on the DOCSIS MAC
interface as downstream secondary channels, and added as QAM interfaces
in service groups.
The show downstream channel set command has also been modified to
show the narrowcast shared channels.
Example:
CASA(conf-if-mac 33)# show this
…
ip bundle 1
downstream 1 interface qam 1/0/32 secondary
…
CASA# show downstream channel set mac-domain 33

MAC Chan Channel
ID Set List
…
33 9 1/0/32
33 10 1/0/33
33 11 1/0/34
33 12 1/0/35
33 13 1/0/36
33 14 1/0/37
33 15 1/0/38
33 16 1/0/39
33 20 1/0/1w
61274 Enhancement: The ISIS process has been optimized for faster processing of route update
Performance messages with no impact on system performance. The enhancement
(Low) addresses possible delays which could occur as the ISIS network scales up.

1-56 Release Notes

ID (Risk level)
61347 Enhancement: After configuring the Event Information Scheduler (EIS) under a VRF instance
Operational, CLI with the video simulcrypt eis vrf <vrfname> command, a timing overlap
(Low) between de-registration and re-initialization of the SimulCrypt process caused
an SMM switchover to occur.
In situations where the SimulCrypt process requires a restart, a timing delay

has been implemented to ensure that the active SimulCrypt process is
properly terminated before being restarted.
61406 Defect: The syslog message: "ER-SIM-1: smm6: service_list_free: NULL input
No service parameter” was being printed to the log when service_list_free() was called
impact with an empty list. The list pointer is now tested for NULL before calling
(Low) service_list_free().
61486 Enhancement: The Radio Frequency over Glass (RFoG) scheduler, defined in DOCSIS3.1
Operational, CLI has been updated to support OFDMA channels.The RFoG scheduler allocates
(Low) the upstream spectrum for modem upstream transmissions to ensure that time
slots do not overlap if these modems are on the same optical fiber. RFoG
mode is enabled or disabled on a per service group basis.
Example:
CASA(config)# service group SVGP
CASA(conf-svc-grp SVGP)# ofdm 11/1.0
CASA(conf-svc-grp SVGP)# upstream rfog-scheduler
61489 Defect: An OFDMA channel configuration change, such as a change to the channel
Possible service width, was causing all the cable modems on that channel to flap. A fix has
impact been applied to correct a possible time stamp matching error which could
(Medium) result during the upstream channel descriptor (UCD) change.
61497 Enhancement: An operational enhancement has been applied for improved handling and
Operational recovery of OFDM data profiles. When the cable modem declares a higher
(Low) OFDM data profile to be usable in the cm-status message, the CMTS will now
switch to the higher OFDM data profile without waiting for the modem to
declare the current OFDM data profile as unusable.
61535 Defect: After performing a system reboot, systems running the QAM 8x192 module
Possible service configured with one OFDM channel were experiencing intermittent outages
impact with video streams on shared channels only. The problem has been fixed.
(Medium)


ID (Risk level)
61621 Defect: A problem was reported where the current Baseline Privacy Interface (BPI)
Possible service certificate status was not being maintained after performing an SMM
impact switchover with the ha module 6 protect command. A fix has been applied to
(Medium) correctly synchronize the current certificate status between the active and
standby SMMs.
61638 Enhancement: The maximum number of supported DVB Simulcrypt Scrambling Control
Operational Groups (SCGs) has been increased in the software from 512 to 10000 per
(Low) C100G chassis. There are no configuration requirements with this change.
61720 Defect: Revised configuration processing of the video simulcrypt cp (crypto period)
Possible service setting in the configuration has been implemented. A problem was observed
impact where the show video simulcrypt scg <identifier> command was reporting
(Medium) inconsistent nominal CP statistics regardless of the video simulcrypt cp
configuration setting. The parameter setting has also been revised to the
configuration range of 10 to 6000 seconds; the default setting is 30 seconds.
61742 Enhancement: The show cable modem [<mac_addr>] verbose command has been
Operational, CLI enhanced in the Casa CLI to include the current OFDMA data IUCs (up to two)
(Low) for each channel in the Upstream Channel Set listing. With multiple IUCs, the
active one is listed first.
Example:
CASA# show cable modem verbose | include "Upstream Channel
Set"
Upstream Channel Set :12/2.0w(5,13), 12/0.0w(13)
61840 Defect: String parsing of the startup-config file has been revised to correct a problem
Possible service where an OFDMA command alias in the file could cause the CMTS to get
impact stuck during the boot-up process while awaiting an expected command input.
(Medium) The parsing process now incorporates improved checking of strings to
determine actual commands versus alias strings which could cause the
system to hang during boot-up.

1-58 Release Notes

ID (Risk level)
61925 Enhancement: The module <number> channel-id-offset command has been introduced in
Operational, CLI the Casa CLI to provide module-specific implementation and override of the
(Low) video channel-id-offset command, which excludes DOCSIS channels from the
video channel numbering space.
Channel numbering begins following the offset, where the first video channel
begins at 0. The offset value depends on the largest of the module
narrowcast-channels <id> narrowcast-channels <number> settings.
Syntax:
[no] module <id> channel-id-offset <1:63>
Example:
CASA(config)# module 11 channel-id-offset 40
CASA(config)# show channel-id-offset
video channel-id-offset 44
module 0 channel-id-offset 40
61975 Enhancement: IPv6 address validation has been added to the loopback, NIC, trunk, and
Operational, VLAN interface configuration screens of the Casa Video Web UI. Symbol rate
Web UI ranges were also validated for Annex A and C channel widths for the QAM
(Low) configuration screen.
62012 Enhancement: A software fix has been applied to increase the TTY input buffer from 64K to
Operational 512K. Previously, a buffer overrun condition was reported when attempting to
(Low) copy and paste a full running configuration over a console connection where
some of the configuration line entries were dropped.


ID (Risk level)
62039 Enhancement: The “Server Last Time Up” statistics reported with the show video simulcrypt
Operational, CLI ecmg command has been corrected to display the time since the ECMG was
(Low) last disconnected. Previously, the reported time was the connection uptime
with the ECMG.
Example:
CASA(config)# show video simulcrypt ecmg
Encryption Period : 30
…
ECMG yli1:
…
Stream Information:
Stream ID Stream ECM ID CP number Status
--------- ------------- --------- ------
1 0 N/A Active
Server Last Time Up : Fri Oct 21 13:34:09 2016
62043 Defect: There was an issue in two-stage PKE session creation so that sometimes
Possible service session query or deletion will fail. This error is now corrected.
impact
(Medium)
62106 Enhancement: An issue which was preventing the minimum reserve bandwidth using
Operational, CLI PacketCable Multimedia (PCMM) from being set to 0 kbps has been fixed. The
(Low) software now accepts the zero value, as shown in show cable modem qos
output as the MinRsvRate (kbps). The problem was observed during unicast
session setup.
Example:
CASA# show cable modem 6814.01f0.3e47 qos
Sfid Dir Curr Sid Sched Prio MaxSusRate MaxBrst
State Type (kbps)
MinRsvRate PeakTrafRate Throughput ServiceClassName
(kbps) (kbps) (kbps)
Mac Addr : 6814.01f0.3e47
16385 US act 1 BE 0 0 30000
0 0 0
24578 DS act N/A UNDEF 0 0 3044
0 0 0
24585 DS act N/A UNDEF 0 0 3044
0 0 0

1-60 Release Notes

ID (Risk level)
62154 Enhancement: The Casa Web UI has been enhanced to include the Output Port Base column
Video Web UI and parameter for the EDIS SRM video configuration. Output port base 0 is
(Low) used by Casa or Cisco SRM by default, while output port base 1 is used by
BigBand SRM.
62337 Enhancement: The maximum number of supported access control lists (ACLs) and route
Operational maps per system has been increased from 32 to 128.
(Low)
62410 Enhancement: Network Management System (NMS) requests are now “green-lighted” in the
Video Web UI, Casa Video Web UI without the need for Video Web UI credentials. Up to eight
CLI NMS servers can be configured at the CMTS.
(Low)
The NMS requests are honored if they are set up through the system nms
<ip_address> command. Requests appear in the show system nms
command output.
Example:
CASA# show system nms
---------------------------------------------------------
server-ip port scheme heartbeat notifyUrl
192.168.8.8 8080 http 60 /nms-web-ui/api/notification
62465 Enhancement: The Program Clock Reference (PCR) discard logic to ignore the PCR PID
Operational indicated in the PMT could result in processing every set of PCRs within an
(Low) input program stream. If there are multiple sets of PCRs in an input stream,
one optimal PCR (PID) set is chosen as the reference. NULL packets are
forwarded to egress to maintain the scheduling parameters to prevent
triggering of drift correction.


ID (Risk level)
62481 Enhancement. The ping docsis command in the Casa CLI has been enhanced to support
Operational, CLI pinging a selected upstream bonded channel. The command previously
(Low) allowed pinging IPv4, IPv6, and MAC addresses for upstream channels with
the option to specify the number of pings and verbose output. OFDMA
channels are now included.
Example:
CASA# ping docsis 0895.2a9b.2a99 ofdma 12/2.0 3 verbose
PING DOCSIS 0895.2a9b.2a99 on ofdma 12/2.0w
RNG-REQ from 0895.2a9b.2a99 on ofdma 12/2.0w 12 ms,
p-offset=1, f-offset=0, t-offset=0
p-offset=1, f-offset=0, t-offset=-1
--- 0895.2a9b.2a99 ping docsis statistics ---
3 station maintenance scheduled, 3 RNG-REQ received 100%
success
62541 Defect: SNMP queries to the ifHighSpeed object in the IF-MIB file now report the
No service OFDMA calculated bandwidth consistently with the CLI show docsis
impact upstream channel utilization command output.
(Low)
62617 Enhancement. The ofdm profile-modulation <type> rxmer threshold command has been
Operational, CLI enhanced with the percentage parameter to set the MER percentage offset
(Low) from the threshold value to prevent bad subcarriers from disqualifying a modu-
lation profile.
The default percentage setting is 90 in the range 0 to 100.
Example:
CASA(conf-ofdm-profile 1)# profile-modulation 256qam rxmer
threshold 190 percentage 90
62651 Defect: A software error which could limit the number of IP bundle interfaces below the
No service configuration maximum has been fixed.
impact
(Low)

1-62 Release Notes

ID (Risk level)
62672 Defect: A software fix has been applied to correct handling of MPTS pass-through
Possible service input streams in cases where two different Program Mapping Tables (PMTs)
impact are pointing to the same audio/video PIDs. A problem resulted in which one of
(Medium) the PMTs remained uninitialized. For MPTS sessions, the first master PMT
Program Clock Reference (PCR) will enable all PMTs to be initialized.
62698 Feature: The Network Management System (NMS) server CCAP monitoring feature
63218 Operational, CLI has been introduced in the Casa CLI with the system nms <ip_address>
63357 (Low) [port <1:65535>] [heartbeat <1:3600>] [notifyURL <url>] command. The
CMTS will send the NMS server any event notifications reported by the show
alarm command and notifications in the /tmp/snmptraplog.gui file. The NMS
server reports event levels CRITICAL, ALARM, WARNING, and INFO.
Up to eight NMS servers can be configured for the CMTS. The no form of the
command removes an NMS server connection.
The show system nms command displays the NMS settings.
The port number (default 8080), heartbeat (default 60 seconds), and

notifyURL (default /nms-web-ui/api/notification) parameters are optional.
Example:
CASA(conf)# system nms 172.0.1.163 port 8080 heartbeat 60
notifyUrl /nms-web-ui/api/notification
CASA(conf)# show system nms
CASA(conf)# no system nms 172.0.1.163
CASA(conf)#


ID (Risk level)
62868 Defect: The SNMP casaSpectrumDataPowerNew has been added to the

No service CASA-SPECTRUM-MIB file to report received power in tenths of dB to
impact maintain consistency with the CLI show spectrum upstream command
(Low) output.
-- 1.3.6.1.4.1.20858.10.56.1.2.1.3
casaSpectrumDataPowerNew OBJECT-TYPE
SYNTAX TenthdBmV
UNITS "TenthdBmV"
STATUS current
DESCRIPTION
"The same as casaSpectrumDataPower, but the Units are
in tenths of a dBmV."
::= { casaSpectrumDataEntry 3 }
62974 Defect: A problem which could cause an original ARP entry to be relearned or even
Possible service removed from the ARP table in a situation where the associated CPE IP
impact address was in use by a different CPE device has been fixed.
(Low)
62998 Defect: A problem was reported where disconnected cable modems were still being
No service reported as online with the show cable modem {upstream | downstream}
impact summary command. The problem was caused by an issue in the CMTS
(Low) internal messaging queue where the offline modems were not being reported.
The problem has been fixed.
63016 Defect: The Casa Video Web UI has been revised so that the default symbol rate for
Operational, the Annex C QAM channel configuration is 5274 (instead of 6952)
Web UI kilo-symbols per second.
(Low)
63037 Enhancement. The debug cable pre-equalization command has been added in the Casa
Operational, CLI CLI enable mode to display the pre-equalization coefficients sent to cable
(Low) modems over non-OFDM channels.
Example:
CASA# debug cable mac-address 0895.2a9b.2a99
CASA# debug cable pre-equalization
CASA# show debugging
Cable:
mac-address: 0895.2a9b.2a99
…
pre-equalization

1-64 Release Notes

ID (Risk level)
63174 Enhancement: The default setting for handling the CPU2FPGA XAUI TIMEOUT ERROR has
Performance been changed to allow self-recovery upon error detection to prevent
(Low) unnecessary hardware switchovers. Three attempts at self-recovery will now
be enforced before a hardware switch over is applied.
63184 Defect: When processing MPTS sessions, a packet queue counter corruption was
Possible service found in the DS scheduler which could result in a QAM module switchover to
impact the standby QAM module. This problem has been fixed.
(Medium)
63206 Defect: Performing the RFoG channel shutdown/no shutdown caused a single
Possible service RFoG group to be managed by two separate upstream scheduling threads
impact with a resulting corruption to the MAP timer. The problem caused an
(Medium) unexpected UPS module switchover.
A software fix has been implemented to remove the RFoG group from the map
timer when all channels are inactive. Protections have been applied to ensure
cleanup of the upstream queue on shutdown of an RFoG channel.
63302 Defect: Software fixes have been applied to ensure that channel-bonding cable
63458 Possible service modems operating in partial service continue to receive multicast traffic over
impact SC-QAM and OFDM channels.
(Medium)
Previously, if a Hitron™ modem rejected the multicast DSID/DBC operation
with a partial service error, the multicast session was not being retained. The
software fix ensures that the multicast replication remains uninterrupted.
Additionally, the multicast replication channel set was being created based on
the full bonding set of the cable modem, even though the modem was in the
partial service state. The software will now create the multicast replication
based on the modem’s active bonding channel set.
The software fixes have been validated with OFDM channel bonding as well.
63372 Defect: An snmpwalk of the docsBpi2CmtsDefaultSelfSignedManufCertTrust MIB was
No service returning an incorrect value of "trusted(1)" instead of “untrusted(2)” for cable
impact modems attempting to register and come online with self-signed certificates.
(Low) By default, the CMTS blocks cable modems attempting to register with
self-signed certificates.
63387 Defect: A recovery issue in the software which could cause encrypted sessions to
No service begin transmitting in the clear after a QAM module switchover has been fixed.
impact The problem was observed with the show video session command reporting
(Low) the “Clear” state for some video sessions.


ID (Risk level)
63392 Enhancement: Multiple recursion is now supported when looking up forwarding destinations
Operational for BGP-learned routes. The enhancement ensures that destination routers
(Low) have the expected MPLS forwarding tags.
63482 Defect: A fix has been applied to the redundancy logic to properly check the availability
Possible service status of the standby module and to ensure correct timing of line card
impact switch-overs to the standby slot. A case was reported where the standby UPS
(Medium) line card in system slot 8 was not assuming the active state for one of the UPS
line cards in a situation where multiple UPS line cards were simultaneously
reset.
63501 Enhancement: For single-carrier (SC) and OFDM capabilities, the supported QAM port power
Operational upper limit has been revised for both QAM 8x96 and QAM 8x192 modules.
(Low)
The port power maximum output levels are:
• 620 dBmV for <= 1 channel

• 610 dBmV for 2 channels
• 600 dBmV for > 2 and <= 8 channels
• 560 dBmV for > 128 channels
The default port power remains at 510 dBmV.

63565 Defect: In configurations where there are two symbol rates on a single QAM port
Possible service configured, there is a possibility of the wrong configuration being programmed.
impact
(Medium) A fix to correct the FPGA driver logic has been applied to correct an
intermittent issue which could cause the QAM 8x96 symbol rate configuration
to be incorrectly re-programmed in software after performing a system reboot
or QAM 8x96 module reset. Performing a QAM 8x96 switchover to the
redundant module corrects the problem.
63664 Defect: A command handling error in the software which could cause a failure to
Possible service properly launch the system shell process at the time of an SMM 8x10G
impact switchover has been fixed.
(Medium)

1-66 Release Notes

ID (Risk level)
63752 Defect: A problem was reported where traffic from a multicast group was not being
Possible service replicated to a QAM module. A fix has been applied to correct a counter error
impact when processing multicast join/leave requests, which was preventing multicast
(Low) session replications.
63767 Enhancement: Session queries/audits conducted by the Explorer Controller (EC) was causing
No service valid SDV sessions created by SRM to be incorrectly deleted by the EC. The
impact CCAP software has been revised to ensure that session queries and session
(Low) deletions are only granted to the creator of the session, such as SRM.
Protections in the software have been applied to ensure that the EC properly
recognizes and does not delete SDV sessions it did not build.
63794 Enhancement: The Casa database capacity has been extended to ensure that SNMP queries
No service to the casaCmtsCmMacToCpeEntry MIB report the same number of CPEs as
impact the CLI show cable modem cpe command output.
(Low)
63935 Defect: A problem which was causing the edge logger process to fail with an SMM
Possible service switchover after the issuing a no logging command or after a Telnet session
impact termination has been fixed. A software change has been applied to ensure that
(Medium) the logger process does not attempt to write to the log file after logging is
disabled.
64017 Defect: Signal-to-noise ratio (SNR) fluctuations of 5–7 dB were being observed under
Possible service normal conditions in the single-carrier QAM channels. This problem has been
impact fixed.
(Low)
64039 Defect: Software fixes to address a situation where a certain D3.1 modem with
Possible service multiple bonded TDMA channels and one OFDMA channel was unable to
impact complete unicast ranging over the OFDMA channel. The problem caused the
(Medium) OFDMA channel to be dropped with the modem going into upstream
partial-service. Both initial-tech unicast-ranging and initial-tech ofdma
unicast-ranging settings were enabled in the DOCSIS MAC interface.
The software fixes apply support for init-tech 6 (unicast IUC 3) and init-tech 7
(unicast IUC 4), and adjustments to the timing offset for OFDMA ranging
requests.
64121 Defect: A software error which was resulting in failed SNMP GET queries to the
No service docsIf3CmtsCmUsStatusSignalNoise MIB object for non-primary bonded
impact upstream channels has been fixed. The message “No Such Instance currently
(Low) exists for this OID” was reported at the time of the SNMP GET request.


ID (Risk level)
64151 Feature: Support has been added for IPv6 Provider Edge Routers (6PE) in BGP routes
Operational as defined in RFC4698. 6PE routers are dual stack in order to connect to IPv6
(Low) islands and to the MPLS core, which is only required to run IPv4 MPLS. The
6PE routers exchange the IPv6 reachability information transparently over the
core using the Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4.
The implementation allows for a single 6PE Autonomous System (AS) and
supports prefix delegation for IPv6 address assignment.

• show ip bgp neighbors A.B.C.D

1-68 Release Notes

ID (Risk level)
64388 Defect The following fixes have been applied to correct issues with multicast
No service debugging:
impact
(Low) • The no debug all command will now properly disable the debug ddm
mcast command setting.
• The show debugging command will now display the DOCSIS Device
Manager (DDM) multicast debugging status.
Example:
CASA# debug ddm mcast
SMM 6 debugging status
PIM debugging status:
IP PIM error debug on
DDM MCAST Debugging Status:
debugging mcast trace ON
debugging mcast igmp ON
debugging mcast error ON
debugging mcast detail ON
debugging mcast dbc ON
CASA# no debug


ID (Risk level)
64452 Feature: Support has been added for NetFlow V9 network traffic flow monitoring.
Operational NetFlow provides the ability to collect IP network traffic as it enters or exits an
(Low) interface. By analyzing the data, a network administrator can determine such
things as the source and destination of traffic, class of service, and the causes
of congestion. A network flow is a unidirectional stream of packets identified as
the combination of factors. Any one of the following factors being different
defines the flow as unique:
• Source and destination IP address

• IP protocol
• Source and destination port number
• Type of service (ToS)
• Ingress interface (SNMP IfIndex).
The Casa NetFlow implementation is based on NetFlow Version 9, described

in RFCs 7011 and 7012. Version 9 is template-based and complies with IPv6
as well as IPv4 addressing. NetFlow information collection is turned on and off
on individual IP bundle interfaces only.
One sampler MAP and one exporter map are supported per CMTS, with one
data template each for IPv4 and IPv6. Each line card is both an observation
domain and an export device. Only UDP transport is supported. NetFlow
depends on a sampling rate. The Casa minimum sampling rate is defined as
one packet out of one thousand packets.
The following commands have been added to support NetFlow monitoring:
• [no] flow exporter-map <name> — Source loopback and destination

addresses and port definitions, template timeouts, and transport
definitions, with accompanying show command.
• [no] flow monitor-map <name> — Protocol, exporter name, and cache
timeout definitions, with accompanying show command.
• [no] flow sampler-map <name> — Sampler rate definition, minimum one
per thousand packets, default 1024, maximum 10000 packets, with
• flow ingress and flow egress definitions applied to the IP bundle
interface.

1-70 Release Notes

ID (Risk level)
64523 Defect. A problem was reported where IP address changes to the ip-bundle
No service configuration were taking a number of minutes to appear in SNMP queries. A
impact software revision has been applied to ensure that IP address changes are
(Low) picked up by SNMP immediately.
64638 Enhancement. The [no] packetcable gate maxcount <1:196607> setting has been added to
Operational, CLI the Casa CLI to set the maximum gate count per chassis for PacketCable,
(Medium) PCMM multicast, and PCMM unicast sessions. The default maximum is 30%
of cable modem count, as indicated in the CLI below.
In addition to the maximum number of PacketCable and PCMM gates to 192K,

the maximum number of IGMP clients has also been increased to 192K.
Example:
CASA(config)# packetcable gate maxcount ?
<1-196607> gate count,default is cm_num*3/
10,Warning: This command may free
all current gates
64666 Enhancement: Deselected table rows presented in Casa Video Web UI screen displays are
65151 Video Web UI now properly identified as deselected. Refreshing a table with a selected table
(Low) row now properly refreshes the table without clearing the selected row.


ID (Risk level)
64685 Enhancement. The BGP router address-family ipv6 labeled-unicast command in the Casa
Operational, CLI CLI has been extended to include additional neighbor functions.
(Low)
Example:
CASA(config-router-bgp)# address-family ipv6
labeled-unicast
CASA(config-router-af)# neighbor 114_by_243_244 ?
activate Enable the Address Family for this
Neighbor
allowas-in Accept as-path with my AS present in
it
attribute-unchanged BGP attribute is propagated unchanged
to this neighbor
distribute-list Filter updates to/from this neighbor
filter-list Establish BGP filters
maximum-prefix Maximum number of prefix accept from
this peer
next-hop-self Disable the next hop calculation for
this neighbor
prefix-list Filter updates to/from this neighbor
remove-private-AS Remove private AS number from
outbound updates
route-map Apply route map to neighbor
send-community Send Community attribute to this
neighbor
weight Set default weight for routes from
this neighbor
64699 Enhancement: When redistributing IGP routes into BGP, route metrics are now carried in the
Operational route advertisement. The enhancement applies to both IPv4 and IPv6 routes.
(Low)
64792 Defect. The Key Gracetime statistic has been removed from the show cable modem
No service privacy verbose command output. Check the modem configuration file for the
impact correct TEKGraceTime setting.
(Low)
65004 Enhancement: The DHCPv4 and DHCPv6 Relay Agent Option TLV reported to cable modems
No service by the CMTS in DHCP provisioning packets has been updated to Minor
impact Version Number 1 to reflect DOCSIS 3.1 capability. Previously, Minor Version
(Low) Number 0 was used to reflect DOCSIS 3.0 capability.

1-72 Release Notes

ID (Risk level)
65064 Defect: A software change has been applied to enable direct TFTP transfer of the
Possible service PowerKey certificate installation application to the standby SMM instead of
impact using the configured loopback interface. When TFTP uses a loopback
(Low) interface as the source-interface for file transfers to the CMTS, as configured
with the ftp-tftp source-interface loopback <number> setting, there was a
possibility that the PowerKey certificate installer would not be replicated to the
standby SMM.
65118 Defect: An error in the software logic which could cause the shell.exe process to fail
Possible service with a resulting SMM switchover while editing the load-balance configuration
impact in the CLI has been fixed.
(Medium)
65123 Defect: The IP Detail Record (IPDR) collector was showing the EqData (field 14) value
No service of the DOCSIS-CMTS-CM-US-STATS-TYPE Session 8 as non-readable
impact binary characters. The value is now presented as a printable hexadecimal
(Low) string.
65339 Defect: In a configuration where a video EDIS IP address was not present in the
Possible service configuration, video sessions created by the SRM could not be deleted. A fix
impact has been applied to ensure video sessions created by SRM can be deleted
(Medium) normally.


ID (Risk level)
65379 Enhancement. The [no] address-family ipv4 mvpn property has been removed from BGP
Operational, CLI and VRF configurations due to MVPN being disabled. The Multicast
(Low) Distribution Tree (MDT) configuration has been was retained.
Example:
CASA(config-router-bgp)# address-family ipv4 ?
mdt Subsequent Address family 66 for
Multicast VPN
unicast Address Family modifier
vrf VPN Routing/Forwarding instance
CASA(config-router-bgp)# no address-family ipv4 ?
Multicast VPN
CASA(config)# ip vrf City-GZ ?

CASA(config-vrf)# multicast-routing
CASA(conf-vrf-mcast)# address-family ipv4 ?
Multicast VPN
CASA(conf-vrf-mcast)# no address-family ipv4 ?
Multicast VPN

1-74 Release Notes

ID (Risk level)
65476 Enhancement. The show ipv6 bgp labeled-unicast neighbors <ipv6> advertised-routes
Informational, command has been introduced in the Casa CLI to identify BGP-advertised
CLI routes for IPv6 neighbors.
(Low)
Example:
CASA(config-router-af)# show ipv6 bgp labeled-unicast
neighbors 177.177.177.79 advertised-routes
BGP table version is 2, local router ID is 177.177.177.106
Status codes: s suppressed, d damped, h history, * valid,
> best, i - internal Origin codes: i - IGP, e - EGP, ? -
incomplete
Network Next Hop Metric LocPrf Weight Path

*>i 177::177:54:1/128
::ffff:b1b1:b16a 0 100 0 65535 ?
*>i 177::177:54:2/128
::ffff:b1b1:b16a 0 100 0 65535 ?
*>i 177::177:54:3/128
::ffff:b1b1:b16a 0 100 0 65535 ?
*>i 177::177:106:1/128
::ffff:b1b1:b16a 0 100 32768 ?
*>i 177::177:106:2/128
::ffff:b1b1:b16a 0 100 32768 ?
*>i 177::177:106:3/128
::ffff:b1b1:b16a 0 100 32768 ?
Total number of prefixes 6

65750 Defect: With Entitlement Control Message Generator (ECMG) load balancing in effect,
Possible service SimulCrypt Entitlement Control Messages (ECMs) were appearing with no
impact bitrate and not being referenced in the Program Mapping Table (PMT). The
(Medium) problem was preventing the active Conditional Access (CA) system from
generating ECM requests.
The software has been revised so that checking for load balancing candidates
is disabled if an active CA is being used to generate ECM requests.
65890 Defect: With the ha service-flow-counters recover parameter enabled in the
No service configuration, cable modem packet counters were not recovering after a QAM
impact process restart. The problem was observed with the show cable modem
(Low) counters command. Packet counters are now recovered.


ID (Risk level)
65993 Feature: The multiple table row selection and deletion feature was introduced in many
Operational, of the configuration and monitoring screens of the Casa Video Web UI.
Video Web UI
(Low)
66093 Enhancement. The show interface qam <slot>/<port> block command has been enhanced
Informational, in the Casa CLI to display the FPGA channel mapping for shared channels.
CLI The output shows the FPGA ID and the channel ID in parentheses at the end
(Low) of shared channel line entries.
Example:
CASA# show interface qam 1/0 block
QCC_MODULE_INFO:
uc_mode 1: mid 1 annex A mod 256qam intlv 12 symb 6952
ref_cnt 128
uc_mode 2: mid 2 annex B mod 256qam intlv 128x1 symb 0
ref_cnt 64
bc_mode 1: mid 3 annex A mod 256qam intlv 12 symb 6952
ref_cnt 20
…
block 3 freq 866000000 mask 00001fef mode_id 3 in_used 1
…
shared-channel 0 freq 906000000 blk 3 off 5 mid 1
annex A mod 256qam intlv 12 sym 6952 dvb 0 act 2 sta_m
0x21 ch 76 sch 0 (10,0)
…
66115 Feature: The Monitoring > Interface > NIC and Monitoring > QAM > Statistics and
66131 Operational, Monitoring >QAM > Video Statistics screens in the Casa Video Web UI have
66135 Video Web UI been enhanced with the capability to toggle between charts and data tables.
66643 (Low) The charts can be grouped or stacked and can be filtered by criteria, such as in
or out packets and detected/available bit rate.

1-76 Release Notes

ID (Risk level)
66150 Enhancement. The debug ddm mcast syslog command has been added in the Casa CLI
Operational, CLI enable mode to control logging of multicast error messages to the system
(Low) non-volatile log file. When enabled, the multicast debug messages are sent to
CASALOG, which are then directed to the system (console) and/or non-volatile
log file (on flash disk).
This enhancement is disabled by default. When disabled, all multicast logging

messages are sent to the /tmp/multicast_log file only.
Example:
CASA# debug ddm mcast ?
<cr>
dbc dbc debugging info
detail detailed debugging info
error error level debugging
igmp igmp level debugging
syslog send debugging messages to local system log
trace trace the path
CASA# debug ddm mcast syslog

send debugging messages to local system log ONLY
66193 Enhancement. The following Casa Video Web UI enhancements have been implemented:
66211 Operational,
Web UI • An additional pie chart of monitoring alarm results on the Monitoring >
(Low) Alarm screen.
• The Monitoring > Log screen now allows toggling between data and chart
display of the log file results.
• The Monitoring > QAM > Power screen now allows toggling between data
and chart display of QAM power results.


ID (Risk level)
66336 Enhancement. The casaQamPortMacAddress object in the CASA-QAM-MIB has been

Operational, modified to be read-only. Previously, the setting was read-write, where an
SNMP SNMP query was returning modifiable values. Zero values are now returned.
(Low)
-- 1.3.6.1.4.1.20858.10.25.1.1.1.4
casaQamPortMacAddress OBJECT-TYPE
SYNTAX MacAddress
STATUS current
DESCRIPTION
"The Qam Port MacAddress."
::= { casaQamPortEntry 4 }
66357 Enhancement. The value range of the casaIpTrunkGroupId object of the
Operational, CASA-IP-TRUNK-MIB has been increased to a maximum of 2147483647
SNMP group IDs.
(Low)
-- 1.3.6.1.4.1.20858.10.23.1.1.1.1
casaIpTrunkGroupId OBJECT-TYPE
SYNTAX Integer32 (1..2147483647)
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"This attribute uniquely identifies a Group."
::= { casaIpTrunkEntry 1 }
66368 Enhancement. The Casa Video Web UI has been enhanced to include the CPU rate, RAM
Operational, rate, and space-used statistics in graphic pie chart format on the System >
Web UI General screen.
(Low)
66450 Feature: The following features have been applied in the Casa Video Web UI:
Operational,
Web UI • The CPU Rate, RAM Rate, and Space Used pie charts on the System >
(Low) General screen now display tool tips for the respective Used and Free
areas of the charts.
• The Monitoring > QAM > Statistics screen now shows color variations for
the Available Bytes and Used Bytes areas of the chart.
66583 Defect: A fix in the software logic has been applied to correct a problem where
Possible service configuring channels 32 to 39 as video channels resulted in a QAM module
impact switchover. The software fix now supports this configuration.
(Medium

1-78 Release Notes

ID (Risk level)
66735 Defect. In cases with multiple IUCs in the OFDMA profile, inaccurate SNR
Possible service measurement on some IUCs were causing the CMTS to incorrectly switch (or
impact toggle) to the higher modulation instead of keeping with the lower modulation.
(Medium) The problem has been fixed.
67214 Enhancement: The show spectrum upstream <slot>/<port>.<chan> chan-width command
Operational, CLI now includes the previously missing 200000 Hz channel width value as
(Low) defined in the CASA-SPECTRUM-MIB
casaSpectrumMeasurementChannelWidth object.
Example:
CASA# show spectrum upstream 13/0 chan-width ?
<200000|400000|800000|1600000|3200000|6400000> channel
width value
67217 Defect: Software fixes and protections have been implemented to prevent the
Possible service upstream scheduler from getting stuck in a dead looping condition on the UPS
impact 16x4 when SID cluster updates are applied to the scheduler queue.
(Medium)
67463 Defect: An issue which was causing the upstream interface pre-equalization
Possible service extended-taps CLI setting to sometimes enable only 16 taps instead of 24 has
impact been fixed.
(Low)

Table 10. Release 7.2.3.2 Build 55fa changes and applied fixes

ID (Risk level)
66224 Enhancement. The CLI show system detail command now displays the Major and Minor
Informational, revision information for installed system modules in both the enable and diag
CLI modes.
(Low)
Note: Modules of earlier manufacture may not have the revision information
programmed into the module and the revision information will not presented in
the display.
Example:
CASA(config)# show system detail
Product: C10G, System Uptime:0 d, 8 h, 28 m, 15 s
System Time: Thu Jan 26 11:35:11 UTC 2017
128MHz, 5 PPM Crystal Clock
Module 6, Master SMM_2x10G, Status ACTIVE

Major rev 1, Minor rev 0
Serial_No: SB14BA7S0299 Part_No: PCA-0037-01
CFE version 12.4.11
Uptime: 0 d, 8 h, 28 m, 15 s
impact 16x4 and UPS 16x8 modules when SID cluster updates are applied to the
(Medium) scheduler queue.
68151 Defect: A problem which was preventing the patch file from being copied to the
Possible service standby SMM with the copy tftp <ip-address> <patchfile.tgz> patch
impact command has been fixed. The problem was observed on SMMs which did not
(Low) previously have a patch successfully applied.
69620 Defect: Software improvements have been applied to the QAM switchover processes
Possible service to prevent situations where modems could possibly lose lock on OFDM
impact channels during a QAM 8x192 module switchover. A problem was observed
(Low) where certain modems on OFDM channels would go into partial-service and
remain locked on SC-QAM channels after the switchover.
71976 Defect: The casaDevSoftwareMib has been removed from the SNMP MIB archive in
No service Release 7.2.4.1 to prevent possible security vulnerabilities at the CMTS.
impact
(Medium)

1-80 Release Notes
Table 10. Release 7.2.3.2 Build 55fa changes and applied fixes

ID (Risk level)
72645 Enhancement: The maximum number of supported DSG vendor parameter IDs has been
Operational increased to 48 to support customer requirements. Previously, the CMTS
(Low) configuration supported a maximum of 32 DSG vendor parameter IDs.
Example:
CMTS# show interface qam 3/0 | inc dsg
channel 0 dsg vendor-param-id 48
72757 Defect: A problem has been observed where the decryption engine process in the
Possible service UPS 16x8 optimized data path stopped functioning and was not able to receive
impact L3 packets for decryption. A corrective change was made to resolve the issue.
(Medium)


ID (Risk level)
67426 Defect: When operating in TaFDM mode with UGS service flows, a problem which
Possible service could cause the UPS process to fail with a resulting module switchover has
impact been fixed. Processing and placement of null grants into the TDMA channel
(Medium) when OFDMA burst is present has been revised to ensure correct insertion of
null grants into USG service flows.
impact 16x4 and UPS 16x8 modules when SID cluster updates are applied to the
(Low) scheduler queue.
70084 Defect: A software issue which could result in PowerKey VOD-encrypted video
Possible service sessions being corrupted after a QAM module switchover has been fixed.
impact Clear VOD, pre-encrypted SDV, and clear SDV sessions were not impacted by
(Medium) this issue.
70092 Defect: A software fix has been applied to correct a problem where transport stream ID
Possible service (TSID) was not being configured correctly for channels 36 to 47 on the QAM
impact 8x96.
(Medium)

ID (Risk level)
61948 Defect: When excessive packet jitter appeared in a video stream, either due to
Possible service network instability or SMM switchover, the video scheduler went into a state
impact which was dropping packets. This problem is resolved by monitoring PCR
(Medium) packet arrival time and compensating the excessive jitter during scheduling.

1-82 Release Notes
Table 13. Release 7.2.3.2 Build 4cb3 changes and applied fixes

ID (Risk level)
62988 Enhancement: The casaCmtsUSModemTable in the CASA-CABLE-CMCPE-MIB file has

SNMP been updated to include OFDMA channels in SNMP queries.
(Low)
63123, Defect: In configurations where there are two symbol rates on a single QAM port
63111 Possible service configured, there is a possibility of the wrong configuration being programmed.
impact
(Medium) A fix to correct the FPGA driver logic has been applied to correct an
intermittent issue which could cause the QAM 8x96 symbol rate configuration
to be incorrectly re-programmed in software after performing a system reboot
or QAM 8x96 module reset. Performing a QAM 8x96 switchover to the
redundant module corrects the problem.
63266 Defect: Performing the RFoG channel shutdown/no shutdown caused a single
Possible service RFoG group to be managed by two separate upstream scheduling threads
impact with a resulting corruption to the MAP timer. The problem caused an
(Medium) unexpected UPS module switchover.
A software fix has been implemented to remove the RFoG group from the map
timer when all channels are inactive. Protections have been applied to ensure
cleanup of the upstream queue on shutdown of an RFoG channel.
63576 Defect: When processing MPTS sessions, a packet queue counter corruption was
Possible service found in the DS scheduler which could result in a QAM module switchover to
impact the standby QAM module. This problem has been fixed.
(Medium)
63577 Defect: A recovery issue in the software which could cause encrypted sessions to
Possible service begin transmitting in the clear after a QAM module switchover has been fixed.
impact The problem was observed with the show video session command reporting
(Medium) the “Clear” state for some video sessions.
63684 Enhancement: Session queries/audits conducted by the Explorer Controller (EC) was causing
No service valid SDV sessions created by SRM to be incorrectly deleted by the EC. The
impact CCAP software has been revised to ensure that session queries and session
(Low) deletions are only granted to the creator of the session, such as SRM.
Protections in the software have been applied to ensure that the EC properly
recognizes and does not delete SDV sessions it did not build.


ID (Risk level)
64160 Defect: An snmpwalk of the docsBpi2CmtsDefaultSelfSignedManufCertTrust MIB

No service was returning an incorrect value of "trusted(1)" instead of “untrusted(2)” for
impact cable modems attempting to register and come online with self-signed
(Low) certificates. By default, the CMTS blocks cable modems attempting to register
with self-signed certificates.
64878 Defect: Revised configuration processing of the video simulcrypt cp (crypto period)
Possible service setting in the configuration has been implemented. A problem was observed
impact where the show video simulcrypt scg <identifier> command was reporting
(Medium) inconsistent nominal CP statistics regardless of the video simulcrypt cp
configuration setting. The parameter setting has also been revised to the
configuration range of 10 to 6000 seconds; the default setting is 30 seconds.
64879 Defect: A command handling error in the software which could cause a failure to
Possible service properly launch the system shell process at the time of an SMM 8x10G
impact switchover has been fixed.
(Medium)
64890 Defect: A fix has been applied to the redundancy logic to properly check the availability
Possible service status of the standby module and to ensure correct timing of line card
impact switch-overs to the standby slot. A case was reported where the standby UPS
(Medium) line card in system slot 8 was not assuming the active state for one of the UPS
line cards in a situation where multiple UPS line cards were simultaneously
reset.
64896 Defect: Software fixes to address a situation where a certain D3.1 modem with
Possible service multiple bonded TDMA channels and one OFDMA channel was unable to
impact complete unicast ranging over the OFDMA channel. The problem caused the
(Medium) OFDMA channel to be dropped with the modem going into upstream
partial-service. Both initial-tech unicast-ranging and initial-tech ofdma
unicast-ranging settings were enabled in the DOCSIS MAC interface.
The software fixes apply support for init-tech 6 (unicast IUC 3) and init-tech 7
(unicast IUC 4), and adjustments to the timing offset for OFDMA ranging
requests.

1-84 Release Notes

ID (Risk level)
64911 Enhancement: For single-carrier (SC) and OFDM capabilities, the supported QAM port power
Operational upper limit has been revised for both QAM 8x96 and QAM 8x192 modules.
(Low)
The port power maximum output levels are:
• 620 dBmV for <= 1 channel

• 610 dBmV for 2 channels
• 560 dBmV for > 128 channels
The default port power remains at 510 dBmV.

64920 Defect: There was an issue in two-stage PKE session creation so that sometimes
Possible service session query or deletion will fail. This error is now corrected.
impact
(Medium)
64923 Enhancement: The Casa database capacity has been extended to ensure that SNMP queries
No service to the casaCmtsCmMacToCpeEntry MIB report the same number of CPEs as
impact the CLI show cable modem cpe command output.
(Low)
64944 Defect: A problem which was causing the edge logger process to fail with an SMM
Possible service switchover after the issuing a no logging command or after a Telnet session
impact termination has been fixed. A software change has been applied to ensure that
(Medium) the logger process does not attempt to write to the log file after logging is
disabled.
64973 Defect: SNMP queries to the ifHighSpeed object in the IF-MIB file now report the
No service OFDMA calculated bandwidth consistently with the CLI show docsis
impact upstream channel utilization command output.
(Low)
64974 Defect: A timing issue in the software which was causing the show {cable | docsis}
No service downstream channel utilization command to report 0 utilization has been
impact fixed. The problem existed on the QAM 8x8 module only.
(Low)


ID (Risk level)
65080 Defect: TCP connectivity with the CCAP was lost after an SMM switchover with the
Possible service Explorer Controller (EC) SRM unable to create new video sessions after the
impact switchover.
(Medium)
The on-failover option has been added to reset-indication parameter in
Enhancement: video edis configuration context to enable the CCAP to send a reset indication
CLI to the EC at the time of an SMM switchover. The reset indication informs the
(Low) EC to reestablish the TCP connection with the CCAP so that video session
establishment is resumed.
Example:
CASA(conf-video-edis 6)# reset-indication on-failure
65138 Defect: A software change has been applied to enable direct TFTP transfer of the
Possible service PowerKey certificate installation application to the standby SMM instead of
impact using the configured loopback interface. When TFTP uses a loopback
(Low) interface as the source-interface for file transfers to the CMTS, as configured
with the ftp-tftp source-interface loopback <number> setting, there was a
possibility that the PowerKey certificate installer would not be replicated to the
standby SMM.
65140 Defect: An error in the software logic which could cause the shell.exe process to fail
Possible service with a resulting SMM switchover while editing the load-balance configuration
impact in the CLI has been fixed.
(Medium)
65266 Enhancement: The DHCPv4 and DHCPv6 Relay Agent Option TLV reported to cable modems
No service by the CMTS in DHCP provisioning packets has been updated to Minor
impact Version Number 1 to reflect DOCSIS 3.1 capability. Previously, Minor Version
(Low) Number 0 was used to reflect DOCSIS 3.0 capability.
65394 Defect: In a configuration where a video EDIS IP address was not present in the
Possible service configuration, video sessions created by the SRM could not be deleted. A fix
impact has been applied to ensure video sessions created by SRM can be deleted
(Medium) normally.

1-86 Release Notes
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes

ID (Risk level)
21489 Feature: Support for the SNMP mpegInputUdpOriginationTable object in the

SNMP SCTE-HMS-MPEG-MIB has been implemented for retrieval and presentation
(Low) of video input stream UDP statistics in SNMP queries.
Example:
1: mpegInputUdpOriginationIfIndex.266256.1 (integer)
1000079 [1000079]
2: mpegInputUdpOriginationInetAddrType.266256.1 (integer)
ipv4(1)
3: mpegInputUdpOriginationSrcInetAddr.266256.1 (octet
string) C0.1D.02.1D (hex)
4: mpegInputUdpOriginationDestInetAddr.266256.1 (octet
string) A9.01.01.01(hex)
5: mpegInputUdpOriginationDestPort.266256.1 (gauge) 67
6: mpegInputUdpOriginationActive.266256.1 (integer)
true(1)
7: mpegInputUdpOriginationPacketsDetected.266256.1
(integer) true(1)
8: mpegInputUdpOriginationRank.266256.1 (gauge) 1
9: mpegInputUdpOriginationInputTSIndex.266256.1 (gauge)
266256
35205 Enhancement: Support for BGP route redistribution to and between VRF instances (based on
Operational the route target) has been implemented. Leaked routes into VRFs will only be
(Low) sent to the customer edge router (CE). Previously, static routes had to be
configured for each VRF. Leaked routes in which the nexthop router is the
ip-bundle interface will enable static host routes to be added to the VRF
instances.
48602 Enhancement: The configurable lower frequency limit for an OFDM channel has been revised
Operational, CLI to 108000000 Hz. The previous lower frequency range in the CLI was
(Low) 115400000 to 119600000 Hz.
Example:
CASA(config-if-qam 0/0)# ofdm-channel 0 lower-freq ?
<108000000-1196000000> frequency in Hz

Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)

ID (Risk level)
51448 Enhancement. The maximum number of QAM modes on QAM 8x196 has been increased
Operational, CLI from two to three on a per-port basis to include up to two unicast modes and
(Low) one broadcast mode. Only one QAM mode may be applied to an 8-channel
block.

introduced in the Casa CLI to display detailed QAM mode statistics for all
ports. There can be up to three QAM modes for a QAM 8x192 module, two for
unicast and one for broadcast (the one with the positive ref_cnt). The second
broadcast mode (bc_mode 2) is used only in per channel interleave mode
where all the module channels have the same annex, modulation, and symbol
rates, and vary only between two interleave values.
Example:
Module 1:
Port 0:
admin status: UP
number uchan up: 24
number bchan up: 4
uchan in mode 1: 12
uchan in mode 2: 12
bchan in mode 1: 4
bchan in mode 2: 0
symbol_rate 6952
symbol rate 0

1-88 Release Notes

ID (Risk level)
53416 Enhancement: Support for selecting the number of upstream pre-equalization taps has been
Operational, CLI implemented in the interface upstream {<slot/port.channel>} configuration
(Medium) using the pre-equalization extended-taps parameter setting. If not enabled,
the default number of taps remains at 16. To revert to the default setting of 16
taps, apply the no version of the command.
Enabling extended-taps will enable all 24 taps of the equalizer. This could
provide the user with additional immunity to large echo and/or group delay
impairments.
Example:
CASA(config-if-ups 13/0.0)# pre-equalization ?
extended-taps support extended taps(tap equalizer),
default is off
CASA(config-if-ups 13/0.0)# pre-equalization

extended-taps
To revert to the default setting of 16 taps:
CASA(config-if-ups 13/0.0)# no pre-equalization

extended-taps


ID (Risk level)
53490 Feature: The following CLI commands have been added to allow users to configure
CLI number of OFDM channels per QAM 8x192 downstream port.
(Low)
• module <slot_num> ofdm-channels <num=1:2>
• show ofdm-channels [<slot_num>]
Example:
CASA(config)# module 1 reboot
CASA(config)# show ofdm-channels ?

| Output modifiers
<cr>
<number> module id
CASA(config)# show ofdm-channels 1

module 1 ofdm-channels 2
For more information, see the section “QAM 8x192 downstream module
enhancements.”
54736 Defect: NFS TCP PORT 2049 is no longer reserved in the system software.
No service Previously, TCP port 2049 was reserved for the NFS process (not in use) and
impact was unavailable as a communications port.
(Low)
55539 Defect: An issue which was preventing properly handling of the group delay in the
Possible service system has been fixed. The calculated coefficients for the cable modem were
impact incorrect, which caused the modem to transmit at a higher power than they
(Medium) normally would on some channels.
A fix has been implemented for the UPS 16x8 and UPS 16x4 upstream burst
receivers to better support cable plants with a large group delay. The fix
improves the receiver's capability to lock on to the preamble and subsequently
maintain lock.

1-90 Release Notes

ID (Risk level)
55556 Feature: The show cable admission-control interface {ofdm <slot/port/channel> |

CLI ofdma <slot/port.channel> command has been introduced to in the Casa CLI
(Low) to display OFDM or OFDMA bandwidth allocation over each application class.
Example:
CASA# show cable admission-control interface ofdma 11/15
App-Class Exclusive Non-Exclusive Curr-Resv Curr-Ovrsb
8.1 0 50 0 0
8.2 50 0 0 0
8 50 50 0 0
9.1 0 20 0 0
9 10 10 0 0
CASA# show cable admission-control interface ofdm 0/4/0

1 20 10 0 0
2 10 20 0 0
3 40 10 0 0
56268 Feature: The system bootfile update command has been introduced in the Casa CLI
CLI, to reduce the time it takes to complete system boot-up. The new command
Performance prepares the line card boot image by extracting the necessary files to the
(Low) CMTS tftpboot directory prior to performing the actual system reboot. This
means that the system reboot process will be freed from the file extraction
process, reducing the boot-up time.
Example:
CASA# system bootfile update
56322 Enhancement: The maximum length of an IPv4 or IPv6 prefix name has been increased from
Operational, CLI 32 to 256 characters in all configuration instances where a named prefix list is
(Low) applied.
56365 Enhancement: To speed up system boot time, priority processing has been revised to allow
Operational, line cards to come up faster. Line cards now acquire SMM status information
Performance at the SMM CONFIG state instead of waiting for the SMM RUNNING state.
(Low)


ID (Risk level)
56380 Enhancement: The system service-delay {snmp <minutes> | tftp-proxy <minutes>}

Performance, command allows users to specify the number of minutes to delay SNMP and
CLI TFTP processing to shorten system boot-up time and to enable faster modem
(Low) registration with the CMTS. The command instructs the CMTS to temporarily
block SNMP packets and to delay the TFTP proxy for the configured number of
minutes before the SMM recovers one or both services.
The default setting is 0 (disabled). Specify a number in the range 0 to a

maximum of 60 minutes.
Example:
CASA(config)# system service-delay ?
snmp delay before processing SNMP
tftp-proxy delay before processing TFTP proxy
CASA(config)# system service-delay snmp ?

<num> time in minutes, max delay 60 (default 0)
CASA(config)# system service-delay snmp 40

CASA(config)# system service-delay tftp-proxy 40
56448 Feature: The [no] cable partial-service tx-power-deficit command has been
Operational, introduced in the Casa CLI to enable DBC reduction of the upstream channel
CLI, set in situations when modem maximum transmit power lowers due to
(Medium) attenuation changes in the cable plant. This setting is enabled by default so
that modems with adequate transmit power to support upstream channel
bonding are recoverable from a marked partial-service state. Prior to the fix,
modems affected by attenuation changes would DBC to channel 1 and would
not be placed in partial-service for eventual recovery.
Apply the no form of the command to disable this setting.
Example:
CASA(config)# cable partial-service tx-power-deficit
CASA(config)# show running-config | inc deficit
cable partial-service tx-power-deficit
CASA(config)#

1-92 Release Notes

ID (Risk level)
56455 Defect: Possible A problem which was resulting in some pseudo wire (PW) tunnels having
service duplicated in-labels caused VPWS traffic to go down. The problem was
impacting observed after changing the Control-Word bit setting to disable at the VPWS
(Medium) neighbor. The problem resulted in the system attempting to use stale virtual
circuit (VC) labels instead of allocating new labels. This problem has been
fixed.
56460 Enhancement: The show cable modem offline counters command output has been
Operational, CLI enhanced to include the rngfail_R2 and rngfail_RC field columns to distinguish
(Low) between R2 and RC cable modem ranging failures.
Example:
CMTS(config)# show cable modem offline counters
Docsis-Mac rngfail_R2 rngfail_RC Dhcpfail Tftpfail...
1 0 0 0 0
2 0 0 0 0
Total: 0 0 0 0
56505 Enhancement: The maximum length of an route-map name has been increased from 32 to
Operational, CLI 256 characters in all configuration instances where a named route-map is
(Low) applied. The route-map description parameter has also been increased from
64 characters to 256 characters.
56582 Defect: A fix has been applied to correct a QAM 8x192 module periodic status polling
No service issue and a resulting endless looping condition which caused the QAM 8x192
impact module to fail heartbeat detection. The problem caused the QAM 8x192
(Low) module to switch over to the redundant module due to expired keep alive
timers. The software fix corrects the status polling logic and incorporates
timing limits to prevent unconditional looping situations. This issue caused the
XLP2's Ethernet interfaces to experience a disruption which resulted in a
secondary issue observed as a XAUI timeout error.
56629 Enhancement: Improved cable modem registration time has been implemented in Release
Operational, 7.2.3. A software change to move BPI operation to a separate thread has been
Performance applied to optimize CPU usage when a large number of cable modems are
(Low) registering with the CMTS.
56682 Defect: Intermittently after a system reboot, D3.1 modems may not be able to come
Possible service up on the OFDMA channel. A reboot of the UPS module was necessary to
impact recover the D3.1 modems. This issue has been fixed.
(Medium)


ID (Risk level)
56777 Enhancement: The upstream interface minimum and maximum edge frequency ranges have
Operational, CLI been revised to 15 MHz and 55 MHz respectively for the UPS 16x8 with the
(Low) I/O 32x4 module. The previously supported frequencies did not extend below
16 MHz or above 52 MHz.
Example:
This board does not support higher than 55 MHz frequency.

This board does not support lower than 15 MHz frequency.

56967 Defect: A software fix has been implemented to correct a problem where a C40G
No service system fan tray module (left or right) could be incorrectly reported as missing.
impact Correct status is now reported whenever a fan module is pulled out or inserted
(Low) into the chassis. Previously, an active fan module was incorrectly reported as
missing after the system performed a fan tray module check.
57000 Defect: Software corrections were made to optimize upstream performance of the
Possible service UPS 16x8 line card.
impact
(Medium)
57054 Feature: The show dmesg peer command has been introduced in the CLI to display
CLI diagnostic messages associated with the SMM presently in standby status.
(None) The command operates in any CLI mode (enable, config, diag).
The show dmesg command presents messages from the boot process in a
controlled manner after the system has started without having to observe the
console output. Even after the system has fully booted, the kernel may
occasionally produce further diagnostic messages which are also captured in
this log. Look for any key words such as Oops, Panic, Warning, or Failure.

1-94 Release Notes

ID (Risk level)
57056 Enhancement: The OFDMA configurable subcarrier-group-minislot end frequency has

Operational, CLI been revised to reflect 400kHz minislots to support eight 50kHz subcarriers for
(Low) 2k FFT and sixteen 25kHz subcarriers for 4k FFT. The valid range has been
changed to 5400000 to 101000000 Hz; the previous range was 11400000 to
101000000 Hz was determined to be in error.
Example:
CASA(conf-minislot-cfg 30)# subcarrier-group-minislot 1 ?
<5000000-100600000> start frequency
CASA(conf-minislot-cfg 30)# subcarrier-group-minislot 1

5000000 ?
<5400000-101000000> end frequency
57134 Defect: After performing a shutdown and no shutdown on a video interface input
Possible service port, some video pass-through sessions failed to become active. A software
impact change has been applied to upstream scheduler to ensure proper handling of
(Medium) the active session status for re-establishing the video session after a
shutdown/no shutdown of the input port.
57142 Defect: A software fix has been applied to ensure successful snmpwalk queries to the
No service SNMP MIB table docsQosCmtsMacToSrvFlowTable (OID
impact 1.3.6.1.4.1.4491.2.1.21.1.11.1.3) for cable service flows. The fix now supports
(None) cases where there is only one index entry to be returned by the SNMP query.
Previously, the message “No such instance currently exists for this OID” was
observed at the time of the query.


ID (Risk level)
57201, Feature: The following SNMP objects have been added to the casa-cable-cmcpe-mib
57726 SNMP file to support upstream and downstream secondary modem counts as
(Low) currently supported with the show cable modem downstream summary and
show cable modem upstream summary commands:
-- 1.3.6.1.4.1.20858.10.12.1.1.1.6
casaCmtsUSSecondaryModemCount OBJECT-TYPE
SYNTAX Unsigned32
STATUS current
DESCRIPTION
"The count of secondary modem on the upstream
channel."
::= { casaCmtsUSModemEntry 6 }
-- 1.3.6.1.4.1.20858.10.12.1.2.1.6
casaCmtsDSSecondaryModemCount OBJECT-TYPE
SYNTAX Unsigned32
STATUS current
DESCRIPTION
"The count of secondary modem on the downstream
channel."
::= { casaCmtsDSModemEntry 6 }
Example:
1: casaCmtsUSSecondaryModemCount.5005632 (gauge) 1
***** SNMP QUERY STARTED *****1:

1: casaCmtsDSSecondaryModemCount.3001536 (gauge) 1
57353 Defect: After performing a QAM module switchover, a timing error in the software logic
Possible service caused a video stream to being processed as a data stream, causing the
impact output program number to change and match the input program number (1).
(Medium) The fix removes the timer in the switchover process so that previously
detected video stream PCRs are not dropped at switchover time. With this fix,
video output program numbers will be maintained.

1-96 Release Notes

ID (Risk level)
57363 Enhancement: The [no] mirror cm traffic <ip_address> in the Casa diag mode has been
Operational, CLI enhanced with the loopback option to specify the loopback interface number
(Low) as the source IP address for traffic mirrored to a destination IP. Specify the
existing loopback interface number in the range 0 to 255. Apply the no version
of the command to remove the current setting.
Example:
CASA(diag)# mirror cm traffic 192.168.8.8 ?
<cr>
<mac_addr> xxxx.xxxx.xxxx. mac addr of cm
loopback loopback interface name for source address
CASA(diag)# mirror cm traffic 192.168.8.8 loopback 0

57376 Defect: A fix has been applied to address a messaging and memory buffer size
Possible service corruption in the upstream scheduler which resulted in the UPS module failing
impact over to the redundant module. The problem was observed with the UPS 16x4
(Medium) module. The fix corrects the data structures which keep track of upstream
grants processed at the UPS module.
57405, Defect: When editing the QAM 8x192 channel interleave setting under the interface
59740 Possible service qam <slot/port> configuration, applying interleave 64 or interleave 128 was
impact rendering a single-carrier channel unusable. This problem has been fixed.
(Low)
57431 Defect: Incorrect spelling of the Cancel button on the Monitoring->Video->Session
No service Details screen in the Casa Video Web interface has been addressed.
impact
(Low)


ID (Risk level)
57673 Feature: The [no] snmp trap logging video alarm {bitrate-threshold <number>|
CLI, Operational missing pat-pmt-pid} command has been implemented in the Casa CLI.
(Low)
The bitrate-threshold parameter sets the bitrate per second (bps) low
threshold in which an SNMP trap will be generated if the detected rate is below
the configured value. The missing pat-pmt-pid parameter forces an SNMP
trap message if any of the required video elements (PAT, PMT, or PID) is
missing from the video session stream. Apply the no form of the command to
cancel the current setting.
Example:
CASA(config)# snmp trap logging video alarm
bitrate-threshold ?
<0-4294967295> bitrate(bps)
bitrate-threshold 1000
CASA(config)# snmp trap logging video alarm missing

pat-pmt-pid
57695 Defect: A software fix has been implemented to correct a possible failure if a clear
Possible service cable modem reset or a clear cable modem offline command is issued
impact while the affected modem is in the partial-service state and is being recovered
(Medium) via DBC.
57857 Defect: A fix has been applied to correct SMM module status inconsistencies between
No service the CLI show system command output and module status reported in SNMP
impact queries after replacing SMM modules in system slots 6 and 7. A problem was
(Low) observed where the active SMM was being reported as NOT READY in SNMP
queries resulting in generation of SNMP trap messages.
57889 Defect: Spectrum management statistics are now correctly calculated and reported in
No service queries to the docsIf3CmtsSpectrumAnalysisMeasAmplitudeData SNMP MIB
impact and with the CLI show spectrum-meas upstream <slot/port.channel>
(Low) command. Previously, continuous wave (CW) ingress data was missing from
the output. The fix was applied to calculations for the UPS 16x8 module; the
UPS 16x4 module was not affected.
58066 Defect: A software change to correct the lower edge OFDMA spectrum center
No service frequency of subcarrier 0 (SC0) to 1350000 Hz for 50 kHz spacing (per
impact DOCSIS PHYv3.1 specification) has been applied. Previously, the center
(Low) frequency for SC0 was set to 1325000 Hz for 50 kHz spacing.

1-98 Release Notes

ID (Risk level)
58366 Defect: An issue which caused SMM7 to reboot right after switchover has been fixed.
Possible service The problem was due to a software logic error which resulted in a process
impact exception, causing the SMM to go down. Conflicting code paths were
(Medium) determined as the root cause of the problem.
58706 Enhancement: The SNMP process has been optimized for faster retrieval of large SNMP
SNMP, query responses to snmpbulkget and other SNMP polling methods. Overall
Performance improved SNMP performance can be expected with this enhancement.
58829 Defect: A correction has been applied to the online help text to proper reflect power
No service levels specified in the CLI and in the Casa Video Web interface. The acronym
impact “db” has been replaced with “dBmV” in the help text.
(Low)
Example:
CASA(config)# interface qam 0/0
CASA(config-if-qam 0/0)# power ?
<250-620> channel power in tenth of dBmV (port
power: 450-620; channel power: 250-620)
CASA(config-if-qam 0/0)# power 523
CASA(config-if-qam 0/0)# channel 0 power-attenuation ?

<0-100> attenuation value in tenth of dBmV
(default: 0)
58966 Defect: A fix has been applied to correct a problem where a VoD table mode session
Possible service could not be established at the set-top box without interactively changing and
impact then re-applying the original video session transport stream ID (TSID). The
(Medium) problem was due to a software issue which was preventing the channel from
scheduling the program association table (PAT), keeping the VoD session from
starting. Re-applying the TSID allowed the PAT to be rebuilt with the affected
VoD session. This problem has been fixed.
58980 Feature: Log messages associated with Casa Spectrum Management (CSM)
Operational, CLI modulation hopping have been revised with a severity level of
(Low) INFORMATIONAL.(6). Previously, the modulation hopping messages were
logged at the DEBUGGING (7) severity level.
The [no] cable spectrum syslog command has been introduced in the Casa
CLI to enable and disable logging of CSM messages. When enabled, syslog
messages will be sent to the configured syslog hosts.
Example:
CASA(config)# cable spectrum syslog


ID (Risk level)
59026 Enhancement: Improved resource management of PacketCable gate-set packets has been
Performance implemented to reduce the possibility of bandwidth allocation errors when
(Low) multiple duplicate multicast-based sessions are requested in quick succession
from a single cable subscriber (ex. fast up and down channel surfing).
A new multicast join session which is already in effect will now be

acknowledged using the current gate-set ID when the duplicate session is
requested. The change enables the CMTS to reduce the number of
bandwidth-consuming transactions by immediately freeing the duplicate
session gate-set request in this situation.
59053 Defect: When a TDMA/ATDMA channel overlapped with an OFDMA channel under
Possible service high traffic load conditions, the upstream scheduler was sometimes able to
impact satisfy UGS grant allocation. The problem has been fixed.
(Medium)
59067 Defect: A QAM 8x96 switchover with reported under-run errors occurred after
Possible service configuring video channels 32 to 37. A fix has been applied to correct a
impact condition where the FPGAs were not operating in the same mode when only
(Medium) shared channels were enabled on one shared FPGA. The QAM 8x96 health
check process will only be turned on after the shared channels have been
enabled.
59081 Defect: A software error in the Protocol Independent Multicast (PIM) process which
Possible service caused network connect and service messages to get out of sequence in the
impact processing queue with a resulting null pointer condition has been fixed. The
(Medium) problem was observed in a test network.
59150 Defect: A software change to include the primary security association identifier (SAID)
No service in TLV 43.5.10 for L2VPN-capable modems has been applied. The
impact L2VPN-capable modem will handle the primary SAID as the L2VPN SAID;
(Low) packets encrypted with the primary SAID will be processed as L2VPN packets
for reliable forwarding to CPEs.
59157 Enhancement: The 200K option has been reinstated to the SNMP
CLI, SNMP casaSpectrumMeasurementChannelWidth MIB object in the
Operational casa-spectrum-mib file. The revised range is 200 kHz to 6400 kHz.
(Low)
The 200000 option has been added back to the show spectrum upstream
<slot/port.channel> chan-width <width> command. The revised range is
200 kHz to 6400 kHz.

1-100 Release Notes

ID (Risk level)
59160 Defect: A condition in which the system logger could be consumed with debugging
Possible service request messages leading to a memory buffer overflow has been fixed. The
impact problem was observed after configuring the system with the debug cable
(Medium) modem verbose option, which caused the message receive queue to fill up
with dropped messages consuming the memory buffer. To prevent the
problem, received debug request messages are now written to file before
being decoded and removed.
59501 Defect: A problem in which multicast DSIDs were not being removed from the cable
Possible service modem ranging list after DBC/DCC and release of the multicast sessions.
impact Previously, the modem’s DSID list would continue to increase and exceed the
(Low) modem’s DSID list capacity.
Timer adjustments have been implemented to ensure that multicast session

DSIDs are not blocked from removal after modem DBC/DCC or timer
expiration.
59584 Defect: A software fix has been applied to correct handling and translation of some
Possible service known TCP protocol port numbers in access-control lists (ACLs). A situation
impact was observed where TCP Port 4737 was translated to the keyword “ipdr”, but
(Low) then dropped from the ACL when the system failed to covert the keyword back
to the known TCP port number after performing a system reboot. Known port
numbers for IPDR, EDIS, and NGOD are now supported for proper handling in
ACLs.
59696 Enhancement: The start-udp-offset parameter of the video table custom prog-per-chan
CLI <number> setting in the Casa CLI has been changed from a fixed sequence
Operational of values to the range <1:65535>.
(Low)
Example:
CASA(config)# video table custom prog-per-chan 64
chan-per-port 24 start-udp-offset 65 skip-chan 12
59706 Defect: A software change has been applied to correct a problem where certain ACL
Possible service rules were incorrectly denying traffic. The problem was caused by additional
impact checks to TCP/UDP packets which resulted in possible ACL mismatches.
(Low)
60080 Defect: A problem which caused the CMTS to send BGP notification packets to a BGP
Possible service peer router when a SAFI OPEN capability message was received at the CMTS
impact has been fixed. This issue caused the BGP peer session to disconnect. BGP
(Low) will now ignore the SAFI OPEN capability update message; notification
packets will not be sent.


ID (Risk level)
60348 Enhancement: The maximum number of channels per DSG tunnel-group has been increased
Operational, CLI to 2560 with a maximum of 5120 DSG channels across all tunnel groups
(Low) system wide. Previously, the software supported up to 1280 DSG channels per
Example:
reached: 5120 ! !
60507 Defect: The CMTS measured cable modem timing offset displayed with the show
No service cable modem command was changing over time due to a calculation error.
impact The actual timing offset to the CM did not change. The timing offset reported
(Low) by the CM with show cable modem phy remained correct. This was a display
issue.
61022 Feature: The output-port-base <0 |1> parameter has been added to the video edis
Operational, CLI configuration to provide an additional channel offset of 1 for interoperability
(Low) with the Cisco SRM Explorer ControllerTM for QAM setup and creation of VOD
sessions. The default setting if not configured remains at 0.
Example:
CASA(conf-video-edis 1)# output-port-base ?
<0-1> 0 or 1 base. Default is 0
CASA(conf-video-edis 1)# output-port-base 1
To revert to the default setting:

61760 Enhancement: Support for two-stage video session creation when performing encryption with
Operational the Cisco SRM Explorer ControllerTM has been implemented in this software
(Low) image. The enhancement changes the behavior of how an encrypted session
creation response occurs when no CA data is present with the Encrypted Flag
set to 1. The second stage handles the video session creation request.

1-102 Release Notes
Table 15. Release 7.2.1.0 Build 482c changes and applied fixes
Tracking ID Fixed in Original problem/fix description

version
55148 482c OFDMA support has been extended to the earlier UPS 16x8 modules. Modules
having serial number prefixes beginning with UB13 and greater, as well as
earlier serial number prefixes, such as UB11CD9S0003, will now support
OFDMA. Use the show system command to verify and display module serial
number information at the CMTS.

Table 16. Release 7.2.1.0 Build 47da changes and applied fixes

version
41408 47da Enhancement. Support has been added for the

docsIf31CmtsCmUsOfdmaChannelStatusTable objects in the SNMP
DOCS-IF31-MIB to support queries to OFDMA channel signal statistics and for
SNMP configuration of the RxMerThreshold (read-write) setting.
• docsIf31CmtsCmUsOfdmaChannelRxPower
• docsIf31CmtsCmUsOfdmaChannelMeanRxMer
• docsIf31CmtsCmUsOfdmaChannelStdDevRxMer
• docsIf31CmtsCmUsOfdmaChannelRxMerThreshold
• docsIf31CmtsCmUsOfdmaChannelThresholdRxMerValue
• docsIf31CmtsCmUsOfdmaChannelThresholdRxMerHighestFreq
• docsIf31CmtsCmUsOfdmaChannelMicroreflections
• docsIf31CmtsCmUsOfdmaChannelHighResolutionTimingOffset
• docsIf31CmtsCmUsOfdmaChannelIsMuted
• docsIf31CmtsCmUsOfdmaChannelRangingStatus
45350 47da PacketCable voice traffic packets over a UGS flow on an OFDMA channel
resulted in HCS errors and were dropped. This problem has been fixed.
46203 47da Enhancement. Three new IPDR ad hoc sessions have been added in Release
7.2.1
• session 19 -- CM-REG-STATUS-TYPE-ADHOC
• session 20 -- CMTS-CM-US-STATS-TYPE-ADHOC
• session 21 -- DOCSIS-DIAG-LOG-TYPE-ADHOC
These ad hoc sessions previously creating interoperability issues with Gauvus

Pipeline collectors. If these ad hoc session are not needed, disable these
sessions with the following commands in the Casa config mode.
• no ipdr enable topo-adhoc

• no ipdr enable cm-status-adhoc
• no ipdr enable us-status-adhoc

1-104 Release Notes
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)

version
51113 47da An issue which was causing intermittent jitter in the FPGA synchronization
message and possible time stamp errors on upstream service flows has been
fixed. Uncorrectable FEC errors on upstream ports were observed, which
caused some cable modems to flap.
51743 47da Enhancement. The show cable ods-report ofdm <slot/port/channel>
command has been added to the Casa CLI to display the OPT-RSP message
containing Rx MER statistics for 7600 different subcarriers for an OFDM
channel with single-carrier spacing of 25 KHz.
Example:
CASA# show cable ods-report ofdm 11/0/0
6814.01f0.3e47 on ofdm 11/0/0 opt_rsp total_len=7525 - 6
TLV head = 7519 subcarrier
RxMER per Subcarrier:
be bc c1 c2 c0 c0 c3 bd c3 bf ba c2 c2 be
be bd c1 bf bf c3 c0 ba c6 c0 bf bd c1 c3
be be be bd c1 c3 bf c2 c0 c0 bf c2 bd c1
c3 c3 c1 be bc c1 c1 ba c2 c0 bf bf c0 c0
be c1 c1 bc bf c1 c2 be
52257 47da Enhancement. The subnet option has been added to the proxy-arp unknown
parameter in the IP bundle address configuration to allow the CMTS to respond
to ARP requests from CPE devices which are outside of the IP bundle address
scope. The enhancement addresses situations where CPE devices were not
able to register due to the CMTS not responding to ARP requests from unknown
IP address subnets. The default setting is disabled.
Use the [no] cable proxy-arp unknown subnet command to set the unknown
subnet option globally in the configuration. The IP bundle proxy-arp unknown
subnet setting takes precedent over the global setting. The global setting only
takes effect only when the IP bundle proxy-arp unknown subnet setting is not
configured on an IP bundle subnet.
Example:
CASA(ip-bundle 15)# ip address 6.6.7.7 255.0.0.0 classname
proxy-arp unknown subnet
Example:
CASA(config)# cable proxy-arp unknown subnet


version
52390 47da Enhancement. The hash tag # character is now used with the show cable
modem output to indicate the OFDM channel profile ID (PFID) which is
unusable due to a DS OFDM PROFILE FAIL status message and replaced with
another OFDM profile. The hash tag indicates the affected profile ID.
Example: Hash tag in OFDM downstream channel set at 11/0/0w, PFID 2.

CASA# show cable modem fe89.2cbc.b0e2 verbose
MAC Address :fe89.2cbc.b0e2
IP Address :10.66.1.26
MAC Status :online
CM-ID :5
Prim Sid :320
MAC Domain :1
Service-Group :1
Upstream Channel Set :0/0.1/0, 0/
0.2/0, 0/0.3/0,0/0.0/0, 0/1.0w
Downstream Channel Set :11/0/
0w(0,3,1,2#), 11/0/1,11/0/2, 11/0/3, 11/0/4, 11/0/5, 11/0/
6, 11/0/7, 11/0/0
Unusable channel list :0/0.0w

1-106 Release Notes

version
52606 47da Enhancement. The following objects have been added to the
CASA-VIDEO-TS-MON-MIB file to support SNMP monitoring of the following
ECMG statistics:
• Current Crypto Period (CP)

• CP remaining time
• ECM channel ID range
• ECMG VRF
• EIS VRF
1.3.6.1.4.1.20858.10.57.7
• casaVideoSimuEcmgCurrentCryptoPeriodNum
• casaVideoSimuEcmgCryptoPeriodRemainingTime
• casaVideoSimuEcmgEcmChannelIdStart
• casaVideoSimuEcmgEcmChannelIdEnd
• casaVideoSimuEcmgEcmVrfName
• casaVideoSimuEcmgEisVrfName
1.3.6.1.4.1.20858.10.57.7.5
• casaVideoSimuConnectionDomainName
• casaVideoSimuConnectionAccessCriteria
• casaVideoSimuConnectionEcmChannelId
• casaVideoSimuConnectionStreamEcmId
• casaVideoSimuConnectionStreamStatus
52687 4682 A software error which was preventing successful CLI ping requests to the
configured ip domain-name setting has been fixed. Ping responses were
observed with the message “Invalid destination.” The software fix revises code
to ensure proper checking for valid and invalid IP domain names.


version
53377 47da A fix has been applied to include all supported cable modem device classes in
the show cable modem docsis-device-class command output. The possible
DOCSIS devices which can now appear in the Device Class column include:
CM, eCM, eMTA, eSTB, ePS, eTEA, eRTR, eDVA, and eSG.
Example:
CMTS(config)# show cable modem docsis-device-class
MAC AddressUS DS Mac Prim Reg Device Class Reg

Intf Intf Status Sid Ver Priv
fe11.b300.0000 13/15.0w 10/0/0 online 45 1.1 eCM eSG BPI
fe11.b300.0001 13/15.0w 10/0/0 online 46 1.1 eCM eSG BPI
53470 47da When performing a manual SMM switchover with the ha redundancy
command, D3.1 modems connected over OFDMA only would go offline until the
affected UPS module was rebooted. The problem has been fixed.
53482 47da Enhancement. The initial-tech ofdma command has been implemented in the
interface docsis-mac configuration to specify the initial ranging technique to be
applied when a D3.1 modem is performing upstream ranging over an OFDMA
channel.
• broadcast-ranging — TLV 46.7 value 1; default

• probing — TLV 46.7 value 5
• station-ranging — TLV 46.7 value 7
• unicast-ranging — TLV 46.7 value 6:
Example:
CASA(config-if-mac 1)# initial-tech ofdma unicast-ranging
53503 47da Enhancement. Handling of IPv6 Neighbor Discovery (ND) packets have been
revised to mitigate denial-of-service vulnerabilities to IPv6 routing. IPv6 ND
packets with TTL 255 (direct neighbor) are now handled with higher priority over
the lower priority non-TTL 255 ND packets.
53653 47da A problem has been observed where a D3.1 modem may not be able to
complete initial ranging and come online with the CMTS over an OFDMA
channel after resetting and recovering the affected UPS module. The issue
occurred after rebooting the UPS module without the OFDMA configuration
present, and then re-configuring OFDMA where the modem failed to range on
the OFDMA channel. This problem has been fixed.

1-108 Release Notes

version
53795 47da Issuing the show tech-support command was causing the upstream process
to become unresponsive at one or more UPS modules. This problem has been
fixed.
54061 47da Enhancement. The show iftable ofdma command has been implemented in
the Casa CLI to display OFDMA upstream interface details and current status,
with up to one OFDMA upstream channel per port.
Example:
CASA# show iftable ofdma
------------------------------------------------
ifIndex: 16000160
ifDescr: OFDMA Upstream 1/0.0
ifType: ifType_ofdma
ifPhysAddress: 00:00:00:00:00:00
ifAdminStatus: Up (2)
ifOperStatus: Up(1)
------------------------------------------------
ifIndex: 16000161
ifOperStatus: Up (1)
54090 47da Mandatory TLV 46.10 is now sent in the REG-RSP-MP message from the
CMTS to DOCSIS 3.1 modems per CableLabs specification (MAC MULPI
C.1.5.1.10 P1.6hi97), as defined below:
When present, this TLV specifies the value for P1.6hi[DOCSIS PHYv3.1]. The
CMTS MUST include the P1.6hiTLV in the REG-RSP-MP being sent to a
DOCSIS 3.1 CM. The CMTS MUST include the P1.6hiTLV in a DBC-REQ
message that modifies the TCC encodings of a DOCSIS 3.1 CM.
The CMTS MUST NOT include the P1.6hiTLV in TCC encodings sent to a
DOCSIS 3.0 CM.
Because it is not associated with a single upstream channel, the CMTS sets the
value of the Upstream Channel ID to "0" when sending this sub-TLV in a TCC
encoding. Since this sub-TLV is for informative purposes, the value of the
Upstream Channel Action is irrelevant.
46.10 1 P1.6hi expressed in units of ¼ dBmV [DOCSIS PHYv3.1]


version
54179 47da Enhancement. The show command history web-gui command has been
implemented in the Casa CLI to capture management activity processed
through the Casa Video Web interface in the current session. On a line-by-line
basis, the output includes the date and time of command execution, the user
login of the person who executed the command, and the GUI command
presented in the equivalent CLI syntax.
Show commands are excluded and do not appear as part of the command
history.
Example:
CASA# show command history web-gui
2016-07-05 16:33:16 <root> shutdown
2016-07-05 16:33:16 <root> no ip pim sparse-mode
2016-07-05 16:33:16 <root> ip address 192.168.5.10
2016-07-05 16:33:16 <root> gige 6/0 mode active
2016-07-05 16:33:16 <root> no vrf forwarding
2016-07-05 16:33:16 <root> no description
2016-07-05 16:33:16 <root> interface trunk 2
2016-07-05 16:33:16 <root> config
2016-07-05 16:32:10 <root> video pat-interval 100
2016-07-05 16:32:10 <root> config
CASA#
54232 47da Handling of malformed BGP update packets has been revised at the CMTS to
ensure that bad packets are ignored to prevent connectivity issues with BGP
peers. Previously, the CMTS would continue to process the malformed packet
and return a notification error message to the peer. BGP will not process any
packet from the peer until adjacency with the CMTS is reestablished.
54308 47da Software fixes have been applied to correct a problem where DSID labels for
multicast sessions were not being successfully sent to set-top boxes due to
DBC failures, causing mismatched or missing DSID labels to exist between the
CMTS and cable modems. Improved DBC handling of labels has been
implemented to guard against duplicate or unconfirmed DSIDs during add and
delete. DSID add failures will cause the multicast session to be deleted.

1-110 Release Notes

version
54347 47da New feature. The video table custom command has been introduced in the
CLI to allow users to add new video on demand (VOD) table modes beyond
those provided by the Casa configuration (mode0 through mode6). The table is
created using the parameters specified in the command.
• prog-per-channel — Number of programs per QAM channel; 32, 64, or 256

(depending on the QAM module); the default is 64.
• chan-per-port — Number of QAM channels per RF port in the range 1 to
32; the default is 32.
• start-upd-offset — Starting UPD offset; first valid UDP port for the channel
mapping. This is an optional setting with allowed values 1, 33,65, or 257; the
default is 1.
• skip-chan — Number of QAM channels to skip in addressing between two
consecutive ports; This is an optional setting in the range 0 to 12; the default
is 0.
Example:
54350 47da The show user current command output now reports the correct TTY
connection type in AAA requests to a TACACS server. Previously, the PTS type
name (Pseudo Terminal Slave) was being reported in all cases instead of the
actual TTY type for the AAA session.
54424 47da The error “get_if_stats_ipv4_file() Stat /proc/net/dev_snmp/lo<number> failed”
was observed on the system console when retrieving video loopback interface
statistics with the show interface loopback command. The problem has been
fixed in the software.
54448 47da A problem which was causing channels to be incorrectly reported in the UP
state when the DOCSIS MAC domain was in the DOWN administrative state
has been fixed. The problem was observed with the show interface
docsis-mac <number> topology command.


version
54500 47da Software fixes have been applied to correct a problem where DSID labels for
multicast sessions were not being successfully sent to set-top boxes due to
DBC failures, causing mismatched or missing DSID labels to exist between the
CMTS and cable modems. Improved DBC handling of labels has been
implemented to guard against duplicate or unconfirmed DSIDs during add and
delete. DSID add failures will cause the multicast session to be deleted.
Enhancement. The show cable modem dbc-failure command has been

implemented in the CLI to display cable modems which have a non-zero DBC
failure count and are failing DBC with the CMTS. The command displays total
number of DBC failures and timeouts per DSID, and the last DBC error code.
Example:
CASA# show cable modem dbc-failure
MAC Address Total TimeOut DSID LastCode
e448.c7ba.5260 10 10 8 537(RETRY_EXHAUST)
CASA#
54580 47da A dynamic IGMP join message from a CPE/Router (on RF side) containing
224.0.0.2 group address record may have caused a loss of LDP adjacency with
the neighboring routers on SMM NSI side.
After a UPS line card switchover, the CPE/Router on the RF side may have sent
a new IGMP join message which contained multiple entries including 224.0.0.2.
The root cause is most likely the IGMP join to the link-local multicast address
224.0.0.2.
A fix has been added to filter out multicast joins to link-local address 224.0.0.x
from any sources (either static or dynamic).
54635 47da Enhancement. The Monitoring->Video->Session functionality in the Casa
Video Web interface has been revised to support the show video session all
brief command output. Highlight the session row and select the Detail button at
the upper right area of the screen to display session-specific statistics (show
video session <session-id>).

1-112 Release Notes

version
54794 47da A software revision to provide ACL filtering of sunRPC (port 111) UPD and TCP
traffic has been implemented when using the sunRPC protocol name in a single
ACL permit or deny rule.
In the following deny rule specifying the sunRPC protocol, traffic on both TCP
and UDP port 111 will be blocked.
Example:
CASA(config)# show ip access-list abc
10 deny sunrpc any any
To block UPD port 111 traffic only, but allow TCP port 111 to pass:
CASA(config)# show ip access-list abc

15 deny udp any any 111 any
54802, 47da A problem which was causing SSH user logins to the CMTS with TACACS
54979 authentication to report insufficient privileges with no enable mode access has
been fixed. The issue was observed with a SecureCRT client login attempt. In
this case, the CMTS could not determine if the SSH user was locally
authenticated or AAA TACACS authenticated causing the system to set an
incorrect privilege level.
54846 47da A time stamp synchronization problem which caused modems to go offline after
a UPS module switchover has been fixed. The timing issue resulted in UCD
changes not completing and MAPs not being generated.
The software fix adjusts the amount of time needed to complete time stamp
synchronization of the UPS modules to allow UCD and MAP processing to
continue during a switchover so that modems are able to complete registration
and come online.


version
54966 47da Time stamp statistics have been added to the show mpls ftn-table and the
show mpls forwarding-table command output to support debugging activities.
Look for the “time” field in the screen display.
Example:
CASA(config)# show mpls forwarding-table
Codes: > - selected FTN, p - stale FTN, B - BGP FTN, K - CLI
FTN, L - LDP FTN, R - RSVP-TE FTN, S - SNMP FTN, I -
IGP-Shortcut, U - unknown FTN
Code FEC Tunnel-id FTN-ID Pri

Nexthop Out-Label Out-Intf time
L> 1.1.1.69/32 0 34 Yes

93.93.93.6 0 xgige7/0 23:45:14
54983, 47da The number of channels per port for the Table Mode 5 implementation has been
55009 revised to 16, with 128 channels per QAM module. UDP port mappings have
also been revised with this change.
See ID 51855 in this notice for information on the Table Mode 5 implementation.
55034 47da Enhancement. The description parameter has been implemented under the
interface qam ofdm-channel and interface ofdma configurations to support
insertion of OFDM and OFDMA channel descriptions in DHCP packets.
Up to 64 characters may be specified. Surround the description text with

quotation marks (“ “) if the description string contains blank spaces, as shown in
the examples below.
Example: OFDM downstream channel description

C100G(config)# interface qam 2/0
C100G(config-if-qam 2/0)# ofdm-channel 0 description "OFDM
channel on 2/0"
Example: On OFDMA upstream channel description

C100G(config)# interface ofdma 12/0.0
C100G(conf-ofdma-channel 12/0.0)# description “OFDMA
channel on 12/0.0”
Example: Inserting descriptions into DHCP

CASA(conf-if-mac 4)# dhcp-insert upstream-description
CASA(conf-if-mac 4)# dhcp-insert downstream-description

1-114 Release Notes

version
55052 47da Enhancement. The cable map-advance-adjust command has been

implemented to adjust the MAP lead time globally across all upstream cards to
support DOCSIS 3.0 cable modems which require longer MAP lead times due
to cable plant characteristics. The adjustment can be configured in the range
-1000 through 5000 microseconds. The default setting is 0.
To override the global setting on a specific upstream interface, use the existing
map-advance parameter in the interface upstream <slot/port> configuration
context.
Example:
CASA(config)# cable map-advance-adjust ?
<-1000-5000> map tx margin in microseconds, default
is 0
CASA(config)# cable map-advance-adjust 500
55060 47da Enhancement. The ofdma-initial-tech parameter has been added to the DBC
configuration to support the initial ranging techniques to use for D3.1 modems
operating over an OFDMA channel. The default initial ranging technique is
broadcast-ranging.
Example:
CASA(config)# cable modem 1234.1234.1343 dbc upstream-list
1,2,3 initial-tech direct ofdma-initial-tech ?
broadcast-ranging use broadcast initial-ranging
opportunity
probing use probing opportunity
station-ranging use station initial-ranging opportunity
unicast-ranging use unicast initial-ranging opportunity
CASA(config)# cable modem 1234.1234.1343 dbc upstream-list

1,2,3 initial-tech direct ofdma-initial-tech
broadcast-ranging


version
55062 47da Enhancement. The show interface trunk stat command now reports the trunk
interface speed (IfSpeed) in the command output.
Example: Display xGigE interface speed

CASA# show interface trunk stat
Interface Trunk 2 statistics

IfIndex 9000002
interface status UP
link status DOWN
mac address 0017.1003.ba5e
link up member xgige 6/0
IfInOctets 1528431
IfInUcastPkts 0
IfInNUcastPkts 2979
IfInDiscards 2979
IfInErrors 0
IfInOversizePkts 0
IfInUnknownProtos 0
IfOutOctets 768512
IfOutUcastPkts 0
IfOutNUcastPkts 6004
IfOutErrors 0
IfOutDiscards 0
IpForwDatagrams 0
IpInReceives 0
IpInDiscards 0
IfSpeed 10000000000
Last clearing of interface stat: never
55063 47da Enhancement. The show cable voice summary command now supports
OFDMA channels in the command output. OFDMA channels include the “w”
character appended to the <slot/port.channel>identifier.
Example: 0/0.1w

1-116 Release Notes

version
55067 47da The show ofdm channel <slot/port/channel> command has been revised to
include the port-exclusion-band setting in the listed interface qam
configuration. Previously, the show ofdm channel <slot/port/channel> detail
command with the extended output had to be used to get the
port-exclusion-band setting.
Example:
CASA# show ofdm channel 2/0/0
interface qam 2/0
ofdm-channel 0 lower-freq 499000000 upper-freq 689000000
plc-freq 592000000
ofdm-channel 0 cyclic-prefix 192
ofdm-channel 0 rolloff-period 64
ofdm-channel 0 interleave 1
ofdm-channel 0 sc-spacing 50
ofdm-channel 0 pilot-scale-factor 48
ofdm-channel 0 ncp-modulation qpsk
no ofdm-channel 0 up-down-trap-enable
ofdm port-exclusion-band 1
ofdm-channel 0 profile 0 1
no ofdm-channel 0 shutdown
CASA#
55162 47da Under network recovery conditions, FTN route updates were being dropped
from the MPLS forwarding table. The problem was observed when the CMTS
was receiving multiple identical routes from the same peer, with each instance
of same route having a different MPLS label. Incorrect handling of the FTN reply
message was the cause of the problem. The CMTS now ignores FTN reply
messages for routes which have already been removed from the forwarding
table.
55198 47da Enhancement. Existing reserved bandwidth for voice calls functionality has
been applied in the OFDMA interface configuration.
Example:
C100G(conf-ofdma-channel 12/0.0)# voice-bw-reserve ?
<0-100> percentage for total call,default is 75 percent
max-calls limit voice band-width by ugs number
C100G(conf-ofdma-channel 12/0.0)# voice-bw-reserve

max-calls 50 emergency 15


version
55258 47da Processing of cable modem RCP priorities has been revised to correct a
problem where some Intel-based modems with a built-in RCP assignment were
unable to come online with the CMTS. An RCP priority handling issue was
observed after reconfiguring the affected modems with a higher priority using
the cable rcp-select <rcp-id-string> priority command and with the modems
continuing to remain offline. This problem has been fixed.
55270 47da The DOCSIS subscriber management default filter group ID can now be set to a
maximum of 1024. If not set, the default filter group ID configuration for all
upstream and downstream filters is 0.
Example:
CASA(config)# docsis submgt default cm-filter-downstream ?
<0-1024> Docsis default: 0
CASA(config)# docsis submgt default cm-filter-downstream
1024
CASA(config)# show docsis submgt default

docsis submgt default cm-filter-downstream 1024
docsis submgt default cm-filter-upstream 1024
docsis submgt default cpe-filter-downstream 1024
docsis submgt default cpe-filter-upstream 1024
docsis submgt default ps-filter-downstream 1024
docsis submgt default ps-filter-upstream 1024
docsis submgt default mta-filter-downstream 1024
docsis submgt default mta-filter-upstream 1024
docsis submgt default stb-filter-downstream 1024
docsis submgt default stb-filter-upstream 1024

1-118 Release Notes

version
55303 447a Enhancement. The docsis submgt default max-ipv6-iapd command has
been added to the subscriber management default configuration to set the
default maximum number of IPv6 prefixes. The configuration range is 0 to 1023.
The default setting is 3.
IA_PD stands for Identity Association for Prefix Delegation and is a collection of
prefixes, each with its own ID, assigned to a requesting router.
Example:
C100G(config)# docsis submgt default max-ipv6-iapd ?
C100G(config)# docsis submgt default max-ipv6-iapd 1023
C100G(config)# show docsis submgt default

docsis submgt default active on
docsis submgt default max-ip 16
docsis submgt default max-ipv6-prefix 16
docsis submgt default max-ipv6-iapd 3
docsis submgt default learnable on
55462 47da The SNMP docsIfDocsisBaseCapability object now correctly returns a value of
5 for DOCSIS 3.1 in SNMP queries. Previously, a value of 4 for DOCSIS 3.0
was being returned in snmpget and snmpwalk queries.


version
55479 47da Enhancement. OFDMA channel utilization statistics are now supported in
SNMP queries to the following SNMP MIB tables:
• casaCmtsChannelUtilizationTable
• docsIfCmtsChannelUtilizationTable
• docsIfCmtsUpChannelCounterTable
Example:
CASA(config)# show docsis upstream channel utilization
Upstream Total-BW Utilization Online Secondary Channel
Slot/Port.Channel (Mb/Sec) Percentage Modems Modems Description
---------------------------------------------------------------------------
11/0.0 (20000000 Hz) 10.2 0 0 0
11/0.1 (28000000 Hz) 10.2 2 0 0
11/0.2 (24000000 Hz) 10.2 5 1 0
11/0.3 (32000000 Hz) 10.2 0 0 0
11/1.0w ( 5M- 40M Hz) 182.8 12 0 0 ofdma
11/2.0w ( 42M- 85M Hz) 225.6 20 0 1 ofdma
CASA-C10G(config)#
SNMP query: docsIfCmtsUpChannelCounterTable
258: casaCmtsChannelUtilization.4002817 (integer) 2

...

1-120 Release Notes

version
55561 47da Enhancement. The show docsis downstream channel utilization output has
been revised to properly present the correct column headings when admission
control (Reserved-BW Utilization) and shared channels are enabled.
Example: Admission control enabled

CASA(config)# show docsis downstream channel utilization
Downstream Total-BW Utilization Reserved-BW Online Secondary Channel

Slot/Port/Channel (Mb/Sec) Percentage Utilization Modems Modems Description
------------------------------------------------------------------------------------
2/0/0 (549000000 Hz) 42.9 3 0 1 0

2/0/1 (555000000 Hz) 42.9 0 0 0 2
2/0/2 (561000000 Hz) 42.9 0 0 0 2
2/0/3 (567000000 Hz) 42.9 0 0 0 2
Example: Shared channels enabled

Downstream Total-BW Utilization Online Secondary Channel

Slot/Shared Channel (Mb/Sec) Percentage Modems Modems Description
--------------------------------------------------------------------------------------
1/0 (453000000 Hz) 42.9 0 0 0 (shared)

1/1 (459000000 Hz) 42.9 0 0 0 (shared)
1/2 (465000000 Hz) 42.9 0 0 0 (shared)
1/3 (471000000 Hz) 42.9 0 0 0 (shared)
1/4 (477000000 Hz) 42.9 0 0 0 (shared)
55572 47da Enhancement. The Annex A symbol rate has been updated to support the
range 5000 to 6999 kilo-symbols per second on multi-port shared channels. The
default setting is 6952 ks/s.
Example:
CASA(config-if-qam 3/0)#shared-channel 0 annex A symbol
rate ?
<5000-6999> Kilo-Symbol per second (default 6952)
55588 47da A problem which was causing modems registered over an OFDM channel to
drop offline when an OFDM profile subcarrier group was configured with the
modulation zero parameter has been fixed. The modulation zero parameter
is now processed as a valid setting. Existing modems remain online and new
modems will register over the OFDM channel in a valid configuration.
55631 47da A fix has been applied to correct reported temperature threshold inconsistencies
between the Casa CLI show system monitor threshold temperature
command and queries to the SNMP casaSysMonTemperatureState MIB. The
show system monitor threshold temperature command output has been
corrected to address misinterpretation of the low threshold and the alert
threshold.


version
55884 47da Enhancement. The show service group <name> verbose command output
now supports the inclusion of the configured OFDM and OFDMA channel
description strings.
Example:
CASA(conf-ofdma-channel 4/12.0)#show service group 2
verbose
service group 2
downstream channel bonding
upstream channel bonding
no upstream rfog-scheduler
qam 13/7/0 657000000 annex B 256qam dmac 2 DOWN aaaaaaa

qam 13/7/1 663000000 annex B 256qam dmac 2 DOWN
upstream 4/12.0 20000000 3200000 prof 2 dmac 2 UP
ofdm 13/7/0 372000000 dmac 2 UP description
ofdma 4/12.0 5000000 20000000 dmac 2 UP description
56108 47da The Program Clock Reference (PCR) estimation threshold has been increased
from 10ms to 1 second to prevent possible false PCR calculations and an
incorrect setting of the PCR discontinuity bit with reported loss of PCR
synchronization. There was no impact to service.
56117 47da A fix has been implemented to address a condition where the CCAP failed to
recover connectivity with the Entitlement Control Message Generator (ECMG)
server after shutting down one active xGigE port on a trunk interface and
restarting the CCAP. Reconfiguring the ECMG at the CCAP provided the
workaround to recovering the connection. The fix includes a software change
which improves checking of the ECMG connection state to prevent possible
recovery problems in this scenario.
56225 47da Upstream neighbor interface entries on a directly-connected subnet were not
being properly deleted after the entries timed out. This caused stale neighbor
entries with some modems being reported stuck in the init(o) state. Because the
entries were not deleted from neighbor table, ARP was not being triggered to
reestablish adjacency with directly-connected neighbors. This problem has
been fixed.

1-122 Release Notes

version
56315 47da A problem which was causing a fragmented UDP packet from a cable modem to
56373 be incorrectly interpreted as a TFTP packet has been fixed. The error triggered
the TFTP proxy timeout timer value, causing in a cable modem to go off line
after 120 seconds if the destination IP for the packet was the CMTS, with
forwarding to the SMM ARP TFTP proxy. The fix corrects software decoding of
the IP fragment to prevent the packet mismatch which caused the modem to
drop off.

version
38790 4682 Enhancement. Checks have been implemented to ensure insertion

compatibility of SFP (1 GB) and SFP+ (10GB) modules with their respective
GigE and xGigE ports on the SMM. If an SFP is inserted into an incompatible
port, an error message will be logged and the link will be reported in the “down”
state. Removing the incompatible SFP and inserting the correct SFP or SFP+
module will clear the error and alarm condition.
Sample ALARM level logs:
[Fri May 20 14:51:21 2016]-AL-SYS-1: smm6: Error: 10G SFP+

plugged in 1G gige port SMM6 G1
[Fri May 20 14:51:21 2016]-AL-SYS-1: smm6: Misplaced SFP/

SFP+ on port 6/0 was removed, ALARM cleared
[Fri May 20 14:51:16 2016]-AL-SYS-1: smm6: Error: 10G SFP+

plugged in 1G gige port SMM6 G0
[Fri May 20 14:51:08 2016]-AL-SYS-1: smm6: Error: 1G SFP

plugged in 10G xgige port SMM6 XG7


version
50771 4682 Enhancement. IPDR for DOCSIS 3.1 OFDM and OFDMA is now supported for
interoperability with IPDR collectors. The following IPDR service type templates
to support OFDM and OFDMA records have been added in Release 7.2.
• DOCSIS-CMTS-CM-DS-OFDM-PROFILE-STATUS-TYPE
• DOCSIS-CMTS-CM-DS-OFDM-STATUS-TYPE
• DOCSIS-CMTS-CM-US-OFDMA-PROFILE-STATUS-TYPE
• DOCSIS-CMTS-CM-US-OFDMA-STATUS-TYPE
• DOCSIS-DS-OFDM-PROFILE-STATS-TYPE
• DOCSIS-US-OFDMA-PROFILE-STATS-TYPE
Example:
CASA(config)# show ipdr template
cm-ds-ofdm-prof-status cm-ds-ofdm-prof-status type
cm-ds-ofdm-status cm-ds-ofdm-status type
cm-us-ofdma-prof-status cm-us-ofdma-prof-status type
cm-us-ofdma-status cm-us-ofdma-status type
ds-ofdm-prof-stats ds-ofdm-prof-stats type
us-ofdma-prof-stats us-ofdma-prof-stats type
50840 4682 A case where connectivity with an IS-IS adjacent router over a CMTS trunk
interface would remain stuck in the init state after a CMTS startup has been
fixed. A problem was found where some trunk configurations have been
changed and IS-IS performs the graceful restart after the system restart.
Performing a shutdown and no shutdown of the affected trunk interfaces

provided a workaround to the problem.
50946 4682 Enhancement. Route leaking (VRF to global, VRF to VRF, and global to VRF)
has been enhanced so that a host route is no longer required to be configured
to the IP bundle as long as the forwarding gateway is the IP bundle interface.
51490 4682 Messaging at the standby SMM has been revised for improved module type
detection whenever an UPS or QAM module is removed from the chassis with a
resulting redundancy switchover. An Internet connectivity issue was reported
after an UPS module was pulled while the standby SMM in slot 7 was active.
This problem has been fixed.

1-124 Release Notes

version
51712 4682 The docsIf31Mib will now appear in SNMP queries to the sysORTable MIB.
Previously, the docsIf31Mib was missing from the list.
Example:
1: sysORID.1 (object identifier) interfaces
2: sysORID.2 (object identifier) ip
3: sysORID.3 (object identifier) icmp
4: sysORID.4 (object identifier) udp
5: sysORID.5 (object identifier) dot3
6: sysORID.6 (object identifier) docsIfMib
7: sysORID.7 (object identifier) host
8: sysORID.8 (object identifier) ifMIB
9: sysORID.9 (object identifier) docsDev
10: sysORID.10 (object identifier) mib-2.82
11: sysORID.11 (object identifier) docsBpi2MIB
12: sysORID.12 (object identifier) docsLoadBalanceMib
13: sysORID.13 (object identifier) docsIfExt2Mib
14: sysORID.14 (object identifier) docsDiagMib
15: sysORID.15 (object identifier) docsSubmgt3Mib
16: sysORID.16 (object identifier) docsSecMib
17: sysORID.17 (object identifier) docsTestMIB
18: sysORID.18 (object identifier) docsMcastMib
19: sysORID.19 (object identifier) docsMcastAuthMib
20: sysORID.20 (object identifier) docsIf3Mib
21: sysORID.21 (object identifier) docsQosMib
22: sysORID.22 (object identifier) docsIf31Mib <<<<<
23: sysORID.23 (object identifier) snmpMIB
24: sysORID.24 (object identifier) snmpVacmMIB
25: sysORID.25 (object identifier) snmpModules.18
26: sysORID.26 (object identifier) snmpFrameworkMIB
27: sysORID.27 (object identifier) snmpMPDMIB
28: sysORID.28 (object identifier) snmpTargetMIB
29: sysORID.29 (object identifier) snmpUsmMIB

22: sysORDescr.22 (octet string) The MIB module contains
the management objects for the management of DOCSIS 3.1
features, primarily OFDM and OFDMA channels.


version
51818 4682 The IP Provisioning Mode TLV has been relocated to the last position in the
MAC Domain Descriptor (MDD) message. The change addresses a situation
where a set-top box (STB) was unable to pick up the IP Provisioning Mode TLV
when processing a fragmented MDD message. Placing the TLV at the end of
the MDD ensures that the TLV will be picked up by the STB from the second
MDD message fragment.
52149 4682 A software change to increase the minimum link-state advertisement (LSA)
retransmission interval to 1 second has been applied to address an issue where
the CMTS keeps retransmitting the same link-state advertisement (LSA)
packets when the calculated retransmission interval is less than 1 second.
52354 4682 A channel number retrieve error in the downstream packet scheduler which was
preventing traffic from being forwarded to a D3.1 modem has been fixed. The
problem involved an L2VPN D3.1 modem which was using an OFDM channel
only and no single-carrier QAM channels.
52388 4682 Enhancement. Up to 32 import and export route targets are now supported
inside a VRF route-map in Release 7.2. The previously supported number was
eight.
52484 4682 A problem has been reported where the CMTS was failing to send DBC
messages (with new DSID labels) for new multicast sessions to a set-top box.
The problem occurred after performing a set-top box power reset. Error
checking has been implemented and additional buffer space has been allocated
to ensure that multicast DSIDs are not dropped when establishing new multicast
sessions.

1-126 Release Notes

version
52543 4682 The software has been revised for improved management and presentation of
spectrum measurement statistics. A problem was observed where using 200K
option in SNMP and CLI queries resulted in a failure to display all statistics due
to a limitation in the CMTS database.
The following SNMP and CLI changes have been applied with this fix to address
the problem:
• The 200K option has been removed from the SNMP

casaSpectrumMeasurementChannelWidth MIB object in the
CASA-SPECTRUM-MIB file. The revised range is 400 kHz to 6400 kHz.
• -The 200000 option has been removed from the show spectrum upstream
The CMTS database now supports up 1024 spectrum measurement data

entries.
52647 4682 A software fix has been applied to protect against possible configuration loss
when physically swapping out QAM or UPS modules in a redundant
configuration. The fix ensures that the startup configuration is properly read into
the new and standby modules during high availability redundancy replacement
with the ha module <number> protect and ha module <number> revert
commands.
A problem was reported where parts of the DSG channel configuration were
dropped after QAM8x192 high availability replacement, where the new module
had different licensing properties than the removed module. The fix applies to all
standby modules and is not limited to a specific module type.


version
52763 4682 New feature. Video on demand (VOD) Table Mode 6 support has been
implemented in Release 7.2. With Table Mode 6, video channel space per QAM
port is eight narrowcast channels.
The UDP port mapping for this mode is 00qqqqqq pppppppp. The UDP port
range of Table Mode 6 is 0x0001 - 0x3FFF. The output program number is in the
range 0 to 255. Video streams with a UDP port out of this range will be treated
as homeless streams, and no output will be generated on the RF side.
Example:
CASA(config)# video table ?
mode0 qqqqqqqq qqpppppp
mode1 1qqqqqqq qqqppppp
mode2 1qqqqqqq qqqpppp0
mode3 qqqqqqqq pppppppp
mode4 qqqqqqqq pppppppp,where q starts from 1
mode5 100qqqqq qqpppppp
mode6 00qqqqqq pppppppp
CASA(config)# video table mode6
Implementation notes:
• If the video channel-id-offset parameter is not configured, the channel x/y/

z to be used for Table Mode 6 ranges from x/y/0 to x/y/7.
• If the video channel-id-offset parameter is configured, the channel ranges
from x/y/offset to x/y/offset+7.

1-128 Release Notes

version
52809 4682 Enhancement. Log messages at the CMTS will now report the state of an IS-IS
peer router whenever the IS-IS process at the peer is cleared, and with the peer
re-initializing adjacency with the CMTS.
Sample WARNING (WA) level logs:
[Sun Jun 5 23:52:59 2016]-WA-ROUTER-0: smm6: IS-IS:

LAN-NFSM[ISIS(ipv6), Adjacency to xgige6/3-0079.0000.0000
Down]: Level 1 State Changed LAN Neighbor UP -> Init, event
OneWayReceived(neighbor forgot us)

LAN-NFSM[xgige6/3-0079.0000.0000]: Level 1 State Changed
LAN Neighbor Init -> up, event TwoWayReceived

P2P-NFSM[ISIS(casa), Adjacency to vlan183-0114.0000.0000
Down]: Level 1 State Changed P2P Neighbor UP -> Init, event




version
53443 4682 Enhancement. The following CLI show commands have been added to the
Casa diag mode to display internal buffer, traffic throughput, and queue usage
statistics:
• show bcm flow-classes

• show bcm congestion-info
• show bcm events
Use these commands with the assistance of Casa Technical Support when
diagnosing throughput issues.
Example:
CASA(diag)# show bcm congestion-info
Total Shared Buffer cells: 38427, Total Shared Buffer cells
in use: 0 (0%)
Buffer cells in use: 0 (0%)
Currently Alarmed: No, Alarm Count 0
Cell usage for port 0: input - 0, output - 0, output uc 0,
ing mmu drops 0
PG Shared Usage: 0 0 0 0 0 0 0 0
PG Headroom Usage: 0 0 0 0 0 0 0 0
Multicast Queue Usage: 0 0 0 0 0 0 0 0
53779 4682 Optimization of table lookups in SNMP queries (snmpget, snmpgetnext,
snmpwalk, and snmpbulkwalk) has been implemented for improved
performance and faster response times. Actual performance will vary
depending on the network and configuration.

1-130 Release Notes

version
53781 4682 Enhancement. The channel <number> power-attenuation command setting

in the interface qam <slot>/<port> configuration has been revised to operate
over a specified range of channels per port. Previously, the command operated
on a single channel only. The revised command operates with the QAM 8x96
and QAM 8x192 modules on both standard and shared channels.
The number of channels over which the specified power-attenuation value is

applied is in the range 1 to 80, depending on the QAM module in use.
Example: Power attenuation (20dB) over 10 channels starting with channel 0
CASA(config-if-qam 2/0)#channel 0 power-attenuation 20 10
CASA(config-if-qam 2/0)#shared-channel 0 power-attenuation

20 10
53913 4682 A problem was reported where a D3.1 modem advertised with a 32-channel
bonding modem capability in the receive channel profile (RCP) came online with
10 bonded downstream channels instead of the expected 32 channels. A fix has
been applied to ensure proper RCP selection when modems register with the
CMTS.
54337 4682 Pmax statistics (maximum power) reported by the cable modem in the
REG-REQ message are now correctly applied in power calculations (pload) at
the CMTS and returned in the REG-RSP message to the modem. The fix
corrects potential DRW violations with D3.1 modems registering with the CMTS.

Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes

version
27729 45b9 Access control for specific access-class services is now supported in Release
7.2 using the <service-name> access-group <ACL-name> command. The
access-class services include: ntp, snmp, telnet, telnets, ssh, ipdr, ftp, smtp,
rtsp, and http. Once specified use the no form of the command to disable the
named access-group from the specified service.
CMTS(config)# <service-name> access-group <ACL-name> [in |

out]
Example:
CMTS(config)# telnet access-group name1
CMTS(config)# ssh access-group name2
CMTS(config)# ipdr access-group name3
CMTS(config)# no telnet access-group

30275 45b9 Signaling parameters for digital optical monitoring (DOM) have been added to
the output for the show interface transceiver, show interface gige transceiver,
and show interface xgige transceiver commands. The output shows real-time
monitoring of Ethernet small-factor pluggable (SFP) transmit and receive power,
optical current, voltage, and temperature.
See the Casa Systems – CMTS Release 7.2 Features Guide for more
information.

1-132 Release Notes
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)

version
31591 45b9 Enhancement. The following channel transport stream ID (TSID) commands
now include a repetition count [<num>] and increment [inc <num>] option
when configuring a TSID range for single carrier and narrowcast shared
channels. The repetition count and increment options allow users to configure
multiple channel TSIDs with one command.
Format:
channel <id> transport stream id <tsid> [<num> [inc <num>]]

no channel <id> transport stream id [<num>]
shared-channel <sid> transport stream id <tsid> [<num> [inc

<num>]]
no shared-channel <sid> transport stream id [<num>]
Example:
CASA(config-if-qam 3/0)# ch 0 transport stream id 1 40 inc
2
32360 45b9 The ngod and edis video options can now be configured to allow traffic filtering
using a specific access control list (ACL), as specified with access-group
parameter. This feature enables separate and uniquely-named ACLs to operate
over separate video and data streams.
(config)# <service-name> access-group <ACL-name> [in | out]
Example:
CMTS(config)# ngod access-group aclfilename1
inCMTS(config)# edis access-group aclfilename2 in
32955 45b9 The [no] send udc rules command has been removed from the interface
docsis-mac configuration and is no longer valid. Use the upstream drop
classifier command to enable or disable UDCs for cable modems which are
attempting to register with the CMTS MAC domain. A UDC has a set of
matching criteria applied by modems to determine if a packet should be dropped
on the upstream.


version
34714 45b9 Enhancement. Video and DOCSIS log messages can now be separated and
sent to different syslog servers. Use the current cable event syslog-server <
ip-address> to direct DOCSIS messages to the specified IP syslog target.
To direct video event messages to a separate syslog server, execute the video
logging host <ip_address> [port <num=1:65535>] [vrf <string>] command
now available in Release 7.2. Up to four syslog server IPs may be specified for
video events. Use the no form of the command to remove any previously
configured video syslog hosts.
Example:
CASA(config)# video logging host 192.168.54.231
video_logging_host_callback, port:514,vrf:0
edge_log_add_syslog_host, index:0
CASA(config)# show logging all

/dev/console : debugging
system log level : debugging
non-volatile log level : debugging
volatile log level : off
syslog level : warnings
trap level : off
system syslog host : 192.168.54.230
video syslog host : 192.168.54.231

1-134 Release Notes

version
35749 45b9 Feature. The cable arp fast-timeout command has been introduced to enable
the system to efficiently remove all aged CPE entries from SMM ARP table
when there no response to ARP polling request cycles. By default, if no ARP
reply is received at the end of the last ARP polling request cycle, the CPE entry
is removed from the ARP table.
When the cable arp fast-timeout setting is enabled, and if there is no response
to an ARP polling request, the fast-timeout mode begins and the configured
arp timeout setting is applied to all CPE entries in the ARP table so that the
aged entries are removed.
The default value setting is disabled. Once set, use the no command to disable
the cable arp fast-timeout setting.
Example:
CASA(config)# cable arp fast-timeout
CASA(config)# show cable arp fast-timeout
cable arp fast-timeout enabled
36094 45b9 The show cpu-history [module <slot-number>] command has been
introduced to show a CLI graphical representation of the CPU utilization per the
specified module slot. The graph includes the CPU load and the history of the
CPU load per process over the last 60-minute time period.
The CPU usage percentage is displayed in values ranging from 00 to 100 along
the left vertical column; CPU usage time (in minutes) displays along the bottom
of the chart in 10-minute increments up to 60 minutes.
See the Casa Systems – CMTS Release 7.2 Features Guide for additional
information.
36497, 45b9 Enhancement. Support has been implemented for up to 128 named VRF
47014, definitions on the SMM 8x10G IPv4 and IPv6 interfaces. A passive ARP (PARP)
47393 update has also been applied to ensure the additional VRFs are supported in
policy-based routing (PBR) where a VRF next-hop instance is applied in a
route-map.
Example:
CASA(config)# vrf definition ?
<string> vrf definition name (size 1 to 128)
CASA(config)# vrf definition vrfname128


version
36575 45b9 The -t option has been added to the traceroute6 command to display the Type
of Service (ToS) value for IPv6 address hops.
Example:
CASA# traceroute6 "-t 0xff 4000::6"
traceroute to 4000::6 (4000::6) from 4040::42, 64 hops max,
16 byte packets
1 4040::1 1.248 ms
2 4001::1 0.759 ms
3 4000::6 0.932 ms
38077, 45b9 Enhancement. To support L2 Business Services over DOCSIS (BSoD), L2
48609 broadcast traffic can now be disabled between two cable modems on the same
VLAN. All L2 traffic will be forwarded to the upstream router over the CMTS
network side interface. The upstream router will then redirect the traffic back to
the CMTS.
The following no commands have been implemented in the CLI to disable L2

traffic.
Example:
CASA(conf-if-vlan 10)# no l2vpn mac-address-movable
CASA(conf-if-vlan 10)# no l2vpn local-traffic-forwarding
The l2vpn mac-address interval <1:1800> command has been implemented

to set the L2VPN interval timer period in seconds to elapse before determining if
a MAC address is no longer active. The default value is 900 seconds. The
configurable range is 1 to 1800 seconds.
Example:
CASA(conf-if-vlan 10)# l2vpn mac-address interval ?
<1-1800> expiry interval in seconds if mac-address is no
longer active. Default is 900 seconds
CASA(conf-if-vlan 10)# l2vpn mac-address interval 400

1-136 Release Notes

version
38078 45b9 Enhancement. To support L2 Business Services over DOCSIS (BSoD), the
CMTS can now add DHCP Option 82 (for IPv4 and IPv6) into cable modem
L2VPN packets to allow the modem MAC address to be carried in the DHCP
Request message from the modem and forwarded to the DHCP server.
The l2vpn dhcp-insert option 82 command has been implemented in the CLI
on a per-VLAN basis. Use the no form of the command to remove the current
setting.
Example:
CASA(conf-if-vlan 10)# l2vpn dhcp-insert option 82
38987 45b9 Enhancement. The ls and dir commands has been revised to display the
memory usage for each SMM. Enhancements include displaying the Size (total
size of folder), Used (storage used), Avail (storage available), Use %
(percentage of total storage used), and Mounted on (identifies the specific
SMM).
Example:
CASA> ls
total 389056
-rw-r--r-- 1 croot root 78016000 Nov 23 15:03
drwxrwxrwx 5 croot root 32768 Feb 11 17:45 cert_manage
-rw-r--r-- 1 croot root 35864 Feb 11 17:45 config_error_log
-rw-r--r-- 1 croot root 64771 Feb 11 17:10 config_error_log.bak
-rw-r--r-- 1 croot root 18 Jan 22 2014 envm_temp_thresd
-rw-r--r-- 1 croot root 0 Mar 20 2015 evids
Filesystem Size Used Avail Use% Mounted on

/dev/hda1 1.9G 677M 1.3G 36% /fdsk


version
39198 45b9 Feature. The set comm-list <community list > delete command has been
implemented in the CLI to allow the deletion of BGP communities. This
command removes communities numbers (in AA:NN format) from the BGP
communities attribute. When the BGP route communities number matches the
community list, the communities value is removed.
Example:
In the following configuration, community numbers 100:1 and 100:2 are
removed from BGP updates. For community value deletion, only the permit
option is used; the deny option is ignored.
router bgp 7675

neighbor 192.168.0.1 remote-as 100
neighbor 192.168.0.1 route-map RMAP in
!
ip community-list standard DEL permit 100:1 100:2
!
route-map RMAP permit 10
set comm-list DEL delete
39215 45b9 The maximum-paths {ebgp | ibgp} <port 1-8> command has been introduced
in the router bgp configuration to enable multi-path load sharing among
external Border Gateway Protocol (eBGP) and internal BGP (iBGP) routes.
The default number of paths is eight. Use the no form of the command to
disable the feature.
Example:
CASA(config-router-bgp)# maximum-paths ebgp ?
<1-8> Number of paths
CASA(config-router-bgp)# maximum-paths ebgp 2
CASA(config-router-bgp)# maximum-paths ibgp ?

<1-8> Number of paths
CASA(config-router-bgp)# maximum-paths ibgp 3
39831 45b9 Frequency, modulation, and symbol rate settings will now remain persistent
when enabling spectral-inversion at the port, channel, or shared channel level.
Previously, enabling spectral-inversion forced the configured frequency,
modulation, and symbol rate settings to be reset.

1-138 Release Notes

version
39854 45b9 The interface loopback <id> command has been revised to support up to 64
loopback interfaces and a loopback port ID range from 0-255. Use the no form
of the command to remove the loopback interface.
Example:
CASA(config)# interface loopback 223
CASA(config-if-lo 223)#
CASA(config)# no interface loopback

39916, 45b9 The casaIPMcastRoutePps MIB object has been added to the CASA-PIM-MIB
45003, file. The MIB object provides multicast traffic statistics in packets per second in
45839 SNMP queries. The show ip multicast traffic command has been revised to
display the multicast statistics in packets per second.
-- 1.3.6.1.4.1.20858.10.58.1.1.1.25
casaIpMcastRoutePps OBJECT-TYPE
SYNTAXCounterBasedGauge64
UNITS "Packet per second"
STATUS current
DESCRIPTION
"Packet per second forwarded by this
router using this multicast routing entry."
::= { casaPimRouteEntry 25 }
information.


version
40203, 45b9 Informational enhancements to partial service SNMP traps have been
45802 implemented in the CASA-DOCS-EXT-MIB. Reasons for the partial service
condition are now provided in the trap message, including DBC, ranging, and
partial service recovery.
casaCmtsPartialServiceEventType
Description: A notification will be sent to SNMP trap with the reason for partial
service.
casaCmtsPartialServiceNotification
Description: A notification will be sent when the impacted cable modem comes
out of partial service.
casaCmtsPartialServiceActionFlag
Description: When a CM goes into partial service, the partial service trap that is
generated will now be listed as “partial-service”.
40212 45b9 Enhancement. The show cable modem phy and show cable modem
remote-query commands now display the complete number of output entry
rows. The commands previously showed only 10 entries even if modems were
bonding on more downstream channels due to a snmpbulkget maximum
repetition count limitation.
40214 45b9 The casaCmtsCMPSDSChExclueList MIB object has been modified in the
CASA-DOCS-EXT-MIB file to include unusable US and DS channels for the
current modem. The matching CLI command is the show cable modem
partial-service command in the Casa configuration mode.
information.

1-140 Release Notes

version
40434 45b9 The show chassis status command has been implemented to display
summary information on current chassis status and card level information.
• An “X” indicates that a module is operational.

• A “-” (dash) indicates that the module is not currently operational.
• Input/Output (IO) status is operational if the Resource Module (RM) is
operational for a specific linecard, or if SMM is active.
LastUptime will display status only if the module has been booted up more than
twice.
information.
40442 45b9 Enhancement. The ntp server <ip address> [prefer] command has been
revised to declare the preferred (primary) NTP server. Once assigned, the
preferred NTP server is the designated primary; other NTP servers are
considered secondary in the event that the primary server is unavailable.
To declare a preferred server:
Example:
CMTS(config)# ntp server 104.131.118.129 prefer
Stopping NTP server: ntpd.
18 Feb 17:22:13 ntpdate[1752]: step time server
104.131.118.129 offset 0.000194 sec
To declare a non-preferred server, omit the prefer option.
Example:
CMTS(config)# ntp server 74.120.8.2
18 Feb 17:20:50 ntpdate[1556]: step time server 74.120.8.2
offset 34.627892 sec
To display all NTP servers:
Example:
CMTS(config)# show ntp-server
ntp server 74.120.8.2
ntp server 104.131.118.129 prefer
no ntp scheck


version
40588 44b9 The md5 checksum command has been revised to include <image> <hash>
to compare the output of the checksum to an MD5 hash value and return a
pass/fail indication if the result of the checksum matches or does not match the
hash value entered. The command uses the following CLI:
CASA# md5 checksum <image_name> <hash>
Example:
CMTS# md5 checksum ccsi.gz.rel7.2.0.0_build43b0
943d96f56361f10492fa3e899dac1e55
ccsi.gz.rel7.2.0.0_build43b1

943d96f56361f10492fa3e899dac1e55
ccsi.gz.rel7.2.0.0_build43b1: OK

943d96f56361f10492fa3e899dac1e56
ccsi.gz.rel7.2.0.0_build43b1: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match

943d96f56361f10492fa3e899dac1e56
ccsi.gz.rel7.2.0.0_build43b1: FAILED
md5sum: WARNING: 1 of 1 computed checksum did NOT match
40624 45b9 Access-list duplication checking has been implemented to prevent duplicate
rules from being added to an access list. Attempts at a duplicate access-list
entry are prompted with an error message.
Example:
CASA(config)# ip access-list kw
CASA(conf-acl kw)# permit all 1.1.1.1 2.2.2.2 3.3.3.3
4.4.4.4 dscp 5 7 8 time-range kw
CASA(conf-acl kw)# permit all 1.1.1.1 2.2.2.2 3.3.3.3
4.4.4.4 dscp 5 7 8 time-range kw
Duplicate ACL rule.
Fail to add rule to access-list kw
40625 45b9 The traceroute and traceroute6 commands in the Casa CLI have been
enhanced to support more than five address hops to a destination IP. They were
previously limited to five hops only. The maximum number of traceroute and
traceroute6 hops has been increased to 64 using the -m option.

1-142 Release Notes

version
40728 45b9 A fix has been applied in the software to ensure proper handling of CPE L2VPN
packets with a TTL=1 destined to an upstream router. Prior to the fix, the CMTS
was incorrectly decrementing the TTL setting, causing the L2VPN packets to be
dropped.
40786 45b9 Enhancement. The quiet option was added to the ping and ping6 commands
in the Casa CLI for a quieter output to show the packets transmitted and
received without the repeated attempts listed.
Example:
CASA(config)# ping quiet repeat 10 192.168.8.8
PING 192.168.8.8 (192.168.8.8): 56 bytes of data.
--- 192.168.8.8 ping statistics ---
10 packets transmitted, 10 packets received, 0% packet loss
round-trip min/avg/max/stddev = 0.506/0.642/1.687/0.349 ms
40840 45b9 Enhancement. Support for embedded systems such as Security Gateways,
embedded Routers, and embedded T1 emulation adapters now exists in the
CMTS. The new CPE types include:
• Embedded t1 emulation (eTEA),

• Embedded router (eROUTER),
• Embedded digital voice adapter (eDVA),
• Embedded security gateway (eSG).
The CPE types map to existing filters (TEA, DVA, and SG map to MTA while
eROUTER maps to PS) and can be verified using the show cable modem
docsis-device-class command in the CLI.
Example:
CASA> show cable modem docsis-device-class
MAC Address US DS Mac Prim Reg Device Class Reg
Intf Intf Status Sid Ver Priv
0030.545e.56e8 11/0.3/0 4/0/13 online 52 1.1 eROUTER BPI
2476.7d98.bd08 11/0.3/0 4/0/4 online 53 1.1 eDVA BPI
fc52.8d5e.9c93 11/0.3/0 4/0/0w online 56 1.1 CM BPI
CASA>


version
41304 45b9 Enhancement. Support has been added for the

docsIf31CmtsUsOfdmaChanTable objects in the SNMP DOCS-IF31-MIB for
OFDMA. These objects include the following:
• docsIf31CmtsUsOfdmaChanTemplateIndex
• docsIf31CmtsUsOfdmaChanConfigChangeCt
• docsIf31CmtsUsOfdmaChanTargetRxPower
• docsIf31CmtsUsOfdmaChanLowerBdryFreq
• docsIf31CmtsUsOfdmaChanUpperBdryFreq
• docsIf31CmtsUsOfdmaChanSubcarrierSpacing
• docsIf31CmtsUsOfdmaChanCyclicPrefix
• docsIf31CmtsUsOfdmaChanNumSymbolsPerFrame
• docsIf31CmtsUsOfdmaChanRollOffPeriod
• docsIf31CmtsUsOfdmaChanPreEqEnable
• docsIf31CmtsUsOfdmaChanFineRngGuardband
• docsIf31CmtsUsOfdmaChanFineRngNumSubcarriers
• docsIf31CmtsUsOfdmaChanFineRngPreambleLen
• docsIf31CmtsUsOfdmaChanInitRngGuardband
• docsIf31CmtsUsOfdmaChanInitRngNumSubcarriers
• docsIf31CmtsUsOfdmaChanInitRngPreambleLen
• docsIf31CmtsUsOfdmaChanProvAttribMask
• docsIf31CmtsUsOfdmaChanTxBackoffStart
• docsIf31CmtsUsOfdmaChanRangingBackoffEnd
• docsIf31CmtsUsOfdmaChanUtilization
41400 45b9 If a linecard is in a down state without switchover being configured, the
Universal Session and Resource Manager (USRM) connections for the video
interface connected to that linecard are now terminated. The SRM connection
was previously not terminated so that mini-carousel data could not be rebuilt
when the linecard was in a running state again. Now, when the QAM card gets
rebooted or is removed without a standby linecard, all SRM connections
associated with the linecard are torn down.

1-144 Release Notes

version
41728 45b9 A new warning syslog message in the format "-WA-CMTS-1: smm: Excessive
<class_name> packets are dropped", where <class_name> is the traffic
class, such as ISIS, RIP, and ARP has been incorporated to log when the
control plane rate limiter drops control plane packets. The chassis will then send
a log when the CPU rate limiter drops packets.
Example:
CMTS(config)# logging system warning
[Fri Jan 29 21:08:14 2016]-WA-CMTS-1: smm7: Excessive ISIS
packets are dropped.
[Fri Jan 29 20:54:08 2016]-WA-CMTS-1: smm7: Excessive RIPNG
packets are dropped.
[Fri Jan 29 20:54:08 2016]-WA-CMTS-1: smm7: Excessive
IP6_Mcast packets are dropped.
[Fri Jan 29 20:52:53 2016]-WA-CMTS-1: smm7: Excessive
ARP_Reply packets are dropped.
docsIf31CmtsUsOfdmaDataIucStatsTable objects in the SNMP
DOCS-IF31-MIB for OFDMA. These objects include the following:
• docsIf31CmtsUsOfdmaDataIucStatsTotalCodewords
• docsIf31CmtsUsOfdmaDataIucStatsCorrectedCodewords
• docsIf31CmtsUsOfdmaDataIucStatsUnreliableCodewords
• docsIf31CmtsUsOfdmaDataIucStatsInOctets
• docsIf31CmtsUsOfdmaDataIucStatsCtrDiscontinuityTime
42035, 45b9 Enhancement. Subscriber Traffic Management (STM) has been enhanced to
51296 monitor interface utilization in addition to the currently supported subscriber
transmission rates. STM only manages a subscriber if its transmission rate and
the interface utilization both exceed predefined limits in the cable traffic-policy
configuration.
The channel-utilization-threshold <0-100> command has been implemented

in the Casa CLI to specify the minimum utilization percentage that will trigger
cable traffic rules.


version
42297 45b9 The maximum transmission unit (MTU) upper limit has been increased from
4470 to 9190 bytes for the GigeE and xGigE network interfaces. The MTU size
now ranges from 1500 through 9180 bytes, with 1500 the default.
Example:
CASA(config-if-gige 6/0)# mtu ?
<1500-9180> mtu size in byte; default is 1500
42436 45b9 Casa now supports the R6 protocol for the Resource Management Real Time
Streaming Protocol (RTSP) interface for Next Generation on Demand (NGOD).
Previously, only the Discovery (D6) protocol was supported. Configuration
details will be provided as soon as available.

1-146 Release Notes

version
43282 45b9 The logical-channel 0 pre-equalization auto-reset command has been

revised to include a time-interval in minutes which will perform and automatic
reset based on the SNR threshold. The auto-reset takes place after the
specified number of minutes have expired and repeats as necessary.
The default setting is 1440 minutes (24 hours); a setting of 0 disables the
auto-reset function. The settable range is 0 to 65535 minutes.
Format: logical-channel 0 pre-equalization auto-reset <minutes>
Example:
CASA(config-if-ups 9/0.0)# logical-channel 1
pre-equalization auto-reset 60
CASA(config-if-ups 9/0.0)# show this
interface upstream 9/0.0

frequency 20000000
channel-width 3200000
power-level -5
map-advance dynamic 200
logical-channel 0 pre-equalization 1
no logical-channel 0 shutdown
logical-channel 1 pre-equalization auto-reset 60
logical-channel 1 shutdown
no shutdown
CASA(config-if-ups 9/0.0)#
43416 45b9 Bonding and non-bonding modem counts are now displayed in show cable
modem summary total and show cable modem downstream summary total
commands.
information.


version
43417 45b9 The show swmgr flow-classes diagnostic mode CLI command has been
implemented to display CPU flow statistics to assist in detecting potential
denial-of-service (DoS) attacks. The output shows non-RED packets as G+Y
Packets. A mitigated DoS attack can be detected either by an increasing RED
packet counter for a Meter type entry, or an increasing total packet counter for a
Filter type entry.
information.
43617 45b9 Enhancement. The show cable modem verbose command has been
enhanced with the following statistics in the displayed output:
• Upstream Channel
• Ranging Status
• Upstream SNR (dB)
• Received Power (dBmV)
• Reported Transmit Power (dBmV)
• Peak Transmit Power (dBmV)
• Phy Max Power (dBmV)
• Minimum Transmit Power (dBmV)
Example:
CASA# show cable modem 0024.d11e.4b2a verbose
Upstream Channel :4/2.3/0
Ranging Status :RNG_SUCCESS
Upstream SNR (dB) :30.7
Received Power (dBmV) : 0.0
Reported Transmit Power (dBmV) :26.5
Peak Transmit Power (dBmV) :58.0
Phy Max Power (dBmV) :-
Minimum Transmit Power (dBmV) :20.2
43653 45b9 An error in the software logic which could cause a failure of IPv6 routes to
properly synchronize with an SMM switchover has been fixed. The lost routes
were IPv6 only; IPv4 routes were not impacted by the synchronization problem.

1-148 Release Notes

version
43678 45b9 Enhancement. A load-balancing dynamic channel change (DCC) or dynamic

bonding change (DBC) request now returns an error if an invalid upstream
channel is specified. The upstream channel is invalid if not included in the
service group requested for the channel change. Previously, there was no error
message returned in this situation.
43806 45b9 Enhancement. The show interface video stat command has been revised to
display the status of each video interface as text, either Up or Down. The
command is available throughout the CLI where applicable.
Example:
CASA(config-if-lo 12)# interface video 3
CASA(conf-if-video 3)# show interface video stat
interface video 3 status: Down
L3 Mode Up
qam module -
video unicast count 849348584
CASA(conf-if-video 3)# video edis 1

CASA(conf-video-edis 1)# ip-address 201.175.175.254
CASA(conf-video-edis 1)# srm-type casa
CASA(conf-video-edis 1)# announce
CASA(conf-video-edis 1)# show interface video stat
interface video 3 status: Down
L3 Mode Up
qam module -
video unicast count 849348584
43981 45b9 The show run command now omits the first five, default modulation profiles in
the output and shows no profiles if no additional ones are defined. The default
profiles were previously shown in the output. However, the show
modulation-profile command does include the default profiles in the output
along with the others defined.
information.


version
44012 45b9 Enhancement. The IPv4 distance bgp <external=1:255> <internal=1:255>

<local=1:255> command to set external, internal, and local administrative
distance from the AS has been applied under the IPv6 unicast address-family
ipv6 global and VRF configuration contexts.
Example:
CMTS(config-router-bgp)# address-family ipv6
CMTS(config-router-af)# distance bgp 77 88 99
CMTS(config-router-af)# show this

!
address-family ipv6
aggregate-address 135::135:1:0/120 summary-only
neighbor 48.48.48.48 activate
neighbor 135.135.135.79 activate
distance bgp 77 88 99
exit-address-family
44328 45b9 A cable modem status error occurred where known “offline” modems continued
to be reported as “online” with the show cable modem summary total
command. The problem was observed in a situation where both the active and
standby line cards were booting up at the same time and were temporarily not in
service.
44503 45b9 C10G and C100G platforms running Release 7.2 now support up to ten QAM
8x96 modules with up 32 channels per port over eight ports for a maximum of
256 channels per module, and 2560 channels per DSG tunnel-group, and 5120
channels across all tunnel groups system wide. The enhancement implements
additional channel capacity for Advanced DOCSIS Set-top Gateway (ADSG)
deployments.
45184 45b9 Enhancement. Route map recursive next-hop support in L3VPNs was added in
order to direct user traffic from the CPEs to the next-hop in the MPLS network.
The set mpls-label parameter must be enabled in the route-map configuration.
information.
45383, 45b9 Enhancement. Support for QAM 8x192 shared channels has been
45957 implemented in Release 7.2. See the Casa Systems – CMTS Release 7.2
Features Guide for detailed information.
45833 45b9 A change to the PCR software logic has been implemented to handle stream
transitioning from data stream where the PCR PID is specified as 0x1FFF to a
normal video stream where the PCR PID is not 0x1FFF.

1-150 Release Notes

version
46077 45b9 Enhancement. The CMTS now supports up to 2000 sub-interfaces system
wide. All 2000 subnets can be configured under a single IP bundle interface or
over multiple IP bundle interfaces. However, the total cannot exceed 2000
subnets across all IP bundles on a per-system basis.
46108 45b9 A fix has been applied to correct a timing problem in the software logic which
could cause the QAM process to attempt video session data retrieval after the
data had been freed. Checks have been applied in the software to ensure
buffers are valid before accessing statistics.
46213, 45b9 Enhancement. The CASA-VIDEO-MIB has been implemented to support
43420, SNMP monitoring of video streams.
42505
46297 45b9 A software change has been applied to improve the processing and timing of
keepalive messages between the active and standby SMMs. When the standby
SMM is in the process of taking over as the active SMM, and if a keepalive
message is received from the peer SMM (going into standby), the peer SMM will
be rebooted immediately to achieve the standby state.


version
46438 45b9 Feature. The [no] ip domain-name <string> command has been introduced in
the Casa configuration mode to allow users to specify a default fully qualified
domain name (FQDN) for the system’s DNS service. The configured domain
name can contain up to 63 characters. Use the no form of the command to
remove the configured domain name.
Ping requests from the CMTS to the configured host domain are supported with
this feature. Note that the nameserver parameter must be set to the source IP
address of the DNS server in order to process domain name requests and
responses at the CMTS.
Example:
CASA(config)# ip domain-name casa-systems.com
CASA(config)# end
CASA# ping www
PING www.casa-systems.com (98.129.229.220): 56 bytes of

data.
64 bytes from 98.129.229.220: icmp_seq=0 ttl=50 time=60.396
ms
64 bytes from 98.129.229.220: icmp_seq=1 ttl=50 time=60.713
ms
--- www.casa-systems.com ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 60.396/60.555/60.713/0.159
ms
46501 45b9 Enhancement. The debug ip bgp updates command has been revised to
include inbound (in) and outbound (out) updates.
Example:
CMTS# debug ip bgp updates
<cr>
in BGP updates of incoming direction
out BGP updates of outcoming direction
CMTS# debug ip bgp updates in

CMTS# debug ip bgp updates out

1-152 Release Notes

version
46849 45b9 A problem which was causing the logging source-interface to revert to loopback
0 after a system reboot has been fixed. Previously, issuing no logging
source-interface loopback 0 followed by a system reboot re-enabled
loopback 0 as the logging source-interface.
46985 45b9 A case was observed in which the BGP router identifier was incorrect after
merging the current BGP configuration into a newer software release. The
problem was caused by incorrect handling of route time stamps where the
routes redistributed by other protocols were considered obsolete and missing.
The fix includes checks to ensure that the correct route identifier is applied after
a configuration merge and with local routes properly distributed to BGP.
47198 45b9 The casaSfpTxPower, casaSfpRxPower, and casaSfpOperStatus MIB
objects have been added to the CASA-SFP-MIB file. The matching CLI
command is the show interface xgige transceiver command in the diag
context. The MIB displays the signal level for each SFP transceiver (optical Tx
and Rx power levels) and operational status. The matching CLI command is the
show interface xgige transceiver command in the Casa diag mode.
information.
47227 45b9 A problem which caused VPWS status to go from the “active” state to the
“inactive” and “standby” states after an SMM switchover to the redundant SMM
has been fixed. The fix applies improved notification processing when LDP
sessions with peers change state. The problem was observed with the show
mpls vpws xconnect command output after the SMM switchover.
47309 45b9 When clearing the system log file in the Casa Video Web interface from the
Monitoring->Log page and selecting the Clean function, the resulting message
captured in the system log and displayed on the Monitoring -> Log page is now
the same message that is generated by the CLI.
Example:
1)GUI
Wed May 4 01:03:57 2016 AL CLI-0:smm2 smm2: User root
cleared system logfile
(2)CLI
[Wed May 4 01:03:57 2016]-AL-CLI-0: smm2: User root
cleared system logfile


version
47421 45b9 Broadcast ARP, multicast IGMP, and ARP packets for unknown IPs are now
sent exclusively to the downstream primary channel in the DOCSIS MAC
domain. Previously, these ARP packets were being sent over both the primary
and secondary channels.
47446 45b9 Enhancement. The tcp mss <68:9140> command has been added to set the
initial maximum MTU segment size for both IPv4 and IPv6. Applying the no
version of the command sets the default behavior to the MTU of the interface
(1500 is the default, but can be user defined), minus 40 bytes for IPv4 or 60
bytes for IPv6. This means that on a default 1500 byte MTU interface, the IPv4
TCP MSS will be 1460, and the IPv6 TCP MSS will be 1440.
Example:
CASA(config)# tcp mss ?
<num=68:9140> MSS (default: IPv4: (MTU - 40B) IPv6:
( MTU-60B))
CASA(config)# tcp mss 100

CASA(config)# end
CASA# show running-config | include "tcp mss"

tcp mss 100
CASA# no tcp mss
47575 45b9 A encryption problem was observed in a lab environment in which PowerKey
sessions were being created as clear sessions. The fix corrects the software
logic used in checking and determining PowerKey encrypted traffic.
47592 45b9 A software error was discovered where the multicast group count was being
updated incorrectly under some conditions, resulting in future multicast session
creations being rejected. The error is fixed in this software build.
47665 45b9 New feature. The dhcp renew keep-server-address command has been
introduced in the Casa CLI to enable the DHCP server source IP address in
DCHP RENEW and DHCP REPLY packets. The new command addresses
situations where cable modems and CPEs behind firewalls end up with a
mismatched DHCP IP address causing DHCP RENEW requests to fail.
The default setting is disabled. Use the no form of the command to revert to the
default setting.
Example:
CASA(config)# dhcp renew keep-server-address

1-154 Release Notes

version
47735 45b9 Release 7.2 introduces a revised Casa Video Web interface with improved
screen presentations and usability enhancement. For detailed information, see
the Casa Systems – CCAP Video Edge User Guide for Release 7.2.
The following Reserved PID functionality has been added to the

Configure->Video Global page:
• Reserved PID Upper Limit

• Drop Reserved Pids (Yes/No)
Corresponding CLI:
CASA(config)# video reserved-pid upper-limit

<1-65535> upper limit of reserved pid. Default is 15
CASA(config)# video drop reserved-pids
CASA(config)# video drop reserved-pids

CASA(config)# no video drop reserved-pids


version
47786 45b9 Enhancements. A number of improvements have been implemented in the

software to address conditions where excessive ingress traffic to the SMM GigE
and xGigE interfaces can cause congestion and resulting IS-IS and OSPF
adjacency flaps with neighbor routers.
The software changes to address traffic congestion include improved

class-of-service (COS) priority queuing and buffering of traffic, as well as
hierarchical QOS (H-QOS) for improved handling of ingress unicast and
multicast video traffic to a single QAM. Rate limiting is NOT enabled with this
enhancement.
Ingress NSI traffic is grouped into three priorities:
• Control (routing protocols, etc)

• Video
• Best Effort (BE)
Each NSI traffic type has a separate, guaranteed, and unshared buffer space so
that other traffic remains unaffected. The output ports (to the line cards) have
eight unicast and four multicast queues with different priorities. The hierarchical
queuing allows an intermingling of the unicast and multicast priority traffic.
Unicast queues 0-3 are scheduled equally with multicast queues 0-3, where
unicast queues 4-7 are given higher priority.
The port buffer thresholds are set up so that over subscription of NSI or line card
ports WILL NOT affect control flows in the system.
There are no CLI additions or changes with these enhancements.

47840 45b9 Enhancement. The number of dynamic free buffers available for active DBC
transactions has been increased from 600 to 1000 for improved processing
during peak traffic periods.
47855, 45b9 Enhancement. The casa-lawful-intercept-mib has been implemented in
42084 Release 7.2 to configure lawful intercept (LI) mirrored data into a VRF.
See the Casa Systems – CMTS Release 7.2 Features Guide for additional
information.

1-156 Release Notes

version
47883 45b8 The attached-bit receive ignore command has been introduced in the
router-isis configuration to configure the IS-IS router or IPv6 address-family to
ignore the attached-bit in received Level 1 link-state packets (LSPs). The
attached-bit can also be set using the set-attached-bit {always | never}
command.
The default setting (no attached-bit receive ignore) allows the router to install
the default route when the attached-bit is set in the LSP receive. The command
can also be set at the IPv6 address-family level.
Example:
CASA(config)# router isis
CASA(config-isis)# attached-bit receive ignore
[no] attached-bit receive ignore
CASA(config-router-isis)# address-family ipv6

CASA(config-router-isis-af)# attached-bit receive ignore
48005 45b9 Enhancement. The set ipv6 next-hop <ipv6-address> command has been
added to the global BGP route-map configuration for establishing neighbor
sessions and route redistribution with the specified peer IPv6 address. Use the
no form of the command to remove the IPv6 next-hop setting from the
route-map configuration.
Example:
CASA(config)# route-map V6-CMTS-TO-HUB permit 5
CASA(conf-route-map V6-CMTS-TO-HUB)# set ipv6 next-hop

2001:578:30:7000:174:68:255:206
CASA(conf-route-map V6-CMTS-TO-HUB)# no set ipv6 next-hop


version
48036 45b9 Enhancement. The show video power-key encrypt-data [session <num>]
has been implemented in the Casa diag mode for helping troubleshoot
PowerKey encrypted sessions.
Example:
CASA(diag)# show video power-key encrypt-data session 88
Power-Key encryptor data for session 001710035f40 00000088:

streamId(local session id): 4474306
Power-Key session id (to lib): 1
is_encrypted: 1
start_immediate: 1
start_time: 0
ecm_update_period: 100
cw_update_period: 4000
cw_setup_peroid: 450
caDATA[0] typeOfData: 0
caDATA[0] deliveryId: 0
caDATA[0] serialNumber: 0
caDATA[0] caDataLen: 80
caDATA[0] caData:
204e050e 00103900 0e000500 0000017e 21003000

00000000 00000000 00000000
00000000 00000001 00000002 00000003 00000004

00000005 00000006 00000000
20202020 20202020 20202020 20202020

1-158 Release Notes

version
48090 45b9 Enhancement. The ip route <net_addr> <strict_ip_address> [gw-vrf

<string>] [<num=1:255>] command has been revised with the [tag
<num=1:4294967295>] option to specify a static route tag inside a VRF
instance.
Example:
CASA(config)# ip route vrf VPN1 10.1.0.0/16 64.0.53.199 tag
40001
CASA(config)# ip route vrf VPN1 10.1.0.0/16 64.0.53.199
global tag 40002
CASA(config)# show ip route 10.1.0.0/16 vrf VPN1

Routing entry for 10.1.0.0/16
Known via "static", distance 1, metric 0, tag 40002, best
64.0.53.199 inactive
tag 40001
* 64.0.53.199, via vlan53
tag 40002
To disable static routes, use the no form of this command.
Example:
CASA(config)# no ip route vrf VPN1 10.1.0.0/16 64.0.53.199
tag 40001
CASA(config)# no ip route vrf VPN1 10.1.0.0/16 64.0.53.199
global tag 40002
CASA(config)# show ip route 10.1.0.0/16 vrf VPN1

Routing entry for 10.1.0.0/16
Known via "static", distance 1, metric 0, tag 40002, best
64.0.53.199 inactive
tag 40001
48229 45b9 A problem which was causing the logging source-interface to revert to loopback
0 after a system reboot has been fixed. Previously, issuing no logging
source-interface loopback 0 followed by a system reboot re-enabled
loopback 0 as the logging source-interface.


version
48270 45b9 Enhancement. IPv4 and IPv6 DHCP authorization for IP bundles and DOCSIS
MAC domains can now be controlled independently using the ipv4-only and
ipv6-only options. Previously, DHCP authorization was either on for both IPv4
and IPv6, or off.
Using the dhcp-authorization command with no options turns DHCP

authorization on for both IPv4 and IPv6.
Example:
CASA(config)# interface docsis-mac 3
CASA(conf-if-mac 3)# dhcp-authorization ?

<cr>
ipv4-only Enable dhcp authorization for IPv4 only
CASA-C10G(conf-if-mac 3)# no dhcp-authorization
CASA(config)# interface ip-bundle 5

CASA(ip-bundle 5)# dhcp-authorization ?
<cr>
default use dhcp authorization in mac-domain
48385 45b9 An optimization issue which was causing “slowest mtype” messages to be
reported in the system log file has been fixed
48407 45b9 A fix has been implemented to address special PMT packets where a non-zero
pointer field existed, and with the PMT table contained in multiple MPEG video
transport packets. In a typical MPEG stream, the pointer filed in a PMT table is
0. The problem resulted in some internal memory overriding due to the non-zero
pointer. The software fix addresses the handling of special PMT packets having
the non-zero pointer field.

1-160 Release Notes

version
48500 45b9 Enhancement. The additional ecdsa and ed25519 encryption algorithm values
were added to the dsa and rsa values for the ssh-server gen-hostkey
command in the CLI. This command generates a host key to replace the default
one. The key can now be based on the Digital Signature Algorithm (DSA);
Elliptic Curve Digital Signature Algorithm (ECDSA); Twisted Edwards-curve
Digital Signature Algorithm (EdDSA); or Rivest, Shamir and Adleman (RSA)
cryptographic algorithm. The command is executed in Casa enable mode.
Example:
CASA# ssh-server gen-hostkey ecdsa
CASA# ssh-server gen-hostkey ed25519
48515 45b9 A software change to ensure SSH key synchronization between active and
standby SMMs has been implemented to prevent possible warning messages
from SSH clients after an SMM switchover.
48642 45b9 A fix has been applied in the software to correct a problem which resulted in
mismatched AAA keys between the CMTS and TACACS/RADIUS servers. The
fix corrects a compatibility issue where keys generated with OpenSSL Version
1.0.0r could not be decrypted with OpenSSL V1.0.2d. Keys will now be
decrypted with their compatible OpenSSL version with migration to Casa
Release 7.2.
48675 45b9 Enhancement. The show video edis statistics command has been revised to
display GQIv2 protocol and RPC 103-105 statistics. This is a display
enhancement only.
48752 45b9 A fix to correct an error handling issue due to malformed Entitlement Control
Message (ECM) channel and stream messages has been applied. The ECM
messages, which were missing the expected error status ID, caused the
receiving Conditional Access (CA) server to be non-responsive to the ECM
messages.


version
48970 45b9 Feature. The domain-name <string> command has been introduced in the
Casa configuration mode to allow users to specify a default fully qualified
domain name (FQDN) for the Entitlement Control Message Generator (ECMG),
where a connection from the CCAP to the ECMG can take place using the
domain name rather than the IPv4 or IPv6 ECMG address. The configured
domain name can contain up to 254 characters.
Note: Either a domain name OR an IP address may be configured at any one

time to establish a connection with the ECMG. The software will return an error
message if an ECMG domain name or an IP address is already configured.
Example:
CASA(config)# video simulcrypt ecmg test
CASA(config-ecmg test)# domain-name ?

<string> domain name of ECMG, maximum length is 254
CASA(config-ecmg test)# domain-name ecmg.casa-systems.com
CASA(config-ecmg test)# ip-address 6.6.7.8

SimulCrypt ECMG domain name is configured.

1-162 Release Notes

version
49059, 45b9 Enhancement. A route map can now be imported from or exported to a Virtual
42172, Routing and Forwarding (VRF) instance under the address-family context of a
48662 Border Gateway Protocol (BGP) configuration or VRF definition. This function
imports or exports IPv4 prefixes from or to the global routing table associated
with the VRF table.
Example:
CASA(config)# ip prefix-list PROV-VOIP seq 10 permit
192.168.151.0/24
CASA(config)# route-map kiwi permit 10

CASA(conf-route-map kiwi)# match ip address prefix-list
PROV-VOIP
CASA(config)# router bgp 1

CASA(config-router-bgp)# address-family ipv4 vrf mango
CASA(config-router-af)# import ipv4 unicast ?
<1-2147483647> import prefixes number, default 1000
map Route-map to modify the attributes
CASA(config-router-af)# export ipv4 unicast 3000 map ?

WORD Name of the route map
CASA(config-router-af)# export ipv4 unicast 3000 map kiwi
CASA(config)# vrf definition kw

CASA(config-vrf)# address-family ipv4
CASA(config-vrf-af)# export ipv4 unicast ?
<1-2147483647> export prefixes number, default 1000
map Route-map to modify the attributes
CASA(config-vrf-af)# export ipv4 unicast 2000 map ?

WORD Name of the route map
CASA(config-vrf-af)# export ipv4 unicast 2000 map kiwi


version

docsIf31CmtsUsOfdmaProfileStatusTable objects in the SNMP
DOCS-IF31-MIB for OFDMA. These objects include the following:
• docsIf31CmtsCmUsOfdmaProfileTotalCodewords
• docsIf31CmtsCmUsOfdmaProfileCorrectedCodewords
• docsIf31CmtsCmUsOfdmaProfileUnreliableCodewords
• docsIf31CmtsCmUsOfdmaProfileLastPartialChanTime
• docsIf31CmtsCmUsOfdmaProfileLastPartialChanReasonCode
• docsIf31CmtsCmUsOfdmaProfilePartialChanReasonCode
49103 45b9 Enhancement. The following fields have been added to the show video
simulcrypt ecmg display output.
• Access-criteria: <message>
• Stream ECM ID: <message>
• Stream status: <message>

1-164 Release Notes

version
49246, 45b9 Enhancement. The show cable modem partial-service and show cable
47449 modem bonding commands in the CLI have been enhanced to display reason
information for cable modem channels (upstream, downstream, OFDM, and
OFDMA) going into the partial service state. The reason types are now listed
with the command and appended to the UD/DS CHANNEL EXCLUDED column
values, as follows:
• 0 – Unknown
• 1 – MAC domain descriptor (MDD) timeout
• 2 – QAM/FEC lock failure
• 3 – Bad transmit channel configuration (TCC)
• 4 – Bad transmit power
• 5 – Range timeout
• 6 – Next codeword pointer (NCP) profile failure
• 7 – Impaired channel
• 8 – Unreachable channel
• 9 – Ranging failure
Example:
CASA# show cable modem partial-service
Reason code: x/y/z(reason_code)
1 MDD timeout, 2 QAM/FEC lock failure
3 Bad tcc, 4 TR power bad
5 Range timeout, 6 NCP profile failure
7 Impaired channel, 8 Channel unreachable
9 Ranging failure, 0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED

id Intf Intf SET SET
08eb.74bc 63 12/0.0/0 2/0/31 256 257(3*23) 12/0.0w(3)
906e.bbd4 63 12/0.1/0 2/0/31 256 257(3*23) 12/0.0w(3)


version
49286 45b9 The show tech-support command has been enhanced to include the following
additional information in the displayed output:
• show dmesg — system kernel messages

• dmesg.sav and coredump.sav files on /fdsk, if present
• ls -ltr /fdsk command output
• ha-log and ha_log.bak files
• ha_debug_log and ha_debug_log.bak files
49505 45b9 Enhancement. Support for MPLS VPWS control-word bit (per RFC 4447) has
been enabled at the CMTS by default. A TLV with a U-bit = True has been
added to all virtual circuit (VC) label mapping messages. There are no
configuration requirements at the CMTS.
The show mpls vpws xconnect mpls-vc-map command has been expanded
to include Control-Word status (enabled or disabled). When LDP receives a VC
label Mapping message with this TLV present, and with the peer being a Casa
CMTS, the VPWS being created will always have the Control-Word bit disabled.
49652 45b9 Support for the latest version of the DOCS-IF31-MIB 2016-03-10 has been
applied in this software build to correct statistics and counter errors reported in
the earlier version of the MIB.
49590 45b9 Logic for the FPGA Driver for SEU Single Bit Error Recovery, SEU Multiple Bit
Error Detection, and SEU Controller Heartbeat loss has been implemented. The
software fix reduces the number observed SEU errors.
49808 45b9 A problem where AAA users with insufficient privileges (read-only) were allowed
to make configuration changes in the Video Web interface has been fixed.

1-166 Release Notes

version
49813 45b9 Enhancement. VRF interoperability has been implemented for the Event
Information Scheduler (EIS) and the Entitlement Control Message Generator
(ECMG) communication interfaces. Configure the named VRF instance string
(with up to 32 characters) prior to issuing the following commands in the Casa
CLI.
• [no] video simulcrypt ecmg <string> [vrf <string>]

• [no] video simulcrypt eis [vrf <string>]
CCAP communication with the ECMG and the EIS will take place over the
configured VRF routing instance.
Example:
CASA(config)# video simulcrypt ecmg vrf vrfname
CASA(config)# video simulcrypt eis vrf vrfname

49855, 45b9 A software fix has been implemented to correct a video recovery delay on DVB
49879 Simulcrypt channels observed at SMM switchover time. The recovery delay was
caused by full reinitialization of the video session at the standby SMM instead of
switching over the currently encrypted video session.


version
49872 45b9 Enhancement. The show snmp statistics command has been enhanced to
display UPD drop statistics. The snmpCongestionDrops field has been added to
the end of the display listing.
CASA#show snmp statistics

SNMP agent statistics
snmpInPkts: 38
snmpOutPkts: 38
snmpInBadVersions: 0
snmpInBadCommunityNames: 0
snmpInBadCommunityUses: 0
snmpInASNParseErrs: 0
snmpInTooBigs: 0
snmpInNoSuchNames: 0
snmpInBadValues: 0
snmpInReadOnlys: 0
snmpInGenErrs: 0
snmpInTotalReqVars: 38
snmpInTotalSetVars: 0
snmpInGetRequests: 0
snmpInGetNexts: 38
snmpInSetRequests: 0
snmpInGetResponses: 0
snmpInTraps: 0
snmpOutTooBigs: 0
snmpOutNoSuchNames: 0
snmpOutBadValues: 0
snmpOutGenErrs: 0
snmpOutGetRequests: 0
snmpOutGetNexts: 0
snmpOutSetRequests: 0
snmpOutGetResponses: 38
snmpOutTraps: 0
snmpEnableAuthenTraps: 1
snmpSilentDrops: 0
snmpProxyDrops: 0
snmpCongestionDrops: 36
49873 45b9 Enhancement. The software now translates the transport stream ID (TSID) to
include the slot/port/channel information for easier translation in video log
messages when logging is enabled with the video logging edis-text command.

1-168 Release Notes

version
49877 45b9 Enhancement. The show video session <session-id> command now
includes the transport stream ID (TSID) in the listed session creation
parameters. Previously, the QAM channel translation to the output port number
was being presented instead of the expected TSID.
49909 45b9 Upstream MPLS traffic received over CMTS trunk interfaces was not being
passed to all member port interfaces, preventing the traffic from being properly
load balanced. Only MPLS traffic is affected by the problem. This problem has
been fixed.
49950 45b9 After performing an SMM switchover from the active to the standby SMM using
the ha module 6 protect command, the SMM in slot 6 (now in standby mode)
continued to be incorrectly reported in the “Not Ready” state with the SMM in
slot 7 now active. A fix has been applied to ensure that the presently active
SMM correctly detects the ready state of the standby SMM in redundancy
switchover operations.
49992 45b9 The cm-mode modulation-immediate command has been introduced in the
Casa spectrum-rule configuration context to immediately hop (up or down) to
the correct modulation profile based on the SNR reading.
To perform the existing behavior of cascading though all available hop profiles,
issue the cm-mode command without the modulation-immediate option.
Example: To immediately hop to the correct modulation profile

CASA(config)# spectrum rule 10CASA(conf-rule 10)# cm-mode
modulation-immediate
Example: To cascade through all available modulation profiles

CASA(config)# spectrum rule 10CASA(conf-rule 10)# cm-mode
49975 45b9 The cable-sec config-file-learning setting (when enabled) can now be
observed with the show running-config verbose command output. Previously,
show running-config would only display the setting when it was disabled. This
fix also corrects the documentation error to state that the cable-sec
config-file-learning setting is enabled by default. There was no change to the
default enabled setting in the software.
50226 45b9 The lawful-intercept source-interface loopback setting is now properly
recovered after an SMM switchover. Previously, an SMM switchover could
cause IPv6 lawful intercept packets to use an incorrect IP address as the source
interface.


version
50313 45b9 Enhancement. Encoding of the Type 1 byte in the OFDM Downstream Profile
Test Request (OPT-REQ) message has been changed from BITS encoding to
standard encoding per CableLabs ECO MULPIv3.1-O-16.1458. Previous to the
change, some D3.1 modems were rejecting the Requested Statistics encoding
in the OPT-REQ message with no OPT-RSP message.
50319 45b9 A software fix has been applied to correct a situation where a modem was able
to come online using the wrong configuration file. The fix enforces the cable sec
config-file-learning setting when enabled to ensure that the correct
configuration file is applied to the cable modem. Configuring the CMTS-MIC
with the shared-secret <mic-string> provided the workaround.
50384 45b9 Performance optimization to enable faster SNMP response times to SNMP
queries (snmpget, snmpwalk, snmpbulkget, and snmpbulkwalk queries to
the Casa database has been applied in the software. Previously, slower than
normal responses were reported with queries to the
docsIfCmtsCmStatusInetAddress MIB. Actual performance will vary depending
on the network and configuration.
50422 45b9 For the QAM 8x192 module, the video channel-id-offset parameter setting has
been increased to 79.
50553 45b9 Enhancement. The default bandwidth/burst for the QAM_ENCAP forwarding
policy class has been increased from 80K/30K to 160K/60K for improved
performance.
50609 45b9 A BGP network topology issue which was causing an MPLS FTN (FEC to
NHLFE) message parsing error during an SMM switchover has been resolved.
The error occurred during the FTN status update where an owner could not be
set in the FTN Reply message. The BGP error logs did not impact service.
50680 45b9 Enhancement. The console-password <password> command has been
removed from the Casa CLI. The console-password configuration is now
specified with the adduser command. The existing setting is converted to the
new configuration and no reconfiguration is necessary.
Example:
CASA# adduser USER1 privilege 15 password Tr3btr3b

1-170 Release Notes

version

docsIf31CmtsDsOfdmProfileStatsTable objects in the SNMP
DOCS-IF31-MIB for OFDM. These objects include the following:
• docsIf31CmtsDsOfdmProfileStatsTable
• docsIf31CmtsDsOfdmProfileStatsEntry
• docsIf31CmtsDsOfdmProfileStatsProfileId
• docsIf31CmtsDsOfdmProfileStatsConfigChangeCt
• docsIf31CmtsDsOfdmProfileStatsFullChannelSpeed
• docsIf31CmtsDsOfdmProfileStatsOutOctets
• docsIf31CmtsDsOfdmProfileStatsOutUnicastOctets
• docsIf31CmtsDsOfdmProfileStatsOutMulticastOctets
• docsIf31CmtsDsOfdmProfileStatsOutFrames
• docsIf31CmtsDsOfdmProfileStatsOutUnicastFrames
• docsIf31CmtsDsOfdmProfileStatsOutMulticastFrames
• docsIf31CmtsDsOfdmProfileStatsCtrDiscontinuityTime


version
50728, 45b9 Enhancement. Support has been added for the

50729 casaCmtsCmMacToCpe2Table objects in the SNMP
CASA-CABLE-CMCPE-MIB to support multiple virtual routing and forwarding
(VRF) queries. These objects include the following:
• casaCmtsCmIpToCpe2Table
• casaCmtsCmIpToCpe2Entry
• casaCmtsCmIpToCpe2CmVrfId
• casaCmtsCmIpToCpe2CmInetAddressType
• casaCmtsCmIpToCpe2CmInetAddress
• casaCmtsCmIpToCpe2VrfId
• casaCmtsCmIpToCpe2InetAddressType
• casaCmtsCmIpToCpe2InetAddress
• casaCmtsCmIpToCpe2MacAddress
• casaCmtsCmMacToCpe2Table
• casaCmtsCmMacToCpe2Entry
• casaCmtsCmMacToCpe2CmMacAddress
• casaCmtsCmMacToCpe2VrfId
• casaCmtsCmMacToCpe2InetAddressType
• casaCmtsCmMacToCpe2InetAddress
• casaCmtsCmMacToCpe2MacAddress

1-172 Release Notes

version

casaCmtsCpeIpNetToPhysical2Table objects in the SNMP
• casaCmtsCpeIpNetToPhysical2Table
• casaCmtsCpeIpNetToPhysical2Entry
• casaCmtsCpeIpNetToPhysical2IfIndex
• casaCmtsCpeIpNetToPhysical2NetAddressType
• casaCmtsCpeIpNetToPhysical2VrfId
• casaCmtsCpeIpNetToPhysical2NetAddress
• casaCmtsCpeIpNetToPhysical2CmPhysAddress
• casaCmtsCpeIpNetToPhysical2Type
50732, 45b9 Enhancement. Support has been added for the
50733 casaCmtsCmMacToCpe2Table objects in the SNMP
• casaCmtsCpeIpToCm2Table
• casaCmtsCpeIpToCm2Entry
• casaCmtsCpeIpToCm2CpeVrfId
• casaCmtsCpeIpToCm2CpeInetAddressType
• casaCmtsCpeIpToCm2CpeInetAddress
• casaCmtsCpeIpToCm2StatusIndex
• casaCmtsCpeIpToCm2Ipv4Address
• casaCmtsCpeIpToCm2Ipv6Address
• casaCmtsCpeIpToCm2MacAddress


version
50765 45b9 An issue which was causing the OFDMA Admin and Operating status fields to
be reported as DOWN when the OFDMA channel was enabled and with
modems registered. The problem was observed in the show controller
upstream command output. OFDMA status information can now be displayed
using the show controller upstream | begin “Interface ofdma” command
under the config-ofdma-channel configuration context in the CLI.
Example:
CASA(conf-ofdma-channel 4/0.0)#show controller upstream |
begin "Interface ofdma"
Interface upstream 4/1.0/0 information:

IfIndex : 5002064
Admin status: UP
Operating status: UP
Frequency: 20000000 Hz
Channel Width: 3200000 Hz
Power Level: 0
Modulation profile 2
SNR: 0.0
50857 45b9 Enhancement. The show cable modem fail counters command has been
removed from the CLI and replaced by the show cable modem offline
counters command to display failure results for cable modems that go offline
due to failure conditions. The counts reflect conditions resulting from ranging,
DHCP, TFTP, CMTS registration, Baseline Privacy Interface (BPI), or online
backup or expiration. The clear cable modem offline counters [docsis-mac
<1:96>] command may be used to reset the offline counters associated with a
DOCSIS-MAC interface.
Example:
1 0 0 0 0
2 0 0 0 0
Total: 0 0 0 0
CASA# clear cable modem offline counters docsis-mac 1

50921 45b9 Enhancement. The Monitoring > QAM screen in the Casa Video web interface
has been changed to the Monitoring > Video QAM screen to clarify that it is the
video QAM interface.

1-174 Release Notes

version
50922 45b9 A software change has been applied to correct a problem where a modem was
unable to begin unicast ranging after sending the INIT_RNG_REQ packet to the
CMTS. The problem was observed after a modem upstream channel partial
service condition followed by DBC recovery with initial ranging not being
scheduled at the CMTS. A fix to the upstream process has been implemented to
ensure scheduling of the correct initial ranging technique after modem DBC.
50928 45b9 Enhancement. The optional base parameter has been added to the video qam
export configuration slot command in the CLI to set the output port base. The
output port base is reflected in the outputPortBase parameter in the
configuration file and varies by device.
The default base value is 0 for a Casa or Cisco System Resource Manager
(SRM) QAM 8x96 or QAM 8x192, or 1 for a BigBand SRM QAM 8x96 or
QAM 8x192. The slot value can be a comma-separated list. The syntax of the
command is:
CASA# video qam export configuration slot <list>

base {0|1} [filename <file>} [in-service-state]
[srm-num <1:8>]
Example:
CASA# video qam export configuration slot 2,11 base 1
in-service-state filename casa-base1
Export video QAM configurations of module 2 to file /
tftpboot/casa-base1_2_1 successfully
50955 45b9 A problem which was preventing upstream channels from being added or
removed using DBC has been fixed. The problem was observed after a modem
upstream partial service condition, DBC rejecting the channel change with a
valid reason, and a failure to add the removed channels back into the upstream
channel set. Resetting the modem allowed the modem to recover and range
with the CMTS.
50965 45b9 The software will now check the route redistribution configuration for OSPF
instances under the same VRF, and not other VRFs. Because route
redistribution was ignored and not checked under the same VRF, the IP bundle
network configuration scope was not being redistributed to OSPF neighbor
routers. This problem was observed in a test network and has been fixed.


version
50972 45b9 Improved error handling associated with video encrypted sessions between the
CMTS and ECMG servers has been implemented to prevent possible looping
conditions. When a stream error is detected, the CMTS will now reset and
reestablish the connection with the ECMG server. Syslog messages to report
stream errors and the ECMG server connection reestablishment have been
implemented.
Example: Sample console log

[Sat Jun 8 19:31:14 2030]-DE-SIM-1: smm6:
ecmg_scs_stream_error:
[Sat Jun 8 19:31:14 2030]-DE-SIM-1: smm6:

send_ecmg_stream_error_msg:
[Sat Jun 8 19:31:14 2030]-DE-SIM-1: smm6:

restartStreamMgr: systemId 18981:
[Sat Jun 8 19:31:14 2030]-DE-SIM-1: smm6: isEcmgActive:

systemId 18981, end=7:
[Sat Jun 8 19:31:14 2030]-DE-SIM-1: smm6: isEcmgActive: 0

is active
50992 45b9 A problem which was causing the Telnet process to get stuck in a repeating
looping state when awaiting a connection response from a remote Telnet client
has been fixed. The looping condition caused added memory and CPU
consumption with defunct Telnet and system shell sessions remaining open in
the observed show current user display output.
51004 45b9 Enhancement. The Replicate Port parameter was removed from the Shared
Channel section of the Configure > QAM screen in the Casa Video web
interface. The table column no longer shows the parameter and it was removed
from the Modify Port dialog.
51084 45b9 Enhancement. The System > Users screen in the Casa Video web interface
was modified to show a User List table with username, privilege level, GUI
access, and read/write privilege columns.
51086 45b9 A fix has been implemented to correct an issue where a virtual circuit peer
remains down when changing the transport-mode from VLAN to Ethernet. The
issue was caused by the CMTS receiving the label withdraw message from the
peer before the new label mapping message for the new virtual circuit thread
was received.

1-176 Release Notes

version
51138 45b9 On the QAM 8x192 module with 64 QAM channels/port, the CLI maximum port
power is now correctly shown as 570 and not 580, as in previous releases.
51183 45b9 A rate limiting and packet counter calculation error in the software which could
cause packets destined for policy-based routing to be dropped instead of being
forwarded has been fixed.
51188 45b9 It was observed that some D3.0 modems will more than double the frequency
offset correction values returned during periodic ranging. As a result, the
frequency offset will continue to increase until the upstream channel drops
offline. To compensate for the modem behavior, the system will now only return
half of the frequency offset correction value during a given periodic ranging
opportunity.
51218 45b9 An issue existed where multi-segment VPWS peers (CMTS, ALU, and ASR)
could not establish a peering session if the control word configuration was not
matched at the end peers. A fix has been applied so that the PW tunnel will be
UP after upgrading the software regardless of whether the control word is
enabled or disabled at the remote PE.
51296 45b9 Enhancement. Subscriber Traffic Management (STM) has been enhanced to
monitor interface utilization in addition to the currently supported subscriber
transmission rates. STM only manages a subscriber if its transmission rate and
the interface utilization both exceed predefined limits in the cable traffic-policy
configuration.

51326 45b9 When changing the symbol rate on a unicast channel using the Casa Video
Web interface, the software incorrectly reported that the Annex had been
changed (and not the symbol rate) in the confirmation dialog box. The problem
was observed in the Web interface only; the CLI was not affected. This issue
has been fixed.


version
51329 45b9 Enhancement. The ECMG error codes which can be returned by the ECMG
protocol when there are session issues between the CMTS and ECMG server
are now included in the system log for troubleshooting purposes.
0x0000 DVB Reserved

0x0001 invalid message
0x0002 unsupported protocol version
0x0003 unknown message_type value
0x0004 message too long
0x0005 unknown Super_CAS_id value
0x0006 unknown ECM_channel_id value
0x0007 unknown ECM_stream_id value
0x0008 too many channels on this ECMG
0x0009 too many ECM streams on this channel
0x000A too many ECM streams on this ECMG
0x000B not enough control words to compute ECM
0x000C ECMG out of storage capacity
0x000D ECMG out of computational resources
0x000E unknown parameter_type value
0x000F inconsistent length for DVB parameter
0x0010 missing mandatory DVB parameter
0x0011 invalid value for DVB parameter
0x0012 unknown ECM_id value
0x0013 ECM_channel_id value already in use
0x0014 ECM_stream_id value already in use
0x0015 ECM_id value already in use
0x0016 to 0x6FFF DVB Reserved
0x7000 unknown error
0x7001 unrecoverable error
0x8000 to 0xFFFF ECMG specific/CA system specific/User
defined
51342 45b9 A change has been made in the software logic to allow up to 16 forwarding
policy (FP) rules with full optimization when the same source MAC address is
learned by multiple IPv4 or IPv6 network side interfaces. If the number of FP
rules exceeds 16, packets will continue to be forwarded over network interfaces,
but with reduced optimization. A warning message will be presented to the user
console in this situation.

1-178 Release Notes

version
51402 45b9 A problem which caused modems to go offline or into downstream partial
service on one random QAM port after a QAM module switchover has been
fixed. During the QAM switchover, traffic on the original QAM port failed to
synchronize properly at the same standby port, preventing modems on that port
from recovering. The problem was observed on the QAM 8x192 module. The fix
has also been applied to the QAM 8x96 module.
51407 45b9 The maximum number of IPv6 subnets under the interface ip-bundle
configuration has been decreased from 2600 to 256 for improved routing table
performance. The software continues to support up to 2600 IPv4 subnets in the
configuration.
51422 45b9 Enhancement. The Casa diagnostic mode module <number>
qam-config-counter reset command was added to the Casa CLI to reset the
QAM Configuration Compiler (QCC) counters without having to perform a
system reboot. Counters requiring reset are revealed after a configuration
change with a message such as Enabled Channels and ref counts
don’t check, event_type: #, when shutting down ports.
The command returns warnings if other than a QAM module is specified and
when not all the QAM ports are shut down. Responding with YES resets the
counters to zero. Ports which are still enabled will show counters as negative
with the show interface qam <slot>/<port> block command. The ports must
be shut down, the command rerun, and the ports re-enabled.
51450 45b9 A software change to correct an issue where the CMTS was continually logging
cable event messages after a modem upstream channel was muted. The
problem was observed in a situation where the cable partial-service
continue-ranging parameter was enabled in the configuration, causing cable
event 82010200 messages to build up in the log files. Cable event messages
associated with upstream muted channels will no longer be logged.
51484 45b9 A fix has been implemented to ensure that the privilege exec level settings in
the configuration allows users to execute the specified CLI commands at each
level with AAA TACACS user authentication enabled and with local user
authorization. The fix provides revised checking of command privileges in this
configuration so that users are only provided access to authorized CLI
commands by privilege level.


version
51822 45b9 The spectrum rule cm-mode tolerance-count parameter range has been
revised from <1-100> to <4-100> to correct a CLI command implementation
error where the range must be greater than the cm-mode backhop count
<3-10> range. The default setting remains at 15.
Example:
CASA(conf-rule 64)# cm-mode tolerance-count ?
<4-100> default to 15
51843 45b9 New feature. The power-adjustment {continue | threshold} has been
implemented in the interface ofdma configuration context to enable
adjustments to the upstream input power on the OFDMA channel in the ranging
response (RNG-RSP) message to the modem.
• continue <2:15> — The CMTS can be set to continue to adjust the modem
power output during ranging response. If the power offset is within the power
level set by the power-adjustment continue command, the modem is
properly ranged in transmit power. If it is beyond this level, the CMTS
continues to send power adjust messages. The adjustment level is in dBmV;
default is 2.
• threshold <0:2> — The upstream input power threshold determines
whether or not the CMTS will send power adjustments. If the modem
transmits power is within the threshold, the CMTS sends no adjustments.. If
it is beyond the threshold, then it sends a power adjustment. After 16 failed
attempts, the CMTS stops sending ranging and the modem remains offline.
The adjustment level is in dBmV; default is 1.
Example:
CASA(conf-ofdma-channel 12/3.0)# power-adjustment ?
continue margin in dB to consider cable modem
properly ranged
threshold threshold in dB to send power
adjustments in RNG-RSP
CASA(..ofdma-channel 12/3.0)#power-adjustment continue ?

<2-15> power adjust level
CASA(..ofdma-channel 12/3.0)# power-adjustment continue 5
CASA (..ofdma-channel 12/3.0)# power-adjustment threshold ?

CASA (..ofdma-channel 12/3.0)# power-adjustment threshold 2

1-180 Release Notes

version
51855 45b9 New feature. Video on demand (VOD) Table Mode 5 support has been
implemented in Release 7.2. With Table Mode 5, video channel space per QAM
port is sixteen narrowcast channels per port.
The UDP port mapping for this mode is 100qqqqq qqpppppp. The UDP port
range of Table Mode 5 is (10000000 00000001 - 10011111 11111111) (0x8001 -
0x9FFF). The output program number is in the range 1 to 63. Video streams
with a UDP port out of this range will be treated as homeless streams, and no
output will be generated on the RF side.
Example:
CASA(config)# video table ?
mode0 qqqqqqqq qqpppppp
mode1 1qqqqqqq qqqppppp
mode2 1qqqqqqq qqqpppp0
mode3 qqqqqqqq pppppppp
mode4 qqqqqqqq pppppppp,where q starts from 1
mode5 100qqqqq qqpppppp
CASA(config)# video table mode5
Implementation notes:
• If the video channel-id-offset parameter is not configured, the channel x/y/

z to be used for Table Mode 5 ranges from x/y/0 to x/y/15.
• If the video channel-id-offset parameter is configured, the channel ranges
from x/y/offset to x/y/offset+15.
51856 45b9 The following log message was observed indicating that an IPv6 prefix
delegation (PD) route could not be removed from the route table as next-hop
routes were being successfully installed.
[Wed May 11 09:54:40 2016]-ER-ROUTER-0: smm7: NSM: Pthread

[route_install],del ipv6-pd route 888:7690::, lc_num 2 ifindex 174 fail ret -3,
reason No such process
The error message was logged as next-hop routes were being processed
(installed and deleted) in the route table. There was no impact to service. A fix
has been applied to ensure that the message will only be logged in the event of
an actual error condition.


version
51918 45b9 An issue was observed where CPEs could not complete DHCP leasequery
when the cable helper address (with an attached CPE class name) specifies a
secondary host. The software now includes checks to ensure that unconfigured
cable helper addresses used by leasequery are skipped when CPE IPs belong
to a secondary host.
52033 45b9 Under certain conditions, Label Distribution Protocol (LDP) sessions with peer
routers would fail to reconnect after dropping off and being reported in the
NON-EXISTENT state with show mpls ldp neighbor command. The problem
was observed with modems getting stuck in the init(d) state with the CMTS no
longer attaching labels to upstream traffic. A fix has been applied to ensure that
the dropped session has been cleared before the reconnect timer restarts the
LDP session.
52056 45b9 When changing the symbol rate on a video shared channel using the Casa
Video Web interface, the software incorrectly reported the number of affected
unicast channels in the confirmation dialog box. The problem was observed in
the Web interface only; the CLI reported the correct number of channels
affected by the symbol rate change. This issue has been fixed.
52066 45b9 Protections have been applied in the software to guard against packet buffer
overflows when processing Protocol Independent Multicast (PIM) join and prune
message packets. Overflows will now be processed in subsequent packets.
Packet buffer overflow conditions can result in packet loss, connectivity
problems with PIM neighbors, and a possible PIM process deadlock.
52068 45b9 Enhancement. The show l2vpn qam command output now includes the
dhcp-insert option 82 state as enabled (1) or disabled (0).

1-182 Release Notes

version
52121 45b9 Enhancement. The video channel-id-offset range has been increased from
32 to 64 for the QAM 8x96 and QAM 8x192 modules.
Example:
CASA(config)# video channel-id-offset ?
<num> Valid range is from 1, or Nmax-64 if Nmax
is greater than 64 to Nmax-1,
where: Nmax is the largest "module
narrowcast-channels" setting
On the QAM 8x96 (Nmax=48) and QAM 8x192 (Nmax=80):
CASA(config)# video channel-id-offset 32
In the example, the channel-id-offset is set to 32, where channels 0–31 are
reserved for DOCSIS and the remaining 16 channels (32–47) are video
channels for QAM 8x96, or channels 32–79 for QAM 8x192. The remaining
video channels are then numbered 0–15 for QAM 8x96 or 0–47 for QAM 8x192.
On the QAM 8x192 (Nmax=80 narrowcast channels):
channels for the QAM 8x192. The remaining video channels are then numbered
0–15.
52128 45b9 A situation was observed where disconnected modems continued to be
reported as “online” in the show cable modem command output. The problem
was caused by an issue where the CMTS failed to clear the modems from the
upstream process when the modems were physically disconnected. This
problem has been fixed.
52277 45b9 Enhancement. The show interface docsis-mac <number> topology
command now reports the operational state (either UP or DOWN) of the
DOCSIS-MAC interface on the first line of the displayed output.
Example:
CASA# show interface docsis-mac 1 topology
interface docsis-mac 1,AdminStatus: UP

Known problems and restrictions in Release 7.2

The following section describes the known problems and restrictions that remain
under investigation for resolution in an upcoming release.
Possible modem flaps with recovery after editing QAM channels (ID 78669)
After making changes to QAM channel parameters, such as changing an SC-QAM
channel frequency, a situation was observed where some modems would de-register
momentarily and then immediately come back online with the CMTS. Upon
investigation of the problem, certain modems with low tolerance could not tolerate a
brief disturbance across QAM ports affected by a parameter change, which could
cause modems to flap briefly followed by quick recovery. The problem continues to
be investigated for improvements.
Observed error message with in-service patch apply/revert (ID 77833)

The message “himem_free_buf: error : negative ref cnt” has been observed when
applying or reverting an in-service patch to systems running the UPS 16x4 module.
Modems remained online and there was no impact to service. The problem will be
fixed in the next major release.
DVB Simulcrypt over QAM 8x96 shared and narrowcast channels (ID 72651)
Presently, enabling DVB Simulcrypt over QAM 8x96 shared channels or narrowcast
channels above and including 32 may not be reliable in Release 7.2.4.2. A fix for this
issue will be applied in a newer release version.
SNMP process restarts under certain conditions (ID 79183)

Restarting of the SNMP process has been observed under certain conditions with no
impact to service. The root cause has been identified as an uninitialized value being
accessed. The issue will be corrected in a future release.
LDP session establishment issue (ID 77793)

A problem which could result in a failure to correctly set up and establish a session
with an adjacent LDP peer is under investigation. The problem has been observed in
situations where there are multiple LDP adjacencies.

1-184 Release Notes
OFDM channel entries in CLI and SNMP (ID 78054)

OFDM channel status entry details are presently being reported incorrectly with the
CLI show ofdm channel command and in SNMP queries to the SNMP
entPhysicalDescr object in the ENTITY-MIB. The problem will be fixed in an
upcoming release.
QAM 8x192 module restart with switchover (ID 73300)

A logic error could cause a process thread to wait for the memory load request queue
to become empty. Under certain conditions, the wait time would exceed the time to
respond to the keepalive polling, which triggers a QAM8x192 module restart with the
message "failed heartbeat." The problem is under investigation.
RFoG with TaFDM partial service issue (ID 72475)

A packet drop issue in RFoG with TaFDM has been observed. The following settings
for OFDMA channels are recommended to yield the best performance:
upstream map size 3

symbols-per-frame 10
fine-ranging-iuc 64 800000
initial-ranging-iuc 64 800000
Modems reporting OFDM MER decrease (ID 71187)

Some modems are presently reporting decreasing OFDM MER away from the
channel center. The problem is under investigation.
Per-channel and per-port power issue in 2-OFDM mode (ID 72434)

When operating the QAM 8x192 module in the 2-OFDM mode, a per-channel and
per-port power increase of 4 dB has been observed in a situation where only SC QAM
channels 32 to 64 have been enabled. The 4 dB power increase was not observed when
enabling SC QAM channels 0 to 31 only. The problem is under investigation.
QAM module redundancy issue with shared channels enabled (ID 66397)
With QAM 8x192 as the backup module, enabling any shared channels on extended
narrowcast or multi-port shared channels on the QAM8x96 is currently preventing
redundancy switchovers. This includes interactive switchovers with the ha module

<slot> protect command in the CLI, as well as any other condition that would
normally trigger a QAM switchover.
Enabling OFDMA probe may increase error rate (ID 61757)

Enabling pre-equalization on the OFDMA upstream interface may increase the
number correctable error frames over upstream sessions. The problem is under review
and will be fixed in an upcoming release.
QAM configuration modify issue (ID 66408)

On systems where the QAM 8x192 is the standby module for the QAM 8x96, and
with the QAM 8x192 presently in the active state, making parameter changes on the
QAM 8x192 while the QAM 8x96 is rebooting will result in DVB FIFO
UNDERRUN messages, causing the QAM 8x192 to also reboot. Do not make
parameter changes on the QAM8x192 while protecting the QAM8x96 module.
OFDMA upstream channel utilization incorrect (ID 66350)

OFDAM upstream channel utilization is currently being reported in error where the
utilization statistics only reflect the logic channel's throughput and NOT the physical
bandwidth usage. The problem was observed in a TaFDM configuration.
MPLS traffic handling during SMM switchover (ID 59247)

During an SMM switchover to the standby SMM, processing of redirected
MPLS-labeled traffic may result in the message, “smm6: Excessive MPLS packets are
dropped." Ignore the message. There is no impact to service.
Upstream partial-service issue with certain modulation profiles (ID 59187)

Upstream partial-service and unstable SNR has been observed with some cable
modems using certain modulation profiles at frequency 59.3 MHz. The problem is
under investigation.
Single carrier 25 kHz spacing in OFDMA (ID 61617)

Presently, the sc-spacing 25 command in the interface ofdma <slot/port.channel>
configuration is not supported. This capability will be added in a future release.

1-186 Release Notes
Operational information
show datapath-config dhcp-lease-tree command (ID 64537)

A problem was observed where the show datapath-config dhcp-lease-tree command
in the Casa diag mode could possibly return a blank output. The problem could not be
immediately reproduced and is under investigation. There is no impact to service.
This section covers operational issues and limitations associated with the CMTS
hardware and software.
Resolutions to security vulnerabilities addressed in Release 7.2.4.1

Release 7.2.4.1 addresses security concerns. Tracking IDs 71982 and 72145 provide
additional information and have been noted as fixed in Build 54cb, as well as in all
future software images. Casa recommends that you contact your Casa Sales Engineer
to discuss additional security measures to protect the CMTS against possible
incursions.
OpenSSL library updates

To further address security vulnerabilities in ID 72145, encryption algorithm updates
to the OpenSSL library have been applied. OpenSSL Version 1.0.2d is presently
implemented in Release 7.2.4.2.
Note: New authentication keys created in Release 7.2.4.2, or in any release in

which updates have been applied to the OpenSSL library, WILL NOT be
compatible with earlier releases if the software is rolled back. This means that
any new authentication keys WILL NOT decrypt in the roll-back software
version.
Casa recommends that customers alway preserve a copy of the startup-config

file before upgrading to the new release in the event of a possible roll-back.
This will preserve the original authentication keys of the earlier software
version. See the section in this notice, “Preserving the current software image”
for information.

“Broadcast FIFO error” detection

The BCAST FIFO ERROR detection bit is now obsolete.
Extended taps on UPS 16x8 upstream channels

When enabling 24 equalizer taps on a single upstream channel on the UPS 16x8
module using the pre-equalization extended-taps parameter in the interface
upstream configuration, all channels on that upstream port will have the 24 taps
enabled.
Presently, extended-taps is a port-wide feature. The extended taps capability is not

supported on the UPS 16x4 module. Any attempt to configure 24 taps on a UPS 16x4
module WILL NOT be applied and will have no effect.
Example
extended-taps support extended taps (tap equalizer),
default is off
CASA(config-if-ups 13/0.0)# pre-equalization extended-taps
Recommended modulation profile over ATDMA with 64QAM

To optimize the equalizer, Casa recommends the following profile over ATDMA
channels using 64QAM modulation:
request atdma qpsk off 64 0 16 338 0 16 fixed on 1 2048 qpsk0

initial atdma qpsk off 640 5 34 338 0 48 fixed on 1 2048 qpsk0
station atdma qpsk off 640 5 34 338 0 48 fixed on 1 2048 qpsk0
a-short atdma 64qam off 152 12 75 338 6 16 shortened on 1 2048 qpsk1
a-long atdma 64qam off 152 16 220 338 0 16 shortened on 1 2048 qpsk1
ugs atdma 64qam off 152 16 220 338 0 16 shortened on 1 2048 qpsk1
Casa always recommends using QPSK for request, initial, and station maintenance
operations. For ranging operations, QPSK provides the best opportunity to equalize an
unequalized channel.

1-188 Release Notes
Reverting to Release 7.1 (and prior) from Release 7.2

Due to SSH security enhancements implemented in Release 7.2, TACACS MD5
authentication keys used by OSPF and ISIS protocols are not backward compatible if
reverting the CMTS software from Release 7.2 to Release 7.1 and prior releases.
Prior to performing an upgrade to a new R7.2 software image, Casa recommends

copying the existing startup configuration file (prior to R7.2) to a separate file for
future use in situations where reverting to R7.1 (or prior release) may be necessary.
This will allow the system to boot up to the earlier image without having to
reconfigure the software.
Perform the following steps:
1. Before upgrading to a new release, copy the startup-config file to a separate file to
preserve the software image.
Example
CASA# copy nvram startup-config nvram <filename>
2. Perform the software upgrade to R7.2, as covered in the section, “Software update
procedures” in this notice.
3. If a downgrade to R7.1 is necessary, copy the file saved in Step 1 to the
startup-config file.
Example
CASA# copy nvram <filename> nvram startup-config
4. Ensure that the Casa release image for the prior release is present on the system.
5. From the CLI, set the boot device to the prior release image and reboot the system.
Example
CASA# system bootdev nvram <release-image-name>
CASA# system reboot
Note that this is also a general procedure which can be applied to all software releases.

OFDM — QAM 8x192 redundancy limitation (by design)
QAM 8x192 line cards operating in the OFDM two-channel mode will not be
redundancy protected if the QAM 8x192 standby is configured for one OFDM
channel and 64 SC-QAM channels. This also applies in the opposite scenario.
For QAM 8x192 redundancy protection, the standby QAM 8x192 module in
redundant system slot 5 or 8 must be configured as a matching one-channel OFDM or
two-channel OFDM channel scheme.
To redundancy-protect the active QAM card with a non-matching standby QAM card,
interactively configure the standby QAM card to match the active QAM so that both
modules are a matching single-channel OFDM or two-channel OFDM before
performing a switchover.
OFDMA — UPS 16x8 redundancy limitation (by design)
UPS 16x8 line cards operating in the TDMA/OFDMA mixed-mode will not be
redundancy protected if the UPS 16x8 standby is configured as a TDMA single-mode
version. This also applies in the opposite scenario.
For TDMA/OFDMA mixed-mode redundancy protection, the standby UPS 16x8

module in redundant system slot 5 or 8 must be configured as a matching mixed-mode
TDMA/OFDMA UPS 16x8.
To redundancy-protect the active UPS card with a non-matching standby UPS card,
interactively configure the standby UPS card to match the active UPS so that both
modules are a matching single-mode or mixed-mode before performing a switchover.
Enabling DVB Simulcrypt channels

On the QAM 8x96 and QAM 8x192 modules, when enabling DVB Simulcrypt on any
QAM channel within an 8-channel block, all remaining channels within that block are
unavailable as DOCSIS channels. All channels within the block must be DVB
Simulcrypt video channels.
Forwarding of clear multicast traffic

A new behavior change has been introduced to ensure that all dynamic IPTV sessions
will only be allowed if there is a matching classifier defined in the multicast group

1-190 Release Notes
configuration. In the multicast group configuration, specify the group-address prefix

to match the supported multicast session. This is required to enable forwarding of both
clear and encrypted multicast IPTV streams. If not matched, IGMP join/leave packets
will be dropped.
An additional configuration parameter is necessary if encryption is to be applied to a

matching multicast sessions. If an encryption-id is not specified, then traffic is
forwarded as clear multicast.
The following multicast group configuration shows the specified group-address

prefix to match the multicast session. IGMP join sessions matching the
group-address prefix are sent to the SMM; non-matching IGMP join sessions are
dropped. In this example, the encryption-id and qos-id parameters are also specified
to indicate encryption and QOS treatment of the matched multicast session.
Example
multicast group config 1
source-address 0.0.0.0/0
group-address 239.195.0.45/32 <- mimimum requirement
qos-id 1 <- only if QOS treatment is required
encryption-id 1 <- only if this stream requires
encryption
Upstream 16x8 channel width limitation

The UPS 16x8 module does not support channel widths less than 1.6MHz.
QAM replication limit on QAM 8x96 and QAM 8x192

Release 7.1 and later releases have the following QAM replication limits. This
limitation will be cleared in a subsequent software release.
Consider the following parameters to calculate and replicate QAM ports.
Where,
c — Is the number of active downstream QAM channels on a given RF port.

r — Is the number of channels to be replicated.
n — Is the number of RF ports for replication.

For any given port, c, r and n must be provisioned so that the following inequality
holds: (c + r * n /2) <= m, where m is 48 for the QAM 8x96 module and 96 is for the
QAM 8x192 module.
For the QAM 8x96 module
Example: 32 active channels, all of which replicated to another port

Where c = 32, r = 32, and n =1 is a valid configuration.
Example: 32 active channels, 8 of which replicated to 4 other ports

Where c = 32, r = 8, and n =4 is a valid configuration
Example: 32 active channels, 16 of which replicated to 3 other ports:

Where c = 32, r = 16, and n = 3 is NOT a valid configuration.
Casa recommends that replication be spread across all participating ports.
Example: Replicating 32 channels of a port to 3 other ports.

On each port, choose the following configuration: c = 8, r = 8, n = 3.
For QAM 8x192 module
Example: 64 active channels, all of which replicated to another port

Where c = 64, r = 64, and n =1 is a valid configuration.
Example: 64 active channels, 16 of which replicated to 4 other ports

Where c = 64, r = 16, and n =4 is a valid configuration
Example: 64 active channels, 32 of which replicated to 3 other ports:

Where c = 64, r = 32, and n = 3 is NOT a valid configuration.
Casa recommends that replication be spread across all participating ports.
Example: Replicating 64 channels of a port to 3 other ports.

On each port, choose the following configuration: c = 16, r = 16, n = 3.

1-192 Release Notes
Baseline Privacy Interface (BPI) and BPI-plus modems

When the bpi-plus-enforce setting is enabled at the CMTS, BPI cable modems
running DOCSIS 1.1 or higher that are not running BPI-plus will not be able to
register with the CMTS. However, non-BPI cable modems will be allowed to register.
Restricted load balancing groups

A restricted load balancing group MUST be a subset of a cable modem service group.
Otherwise, cable modems will not be able to reliably register with the CMTS.
Rapid Spanning Tree Protocol

The CMTS only supports RSTP as the bridging protocol. RSTP is enabled by default.
When using L2VPN with a redundant configuration, Casa recommends enabling
RSTP on the uplink switch to avoid broadcast loops.
Open Shortest Path First Protocol

After setting the interface OSPF hello-interval timer to a value less than the default
setting, you must also change the dead-interval timer and the transmit-delay timer to
a value that is four-times (4X) the hello-interval setting with a maximum value of
65535. These settings are required to establish adjacency with neighbor OSPF routers.
Example
CASA(config-if-gige 5)# ip ospf hello-interval 100
CASA(config-if-gige 5)# ip ospf dead-interval 400
CASA(config-if-gige 5)# ip ospf transmit-delay 400

Reverting to a prior software release
Reverting to a prior software release

To revert back to an earlier software image, locate the image file in your CMTS
directory and then select the boot device from which the image file will be installed.
Note: When reverting to a prior software release, Casa recommends using

the saved startup-config file from that release. This will allow the system to
boot up to the earlier image without having to reconfigure the software. See
the section in this notice, “Preserving the current software image” for
information on creating this file.
Copy the saved file to the startup-config file.
Example:
CASA# copy nvram <filename> nvram startup-config
Example
To display the current CMTS boot device and software image:
CASA-CMTS# show bootdev

System boot device is: nvram
Boot Image: ccsi.gz.rel7.2.4.2_build59e9
Example
To display the CMTS directory and any previously-installed images, enter the
dir(ectory) command:
CASA-CMTS# dir
total 52192
-rw------- 1 root root 153088000 Feb 04 11:50
ccsi.gz.rel7.1.3.0_build421c
-rw------- 1 root root 187584000 Sep 29 16:56
ccsi.gz.rel7.2.4.2_build59e9
In the above example, there are two software images: 7.1.3.0_build421c and the
current version, 7.2.4.2_build59e9.
Example
To boot the CMTS and load the earlier image (build 421c in this example), specify the
boot device and the image name as it appears in the CMTS directory. Then, issue the
system reboot command.

1-194 Release Notes
SNMP MIB objects and OIDs in Release 7.2
CASA-CMTS# system bootdev nvram ccsi.gz.rel7.1.3.0_build421c

CASA-CMTS# system reboot
SNMP MIB objects and OIDs in Release 7.2

The following Casa MIB objects are included in the Release 7.2 archive file. Entries
in bold text are new in Release 7.2
MIB archive name Identifier
casa OID 1.3.6.1.20858

casa-3K-10K-module OID 1.3.6.1.4.1.20858.10.36
casa-802-Tap-mib OID 1.3.6.1.4.1.20858.10.19
casa-alert-mib OID 1.3.6.1.4.1.20858.10.17
casa-bsod-l2vpn-mib OID 1.3.6.1.4.1.20858.10.102
casa-cable-cmcpe-mib OID 1.3.6.1.4.1.20858.10.12
casa-cable-cmauery-mib OID 1.3.6.1.4.1.20858.10.18
casa-cable-flaplist-mib OID 1.3.6.1.4.1.20858.10.11
casa-copy-running-to-startup-mib OID 1.3.6.1.4.1.20858.10.30
casa-dev-software-mib OID 1.3.6.1.4.1.20858.10.24
casa-docs-ext-mib OID 1.3.6.1.4.1.20858.10.22
casa-entity-ext-mib OID 1.3.6.1.4.1.20858.10.13
casa-fan-mib OID 1.3.6.1.4.1.20858.10.31
casa-gige-management-mib OID 1.3.6.1.4.1.20858.10.25
casa-host-ext-mib OID 1.3.6.1.4.1.20858.10.28
casa-id-mib OID 1.3.6.1.4.1.20858.2
casa-ipdr-mib OID 1.3.6.1.4.1.20858.10.55
casa-ip-trunk-mib OID 1.3.6.1.4.1.20858.10.23
casa-lawful-intercept-mib OID 1.3.6.1.4.1.20858.10.101
casa-log-mib OID 1.3.6.1.4.1.20858.10.16
casa-module-mib OID 1.3.6.1.4.1.20858.10.14
casa-ntp-mib OID 1.3.6.1.4.1.20858.10.29
casa-pim-mib OID 1.3.6.1.4.1.20858.10.60
casa-power-mib OID 1.3.6.1.4.1.20858.10.32
casa-qam-mib OID 1.3.6.1.4.1.20858.10.27
casa-sfp-mib OID 1.3.6.1.4.1.20858.10.37
casa-spectrum-mib OID 1.3.6.1.4.1.20858.10.56
casa-stream-mib OID 1.3.6.1.4.1.20858.10.15
casa-sys-mon-mib OID 1.3.6.1.4.1.20858.10.33
casa-system-mib OID 1.3.6.1.4.1.20858.10.38

SNMP management using the Casa MIBs
casa-video-mib OID 1.3.6.1.4.1.20858.10.103

casa-video-ts-mon-mib OID 1.3.6.1.4.1.20858.10.57
casa-vpws-mib OID 1.3.6.1.4.1.20858.10.58
SNMP management using the Casa MIBs

Both standard and Casa Enterprise MIBs are available from the Casa FTP server at
ftp://support. casa-systems.com in the compressed file named
mibs-rel7242b5861-20170815.tar.
For complete information on using SNMP to configure and monitor the CMTS, refer
to the Casa Systems – SNMP MIBs and Traps Reference.

1-196 Release Notes
Appendix A. CLI changes in Release 7.2

The following table lists the CLI changes which have applied in Releases 7.2.1
through R7.2.4.2. For CLI changes originally introduced in Releases 7.2, see the Casa
Systems – CMTS Release 7.2 Features Guide.
Table 19. CLI additions and changes in Release 7.2
Command name and New or revised CLI description

tracking ID
[no] send udc rules The [no] send udc rules command has been removed from the interface
docsis-mac configuration and is no longer valid. Use the upstream drop
Tracking ID: 32955 classifier command to enable or disable UDCs for cable modems which are
attempting to register with the CMTS MAC domain. A UDC has a set of
matching criteria applied by modems to determine if a packet should be
dropped on the upstream.
video table custom The video table custom command has been introduced in the CLI to allow
users to add new video on demand (VOD) table modes beyond those provided
Tracking ID: 54347 by the Casa configuration (mode0 through mode6). The table is created using
the parameters specified in the command.
• prog-per-channel — Number of programs per QAM channel; 32, 64, or 256

(depending on the QAM module); the default is 64.
• chan-per-port — Number of QAM channels per RF port in the range 1 to
32; the default is 32.
• start-upd-offset — Starting UPD offset; first valid UDP port for the channel
mapping. This is an optional setting with allowed values 1, 33,65, or 257; the
default is 1.
• skip-chan — Number of QAM channels to skip in addressing between two
consecutive ports; This is an optional setting in the range 0 to 12; the default
is 0.
Example:

Table 19. CLI additions and changes in Release 7.2 (continued)

tracking ID
show iftable ofdma The show iftable ofdma command has been implemented in the Casa CLI to
display OFDMA upstream interface details and current status, with up to one
Tracking ID: 54061 OFDMA upstream channel per port.
Example:
CASA# show iftable ofdma
------------------------------------------------
ifIndex: 16000160
ifOperStatus: Up(1)
------------------------------------------------
ifIndex: 16000161
ifOperStatus: Up (1)
proxy-arp unknown The subnet option has been added to the proxy-arp unknown parameter in
subnet the IP bundle address configuration to allow the CMTS to respond to ARP
requests from CPE devices which are outside of the IP bundle address scope.
Tracking ID: 52257 The enhancement addresses situations where CPE devices were not able to
register due to the CMTS not responding to ARP requests from unknown IP
address subnets. The default setting is disabled.
Use the [no] cable proxy-arp unknown subnet command to set the unknown
subnet option globally in the configuration. The IP bundle proxy-arp unknown
subnet setting takes precedent over the global setting. The global setting only
takes effect only when the IP bundle proxy-arp unknown subnet setting is not
configured on an IP bundle subnet.
Example:
CASA(ip-bundle 15)# ip address 6.6.7.7 255.0.0.0 classname
proxy-arp unknown subnet
Example:
CASA(config)# cable proxy-arp unknown subnet

1-198 Release Notes

tracking ID
show spectrum The software has been revised for improved management and presentation of
upstream <slot/ spectrum measurement statistics. A problem was observed where using 200K
port.channel> option in SNMP and CLI queries resulted in a failure to display all statistics due
chan-width <width> to a limitation in the CMTS database.
Tracking ID: 52543 The following SNMP and CLI changes have been applied with this fix to address
the problem:
• The 200K option has been removed from the SNMP

casaSpectrumMeasurementChannelWidth MIB object in the
CASA-SPECTRUM-MIB file. The revised range is 400 kHz to 6400 kHz.
• -The 200000 option has been removed from the show spectrum upstream
The CMTS database now supports up 1024 spectrum measurement data

entries.
show bcm flow-classes The following CLI show commands have been added to the Casa diag mode to
display internal buffer, traffic throughput, and queue usage statistics:
show bcm
congestion-info • show bcm flow-classes
• show bcm congestion-info
show bcm events
• show bcm events
Tracking ID: 53443
Use these commands with the assistance of Casa Technical Support when
diagnosing throughput issues.
Example:
CASA(diag)# show bcm congestion-info
Total Shared Buffer cells: 38427, Total Shared Buffer cells
in use: 0 (0%)
Buffer cells in use: 0 (0%)
Currently Alarmed: No, Alarm Count 0
Cell usage for port 0: input - 0, output - 0, output uc 0,
ing mmu drops 0
PG Shared Usage: 0 0 0 0 0 0 0 0
PG Headroom Usage: 0 0 0 0 0 0 0 0
Multicast Queue Usage: 0 0 0 0 0 0 0 0


tracking ID
channel <number> The channel <number> power-attenuation command setting in the interface
power-attenuation qam <slot>/<port> configuration has been revised to operate over a specified
range of channels per port. Previously, the command operated on a single
Tracking ID: 53781 channel only. The revised command operates with the QAM 8x96 and QAM
8x192 modules on both standard and shared channels.
The number of channels over which the specified power-attenuation value is

applied is in the range 1 to 80, depending on the QAM module in use.
Example: Power attenuation (20dB) over 10 channels starting with channel 0
CASA(config-if-qam 2/0)#channel 0 power-attenuation 20 10
CASA(config-if-qam 2/0)#shared-channel 0 power-attenuation

20 10
channel <id> transport The following channel transport stream ID (TSID) commands now include a
stream id repetition count [<num>] and increment [inc <num>] option when configuring a
TSID range for single carrier and narrowcast shared channels. The repetition
Tracking ID: 31591 count and increment options allow users to configure multiple channel TSIDs
with one command.
Format:
channel <id> transport stream id <tsid> [<num> [inc <num>]]

no channel <id> transport stream id [<num>]
shared-channel <sid> transport stream id <tsid> [<num> [inc

<num>]]
no shared-channel <sid> transport stream id [<num>]
Example:
CASA(config-if-qam 3/0)# ch 0 transport stream id 1 40 inc
2

1-200 Release Notes

tracking ID
show video power-key The show video power-key encrypt-data [session <num>] has been
encrypt-data [session implemented in the Casa diag mode for helping troubleshoot PowerKey
<num> encrypted sessions.
Tracking ID: 48036 Example:

CASA(diag)# show video power-key encrypt-data session 88
Power-Key encryptor data for session 001710035f40 00000088:

streamId(local session id): 4474306
Power-Key session id (to lib): 1
is_encrypted: 1
start_immediate: 1
start_time: 0
ecm_update_period: 100
cw_update_period: 4000
cw_setup_peroid: 450
caDATA[0] typeOfData: 0
caDATA[0] deliveryId: 0
caDATA[0] serialNumber: 0
caDATA[0] caDataLen: 80
caDATA[0] caData:
204e050e 00103900 0e000500 0000017e 21003000

00000000 00000000 00000000
00000000 00000001 00000002 00000003 00000004

00000005 00000006 00000000
20202020 20202020 20202020 20202020

ssh-server gen-hostkey The additional ecdsa and ed25519 encryption algorithm values were added to
the dsa and rsa values for the ssh-server gen-hostkey command in the CLI.
Tracking ID: 48500 This command generates a host key to replace the default one. The key can
now be based on the Digital Signature Algorithm (DSA); Elliptic Curve Digital
Signature Algorithm (ECDSA); Twisted Edwards-curve Digital Signature
Algorithm (EdDSA); or Rivest, Shamir and Adleman (RSA) cryptographic
algorithm. The command is executed in Casa enable mode.
Example:
CASA# ssh-server gen-hostkey ecdsa
CASA# ssh-server gen-hostkey ed25519


tracking ID
show video simulcrypt The following fields have been added to the show video simulcrypt ecmg
ecmg display output.
Tracking ID: 49103 • Access-criteria: <message>

• Stream status: <message>
• ECM status: <message>
show cable modem The show cable modem partial-service and show cable modem bonding
partial-service commands in the CLI have been enhanced to display reason information for
cable modem channels (upstream, downstream, OFDM, and OFDMA) going
show cable modem into the partial service state. The reason types are now listed with the command
bonding and appended to the UD/DS CHANNEL EXCLUDED column values, as follows:
Tracking ID: 49246 • 0 – Unknown

• 1 – MAC domain descriptor (MDD) timeout
• 2 – QAM/FEC lock failure
• 3 – Bad transmit channel configuration (TCC)
• 4 – Bad transmit power
• 5 – Range timeout
• 6 – Next codeword pointer (NCP) profile failure
• 7 – Impaired channel
• 8 – Unreachable channel
• 9 – Ranging failure
Example:
CASA# show cable modem partial-service
Reason code: x/y/z(reason_code)
1 MDD timeout, 2 QAM/FEC lock failure
3 Bad tcc, 4 TR power bad
5 Range timeout, 6 NCP profile failure
7 Impaired channel, 8 Channel unreachable
9 Ranging failure, 0 Unknown
MAC Address MAC US DS US DS US/DS CHAN EXCLUDED

id Intf Intf SET SET
08eb.74bc 63 12/0.0/0 2/0/31 256 257(3*23) 12/0.0w(3)
906e.bbd4 63 12/0.1/0 2/0/31 256 257(3*23) 12/0.0w(3)

1-202 Release Notes

tracking ID
show snmp statistics The show snmp statistics command has been enhanced to display UPD drop
statistics. The snmpCongestionDrops field has been added to the end of the
Tracking ID: 49872 display listing.
CASA#show snmp statistics

SNMP agent statistics
snmpInPkts: 38
snmpOutPkts: 38
snmpInBadVersions: 0
snmpInBadCommunityNames: 0
snmpInBadCommunityUses: 0
snmpInASNParseErrs: 0
snmpInTooBigs: 0
snmpInNoSuchNames: 0
snmpInBadValues: 0
snmpInReadOnlys: 0
snmpInGenErrs: 0
snmpInTotalReqVars: 38
snmpInTotalSetVars: 0
snmpInGetRequests: 0
snmpInGetNexts: 38
snmpInSetRequests: 0
snmpInGetResponses: 0
snmpInTraps: 0
snmpOutTooBigs: 0
snmpOutNoSuchNames: 0
snmpOutBadValues: 0
snmpOutGenErrs: 0
snmpOutGetRequests: 0
snmpOutGetNexts: 0
snmpOutSetRequests: 0
snmpOutGetResponses: 38
snmpOutTraps: 0
snmpEnableAuthenTraps: 1
snmpSilentDrops: 0
snmpProxyDrops: 0
snmpCongestionDrops: 36
show video session The show video session <session-id> command now includes the transport
<session-id> stream ID (TSID) in the listed session creation parameters. Previously, the QAM
channel translation to the output port number was being presented instead of
Tracking ID: 49877 the expected TSID.


tracking ID
console-password The console-password <password> command has been removed from the
<password> Casa CLI. The console-password configuration is now specified with the
adduser command. The existing setting is converted to the new configuration
Tracking ID: 50680 and no reconfiguration is necessary.
CASA# adduser USER1 privilege 15 password Tr3btr3b

show cable modem fail The show cable modem fail counters command has been removed from the
counters CLI and replaced by the show cable modem offline counters command to
display failure results for cable modems that go offline due to failure conditions.
show cable modem The counts reflect conditions resulting from ranging, DHCP, TFTP, CMTS
offline counters registration, Baseline Privacy Interface (BPI), or online backup or expiration.
The clear cable modem offline counters [docsis-mac <1:96>] command
clear cable modem may be used to reset the offline counters associated with a DOCSIS-MAC
offline counters interface.
[docsis-mac <1:96>]
Example:
Tracking ID: 50857 CASA# show cable modem offline counters
1 0 0 0 0
2 0 0 0 0
Total: 0 0 0 0
CASA# clear cable modem offline counters docsis-mac 1

1-204 Release Notes

tracking ID
video qam export The optional base parameter has been added to the video qam export
configuration slot configuration slot command in the CLI to set the output port base. The output
port base is reflected in the outputPortBase parameter in the configuration file
Tracking ID: 50928 and varies by device.
The default base value is 0 for a Casa or Cisco System Resource Manager
(SRM) QAM 8x96 or QAM 8x192, or 1 for a BigBand SRM QAM 8x96 or
QAM 8x192. The slot value can be a comma-separated list. The syntax of the
command is:
CASA# video qam export configuration slot <list>

base {0|1} [filename <file>} [in-service-state]
[srm-num <1:8>]
Example:
CASA# video qam export configuration slot 2,11 base 1
in-service-state filename casa-base1
channel-utilization-thres Subscriber Traffic Management (STM) has been enhanced to monitor interface
hold <0-100> utilization in addition to the currently supported subscriber transmission rates.
STM only manages a subscriber if its transmission rate and the interface
Tracking ID: 51296 utilization both exceed predefined limits in the cable traffic-policy
configuration.



tracking ID
show video simulcrypt Enhancement. The ECMG error codes which can be returned by the ECMG
ecmg protocol when there are session issues between the CMTS and ECMG server
are now included in the system log for troubleshooting purposes.
Tracking ID: 51329
0x0000 DVB Reserved
0x0001 invalid message
0x0002 unsupported protocol version
0x0003 unknown message_type value
0x0004 message too long
0x0005 unknown Super_CAS_id value
0x0006 unknown ECM_channel_id value
0x0007 unknown ECM_stream_id value
0x0008 too many channels on this ECMG
0x0009 too many ECM streams on this channel
0x000A too many ECM streams on this ECMG
0x000B not enough control words to compute ECM
0x000C ECMG out of storage capacity
0x000D ECMG out of computational resources
0x000E unknown parameter_type value
0x000F inconsistent length for DVB parameter
0x0010 missing mandatory DVB parameter
0x0011 invalid value for DVB parameter
0x0012 unknown ECM_id value
0x0013 ECM_channel_id value already in use
0x0014 ECM_stream_id value already in use
0x0015 ECM_id value already in use
0x7000 unknown error
0x7001 unrecoverable error
0x8000 to 0xFFFF ECMG specific/CA system specific/User
defined
interface ip-bundle The maximum number of IPv6 subnets under the interface ip-bundle
configuration configuration has been decreased from 2600 to 256 for improved routing table
performance. The software continues to support up to 2600 IPv4 subnets in the
Tracking ID: 51407 configuration.

1-206 Release Notes

tracking ID
module <number> The Casa diagnostic mode module <number> qam-config-counter reset
qam-config-counter command was added to the Casa CLI to reset the QAM Configuration Compiler
reset (QCC) counters without having to perform a system reboot. Counters requiring
reset are revealed after a configuration change with a message such as
Tracking ID: 51422 Enabled Channels and ref counts don’t check, event_type:
#, when shutting down ports.
The command returns warnings if other than a QAM module is specified and
when not all the QAM ports are shut down. Responding with YES resets the
counters to zero. Ports which are still enabled will show counters as negative
with the show interface qam <slot>/<port> block command. The ports must
be shut down, the command rerun, and the ports re-enabled.
cm-mode The spectrum rule cm-mode tolerance-count parameter range has been
tolerance-count <4-100> revised from <1-100> to <4-100> to correct a CLI command implementation
error where the range must be greater than the cm-mode backhop count
Tracking ID: 51822 <3-10> range. The default setting remains at 15.
Example:
CASA(conf-rule 64)# cm-mode tolerance-count ?
<4-100> default to 15


tracking ID
power-adjustment The power-adjustment {continue | threshold} has been implemented in the

{continue | threshold} interface ofdma configuration context to enable adjustments to the upstream
input power on the OFDMA channel in the ranging response (RNG-RSP)
Tracking ID: 51843 message to the modem.
• continue <2:15> — The CMTS can be set to continue to adjust the modem
power output during ranging response. If the power offset is within the power
level set by the power-adjustment continue command, the modem is
properly ranged in transmit power. If it is beyond this level, the CMTS
continues to send power adjust messages. The adjustment level is in dBmV;
default is 2.
• threshold <0:2> — The upstream input power threshold determines
whether or not the CMTS will send power adjustments. If the modem
transmits power is within the threshold, the CMTS sends no adjustments. If
it is beyond the threshold, then it sends a power adjustment. After 16 failed
attempts, the CMTS stops sending ranging and the modem remains offline.
The adjustment level is in dBmV; default is 1.
Example:
CASA(conf-ofdma-channel 12/3.0)# power-adjustment ?
continue margin in dB to consider cable modem
properly ranged
threshold threshold in dB to send power
adjustments in RNG-RSP
CASA(..ofdma-channel 12/3.0)#power-adjustment continue ?

CASA(..ofdma-channel 12/3.0)# power-adjustment continue 5
CASA (..ofdma-channel 12/3.0)# power-adjustment threshold ?

CASA (..ofdma-channel 12/3.0)# power-adjustment threshold 2
show l2vpn qam The show l2vpn qam command output now includes the dhcp-insert option 82
state as enabled (1) or disabled (0).
Tracking ID: 52068

1-208 Release Notes

tracking ID
video channel-id-offset The video channel-id-offset range has been increased from 32 to 64 for the
QAM 8x96 and QAM 8x192 modules.
Tracking ID: 52121
Example:
CASA(config)# video channel-id-offset ?
<num> Valid range is from 1, or Nmax-64 if Nmax
is greater than 64 to Nmax-1,
where: Nmax is the largest "module
narrowcast-channels" setting
On the QAM 8x96 (Nmax=48) and QAM 8x192 (Nmax=80):
channels for QAM 8x96, or channels 32–79 for QAM 8x192. The remaining
video channels are then numbered 0–15 for QAM 8x96 or 0–47 for QAM 8x192.
On the QAM 8x192 (Nmax=80 narrowcast channels):
channels for the QAM 8x192. The remaining video channels are then numbered
0–15.


tracking ID
cable The cable map-advance-adjust command has been implemented to adjust the
map-advance-adjust MAP lead time globally across all upstream cards to support DOCSIS 3.0 cable
modems which require longer MAP lead times due to cable plant
Tracking ID: 55052 characteristics. The adjustment can be configured in the range -1000 through
5000 microseconds. The default setting is 0.
To override the global setting on a specific upstream interface, use the existing
map-advance parameter in the interface upstream <slot/port> configuration
context.
Example:
CASA(config)# cable map-advance-adjust ?
<-1000-5000> map tx margin in microseconds, default
is 0
CASA(config)# cable map-advance-adjust 500
show interface The show interface docsis-mac <number> topology command now reports
docsis-mac <number> the operational state (either UP or DOWN) of the DOCSIS-MAC interface on the
topology first line of the displayed output.

CASA# show interface docsis-mac 1 topology
interface docsis-mac 1,AdminStatus: UP
initial-tech ofdma The initial-tech ofdma command has been implemented in the interface
docsis-mac configuration to specify the initial ranging technique to be applied
Tracking ID: 53482 when a D3.1 modem is performing upstream ranging over an OFDMA channel.
• broadcast-ranging — TLV 46.7 value 1; default

• probing — TLV 46.7 value 5
• station-ranging — TLV 46.7 value 7
• unicast-ranging — TLV 46.7 value 6:
Example:
CASA(config-if-mac 1)# initial-tech ofdma unicast-ranging

1-210 Release Notes

tracking ID
show interface trunk stat The show interface trunk stat command now reports the trunk interface speed
(IfSpeed) in the command output.
Tracking ID: 55062
Example: Display xGigE interface speed
CASA# show interface trunk stat
Interface Trunk 2 statistics

IfIndex 9000002
interface status UP
link status DOWN
mac address 0017.1003.ba5e
link up member xgige 6/0
IfInOctets 1528431
IfInUcastPkts 0
IfInNUcastPkts 2979
IfInDiscards 2979
IfInErrors 0
IfInOversizePkts 0
IfInUnknownProtos 0
IfOutOctets 768512
IfOutUcastPkts 0
IfOutNUcastPkts 6004
IfOutErrors 0
IfOutDiscards 0
IpForwDatagrams 0
IpInReceives 0
IpInDiscards 0
IfSpeed 10000000000
Last clearing of interface stat: never


tracking ID
show command history The show command history web-gui command has been implemented in the
web-gui Casa CLI to capture management activity processed through the Casa Video
Web interface in the current session. On a line-by-line basis, the output includes
Tracking ID: 54179 the date and time of command execution, the user login of the person who
executed the command, and the GUI command presented in the equivalent CLI
syntax.
Show commands are excluded and do not appear as part of the command
history.
Example:
CASA# show command history web-gui
2016-07-05 16:33:16 <root> shutdown
2016-07-05 16:33:16 <root> no ip pim sparse-mode
2016-07-05 16:33:16 <root> ip address 192.168.5.10
2016-07-05 16:33:16 <root> gige 6/0 mode active
2016-07-05 16:33:16 <root> no vrf forwarding
2016-07-05 16:33:16 <root> no description
2016-07-05 16:33:16 <root> interface trunk 2
2016-07-05 16:33:16 <root> config
2016-07-05 16:32:10 <root> video pat-interval 100
2016-07-05 16:32:10 <root> config
CASA#

1-212 Release Notes

tracking ID
description The description parameter has been implemented under the interface qam
ofdm-channel and interface ofdma configurations to support insertion of
Tracking ID: 55034 OFDM and OFDMA channel descriptions in DHCP packets.
Up to 64 characters may be specified. Surround the description text with

quotation marks (“ “) if the description string contains blank spaces, as shown in
the examples below.
Example: OFDM downstream channel description

C100G(config)# interface qam 2/0
C100G(config-if-qam 2/0)# ofdm-channel 0 description "OFDM
channel on 2/0"
Example: On OFDMA upstream channel description

C100G(conf-ofdma-channel 12/0.0)# description “OFDMA
channel on 12/0.0”
Example: Inserting descriptions into DHCP

CASA(conf-if-mac 4)# dhcp-insert upstream-description
CASA(conf-if-mac 4)# dhcp-insert downstream-description


tracking ID
show ofdm channel The show ofdm channel <slot/port/channel> command has been revised to
include the port-exclusion-band setting in the listed interface qam
Tracking ID: 55067 configuration. Previously, the show ofdm channel <slot/port/channel> detail
command with the extended output had to be used to get the
port-exclusion-band setting.
Example:
CASA# show ofdm channel 2/0/0
interface qam 2/0
ofdm-channel 0 lower-freq 499000000 upper-freq 689000000
plc-freq 592000000
ofdm-channel 0 cyclic-prefix 192
ofdm-channel 0 rolloff-period 64
ofdm-channel 0 interleave 1
ofdm-channel 0 sc-spacing 50
ofdm-channel 0 pilot-scale-factor 48
ofdm-channel 0 ncp-modulation qpsk
no ofdm-channel 0 up-down-trap-enable
ofdm port-exclusion-band 1
ofdm-channel 0 profile 0 1
no ofdm-channel 0 shutdown
CASA#
voice-bw-reserve Existing reserved bandwidth for voice calls functionality has been applied in the
OFDMA interface configuration.
Tracking ID: 55198
Example:
C100G(conf-ofdma-channel 12/0.0)# voice-bw-reserve ?
<0-100> percentage for total call,default is 75 percent
max-calls limit voice band-width by ugs number
C100G(conf-ofdma-channel 12/0.0)# voice-bw-reserve

max-calls 50 emergency 15

1-214 Release Notes

tracking ID
show mpls ftn-table Time stamp statistics have been added to the show mpls ftn-table and the
show mpls forwarding-table command output to support debugging activities.
show mpls Look for the “time” field in the screen display.
forwarding-table
Example:
Tracking ID: 54966 CASA(config)# show mpls forwarding-table
Codes: > - selected FTN, p - stale FTN, B - BGP FTN, K - CLI
FTN, L - LDP FTN, R - RSVP-TE FTN, S - SNMP FTN, I -
IGP-Shortcut, U - unknown FTN
Code FEC Tunnel-id FTN-ID Pri

Nexthop Out-Label Out-Intf time
L> 1.1.1.69/32 0 34 Yes

93.93.93.6 0 xgige7/0 23:45:14
docsis submgt default The DOCSIS subscriber management default filter group ID can now be set to a
maximum of 1024. If not set, the default filter group ID configuration for all
Tracking ID: 55270 upstream and downstream filters is 0.
Example:
CASA(config)# docsis submgt default cm-filter-downstream ?
CASA(config)# docsis submgt default cm-filter-downstream
1024
CASA(config)# show docsis submgt default



tracking ID
docsis submgt default The docsis submgt default max-ipv6-iapd command has been added to the
max-ipv6-iapd subscriber management default configuration to set the default maximum
number of IPv6 prefixes. The configuration range is 0 to 1023. The default
Tracking ID: 55303 setting is 3.
IA_PD stands for Identity Association for Prefix Delegation and is a collection of
prefixes, each with its own ID, assigned to a requesting router.
Example:
C100G(config)# docsis submgt default max-ipv6-iapd ?
C100G(config)# docsis submgt default max-ipv6-iapd 1023
C100G(config)# show docsis submgt default

docsis submgt default active on
docsis submgt default max-ip 16
docsis submgt default max-ipv6-prefix 16
docsis submgt default max-ipv6-iapd 3
docsis submgt default learnable on

1-216 Release Notes

tracking ID
show docsis Enhancement. The show docsis downstream channel utilization output has
downstream channel been revised to properly present the correct column headings when admission
utilization control (Reserved-BW Utilization) and shared channels are enabled.
Tracking ID: 55561 Example: Admission control enabled

Downstream Total-BW Utilization Reserved-BW Online Secondary Channel

Slot/Port/Channel (Mb/Sec) Percentage Utilization Modems Modems Description
------------------------------------------------------------------------------------
2/0/0 (549000000 Hz) 42.9 3 0 1 0

2/0/1 (555000000 Hz) 42.9 0 0 0 2
2/0/2 (561000000 Hz) 42.9 0 0 0 2
2/0/3 (567000000 Hz) 42.9 0 0 0 2
Example: Shared channels enabled

Downstream Total-BW Utilization Online Secondary Channel

Slot/Shared Channel (Mb/Sec) Percentage Modems Modems Description
--------------------------------------------------------------------------------------
1/0 (453000000 Hz) 42.9 0 0 0 (shared)

1/1 (459000000 Hz) 42.9 0 0 0 (shared)
1/2 (465000000 Hz) 42.9 0 0 0 (shared)
1/3 (471000000 Hz) 42.9 0 0 0 (shared)
1/4 (477000000 Hz) 42.9 0 0 0 (shared)
show system monitor A fix has been applied to correct reported temperature threshold inconsistencies
threshold temperature between the Casa CLI show system monitor threshold temperature
command and queries to the SNMP casaSysMonTemperatureState MIB. The
Tracking ID: 55631 show system monitor threshold temperature command output has been
corrected to address misinterpretation of the low threshold and the alert
threshold.
show cable voice The show cable voice summary command now supports OFDMA channels in
summary the command output. OFDMA channels include the “w” character appended to
the <slot/port.channel>identifier.
Tracking ID: 55063
Example: 0/0.1w
shared-channel annex A The Annex A symbol rate has been updated to support the range 5000 to 6999
symbol rate kilo-symbols per second on multi-port shared channels. The default setting is
6952 ks/s.
Tracking ID: 55572
Example:
CASA(config-if-qam 3/0)#shared-channel 0 annex A symbol
rate ?
<5000-6999> Kilo-Symbol per second (default 6952)


tracking ID
show cable ods-report The show cable ods-report ofdm <slot/port/channel> command has been
added to the Casa CLI to display the OPT-RSP message containing Rx MER
Tracking ID: 51743 statistics for 7600 different subcarriers for an OFDM channel with single-carrier
spacing of 25 KHz.
Example:
CASA# show cable ods-report ofdm 11/0/0
6814.01f0.3e47 on ofdm 11/0/0 opt_rsp total_len=7525 - 6
TLV head = 7519 subcarrier
RxMER per Subcarrier:
be bc c1 c2 c0 c0 c3 bd c3 bf ba c2 c2 be
be bd c1 bf bf c3 c0 ba c6 c0 bf bd c1 c3
be be be bd c1 c3 bf c2 c0 c0 bf c2 bd c1
c3 c3 c1 be bc c1 c1 ba c2 c0 bf bf c0 c0
be c1 c1 bc bf c1 c2 be
show cable modem The hash tag # character is now used with the show cable modem output to
<mac-address> verbose indicate the OFDM channel profile ID (PFID) which is unusable due to a DS
OFDM PROFILE FAIL status message and replaced with another OFDM profile.
Tracking ID: 52390 The hash tag indicates the affected profile ID.
Example: Hash tag in OFDM downstream channel set at 11/0/0w, PFID 2.

CASA# show cable modem fe89.2cbc.b0e2 verbose
MAC Address
:fe89.2cbc.b0e2
IP Address :10.66.1.26
MAC Status :online
CM-ID :5
Prim Sid :320
MAC Domain :1
Service-Group :1
Upstream Channel Set :0/0.1/0,
0/0.2/0, 0/0.3/0,0/0.0/0, 0/1.0w
Downstream Channel Set :11/0/
0w(0,3,1,2#), 11/0/1,11/0/2, 11/0/3, 11/0/4, 11/0/5, 11/0/
6, 11/0/7, 11/0/0
Unusable channel list :0/0.0w

1-218 Release Notes

tracking ID
show service group The show service group <name> verbose command output now supports the
<name> verbose inclusion of the configured OFDM and OFDMA channel description strings.

CASA(conf-ofdma-channel 4/12.0)#show service group 2
verbose
service group 2
downstream channel bonding
upstream channel bonding
no upstream rfog-scheduler
qam 13/7/0 657000000 annex B 256qam dmac 2 DOWN aaaaaaa

ofdm 13/7/0 372000000 dmac 2 UP description
ofdma 4/12.0 5000000 20000000 dmac 2 UP description
show mirror The show mirror command has been introduced in the Casa CLI diag mode to
display the current mirror state defined by the mirror cm traffic <ip_address>
Tracking ID: 21131 command.
Example:
CASA# show mirror
Mirroring CM e4.48.c7.b4.a8.cc to host IP 0xc0a8059a
ofdm-channel <number> The configurable lower frequency limit for an OFDM channel has been revised
lower-freq <frequency> to 108000000 Hz. The previous lower frequency range in the CLI was
115400000 to 119600000 Hz.
Tracking ID: 48602
Example:
CASA(config-if-qam 0/0)# ofdm-channel 0 lower-freq ?
<108000000-1196000000> frequency in Hz


tracking ID
show module <slot> The maximum number of QAM modes on QAM 8x196 has been increased from
qam-mode [summary] two to three on a per-port basis to include up to two unicast modes and one
broadcast mode. Only one QAM mode may be applied to an 8-channel block.
Tracking ID: 51448
introduced in the Casa CLI to display detailed QAM mode statistics for all ports.
There can be up to three QAM modes for a QAM 8x192 module, two for unicast
and one for broadcast (the one with the positive ref_cnt). The second broadcast
mode (bc_mode 2) is used only in per channel interleave mode where all the
module channels have the same annex, modulation, and symbol rates, and vary
only between two interleave values.
Example:
Module 1:
Port 0:
admin status: UP
number uchan up: 24
number bchan up: 4
uchan in mode 1: 12
uchan in mode 2: 12
bchan in mode 1: 4
bchan in mode 2: 0
symbol_rate 6952
symbol rate 0

1-220 Release Notes

tracking ID
show run verbose The show run verbose command now displays the default values for various
L2VPN, DHCP, and cable ARP settings.
Tracking ID: 51839
module <slot_num> The following CLI commands have been added to allow users to configure
ofdm-channels number of OFDM channels per QAM 8x192 downstream port.
<num=1:2>
• module <slot_num> ofdm-channels <num=1:2>
show ofdm-channels
• show ofdm-channels [<slot_num>]
[<slot_num>]
Example:
Tracking ID: 53490
CASA(config)# module 1 reboot
CASA(config)# show ofdm-channels ?

| Output modifiers
<cr>
<number> module id
CASA(config)# show ofdm-channels 1

module 1 ofdm-channels 2
For more information, see the section “QAM 8x192 downstream module
enhancements.”


tracking ID
show cable The show cable admission-control interface {ofdm <slot/port/channel> |

admission-control ofdma <slot/port.channel> command has been introduced to in the Casa CLI
interface {ofdm <slot/ to display OFDM or OFDMA bandwidth allocation over each application class.
port/channel> | ofdma
<slot/port.channel> Example:
CASA# show cable admission-control interface ofdma 11/15
Tracking ID: 55556 App-Class Exclusive Non-Exclusive Curr-Resv Curr-Ovrsb
8.1 0 50 0 0
8.2 50 0 0 0
8 50 50 0 0
9.1 0 20 0 0
9 10 10 0 0
CASA# show cable admission-control interface ofdm 0/4/0

1 20 10 0 0
2 10 20 0 0
3 40 10 0 0
system bootfile update The system bootfile update command has been introduced in the Casa CLI to
reduce the time it takes to complete system boot-up. The new command
Tracking ID: 56268 prepares the line card boot image by extracting the necessary files to the CMTS
tftpboot directory prior to performing the actual system reboot. This means that
the system reboot process will be freed from the file extraction process,
reducing the boot-up time.
Example:
CASA# system bootfile update

1-222 Release Notes

tracking ID
system service-delay The system service-delay {snmp <minutes> | tftp-proxy <minutes>}

{snmp <minutes> | command allows users to specify the number of minutes to delay SNMP and
tftp-proxy <minutes>} TFTP processing to shorten system boot-up time and to enable faster modem
registration with the CMTS. The command instructs the CMTS to temporarily
Tracking ID: 56380 block SNMP packets and to delay the TFTP proxy for the configured number of
minutes before the SMM recovers one or both services.
The default setting is 0 (disabled). Specify a number in the range 0 to a

maximum of 60 minutes.
Example:
CASA(config)# system service-delay ?
snmp delay before processing SNMP
tftp-proxy delay before processing TFTP proxy
CASA(config)# system service-delay snmp ?

<num> time in minutes, max delay 60 (default 0)
CASA(config)# system service-delay snmp 40

CASA(config)# system service-delay tftp-proxy 40


tracking ID
pre-equalization Support for selecting the number of upstream pre-equalization taps on the
extended-taps UPS 16x8 module has been implemented in the interface upstream {<slot/
port.channel>} configuration using the pre-equalization extended-taps
Tracking ID: 53416 parameter setting. If not enabled, the default number of taps remains at 16. To
revert to the default setting of 16 taps, apply the no version of the command.
Enabling extended-taps will enable all 24 taps of the equalizer. This could
provide the user with additional immunity to large echo and/or group delay
impairments.
Note: When enabling extended-taps to the 24 taps on a single upstream

channel, then all channels on the upstream port will have the 24 taps enabled.
The extended taps capability is not supported on the UPS 16x4 module.
Example:
extended-taps support extended taps(tap equalizer),
default is off
CASA(config-if-ups 13/0.0)# pre-equalization extended-taps
To revert to the default setting of 16 taps:
CASA(config-if-ups 13/0.0)# no pre-equalization

extended-taps

1-224 Release Notes

tracking ID
[no] cable partial-service The [no] cable partial-service tx-power-deficit command has been
tx-power-deficit introduced in the Casa CLI to enable DBC reduction of the upstream channel
set in situations when modem maximum transmit power lowers due to
Tracking ID: 56448 attenuation changes in the cable plant. This setting is enabled by default so that
modems with adequate transmit power to support upstream channel bonding
are recoverable from a marked partial-service state. Prior to the fix, modems
affected by attenuation changes would DBC to channel 1 and would not be
placed in partial-service for eventual recovery.
Apply the no form of the command to disable this setting.
Example:
CASA(config)# cable partial-service tx-power-deficit
CASA(config)# show running-config | inc deficit
cable partial-service tx-power-deficit
CASA(config)#
show cable modem The show cable modem offline counters command output has been
offline counters enhanced to include the rngfail_R2 and rngfail_RC field columns to distinguish
between R2 and RC cable modem ranging failures.
Tracking ID: 56460
Example:
1 0 0 0 0
2 0 0 0 0
Total: 0 0 0 0
description The maximum length of an route-map name has been increased from 32 to 256
characters in all configuration instances where a named route-map is applied.
Tracking ID: 56505 The route-map description parameter has also been increased from 64
characters to 256 characters.


tracking ID
frequency The upstream interface minimum and maximum edge frequency ranges have
been revised to 15 MHz and 55 MHz respectively for the UPS 16x8 with the
Tracking ID:56777 I/O 32x4 module. The previously supported frequencies did not extend below 16
MHz or above 52 MHz.
Example:
This board does not support higher than 55 MHz frequency.

This board does not support lower than 15 MHz frequency.

show dmesg peer The show dmesg peer command has been introduced in the CLI to display
diagnostic messages associated with the SMM presently in standby status. The
Tracking ID: 57054 command operates in any CLI mode (enable, config, diag).
The show dmesg command presents messages from the boot process in a
controlled manner after the system has started without having to observe the
console output. Even after the system has fully booted, the kernel may
occasionally produce further diagnostic messages which are also captured in
this log. Look for any key words such as Oops, Panic, Warning, or Failure.
subcarrier-group- The OFDMA configurable subcarrier-group-minislot end frequency has been
minislot revised to reflect 400kHz minislots to support eight 50kHz subcarriers for 2k
FFT and sixteen 25kHz subcarriers for 4k FFT. The valid range has been
Tracking ID: 57056 changed to 5400000 to 101000000 Hz; the previous range was 11400000 to
101000000 Hz was determined to be in error.
Example:
CASA(conf-minislot-cfg 30)# subcarrier-group-minislot 1 ?
<5000000-100600000> start frequency
CASA(conf-minislot-cfg 30)# subcarrier-group-minislot 1

5000000 ?
<5400000-101000000> end frequency

1-226 Release Notes

tracking ID
show cable modem The Pmax value has been added to show cable modem verbose command
verbose Pmax value output as part of DOCSIS 3.1. Pmax is the maximum total transmit power that
the cable modem can support. The default and lowest possible value is 65
Tracking ID: 57358 dBmV.
Example:
CASA(config)# show cable modem verbose
…
Reported Max Total Power Output (dBmV) :65.0
Timing Offset :2478
Initial Timing Offset :2478
Received Power :0 dBmV
…
[no] mirror cm traffic The [no] mirror cm traffic <ip_address> in the Casa diag mode has been
<ip_address> enhanced with the loopback option to specify the loopback interface number as
the source IP address for traffic mirrored to a destination IP. Specify the existing
Tracking ID: 57363 loopback interface number in the range 0 to 255. Apply the no version of the
command to remove the current setting.
Example:
CASA(diag)# mirror cm traffic 192.168.8.8 ?
<cr>
<mac_addr> xxxx.xxxx.xxxx. mac addr of cm
loopback loopback interface name for source address
CASA(diag)# mirror cm traffic 192.168.8.8 loopback 0


tracking ID
[no] snmp trap logging The [no] snmp trap logging video alarm {bitrate-threshold <number>|
video alarm missing pat-pmt-pid} command has been implemented in the Casa CLI.
{bitrate-threshold
<number>| missing The bitrate-threshold parameter sets the bitrate per second (bps) low
pat-pmt-pid} threshold in which an SNMP trap will be generated if the detected rate is below
the configured value. The missing pat-pmt-pid parameter forces an SNMP
Tracking ID: 57673 trap message if any of the required video elements (PAT, PMT, or PID) is
missing from the video session stream. Apply the no form of the command to
cancel the current setting.
Example:
bitrate-threshold ?
<0-4294967295> bitrate(bps)
bitrate-threshold 1000
CASA(config)# snmp trap logging video alarm missing

pat-pmt-pid

1-228 Release Notes

tracking ID
show cable modem OFDMA Upstream Data Profile (OUDP) Interval Usage Code (IUC) changes for
<mac-address> verbose the Upstream Channel Set now allow the ability to send a dynamic bonding
change (DBC) of a changing IUC set to the modem and use multiple IUCs for
Tracking ID: 58971 secondary bonding of OFDMA channels in the IUC profile (iuc-profile).
Changes are now reported in the show cable modem <mac-address> ver-
bose command output. IUCs (up to two) are reported in parentheses, with the
leftmost value reflecting the IUC presently in use. IUC 13 will always be present
as the default.
Example:
CASA(config)# show cable modem 6814.01f0.3e47 verbose
MAC Address :6814.01f0.3e47
IP Address :10.64.1.158
MAC Status :online
CM-ID :1
Prim Sid :11
MAC Domain :2
Service-Group :G1
Upstream Channel Set :12/0.0/0, 12/0.1/0, 12/0.2/0,
12/0.3/0, 12/0.0w(10,13)
Downstream Channel Set :1/0/29, 1/0/1, 1/0/2, 1/0/3,
1/0/4, 1/0/5, 1/0/6, 1/0/7,
1/0/8, 1/0/9, 1/0/10, 1/0/11,
1/0/12, 1/0/13, 1/0/14,
1/0/15, 1/0/16, 1/0/17,
1/0/18, 1/0/19, 1/0/20,
1/0/21, 1/0/22, 1/0/23,
1/0/24, 1/0/25, 1/0/26,
1/0/27, 1/0/28, 1/0/0, 1/0/30,
1/0/31
Unusable channel list :
Upstream Channel :12/0.0/0 12/0.1/0
12/0.2/0 12/0.3/0 12/0.0w
Ranging Status :RNG_SUCCESS RNG_SUCCESS
RNG_SUCCESS RNG_SUCCESS
RNG_SUCCESS


tracking ID
[no] cable spectrum Log messages associated with Casa Spectrum Management (CSM) modulation
syslog hopping have been revised with a severity level of INFORMATIONAL.(6).
Previously, the modulation hopping messages were logged at the DEBUGGING
Tracking ID: 58980 (7) severity level.
The [no] cable spectrum syslog command has been introduced in the Casa
CLI to enable and disable logging of CSM messages. When enabled, syslog
messages will be sent to the configured syslog hosts.
Example:
CASA(config)# cable spectrum syslog
show spectrum The 200K option has been reinstated to the SNMP
upstream <slot/ casaSpectrumMeasurementChannelWidth MIB object in the
port.channel> CASA-SPECTRUM-MIB file. The revised range is 200 kHz to 6400 kHz.
chan-width <width>
The 200000 option has been added back to the show spectrum upstream
Tracking ID: 59157 <slot/port.channel> chan-width <width> command. The revised range is 200
kHz to 6400 kHz.
show upstream fec Forward Error Correction (FEC) results can now be derived specifically for
ofdma <slot>/ OFDMA upstream channels in the Casa CLI using the show upstream fec
<port>.<chan> ofdma <slot>/<port>.<chan> command. The upstream FEC counters can also
be cleared specifically for OFDMA channels using the clear upstream fec
Tracking ID: 59358 counters ofdma <slot>/<port>.<chan> command.
Example:
CASA(config)# show upstream fec ofdma 12/0.0
US chan frequency status cFEC uFEC
12/0.0w - UP 2226783 1565
CASA# clear upstream fec counters ofdma 12/0.0

1-230 Release Notes

tracking ID
show cable modem The downstream OFDM channel power now appears in show cable modem
remote-query remote-query [immediate] command output. It was previously omitted if the
[immediate] OFDM channel was the first channel bonded.

CASA(config)# show cable modem 6814.01f0.3ea1 remote-query
ofdm 12/3/0
MAC Address IP Address
S/N US DS TX Time Micro(dB) Modem
Ratio Power Power Offset Reflection State
6814.01f0.3ea1 0.0.0.0
-- 34.3 7.4 2704 -- online(pt)
2001:0:168:24:e885:c04:f3a0:1a93
video table custom The start-udp-offset parameter of the video table custom prog-per-chan
prog-per-chan <number> setting in the Casa CLI has been changed from a fixed sequence of
<number> values to the range <1:65535>.
start-udp-offset
Example:
Tracking ID: 59696 CASA(config)# video table custom prog-per-chan 64
debug cable igmp The debug cable igmp command has been introduced in the Casa CLI to log
Internet Group Management Protocol (IGMP) event messages.
Tracking ID: 59934
Example:
CASA# debug cable igmp


tracking ID
debug config qam flag The cumulative debug levels from 5 through 7 were added to the debug config
qam flag command in diagnostic mode. The modes currently are defined as:
Tracking ID: 60141
• 0 – All off
• 1 – Debug
• 2 – BQAM
• 3 – QCC
• 4 – Mode
• 5 – Power
• 6 – DVB
• 7 – All on
Example:
CASA(diag)# debug config qam flag 7
CASA(diag)# show debug config qam flag
Qam config debug flag:
debug_flag=1
debug_bqam=1
debug_qcc=1
debug_mode=1
debug_power=1
debug_dvb=1
dsg tunnel-group The maximum number of channels per DSG tunnel-group has been increased
to 2560 with a maximum of 5120 DSG channels across all tunnel groups system
Tracking ID: 60348 wide. Previously, the software supported up to 1280 DSG channels per
Example:
reached: 5120 ! !
standby SMM warning The message "This is the standby SMM. Please log into the system from the
active SMM!" will now be presented if a newly configured user with level 0 to 14
Tracking ID: 60569 access privileges attempts to login over the console port at the SMM standby.
Console logins to the system are only supported at the active SMM.

1-232 Release Notes

tracking ID
video interfaces on Up to sixteen video interfaces (1 to 16) can now be configured on a single GigE
Gige/XGigE ports or xGigE port, with each port having a unique IP address. The previously
increased supported number of video interfaces per port was four.

CASA(config)# show interface video
interface video 1
ip address 192.168.18.200 255.255.255.0
ip igmp
input-port-id 1
bandwidth 10000000
gige 6/0
.
.
interface video 16
ip address 192.168.18.215 255.255.255.0
ip igmp
input-port-id 1
bandwidth 10000000
gige 6/0


tracking ID
show multicast client The show multicast client stat command was added in the Casa CLI to dis-
stat play multicast client statistics, including forwarded, filtered and dropped reports,
and rate limit drops.
show multicast client
summary The show multicast client summary command was also enhanced with IGMP
statistics, including total joins and the number of total reports for IPv4 and IPv6.
Tracking ID: 60896
Example:
CASA(config)# show multicast client stat
|Forwarded Reports |Filtered Reports
module|total |rate/min |acl |submgt
3 |67 |10 |4 |0
|Dropped Reports
|group mismatch |invalid
|3 |13
|Rate Limit Drops
|per cm |per module
|16 |13
…
CASA(config)# show multicast client summary

MD Static/Dynamic Last Reporter Multicast Session
1 0 /2 10.94.0.180 <226.94.2.0, 0.0.0.0>
1 0 /2 10.94.0.180 <226.94.2.1, 0.0.0.0>
…
MD Total Joins (v4/v6) Active Groups (v4/v6) Total
Reports (v4/v6) Rate/Min (v4/v6)
1 2/0 2/0
3 1/1 1/1
…

1-234 Release Notes

tracking ID
video edis The output-port-base <0 |1> parameter has been added to the video edis
output-port-base <0-1> configuration to provide an additional channel offset of 1 for interoperability with
the Cisco SRM Explorer ControllerTM for QAM setup and creation of VOD
Tracking ID: 61022 sessions. The default setting if not configured remains at 0.
Example:
CASA(conf-video-edis 1)# output-port-base ?
<0-1> 0 or 1 base. Default is 0
To revert to the default setting:


tracking ID
show downstream The QAM 8x192 module with two OFDM channels now allows pre-binded
channel set: narrowcast narrowcast DOCSIS channels in the shared channel range 32–63 as secondary
shared channels channels. These channels can be configured on the DOCSIS MAC interface as
downstream secondary channels, and added as QAM interfaces in service
Tracking ID: 61048 groups.
The show downstream channel set command has also been modified to
show the narrowcast shared channels.
Example:
CASA(conf-if-mac 33)# show this
…
ip bundle 1
…
CASA# show downstream channel set mac-domain 33

MAC Chan Channel
ID Set List
…
33 9 1/0/32
33 10 1/0/33
33 11 1/0/34
33 12 1/0/35
33 13 1/0/36
33 14 1/0/37
33 15 1/0/38
33 16 1/0/39
33 20 1/0/1w

1-236 Release Notes

tracking ID
video simulcrypt eis vrf After configuring the Event Information Scheduler (EIS) under a VRF instance
<vrfname> with the video simulcrypt eis vrf <vrfname> command, a timing overlap
between de-registration and re-initialization of the SimulCrypt process caused
Tracking ID: 61347 an SMM switchover to occur.
In situations where the SimulCrypt process requires a restart, a timing delay has
been implemented to ensure that the active SimulCrypt process is properly
terminated before being restarted.
service group: ofdm: The Radio Frequency over Glass (RFoG) scheduler, defined in DOCSIS3.1 has
upstream rfog-scheduler been updated to support OFDMA channels.The RFoG scheduler allocates the
upstream spectrum for modem upstream transmissions to ensure that time slots
Tracking ID: 61486 do not overlap if these modems are on the same optical fiber. RFoG mode is
enabled or disabled on a per service group basis.
Example:
CASA(config)# service group SVGP
CASA(conf-svc-grp SVGP)# ofdm 11/1.0
CASA(conf-svc-grp SVGP)# upstream rfog-scheduler
show cable modem The show cable modem [<mac_addr>] verbose command has been
[<mac_addr>] verbose: enhanced in the Casa CLI to include the current OFDMA data IUCs (up to two)
OFDMA data IUCs for each channel in the Upstream Channel Set listing. With multiple IUCs, the
active one is listed first.
Tracking ID: 61742
Example:
CASA# show cable modem verbose | include "Upstream Channel
Set"
Upstream Channel Set :12/2.0w(5,13), 12/0.0w(13)


tracking ID
[no] module <number> The module <number> channel-id-offset command has been introduced in
channel-id-offset the Casa CLI to provide module-specific implementation and override of the
video channel-id-offset command, which excludes DOCSIS channels from the
Tracking ID: 61925 video channel numbering space.
Channel numbering begins following the offset, where the first video channel
begins at 0. The offset value depends on the largest of the module
narrowcast-channels <id> narrowcast-channels <number> settings.
Syntax:
[no] module <id> channel-id-offset <1:63>
Example:
CASA(config)# module 11 channel-id-offset 40
CASA(config)# show channel-id-offset
video channel-id-offset 44
module 0 channel-id-offset 40
show video simulcrypt The “Server Last Time Up” statistics reported with the show video simulcrypt
ecmg: Server Last Time ecmg command has been corrected to display the time since the ECMG was
last disconnected. Previously, the reported time was the connection uptime with
Tracking ID: 62039 the ECMG.
Example:
CASA(config)# show video simulcrypt ecmg
Encryption Period : 30
…
ECMG yli1:
…
Stream Information:
Stream ID Stream ECM ID CP number Status
--------- ------------- --------- ------
1 0 N/A Active
Server Last Time Up : Fri Oct 21 13:34:09 2016
EDIS SRM Output Port The Casa Web UI has been enhanced to include the Output Port Base column
Base and parameter for the EDIS SRM video configuration. Output port base 0 is
used by Casa or Cisco SRM by default, while output port base 1 is used by
Tracking ID: 62154 BigBand SRM.

1-238 Release Notes

tracking ID
ACL support increased The maximum number of supported access control lists (ACLs) and route maps
per system has been increased from 32 to 128.
Tracking ID: 62337
system nms Network Management System (NMS) requests are now “green-lighted” in the
<ip_address> Casa Video Web UI without the need for Video Web UI credentials. Up to eight
NMS servers can be configured at the CMTS.
show system nms
The NMS requests are honored if they are set up through the system nms
Tracking ID: 62410 <ip_address> command. Requests appear in the show system nms
command output.
Example:
CASA# show system nms
---------------------------------------------------------
ping docsis The ping docsis command in the Casa CLI has been enhanced to support
pinging a selected upstream bonded channel. The command previously allowed
Tracking ID: 62481 pinging IPv4, IPv6, and MAC addresses for upstream channels with the option
to specify the number of pings and verbose output. OFDMA channels are now
included.
Example:
CASA# ping docsis 0895.2a9b.2a99 ofdma 12/2.0 3 verbose
PING DOCSIS 0895.2a9b.2a99 on ofdma 12/2.0w
p-offset=1, f-offset=0, t-offset=0
--- 0895.2a9b.2a99 ping docsis statistics ---
3 station maintenance scheduled, 3 RNG-REQ received 100%
success


tracking ID
ofdm profile-modulation The ofdm profile-modulation <type> rxmer threshold command has been
<type> rxmer threshold enhanced with the percentage parameter to set the MER percentage offset
from the threshold value to prevent bad subcarriers from disqualifying a modula-
Tracking ID: 62617 tion profile.
The default percentage setting is 90 in the range 0 to 100.
Example:
CASA(conf-ofdm-profile 1)# profile-modulation 256qam rxmer
threshold 190 percentage 90
system nms The Network Management System (NMS) server CCAP monitoring feature has
<ip_address> [port been introduced in the Casa CLI with the system nms <ip_address> [port
<1:65535>] [heartbeat <1:65535>] [heartbeat <1:3600>] [notifyURL <url>] command. The CMTS will
<1:3600>] [notifyURL send the NMS server any event notifications reported by the show alarm
<url>] command and notifications in the /tmp/snmptraplog.gui file. The NMS server
reports event levels CRITICAL, ALARM, WARNING, and INFO.
Tracking ID: 62698
Up to eight NMS servers can be configured for the CMTS. The no form of the
command removes an NMS server connection.
The show system nms command displays the NMS settings.
The port number (default 8080), heartbeat (default 60 seconds), and

notifyURL (default /nms-web-ui/api/notification) parameters are optional.
Example:
CASA(conf)# system nms 172.0.1.163 port 8080 heartbeat 60
notifyUrl /nms-web-ui/api/notification
CASA(conf)# no system nms 172.0.1.163
CASA(conf)#

1-240 Release Notes

tracking ID
debug cable The debug cable pre-equalization command has been added in the Casa CLI
pre-equalization enable mode to display the pre-equalization coefficients sent to cable modems
over non-OFDM channels.
Tracking ID: 63037
Example:
CASA# debug cable mac-address 0895.2a9b.2a99
CASA# debug cable pre-equalization
Cable:
mac-address: 0895.2a9b.2a99
…
pre-equalization
6PE in BGP Support has been added for IPv6 Provider Edge Routers (6PE) in BGP routes
as defined in RFC4698. 6PE routers are dual stack in order to connect to IPv6
Tracking ID: 64151 islands and to the MPLS core, which is only required to run IPv4 MPLS. The
6PE routers exchange the IPv6 reachability information transparently over the
core using the Multiprotocol Border Gateway Protocol (MP-BGP) over IPv4.
The implementation allows for a single 6PE Autonomous System (AS) and
supports prefix delegation for IPv6 address assignment.

show ip bgp neighbors A.B.C.D


tracking ID
NetFlow monitoring The following commands have been added to support NetFlow monitoring:
Tracking ID: 64452 • [no] flow exporter-map <name> — Source loopback and destination
addresses and port definitions, template timeouts, and transport definitions,
with accompanying show command.
• [no] flow monitor-map <name> — Protocol, exporter name, and cache
timeout definitions, with accompanying show command.
• [no] flow sampler-map <name> — Sampler rate definition, minimum one
per thousand packets, default 1024, maximum 10000 packets, with
flow ingress and flow egress definitions applied to the IP bundle interface.
[no] packetcable gate The [no] packetcable gate maxcount <1:196607> setting has been added to
maxcount the Casa CLI to set the maximum gate count per chassis for PacketCable,
PCMM multicast, and PCMM unicast sessions. The default maximum is 30% of
Tracking ID: 64638 cable modem count, as indicated in the CLI below.
In addition to the maximum number of PacketCable and PCMM gates to 192K,

the maximum number of IGMP clients has also been increased to 192K.
Example:
CASA(config)# packetcable gate maxcount ?
<1-196607> gate count,default is cm_num*3/
10,Warning: This command may free
all current gates

1-242 Release Notes

tracking ID
BGP router The BGP router address-family ipv6 labeled-unicast command in the Casa
address-family ipv6 CLI has been extended to include additional neighbor functions.
labeled-unicast
neighbor Example:
CASA(config-router-bgp)# address-family ipv6 labeled-uni-
Tracking ID: 64685 cast
CASA(config-router-af)# neighbor 114_by_243_244 ?
activate Enable the Address Family for this
Neighbor
allowas-in Accept as-path with my AS present in
it
attribute-unchanged BGP attribute is propagated unchanged
to this neighbor
distribute-list Filter updates to/from this neighbor
filter-list Establish BGP filters
maximum-prefix Maximum number of prefix accept from
this peer
next-hop-self Disable the next hop calculation for
this neighbor
prefix-list Filter updates to/from this neighbor
remove-private-AS Remove private AS number from
outbound updates
route-map Apply route map to neighbor
send-community Send Community attribute to this
neighbor
weight Set default weight for routes from
this neighbor
video edis The on-failover option has been added to the reset-indication parameter in
reset-indication the video edis configuration context to enable the CCAP to send a reset indica-
on-failover tion to the EC at the time of an SMM switchover. The reset indication informs
the EC to reestablish the TCP connection with the CCAP so that video session
Tracking ID: 65080 establishment is resumed.
Example:
CASA(conf-video-edis 6)# reset-indication on-failure


tracking ID
[no] address-family ipv4 The [no] address-family ipv4 mvpn property has been removed from BGP
mvpn command and VRF configurations due to MVPN being disabled. The Multicast Distribution
removed Tree (MDT) configuration has been was retained.

CASA(config-router-bgp)# address-family ipv4 ?
Multicast VPN
CASA(config-router-bgp)# no address-family ipv4 ?
Multicast VPN
CASA(config)# ip vrf City-GZ ?

CASA(config-vrf)# multicast-routing
CASA(conf-vrf-mcast)# address-family ipv4 ?
Multicast VPN
CASA(conf-vrf-mcast)# no address-family ipv4 ?
Multicast VPN

1-244 Release Notes

tracking ID
show ipv6 bgp The show ipv6 bgp labeled-unicast neighbors <ipv6> advertised-routes
labeled-unicast command has been introduced in the Casa CLI to identify BGP-advertised
neighbors <ipv6> routes for IPv6 neighbors.
advertised-routes
Example:
Tracking ID: 65476 CASA(config-router-af)# show ipv6 bgp labeled-unicast
neighbors 177.177.177.79 advertised-routes
BGP table version is 2, local router ID is 177.177.177.106
Status codes: s suppressed, d damped, h history, * valid, >
best, i - internal Origin codes: i - IGP, e - EGP, ? -
incomplete
Network Next Hop Metric LocPrf Weight Path

*>i 177::177:54:1/128
::ffff:b1b1:b16a 0 100 0 65535 ?
*>i 177::177:54:2/128
::ffff:b1b1:b16a 0 100 0 65535 ?
*>i 177::177:54:3/128
::ffff:b1b1:b16a 0 100 0 65535 ?
*>i 177::177:106:1/128
::ffff:b1b1:b16a 0 100 32768 ?
*>i 177::177:106:2/128
::ffff:b1b1:b16a 0 100 32768 ?
*>i 177::177:106:3/128
::ffff:b1b1:b16a 0 100 32768 ?
Total number of prefixes 6


tracking ID
show interface qam The show interface qam <slot>/<port> block command has been enhanced
<slot>/<port> block in the Casa CLI to display the FPGA channel mapping for shared channels. The
output shows the FPGA ID and the channel ID in parentheses at the end of
Tracking ID: 66093 shared channel line entries.
Example:
CASA# show interface qam 1/0 block
QCC_MODULE_INFO:
uc_mode 1: mid 1 annex A mod 256qam intlv 12 symb 6952
ref_cnt 128
uc_mode 2: mid 2 annex B mod 256qam intlv 128x1 symb 0
ref_cnt 64
bc_mode 1: mid 3 annex A mod 256qam intlv 12 symb 6952
ref_cnt 20
…
block 3 freq 866000000 mask 00001fef mode_id 3 in_used 1
…
shared-channel 0 freq 906000000 blk 3 off 5 mid 1 annex
A mod 256qam intlv 12 sym 6952 dvb 0 act 2 sta_m 0x21 ch 76
sch 0 (10,0)
…

1-246 Release Notes

tracking ID
debug ddm mcast The debug ddm mcast syslog command has been added in the Casa CLI
syslog enable mode to control logging of multicast error messages to the system
non-volatile log file. When enabled, the multicast debug messages are sent to
Tracking ID: 66150 CASALOG, which are then directed to the system (console) and/or non-volatile
log file (on flash disk).
This enhancement is disabled by default. When disabled, all multicast logging

messages are sent to the /tmp/multicast_log file only.
Example:
CASA# debug ddm mcast ?
<cr>
dbc dbc debugging info
detail detailed debugging info
error error level debugging
igmp igmp level debugging
syslog send debugging messages to local system log
trace trace the path
CASA# debug ddm mcast syslog

send debugging messages to local system log ONLY


tracking ID
show system detail The CLI show system detail command now displays the Major and Minor
revision information for installed system modules in both the enable and diag
Tracking ID: 66224 modes.
Note: Modules of earlier manufacture may not have the revision information
programmed into the module and the revision information will not presented in
the display.
Example:
CASA(config)# show system detail
Product: C10G, System Uptime:0 d, 8 h, 28 m, 15 s
System Time: Thu Jan 26 11:35:11 UTC 2017
128MHz, 5 PPM Crystal Clock
Module 6, Master SMM_2x10G, Status ACTIVE

Major rev 1, Minor rev 0
Serial_No: SB14BA7S0299 Part_No: PCA-0037-01
CFE version 12.4.11
Uptime: 0 d, 8 h, 28 m, 15 s
show spectrum The show spectrum upstream <slot>/<port>.<chan> chan-width command
upstream <slot>/ now includes the previously missing 200000 Hz channel width value as defined
<port>.<chan> in the CASA-SPECTRUM-MIB casaSpectrumMeasurementChannelWidth
chan-width object.

CASA# show spectrum upstream 13/0 chan-width ?
<200000|400000|800000|1600000|3200000|6400000> channel
width value

1-248 Release Notes

tracking ID
[no] l2vpn The [no] l2vpn local-traffic-forwarding and [no] l2vpn

local-traffic-forwarding mac-address-movable commands have been reinstated in the Casa CLI to
enhance local forwarding of L2VPN MPLS packets.
[no] l2vpn
mac-address-movable • The local-traffic-forwarding property allows local traffic forwarding to local
addresses.
Tracking ID: 67611
• The mac-address-movable property allows location changes for MAC
addresses attached to the L2VPN.
The two properties had been applied to the interface vlan configuration and to
the global L2VPN setting, which takes precedence over the interface vlan
configuration.
Example:
CASA(config)# l2vpn local-traffic-forwarding
CASA(config)# l2vpn mac-address-movable
CASA(conf-if-vlan 1)# l2vpn local-traffic-forwarding

CASA(conf-if-vlan 1)# l2vpn mac-address-movable


tracking ID
interface ofdma The symbols-per-frame command has been added to Casa CLI in the
symbols-per-frame interface ofdma configuration context to warn users if the configured symbol
per frame or number of init/fine ranging subcarriers is too small.
Tracking ID: 69633
The following recommended OFDMA ranging slot settings are based on symbol
rate. Ranging slots settings in number of subcarriers can be changed in ofdma
iuc profile.
Note that the number of fine ranging carriers larger than 64 not be used as it
may cause fine ranging failures. This also means symbol per frame number less
than 10 should NOT be used.
Recommended settings:
Symbol Initial Fine

per frame Ranging Ranging
6 64 192
7 64 192
8 64 96
9 64 96
10 64 64
11 64 64
12 32 64
13 32 64
14 32 64
15 32 64
16 32 32
Example:
symbol per frame 6 requires at least 16 initial ranging
minislots in IUC profile
warning: symbol per frame is too small

1-250 Release Notes

tracking ID
cable modem deny The cable modem deny list capacity has been increased to 2048 cable modem
MAC address entries. Previously, the maximum number of supported entries in
Tracking ID: 69673 the list was 512. The cable modem deny command specifies the MAC address
of a cable modem which is prohibited from registering with the CMTS.
Example:
set black cm to database failed!
CASA(config)#
CASA(config)# show running-config | count-only "modem deny"

Wed Mar 8 03:59:58 UTC 2017
Count Line: 2048
CASA(config)#
packetcable multiple Support has been implemented to enable PacketCable and PCMM to run over
VRF instances multiple VRF instances. Previously, the CLI would only allow one VRF instance
to handle all PacketCable and PCMM connections. Multiple named VRFs can
Tracking ID: 69831 now be created under the packetcable configuration in the CLI to allow users to
separate voice and PCMM multicast traffic.
partial service timing A timing delay has been applied when recovering channels in partial service to
delay prevent modems from reporting CM-STATUS failure/recovery events. The
partial service update now occurs after the CM-STATUS message indicates a
Tracking ID: 69837 recovery.
If the modem reports a failure across all profiles on an OFDM channel, the
channel is now marked as unusable instead of using Profile A.


tracking ID
show bonding-group The show bonding-group utilization command now provides the application
utilization class child identifier in the App-Class-Id column. Child IDs are in the format #.#,
as shown in the partial sample output below:
Tracking ID: 70888
Example:
CMTS(config)# show bonding-group utilization
Mac GroupID App-Class-Id Total BW(kbps) Used BW(kbps).
2 - 1.1 102865 0 0
2 - 1.2 102865 0 0
2 - 1.3 102865 0 0
2 - 1 102865 0 0
packetcable cops The number of supported PacketCable COPS servers has been increased from
servers increased to 128 64 to a maximum of 128.
Tracking ID: 71196

1-252 Release Notes

tracking ID
show cpuinfo module The show cpuinfo module <number> command has been revised to retrieve
<number> QAM or UPS utilization statistics for all CPU processes running on the specified
line card. CPU utilization statistics are reported as minimum, average, and
Tracking ID: 77227 maximum percentages.
The equivalent objects in the CASA-ENTITY-EXT-MIB are:
• casaModuleDataCpuUtilizationTable
• casaModuleDataCpuUtilizationEntry
• casaModuleDataCpuUtilizationMin
• casaModuleDataCpuUtilizationAvg
• casaModuleDataCpuUtilizationMax
Example:
CASA> show cpuinfo module 12
Module 12:
cpu model XLS616 Rev B1 V0.3
BogoMIPS 134.52
microsecond timers yes
tlb_entries 64
00:45:15 up 2 days, 5:26, 0 users, load average: 16.18,

16.13, 16.09
115 processes: 114 sleeping, 1 running, 0 zombie, 0 stopped
CPU states: 0.0% user, 0.4% system, 0.0% nice, 99.6%
idle
D-CPU utilization(Min/Avg/Max) (13%/68%/95%)
Mem: 949336K total, 434516K used, 514820K free,
82772K buffers
cable-helper-ipv6-addre The dva parameter has been added to the interface ip-bundle
ss <mac_addr> dva cable-helper-ipv6-address command to enable forwarding Digital Voice
Adapter (DVA) broadcasts only.
Tracking ID: 77575
DHCPv6 packets which contain device type suboption(2) EDVA or EMTA device
will be forwarded to specified server, if present.
Example:
CASA(ip-bundle 1.1)# cable helper-ipv6-address
2001:20:158::6 dva


tracking ID
interface qam channel The maximum number of supported DSG vendor parameter IDs has been
dsg vendor-param-id 48 increased to 48 to support customer requirements. Previously, the CMTS
configuration supported a maximum of 32 DSG vendor parameter IDs.
Tracking ID: 77813
Example:
CASA(config-if-qam 0/0)# channel 1 dsg vendor-param-id 48
show running-config The configured Privacy Mode Encryption (PME) device ID and password have
video pme device-id been added to the show running-config command output.

CASA(config)# video pme device-id pme password pme
CASA(config)# show run | in device-id
video pme device-id 2 c67b1a0a29a72bca password 2
c67b1a0a29a72bca

1-254 Release Notes

tracking ID
ha hardware qam8x96 Hardware “Broadcast FIFO error” detection has been added to hardware
recovery monitoring to trigger QAM 8x96 high availability module switchovers if
configured. A new bitmask 0001000 value was added to the ha hardware
Tracking ID: 78513 qam8x96 recovery <bitmask> self-recover <bitmask> command to trigger
the switchover.
Example:
CASA(config)# ha hardware qam8x96 recovery 00001000
self-recover 00001000
CASA(config)# show ha hardware qam8x96 recovery

Current configuration:
Bit Recovery Self-recover HW Error Condition
-------- -------- ------------ ------------------
00000001 On Off DUC FIFO UNDERRUN
00000002 Off Off DUC FIFO OVERRUN
00000004 On On DUC/DAC PARITY ERROR
00000008 Off Off DUC/DAC LOCK ERROR
00000010 Off Off SEU UNCORRECTABLE_ERROR
00000020 On On FPGA 128MHZ LOCK ERROR
00000040 On Off DUC SPI ERROR
00000080 On On FPGA DDR PARITY ERROR
00000100 On On SEU CORRECTABLE ERROR
00000200 Off Off SEU CONTROLLER
HEARTBEAT ERROR
00000400 Off Off PCR CLOCKING ERROR
00000800 Off Off
00001000 On On BCAST FIFO ERROR…
Note: The BCAST FIFO ERROR detection bit is now obsolete.


tracking ID
video program-number The video program-number pass-through configuration command has been
pass-through introduced in the Casa CLI to support customers who are using table mode
VOD to send the initial STB configuration file where both the input and output
Tracking ID: 79111 program numbers are the same.
The default behavior is the output program number, based on table mode VOD
mapping.
If enabled, apply the no form of the command to disable this functionality.
Example:
CASA(config)# video program-number pass-through

1-256 Release Notes

100 Old River Road
Andover, MA 01810
USA
978-688-6706
CMTS
Release Notes
© 2017 Casa Systems, Inc.

All rights reserved.
DOC-3004-01
Document Revision 07.02.04.02_B59e9

October 10, 2017
Printed in United States of America

Rel Notes 7.2.4.2 Build59e9 PDF

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

Rel Notes 7.2.4.2 Build59e9 PDF

Caricato da

Copyright:

Formati disponibili

CMTS

Casa CMTS Release Notes, Version 7.2.4.2

Contacting Casa ............................................................................................... 1-4

Corporate facility ......................................................................................... 1-4

Technical support ........................................................................................ 1-4 .

Technical documentation .................................................................................. 1-4 .

Release note revision history ...................................................................... 1-5 .

Major features in Release 7.2 ........................................................................... 1-5 .

QAM 8x192 downstream module enhancements ....................................... 1-6 .

Implementation notes .............................................................................1-7

QAM 8x192 redundancy requirements for OFDM ...................................... 1-8 .

Support for two OFDM downstream channels in R7.2 ................................ 1-8 .

Configuration steps .................................................................................. 1-9 .

Reverting to one OFDM channel ..........................................................1-10

Dynamic modulation profile change on OFDM channels .......................... 1-10 .

Orthogonal Frequency Division Multiple Access (OFDMA) .......................1-11 .

Low-density parity-check (LDPC) code support in OFDMA ....................1-11 .

TaFDM between OFDMA and TDMA channels ......................................1-11 .

TaFDM configuration ............................................................................1-12

Casa Systems CMTS

Multiple IUC TLV support ....................................................................... 1-16 .

Monitoring OFDMA in SNMP ................................................................. 1-18 .

IPv6 Provider Edge routers (6PE) in BGP ................................................ 1-18 .

NetFlow V9 traffic flow monitoring ............................................................. 1-18 .

CMTS Release 7.2.4.2 software installation ................................................... 1-19 .

Version 7.2.4.2 distribution image ............................................................. 1-19 .

Software update procedures ..................................................................... 1-20 .

Verify any previously-installed software patches ................................... 1-20 .

Verifying the minimum boot loader firmware images ............................. 1-20 .

For Release 7.2 ....................................................................................1-21

Updating the application image ............................................................. 1-22 .

Reverting a previously-installed software patch .................................... 1-23 .

Resolved issues and changes in Version 7.2 ................................................. 1-24 .

Possible modem flaps with recovery after editing QAM

Casa Systems CMTS Release Ver. 7.2.4.2

Observed error message with in-service patch

DVB Simulcrypt over QAM 8x96 shared and narrowcast

SNMP process restarts under certain conditions (ID 79183) ...............1-183 .

LDP session establishment issue (ID 77793) ......................................1-183 .

OFDM channel entries in CLI and SNMP (ID 78054) ..........................1-184 .

QAM 8x192 module restart with switchover (ID 73300) .......................1-184 .

RFoG with TaFDM partial service issue (ID 72475) .............................1-184 .

Modems reporting OFDM MER decrease (ID 71187) ..........................1-184 .

QAM module redundancy issue with shared channels

QAM configuration modify issue (ID 66408) ........................................1-185 .

OFDMA upstream channel utilization incorrect (ID 66350) ..................1-185 .

MPLS traffic handling during SMM switchover (ID 59247) ...................1-185 .

Upstream partial-service issue with certain modulation

Single carrier 25 kHz spacing in OFDMA (ID 61617) ...........................1-185 .

show datapath-config dhcp-lease-tree command (ID 64537) ..............1-186 .

Operational information .................................................................................1-186

Resolutions to security vulnerabilities addressed in Release 7.2.4.1 ..1-186 .

OpenSSL library updates .....................................................................1-186 .

“Broadcast FIFO error” detection .........................................................1-187 .

Extended taps on UPS 16x8 upstream channels ................................1-187 .

Recommended modulation profile over ATDMA with 64QAM ..............1-187 .

Reverting to Release 7.1 (and prior) from Release 7.2 .......................1-188 .

OFDM — QAM 8x192 redundancy limitation (by design) ....................1-189 .

OFDMA — UPS 16x8 redundancy limitation (by design) .....................1-189 .

Enabling DVB Simulcrypt channels .....................................................1-189 .

Forwarding of clear multicast traffic .....................................................1-189 .

Upstream 16x8 channel width limitation ..............................................1-190 .

Casa Systems CMTS