Cisco Headend System Release 2.7
Chapter 1 Introducing System Release 2.7/3.7/4.2 Service Pack 2
4
4019475 Rev D
Source ID
Source ID Name
24 (the original)
SGM IB
26
SGM IB1
28
SGM IB2
30
SGM IB3
32
SGM IB4
Notes:
After upgrading to SR 2.7/3.7/4.2 SP2, Source IDs 26, 28, 30, and 32 are created,
but are disabled by default.
Important: If a BFS source is enabled prior to the upgrade, the source will remain
enabled after the upgrade.
but are disabled by default.
Important: If a BFS source is enabled prior to the upgrade, the source will remain
enabled after the upgrade.
The data rate for each source (including source ID 24) should be set to 0.50 Mbps
and the block size should be 4,000 bytes.
and the block size should be 4,000 bytes.
Additional carousels (more than 4) may always be manually configured for a
system.
system.
When you exceed 475 SDV service groups, refer to the SDV Operator's Guide For
System Releases 2.7/3.7 or SR 4.2 Service Pack 2 (part number 4019781) for specific
instructions on how to expand SDV service groups.
System Releases 2.7/3.7 or SR 4.2 Service Pack 2 (part number 4019781) for specific
instructions on how to expand SDV service groups.
BOSS Query Support for Package Transactions
The Business Operations Support System (BOSS) package transactions are required
to successfully use SSC DHCTs in your DBDS. BOSS transactions have been
enhanced to allow for provisioning of M-Card modules for network operation and
conditional access.
to successfully use SSC DHCTs in your DBDS. BOSS transactions have been
enhanced to allow for provisioning of M-Card modules for network operation and
conditional access.
Netcrypt Bulk Encryptor Bandwidth Savings
In SRs earlier than 2.7/3.7/4.2 SP2, if a site utilized a Netcrypt Bulk Encryptor, all
exclusive sessions were routed through the Netcrypt Bulk Encryptor, regardless of
whether or not they were clear or encrypted sessions.
exclusive sessions were routed through the Netcrypt Bulk Encryptor, regardless of
whether or not they were clear or encrypted sessions.
An enhancement to SR 2.7/3.7/4.2 SP2 streamlines the session setup process by not
requiring that clear sessions be routed through the Netcrypt Bulk Encryptor.
requiring that clear sessions be routed through the Netcrypt Bulk Encryptor.
Note: If your site uses a Network Bulk Encryptor, make sure that your routing
device contains paths for both encrypted and clear sessions.
device contains paths for both encrypted and clear sessions.