Professional Documents
Culture Documents
Rel Notes 7.2.4.2 Build59e9 PDF
Rel Notes 7.2.4.2 Build59e9 PDF
Rel Notes 7.2.4.2 Build59e9 PDF
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
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 4. Release 7.2.4.1 Build 5791 changes and applied fixes..... 1-29
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 8. Release 7.2.4.0 Build 5219 changes and applied fixes..... 1-41
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 11. Release 7.2.3.2 Build 5382 changes and applied fixes..... 1-81
Table 12. Release 7.2.3.2 Build 5199 changes and applied fixes..... 1-81
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 .
Per-channel and per-port power issue in 2-OFDM mode (ID 72434) ..1-184 .
Enabling OFDMA probe may increase error rate (ID 61757) ...............1-185 .
QAM replication limit on QAM 8x96 and QAM 8x192 .......................... 1-190 .
Table 19. CLI additions and changes in Release 7.2 ...................... 1-196
Casa CMTS
Release Notes, Version 7.2.4.2
Topic Page
Topic Page
Topic Page
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 – C100G CMTS Hardware Installation Guide
• Casa Systems – C40G CMTS Hardware Installation Guide
• 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
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.
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.
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:
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.
• 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.
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.
• 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:
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).
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.
To undo the 2-channel OFDM configuration and revert to one OFDM channel and 64
SC-QAM channels, perform the following steps:
Example
CASA(config)# module 4 ofdm-channels 1
Need to reboot module 4 to apply the change.
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. 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.
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.
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.
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
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
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
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).
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.
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.
Example
The following shows a guardband assignment based on changing a TDMA upstream
interface frequency.
power-adjust continue 4
rolloff-period 64
iuc-profile 1
no shutdown
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.
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.
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
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.
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)#
The implementation allows for a single 6PE Autonomous System (AS) and supports
prefix delegation for IPv6 address assignment.
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.
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.
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
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.”
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.
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
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
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
Size Created on Status Patch name
--------- ------------------------ -------- ------------------------------------
3544158 Mon Dec 7 11:48:06 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
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.
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.
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.
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 *****
Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes (continued)
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.
• 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
Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes (continued)
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.
Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes (continued)
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.
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.
Table 3. Release 7.2.4.2 Build 5861 changes and applied fixes (continued)
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.
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.
Table 4. Release 7.2.4.1 Build 5791 changes and applied fixes (continued)
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
Table 4. Release 7.2.4.1 Build 5791 changes and applied fixes (continued)
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.
Table 4. Release 7.2.4.1 Build 5791 changes and applied fixes (continued)
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.
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.
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.
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.
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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)
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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:
Example:
CASA(conf-ofdma-channel 10/6.0)# symbols-per-frame 6
symbol per frame 6 requires at least 16 initial ranging
minislots in IUC profile
warning: symbol per frame is too small
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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
CASA(config)# cable modem deny 0001.0001.2044
CASA(config)# cable modem deny 0001.0001.2045
CASA(config)# cable modem deny 0001.0001.2046
CASA(config)# cable modem deny 0001.0001.2047
CASA(config)# cable modem deny 0001.0001.2048
CASA(config)# cable modem deny 0001.0001.2049
set black cm to database failed!
CASA(config)#
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.
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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.
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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)
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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)
Table 7. Release 7.2.4.1 Build 54cb changes and applied fixes (continued)
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)]
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
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)
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.
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
uc_mode 2: annex A modulation 64qam interleave 12
symbol_rate 6952 ref_cnt 24
bc_mode 1: annex A modulation 256qam interleave 12
symbol_rate 6900 ref_cnt 8
bc_mode 2: annex B modulation 256qam interleave 128x1
symbol_rate 0 ref_cnt 0
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
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
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)
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
::= { docsIf31MibObjects 1 }
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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 ! !
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
…
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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)
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
downstream 2 interface qam 1/0/33 secondary
downstream 3 interface qam 1/0/34 secondary
downstream 4 interface qam 1/0/35 secondary
downstream 5 interface qam 1/0/36 secondary
downstream 6 interface qam 1/0/37 secondary
downstream 7 interface qam 1/0/38 secondary
downstream 8 interface qam 1/0/39 secondary
…
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
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)
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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:
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
RNG-REQ from 0895.2a9b.2a99 on ofdma 12/2.0w 12 ms,
p-offset=1, f-offset=0, t-offset=-1
RNG-REQ from 0895.2a9b.2a99 on ofdma 12/2.0w 12 ms,
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.
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)
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Example:
CASA(conf)# system nms 172.0.1.163 port 8080 heartbeat 60
notifyUrl /nms-web-ui/api/notification
CASA(conf)# show system nms
server-ip port scheme heartbeat notifyUrl
172.0.1.163 8080 http 60 /nms-web-ui/api/notification
CASA(conf)# no system nms 172.0.1.163
CASA(conf)# show system nms
CASA(conf)#
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
-- 1.3.6.1.4.1.20858.10.56.1.2.1.3
casaSpectrumDataPowerNew OBJECT-TYPE
SYNTAX TenthdBmV
UNITS "TenthdBmV"
MAX-ACCESS read-only
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
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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:
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
CASA# show debugging
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
CASA# show debugging
SMM 6 debugging status
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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:
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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 ?
mdt Subsequent Address family 66 for
Multicast VPN
unicast Address Family modifier
vrf VPN Routing/Forwarding instance
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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.
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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).
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
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
Table 9. Release 7.2.4.0 Build 51c9 changes and applied fixes (continued)
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
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
Table 10. Release 7.2.3.2 Build 55fa changes and applied fixes
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)
Table 11. Release 7.2.3.2 Build 5382 changes and applied fixes
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.
68023 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 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)
Table 12. Release 7.2.3.2 Build 5199 changes and applied fixes
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.
Table 13. Release 7.2.3.2 Build 4cb3 changes and applied fixes
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.
Table 13. Release 7.2.3.2 Build 4cb3 changes and applied fixes
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.
Table 13. Release 7.2.3.2 Build 4cb3 changes and applied fixes
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:
Table 13. Release 7.2.3.2 Build 4cb3 changes and applied fixes
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.
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes
Example:
***** SNMP QUERY STARTED *****
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
***** SNMP QUERY FINISHED *****
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)
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.
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
uc_mode 2: annex A modulation 64qam interleave 12
symbol_rate 6952 ref_cnt 24
bc_mode 1: annex A modulation 256qam interleave 12
symbol_rate 6900 ref_cnt 8
bc_mode 2: annex B modulation 256qam interleave 128x1
symbol_rate 0 ref_cnt 0
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
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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)# interface upstream 13/0.0
CASA(config-if-ups 13/0.0)# pre-equalization ?
extended-taps support extended taps(tap equalizer),
default is off
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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 ofdm-channels 2
Need to reboot module 1 to apply the change.
CASA(config)# module 1 reboot
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.
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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
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)
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
Example:
CASA(config)# system service-delay ?
snmp delay before processing SNMP
tftp-proxy delay before processing TFTP proxy
Example:
CASA(config)# cable partial-service tx-power-deficit
CASA(config)# show running-config | inc deficit
cable partial-service tx-power-deficit
CASA(config)#
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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)
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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:
CASA(config-if-ups 9/31.0)# frequency 56000000
This board does not support higher than 55 MHz frequency.
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.
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
Example:
CASA(conf-minislot-cfg 30)# subcarrier-group-minislot 1 ?
<5000000-100600000> start frequency
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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
MAX-ACCESS read-only
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
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The count of secondary modem on the downstream
channel."
::= { casaCmtsDSModemEntry 6 }
Example:
***** SNMP QUERY STARTED *****
1: casaCmtsUSSecondaryModemCount.5005632 (gauge) 1
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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)
CASA(config)# snmp trap logging video alarm
bitrate-threshold 1000
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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
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
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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).
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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.
Table 14. Release 7.2.3.0 Build 49e9 changes and applied fixes (continued)
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 ! !
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
Table 15. Release 7.2.1.0 Build 482c changes and applied fixes
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
• 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
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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:
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
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.
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
ifDescr: OFDMA Upstream 1/1.0
ifType: ifType_ofdma
ifPhysAddress: 00:00:00:00:00:00
ifAdminStatus: Up (2)
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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.
Example:
CASA(config)# video table custom prog-per-chan 64
chan-per-port 24 start-udp-offset 65 skip-chan 12
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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.
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>).
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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:
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
55062 47da Enhancement. The show interface trunk stat command now reports the trunk
interface speed (IfSpeed) in the command output.
Example: 0/0.1w
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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(config)# interface ofdma 12/0.0
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
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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 ?
<0-1023> Docsis default: 3
C100G(config)# docsis submgt default max-ipv6-iapd 1023
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
---------------------------------------------------------------------------
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)#
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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.
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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
CASA(conf-ofdma-channel 4/12.0)#
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.
Table 16. Release 7.2.1.0 Build 47da changes and applied fixes (continued)
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.
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
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.
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
51712 4682 The docsIf31Mib will now appear in SNMP queries to the sysORTable MIB.
Previously, the docsIf31Mib was missing from the list.
Example:
***** SNMP QUERY STARTED *****
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
***** SNMP QUERY FINISHED *****
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
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.
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
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:
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.
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
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:
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
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.
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
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:
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.
Table 17. Release 7.2.1.0 Build 4682 changes and applied fixes (continued)
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes
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.
Example:
CMTS(config)# telnet access-group name1
CMTS(config)# ssh access-group name2
CMTS(config)# ipdr access-group name3
See the Casa Systems – CMTS Release 7.2 Features Guide for more
information.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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:
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.
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Example:
CASA(conf-if-vlan 10)# no l2vpn mac-address-movable
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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)#
-- 1.3.6.1.4.1.20858.10.58.1.1.1.25
casaIpMcastRoutePps OBJECT-TYPE
SYNTAXCounterBasedGauge64
UNITS "Packet per second"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Packet per second forwarded by this
router using this multicast routing entry."
::= { casaPimRouteEntry 25 }
See the Casa Systems – CMTS Release 7.2 Features Guide for more
information.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
See the Casa Systems – CMTS Release 7.2 Features Guide for more
information.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
40434 45b9 The show chassis status command has been implemented to display
summary information on current chassis status and card level information.
LastUptime will display status only if the module has been booted up more than
twice.
See the Casa Systems – CMTS Release 7.2 Features Guide for more
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.
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
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
Example:
CMTS(config)# show ntp-server
ntp server 74.120.8.2
ntp server 104.131.118.129 prefer
no ntp scheck
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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:
Example:
CMTS# md5 checksum ccsi.gz.rel7.2.0.0_build43b0
943d96f56361f10492fa3e899dac1e55
ccsi.gz.rel7.2.0.0_build43b1
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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:
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>
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
• 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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
41951 45b9 Enhancement. Support has been added for the
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Example:
CASA(config-if-ups 9/0.0)# logical-channel 1
pre-equalization auto-reset 60
See the Casa Systems – CMTS Release 7.2 Features Guide for more
information.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
See the Casa Systems – CMTS Release 7.2 Features Guide for more
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
See the Casa Systems – CMTS Release 7.2 Features Guide for more
information.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
Example:
CMTS(config-router-bgp)# address-family ipv6
CMTS(config-router-af)# distance bgp 77 88 99
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Example:
CMTS# debug ip bgp updates
<cr>
in BGP updates of incoming direction
out BGP updates of outcoming direction
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
See the Casa Systems – CMTS Release 7.2 Features Guide for more
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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))
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Corresponding CLI:
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
See the Casa Systems – CMTS Release 7.2 Features Guide for additional
information.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Example:
CASA(config)# route-map V6-CMTS-TO-HUB permit 5
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Example:
CASA(config)# interface docsis-mac 3
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Example:
CASA(config)# video simulcrypt ecmg test
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
• 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>
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
49286 45b9 The show tech-support command has been enhanced to include the following
additional information in the displayed output:
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
• docsIf31CmtsDsOfdmProfileStatsTable
• docsIf31CmtsDsOfdmProfileStatsEntry
• docsIf31CmtsDsOfdmProfileStatsProfileId
• docsIf31CmtsDsOfdmProfileStatsConfigChangeCt
• docsIf31CmtsDsOfdmProfileStatsFullChannelSpeed
• docsIf31CmtsDsOfdmProfileStatsOutOctets
• docsIf31CmtsDsOfdmProfileStatsOutUnicastOctets
• docsIf31CmtsDsOfdmProfileStatsOutMulticastOctets
• docsIf31CmtsDsOfdmProfileStatsOutFrames
• docsIf31CmtsDsOfdmProfileStatsOutUnicastFrames
• docsIf31CmtsDsOfdmProfileStatsOutMulticastFrames
• docsIf31CmtsDsOfdmProfileStatsCtrDiscontinuityTime
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
• casaCmtsCmIpToCpe2Table
• casaCmtsCmIpToCpe2Entry
• casaCmtsCmIpToCpe2CmVrfId
• casaCmtsCmIpToCpe2CmInetAddressType
• casaCmtsCmIpToCpe2CmInetAddress
• casaCmtsCmIpToCpe2VrfId
• casaCmtsCmIpToCpe2InetAddressType
• casaCmtsCmIpToCpe2InetAddress
• casaCmtsCmIpToCpe2MacAddress
• casaCmtsCmMacToCpe2Table
• casaCmtsCmMacToCpe2Entry
• casaCmtsCmMacToCpe2CmMacAddress
• casaCmtsCmMacToCpe2VrfId
• casaCmtsCmMacToCpe2InetAddressType
• casaCmtsCmMacToCpe2InetAddress
• casaCmtsCmMacToCpe2MacAddress
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
• casaCmtsCpeIpNetToPhysical2Table
• casaCmtsCpeIpNetToPhysical2Entry
• casaCmtsCpeIpNetToPhysical2IfIndex
• casaCmtsCpeIpNetToPhysical2NetAddressType
• casaCmtsCpeIpNetToPhysical2VrfId
• casaCmtsCpeIpNetToPhysical2NetAddress
• casaCmtsCpeIpNetToPhysical2CmPhysAddress
• casaCmtsCpeIpNetToPhysical2Type
50732, 45b9 Enhancement. Support has been added for the
50733 casaCmtsCmMacToCpe2Table objects in the SNMP
CASA-CABLE-CMCPE-MIB to support multiple virtual routing and forwarding
(VRF) queries. These objects include the following:
• casaCmtsCpeIpToCm2Table
• casaCmtsCpeIpToCm2Entry
• casaCmtsCpeIpToCm2CpeVrfId
• casaCmtsCpeIpToCm2CpeInetAddressType
• casaCmtsCpeIpToCm2CpeInetAddress
• casaCmtsCpeIpToCm2StatusIndex
• casaCmtsCpeIpToCm2Ipv4Address
• casaCmtsCpeIpToCm2Ipv6Address
• casaCmtsCpeIpToCm2MacAddress
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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"
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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:
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
Export video QAM configurations of module 11 to file /
tftpboot/casa-base1_11_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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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:
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.
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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).
Table 18. Release 7.2.0.0 Build 45b9 changes and applied fixes (continued)
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
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.
In the example, the channel-id-offset is set to 64, where channels 0–63 are
reserved for DOCSIS and the remaining 16 channels (64–79) are video
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
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.
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.
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.
Operational information
This section covers operational issues and limitations associated with the CMTS
hardware and software.
Example
CASA(config)# interface upstream 13/0.0
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
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. 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.
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.
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.
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.
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
Where,
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.
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
Example:
CASA# copy nvram <filename> nvram startup-config
Example
To display the current CMTS boot device and software image:
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.
For complete information on using SNMP to configure and monitor the CMTS, refer
to the Casa Systems – SNMP MIBs and Traps Reference.
[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.
Example:
CASA(config)# video table custom prog-per-chan 64
chan-per-port 24 start-udp-offset 65 skip-chan 12
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
ifDescr: OFDMA Upstream 1/0.0
ifType: ifType_ofdma
ifPhysAddress: 00:00:00:00:00:00
ifAdminStatus: Up (2)
ifOperStatus: Up(1)
------------------------------------------------
ifIndex: 16000161
ifDescr: OFDMA Upstream 1/1.0
ifType: ifType_ofdma
ifPhysAddress: 00:00:00:00:00:00
ifAdminStatus: Up (2)
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
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:
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
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.
Format:
Example:
CASA(config-if-qam 3/0)# ch 0 transport stream id 1 40 inc
2
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.
Example:
CASA# ssh-server gen-hostkey ecdsa
CASA# ssh-server gen-hostkey ed25519
show video simulcrypt The following fields have been added to the show video simulcrypt ecmg
ecmg display output.
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
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.
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.
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:
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
Export video QAM configurations of module 11 to file /
tftpboot/casa-base1_11_1 successfully
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.
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
0x0016 to 0x6FFF DVB Reserved
0x7000 unknown error
0x7001 unrecoverable error
0x7002 to 0x7FFF DVB Reserved
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.
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
• 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
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
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.
In the example, the channel-id-offset is set to 64, where channels 0–63 are
reserved for DOCSIS and the remaining 16 channels (64–79) are video
channels for the QAM 8x192. The remaining video channels are then numbered
0–15.
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.
Example:
CASA(config-if-mac 1)# initial-tech ofdma unicast-ranging
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
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#
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.
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(config)# interface ofdma 12/0.0
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
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
Example:
CASA(config)# docsis submgt default cm-filter-downstream ?
<0-1024> Docsis default: 0
CASA(config)# docsis submgt default cm-filter-downstream
1024
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 ?
<0-1023> Docsis default: 3
C100G(config)# docsis submgt default max-ipv6-iapd 1023
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.
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)
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.
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.
service group 2
downstream channel bonding
upstream channel bonding
no upstream rfog-scheduler
CASA(conf-ofdma-channel 4/12.0)#
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
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
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
uc_mode 2: annex A modulation 64qam interleave 12
symbol_rate 6952 ref_cnt 24
bc_mode 1: annex A modulation 256qam interleave 12
symbol_rate 6900 ref_cnt 8
bc_mode 2: annex B modulation 256qam interleave 128x1
symbol_rate 0 ref_cnt 0
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
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 ofdm-channels 2
Need to reboot module 1 to apply the change.
CASA(config)# module 1 reboot
For more information, see the section “QAM 8x192 downstream module
enhancements.”
Example:
CASA# system bootfile update
Example:
CASA(config)# system service-delay ?
snmp delay before processing SNMP
tftp-proxy delay before processing TFTP proxy
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.
The extended taps capability is not supported on the UPS 16x4 module.
Example:
CASA(config)# interface upstream 13/0.0
CASA(config-if-ups 13/0.0)# pre-equalization ?
extended-taps support extended taps(tap equalizer),
default is off
[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.
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:
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
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.
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:
CASA(config-if-ups 9/31.0)# frequency 56000000
This board does not support higher than 55 MHz frequency.
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
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
[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:
CASA(config)# snmp trap logging video alarm
bitrate-threshold ?
<0-4294967295> bitrate(bps)
CASA(config)# snmp trap logging video alarm
bitrate-threshold 1000
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
[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
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.
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
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 ! !
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.
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.
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
…
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
CASA(conf-video-edis 1)# output-port-base 1
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
downstream 1 interface qam 1/0/32 secondary
downstream 2 interface qam 1/0/33 secondary
downstream 3 interface qam 1/0/34 secondary
downstream 4 interface qam 1/0/35 secondary
downstream 5 interface qam 1/0/36 secondary
downstream 6 interface qam 1/0/37 secondary
downstream 7 interface qam 1/0/38 secondary
downstream 8 interface qam 1/0/39 secondary
…
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)
[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:
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.
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
---------------------------------------------------------
server-ip port scheme heartbeat notifyUrl
192.168.8.8 8080 http 60 /nms-web-ui/api/notification
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
RNG-REQ from 0895.2a9b.2a99 on ofdma 12/2.0w 12 ms,
p-offset=1, f-offset=0, t-offset=0
RNG-REQ from 0895.2a9b.2a99 on ofdma 12/2.0w 12 ms,
p-offset=1, f-offset=0, t-offset=-1
RNG-REQ from 0895.2a9b.2a99 on ofdma 12/2.0w 12 ms,
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
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.
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.
Example:
CASA(conf)# system nms 172.0.1.163 port 8080 heartbeat 60
notifyUrl /nms-web-ui/api/notification
CASA(conf)# show system nms
server-ip port scheme heartbeat notifyUrl
172.0.1.163 8080 http 60 /nms-web-ui/api/notification
CASA(conf)# no system nms 172.0.1.163
CASA(conf)# show system nms
CASA(conf)#
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
CASA# show debugging
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.
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
accompanying show command.
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.
Example:
CASA(config)# packetcable gate maxcount ?
<1-196607> gate count,default is cm_num*3/
10,Warning: This command may free
all current gates
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
[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.
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
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)
…
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).
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
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
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
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:
Example:
CASA(conf-ofdma-channel 10/6.0)# symbols-per-frame 6
symbol per frame 6 requires at least 16 initial ranging
minislots in IUC profile
warning: symbol per frame is too small
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:
CASA(config)# cable modem deny 0001.0001.2043
CASA(config)# cable modem deny 0001.0001.2044
CASA(config)# cable modem deny 0001.0001.2045
CASA(config)# cable modem deny 0001.0001.2046
CASA(config)# cable modem deny 0001.0001.2047
CASA(config)# cable modem deny 0001.0001.2048
CASA(config)# cable modem deny 0001.0001.2049
set black cm to database failed!
CASA(config)#
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.
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.
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.
• 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
Example:
CASA(ip-bundle 1.1)# cable helper-ipv6-address
2001:20:158::6 dva
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.
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
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.
Example:
CASA(config)# video program-number pass-through
978-688-6706
CMTS
Release Notes
DOC-3004-01