Cisco Headend Digital Broadband Delivery System Manual De Manutenção
Chapter 7 Troubleshooting
138
4004455 Rev G
Deleting Stranded Audio Links
1 From the DNCS Administrative Console, select the Application Interface
1 From the DNCS Administrative Console, select the Application Interface
Modules tab.
2 Click BFS Client. The Broadcast File Server List window opens.
3 Scroll down the window and double-click the MMMAud icon.
3 Scroll down the window and double-click the MMMAud icon.
Note: The icon looks like a filing cabinet.
Result: The filing cabinet "opens" to display its files.
Result: The filing cabinet "opens" to display its files.
4 Highlight the file that corresponds to the stranded audio link you identified in
Checking for Stranded Audio Links (on page 137).
5
Click File > Delete. A confirmation window displays.
6 Click Yes. The system deletes the file.
Notes:
In some cases, you might have to repeat this procedure until the system
finally deletes the file.
finally deletes the file.
If, after several attempts, the system does not delete the file, delete the entire
MMMAud filing cabinet.
MMMAud filing cabinet.
7 Close the Broadcast File Server List window.
Server Error when Registering with BFS
Beginning with DNCS SR 2.5/3.5, there can be times when the MMMServer fails to
recover if, for some reason, the MMMAud BFS cabinet is removed, but the MMMCfg
cabinet remains. When this happens, the DNCS writes an error message similar to
the following in the dncsLog file:
recover if, for some reason, the MMMAud BFS cabinet is removed, but the MMMCfg
cabinet remains. When this happens, the DNCS writes an error message similar to
the following in the dncsLog file:
...MMMBfs::_registerServer(): BFS Error registering with BFS
The initial symptom of this error shows up when you try to send an EAS message
with both audio and video, and the DNCS GUI disappears from the screen.
with both audio and video, and the DNCS GUI disappears from the screen.
If you see this behavior, follow the procedure in this section to remedy the error.
Note: This behavior was fixed by CR 52603 in DNCS SR 2.5/3.5 SP1.