set logging application

Use this command to set the severity level of log messages and the server(s) to which messages will be sent for one or all applications.

Syntax

set logging application {[mnemonic | all]} [level level] [servers servers]

Parameters

mnemonic Specifies a case sensitive mnemonic abbreviation of an application to be logged. This parameter will vary depending on the number and types of applications running on your system. To display a complete list, use the show logging application command as described in show logging application. Sample values and their corresponding applications are listed in Sample Mnemonic Values for Logging Applications.
all Sets the logging severity level for all applications.
level level (Optional) Specifies the severity level at which the server will log messages for applications. Valid values and corresponding levels are:
  1. emergencies (system is unusable)
  2. alerts (immediate action required)
  3. critical conditions
  4. error conditions
  5. warning conditions
  6. notifications (significant conditions)
  7. informational messages
  8. debugging messages
servers servers (Optional) Specifies the index number(s) of the Syslog server(s) to which messages will be sent. Valid values are 1 - 8 and are set using the command set logging server.

Defaults

  • If level is not specified, none will be applied.
  • If server is not specified, messages will be sent to all Syslog servers.

Mode

All command modes.

Usage

The security application must be set to a level of 7 and logged to the security file (sfile). See below for an example security application CLI input.

If C2 security mode is enabled, You can not create, modify, or clear a logging application configuration while in Read-Write user mode.

Use set logging local to enable logging to the console, standard logging file, or security logging file.

Mnemonic values are case sensitive and must be typed as they appear in Sample Mnemonic Values for Logging Applications.

Click to expand in new window

Sample Mnemonic Values for Logging Applications

Mnemonic Application
AAA Authentication, Authorization, & Accounting
AddrNtfy Address Add and Move Notification
BGP Border Gateway Protocol
CDP Enterasys Discovery Protocol
CiscoDP Cisco Discovery Protocol
CLI Command Line Interface
DbgIpPkt Debug IP Packet
DVMRP Distance Vector Multicast Routing Protocol
FlowLimit Flow Limiting
HostDos Host DoS
IPmcast IP Multicast
IPsec Internet Protocol Security
LACP Link Aggregation Control Protocol
LinkFlap Link Flap
Linktrap Link SNMP Trap
LLDP Link Layer Discovery Protocol
OAM Ethernet Operations, Administration, and Maintenance
OSPF Open Shortest Path First Routing Protocol
PIM Protocol Independent Multicast
RMON Remote Monitoring
Router Router
RtrAcl Router Access Control List
RtrArpProc Router Arp Process
RtrFE Router Forwarding Engine
RtrLSNat Router Load Sharing Network Address Translation
RtrMcast Router Multicast
RtrNat Router Network Address Translation
RtrTwcb Router Transparent Web Cache Balancing
Security Security
SNMP Simple Network Management Protocol
Spantree Spanning Tree Protocol
Spoof CheckSpoof
System Non-Application items such as general blade/chassis/configurations, etc.
Trace Router Tracing
Trackobj Track Object Manager
UPN User Personalized Networking
VRRP Virtual Router Redundancy Protocol
Webview Webview Device Management

Examples

This example shows how to set the severity level for SSH (Secure Shell) to 4 so that error conditions will be logged for that application and sent to Syslog server 1:

System(rw)->set logging application SSH level 4 server 1

This example shows how to set the security application to send security logging with a severity level of 7 to server 1, the console, and the security logging file:

System(rw)->set logging application security servers 1,console,sfile level 7