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)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
November 24, 2009
OL-15874-10
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)SCC. 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)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: Use Cisco uBR7246-VXR routers.
•
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 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: Use a Cisco uBR7246VXR router.
•
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 (see, PBR Support for Multiple Tracking Options) whether the next-hop is active or not.
•
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: All CMs on adjacent downstreams are offline. The adjacent downstream ports are 0 and 1, or 2 and 3, or 4.
Conditions: The downstream ports that share JIB may be nonfunctional if the JIB that services both downstream ports is locked.
Workaround: Reload the cable line card.
•
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 gigabit ethernet port.
Workaround: Use a fiber SFP and a fiber link instead of a copper link.
•
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 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.
Workaround: There is no workaround.
•
Symptoms: Potential wideband SPA Index leak is found during the line card switchover.
Conditions: This issue is found when the modem is deleted before the IPC is returned from the guardian.
Workaround: There is no workaround.
•
Symptoms: The docsIfUpChannelTxBackoffStart/end value is inconsistent with the output from the command value.
Workaround: There is no workaround.
•
Symptoms: During the VDOC video channel changes, it is possible that the multicast QoS service flow cannot be created because a stale 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 is seen in multicast QoS service flows.
•
Symptoms: The "Gate Report State" counter in the output of the show packetcable cms verbose command does not increment for PacketCable Multimedia (PCMM) policy servers.
Conditions: This issue is seen for PCMM policy servers.
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.
Workaround: There is no workaround.
•
Symptoms: HQF logging does not work on Cisco PRE4.
Workaround: There is no workaround.
•
Symptom: CMTS will accept inconsistent "per-SF L2VPN TLV" in the cable modem configuration file.
Conditions: This is seen in the following conditions:
–
–
–
Workaround: There is no workaround.
•
Symptoms: CMTS may crash when an MPLS sub interface is deleted.
Workaround: Do not delete the sub interface.
•
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: CM uptime mismatch is reported between the CMTS and few CMs.
Workaround: There is no workaround.
•
Symptoms: CPU increases to 100% on the Cisco MC5x20U and MC5x20S line cards after upgrading to the Cisco IOS Release 12.2.(33)SCB2.
Workaround: Downgrade the image version to Cisco IOS Release 12.3(23)BC7 or use MC5x20H cards.
•
Symptoms: Legitimate CM which was online and BPI enabled will get disconnected along with the following error messages printed with "CLONED_CM_DETECTED" corresponding to legitimate modem's MAC address.
Workaround: Once the legitimate CM goes offline and comes back again online with BPI enabled, the next cloned CM attempt will fail.
•
Symptoms: In a SAMIS operation, counters are stuck in the downstream direction for cable modems.
Workaround: Reset the cable modems.
•
Symptoms: Traceback is seen at cable_hwidb2macdomain.
Workaround: Do not pre-configure the card command with ubr10k-clc-5x20h option. The card command to use for the Cisco UBR-MC520H cards is card x/x 5cable-mc520h-d.
•
Symptoms: Tracebacks are seen on the Cisco uBR10012 router after two multicast clients initiate multiple joins and leaves.
Workaround: There is no workaround.
•
Symptoms: Entries in docsBpi2CmtsMulticastObjects duplicate after the line card revertback.
Workaround: There is no workaround.
•
Symptoms: The modems on a specific line card cannot come online after upgrading to Cisco IOS Release 12.3(23)BC4.
Conditions: The following message is seen in the logs report the message:
%PXF_DMA-3-IRONBUS_NOTRUNNING: Data path to slot 5/0 failed to synchronize.Workaround: There is no workaround.
•
Symptoms: Spurious memory access occurs or CMTS crashes.
Conditions: This issue is observed when DSG configuration is removed and protect line card is active.
Workaround: Do not update configuration when protect line card is active.
•
Symptoms: Multicast functionality stops when the modems are reset on a different interface.
Workaround: Change to different multicast stream and then change back to original stream to restore the stream.
•
Symptoms: Wrong DS frequencies are offered to wideband CMs.
Workaround: There is no workaround.
•
Symptoms: CPU utilization shoots to 100% for multiple times during FPGA upgrade.
Workaround: There is no workaround.
•
Symptoms: Non-bonding capable modems are wrongly registered in bonded channels.
Workaround: There is no workaround.
•
Symptoms: Improper SPA temperature minor warning reminder message is observed.
Conditions: This issue is observed when the WBCMTS SPA temperature crosses over minor warning threshold 58C, and remains in the range of 58C ~ 68C for more than 10 minutes.
Workaround: There is no workaround.
•
Symptoms: CIR queue or service flow is not created for the multicast session.
Workaround: Run the shut/no shut interface command and the session will be recreated.
•
Symptoms: During the IPDR process, it is unable to delete config for cable metering.
Workaround: There is no workaround.
•
Symptoms: CMTS may crash due to stack corruption.
Workaround: There is no workaround.
•
Symptoms: CMTS may crash after a key-string is entered.
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: Set cable upstream docsis mode by CLI instead of SNMP.
•
Symptoms: The arp entries are lost after a redundancy switchover or a crash
Workaround: There is no workaround.
•
Symptoms: The Cisco SIP-600 crashed after executing the hw-module bay 1/0 shutdown and the hw-module bay 1/1 shutdown commands at the same time.
Workaround: There is no workaround.
•
Symptoms: Tracebacks appears while unconfiguring cable service attribute non-ds-bonded downstream-type bonding-disabled and cable fiber node.
Workaround: There is no workaround.
•
Symptoms: The show interface multicast-session command may show wrong multicast session instances.
Workaround: There is no workaround.
•
Symptoms: CMTS does not add IP address to the relayed DHCP packets.
Workaround: There is no workaround.
•
Symptoms: The following CPUHOG message is seen when CPE is rapidly performing hundreds of multicast joins and leaves and a hw-module reset is done on the line card.
005812: Jul 2 11:53:06.925: %SYS-3-CPUHOG: Task is running for (2000)msecs, more than (2000)msecs (66/36),process = Net Background.-Traceback= 4188E9F8 4187AFAC 4187E2C0 4187EB70 4187F5CC 4187F860 418848D4 41884988 41884A3C 402ACBC8 40264654 40264ABC 403E87FC 403E8AF0 403E8B44 402654D8Workaround: There is no workaround.
•
Symptoms: After sending multicast traffic and then a PRE switchover, the following unexpected messages are displayed on the Standby PRE console.
Sid : 22, Interface: Cable6/1/0000715: Jul 2 22:56:44.605: CMInstp is NULL![cmts_mcast_add_session_interface]Sid : 93, Interface: Cable5/0/0000716: Jul 2 22:56:44.609: CMInstp is NULL![cmts_mcast_add_session_interface]Workaround: There is no workaround.
•
Symptoms: Non default service flows and DSID entries were created when default multicast service flow failed.
Conditions: This happens only when MQoS enabled scenario where admission control failed to create multicast default SF.
Workaround: Make valid admission control parameters for the default service class template.
•
Symptoms: A cable modem is wrongly assigned with a DS-SG-ID which does not exist on RP after the line card switchover.
Workaround: There is no workaround.
•
Symptoms: The PRE crashes when an Etherchannel subinterface with dot1q encapsultation is deleted.
Workaround: There is no workaround.
•
Symptoms: DSG traffic is no longer forwarded to modular interface after changing bundle.
Workaround: Remove and add the bundle again
•
Symptoms: Intermittent traceback message at OIR of PRE-4 flash disk.
Workaround: There is no workaround.
•
Symptoms: When changing the service class on the fly for DSG tunnel, CMTS removes the old service flow but fails to repopulate new service flows.
Workaround: Remove the DSG tunnel from the interface and re-config it.
•
Symptoms: On a uBR10012 router with Cisco SIP-600 and wideband SPA, SIP-600 went down and came back up due to the Software Watchdog Reset.
Workaround: There is no workaround.
•
Symptoms: After a crash or a OIR of a cable line card, the RCC template is not applied to cable interface.
Conditions: LCHA must be enabled. The initially active card crashes and comes up and becomes active.
Workaround: When in this state unconfigure and re-configure the associated fiber-node.
•
Symptoms: Active PRE4 reloaded after the hw-module bay 1/1/0 reload command was run.
Workaround: There is no workaround.
•
Symptoms: Traceback messages have been observed while executing the show interface command.
Workaround: There is no workaround.
•
Symptoms: Traceback messages have been observed after pulling the active PRE-B (PRE4) while it was active.
Workaround: There is no workaround.
•
Symptoms: The MC5x1GE WAN SPA crashed after OIR.
Workaround: There is no workaround.
•
Symptoms: CMTS watchdog timeout crash is observed at cmts_address_filter or cmts_cm_lookup.
Workaround: Downgrade the image version to Cisco IOS Release 12.2(33)SCB2.
•
Symptoms: Memory fragmentation might occur with memory allocation of 65535 bundle MAC entry elements.
Conditions: This issue is likely to occur with multicast traffic.
Workaround: There is no workaround.
•
Symptoms: Some cable modems may go offline during a line card switchover process.
Conditions: This issue is observed when a Cisco MC5x20H line card that serves as a protect card and Cisco MC5x20U line card is the working card, switches over from MC5x20H line card to MC5x20U line card.
Workaround: Reduce the number of modems connected to the Cisco MC5x20U line card.
Resolved Caveats — Cisco IOS Release 12.2(33)SCB4
•
Symptoms: The no ip dhcp relay info policy removal pad config command has no effect.
Workaround:
1.
2.
3.
•
Symptoms: Memory leak at CMTS_HCCP_GET_TLV_PARSE_TLV has been observed at the RP.
Workaround: There is no workaround.
•
Symptoms: It was not possible to ping the wideband cable modem after the test cable dcc tech 1 command is executed.
Conditions: This issue is observed when the cable modem is in the w-online MAC state.
Workaround: Use tech 0 for DCC operation for wideband cable modems.
•
Symptoms: A cable line card crash may occur if a test cable dcc command is executed on a 2.0 modem, move it from an ATDMA upstream to a TDMA upstream (with fragmentation disabled).
Conditions: The issue is seen in routers running Cisco IOS Release 12.3(23)BC4.
Workaround: There is no workaround.
•
Symptom: Invalid/ corrupt values seen for OctetsPassed and PacketsPassed fields in SAMIS records.
Conditions: CMTS with wideband SPA configured, query the service flow counters using SAMIS, snmp or show CLI, sometimes it will show wrong value for the octets or/and packets for the wideband modems or narrowband modems but using the remote SPA channel as primary downstream.
Workaround: There is no workaround.
•
Symptoms: The startup configuration information for a standby PRE is not displayed.
Workaround: There is no workaround.
•
Symptoms: CMTS crashes after performing multiple IGMP join and leave messages.
Conditions: This issue is observed when multiple IGMP join and leave messages are transmitted and with a standby PRE available.
Workaround: There is no workaround.
•
Symptoms: After a PRE processor module switchover, the following message is displayed:
"*Jan 29 10:22:33.187: %IPC-5-INVALID: Message Port index Dest Port 0x1001C Session 0x1 Source 0x60000"Conditions: This issue has been observed on In Service Software Upgrade (ISSU) while upgrading PRE A slot to PRE B slot processor modules.
Workaround: There is no workaround.
•
Symptoms: The Cisco Broadband Troubleshooter trace window appears to show incorrect data when triggering an upstream by CM MAC address. The MIB object "server% getmany -v2c ccsSpectrumDataPower" returns values that when graphed do not show the expected QAM haystack. This MIB does not provide data until the CMTS is first configured appropriately via SNMP sets.
Conditions: This issue occurs in upstream frequency stacking and configured MAC domains.
Workaround: Remove the frequency stacking and configured MAC domains.
•
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.
•
Symptom: The title field "Name" in the show cable admission-control interface is missing.
Conditions: This is seen in the output of the show cable admission-control interface command.
Workaround: There is no workaround.
•
Symptoms: The wideband cable interface is not able to pass traffic.
Conditions: The issue occurs because the bonded channel-to-RF channel mapping configuration is missing from the SPA.
Workaround: There is no known workaround.
•
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: Upstream-and-downstream-related tables are not retrieved while querying via SNMP.
Conditions: This issue is seen while querying via SNMP.
Workaround: There is no workaround.
•
Cisco IOS Software configured with Authentication Proxy for HTTP(S), Web Authentication or the consent feature, contains a vulnerability that may allow an unauthenticated session to bypass the authentication proxy server or bypass the consent webpage.
There are no workarounds that mitigate this vulnerability.
This advisory is posted at the following link:
http://www.cisco.com/warp/public/707/cisco-sa-20090923-auth-proxy.shtml
•
Symptom: The Cisco uBR10012 router experienced several crashes when upgrading from Cisco IOS Release12.3(21a)BC6 to Cisco IOS Release 12.3(23)BC6.
Conditions: These crashes have been found when upgrading from Cisco IOS Release 12.3(21a)BC6 to Cisco IOS Release 12.3(23)BC6.
Workaround: There is no workaround.
•
Symptoms: The PRE crashes when the no cable modem remote-query command is run.
Conditions: This issue may occur only when the minimum polling interval is "cable modem remote-query 1 public".
Workaround: The polling interval should not be a minimum value.
•
Symptoms: Different values for the MAC Domain Downstream Service Group (MD-DS-SG) are seen after an RPR switchover, using the show cable modem wideband and show cable mac-domain downstream-service-group commands.
Conditions: This issue occurs while changing the MD-DS-SG by changing the fiber node when CMTS is up and after a RPR switchover.
Workaround: There is no workaround. This symptom is not critical. It does not affect normal use of relative features.
•
Symptoms: The show controller modular-cable command output displays invalid voltage measurement readings for the 24 rf-channel SPA.
Conditions: This is seen on the 24 rf-channel SPA.
Workaround: Re-execute the show controller modular-cable command.
•
Symptoms: 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 secondary PRE processor module may crash directly after the primary PRE processor module crashes.
Conditions: This issue occurs in routers running Cisco IOS Release 12.3(21)BC.
•
Symptoms: Due to the way the CMTS US scheduler is designed, the VoIP traffic from a single CMTS shows the tendency to get synchronized in time.
Conditions: This issue is seen when multiple CMTSs are connected to the same DTI server, and the egress VoIP traffic from these CMTSs to get synchronized. This multi-CMTS VOIP synchronization causes the peak VoIP rate on the aggregation routers to the levels which default buffers cannot be handled.
Workaround: If the UGS scheduling across US channels is randomized on a single CMTS, it may to resolve the issue.
•
Symptoms: Facility alarms are incorrectly generated for cable line card interfaces.
Conditions: This issue occurs when line card redundancy is configured or upstream frequency stacking is configured.
Workaround: There is no 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: If a modular-cable channel with online modems is removed from its host and reconfigured to another host, the flows counter are incorrectly displayed.
Conditions: This is seen when a modular-cable channel is removed from its host and reconfigured to another host.
Workaround: There is no workaround.
•
Symptoms: During the PRE switchover, Subscriber Account Management Interface Specification (SAMIS) feature may not successfully export data.
Workaround: There is no workaround.
•
Symptoms: The fiber node accepts non-existent upstream connectors, which may confuse the user on physical and logical topology.
Conditions: This issue occurs when configuring non-existent upstream connectors on the fiber node.
Workaround: Do not configure non-existent upstream connectors for the fiber node.
•
Symptoms: A cable modem with multiple service flows failed to respond to pings from the RP after the line card switchover.
Workaround: There is no workaround.
•
Symptom: The DOCSIS Timing, Communication and Control (DTCC) card information is displayed in the output of the show diagnostic command when the card is not present.
Conditions: This issue is seen when both SPA cards are present in the slot/subslot and utility cards are present in slot/subslot. For example, a SPA is present in 1/1 and a DTCC card is present in 1/1.
Workaround: There is no workaround.
•
Symptom: The number of wideband modems collected via snmp walk and show cable modem wideband command does not match.
Conditions: This is an intermittent problem and is not seen on all routers.
Workaround: Run the show cable modem wideband command to know the exact number of wideband modems.
•
Symptom: The running configuration shows "-2147483" for ip rsvp dsbm non-resv-send-limit [ burst | peak | rate ] 2147483 command, which may indicate that the CMs are not working properly.
Conditions: This issue is seen while configuring the upper limit value for ip rsvp dsbm non-resv-send-limit command.
Workaround: Do not configure the upper limit value for ip rsvp dsbm non-resv-send-limit command.
•
Symptoms: The guardian line card does not synchronize with the new key to the standby line card, when a key is renewed for a wideband multicast sid,. This causes the wrong key to be sent to a wideband CM for that multicast sid after the guardian lie card switches over.
The information is not synchronized to the standby line card when the guardian line card assigns an index to a modular-cable multicast sid and key. It may reassign, the same key after a switchover.
If the index of a remote guardian line card is not rightly made free for a modular-cable multicast sid and key, This could cause an index leak for the remote guardian line card and the information is not synced to the standby for both local and remote line cards.An index leak may happen if the guardian line card switches over.
When an modular-cable interface is shut or removed from a Channel Grouping Domain (CGD), indexes are not cleaned up on standby guardian line card causing an index leak if the guardian switches over.
Condition: This is seen after a guardian line card switchover.
Workaround: There is no workaround.
•
Symptom: The test cable dcc frequency command moves one modem to target frequency does not work when the upstream channel ID of the modem does not belong to the target downstream channel.
Conditions: This issue only affect test cable dcc frequency command.
Workaround: Use test cable dcc frequency command to move the modem where the upstream channel ID belongs to the target downstream channel.
•
Symptom: The cdxIfUpChannelAvgUtil reports incorrect numbers when rate adapt is enabled on router
Conditions: This is seen when using SNMP to poll cdxIfUpChannelAvgUtil with rate adapt enabled.
Workaround:
1) Use CLI to obtain numbers
2) Disable rate-adapt
•
Symptom: The Multimedia Terminal Adapter (MTA) lacks IP connectivity and cannot be reached.
Conditions: This is seen when upgrading to Cisco IOS Release 12.2(33)SCB2.
Workaround: Reset the MTA.
•
Symptoms: The Cisco CMTS cable line card crashes under some rare conditions when a cable modem is doing initial ranging.
Conditions: This issue may occur when an online modem goes offline and does an initial ranging before the CMTS can detect that the modem has gone offline.
Workaround: There is no workaround.
•
Symptoms: The cable dynamic-secret lock command does not lock the rogue modem to 10kbps upstream or 10kbps upstream /downstream profile. The show cable modem <mac of rogue modem> qos command reports 0/0 kbps upstream/ downstream rates for the same modem after the same modem reboots or resets.
Conditions: The issue has been observed on Cisco uBR10012 router with PRE2 processor module running Cisco 12.3(23)BC4 with cable dynamic-secret lock command configured under the cable interface.
Workaround: There is no workaround.
•
Symptom: The "PXF DMA Cumulative Ironbus Error Statistics" values are incriminated when executing the show pxf dma counters | include Ironbus command. For example, the error statistics displayed are:
PXF DMA Cumulative Ironbus Error Statistics:Ironbus Event 1/0: 0Ironbus Event 1/1: 166Ironbus Event 2/0: 2843674Ironbus Event 2/1: 2843674Ironbus Event 3/0: 70Ironbus Event 3/1: 67Ironbus Event 4/0: 63Ironbus Event 4/1: 64Ironbus Event 5/0: 241Ironbus Event 5/1: 2843674Ironbus Event 6/0: 278Ironbus Event 6/1: 268Ironbus Event 7/0: 250Ironbus Event 7/1: 269Ironbus Event 8/0: 2843674Ironbus Event 8/1: 1580072Conditions: The above errors are observed on a Cisco uBR10012 router with a PRE2 processor module running Cisco IOS Release 12.2(33)SCB1 and Cisco IOS Release 12.2(33)SCB2.
Workaround: There is no workaround.
•
Symptoms: The Arris Embedded Multimedia Terminal Adapter (EMTA) modems do not get a dial tone after a PXF crash.
Conditions: This issue is seen on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB2. This is seen after a PXF crash and when the Arris modems are in the "In Progress Telephony-DHCP" state.
Workaround: Switch over to the standby PRE module and execute the clear cable modem command.
•
Symptoms: The following SPA bus error and Jacket watchdog reset is displayed on a Cisco Wideband SIP crashinfo:
SPI FPGA: TIB SPA1 Bus Error [1/16]Machine Check Error, can be ECC or Watchdog..ECC 1 bit errors since last time we cleared = 0ECC 1 bit errors while up (total) = 0Conditions: This issue is seen when Cisco Wideband SPA power is shutdown and if power supply violation is watched by power management hardware to protect components on SPA.
Workaround: There is no workaround.
•
Symptom: The active time is inaccurate both downstream and upstream service flows with Cisco uBR10012 router The show interface cable x/y/c sid command indicates a correct age value.
Conditions: This issue was observed on both Cisco uBR7246VXR and Cisco uBR10012 routers running Cisco IOS Release 12.3(23)BC7 when DOCSIS QoS calls were created on a non DOCSIS QoS packetCable environment.
Workaround: Use the show interfaces cable x/yz sid command to see the correct value.
•
Symptoms: The PacketCable Multimedia (PCMM) calls fail as the Gate Set Ack/Err is not received.
Conditions: This issue is seen in PCMM calls with a small value used for timer T1 (such as 1 second).
Workaround: Use larger values for the PCMM timer T1 (at least 5 seconds).
•
Symptoms: A a long latency for VDOC video channel change is seen as the Dynamic Bonding Change (DBC) timer restricts the CMTS to have another transaction on the same CM.
Conditions: This is seen due to the DBC timer value.
Workaround: Lower the T10 timer to 10 ms.
•
Symptom: The Policy Based Routing (PBR) functionality (set ip next-hop and set ip default next-hop) does not work with the PRE4 processor module.
Conditions: This is seen in the PRE4 processor module.
Workaround: There is no workaround.
•
Symptoms: When one Cisco SIP-600 card is removed, the downstream data on the second SIP-600 card may be permanently disrupted on some service flows.
Workaround: Choose one of the following options as a workaround to this issue.
–
–
•
Symptoms: When downstream load balancing (modem count method) is configured on a MAC Domain, where DOCSIS 3.0 and DOCSIS 2.0 are mixed, the total number of CMs to be load-balanced across the downstream interfaces are incorrect.
Conditions: The wideband modem may be corrupted. The downstream interface may go into the initial state with active CMs.
Workaround: Reload the CMTS.
•
Symptoms: The "No map buffer" error is seen during a PXF crash and modem drop offline.
Workaround: There is no workaround.
•
Symptoms: The wideband cable modem goes offline after the working line card is changed during the line card switchover.
Workaround: Do not change the working line card configuration after restarting the modem.
•
Symptoms: The show inventory command output does not display the SPA's correct serial number after swapping any two SPAs.
Workaround: There is no workaround.
•
Symptoms: Admission control checking in the dynamic load balancing state may not work in some circumstances.
Workaround: There is no workaround.
•
Symptoms: Traceback is observed after running the show diag command.
Conditions: This issue was observed on the Cisco uBR10012 routers running Cisco IOS Release 12.2(33)SCB3 with WBCMTS SPA.
Workaround: There is no workaround.
•
Symptoms: After squeezing (removing the deleted files from the bootflash) the bootflash on a cable line card, the following system log is generated that may encourage reformatting of line card bootflash.
cisco#squeeze clc5_0-bootflash:All deleted files will be removed. Continue? [confirm]Squeeze operation may take a while. Continue? [confirm]Squeeze of clc5_0-bootflash completecisco#SLOT 5/0: Jun 1 14:05:24.541 CDT: %FILESYS-5-MISMATCH: bootflash device programming algorithm mismatch detected, reformat is recommendedConditions: This issue is observed on the Cisco uBR10-MC5X20S, Cisco uBR10-MC5X20H, and Cisco uBR10-MC5X20U cards running Cisco IOS Release 12.2(33)SCB2.
Workaround: Format the bootflash as recommended.
•
Symptoms: A PRE with a faulty ethernet controller for the IPC data path may indirectly cause cable line cards to crash.
Conditions: The router must be configured to use remote SPA channels using the downstream Modular-Cable command.
Workaround: There is no workaround.
•
Symptoms: More than one classifier cannot be added to the DOCSIS Set-Top Gateway (DSG) tunnel and it remains in disabled state.
Conditions: The router had the DSG source specific tunnel-group configuration.
Workaround: There is no workaround.
•
Symptoms: The interfaces using frequency stacking may get dropped up to 10 dB in the average MER readings of show controllers cable command.
Conditions: This is seen in routers running Cisco IOS Release 12.3(23)BC7.
Workaround: Remove the frequency stacking or remove the frequency on the unused upstream.
•
Symptoms: PXF crashes with the following error message in the PXF Crashinfo report.
PXF DMA Error - Invalid Source Descriptor Based on CommandConditions: This is seen in routers running Cisco IOS Release 12.2(33)SCB2.
Workaround: There is no workaround.
•
Symptoms: Packetcable gates are stuck in the ALLOC state after HW-Module reset.
Workaround: There is no workaround.
•
Symptoms: DOCSIS Set-Top Gateway (DSG) statistics does not show the modular cable interfaces Downstream Channel Descriptor (DCD) counters.
Conditions: This occurs in normal conditions.
Workaround: There is no workaround.
•
Symptom: When a modem is load balanced with Dynamic Channel Change (DCC), receives a "cdxCmtsCmOnOffNotification" OFF trap from the cmts, but no corresponding ON trap.
Conditions: This is seen on a Cisco uBR10012 router running Cisco IOS Release12.3(23)BC2 with snmp-server traps enable cable cm-onoff command configured in the global configuration and cable enable-trap [cm onoff-notification] command on each interface along with load balancing
Workaround: There is no workaround.
•
Symptoms: FPGA upgrade may fail and corrupt the SPAs that are plugged into the Cisco SIP-600.
Conditions: This issue is observed during OIR of one SPA while the FPGA of another SPA is being upgraded or hardware/ low-level software failures on the jacket card.
Workaround: Perform the following tasks.
1.
2.
•
Symptoms: A Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB2 may have a counter issue as observed with show interface command.
Workaround: There is no workaround.
•
Symptoms: CMTS may crash when the IPDR Exporter/Collector session restarts too fast.
Conditions: This issue is observed when the IPDR session is configured and the IPDR exporter is running.
Workaround: The collector does not restart the session at a faster rate, so delay the time interval to connect of 1 minute before restart.
•
Symptoms: The default facility-alarm command does not set the facility alarm values to the default values but wrongly executes the no facility-alarm command.
Workaround: There is no workaround.
•
Symptoms: Modems do not go online during CM steering even if load balancing is configured on them.
Workaround: There is no workaround.
•
Symptoms: Some signal-to-noise ratio (SNR) difference is observed when frequency stacking is configured.
Conditions: This issue is only on the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U cards and when PRE-EQ (equalization-coefficient) is configured.
Workaround: Run the no-shut the first upstream command.
•
Symptoms: After a PRE switchover, local CMTSs can ping the affected modems but the remote hosts cannot ping modems.
Workaround: Reset the modems.
•
Symptoms: PRE and line cards crash while accessing invalid memory area.
Conditions: This issue is observed when default multicast service flow is being deleted.
Workaround: There is no workaround.
•
Symptoms: Dropped or delayed DOCSIS MAC management packets resulted in problems such as call failures.
Conditions: Combination of Multicast QoS configuration with BPI+ encryption coupled with the blocking of IGMP for those same multicast groups.
Workaround: Do not configure multicast QoS with BPI+ for groups where IGMP is blocked.
•
Symptoms: Multicast QoS service flow is not created for the DSG tunnel, after the CMTS reloads with the service class and DSG configuration.
Workaround: There is no workaround.
•
Symptoms: CPUHOG error messages appear when many multicast QOS sessions get deleted after IGMP leave within a short time.
Workaround: There is no workaround.
•
Symptoms: Cable line card crashes during CM registration in Remote Copy Protocol (RCP) verbose reporting mode.
Conditions: This issue is observed when the cable rcp-control verbose command is enabled and if the CM is sending the CLABS defined RCP 00 10 00 00 05 in the verbose format.
Workaround: Do not enable the cable rcp-control verbose command under the cable interface.
•
Symptoms: The show controller cable upstream command output for the MAC Parser queue information shows the same numerical value for the queue depth and wait time. The wait time is not shown correctly, the wait time is shown as a duplicate of the queue depth.
Workaround: There is no workaround.
•
Symptoms: The wideband SPA cannot upgrade firmware for a corrupted field-programmable gate array (FPGA) with field-programmable devices (FPD).
Workaround: If the SPA with the corrupt FPGA is plugged into the UBR10-2XDS-SIP, then the FPGA gets upgraded properly.
•
Symptoms: Narrowband cable modems cannot get online on remote downstreams after both the Protect and the Working line cards are reset in a CMTS with more than 2 SPAs in the system.
Workaround: Revert to the previous configuration or reload the CMTS.
•
Symptoms: The wideband SPA in Cisco SIP-600 is stuck after executing the hw-module bay x/y shutdown and no shutdown command.
Workaround: Reload the wideband SPA.
•
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:
–
–
–
–
•
Symptoms: Router is experiencing spurious memory access during the ipv6_spd_pak_classify.
Conditions: This issue is observed after configuring IPv6 on the Fast Ethernet interface.
Workaround: There is no workaround.
•
Symptoms: DSG:Downstream Channel Descriptor (DCD) counters increment even while modular interfaces are down.
Workaround: There is no workaround.
•
Symptoms: Memory leak is observed in cmts_fill_peak_offpeak_parameters.
Conditions: This issue is observed when the peak-offpeak enforce rule is changed to legacy settings and the rule is enabled.
Workaround: Do not change peak-offpeak rule to legacy and define a new enforce rule.
•
Symptoms: Traceback and spurious memory access is observed due to failover of either PREs.
Workaround: There is no workaround.
•
Symptoms: The SPA flaps after reloading the CMTS.
Conditions: This issue is observed on the Cisco router running Cisco IOS Release 12.2(33)SCB3 with 5 SFPs in slots 1 and 3 after reloading the CMTS.
Workaround: There is no workaround.
•
Symptoms: The ip dhcp relay info policy removal pad command is not ISSU compliant.
Workaround: ISSU cannot be conducted and the CMTS must be reloaded.
•
Symptoms: Though cable modems are online, the CMTS is not able to ping them after unrelated wideband or modular cable interface is shut down.
Workaround: Shut down the affected interface and then re-enable that interface.
•
Symptoms: CMTS crashes when removing the flash card.
Workaround: There is no workaround.
•
Symptoms: Traceback is observed after the Multicast client initiating igmp join with group-encryption is enabled.
Workaround: There is no workaround.
•
Symptoms: The interrupts are not disabled when a SPA is stopped.
Workaround: There is no workaround.
•
Symptoms: Multicast traffic was not sent when a RF channel is added to the existing multicast tunnel.
Workaround: Re-apply the DSG configuration or execute the shut and no shut command for the RF channel.
•
Symptoms: Ping failure observed after weekend traffic and the cable modem reset.
Workaround: There is no workaround.
•
Symptoms: Wideband modems go offline after line card switchover was triggered by cable power off.
Workaround: There is no workaround.
•
Symptoms: The IGMP input process causes high CPU utilization on the PRE.
Conditions: This issue is observed during high rate of IGMP joins received and multiple cable interfaces present on CMTS.
Workaround: Enable "multicast echo" on bundle interface.
•
Symptoms: After service flows are created for the multicast traffic, the show interface wideband 1/1/0:2 service-flow x counters command unexpectedly displays the service flow counters as zero.
Workaround: There is no workaround.
•
Symptoms: A few DSIDs are wrongly assigned to more than one wideband cable modem and ping failure occurs to one of them.
Workaround: Execute clear cable modem reset command to issue a new DSID.
Open Caveats—Cisco IOS Release 12.2(33)SCB3
•
Symptoms: Wideband modem downstream throughput rate is not yet supported.
Conditions: The packet per second and bits per second throughput rate for each wideband CM downstream service flow is not available. This affects both the show cable modem Cx/y/z service-flow [counters | verbose] and show cable modem a.b.c.d qos commands.
Workaround: There is no workaround.
•
Symptoms: String commands fail to run in the Cisco IOS Tcl shell.
Conditions: This issue occurs while running string commands in Cisco IOS Tcl shell.
Workaround: There is no workaround.
•
Symptoms: The throughput rate shows (slightly) more than the expected range.
Conditions: This issue happens when the Dynamic Message Integrity Check (DMIC) feature is enabled and the modem is marked with given maximum rate values. This can also happen when the QoS profile has got lower maximum rates.
Workaround: There is no workaround.
•
Symptom: The DOCSIS Set-Top Gateway (DSG) client does not work on the modular cable interface.
Conditions: This issue occurs on a fully functional and configured MAC domain on the Cisco uBR10-MC5X20 cable line card. When a modular cable SPA is inserted and configured, and the modular-cable downstream is applied to the MAC domain on the Cisco uBR10-MC5X20 line card, Downstream Channel Descriptor (DCD) messages are not sent.
Workaround: To enable the modular cable interface to function properly, it is necessary to execute the shut and the no shut commands on the MAC domain of the Cisco uBR10-MC5X20 line card that is associated with the modular cable interface.
•
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: The cable line card crashes after the execution of the clear arp and clear cable modem delete commands.
Conditions: The condition is unknown.
Workaround: There is no workaround.
•
Symptoms: Certain PCMM calls using wideband CMs may have one way audio.
Conditions: This issue occurs when PCMM calls between w-online (pt) and online (pt) on wideband CMs have one-way audio.
Workaround: There is no workaround.
•
Symptoms: When Multicast Virtual Private Network (MVPN) is configured on the CMTS, and a CPE joins a multicast group that a source is already transmitting to, then the (S,G) entry is not created in the MVRF table of the CMTS.
Conditions: This issue occurs when MVPN is configured on the CMTS.
Workaround: There is no workaround.
•
Symptoms: The online cable modems go offline with no alert or log message.
Conditions: This issue is only related to Cisco uBR10-MC5X20U cards on the Cisco uBR10012 platform. This issue is similarly seen in Cisco uBR10-MC5X20H cards.
Workaround: Executing the shut or the no-shut commands on the affected interfaces or power-cycling the cable line card solves the problem.
•
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, it is 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: The CPE device disappears from the cable host table and sometimes from the ARP table, thus causing the CPE to lose IP connectivity. This shows up across different CM vendors, different CLC types, different plants, and on different Cisco uBR10012 routers.
Conditions: The issue is seen in the following:
–
–
–
–
Workaround: Execute clear cable host command for the CPE device until the device shows up on the CPE table again.
•
Symptoms: The upstream ports configured as HCCP protect show the port link down when executing the show facility-alarm status command.
Condition: 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: Memory leak at CMTS_HCCP_GET_TLV_PARSE_TLV has been observed at the RP.
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 percent 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 not admit 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: After a PRE processor module switchover, the following message is displayed:
"*Jan 29 10:22:33.187: %IPC-5-INVALID: Message Port index Dest Port 0x1001C Session 0x1 Source 0x60000"Conditions: This issue has been observed on In Service Software Upgrade (ISSU) while upgrading PRE A slot to PRE B slot processor modules.
Workaround: There is no workaround.
•
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 Cisco Broadband Troubleshooter trace window appears to show incorrect data when triggering an upstream by CM MAC address. The MIB object "server% getmany -v2c ccsSpectrumDataPower" returns values that when graphed do not show the expected QAM haystack. This MIB does not provide data until the CMTS is first configured appropriately via SNMP sets.
Conditions: This issue occurs in upstream frequency stacking and configured MAC domains.
Workaround: Remove the frequency stacking and configured MAC domains.
•
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.
•
Symptom: The title field "Name" in the show cable admission-control interface is missing.
Conditions: This is seen in the output of the show cable admission-control interface command.
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 wideband cable interface is not able to pass traffic.
Conditions: The issue occurs because the bonded channel-to-RF channel mapping configuration is missing from the SPA.
Workaround: There is no known workaround.
•
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: Upstream-and-downstream-related tables are not retrieved while querying via SNMP.
Conditions: This issue is seen while querying via SNMP.
Workaround: There is no workaround.
•
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: All CMs on adjacent downstreams are offline. The adjacent downstream ports are 0 and 1, or 2 and 3, or 4.
Conditions: The downstream ports that share JIB may be nonfunctional if the JIB that services both downstream ports is locked.
Workaround: Reload the cable line card.
•
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 the Cisco 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 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: Different values for the MAC Domain Downstream Service Group (MD-DS-SG) are seen after an RPR switchover, using the show cable modem wideband and show cable mac-domain downstream-service-group commands.
Conditions: This issue occurs while changing the MD-DS-SG by changing the fiber node when CMTS is up and after a RPR switchover.
Workaround: There is no workaround. This symptom is not critical. It does not affect normal use of relative features.
•
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 information 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 controller modular-cable command output displays invalid voltage measurement readings for the 24 rf-channel SPA.
Conditions: This is seen on the 24 rf-channel SPA.
Workaround: Re-execute the show controller modular-cable command.
•
Symptoms: The cable monitor duplicates one more MAC Domain Descriptor (MDD) for every generated MDD if it is configured to monitor cm_multicast_addr(01e0.2f00.0001).
Conditions: This issue is seen when cm_multicaset_addr(01e0.2f00.0001) is configured.
Workaround: Configure the paktype mac command to capture MAP/MDD/UCD.
•
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: Delays occur in calls after a failover from a Cisco uBR10-MC5X20S card to a Cisco uBR10-MC5x20H card.
Conditions: This issue is seen in a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB1 and configured for N+1 Redundancy and after a failover of a Cisco uBR10-MC5X20S card to Cisco uBR10-MC5X20H card. A call take approximately 20 seconds to successfully hang up. Before that period, if the handset is placed on the hook and then picked up, dial tone would not be heard.
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: 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 secondary PRE processor module may crash directly after the primary PRE processor module crashes.
Conditions: This issue occurs in routers running Cisco IOS Release 12.3(21)BC.
•
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: Facility alarms are incorrectly generated for cable line card interfaces.
Conditions: This issue occurs when line card redundancy is configured or upstream frequency stacking is configured.
Workaround: There is no workaround.
•
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: DMIC code is being corrupted due to a DHCP packet.
Conditions: This issue seen on PRE2 processor module running Cisco IOS Release 12.3(23)BC2.
Workaround: There is no workaround.
•
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 multicast traffic is not forwarded by the CMTS to the multicast clients after the IGMP join request is sent by the client. The "packets received" counter keeps increasing, but the "packets forwarded" counter stops increasing
Conditions: The issue is seen with Cisco uBR10-MC5X20H line cards with multicast configuration enabled.
Workaround: Configure the ip igmp version 3 command in the bundle interface associated with the multicast traffic forwarding line card.
•
Symptoms: When the upstream service flow of modem exceeds the 1 MB limit on a Cisco DPC3000 cable modem, no traffic can be sent.
Conditions: This happens when the upstream traffic is sent at 1 MB or above.
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: If a modular-cable channel with online modems is removed from its host and reconfigured to another host, the flows counter are incorrectly displayed.
Conditions: This is seen when a modular-cable channel is removed from its host and reconfigured to another host.
Workaround: There is no 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: The fiber node accepts non-existent upstream connectors, which may confuse the user on physical and logical topology.
Conditions: This issue occurs when configuring non-existent upstream connectors on the fiber node.
Workaround: Do not configure non-existent upstream connectors for the fiber node.
•
Symptom: The CMTS causes high CPU utilization on the IPDR/SAMIS collector by sending multiple records for a flow with the same creation time.
Conditions: The service flow export and service flow deletion occur at the same time.
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.
•
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 un-fragmented memory.
Conditions: This is seen in Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptom: The DOCSIS Timing, Communication and Control (DTCC) card information is displayed in the output of the show diagnostic command when the card is not present.
Conditions: This issue is seen when both SPA cards are present in the slot/subslot and utility cards are present in slot/subslot. For example, a SPA is present in 1/1 and a DTCC card is present in 1/1.
Workaround: There is no workaround.
•
Symptoms: Stale multicast BPI encryption keys remain on protect line cards that are in standby state.
Conditions: This issue is seen while joining and leaving a multicast group (present in cable match command). Conduct a line card switchover from working to protect and then revert back to working from protect.
Workaround: There is no workaround.
•
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: 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.
•
Symptom: The Multimedia Terminal Adapter (MTA) lacks IP connectivity and cannot be reached.
Conditions: This is seen when upgrading to Cisco IOS Release 12.2(33)SCB2.
Workaround: Reset the MTA.
•
Symptom: The "PXF DMA Cumulative Ironbus Error Statistics" values are incriminated when executing the show pxf dma counters | include Ironbus command. For example, the error statistics displayed are:
PXF DMA Cumulative Ironbus Error Statistics:Ironbus Event 1/0: 0Ironbus Event 1/1: 166Ironbus Event 2/0: 2843674Ironbus Event 2/1: 2843674Ironbus Event 3/0: 70Ironbus Event 3/1: 67Ironbus Event 4/0: 63Ironbus Event 4/1: 64Ironbus Event 5/0: 241Ironbus Event 5/1: 2843674Ironbus Event 6/0: 278Ironbus Event 6/1: 268Ironbus Event 7/0: 250Ironbus Event 7/1: 269Ironbus Event 8/0: 2843674Ironbus Event 8/1: 1580072Conditions: The above errors are observed on a Cisco uBR10012 router with a PRE2 processor module running Cisco IOS Release 12.2(33)SCB1 and Cisco IOS Release 12.2(33)SCB2.
Workaround: There is no workaround.
•
Symptoms: The Arris Embedded Multimedia Terminal Adapter (EMTA) modems do not get a dial tone after a PXF crash.
Conditions: This issue is seen on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB2. This is seen after a PXF crash and when the Arris modems are in the "In Progress Telephony-DHCP" state.
Workaround: Switch over to the standby PRE module and execute the clear cable modem command.
•
Symptoms: A line card switchover from a Cisco uBR10-MC5X20U card to a Cisco uBR10-MC5X20H card causes only Cisco DPC3000 modems to go offline.
Conditions: This issue is seen in Cisco DPC3000 cable modems.
•
Symptoms: During the VDOC video channel changes, it is possible that the multicast QoS service flow cannot be created because a stale 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 is seen in multicast QoS service flows.
•
Symptoms: The "Gate Report State" counter in the output of the show packetcable cms verbose command does not increment for PacketCable Multimedia (PCMM) policy servers.
Conditions: This issue is seen for PCMM policy servers.
Workaround: There is no workaround.
•
Symptoms: The PacketCable Multimedia (PCMM) calls fail as the Gate Set Ack/Err is not received.
Conditions: This issue is seen in PCMM calls with a small value used for timer T1 (such as 1 second).
Workaround: Use larger values for the PCMM timer T1 (at least 5 seconds).
•
Symptoms: A a long latency for VDOC video channel change is seen as the Dynamic Bonding Change (DBC) timer restricts the CMTS to have another transaction on the same CM.
Conditions: This is seen due to the DBC timer value.
Workaround: Lower the T10 timer to 10 ms.
•
Symptom: CMTS will accept inconsistent "per-SF L2VPN TLV" in the cable modem configuration file.
Conditions: This is seen in the following conditions:
–
–
–
Workaround: There is no workaround.
•
Symptom: The Policy Based Routing (PBR) functionality (set ip next-hop and set ip default next-hop) does not work with the PRE4 processor module.
Conditions: This is seen in the PRE4 processor module.
Workaround: There is no workaround.
Resolved Caveats — Cisco IOS Release 12.2(33)SCB3
•
Symptoms: While viewing a modem upstream trace with Cisco Broadband Troubleshooter Release 3.2, the burst is not be displayed when equalization is configured on the US port. This seems to be happening with the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U cards only.
Conditions: This issue is only on the Cisco uBR10-MC5X20S and Cisco uBR10-MC5X20U cards and when PRE-EQ (equalization-coefficient) is configured.
Workaround: Do not configure the PRE-EQ feature. This feature is off by default.
•
Symptoms: A PRE module failover can result in tracebacks and errors when the DOCSIS trust points are configured.
Conditions: Simply attempting a failover will result in failure.
Workaround: Remove the trustpoint keys for the DOCSIS-US-TRUSTPOINT and DOCSIS-EU-TRUSTPOINT. This keeps the trustpoints in place but does not associate any crypto keys with it.
•
Symptoms: The Cisco uBR10-MC5X20H card reloaded during forced line card failover.
Conditions: This is seen in the Cisco uBR10-MC5X20H.
Workaround: There is no workaround.
•
Symptoms: When a router (with a large-scaled configuration) is provisioned to perform a PRE module failover and a PXF crash occurs (for example, issuing a switchover pxf restart 1 0 command), this could result in missed IPC keepalives and a large crash information file being written, causing unexpected behavior including line card reloads.
Conditions: This issue is seen in a router that has a large configuration and has redundancy, mode switchover, main-cpu and switchover pxf restart 1 0 commands configured.
•
Symptoms: The ip tcp adjust-mss command results in packet loss for non-TCP traffic.
Conditions: This issue is seen when using the ip tcp adjust-mss command.
Workaround: Disable ip tcp adjust-mss on all interfaces in the device. This may cause higher CPU due to fragmentation and reassembly in certain tunnel environments where the command is intended to be used.
•
Symptoms: The Cisco uBR10012 router does not properly re-initialize the sequence number field in the downstream extended header of the first packet transmitted on a newly created re-sequencing Downstream Service Identifier (DSID). The CMTS must use a Packet Sequence Number of zero (0) in the DS EHDR of the first packet transmitted on a newly created re-sequencing DSID.
Conditions: This is seen in wideband when multiple downstream primary and secondary flows are used.
Workaround: There is no workaround.
•
Symptoms: An SNMP v3 walk with authentication does not complete against a virtual switch system (VSS).
Conditions: This issue occurs on an SNMP v3 walk with authentication on a VSS.
•
Symptoms: Modems on a modular interface suffer long-time recovery time or even fall offline after switchover or revertback.
Conditions: This only affects Cisco uBR-MC5X20S/U card as the active card. It affects modems on the modular interface and is more visible for Annex A modulation type.
Workaround: There is no workaround.
•
Symptoms: On the Cisco uBR10012 platform, during PRE module runversion of the ISSU upgrade process, the IPC connection between the RP and the cable line cards may take additional seconds to come up.
Conditions: This issue happens during PRE module runversion.
Workaround: There is no workaround.
•
Symptoms: A warning message such as the one below is erroneously printed during ISSU, even when actual CPU utilization is not high:
%HCCP_LC_ISSU_SHIM-3-RP_HIGH_CPU_UTILIZATION: High CPU utilization on PRE, line card ISSU may fail.Conditions: This happens during ISSU load version.
•
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 crash first was seen on a Cisco 3825 running Cisco IOS Release12.4(22)T with ISDN connections going on. At the moment of the crash, the customer was monitoring the router using an SNMP Get program. After some minutes, the router reloaded by itself.
Workaround: There is no workaround.
•
Symptoms: A memory leak at buffer_peak_notify is observed.
Workaround: There are no workarounds.
•
Symptom: When Three Way Calling (TWC) is used, the admitted service flow of the on-hold side still has traffic going through.
Conditions: This is seen in three-way calling when one side is on hold. This is seen in Cisco IOS Release 12.3(23)BC and Cisco IOS Release 12.2(33)SCB release.
Workaround: There is no workaround.
•
Symptoms: The SP messages can get logged on the RP console but are not sent over as SNMP traps by the RP SNMP agent.
Conditions: This was first seen in Cisco IOS Release 12.2(18)SXF.
Workaround: There is no workaround.
•
Symptoms: Cable metering collection enters the "write-error" state and does not recover.
Conditions: This issue occurs when cable metering is configured with default TCP parameters.
Workaround: Enabling "ip tcp path-mtu-discovery" may help prevent occurrences of the issue. Also, the test cable metering abort command will clear the "hung" state and allows the next iteration of cable metering to occur.
•
Symptoms: The show interface cable x/y/z sid command shows null MAC address and null IP address SID entries. The show cable modem summary total command reports many more offline modems than are actually offline.
Conditions: This is observed in Cisco IOS Release 12.2(33)SCB.
Workaround: Clear the offline modems using the clear cable modem offline delete command. This issue is cosmetic.
•
Symptoms: A cable modem may disappear after a line card switchover.
Conditions: This issue occurs when configuring the member subslob x/y working command and when this configuration already exists and the working card x/y has downstream modular a/b/c RF configured.
Workaround: Execute a shutdown command followed by a noshutdown command on the corresponding modular interface.
•
Symptoms: Erroneous routing prefixes may be added to the routing table.
Conditions: This is seen when the DHCPv6 relay feature is enabled and a router receives a normal DHCPv6 relay reply packet, and this may lead to an erroneous route being added to the routing table.
Workaround: There is no workaround.
•
Symptoms: When issuing the show cable multicast db command with a page break, there may be a crash when there are IGMP activities undergoing.
Workaround: Use the term len 0 to print all data at one time to prevent this race condition.
•
Symptom: The following warning is seen when wideband (WB) resiliency is enabled, and the modem is moved from WB to NB.
%GENERAL-2-CRITEVENT: Request CIR exceeds available link rate.%UBR10K-3-QALLOCFAIL: Failure to allocate QoS queue for service flow 34, CM 001e.6bfa.f67aConditions: This issue is seen when wideband (WB) resiliency is enabled. The primary WB channel fails to work, and the modem is removed from WB to NB to recover service. The modem is configured with non-zero CIR. The NB reserved bandwidth is not enough to add a new modem.
Workaround: Disable WB resiliency.
•
Symptoms: After clearing all modems on c5/0/0, statistics on SPA downstream service flows may not work correctly.
Conditions: This issue is seen while executing the clear cable modem command causing the SPA statistics information on the SIPs to be removed.
•
Symptoms: The IPDR can trigger high RP CPU utilization when entries in the service flow log table time-out, and the data is written to the disk.
Conditions: This issue is seen when IPDR uses the file system for the deleted service flow information if the cable sflog command is configured such that the entry-duration is too short or the number of entries is too low.
Workaround: Prevent storage of deleted service flows on the disk by using the recommended configuration of the cable sflog command. The entry duration should be at least four times the metering interval and the max-entry should be large enough to store the deleted flows that exist in a metering interval.
cable metering destination < retries> 15 non-securecable sflog max-entry 30000 entry-duration 3600With the metering interval at 15 minutes, the service flow log should be at least 1 hour or 3600 seconds. The high CPU occurs when the file system is full, and attempts to write are continued.
•
Symptoms: Multiple memory leaks are seen at Cisco 10000 router On Board Failure Logging (OBFL) process.
Conditions: This is seen in the Cisco 10000 router OBFL process.
•
Symptoms: The CMTS metering collection process on the line card or Route Processor (RP) gets terminated after the metering is completed. If destination-based CMTS-metering is enabled, and the export fails, a traceback is received around the data collection intervals. No tracebacks are reported if the export succeeds.
Conditions: This could be an issue in the production environment. If the destination collector stops responding on the port or if it is unavailable, then a traceback is received on the CMTS.
•
Symptoms: When a PRE processor module switchover occurs, the diagnostic log gets blocked for several hundred milliseconds.
Conditions: This occurs when a PRE processor module switchover occurs with multiple line cards installed.
Workaround: There is no workaround.
•
Symptoms: The Cisco uBR10012 router is returning docsIf3CmtsCmRegStatusIPv6Addr as a string. This value should be in hexadecimal.
Conditions: This issue occurs if the modem does not have an IPv6 address. The default IPv6 addresses are displayed as a string.
Workaround: There is no workaround.
•
Symptoms: An incorrect MAC address or IP address is obtained when the show cable mode [mac | ip] access-group command is executed.
Conditions: This is seen in Cisco IOS Releases 12.3(23)BC and Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: The protect line card is showed as revertive in the show hccp detail command when no member subslot x/y revertive is configured.
Conditions: This issue is seen when line card redundancy is configured and after removing the working line card configuration and reconfiguring it.
Workaround: Reconfigure the no member subslot x/y revertive command.
•
Symptoms: Unintentional reset of the Cisco SIP-600 card can occur if the show controller command is executed and there is a Cisco Wideband SPA card that is currently in a state of initialization.
Conditions: This is seen if there is a SPA in a Cisco SIP-600 card that is in the process of being initialized.
Workaround: Do not execute the show controller command if there is a Cisco SIP-600 card with a SPA that is in the process of being initialized
•
Symptoms: The following traceback is seen when getting docsIfDownstreamChannelEntry:
SLOT 5/0: 00:09:18: %ALIGN-3-SPURIOUS: Spurious memory access made at 0x6061A388 reading 0x2B0SLOT 5/0: 00:09:18: %ALIGN-3-TRACE: -Traceback= 6061A388 60334794 6061D31C 606200D0 60519EBC 60519538 6050A97C 6050AB9CSLOT 5/0: 00:09:18: %ALIGN-3-TRACE: -Traceback= 6061A390 60334794 6061D31C 606200D0 60519EBC 60519538 6050A97C 6050AB9CSLOT 5/0: 00:09:18: %ALIGN-3-TRACE: -Traceback= 6061A3B4 60334794 6061D31C 606200D0 60519EBC 60519538 6050A97C 6050AB9CSLOT 5/0: 00:09:18: %ALIGN-3-TRACE: -Traceback= 6061A3C8 60334794 6061D31C 606200D0 60519EBC 60519538 6050A97C 6050AB9CConditions: This is seen when the broadband innovation upconverter is used.
Workaround: There is no workaround.
•
Symptoms: Frequency range overlapping occurs.
Conditions: This is seen when cable freq-range north-american/european is configured on the CMTS.
Workaround: Do not configure the cable freq-range north-american/european command in global mode.
•
Symptoms: After a PRE processor module failover, certain modems and their CPEs are not reachable by their IP addresses.
Conditions: This is seen in Cisco uBR10012 router with the ESR-PRE2.
Workaround: Fail over to original PRE processor module or execute the clear cable modem delete command on the affected modem.
•
Symptoms: Configuring more than four upstream channels in one downstream may cause a crash on the CMTS.
Conditions: This issue is seen while configuring more than four upstream channels in one downstream and when a UGS_AD service flow is used.
Workaround: Do not configure more than four upstream channels in one downstream.
•
Symptom: If Dynamic Message Integrity Check (DMIC) is configured in conjunction with IPv6 enabled CMs, the PRE will crash with the following message:
*** System received a Bus Error exception ***signal= 0xa, code= 0x8, context= 0x6493a1a4PC = 0x60a49ad0, Cause = 0x420, Status Reg = 0x34008002System Bootstrap, Version 12.0(20020314:211744) [REL-pulsar_sx.ios-rommon 112], DEVELOPMENT SOFTWARECopyright (c) 1994-2002 by cisco Systems, Inc.Reset Reason Register = RESET_REASON_RESET_REG (0x76)C10000 platform with 1044480 Kbytes of main memoryConditions: This issue is seen when DMIC is configured in conjunction with IPv6-enabled CMs.
•
Symptoms: The downstream load is not balanced when downstream load balancing group (DS LB) is configured with us-across-ds policy.
Conditions: This is seen when us-across-ds policy is configured on DS LB group.
Workaround: Do not configure us-across-ds policy on DS LB group.
•
Symptoms: An error "%GENERAL-2-CRITEVENT: MRI Unlink Error: Cable", is seen in the system logs for different CMs.
%GENERAL-2-CRITEVENT: MRI Unlink Error: Cable6/0/3 cpe_info->name: Cable8/1/3 current sid: 1464 cpe_info->sid: 1922current mri: 472 cpe_info->mri: 472modem->mac_addr: 001a.ad90.be36 cpe_info->mac_addr: 001a.ada7.c1a6Current IP address: 78.94.54.211 cpe_info->ipaddress: 10.80.64.206 cpe_info->next_slot: 1048576cpe_sidinstp: 0x0 cpe_sidinstp->prim_sid: 65535 cpe_sidinstp->cm_macaddr: 0000.0000.0000Conditions: This issue is seen on the Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptoms: The calculated channel utilization percents can become inaccurate. The short term utilization seen via the output of the show interface cable X/Y/Z mac-scheduler command, shows the "Avg upstream channel utilization" value much larger than the actual channel usage. The longer term utilization used by the load-balancing module may also be much larger than the actual channel usage.
Conditions: This issue is seen when "rate-adapt" is configured for a particular upstream channel under certain configured conditions. The MAC scheduler for that upstream allocates additional data grants to one or more cable modems in a given MAP message. When the data grants go unused by the cable modems, the utilization calculations made by the scheduler become skewed.
Workaround: There is no workaround.
•
Symptoms: The MAC Domain x/y/z interface loses modular-cable configuration.
Conditions: This is seen after a Cisco uBR100012 router bootup.
Workaround: There is no workaround.
•
Symptoms: A remote primary wideband cable modem sometimes forwards primary downstream service-flow traffic from a secondary wideband interface.
Conditions: This issue occurs in a remote primary wideband cable modem.
Workaround: There is no workaround.
•
Symptoms: The LED on the HCCP-protected downstream port lights up even when the protected downstream port is in standby mode.
Conditions: This is seen on a Cisco uBR10012 router with HCCP protect.
Workaround: There is no workaround.
•
Symptoms: After changing the load-interval on the RP, the interface load-interval on the line card does not change. This results in the utilization of load balancing updated using the default interval.
Conditions: This is seen while changing the load-interval on the legacy cable interface.
Workaround: There is no workaround.
•
Symptoms: An error message is displayed when the terminal monitor is enabled instead of displaying an error message when a terminal monitor is not present. The error message that needs to be displayed as follows:
000715: Feb 25 18:35:51.554: %Advanced Spectrum Management does not support three Modulation Profile configurations. Modulation Profile 221 has been removed from the Dynamic Modulation configuration.SLOT 5/0: Feb 25 18:35:51.606: %UBR10000-5-USFREQCHG: Interface Cable5/0/0 U0, changed to Freq 26.230 MHz Feb 25 18:35:51.606: %Advanced Spectrum Management does not support three Modulation Profile configurations. Modulation Profile 221 has been removed from the Dynamic Modulation configuration.Conditions: This issue occurs when the upstream is configured for three-step dynamic modulation functionality and than upstream port is added to the spectrum group.
•
Symptoms: The cable metering commands are configured via SNMP as well using CISCO-CABLE-METERING-MIB objects. Because changes made via SNMP are not synchronized between the primary and secondary RPs, the cable metering-related configurations done via SNMP are not seen in the secondary PRE and configurations are lost after PRE switchover.
Conditions: This issue is seen with a high availability CMTS and images having CISCO-CABLE-METERING-MIB support.
Workaround: There is no workaround.
•
Symptoms: A wrong description on a facility alarm shows up for some upstream ports after resetting a modular-host line card. The wrong description means that "Physical Port Administrative State Down" shows up for some upstream ports even when those upstream ports are not administratively shut down.
Similarly, a wrong description on a facility alarm shows up for some upstream ports after reloading a Cisco uBR10012 router. The wrong description means that "Physical Port Link Down" shows up for some upstream ports even when those upstream ports are up.
Conditions: This issue only occurs on line cards with upstream max-ports 6 configured.
Workaround: Execute the shut command followed by a no shut command on the upstream ports.
•
Symptoms: A wideband CM cannot go into the w-online state after resetting both the working line card (guardian line card) and the protect line card and after the working line card reboots and becomes active.
Conditions: This issue is seen while resetting the working line card which is the guardian line card and when the working line card reboots first and becomes active.
Workaround: Remove and reconfigure the guardian configuration.
•
Symptoms: The PRE processor module crashes when the subinterface bundle is removed.
Conditions: This issue is seen when the CM has a lawful intercept configured and the CM is removed before the subinterface bundle is removed.
Workaround: Remove the bundle before removing the CM. For example, remove the subinterface bundle before shutting down the cable interface, or remove the subinterface bundle before executing the clear cable modem command.
•
Symptoms: Some DOCSIS 3.0 cable modems are not able to get to the w-online state.
Conditions: This is seen in DOCSIS 3.0 cable modems that require the presence of TLV7 and/or TLV8 in the primary channel MAC Domain Descriptor (MDD) in order to consider the MDD valid.
Workaround: There is no workaround.
•
Symptoms: The show cable modem remote-query command on the CMTS reports a modem downstream power level as a positive value while the SNMP query shows a negative value for the downstream power level between (-1 and 0).
Conditions: This issue is seen when "remote query" is enabled and the show cable modem remote-query command is issued. It only shows if the modem downstream power level is between 0 and -1.0 dBmV.
Workaround: There is no workaround.
•
Symptoms: The DOCSIS Timing, Communication and Control (DTCC) card reference source changes with execution of redundancy force-failover main-cpu command.
Conditions: This issue occurs during a PRE switchover on a Cisco uBR10012 router and the DTCC clock reference changes resulting in the following messages being shown:
%UBR10KTCC-4-CHG_CLK_REF: Clock reference source set to DTI for DTCC card 2/1 by process Plugin Start*Mar 3 08:26:03.172 CST: %UBR10KTCC-1-DTISLOT: DTCC slot 2/1: card role changed to Active*Mar 3 08:26:03.172 CST: %UBR10KTCC-1-DTIPORTCLIENT: DTCC slot 2/1 port 1 DTI client status changed to Active normal*Mar 3 08:26:03.172 CST: %UBR10KTCC-1-DTIPORTSERVER: DTCC slot 2/1 port 1 DTI server status changed to freerun, external clock source: none*Mar 3 08:26:03.620 CST: %UBR10KTCC-4-CHG_CLK_REF: Clock reference source set to DTI for DTCC card 1/1 by process Plugin Start*Mar 3 08:26:04.172 CST: %UBR10KTCC-1-DTISLOT: DTCC slot 1/1: card role changed to Standby*Mar 3 08:26:05.172 CST: %UBR10KTCC-1-DTIPORTCLIENT: DTCC slot 1/1 port 1 DTI client status changed to Active normal*Mar 3 08:26:05.172 CST: %UBR10KTCC-1-DTIPORTSERVER: DTCC slot 1/1 port 1 DTI server status changed to normal, external clock source: noneWorkaround: There is no workaround.
•
Symptoms: Cable metering commands can be configured via SNMP as well using CISCO-CABLE-METERING-MIB objects. Because changes made via SNMP is not synced between the primary and secondary RPs, cable metering-related configurations done via SNMP are not seen in the secondary PRE and configurations are lost after a PRE switchover.
Conditions: This issue is seen with a high availability CMTS and images having CISCO-CABLE-METERING-MIB support.
•
Symptoms: The wideband CM cannot be in the w-online state. It can only be online.
Conditions: This issue occurs when high availability synchronization is not completed.
Workaround: Reconfigure the fiber node.
•
Symptom: A traceback is seen during line card static synchronization.
Conditions: The traceback is seen occasionally when the length of data to be sent is near to the Maximum Transmission Unit (MTU).
Workaround: There is no workaround.
•
Symptoms: The RCC receive-module first-center-frequency encoding in the registration response message is not correct when using a rcc-template with multiple receive-modules. The CM rejects this INVALID-RCC error message in the registration ACK.
Conditions: This issue is seen in a DOCSIS 3.0 compliant CM using RCC-template which is configured with multiple receive-modules and distinct first-center-frequencies.
Workaround: Modify the RCC-template to use a single receive-module, but this may restrict the CM's capabilities.
•
Symptoms: Load-balancing of default routes originated by Open Shortest Path First (OSPF) from upper layer switches is not working.
Conditions: This issue is seen in a CMTS running Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: For the Cisco uBR-10-MC5X20 NB CM with the primary channel on remote a Cisco Wideband SPA downstream interface, its toaster BPI index is reset to 0 after a line card switchover; thus the downstream traffic is not encrypted.
Conditions: The condition is unknown.
Workaround: There is no workaround.
•
Symptoms: The device classification of certain types of CPEs impacts the cable filter groups applied to the CPE.
Conditions: This is seen in Cisco routers such as the Cisco 831 and Cisco 1841 used as CPEs behind CMs and are classified as "MTA" and not as "CPE". As a result, an unexpected cable filter group, or, in cases where defaults are not configured for "MTA", no filter group is applied to the device. A serious security gap is thus possible as all traffic from behind the device bypasses the established security policies.
•
Symptoms: Logging on to the console is disabled on the cable line cards.
Conditions: This issue is seen if any debugging is done. The logging must be explicitly enabled using the "logging console". Previously, the logging was enabled by default on cable line cards.
•
Symptoms: A preamble length of 49 symbols causes an issue with a Broadband BCM3300 chip with H cards. Imposing the minimum 50 symbols preamble length as to IM and SM bursts still reports the same issue.
Conditions:
Workaround: Do a shut command followed by a no shut command on the interface or execute cable upstream shutdown or a no cable upstream shutdown.
•
Symptoms: The Downstream Service Group (DS-SG) is missed after resetting the protect line card and working line card.
Conditions: This issue is seen while configuring Channel Grouping Domain (CGD) under c5/0/1 using the downstream modular-Cable 1/0/0 rf-channel 2 command and adding a modular interface to the fiber node.
Router#cable power off 5/1Router#cable power on 5/1sleep about 5 secondsRouter#cable power off 5/0Router#cable power on 5/0Workaround: Perform a line card switchover once more.
•
Symptoms: The show cable rf-status command is supposed to display the RF channels whose logical state shows "up", but sometime when the command is issued for individual channels separately, it displays RF channels that are not logically "up".
Conditions: This is seen while executing the show cable rf-status command.
Workaround: Use the show cable rf-status command on all the interfaces instead of trying to check each individual rf-channel separately.
•
Symptoms: The SNMP service primary flow counters include the pre-registration statistics while the corresponding commands do not include it. The ARP packets from CMTS are not mapped to the MAC destination address-based MAC classifiers on the Cisco uBR10012 platform.
Conditions: This happens for both upstream and downstream ports on the Cisco uBR7200 router and for the upstream port on the Cisco uBR10012 router.
Workaround: There is no workaround.
•
Symptom: When the CMTS receives IGMPv3 SSM Leave, the multicast session may time out prematurely.
Conditions: This issue is seen when IGMPv3 Leave is received by the CMTS.
•
Symptoms: Bonding-capable CMs may take a long time to get to the w-online state, or possibly fail to get to the w-online state.
Conditions: This issue is seen when the CMTS is configured to forward for a bonding-capable CM to a bonding-capable primary downstream channel, the CMTS randomly selects the target from the set of DS channels defined in the MAC Domain Downstream Service Group (MD-DS-SG). When complex fiber nodes are configured, it is possible that one or more of those channels are primary in a different DOCSIS MAC domain. In the event the upstream channels for that MAC domain are not available at the current fiber node, then the CM fails to initialize at the target frequency. Due to the random nature of the target DS selection, multiple failures are possible.
Workaround: There is no workaround.
•
Symptoms: Multicast Downstream Service Identifier (DSID)s are not synced over.
Conditions: This issue occurs when there is no hardware or the hardware is not up in the line card slot, before a line card that hosts modular channels with multicast traffic.
Workaround: There is no workaround.
•
Symptoms: In a PRE processor module switchover, the standby is reset repeatedly by the active because of a mismatch in the command list.
Conditions: This is seen while configuring IPDR sessions, and the metering session, and then removing the IPDR session.
Workaround: Configure the IPDR corresponding session as in the below example and follow the procedure to unconfigure the cable metering session with IPDR if it is already configured.
–
Router(config)# cable metering ipdr 2 session 100–
Router# show running-config | include cable metering ipdrRouter# cable metering ipdr 2 session 0–
Router(config)# no cable metering ipdr 2 session 100•
Symptoms: The CMTS exhausts more than 50 percent of the CPU utilization with "getmany docsIf3MdUsToDsChMappingTable".
bash-3.00$ for ((i=0; i<100; i++)) do ` getmany -v2c 20.4.0.48 public docsIf3MdUsToDsChMappingTable>/dev/null`; done;nm-ubr10k-3#sh process cpu | i SNMP ENGINECPU utilization for five seconds: 0%/0%; one minute: 0%; five minutes: 2%PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process346 84140 57115 1473 67.11% 45.98% 14.07% 0 SNMP ENGINE ========> HighConditions: This is seen when an SNMP get operation is performed.
•
Symptoms: A traceback is seen when the show pxf cpu queue hqf pblt detail command is executed.
Conditions: This is seen when pblt_id is invalid and the according pblt is not used.
Workaround: Use the correct pblt_id.
•
Symptoms: The modem gets stuck in the init (io) state when both working and protect line cards are reset at almost the same time.
Conditions: This issue is seen when both the working and protect line cards are reset.
Workaround: Reset the working card using the hw-module subslot x/y command or do a switchover.
•
Symptom: The CMTS can crash.
Conditions: The issue is seen when ETDB show commands are paused and multicast sessions are removed because of a CPE leave or a CM goes offline.
Workaround: The term length can be set to 0 for no pausing during command display.
•
Symptoms: During ISSU commit version for the Cisco uBR10012 router, these errors are seen:
00:27:58: %COMP_MATRIX-3-PRST_VBL_DELETE: ISSU Compatibility Matrix was unable todelete a persistent variable from the peer system (rc = -2).[OK]00:30:19: %COMP_MATRIX-3-PRST_VBL_WRITE: ISSU Compatibility Matrix was unable towrite to persistent variables on the peer system (rc = 0).Conditions: This issue is seen during ISSU commit version for the Cisco uBR10012 router, and while upgrading from Cisco IOS Release 12.2(33)SCB2 to Cisco IOS Release 12.2(33)SCB3 or later.
Workaround: There is no workaround.
•
Symptoms: A configuration mismatch is seen between card slot and card type while configuring a card type. The configuration failed and an error message is displayed.
Conditions: This is seen on the Cisco uBR10012 router.
Workaround: Configure the correct card type for the card slot.
•
Symptoms: CM fails to get online.
Conditions: This issue is seen when a CM begins initial-ranging on an upstream port, and reports a DOCID for a different MAC domain.
The CMTS issues a downstream frequency override (DFO) to the downstream frequency of the hosting interface (for example, Cisco uBR10-MC5X20 line card) of the upstream port being used. In this event, the target downstream port is in an "rf-shutdown' state", and the DFO fails.
Workaround: There is no workaround.
•
Symptoms: The following syslog is generated at a very high rate:
%UBR10000-6-MAP_UPSTREAM_BW_ALLOCATION:This can cause high CPU utilization due to an interrupt on a Cisco uBR10012 router.
Conditions: The condition is unknown.
Workaround: Disable console logging or raise the minimum level sent to the console.
•
Symptoms: The upstream connector configuration is different when the show run command is executed on the active PRE and standby PRE processor modules.
Conditions: This issue is seen in a line card switchover.
Workaround: Perform a line card revertback and a line card switchover again.
•
Symptoms: The SA Descriptor Length field size is changed by 2 bytes.
Conditions: This update is required by EuroDOCSIS standard (ECR).
•
Symptoms: When sending Dynamic Bonding Change (DBC) to a CM, while adding or deleting a host on the MAC domain, the CMTS always sends with a GMAC authentication which is not required for Main Distribution Frame (MDF) 2 CM. The "Re-seq" flag is set to 0, which causes multicast forwarding to stop at the CM.
•
Symptoms: The cable metering options "flow-aggregate" and "cpe-list-suppress" get lost from the cable metering configuration if cable metering data-per-session x timer y is present.
Conditions: This is seen in the cable metering command.
Workaround: Reconfigure the metering options "flow-aggregate" and "cpe-list-suppress" in the command.
•
Symptoms: After the Cisco uBR10012 router is upgraded from Cisco IOS Release 12.3(13a)BC1 to Cisco IOS Release 12.3.(23)BC2, the advanced spectrum management feature does not work.
Conditions: The SNR value goes below the first threshold and enters the second modulation as required. The issue occurs if a change is made to the first modulation, using the second threshold as reference. For example:
Router# cable upstream 0 threshold snr-profiles 22 5Mar 5 17:13:48 M 16-QAM QPSK SNR 21<22 CNR 21<22 CFEC 11>=10 <<CORRECTMar 5 17:14:10 M QPSK 16-QAM SNR 24>=8 CFEC 0<=10 UnCFEC 0<=1 << WRONG, it \should be SNR >=25Workaround: Disable the second threshold value cable upstream 0 threshold snr-profiles 22 0 command.
•
Symptoms: The calculated upstream port utilization percentage on ports 1 to 3 is below the actual usage.
Conditions: This is seen when more than one upstream port is active for a given MAC domain. The upstream utilization for the higher port numbers can be too low.
Workaround: There is no workaround.
•
Symptoms: Enhanced Interior Gateway Routing Protocol (EIGRP) reports a bad checksum.
Conditions: This is seen when EIGRP adjacency is configured over a Generic Routing Encapsulation (GRE) tunnel.
Workaround: Disable PXF on the Cisco uBR10012 router.
•
Symptoms: When a show diagnostic command is executed, the card uptimes are reported as a factor of weeks, while others commands display the card uptimes as a factor of days such as "Card uptime 12 days, 7 hours, 26 minutes, 12 seconds" instead of "Card uptime 1 weeks, 5 days, 7 hours, 25 minutes, 45 seconds".
Conditions: This is seen on a Cisco uBR10012 router running Cisco IOS Release12.2(33)SCB2.
•
Symptoms: Manually setting the MTU to "mtu 1500" on interface modular-cable is not reflected in the show interface command.
Conditions: This issue is seen on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SBC.
Workaround: First manually set the MTU to "mtu 1464" and then manually set it to "mtu 1500".
•
Symptoms: Traceback occurs when the show pxf cpu statistics ip-session command is executed.
Conditions: This traceback is always shown whenever these commands are executed.
Workaround: There is no workaround.
•
Symptoms: A Cisco uBR10012 router running on Cisco IOS Release 12.2(33)SCB1 crashes with following error:
"PXF DMA Toaster Stall Error".
Conditions: The crash happens during normal operation and is caused by a corrupted packet.
Workaround: There is no workaround.
•
Symptoms: SNMP query docsIf3MdChCfgTable is much slower than "ifStackTable".
Conditions: This is an issue in the SNMP walk of docsIf3MdChCfgTable.
Workaround: There is no workaround.
•
Symptoms: Some wideband interface association with bundle-related errors may occur if line card switchover and revertback is done once on active the PRE-A and the same action is performed on PRE-B after a PRE switchover to PRE-B.
Conditions: This issue occurs on line card switchover.
Workaround: There is no workaround.
•
Symptoms: The DHCPv6 relay process crashes on the active RP.
Conditions: The condition is unknown.
Workaround: There is no workaround.
•
Symptoms: The critical facility alarms are incorrectly reported for wideband SPA SFPs.
Conditions: This issue is seen on a Cisco uBR10012 router running Cisco IOS Release 12.2(33)SCB.
Workaround: There is no workaround.
•
Symptoms: The standby PRE module reloads if cable metering is unconfigured while metering is in progress.
Conditions: This is seen if cable metering is unconfigured.
Workaround: Ensure metering is completed and not in progress using the show cable metering status verbose command before unconfiguring the cable metering command.
•
Symptoms: When SF-based assignment is used to assign SF forwarding to a non-primary MC interface for the wideband CM, the downstream traffic fails.
Conditions: This is seen when attribute-based forwarding on a wideband CM attempts to assign forwarding to MC interfaces that are not the CM primary downstream interface.
Workaround: If forwarding is required to be non-bonded forward on the CM primary downstream interface, use the default bonded forwarding.
•
Symptoms: All the 65535 Blaze indices are used up.
Conditions: This happens when the guardian is remote and there are multiple service flows per CM.
Workaround: Use a local guardian.
•
Symptoms: The ISR processes and higher priority tasks on the line card are busy
Guest
