Solutions

Configuring a protocol to use a specific log facility

Solutions ID:    KB1457
Version:    2.0
Status:    Published
Published date:    03/02/2009
Updated:    04/22/2009
 

Problem Description

Configuring a protocol to use a specific log facility
You want to configure a protocol to use a specific log facility

Resolution

The following list shows the protocols supported and the default log facilities assigned to them, if any:

  • Endpoint Mapper: main
  • FTP: main
  • HTTP: main
  • HTTPS-Reverse-Proxy: main (Set to the same log facility that HTTP is using upon upgrade.)
  • HTTPS-Forward-Proxy: ssl (If the facility for HTTP, TCP, or SOCKS is set before upgrade.)
  • ICP: none
  • Instant Messaging: im
  • Peer to Peer: p2p
  • Real Media/QuickTime: streaming
  • SOCKS: none
  • SSL: ssl (If the facility for HTTP, TCP or SOCKS is set before upgrade.)
  • TCP Tunnel: main
  • Telnet: main
  • Windows Media: streaming

To associate a log facility with a protocol from the Management Console go to Configuration > Access Logging > General > Default Logging.

To associate a log facility with a protocol from the CLI, use the following commands:
SGOS#(config) access-log
SGOS#(config access-log) default-logging {epmapper | ftp | http | https-forward-proxy | https-reverse-proxy | icp | im | mms | p2p | rtsp | socks | ssl | tcp-tunnel | telnet}


Rate this Page

Please take a moment to complete this form to help us better serve you.

Did this document help answer your question?
 
 
If you are finished providing feedback, please click the RATE CONTENT button. Otherwise, please add more detail in the following text box and then click RATE CONTENT.
 
 

Your response will be used to improve our document content.

Ask a Question