Testing A Specific Transaction; Enabling Debug Operations - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Administrator's Guide
Connecting to 172.16.254.2:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 165 [text/plain]
Saving to: `newtest'
100%[=======================================>] 165
16:17:55 (13.1 MB/s) - `newtest' saved [165/165]
[joe@sv05 joe]$
test-vos-cl11 (config) # show counters
Total number of Active Connections
Total Bytes served from RAM cache
Total Bytes served from Origin Server : 0 Bytes
Total Bytes served from Disk cache
Total Bytes served
Total number of HTTP Connections
Total number of HTTP Transactions
Total number of HTTP 200 responses
Total HTTP Well finished count

Testing a Specific Transaction

If a specific video is having delivery problems, you can use the trace log facility to debug. This
involves setting the delivery trace:
delivery protocol http trace enable
And using WGET (or other tool, cURL, and so forth) to request the problem video with this
header added:
X-NKN-Trace
The Media Flow Controller HTTP modules then set the flag "HRF_TRACE_REQUEST" as well
as other flags that direct each relevant module to log meaningful trace points. To see the trace
points and for additional information, see

Enabling Debug Operations

Media Flow Controller provides a system-level debugging utility as well as a trace facility; see
"Trace Log (tracelog)" on page 223
Important!
commands should be turned on only for troubleshooting specific problems or during
troubleshooting sessions with technical support personnel. Excessive debugging output can
render the system inoperable.
1. Generate debugging information for all system functions.
debug generate dump
2. View a list of debug-dump files.
show files debug-dump
3. View a summary of a specific debug-dump.
show files debug-dump <filename_of_debug_dump>
Total Bytes served from HTTP Origin Server : 0 Bytes
Total Bytes served from NFS Origin Server : 165 Bytes
The system gives high priority to debugging output. For this reason, debugging
: 0
: 0 Bytes
: 165 Bytes
: 495 Bytes
: 3
: 3
: 3
: 3
"Trace Log (tracelog)" on page
for details.
Media Flow Controller Troubleshooting
--.-K/s
223.
Enabling Debug Operations
in 0s
281

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents