Cisco Headend System Release 2.5 Notas de publicación
4001159 Rev B
Known Issues for Optional Features
6-3
Known Issues for RCS in SR 3.5,
Continued
CR 50771-01: Incorrect Site IDs Affect Alarms for RNCS Systems
Site IDs for RNCS devices are reported correctly in the DNCS database. However,
site IDs in the RNCS database are incorrect. For example, if the site ID for a QAM
connected to a RNCS is 2, the site ID is 2 in the DNCS database. However, the site ID
in the RNCS database is 1.
Given these incorrect site IDs, the RNCS cannot detect when a device, such as a
Given these incorrect site IDs, the RNCS cannot detect when a device, such as a
QAM, should be part of its system. As a result, alarms are not issued in Alarm
Manager if the device experiences issues, such as failure to connect.
CR 53407: dncs_host Alias Added To /etc/host Files For RNCS and Object Carousel
The ntp.conf file uses the dncs_host alias for its server. The dncs_host alias was
added to the /etc/host files for the RNCS and the Object Carousel to allow the
ntp.conf file to work correctly.
bfsServer Will Not Go Active When a QAM Is Not Directly Connected to the DNCS
Some sites do not have headend equipment directly connected to the DNCS. If this
scenario is in place, then all QAMs and QPSKs must be routed through a LIONN first.
Workaround: To enable this scenario, connect a QAM directly to the DNCS and
Workaround: To enable this scenario, connect a QAM directly to the DNCS and
allow the local BFS Sessions to go active. Once the BFS Sessions go active, you can
remove and disable the QAM, then disable the sources for the DNCS. (Do not
disable the sources for the RNCS.)