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
Related Documentation
Configuring System Logging (SRC CLI)
Use the following statements to configure the SRC software to send log messages to the system logging facility:
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. See Categories and Severity Levels for Event Messages.
To configure component logging to the system log server:
- From configuration mode, access the configuration statement
that configures the logging destination for the component. For example:[edit]user@host# component-hierarchy logger name syslog
For example:
[edit]user@host# edit shared sae configuration logger sae-sys-1 syslog [edit]user@host# edit snmp agent logger snmp-sys-1 syslog [edit]user@host# edit slot 0 jps logger jps-sys-1 syslog - (Optional) Specify the filter to define which event messages
the software logs or disregards. [edit shared sae configuration logger sae-sys-1 syslog] user@host# set filter filter
Filters can specify the logging level, such as debug, or can specify expressions.
- (Optional) Change the IP address or name of a host that
collects event messages by means of a standard system logging daemon. [edit shared sae configuration logger sae-sys-1 syslog] user@host# set host host
By default, the host is loghost for the system log server on the local host. (Configuration in the /etc/hosts file sets loghost to localhost.)
Make sure that the user under which the J2EE application server or Web application server runs has write access to this folder. If this user does not have write access to the default folder, configure the component or application to write logs in folders to which the user has write access.
- (Optional) Specify the type of system log in accordance
with the system logging protocol, a value of 0–23. [edit shared sae configuration logger sae-sys-1 syslog] user@host# set facility facility
- (Optional) Specify the Message Format string that indicates
how the information in an event message is printed. [edit shared sae configuration logger sae-sys-1 syslog] user@host# set format format
Specify a Message Format string as defined in
http://docs.oracle.com/javase/1.5.0/docs/api/java/text/MessageFormat.html
The fields available for events are:
- 0—Time and date of the event
- 1—Name of the thread generating the event
- 2—Text message of the event
- 3—Category of the event
- 4—Priority of the event
- (Optional) Specify the port used for system logging, a
value of 0–65535. [edit shared sae configuration logger sae-sys-1 syslog] user@host# set port port
Related Documentation
- Configuring an SRC Component to Store Log Messages in a File (SRC CLI)
- Saving System Log Messages to a File (SRC CLI)
- Configuration Statements for SRC Component Logging
- Before You Configure Logging for SRC Components
- Logging for SRC Components Overview
