The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes the system management commands available on Cisco Nexus 5000 Series switches.
To discard the current configuration session, use the abort command.
abort
This command has no arguments or keywords.
None
Session configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to abort the current configuration session:
switch# configure session MySession1
switch(config-s)# abort
switch#
|
|
---|---|
commit |
Commits a session. |
configure session |
Creates a configuration session. |
show configuration session |
Displays the contents of the session. |
verify |
Verifies a session. |
To clears the contents of the log file, use the clear logging logfile command.
clear logging logfile
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to clear the logging logfile:
switch# clear logging logfile
switch#
|
|
---|---|
show logging logfile |
Displays the messages in the log file. |
To clear the NVRAM logs, use the clear logging nvram command.
clear logging nvram
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to clear the NVRAM logs:
switch# clear logging nvram
|
|
---|---|
show logging nvram |
Displays the NVRAM logs. |
To clear the onboard failure logging (OBFL) entries in the persistent log, use the clear logging onboard command.
clear logging onboard [environmental-history] [exception-log] [obfl-log] [stack-trace]
None
EXEC mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to clear the OBFL environmental history entries:
switch# clear logging onboard environmental-history
This example shows how to clear the OBFL exception-log entries:
switch# clear logging onboard exception-log
This example shows how to clear the OBFL (boot-uptime/device-version/obfl-history) entries:
switch# clear logging onboard obfl-log
This example shows how to clear the OBFL stack trace entries:
switch# clear logging onboard stack-trace
|
|
---|---|
show logging onboard |
Displays onboard failure logs. |
To clear the current logging session, use the clear logging session command.
clear logging session
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to clear the current logging session:
switch# clear logging session
|
|
---|---|
show logging session |
Displays the logging session status. |
To clear the Network Time Protocol (NTP) session, use the clear ntp session command.
clear ntp session
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to discard the NTP Cisco Fabric Services (CFS) distribution session in progress:
switch# clear ntp session
|
|
---|---|
show ntp |
Displays NTP information. |
To clear the Network Time Protocol (NTP) session, use the clear ntp session command.
clear ntp statistics {all-peers | io | local | memory}
all-peers |
Clears all peer transaction statistics. |
io |
Clears I/O statistics. |
local |
Clears local statistics. |
memory |
Clears memory statistics. |
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to discard the NTP I/O statistics:
switch# clear ntp statistics io
|
|
---|---|
show ntp |
Displays NTP information. |
To commit the current configuration session, use the commit command.
commit
This command has no arguments or keywords.
None
Session configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to commit the current session:
switch(config-s)# commit
switch(config-s)#
|
|
---|---|
configure session |
Creates a configuration session. |
show configuration session |
Displays the contents of the session. |
verify |
Verifies a session. |
To configure the bootup diagnostic level to trigger diagnostics when the device boots, use the diagnostic bootup level command. To remove bootup diagnostic level configuration, use the no form of this command.
diagnostic bootup level {bypass | complete}
no diagnostic bootup level {bypass | complete}
bypass |
Specifies that all bootup tests are skipped. |
complete |
Specifies that all bootup diagnostics are performed. This is the default value. |
Complete.
Global configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to configure the bootup diagnostics level to trigger the complete diagnostics:
switch(config)# diagnostic bootup level complete
switch(config)#
This example shows how to remove the bootup diagnostics level configuration:
switch(config)# no diagnostic bootup level complete
switch(config)#
|
|
---|---|
show diagnostic bootup level |
Displays the bootup diagnostics level. |
show diagnostic bootup level |
Displays the results of the diagnostics tests. |
To create an IPv4 access control list (ACL) within a configuration session, use the ip access-list command. To remove an ACL from a configuration session, use the no form of this command.
ip access-list ACL-name
no ip access-list ACL-name
ACL-name |
Name of the IPv4 ACL. The name can be up to 64 alphanumeric characters and cannot contain a space or quotation mark. |
No IPv4 ACLs are defined by default.
Global session configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to create an IPv4 ACL for a configuration session:
switch# configure session MySession1
switch(config-s)# ip access-list myACL
switch(config-s-acl)#
To apply an IPv4 access control list (ACL) to an interface as a port ACL, use the ip port access-group command. To remove an IPv4 ACL from an interface, use the no form of this command.
ip port access-group access-list-name {in | out}
no ip port access-group access-list-name {in | out}
None
Session interface configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to apply an IPv4 ACL named ip-acl-01 to the Ethernet interface 1/2 as a port ACL:
switch# configure session MySession1
switch(config-s)# interface ethernet 1/2
switch(config-s-if)# ip port access-group ip-acl-01 in
switch(config-s-if)#
This example shows how to remove an IPv4 ACL named ip-acl-01 from Ethernet interface 1/2:
switch(config-s)# interface ethernet 1/2
switch(config-s-if)# no ip port access-group ip-acl-01 in
switch(config-s-if)#
|
|
---|---|
show access-lists |
Displays all ACLs. |
show configuration session |
Displays the contents of the session. |
To discard the pending changes to the syslog server configuration, use the logging abort command.
logging abort
This command has no arguments or keywords.
None
Global configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to discard the changes made to the syslog server configuration:
switch(config)# logging distribute
switch(config)# logging abort
switch(config)#
To commit the pending changes to the syslog server configuration for distribution to the switches in the fabric, use the logging commit command.
logging commit
This command has no arguments or keywords.
None
Global configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to commit the distribution of the syslog server configuration:
switch(config)# logging distribute
switch(config)# commit
switch(config)#
|
|
---|---|
logging distribute |
Enables the distribution of the syslog server configuration to network switches using the CFS infrastructure. |
show logging status |
Displays the logging status. |
To enable logging messages to the console session, use the logging console command. To disable logging messages to the console session, use the no form of this command.
logging console [severity-level]
no logging console
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to enable logging messages with a severity level of 4 (warning) or higher to the console session:
switch# configure terminal switch(config)# logging console 4
|
|
---|---|
show logging console |
Displays the console logging configuration. |
To enable the distribution of the syslog server configuration to network switches using the Cisco Fabric Services (CFS) infrastructure, use the logging distribute command. To disable the distribution, use the no form of this command.
logging distribute
no logging distribute
This command has no arguments or keywords.
Distribution is disabled.
Global configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to enable the distribution of the syslog server configuration:
switch(config)# logging distribute
switch(config)#
This example shows how to disable the distribution of the syslog server configuration:
switch(config)# no logging distribute
switch(config)#
To log interface events, use the logging event command. To disable logging of interface events, use the no form of this command.
logging event port {link-status | trunk-status} {default | enable}
no logging event port {link-status | trunk-status} {default | enable}
None
Global configuration mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to log interface events:
switch# configure terminal switch(config)# logging event link-status default
|
|
---|---|
show logging |
Displays the logging status. |
To log events on an interface, use the logging event port command. To disable logging of interface events, use the no form of this command.
logging event port {link-status | trunk-status} [default]
no logging event port {link-status | trunk-status}
None
Interface configuration mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to log interface events:
switch# configure terminal switch(config)# interface ethernet 1/1 switch(config-if)# logging event port link-status default
|
|
---|---|
show interface |
Displays the interface configuration information. |
show logging |
Displays the logging status. |
To enable logging messages from a defined facility that have the specified severity level or higher, use the logging level command. To disable logging messages from a defined facility, use the no form of this command.
logging level facility severity-level
no logging level facility severity-level
facility |
Appropriate facility. The facilities are listed in the "System Message Logging Facilities" section. To apply the same severity level to all facilities, use the all facility. |
severity-level |
Number of the desired severity level at which messages should be logged. Messages at or numerically lower than the specified level are logged. Severity levels are as follows: •0—emergency: System unusable •1—alert: Immediate action needed •2—critical: Critical condition—default level •3—error: Error condition •4—warning: Warning condition •5—notification: Normal but significant condition •6—informational: Informational message only •7—debugging: Appears during debugging only |
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to enable logging messages from the AAA facility that have a severity level of 2 or higher:
switch(config)# logging level aaa 2
|
|
---|---|
show logging level |
Displays the facility logging level configuration. |
To configure the name of the log file used to store system messages and the minimum severity level to log, use the logging logfile command. To disable logging to the log file, use the no form of this command.
logging logfile logfile-name severity-level [size bytes]
no logging logfile [logfile-name severity-level [size bytes]]]
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to configure a log file called logfile to store system messages and set its severity level to 4:
switch(config)# logging logfile logfile 4
|
|
---|---|
show logging logfile |
Displays the log file. |
To enable module log messages, use the logging module command. To disable module log messages, use the no form of this command.
logging module [severity-level]
no logging module
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
Set a specified severity level or use the default.
This example shows how to enable module log messages:
switch(config)# logging module
|
|
---|---|
show logging module |
Displays the module logging status. |
To enable the device to log messages to the monitor (terminal line), use the logging monitor command. To disable monitor log messages, use the no form of this command.
logging monitor [severity-level]
no logging monitor
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This configuration applies to Telnet and Secure Shell (SSH) sessions.
This example shows how to enable monitor log messages:
switch(config)# logging monitor
|
|
---|---|
show logging monitor |
Displays the status of monitor logging. |
To configure a remote syslog server at the specified hostname or IPv4/IPv6 address, use the logging server command. To disable the remote syslog server, use the no form of this command.
logging server host [severity-level] [facility {auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp}| use-vrf {vrf_name | management}]
no logging server host [severity-level] [facility {auth | authpriv | cron | daemon | ftp | kernel | local0 | local1 | local2 | local3 | local4 | local5 | local6 | local7 | lpr | mail | news | syslog | user | uucp}| use-vrf {vrf_name | management}]
host |
Hostname or IPv4/IPv6 address of the remote syslog server. |
severity-level |
(Optional) Number of the desired severity level at which messages should be logged. Messages at or numerically lower than the specified level are logged. Severity levels are as follows: •0—emergency: System unusable •1—alert: Immediate action needed •2—critical: Critical condition—default level •3—error: Error condition •4—warning: Warning condition •5—notification: Normal but significant condition •6—informational: Informational message only •7—debugging: Appears during debugging only |
facility facility |
(Optional) Specifies the appropriate outgoing facility. The facilities are listed in the System Message Logging Facilities section. The default outgoing facility is local7. |
vrf vrf_name |
(Optional) Specifies the virtual routing and forwarding (VRF) to be used in the remote server. The name can be a maximum of 32 alphanumeric characters. |
management |
Specifies the management VRF. This is the default VRF. |
The default outgoing facility is local7.
The default VRF is management.
Global configuration mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
4.1(3)N2(1) |
The use-vrf keyword was added. |
This example shows how to configure a remote syslog server at a specified IPv4 address, using the default outgoing facility:
switch(config)# logging server 192.168.2.253
This example shows how to configure a remote syslog server at a specified hostname with severity level 5 or higher:
switch(config)# logging server syslogA 5
|
|
---|---|
show logging server |
Displays the configured syslog servers. |
To set the logging time-stamp units, use the logging timestamp command. To reset the logging time-stamp units to the default, use the no form of this command.
logging timestamp {microseconds | milliseconds | seconds}
no logging timestamp {microseconds | milliseconds | seconds}
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
By default, the units are seconds.
This example shows how to set the logging time-stamp units to microseconds:
switch(config)# logging timestamp microseconds
|
|
---|---|
show logging timestamp |
Displays the logging time-stamp configuration. |
To configure the Network Time Protocol (NTP) peers and servers for the switch, use the ntp command. To remove configured peers and servers, use the no form of this command.
ntp {peer hostname | server hostname} [prefer] [use-vrf vrf-name]
no ntp {peer hostname | server hostname}
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
4.0(1a)N1(1) |
The keyword use-vrf replaces the keyword vrf. The keyword vrf is retained for backwards compatibility. |
You can specify multiple peer associations.
This example shows how to form a server association with a server:
switch(config)# ntp server ntp.cisco.com
This example shows how to form a peer association with a peer:
switch(config)# ntp peer 192.168.10.0
This example shows how to delete an association with a peer:
switch(config)# no ntp peer 192.168.10.0
|
|
---|---|
ntp distribute |
Enables CFS distribution for NTP. |
show ntp |
Displays NTP information. |
To discard the Network Time Protocol (NTP) Cisco Fabric Services (CFS) distribution session in progress, use the ntp abort command.
ntp abort
This command has no arguments or keywords.
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to discard the NTP CFS distribution session in progress:
switch(config)# ntp abort
|
|
---|---|
ntp distribute |
Enables CFS distribution for NTP. |
show ntp |
Displays NTP information. |
To apply the pending configuration pertaining to the Network Time Protocol (NTP) Cisco Fabric Services (CFS) distribution session in progress in the fabric, use the ntp commit command.
ntp commit
This command has no arguments or keywords.
None
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to commit changes to the active NTP configuration:
switch(config)# ntp commit
|
|
---|---|
ntp distribute |
Enables CFS distribution for NTP. |
show ntp |
Displays NTP information. |
To enable Cisco Fabric Services (CFS) distribution for Network Time Protocol (NTP), use the ntp distribute command. To disable this feature, use the no form of this command.
ntp distribute
no ntp distribute
This command has no arguments or keywords.
Disabled
Global configuration mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
Before distributing the Fibre Channel timer changes to the fabric, the temporary changes to the configuration must be committed to the active configuration using the ntp commit command.
This example shows how to distribute the active NTP configuration to the fabric:
switch(config)# ntp distribute
|
|
---|---|
ntp commit |
Commits the NTP configuration changes to the active configuration. |
show ntp |
Displays NTP information. |
To retry synchronization with the configured Network Time Protocol (NTP) servers, use the ntp sync-retry command.
ntp sync-retry
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to retry synchronization with the configured NTP servers:
switch# ntp sync-retry
|
|
---|---|
ntp distribute |
Enables CFS distribution for NTP. |
show ntp |
Displays NTP information. |
To display the current bootup diagnostic level on the switch, use the show diagnostic bootup level command.
show diagnostic bootup level
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the current bootup diagnostic level:
switch# show diagnostic bootup level
Current bootup diagnostic level: complete
switch#
|
|
---|---|
diagnostic bootup level |
Configures the bootup diagnostic level for a faster module bootup time. |
show diagnostic result |
Displays the results of the diagnostics tests. |
To display the results of the diagnostic tests, use the show diagnostic result command.
show diagnostic result module {module-no | all}
module |
Specifies the module for which diagnostic results are displayed. |
module-no |
Module number. Valid values are 1 to 3. |
all |
Displays the diagnostic results for all modules. |
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the diagnostic results for a specific module:
switch# show diagnostic result module 1
Current bootup diagnostic level: complete
Module 1: 48X10GE/Supervisor SerialNo : JAF1339ANGH
Overall Diagnostic Result for Module 1 : PASS
Diagnostic level at card bootup: complete
Test results: (. = Pass, F = Fail, I = Incomplete,
U = Untested, A = Abort)
1) TestUSBFlash ------------------------> .
2) TestSPROM ---------------------------> .
3) TestPCIe ----------------------------> .
4) TestLED -----------------------------> .
5) TestOBFL ----------------------------> .
6) TestNVRAM ---------------------------> .
7) TestPowerSupply ---------------------> F
8) TestTemperatureSensor ---------------> .
9) TestFan -----------------------------> .
10) TestVoltage -------------------------> .
11) TestGPIO ----------------------------> .
12) TestInbandPort ----------------------> .
13) TestManagementPort ------------------> .
14) TestMemory --------------------------> .
15) TestFabricEngine :
Eth 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Eth 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
16) TestFabricPort :
Eth 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Eth 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
17) TestForwardingEngine :
Eth 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Eth 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
18) TestForwardingEnginePort :
Eth 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Eth 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
19) TestFrontPort :
Eth 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
Eth 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48
Port ------------------------------------------------------------------------
. . . . . . . . . . . . . . . . . . . . . . . .
switch#
|
|
---|---|
diagnostic bootup level |
Configures the bootup diagnostic level for a faster module bootup time. |
show diagnostic bootup level |
Displays the bootup diagnostics level. |
To display the console logging configuration, use the show logging console command.
show logging console
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the console logging configuration:
switch# show logging console
|
|
---|---|
logging console |
Configures logging to the console. |
To display the logging configuration, use the show logging info command.
show logging info
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the logging configuration:
switch# show logging info
To display the last number of lines of the logfile, use the show logging last command.
show logging last number
number |
Enters the number of lines to display from 1 to 9999. |
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the last 42 lines of the log file:
switch# show logging last 42
To display the facility logging severity level configuration, use the show logging level command.
show logging level [facility]
facility |
(Optional) Appropriate logging facility. The facilities are listed in the System Message Logging Facilities section. |
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the EtherChannel logging severity level configuration:
switch# show logging level port-channel
|
|
---|---|
logging level |
Configures the facility logging level. |
To display the messages in the log file that were timestamped within the span entered, use the show logging logfile command.
show logging logfile [start-time yyyy mmm dd hh:mm:ss] [end-time yyyy mmm dd hh:mm:ss]
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
If you do not enter an end time, the current time is used.
This example shows how to display the messages in the log file that were timestamped within the span shown:
switch# show logging logfile start-time 2008 mar 11 12:10:00
|
|
---|---|
logging logfile |
Configures logging to a log file. |
To display the module logging configuration, use the show logging module command.
show logging module
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the module logging configuration:
switch# show logging module
|
|
---|---|
logging module |
Configures module logging. |
To display the monitor logging configuration, use the show logging monitor command.
show logging monitor
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the monitor logging configuration:
switch# show logging monitor
|
|
---|---|
logging monitor |
Configures logging on the monitor. |
To display the messages in the nonvolatile random access memory (NVRAM) log, use the show logging nvram command.
show logging nvram [last number-lines]
last number-lines |
(Optional) Specifies the number of lines to display. The number of lines is from 1 to 100. |
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the last 20 messages in the NVRAM log:
switch# show logging nvram last 20
To display the onboard logging information based on the error type, use the show logging onboard command.
show logging onboard {boot-uptime | device-version | endtime | environmental-history | exception-log | kernel-trace | obfl-history | obfl-logs | stack-trace | starttime | status} [> file | | type]
None
EXEC mode
|
|
---|---|
4.0(0)N1(1a) |
This command was introduced. |
The date and time arguments for the starttime and endtime keywords are entered as the date month/day/year (mm/dd/yy), followed by a hyphen, and the time in 24-hour format in hours:minutes:seconds (HH:MM:SS). For example:
•starttime 03/17/08-15:01:57
•endtime 03/18/08-15:04:57
The valid values for file are as follows:
•bootflash:
•ftp:
•scp:
•sftp:
•tftp:
•volatile:
The valid values for type are as follows:
•begin [-i] [-x] [word]—Begin with the line that matches the text.
–-i—Ignores the case difference when comparing the strings.
–-x—Prints only the lines where the match is a whole line.
–word—Specifies for the expression.
•count [> file | | type]—Counts number of lines.
•egrep | grep print-match—Egrep or Grep. Egrep searches for lines of text that match more sophisticated regular expression syntax than grep. Grep searches for lines of text that match one or many regular expressions, and outputs only the matching lines.
–-A num—Prints the specifies number of lines of context after every matching line. Range: 1 to 999.
–-B num—Prints the specifies number of lines of context before every matching line. Range: 1 to 999.
–-c—Prints a total count of matching lines only.
–-i—Ignores the case difference when comparing the strings.
–-n—Prints each match preceded by its line number.
–-v—Prints only the lines that contain no matches for the word argument.
–-w—Prints only lines where the match is a complete word.
–-x—Prints only the lines where the match is a whole line.
–word—Specifies for the expression.
•exclude [-i] [-x] [word]—Excludes the lines that match.
–-i—Ignores the case difference when comparing the strings.
–-x—Prints only the lines where the match is a whole line.
–word—Specifies for the expression.
•head [-n num]—Stream Editor. The optional -n num keyword and argument allow you to specify the number of lines to print. Range: 0 to 2147483647.
•include [-i] [-x] [word]—Include the lines that match.
–-i—Ignores the case difference when comparing the strings.
–-x—Prints only the lines where the match is a whole line.
–word—Specifies for the expression.
•last [num]—Displays the last lines to print. The optional num specifies the number of lines to print. Range: 0 to 9999.
•less [-E | -d]—Quits at the end of the file.
–-E—(Optional) Quits at the end of the file.
–-d—(Optional) Specifies a dumb terminal.
•no-more—Turns-off pagination for command output.
•sed command—Stream Editor
•wc—Counts words, lines, and characters.
–-c—(Optional) Specifies the output character count.
–-l—(Optional) Specifies the output line count.
–-w—(Optional) Specifies the output word count.
–>—Redirects it to a file.
–|—Pipes command output to filter.
Use this command to view OBFL data from the system hardware. The OBFL feature is enabled by default and records operating temperatures, hardware uptime, interrupts, and other important events and messages that can assist with diagnosing problems with hardware cards or modules installed in a Cisco router or switch. Data is logged to files stored in nonvolatile memory. When the onboard hardware is started up, a first record is made for each area monitored and becomes a base value for subsequent records.
The OBFL feature provides a circular updating scheme for collecting continuous records and archiving older (historical) records, ensuring accurate data about the system. Data is recorded in one of two formats: continuous information that displays a snapshot of measurements and samples in a continuous file, and summary information that provides details about the data being collected. The message "No historical data to display" is seen when historical data is not available.
This example shows how to display the OBFL boot and uptime information:
switch# show logging onboard boot-uptime Sun Nov 9 06:11:59 2008: Boot Record ------------------------------------------------------------------------------- Boot Time..........: Sun Nov 9 06:11:58 2008 Slot Number........: 1 Serial Number......: FLC12280050 Bios Version.......: v1.2.0(06/19/08) Firmware Version...: 4.0(1a)N1(1) [build 4.0(1a)N1(1)]
Table 7-1 describes the significant fields shown in the display.
This example shows how to display the OBFL logging device information:
switch# show logging onboard device-version ---------------------------- OBFL Data for Module: 1 ---------------------------- Device Version Record ---------------------------------------------------------------------- Timestamp Device Name Instance Hardware Software Num Version Version ---------------------------------------------------------------------- Sun Nov 3 07:07:00 2008 GATOS 2 2 0 Sun Nov 3 07:07:00 2008 GATOS 3 2 0 Sun Nov 3 07:07:00 2008 GATOS 4 2 0 Sun Nov 3 07:07:00 2008 GATOS 5 2 0 Sun Nov 3 07:07:00 2008 GATOS 6 2 0 Sun Nov 3 07:07:00 2008 GATOS 7 2 0 Sun Nov 3 07:07:00 2008 GATOS 8 2 0 Sun Nov 3 07:07:00 2008 GATOS 9 2 0 Sun Nov 3 07:07:00 2008 GATOS 10 2 0 Sun Nov 3 07:07:00 2008 GATOS 11 2 0 Sun Nov 3 07:07:00 2008 GATOS 12 2 0 Sun Nov 3 07:07:00 2008 GATOS 13 2 0 Mon Nov 4 00:15:08 2008 ALTOS 0 2 0 Mon Nov 4 00:15:08 2008 GATOS 0 2 0 Mon Nov 4 00:15:08 2008 GATOS 1 2 0 Mon Nov 4 00:15:08 2008 GATOS 2 2 0
Table 7-2 describes the significant fields shown in the display.
This example shows how to display the OBFL history information:
switch# show logging onboard obfl-history
The show logging onboard obfl-history command displays the following information:
•Timestamp when OBFL is manually disabled.
•Timestamp when OBFL is manually enabled.
•Timestamp when OBFL data is manually cleared.
This example shows how to display the OBFL kernel stack trace information:
switch# show logging onboard stack-trace
The show logging onboard stack-trace command displays the following information:
•Time in seconds
•Time in microseconds
•Error description string
•Current process name and identification
•Kernel jiffies
•Stack trace
clear logging onboard |
Clears the OBFL entries in the persistent log. |
hw-module logging onboard |
Enables or disabled OBFL entries based on the error type. |
To display the pending changes to the syslog server configuration, use the show logging pending command.
show logging pending
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the pending changes to the syslog server configuration:
switch# show logging pending
switch#
|
|
---|---|
logging abort |
Cancels the pending changes to the syslog server configuration. |
To display the differences from the current syslog server configuration to the pending changes of the syslog server configuration, use the show logging pending-diff command.
show logging pending-diff
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the pending differences of the syslog server configuration:
switch# show logging pending-diff
switch#
|
|
---|---|
logging abort |
Cancels the pending changes to the syslog server configuration. |
To display the logging session status, use the show logging session status command.
show logging session status
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the logging session status:
switch# show logging session status
To display the syslog server configuration, use the show logging server command.
show logging server
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the syslog server configuration:
switch# show logging server
|
|
---|---|
logging server |
Configures a remote syslog server. |
To display the logging status, use the show logging status command.
show logging status
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the logging status:
switch# show logging status
Fabric Distribute : Enabled
Session State : IDLE
switch#
|
|
---|---|
logging distribute |
Enables the distribution of the syslog server configuration to network switches using the Cisco Fabric Services (CFS) infrastructure. |
To display the logging time-stamp configuration, use the show logging timestamp command.
show logging timestamp
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the logging time-stamp configuration:
switch# show logging timestamp
|
|
---|---|
logging timestamp |
Configures the logging time stamp granularity. |
To display the status of the Network Time Protocol (NTP) peers, use the show ntp peer-status command.
show ntp peer-status
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the peer status for NTP:
switch(
config)#
show ntp peer-status
|
|
---|---|
show ntp peers |
Displays information about NTP peers. |
To display information about Network Time Protocol (NTP) peers, use the show ntp peers command.
show ntp peers
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display information about NTP peers:
switch(
config)#
show ntp peers
|
|
---|---|
show ntp peer-status |
Displays status information about NTP peers. |
To display Network Time Protocol (NTP) statistics, use the show ntp statistics command.
show ntp statistics {io | local | memory | peer {ipaddr address | name name1 [..nameN]}
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the statistics for NTP:
switch(
config)#
show ntp statistics local
|
|
---|---|
clear ntp statistics |
Clears NTP statistics |
To display the Network Time Protocol (NTP) time-stamp information, use the show ntp timestamp-status command.
show ntp timestamp-status
This command has no arguments or keywords.
None
EXEC mode
|
|
4.0(0)N1(1a) |
This command was introduced. |
This example shows how to display the NTP time-stamp status:
switch(
config)#
show ntp timestamp-status
To display the Simple Network Management Protocol (SNMP) community strings configured on the switch, use the show snmp community command.
show snmp community
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the SNMP community strings:
switch# show snmp community
Community Group / Access context acl_filter
--------- -------------- ------- ----------
public network-admin
switch#
|
|
---|---|
snmp-server community |
Configures the community access string to permit access to the SNMP protocol. |
To display the Simple Network Management Protocol (SNMP) contexts configured on the switch, use the show snmp context command.
show snmp context
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the SNMP contexts:
switch# show snmp context
|
|
---|---|
snmp-server context |
Configures an SNMP context. |
To display the identification of the local Simple Network Management Protocol (SNMP) engine, use the show snmp engineID command.
show snmp engineID
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
An SNMP engine is a copy of SNMP that can reside on a local or remote device. SNMP passwords are localized using the SNMP engine ID of the authoritative SNMP engine.
This example shows how to display the SNMP engine ID:
switch# show snmp engineID
Local SNMP engineID: [Hex] 8000000903000DECB230C0
[Dec] 128:000:000:009:003:000:013:236:178:048:192
switch#
To display the names of the Simple Network Management Protocol (SNMP) groups configured on the switch, use the show snmp group command.
show snmp group
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the SNMP groups:
switch# show snmp group
Role: network-admin
Description: Predefined network admin role has access to all commands
on the switch
-------------------------------------------------------------------
Rule Perm Type Scope Entity
-------------------------------------------------------------------
1 permit read-write
Role: network-operator
Description: Predefined network operator role has access to all read
commands on the switch
-------------------------------------------------------------------
Rule Perm Type Scope Entity
-------------------------------------------------------------------
1 permit read
Role: vdc-admin
Description: Predefined vdc admin role has access to all commands within
a VDC instance
-------------------------------------------------------------------
Rule Perm Type Scope Entity
-------------------------------------------------------------------
1 permit read-write
Role: vdc-operator
Description: Predefined vdc operator role has access to all read commands
within a VDC instance
-------------------------------------------------------------------
Rule Perm Type Scope Entity
-------------------------------------------------------------------
1 permit read
Role: priv-3
Description: This is a system defined privilege role.
vsan policy: permit (default)
Vlan policy: permit (default)
Interface policy: permit (default)
Vrf policy: permit (default)
Role: priv-2
Description: This is a system defined privilege role.
vsan policy: permit (default)
Vlan policy: permit (default)
Interface policy: permit (default)
Vrf policy: permit (default)
Role: priv-1
Description: This is a system defined privilege role.
vsan policy: permit (default)
Vlan policy: permit (default)
Interface policy: permit (default)
Vrf policy: permit (default)
Role: priv-0
Description: This is a system defined privilege role.
vsan policy: permit (default)
Vlan policy: permit (default)
Interface policy: permit (default)
Vrf policy: permit (default)
-------------------------------------------------------------------
Rule Perm Type Scope Entity
-------------------------------------------------------------------
10 permit command traceroute6 *
9 permit command traceroute *
8 permit command telnet6 *
7 permit command telnet *
6 permit command ping6 *
5 permit command ping *
4 permit command ssh6 *
3 permit command ssh *
2 permit command enable *
1 permit read
Role: priv-15
Description: This is a system defined privilege role.
vsan policy: permit (default)
Vlan policy: permit (default)
Interface policy: permit (default)
Vrf policy: permit (default)
-------------------------------------------------------------------
Rule Perm Type Scope Entity
-------------------------------------------------------------------
1 permit read-write
switch#
To display the Simple Network Management Protocol (SNMP) host information, use the show snmp host command.
show snmp host
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the SNMP host:
switch# show snmp host
|
|
---|---|
snmp-server host |
Configures an SNMP host. |
To display the current Simple Network Management Protocol (SNMP) sessions, use the show snmp sessions command.
show snmp sessions
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the SNMP sessions:
switch# show snmp sessions
To display the Simple Network Management Protocol (SNMP) link trap generation information, use the show snmp trap command.
show snmp trap
This command has no arguments or keywords.
None
EXEC mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to display the SNMP traps:
switch# show snmp trap
--------------------------------------------------------------------------------
Trap type Description Enabled
--------------------------------------------------------------------------------
entity : entity_mib_change Yes
entity : entity_module_status_change Yes
entity : entity_power_status_change Yes
entity : entity_module_inserted Yes
entity : entity_module_removed Yes
entity : entity_unrecognised_module Yes
entity : entity_fan_status_change Yes
link : linkDown Yes
link : linkUp Yes
link : IETF-extended-linkDown Yes
link : IETF-extended-linkUp Yes
link : cisco-extended-linkDown Yes
link : cisco-extended-linkUp Yes
callhome : event-notify No
callhome : smtp-send-fail No
cfs : state-change-notif No
cfs : merge-failure No
rf : redundancy_framework Yes
aaa : server-state-change No
license : notify-license-expiry Yes
license : notify-no-license-for-feature Yes
license : notify-licensefile-missing Yes
license : notify-license-expiry-warning Yes
zone : unsupp-mem No
upgrade : UpgradeOpNotifyOnCompletion Yes
upgrade : UpgradeJobStatusNotify Yes
feature-control : FeatureOpStatusChange No
sysmgr : cseFailSwCoreNotifyExtended No
rmon : risingAlarm No
rmon : fallingAlarm No
rmon : hcRisingAlarm No
rmon : hcFallingAlarm No
config : ccmCLIRunningConfigChanged No
snmp : authentication No
bridge : topologychange No
bridge : newroot No
stp : inconsistency No
stpx : loop-inconsistency No
stpx : root-inconsistency No
switch#
|
|
---|---|
snmp trap link-status |
Enables SNMP link trap generation. |
To create Simple Network Management Protocol (SNMP) communities for SNMPv1 or SNMPv2c, use the snmp-server community command. To revert to the defaults, sue the no form of this command.
snmp-server community com-name [group grp-name | ro | rw | use-acl acl-name]
no snmp-server community com-name [group grp-name | ro | rw | use-acl acl-name]
None
Global configuration mode
|
|
---|---|
4.2(1)N1(1) |
This command was introduced. |
You can assign an access list (ACL) to a community to filter incoming SNMP requests. If the assigned ACL allows the incoming request packet, SNMP processes the request. If the ACL denies the request, SNMP drops the request and sends a system message.
See the Cisco Nexus 5000 Series NX-OS Security Configuration Guide for more information on creating ACLs. The ACL applies to both IPv4 and IPv6 over UDP and TCP. After creating the ACL, assign the ACL to the SNMP community.
This example shows how to create an SNMP community string and assign an ACL to the community to filter SNMP requests:
switch(config)# snmp-server community public use-acl my_acl_for_public
switch(config)#
|
|
---|---|
show snmp community |
Displays the SNMP community strings. |
Table 7-3 lists the facilities that you can use in system message logging configuration.
To verify the current configuration session, use the verify command.
verify
This command has no arguments or keywords.
None
Session configuration mode
|
|
---|---|
4.0(0)N1(1) |
This command was introduced. |
This example shows how to verify a session:
switch(config-s)# verify
Failed to start Verification: Session Database already locked, Verify/Commit in
Progress.
switch(config-s)#
|
|
---|---|
commit |
Commits a session. |
configure session |
Creates a configuration session. |
show configuration session |
Displays the contents of the session. |