Cisco Nexus 5000 Series NX-OS Software Configuration Guide

Step 1

switch# configure terminal

Enters configuration mode.

Step 2

switch(config)# logging console [ severity-level ]

Enables the switch to log messages to the console session based on a specified severity level or higher. Severity levels, which can range from 0 to 7, are listed in Table 1-1 . If the severity level is not specified, the default of 2 is used.

switch(config)# no logging console [ severity-level ]

Disables the switch’s ability to log messages to the console.

Step 3

switch(config)# show logging console

(Optional) Displays the console logging configuration.

Step 4

switch(config)# logging monitor [ severity-level ]

Enables the switch to log messages to the monitor based on a specified severity level or higher. The configuration applies to Telnet and SSH sessions. Severity levels, which can range from 0 to 7, are listed in Table 1-1 . If the severity level is not specified, the default of 2 is used.

switch(config)# no logging monitor [ severity-level ]

Disables logging messages to telnet and SSH sessions.

Step 5

switch(config)# show logging monitor

(Optional) Displays the monitor logging configuration.

Step 6

switch(config)# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Step 1

switch# configure terminal

Enters configuration mode.

Step 2

switch(config)# logging logfile logfile-name severity-level [ size bytes ]

Configures the name of the log file used to store system messages and the minimum severity level to log. You can optionally specify a maximum file size. The default severity level is 5 and the file size is 10485760. Severity levels are listed in Table 1-1 . The file size is from 4096 to 10485760 bytes.

switch(config)# no logging logfile [ logfile-name severity-level [ size bytes ]]

Disables logging to the log file.

Step 3

switch(config)# show logging info

(Optional) Displays the logging configuration.

Step 4

switch(config)# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Step 1

switch# configure terminal

Enters configuration mode.

Step 2

switch(config)# logging module [ severity-level ]

Enables module log messages that have the specified severity level or higher. Severity levels, which range from 0 to 7, are listed in Table 1-1 . If the severity level is not specified, the default of 5 is used.

switch(config)# no logging module [ severity-level ]

Disables module log messages.

Step 3

switch(config)# show logging module

(Optional) Displays the module logging configuration.

Step 4

switch(config)# logging level facility severity-level

Enables logging messages from the specified facility that have the specified severity level or higher. Severity levels, which range from 0 to 7, are listed in Table 1-1 . To apply the same severity level to all facilities, use the all facility. For defaults, see the show logging level command.

switch(config)# no logging level [ facility severity-level ]

Resets the logging severity level for the specified facility to its default level. If you do not specify a facility and severity level, the switch resets all facilities to their default levels.

Step 5

switch(config)# show logging level [ facility ]

(Optional) Displays the logging level configuration and the system default level by facility. If you do not specify a facility, the switch displays levels for all facilities.

Step 6

switch(config)# logging timestamp { microseconds | milliseconds | seconds }

Sets the logging time-stamp units. By default, the units are seconds.

switch(config)# no logging timestamp { microseconds | milliseconds | seconds }

Resets the logging time-stamp units to the default of seconds.

Step 7

switch(config)# show logging timestamp

(Optional) Displays the logging time-stamp units configured.

Step 8

switch(config)# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Facility

Creator of the message, which can be auth, authpriv, cron, daemon, kern, lpr, mail, mark, news, syslog, user, local0 through local7, or an asterisk (*) for all. These facility designators allow you to control the destination of messages based on their origin.

Note Check your configuration before using a local facility.

Level

Minimum severity level at which messages are logged, which can be debug, info, notice, warning, err, crit, alert, emerg, or an asterisk (*) for all. You can use none to disable a facility.

Action

Destination for messages, which can be a filename, a host name preceded by the at sign (@), or a comma-separated list of users or an asterisk (*) for all logged-in users.

Step 1

switch# configure terminal

Enters configuration mode.

Step 2

switch(config)# logging server host [ severity-level [ facility ]]

Configures a syslog server at the specified host name or IPv4 or IPv6 address. You can limit logging of messages with a minimum severity level and for a specific facility. Severity levels, which range from 0 to 7, are listed in Table 1-1 . The default outgoing facility is local7.

switch(config)# no logging server host

Removes the logging server for the specified host.

Step 3

Repeat Step 2 for up to three syslog servers.

Step 4

switch(config)# show logging server

(Optional) Displays the syslog server configuration.

Step 5

switch(config)# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Step 1

switch# configure terminal

Enters configuration mode.

Step 2

switch(config)# logging distribute

Enables distribution of syslog server configuration to network switches using the CFS infrastructure. By default, distribution is disabled.

switch(config)# no logging distribute

Disables distribution of syslog server configuration to network switches using the CFS infrastructure. You cannot disable distribution when configuration changes are pending. See the logging commit and logging abort commands. By default, distribution is disabled.

Step 3

Enter syslog server configuration commands.

See the “Configuring syslog Servers” section.

Step 4

switch(config)# show logging pending

(Optional) Displays the pending changes to the syslog server configuration.

Step 5

switch(config)# show logging pending-diff

(Optional) Displays the differences from the current syslog server configuration to the pending changes of the syslog server configuration.

Step 6

switch(config)# logging commit

Commits the pending changes to the syslog server configuration for distribution to the switches in the fabric.

switch(config)# logging abort

Cancels the pending changes to the syslog server configuration.

Step 7

switch(config)# show logging internal info

(Optional) Displays information about the current state of syslog server distribution and the last action taken.

Step 8

switch(config)# copy running-config startup-config

(Optional) Copies the running configuration to the startup configuration.

Step 1

switch# show logging last number-lines

Displays the last number of lines in the logging file. You can specify from 1 to 9999 for the last number of lines.

Step 2

switch# show logging logfile [ start-time yyyy mmm dd hh:mm:ss ] [ end-time yyyy mmm dd hh:mm:ss ]

Displays the messages in the log file that have a time stamp within the span entered. If you do not enter an end time, the current time is used. You enter three characters for the month time field, and digits for the year and day time fields.

Step 3

switch# show logging nvram [ last number-lines ]

Displays the messages in the NVRAM. To limit the number of lines displayed, you can enter the last number of lines to display. You can specify from 1 to 100 for the last number of lines.

Step 4

switch# clear logging logfile

Clears the contents of the log file.

Step 5

switch# clear logging nvram

Clears the logged messages in NVRAM.