Table Of Contents
Caveats for the Cisco uBR10012 Universal Broadband Router in Cisco IOS Release 12.2SC
Open Caveats—Cisco IOS Release 12.2(33)SCC2
Closed Caveats—Cisco IOS Release 12.2(33)SCC2
Open Caveats—Cisco IOS Release 12.2(33)SCD
Resolved Caveats—Cisco IOS Release 12.2(33)SCD
Open Caveats—Cisco IOS Release 12.2(33)SCB6
Resolved Caveats—Cisco IOS Release 12.2(33)SCB6
Open Caveats—Cisco IOS Release 12.2(33)SCC1
Resolved Caveats—Cisco IOS Release 12.2(33)SCC1
Open Caveats—Cisco IOS Release 12.2(33)SCB5
Resolved Caveats — Cisco IOS Release 12.2(33)SCB5
Open Caveats—Cisco IOS Release 12.2(33)SCC
Resolved Caveats—Cisco IOS Release 12.2(33)SCC
Open Caveats—Cisco IOS Release 12.2(33)SCB4
Resolved Caveats — Cisco IOS Release 12.2(33)SCB4
Open Caveats—Cisco IOS Release 12.2(33)SCB3
Resolved Caveats — Cisco IOS Release 12.2(33)SCB3
Open Caveats—Cisco IOS Release 12.2(33)SCB2
Resolved Caveats — Cisco IOS Release 12.2(33)SCB2
Open Caveats — Cisco IOS Release 12.2(33)SCB1
Resolved Caveats — Cisco IOS Release 12.2(33)SCB1
Open Caveats — Cisco IOS Release 12.2(33)SCB
Resolved Caveats — Cisco IOS Release 12.2(33)SCB
Open Caveats — Cisco IOS Release 12.2(33)SCA2
Resolved Caveats — Cisco IOS Release 12.2(33)SCA2
Open Caveats — Cisco IOS Release 12.2(33)SCA1
Resolved Caveats — Cisco IOS Release 12.2(33)SCA1
Open Caveats — Cisco IOS Release 12.2(33)SCA
Resolved Caveats — Cisco IOS Release 12.2(33)SCA
Obtaining Documentation and Submitting a Service Request
Caveats for the Cisco uBR10012 Universal Broadband Router in Cisco IOS Release 12.2SC
February 22, 2010
OL-15874-14
This document lists severity 1 and 2 caveats and select severity 3 caveats for the Cisco uBR10012 Universal Broadband Router in Cisco IOS Release 12.2SC, up to and including Cisco IOS Release 12.2(33)SCC2. Caveats describe unexpected behavior or defects in Cisco IOS software releases. Severity 1 caveats are the most serious caveats; severity 2 caveats are less serious. Severity 3 caveats are moderate caveats, and only select severity 3 caveats are included in the caveats document.
Use this caveats document with the following release notes available on Cisco.com:
•
Cross-Platform Release Notes for Cisco Universal Broadband Routers in Cisco IOS Release 12.2SC
•
•
Note
Contents
•
Caveats
This document describes open and resolved severity 1 and 2 caveats and select severity 3 caveats:
•
•
Within the sections, the caveats are sorted by component in alphabetical order. The caveats are also sorted alphanumerically by caveat number.
The following information is provided for each caveat:
•
•
•
Open Caveats—Cisco IOS Release 12.2(33)SCC2
•
Symptoms: The CPUHOG error message and traceback may be seen on the protect line card of a Cisco uBR10012 router.
Conditions: This issue occurs when the clear cable modem all reset command is executed.
Workaround: There is no workaround.
•
Symptoms: The active DOCSIS queues remain active in the event of a DOCSIS SPA failure.
Conditions: This issue is observed if there are modems online and passing traffic on the modular-cable and/or on wideband-cable interfaces and the DOCSIS SPA fails, the DOCSIS queues associated with these online modems remain active attempting to dequeue.
Workaround: Execute the microcode reload pxf command.
•
Symptoms: Cable modems do not respond to Layer 3 pings.
Conditions: This issue is observed only on the Cisco uBR10-MC5X20S/U line cards and when equalization-coefficient (PRE-Egis configured.
Workaround: Restart the cable line card.
•
Symptoms: A multicast QoS session is not automatically created when changing group configuration or GQC.
Conditions: This issue is seen when a multicast QoS group is configured on a bundle interface and a matching static-group is defined. However, any change in the group configuration after it is applied to the bundle interface is not taken into effect, and the original multicast QoS session is removed.
Workaround: Remove the multicast QoS session from the bundle interface and re-apply it to the bundle.
•
Symptoms: Alignment traceback messages are found when the show memory leak res user and show buffer usage commands are executed.
Conditions: This issue occurs when the show memory leak res user and show buffer usage commands are executed in Cisco IOS Release 12.2(33)SCB.
•
Symptoms: Memory leak is observed on the line card due to MAC parser with overnight PC calls.
Conditions: This issue occurs after making overnight PC calls.
Workaround: There is no workaround.
•
Symptoms: OIR of a PCMCIA flash disk can cause a watchdog reset of the PRE.
Conditions: This issue is observed during OIR of the PCMCIA flash disk that is being actively accessed.
Workaround: Restrict the removal of PCMCIA flash disks.
•
Symptoms: There may be sporadic short losses (of a few minutes) of multiple CMs going off on a (random) upstream. These losses are usually accompanied by a spike of the error per second rate or by an MER drop and a decrease in docsIfSigQUnerroreds.
However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.
Conditions: This issue is observed on Cisco uBR10-MC5X20H line cards.
Workaround: There is no workaround.
•
Symptoms: Entries in docsBpi2CmtsMulticastObjects duplicate after the line card revertback.
Conditions: This issue is observed when a cable match command is configured with BPI. The IGMP join is received for the group in cable match command and the docsBpi2CmtsMulticastObjects is populated. This results in the line card switchover and revertback.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000 PRE CPU goes to 100% when the FPGA on the Wideband SPAs plugged into a Cisco SIP-600 are being upgraded.
Conditions: This issue only occurs during the SPA FPGA upgrade process.
Workaround: There is no workaround.
•
Symptoms: The cable modems (CMs) that are not capable of downstream bonding are expected to come online on downstreams that are not part of a bonding group. Non-bonding capable CMs are wrongly registered in bonded channels.
Conditions: This issue occurs when the cable service attribute non-ds-bonded downstream-type bonding-disabled command is configured on the Cisco CMTS.
Workaround: There is no workaround.
•
Symptoms: Active PRE fails over to the secondary reporting:
ACTIVE RP WATCHDOG TIMEOUT TRIGGEREDConditions: This issue was first observed on Cisco IOS Release 12.3(23)BC7.
Workaround: There is no workaround.
•
Symptoms: While configuring the cable upstream docsis-mode command using SNMP, the standby PRE module does not synchronize with this configuration.
Conditions: This issue occurs when configuring the cable upstream docsis-mode command using SNMP.
Workaround: Configure the cable upstream docsis-mode command using the CLI instead of SNMP.
•
Symptoms: Around 60 to 70 bytes of buffer memory space is allocated when the protect line card becomes active after a system bootup.
Condition: This issue occurs during a line card switchover.
Workaround: There is no workaround.
•
Symptoms: After PRE switchover, the service flow counter shows 0 on the Cisco uBR10012 router.
Conditions: This issue occurs during a PRE switchover.
Workaround: There is no workaround.
•
Symptoms: Executing the term len 0 and show cable modem commands pauses the generated output randomly for up to a second on PRE4 module with hundreds of CMs.
Conditions: This issue occurs on PRE4 module with hundreds of CMs.
Workaround: There is no workaround.
•
Symptoms: The wideband association is displayed incorrectly after the cable power is switched off on all the line cards.
Conditions: This issue is observed when running the following script:
1.
2.
3.
Workaround: There is no workaround.
•
Symptoms: The modem's accumulated timing-offset goes to a negative value. The following error message is displayed at the CMTS:
%UBR10000-4-BADTXOFFSET: Bad timing offset -182443 detected for cable modem 000a.73cc.c7b7.Conditions: This issue occurs on the Cisco uBR-MC5X20D line card.
Workaround: There is no workaround.
•
Symptoms: The MIB object docsIfCmtsChannelUtUtilzation is not supported on modular cable or integrated cable (MC/IC) interfaces.
Conditions: This issue occurs when you set the MIB objects docsIfCmtsChannelUtilizationInterval and ccwbRFChanUtilInterval, and use the SNMP query for docsIfCmtsChannelUtilization. The results are displayed only for Cisco UBR10-MC28U and Cisco UBR-MC5X20 line card downstream channels.
Workaround: Use the MIB object ccwbRFChannelUtilization for MC/IC interfaces instead.
•
Symptoms: The Cisco uBR10-MC5X20H line card may crash after reporting memory allocation failures.
Conditions: This issue is observed when multiple memory allocations failures occur.
Workaround: There is no workaround.
•
Symptoms: The 24th MAC Domain Downstream Service Group (MD-DS-SG) is missing in output of show command show cable mac-domain downstream-service-group.
Conditions: This issue occurs when fiber-node configuration has channels in a MAC domain belonging to 24 different fiber-nodes.
Workaround: There is no workaround.
•
Symptoms: The Cable line card crashes with PacketCable Multimedia (PCMM) voice call testing.
Conditions: This issue was seen in multi-line Cisco Analog Telephone Adaptor (ATA) behind cable modems (CMs) in a PCMM setup.
Workaround: There is no workaround.
•
Symptoms: Dynamic multicast service flow and reserved bandwidth exist even after removal of multicast QoS (MQoS) configuration from the second bonding group.
Conditions: This issue occurs after a multicast QoS bandwidth reservation oversubscription takes place.
Workaround: Perform a PRE switchover.
•
Symptoms: The MIB object docsIfCmtsCmStatusTable does not display all modem entries as the MIB object docsIf3CmtsCmRegStatusTable.
Conditions: This issue occurs when the modem is in offline state.
Workaround: There is no workaround.
•
Symptoms: The following traceback is seen when unconfiguring the bundle interfaces:
Oct 21 23:40:08.951 PDT: %GENERAL-3-EREVENT: No HWIDB_SB_C10K_TT-Traceback= 60A32A5C 6182EEE0 619159A0 61916248 6019EEFC 601936C0 60198EE0 60AADBB0 60A91CF4 60A9CCA8 609B8940 601384B4 609E4628 60B2E6B8 60B2E6A4Conditions: This issue occurs when a complicated testing case runs scripts in which all bundle interfaces are unconfigured.
Workaround: There is no workaround.
•
Symptoms: The WB association is incorrect after line card switchover and hardware reset.
Conditions: This issue occurs when a series of power-off/power-on operations are performed on the working and protect line cards.
Workaround: There is no workaround.
•
Symptom: The MIB object CLAB-TOPO-MIB returns more interface instances compared to the CLI.
Conditions: This issue occurs under normal conditions.
Workaround: Use CLI instead of SNMP to get the fiber-node information.
•
Symptoms: The Layer2 VPN failed to forward ARP traffic on Cisco uBR10012 router.
Conditions: This issue occurs while sending traffic through Layer2 VPN.
Workaround: There is no workaround.
•
Symptom: The classifiers for Cisco DPC2607 CPE types correctly identifies the CPE, but the filters are not effective in filtering the packets from these devices.
Conditions: This issue occurs in normal operations of the cable plant. Some CPEs do not behave properly and send an ARP before sending a DHCP Discover message. This causes the CPE to be populated in the CMTS database as an "Unknown" device type. Once the CPE sends the DHCP discover message, the device type is updated in the software, but the hardware entries are still categorized as "Unknown".
Workaround: There is no workaround.
•
Symptoms: The "Total DS/US pkts/bytes" counters displayed by the show cable l2-vpn xconnect dot1q-vc-map verbose command are inconsistent on Cisco uBR10012 router.
Conditions: This issue occurs when DOCSIS SF-based 802.1Q mapping L2VPN is configured.
Workaround: There is no workaround.
•
Symptoms: Number of pre-equalization taps decreases incorrectly after CLC failover.
Conditions: This issue is observed on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB4 with N+1 redundancy.
Workaround: There is no workaround.
•
Symptoms: Traceback is seen during auto-upgrade of DOCSIS Timing, Communication and Control (DTCC) card firmware.
Conditions: This issue occurs on a firmware upgrade of DTCC card.
Workaround: There is no workaround.
•
Symptoms: The cable clock dti command does not work.
Conditions: This issue occurs when the system starts with two DTCC cards, and one card is unplugged during the run time.
Workaround: There is no workaround.
•
Symptom: The following items of the MIB object docsIfCmtsCmStatusTable are not supported on DOCSIS 3.0 online cable modem. This is because these objects rely on single upstream channel while the online DOCSIS 3.0 cable modem has many upstream channels.
–
–
–
–
–
–
docsIf3CmtsCmUsStatusTable has following objects:
–
–
–
–
–
–
Conditions: This issue occurs when there is an online DOCSIS 3.0 modem.
Workaround: There is no workaround.
•
Symptoms: Generic Routing Encapsulation (GRE) tunnel does not forward traffic.
Conditions: This issue occurs when a new GRE tunnel is created on a Cisco uBR1012 router.
Workaround: Execute the shutdown and the no shutdown commands on the tunnel interface.
•
Symptoms: The IGMPv3 CPE behind the DOSCSIS 3.0 main distribution frame (MDF) capable modem using local integrated-cable downstream interface as primary fails to receive any multicast traffic after the UBR10-MC20X20 line card switchover occurs due to DSID change.
Conditions: The UBR10-MC20X20 line card fails to receive traffic after a switchover.
Workaround: There is no workaround.
•
Symptoms: The debug output to the terminal is curtailed when "logging discriminator" is enabled.
Conditions: This issue was observed in Cisco IOS Release 12.2(33)SCB5.
Workaround: There is no workaround.
•
Symptoms: Flow-control does not work on ESR-HH-1GE interface of a Cisco uBR10012 router.
Conditions: This issue occurs on ESR-HH-1GE interface of a Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptoms: The MIB object docsDevEvReporting does not display the local volatile bit.
Conditions: This issue occurs as the MIB object ignores bits from 3 to 7. When the 3rd bit is set, the local volatile is not set.
Workaround: There is no workaround.
•
Symptoms: The Wideband DOCSIS 3.0 modem does not receive MDD from Cisco uBR10012 router. The Modem falls back to narrowband.
Conditions: This issue occurs on a Cisco uBR10-MC5x20H line card.
Workaround: Remove the downstream modular-cable configuration from the cable interface and then reinstall the line card. Another workaround is to reload the line card.
•
Symptoms: The show tech command does not include contents of show controller integrated-cable x/y/z for the Cisco UBR10-MC20X20 cable line card.
Conditions: This issue occurs on the Cisco UBR10-MC20X20 cable line card.
Workaround: Execute the show controller integrated-cable x/y/z command after the executing the show tech command.
•
Symptoms: The PRC_CONFIG_CHANGE change-type is displayed while configuring privacy related commands.
Conditions: This issue occurs when terminal prc expose is enabled on theCisco uBr10012 router.
Workaround: There is no workaround.
•
Symptom: The show inventory command displays the Cisco UBR10-MC5X20T line card when a Cisco uBR10-MC5x20H line card is pre-provisioned in the configuration.
Conditions: This issue occurs when the show inventory command is executed during the pre-configuration of hardware.
Workaround: Use the output of show diag command to determine the installed hardware.
•
Symptoms: A crash may occur on the Cisco uBR10-MC5X20H line card.
Conditions: This issue occurs as the PRE module crashes due to a IPC time out.
Workaround: There is no workaround.
•
Symptoms: The upstream service flow is rejected although the reserved bandwidth and the requested bandwidth is lesser than max-reserved-bandwidth.
Conditions: This issue is triggered if the admission control (AC) event is not configured, but AC max-reserved-bandwidth and AC threshold are configured.
Workaround: Do not configure the AC threshold if the AC event is not configured.
•
Symptoms: The standby PRE2 module may keep getting automatically reset due to PEER_INIT_TIMEOUT.
Conditions: This issue occurs when the standby PRE2 module is normalized for more than 100 times.
Workaround: Power cycle the Cisco uBR10012 chassis.
•
Symptoms: The high availability Baseline Privacy Index (BPI) TEK encryption key sync occurs repeatedly.
Conditions: This issue occurs when BPI is enabled.
Workaround: There is no workaround.
•
Symptom: The Wideband cable modem enters online state but does not enter w-online state, even after executing clear cable modem command.
Conditions: This issue occurs after a Cisco UBR10-MC20X20 line card switchover.
Workaround: There is no workaround.
•
Symptoms: The standby PRE2 module may keep getting automatically reset due to PEER_INIT_TIMEOUT.
Conditions: This issue occurs when the standby PRE2 module is normalized for more than 100 times.
Workaround: Power cycle theCisco uBR10012 chassis.
•
Symptoms: The LinkDown SNMP traps are sent twice instead of once causing some Network Management Systems (NMS) tools to erroneously think the link is still down.
Conditions: This issue occurs when a Wideband SPA or GigabitEthernet interface on the Cisco uBR10012 router goes down or an attached cable is disconnected.
Workaround: There is no workaround.
•
Symptoms: A message indicating duplicate frequencies are configured on the integrated-cable controllers is required.
Conditions: This is required during migration of the Cisco uBR10-MC5x20H line card to the Cisco UBR10-MC20X20V line card.
Workaround: The downstream rf-channel assignment mapping needs to be done prior to migration.
•
Symptoms: The port does not become active.
Condition: This issue occurs on a Cisco uBR10012 router with DEPI control plane configured.
Workaround: There is no workaround.
•
Symptoms: The Cisco CMTS may incorrectly attempt to load-balance to a disabled interface.
Conditions: This issue occurs in Cisco IOS Release 12.2(33)SCB5.
Workaround: There is no workaround.
•
Symptoms: Excessive unicast and multicast packet loss is seen on a Wideband SPA switchover.
Conditions: This issue occurs on a Wideband SPA GigabitEthernet interface. The switchover takes 70 seconds to converge.
Workaround: There is no workaround.
•
Symptoms: The cable modems go offline on a port.
Conditions: This issue is seen on the downstream PHY on the cable line cards
Workaround: Reload the line cards.
Closed Caveats—Cisco IOS Release 12.2(33)SCC2
•
Symptoms: The cable clock dti command does not work.
Conditions: This issue occurs when the system starts with two DTCC cards, and one card is unplugged during run time.
Workaround: There is no workaround.
•
Symptoms: The modem may register in partial mode. This is seen when the show cable modem [mac] verbose | inc partial command was executed. The DOCSIS 3.0 modem keeps cycling from offline to "UB init(t)" state, but is unable to register online.
Conditions: These issue occurs in the following conditions:
The PHYv3.0 section 6.2.19 Transmit Power Requirement contains the transmit power budget on per channel basis, derived from the modem transmit channel set, and each individual upstream channel parameters. The existing DOCSIS plant may be designed for single channel DOCSIS 1.x/2.0 modems, which has a much higher maximum transmit power level, comparing to DOCSIS 3.0 modem operating in MTC-mode and having 2 or more channels.
In such a case, the modem may range successfully prior to REGISTRATION, since the modem is still operating with a single channel, like legacy 2.0/1.x modem. As soon as it is transitions to MTC-mode during REG-RESP, its allowable maximum transmit power level is below the ranged reference channel power level, thus causing the above error condition, and modem stop any ranging attempts on the newly assigned channels. Eventually, it fails to register and goes offline. This cycle repeats. This case is only applicable if all upstream channels assigned to the modem channel set are exceeding the peak allowable transmit power level.
If all channel are not exceeding the peak transmit power level, then modem may register in partial mode. The modem may be able to continue to range successfully on the channel(s) that are still within the range, and transmitting data on those channel in partial-mode.
Workaround: For those modems having severe upstream signal lost, and are required to transmit at far beyond the PHY3.0 maximum per channel transmit power budget, they can be individually selected to register in non-bonded mode (non-MTC-mode), as in normal DOCSIS 2.0/1.x modem, for the upstream path. Use the cable modem (CM) config file with the bonded-bit set to off in CM-required-attribute via TLV 43.8 and 43.9; also make sure that the CMTS mtc-mode configuration is the default setting which would enforce the CM required-attribute bonded-bit checking to allow DOCSIS 3.0 modem to register in mtc-mode.
By disabling mtc-mode for these modems, they now have the same maximum transmit power budget as a DOCSIS 2.0/1.x modem would have.
•
Symptoms: A crash was observed on the line card at cmts_crane_read_key.
Conditions: This issue occurs when multicast service identifiers (SID)s are configured on the line card. This was seen while executing the show interface cable key command.
Workaround: Do not configure multicast SIDs on the line card.
•
Symptoms: A bus error may occur on Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCC.
Conditions: This issue was observed as the traceback showed the SNMP getNext query was in progress for the MIB object named docsIf3CmtsCmRegStatusEntry.
Workarounds: There is no workaround.
•
Symptoms: The OIR upgrade from a Cisco uBR-MC5X20x line card to Cisco UBRMC20X20V line card fails when DOCSIS mode is Annex A and spectrum range of (5-65 Mhz) is configured.
The failure of the OIR upgrade is seen via messages and all the Cable interfaces will be placed in "administratively down" state.
Jan 14 09:15:20.950: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/0.Jan 14 09:15:20.970: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/1.Jan 14 09:15:20.974: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/2.Jan 14 09:15:20.974: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/3.Jan 14 09:15:20.978: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/4.Conditions: This issue occurs when the Annex mode is configured as Annex A on downstream ports of a Cisco uBR-MC5X20x line card and the upstream ports are using spectrum range of 5-65Mhz.
Workaround: The issue is due to increased frequency range supported by Annex A <5-65Mhz> as compared to Annex B <5-55Mhz>. Since the upgrade fails due to increased spectrum range it is advised to
1.
2.
3.
4.
5.
If a spectrum group is configured on the line card, do the following as in the example:
Example: cable spectrum-group 1 band 27000000 65000000 configuration
1.
2.
3.
4.
Note
•
Symptoms: The first line card does not get upgraded on the Cisco uBR10012 router.
Conditions: This issue occurs when performing Single Step In-Service Software Upgrade (ISSU) on the line card.
Workaround: Manually upgrade the first line card.
•
Symptoms: Layer 2 VPN configuration with BPI configuration failed on the Cisco uBR10012 router.
Conditions: This issue occurs when both Layer 2 VPN and BPI are configured.
Workaround: There is no workaround.
•
Symptoms: The Cisco UBR-MC20X2V line card may crash when it receives an invalid bandwidth request.
Conditions: This issue occurs when an error condition exists where the CMTS can receive a bonded request from an invalid SID, thus causing the line card crash.
Workaround: There is no workaround.
•
Symptom: "%SYS-2-BADSHARE: Bad refcount in pak_enqueue" type of tracebacks are seen in the PRE module running Cisco IOS Release 12.2(33)SCC1.
Conditions: This issue occurs when a particle-based packet is pushed into the toaster by the PRE module.
Workaround: There is no workaround.
•
Symptoms: The line card reloads due to an error when Layer 2 VPN is configured on the cable modem.
Conditions: This issue occurs in cable modems when Layer 2 VPN configured and Baseline Privacy Index (BPI+) not configured.
Workaround: Configure BPI+ on cable modems with Layer 2 VPN configurations.
•
Symptoms: The Cisco uBR10012 router delays the response to SNMP client causing an ongoing SNMP polling timeout.
Conditions: This issue occurs in Cisco uBR10012 routers running PRE2 while polling the ccwbWBCmStatusTable or ccwbWBCmStatusExtTable. This issue was observed when many narrowband modems were online, but no wideband modem.
Workaround: Increase the SNMP timeout used by Network Management Applications or exclude the tables ccwbWBCmStatusTable or ccwbWBCmStatusExtTableby configure the SNMP view:
snmp-server view excludewideband iso includedsnmp-server view excludewideband 1.3.6.1.4.1.9.9.479.1.6 excludedsnmp-server view excludewideband 1.3.6.1.4.1.9.9.479.1.7 excludedsnmp-server community <community> view excludewideband RO <acl number>•
Symptoms: The cable modems loses connectivity periodically on Cisco UBR-MC20X20 linecards. An outage is caused when the default TEK life-time interval is configured at the MAC domain.
Conditions: This issue occurs during normal operations and is caused by a problem decrypting the upstream traffic when the modem uses key sequence 15 to encrypt the traffic.
Workaround: There is no workaround.
•
Symptoms: The cable modem (CM) fails to receive the Ranging-Response (RNG-RSP) message.
Conditions: This issue occurs when the CMTS detects that a CM performs initial ranging on a upstream/downstream pair that are not within the same MAC domain.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(33)SCD
•
Symptoms: Cable modems do not respond to layer 3 pings.
Conditions: This issue is only on the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U cards and when PRE-EQ (equalization-coefficient) is configured.
Workaround: Restart the cable line card.
•
Symptoms: A multicast quality of service (QoS) session is not automatically created when changing group configuration or group QoS configuration (GQC).
Conditions: This issue is seen when a multicast QoS group is configured on a bundle interface and a matching static-group is defined. However, any change in the group configuration after it is applied to the bundle interface is not taken into effect, and the original multicast QoS session is removed.
Workaround: Remove the multicast QoS session from the bundle interface and re-apply it to the bundle.
•
Symptoms: Alignment traceback messages are found when the show memory leak res user and show buffer usage commands are executed.
Conditions: This issue occurs when you execute the show memory leak res user and show buffer usage commands in Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed due to service identifier (SID) management task.
Conditions: This issue is observed when the packetcable calls are present.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed on the line card due to MAC parser with overnight packetcable calls.
Conditions: This issue is observed when overnight packetcable calls are present.
Workaround: There is no workaround.
•
Symptoms: OIR of a Personal Computer Memory Card Industry Association (PCMCIA) flash disk can cause a watchdog reset of the PRE.
Conditions: This issue is observed during OIR of the PCMCIA flash disk that is being actively accessed.
Workaround: Restrict the removal of PCMCIA flash disks.
•
Symptoms: There may be sporadic short losses (of a few minutes) of multiple CMs going off on a (random) upstream. These losses are usually accompanied by a spike of the error per second rate or by an modulation error ratio (MER) drop and a decrease in docsIfSigQUnerroreds.
However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.
Conditions: This issue is observed on Cisco uBR10-MC5X20H line cards.
Workaround: There is no workaround.
•
Symptoms: Entries in docsBpi2CmtsMulticastObjects duplicate after the line card revertback.
Conditions: This issue is observed when a cable match command is configured with Baseline Privacy Index (BPI). The Internet Group Management Protocol (IGMP) join is received for the group in cable match command and the docsBpi2CmtsMulticastObjects is populated. This results in the line card switchover and revertback.
Workaround: There is no workaround.
•
Symptoms: Users with a privilege level of 15 and `view root' cannot perform a secure copy (SCP).
Conditions: This issue occurs when users with `view root' privilege tries to perform SCP.
Workaround: Remove the `view root' privilege.
•
Symptoms: The Cisco uBR10000 PRE CPU goes to 100% when the field-programmable gate array (FPGA) on the Wideband SPAs plugged into a Cisco SIP-600 are being upgraded.
Conditions: This issue only occurs during the SPA Field Programmable Gate Array (FPGA) upgrade process.
Workaround: There is no workaround.
•
Symptoms: The cable modems (CMs) that are not capable of downstream bonding are expected to come online on downstreams that are not part of a bonding group. Non-bonding capable CMs are wrongly registered in bonded channels.
Conditions: This issue occurs when the cable service attribute non-ds-bonded downstream-type bonding-disabled command is configured on the Cisco CMTS.
Workaround: There is no workaround.
•
Symptoms: Active PRE fails over to the secondary reporting:
ACTIVE RP WATCHDOG TIMEOUT TRIGGEREDConditions: This issue was first observed on Cisco IOS Release 12.3(23)BC7.
Workaround: There is no workaround.
•
Symptoms: While configuring the cable upstream docsis-mode command using SNMP, the standby PRE module does not synchronize with this configuration.
Conditions: This issue occurs when configuring the cable upstream docsis-mode command using SNMP.
Workaround: Configure the cable upstream docsis-mode command using the CLI instead of SNMP.
•
Symptoms: The Cisco Wideband SPA does not transmit traffic. The Edge Quadrature Amplitude Modulation (EQAM) indicates no input traffic.
Conditions: This issue is seen on the Cisco SIP-600 with a PRE4 module, 5 x1 GigabitEthernet interface, and SPA-24XDS-SFP Wideband SPAs.
Workaround: Perform a PRE module reload.
•
Symptoms: Around 60 to 70 bytes of buffer memory space is allocated when the protect line card becomes active after a system bootup.
Condition: This issue occurs during a line card switchover.
Workaround: There is no known workaround.
•
Symptoms: Some cable modems (CMs) may go offline during a line card switchover.
Condition: This issue occurs during a switchover of the protect Cisco uBR10-MC5X20H line card and the working Cisco uBR10-MC5X20U line card.
Workaround: Reduce the number of modems connected to the Cisco uBR10-MC5X20U line card.
•
Symptoms: After PRE switchover, the service flow counter shows 0 on the Cisco uBR10012 router.
Conditions: This issue occurs during a PRE switchover.
Workaround: There is no workaround.
•
Symptoms: Executing the term len 0 and show cable modem commands pauses the generated output randomly for up to a second on PRE4 module with hundreds of CMs.
Conditions: This issue occurs on PRE4 module with hundreds of CMs.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR-MC5X20U-D card crashes multiple times with the following message in the crashinfo file:
Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0x6038C709Conditions: This issue has been observed on the Cisco uBR10012 router with PRE2 module.
Workaround: There is no workaround.
•
Symptoms: The modem's accumulated timing-offset goes to a negative value. The following error message is displayed at the CMTS:
%UBR10000-4-BADTXOFFSET: Bad timing offset -182443 detected for cable modem 000a.73cc.c7b7.Conditions: This issue occurs on the Cisco uBR10-MC5X20 line card.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10-MC5X20H line card may crash after reporting memory allocation failures.
Conditions: This issue is observed when multiple memory allocations failures occur.
Workaround: There is no workaround.
•
Symptoms: The cable line card crashes when a specific 3-way call scenario is initiated.
Conditions: This issue occurs where multi-line ATAs are placed behind CMs in a PacketCable Multimedia (PCMM) setup.
Workaround: There is no workaround.
•
Symptoms: Dynamic multicast service flow and reserved bandwidth exist even after removal of multicast QoS (MQoS) configuration from the second bonding group.
Conditions: This issue occurs after a multicast QoS bandwidth reservation oversubscription takes place.
Workaround: Perform a PRE switchover.
•
Symptoms: The show inventory command output is not showing the secondary PRE on an uBR10012 router.
Conditions: This issue occurs on an uBR10012 router running Cisco IOS Release 12.2(33)SCB2.
Workaround: There is no workaround.
•
Symptoms: Inaccurate timing offset values from Cable Modem Termination Systems (CMTS).
Conditions: None.
Workaround: Apply the modem firmware patch.
•
Symptoms: When VPN routing and forwarding (VRF) and tunneling is configured, the output traffic rate through tunnel interface cannot exceed 4 Kbps.
Conditions: This issue occurs when the destination IP of the tunnel interface belongs to non-global VRF and the traffic direction is outgoing.
Workaround: Make sure that the destination IP address of the tunnel interface belongs to global VRF, and not to any specific VRF.
•
Symptoms: Cisco Wideband SPA sends only "sync Tx" packets.
Conditions: This issue is observed after Cisco Wideband SPA reload and when a DOCSIS Timing Interface (DTI) server is used.
Workaround: Reload the jacket card.
•
Symptoms: Generic Routing Encapsulation (GRE) tunnel does not forward traffic.
Conditions: This issue occurs when a new GRE tunnel is created on a Cisco uBR10012 router.
Workaround: Execute the shutdown and the no shutdown commands on the tunnel interface.
•
Symptoms: The IGMPv3 CPE behind the DOCSIS 3.0 main distribution frame (MDF) capable modem using local integrated-cable downstream interface as primary fails to receive any multicast traffic after the UBR-MC20X20V line card switchover occurs due to Downstream Service Identifier (DSID) change.
Conditions: The UBR-MC20X20V line card fails to receive traffic after a switchover.
Workaround: There is no workaround.
•
Symptoms: The debug output to the terminal is curtailed when "logging discriminator" is enabled.
Conditions: This issue was observed in Cisco IOS Release 12.2(33)SCB5.
Workaround: There is no workaround.
•
Symptoms: Flow-control does not work on ESR-HH-1GE interface of a Cisco uBR10012 router.
Conditions: This issue occurs on ESR-HH-1GE interface of a Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptoms: It is not possible to configure the 5X1 Gigabit Ethernet port after swapping SPAs.
Conditions: This condition occurs after replacing 24rfchannel-spa-1 card with a SPA-5X1GE-V2 card.
Workaround: Reload the router or OIR the 24rfchannel-spa-1 card with another 24rfchannel-spa-1 card.
•
Symptoms: The Wideband DOCSIS 3.0 modem does not receive MAC Domain Descriptor (MDD) from Cisco uBR10012 router. The Modem falls back to narrowband.
Conditions: This issue occurs on a Cisco uBR10-MC5X20H line card.
Workaround: Remove the downstream modular-cable configuration from the cable interface and then reinstall the line card. Another workaround is to reload the line card.
•
Symptoms: A crash may occur on the Cisco uBR10-MC5X20H line card due to Internet Protocol Communications (IPC) timeout.
Conditions: This issue occurs as the PRE module crashes due to a IPC time out.
Workaround: There is no workaround.
•
Symptoms: A message indicating duplicate frequencies are configured on the integrated-cable controllers is required.
Conditions: This is required during migration of the Cisco uBR10-MC5X20H line card to the Cisco UBR-MC20X20V line card.
Workaround: The downstream rf-channel assignment mapping needs to be done prior to migration.
•
Symptoms: The secondary port does not become active.
Condition: This issue occurs on a Cisco uBR10012 router with Downstream External PHY Interface (DEPI) control plane configured.
Workaround: There is no workaround.
•
Symptoms: Static group and session is not created when static multicast group and source address exists in cable modem configuration file.
Conditions: This issue occurs when you specify the static multicast group and source address in cable modem configuration file.
Workaround: There is no workaround.
•
Symptoms: Excessive unicast and multicast packet loss is seen on a Wideband SPA switchover.
Conditions: This issue occurs on a Wideband SPA GigabitEthernet interface. The switchover takes 70 seconds to converge.
Workaround: There is no workaround.
•
Symptoms: The router shows high CPU utilization for 1 to 2 minutes after issuing privilege interface commands. Similarly, the router is taking a long time to reload, after saving the configuration changes.
Conditions: This issue has been observed while using privilege interface commands on uBR10012 router running Cisco IOS Release 12.2(33)SCB5.
Workaround: Avoid using privilege interface commands.
•
Symptoms: The DOCSIS 3.0 cable modem goes offline after giving the test cable dcc command with a ranging technique of 1.
Conditions: This issue occurs when the test cable dcc command is issued with a ranging technique of 1.
Workaround: There is no workaround.
•
Symptoms: The Wideband SPA is not performing Address Resolution Protocol (ARP) after the failure of the active port.
Conditions: This issue occurs under normal operating conditions.
Workaround: There is no workaround.
•
Symptoms: The cable modems go offline on a port.
Conditions: This issue is seen on the downstream PHY on the cable line cards
Workaround: Reload the line cards.
•
Symptoms: The upstream-service-group is getting removed from mac-domain after the line card and PRE switchover.
Conditions: This issue has been observed following the UBR-MC20X20V line card and PRE switchover on Cisco IOS Release 12.2(33)SCD.
Workaround: There is no workaround.
•
Symptoms: PRC_CONFIG_CHANGE is returned instead of the PRC_CONFIG_NO_CHANGE.
Conditions: This issue occurs when cable admission-control ds-bandwidth and cable admission-control us-bandwidth commands are given for the second time in global or interface configuration mode.
Workaround: There is no workaround.
•
Symptoms: Minor alarm on the uBR10012 router when the cable line card is administratively down.
Conditions: This issue has been observed on the uBR10012 router with Cisco IOS Releases 12.3(23)BC08 and 12.2(33)SCB5.
Workaround: Reload the router.
•
Symptoms: PRE4 shows high-rate of IPC errors consistently.
Conditions: This issue occurs under normal operating conditions.
Workaround: There is no workaround.
•
Symptoms: All cable modems under a single upstream are suddenly moving to expire(pt) state.
Conditions: This issue occurs on a uBR10012 router running Cisco IOS Release 12.2(33)SCB3. The other upstreams on the same line card are not affected.
Workaround: The modems do not recover automatically. Run shut/no shut on the upstream to restore CMs.
•
Symptoms: The route processor crashes when polling for cefFESelectionEntry.
Conditions: This issue occurs after performing the following steps:
1.
2.
3.
4.
5.
The router crashes following the query.
Workaround: Configure a new bundle with a different bundle index. Do not reuse a removed bundle.
•
Symptoms: Multicast data traffic is not forwarded to VRF group.
Conditions: This issue occurs when Multicast Virtual Private Network (MVPN) is set up.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR-MC8X8V cable interface line card may crash.
Conditions: This issue occurs while trying to access an active multicast session key using show interface key sid command with multicast sids on a Cisco uBR7200 series router.
Workaround: Do not use multicast sids.
•
Symptoms: System Event Archive (SEA) console feature is enabled on the PRE4.
Conditions: This issue occurs when the SEA feature is present in the IOS image.
Workaround: Delete the sea_console.dat file present on the PRE4 bootflash.
•
Symptoms: The "ARP-3-STCKYARPOVR: Attempt to overwrite Sticky ARP entry" message is logged as a higher severity level error.
Conditions: This issue has been observed while the router tries to overwrite the sticky ARP entry.
Workaround: There is no workaround.
•
Symptoms: A bus error occurs on uBR10012 router running Cisco IOS Release 12.2(33)SCC.
Conditions: This issue occurs when SNMP getNext query was in progress for the docsIf3CmtsCmRegStatusEntry MIB object.
Workaround: There is no workaround.
•
Symptoms: Tracebacks occur after the Hot Standby Connection-to-Connection Protocol (HCCP) failover and revertback of the line card.
Conditions: This issue occurs after a line card reset, and an HCCP failover and revertback of the line card.
Workaround: There is no workaround.
•
Symptoms: RNE incomplete. mailed Anjum Khurshid (akhurshi) for input.
Conditions: .
Workaround: AWAITING INPUT.
•
Symptoms: The output of the show interface service flow counter command shows wrong result.
Conditions: This issue has been observed on following conditions:
1.
2.
Workaround: This is a display issue and the actual traffic goes through the right service flow.
•
Symptoms: The CMTS crashes due to a bus error.
Conditions: This issue occurs only when the PRE is out of memory.
Workaround: There is no workaround.
•
Symptoms: The modulation profile preamble length for internal usage code (IUC) types, station, and initial becomes very large.
Conditions: This issue has been observed on the uBR10012 routers with uBR10-MC5X20H-D and UBR-MC20X20V-D line cards on Cisco IOS Release versions 12.2(33)SCC and 12.3(23)BC.
Workaround: Use a different modulation profile.
•
Symptoms: Memory leak and traceback occurs when large number of modems are reset from the Cisco uBR10-MC5X20H line cards.
Conditions: This issue has been observed after the resetting large number of modems when they are provisioned with Baseline Privacy Interface Plus (BPI+) enabled DOCSIS configuration.
Workaround: Provision the cable modems with non-BPI configuration file.
•
Symptoms: The "service unsupported-transceiver" configuration on a PRE4 is not available.
Conditions: This issue has been observed only on PRE running the Cisco IOS Releases 12.2(33)SCB5, 12.2(33)SCC, and 12.2(33)SCD.
Workaround: There is no workaround.
•
Symptoms: All cable modems on adjacent downstreams (0 and 1, or 2 and 3, or 4) are offline.
Conditions: The downstream ports that share JIB may be nonfunctional if the JIB that services both downstream ports are locked.
Workaround: Reload the line card.
Resolved Caveats—Cisco IOS Release 12.2(33)SCD
•
Symptoms: Cable modem drops offline during In-Service Software Upgrade (ISSU) procedure for line card upgrade.
Conditions: This issue occurs after performing the following steps:
1.
2.
3.
4.
5.
6.
7.
Workaround: There is no workaround.
•
Symptoms: Router crashes while trying to delete files from corrupt Analog Telephone Adaptor (ATA) disk.
Conditions: This issue occurs when the ATA disk is corrupted. The ATA disk displays "Cluster chain broken on file" message during access.
Workaround: There is no workaround.
•
Symptoms: OIR upgrade from uBR10-MC5X20S/U/H line card to UBR-MC20X20V line card fails when Data-over-Cable Service Interface Specifications (DOCSIS) mode is Annex A and the spectrum range is 5-65 Mhz. All the cable interfaces are placed in `administratively down' state and the following error messages may be seen:
%UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/0.%UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/1.%UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/2.%UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/3.%UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/4.Conditions: This issue occurs when Annex A is configured on the downstream and spectrum range of 5-65 Mhz is configured on the upstream of a uBR10-MC5X20S/U/H line card.
Workaround: Follow the steps given below:
1.
2.
3.
4.
5.
Note
Open Caveats—Cisco IOS Release 12.2(33)SCB6
•
Symptoms: Cable modem is stuck in init(d) state before coming online.
Conditions: This issue occurs when a cable modem (CM) is provisioned using an external DHCP server. The CM takes some hours to initialize.
Workaround: Perform a cable card reset.
•
Symptoms: All the routers are synchronized to one router and displays the following message every 10 seconds:
Apr 23 13:33:41.929: %SYS-3-TIMERNEG: Cannot start timer (0x7543D68) withnegative offset (-996736100).-Process= "TTY Background", ipl= 0, pid= 42Conditions: This issue is observed on some Cisco gigabit switch routers (GSRs) running Cisco IOS Releases 12.0(28)S, 12.0(31)S, 12.0(32)S, and 12.0(32)SY.
The issue occurs when a telnet session is initiated on the router, and then a new telnet session to a different device is initiated from the same telnet session.
When you log into a router through telnet, and then open another telnet session in a different location, the exec-timeout does not disconnect the session even if no keystrokes are issued. At the exact moment the timeout expires, the error message is displayed every 10 seconds.
Workaround: Use the show users command to determine which users are logged in through telnet. Then use the clear line X command to clear the line, disconnect the users, and stop the error messages.
•
Symptoms: The clear cable modem command does not reset the modular-host tables.
Conditions:
–
–
–
After you execute this command, all the stat/BPI/PHS indexes in the modular-host tables are expected to be freed, but are not freed.
This causes a leak in the stat/BPI/PHS indexes and raises a Cable Modem Transmission System (CMTS) scalability issue, that is, CMTS is unable to support the stated number of modems online from the SPA downstream.
Workaround: There is no workaround.
•
Symptoms: The file system device returns a pseudo-positive value when the file system fails. This results in the file operation being displayed as successful even though it failed.
Conditions: This issue occurs when the file system device displays an error, but the code follows the path in the file system buffer cache, where the error is masked. The device error could occur if the code was written on damaged media or during online insertion and removal (OIR) of a line card.
Workaround: There is no workaround.
•
Symptoms: The active DOCSIS queues remain active in the event of a DOCSIS SPA failure.
Conditions: This issue is observed if there are modems online and passing traffic on the modular-cable and/or on wideband-cable interfaces and the DOCSIS SPA fails, the DOCSIS queues associated with these online modems remain active attempting to dequeue.
Workaround: Execute the microcode reload pxf command.
•
Symptom: When attempting to upgrade a Cisco uBR10012 router from Cisco IOS Release 12.3(21)BC to Cisco IOS Release 12.2(33)SCB, the primary PRE may crash.
Conditions: This issue is seen when the CMTS is running Cisco IOS Release 12.3(21)BC and while upgrading to Cisco IOS Release 12.2(33)SCB. The CMTS must then be powered down and physically reconfigured to run as a M-CMTS (Cisco SIP-600 inserted, WB SPAs inserted, DTCCs inserted, so on.). Lastly, the CMTS must be turned on to run its new Cisco IOS Release 12.2(33)SCB IOS image and physical configuration.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000 series PRE 2 running crashes the Cisco IOS Release 12.3(23)BC6.
Conditions: This issue is observed when the PRE 2 is running the Cisco IOS Release 12.3(23)BC6 software, enabling ESR-HH-1GE. The cable source-verify dhcp command is executed but no cable line card is configured or inserted.
This issue occurs in Cisco IOS Releases 12.3(23)BC, 12.3(21a)BC, and 12.2(33)SCB.
Workaround: Configure or insert the cable line card in the Cisco CMTS.
•
Symptoms: After a reconfigure of "member subslot x/y working" and switchover of the line card, the CM does not come online.
Conditions: This issue is observed when you configure "member subslot x/y working" twice.
Workaround: Ensure that you configure "member subslot x/y working" only once. Do not reconfigure it.
•
Symptoms: Cable modems do not respond to layer 3 pings.
Conditions: This issue is observed only on the Cisco uBR10-MC5X20S/U line cards and when PRE-EQ (equalization-coefficient) is configured.
Workaround: Restart the cable line card.
•
Symptoms: A multicast QoS session is not automatically created when changing group configuration or GQC.
Conditions: This issue is seen when a multicast QoS group is configured on a bundle interface and a matching static-group is defined. However, any change in the group configuration after it is applied to the bundle interface is not taken into effect, and the original multicast QoS session is removed.
Workaround: Remove the multicast QoS session from the bundle interface and re-apply it to the bundle.
•
Symptoms: Alignment traceback messages are found when the show memory leak res user and show buffer usage commands are executed.
Conditions: This issue occurs when the show memory leak res user and show buffer usage commands are executed in Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed due to SID management task.
Conditions: This issue is observed when the packetcable calls are present.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed on the line card due to MAC parser with overnight PC calls.
Conditions: This issue occurs after making overnight PC calls.
Workaround: There is no workaround.
•
Symptoms: OIR of a PCMCIA flash disk can cause a watchdog reset of the PRE.
Conditions: This issue is observed during OIR of the PCMCIA flash disk that is being actively accessed.
Workaround: Restrict the removal of PCMCIA flash disks.
•
Symptoms: There may be sporadic short losses (of a few minutes) of multiple CMs going off on a (random) upstream. These losses are usually accompanied by a spike of the error per second rate or by an MER drop and a decrease in docsIfSigQUnerroreds.
However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.
Conditions: This issue is observed on Cisco uBR10-MC5X20H line cards.
Workaround: There is no workaround.
•
Symptoms: Entries in docsBpi2CmtsMulticastObjects duplicate after the line card revertback.
Conditions: This issue is observed when a cable match command is configured with BPI. The IGMP join is received for the group in cable match command and the docsBpi2CmtsMulticastObjects is populated. This results in the line card switchover and revertback.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000 PRE CPU goes to 100% when the FPGA on the Wideband SPAs plugged into a Cisco SIP-600 are being upgraded.
Conditions: This issue only occurs during the SPA FPGA upgrade process.
Workaround: There is no workaround.
•
Symptoms: The cable modems (CMs) that are not capable of downstream bonding are expected to come online on downstreams that are not part of a bonding group. Non-bonding capable CMs are wrongly registered in bonded channels.
Conditions: This issue occurs when the cable service attribute non-ds-bonded downstream-type bonding-disabled command is configured on the Cisco CMTS.
Workaround: There is no workaround.
•
Symptoms: Active PRE fails over to the secondary reporting:
ACTIVE RP WATCHDOG TIMEOUT TRIGGEREDConditions: This issue was first observed on Cisco IOS Release 12.3(23)BC7.
Workaround: There is no workaround.
•
Symptoms: While configuring the cable upstream docsis-mode command using SNMP, the standby PRE module does not synchronize with this configuration.
Conditions: This issue occurs when configuring the cable upstream docsis-mode command using SNMP.
Workaround: Configure the cable upstream docsis-mode command using the CLI instead of SNMP.
•
Symptoms: The show interface multicast-session command may show erroneous multicast session instances.
Conditions: This issue occurs when:
–
–
–
Workaround: There is no workaround.
•
Symptoms: The Cisco Wideband SPA does not transmit traffic. The EQAM indicates no input traffic.
Conditions: This issue is seen on the Cisco SIP-600 with a PRE4 module, 5 x1 GigabitEthernet interface, and SPA-24XDS-SFP Wideband SPAs.
Workaround: Perform a PRE module reload.
•
Symptoms: Around 60 to 70 bytes of buffer memory space is allocated when the protect line card becomes active after a system bootup.
Condition: This issue occurs during a line card switchover.
Workaround: There is no workaround.
•
Symptoms: After PRE switchover, the service flow counter shows 0 on the Cisco uBR10012 router.
Conditions: This issue occurs during a PRE switchover.
Workaround: There is no workaround.
•
Symptom: No system log or SNMP trap is generated when the COPS process that is used for packetcable, fails.
Conditions: This issue is observed in a packetcable environment.
Workaround: There is no workaround.
•
Symptoms: Executing the term len 0 and show cable modem commands pauses the generated output randomly for up to a second on PRE4 module with hundreds of CMs.
Conditions: This issue occurs on PRE4 module with hundreds of CMs.
Workaround: There is no workaround.
•
Symptoms: Wideband modems do not come w-online and often flap in Reject(c) state. A telnet into the line card console and IPC troubleshooting reveals IPC issues, such as failure of the "ubr-test-request-api x/y block" for other slots.
Conditions: This issue is observed in the Cisco uBR10012 line card with DOCSIS 3.0 Wideband- setup and Wideband-capable modems.
Workaround: Change the Modular-host subslot in the Modular-Controller configuration. It is recommended that you use the Cisco uBR10-MC5X20H-D line cards. These cards provide better CPU capacity.
You can also reset the hardware-module subslot x/y.
•
Symptoms: The wideband association is displayed incorrectly after the cable power is switched off on all the line cards.
Conditions: This issue is observed when running the following script:
1.
2.
3.
Workaround: There is no workaround.
•
Symptoms: If the packetcable feature is not enabled in the CMTS configuration while conducting the DQoS lite Voice calls, the DiffServ service flows are on the committed information rate (CIR) queue instead of the low latency queuing (LLQ).
Conditions: This issue occurs on all releases of 12.2(33)SCB.
Workaround: Enable the following commands in the CMTS configuration.
–
packetcable authorize vanilla-docsis-mta
•
Symptoms: The write operation fails when a disk card is removed while it is still being updated, or if a disk card contains bad sectors, or does not respond during updation.
Conditions: This issue is observed in the following two conditions:
1.
2.
If you execute the show file system, dir disk, or show disk commands during this period, the system hangs.Workaround: For condition 1, avoid removing the card when the card is being updated.
For condition 2, replace the card with a good card.•
Symptoms: ICCN drops and traffic outage are observed on a tunnel with sessions.
Conditions: This issue is observed during bootup or SUP SSO on RFGW.
Workaround: There is no workaround.
•
Symptoms: The write operation fails when a disk card is removed while being updated, has some bad sectors, or does not respond when the card is being updated.
Conditions: This issue is observed in the following two conditions:
1.
2.
Workaround: For condition 1, avoid removing the card when the card is being updated. For condition 2, replace the bad card with a good card.
•
Symptoms: The Cisco uBR10-MC5X20S/U/H card crashes multiple times with the following message in the crashinfo file:
Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0x6038C709Conditions: This issue has been observed on the Cisco uBR10012 router with PRE2 module.
Workaround: There is no workaround.
•
Symptoms: On a Cisco uBR10000 cable line card, the show memory debug leak command displays a large number of buffer leaks for SA-MAP request count.
Conditions: This issue occurs when a number of SA-MAP requests are received from multiple modems connected on the line card.
Workaround: There is no workaround.
•
Symptoms: The Cisco IOS Release 12.3(33)SCB crashes if the Cisco UBR-MC20X20V card is added or removed from the redundancy configuration.
Conditions: This issue is observed when the line card type is unknown and the line card redundancy is configured.
Workaround: There is no workaround.
•
Symptoms: The internal accounting of the number of MAC domains is incorrect.
Conditions: This issue is observed only on boot up and affects only Cisco IOS Release 12.2(33)SCC.
Workaround: There is no workaround.
•
Symptoms: docsIfCmtsChannelUtUtilzation is not supported for MC/IC interfaces.
Conditions: This issue occurs when you set the MIB objects docsIfCmtsChannelUtilizationInterval and ccwbRFChanUtilInterval, and use the SNMP query for docsIfCmtsChannelUtUtilzation. The results are displayed only for Cisco uBR10-MC28U/MC5X20 downstream channels.
Workaround: Use the object ccwbRFChannelUtilization for MC/IC interfaces instead.
•
Symptoms: Tracebacks occur when the bundle secondary ip address is removed.
Conditions: This issue occurs when you configure and remove the bundle secondary ip address.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10-MC5X20H line card may crash after reporting memory allocation failures.
Conditions: This issue is observed when multiple memory allocations failures occur.
Workaround: There is no workaround.
•
Symptom: The redzone of the memory block is corrupted. The following output in the line card console displays the corruption:
validblock_diagnose, code = 1current memory block, bp = 0x1FB53398,memory pool type is Processordata check, ptr = 0x1FB533C8Conditions: This issue is observed when the line card is configured for a specific size.
Workaround: Change the configuration of the mac domain.
•
Symptom: The init-tech-ovr command in LBG does not work for the second logical channel.
Conditions: This issue is observed when the second logical channel is selected as the source channel.
Workaround: There is no workaround.
•
Symptoms: When configuring the IGMP static-group, the CMTS console may hang and eventually crash.
Conditions: This issue is observed when the Group-config is configured before configuring the static-group. This may result in the MQoS config process getting into an infinite loop.
Workaround: Configure the static-group before configuring the Group-Config.
•
Symptoms: The IGMPv3 client may stop receiving multicast traffic after the leave and rejoin commands are executed in quick succession.
Conditions: This issue occurs when leave and join commands are sent in a quick succession before the previous leave is executed on the CMTS. Once the modem is in this state, it will not receive any multicast data even after multiple leave and joins.
Work around: Reset the modem reset and execute a fresh join command.
•
Symptoms: The CLC crashes when a specific 3-way call scenario is initiated.
Conditions: This issue occurs where multi-line ATAs are placed behind CMs in a PCMM setup.
Workaround: There is no workaround.
•
Symptoms: The ETDB and DSID entries are removed during UBR-MC20X20V line card HA.
Conditions: This issue is observed in the Cisco IOS Release 12.2(33)SCC.
Workaround: There is no workaround.
•
Symptoms: Line card crashes after executing the show controllers c5/0/4 tech-support command.
Conditions: This issue is observed on UBR-MC20X20V line cards running the Cisco IOS Release 12.2(33)SCC.
Workaround: There is no workaround.
•
Symptoms: A traceback occurs when confirmation-to-receive (CFR) is configured without being associated with the tunnel.
Conditions: This issue occurs in Cisco IOS Release 12.2(33)SCB.
Workaround: Configure the CFR and associate it with the tunnel using the same command.
•
Symptoms: The BPI index information is missing from the show controller command.
Conditions: This issue occurs if the interface is on working or standalone card.
Workaround: There is no workaround.
•
Symptom: The MIB object snmpwalkoverccsCmFlapTable does not return all the entries.
Conditions: This issue occurs during subsequent reboots where the CMTS does not contain ifindexes, which are after wideband interfaces: narrowband ifindexes.
This issue also occurs if the wideband cables are on the cable flap list.
Workaround: There is no workaround.
•
Symptoms: The operation fails and no DCC is issued when you use docsLoadbal3ChgOverGroupMacAddress, docsLoadbal3ChgOverGroupUsChSet and docsLoadbal3ChgOverGroupCommit to change a CM's upstream through SNMP.
Conditions: This issue is observed only when the CM's downstream is a Modular Cable or Integrated Cable interface and its host Cable interface has no frequency configured.
Workaround: Set docsLoadbal3ChgOverGroupdownFrequency to the appropriate target frequency, even if it is identical to the source. Or, if the use of UCC is acceptable, set docsLoadbal3ChgOverGroupForceUCC to TRUE.
•
Symptoms: The following traceback is seen when unconfiguring the bundle interfaces:
Oct 21 23:40:08.951 PDT: %GENERAL-3-EREVENT: No HWIDB_SB_C10K_TT-Traceback= 60A32A5C 6182EEE0 619159A0 61916248 6019EEFC 601936C0 60198EE0 60AADBB0 60A91CF4 60A9CCA8 609B8940 601384B4 609E4628 60B2E6B8 60B2E6A4Conditions: This issue occurs when a complicated testing case runs scripts in which all bundle interfaces are unconfigured.
Workaround: There is no workaround.
•
Symptoms: Attribute-based service flow assignment does not work.
Conditions: This issue is observed when you change the attribute-mask configuration under wideband-interface after the chassis boots up.
Workaround: Perform a line card switch over and revert back to recover from the problem.
•
Symptom: The multicast traffic does not pass through the modem in wideband interfaces during some line card switchovers.
Conditions: The issue is observed in the following two conditions:
–
–
The second condition affects all line cards.
Workaround: There is no workaround.
•
Symptoms: The DFO retry counter does not rise beyond the number zero.
Conditions: This issue occurs when you execute the cable service attribute ds-bonded downstream-type bonding-enabled [enforce] and then power on/off the wideband cable modem.
Workaround: There is no workaround.
•
Symptom: The object CLAB-TOPO-MIB returns more interface instances compared to the CLI.
Conditions: This issue occurs under normal conditions.
Workaround: Use CLI instead of SNMP to get the fiber-node information.
•
Symptoms: Fiber node is invalid after line card switchover.
Conditions: This issue occurs in a MC-2020 protect 520 case, when one 520 MD is in shutdown state and in fiber node.
Workaround: Ensure that all the 520 MDs configured in MD should not be in shutdown state.
•
Symptoms: The multicast DSID may generate incorrectly and multicast traffic does not reach CPE.
Conditions: This issue is observed when line card high-availability (LCHA) is configured and the static-sync is running.
Workaround: There is no workaround. Once the timer stops (after approximately 30 to 60 seconds of LCHA operation), the subsequent IGMP join populates the DSID and the forwarding functions normally.
•
Symptoms: After LCHA on the Cisco UBR-MC20X20V line card, multicast traffic fails to reach CPE.
Conditions: This issue is observed when the CM is MDF enabled after the Cisco UBR-MC20X20V LCHA.
Workaround: CPE should leave and re-join the group.
•
Symptoms: Number of pre-equalization taps decreases incorrectly after CLC failover.
Conditions: This issue is observed on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB4 with N+1 redundancy.
Workaround: There is no workaround.
•
Symptoms: Polling of the IfHCInOctets and IfHCOutOctets wraps at the 32-bit point for cable interfaces.
Conditions: This issue is observed on Cisco uBR10012 routers running Cisco IOS Release 12.2(33)SCB4.
Workaround: There is no workaround.
•
Symptoms: Cisco uBR10000 series router may experience packet drops on PXF complex when using QoS and the number of connected customers reach approximately eight thousand subscribers.
Conditions: This issue is observed on Cisco uBR10012 routers running Cisco IOS Release 12.2(33)SCB with QoS enabled.
Workaround: There is no workaround.
•
Symptoms: The Entity MIB returns an incorrect OID value for the DTCC card. This means that SNMP applications using the Entity MIB incorrectly classifies the DTCC as a TCC+ card.
Conditions: This issue is observed for an SNMP read operation of the ENTITY-MIB.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(33)SCB6
•
Symptoms: File copy from active PRE2 to standby PRE2 may fail or MD5 checksum may fail while reading a file on the disk.
Conditions: This issue is observed on STI 7.4.0 Compact Flash and PCMCIA Flash cards.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(33)SCC1
•
Symptoms: The Cisco uBR10012 router may generate the following message:
UBR10000-6-BADIPASSIGNMENT: DHCPOFFER dropped : Interface Cablex/y/zMac abcd.efgh.ijkl SID 2205 L3_Interface Cablex/y/z IP x.y.z.talready assigned to MAC=mnop.qrst.uvwx Interface Cablex/y/z SID 6367Conditions: This issue occurs when a cable modem (CM) is provisioned using an external DHCP server. The CM takes some hours to initialize.
Workaround: Reset the cable card to fix the issue.
•
Symptoms: The CPUHOG error message and traceback may be seen on the protect line card of a Cisco uBR10012 router.
Conditions: This issue occurs when the clear cable modem all reset command is executed.
Workaround: There is no workaround.
•
Symptoms: The active DOCSIS queues remain active in the event of a DOCSIS SPA failure.
Conditions: This issue is observed if there are modems online and passing traffic on the modular-cable and/or on wideband-cable interfaces and the DOCSIS SPA fails, the DOCSIS queues associated with these online modems remain active attempting to dequeue.
Workaround: Execute the microcode reload pxf command.
•
Symptoms: CMs do not respond to layer 3 pings.
Conditions: This issue is observed only on the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U cards and when PRE-EQ (equalization-coefficient) is configured.
Workaround: Reset the cable line card.
•
Symptoms: A multicast quality of service (QoS) session is not automatically created when changing group configuration or group QoS configuration (GQC).
Conditions: This issue is observed when a multicast QoS group is configured on a bundle interface and a matching static-group is defined. However, any change in the group configuration after it is applied to the bundle interface is not taken into effect, and the original multicast QoS session is removed.
Workaround: Remove the multicast QoS session from the bundle interface and re-apply it to the bundle.
•
Symptoms: Alignment traceback messages are found after the execution of show memory leak res user and show buffer usage commands.
Conditions: This issue occurs when show memory leak res user and show buffer usage commands are executed.
Workaround: There is no workaround.
•
Symptoms: The service identifier (SID) management task results in a memory leak.
Conditions: This issue is observed when the packetcable calls are present.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed on the line card due to MAC parser with overnight PC calls.
Conditions: This issue is observed when the packetcable calls are present overnight.
Workaround: There is no workaround.
•
Symptoms: OIR of a PCMCIA flash disk can cause a watchdog reset of the PRE module.
Conditions: This issue is observed during OIR of the PCMCIA flash disk that is being actively accessed.
Workaround: Deactivate the features that access the PCMCIA flash disk. These features include:
–
–
–
–
It is recommended that you restrict the removal of PCMCIA flash disks to a maintenance window.
•
Symptoms: There may be sporadic short losses (of a few minutes) of multiple CMs going off on a (random) upstream. These losses are usually accompanied by a spike of the error per second rate or by an MER drop and a decrease in docsIfSigQUnerroreds.
However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.
Conditions: This issue is observed on Cisco uBR10-MC5X20H line cards.
Workaround: There is no workaround.
•
Symptoms: Entries in docsBpi2CmtsMulticastObjects duplicate after the line card revertback.
Conditions: This issue is observed when a cable match command is configured with BPI. The IGMP join is received for the group in cable match command and the docsBpi2CmtsMulticastObjects is populated. This results in the line card switchover and revertback.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000 PRE CPU goes to 100% when the FPGA on the Wideband SPAs plugged into a Cisco SIP-600 are being upgraded.
Conditions: This issue only occurs during the SPA FPGA upgrade process.
Workaround: There is no workaround.
•
Symptoms: The cable modems (CMs) that are not capable of downstream bonding are expected to come online on downstreams that are not part of a bonding group. Non-bonding capable CMs are wrongly registered in bonded channels.
Conditions: This issue occurs when the cable service attribute non-ds-bonded downstream-type bonding-disabled command is configured on the Cisco CMTS.
Workaround: There is no workaround.
•
Symptoms: Active PRE fails over to the secondary reporting:
ACTIVE RP WATCHDOG TIMEOUT TRIGGEREDConditions: This issue was first observed on Cisco IOS Release 12.3(23)BC7.
Workaround: There is no workaround.
•
Symptoms: While configuring the cable upstream docsis-mode command using SNMP, the standby PRE module does not synchronize with this configuration.
Conditions: This issue occurs when configuring the cable upstream docsis-mode command using SNMP.
Workaround: Configure the cable upstream docsis-mode command using the CLI instead of SNMP.
•
Symptoms: The show interface multicast-session command may show erroneous multicast session instances.
Conditions: This issue occurs when:
–
–
–
Workaround: There is no workaround.
•
Symptoms: The Cisco Wideband SPA does not transmit traffic. The EQAM indicates no input traffic.
Conditions: This issue is seen on the Cisco SIP-600 with a PRE4 module, 5 x1 GigabitEthernet interface, and SPA-24XDS-SFP Wideband SPAs.
Workaround: Perform a PRE module reload.
•
Symptoms: The cable dsg tg command configuration is not synched to standby PRE.
Conditions: This issue occurs when the DOCSIS Set-top Gateway (DSG) configuration is done with bundle subinterface.
Workaround: There is no workaround.
•
Symptoms: Around 60 to 70 bytes of buffer memory space is allocated when the protect line card becomes active after a system bootup.
Condition: This issue occurs during a line card switchover.
Workaround: There is no known workaround.
•
Symptoms: After the PRE switchover, the service flow counter displays the value 0. However, the right service flow is used to forward the packets. And also the packets will reach CPEs as well.
Conditions: This issue is observed during a PRE switchover.
Workaround: There is no workaround.
•
Symptoms: No syslog or SNMP trap messages are generated when the Common Open Policy Service (COPS) process for Packet Cable fails.
Conditions: This is occurs in a PacketCable environment where the COPS session fails.
Workaround: There is no workaround.
•
Symptoms: Executing the term len 0 and show cable modem commands pauses the generated output randomly for up to a second on PRE4 module with hundreds of CMs.
Conditions: This issue occurs on PRE4 module with hundreds of CMs.
Workaround: There is no workaround.
•
Symptoms: The wideband association is displayed incorrectly after the cable power is switched off on all the line cards.
Conditions: This issue is observed when running the following script:
1.
2.
3.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR-MC5X20U-D card crashes multiple times with the following message in the crashinfo file:
Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0x6038C709Conditions: This issue has been observed on the Cisco uBR10012 router with PRE2 module.
Workaround: There is no workaround.
•
Symptoms: The modem's accumulated timing-offset goes to a negative value. The following error message is displayed at the CMTS:
%UBR10000-4-BADTXOFFSET: Bad timing offset -182443 detected for cable modem 000a.73cc.c7b7.Conditions: This issue occurs on the Cisco uBR-MC5X20D line card.
Workaround: There is no workaround.
•
Symptoms: The MIB object docsIfCmtsChannelUtUtilzation is not supported on modular cable or integrated cable (MC/IC) interfaces.
Conditions: This issue occurs when you set the MIB objects docsIfCmtsChannelUtilizationInterval and ccwbRFChanUtilInterval, and use the SNMP query for docsIfCmtsChannelUtilization. The results are displayed only for Cisco UBR10- MC28U and Cisco UBR-MC5X20 downstream channels.
Workaround: Use the MIB object ccwbRFChannelUtilization for MC/IC interfaces instead.
•
Symptoms: The Cisco uBR10-MC5x20H line card may crash after reporting memory allocation failures.
Conditions: This issue is observed when multiple memory allocations failures occur.
Workaround: There is no workaround.
•
Symptoms: The 24th MAC Domain Downstream Service Group (MD-DS-SG) is missing in output of show command show cable mac-domain downstream-service-group.
Conditions: This issue occurs when fiber-node configuration has channels in a MAC domain belonging to 24 different fiber-nodes.
Workaround: There is no workaround.
•
Symptoms: Cable line card crashes with PacketCable Multimedia (PCMM) voice call testing.
Conditions: This issue was seen in multi-line Cisco Analog Telephone Adaptor (ATA) behind cable modems (CMs) in a PCMM setup.
Workaround: There is no workaround.
•
Symptoms: Dynamic multicast service flow and reserved bandwidth exist even after removal of multicast QoS (MQoS) configuration from the second bonding group.
Conditions: This issue occurs after a multicast QoS bandwidth reservation oversubscription takes place.
Workaround: Perform a PRE switchover.
•
Symptoms: The MIB object docsIfCmtsCmStatusTable does not display all modem entries as the MIB object docsIf3CmtsCmRegStatusTable.
Conditions: This issue occurs when the modem is in offline state.
Workaround: There is no workaround.
•
Symptoms: The following traceback is seen when unconfiguring the bundle interfaces:
Oct 21 23:40:08.951 PDT: %GENERAL-3-EREVENT: No HWIDB_SB_C10K_TT-Traceback= 60A32A5C 6182EEE0 619159A0 61916248 6019EEFC 601936C0 60198EE0 60AADBB0 60A91CF4 60A9CCA8 609B8940 601384B4 609E4628 60B2E6B8 60B2E6A4Conditions: This issue occurs when a complicated testing case runs scripts in which all bundle interfaces are unconfigured.
Workaround: There is no workaround.
•
Symptoms: The WB association is incorrect after line card switchover and hardware reset.
Conditions: This issue occurs when a series of power-off/power-on operations are performed on the working and protect line cards.
Workaround: There is no workaround.
•
Symptom: The MIB object CLAB-TOPO-MIB returns more interface instances compared to the CLI.
Conditions: This issue occurs under normal conditions.
Workaround: Use CLI instead of SNMP to get the fiber-node information.
•
Symptoms: The Layer2 VPN failed to forward ARP traffic on Cisco uBR10012 router.
Conditions: This issue occurs while sending traffic through Layer2 VPN.
Workaround: There is no workaround.
•
Symptom: The classifiers for Cisco DPC2607 CPE types correctly identifies the CPE, but the filters are not effective in filtering the packets from these devices.
Conditions: This issue occurs in normal operations of the cable plant. Some CPEs do not behave properly and send an ARP before sending a DHCP Discover message. This causes the CPE to be populated in the CMTS database as an "Unknown" device type. Once the CPE sends the DHCP discover message, the device type is updated in the software, but the hardware entries are still categorized as "Unknown".
Workaround: There is no workaround.
•
Symptoms: The "Total DS/US pkts/bytes" counters displayed by the show cable l2-vpn xconnect dot1q-vc-map verbose command are inconsistent on Cisco uBR10012 router.
Conditions: This issue occurs when DOCSIS SF-based 802.1Q mapping L2VPN is configured.
Workaround: There is no workaround.
•
Symptoms: The RNG-RSP sends inaccurate timing offset values after the US redirection.
Conditions: This issue is observed when the CM aligns itself to the timing offset according to the values in the RNG-RSP, but the CMTS does not receive the RNG-request. Therefore, the CM does not receive any RNG-RSP.
Workaround: Apply the modem firmware patch.
•
Symptoms: Spurious memory accesses and tracebacks observed after a ping time out.
Conditions: This issue was first observed in Cisco 12.2(33)SCB5 release.
Workaround: There is no workaround.
•
Symptoms: Number of pre-equalization taps decreases incorrectly after CLC failover.
Conditions: This issue is observed on a Cisco uBR10000 router running Cisco IOS Release 12.2(33)SCB4.
Workaround: There is no workaround.
•
Symptoms: A wideband Baseline Privacy Index (BPI) error is seen.
Conditions: This issue occurs on a UBR10-MC20X20 line card switchover when multicast traffic was sent.
Workaround: There is no workaround.
•
Symptoms: Cisco Wideband SPA sends only "sync Tx" packets.
Conditions: This issue is observed after Cisco Wideband SPA reload and when a DTI server is used.
Workaround: Reload the jacket card r
•
Symptoms: Traceback is seen during auto-upgrade of DOCSIS Timing, Communication and Control (DTCC) card firmware.
Conditions: This issue occurs on a firmware upgrade of DTCC card.
Workaround: There is no workaround.
•
Symptoms: The cable clock dti command is does not work.
Conditions: This issue occurs when the system starts with two DTCC cards, and one card is unplugged during the run time.
Workaround: There is no workaround.
•
Symptom: The following items of the MIB object docsIfCmtsCmStatusTable are not supported on DOCSIS 3.0 online cable modem. This is because these objects rely on single upstream channel while the online DOCSIS 3.0 cable modem has many upstream channels.
–
–
–
–
–
–
docsIf3CmtsCmUsStatusTable has following objects:
–
–
–
–
–
–
Conditions: This issue occurs when there is an online DOCSIS 3.0 modem.
Workaround: There is no workaround.
•
Symptoms: Generic Routing Encapsulation (GRE) tunnel does not forward traffic.
Conditions: This issue occurs when a new GRE tunnel is created on a Cisco uBR1012 router.
Workaround: Execute the shutdown and the no shutdown commands on the tunnel interface.
•
Symptoms: The IGMPv3 CPE behind the DOSCSIS 3.0 main distribution frame (MDF) capable modem using local integrated-cable downstream interface as primary fails to receive any multicast traffic after the UBR10-MC20X20 line card switchover occurs due to DSID change.
Conditions: The UBR10-MC20X20 line card fails to receive traffic after a switchover.
Workaround: There is no workaround.
•
Symptoms: The debug output to the terminal is curtailed when "logging discriminator" is enabled.
Conditions: This issue was observed in Cisco IOS Release 12.2(33)SCB5.
Workaround: There is no workaround.
•
Symptoms: Flow-control does not work on ESR-HH-1GE interface of a Cisco uBR10012 router.
Conditions: This issue occurs on ESR-HH-1GE interface of a Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptoms: The MIB object docsDevEvReporting does not display the local volatile bit.
Conditions: This issue occurs as the MIB object ignores bits from 3 to 7. When the 3rd bit is set, the local volatile is not set.
Workaround: There is no workaround.
•
Symptoms: The Wideband DOCSIS 3.0 modem does not receive MDD from Cisco uBR10012 router. The Modem falls back to narrowband.
Conditions: This issue occurs on a Cisco uBR10-MC5x20H line card.
Workaround: Remove the downstream modular-cable configuration from the cable interface and then reinstall the line card. Another workaround is to reload the line card.
•
Symptoms: The show tech command does not include contents of show controller integrated-cable x/y/z for the Cisco UBR10-MC20X20 cable line card.
Conditions: This issue occurs on the Cisco UBR10-MC20X20 cable line card.
Workaround: Execute the show controller integrated-cable x/y/z command after the executing the show tech command.
•
Symptoms: The PRC_CONFIG_CHANGE change-type is displayed while configuring privacy related commands.
Conditions: This issue occurs when terminal prc expose is enabled on theCisco uBr10012 router.
Workaround: There is no workaround.
•
Symptom: The show inventory command displays the Cisco UBR10-MC5X20T line card when a Cisco uBR10-MC5x20H line card is pre-provisioned in the configuration
Conditions: This issue occurs when the show inventory command is executed during the pre-configuration of hardware.
Workaround: Use the output of show diag command to determine the installed hardware.
•
Symptoms: A crash may occur on the Cisco uBR10-MC5X20H line card.
Conditions: This issue occurs as the PRE module crashes due to a IPC time out.
Workaround: There is no workaround.
•
Symptoms: The upstream service flow is rejected although the reserved bandwidth and the requested bandwidth is lesser than max-reserved-bandwidth.
Conditions: This issue is triggered if the admission control (AC) event is not configured, but AC max-reserved-bandwidth and AC threshold are configured.
Workaround: Do not configure the AC threshold if the AC event is not configured.
•
Symptoms: The standby PRE2 module may keep getting automatically reset due to PEER_INIT_TIMEOUT.
Conditions: This issue occurs when the standby PRE2 module is normalized for more than 100 times.
Workaround: Power cycle of the Cisco uBR10012 chassis.
•
Symptoms: The high availability Baseline Privacy Index (BPI) TEK encryption key sync occurs repeatedly.
Conditions: This issue occurs when BPI is enabled.
Workaround: There is no workaround.
•
Symptoms: Upgrading a Cisco uBR10012 router from Cisco IOS Release 12.2(33)SCB4 to Cisco IOS Release SCB5 may result in the following series of messages, resulting in the Cisco SIP-600 becoming unresponsive:
Dec 1 09:23:13.443 CST: %IPCOIR-3-CARD_WRONGTYPE: Mismatched card type (4jacket-1) in slot 1/0. Expected type 4jacket-1. Use 'no card 1/0' command to override preprovisioning and update card type.Dec 1 09:23:13.443 CST: %IPCOIR-3-CARD_WRONGTYPE_4JACKET: Discovered card type requries 2 slots. Use 'no card' for slots 1 & 2 to override preprovisioning and update card type.Condition: This issue occurs when the no card 1/0 4jacket-1 option is not present and OIR does not work.
Workaround: Reload the box.
•
Symptom: The Wideband cable modem enters online state but does not enter w-online state, even after executing clear cable modem command.
Conditions: This issue occurs after a Cisco UBR10-MC20X20 line card switchover.
Workaround: There is no workaround.
•
Symptoms: The standby PRE2 module may keep getting automatically reset due to PEER_INIT_TIMEOUT.
Conditions: This issue occurs when the standby PRE2 module is normalized for more than 100 times.
Workaround: Power cycle of the Cisco uBR10012 chassis.
•
Symptoms: The following error messages and tracebacks were displayed followed a redundancy force-failover:
Oct 28 18:00:03.851: %SYS-5-SWITCHOVER: Switchover requested by <removed>on vty0 (10.148.165.21). Reason: redundancy force-failover.Oct 28 18:00:47.360: %SYS-3-CPUHOG: Task is running for (2000)msecs, morethan (2000)msecs (238/95),process = CMTS SID mgmt task.-Traceback= 605176D4 60530A40 6053E838 6211D9E4 6171FE44 6163A2C4 6163AB306163B578 6163B800 616407CC 61640880 6164093C 6171F5F0 60232A50 6034ED0C609F1870Conditions: This issue occurs on a Cisco uBR10012 router with a PRE2 module.
Workaround: There is no workaround.
•
Symptoms: The LinkDown SNMP traps are sent twice instead of once causing some Network Management Systems (NMS) tools to erroneously think the link is still down.
Conditions: This issue occurs when a Wideband SPA or GigabitEthernet interface on the Cisco uBR10012 router goes down or an attached cable is disconnected.
Workaround: There is no workaround.
•
Symptoms: The uBR10-MC5X20H line card is not recognized after a cable power off/on.
Conditions: This issue occurs on a PRE4 module with uBR10-MC5X20H line card.
Workaround: There is no workaround.
•
Symptoms: A message indicating duplicate frequencies are configured on the integrated-cable controllers is required.
Conditions: This is required during migration of the Cisco uBR10-MC5x20H line card to the Cisco UBR10-MC20X20V line card.
Workaround: The downstream rf-channel assignment mapping needs to be done prior to migration.
•
Symptoms: The port does not become active.
Condition: This issue occurs on a Cisco uBR10012 router with DEPI control plane configured.
Workaround: There is no workaround.
•
Symptoms: The Cisco CMTS may incorrectly attempt to load-balance to a disabled interface.
Conditions: This issue occurs in Cisco IOS Release 12.2(33)SCB5.
Workaround: There is no workaround.
•
Symptoms: Excessive unicast and multicast packet loss is seen on a Wideband SPA switchover.
Conditions: This issue occurs on a Wideband SPA GigabitEthernet interface. The switchover takes 70 seconds to converge.
Workaround: There is no workaround.
•
Symptoms: The cable modems go offline on a port.
Conditions: This issue is seen on the downstream PHY on the cable line cards
Workaround: Reload the line cards.
•
Symptoms: The modem may register in partial mode. This is seen when the show cable modem [mac] verbose | inc partial command was executed. The DOCSIS 3.0 modem keeps cycling from offline to "UB init(t)" state, but is unable to register online.
Conditions: These issue occurs in the following conditions:
The PHYv3.0 section 6.2.19 Transmit Power Requirement contains the transmit power budget on per channel basis, derived from the modem transmit channel set, and each individual upstream channel parameters. The existing DOCSIS plant may be designed for single channel DOCSIS 1.x/2.0 modems, which has a much higher maximum transmit power level, comparing to DOCSIS 3.0 modem operating in MTC-mode and having 2 or more channels.
In such a case, the modem may range successfully prior to REGISTRATION, since the modem is still operating with a single channel, like legacy 2.0/1.x modem. As soon as it is transitions to MTC-mode during REG-RESP, its allowable maximum transmit power level is below the ranged reference channel power level, thus causing the above error condition, and modem stop any ranging attempts on the newly assigned channels. Eventually, it fails to register and goes offline. This cycle repeats. This case is only applicable if all upstream channels assigned to the modem channel set are exceeding the peak allowable transmit power level.
If all channel are not exceeding the peak transmit power level, then modem may register in partial mode. The modem may be able to continue to range successfully on the channel(s) that are still within the range, and transmitting data on those channel in partial-mode.
Workaround: For those modems having severe upstream signal lost, and are required to transmit at far beyond the PHY3.0 maximum per channel transmit power budget, they can be individually selected to register in non-bonded mode (non-MTC-mode), as in normal DOCSIS 2.0/1.x modem, for the upstream path. Use the cable modem (CM) config file with the bonded-bit set to off in CM-required-attribute via TLV 43.8 and 43.9; also make sure that the CMTS mtc-mode configuration is the default setting which would enforce the CM required-attribute bonded-bit checking to allow DOCSIS 3.0 modem to register in mtc-mode.
By disabling mtc-mode for these modems, they now have the same maximum transmit power budget as a DOCSIS 2.0/1.x modem would have.
•
Symptoms: The OIR upgrade from a Cisco uBR-MC5X20x line card to Cisco UBRMC20X20V line card fails when DOCSIS mode is Annex A and spectrum range of (5-65 Mhz) is configured.
The failure of the OIR upgrade is seen via messages and all the Cable interfaces will be placed in "administratively down" state.
Jan 14 09:15:20.950: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/0.Jan 14 09:15:20.970: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/1.Jan 14 09:15:20.974: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/2.Jan 14 09:15:20.974: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/3.Jan 14 09:15:20.978: %UBR10K-6-COMPAT_SHUTDOWN_CARD: Failed to restore the configuration for Cable8/0/4.Conditions: This issue occurs when the Annex mode is configured as Annex A on downstream ports of a Cisco uBR-MC5X20x line card and the upstream ports are using spectrum range of 5-65Mhz.
Workaround: The issue is due to increased frequency range supported by Annex A <5-65Mhz> as compared to Annex B <5-55Mhz>. Since the upgrade fails due to increased spectrum range it is advised to
1.
2.
3.
4.
5.
If a spectrum group is configured on the line card, do the following as in the example:
Example: cable spectrum-group 1 band 27000000 65000000 configuration
1.
2.
3.
4.
Note
Resolved Caveats—Cisco IOS Release 12.2(33)SCC1
•
Symptoms: Executing the show commands pushes the CPU utilization to 100%.
Conditions: Long running show commands, such as show running-config, show voice call summary, and show memory summary affect voice call processing adversely, even if they periodically suspend.
Workaround: There is no workaround.
•
Symptoms: A file copy to the standby PRE module fails. The following error may be seen
%Error writing stby-disk0: (TF I/O failed in data-in phase).The MD5 checksum failed when reading a file off the disk.
Conditions: This issue occurred on the STI 7.4.0 Compact Flash and PCMCIA Flash cards.
Workaround: Try copying the file to the disk and the see that MD5 checksum matches the file.
Note
•
Symptoms: The file system device returns a pseudo-positive value when the file system fails. This results in the file operation being displayed as successful even though it failed.
Conditions: This issue occurs when the file system device displays an error, but the code follows the path in the file system buffer cache, where the error is masked. The device error could occur if the code was written on damaged media or during online insertion and removal (OIR) of a line card.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000 series PRE 2 running crashes the Cisco IOS Release 12.3(23)BC6.
Conditions: This issue is observed when the PRE 2 is running the Cisco IOS Release 12.3(23)BC6 software, enabling ESR-HH-1GE. The cable source-verify dhcp command is executed but no cable line card is configured or inserted.
This issue occurs in Cisco IOS Releases 12.3(23)BC, 12.3(21a)BC, and 12.2(33)SCB.
Workaround: Configure or insert the cable line card in the Cisco CMTS.
•
Symptoms: The Cisco uBR10012 router crashes with an address error (load or instruction fetch) exception.
Conditions: This issue occurs when router is configured to act as a DHCP client.
Workaround: There is no workaround.
•
Symptoms: Tracebacks appears while unconfiguring cable service attribute non-ds-bonded downstream-type bonding-disabled and cable fiber node.
Conditions: This issue occurs when the cable service attribute non-ds-bonded downstream-type bonding is disabled.
Workaround: There is no workaround.
•
Symptoms: The cable dsg tg command configuration is not synched to standby PRE.
Conditions: This issue occurs when the DOCSIS Set-top Gateway (DSG) configuration is done with bundle subinterface.
Workaround: There is no workaround.
•
Symptoms: All WCMs on Wideband SPA unexpectedly go offline and never tried ranging.
During this period, the SPA sends out only the SYNC packets, and not packets from MC520 (MDD, secondary MDD, UCD, MAP, and so on).
Conditions: This issue is observed in 3-Channel bonding with DTI.
Workaround: Online insertion and removal of the SPA might resolve this issue.
•
Symptoms: Wideband modems do enter the w-online state and are often flapping in reject(c) state. IPC troubleshooting reveals IPC issues such as ubr-test-request-api x/y block commands fails.
Condition: This issue occurs on a Cisco ubR10012 router with DOCSIS 3.0 Wideband configured on Wideband-capable modems.
Workaround: Change the modular-host subslot in the modular-controller configuration. It is recommended that you use the Cisco uBR10-MC5X20H-D line cards as these cards provide better CPU capacity. You can also execute the hw-module subslot x/y reset command.
•
Symptoms: The following system event message is not displayed in the receiving syslog server:
wbcmts_idxtbl_assign(): failed. Tbl fullConditions: This issue occurs in rare, severe error conditions, which cause the Stats index table to become full. When this condition persists, other symptoms like modems failing to come online or falling offline after coming online are observed.
Workaround: There is no workaround.
•
Symptoms: When transmitting distributed QoS (DQoS) Lite voice calls, the downstream service flows are listed on the committed information rate (CIR) queue instead of Low Latency Queuing (LLQ), if PacketCable is not enabled in the Cisco CMTS configuration
Conditions: This issue occurs when the PacketCable is not configured on the Cisco CMTS and DQoS Lite or vanilla DOCSIS voice calls are performed.
Workaround: Configure the following commands:
–
–
The above commands do not impact the current configuration.
•
Symptoms: The show memory debug leak command shows a large number of buffer leaks for the Security Association (SA) map request count.
Conditions: This issue occurs when a large number of SA map requests are received from multiple modems connected on the line card.
Workaround: There is no workaround.
•
Symptoms: SNMP traps and informs source interface do not work.
Conditions: This issue occurs when the snmp-server trap-source Loopback0 and snmp-server source-interface informs Loopback0 commands are configured.
Workaround: There is no workaround.
•
Symptoms: Tracebacks occur when the bundle secondary ip address is removed.
Conditions: This issue occurs when you configure and remove the bundle secondary ip address.
Workaround: There is no workaround.
•
Symptoms: Although the 128 bits-aes encryption algorithm is configured, the 56 bit-des encryption algorithm is used for encrypting multicast traffic. The CPE does not receive packets.
Conditions: This issue occurs when group-encryption algorithm is configured with 128bits-aes algorithm.
Workaround: Use the 56bits-des encryption algorithm.
CSCtc55329
•
Symptom: The redzone of the memory block is corrupted. The following output in the line card console displays the corruption:
validblock_diagnose, code = 1current memory block, bp = 0x1FB53398,memory pool type is Processordata check, ptr = 0x1FB533C8Conditions: This issue is observed when the line card is configured for a specific size.
Workaround: Change the configuration of the MAC domain.
•
Symptom: The init-tech-ovr command in LBG does not work for the second logical channel.
Conditions: This issue is observed when the second logical channel is selected as the source channel.
Workaround: There is no workaround.
•
Symptoms: When configured peak-rate is high relative to max-sustained-rate, it is difficult to burst to peak-rate level. If rate shaping is triggered when multiple sid-cluster are configured, the modem may not use the delayed grant.
Conditions: This issue occurs when large peak rate and max-sustain rate are configured, multiple sid clusters are configured and rate shaping is triggered.
Workaround: There is no workaround.
•
Symptoms: A traceback occurs when confirmation-to-receive (CFR) is configured without being associated with the tunnel.
Conditions: This issue was first observed in Cisco IOS Release 12.2(33)SCB.
Workaround: Configure the CFR and associate it with the tunnel using the same command.
•
Symptoms: Cable modems using remote downstream drop during ISSU-RUNVERSION and they never recover.
Conditions: This issue occurs when the system is executing In Service Software Upgrade (ISSU), and is upgrading to an image that requires minor Minimum Disruptive Restart (MDR) process, and if the system is configured to use DEPI control plane via the Wideband DOCSIS SPA.
Workaround: Reset the DEPI connection.
•
Symptoms: An error message similar to the following may be seen:
Oct 19 10:57:06.234 PDT: %ALIGN-3-TRACE: -Traceback= 60430234 60663EF0 60664378 00000000 00000000 00000000 00000000 00000000The Traceback decode will have wbcmts_guardian_check_periodic(0x60430178)+0xbc at the top of stack.
Conditions: This issue occurs in a routine that runs periodically through a timer. This error may be seen during OIR of a card, card failure, etc.
Workaround: There is no workaround.
•
Symptoms: The show cable modem docsis command incorrectly counts UB modem.
Conditions: This issue occurs when the upstream channel has modem operating in MTC-mode.
Workaround: There is no workaround.
•
Symptoms: Memory leak in buffers from the header buffer pool may be observed.
Conditions: This issue occurs when lots of traffic is being Cisco Express Forwarding (CEF) switched on the PRE. It is not specific to any particular type of interface or PRE.
Workaround: Reload or do a forced switchover to clear the memory buffer leak.
•
Symptoms: A Cisco IOS device may experience an unexpected reload.
Conditions: This issue occurs due to "mtrace" packet processing.
Workaround: Avoid using mtrace functionality.
•
Symptom: The MIB object snmpwalkoverccsCmFlapTable does not return all the entries.
Conditions: This issue occurs during subsequent reboots where the CMTS does not contain ifindexes, which are after wideband interfaces: narrowband ifindexes.
This issue also occurs if the wideband cables are on the cable flap list.
Workaround: There is no workaround.
•
Symptoms: The operation fails and no DCC is issued when you use docsLoadbal3ChgOverGroupMacAddress, docsLoadbal3ChgOverGroupUsChSet and docsLoadbal3ChgOverGroupCommit to change a CM's upstream through SNMP.
Conditions: This issue is observed only when the CM's downstream is a Modular Cable or Integrated Cable interface and its host Cable interface has no frequency configured.
Workaround: Set docsLoadbal3ChgOverGroupdownFrequency to the appropriate target frequency, even it is identical to the source. Or, if the use of UCC is acceptable, set docsLoadbal3ChgOverGroupForceUCC to TRUE.
•
Symptoms: CPUHOG and traceback may be observed.
Conditions: This issue occurs when large number of cable modems (CM)s are present on a particular cable interface, and executing the shutdown and no shutdown commands on the upstream channel.
Workaround: There is no workaround.
•
Symptom: The multicast traffic does not pass through the modem in wideband interfaces during some line card switchovers.
Conditions: The issue is observed in the following two conditions:
–
–
This issue affects all line cards.
Workaround: There is no workaround.
•
Symptoms: The DFO retry counter does not rise beyond the number zero.
Conditions: This issue occurs when you execute the cable service attribute ds-bonded downstream-type bonding-enabled [enforce] and then power on/off the wideband cable modem.
Workaround: There is no workaround.
•
Symptoms: Some memory leaks are observed on both active standby and protect card.
Conditions: This issue is seen on a line card switchover from standby to protect with some multicast clients receiving a multicast session.
Workaround: There is no workaround.
•
Symptoms: Fiber node is invalid after line card switchover for a Cisco UBR10-MC20X20 line card, protect Cisco uBR10-MC5X20 line card.
Conditions: This issue occurs in a Cisco UBR10-MC20X20 line card protect Cisco uBR10-MC5X20 line card case, when one Cisco uBR10-MC5X20 line card MAC domain (MD) is in shutdown state.
Workaround: Ensure that all the Cisco uBR10-MC5X20 line card MDs configure, are not in shutdown state.
•
Symptoms: Cisco Broadband Troubleshooter (CBT) 3.3 continuous sweep function fails after some time when performed on Cisco uBR10000 series routers with PRE4 line cards.
Conditions: This issue was first observed in Cisco IOS Release 12.2(33)SCB4. This issue occurs as a result of the following MIB object returning a value of "10":
CISCO-CABLE-SPECTRUM-MIB::ccsSpectrumRequestTable - ccsSpectrumRequestOperStateWorkaround: There is no workaround.
•
Symptoms: The cable filter group command fails to be displayed in the show running-config command output.
Conditions: This issue occurs when the cable filter group command was generated.
Output: Re-issue the cable filter group command.
•
Symptoms: Memory leaks are observed on both the working and protect Cisco UBR10-MC20X20 line cards, with multicast session with clients configured.
Conditions: This issue occurs on a Cisco UBR10-MC20X20 line card switchover or when a shutdown and no shutdown command in issued on the Wideband interface.
Workaround: There is no workaround.
•
Symptoms: Polling of the SNMP IfHCInOctets and IfHCOutOctets values wraps at the 32-bit point for cable interfaces instead of the 64-bit values.
Conditions: This issue was first observed on Cisco uBR10012 routers running Cisco IOS Release 12.2(33)SCB4.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10012 router may experience packet drops on Parallel eXpress Forwarding (PXF) complex when using QoS and the number of connected customers reach approximately eight thousand subscribers.
Conditions: This issue was first observed on Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB with QoS enabled.
Workaround: There is no workaround.
•
Symptoms: The ENTITY-MIB object returns an incorrect OID value for the DTCC card. This means that SNMP applications using the ENTITY-MIB object incorrectly classifies the DTCC as a TCC+ card.
Conditions: This issue is occurs on the SNMP read operation of the ENTITY-MIB object.
Workaround: There is no workaround.
•
Symptoms: The Cisco 1-Port 10-Gigabit Ethernet SPA or Cisco 5-Port Gigabit Ethernet SPA ports are not able to transmit at expected data rate. Tail dropping and flowbit counters are observed on the SPAs.
Conditions: This issue occurs on PRE4 modules. PRE2 modules are unaffected. This issue may affect a Cisco 1-Port 10-Gigabit Ethernet SPA which is installed in bays 1,2 or 3. This issue may affect Cisco 5-Port Gigabit Ethernet SPA installed in ports 0, 1 or 4.
Workaround: Confirm that the Ethernet SPA (1x10 GigE or 5x1 GigE) is installed in bay 0 of the Cisco SIP-600 jacket card as suggested by the Cisco uBR10012 Universal Broadband Router SIP and SPA Hardware Installation Guide. Moving the SPA will resolve the issue for the Cisco 1-Port 10-Gigabit Ethernet SPA.
For Cisco 5-Port Gigabit Ethernet SPA ports 1 or 4 after moving the SPA to bay 0, please find the affected port in the list below and implement the specified workaround.
–
interface Wideband-Cable1/1/0:30shutdowncable rf-channel 23 bandwidth-percent 1–
interface Wideband-Cable3/1/0:30shutdowncable rf-channel 23 bandwidth-percent 1–
interface Wideband-Cable3/0/0:31shutdowncable rf-channel 23 bandwidth-percent 1–
•
Symptoms: Route processor or Network Processing Engine side memory leak is observed when querying the MIB object docsIetfQosCmtsMacToSrvFlowTable.
Conditions: This issue occurs when the MIB object docsIetfQosCmtsMacToSrvFlowTable is queried and there are items returned.
Workaround: Do not query this table, use docsQosCmtsMacToSrvFlowTable and docsQos3CmtsMacToSrvFlowTable objects.
•
Symptoms: Modem is showing init(t) when it should show init(o).
Conditions: This issue occur when the modem is in the process of coming online
Workaround: There is no workaround.
•
Symptoms: Adding a new host in the ACL in the route-map is not effective.
Conditions: The issue was first observed on the Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB.
Workaround: Modify the route-map configuration (for example, add/ or remove an unrelated set ip next-hop) whenever a modification is done to the IP access list used by that route-map.
•
Symptoms: The mtc-mode modem may be stuck in continuous ranging state on a channel.
Conditions: This issue occurs after changing the cable upstream docsis-mode from TDMA with default QPSK modulation to a ATDMA; the power per channel delta could be as high as 6dBmV. CMTS is unable to make the adjustment correctly, and results in continuous ranging, and power-adjustment.
Workaround: Recover using clear cable modem reset command. You can also change to DOCSIS mode during the maintenance window, if the upstream has mtc-mode (upstream channel bonding) modems.
•
Symptoms: Traffic could be blocked while configuring the cable modem mode ATOM Layer2 VPN and policy-map and applying it to the WAN interface.
Conditions: This issue occurs during the configuration of the cable modem mode ATOM Layer2 VPN and policy-map and applying it to the WAN interface.
Workaround: There is no workaround.
•
Symptoms: The protect interface remains in the load balance group table after revertback.
Conditions: This issue occurs after a line card switchover and revertback.
Workaround: There is no workaround.
•
Symptoms: Performing ISSU with an invalid license on Cisco UBR-MC20X20V cable interface line card will result in RPR mode of the PRE and service disruption.
Conditions: The issue occurs when performing ISSU upgrade from the Cisco IOS Release 12.2(33)SCC to Cisco IOS rebuild releases such as Cisco IOS 12.2(33)SCCx and when any one of the Cisco UBR-MC20X20V line cards in the chassis is in the "Maintenance" mode (without a valid license or unrecognized license).
Workaround: Install the Cisco UBR-MC20X20V line card with a valid license or remove the Cisco UBR-MC20X20V line card in maintenance mode before performing ISSU.
•
Symptoms: The following error message and traceback are seen on standby PRE:
*Nov 28 14:15:54.147 PST: %SYS-2-NOTQ: unqueue didn't find 0 in queue 656D5C80 -Process= "CHKPT rcv MSG process", ipl= 0, pid= 102-Traceback= 60A32018 60B37948 605050FC 6066ECD8 60680BB4 60681B84 605D07E8 605CB9A4 605CDCC4 605EDAC0 61B438C0 61B42684 61B41D8C 61B3ED74 61B39628Conditions: This issue may occur during a line card OIR.
Workaround: There is no workaround.
•
Symptoms: The upconverter firmware version is updated to version 0x31.
Condition: This upconverter works with the UBR10-MC20X20 line card.
Workaround: There is no workaround.
•
Symptoms: The Cisco CMTS crashed when the SNMP client was querying the ifRcvAddressEntry table.
Conditions: This issue occurs on a Cisco uBR10012 router with a 5-Port Gigabit Ethernet SPA and "getnext -v2c x.x.x.x(cmts address) [community] ifRcvAddressStatus(or ifRcvAddressType).11(ifIndex of GE in SPA).6.2.0.0.0.0.160(an non-zero address)" SNMP command was issued.
Workaround: Do not query this entry of the table.
•
Symptoms: The telnet session(s) that were used to conduct and modify the license become
unresponsive for more than fifteen minutes.
Conditions: This issue occurs on the UBR10-MC20X20 line card.
Workaround: Open a new telnet session and conduct the procedure over the console.
•
Symptoms: The line card is not operational with the new hardware revision of Upconverter.
Conditions: This issue occurs when the linecard with an upconverter uses an older image is used. The automatic IOS image downgrade could make the line card inoperative.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(33)SCB5
•
Symptoms: The Cisco uBR10012 router may generate the following message:
UBR10000-6-BADIPASSIGNMENT: DHCPOFFER dropped : Interface Cablex/y/zMac abcd.efgh.ijkl SID 2205 L3_Interface Cablex/y/z IP x.y.z.talready assigned to MAC=mnop.qrst.uvwx Interface Cablex/y/z SID 6367Conditions: This issue occurs when a cable modem (CM) is provisioned using an external DHCP server. The CM takes some hours to initialize.
Workaround: Reset the cable card to fix the issue.
•
Symptoms: All the routers are synchronized to one router and display the following message every 10 seconds:
Apr 23 13:33:41.929: %SYS-3-TIMERNEG: Cannot start timer (0x7543D68) withnegative offset (-996736100).-Process= "TTY Background", ipl= 0, pid= 42Conditions: This issue is observed on some Cisco gigabit switch routers (GSRs) running Cisco IOS Releases 12.0(28)S, 12.0(31)S, 12.0(32)S, and 12.0(32)SY.
The issue occurs when a telnet session is initiated on the router, and then a new telnet session to a different device is initiated from the same telnet session.
When you log into a router through telnet, and then open another telnet session in a different location, the exec-timeout does not disconnect the session even if no keystrokes are issued. At the exact moment the timeout expires, the error message is displayed every 10 seconds.
Workaround: Use the show users command to determine which users are logged in through telnet. Then use the clear line X command to clear the line, disconnect the users, and stop the error messages.
•
Symptoms: The clear cable modem command does not reset the modular-host tables.
Conditions:
–
–
–
After you execute this command, all the stat/BPI/PHS indexes in the modular-host tables are expected to be freed, but are not freed.
This causes a leak in the stat/BPI/PHS indexes and raises a Cable Modem Transmission System (CMTS) scalability issue, that is, CMTS is unable to support the stated number of modems online from the SPA downstream.
Workaround: There is no workaround.
•
Symptoms: The file system device returns a pseudo-positive value when the file system fails. This results in the file operation being displayed as successful even though it failed.
Conditions: This issue occurs when the file system device displays an error, but the code follows the path in the file system buffer cache, where the error is masked. The device error could occur if the code was written on damaged media or during online insertion and removal (OIR) of a line card.
Workaround: There is no workaround.
•
Symptoms: The active DOCSIS queues remain active in the event of a DOCSIS SPA failure.
Conditions: This issue is observed if there are modems online and passing traffic on the modular-cable and/or on wideband-cable interfaces and the DOCSIS SPA fails, the DOCSIS queues associated with these online modems remain active attempting to dequeue.
Workaround: Execute the microcode reload pxf command.
•
Symptom: When attempting to upgrade a Cisco uBR10012 router from Cisco IOS Release 12.3(21)BC to Cisco IOS Release 12.2(33)SCB, the primary PRE may crash.
Conditions: This issue is observed when the CMTS is running the Cisco IOS Release 12.3(21)BC and while upgrading to Cisco IOS Release 12.2(33)SCB. The CMTS must then be powered down and manually reconfigured to run as an M-CMTS (Cisco SIP-600 inserted, WB SPAs inserted, DTCCs inserted, and so on). The CMTS must then be turned on to run its new Cisco IOS Release 12.2(33)SCB IOS image and physical configuration.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000 series PRE 2 running crashes the Cisco IOS Release 12.3(23)BC6.
Conditions: This issue is observed when the PRE 2 is running the Cisco IOS Release 12.3(23)BC6 software, enabling ESR-HH-1GE. The cable source-verify dhcp command is executed but no cable line card is configured or inserted.
This issue occurs in Cisco IOS Releases 12.3(23)BC, 12.3(21a)BC, and 12.2(33)SCB.
Workaround: Configure or insert the cable line card in the Cisco CMTS.
•
Symptoms: After a reconfigure of "member subslot x/y working" and switchover of the line card, the CM does not come online.
Conditions: This issue is observed when you configure "member subslot x/y working" twice.
Workaround: Ensure that you configure "member subslot x/y working" only once. Do not reconfigure it.
•
Symptoms: CMs do not respond to layer 3 pings.
Conditions: This issue is observed only on the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U cards and when PRE-EQ (equalization-coefficient) is configured.
Workaround: Reset the cable line card.
•
Symptoms: A multicast quality of service (QoS) session is not automatically created when changing group configuration or group QoS configuration (GQC).
Conditions: This issue is observed when a multicast QoS group is configured on a bundle interface and a matching static-group is defined. However, any change in the group configuration after it is applied to the bundle interface is not taken into effect, and the original multicast QoS session is removed.
Workaround: Remove the multicast QoS session from the bundle interface and re-apply it to the bundle.
•
Symptoms: Alignment traceback messages are displayed when the show memory leak res user" and show buffer usage commands are executed.
Conditions: This issue is observed on the Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: The service identifier (SID) management task results in a memory leak.
Conditions: This issue is observed when the packetcable calls are present.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed on the line card due to MAC parser with overnight PC calls.
Conditions: This issue is observed when the packetcable calls are present overnight.
Workaround: There is no workaround.
•
Symptoms: OIR of a PCMCIA flash disk can cause a watchdog reset of the PRE.
Conditions: This issue is observed during OIR of the PCMCIA flash disk that is being actively accessed.
Workaround: Deactivate the features that access the PCMCIA flash disk. These features include:
–
–
–
–
It is recommended that you restrict the removal of PCMCIA flash disks to a maintenance window.
If the system has redundant PRE's, then it is further recommended that you remove the PCMCIA flash disks only from the STANDBY PRE. However, if it is imperative that you remove a PCMCIA flash disk from the current PRIMARY PRE, then swap the PRE roles by initiating a switchover before the PCMCIA flash disk removal. Use the redundancy force-switchover main-cpu command to initiate a PRE switch over:
If SEA or DOCSIS 3.0 IPDR is enabled, verify that no IPDR transactions are in progress by executing the following command until there is no output:
show cable metering verbose | inc In progressAfter the verification, execute the following commands to disable SEA and IPDR:
conf tno logging system ! Disable SEAno cable sflog ! Disable IPDR sflog writesno cable metering ! Disable IPDRendVerify that all PCMCIA flash disk accesses have been halted by confirming that the PCMCIA flash disk access LEDs are not illuminated, before physically removing the PCMCIA flash disk.
•
Symptoms: There may be sporadic short losses (of a few minutes) of multiple CMs off a (random) upstream. These losses are usually accompanied by a spike of the error per second rate or by an MER drop and a decrease in docsIfSigQUnerroreds.
However, the reverse is not true—a brief degradation of the physical connectivity parameters does not necessarily trigger a brief CM loss.
Conditions: This issue is observed on Cisco uBR10-MC5X20H line cards.
Workaround: There is no workaround.
•
Symptoms: Entries in docsBpi2CmtsMulticastObjects duplicate after the line card revertback.
Conditions: This issue is observed when a cable match command is configured with BPI. The IGMP join is received for the group in cable match command and the docsBpi2CmtsMulticastObjects is populated. This results in the line card switchover and revertback.
Workaround: There is no workaround.
•
Symptoms: Cisco uBR10000 PRE CPU goes to 100% when the FPGA on the Wideband SPAs plugged into a SIP-600 are being upgraded.
Conditions: This issue only occurs during the SPA FPGA upgrade process.
Workaround: There is no workaround.
•
Symptoms: Non-bonding cable modems are wrongly registered in bonded channels.
Workaround: There is no workaround.
•
Symptoms: Active PRE fails over to the secondary reporting:
ACTIVE RP WATCHDOG TIMEOUT TRIGGEREDConditions: This issue is observed on Cisco IOS Release 12.3(23)BC7.
Workaround: There is no workaround.
•
Symptoms: When setting cable upstream docsis mode by SNMP, the standby PRE does not synchronize this configuration.
Workaround: Use the CLI mode to set up the cable upstream docsis mode instead of SNMP.
•
Symptoms: The show interface multicast-session command may show erroneous multicast session instances.
Conditions: This issue occurs when:
–
–
–
Workaround: There is no workaround.
•
Symptoms: The standby PRE may crash during initial configuration comprising features, such as crypto certificates, multicast, and ipv6 configuration.
Conditions: If a configuration file with the above features is copied directly from a file to the running configuration while both—active RP and standby RP—are booted with no configuration, the standby RP might reload unexpectedly.
Workaround: Ensure that the standby RP is online and available after the initial running configuration file is saved to the startup configuration file.
•
Symptoms: Wideband SPA does not transmit. Harmonic EQAM indicates there is no incoming traffic.
Conditions: This issue is observed in Cisco IOS Release 12.2(33)SCB3/ PRE 4/ 2 SIP-600's/ 2 5x1GE's/ 6 SPA-24XDS-SFP.
Workaround: Reload the PRE.
•
Symptoms: When the protect line-card becomes active for the first time after system bootup, about 60 to 70 buffers are indefinitely, as owned by the "CR10K IPC Dispatcher" process.
Workaround: There is no known workaround for this issue.
•
Symptoms: All WCMs on Wideband SPA unexpectedly go offline and never tried ranging.
During this period, the SPA sends out only the SYNC packets, and not packets from MC520 (MDD, secondary MDD, UCD, MAP, and so on).
Conditions: This issue is observed in 3-Channel bonding with DTI.
Workaround: Online insertion and removal of the SPA might resolve this issue.
•
Symptoms: After the PRE switchover, the service flow counter displays the value 0. However, the right service flow is used to forward the packets. And also the packets will reach CPEs as well.
Conditions: This issue is observed during a PRE switchover.
Workaround: There is no workaround.
•
Symptom: No system log or SNMP trap is generated when the COPS process that is used for packetcable, fails.
Conditions: This issue is observed in a packetcable environment.
Workaround: There is no workaround.
•
Symptoms: When you execute the term len 0 and show cable modem commands on PRE 4 with more than a hundred CMs, printout pauses randomly for up to a second.
Conditions: This issue occurs when there are hundreds.
Workaround: There is no workaround.
•
Symptoms: The system logs record a line-card crash (8/0), which is immediately followed by a PRE failover.
Conditions: There is no query on the object, cefcFRUPowerSupplyGroupTable, when the failover occurs.
Workaround: There is no workaround.
•
Symptoms: Wideband modems do not come w-online and often flap in Reject(c) state. A telnet into the line card console and IPC troubleshooting reveals IPC issues, such as failure of the "ubr-test-request-api x/y block" for other slots.
Conditions: This issue is observed in the cisco uBR10000-2 line card with Docsis 3.0 Wideband- setup and Wideband-capable modems.
Workaround: Change the Modular-host subslot in the Modular-Controller configuration. It is recommended that you use the Cisco uBR10-MC5X20H-D line cards. These cards provide better CPU capacity.
You can also reset the hardware-module subslot x/y.
•
Symptoms: The wideband association is displayed incorrectly after the cable power is switched off on all the line cards.
Conditions: This issue is observed when running the following script:
1.
2.
3.
Workaround: There is no workaround.
•
Symptoms: If the packetcable feature is not enabled in the CMTS configuration while conducting the DQoS lite Voice calls, the DiffServ service flows are on the committed information rate (CIR) queue instead of the low latency queuing (LLQ).
Conditions: This issue occurs on all Cisco IOS Releases 12.2(33)SCB.
Workaround: Enable the following commands in the CMTS configuration.
–
–
•
Symptoms: The Pool Manager process might result in a memory leak.
Conditions: This issue is observed when QoS is configured.
Workaround: There is no workaround.
•
Symptoms: The write operation fails when a disk card is removed while it is still being updated, or if a disk card contains bad sectors, or does not respond during updation.
Conditions: This issue is observed in the following two conditions:
1.
2.
If you execute the show file system, dir disk, or show disk commands during this period, the system hangs.Workaround: For condition 1, avoid removing the card when the card is being updated.
For condition 2, replace the card with a known good card.•
Symptoms: ICCN drops and traffic outage are observed on a tunnel with sessions.
Conditions: This issue is observed during bootup or SUP SSO on RFGW.
Workaround: There is no workaround.
•
Symptoms: With Cisco IOS Release 12.2(33)SCB, multiple next-hop IP addresses are configured in PBR action. The PBR continues to use the first next-hop IP without switching to the second next-hop IP even after the first next-hop is shut down and its ARP adjacency in CMTS becomes obsolete.
Conditions: This issue is observed when the first next-hop is down and its ARP adjacency is removed from CMTS due to timeout.
The interface (on CMTS) connected to the first next-hop is still in "Up" status (for certain configuration, the interface can become down if the peer is shut down).Workaround: Configure "PBR Support for Multiple Tracking Options" that is designed to detect whether the next-hop is active or not. Refer to the PBR Support for Multiple Tracking Options Guide for more configuration information.
•
Symptoms: The modular association with the DS cable controller displays incorrectly. In show controller cable x/x/x, the modular YY is displayed as "Up," although this association is not configured under the cable interface.
Conditions: This issue is observed after a stateful switchover (SSO).
Workaround: Perform these steps to recover from this issue:
1.
2.
•
Symptoms: The Cisco uBR10-MC5X20U-D line card crashes multiple times displaying the following message:
Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0x6038C709Conditions: This issue is observed on the Cisco uBR10k with PRE2 running Cisco IOS release 12.2(33)SCB3 & SCB4.
Workaround: There is no workaround.
•
Symptoms: On a Cisco uBR10000 cable line card, the show memory debug leak command displays a large number of buffer leaks for SA-MAP request count.
Conditions: This issue occurs when a number of SA-MAP requests are received from multiple modems connected on the line card.
Workaround: There is no workaround.
•
Symptoms: Modems do not come online or once online quickly return to the offline state on interfaces with modular remote primary.
The show cable modem primary summary total command displays the non-zero blaze indices stay non-zero:
Conditions: This issue is observed on a PRE-Failover event and when modems are on a domain that has only modular remote primaries.
This issue is observed on Cisco uBR10000 with PRE2 running Cisco IOS Release 12.3(23)BC7.
Workaround: Unplug the power cable off the affected line card and plug it back again.
•
Symptoms: The Cisco IOS Release 12.3(33)SCB crashes if the MC-2020 card is added or removed from the redundancy configuration.
Conditions: This issue is observed when the line card type is unknown and the line card redundancy is configured.
Workaround: There is no workaround.
•
Symptoms: If you have lower privilege levels than Enable Access, you may not be able to execute some show cable command options.
Conditions: This issue occurs because the parent privilege level is not carried over correctly. This issue occurs on the Cisco IOS Releases 12.3BC, 12.2SCB, and 12.2SCC CMTS.
Workaround: Repeat the privilege level command for each interface. For the above example,
privilege exec level 1 show cable mac-domain c5/0/0 downstream-service-groupprivilege exec level 1 show cable mac-domain c5/0/1 downstream-service-groupprivilege exec level 1 show cable mac-domain c5/0/2 downstream-service-group......privilege exec level 1 show cable mac-domain c8/1/4 downstream-service-group•
Symptoms: The internal accounting of the number of MAC domains is incorrect.
Conditions: This issue is observed only on boot up and affects only Cisco IOS Release 12.2(33)SCC.
Workaround: There is no workaround.
•
Symptoms: docsIfCmtsChannelUtUtilzation is not supported for MC/IC interfaces.
Conditions: This issue occurs when you set the MIB objects docsIfCmtsChannelUtilizationInterval and ccwbRFChanUtilInterval, and use the SNMP query for docsIfCmtsChannelUtUtilzation. The results are displayed only for MC28U/MC520 downstream channels.
Workaround: Use the object ccwbRFChannelUtilization for MC/IC interfaces instead.
•
Symptoms: Tracebacks occur when the bundle secondary ip address is removed.
Conditions: This issue occurs when you configure and remove the bundle secondary ip address.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10000-MC5x20H line card may crash after reporting memory allocation failures.
Conditions: This issue is observed when multiple memory allocations failures occur.
Workaround: There is no workaround.
•
Symptom: The redzone of the memory block is corrupted. The following output in the line card console displays the corruption:
validblock_diagnose, code = 1current memory block, bp = 0x1FB53398,memory pool type is Processordata check, ptr = 0x1FB533C8Conditions: This issue is observed when the line card is configured for a specific size.
Workaround: Change the configuration of the mac domain.
•
Symptom: The init-tech-ovr command in LBG does not work for the second logical channel.
Conditions: This issue is observed when the second logical channel is selected as the source channel.
Workaround: There is no workaround.
•
Symptoms: When configuring the IGMP static-group, the CMTS console may hang and eventually crash.
Conditions: This issue is observed when the Group-config is configured before configuring the static-group. This may result in the MQoS config process getting into an infinite loop.
Workaround: Configure the static-group before configuring the Group-Config.
•
Symptoms: The IGMPv3 client may stop receiving multicast traffic after the leave and rejoin commands are executed in quick succession.
Conditions: This issue occurs when leave and join commands are sent in a quick succession before the previous leave is executed on the CMTS. Once the modem is in this state, it will not receive any multicast data even after multiple leave and joins.
Work around: Reset the modem reset and execute a fresh join command.
•
Symptoms: The CLC crashes when a specific 3-way call scenario is initiated.
Conditions: This issue occurs where multi-line ATAs are placed behind CMs in a PCMM setup.
Workaround: There is no workaround.
•
Symptoms: The ETDB and DSID entries are removed during MC-2020 LCHA.
Conditions: This issue is observed in the Cisco IOS Release 12.2(33)SCC.
Workaround: There is no workaround.
•
Symptoms: CLC crashes after executing the show controllers c5/0/4 tech-support command.
Conditions: This issue is observed on MC-2020 line cards running the Cisco IOS Release 122-32.8.5.SCC.
Workaround: There is no workaround.
•
Symptoms: A traceback occurs when confirmation-to-receive (CFR) is configured without being associated with the tunnel.
Conditions: This issue occurs in Cisco IOS Release 12.2(33)SCB.
Workaround: Configure the CFR and associate it with the tunnel using the same command.
•
Symptoms: The BPI index information is missing from the show controller command.
Conditions: This issue occurs if the interface is on working or standalone card.
Workaround: There is no workaround.
•
Symptom: The MIB object snmpwalkoverccsCmFlapTable does not return all the entries.
Conditions: This issue occurs during subsequent reboots where the CMTS does not contain ifindexes, which are after wideband interfaces: narrowband ifindexes.
This issue also occurs if the wideband cables are on the cable flap list.
Workaround: There is no workaround.
•
Symptoms: The operation fails and no DCC is issued when you use docsLoadbal3ChgOverGroupMacAddress, docsLoadbal3ChgOverGroupUsChSet and docsLoadbal3ChgOverGroupCommit to change a CM's upstream through SNMP.
Conditions: This issue is observed only when the CM's downstream is a Modular Cable or Integrated Cable interface and its host Cable interface has no frequency configured.
Workaround: Set docsLoadbal3ChgOverGroupdownFrequency to the appropriate target frequency, even it is identical to the source. Or, if the use of UCC is acceptable, set docsLoadbal3ChgOverGroupForceUCC to TRUE.
•
Symptoms: The following traceback is seen when unconfiguring the bundle interfaces:
Oct 21 23:40:08.951 PDT: %GENERAL-3-EREVENT: No HWIDB_SB_C10K_TT-Traceback= 60A32A5C 6182EEE0 619159A0 61916248 6019EEFC 601936C0 60198EE0 60AADBB0 60A91CF4 60A9CCA8 609B8940 601384B4 609E4628 60B2E6B8 60B2E6A4Conditions: This issue occurs when a complicated testing case runs scripts in which all bundle interfaces are unconfigured.
Workaround: There is no workaround.
•
Symptoms: Attribute-based service flow assignment does not work.
Conditions: This issue is observed when you change the attribute-mask configuration under wideband-interface after the chassis boots up.
Workaround: Perform a line card switch over and revert back to recover from the problem.
•
Symptom: The multicast traffic does not pass through the modem in wideband interfaces during some line card switchovers.
Conditions: The issue is observed in the following two conditions:
–
–
This issue affects all line cards.
Workaround: There is no workaround.
•
Symptoms: The DFO retry counter does not rise beyond the number zero.
Conditions: This issue occurs when you execute the cable service attribute ds-bonded downstream-type bonding-enabled [enforce] and then power on/off the wideband cable modem.
Workaround: There is no workaround.
•
Symptoms: The standby PRE may crash with a value of signal 10 after a spurious memory access. The following message is displayed:
%UBR10K-3-QALLOCFAIL_INFO: Failure to allocate QoS queue: No hardware IDB or sf_datp.%UBR10K-3-QALLOCFAIL: Failure to allocate QoS queue for service flow 11270, CM%UBR10K-3-QALLOCFAIL_INFO: Failure to allocate QoS queue: No hardware IDB or sf_datp.%UBR10K-3-QALLOCFAIL: Failure to allocate QoS queue for service flow 11634, CMcr10k_rp_ha_parse_ds_srv_flow: DSA sfid 11634 failed to create new sfid%GENERAL-2-CRITEVENT: Couldn't get C10k Subblock-Traceback= 60189FD0 6018A008 60197EF8 60196CBC 6034B394 6034AA9C 6034ABE0 6034E4E4 603E3C14 601DF2F4 601E3EB4 601DB628 601DBF50 601DC120 606BFEF8%ALIGN-3-SPURIOUS: Spurious memory access made at 0x6019BE14 reading 0xBC%ALIGN-3-TRACE: -Traceback= 6019BE14 6019C7B4 60198460 6019940C 601DE3A4 601DF324 601E3EB4 601DB628The crash only affects redundancy and has no impact on services.
Workaround: There is no workaround.
•
Symptom: The object CLAB-TOPO-MIB returns more interface instances compared to the CLI.
Conditions: This issue occurs under normal conditions.
Workaround: Use CLI instead of SNMP to get the fiber-node information.
•
Symptoms: Fiber node is invalid after LCSO for Cisco MC-2020 protect 520.
Conditions: This issue occurs in a MC-2020 protect 520 case, when one 520 MD is in shutdown state and in fiber node.
Workaround: Ensure that all the 520 MDs configured in MD should not be in shutdown state.
•
Symptoms: The multicast DSID may generate incorrectly and multicast traffic does not reach CPE.
Conditions: This issue is observed when LCHA is configured and the static-sync is running.
Workaround: There is no workaround. Once the timer stops (after approximately 30 to 60 seconds of LCHA operation), the subsequent IGMP join populates the DSID and the forwarding functions normally.
•
Symptoms: The RNG-RSP sends inaccurate timing offset values after the US redirection.
Conditions: This issue is observed when the CM aligns itself to the timing offset according to the values in the RNG-RSP, but the CMTS does not receive the RNG-request. Therefore, the CM does not receive any RNG-RSP.
Workaround: Apply the modem firmware patch.
•
Symptoms: After LCHA on the Cisco MC-2020 CLC, multicast traffic fails to reach CPE.
Conditions: This issue is observed when the CM is MDF enabled after the 2020 LCHA.
Workaround: CPE should leave and re-join the group.
•
Symptoms: Number of pre-equalization taps decreases incorrectly after CLC failover.
Conditions: This issue is observed on a Cisco uBR10000 router running Cisco IOS Release 12.2(33)SCB4.
Workaround: There is no workaround.
•
Symptoms: Polling of the IfHCInOctets and IfHCOutOctets wraps at the 32-bit point for cable interfaces.
Conditions: This issue is observed on Cisco uBR 10000 routers running Cisco IOS Release 12.2(33)SCB4.
Workaround: There is no workaround.
•
Symptoms: Cisco Wideband SPA sends only "sync Tx" packets.
Conditions: This issue is observed after Cisco Wideband SPA reload and when a DTI server is used.
Workaround: Reload the jacket card reload EQAM reboot.
•
Symptoms: Cisco uBR10000 series router may experience packet drops on PXF complex when using QoS and the number of connected customers reach approximately eight thousand subscribers.
Conditions: This issue is observed on Cisco uBR10000 series router running Cisco IOS Release 12.2(33)SCB with QoS enabled.
Workaround: There is no workaround.
•
Symptoms: The Entity MIB returns an incorrect OID value for the DTCC card. This means that SNMP applications using the Entity MIB incorrectly classifies the DTCC as a TCC+ card.
Conditions: This issue is observed for an SNMP read operation of the Entit-MIB.
Workaround: There is no workaround.
Resolved Caveats — Cisco IOS Release 12.2(33)SCB5
•
Symptoms: Executing the show commands pushes the CPU utilization to 100%.
Conditions: Long running show commands, such as show running-config, show voice call summary, and show memory summary affect voice call processing adversely, even if they periodically suspend.
Workaround: There is no workaround.
•
Symptoms: An error message is displayed when you execute the show pxf cpu stati drop <interface> command if the interface is not supported by toasters, such as Ethernet, FastEthernet.
Conditions: This issue is observed while executing the show pxf cpu stati drop command on interfaces, such as Ethernet, FastEthernet, and so on.
Workaround: There is no workaround.
•
Symptoms: A traceback occurs when you reset the line cards. The following output is displayed:
RTTY ISSU Start Nego failed: rc: -287%ISSU-3-NOT_REG_UNDER_ENTITY: msg session(528938704) is not registered under client ISSU RTTY Client(2033) and entity(1)-Traceback= ...Error in rtty_issu_unregister_sessions at 103%C7600_PWR-SP-4-DISABLED: power to module in slot 2 set off (Reset)Conditions: This issue occurs after inserting or removing the cards from the chassis, or during an OIR.
Workaround: There is no workaround.
•
Symptoms: A traceback occurs in the cr10k_docsis_get_ses_info for failed assert.
Workaround: There is no workaround.
•
Symptoms: A Cisco IOS device may reload with address or alignment errors, and tracebacks, such as %ALIGN-3-SPURIOUS or %ALIGN-3-TRACE.
Conditions: This issue occurs when the TACACS+ server (ACS) transmits an "authentication error" during ACS configuration, or when a request times out. There may also be other AAA or TACACS-related conditions that cause this symptom.
Workaround: There is no workaround.
•
Symptoms: A Catalyst 6500 or a Cisco 7600 may reload unexpectedly. On the console or in the RP crashinfo file, the following message may be displayed:
%SYS-2-WATCHDOG: Process aborted on watchdog timeout, process = Per-Second JobsConditions: This issue occurs when NetFlow is configured on one of the following:
–
–
Workaround: Disable Netflow by using one of the following commands on every sub-interface for which Netflow is configured:
1.
2.
3.
•
Symptoms: A memory leak might occur on a Cisco uBR10000 line card memory leak in the cr10k_card_ib_ipc_init().
Workaround: There is no workaround.
•
Symptoms: A CLC may crash when one of its upstreams is shut down.
Conditions: This issue occurs only if the upstream route and its associated downstream are configured in to load balance groups.
Workaround: There is no workaround.
•
Symptoms: Service flow packet drop counters displayed by show int Cableslot/subslot/port service-flow <sfid> counters are not accurate after a clear counters command has been issued.
Conditions: If a CM service flow has packet drops in toaster (rate-limited and queue drops), these counters are not cleared on clear counters command causing inaccurate values to be displayed for these counters by the show int Cableslot/subslot/port service-flow <sfid> counters command.
Workaround: There is no workaround.
•
Symptoms: The output "sid" is incorrect in the show cable modem x.x.x.x service-flow [verbose] command.
Conditions: This issue is observed in the Cisco IOS Release 12.3(23)BC and Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: Multicast packets remain unaccounted.
Conditions: This issue is observed when sending multicast traffic. The packets are received properly, but are not accounted for.
Workaround: There is no workaround.
•
Symptoms: The value range of the MIB object ccmtrCollectionInterval is not consistent with the command. The valid range for a MIB object is 15 to 1440, but 2 to 1440 for the command.
Conditions: This issue occurs while setting the MIB object ccmtrCollectionInterval using the SNMP set operation.
Workaround: Set the interval using the command.
•
Symptoms: A memory leak is observed after executing the multicast test case command.
Conditions: This issue is observed when the cable multicast group-qos and cable multicast qos group priority commands are unconfigured.
Workaround: Unconfigure the session-range using the cable multicast qos group priority command.
•
Symptoms: The CMTS allows any upstream to be attached to any connector without any warning message. A "no" is displayed for the conflicting connector.
Conditions: This issue is observed when a new card is plugged into a slot with no pre-configuration.
Workaround: Reload the line card or use default connectors.
•
Symptoms: Dynamic PCMM service flow disappears after 520U line card switchover or reset.
Conditions: This issue is observed when switchover occurs after PCMM gate built about [T3-20, T3] seconds or after sequential switchover/revertback.
Workaround: Change the PCMM policy to revive the PCMM gate from COMMIT_RECOVERY back to COMMIT status.
•
Symptoms: The ESR-PRE2 processor module crashes and the crash infomation logs may contain the following:
%UBR10K-6-US_SFID_INCONSISTENCY: US-SF found: SFID xxxx, type 0, sid 0(yyyy), MAC aaaa.aaaa.aaaa(bbbb.bbbb.bbbb), prim_sid xxx(yyy)CMD: 'no cable service attribute voice-enabled downstream-type HA-capable'Conditions: This issue is observed in the Cisco IOS Release 12.3(23)BC4 and Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: The show inventory command on a uBR10012 router running Cisco IOS Release 12.2(33)SCB1 may show duplicate versions of the DTCC cards in the chassis.
Workaround: There is no workaround.
•
Symptoms: After a PRE switchover, the wideband interfaces status on SPA drop offline. The wideband modems on these wideband interfaces also drop offline.
Conditions: This issue occurs when the primary PRE and secondary PRE boot up at same time.
Workaround: Boot up the secondary PRE much later than the primary PRE, or boot up the secondary PRE when the primary PRE is already up and running.
•
Symptoms: A Cisco router may reload when it is configured for SNMP notifications.
Workaround: Disable the SNMP notifications with the command no snmp-server host host-address informs.
•
Symptoms: Multicast traffic forwarding halts on modular cable interfaces.
Conditions: This issue occurs on modular downstream interfaces with multicast QoS functionality configured and when the Parallel Express Forwarding (PXF) on the CMTS restarts.
Workaround: In the event of a static multicast, unconfigure and reconfigure the ip igmp static-group commands. In the event of the dynamic multicast, use the clear ip mroute command.
•
Symptoms: During the VDOC video channel changes, it is possible that the multicast QoS service flow is not created because an outdated multicast QoS service flow exists for 140 seconds after the last IGMP member. This prevents a new multicast QoS service flow from being created.
Conditions: This issue is observed in multicast QoS service flows.
•
Symptom: CMTS will accept inconsistent "per-SF L2VPN TLV" in the cable modem configuration file.
Conditions: This is observed in the following conditions:
–
–
–
Workaround: There is no workaround.
•
Symptoms: When exporting the SAMIS20 scheme data through Internet Protocol Detail Record (IPDR), the type of RecCreationTime of SAMIS20 scheme is dataTime. The correct value is dataTimeMsec per CM-SP-OSSIv2.
Conditions: This issue occurs when the cable metering object SAMIS20 is configured before the IPDR.
Workaround: There is no workaround.
•
Symptoms: A legitimate CM which was online and BPI enabled, gets disconnected along with the following error messages printed with "CLONED_CM_DETECTED" corresponding to legitimate modem's MAC address.
Conditions: This issue occurs when once the legitimate CM goes offline and comes back again online with BPI enabled, the next cloned CM attempt fails.
•
Symptoms: The show cable modem wideband command displays a wrong MD-DS-SG numerical value.
Conditions: There is a mismatch between the MD-DS-SG value, CLI show cable modem wideband, and show cable mac-domain cable */*/* downstream-service-group command values.
SCM wi displays the MD-DS-SG value from the line card and show cable mac-domain cable */*/* downstream-service-group displays MD-DS-SG from RP.
Workaround: There is no workaround.
•
Symptoms: Dequeue counts stop incrementing for the queue, the queue fills up and eventually begins to tail drop. In some instances the entire interface appears stop responding. Often data corruption messages similar to the following are observed on the system:
%DATACORRUPTION-1-DATAINCONSISTENCY: Doubly-linked list corruptionAdditionally, it is possible to sometimes see duplicate QID messages similar tothe following:%GENERAL-2-CRITEVENT: duplicate qidConditions: This issue occurs in the following conditions:
–
–
Workaround: Perform two PRE switchovers. This will result in the linked lists of free and active QIDs on both PREs being completely reset. Ensure that you collect the following data before performing the switchovers:
show pxf cpu queue hqf statshow pxf cpu queue [interface] for interface with the stuck queue (two times to verify the queue is stuck).
show techshow tech cmts [interface] for interface with the affected modem.
show tech cmts modem [mac_address | ip_address] for the affected modem.
•
Symptoms: A spurious memory access occurs or CMTS crashes.
Conditions: This issue is observed when the DSG is configured and line card is in protect mode.
Workaround: Do not update the configuration when protect mode is active.
•
Symptoms: A minor warning message about improper SPA temperature is displayed.
Conditions: This issue is observed when the WBCMTS SPA temperature crosses over the minor warning threshold of 58C, and remains in the range of 58C ~ 68C for more than 10 minutes.
Workaround: There is no workaround.
•
Symptoms: The following logging errors may be displayed:
Jun 24 18:44:38.727 CST:%SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (62/60),process = Exec.Conditions: This issue is observed on the Cisco MC-520 card. This issue is also observed on the Cisco IOS Release 12.2 (33)SCB.
Workaround: There is no workaround.
•
Symptoms: The system is unable to unconfigure the cable metering during the IPDR process.
Workaround: There is no workaround.
•
Symptoms: The ARP entries are lost after a redundancy switchover or a crash.
Workaround: There is no workaround.
•
Symptoms: After the line card switchover is reverted back, the wideband modem can only come up online as a narrow band.
The Blaze index leaks, causing the errors "zero blaze index", and "wbcmts_idxtbl_assign(): failed. Tbl full".Conditions: This issue is observed under the following conditions:
–
–
–
Workaround: To prevent this issue, type:
hw-module subslot x/y resetor let the line card crash/power-off/OIR to trigger LCSO/revertback.
Do not use:
redundancy linecard switchover from / revertback x/yto trigger LCSO/revertback.
If the issue has occurred, to recover:
1.
2.
•
Symptoms: PC/PCMM gates remain stuck on CMTS after PRE/LC switchover.
Conditions: This issue is observed when the CMTS is running more than 300 PC/PCMM calls and the PRE/LC switchover is triggered.
Workaround: Manually delete the gates using test packetcable gc gate-delete.
However, There is no workaround in the Cisco IOS Release 23BC, where the above command fails.•
Symptoms: After revertback, the show cable modem command displays the CMs under 5/0, but they do not respond, and the show cable modem <mac-address> command returns with the message "Cable modem with MAC address xxxx.xxxx.xxxx not registered".
Conditions: This issue occurs when:
1.
2.
3.
4.
5.
6.
7.
Workaround: Clear the CM and bring it back online.
•
Symptoms: MD-DS-SG ID is set to zero after LC switchover and PRE switchover.
Conditions: This issue is observed when two PREs boot up at the same time.
Workaround: Perform a revertback on the PRE.
•
Symptoms: The PRE crashes when an Etherchannel subinterface with dot1q encapsultation is deleted.
Conditions: This issue is observed when there are no more subinterfaces for that Etherchannel interface.
Workaround: There is no workaround.
•
Symptoms: The DSG traffic is no longer forwarded to the modular interface after changing the bundle.
Conditions: This issue is observed when you change the bundle of mac-domain, and only DSG traffic on MC interface is affected.
Workaround: Remove and add the bundle again.
•
Symptoms: After a crash or a OIR of a cable line card, the RCC template is not applied to the cable interface.
Conditions: LCHA must be enabled. The initially active card crashes and comes up again to become active.
Workaround: Unconfigure and re-configure the associated fiber-node when the line card is still in this state.
•
Symptoms: If the line card is OIR, the get mib entry command displays an incorrect physical index.
Conditions: This issue is observed when system boots up, and any LC OIR, except SPA.
Workaround: Do not perform an OIR on the line card.
•
Symptoms: After SFP OIR, the Cisco Wideband SFP physical index is displayed incorrectly and the name of SFP does not match the show inventory.
Conditions: This issue is observed while performing a Cisco Wideband SFP OIR.
Workaround: Do not perform an OIR on the Cisco Wideband SFP.
•
Symptoms: The show version command displays an incorrect value (higher or lower) for the SIPs and SPAs.
Conditions: This issue is observed on the Cisco IOS Release 12.2(33)SCB3/ PRE4/ 2 SIP-600's/ 2 5x1GE's/ 6 SPA-24XDS-SFP.
Workaround: Reload the PRE.
•
Symptoms: The CMTS crashes when an IPV6 address is deleted from a client database after sending bi-directional FTP traffic to ~319 dual-stack CPE devices and then stopping traffic.
Conditions: This issue is observed when the CMTS is configured for only IPv4. A crash occurs in the CMTS source verify init tables.
Alternatively, if the CMTS is configured for both IPv4 and IPv6 and dual-stack CPEs are used behind cable modems, a crash occurs when the CMTS internal code deletes an IPv6 address of the CPE from the CMTS database.
Workaround: There is no workaround.
•
Symptoms: When you execute the shutdown command on the Ethernet NSI interface and then execute the no shutdown command, the TLS L2VPN traffic fails.
Conditions: This issue is observed when the NSI interface is SPA-5X1GE.
Workaround: Unconfigure and re-configure the TLS L2VPN configuration.
For example:
no cable l2-vpn-service xconnect nsi dot1qno cable dot1q-vc-map 001c.eaa5.0a9e GigabitEthernet1/0/0 17cable l2-vpn-service xconnect nsi dot1qcable dot1q-vc-map 001c.eaa5.0a9e GigabitEthernet1/0/0 17•
Symptoms: Traceback messages are displayed while executing the show interface command.
Workaround: There is no workaround.
•
Symptoms: A positive integer value is returned for the MB object docsIfCmtsChannelUtUtilization (OID 1.3.6.1.2.1.10.127.1.3.9.1.3) of the Cisco uBR10000 5/1 HCCP Protect Interface when it is on standby.
When a HCCP 5/1 protect card is in standby no traffic utilization should be reported.Conditions: This issue is observed on the Cisco IOS Release 12.3(23)BC4 running on a Cisco uBR10000 series router with redundant ESR-PRE2 Modular Cable Docsis 3.0 configurations.
Workaround: There is no workaround.
•
Symptoms: On a Cisco uBR10000 series router running Cisco IOS Release 12.2(33)SCC, PRE2. The following traceback may be seen:
Jul 27 11:13:17.181 CDT: %PIM-5-DRCHG: DR change from neighbor 0.0.0.0 to 10.254.0.1 on interface Bundle1.10Jul 27 15:26:30.419 CDT: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x613BA3C4 reading 0x37BCJul 27 15:26:30.419 CDT: %ALIGN-3-TRACE: -Traceback= 613BA3C4 618CD74C 618E056C 601704E4 60172B8C 60173958 601CD504 601CDA00Workaround: There is no workaround.
•
Symptoms: Unused multicast flows, that is, flows that have no member CMs in the system, can take a long time to be cleaned up and the IGMP Input process continues to hold large amount of memory.
Conditions: This issue occurs when:
–
–
Workaround: There is no workaround.
•
Symptoms: When the ip-init mdd command is changed from IPv4 to dual-stack, a traceback may be
observed on the CMTS console.
Conditions: This issues might occur if the CMTS is configured for both IPv4 and IPv6, then going from IPv4 MDD CLI to dual-stack.
Workaround: There is no workaround.
•
Symptoms: The show pxf cpu queue hqf stat command is not included while executing a show tech-support command.
Workaround: When capturing information with the show tech-support command, also collect information using the show pxf cpu queue hqf stat command.
•
Symptoms: Tracebacks are observed that may be caused by traffic to the CMTS from an unknown source.
•
Symptoms: A DOCSIS 3.0 CM rejects REQ-RSP-MP during modem registration.
Conditions: This issue is observed when the DSID Reseq Wait time 0xff is sent as part of REQ-RSP-MP as against the DDOCSIS 3.0 MULPI specification specified range of 1-180.
Workaround: There is no workaround.
•
Symptoms: Multiple Modular Remote Primary modems report majority or all of the modems offline because of more than one identical "downstream modular x/y/z rf-channel n" in multiple domains.
Conditions: This issue is observed in the Cisco IOS Release 12.3(23)BC4 with Cisco uBR10000-2 with redundant ESR-PRE2 Modular Cable Docsis 3.0 configurations.
Workaround: Remove the duplicate configurations from the unwanted interface by executing the no downstream modular command.
You may also need to completely remove the downstream modular configurations on all interface and reconfigure.
•
Symptoms: Change in the cable multicast-echo CLI does not synchronize to the second PRE.
•
Symptoms: Remote narrow band eMTAs drop offline after LCSO if the modular-host is on another card.
Conditions: This issue is observed when:
–
–
–
–
Workaround: Configure modular-host and MD host on the same CLC.
•
Symptoms: The message TEK_INVALID_INVALID_KEY_SEQUENCE may display in the logs and after some time, voice calls using DQoS will fail. At the same time, modems that are reset return to the online(pk) state and do not progress to the online(pt) state. Messages, such as UNAUTHSIDTIMEOUT and UNREGSIDTIMEOUT messages also accompany this condition. The condition only affects a single line card on the CMTS.
Conditions: This issue is observed when the packet buffer memory is full, resulting in upstream packets not being received. Simultaneously, downstream packets periodically fail to transmit.
Workaround: Disable DQoS and reset the CLC during a maintenance window.
•
Symptoms: Voice modems on non-HA-capable downstreams that could not be moved to HA-capable downstreams, attempt the move process again after its MAC domain host line card does an N+1 switchover.
The modems will go offline, and comeback online on an HA-capable or the non-HA-capable downstream after the maximum move tries have been exceeded.
Conditions: This issue is observed on the Cisco IOS Release 12.2SC.
•
Symptoms: Active PRE crashes when you perform an OIR from a Cisco MC-2020 to a Cisco 520H line card.
Conditions: This issue also occurs when:
–
–
–
Workaround: There is no workaround.
•
Symptoms: CGD is lost after LCSO and PRE SO.
Workaround: There is no workaround.
•
Symptoms: The active and secondary PREs might crash while attempting to debug a cable DHCP server, after enabling the logging discriminator.
Conditions; This issue is observed on both the PRE2 and PRE4.
Workaround: Remove the logging discriminator or do not execute the debug cable dhcp command.
•
Symptoms: Despite repeated DCC init 3/4 messages, the CMTS continues with its attempts at load balancing a D3 CM, ignoring the messages.
Conditions: This issue is observed when upstream dynamic LB is configured with DCC init tech 3/4 and the D3.0 modem does not respond to DCC messages.
Workaround: Disable dynamic upstream LB or remove the D3.0 modems that does not respond to DCC.
•
Symptoms: The MIB objects docsQos3ServiceFlowOctets and docsQos3ServiceFlowPkts have only 32-bit representation capability.
Workaround: Use the docsIetfQosServiceFlowOctets and docsIetfQosServiceFlowPkts to get the counters.
•
Symptoms: When upstream frequency is changed from 35Mhz to 38MHz, cable modem reports about 7db increment in transmission power.
Conditions: This issue is observed on a Cisco uBR10000 series router with PRE2, and running Cisco IOS Release 12.3(23)BC4.
Workaround: There is no workaround.
•
Symptoms: The LCM dump in PXF crashinfo is empty.
•
Symptoms: After a line card switchover, all downstream service flows are deleted.
Workaround: There is no workaround.
•
Symptoms: The standby PRE4/PRE2 resets/reboots while becoming active after a switch over from active PRE due to a test crash.
Conditions: This issue is triggered by the following configured commands:
exception core-file R7259CMTS-coreexception dump 1.8.65.30Workaround: Unconfigure the exception-related configuration before a test crash.
•
Symptoms: Some CPEs show the following output after an IOS upgrade to SCB3.
ping to PC from CMTS is OKping to PC from Router that is connected to CMTS is failedping to CMTS from CPE is failed.any internet connection from CPE is failedtelnet to CMTS from CPE is OK'ipconfig/release' and 'ipconfig/renew' is OK, so CPE can be re-assigned IP address from DHCP serverConditions: This issue occurs when:
–
–
–
–
Workaround: Clear the IP ARP <mac-address>.
•
Symptoms: A Cisco uBR10000 series router may experience repeated PXF/PRE crashes. The PXF crashinfo starts with the following message:
PXF DMA Toaster Stall ErrorConditions: The issue is observed when the CMTS is configured with a dotlq DOCSIS l2vpn configuration.
Workaround: There is no workaround.
•
Symptoms: The following system event message is not displayed in the receiving syslog server:
wbcmts_idxtbl_assign(): failed. Tbl fullConditions: This issue occurs in rare, severe error conditions, which cause the Stats index table to become full. When this condition persists, other symptoms like modems failing to come online or falling offline after coming online are observed.
Workaround: There is no workaround.
•
Symptoms: The state of external entry keeps flaps in show cable load internal and load may not be balanced after LCSO.
Conditions: This issue occurs after a LCSO.
Workaround: Do not configure cross-line card load balance.
•
Symptoms: WCM on the SPA may go offline after PRESW.
Conditions: This issue is observed when multiple SPAs are present in the system
Workaround: There is no workaround.
•
Symptoms: During ISSU with major MDR testing, the following error message and traceback are observed:
002047: .Sep 17 21:36:10.790: %SPA_OIR-3-OUT_OF_SYNC: bay 1/1: failure code (0x1008)002048: .Sep 17 21:36:10.790: SPA TSM Error: unrecognized error002049: .Sep 17 21:36:10.798: %SPA_OIR-3-EVENT_TIMEOUT: bay 1/0: Timeout waiting for SPA OIR event-Traceback= 60A263D8 605C41D0 605C3A60 6191751C 605C1DA4 605C43C4 6015F328 6015F480Conditions: This issue is observed on a Cisco Wideband SIP and running the Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: The show interface cable x/y/z cable-monitor cam command displays an incorrect hit counter on the last upstream when using an interface with eight upstreams.
Conditions: This issue is observed when using cable monitor on an interface that has cable upstream max-ports set to 8. The hit counters will display 0 for the 8th upstream if cable monitor is not configured. If it is configured to monitor a cable modem using a mac address on that interface, the 8th upstream shows a random number of hits.
Workaround: There is no workaround.
•
Symptoms: Packets are not transmitted on a WB interface in DBS mode, if the last RF channel in the interface is unconfigured and configured, while there still are untransmitted packets in any of the packet queues on that interface.
Conditions: This issue is observed in the following conditions:
1.
2.
Workaround: This issue can be prevented at the following two levels:
1.
2.
However, if the issue has already occurred, execute the micro reload pxf command or perform a switchover on the standby PRE.
•
Symptoms: Service flows are not created for Persistent Gate after a cable modem reset.
Conditions: This issue is observed when cable modem is not BPI enabled.
PCMM persistent gate needs to be set up on the BPI enabled CM. CM should go offlineWorkaround: There is no workaround.
•
Symptoms: The command cable privacy hotlist cm <a.a.a> does not block CMs from coming online.
Conditions: This issue occurs when the modems do not have the appropriate certificates.
Workaround: There is no workaround.
•
Symptoms: On a Cisco uBR10000 series router running Cisco IOS Release 12.2(33)SCB4, the following message may be displayed from one or all CLCs:
SLOT 5/0: Sep 24 10:00:41.586: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x6078B558 reading 0x10SLOT 5/0: Sep 24 10:00:41.586: %ALIGN-3-TRACE: -Traceback= 6078B558 6078D39C 6078D760 608D2FC8 608BA4A0 608B1E28 608ABEE0 608AC320Conditions: There is no known condition for this issue.
Workaround: There is no workaround.
•
Symptoms: When CMTS sends DBC to delete multicast DSID, the DBC sends with option 0 on reseq.
•
Symptoms: Toaster queue statistics are not displayed by executing the show tech-support command.
Conditions: This issue is observed in the Cisco IOS Release 12.2(33)SCB.
Workaround: The data can be collected manually by executing the show pxf cpu queue command for every interface.
•
Symptoms: The following symptoms are observed:
–
–
Conditions: When the CMTS has been running for a few days, a CM that comes online is assigned a previously used DSID that has some residual seq-num in the SRAM. This results in using a non-zero value as a packet sequence number in the DS EHDR of the first packet. Some CMs do not accept non-zero seq num in first packet.
Workaround: There are two workarounds:
–
–
•
Symptoms: The following log message and traceback are seen in the log:
005279: Oct 1 13:19:57.918 CET: %IPCGRP-3-CMDOP: IPC command 400 (slot1/0): undersized command response length-Traceback= 4094109C 409417B8 40B5A51C 40B5AB14 405B5EB8 4055FA08 410F50CC 410F2734 41466D08 4143CE9C 4142B900 4145774C 40A3B7C8 40A3B7B4Conditions: This issue is observed after a configured wideband SPA is removed and an snmpwalk of OID 1.3.6.1.4.1.9.9.479.1.1 or the CLI command show hw-module bay all counters rf-channel is executed.
Workaround: Either replace the WB-SPA or unconfigure the relevant controller modular-cable.
•
Symptoms: After running an overnight multicast test, a memory leak is seen at cr10k_clc_snmp_do_trap on 2020 line card. As a result, continuous IPC tracebacks are seen on the console and the RP is not able to communicate with the 2020 line card.
Conditions: This issue occurs when:
1.
2.
3.
4.
•
Symptoms: When the configuration changes the non-primary channel on the peer protect card to primary channel, and add it to the MD with active mcast sessions, it causes the peer protect card to crash.
Conditions: This issue is observed when the channel is a non-primary channel on the card, which means some wideband channel include this RF channel and on the same fiber node with the primary channels on the card.
Workaround: Tear down the multicast session before changing the configuration and perform the IGMP join again after the configuration change is done.
•
Symptoms: Crash occurs on the CMTS.
Conditions: This issue is observed when the modular-host is changed while the CMTS is running.
Workaround: There is no workaround.
•
Symptoms: A PRE-4 line card hangs during boot up, and before a configuration. However, this issue does not affect all PRE-4 RPs.
Conditions: This issue is observed during the basic booting of PRE-4.
Workaround: There is no workaround.
•
Symptoms: An OIR results in a crash.
Conditions: This issue is observed when a PCMCIA card is extracted and inserted back rapidly.
Workaround: Wait for a few seconds after extracting a card or before inserting it back.
•
Symptoms: While changing a multicast video channel rapidly, within a short period of time, the CMTS may reject new IGMP join because of insufficient BW.
Conditions: This issue is observed when a single MQoS SF is used, with larger CIR parameters and an influx of channel changes.
Workaround: Use "aggregate" MQoS SF instead of "Single".
•
Symptoms: A CMTS line card occasionally crashes with the traceback pointing to data that corrupts while performing DBC operation.
Conditions: This issue occurs while executing the clear cable interface command while stress testing the VDOC and multicast traffic.
Workaround: Do not execute the clear cable interface command.
•
Symptoms: If you change the channel-ID of a MAC Domain interface that has modems online, the modems stop responding.
Conditions: This issue occurs when channel-id in MAC Domain are changed.
Workaround: Do not change channel IDs of MAC Domains when the domains have modems w-online.
If required, change the channel-IDs of the new MAC Domains on the newly inserted LC before moving modems to this newly added line card.
•
Symptoms: CBT 3.3 Continuous Sweep Function fails after some time when performed on Cisco uBR10000 series routers with PRE-4 linecards.
Conditions: This issue is observed on the Cisco IOS Release 12.2(33)SCB4. This issue occurs as a result of the following MIB object returning a value of "10":
CISCO-CABLE-SPECTRUM-MIB::ccsSpectrumRequestTable - ccsSpectrumRequestOperState
Workaround: There is no workaround.
•
Symptoms: During the ISSU regression test from SCB 4 to SCB 5, a traceback is observed during ISSU PRE runversion.
mars#issu runversion BConditions: This issue is observed during a regression test where the ISSU upgrade is performed from an SCB 4 to SCB 5.
Workaround: There is no workaround.
Open Caveats—Cisco IOS Release 12.2(33)SCC
•
Symptoms: The Cisco uBR10012 router generates the following message when the cable modem (CM) fails to come online for a long duration.
UBR10000-6-BADIPASSIGNMENT: DHCPOFFER dropped : Interface Cablex/y/zMac abcd.efgh.ijkl SID 2205 L3_Interface Cablex/y/z IP x.y.z.talready assigned to MAC=mnop.qrst.uvwx Interface Cablex/y/z SID 6367Conditions: This issue occurs when a cable modem (CM) is provisioned using an external DHCP server. The CM takes some hours to initialize.
Workaround: Reset the cable card to fix this issue.
•
Symptoms: The active DOCSIS queues remain active in the event of a DOCSIS SPA failure.
Conditions: This issue occurs when online cable modems passing traffic on the modular-cable and on wideband-cable interfaces and the DOCSIS SPA fail. The DOCSIS queues associated with these online modems remain active, attempting to dequeue.
Workaround: Execute the microcode reload {pxf} command.
•
Symptoms: The Gigabit Ethernet interface on an ESR-1GE fails to send packets.
Conditions: This issue occurs just after performing online insertion and removal (OIR) of an ESR-1GE with low rate.
Workaround: Execute the hw-module slot reset command.
•
Symptoms: The Cisco uBR10012 router crashed because it ran out of unfragmented memory and the following message was displayed:
%SYS-2-MALLOCFAIL: Memory allocation of65536 bytes failed from 0x60A33948, alignment 16Pool: Processor Free: 44813096 Cause: Memory fragmentationAlternate Pool: None Free: 0 Cause: No Alternate pool-Process= "IP ARP Adjacency", ipl= 2, pid= 176%COMMON_FIB-3-NOMEM: Memory allocationfailure for fib entry insertion in IPv4 CEF [0x606164D0] (fatal) (1subsequent failure)Conditions: This issue was first seen in Cisco IOS Release 12.2(33)SCB on a PRE2 module.
Workaround: There is no workaround.
•
Symptoms: Cable modems do not respond to Layer 3 pings.
Conditions: This issue is on the Cisco uBR10-MC5X20U-D card.
Workaround: Restart the cable line card.
•
Symptoms: A multicast QoS session is not automatically created when changing group configuration.
Conditions: This issue occurs when a multicast QoS group is configured on a bundle interface and a matching static-group is defined. However, any change in the group configuration after it is applied to the bundle interface is not implemented, and the original multicast QoS session is removed.
Workaround: Remove the multicast QoS session from the bundle interface and reapply the QoS session to the bundle.
•
Symptoms: Alignment traceback messages are found after the execution of show memory leak res user and show buffer usage commands.
Conditions: This issue occurs when show memory leak res user and show buffer usage commands are executed.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed due to SID management task.
Conditions: This issue occurs when the PacketCable calls are present.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed on the line card due to overnight PC calls on the MAC parser.
Conditions: This issue occurs while running PacketCable calls.
Workaround: There is no workaround.
•
Symptoms: Online insertion and removal (OIR) of a PCMCIA flash disk causes a reset of the PRE module.
Conditions: This issue occurs during OIR of the PCMCIA flash disk that is being actively accessed.
Workaround: Restrict the removal of PCMCIA flash disks.
•
Symptoms: Multiple cable modems (CMs) go offline for a short time on a random upstream port. This is seen as a spike of the error-per-second rate or a modulation error ratio (MER) drop and by a decrease in the "docsIfSigQUnerroreds" MIB object.
Conditions: This issue occurs on a Cisco uBR10012 router with Cisco uBR10-MC5x20H cards. The issue is not seen on Cisco uBR7246VXR router.
Workaround: There is no workaround.
•
Symptoms: Entries in the MIB object "docsBpi2CmtsMulticastObjects" duplicate after the line card revertback after a switchover.
Conditions: This issue occurs when cable match command with is configured with the Baseline Privacy Interface (BPI) is configured.
Workaround: There is no workaround.
•
Symptoms: Cable modems (CMs) that are not capable of downstream bonding are expected to come online on downstreams that are not part of a bonding group. Non-bonding capable CMs are wrongly registered in bonded channels.
Conditions: This issue occurs when the cable service attribute non-ds-bonded downstream-type bonding-disabled command is configured on the Cisco CMTS.
Workaround: There is no workaround.
•
Symptoms: Active PRE fails over to the secondary reporting.
Conditions: This issue was first seen in Cisco IOS Release 12.3(23)BC7.
Workaround: There is no workaround.
•
Symptoms: While configuring the cable upstream docsis-mode command using SNMP, the standby PRE module does not synchronize with this configuration.
Conditions: This issue occurs when configuring the cable upstream docsis-mode command using SNMP.
Workaround: Configure the cable upstream docsis-mode command using the CLI instead of SNMP.
•
Symptoms: The show interface multicast-session command shows wrong multicast session instances.
Conditions: This issue occurs when one matching group QoS configuration (GQC) of type aggregate is created and two sessions of IGMP join are sent. This occurs when a send leave request is executed first for session 1 and then for session 2, and then a rejoin request is executed for the session 2 immediately after session 1 is deleted.
Workaround: There is no workaround.
•
Symptoms: The Cisco SIP-600 goes down and comes up due to the software watchdog reset on a Cisco uBR10012 router.
Conditions: This issue occurs when the software watchdog is reset on the Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptoms: The standby PRE module crashes during initial configuration with features such as crypto certificates, multicast, and IPv6 configured.
Conditions: This issue occurs when a configuration file with the above features is copied directly from a file to the running configuration and both the active and standby Route Processors (RPs) are booted with no configuration, the standby RP reloads unexpectedly.
Workaround: Ensure that the standby RP is up and available, after the initial running configuration file is saved to the startup configuration file.
•
Symptoms: The Cisco Wideband SPA does not transmit traffic. The EQAM indicates no input traffic.
Conditions: This issue is seen on the Cisco SIP-600 with a PRE4 module, 5 x1 GigabitEthernet interface, and SPA-24XDS-SFP Wideband SPAs.
Workaround: Perform a PRE module reload.
•
Symptoms: Around 60 to 70 bytes of buffer memory space is allocated when the protect line card becomes active after a system bootup.
Condition: This issue occurs during a line card switchover.
Workaround: There is no known workaround.
•
Symptoms: Some cable modems (CMs) may go offline during a line card switchover.
Condition: This issue occurs during a switchover of the protect Cisco uBR-MC5x20H line card and the working Cisco uBR-MC5x20U line card.
Workaround: Reduce the number of modems connected to the Cisco uBR-MC5x20U line card.
•
Symptoms: The Cisco CMTS is unable to ping some Wideband CMs.
Condition: This issue occurs in rare conditions.
Workaround: Reload the Cisco Wideband SPA and the Cisco SIP-600.
•
Symptoms: All Wideband cable modems (CMs) on Cisco Wideband SPA go offline unexpectedly. Only SYNC packets, which are from the SPA are sent but packets (such as MDD, Secondary MDD, UCD, MAP, and so on) from Cisco uBR-MC5X20 line card are not sent.
Conditions: This issue occurs when channel bonding with DOCSIS Timing Interface (DTI) is configured.
Workaround: Perform Cisco Wideband SPA Online Insertion and Removal (OIR).
•
Symptoms: After PRE switchover, the service flow counter shows 0 on the Cisco uBR10012 router.
Conditions: This issue occurs during a PRE switchover.
Workaround: There is no workaround.
•
Symptoms: No syslog or SNMP trap messages are generated when the Common Open Policy Service (COPS) process forPacketCable fails.
Conditions: This is occurs in a PacketCable environment where the COPS session fails.
Workaround: There is no workaround.
•
Symptoms: Executing the term len 0 and show cable modem commands pauses the generated output randomly for up to a second on PRE4 module with hundreds of CMs.
Conditions: This issue occurs on PRE4 module with hundreds of CMs.
Workaround: There is no workaround.
•
Symptoms: Syslog messages indicate a line card crash followed less than a minute later by a PRE failover.
Conditions: This issue occurs when a query of the "cefcFRUPowerSupplyGroupTable" MIB object does not occur at the time of PRE failover.
Workaround: There is no workaround.
•
Symptoms: Wideband modems do not come w-online state and are often flapping in reject(c) state. IPC troubleshooting reveals IPC issues such as ubr-test-request-api x/y block commands fails.
Condition: This issue occurs on a Cisco ubR10012 router with DOCSIS 3.0 Wideband configured on Wideband-capable modems.
•
Symptoms: There is an incorrect Wideband cable association after a cable line card is powered off..
Conditions: This issue occurs only after a cable line card is powered off.
Workaround: There is no workaround.
•
Symptoms: The following system event message does not reach the receiving syslog server:
Sep 11 07:43:25 CDT: wbcmts_idxtbl_assign(): failed. Tbl full.Conditions: This issue occurs under rare, severe error conditions, which cause the Stats index table to fill up. When this condition persists, other symptoms such as cable modems failing to come online or falling offline, after coming online, is seen.
Workaround: Monitor the Route Processor (RP) console logs. Check for the message if modems fail to come online or fall offline.
•
Symptoms: When transmitting distributed QoS (DQoS) Lite voice calls, the downstream service flows are listed on the committed information rate (CIR) queue instead of Low Latency Queuing (LLQ), if PacketCable is not enabled in the Cisco CMTS configuration
Conditions: This issue occurs when the PacketCable is not configured on the Cisco CMTS and DQoS Lite or vanilla DOCSIS voice calls are performed.
Workaround: Configure the following commands:
–
–
The above commands do not impact the current configuration.
•
Symptoms: A memory leak was observed in the Pool Manager process on the Cisco CMTS.
Conditions: This issue occurs when QoS is configured.
Workaround: There is no workaround.
•
Symptoms: Policy Based Routing (PBR) using the set ip next-hop command with multiple next-hops does not work. The second available next-hop is skipped when Address Resolution Protocol (ARP) of the first hop times out after the first next-hop goes offline.
Conditions: This issue was first seen in Cisco IOS Release 12.2(33)SC4.
Workaround: Configure "PBR Support for Multiple Tracking Options" that is designed to detect whether the next-hop is active or not. Refer to the PBR Support for Multiple Tracking Options Guide for more configuration information.
•
Symptoms: After a Stateful Switchover (SSO), the modular association of cable interface with downstream cable controller is incorrect. The show controller cable command displays the modular interface is up, though it is not configured.
Conditions: This issue occurs after an SSO.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR-MC5X20U-D card crashes multiple times with the following message in the crashinfo file:
Address Error (load or instruction fetch) exception, CPU signal 10, PC = 0x6038C709Conditions: This issue has been observed on the Cisco uBR10012 router with PRE2 module.
Workaround: There is no workaround.
•
Symptoms: The show memory debug leak command shows a large number of buffer leaks for the Security Association (SA) map request count.
Conditions: This issue occurs when a large number of SA map requests are received from multiple modems connected on the line card.
Workaround: There is no workaround.
•
Symptoms: The cable modems (CMs) do not come online or comes online and quickly flap offline on interfaces with remote primary narrowband values. The show cable modem primary summary total command shows non-zero blaze indices as non-zero.
Remote Primary Narrowband:Mo1/0/0:0 31 31 31 0 0 0 0 0 0 0 0Mo1/0/0:3 23 23 23 0 0 0 0 0 0 0 0Mo1/0/0:6 25 25 25 0 0 0 0 0 0 0 0Mo1/0/0:9 34 19 19 15 12 0 0 0 1 1 17 <<<<<Mo1/0/0:12 33 33 33 0 0 0 0 0 0 0 0Subtotal: 146 131 131 15 12 0 0 0 1 1 17Condition: This issue occurs in a PRE module failover.
Workaround: Power cycle the affected line card.
•
Symptoms: Users with privilege levels lower than enable access are unable to execute some show cable command options.
Conditions: This issue was observed with the show cable mac-domain command and its downstream-service-group option that displays downstream channel information for wideband cable modems.
Workaround: Repeat the privilege level command in a more granular way. For example, the command needs to be repeated for each interface as follows:
privilege exec level 1 show cable mac-domain c5/0/0 downstream-service-groupprivilege exec level 1 show cable mac-domain c5/0/1 downstream-service-groupprivilege exec level 1 show cable mac-domain c5/0/2 downstream-service-group..privilege exec level 1 show cable mac-domain c8/1/4 downstream-service-group•
Symptoms: The Cisco CMTS console freezes up and eventually crashes.
Conditions: This issue occurs when configuring IGMP static-group after configuring the group configuration on the bundle interface
Workaround: Configure static-group before the group configuration.
•
Symptoms: Cable line card crashes with PacketCable Multimedia (PCMM) voice call testing.
Conditiosn: This issue was seen in multi-line Cisco Analog Telephone Adaptor (ATA) behind cable modems (CMs) in a PCMM setup.
Workaround: There is no workaround.
Resolved Caveats—Cisco IOS Release 12.2(33)SCC
•
Symptoms: The DHCPv6 relay process crashes on the active Route Processor (RP).
Conditions: The condition is unknown.
Workaround: There is no workaround.
•
Symptoms: A crash occurs due to a bus error after displaying the following error messages:
%DATACORRUPTION-1-DATAINCONSISTENCY: copy error,%ALIGN-1-FATAL: Illegal access to a low address < isdn function decoded>Conditions: This issue was first observed on a Cisco 3825 running Cisco IOS Release12.4(22)T with ISDN connections going on. At the moment of the crash, the router was being monitored using an SNMP Get program. After some minutes, the router reloaded by automatically.
Workaround: There is no workaround.
•
Symptoms: Erroneous routing prefixes are added to the routing table.
Conditions: This issue occurs when the DHCPv6 relay feature is enabled and a router receives a normal DHCPv6 relay reply packet, which leads to an erroneous route being added to the routing table.
Workaround: There is no workaround.
•
Cisco devices running affected versions of Cisco IOS Software are vulnerable to a denial of service (DoS) attack if configured for IP tunnels and Cisco Express Forwarding.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-tunnels.shtml.
•
Cisco IOS devices that are configured for Internet Key Exchange (IKE) protocol and certificate based authentication are vulnerable to a resource exhaustion attack. Successful exploitation of this vulnerability may result in the allocation of all available Phase 1 security associations (SA) and prevent the establishment of new IPsec sessions.
Cisco has released free software updates that address this vulnerability.
This advisory is posted at http://www.cisco.com/warp/public/707/cisco-sa-20090923-ipsec.shtml
•
Symptoms: The DOCSIS Timing and Control Card (DTCC) (Eightbells) main field-programmable gate array (FPGA) is not fully functional in standalone mode and requires an upgrade.
Conditions: This issue occurs in standalone mode.
Work around: Upgrade the DTCC card.
•
Symptoms: After upgrading to Cisco IOS Release 12.2(33)SCB3, some CPEs cannot communicate with the Cisco CMTS.
Conditions: This issue is seen after upgrading to Cisco IOS Release 12.2.(33)SCB3, when DOCSIS Timing Interface (DTI) is used with a wideband cable modem. This issue occurs when the cable modem (CM) assigns a private IP address to a CM before connecting to the CMTS, and when the CMTS reassigns the IP address from the DHCP server.
Workaround: Execute the clear ip arp command.
•
Symptoms: The following log message and traceback are seen in the log after a configured Cisco Wideband SPA is removed::
005279: Oct 1 13:19:57.918 CET: %IPCGRP-3-CMDOP: IPC command 400 (slot1/0): undersized command response length-Traceback= 4094109C 409417B8 40B5A51C 40B5AB14 405B5EB8 4055FA08 410F50CC 410F2734 41466D08 4143CE9C 4142B900 4145774C 40A3B7C8 40A3B7B4Conditions: This issue occurs after a configured Cisco Wideband SPA is removed and snmpwalk command is executed or show hw-module bay all counters rf-channel command are executed.
Workaround: Either replace the Cisco Wideband SPA or unconfigure the relevant controller modular-cable.
•
Symptoms: Internal accounting of the number of MAC domains is incorrect.
Conditions: This issue occurs after a bootup.
Workaround: There is no workaround.
•
Symptoms: A crash is observed on the Cisco CMTS after online insertion and removal (OIR) of the PCMIA card.
Conditions: This issue occurs in rapid insertion or extraction of the PCMCIA card.
Workaround: Wait for a few seconds after extracting a card and before inserting it back.
•
Symptoms: When changing video multicast channel quickly within a short period of time, the Cisco CMTS rejects new IGMP joins because of insufficient bandwidth.
Conditions: This issue occurs when Multicast QoS (MQoS) is used with large committed information rate (CIR) parameters and an influx of channel changes.
Workaround: Use aggregate control type MQoS service flows instead of single control type service flows.
•
Symptoms: The IGMPv3 client stops receiving multicast traffic when the client rejoins the same session.
Conditions: This issue occurs if Security Association Identifier (SAID) encryption is the same on the Cisco CMTS.
Workaround: Reset the cable modem.
•
Symptoms: The cable modem (CM) is stuck in reject(c). Enabling the debug cable tlv and the debug cable mac-address <cm-mac> verb commands shows the following log:
SLOT 4: Oct 15 13:16:23.379: Found Upstream Service Flow TLVSLOT 4: Oct 15 13:16:23.379: Service Flow Reference : 1SLOT 4: Oct 15 13:16:23.379: Service Class Name String Length 16, Exceeds Limit of 15SLOT 4: Oct 15 13:16:23.379: PARSER-ERROR: TLV 4 has bad length 16SLOT 4: Oct 15 13:16:23.379: Primary CoS/Sflow encodings missing. CoSs:0 Sflows[US, DS]: [1, 0]SLOT 4: Oct 15 13:16:23.379: Registration failed for Cable Modem 001a.c3ff.d77e on interface Cable4/0/U1:CoS/Sflow/Cfr/PHS failed in REG-REQ-MPConditions: This issue occurs when the config file includes 15 bytes of the service class name string for upstream or downstream service flow.
Workaround: Change the service class name to string less than 15 bytes.
•
Symptoms: The CPE lost multicast traffic after line card switchover.
Conditions: This issue occurs when the ETDB and Downstream Service Identifier (DSID) entries are removed during Cisco UBR-MC20X20 line card high availability.
Workaround: There is no workaround.
•
Symptoms: The Baseline Privacy Interface (BPI) index information is missing from the show controller command.
Conditions: This issue occurs on the working card or standalone card.
Workaround: There is no workaround.
•
Symptoms: The line card crashes with traceback pointing to data corrupted when performing Dynamic Bonding Change (DBC) operation.
Conditions: This issue occurs when the clear cable interface command is executed.
Workaround: Do not execute the clear cable interface command.
•
Symptoms: Attribute-based service flow assignment does not work.
Conditions: This issue occurs when the attribute-mask configuration is changed under the wideband interface after booting up the chassis, and a line card switchover occurs.
Workaround: Perform a line card switchover and revertback.
Open Caveats—Cisco IOS Release 12.2(33)SCB4
•
Symptoms: Wideband modem downstream throughput rate is not yet supported.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10012 router may generate the following message:
UBR10000-6-BADIPASSIGNMENT: DHCPOFFER dropped : Interface Cablex/y/zMac abcd.efgh.ijkl SID 2205 L3_Interface Cablex/y/z IP x.y.z.talready assigned to MAC=mnop.qrst.uvwx Interface Cablex/y/z SID 6367Conditions: The cable modem may be stuck in init(d) for some hours before coming online. The Cable Modems are provisioned by an external DHCP server.
Workaround: If it is not possible to wait for the CM to come up, then a cable card reset will fix the issue.
•
Symptoms: In syntax check mode, if there is a standby in SSO mode, the cts dot1x command does not work.
Workaround: There are no workarounds.
•
Symptoms: The throughput rate shows (slightly) more than the expected range.
Conditions: This happens when the DMIC feature is enabled and the modem is marked with given maximum rate values. This can also happen when the QoS profile has lower maximum rates.
Workaround: There are no workarounds.
•
Symptoms: 12.3(23)BC2 mixed docsis mode (atdma-tdma) can only achieve 40 UGS for an upstream. But, 12.3(17b)BC9 can achieve 48 UGS flows.
Conditions: Currently, it looks like this may have something to do with mixed mode and modems.
Workaround: There is no workaround.
•
Symptoms: Multicast stream drop, after changing the "ip igmp query-interval". The following show the output before and after the change:
Before the change:
Router# show ip mroute<<..skipped..>>(, ), 01:09:04/00:02:52, flags: sTIIncoming interface: TenGigabitEthernet1/1, RPF nbr 10.x.x.x, RPF-MFDOutgoing interface list:Vlan50, Forward/Sparse, 00:48:45/00:02:52, H <<====After the change:
Router# show ip mroute<<..skipped..>>(, ), 01:28:19/00:02:36, flags: sPTIncoming interface: TenGigabitEthernet1/1, RPF nbr 10.x.x.x, RPF-MFDOutgoing interface list: Null <<====Conditions: The issue is was first seen in a Cisco 7600 chassis with a Supervisor 720 engine running Cisco IOS Release 12.2(33)SRB.
Workaround: There is no workaround.
•
Symptoms: Inactive sessions are observed in the multicast explicit tracking database.
Conditions: This issue is seen when IGMP leave is received for a group followed by a CLC switchover.
Workaround: There is no workaround.
•
Symptoms: When a modem comes up during off-peak time when it is not supposed to be monitored, as per the enforce-rule configured, the SNMP is not synced to the standby line card.
Conditions: This issue is seen if a line card switchover is done during off-peak time. Even if the modem enters the peak time, iti s not monitored as per the enforced rule configured. The SNMP is synced to the standby line card once the modem is monitored during the peak time.
•
Symptoms: CMTS crashes and the following error message is seen when the no ip routing or the no router bgp xx command is run.
%IPRT-3-IPDB_DEL_ERROR: i_pdb delete error bgp, 4, 210074C8, 20E322E0, 0, 0 -Process= "IP RIB Update", ipl= 0, pid= 117, -Traceback= 0x61FD7F58 0x62005498 0x62006D24Conditions: A large number of VRFs must be configured and BGP is also configured to support these VRFs.
Workaround: There is no workaround.
•
Symptoms: The show controller modular-cable 1/0/0 command displays that rf-channel 0 becomes unknown after a SPA hw-module reset.
Conditions: This issue occurred executing the hw-module reset and show diagnostic 1/0/0 commands. This causes all wideband modems also to go online.
Workaround: Reload the router to fix the issue.
•
Symptoms: The upstream ports configured as HCCP protect show the port link down when executing the show facility-alarm status command.
Conditions: This issue is seen when the cable line card is configured as HCCP protect, and the router is running a later image version than Cisco IOS Release 12.3(23)BC2.
Workaround: There is no workaround.
•
Symptoms: For deleted service flows associated with PCMM calls, the last character in the Service Class Name field is dropped in SAMIS records as well as in the SNMP MIB object "docsQosServiceFlowLogServiceClassName".
Conditions: This issue is seen when the dynamic service flows associated with PCMM calls are deleted. The last character is missing from the service class name in the MIB object "docsQosServiceFlowLogServiceClassName" and SAMIS records.
•
Symptoms: While executing the clear counter command, service flow statistics are not getting cleared under the wideband interface.
Conditions: This issue is seen in cases of multicast and the forwarding is through the wideband interface. Multicast service flows are created and the counters are maintained under the wideband interfaces.
Workaround: There is no workaround.
•
Symptoms: Both the working card and protect card are active.
Conditions: This issue is seen when a line card switchover happens from 5/0 to 5/1. After synchronization, shut down the 5/0/2 interface, and then revert from 5/1 to 5/0. If the 5/0/2 interface is not shut down, and after the suspend timer interval expires, both 5/0 and 5/1 are active.
Workaround: Do not shut down an active protect interface. If both the cards (working and protect) are active, reset the protect card.
•
Symptoms: Cable metering fails and enters a "hung" state.
Conditions: The issue happens when the "ip tcp timestamp" option is configured globally.
Workaround: Do not use the "ip tcp timestamp" option.
•
Symptoms: Traffic fluctuation only happens when the WB/MC topology and traffic rate are exactly the same.
Conditions: This issue is seen in Cisco IOS release 12.2SC with HQF scheduler. When 46 pecent of bandwidth is allocated to Channel 0 for MC0 and 46 percent of the bandwidth is allocated to Channel 1 for MC1,the rest of the bandwidth is allocated to WB0.
Thus, the traffic rate of WB is higher than the configured percentage. The traffic rate of MC0 is a little lower than the configured percentage and the traffic rate of MC1 is a little higher than the configured percentage.
Workaround: Do the following:
–
–
–
•
Symptoms: During line card high availability, the CM instance bpi_enable flag on the Route Processor (RP) is not synced over correctly.
Conditions: This issue is seen while generating multicast stream to CMs, and if BPI CM is used during a line card switchover.
Workaround: There is no workaround.
•
Symptoms: The MAC Domain Descriptor (MDD) change message is generated on all the RF channels globally for any RF channel configured on the CMTS.
Conditions: This issue occurs when an MDD change is supposed to be generated for channels within the MAC domain.
Workaround: There is no workaround.
•
Symptoms: When a Cisco uBR10012 router has a lot of CMs, the show cable modem docsis version summary command total may not be able to display each column properly because there is not enough space between columns.
Conditions: This issue is seen when there are a lot of cable modems. This issue is seen in Cisco IOS Release 12.3(23)BC and Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: When the cable sync-interval command is configured, the cable interface needs to execute a shut or no-shut command for the interval change to take effect.
Conditions: This issue occurs while configuring the cable sync-interval command.
Workaround: There is no workaround.
•
Symptoms: The downstream Committed Information Rate (CIR) reservation for wideband cable modems works as expected, however they are displayed incorrectly under admission control command.
Conditions: This issue is seen in any w-online state wideband cable modem with non-zero CIR reservations. It displays the CIR reservation as 0 although the reservation admit or unadmit works properly. The show interface admission-control reservation downstream command displays the 0 CIR for the wideband CM.
Workaround: Use the show cable modem qos command to display the correct reservation.
•
Symptoms: When either Cisco uBR-MC5X20U/S/H card MAC domains have wideband associations, a traceback may be observed along with a message similar to the following when NO CARD x/x is used:
*Jan 25 05:41:57.235 PST: %SYS-3-BADLIST_DESTROY: Removed a non-empty list(2F3F7BF4, name: (unknown)), having 36 elements -Process= "C10K Card Actions", ipl= 0, pid= 75A small amount of memory leak may also happen. No other side effects are expected.
Conditions: This traceback is seen only if the card had a NB-WB association previously, and was powered down or removed.
Workaround: There are no workarounds.
•
Symptoms: Port-channel interfaces used in conjunction with 802.1q subinterfaces show a number of problems on both the PRE4 and PRE2 processor modules. This was observed while testing the Cisco SPA-5X1GE-V2 in Cisco IOS Release 12.2(33)SCB. The problem appears to be with the 4-jacket WAN interface, and not with the older half-height Gigabit Ethernet interfaces.
Conditions: This issue occurs in a PRE2 processor module under the following conditions:
–
–
This issue occurs in a PRE4 processor module under the following conditions:
–
–
Workarounds: To restore the traffic, do the following:
1.
2.
3.
4.
Theoretically, you can boot the CMTS with no Ethernet channel configured, and copy an edited production configuration file to running-config after all the interfaces are up.
•
Symptoms: The w-online state modem comes online after protect line cards are reset before a resynchronization.The CMTS is configured with N+1 redundancy. If the working line card (7/0) is reset, the modem switches to protect (5/0). If the protect (5/0) line card is reset before resynchronization, the modem disappears, and comes in online instead of being in the w-online state.The clear cable modem reset command does not work to bring the modem back to the w-online state.
Conditions: This issue occurs while resetting an active line card during the standby line card bootup period, but before the static synchronization of an active to standby line card finishes.
Workaround: Reload the line card or the CMTS.
•
Symptoms: An IRONBUS_FAULT is displayed while pulling out the Cisco SIP-600.
Conditions: This issue is seen in Cisco IOS Release 12.2(33)SCB image running on a Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptoms: A spurious memory access was observed on a cable line card when Online Insertion and Removal (OIR) of the Cisco SIP-600 was done on a PRE 4 processor module.
Conditions: This issue is observed on PRE 4 processor module with an active wideband SPA.
Workaround: There is no workaround.
•
Symptoms: The show cable bundle multicast command does not display the entire bundle in the interface column.
Conditions: This issue is seen in the output of the show cable bundle multicast command.
•
Symptoms: Multimedia Terminal Adaptor (MTA) CMs are not accessible from the CMTS or Internet because the ARP entry is replaced with an all-zero MAC address. Hence it is not accessible when a crafted packet is sent.
Conditions: This issue occurs when a crafted packet is sent to the CMTS, causing the CMTS to use the wrong MAC address for the ARP table.
Workaround: Execute the cable source-verify dhcp server x.x.x.x command, where x.x.x.x is your DHCP server, and use cable arp filter to limit the potential ARP storm.
•
Symptoms: Wideband CMs using a stats index are not managed by the modular-host. This causes two modems using the same Blaze header stats index, thus leading to incorrect downstream traffic statistics on these modems.
Conditions: This issue occurs when there are wideband modems in the w-online state and a change is made to the downstream channel ID of the MAC domain host of these wideband modems.
Workaround: There is no workaround.
•
Symptoms: The output of "sid" is incorrect in the show cable modem x.x.x.x service-flow [verbose] command.
Conditions: This issue is seen in Cisco IOS Release 12.3(23)BC and Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: Traceback and IPC error messages may appear after the CMTS is loaded with the Cisco IOS Release 12.2(33)SCB1 image.
Conditions: This issue is seen in routers running Cisco IOS Release 12.2(33)SCB1.
Workaround: There is no workaround.
•
Symptoms: The show pxf cable multicast-echo does not display the entire interface when the subinterface is greater than 13 characters.
Conditions: This issue is seen for subinterfaces greater than 13 characters.
•
Symptoms: Modifying the second-choice-channel-width has no affect on the configuration even though the cable upstream channel-width command accepts the input.
Conditions: This issue is seen in Cisco IOS Release 12.3BC.
Workaround: Modify the first-choice-channel-width, and then reconfigure the first and second choice.
•
Symptoms: The packet drop counter is not getting updated in show interface service-flow counter for single-session multicast service-flows
Conditions: This issue is seen in single session multicast service-flows.
•
Symptoms: No multicast-session is permitted when cable multicast authorization profile (mauth) is enabled and the debug messages display "session limit reached".
Conditions: This issue is seen in the following conditions:
–
–
–
–
–
Workaround: Delete the cable modem and allow the modem to come online with second cable modem configuration (non-mauth cm-file).
•
Symptoms: The CMTS may initiate DCC/DSA/DSC when Dynamic Bonding Change (DBC) is outstanding.
Conditions: If the customer is running Video over DOCSIS (VDOC) and Cisco Load Balancing (or CMTS initiated DSA) with a DPC3000, the CMTS makes VDOC higher priority over load balancing (or CMTS-initiated DSA) when a DBC is outstanding. According to DOCSIS 3.0 specifications, the CMTS must not issue a DCC or DSA/DSC command when it has previously issued a DBC command and that command is still outstanding.
Workaround: There is no workaround.
•
Symptoms: CMTS does not reject the CM-initialized DSC/DSA messages during Dynamic Bonding Change (DBC) or Dynamic Channel Change (DCC).
Conditions: This issue is seen if the customer is running Video over DOCSIS (VDOC) with a Cisco DPC3000 cable modem, and the CM is making a DSA call. The CMTS responds with a confirmation code of "reject-temporary" for the DSA-REQ or DSC-REQ for Annex B.
Workaround: There is no workaround.
•
Symptoms: After issuing the no cable trust command on the active PRE module, that same command is not removed from the standby PRE module and as a result the active and standby PRE modules are out of sync.
Conditions: This behavior is only seen if the MAC address used in the cable trust command does not exist in the CMTS.
Workaround: There is no workaround.
•
Symptom: Traffic does not resume after a PRE module switchover and modems are not accessible after a PRE module switchover.
Conditions: This issue occurs after a PRE module switchover and "cef"is not running in the standby PRE module.
Workaround: There is no workaround.
•
Symptoms: After unconfiguring the cable source-verify dhcp command, the "SrcVfy" field continues to display "On".
Conditions: This is seen when the cable ipv6 source-verify and cable source-verify dhcp commands are configured on the same bundle interface, and when the cable source-verify dhcp command is unconfigured before the cable ipv6 source-verify command.
•
Symptoms: When configuring cable upstream threshold cnr-profile snr-profile, the parser shows and accepts the second threshold value. It does not give an error message, and does not display the configuration with only the first threshold value.
Conditions: This issue is seen while configuring the CNR and SNR thresholds for modulation profiles.
Workaround: Either enter any valid threshold value or "0" to bypass.
•
Symptoms: The value range of the MIB object "ccmtrCollectionInterval" is not consistent with the command. The valid range for MIB object is 15 to 1440, but for the command, the range is 2 to 1440.
Conditions: This issue occurs while setting the MIB object "ccmtrCollectionInterval" using the SNMP set operation.
Workaround: Set the interval using the command.
•
Symptoms: A memory leak was observed after deleting the subinterface.
Conditions: This issue is seen while deleting a subinterface.
Workaround: There is no workaround.
•
Symptoms: When applying modulation profiles to an upstream port, the modulation profiles are re-ordered, high performance to robust/low performance. Modifying the order of the modulation/symbol rate on the profile does not happen.
Conditions: If the signal-to-noise ratio (SNR) threshold is set at 25 with a hysteresis of 2 (bypassing all FEC), the modulation on the upstream will be QPSK until the SNR falls below 25 dB where it will change to 16-QAM. When the SNR reaches 27 dB (25 dB + 2 dB), the modulation reverts to QPSK. When a line card switchover is performed, the modulation profiles are re-ordered on the protect card.
Workaround: Remove and re-apply modulation-profile configuration on the upstream port after modifying the modulation profiles.
•
Symptoms: A memory leak was observed after executing the multicast test case.
Conditions: This issue is seen when the cable multicast group-qos and cable multicast qos group priority commands are unconfigured.
Workaround: First unconfigure the session-range using the cable multicast qos group priority command.
•
Symptom: Removing the line card configuration causes %LINEPROTO-5-UPDOWN and scm sum total, scm vendor sum, and scm show modem commands show no CMs.
Conditions: This is seen when line card high availability is removed and while executing scm sum total, scm vendor sum. and scm show modem commands.
Workaround: There is no workaround.
•
Symptoms: PXF forwards traffic up to 300 Mbps to the Route Processor (RP) using 1500-byte IPv6 packets.
Conditions: This issue occurs when Physical Logical Bandwidth Limiting Traffic (PBLT) for the RP CPU queue is set to 300 Mbps. The show pxf cpu queue command displays this information.
Workaround: Change the value to 44 Mbps (DS3 Bandwidth) for the PRE2 processor module and 1.6 times 44 Mbps for the PRE4 processor module.
•
Symptoms: The MIB object "entPhysicalName" for theCisco uBR10012 router does not display the values correctly. The values as displayed as slot 0/0/0 and slot 0/1/0 for the PRE processor modules instead of being displayed as 0A and 0B from left to right. Similarly, the MIB object "entPhysicalName" returns slot x/x/x (for example, 1/0/0) instead of the values displayed in the device.
Conditions: This issue occurs while querying the MIB object "entPhysicalName".
Workaround: There is no workaround.
•
Symptoms: When applying new RF channels in Cisco IOS Release 12.2(33)SCB, a corresponding modular-cable interface is created. These interfaces appear under router RIP, router OSPF, and router isis routing protocol processes as "no passive-interface", even when passive-interface default is configured. Cable, modular-cable, and wideband interfaces should not appear under a routing protocol process as there is no Layer 3 control.
Conditions: The creation of new cable bundle interfaces is configured rightly using the passive-interface default command. Because there is no Layer 3 control on cable, modular-cable, or wideband cable interfaces, such a problem with the Layer 2 interfaces appearing as "no passive-interface" does not lead to improper routing protocol control, but this can create some confusion even though the issue is cosmetic.
•
Symptoms: A crash is observed on the CMTS.
Conditions: This issue is seen in cases ETDB show commands are paused and multicast sessions removed because a CPE leave or a CM goes offline.
Workaround: Set the term length to 0 for no pausing while displaying the command.
•
Symptoms: The following configuration on the uBR10000 Series Universal Broadband Routers (PRE-2) can cause a system reload on both the primary and standby.
ip access-list extended CABLEINdeny udp A.0.0.0 0.255.255.255 B.C.D.0 0.0.0.255 eq tftp logdeny tcp A.0.0.0 0.255.255.255 B.C.D.0 0.0.0.255 eq 69 logpermit ip any anyWorkaround: There is no workaround.
•
Symptoms: The CMTS allows any upstream to be attached to any connector without any warning message. A "no" is displayed for the conflicting connector.
Conditions: This issue is seen when a new card is plugged into a slot with no pre-configuration.
Workaround: Reload the line card or use default connectors.
•
Symptoms: The range for Security Association Identifier (SAID) is not correct. The correct range should be 8192 to 12272.
Conditions: This issue is seen in routers running Cisco IOS Release 12.2(33)SCA.
•
Symptoms: Dynamic Packetcable Multimedia (PCMM) service flow disappears after Cisco uBR-MC5X20U line card switchover or reset.
Conditions: This issue is observed when switchover occurs after PCMM gate built about [T3-20, T3] seconds or after sequential switchover/revertback.
Workaround: Change PCMM policy to rescue PCMM gate from COMMIT_RECOVERY back to COMMIT status.
•
Symptoms: The PRE4 processor module rate shaping allows the traffic throughput on a service flow to exceed its maximum rate.
Conditions: This issue is seen on PRE4 processor module best effort service flows.
Workaround: There is no workaround.
•
Symptoms: A crash is observed on the ESR-PRE2 processor module. The crash infomation logs may contain the following:
%UBR10K-6-US_SFID_INCONSISTENCY: US-SF found: SFID xxxx, type 0, sid 0(yyyy), MAC aaaa.aaaa.aaaa(bbbb.bbbb.bbbb), prim_sid xxx(yyy)CMD: 'no cable service attribute voice-enabled downstream-type HA-capable'Conditions: This issue is seen in Cisco IOS Release 12.3(23)BC4 and Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: The show inventory command on a uBR10012 router running Cisco IOS Release 12.2(33)SCB1 may show duplicates of the DTCC cards in the chassis.
Workaround: There is no workaround.
•
Symptoms: After a reload, cable metering source-interface FastEthernet0/0/0 is not present at the running configuration, although cable metering filesystem disk0: cpe-list-suppress and cable metering source-interface FastEthernet0/0/0 were configured.
Conditions: This issue is seen only in Cisco IOS release versions on the PRE2 processor module and not in Cisco IOS releases versions of the Cisco uBR7200 router.
Workaround: There is no workaround.
•
Symptoms: The active DOCSIS queues remain active in the event of a DOCSIS SPA failure.
Conditions: If there are modems online and passing traffic on the modular-cable and/or on wideband-cable interfaces and the DOCSIS SPA fails, the DOCSIS queues associated with these online modems remain active attempting to dequeue.
Workaround: There is no workaround.
•
Symptom: When attempting to upgrade a Cisco uBR10012 router from Cisco IOS Release 12.3(21)BC to Cisco IOS Release 12.2(33)SCB, the primary PRE may crash.
Conditions: This issue is seen when the CMTS is running Cisco IOS Release 12.3(21)BC and while upgrading to Cisco IOS Release 12.2(33)SCB. The CMTS must then be powered down and physically reconfigured to run as a M-CMTS (Cisco SIP-600 inserted, WB SPAs inserted, DTCCs inserted, so on.). Lastly, the CMTS must be turned on to run its new Cisco IOS Release 12.2(33)SCB IOS image and physical configuration.
•
Symptoms: The RFGW-1 reports channel(s) as down following rf-channel and fiber node configuration changes.
Conditions: This issue is seen when there are changes made to the rf-channel/fiber node configuration on the RFGW-1. It reports the affected channels as DOWN.
Workaround: Exit fiber node configuration level and the changes are be committed and the rf-channel status as reported by the RFGW-1. It shows the correct state.
•
Symptoms: Modems marked by tftp-enforce mark-only show up in show cable modem as marked with the # sign. Syslog messages might report that the modem was marked as follows:
SLOT 6/1: Mar 25 12:21:58.967 CDT: %UBR10000-4-REGISTRATION_BEFORE_TFTP_MARK: Registration request unexpected: Cable Modem did not attempt TFTP. Modem marked with #. CM Mac AddrBut the modem does not show up with the "#" in front of the online status in show cable modem command.
Conditions: This is seen in routers running Cisco IOS Release 12.2(33)SCB1.
Workaround: There is no workaround.
•
Symptoms: The show facility-alarm status command displays a false alarm.
Conditions: This issue is seen for the protect line cards when connectors are not set.
Workaround: There is no workaround.
•
Symptoms: When a bundle subinterface number is greater than 64K, the statindex assignment for multicast session shows 0.
Conditions: This is a rare situation and only happens when a subinterface number is greater than 64K.
Workaround: Use a smaller subinterface number.
•
Symptoms: The CMTS sends DBC to the CM to change the primary downstream port
Conditions: This issue is seen when the VDOC broadcast feature is configured such that multiple RCCs in the same MAC domain have exact same frequencies for the primary bonding group, but the primary frequency is different. For example, if you have frequencies f1 and f2 as the primary bonding group frequencies, then rcc1 (f1f2f3) and rcc2 (f1f2f4) have the first two frequencies as f1f2, while rcc3 (f2f1f3) and rcc4 (f2f1f4) have the first two frequencies as f2f1. With this configuration, the CM is first online using rcc3 and the CPE sends an IGMP join for the channel corresponding to f3.
Workaround: For the VDOC broadcast feature, configure RCC templates such that a set of primary bonding group frequencies are in the same order in all RCC templates.
•
Symptoms: Executing the cmts walk command on ARP table causes high CPU utilization. This is also seen while using the snmp walk command on the ARP table.
Conditions: This issue occurs while using the cmts walk and snmp walk commands.
Workaround: To prevent high CPU utilization when using the snmp walk command, use snmp view commands:
snmp-server view cutdown iso included
snmp-server view cutdown at excluded
snmp-server community public view cutdown ro
snmp-server community private view cutdown rw
•
Symptoms: Although the CM is in non-BPI mode, after line card high availability, its downstream packet or the ping are still encrypted and fail.
Conditions: This issue is seen in the following conditions:
–
–
–
Workaround: After the change to non-BPI configuration, use the delete command instead of reset.
•
Symptom: The CM goes offline after line card fails with different types of working and protect line card (for example, Cisco uBR10-MC5X20H protect and Cisco uBR10-MC5X20U line cards)
Conditions: This issue occurs when a manual line card switchover is done and when a new active line card crashes or reboots before HCCP Static Sync is done.
Workaround: There is no workaround.
•
Symptoms: The show interface bundle command output displays incorrect upstream input bit/sec traffic counter.
Workaround: There is no workaround.
•
Symptoms: After a line card switchover the key-index becomes 0 for a multicast QoS that is configured for a active static IGMP session along with encryption.
Conditions: This issue is seen only for static IGMP groups which has multicast QoS with encryption configured.
Workaround: There is no workaround.
•
Symptoms: An unused Downstream Service Identifier (DSID) and statsindex is shown in the show cable multicast dsid command. The Service Flow Identifier (SFID) value displays "0" in the show interface multicast-session command.
Conditions: This happens when admission control checks fails at the cable line card (CLC) during multicast service flow creation.
Workaround: There is no known workaround.
•
Symptoms: Cable modems report non-primary DS channel impairments during registration time via the partial-service in the REG-ACK message.
Workaround: There is no workaround.
•
Symptoms: A uBR10012 router may see the following syslog generated repeatedly:
%UBR10000-6-MAP_UPSTREAM_BW_ALLOCATION: A transmit opportunity was missed because MAP arrived too lateWorkaround: There is no known workaround.
•
Symptoms: Service flow statistics wrongly resets to 0 after executing the dcc technique 1 command.
Workaround: There is no known workaround.
•
Symptoms: The Gigabit Ethernet interface on an ESR-1GE may fail to send packets.
Conditions: This might be seen just after executing online insertion and removal (OIR) of an ESR-1GE with low rate.
Workaround: Execute the hw-module slot reset command.
•
Symptoms: The multicast packets are forwarded to a cable downstream interface that is in rf-shutdown state.
Conditions: This issue occurs if the cable interface is in rf-shutdown state and multicast traffic is forwarded to that interface unnecessarily.
Workaround: There is no workaround.
•
Symptoms: Multicast traffic forwarding stops on modular cable interfaces.
Conditions: This issue occurs on modular downstream interfaces with multicast QoS functionality configured and the Parallel Express Forwarding (PXF) on the CMTS has restarted.
Workaround: In case of a static multicast, unconfigure and reconfigure the ip igmp static-group commands. In case of dynamic multicast, use the clear ip mroute command.
Workaround: There is no workaround.
•
Symptoms: When using the RCC template with multiple channels marked as primary, the cable modem will see sporadic downstream traffic loss depending on the modem's selection of the primary downstream.
Conditions: The cable modem must be locked on to the primary downstream that is not RC-1 in the RCC template.
Workaround: Assign only a single RC/DS as primary per RCC-template.
•
Symptoms: Index allocation might fail due to an IPC drop between the host and the working line card, or because the guardian is down.
Workaround: Reset the line card, guardian, and the SPA.
•
Symptom: Logged messages are sent not only to the IOS system log in memory on the Cisco MC5X20 line cards, but to the console serial port. This I/O activity uses CPU resources unnecessarily especially at card bootup time. Console logging may be re-enabled by configuring the logging console command.
Conditions: This issue is seen in all Cisco uBR10-MC5X20 line cards.
•
Symptoms: The Cisco uBR10012 router crashed because it ran out of unfragmented memory.
Conditions: This is seen in Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: Multicast session is in I-state on the active PRE.
Workaround: There is no workaround.
•
Symptoms: In Cisco IOS Release 2.2(33)SCB3, executing the show controller modular-cable x/y/z command with a copper SFP, SFP-GE-T, causes the wideband SIP to crash.
Conditions: The issue will occur if we have Copper SFP in a Wideband SPA gigabi
Guest
