Preview Tool

Cisco Bug: CSCvs80572 - cBR-8 Vecima 2x2 pilot tone configuration issue

Last Modified

Aug 29, 2020

Products (4)

  • Cisco cBR Series Converged Broadband Routers
  • Cisco Catalyst 9800-L-C Wireless Controller
  • Cisco Catalyst 9800-L-F Wireless Controller
  • Cisco cBR-8 Converged Broadband Router

Known Affected Releases


Description (partial)

The first is the initialization GCP message exchange, which shows the core doing the correct behaviour.  (use the wireshark filter "gcp.rcp.tlv.DsScQamChannelConfig.OperationaMode == 5" in order to see both SC-QAM as CW configuration messages If you're not using our dissectors, packets 289, 393, 679, and 776 show the core correctly sending the pilot tone configuration to both ports.  There is no bug in this first capture, it is simply to show that 2 DS RF ports are configured.
The problem comes into play when you try to issue a mute command from the cBR-8 command line.  Specifically, the mute is issued from within the pilot tone profile.  In this case, the core only sends the mute / unmute command for port 0.  The mute command can be found in packets 63/67 of the second capture file, while the unmute command can be found in packets 574/582 by using the same command.  If we were to use two different profiles, however, then the mute/unmute would be set for the appropriate port.
This is similar to scenario 1, except the configuration has unconfigured the SC-QAM as CW to have ONLY dedicated CW carriers in the pilot tone profile.  
In the initialization capture,there are indeed 2 ports configured and that the core is configuring them correctly.  The dedicated CWs for port 0 are configured as a part of a very large message that spans packets 18+19 (for port 0) and is responded to in packet 28.  The second port is configured in packet 274 and responded to in packet 363. Again, this is simply a reference, not a bug report.
In the dynamic change capture, the mute command (for tone index 3) at packets 53/63, the corresponding unmute command at packets 456/464.  No command is issued for the second port.  If we were to use two different profiles, however, then the mute/unmute would be sent by the core for the appropriate port.

See attachements
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.