Cisco Headend System Release 2.5 Release Notes
5-8
Known Issues for Standard SR 3.5
4001159 Rev B
Known Issues in the Standard Version of SR 3.5,
Continued
CR 52603-01: MMMServer May Not Recover and Register with BFS
Correct operation requires you to delete both the MMMAud and MMMCfg servers at
the same time before stopping the MMMServer process. When you do this, both
servers rebuild correctly when you restart the MMMServer process. If you delete
only the MMMAud server (leave the MMMCfg server as is), then the following error
conditions occur when you restart the MMMServer process:
•
•
The MMMAud server does not rebuild.
•
The MMMServer process does not recover and register with BFS. Instead, the
following message appears multiple times in the dncsLog:
...MMMBfs::_registerServer(): BFS Error registering with BFS
...MMMBfs::_registerServer(): BFS Error registering with BFS
•
You cannot successful send an EAS message with both text and audio content. The
user interface disappears without processing the message.
Workaround: Currently, if you want avoid these error conditions, you must delete
both the MMMAud and MMMCfg servers from the Broadcast File Server List before
you stop and restart the MMMServer process. If you have already experienced the
error conditions previously detailed, complete the following workaround to correct
the error conditions.
1.
From the DNCS Administrative Console, click the Application Interface
Modules tab.
2.
Click BFS Client.
3.
From the Broadcast File Server List, select the MMMCfg server.
4.
Click File and choose Delete.
5.
Stop and restart the MMMServer process again.
Result: The MMMServer process registers both the MMMAud server and the
Result: The MMMServer process registers both the MMMAud server and the
MMMCfg server with the BFS.
CR 52833-03: Encrypted Service Content May Go in the Clear Due to sgManager Refresh Cache
This CR describes a corner case. Intermittently, the sgManager sends out a refresh
cache to the drm that causes a mismatch between the drm and dsm. This mismatch
results in segment information not being sent to the bsm; therefore, the content could
go out in the clear.
Workaround: A correction to this CR is available through an emergency software
Workaround: A correction to this CR is available through an emergency software
patch. Contact Cisco Services for more information.