Cisco Headend System Release 2.5
4001159 Rev B
What CRs Are Included in SR 3.5?
4-3
Want to Know More?
Overview
This section provides more detail about each fix in SR 3.5. The descriptions in this
section are not intended to be comprehensive. If you have additional questions about
a particular change request, contact Cisco Services.
File Names Greater Than 100 Characters in Length Now Supported in dncsFilesBackup Script
The DNCS key files consist of those files required to boot the DNCS. The script that
backs up the DNCS key files is called dncsFilesBackup. Previously, if a DNCS key file
name was greater than 100 characters, the dncsFilesBackup script was reporting an
error. Although the script was reporting an error, the files were still backed up to tape.
To address this issue, reported in CR 36770, Cisco modified the dncsFilesBackup
To address this issue, reported in CR 36770, Cisco modified the dncsFilesBackup
script to accept filenames greater than 100 characters in length.
Size Limitations for the SAM Bulk Table Are Managed Effectively
Each time you register a service with the SAM, the DNCS assigns the service a unique
service ID and, in some cases, a new URL. These URLs are stored in the bulk.tbl file,
which is located in the /dvs/dvsFiles/SAM directory. Previously, when the bulk.tbl
size limitation of 65 KB was exceeded, a much smaller, incomplete bulk.tbl file was
created by saManager. When set-tops downloaded this smaller, incomplete file from
the BFS, the set-tops no longer received complete service information. As a result, set-
tops displayed black screens and/or continuously rebooted.
To address this issue, reported in CR 38526-01, the DNCS code was updated to
To address this issue, reported in CR 38526-01, the DNCS code was updated to
ensure a new SubTable is created anytime data threatens to push the size of bulk.tbl
over 65 KB. In addition, a new 4-bit SubTable is created for extremely rare cases
where the number of unique service IDs exceeds 65536.
Continued on next page