
FMSAccess Log (fmsaccesslog)
217
Media Flow Controller Administrator’s Guide
Configuring and Using Media Flow Controller Logs and Alarms
errorlog
copy <SCP>
filename <name>
level {1 | 2 | 3 | 4 | 5-7}
module <module>
on-the-hour {disable | enable}
rotate {filesize-MB <integer> | time-interval <integer>}
syslog replicate {disable | enable}
Viewing the Errorlog
To view the Media Flow Controller errorlog:
•
Web interface—Media Flow Controller errorlog entries are available for viewing on the
Web interface Logs > Error Logs page.
•
CLI—To upload an errorlog, run upload errorlog scp://<URL>. Now you can access the
errorlog at the specified system, move it (if needed) and view its contents. See
“Terminology” on page 30
for the scp URL format and requirements.
FMSAccess Log (fmsaccesslog)
FMSAccess Log lists all FMS server command executions. Streaming fmsaccesslog events
include play, pause, seek, and stop events; session fmsaccesslog events include connect,
disconnect, and connect-pending events, by default. This log is generated by the FMS server
(must be installed, see
“Installing and Using FMS in Media Flow Controller (CLI)” on page 97
).
This log is written to /nkn/adobe/fms/logs/access.<nn>.log, by default (you can access this
using application fms shell). See
fmsaccesslog
for CLI details. See
“Configuring Media
Flow Controller Service Logs (CLI)” on page 226
for implementation details. See also
“Log
Codes and Sub-Codes” on page 210
.
fmsaccesslog
copy <SCP>
filename <filename>
on-the-hour {disable | enable}
rotate {filesize-MB <integer> | time-interval <integer>}
syslog
The FMSAccess log provides this information:
•
accesslog events—Play, pause, seek, stop, connect, disconnect, connect-pending
•
accesslog category—Session, stream, server, vhost, application, authorization
•
date—Date when the event occurred
•
time—Time when the event occurred
•
x-pid—Server process ID
•
c-ip—Client IP address
•
cs-bytes—The number of bytes transferred from the client to the server
•
sc-bytes—The number of bytes transferred from the server to the client
Содержание MEDIA FLOW CONTROLLER 2.0.4 -
Страница 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Страница 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Страница 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Страница 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Страница 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Страница 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...