![Juniper MEDIA FLOW CONTROLLER 2.0.4 - Administrator'S Manual Download Page 219](http://html1.mh-extra.com/html/juniper/media-flow-controller-2-0-4/media-flow-controller-2-0-4_administrators-manual_2032854219.webp)
FMSConnector Log / fuselog
219
Media Flow Controller Administrator’s Guide
Configuring and Using Media Flow Controller Logs and Alarms
fmsedgelog
for CLI details. See
“Configuring Media Flow Controller Service Logs (CLI)” on
page 226
for implementation details.
fmsedgelog
copy <SCP>
filename <filename>
on-the-hour {disable | enable}
rotate {filesize-MB <integer> | time-interval <integer>}
syslog
The FMSEdge log provides this information:
•
Date—Date of the event
•
Time—Time of the event
•
x- pid—Server process ID
•
x-status—The code is category and message ID (i) information and message id. See
Flash Media Server Diagnostic Log Messages
for descriptions of all message ID.
•
x-ctx—Event dependent context information
Example:
2010-05-27 09:57:23 13826 (i)2581173 Host: QA10 IPv4: 127.0.0.1 -
2010-05-27 09:57:23 13826 (i)2631174 Listener started ( _defaultRoot__edge1 ) :
localhost:19350/v4 -
2010-05-27 09:57:23 13826 (i)2581252 Registering core (13829). -
2010-05-27 09:57:24 13826 (i)2631174 Listener started ( _defaultRoot__edge1 ) :
1935/v4 -
2010-05-27 09:57:24 13826 (i)2631174 Listener started ( _defaultRoot__edge1 ) :
8888/v4 -
2010-05-27 09:58:29 13826 (i)2581252 Registering core (14959). -
2010-05-27 10:28:34 13826 (i)2581250 Edge disconnected from core (14959).
Viewing the FMSEdge Log
To view the Media Flow Controller FMSEdge log:
•
Web interface—Media Flow Controller FMSEdge log entries are available for viewing on
the Web interface Logs tab, FMSEdge Log page.
•
CLI—To upload the fmsedgelog, run upload fmsedgelog scp://<URL>. Now you can
access the FMSEdge log at the specified system, move it (if needed) and view its
contents. See
“Terminology” on page 30
for the scp URL format and requirements.
FMSConnector Log / fuselog
The Media Flow Controller FMSConnector Log records RTSP transaction details including
what URIs are accessed and how many bytes are returned by the FUSE module. This log is
generated by Media Flow Controller. See
fuselog
for CLI details. See
“Configuring Media
Flow Controller Service Logs (CLI)” on page 226
for implementation details.
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...