Guest

Preview Tool

Cisco Bug: CSCun17923 - DBDS: RNCS setup N/W devices are listed as dncs system devices

Last Modified

Jun 22, 2020

Products (1)

  • Headend System Releases

Known Affected Releases

dbdsUtil-6.5.0.18

Description (partial)

Symptom:
DBDS: RNCS setup N/W devices are listed as dncs system devices

Conditions:
Issue1:
Steps to follow,

Preamble: Make sure the system having RNCS setup(lionn) and make sure it is up and running

1. Go to /dvs/dncs/Utilities/doctor directory
2. run doctor -n
3. Open the report file
4. we have 2 parts - System Name : dncs (RF) and System Name : lionn


Actual Result: All the N/W devices(lionn N/W devices too) are listed under 'System Name : dncs (RF)'. And the 'System Name : lionn' part doesn't have any devices eventhough it having.

Expected Result: If the N/W elements belongs to DNCS then it should be listed under 'System Name : dncs (RF)' and if the N/W elements belongs to RNCS then it should be listed under 'System Name : lionn'.


Issue2: Looks like the above one.

DBDS: RNCS GQAM's smdg entries are listed under DNCS system instead of RNCS section

Steps to follow,

Preamble: Make sure the system having SMDG entry on DNCS GQAM and on RNCS GQAM 

1. Go to /dvs/dncs/Utilities/doctor directory
2. run doctor -r smdgInfo
3. Open the report file
4. we have 2 parts - System Name : dncs (RF) and System Name : lionn


Actual Result: Now, RNCS GQAM's smdg entries are listed under 'System Name : dncs (RF)'

Expected Result: RNCS GQAM's smdg entries should be displayed under 'System Name : lionn'.' not under 'System Name : dncs (RF)'

Refer attached doc.
Bug details contain sensitive information and therefore require a Cisco.com 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.