Cisco Headend System Release 2.7 Release Notes
Known Issues
4012155 Rev B
29
CR 65909
Users may not be able to change or remove hub associations from the channel map.
CR 65972
When a user creates a segment with the same name as an existing segment, the
system modifies the existing segment without notifying the user.
system modifies the existing segment without notifying the user.
CR 65976
Users cannot edit the IP/Bridge name for a Cable Modem Termination System
(CMTS) that is already provisioned on the system.
(CMTS) that is already provisioned on the system.
Workaround: Delete the CMTS and provision it again with the new name.
CR 66213
The Multi-Media Message (MMM) UI occasionally fails unexpectedly. When this
failure occurs, users are unable to send EAS messages from the DNCS.
failure occurs, users are unable to send EAS messages from the DNCS.
CR 66354
If the .profile file on the DNCS contains the variable LOG_TO_EMS and the value is
set to “1,” several system GUIs core dump.
set to “1,” several system GUIs core dump.
Workaround: Set the LOG_TO_EMS variable to “0” (zero), source the .profile file,
and then re-open the DNCS Administrative Console.
and then re-open the DNCS Administrative Console.
CR 66393
If the system operator changes the DNCS system IP address, the remote procedure
call (RPC) UI is not available when the operator creates a new Value Added Service
Provider (VASP) Type.
call (RPC) UI is not available when the operator creates a new Value Added Service
Provider (VASP) Type.
CR 66862
The qpskManager process occasionally causes corrupt SI packets. Corrupt SI packets
may cause the set-top to lose its authorization and go into brick mode.
may cause the set-top to lose its authorization and go into brick mode.
CR 67052
PowerKEY CableCARD modules may not receive split channels correctly during
DST changes.
DST changes.
CR 67063
The dataPump (carousel) is sending bad packets to the ASI card, which causes the
card to reset. When this reset occurs, there is no BFS data transmitted from the
DNCS.
card to reset. When this reset occurs, there is no BFS data transmitted from the
DNCS.
Workaround: Reboot the DNCS host to correct this condition.