Cisco Headend System Release 2.7 Release Notes
6-2
What Are the Known Issues for Optional Features in SR 4.0?
4001703 Rev B
Known Issues for RCS in SR 4.0
CR 48374: BFS Elements Created from All Sites Must Be Edited from All Sites
If you create links, files, directories, servers, and sources using the All Sites feature
from the BFS Client, you must make any changes to these elements through the
Broadcast File Server List for All Sites. Changes you make to these BFS elements
from All Sites are propagated to all of the individual sites by the bfsServer process.
If the BFS elements were originally propagated using the All Sites feature, deleting
If the BFS elements were originally propagated using the All Sites feature, deleting
or editing these elements from individual sites can result in error conditions, such as
missing or broken links, that prevent set-tops from receiving BFS services.
Important: If you did not use the All Sites feature to create BFS elements, edit those
elements from the individual sites as necessary.
CR 50551: Emergency Alert Messages Are Not Filtered on the Inband Path
The FIPS code filtering is currently only done OOB per QPSK/CMTS. However,
hosts without CableCARD modules receive all Emergency Alert Messages through
the inband path. In the RNCS architecture, this means if Site2 in Florida receives a
tornado warning, Hosts without CableCARD modules at Site3 in Colorado will also
receive the warning.
Access the Broadcast File
Server List from All Sites rather
than from an individual site.
Server List from All Sites rather
than from an individual site.