-
Cisco SN 5400 Series Storage Router Command Reference, Release 3.4
-
About This Guide
-
Chapter 1 - CLI Overview
-
Chapter 2 - A Commands
-
Chapter 3 - C Commands
-
Chapter 4 - D Commands
-
Chapter 5 - E Commands
-
Chapter 6 - F Commands
-
Chapter 7 - H Commands
-
Chapter 8 - I Commands
-
Chapter 9 - L Commands
-
Chapter 10 - M Commands
-
Chapter 11 - N Commands
-
Chapter 12 - P Commands
-
Chapter 13 - R Commands
-
Chapter 14 - S Commands
-
Chapter 15 - Show Commands
-
Chapter 16 - T Commands
-
Chapter 17 - U Commands
-
Chapter 18 - V Commands
-
Chapter 19 - Z Commands
-
Table Of Contents
L Commands
This chapter covers the following commands:
logging #?
To insert a routing rules entry into the logging table before the specified entry, use the logging #? command.
logging #?
logging #nn level notification-level from facility-name to destination1 [destination2...]
Syntax Description
#?
Request an indexed list of entries in the logging table.
#nn
The index number from the displayed list of entries. The new routing rule will be inserted before the specified logging table entry.
notification-level
Limit logging to messages of a specified level or lower levels. See Table 9-1 in the Usage Guidelines section for a list of valid names that can be used for the notification-level argument.
from facility-name
The name of the facility. A facility is the feature area from which the message is received. See Table 9-2 in the Usage Guidelines section for a list of valid facility names. Each facility can have eight notification levels. Each notification level can have up to seven destination.
to destination1 [destination2...]
At least one of the destinations described in Table 9-3.
Defaults
None.
Command Modes
Administrator.
Command History
2.3.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced.
Usage Guidelines
Event, trace and debug messages can be routed to various destinations, based on the notification level of the message and the application area (facility) that generated the message. When a log message is received by the storage router, the logging table rules are searched by facility name and by message level until a match is found. The log message is sent to all the destinations specified by the matching rule.
New routing rules are normally appended to the existing rules in the table. Use this command to insert a routing rule at a specific location within the table.
To display an indexed lists of entries in the logging table, use the number sign (#) character followed by a question mark (?). That action will cause the routing rules in the logging table to be displayed as a numbered (indexed) set of lines. The command is displayed at the prompt below the list to the point of the # keyword. Complete the command by entering the appropriate index number and the desired keywords and variables to compose the new routing rule. The new routing rule will be added to the table before the specified entry.
The level limits logging to messages of the specified notification level or lower levels, based on level number. Table 9-1 describes the available logging levels.
Note
The debug notification level should be used for specific troubleshooting purposes only. System performance and HA behavior may be adversely affected by logging at the debug notification level.
Each facility can have up to eight notification levels. Each facility and notification level pair can have up to seven destinations. Table 9-2 describes the available facility names.
Table 9-3 describes the available logging destinations.
Use the save system bootconfig or save all bootconfig commands to save the list of log route entries. To delete a log route entry by its index number, use the delete logging command.
Examples
The following example displays an indexed list of the routing rules in the logging table, and then inserts an entry to log anything from the HA facility with notification level of notice (or lower) to all logging destinations before the third entry. The show logging command displays the newly inserted entry.
[SN5428-2A]# logging #?[SN5428-2A]# logging #?Index Level Priority Facility Route1 critical 2 all console vty logfile2 debug 7 SNMP rslog3 warning 4 CDP rslog[SN5428-2A]# logging #3 level notice from HA to all[SN5428-2A]# show loggingLogging is enabledIndex Level Priority Facility Route1 critical 2 all console vty logfile2 debug 7 SNMP rslog3 notice 5 HA all4 warning 4 CDP rslogSyslog host is enabled, ip-address is 10.1.1.144Related Commands
logging level
To add a routing rule to the logging table, use the logging level command.
logging level notification-level from facility-name to destination1 [destination2...]
Syntax Description
notification-level
Limit logging to messages of a specified level or lower levels. See Table 9-4 in the Usage Guidelines section for a list of valid names that can be used for the notification-level argument.
from facility-name
The name of the facility. A facility is the feature area from which the message is received. See Table 9-5 in the Usage Guidelines section for a list of valid facility names. Each facility can have eight notification levels. Each notification level can have up to seven destination.
to destination1 [destination2...]
At least one of the destinations described in Table 9-6.
Defaults
The factory default logging rules are as follows:
•
•
•
Command Modes
Administrator.
Command History
2.3.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Event, trace and debug messages can be routed to various destinations, based on the notification level of the message and the application area (facility) that generated the message. When a log message is received by the storage router, the logging table rules are searched by facility name and by notification level until a match is found. The log message is sent to all the destinations specified by the matching rule. When a new routing rule is added, it is appended to the existing list of entries.
Messages are sent in the following format:
<timestamp>: %<facility>-<level_number>-<mnemonic>: <message text>The following is an example log message, for the SNMP facility:
Mar 18 11:48:05: %SNMP-5-SASAS: SnmpApp starting...Each facility can have up to eight notification levels. The notification level limits logging to messages of the specified level or lower levels, based on level number. Table 9-4 describes the available logging levels.
Each facility and notification level pair can have up to seven destinations. Table 9-5 describes the available facility names.
Note
Table 9-6 describes the available logging destinations.
Use the save system bootconfig or save all bootconfig commands to save the logging table
To delete a routing rule from the logging table, use the delete logging command.
Note
Examples
The following example logs anything from the HA facility with notification level of notice (or lower) to all logging destinations.
[SN5428-2A]# logging level notice from HA to allThe following example logs messages from all facilities with a notification level of warning or lower to all destinations. (If this is the only rule in the logging table, any message with a notification level of debug, info or notice is discarded and not logged.) The log route entries are saved to the bootable configuration of the storage router.
[SN5428-2A]# logging level warning from all to all[SN5428-2A]# save system bootconfigRelated Commands
logging on
To enable logging of storage router event messages based on the rules in the logging table, use the logging on command. To temporarily disable logging of all event messages, use the no form of this command.
logging on
no logging on
Syntax Description
This command has no arguments or keywords.
Defaults
Logging is enabled by default. The factory default logging rules are as follows:
•
•
•
Command Modes
Administrator.
Command History
2.3.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
Use the no form of this command to quickly disable logging of all messages. For example, if there is an error condition that is overwhelming the console with messages, enter no logging on to temporarily disable logging without changing the logging table. Use the logging on command to re-enable logging when the problem is resolved.
Examples
The following example temporarily disables logging of all event messages:
[SN5428-2A]# no logging onRelated Commands
logging syslog
To identify a remote syslog host to be used to log storage router event messages, use the logging syslog command. Use the no form of this command to disable remote logging.
logging syslog A.B.C.D
no logging syslog
Syntax Description
Defaults
Remote logging is disabled by default.
Command Modes
Administrator.
Command History
2.3.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
This command identifies a remote syslog host to receive storage router event messages.
•
•
•
•
Examples
The following example identifies the IP address of the remote syslog host as 10.1.1.144 and adds a entry to the logging table to route all emergency level messages to that remote host.
[SN5428-2A]# logging syslog 10.1.1.144[SN5428-2A]# logging level emergency from all to rslogRelated Commands
logout
To terminate the current CLI management session, use the logout command.
logout
Syntax Description
This command has no arguments or keywords.
Defaults
None.
Command Modes
Administrator or Monitor.
Command History
2.2.1
This command was introduced for the SN 5428.
3.2.1
This command was introduced for the SN 5428-2.
Usage Guidelines
•
•
•
Related Commands
