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)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
December 17, 2008
OL-15874-04
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)SCB. 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 selected 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
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.
In this section, the following information is provided for each caveat:
•
•
•
Open Caveats — Cisco IOS Release 12.2(33)SCB
The open caveats are grouped based on their component types. The open caveats documented from prior releases that are unresolved might also apply to this release.
CMTS-Application
•
Symptom: MC520U card crashes due to TLB BUS error when too many "cable modem xxxx change-frequency yyyy" command are executed.
Conditions: More than one DS ports are connected to one HFC. When one LC crashes, modems can be onlined to other LC's DS port. LB is used.
Workaround: There are no workarounds.
•
Symptom: Periodic 1 second delays between ubr10k transmission of SAMIS packets; enough of these are occurring to make a significant impact on overall SAMIS transfer time.
•
Symptom: Inactive sessions are observed in the multicast explicit tracking database.
Conditions:IGMP leave received for a group followed by a CLC switchover
Workaround:None
•
Symptom: When MVPN is configured on the CMTS, and a CPE joins a multicast group that a source.
Conditions: The issue only happens when igmp join arrives at the same time no mutlicast data sendingis already transmitting to, then the (S,G) entry is not created in mvrf table of the CMTS.
Workaround: There are no workarounds.
•
Symptom: Traceback observed after a uBR10000 PRE switchover %COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Tunnel1 (ifindex 144)
Conditions: Multicast VPNs are configured
Workaround: There are no workarounds.
•
Symptom: Throughput rate shows (slightly) more than than the expected range.
Conditions: Happens when DMIC feature enabled and modem marked with given MAX rate values. This can also happen when QoS profile has got lower Max rates.
Workaround: No known workaroud exists. This behaviour is mostly due to smaller value of the MAX-rate, which is not very much applicable with customer scenario. Also the slight change on the throughput values does not have impact on other functionalities
•
Symptom:Downstrean dynamic service flow reserve CIR release from wrong channel if it change from one dowstream channel to another because attribute mask change when DSC.
Conditions: Create a dynamic service flow with reserve CIR in one downstream channel with attribute-mask configured. Change this attribute configuration, then if dynamic service flow is changed, it maybe reassigned to another downstream channel, then the reserve bandwith would be released from new assigned channel but not original channel.
Workaround: Do not change attribute-mask configuration when there are downstream dynamic service flows created in it.
•
Symptom: ToS value on MCAST packets are being incorrectly overwritten.
Conditions: This is in 12.2(33)SCB.
Workaround: There is no workaround
•
Symptom: IGMP join from a cable CPE is timed out improperly by the CMTS.
Conditions: IGMP query interval is set to a large value on the cable bundle interface.
Workaround: There is no workaround.
•
Symptom: When modem comes up during off-peak time when it is not supposed to be monitored as per enforce-rule configured, the smp is not synced to standby LC.
Conditions: If an LC- Switchover is done during off-peak time, Even if the modem enters peak-time, its not monitored as per the enforced rule configured.The smp is synced to standby LC only once the modem is monitored during peak-time.
CMTS-Database
•
Symptom: For deleted service flows the last character in the Service Class Name field is dropped in SAMIS records as well as in the SNMP MIB docsQosServiceFlowLogServiceClassName
CMTS-DOCSIS
•
Symptom: The Cisco uBR10012 doesn't properly reinitialize the sequence number field in the DS extended header of the first packet transmitted on a newly created resequencing DSID. There's no problem in case CM is prepared to receive a non-zero initial sequence number but Cisco uBR should meet the following specification. --- CM-SP-MULPIv3.0-I08-080522 --- 8.2.3 Sequenced Downstream Packets (snip) The CMTS MUST use a Packet Sequence Number of zero (0) in the DS EHDR of the first packet transmitted on a newly created Resequencing DSID.
Workaround: None
•
Symptom: Packet classifier match count is a 32-bit signed counter. It goes negative when it goes above 2 billion packets.
Workaround: There is no workaround.
•
Symptom: The Number of Downstream PHS rules for a Cable MAC Domain stays the same even though more downstreams can be added to the MAC Domain (via Modular Downstreams).
Workaround: There is no workaround.
•
Symptom: Using the test cable dcc command from the modular to the native interface moves the CM just fine. Using the test cable dcc command from the native to the modular drives the CM offline, at which point it's reported [offline] on another native DS where it can never possibly register by the cable plant design. Finally the CM reaches the right online on the right DS again. Conditions: Wideband Cable deployment. The CM must fail to move from the native to the modular DS.
Workaround: When the CM is allowed to recover it is reported under a correct interface.
CMTS-Drivers
•
Symptom: Ironbus restarts have been observed on the Cisco uBR10012 due to ironbus link status 0x1180 errors. You observe the following messages in the PRE log: ------------------------------------------------------------------------------------------------------ 811468: Jun 17 03:10:17.233 UTC: slotindex is 8. 811469: Jun 17 03:10:17.233 UTC: IB Link status: 00001180 811470: Jun 17 03:10:17.233 UTC: %C10KEVENTMGR-1-IRONBUS_FAULT: Ironbus Event 5/0, Restarting Ironbus 811471: Jun 17 03:10:17.645 UTC: %C10KEVENTMGR-1-IRONBUS_SUCCESS: Ironbus Event 5/0, Restart Successful -----------------------------------------------------------------------------------------------------
The ironbus link status 0x1180 error will trigger an line card switchover on uBR10012s configured with N 1 redundancy. The ironbus restart is fast enough to keep modems online and has negligible affect to customers on uBR10012s without N 1 redundancy.
Conditions: This ironbus link status 0x1180 error has only been observed on slot 5/0 with the following hardware configuration. - Working MC520H Linecard in slot 5/0 (the problem has not been reported on the MC520U/S cards) - Active PRE2 in slot A (the problem has not been reported on a PRE1) The CMTS BU is still investigating the root cause of the ironbus link status 0x1180 error.
Workaround: There are two workarounds for ironbus link status 0x1180 error 1. Use Active PRE2 in slot B 2. Do not use a MC520H in slot 5/0 Customers should not RMA any equipment due to the ironbus link status 0x1180 error. The CMTS BU has not confirmed that this is a hardware issues and would need to identify the faulty hardware (e.g., PRE2, MC520H, chassis) if it is a hardware issue.
CMTS-Management
•
Symptom: When setting wide band interface to secondary through snmp, it doesn't work as expected.
Conditions: This symptom is observed in a wide band cmts which configure the wide band interfaces.
Workaround: Modify the wideband configuration through the CLI.
•
Symptom: Memory leak at buffer_peak_notify has been observed.
Workaround: There is no known workaround at this time.
CMTS-Packetcable
•
Symptom: When CM is primaryed on modular interfce, multiple vioce call tone were observed when bulk call is ongoing. Dropout time is about 4500~5000ms It is difficult to be reprodced on other testbed.
Workaround: There is no workaround.
CMTS-Platform
•
Symptom: When setting the Fragment-force 2000 the upstream performance drops to zero. There is no upstream thought-put.
Conditions: Problem is found only on the 5x20s card with ios ubr10k2-k8p6u2-mz.123-23.BC1.
Workaround: Put Fragment-force to Frag-force 1987 for best performance.
•
Symptom: PRE2 crashed multiple times at sch_rp_cm_reg_info_request_handler process.
Conditions: Above problem has been observed on ubr10K with PRE2 running Cisco IOS Release 12.3(23)BC4.
Workaround:There is no workaround.
•
Symptom: CMTS crashed at c10k_remote_crash_interrupt.
Conditions: The issue happens when continuously configuring 21BC customer configs.
Workaround: There is no workaround.
•
Symptom: On a UBR10k the input rate counter of all GRE tunnels is incorrect. It's doubled compared to the real value. Only tunnels interfaces are affected.
Conditions: This occurs on a UBR10k/ESR-PRE2 running IOS versions 12.3(23)BC1 and 12.3(23)BC2 and 12.3(23)BC5.
Workaround: There is no workaround.
•
Symtoms: 1)Do not configure any fiber node. 2)Bring some narrow band modems online from SPA downstream. 3)Type "clear cable modem all reset" to reset modems. After this command, all the stat/BPI/PHS indexes in the modular-host tables are expected to be freed by design. But, this didn't happen. None of those indexes are freed. Consequence: This will cause stat/BPI/PHS indexes pool leaking, and leading to CMTS scalability issue, i.e., CMTS won't be able to support the stated amount of modems online from SPA downstream. Root cause: The current implementation for "clear cable modem all reset" is implemented for wideband modems, which checking the WB/NB association before releasing the indexes. This is not appropriate for a system which doesn't have fiber-node configuration, and is only to support NB modems.
Workaround: There is no workaround.
•
Symptom: Modems go off line.
Conditions: pre-eq is enabled with ATDMA 64QAM 6.4Mz
Workaround: Use a different modulation profile.
•
Symptom: From logs collected from the customer's network, at least three routers show the symptom of the problem. For the two SPAs installed in the Saratoga jacket card, SPA1/0/1 lost all its configurations, including its IP and MAC addresses, and all its RF channel configurations. SPA1/0/0 lost some of its configurations. IP and MAC addresses remain but some of the RF channel configurations are missing. Recovery measures were attempted, including PRE S/O, hw-module reset, unprovision/reprovision the SPAs, but none succeeded. Reloading the router seems to be the only way to recover.
Workaround: Reloading the router is the only way to recover.
•
Symptom: Backup DTCC card may experience a unexpected reload irregularly with following messages. Oct 14 23:01:25.487: %IPCOIR-3-TIMEOUT: KA Timeout: slot1/1, LRCV:00:00:07 LKA:00:00:07 LRMV:never, NKA:00:00:00, cpu 1%/1% 2% Oct 14 23:01:25.491: %IPCOIR-3-TIMEOUT: KA Timeout: slot1/1, LRCV:never LKA:never LRMV:never, NKA:00:00:00, cpu 1%/1% 2% Oct 14 23:01:25.491: %IPCOIR-2-CARD_UP_DOWN: Card in slot 1/1 is down. Notifying 2cable-dtcc driver. Oct 14 23:01:25.491: %UBR10K_ALARM-6-INFO: ASSERT CRITICAL slot 1/1/0 Active Card Removed OIR Alarm - subslot 1 Oct 14 23:01:26.555: %IPCOIR-5-CARD_DETECTED: Card type 2cable-dtcc (0x5B0) in slot 1/1 Oct 14 23:01:26.555: %IPCOIR-5-CARD_LOADING: Loading card in slot 1/1 Oct 14 23:01:27.767: %C10K-5-LC_NOTICE: Slot[1/1] Line-card Image Downloaded...Booting... Oct 14 23:01:45.580: %IPCOIR-5-CARD_DETECTED: Card type 2cable-dtcc (0x5B0) in slot 1/1 Oct 14 23:01:45.656: %UBR10KTCC-4-CHG_CLK_REF: Clock reference source set to DTI for DTCC card 1/1 Oct 14 23:01:45.936: %UBR10K_ALARM-6-INFO: CLEAR CRITICAL slot 1/1/0 Active Card Removed OIR Alarm - subslot 1 Oct 14 23:01:45.936: %IPCOIR-2-CARD_UP_DOWN: Card in slot 1/1 is up. Notifying 2cable-dtcc driver. Oct 14 23:01:47.040: %UBR10KTCC-1-DTIPORTCLIENT: DTCC slot 1/1 port 1 DTI client status changed to Active fast Oct 14 23:02:20.042: %UBR10KTCC-1-DTIPORTCLIENT: DTCC slot 1/1 port 1 DTI client status changed to Active normal
Conditions: This problem was seen on only Backup DTCC irregularly of uBR10K running 12.3(23)BC2.
Workaround: There is no workaround.
•
Symptom: CLI shows 0-23 for ports, always 0-3 for subslot/bay.
Conditions: 12.3(23)BC, 12.2(33)SCA, 12.2(33)SCB, cobra_cable
Workaround: There is no workaround.
•
Symptom: The CLC is crashing after the execution of the commands 'clear arp' and 'clear cable modem all delete'.
Workaround: No workaround.
•
Symptom:When running 12.3(21a)BC7 and BC8, there are instances where the CPE device will disappear from the cable host table and sometimes from the ARP table. In all cases, the CPE loses IP connectivity. This shows up across different CM vendors, different CLC types, different plants, different 10ks. (This has also been seen in earlier IOS versions, including 12.3(17b)BC8. These are usually the symptoms seen: a) CPE loses connectivity. b) The CPE is not showing up on the CMTS using any "show" CLI like, "show cable modem <cm> <cpe>" or "show cable <interface> modem <sid>" c) Sometimes, the ARP entry for the CPE is seen in the ARP Table. d) When the CPE sends a DHCPDISCOVER packet, the CNR responds with DHCPOFFER. But for some reason, the CPE keeps sending DHCPDISCOVER. e) The work around is to clear the host by running the CLI "clear cable host". f) Although the CPE is not found in any of the "show" CLIs, "clear cable host" when ran for the first time, does not complain, indicating that some part of the CPE information is still resident in the memory. g) After the "clear cable host" is ran a couple of times (Until the error, "No such host" is seen), the CPE successfully acquires the IP address. Workaround at this point is to try "clear cable host" until the device appears back in the host table. Does not work 100% of the time.
Workaround: Workaround only sometimes works, and that's to "clear cable host" for the CPE device until the device shows up on the CPE table again.
•
Symptom: Executing the show interface bundle or show interface bundle sum/stat commands shows wrong rate, then the rate value becomes 0 after a while.
Conditions: Data rate reaches a large value, such as 2G. It depends on the load-interval value and the rate.
Workaround: There is no workaround.
CMTS-Redundancy
•
Symptom:
Memory leak at sch_rp_update_cm_cfr_list has been observed.
Workaround: There is no workaround.
•
Symptom: msid for same group changed after PRE SO. It will not impact mcast traffic and just show different msid before and after PRE SO.
Conditions: Setup msession then delete. Setup msession again and do PRE SO, the related msid is different before and after PRE SO.
Workaround: After PRE SO, send IGMP leave to re-trigger msession deletion.
•
Symptom: The crash has occurred on the secondary PRE when try to apply DBS function to wideband interface.
Conditions: Problem is seen on a PRE-2 running 12.3(23)BC2, - To apply DBS, the customer has to shut down the wideband interface first, then they met a IOS crash when "chunk_free(docsis_srv_flow_chunk,flowp)" at the last step of cmts_destroy_ds_service_flow on secondary PRE. No PXF happens.
Workaround: None.
•
Symptom: A few cable modems may become offline during ISSU upgrade, specifically during the ISSU line card prepareversion phase. Those few modems come back online shortly afterwards.
Conditions:There are multiple cable line cards being upgraded via ISSU in sequence, with one or more cable line cards being the modular host. The cable line cards being upgraded subsequent to the modular host cable line cards may encounter this symptom.
Workaround: There is no workaround.
•
Symptom: Modems on modular interface suffer long-time recovery time or even fall offline after switchover or revertback.
Conditions:1. only affects 520S/520U card as active card. 2. only affects modems on modular interface 3. more visible for annex A modulation type.
Workaround: There is no work around.
CMTS-Voice
•
Symptom: 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.
CMTS-Wideband
•
Symptom: The show controller modular-cable 1/0/0: command shows that rf-channel 0 become unknown after hw-module reset. SPA IP address = 192.168.5.1 SPA MAC Addr = 0012.001A.67D7 QAM MOD ANNEX TKB Interval Rate adjust State 0 Unknown Unknown 0 1 Enabled ====> unknown 1 QAM 256 Annex B 2423 132 Enabled 2 QAM 256 Annex B 2423 132 Enabled 3 QAM 256 Annex B 2423 132 Enabled
Conditions: Happened afte hw-module reset and show diag 1/0/0 This will cause all wideband modems also go to NB .
Workaround: Reload the router to correct the issue.
•
Symptom: When using modem-method load balancing, the docsis 3.0 modems are counted as single modem PER downstream channel. This results in many D3.0 modems on 1 channel, which means D2.0 modems will get pushed off, leaving that channel only for bonded traffic (in the case that Dynamic Bandwidth Sharing is in use, with the SPA channel given 90% remaining ratio for both types of traffic i.e. best effort). If the D3.0 modem was counted as a single modem on the Bonded Group of channels i.e. on 3 channels, then they would not influence the movement of D2.0 modems as the D3.0 modems would appear to be equally spread across the SPA channels. Virgin Media have encountered this and it creates issues for capacity planning and scalability, so would like to request this be implemented.
Conditions: D3.0 Modem with 12.3(23)BC5. Load Balance is enabled.
Workaround: There is no workaround.
•
Symptom: 1. When query for the entPhysicalName output there is a mismatch in the SFP output for12.3BC and 12.2SC images. 2. The WB SPA showed twice when running the show inventorycommand.
Conditions: When there are WB SPA cards working on sip, use the show inventory command or query for the entPhysicalName, the Symptom happens. This Symptom does not affect other functions of the WB SPA card.
Workaround: This a cosmetic mismatch of the SFP output string. Be aware that the output string is different between 12.3(21)BC and 12.2(33)SCA
Resolved Caveats — Cisco IOS Release 12.2(33)SCB
The resolved caveats are grouped based on their component types.
CMTS-Application
•
Symptom: Executing the show interface x/y/z modem 0 command may show duplicate MAC entries.
Workaround: There is no workaround.
•
Symptom: While configuring a modular cable interface on cable SPA 3/3/0, there is a memory corruption on the mac-domain host linecard. This eventually causes the mac-domain host linecard to crash. If linecard HA is configured then after the linecard crash, an HA switchover to the Protect LC is triggered, and the Protect LC will now start to crash.
Condition: Cable SPA is in Slot 3, bay 3 and default multicast QOS is configured on the CMTS.
Workaround: 1. Do not use slot 3 and bay 3 for cable SPA or 2. Do not configure multicast QoS on the CMTS (including multicast QoS related to DSG).
•
Symptom:IGMP query messages are not fowarded to the multicast client from CMTS when modems are registered in modular interface with TLS. Due to this packets are not received in the client end.
Conditions:TLS and Multicast
Workaround:There is no issue with legacy setup.
•
Symptom:TLS data traffic either stops or is forwarded unencrypted after OIR of cable line card.
Conditions: TLS is provisioned on a CM with Modular Cable primary downstream and the Modular host is on a different line card than the MAC-domain host interface of the CM.
Workaround: Configure Modular host on the same line card as the MAC-domain host interface of the TLS provisioned CM.
CMTS-Platform
•
Symptom: UBR10-MC5X20H linecard is crashing by breakpoint exception. Error message reported in the crashinfo file is the following : cr10k_clc_pre_poll: IPC not up. Reloading Line Card.. Conditions: This occurs on uBR10k running 12.3(21a)BCx or 12.3(23)BC.
Conditions: This occurs on uBR10k running 12.3(21a)BCx or 12.3(23)BC When the standby PRE in eboot state, it's easier to see this bug. <B>Workaround:</B> If this bug is generated by standby PRE in eboot state, the workaround is : a. Using the eboot image c10k2-eboot-mz.122-16.BX b. Don't keep standby PRE in eboot state, at least should not keep it in eboot for a long time. As to 12.2S image, we didn't see this problem so far. Sometimes, the continous CLI commands in test script may also lead to this problem. It's better to add some "sleep" between CLI commands.
Workaround: None.
Open Caveats — Cisco IOS Release 12.2(33)SCA2
•
Symptom: When UCD change occurs, some data structures related to US scheduler of secondary upstream service flows do not get properly updated. One example is minislot size. Hence any traffic through these service flow might get affected.
Workaround: There is no workaround.
•
Symptoms: When setting wideband interface to secondary through SNMP, it doesn't work as expected.
Conditions: This symptom is observed in a wide band cmts which configure the wide band interfaces.
Workaround: Modify the wideband configuration through the CLI.
•
Symptoms: When query for the entPhysicalName output there is a mismatch in the SFP output for Cisco IOS Release 12.3(21)BC and 12.2(33)SCA or the Cisco Wideband SPA showed twice when using the show inventory command.
Conditions: When there are Cisco Wideband SPAs on a Cisco Wideband SIP, use the show inventory command or query for the entPhysicalName, the Symptom happens.
This Symptom does not affect other functions of a Cisco Wideband SPA.
Workaround: This a cosmetic mismatch of the SFP output string. Be aware that the outputstring is different between Cisco IOS Release 12.3(21)BC and 12.2(33)SCA.
•
Symptoms: The Number of Downstream PHS rules for a Cable MAC Domain stays the same even though more Downstreams can be added to the MAC Domain (via Modular Downstreams).
Conditions: A MAC Domain can have 4K Downstream PHS rules. This is the current limit.
Workaround: There is no workaround.
•
Symptoms: With the wideband multicast BPI and wideband host HA configuration, the linecard crashes while syncing BPI data.
Conditions: This occurs when there are a large number of BPI multicast keys in wideband host data. It causes linecard memory corruption and eventually crashes the line card.
Workaround: Disable the wideband multicast BPI configuration or disable the wideband host HA configuration.
•
Symptoms: SLOWRPC error message seen in IPC code while the Cisco uBR10000 is booting up.
Workaround: There is no workaround.
•
Symptoms: On a Cisco uBR10000 Service flow counts are not updated for downstream service flows handled by the 24 RF channel SPA. As a result dynamic service flows for voice may be torn down when the T8 (inactivity) timer expires.
Conditions: Occurs when SPA in Bay 0 is inserted but the GigE link is disconnected or down.
Workarounds: Ensure that the SPA0 GigE link is up whenever SPA 0 exists.
•
Symptoms: On a Cisco uBR10000 running Cisco IOS release 12.3(23)BC3, the following message is seen when the show cable modem is used: "Warning: Zero Blaze index for SFID 173 "
Conditions: Cosmetic issue, not affecting the real data flow
Workarounds: There are no workarounds.
•
Symptoms: The indexes maintained for the 24 RF-channel SPA do no get freed after modems using SPA downstream get reset or deleted by using the clear cable modem cx/y/z all reset|delete command.
Conditions: The 5x20 host of the modular cable interface is using non-default downstream channel ID.
Workarounds: Use the clear cable modem all reset command.
•
Symptoms: SNMP Set of docsIf3MdCfgIpProvMode returns COMMIT_FAILED_ERROR. It should be supported to set.
Conditions: SNMP Set of docsIf3MdCfgIpProvMode.
Workarounds: Use CLI to change the IP prov Mode
•
Symptoms: When a policy-map is applied inbound on a GRE tunnel, the GRE tunnel outbound traffic is policed.
•
Symptoms: AFter PRE Switchover, show cable privacy root-cert provides no ouput
Conditions: The problem is only on uBR10K, and occurs after PRE failovers. Resetting all modems does not bring back the certificates on the PRE, although the modems do come online(pt) on the linecards. Performing a LC failover after the PRE failover does cause the values to be re-populated.
Workarounds: Wait till the Modems come up an learn the certificiations, and they will be repopulated again.
•
Symptoms: Throughput rate shows (slightly) more than than the expected range.
Conditions: Happens when DMIC feature enabled and modem marked with given MAX rate values. This can also happen when QoS profile has got lower Max rates.
Workarounds: No known workaroud exists. This behaviour is mostly due to smaller value of the MAX-rate, which is not very much applicable with customer scenario. Also the slight change on the throughput values does not have impact on other functionalities.
•
Symptoms: The show cable qos profile command shows an incorrect value for the number of modems that has come online with the CM generated QOS profile, in the standby PRE.
Conditions: When the CM comes online with DOCSIS1.0 config file, it creates a profile which can be seen in "show cable qos profile". Modems are registered with qos profile.
The show cable qos profile command does not show the correct value for the number of modems that has come online with the cm-created profile in the standby PRE, but the modems are registered with the cm-created profile in the active PRE.
Workaround: There is no workaround.
•
Symptoms: The multicast fastswitching path has overwritten the ToS value of the multicast packet. ToS value is correct via process-switching path.
Workaround: There is no workaround.
•
Symptoms: When a cisco uBR series CMTS is configured to perform CPE IP to MAC address resolution through the use of DHCP LEASEQUERY messages rather than ARP the address resolution will fail when it is inspired by downstream packets to the unresolved destination.
Workaround: Temporarily allow downstream ARP resolution with the cable bundle interface commands cable arp and cable proxy-arp.
•
Symptoms: IGMP join from a cable CPE is timed out improperly by the CMTS
Conditions: IGMP query interval is set to a large value on the cable bundle interface.
Workarounds: There are no workarounds.
•
Symptoms:When 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 mvrf table of the CMTS.
Workarounds: There are no workarounds.
•
Symptoms: Traceback observed after a uBR10000 PRE switchover%COMMON_FIB-4-FIBNULLHWIDB: Missing hwidb for fibhwidb Tunnel1 (ifindex 144)
Conditions: Multicast VPNs are configured
Workarounds: There are no workarounds.
•
Symptoms: After a N+1 linecard switchover to protect and revert back to working, the standby PRE may reset with some configurations.
Conditions: The problem has been observed when removing some DSG configuration after the revert back, particularly when executing the command "no cable dsg tg". In the error case, the standby PRE resets and the configuration is re-synced with the active PRE.
Workarounds: There are no workarounds.
•
Symptoms: Modems registerd on remote modular interface may go offline and quickly back online during linecard revertback when "cable default-phy-size" or "cable upstream x ingress cancellation" are not same as default value.
Conditions: This condition occurs only when "cable default-phy-size" or "cable upstream x ingress-noise-cancellation" are not same as default value or only modems registered on remote modular interface will be affected, or only during linecard revertback.
Workaround: Use the default cable default-phy-size or default cable upstream x ingress-noise-cancellation commands on the interface.
•
Symptoms: Using the show int <wb intf> downstream command displays 0/0 for "reserved/reservable" bandwidth
Conditions: With some wideband interface reserved bandwidth execute N+1 switchover
Workarounds: No workarounds. Can have correct data from output using the show hw-module bay bay number wideband wideband interface number command.
•
Symptoms: When RSA keys for use by SSH are generated on a Cisco uBR10000 series CMTS with the configuration command crypto key generate rsa the generated RSA keys are not synchronized across to the standby PRE. This means that SSH will not work if the standby becomes active.
Workaround: Use telnet to connect to the system when the standby PRE is active.
•
Symptoms: Traffic is not encrypted even with BPI enabled.
Conditions: If BPI is enabled and there is no SPA in bay 0, traffic will be sent in the clear instead of being encrypted.
Workaround: A workaround is to always leave a SPA in bay 0. If for some reason the SPA in bay 0 must be removed and there is still a SPA in bay 1, move the SPA in bay 1 to bay 0 and continue service with the SPA in bay 0.
•
Symptom: Some voice Calls DS service flow counters increase drastically after LC SO. It will reduce to its normal values but will become abnormal value again if the time between two executions of the show interface Cx/y/z service-flow xxx counters/qos command is long enough.
•
Symptom: Inactive sessions are observed in the multicast explicit tracking database.
Conditions: IGMP leave received for a group followed by a CLC switchover
Workaround: None
•
Symptom: If the modular interface is deleted from legacy interface,trace back "lb: Mo1/0/0:2:handle_stats_report_common(): no stats data "will show up and modem from other Line card could wait to come on line on inf that interface.
Conditions: CMTS has configured modular cable interface with load balance group, and this load balance group includes interface from other Line card.
Workaround: Modular interfaces is not included in Load balance group that has interface from other line card.
•
Symptom: Occasionally when inter cable line card load balancing is enabled, a spurious memory access occurs.
•
Symptom: The show interface bundle command or show interface bundle sum/stat command shows the wrong rate, then the rate value becomes 0 after a while.
Conditions: The data rate reaches a large value, such as 2G. It depends on the load-interval value and the rate.
Workaround: None
•
Symptom:When modem comes up during off-peak time when it is not supposed to be monitored as per enforce-rule configured, the smp is not synced to standby LC.
Conditions: If an LC- Switchover is done during off-peak time, even if the modem enters peak-time it is not monitored as per the enforced rule configured.The smp is synced to standby LC only once the modem is monitored during peak-time.
Resolved Caveats — Cisco IOS Release 12.2(33)SCA2
•
Symptom: An INFO level alarm is raised when using non-default config for "max-ports"and "connector" on an upstream port even though the port is actually up and running.
[Sample Alarm]
Source Severity ACO Description [Index]
------ -------- --- -------------------
Cable5/0-US19 INFO NORMAL Physical Port Administrative State Down [1]
Conditions: Non-default value is configured for "max-ports" and "connector" on Cable upstream port.
[Sample Config]
Ca5/0/3
cable upstream max-ports 5
cable upstream 0 connector 12
cable upstream 1 connector 13
cable upstream 2 connector 14
cable upstream 3 connector 15
cable upstream 4 connector 16
Ca5/0/4
cable upstream max-ports 3
cable upstream 0 connector 17
cable upstream 1 connector 18
cable upstream 2 connector 19
Workaround: There is no workaround.
•
Symptom: Customer is trying to snmpwalk the CMTS (UBR 10000). He sees that a packet has been sent, but never gets a response back. The SNMPWALK times out eventually.
Conditions: Customer has a UBR10000 series router running 12.3(21a)BC4
Workaround: Don't use the MIB object 'sysClearARP' to clear arp table, use CLI instead.
•
Symptom:Duplicate traps are generated at the end of 'file mode SAMIS' write operations when configuring SNMP traps for Cable billing operations.
Conditions:Setup per http://www.cisco.com/en/US/docs/ios/cable/configuration/guide/cmts_use-bsd_bill.html#wp1027195
Workaround: There are no workarounds.
•
Symptoms: Unable to set the MIB objects "ccwbRFChanQamIPAddress", "ccwbRFChanQamMacAddress" and "ccwbRFChanQamUdpPort" separately.
Conditions: This occurs on a Cisco uBR10012 router running ubr10k2-k9p6u2-mz.122-122_33_SCA when the MIB objects are individually set using the SNMP set command.
Workaround: Set the MIB objects "ccwbRFChanQamIPAddress", "ccwbRFChanQamMacAddress" and "ccwbRFChanQamUdpPort" using one SNMP set command.
•
Symptom: A incorrect value may be displayed in the show interface Cablex/y/z with 256QAM is enabled. The value should be BW 37500 Kbit. A degradation of service may be experienced when the behavior is observed.
Conditions: uBR10012 with IOS's 123-17b.BC3 & 123-23.BC2.
Workaround: Reverting the modulation from 256QAM to 64QAM and back to recover.
•
Symptoms: Wideband modems associated with the first shared port adapter (SPA) do not display wideband counters as expected for the downstream service flows.
Conditions: This occurs on a Cisco uBR10012 router running Cisco IOS Release 12.2SBU05. The wideband modems associated with the first SPA in 1/0/0 bay have their downstream service flow counters incremented as expected. But the wideband modems in 1/0/1 bay do not show incrementing counters for their downstream service flows.
Workaround: There is no workaround.
•
Symptom: A Cisco uBR10012 running 12.3(23)BC1 may experience a memory leak in "Pool Manager". Use show processes memory to view memory. Alternatively, you can monitor via the ciscoMemoryPoolUsed MIB object.
Conditions: Mixture of best effort data traffic, UGS voice traffic and SNMP polling.
•
Symptom: Duplicated CALEA request to CMTS when doing FCNA with BTS version 4.5 or before. SII code working well with BTS 5.0 or later due to no duplicated PacketCable CALEA requestion at FCNA. This fix make CMTS CALEA working with early version BTS at FCNA case.
•
Symptoms:The configuration command default cable upstream rate-limit is interpreted as no cable upstream rate-limit instead of cable upstream rate-limit token-bucket shaping.
Workaround: Configure the cable upstream rate-limit token-bucket shaping command instead of the default CLI.
•
Symptom: Running-config and the show controllers command have different values for upstream center frequency. Also, 16 KHz resolution is not proper for newer linecard.
Conditions: Configure fixed upstream center frequency.
Workaround: This is a sort of cosmetic issue, no side effect.
•
Symptom: Seeing %LCINFO-4-LCHUNG error messages line card is not coming up.
Conditions: With multiple loads and unloads of fdiag image line card is not coming online.
Workaround: There are no workarounds.
•
Symptom: When the cable dhcp-giaddr policy strict command is configured at the Cisco CMTS, the CPEs behind the CMs are expected to get the DHCPOFFER message with its source IP address belonging to the secondary IP Network Address range of the downstream Cable interface in the CMTS. Currently the DHCPOFFER has the source IP-Address from the downstream's primary IP Network address range.
Conditions: The issue occurs when the cable dhcp-giaddr policy strict command is configured at the CMTS cable downstream interface.
•
Symptom: A Cisco uBR10012 may reload due to a bus error.
Conditions: This has been seen on a UBR10000 running 12.3(23)BC1.
Workaround: There is no workaround.
•
Symptom: Incorrect last test pass time from cli show diagnotstic result subslot x/y detail
Conditions: When we execute the offline-filed diagnostic tests, the last test pass time is not showing correctly.
Workaround: Use the show diagnostics events subslot x/y command to see the correct last test pass time.
•
Symptom:
The Cisco uBR10012 router has spurious memory traceback observed while testing Field Diagnostics.
Conditions: After loading the fdiag iamge to the line card starting and stoping the ood tests some times crashing the PRE.
Workaround: There is no work-around.
•
Symptom:All the CPEs/Hosts/MTAs behind the Cable Modems on existing bundle sub-interface will be disappeared or deleted from the CPE table when a new Cable Bundle sub-interface is added with ip address. Same issue will also happen when newly created bundle sub-interface is deleted.
IP connectivity will be broken from CMTS to those CPEs/Hosts/MTAs as they are deleted from CPE table.
Conditions: Above issue has been observed on uBR10k with PRE2 running IOS 12.3(21a)BC8, 12.3(23)BC2 and 12.3(23)BC4 images.
Workaround: There is no workaround.
•
Symptom: CPE devices behind CableHome devices are not able to acquire IP address via DHCP when the cable helper-address x.x.x.x host command is used under the cable bundle interface.
Conditions: Problem is seen on a CMTS ubr10k with IOS 123-23.BC4. The problem has only been observed for the CPE devices with CableHome devices like Netgear. CPE device behind Cable Modem do acquire IP address via DHCP just fine and work as expected.
Workaround: Configure the cable helper-address x.x.x.x command without host option at the end of the command line under the cable bundle interface.
•
Symptom: the behavior of the priority setting isn't working correctly. A default MQoS group is required for proper implementation of MQoS over an MPLS VPNs. The default group config must appear before any other MQoS group config in the startup config in order for the feature to work correctly after a reload. For example:
!cable multicast qos group 1 priority 255 globalsession-range 224.0.0.0 224.0.0.0group-qos 2vrf VOIP!cable multicast qos group 2 priority 2 globalsession-range 239.255.70.7 255.255.255.255group-qos 1vrf VOIP!However, testing shows that the default group with priority 255 matches all mcast traffic indicating that priority 255 is in fact a higher not a lower priority. Thus, session-range 239.255.70.7 255.255.255.255 will never get used.
Workaround: There are no workarounds.
•
Symptom: Standby PRE Reset
Conditions: Sequence:
1. delete the service class used by multicast default group-qos
2. perform PRE sw
3. all group-qos configurations under qos group are removed on standby PRE, while exist on active PRE
4. try to modify group-qos under qos group on active PRE, standby PRE will be reset for configuration mismatch.
Workaround: Delete all group-qos configuration before deleting the service class used by multicast default group-qos.
•
Symptom: Wideband SPA may not accept the SFP with S/N starting with "AG" after OIR the SFP.You will see below log message when you run into this condition.
*Jul 1 19:38:42.887: %SPAWBCMTS-4-SFP_UNINITIALIZED: Modular-Cable 1/0/0, Unknown SFP inserted in port 0 failed initialization
This message itself will display when non-Cisco SFP is inserted into the SPA, but the above
SFP is indeed made from Cisco.
Conditions: SFP has S/N starting with "AG", and OIR has been performed on the the SFP one or several times.
Workaround: Execute the hw-module bay x/y/z reload command.
•
Symptom: Interrupt counts displayed by the show command show controller Modular-Cable brief are incorrect since these counts are accumulated on per jacket card basis and not per SPA i.e. controller Modular-Cable basis.
Conditions: Normal operating conditions.
Workaround: There is no workaround.
•
Symptom: Cisco uBR10012 PRE crash.
Conditions: Executed the show ip interface brief command soon after load and bootup
Workaround: There is no workaround.
•
Symptoms: If the show cable modem command is used after a PRE switchover, cable modems are duplicated with the same MAC address.
Conditions: This issue occurs on a Cisco uBR10000 series router running Cisco IOS Release 12.3(00)BC3.
Workaround: There is no workaround.
•
Symptom:After linecard switchover or revertback, some modems go offline, and us phy register shows late map issue.
Conditions: This condition occurs when dynamic map-advance safety is configured not big enough.
Workaround: Use a large dynamic map-advance safety value or use static map-advance.
•
Symptoms: In some situation, we do LC SO and revertback, we got the CMs on some upstream offline, and never online again because the PHY is in error state. It occurs on both BC2 and BC3 image.
Conditions: There are many upstream channels in no-shut state in 520H linecard. Do switchvover and then revertback. Sometimes we can see this bug.
Workaround: When this problem happens, shut/no-shut the interface could recover this problem.
•
Symptom: Line card crashes.
Conditions: When doing pre-switchover, ISSU or running the clear cable mode command, there is a chance to hit this linecard crash issue.
Workaround: There are no workarounds.
•
Symptom: Protect card are forwarding data for two or more working cards. And some CM fall offline.
Conditions: There are some interfaces admindown in working cards.
Workaround: Revert back to the working card.
•
Symptom: Traceback was observed on both active RP and standby RP.
Conditions: Issue linecard switchover when active RP is syncing configuration to standby RP.
Workaround: Do not perform a linecard failover until standby RP reach Standby_Hot state (for SSO mode) or Standby_Cold (for other PRE HA mode, like, RPR mode) .
•
Symptom: Show cable clock command may show that number of TCC Cards in the Chassis: 255". In fact, it should only show up "2" maximum for slot 1/1 and slot 2/1.
router#show cable clockLoad for five secs: 23%/8%; one minute: 26%; five minutes: 27%Time source is NTP, *13:27:28.715 EDT Mon Apr 14 2008Number of TCC Cards in the Chassis: 255Active TCC Card is in slot: 2 subslot: 1,(DTCC Eightbells card)Backup TCC Card is in slot: 1 subslot: 1,(DTCC Eightbells card)Clock reference used by the active card is Local OscillatorConditions: Removed TCC or DTCC cards and performed a PRE switchover.
Workaround: Perform another PRE2 switchover.
•
Symptom: When perform PRE switchover, it gave the following errors: UBR10K-1#redundancy force-failover main-cpu. Proceed with switchover to standby PRE? [confirm]y
% HCCP 1 50 Switchover in progress.
HA system in transient state, switchover aborted.
Conditions: One or more CLC is locked out.
Workaround: Execute the redundancy linecard-group unlockout x/y command, do PRE switchover, and then lockout x/y again.
•
Symptom: With an unrecognized LCP linecard present in the uBR10k chassis the standby PRE will not be allowed to come up.
Workaround: Remove the unsupported line card from the chassis.
•
Symptoms: IPC timeout does not trigger linecard switchover.
Conditions: The sync-pulse failure was designed to trigger linecard switchover but based on the HCCP design, IPC timeout should trigger linecard switchover.
Workaround: There is no workaround.
•
Symptom: All modems go offline on the protect port after LC swithover and never come back online.
Conditions: The cable default-phy-burst command is configured as some value other than default(=2000).
Workaround: Shut/no shut the upstream port, and configure the cable default-phy-burst command with the default value.
•
Symptoms: Inconsistent running-configuration between active and standby after route processor switchover.
Conditions: This occurs with global N+1 configured and after a route processor switchover.
Workaround: There is no workaround.
•
Symptom:US throughput would drop by half after 12-18 minutes for WB modems
Conditions: Images using 12.3(23)BC
Running config would have cable upstream X rate-limit token-bucket shaping, where X is the upstream number
Workaround: Configure the CMTS without the shaping command. Example:
cable upstream X rate-limit token-bucket, where X is the upstream number.
•
Symptom: PRE crashes. The crash might happen in only 12.2S based images since the fix was not ported from 12.3 based images correctly.
•
Symptoms: If DSA/DSC-REQ is sent by the eMTA with DOCSIS Nominal Grant Interval set to 0 then CLC would crash.
Conditions: Misbehaving eMTA with DOCSIS Nominal Grant Interval for a UGS-AD service flow is set to 0 which according to the spec is incorrect.
Workarounds: Turn off silence suppression.
•
Symptom:The US and EU root certificates must be present on the file system. If the certificate files are missing, the user must get them over to the FS before security can be enabled.
Conditions: This requirement is a general use requirement when running security on the CMTS.
Workaround: The solution to the problem is to embed the certificates in the software. In this case there is no need to have the files present on the file system and security can be used by default.
•
Symptom: If the CM is cleard on the CMTS, the CMTS forwards its DHCP Discover via the VRF of the first bundle interface, just as expected. If the CM is rebooted instead, the CMTS forwards its DHCP Discover via another VRF. The subsequent DHCP Request is sent via the correct VRF, so that it cannot be correlated to the DHCP Offer.
Conditions: When multiple bundle interfaces with unique VRFs are associated with the same downstream:
Workaround: Either terminate VRFs on a single DHCP server ignoring VRF values or keep clearing the CMs with a script.
•
Symptom:Gate is refused due to exceeded activity although the subscriber has no gate assigned to it.
Conditions: Running packet cable.
Workaround: Increase the Activity count in the gate set message.
•
Symptom: When removing the configuraiton "cable privacy acecpt-self-signed" and attempting to place a manufacturer's self-signed certificate onto the bootflash: of the CMTS with the filename "root-cert" or "euro-root-cert" the self-signed certificate appaers to be loaded, but the devices still cannot come online(pt)... BPI+ negotiation fails.
Conditions: Attempts to provision a cable modem whose BPI+ certificate is not signed by a signing authority (eg: self-signed) while the CMTS is configured to reject self-signed certs, and attempting to load a copy of the manufacturer's cert into the bootflash of the device as a workaround.
Workaround:There is no workaround.
•
Symptom: Backup TCC card may experience a reload with following messages in PRE log
%IPCOIR-3-TIMEOUT: KA Timeout: slot2/1, LRCV:00:00:14
LKA:00:00:09 LRMV:never, NKA:00:00:00, cpu 16%/5% 18%
%IPCOIR-3-TIMEOUT: KA Timeout: slot2/1, LRCV:never LKA:never
LRMV:never, NKA:00:00:00, cpu 16%/5% 18%
%IPCOIR-2-CARD_UP_DOWN: Card in slot 2/1 is down. Notifying
2cable-tccplus driver.
Conditions: The issue has been experienced on uBR10K running 12.3(23)BC1
Workaround: There are no workarounds.
•
Symptom: Two upstream ports on the same PHY receiver of a MC520H line cards show SNR degradation about 10 dB.
Conditions: Ingress-noise cancellation on.
Workaround: There are no workarounds
•
Symptom: When invoking the 'show cable modem' or related commands the following warning will be displayed "Warning: Zero Blaze index for SFID "
Conditions: When the CM/SF is in this state the traffic to the CM won't be impacted but the stats counters for the SF will report invalid numbers.
Workaround: The CM that is impacted can be reset during maintenance windows.
•
Symptom: DHCP assignement failed to CPE
Conditions: Using 2 CPEs on on CM with the second using the UNICAST DHCP DISCOVER (broadcast bit == 0)
Workaround: Delete the modem using the clear cable modem mac addres delete command. Then use a CPE settting Broadcast bit.
•
Symptom:520U card crashes due to memory corruption running 12.3(23)BC1.
Conditions: This only occurs when the CLC is subjected to a constant 80 to 100 % CPU load over a long period of time, a storm created by repeated and non rate limited cli invocations targeting the line card. Show tech and show controller are couple of examples of the cli calls that are invoked every 2 seconds as part of the scripts to reproduce the bug .
Workaround: Show tech and show controller cli calls result in reading of a long list of internal register values from the IPC mac controller while disabling the interrupts for a long time, which is not desirable when the system is under severe stress.
As a workaround, the mac device registers are not read when the show tech or show controller cli calls are invoked under normal circumstances. If the mac controller internal register values are need to be read, a debug flag is provided to accomplish that.
The debug cr10k-clc amd command can be called explicitly to turn on reading of the register contents of the mac controller.
•
Symptom: In the walk output of the table 'cpmProcessTable', process
corresponding to process id 256 is not listed.
Conditions: Steps to reproduce:
1. Configure snmp-server on the DUT.
2. On the DUT exec 'show processes cpu sorted | inc 256'. It returns the
details of the process for id 256.
3. For example, walk on the OID: '1.3.6.1.4.1.9.9.109.1.2.1.1'. This returns
the process names for all the running process. In this output the id 256 is
missing.
4. Get on the particualr instance returns 'No Such Instance' error message.
Workaround: There are no workarounds.
•
Symptom: Certain sprintf() calls in tcp/telnet.c are incorrect.
Conditions: They have the potential to overflow the destination buffers.
Workaround: snprintf() should be used with a bounding length of the size of the destination buffer.
•
Symptom: Secondary PRE2 crashes.
Conditions:
no exception-slave core-file ubr3
no exception-slave dump 172.18.98.28
no exception core-file ubr3
no exception dump 172.18.98.28
After removing the last command of "no exception dump 172.18.98.28" and then wr
Workaround: Don't remove exception in 12.3(23)BC1.
•
Symptom: Upstream Load Balancing Breaks with DOCSIS 3.0 modems in w-online(pt) state.
Conditions: UBR10k running 12.3BC with D3.0 modems online.
Workaround: There is no known workaround for performing upstream channel change with modems in w-online(pt) state.
•
Symptom: This is a internal coding issue, and have the possibility to cause memeory overflow.
Conditions: Found by source code analysis.
Workaround: There is no workaround.
•
Symptom: Incorrect display of active calls when nRTPS/RTPS is configured. The RTPS/nRTPS is interpreted as a "call" in the output of the "show cable calls" and "show cable modem calls" commands.
Condition: The problem only occurred when nRTPS or RTPS is configured.
Workaround: Use the show packetcable gate summary command to check how many calls on going.
•
Symptom: Configure bundle sub-interface, and traceback occurs occasionally.
Conditions: If we create a bundle firstly and then delete it. After these, we use command "cable bundle " configure it to one interface, this bundle will be created again, and then if we configure a sub-interface of it, the traceback occurs. It's seen in 12.2S and 12.2SCA, but not seen in 23BC.
Workaround: There is no workaroud.
•
Symptom:Flowbits keep asserting after SPA OIRed, and traceback observed when "show pxf cpu queue xxx". The traceback can only observed in 12.3(23)BC.
Conditions:SPA OIR will trigger the flowbits problem. And queue deletion is condition for the traceback.
Workaround: There is no workaround.
•
Symptoms: When editing the service class name in an enforce-rule, tracebacks/crashes were observed on the linecard.
Workaround: When the registered service class name is to be changed, remove the enforce rule and configure it with the updated service class name.
•
Symptom:Static upstream LB may be unbalanced in some scenrios. It doesn't happen with dynamic or static downstream LB.
Conditions:Static LB was configured on an interface with more than one upstream.
Workaround: Enable dynamic LB. If interface has more than two upstream. There should be a little chance to get unbalance result.
•
Symptom: Standby PRE crash at the time more than 512 calls are on going.
Conditions: Only occured at the time 2 gates with the same offset are in the free gate list.
Workaround: Remove the Standy PRE.
•
Symptoms: CNR is not shown for freq stacked upstreams. For example, if the following configuration is used on a 1x4 mac domain:
Conditons: cable upstream 0 connector 0 shared, cable upstream 1 connector 0 shared
Only US0 will show a CNR value in the show controller cx/y/z upstream command. US1 will show only a MER value. This can break CNR based freq hopping as show cable hop thresholds does not display a CNR for the affected upstream either.
Workaround: Do not use freq stacking.
•
Conditions: If "debug cr10k_rp" is on, the traceback may be observed when an arp entry on a bundle interface is to be deleted, or at the first time being created.
Workaround: There is no workaround.
•
Symptom: AAA accounting records for commands executed from remote host using rsh are sent with empty username. The username sent in exec accounting record and command accounting record is empty.
Conditions: Occurs for the commands execute from remote host using rsh.
Workaround: One can consider stopping generation of accounting records with "null" username by using the aaa accounting suppress null-username command.
•
Symptom: When cable metering is enabled, the following scheduler thrashing error message has been seen in PRE log related to all cable linecards:
SLOT 5/0: Oct 14 23:31:32 EDT: %SCHED-3-THRASHING: Process thrashing on watched message event.
-Process= "CMTS METERING Collection Process", ipl= 4, pid= 105
-Traceback= 6013579C 60135880 60585190 60584C58 601134B4 60113498
Conditions: Above problem has been observed only when "cable metering" is configured on uBR10K with PRE2 running 12.3(23)BC2 image.
Workaround: There is no workaround.
•
Symptom: In a high availability configuration with multiple PREs the standby PRE may reload when a new linecard is inserted.
Conditions: This issue may occur when inserting a new linecard in the chassis.
Workaround: There is no workaround available.
•
Symptom: Spectrum Management sometimes fails to assign upstream frequencies to cable interfaces after an OIR operation. For example replacing an MC520U with an MC520H with OIR-compatibility enabled might trigger the problem.
–
–
–
–
–
When the problem occurs the upstream channels will display "Frequency not set" in the US sections of the show controller command. The show running interface command will show that the affected US channels are included in a spectrum management group.
interface Cable<#>cable downstream frequency <#>no cable downstream rf-shutdowncable upstream 0 spectrum-group <#>no cable upstream 0 shutdowncable upstream 1 spectrum-group <#>no cable upstream 1 shutdowncable upstream 2 spectrum-group <#>no cable upstream 2 shutdowncable upstream 3 spectrum-group <#>no cable upstream 3 shutdownCable<#> Downstream is upFrequency <#> MHz, Channel Width <#> MHz, <#>-QAM, Symbol Rate <#> Msps<..>Cable<#> Upstream 0 is downFrequency not set, Channel Width <#> MHz, <#>-QAM Symbol Rate <#> MspsThis upstream is mapped to physical port <#>Spectrum Group <#><..>Cable<#> Upstream 2 is downFrequency not set, Channel Width <#> MHz, <#>-QAM Symbol Rate <#> MspsThis upstream is mapped to physical port <#>Spectrum Group <#><..>The failure might also occur after an MC520U or MC520S is installed into a previously empty, unconfigured slot.
Conditions: The problem might occur if an upstream channel is configured for Spectrum Management and included in a Fiber Node.
Workaround: Remove the failing US channels from the fiber node then re-insert them. If that doesn't correct the problem reload the CMTS.
•
Symptoms: All modems on a given upstream may go offline when the problem occurs.
Workaround: shut and follow by no shut of the cable upstream interface by using the following commands:
–
–
Open Caveats — Cisco IOS Release 12.2(33)SCA1
The open caveats are grouped based on their component types. The open caveats documented from prior releases that are unresolved might also apply to this release.
CMTS-Application
•
Symptoms: If the show cable modem command is used after a PRE switchover, cable modems are duplicated with the same MAC address.
Conditions: This issue occurs on a Cisco uBR10000 series router running Cisco IOS Release 12.3(00)BC3.
Workaround: There is no workaround.
•
Symptoms: The show interface cable modem command output is misaligned with the column headings and a heading is missing for the dual IP flag.
Conditions: The show interface cable modem output shows a 'Y' or 'N' but the field does not have a heading for this Dual IP field.
Workaround: The output needs to be aligned with the heading fields. See the show interface cable modem command documentation in the Cisco IOS CMTS Cable Command Reference.
•
Symptoms: In rare occasions, a service flow with minimal reserved rate requirement may get admitted but no traffic can be sent over it.
Conditions: This occurs when a service flow tries to reserve more than 99% of the bandwidth. Only 99% of the bandwidth that is shown as reservable in show interface cable downstream command can actually be reserved.
Workaround: There is no workaround.
•
Symptoms: The PRE2 revision number is not displayed in the show version command output.
Workaround: There is no workaround.
CMTS-Management
•
Symptoms: Unable to set the MIB objects "ccwbRFChanQamIPAddress", "ccwbRFChanQamMacAddress" and "ccwbRFChanQamUdpPort" separately.
Conditions: This occurs on a Cisco uBR10012 router running ubr10k2-k9p6u2-mz.122-122_33_SCA when the MIB objects are individually set using the SNMP set command.
Workaround: Set the MIB objects "ccwbRFChanQamIPAddress", "ccwbRFChanQamMacAddress" and "ccwbRFChanQamUdpPort" using one SNMP set command.
CMTS-Platform
•
Symptoms: The network interface on a Cisco uBR10012 router fails to acquire a global IPv6 address when using IPv6 autoconfiguration on an interface.
Conditions: The Cisco uBR10012 does not support stateless address autoconfiguration (SLAAC) for cable modems or CPEs. However, SLAAC should be supported for the CMTS router networ
Guest
