Navigation
Back up to About Overview
[+] Expand All
[-] Collapse All
A
- access lines 1
- accesses
- configuring subscriptions
- accounting
- anonymous subscriber
- attributes
- authenticated subscriber
- authentication plug-ins
- authorization plug-ins
B
C
- captive portal
- classification scripts
- conditions 1
- configuring
- descriptions
- DHCP classification, C Series Controller
- interface classification, C Series Controller
- structure
- subscriber classification, C Series Controller
- target, C Series Controller
- component interactions
- conventions
- COPS (Common Open Policy Service)
- custom RADIUS accounting plug-ins 1
- configuring
- custom RADIUS authentication plug-ins 1
- configuring
- customer support 1
D
- default retailer authentication plug-ins
- configuring
- default retailer DHCP authentication plug-ins
- configuring
- denial-of-service attacks
- DHCP (Dynamic Host Configuration Protocol)
- address assignment
- classification scripts. See classification scripts
- options
- profiles
- subscribers
- documentation
E
- enterprise
- enterprise subscribers 1
- adding
- enterprise subscribers, login process
- event publishers
- configuring
- default retailer authentication, configuring
- default retailer DHCP authentication, configuring
- description
- retailer-specific
- service-specific
- virtual router-specific
- external plug-ins
- configuring
F
- file upload settings for log rotation
- configuring
- flat file accounting plug-ins 1
- flexible RADIUS accounting plug-ins 1
- attributes, defining
- configuring
- RADIUS packets, defining
- flexible RADIUS authentication plug-ins 1
- attributes, defining
- configuring
- RADIUS packets, defining
- setting responses
- FTP server for log rotation
G
- general properties
- configuring
H
- HTTP proxy 1, 2
- HTTPS traffic
I
- interface classification scripts. See classification scripts
- interim accounting, configuring on SAE
- internal plug-ins
- configuring
L
- LDAP authentication plug-in 1
- configuring
- limiting subscribers plug-in 1
- configuring
- log rotation
- overview
- logging
- login events, description
- login process
- login registration
- configuring
- logout process, residential
M
- managers
- manuals
N
- NAT (Network Address Translation)
- notice icons
P
- plug-ins
- activating service sessions
- authentication
- authorization
- basic RADIUS accounting 1
- basic RADIUS authentication 1
- creating subscriber sessions
- custom RADIUS accounting 1
- custom RADIUS authentication 1
- defining RADIUS packets
- DHCP address assignment
- event publishers. See event publishers
- external
- flat file accounting 1
- flexible RADIUS accounting 1
- flexible RADIUS authentication 1
- internal 1
- LDAP authentication 1
- limiting subscribers 1
- state synchronization
- tracking
- policy groups
- policy management
- PPP subscribers
- prevention, use of unauthorized resources
- protocols
- proxy HTTP 1, 2
- proxy request management
- public addresses, VPNs
Q
R
- RADIUS accounting
- RADIUS attributes
- defining in RADIUS plug-ins
- examples, defining in RADIUS plug-ins
- RADIUS client library, custom RADIUS plug-ins
- RADIUS packets, customizing in plug-ins
- RADIUS peers
- configuring in plug-ins
- RADIUS plug-ins 1, See also plug-ins
- redirect server
- assessing load
- configuration statements
- configuring
- configuring DNS server for
- configuring HTTP proxy support
- configuring redundant
- directory connection
- failover
- file extensions
- logging
- number of requests
- protection against denial-of-service attacks
- redundancy 1, 2, 3
- static route to router
- traffic definition
- verifying
- redundancy
- residential subscribers 1
- adding
- login process. See login process
- retailers
- subscribers 1
- router subscribers 1
- adding
- routing instances
- routing scheme
S
- SAE (service activation engine)
- classification scripts. See classification scripts
- login events
- login process. See login process
- SAE (service activation engine), configuring
- service activation engine. See SAE
- service sessions
- sites 1, 2, 3
- subscriber 1
- state synchronization plug-in interface
- configuring
- static IP subscribers, login process
- static routing
- subscriber classification scripts. See classification scripts
- subscriber folders 1
- adding
- subscriber sessions
- subscribers
- 3gpp attributes (Gx router driver)
- adding
- enterprise 1
- inheriting properties
- inheriting subscriptions
- residential 1
- retailer 1
- router 1
- sessions
- sites 1
- types
- subscriptions 1
- access, configuring
- an orderly deactivation, activation order, specifying
- configuring
- multiple per subscriber
- support, technical See technical support
T
- targets. See classification scripts
- technical support
- text conventions defined
- tracking plug-ins 1
- configuring
U
- UDP ports
- User Datagram Protocol. See UDP
V
- validating
- virtual private networks. See VPNs
- VPNs (virtual private networks)
- adding
- configuration requirements
- configuration statements
- extranet clients, modifying
- invalid subscriptions
- modifying
- routing schemes
- using NAT
- validating
Download This Guide
Configuring Log Rotation (SRC CLI)
To configure log rotation, you need to configure the FTP server where files are uploaded and stored, and configure the SRC upload client.
You perform the following tasks to configure log rotation:
- Configuring the FTP Server for Log Rotation (SRC CLI)
- Configuring the Upload Client for Log Rotation (SRC CLI)
Configuring the FTP Server for Log Rotation (SRC CLI)
This procedure is optional. You are not required to configure a remote FTP server. If you do not configure a server, the SRC file upload client simply deletes the older files and compresses and stores the specified n number of the most recent files in the backup directory.
 | Note: The SRC software uses passive mode on the outgoing connections to the FTP server. The FTP server must support passive mode. |
Use the following configuration statements to configure the FTP server used for log file rotation:
system file-uploading-specifications name ftp {server server;user-name user-name;password password;port port;destination-path destination-path;}
To configure the FTP server information for log file rotation:
- (Optional) From configuration mode, access the configuration
statement used to configure the FTP server. In this sample procedure,
the upload client is named acct_file and the server is named kimberly.[edit]user@host# edit system file-uploading-specifications acct_file ftp
- Specify the FTP server to connect to for file uploading. [edit system file-uploading-specifications acct_file ftp]user@host# set server kimberly
- (Optional) Specify the username to log in to the FTP server.[edit system file-uploading-specifications acct_file ftp]user@host# set user-name user-name
- (Optional) Specify the password to log in to the FTP server.[edit system file-uploading-specifications acct_file ftp]user@host# set password password
- (Optional) Configure the port number for the FTP server.[edit system file-uploading-specifications acct_file ftp]user@host# set port port
- Specify the directory on the remote server where you want
to store the uploaded files.[edit system file-uploading-specifications acct_file ftp]user@host# set destination-path destination-path
- Verify the configuration for the remote FTP server.
[edit system file-uploading-specifications acct_file ftp] user@host# show destination-path /accounting/logs; password ********; port 1220; server kimberly; user-name jsmith;
Configuring the Upload Client for Log Rotation (SRC CLI)
Use the following configuration statements to configure the file upload client:
system file-uploading-specifications name {file-search-pattern [file-search-pattern...];random-delay random-delay;retry-time retry-time;interval (1 | 2 | 3 | 4 | 6 | 8 | 12 | 24);start-time start-time;keep keep;append (time-stamp | host-name | time-stamp-and-host-name);}
To configure the file upload client for log rotation:
- From configuration mode, access the configuration statement
for configuring the file upload client for log rotation. You can configure
multiple uploads. Each upload client must have a unique name. In this
sample procedure, the upload client is named “acct_file.”[edit]user@host# edit system file-uploading-specifications name
For example, to configure an upload named acct_file:
[edit]user@host# edit system file-uploading-specifications acct_file - Specify the directory path and filename pattern you want
to upload from the C Series Controller disk to the remote server.
After the file upload is successfully completed, the files are deleted
from the local disk.[edit system file-uploading-specifications acct_file]user@host# set file-search-pattern file-search-pattern
For example, to upload all accounting files located in the /opt/UMC/sae/var/acct directory, that begin with “log”:
[edit system file-uploading-specifications acct_file]user@host# set file-search-pattern /opt/UMC/sae/var/acct/log* - Configure the delay in seconds to connect to the upload
server; the upload client waits a random time between 1 and this specified
delay to connect to the remote server. [edit system file-uploading-specifications acct_file]user@host# set random-delay random-delay
- (Optional) Configure the retry time interval. If the upload
fails, this is the amount of time in seconds that the upload client
waits before trying the upload again.[edit system file-uploading-specifications acct_file]user@host# set retry-time retry-time
- (Optional) Specify the time interval, in hours, for uploading
files. [edit system file-uploading-specifications acct_file]user@host# set interval (1 | 2 | 3 | 4 | 6 | 8 | 12 | 24)
Note: Uploading large files can consume disk, CPU, and network resources. We recommend scheduling uploads at a specific time of day when use of these resources does not impact users on the network.
- Configure the time to start file uploading in a form of
hh:mm in 24-hour format—for example, “13:40.”[edit system file-uploading-specifications acct_file]user@host# set start-time start-time
- (Optional) Specify the number of the most recent files
you want to keep on the local disk after the files have been successfully
uploaded to the remote server. After successfully being uploaded to
the remote server, this number of files are compressed and moved to
a subdirectory of the current directory.[edit system file-uploading-specifications acct_file]user@host# set keep keep
- (Optional) Append a suffix to the files that are uploaded
to the remote server. If this attribute is not set, nothing is appended
to the filenames that are uploaded to the remote server. [edit system file-uploading-specifications acct_file ftp]user@host# set append (time-stamp | host-name | time-stamp-and-host-name);
Where append is one of the following:
- time-stamp—Append a timestamp in the form of “-YYYYMMDDHHMMSS” to the end of the file.
- host-name—Append the hostname in the form of “-hostname” to the end of the file.
- time-stamp-and-host-name—Append both a timestamp and hostname in the form of “-YYYYMMDDHHMMSS-hostname” to the end of the file.
- Verify the configuration.
[edit system file-uploading-specifications acct_files] user@host# show file-search-pattern '/opt/UMC/sae/var/acct/log*'; ftp { destination-path /accounting/logs; port 1220; ..server kimberly; ..user-name jsmith; } interval 24; keep 3; append time-stamp;
random-delay 3; retry-time 3600; start-time 00:00;
