A
C
- C Series Controllers
- boot messages, viewing
- interface information
- monitoring
- system date, viewing
- system information, viewing
- C-Web interface
- conventions
- currently active service sessions
- viewing on SAE
- customer support 1
D
- device drivers
- simulated, configuring 1
- viewing on SAE
- documentation
E
- equipment registration
- viewing on SAE
- event messages. See logging
F
I
- interfaces
- information, viewing
- iptables Linux tool
- monitoring
J
L
- license
- viewing on SAE
- licenses
- logging
- configuration statements
- configuring component
- file folders
- file logging, configuring
- log files
- messages
- categories
- filters 1, 2
- format
- severity levels
- overview
- system log, configuring
- login registration
- viewing on SAE
- logrotate utility
- configuration statements
- configuring
- overview
M
- manuals
- MIBs
- monitoring tools
N
- network devices
- Network Time Protocol. See NTP
- NIC (network information collector)
- agents, viewing
- hosts, viewing
- monitoring
- resolution data, troubleshooting
- resolution data, viewing
- C-Web interface
- SRC CLI 1, 2, 3
- statistics, viewing
- notice icons
- NTP (Network Time Protocol)
- monitoring
- C-Web interface
- SRC CLI 1, 2
- statistics, viewing
P
- policies
- SNMP information, viewing
- viewing on SAE
- portals, testing
R
- RADIUS statistics
- redirect server
- statistics, viewing
- router interfaces
- viewing on SAE
- routing table, viewing
S
- SAE (service activation engine)
- configuration, viewing
- directory blacklist, viewing
- SNMP information, viewing
- SAE (service activation engine), configuring
- simulated router driver
- security certificates
- information, viewing
- server processes
- SNMP information, viewing
- service sessions
- SNMP information, viewing
- services
- viewing on SAE
- simulated router driver, configuring
- simulated subscribers
- SNMP agent
- SNMP alarm
- SNMP chassis alarms
- SNMP events 1, 2
- SNMP monitors
- alarms 1
- Boolean test
- existence test
- threshold test 1, 2
- chassis alarms 1, 2, 3
- events 1, 2
- overview
- security name
- statement hierarchy
- SNMP traps
- alarm state transitions
- configuring 1, 2
- event traps
- notifications
- overview
- performance traps
- SRC CLI, viewing
- SRC components
- activity, monitoring
- information, viewing
- storing log messages
- subscriber session count by managed router
- viewing on SAE
- subscriber sessions
- logging in
- logging out
- SNMP information, viewing
- viewing on SAE 1
- support, technical See technical support
- system logging. See logging
T
- technical support
- testing
- text conventions defined
- threads
- viewing on SAE
- traps. See SNMP traps
- troubleshooting
U
- user permissions, viewing
- users, viewing
Download This Guide
Rotating Log Files
Logrotate is a log file management utility that allows you to manage the large number of log files the SRC software generates. Logrotate is essential for managing the disk space on the C Series Controller.
The following SRC components support the logrotate utility:
- Third-Generation Partnership Project (3GPP) gateway
- 3GPP Gy
- SRC Admission Control Plug-in (ACP)
- Activity Monitor
- SNMP agent
- Web application server
- Command-line interface (CLI)
- Diameter server
- Dynamic Service Activator
- IP Multimedia Subsystem (IMS)
- Juniper Policy Server (JPS)
- License server
- Monitoring Agent application
- Network information collector (NIC)
- Service activation engine (SAE)
- Subscriber information collector (SIC)
- C-Web interface
You can use logrotate to regularly rotate log files by removing the oldest log files from your system and creating new log files. You can rotate files based on size. You can rotate log files daily, weekly, or monthly. Logrotate can also be used to compress log files. Logrotate usually runs automatically through the Cron utility.
When a new log file is opened to replace an older log file that contains content, a number is appended to the name of the older file. For example, sae_debug.log.4 is an older log file than sae_debug.log.1; whereas sae_debug.log is the active log file for SAE.
On C Series Controllers, the software compresses log files and appends the .gz suffix; for example, sae_debug.log.4.gz. Log files are stored in the /opt/UMC/component-name/var/log directory; for example, /opt/UMC/sae/var/log.
You can configure components to send log messages to the system log server on the platform on which the SRC software is running.
If you plan to filter log messages, you should be familiar with severity levels and filters for logging before you configure system logging for a component.
Configuration Overview
You can specify any number of log rotation configuration files on the command line. Configuration options that you specify for a group of log files are considered local options and they override global options of the same name.
Both global and local options can be set in the /etc/logrotate.conf file. You set global options
under the [edit system logrotate logrotate.conf] hierarchy
level. You set local options for specific logging configuration files
such as the /var/log/wtmp file under
the [edit system logrotate logrotate.conf logfiles name] hierarchy level. You can also configure log
rotation for system and SRC components under the [edit system
logrotate file-name logfiles] hierarchy
level.
Related Documentation
- Logging for SRC Components Overview
- Configuring an SRC Component to Store Log Messages in a File (SRC CLI)
- Configuration Statements for the Logrotate Utility (SRC CLI)
- Configuring the Logrotate Utility (SRC CLI)
