Mediaroom Troubleshooting Tools: Client Trace Log Viewer
During my
previous blog posts we have discussed what Microsoft Mediaroom is and some of its features which help differentiate it from standard television providers. In my next set of posts we’ll discuss some of the tools that Mediaroom support personnel can use to troubleshoot various aspects of the Mediaroom environment. Over the last couple of months, I’ve had occasion to work with a customer that is new to the Mediaroom environment, and the one tool that we are constantly using is called the
Client Trace Log Viewer, so I figured it would be a great place to start our Mediaroom tools discussions.
Often times, we are asked to investigate why end user
set top boxes (STBs) are not performing as expected; slow performance, missing guide information, VOD playback, etc. All of these issues are visible to the end users eye but are hard to quantify without any real data from the components themselves, this is where the Client Trace Log Viewer (
CTL Viewer) comes into play. In the next couple of sections we’ll discuss CTLs features and how to configure, view, and filter the captured events.
Features
The CTL Viewer allows support personnel to gather real-time debugging information from any STB in the Mediaroom environment. We can easily enable CTL viewing on any specific STB we choose. This ability to drill down to individual devices is particularly useful as often times end users have multiple units. Once CTL viewing is enabled, it changes the logging state of the STB and tells the device to start collecting trace logging of the actions it performs and to pass this information to the Mediaroom servers. Nothing is physically connected to the STB nor is there any additional tracing software needed (all logging is implemented server-side). This means that the operator can have multiple sinks and filters running without fear of performance impact.
Configuring Client Trace Log Viewer
The first step is to configure the CTL Viewer (generally the executable will be located in the Mediaroom Resource Kit)
- Run ClientTraceLogViewer.exe
- Select Connection > Open Serverlayout
- Navigate to the serverlayout.xml file (the path C:\Program Files\Microsoft IPTV Services\config\serverLayout.xml)
Enabling Logging
- From the Menu bar, select Connection > Set Client Log State
- You uniquely identify the STB using the external client ID. This information can found in the Branch SMT
- Select the length of time for the STB to log
- Click “Client Filter”. You can set up your filters based on the type of event as well as the severity of the event
- Click OK twice. Now select the “Start Retrieving Events” icon. The STB will begin logging the events and push them forward to the server
6. To stop logging, select the “
Stop Retrieving Events” icon from the Menu bar.
7. If you wish to save the events for future viewing, click the
Save button from the Menu bar
Viewing Events
- If you saved the events as per Step 7 above, they can be viewed as a text file. Otherwise you can use the CTL Viewer to review the events captured
- Select Events > Retrieve Events
- Ensure the information in the Connect dialog box is correct and select OK
- If you wish to further filter the information, choose View > Options
- Select the Filters tab, filter based upon your needs
- In the CTL Viewer, all information in the left pane represents Web Service calls and TV2 events. The right pane is for logging message. If you select an individual message, the details will be presented Details pane in the bottom third of the viewer
Hopefully this overview gives you at least a basic understanding of the Client Trace Log Viewer and its usage. In the following months we’ll continue to investigate more troubleshooting tools and how they relate to Mediaroom. If you wish to learn more about the Mediaroom platform, please visit
http://www.microsoft.com/Mediaroom/
Thansk to
Warren Johns from http://www.opsvault.com/mediaroom-troubleshooting-tools-client-trace-log-viewer/
