Specifications
7-35
Cisco Internet Streamer CDS 2.0-2.3 Software Configuration Guide
OL-13493-04
Chapter 7 Monitoring the Internet Streamer CDS
Transaction Logs
• Path of the directory where transferred files are written
Use a fully qualified path or a relative path for the user login. The user must have write permission
to the directory.
You can also compress archived log files into gzip format before exporting them to external FTP servers.
The compressed filename has a .gz extension. This compression feature uses less disk space than that
required for noncompressed archived files on both the SE and the FTP export server and also requires
less bandwidth during export because of the smaller size of the files to be exported.
Restarting Export After Receiving a Permanent Error from the External FTP Server
When an FTP server returns a permanent error to the SE, the archive transaction logs are no longer
exported to that server. You must re-enter the SE transaction log export parameters for the misconfigured
server to clear the error condition.
A permanent error (Permanent Negative Completion Reply, RFC 959) occurs when the FTP command
to the server cannot be accepted, and the action does not take place. Permanent errors can be caused by
invalid user logins, invalid user passwords, and attempts to access directories with insufficient
permissions or directories that do not exist.
Exporting Transaction Logs to External SFTP Servers
You can also export transaction logs to a Secure File Transfer Protocol (SFTP) server. You must first
enable the feature and configure the SFTP server parameters. The following information is required for
each target SFTP server:
• SFTP server IP address or the hostname
The SE translates the hostname with a DNS lookup and then stores the IP address in the
configuration.
• SFTP user login and user password
• Path of the directory where transferred files are written
Use a fully qualified path or a relative path for the user login. The user must have write permission
to the directory.
To enable this feature, enter the sshd allow-non-admin-users command on the SE. If this feature is
enabled, the output of the show running-config EXEC command shows that this feature is enabled on
the SE.
Windows Media Transaction Logging
The following logging formats are supported for Windows Media transaction logging:
• Standard Windows Media Services Version 4.1
• Extended Windows Media Services Version 4.1
• Standard Windows Media Services Version 9.0
• Extended Windows Media Services Version 9.0
The extended versions of the logging formats contain additional fields that are SE specific (For example,
the SE-action field specifies a cache hit or miss, and the SE-bytes field specifies the number of bytes that
were sent from the SE.)