Release Notes for Cisco RF Gateway 10, Cisco IOS-XE Release 3.2SQ

RFGW-10

Chassis with the following slots: 2 Supervisor, 10 RF line card, two TCC, and 12 RFGW-10-RFSW (RF switch card) slots. Also includes the RFGW-10 fan assembly and front panel display (FPD).

RFGW-X45-SUP7-E

Cisco RFGW Supervisor 7-E, 4xSFP+ (10/1GE) (primary)

RFGW-X45-SUP7-E=

Cisco RFGW Supervisor 7-E, 4xSFP+ (10/1GE) (spare)

RFGW-TCC1

RFGW timing, communication, and control card v1

RFGW-TCC1=

RFGW timing, communication, and control card v1 (spare)

RFGW-DS384

RFGW universal downstream EQAM card, 8 RF ports, 384 QAMs

RFGW-DS384=

RFGW universal downstream EQAM card, 8 RF ports, 384 QAMs (spare)

RFGW-DS48

RFGW Universal Downstream EQAM Card, 48 QAMs

RFGW-DS48=

RFGW Universal Downstream EQAM Card, 48 QAMs

RFGW-DS48-1G

RFGW Universal Downstream EQAM card, 48 QAMs, 1 GHz

RFGW-DS48-1G=

RFGW Universal Downstream EQAM card, 48 QAMs, 1 GHz

RFGW-DS48-1G-BUN

RFGW Universal Downstream EQAM Card 48 QAMs 1G

RFGW-10RFSW1=

RFGW RF switch v1 spare.

RFGW-10-PWR-DC

RFGW DC PEM with monitoring v1a.

RFGW-10-PWR-DC1=

RFGW DC PEM with monitoring v1 spare.

SD-X45-2GB-E

Catalyst 4500 2GB SD Memory Card for Sup7-E

SD-X45-2GB-E=

Catalyst 4500 2GB SD Memory Card for Sup7-E spare

USB-X45-4GB-E

Catalyst 4500 4GB USB device for Sup7-E

USB-X45-4GB-E=

Catalyst 4500 4GB USB device for Sup7-E (spare)

SFP-GE-T

1000BASE-T SFP (NEBS 3 ESD) (100 m on Cat5 UTP)

SFP-GE-S

1000BASE-SX short wavelength; with DOM (550 m on MMF)

SFP-GE-L

1000BASE-LX/LH long wavelength; with DOM (10 km on SMF)

SFP-10G-SR

10GBASE-SR SFP Module

SFP-10G-LR

10GBASE-LR SFP Module

• GLC-SX-MMD
• GLC-LH-SMD

1 Gbps Optical SFP Modules

Cisco IOS-XE Release

3.2.0SQ

3.2.3SQ

ROMMON Release

15.0(1r)SQ(315)

15.0(1r)SQ(315)

Cisco IOS-XE Release 3.2.0SQ

• RFGW-X45-SUP7-E (Supervisor card)¹
• SD-X45-2GB-E (SD memory card for Supervisor card)
• USB-X45-4GB-E (USB memory card for Supervisor card)
• RFGW-DS384
• CHAS-RFGW-10= (VID 03 or higher)
• RFGW-TCC1 (VID 04 or higher)
• RFGW-DS48
• RFGW-DS48-1G
• SFP-GE-T (SFP transceiver)
• SFP-GE-S (SFP transceiver)
• SFP-GE-L (SFP transceiver)
• SFP-10G-SR (SFP transceiver)
• SFP-10G-LR (SFP transceiver)
• GLC-SX-MMD
• GLC-LH-SMD

• Cisco RFGW-10 DS-384 line card RF QAM port configuration
• Software Licensing for Cisco RFGW-10 DS-384
• M-CMTS DEPI
• M-CMTS Ingress DLM
• 1:1 and 1:N Line Card Redundancy (up to 2 redundancy groups)
• 1:1 Supervisor Card Redundancy
• 1:1 Timing, Communication and Control Card Redundancy
• SNMP MIBs

Cisco IOS-XE Release 3.2.1SQ

No new hardware support

• Annex A support

Cisco IOS-XE Release 3.2.2SQ

No new hardware support

• Management port
• Limited Etherchannel functionality

Cisco IOS-XE Release 3.2.3SQ

• New version of the Cisco DS-384 line card with P4080 CPU revision 3

• Setting Platform Variables from IOS Environment

Cisco RFGW-10 DS-384 line card

Cisco IOS-XE Release 3.2.0SQ

The stock keeping unit (SKU) for the Cisco RFGW-10 DS-384 line card are:

• SWLIC-DS384-BUN (DS-384 QAM license (single QAM) bundle)
• SWLIC-DS384 (DS-384 QAM license (single QAM)
• L-DS384 (DS-384 QAM Upgrade Licenses (single QAM)

Yes

No

No

No

Yes

Yes

No

No

Yes

CSCug82444

Symptom: Tracebacks occur on Cisco RFGW-10 chassis loaded with Cisco RFGW 10 DS48 and Cisco RFGW-10 D384 line cards.

* May 8 22:25:03.667: %COMMON_FIB-3-FIBIDBEARLYCALL: STANDBY:Attempt to update fibidb prior to completion of idb initialization.

-Traceback= 1#0a67a835e76525f78861b61100ebf057 :10000000+13923F0 :10000000+1586208 :10000000+1FD5094 :10000000+16AD67C :10000000+13A4578 :10000000+5AB2DC :10000000+C7ACA0 :10000000+C7BCA0 :10000000+C7CCE8

Conditions: This occurs when Cisco RFGW-10 DS48 line card and Cisco RFGW 10 D384 line card are swapped.

Workaround: There is no workaround.

CSCum79761

Symptom: Inter-Processor Communication (IPC) failure occurs.

Condition: This occurs when some Cisco RFGW-10 DS384 line cards reboot with bb_root.core on Cisco RFGW-10 chassis with ten Cisco RFGW-10 DS384 line cards on boot-up.

Workaround: The line card recovers automatically.

CSCum95021

Symptom: Some Cisco RFGW-10 DS384 line cards reboot with bb_root.core and io_pkt_v4.core.

Condition: This occurs during boot-up and upgrades.

Workaround: The line card recovers automatically.

CSCun06883

Symptom: Following error message is displayed:

ERROR: Rf Profile mismatches group's profile for Qam

Conditions: This occurs when the Cisco RFGW 10 chassis, loaded with ten Cisco RFGW-10 DS384 linecards with 1:9 redundancy, is fully configured for DEPI.

Workaround: There is no service impact. There is no workaround.

CSCun12989

Symptom: A traceback occurs when the Supervisor card reloads.

Conditions: This occurs when two redundancy groups are configured, followed by a redundancy reload peer command to reset the linecards.

Workaround: There is no workaround.

CSCun14784

Symptom: The following message is displayed:

SYS-3-CPUHOG: Task is running for (2040)msecs, more than (2000)msecs (15/15),process = RF Slave Main Thread

Conditions: This occurs on the Cisco RFGW 10 chassis fully loaded with ten linecards, when the Supervisor card statefully switches over (SSO) multiple times.

Workaround: There is no service impact. There is no workaround.

CSCun06775

Symptom: A traceback occurs.

Conditions: This occurs when OIR and Switchover of TCC card are performed simultaneously.

Workaround: Do not perform OIR and Switchover of the TCC card simultaneously.

CSCun07965

Symptom: The Cat4k Mgmt HiPri process resets the Supervisor card.

Conditions: This occurs while internal management activities are running.

Workaround: The secondary Supervisor card becomes active and no workaround is required.

CSCun18392

Symptom: The linecard resets with the UPX error and modems go offline.

Conditions: This occurs when the interleaver depth value is changed.

Workaround: Remove the interleaver depth value using the no cable downstream interleaver-depth command. Then re-configure the interleaver-depth value.

CSCue76243

Symptom: The Supervisor 7E, the Supervisor 7LE or the Catalyst 4500X cards lose all layer 3 connectivity to or from the switch IP address. Switching continues to work, but IP traffic to or from the switch fails. This includes snmp, ntp, telnet, ssh, and other traffic.

Conditions: Supervisor 7E in RFGW-10 platform running Cisco IOS XE Software Release 3.2.2SQ; RFGW-10 3.2.2SQ is based on Catalyst 4K 3.2.0SG with Fa1 functionality ported from 3.4.0SG.

Workaround: Disable Cisco Express Forwarding (CEF) on the layer 3 interfaces to temporarily restore service. When the problem occurs, the switch must be rebooted. To prevent the problem from occurring, shutdown interface Fa1.

CSCuj15596

Symptom: The active Cisco RFGW-10 Supervisor card crashes.

Conditions: This issue occurs if a faulty Timing, Communications, & Control (TCC) card is inserted, causing read/write failures.

Workaround: Replace the faulty TCC line card.

CSCul10921

Symptom: Cisco RFGW 10 DS384 line card fails with the following heartbeat failure message:

Conditions: This occurs when Cisco RFGW 10 (running with Cisco RFGW 10 DS384 linecard) generates io-pkt crash while printing error message. Crash is triggered due to double initialization of already initialized mutex.

Workaround: None.

Additional Information: The line card recovers automatically as apart of the standard line card failover process.

CSCul59238

Symptom: Standby and active Supervisor cards crash.

Conditions: This occurs when older Small Form-factor Pluggable (SFP) transceivers are used on the Cisco RFGW 10 DS384 line card and the service unsupported-transceiver command is used.

Workaround: Disable the unsupported transceivers using no service unsupported-transceiver command OR
Remove the SFPs before removing the Cisco RFGW 10 DS384 line card and reinsert the SFPs after the Cisco RFGW 10 DS384 line card is reinserted.

CSCum47570

Symptom: The linecard remains in “init” state for a long time.

Conditions: This occurs when linecard redundancy is configured, the primary linecard is failed and is automatically reset.

Workaround: If the primary linecard remains in “init” state for more than 10 minutes, reset the linecard.

CSCuc26905

Symptom: The following error message is displayed followed by traceback on the active Supervisor card:

Conditions: This issue occurs after a Supervisor card switchover, when the system CPU load is high (over 90%).

Workaround: There is no workaround.

CSCud76381

Symptom: Upconverter and Timing Communication and Control (TCC) card soft failure error messages are observed on the Cisco RFGW-10. Line cards resets after reporting FPGA failure, and alarm LED turns red.

Conditions: This issue occurs when the active TCC in slot 13 is in normal mode and standby TCC in slot 14 is in free run mode and TCC card switchover or failover is performed.

Workaround: Perform the following:

1. Verify if the standby TCC card clock is functioning before commanding a switchover.

2. Connect both Cisco RFGW-10 TCC cards and the Cisco CMTS to DTI servers that are traceable to a common clock source.

3. Reset the card is so that the alarm LED turns green. If the card does not reset, clear the alarm using the clear facility-alarm command.

CSCue13243

Symptom: The management Fast Ethernet interface goes down.

Conditions: This issue occurs when speed and duplex values are set to different values other than the default (auto) value.

Workaround: Configure the default (auto) value for speed and duplex settings on the management interface.

CSCue15419

Symptom: The management interface accepts spanning tree configuration.

Conditions: This issue occurs on the Cisco Supervisor Engine 7-E.

Workaround: Set default Management interface spanning tree configurations.

CSCue27919

Symptom: Stale sessions count observed in the show cable depi-sessions slot count command output.

Conditions: This issue occurs in large scale set up, after configuring DEPI sessions.

Workaround: There is no workaround. This is a display issue.

CSCue52025

Symptom: The frequency profile is removed when start-frequency is unconfigured.

Conditions: This issue occurs when the start-frequency is configured with an existing frequency profile, and the start-frequency is unconfigured.

Workaround: Reconfigure the frequency profile.

CSCue55078

Symptom: The consumed license count shows zero after resetting the line card.

Conditions: This issue occurs in DEPI remote learn mode when 1:N line card redundancy is configured and the secondary line card is reset before the primary line card comes up.

Workaround: There is no workaround. There is no service impact and only the license count is displayed as zero

CSCue72634

Symptom: Configuring QAM lock using qam range command fails throwing an error.

Conditions: This issue occurs after issuing the qam range command on a QAM port without any max-carriers configured

Workaround: Configure max-carriers to all the QAM ports in the line card and configure the QAM lock using qam range command. There is no service impact.

CSCue76243

Symptom: The Supervisor 7E, Supervisor 7LE, or Catalyst 4500X cards lose all layer 3 connectivity to or from the switch IP address. Switching continues to work, but IP traffic to or from the switch fails. This includes snmp, ntp, telnet, ssh, and other traffic.

Conditions: This occurs when the Supervisor 7E, Supervisor 7LE, or Catalyst 4500X cards are configured with Cisco IOS-XE Release 3.4.0SG.

Workaround: Disable Cisco Express Forwarding (CEF) on the layer 3 interfaces to temporarily restore service. When the problem occurs, the switch must be rebooted. To prevent the problem from occurring, shutdown the interface Fa1.

CSCue77864

Symptom: Modems go offline after changing the interleave depth value.

Conditions: This issue occurs after changing the interleave depth value from 32 to 64 on Cisco CMTS.

Workaround: Before changing the interleave depth value at the RF-channel modular-controller terminal on Cisco CMTS, unconfigure and reconfigure interleave depth value.

CSCue78139

Symptom: The rf-parameters in show depi session verbose command output display incorrectly.

Conditions: This issue occurs after a Supervisor switchover. The current Supervisor shows incorrect values and then becomes standby.

Workaround: Verify the same rf-parameters using the show controllers qam downstream command. There is no service impact.

CSCue78860

Symptom: RF profile mismatch error messages are seen on the Cisco RFGW-10 router.

Conditions: This issue occurs when a mismatched frequency is applied for an active DEPI session and controller configuration is reverted back to the Cisco CMTS.

Workaround: There is no workaround. There is no service impact.

CSCue86632

Symptom: Error messages are seen while adding a new interface to an existing channel group using the channel-group y mode command.

Conditions: This issue occurs when an interface from channel group Y is added to existing channel group X and a new interface without any assigned channel group is configured with channel group Y. The error occurs when group X and Y have eight members.

Workaround: There is no workaround.

CSCue87315

Symptom: QAM port that is administratively shut becomes unshut.

Conditions: This issue occurs when:

1. Line card is standalone; that is line redundancy is not configured.

2. Standalone line card is reset, causing the port in shut state to become unshut once the line card comes up.

Workaround: Configure the port as shutdown after the card comes up.

CSCue91581

Symptom: The show controllers qam downstream command output displays incorrect values after Annex change.

Conditions: This issue when:

1. Minimum two QAM channels with Annex B come up

2. Active sessions with rf-profile configured and used by QAM channels have the modulation value modified from Annex B to Annex A

Workaround: Unconfigure and reconfigure using no cable downstream rf-profile rf-profile-id command at the QAM channel.

CSCuf05080

Symptom: Memory leak is seen after several line card switchover procedures are performed.

Conditions: This issue occurs on the Cisco RFGW-10 with line card redundancy and Etherchannel configured, and line card switchover is performed.

Workaround: There is no workaround. There is no service impact. The memory leak is marginal and is directly proportional to the number of line card switchover procedures performed.

CSCuf05890

Symptom: Configuration synchronization parser mode error messages are displayed on the Cisco RFGW-10 standby Supervisor card.

Conditions: This issue occurs while performing the Supervisor switchover.

Workaround: There is no workaround.

CSCtw57111

Symptom: The show interface qam command output displays incorrect bandwidth values when executed at the port level.

Conditions: This issue is observed on the Cisco RFGW-10 DS-48 line card.

Workaround: There is no workaround.

CSCtx99408

Symptom: The standby Supervisor goes into Route Processor Redundancy (RPR) mode if rf-profile with invalid interleaver-depth value is applied to the QAM channel.

Conditions: This issue occurs while configuring rf-profile on the line cards. When the rf-profile is applied to a QAM Channel, the system automatically applies the interleaver-depth value from the rf-profile to the QAM Channel. This invalid configuration causes a configuration synchronization failure and results in the standby Supervisor going to RPR mode.

Workaround: Set default values on QAM channel and perform a redundancy reload of the Cisco RFGW-10.

CSCtz92104

Symptom: Error message are seen on the Supervisor console when the first clock source is connected to the TCC card:

Conditions: This issue occurs when the TCC cards have no clock sources and the first clock source is connected to a TCC. The active TCC card goes into fast mode, re-acquiring the lock. The Cisco RFGW-10 DS-384 line card upconverter loses and re-acquires the lock.

Workaround: There is no workaround.

Ignore this incorrect error message. The upconverter will lose and re-acquire the lock when the TCC cards lose and re-acquire the lock. This is expected behavior

CSCua58184

Symptom: Error messages are seen on the Supervisor console when a line card is inserted into a slot:

Conditions: This issue occurs if the Supervisor card is unable to read the serial EEPROM (SEEPROM) of the line card when the card is being slowly inserted into the chassis.

Workaround: Reinsert the line card. The Supervisor card is successful in reading the EEPROM in the second attempt.

CSCua99738

Symptom: The show inventory command output displays the TCC card hardware revision value incorrectly.

Conditions: This issue occurs on normal conditions.

Workaround: Use the show idprom module module-number command to view the correct TCC card versions.

CSCub01890

Symptom: The following error message is displayed:

Conditions: This issue occurs after the TCC card switchover.

Workaround: There is no workaround. This issue has no service-affecting impact.

CSCub01894

Symptom: After the line card redundancy is removed, previous configuration of the new independent card (prior to configuring redundancy) are still preserved and an attempt to bring up the sessions fails.

Conditions: This issue occurs under normal conditions.

Workaround: Before configuring the stand alone line card as a secondary line card, default all QAM ports of the line card to be configured, as secondary.

or manually remove all the configuration for that line card slot in the newly independent card.

CSCub34355

Symptom: The following error message is displayed:

ERROR: Qam <slot>/<port> is administratively shut and will reject the configuration.

Conditions: This issue occurs when the default configuration is applied to the port that is in shutdown state.

Workaround: If the port is admin_down state, unshut the port before applying the default configuration at the port level.

CSCub46436

Symptom: Continuous “Up/down reason: QC RF Mute mismatch” messages are observed on the Cisco RFGW-10.

Conditions: This issue occurs when DEPI remote-learn QAM sessions exist on the Cisco RFGW-10 and few QAM licenses exist for the configured QAM channels.

Workaround: Upgrade the line card to have enough QAM licenses for all configured QAM channels.

CSCub46770

Symptom: Modems go from w-online to online(pt) state when the modulation is changed to 64 and then reverted back to 256.

Conditions: This issue occurs when the modulation is directly modified.

Workaround: Remove the frequency modulation using no form of the command and reapply.

Example:

CSCub73486

Symptom: The LQAM configuration is rejected with the following error:

Conditions: This issue occurs if a saved configuration is copied from a storage device to the running configuration after the RF Gateway 10 is booted up with all default configurations.

Workaround: Remove the carrier ID command from the saved configuration and then apply it onto the running configuration.

CSCub82362

Symptom: For the Cisco RFGW 10 DS-384 line card, auto-negotiation is not supported on ports 9 and 10 with 1 Gbps SFPs.

For a scenario where a primary port on the Cisco uBR-MC3GX60V line card is directly connected to ports 9 or 10 of the Cisco RFGW 10 DS-384 line card and primary port link is restored, the backup port still remains active because the primary port does not complete autonegotiation.

Conditions: This issue occurs under normal conditions.

Auto-negotiation is disabled by default on ports 9 and 10 when using 1 Gbps SFPs. Auto-negotiation remains disabled even after the user enables it from the management system. With port redundancy, the Cisco uBR-MC3GX60V line card always checks for auto-negotiation completion before allowing a failed primary port to return to active state. This behavior does not change even after the user tries to disable auto-negotiation on the Cisco uBR-MC3GX60V primary port.

Workaround: Use ports 11 and 12 instead of ports 9 and 10. For ports 9 and 10, configure connected devices for 1 Gbps speed, full duplex, and with auto-negotiation off. With Cisco uBR-MC3GX60V line card port redundancy, use Cisco RFGW 10 DS-384 ports 11 and 12 for primary connections and use ports 9 and 10 for backup and non-redundant connections.

CSCub88510

Symptom: Error message is reported on the Supervisor console by the Cisco RFGW-10 DS-384 line card indicating that an RF power level event has occurred.

Conditions: This issue occurs after issuing hw-module reset command.

The "RF power level out of spec" event is generated due a transient power fluctuation when the arrival of traffic to a port is delayed due to a rare race condition during the un-mute of a QAM carrier on a port.

Workaround: Perform the RF port interface level shutdown and no shutdown to restore any DEPI sessions on port. If any operational issues follow the hardware module reset (with RF power level event), perform a software reset of the DS-384 line card using the cable linecard reset command to re-program the upconverter module.

The hw-module reset command resets a given line card and simulates a power cycle of the line card. If any line card reset is performed during normal operation with redundancy configuration, service is maintained by the secondary designated line card.

CSCuc10713

Symptom: QAMs are stuck in “Idle” state.

Conditions: This issue occurs when multiple line card failures occur before the revertive timer expires.

Workaround: Wait till the revertive timer expires and the revertive switchover completes before initiating another line card failover. Reload the Cisco RF Gateway 10 chassis to recover from the error.

CSCuc13374

Symptom: The following error message is observed on the active and standby Supervisor cards when using default settings for a qam-channel:

Conditions: This error message appears during default of the channels in which the RF-profiles have interleaver depth values other than I32-J4.

Workaround: Associate rf-profile with interleaver depth values as I32-J4.

CSCuc27292

Symptom: The RF profile is not removed even when the no cable downstream rf profile command is accepted without any errors or warnings.

Conditions: This issue occurs when the RF profile is removed while still applied to the QAM interface. The command to remove the RF profile is accepted, but the RF profile is not removed.

Then even after the no cable downstream rf profile command is run to remove the RF profile from the interface, the RF profile is still displayed in running configuration.

Workaround: Reset the interface that the RF profile was applied to, using the default interface command.

The following error messages appears when you default the interface, but this is expected behavior:

CSCuc27709

Symptom: Line card in slot 12 cannot be configured as the primary line card to a redundancy group when the line card in slot 11 is configured as a secondary.

Conditions: This issue occurs when the line card in slot 11 is configured as secondary before configuring line card-12 a primary.

Workaround: Configure line card-12 as primary before configuring the redundancy group.

CSCuc37532

Symptom: Remote RF profiles created on the Supervisor display the same symbol rate for both Annex-B 256qam and Annex-B 64qam.

Conditions: This issue is only a display issue on the Supervisor. In reality, the line card uses the correct symbol rate when 256qam is configured.

Workaround: There is no workaround.

CSCuc45114

Symptom: The show inventory command output displays Child Serial Number for the chassis instead of parent.

Conditions: This issue occurs in normal conditions.

Workaround: Use the show idprom chassis command to get both parent and child serial number.

CSCuc56647

Symptom: Traceback occurs when a new remote RF profile is created.

Conditions: This issue occurs when there are 16 RF profiles existing in the system. The maximum number of RF profile in the systems is 16, and that limit is reached.

Workaround: Check the number of existing RF profiles before creating a new one.

CSCuc58675

Symptom: A Qam-redundancy port configured as shutdown comes up in "UP" state instead of remaining in shutdown state.

Conditions: This issue occurs if the secondary line card initially goes in active state following the reset of both the primary and secondary line cards.

Note This issue affects only the running-configuration and not the startup-configuration.

Workaround: Manually configure the Qam-red port as shutdown.

CSCuc69406

Symptom: The primary Supervisor card crashes after the Cisco CMTS is reconfigured with a frequency change.

Conditions: This issue occurs when RF channels are reconfigured with 6Mhz shifted frequencies. and the last frequency overlaps with another existing RF channel on another controller that has same frequency.

Workaround: There is no workaround. However, fix the frequency overlap to recover the overlap channel.

CSCuc90077

Symptom: The show inventory oid command displays an incorrect OID value for the Cisco RFGW-10 DS-384 line cards.

Conditions: This issue occurs under normal conditions.

Workaround: There is no workaround.

CSCud07306

Symptom: The standby Supervisor card resets and enters into RPR mode when invalid interleaver-depth value is configured for a Annex C rf-profile.

Conditions: This issue happens for annex C profile and only when invalid interleaver-depth value is configured.

Workaround: Do not configure unsupported options such as I12-J17.

CSCud13562

Symptom: The output of the show interface qam-red command displays the bandwidth as 64 QAM even though 256 QAM is configured.

Conditions: This issue occurs only after a Supervisor card switchover.

Workaround:

• Use the show controllers qam qam slot / rf port. qam channel command to view the correct values.
• Do not perform a Supervisor switchover.

CSCud14141

Symptom: Fast Ethernet 1(Management port) is enabled on the Cisco RFGW-10 for management related operations like SNMP, SSH.

Conditions: This is an enhancement.

Workaround: There is no workaround.

CSCud28064

Symptom: The following error message and traceback is observed on the RFGW console.

Conditions: This issue occurs when SNMP walk is performed for 9 hours continuously.

Workaround: There is no workaround.

CSCud32498

Symptom: Ether Channel feature does not work in Cisco RFGW-X45-SUP7-E and it crashes when shutting down the port-channel interface.

Conditions: This issue occurs when ether channel has more than one port mapped to it.

Workaround: Remove the ether-channel configuration.

CSCud39372

Symptom: Supervisor throws the below error message and traceback when line card is removed.

Conditions: This issue occurs when a line card is removed from the line card redundancy group (line card redundancy member) and then reconfigured as a member after the line card has been re-inserted.

Workaround: Ensure that a line card is present when deconfiguring it as a line card redundancy member.

CSCud63812

Symptom: Values entered for the counters command for IPv4 and IPv6 addresses is not inserted in the configuration.

Conditions: This issue occurs while entering the counters command in a VLAN interface.

Workaround: There is no workaround.

CSCud71246

Symptom: Incorrect slot number is reported in error message.

Conditions: This issue occurs when max-carriers value greater than 384 is configured.

Workaround: There is no workaround.

CSCud80455

Symptom: Snmpwalk output on QAM channel displays ifSpeed MIB object output is as 155, which is roughly half of the total speed.

Conditions: This issue occurs when only 4 ports were configured and then 4 more ports were added. The SNMP output does not change.

Workaround: There is no workaround.

CSCud81765

Symptom: Error messages are seen on the Supervisor console causing line card to resets:

Conditions: This issue occurs when frequency profile or rf-profile is changed.

Workaround: There is no workaround.

CSCud91413

Symptom: The line card log files— slogs1 and slogs2—is not created by the software utility slogger.

Conditions: This issue occurs randomly

Workaround: Perform the following:

1. Telnet to line card from Supervisor and manually kill slogger using s lay slogger command

2. Launch the slogger manually.

CSCue05875

Symptom: The secondary Supervisor keeps reloading with PRC mismatch after stateful switchover (SSO).

Conditions: This issue occurs when Supervisor and line cad redundancy is configured and SSO switchover is performed.

Workaround: Before doing the SSO, reset the secondary card using hw-module slot reset command and perform the SSO after line card comes up.

CSCue09705

Symptom: QAM channels configuration on standby Supervisor gets changed after executing cable downstream rf-shutdown command.

Conditions: This issue occurs on QAM channel modes other than DEPI remote-learn.

Workaround: Configure cable downstream rf-shutdown command followed by no cable downstream rf-shutdown command at the port-level for all affected ports before doing an SSO switchover.

CSCue11899

Symptom: The line card re-formats and corrupts the flash file system on the Cisco RFGW-10.

Conditions: This issue occurs when repeated line card switchover is performed.

Workaround: Re-install the license after line card boots up.

CSCue27843

Symptom: The Cisco RFGW 10 front panel is showing Cisco IOS version instead of Cisco IOS-XE release version.

Conditions: This issue is observed on Cisco RFGW-10 with SUP7-E running Cisco IOS-XE. release

Workaround: There is no workaround. This does not impact service.

CSCue34849

Symptom: The force shut channels cannot be enabled after upgrading the license in remote DEPI mode.

Conditions: This issue occurs if the installed license count is reduced and increased back.

Workaround: Resetting the line card will enable the channels.

CSCtx99408

Symptom:

The standby route processor goes into Route Processor Redundancy (RPR) mode if an rf-profile with an invalid interleaver-depth is applied to a QAM channel.

Conditions:

This issue occurs when an invalid interleaver-depth value is configured for an rf-profile. This invalid configuration causes configuration-sync failure and results in the standby going to RPR mode.

Workaround:

Apply the defaulting rf-profile to the affected QAM channel.

CSCuc69406

Symptom:

The primary Supervisor card crashes after the Cisco CMTS is reconfigured with a frequency change.

Conditions:

This issue occurs when RF channels are reconfigured with 6Mhz shifted frequencies. and the last frequency overlaps with another existing RF channel on another controller that has same frequency.

Workaround:

There is no workaround. However, fix the frequency overlap to recover the the overlap channel.

CSCuc74644

Symptom:

A line card switchover is followed by a Supervisor switchover. Also, the modems dropped offline and recovered immediately.

Conditions:

This issue occurs when the system is upgraded to a new release.

Workaround:

There is no workaround.

CSCuc83164

Symptom:

The following error messages are observed when the Annex value is changed from Annex A to Annex B or from Annex B to Annex A:

Conditions:

This issue occurs when the Annex value is changed (from Annex A to Annex B or from Annex B to Annex A) on the Cisco CMTS with remote DEPI configured.

Workaround:

Choose frequency range + 4Mhz while choosing the frequency range from the frequency profile.

CSCuc88700

Symptom:

The Cisco DS48 modems do not come w-online(pt) (wideband-online).

Conditions:

This issue occurs in remote learn DEPI mode when DEPI tunnels are removed and added on the RF Gateway-10 QAM interface.

Workaround:

Reset the line card to enable modems to come w-online(pt).

CSCuc90077

Symptom:

The show inventory oid command displays an incorrect OID value for the Cisco DS384 line cards.

Conditions:

This issue occurs under normal conditions.

Workaround:

There is no workaround.

CSCud03215

Symptom:

Modems fall offline after a hw-module reset of the secondary line card is performed.

Conditions:

This issue occurs under the following conditions:

1. Slot 11 is a primary line card and slot 12 is the secondary line card

2. A line card switchover from slot 11 to slot 12 is performed.

3. A line card switchover back from slot 12 to slot 11 is performed using the hw-module module 12 reset command.

Modems drop offline and services through these modems are disrupted.

Workaround:

Avoid using the hw-module module 12 reset command. Instead, use the redundancy linecard switchover command from slot 12 to revert back.

Note The redundancy linecard switchover command only does a soft reset of slot 12.

To perform a hard reset:

1. redundancy linecard switchover from slot 12.

2. hw-module module 12 reset

This triggers a hard reset. Because slot 12 is in a standby state, the hard reset does not affect services.

CSCud09192

Symptom:

The following traceback and error messages are displayed:

Conditions:

This issue occurs after powering off the cisco RFGW 10 DS-384 line card.

Workaround:

Reload the RF Gateway 10 chassis.

CSCud09384

Symptom:

The following line card failure messages are displayed:

Conditions:

This issue occurs after a Supervisor switchover.

Workaround:

Reload the RF Gateway 10 chassis.

CSCud13562

Symptom:

The output of the show interface qam-red command displays the bandwidth as 64 QAM even though 256 QAM is configured.

Conditions:

This issue occurs only after a Supervisor switchover.

Workaround:

• Use the show controllers qam < qam slot >/< rf port >.< qam channel > command to view the correct values.
• Do not perform a Supervisor switchover.

CSCud17139

Symptom:

Some remote learn DEPI sessions are in IDLE state when the frequency profile is un-configured from QAM interface.

Conditions:

This issue occurs when the QAM port is set to a start frequency of 143 Mhz by default and the frequency profile is unconfigured. This causes issues for some Annex A carriers.

Workaround:

If you need to switch from the frequency profile method to the start frequency method for annexA, do not un-configure the existing frequency profile by using the no cable downstream freq-profile command. Instead, simply apply a proper start frequency other than 143 Mhz.

CSCud21027

Symptom:

The following error message is displayed:

Conditions:

This issue occurs when line cards are un-configured and re-configured along with resetting or removing/re-inserting the same line cards.

Workaround:

There is no workaround.

CSCud24936

Symptom:

Modulation change in the rf-profile are not updated on active sessions in the Manual DEPI mode.

Conditions:

This issue occurs under modulation values are changed from 64 QAM to 256 QAM, or from 256 QAM to 64 QAM.

Workaround:

Manually create two different Annex A rf-profiles—each for 64 qam and 256 qam and apply them based on the requirement.

CSCub99200

Symptom:

Annex A modems connected to the Cisco RF Gateway 10 DS-384 line card go offline when the frequency profile is changed.

Conditions:

This issue occurs when the frequency profile is changed from low to high or high to low and some Annex A QAM channels go offline.

Workaround:

Shut/no shut the QAM port to bring the modems back online.

CSCuc29309

Symptom:

The output for the show tech command is unable to get the boot log output from the Cisco RFGW-10 DS-384 line card flash.

Conditions:

This issue occurs when the system log files exceed 1 Mb in size and the Supervisor card logs an IPC failure message for the Cisco RFGW-10 DS-384 line card.

Workaround:

1. Telnet to the line card to manually convert the line card log from binary format to TXT:

On the line card console, do the following:

2. From the Supervisor console, transfer these files to another location:

CSCuc51836

Symptom:

The speed of the fan is at a higher value than the level needed for controlling the chassis temperature.

Conditions:

This issue occurs under normal conditions.

Workaround:

There is no workaround. There is no functional impact.

CSCuc61424

Symptom:

On the Cisco RFGW-10 DS-384 line card, the DTI timing offset increases in time, when the offset should reduce it.

Conditions:

This issue occurs when the user inputs the DS-384 timing offset in the command line interface (CLI).

Workaround:

Do not use the timing offset for the Cisco RFGW-10 DS-384 line card.

CSCuc99361

Symptom:

Traffic is lost if user downgrades from a release later than Cisco IOS-XE Release 3.2.1SQ to Cisco IOS-XE Release 3.2.1SQ or Cisco IOS-XE Release 3.2.0SQ.

Conditions:

This issue occurs under normal conditions.

Workaround:

First downgrade to Cisco IOS-XE Release 3.2.1SQ before downgrading to IOS-XE 3.2.0SQ.

CSCud06038

Symptom:

Cannot configure 24 QAM DEPI local sessions for Annex A with modulation 256.

Conditions:

This issue occurs on the Cisco DS-48 line cards where the max bandwidth on mid-plane is 1Gbps. Because there is insufficient bandwidth, the line card rejects the sessions.

Workaround:

Use a maximum of 19 DEPI sessions on the line card.

CSCud15925

Symptom:

The following error message is displayed:

Conditions:

This issue occurs when there is a reset of the Cisco CMTS with remote DEPI sessions configured in Annex A and Annex A modems are connected to DS384 line card.

Workaround:

Reset line card.

CSCud30159

Symptom:

Duplicate RF profiles are allowed, thereby causing synchronization issues and Supervisor switchover failure.

Conditions:

This issue occurs when duplicate local rf-profile is created and then a supervisor switchover is triggered.

Workaround:

Remove the RF profile. Do not convert this RF profile to a duplicate of existing profiles

CSCud36776

Symptom:

The Supervisor card crashes.

Conditions:

This issue occurs when the show platform hardware interface all command is executed through the show tech-support command.

Workaround:

There is no workaround.

CSCty03978

Symptom:

The following error message is displayed when modifying the license priority:

Conditions:

This issue occurs when modifying the temporary license priority.

Workaround:

Reload the line card.

CSCty84981

Symptom:

The 'missing IDB for FIBIDB' error message is displayed after the Supervisor switchover:

Conditions:

This issue occurs when:

1. 1:1 redundancy (with 3 and 11 cards) and 1:N redundancy (with 4, 5, 6, 12) redundancy groups are configured.

2. A 'redundancy reload peer' is performed.

3. After both supervisors are up again, a 'redundancy force-switchover' is performed.

Workaround:

There is no workaround.

CSCty99783

Symptom:

The following error message is displayed when the license priority is modified:

Conditions:

This issue occurs when the temporary license priority is modified and the license count is not updated or synchronized with the Supervisor card.

Workaround:

Reload the line card.

CSCtz92104

Symptom:

DPLL and MPEG error messages are printed to the console when the TCC cards are disconnected and then reinserted.

Conditions:

This issue occurs when:

1. Either both the TCC card have failed.

2. Or when the TCC card is in 'fast' mode (reacquiring clock). This error is expected for that transient period.

Workaround:

There is no workaround.

CSCua58184

Symptom>

The following error is seen on the Supervisor console when a line card is inserted into a slot:

Conditions:

This issue occurs if the Supervisor card is unable to read the serial EEPROM (SEEPROM) of the line card when the card is being slowly inserted into the chassis.

Workaround:

Reinsert the line card. The Supervisor card is successful in reading the EEPROM in the second attempt.

CSCua62962

Symptom:

The following error message may be generated on the standby Supervisor card for the primary line card ports:

Conditions:

This issue occurs for a line card redundancy group, if one or more primary line cards are reset, followed by configuration of a secondary line card.

This issue can impact data traffic following a Supervisor switchover for the affected ports.

Workaround:

Either reset the standby Supervisor card or modify the secondary configuration requirement to ensure all primary line cards in the redundancy group are present and active before configuring the secondary line card for the group.

CSCua72252

Symptom:

The output of the show controller linecard 3 bandwidth displays the value "0" for the used-bandwidth field.

Conditions:

This issue occurs when:

1. A line card switchover occurs from the CMTS side.

2. The standby line card became active.

3. The associated QAM-channel used-bandwidth field of the show controller linecard 3 bandwidth displays the value "0".

Workaround:

Switch back over to the primary line card on CMTS side.

CSCua99738

Symptom:

The show inventory command shows incorrect values for the TCC hardware revision.

Conditions:

This issue occurs under normal conditions.

Workaround:

Use the show idprom module command to get the correct values.

CSCub01890

Symptom:

The following error message is displayed:

Conditions:

This issue occurs after the timing and clock card (TCC) switchover. This issue has no service-affecting impact.

Workaround:

There is no workaround.

CSCub01894

Symptom:

After the line card redundancy is removed, previous configuration of the new independent card (prior to configuring redundancy) are still preserved and an attempt to bring up the sessions fails.

Conditions:

This issue occurs under normal conditions.

Workaround:

Before configuring the stand alone line card as a secondary line card, default all QAM ports of the line card to be configured, as secondary.

Or, manually remove all the configuration for that line card slot in the newly independent card.

CSCub02324

Symptom:

The following error is observed:

Conditions:

This issue occurs when executing the redundancy force-switchover command.

Workaround:

There is no workaround. Ignore message; there is no operational impact.

CSCub34355

Symptom:

The following error message is displayed:

Conditions:

This issue occurs when the default configuration is applied to the port that is in shutdown state.

Workaround:

If the port is admin_down state, unshut the port before applying the default configuration at the port level.

CSCub40326

Symptom:

Removing a SPAN configuration causes both Supervisor cards to reload.

Conditions:

This issue occurs when SPAN source and SPAN destination interfaces are configured. The filter should be negated using the no config command for a non-switchport interface.

Workaround:

1. Do not remove the filter configuration.

2. Configure monitor source command before configuring the interface with no switchport.

CSCub46770

Symptom:

Modems go from w-online(pt) to online(pt) state when the modulation is changed to 64 and then reverted back to 256.

Conditions:

This issue occurs when the modulation is directly modified.

Workaround:

To change configuration:

CSCub46777

Symptom:

When different versions of the Cisco IOS-XE image are loaded, the sessions on the RF Gateway10 front panel TenGigE are absent.

Conditions:

This issue occurs under normal conditions.

Workaround:

Set link-flap value to 10 on the aggregation switch.

CSCub49579

Symptom:

The output of the show interfaces modular-Cable < controller:channel > dlm command does not display the values for DLM.

Conditions:

This issue occurs when the sampling rate for the corresponding rf-channel of the modular controller is set to 500.

Workaround:

For the depi-tunnel configured in the corresponding rf-channel of modular controller, set the retransmit retries value and the retransmit initial retries value to 10.

CSCub59125

Symptom:

DEPI sessions stay 'Idle' on the line card.

Conditions:

This issue occurs while rebooting RF Gateway 10.

Workaround:

Reset the faulty line card.

CSCub73486

Symptom:

The LQAM configuration is rejected with the following error:

Conditions:

This issue occurs if a saved configuration is copied from a storage device to the running configuration after the RF Gateway 10 is booted up with all default configurations.

Workaround:

Remove the carrier ID command from the saved configuration and then apply it onto the running configuration.

CSCub75878

Symptom:

The following error message is displayed on the Supervisor standby console:

Conditions:

This issue occurs the Cisco RFGW-10 DS-384 line card is inserted in a slot after removing the Cisco DS-48 line card.

Workaround:

Reset the line card in the slot.

CSCub82362

Symptom:

For the Cisco RFGW 10 DS-384 line card, autonegotiation is not supported on ports 9 and 10 with 1 Gbps SFPs.

For a scenario where a primary port on the Cisco uBR-MC3GX60V line card is directly connected to ports 9 or 10 of the Cisco RFGW 10 DS-384 line card and primary port link is restored, the backup port still remains active because the primary port does not complete autonegotiation.

Conditions:

This issue occurs under normal conditions. Autonegotiation is disabled by default on ports 9 and 10 when using 1 Gbps SFPs. Autonegotiation remains disabled even after the user enables it from the management system. With port redundancy, the Cisco uBR-MC3GX60V line card always checks for autonegotiation completion before allowing a failed primary port to return to active state. This behavior does not change even after the user tries to disable autonegotiation on the Cisco uBR-MC3GX60V primary port.

Workaround:

Use ports 11 and 12 instead of ports 9 and 10. For ports 9 and 10, configure connected devices for 1 Gbps speed, full duplex, and with autonegotiation off. With Cisco uBR-MC3GX60V line card port redundancy, use Cisco RFGW 10 DS-384 ports 11 and 12 for primary connections and use ports 9 and 10 for backup and non-redundant connections.

CSCub87522

Symptom:

The following error is seen on the Supervisor console:

Conditions:

This issue occurs when a file is copied to the USB device.

Workaround:

There is no workaround. The system retries the read and write operation and the error is recovered automatically.

CSCub89864

Symptom:

The following error message is seen on active Supervisor console when the standby Supervisor comes up after a redundancy switchover.

Conditions:

This issue occurs when the primary line card is reset/removed and the switchover happens simultaneously.

Workaround:

There is no workaround. This issue occurs rarely because of an initialization issue, which completes upon retry.

CSCub95552

Symptom:

Cable modems flap when the line card switchover is initiated using the cable linecard reset command.

Conditions:

This issue occurs with line card in slot 11 to line card in slot 12 switchovers. However, this issue can happen on any line card switchover.

Workaround:

Do not use the cable linecard reset command. Instead use the redundancy linecard switchover command.

CSCuc01025

Symptom:

After a Supervisor switchover, when executing the configuration to remove the line card redundancy, the standby supervisor silently reloads itself.

Conditions:

This issue occurs under normal conditions.

Workaround:

There is no workaround. The standby supervisor resets itself and comes back healthy without any issues. No manual intervention is required.

CSCuc01153

Symptom:

The following error messages are observed:

Conditions:

This issue occurs while configuring line card redundancy with remote DEPI configurations followed by a reset of the line card.

Workaround:

Reload the Cisco RF Gateway 10 chassis.

CSCuc02064

Symptom:

If the line card switchover and Supervisor card switchover occur with a few seconds of each other, the QAM channels are moved to muted state.

The line card status for the DEPI sessions are also displayed as being in OFF state.

Conditions:

This issue occurs while performing a line card switchover within a few seconds of a Supervisor card switchover.

Workaround:

Reset the primary and secondary line cards.

CSCuc02232

Symptom:

After the online insertion and removal (OIR) of the Cisco RFGW 10 DS-384 line card, some "idle" DEPI sessions are also displayed in the output of the show cable depi l2tp command.

Conditions:

This issue occurs only on a standalone DS-384 line card and when line card redundancy is not configured.

Workaround:

There is no workaround; sessions are cleared once they are timed out. No manual intervention is needed.

CSCuc10713

Symptom:

QAMs are stuck in "Idle" state.

Conditions:

This issue occurs when multiple line card failures occur before the revertive timer expires.

Workaround:

Wait till the revertive timer expires and the revertive switchover completes before initiating another line card failover. Reload the Cisco RF Gateway 10 chassis to recover from the error.

CSCuc13374

Symptom:

The following error message is observed on the active and standby Supervisor cards when using default settings for a qam-channel:

Conditions:

This error message appears during default of the channels in which the RF-profiles have interleaver depth values other than I32-J4.

Workaround:

Associate rf-profile with interleaver depth values as I32-J4.

CSCuc24855

Symptom:

The QAM ports of a non-redundant Cisco RFGW 10 DS-384 line card are not displayed in the output of the show running-configuration command on the standby Supervisor card.

Conditions:

This issue occurs only on the Cisco RFGW 10 DS-384 line card in slot 11 or 12 after the card is unconfigured as a Secondary member of the line card redundancy group.

Any configuration of the QAM port of such line card can cause the standby Supervisor to detect a configuration mismatch condition resulting in the reboot of the standby Supervisor. After the standby Supervisor reboots, the condition is fully recovered.

Workaround:

There are two workarounds:

• Reboot the standby Supervisor.
• After the line card in slot 11 or 12 comes back up following its uncofiguration as a Secondary line card, run the hw module reset command to reset the line card.

CSCuc26905

Symptom:

The following error message is displayed followed by traceback on the active supervisor card:

Conditions:

This issue occurs after the Supervisor card switchover when the system CPU load is high (over 90%).

Workaround:

There is no workaround.

CSCuc27292

Symptom:

The RF profile is not removed even when the no cable downstream rf profile command is accepted without any errors or warnings.

Conditions:

This issue occurs when the RF profile is removed while still applied to the QAM interface. The command to remove the RF profile is accepted, but the RF profile is not removed.

Then even after the no cable downstream rf profile command is run to remove the RF profile from the interface, the RF profile is still displayed in running configuration.

Workaround:

Reset the interface that the RF profile was applied to, using the default interface command.

The following error messages appears when you default the interface, but this is expected behavior:

CSCuc27709

Symptom:

Line card in slot 12 cannot be configured as the primary line card to a redundancy group when the line card in slot 11 is configured as a secondary.

Conditions:

This issue occurs when the line card in slot 11 is configured as secondary before configuring line card-12 a primary.

Workaround:

Configure line card-12 as primary before configuring the redundancy group.

CSCuc29309

Symptom:

The output for the show tech command is unable to get the boot log output from the Cisco RFGW-10 DS-384 line card flash.

Conditions:

This issue occurs when the system log files exceed 1 Mb in size and the Supervisor card logs an IPC failure message for the Cisco RFGW-10 DS-384 line card.

Workaround:

1. Telnet to the line card to manually convert the line card log from binary format to TXT:

On the line card console, do the following:

2. From the Supervisor console, transfer these files to another location:

CSCuc29634

Symptom:

While changing an RF profile that is applied to manual qam interface, the system stops responding and the following IPC message is displayed:

Conditions:

This issue occurs when the RF profile that is being changed is applied to a QAM interface.

Workaround:

There is no workaround.

CSCuc37532

Symptom:

Remote RF profiles created on the Supervisor display the same symbol rate for both Annex-B 256qam and Annex-B 64qam.

Conditions:

This issue is only a display issue on the Supervisor. In reality, the line card uses the correct symbol rate when 256qam is configured.

Workaround:

There is no workaround.

CSCuc39115

Symptom:

When a secondary line card, which is in Active state due to a line card switchover, is removed from a redundancy group, an error message is displayed:

Conditions:

This issue occurs when a Secondary line card is in Active state due to a line card switchover and the other primary line cards are powered down.

Workaround:

There is no workaround.

CSCuc40784

Symptom:

The following entity MIB-related traceback and error messages are displayed:

Conditions:

This issue occurs when the line card is powered off, powered on, and then powered off again within a period of 5 to 10 seconds.

Workaround:

There is no workaround.

CSCuc42319

Symptom:

During a Supervisor switchover, or during system boot up, the following message is displayed on the Supervisor console:

Conditions:

This issue is seen during a Supervisor switchover because the line card needs to reconnect to the new active Supervisor.

This message indicates that the line card has detected a backplane link failure between the line card and the active Supervisor. This link failure event was reported to the active Supervisor, which triggered an XPOINTSWITCH reset.

This message informs that a XPOINTSWITCH reset has been issued to recover the backplane links between the line card and the active supervisor.

Workaround:

There is no workaround.

The XPOINTSWITCH reset recovers from the link failure. Modems connected to the line card may temporarily drop offline.

CSCuc43664

Symptom:

All manual DEPI sessions are in "rf-shut" state.

Conditions:

This issue occurs after a combination of line card high availability, stateful switchover (SSO), and a hardware module reset.

Workaround:

To recover from this condition:

1. Run the no cable downstream rf-shut on each rf-shut channel.

2. Initiate a single SSO without saving the configuration.

This recovers all sessions.

CSCuc47174

Symptom:

SNMP traps for link-status are not sent for some QAM ports when they are added to a redundancy group.

Conditions:

This issue occurs under two conditions:

1. When the SNMP trap link status is removed from the QAM port when it is configured on a standalone line card and this line card is added to a redundancy group.

2. When SNMP trap link status is configured in Qam-redundancy port, SNMP traps are removed if there is a corresponding LC_IMAGE_UPGRADE event.

Workaround:

Reconfigure SNMP trap link status on the Qam port from where it is removed.

CSCuc49069

Symptom:

Remote DEPI ports are impaired after a series of line card high availability, stateful switchover (SSO), and a hardware module resets. DEPI session are displayed as Active, but modem do not come online.

Conditions:

This issue occurs when start frequency on the remote DEPI port is modified a few times before the line card high availability, SSO, and a hardware module reset combination.

Workaround:

To avoid this issue, save the configuration and reboot after changing the start frequency.

To recover from this issue, perform a shut/no shut of the RF port.

CSCuc53957

Symptom:

The QAM associated with the Cisco RFGW-10 DS-384 line card is removed if line card high availability and stateful switchover (SSO) are executed in a particular sequence.

Conditions:

This issue occurs when:

1. The secondary line card is initializing and the SSO is triggered

2. The next line card redundancy (LCRED) operation from primary line card to secondary line card triggers a missing QAM configuration problem.

Workaround:

Trigger another LCRED. The missing QAM issue is resolved.

CSCuc54049

Symptom:

Tracebacks are observed after replacing the secondary Cisco DS48-1G line card with a Cisco DS-48 line card.

Conditions:

This issue occurs when the secondary Cisco DS48-1G line card is configured to protect other DS48-1G line cards. After replacing the secondary DS48-1G with the Cisco DS48 line card, the tracebacks are observed.

Workaround:

There is no workaround. A Cisco DS-48 line card cannot protect the Cisco DS48-1G line cards.

CSCuc56647

Symptom:

Traceback occurs when a new remote RF profile is created.

Conditions:

This issue occurs when there are 16 RF profiles existing in the system. The maximum number of RF profile in the systems is 16, and that limit is reached.

Workaround:

Check the number of existing RF profiles before creating a new one.

CSCuc58675

Symptom:

A Qam-redundancy port configured as shutdown comes up in "UP" state instead of remaining in shutdown state.

Conditions:

This issue occurs if the secondary line card initially goes in active state following the reset of both the primary and secondary line cards.

Note This issue affects only the running-configuration and not the startup-configuration.

Workaround:

Manually configure the Qam-red port as shutdown.

CSCuc61424

Symptom:

On the Cisco RFGW-10 DS-384 line card, the DTI timing offset increases in time, when the offset should reduce it.

Conditions:

This issue occurs when the user inputs the DS-384 timing offset in the command line interface (CLI).

Workaround:

Do not use the timing offset for the Cisco RFGW-10 DS-384 line card.