Published On: July 14ᵗʰ, 2021 08:10

System Management Configuration Guide, Cisco IOS XE Amsterdam 17.3.x (Catalyst 9500 Switches)

Contents

This chapter describes how to identify and resolve software problems related to the Cisco IOS software on the switch. Depending on the nature of the problem, you can use the command-line interface (CLI), Device Manager, or Network Assistant to identify and solve problems.

Additional troubleshooting information, such as LED descriptions, is provided in the hardware installation guide.

Information About Troubleshooting the Software Configuration

Software Failure on a Switch

Switch software can be corrupted during an upgrade by downloading the incorrect file to the switch, and by deleting the image file. In all of these cases, the switch does not pass the power-on self-test (POST), and there is no connectivity.Follow the steps described in the Recovering from a Software Failure section to recover from a software failure.

Lost or Forgotten Password on a Device

The default configuration for the device allows an end user with physical access to the device to recover from a lost password by interrupting the boot process during power-on and by entering a new password. These recovery procedures require that you have physical access to the device.


Note

On these devices, a system administrator can disable some of the functionality of this feature by allowing an end user to reset a password only by agreeing to return to the default configuration. If you are an end user trying to reset a password when password recovery has been disabled, a status message reminds you to return to the default configuration during the recovery process.



Note

You cannot recover encryption password key, when Cisco WLC configuration is copied from one Cisco WLC to another (in case of an RMA).


Follow the steps described in the section Recovering from a Lost or Forgotten Password to recover from a lost or forgotten password.

Ping

The device supports IP ping, which you can use to test connectivity to remote hosts. Ping sends an echo request packet to an address and waits for a reply. Ping returns one of these responses:

  • Normal response—The normal response (hostname is alive) occurs in 1 to 10 seconds, depending on network traffic.

  • Destination does not respond—If the host does not respond, a no-answer message is returned.

  • Unknown host—If the host does not exist, an unknown host message is returned.

  • Destination unreachable—If the default gateway cannot reach the specified network, a destination-unreachable message is returned.

  • Network or host unreachable—If there is no entry in the route table for the host or network, a network or host unreachable message is returned.

Refere the section Executing Ping to understand how ping works.

Layer 2 Traceroute

The Layer 2 traceroute feature allows the switch to identify the physical path that a packet takes from a source device to a destination device. Layer 2 traceroute supports only unicast source and destination MAC addresses. Traceroute finds the path by using the MAC address tables of the devices in the path. When the Device detects a device in the path that does not support Layer 2 traceroute, the Device continues to send Layer 2 trace queries and lets them time out.

The Device can only identify the path from the source device to the destination device. It cannot identify the path that a packet takes from source host to the source device or from the destination device to the destination host.

Layer 2 Traceroute Guidelines

  • Cisco Discovery Protocol (CDP) must be enabled on all the devices in the network. For Layer 2 traceroute to function properly, do not disable CDP.

    If any devices in the physical path are transparent to CDP, the switch cannot identify the path through these devices.

  • A device is reachable from another device when you can test connectivity by using the ping privileged EXEC command. All devices in the physical path must be reachable from each other.

  • The maximum number of hops identified in the path is ten.

  • You can enter the traceroute mac or the traceroute mac ip privileged EXEC command on a device that is not in the physical path from the source device to the destination device. All devices in the path must be reachable from this switch.

  • The traceroute mac command output shows the Layer 2 path only when the specified source and destination MAC addresses belong to the same VLAN. If you specify source and destination MAC addresses that belong to different VLANs, the Layer 2 path is not identified, and an error message appears.

  • If you specify a multicast source or destination MAC address, the path is not identified, and an error message appears.

  • If the source or destination MAC address belongs to multiple VLANs, you must specify the VLAN to which both the source and destination MAC addresses belong. If the VLAN is not specified, the path is not identified, and an error message appears.

  • The traceroute mac ip command output shows the Layer 2 path when the specified source and destination IP addresses belong to the same subnet. When you specify the IP addresses, the device uses the Address Resolution Protocol (ARP) to associate the IP addresses with the corresponding MAC addresses and the VLAN IDs.

    • If an ARP entry exists for the specified IP address, the device uses the associated MAC address and identifies the physical path.

    • If an ARP entry does not exist, the device sends an ARP query and tries to resolve the IP address. If the IP address is not resolved, the path is not identified, and an error message appears.

  • When multiple devices are attached to one port through hubs (for example, multiple CDP neighbors are detected on a port), the Layer 2 traceroute feature is not supported. When more than one CDP neighbor is detected on a port, the Layer 2 path is not identified, and an error message appears.

  • This feature is not supported in Token Ring VLANs.

  • Layer 2 traceroute opens a listening socket on the User Datagram Protocol (UDP) port 2228 that can be accessed remotely with any IPv4 address, and does not require any authentication. This UDP socket allows to read VLAN information, links, presence of particular MAC addresses, and CDP neighbor information, from the device. This information can be used to eventually build a complete picture of the Layer 2 network topology.

  • Layer 2 traceroute is enabled by default and can be disabled by running the no l2 traceroute command in global configuration mode. To re-enable Layer 2 traceroute, use the l2 traceroute command in global configuration mode.

IP Traceroute

You can use IP traceroute to identify the path that packets take through the network on a hop-by-hop basis. The command output displays all network layer (Layer 3) devices, such as routers, that the traffic passes through on the way to the destination.

Your Device can participate as the source or destination of the traceroute privileged EXEC command and might or might not appear as a hop in the traceroute command output. If the Device is the destination of the traceroute, it is displayed as the final destination in the traceroute output. Intermediate devices do not show up in the traceroute output if they are only bridging the packet from one port to another within the same VLAN. However, if the intermediate Device is a multilayer Device that is routing a particular packet, this device shows up as a hop in the traceroute output.

The traceroute privileged EXEC command uses the Time To Live (TTL) field in the IP header to cause routers and servers to generate specific return messages. Traceroute starts by sending a User Datagram Protocol (UDP) datagram to the destination host with the TTL field set to 1. If a router finds a TTL value of 1 or 0, it drops the datagram and sends an Internet Control Message Protocol (ICMP) time-to-live-exceeded message to the sender. Traceroute finds the address of the first hop by examining the source address field of the ICMP time-to-live-exceeded message.

To identify the next hop, traceroute sends a UDP packet with a TTL value of 2. The first router decrements the TTL field by 1 and sends the datagram to the next router. The second router sees a TTL value of 1, discards the datagram, and returns the time-to-live-exceeded message to the source. This process continues until the TTL is incremented to a value large enough for the datagram to reach the destination host (or until the maximum TTL is reached).

To learn when a datagram reaches its destination, traceroute sets the UDP destination port number in the datagram to a very large value that the destination host is unlikely to be using. When a host receives a datagram destined to itself containing a destination port number that is unused locally, it sends an ICMP port-unreachable error to the source. Because all errors except port-unreachable errors come from intermediate hops, the receipt of a port-unreachable error means that this message was sent by the destination port.

Go to Example: Performing a Traceroute to an IP Host to see an example of IP traceroute process.

Debug Commands


Caution

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. It is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.


All debug commands are entered in privileged EXEC mode, and most debug commands take no arguments.

System Report

System reports or crashinfo files save information that helps Cisco technical support representatives to debug problems that caused the Cisco IOS image to fail (crash). It is necessary to quickly and reliably collect critical crash information with high fidelity and integrity. Further, it is necessary to collect this information and bundle it in a way that it can be associated or identified with a specific crash occurrence.

System reports are generated in these situations:

  • In case of a switch failure—A system report is generated on the switch that failed

  • In case of a switchover—System reports are generated only on high availability (HA) member switches. reports are not generated for non-HA members.

The system does not generate reports in case of a reload.

During a process crash, the following is collected locally from the switch:

  1. Full process core

  2. Tracelogs

  3. IOS syslogs (not guaranteed in case of non-active crashes)

  4. System process information

  5. Bootup logs

  6. Reload logs

  7. Certain types of /proc information

This information is stored in separate files which are then archived and compressed into one bundle. This makes it convenient to get a crash snapshot in one place, and can be then moved off the box for analysis. This report is generated before the switch goes down to rommon/bootloader.

Except for the full core and tracelogs, everything else is a text file.

Use the request platform software process core fed active command to generate the core dump.

h2-macallan1# request platform software process core fed active
Process : fed main event (28155) encountered fatal signal 6
Process : fed main event stack :

SUCCESS: Core file generated.

h2-macallan1#dir bootflash:core
Directory of bootflash:/core/

178483  -rw-                1  May 23 2017 06:05:17 +00:00  .callhome
194710  drwx             4096  Aug 16 2017 19:42:33 +00:00  modules
178494  -rw-         10829893  Aug 23 2017 09:46:23 +00:00  h2-macallan1_RP_0_fed_28155_20170823-094616-UTC.core.gz

Crashinfo Files

By default the system report file will be generated and saved into the /crashinfo directory. Ifit cannot be saved to the crashinfo partition for lack of space, then it will be saved to the /flash directory.

To display the files, enter the dir crashinfo: command. The following is sample output of a crashinfo directory:

Switch#dir crashinfo:
Directory of crashinfo:/


23665 drwx 86016 Jun 9 2017 07:47:51 -07:00 tracelogs
11 -rw- 0 May 26 2017 15:32:44 -07:00 koops.dat
12 -rw- 4782675 May 29 2017 15:47:16 -07:00 system-report_1_20170529-154715-PDT.tar.gz
1651507200 bytes total (1519386624 bytes free)

System reports are located in the crashinfo directory in the following format:

system-report_[switch number]_[date]-[timestamp]-UTC.gz

After a switch crashes, check for a system report file. The name of the most recently generated system report file is stored in the last_systemreport file under the crashinfo directory. The system report and crashinfo files assist TAC while troubleshooting the issue.

The system report generated can be further copied using TFTP, HTTP and few other options.

Switch#copy crashinfo: ?
crashinfo:     Copy to crashinfo: file system 
flash:         Copy to flash: file system
ftp:           Copy to ftp: file system 
http:          Copy to http: file system 
https:         Copy to https: file system 
null:          Copy to null: file system
nvram:         Copy to nvram: file system
rcp:           Copy to rcp: file system
running-config Update (merge with) current system configuration
scp:           Copy to scp: file system
startup-config Copy to startup configuration
syslog:        Copy to syslog: file system
system:        Copy to system: file system
tftp:          Copy to tftp: file system
tmpsys:        Copy to tmpsys: file system

The general syntax for copying onto TFTP server is as follows:

Switch#copy crashinfo: tftp:
Source filename [system-report_1_20150909-092728-UTC.gz]?
Address or name of remote host []? 1.1.1.1
Destination filename [system-report_1_20150909-092728-UTC.gz]?

The tracelogs can be collected by issuing a trace archive command. This command provides time period options. The command syntax is as follows:

Switch#request platform software trace archive ?
last     Archive trace files of last x days
target   Location and name for the archive file

The tracelogs stored in crashinfo: or flash: directory from within the last 3650 days can be collected.

Switch# request platform software trace archive last ?
<1-3650> Number of days (1-3650)
Switch#request platform software trace archive last 3650 days target ?
crashinfo: Archive file name and location
flash:     Archive file name and location

Note

It is important to clear the system reports or trace archives from flash or crashinfo directory once they are copied out, in order to have space available for tracelogs and other purposes.


In a complex network it is difficult to track the origin of a system-report file. This task is made easier if the system-report files are uniquely identifiable. Starting with the Cisco IOS XE Amsterdam 17.3.x release, the hostname will be prepended to the system-report file name making the reports uniquely identifiable.

The following example displays system-report files with the hostname prepended:

HOSTNAME#dir flash:/core | grep HOSTNAME
40486  -rw-        108268293  Oct 21 2019 16:07:50 -04:00  HOSTNAME-system-report_20191021-200748-UTC.tar.gz
40487  -rw-            17523  Oct 21 2019 16:07:56 -04:00  HOSTNAME-system-report_20191021-200748-UTC-info.txt
40484  -rw-         48360998  Oct 21 2019 16:55:24 -04:00  HOSTNAME-system-report_20191021-205523-UTC.tar.gz
40488  -rw-            14073  Oct 21 2019 16:55:26 -04:00  HOSTNAME-system-report_20191021-205523-UTC-info.txt

Onboard Failure Logging on the Switch

You can use the onboard failure logging (OBFL) feature to collect information about the device. The information includes uptime, temperature, and voltage information and helps Cisco technical support representatives to troubleshoot device problems. We recommend that you keep OBFL enabled and do not erase the data stored in the flash memory.

By default, OBFL is enabled. It collects information about the device and small form-factor pluggable (SFP) modules. The device stores this information in the flash memory:

  • CLI commands—Record of the OBFL CLI commands that are entered on a standalone device.

  • Environment data—Unique device identifier (UDI) information for a standalone device and for all the connected FRU devices: the product identification (PID), the version identification (VID), and the serial number.

  • Message—Record of the hardware-related system messages generated by a standalone device .

  • Power over Ethernet (PoE)—Record of the power consumption of PoE ports on a standalone device .

    Note

    This feature is not supported on the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches.


  • Temperature—Temperature of a standalone deicev .

  • Uptime data—Time when a standalone device starts, the reason the device restarts, and the length of time the device has been running since it last restarted.

  • Voltage—System voltages of a standalone device .

You should manually set the system clock or configure it by using Network Time Protocol (NTP).

When the device is running, you can retrieve the OBFL data by using the show logging onboard privileged EXEC commands. If the device fails, contact your Cisco technical support representative to find out how to retrieve the data.

When an OBFL-enabled device is restarted, there is a 10-minute delay before logging of new data begins.

Fan Failures

By default, the feature is disabled. When more than one of the fans fails in a field-replaceable unit (FRU) or in a power supply, the device does not shut down, and this error message appears:


Multiple fan(FRU/PS) failure detected. System may get overheated. Change fan quickly.


The device might overheat and shut down.

To enable the fan failures feature, enter the system env fan-fail-action shut privileged EXEC command. If more than one fan in the device fails, the device automatically shuts down, and this error message appears:


Faulty (FRU/PS) fans detected, shutting down system! 


After the first fan shuts down, if the device detects a second fan failure, the device waits for 20 seconds before it shuts down.

To restart the device, it must be power cycled.

Possible Symptoms of High CPU Utilization

Excessive CPU utilization might result in these symptoms, but the symptoms might also result from other causes, some of which are the following:

  • Spanning tree topology changes

  • EtherChannel links brought down due to loss of communication

  • Failure to respond to management requests (ICMP ping, SNMP timeouts, slow Telnet or SSH sessions)

  • UDLD flapping

  • IP SLAs failures because of SLAs responses beyond an acceptable threshold

  • DHCP or IEEE 802.1x failures if the switch does not forward or respond to requests

How to Troubleshoot the Software Configuration

Recovering from a Software Failure

Before you begin

This recovery procedure requires that you have physical access to the switch.

This procedure uses boot loader commands and TFTP to recover from a corrupted or incorrect image file.

Set the baud rate of the terminal to match the the default rate of 9600 bits per second [bps] of the switch console port. If the baud rate is set to a value other than 9600 bps, access to the console will be lost until the speed is set back to the dafault.

Procedure


Step 1

From your PC, download the software image file (image.bin ) from Cisco.com.

Step 2

Load the software image to your TFTP server.

Step 3

Connect your PC to the switch Ethernet management port.

Step 4

Unplug the switch power cord.

Step 5

Press the Mode button, and at the same time, reconnect the power cord to the switch.

Step 6

From the bootloader prompt, ensure that you can ping your TFTP server.

  1. Set switch IP address: set IP_ADDRESS ip_address

    Example:

    switch: set IP_ADDRESS 192.0.2.123
    
    
    
  2. Set switch subnet mask: set IP_SUBNET_MASK subnet_mask

    Example:

    switch: set IP_SUBNET_MASK 255.255.255.0
    
    
    
  3. Set default gateway: set DEFAULT_GATEWAY ip_address

    Example:

    switch: set DEFAULT_ROUTER 192.0.2.1
    
    
    
  4. Verify that you can ping the TFTP server switch: ping ip_address_of_TFTP_server

Example:

switch: ping 192.0.2.15 
ping 192.0.2.1 with 32 bytes of data...
Host 192.0.2.1 is alive.
switch:


Step 7

Choose one of the following:

  • From the bootloader prompt, initiate the boot tftp command that assists you in recovering the software image on your switch.
    switch: boot tftp://10.168.0.1/cat9k/cat9k_iosxe.2017-08-25_09.41.bin
    attempting to boot from [tftp://10.168.0.1/cat9k/cat9k_iosxe.2017-08-25_09.41.SSA.bin]
    
     interface : eth0
     macaddr   : E4:AA:5D:59:7B:44
     ip        : 10.168.247.10
     netmask   : 10.255.0.0
     gateway   : 10.168.0.1
     server    : 10.168.0.1
     file      : cat9k/cat9k_iosxe.2017-08-25_09.41.bin
    !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
    
    
    
    
                 Restricted Rights Legend
    
    Use, duplication, or disclosure by the Government is
    subject to restrictions as set forth in subparagraph
    (c) of the Commercial Computer Software - Restricted
    Rights clause at FAR sec. 52.227-19 and subparagraph
    (c) (1) (ii) of the Rights in Technical Data and Computer
    Software clause at DFARS sec. 252.227-7013.
    
               cisco Systems, Inc.
               170 West Tasman Drive
               San Jose, California 95134-1706
    
    
    
    Cisco IOS Software [Everest], Catalyst L3 Switch Software (CAT9K_IOSXE), Version 16.6.1 RELEASE SOFTWARE (fc2)
    Copyright (c) 1986-2017 by Cisco Systems, Inc.
    Compiled Thu 24-Aug-17 13:23 by mcpre
    
    
    
    Cisco IOS-XE software, Copyright (c) 2005-2017 by cisco Systems, Inc.
    All rights reserved.  Certain components of Cisco IOS-XE software are
    licensed under the GNU General Public License ("GPL") Version 2.0.  The
    software code licensed under GPL Version 2.0 is free software that comes
    with ABSOLUTELY NO WARRANTY.  You can redistribute and/or modify such
    GPL code under the terms of GPL Version 2.0.  For more details, see the
    documentation or "License Notice" file accompanying the IOS-XE software,
    or the applicable URL provided on the flyer accompanying the IOS-XE
    software.
    
    
    
    
    FIPS: Flash Key Check : Begin
    FIPS: Flash Key Check : End, Not Found, FIPS Mode Not Enabled
    
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    
    If you require further assistance please contact us by sending email to
    export@cisco.com.
    
    cisco C9XXX (X86) processor (revision V00) with 869398K/6147K bytes of memory.
    Processor board ID FXS1939Q3LZ
    144 Gigabit Ethernet interfaces
    16 Ten Gigabit Ethernet interfaces
    4 Forty Gigabit Ethernet interfaces
    32768K bytes of non-volatile configuration memory.
    15958516K bytes of physical memory.
    11161600K bytes of Bootflash at bootflash:.
    1638400K bytes of Crash Files at crashinfo:.
    0K bytes of WebUI ODM Files at webui:.
    
    %INIT: waited 0 seconds for NVRAM to be available
    
    
    
    Press RETURN to get started!
    
    
    
  • Install the software from the recovery partition. This recovery image is required for recovery using the emergency-install feature.

  1. Verify that you have a recovery image in your recovery partition (sda9:).

    Example:

    
    switch: dir sda9:
    
    Size            Attributes      Name
     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    21680202        -rw-            cat9k-recovery.SSA.bin
     - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
    
    
  2. From the bootloader prompt, initiate the emergency-install feature that assists you in recovering the software image on your switch. WARNING: The emergency install command will erase your entire boot flash!

    Example:

    switch: emergency-install tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin
    WARNING: The system partition (bootflash:) will be erased during the system recovery install process.
    Are you sure you want to proceed? [y]  y/n [n]: y
    Starting system recovery (tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin) ...
    Attempting to boot from [sda9:cat9k-recovery.SSA.bin]
    Located cat9k-recovery.SSA.bin
    ###########################################################################################################################################
    
    Warning: ignoring ROMMON var "BOOT_PARAM"
    
    PLATFORM_TYPE C9X00 speed 9600
    
    Booting Recovery Image 16.5.1a
    
    
    
    Initiating Emergency Installation of bundle tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin
    
    
    Downloading bundle tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin...
    curl_vrf=2
      % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                     Dload  Upload   Total   Spent    Left  Speed
    100  485M  100  485M    0     0  5143k      0  0:01:36  0:01:36 --:--:-- 5256k
    100  485M  100  485M    0     0  5143k      0  0:01:36  0:01:36 --:--:-- 5143k
    
    Validating bundle tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin...
    Installing bundle tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin....
    Verifying bundle tftp://10.255.254.254/auto/tftpboot/X86/cat9k_iosxe.16.05.01a.SPA.bin...
    Package cat9k-cc_srdriver.16.05.01a.SPA.pkg /temp//stage/cat9k-cc_srdriver.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-espbase.16.05.01a.SPA.pkg /temp//stage/cat9k-espbase.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-guestshell.16.05.01a.SPA.pkg /temp//stage/cat9k-guestshell.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-rpbase.16.05.01a.SPA.pkg /temp//stage/cat9k-rpbase.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-sipbase.16.05.01a.SPA.pkg /temp//stage/cat9k-sipbase.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-sipspa.16.05.01a.SPA.pkg /temp//stage/cat9k-sipspa.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-srdriver.16.05.01a.SPA.pkg /temp//stage/cat9k-srdriver.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-webui.16.05.01a.SPA.pkg /temp//stage/cat9k-webui.16.05.01a.SPA.pkg is Digitally Signed
    Package cat9k-wlc.16.05.01a.SPA.pkg /temp//stage/cat9k-wlc.16.05.01a.SPA.pkg is Digitally Signed
    Package /cat9k-rpboot.16.05.01a.SPA.pkg /temp//rpboot/cat9k-rpboot.16.05.01a.SPA.pkg is Digitally Signed
    Preparing flash....
    Flash filesystem unmounted successfully /dev/sdb3
    Syncing device....
    Emergency Install successful... Rebooting
    Will reboot now
    
    Initializing Hardware...
    
    System Bootstrap, Version 16.5.2r, RELEASE SOFTWARE (P)
    Compiled Wed 05/31/2017 15:58:35.22 by rel
    
    Current image running:
    Primary Rommon Image
    
    Last reset cause: SoftwareReload
    C9X00 platform with 8388608 Kbytes of main memory
    
    
    

Alternatively, you can copy the image from TFTP to local flash through Telnet or Management port and then boot the device from local flash.


Recovering from a Lost or Forgotten Password

The default configuration for the switch allows an end user with physical access to the switch to recover from a lost password by interrupting the boot process during power-on and by entering a new password. These recovery procedures require that you have physical access to the switch.


Note

On these switches, a system administrator can disable some of the functionality of this feature by allowing an end user to reset a password only by agreeing to return to the default configuration. If you are an end user trying to reset a password when password recovery has been disabled, a status message shows this during the recovery process.


Procedure


Step 1

Connect a terminal or PC to the switch.

  • Connect a terminal or a PC with terminal-emulation software to the switch console port.

  • Connect a PC to the Ethernet management port.

Step 2

Set the line speed on the emulation software to 9600 baud.

Step 3

Power off the standalone switch or the entire switch stack.

Step 4

For Cisco Catalyst 9500 Series Switches, reconnect the power cord to the switch or the active switchAs soon as the System LED blinks, press and release the Mode button 2-3 times. The switch enters the ROMMON mode.

Note 

Cisco Catalyst 9500 Series Switches- High Performance do not have a Mode button. You can exit the configuration dialog at any prompt using Ctrl-C to kill the bootup sequence.

The following console messages are displayed during the reload:

Initializing Hardware...

System Bootstrap, Version 16.6.1r [FC1], RELEASE SOFTWARE (P)
Compiled Sat 07/15/2017  8:31:57.39 by rel

Current image running: 
Primary Rommon Image

Last reset cause: SoftwareReload         <---- Start pressing and releasing the mode button
C9500-12Q platform with 8388608 Kbytes of main memory

attempting to boot from [flash:packages.conf]

Located file packages.conf 
#
#####################################################################

Unable to load cat9k-rpboot.16.06.02b.SPA.pkg
Failed to boot file flash:user/packages.conf
ERROR: failed to boot from flash:packages.conf (Aborted) <--- will abort
switch:  
switch:  <---- ROMMON

Initializing Hardware...

System Bootstrap, Version 16.8.1r [FC4], RELEASE SOFTWARE (P)
Compiled 20-03-2018 15:12:03.01 by rel

Current ROMMON image : Primary Rommon Image

Last reset cause:PowerOn
C9500-48Y4C platform with 16777216 Kbytes of main memory

Preparing to autoboot. [Press Ctrl-C to interrupt]     <<<<<<<<< Break sequence to be pressed to get to rommon

Proceed to the Procedure with Password Recovery Enabled section, and follow the steps.

Step 5

After recovering the password, reload the switch or the active switch.

On a switch:

Switch> reload
Proceed with reload? [confirm] y



Procedure with Password Recovery Enabled

Procedure

Step 1

Ignore the startup configuration with the following command:


Device: SWITCH_IGNORE_STARTUP_CFG=1


Step 2

Boot the switch with the packages.conf file from flash.


Device: boot flash:packages.conf


Step 3

Terminate the initial configuration dialog by answering No.


Would you like to enter the initial configuration dialog? [yes/no]: No


Step 4

At the switch prompt, enter privileged EXEC mode.


Device> enable      
Device#  


Step 5

Copy the startup configuration to running configuration.


Device# copy startup-config running-config Destination filename [running-config]?


Press Return in response to the confirmation prompts. The configuration file is now reloaded, and you can change the password.

Step 6

Enter global configuration mode and change the enable password.


Device# configure terminal
Device(config)# enable secret password


Step 7

Return to privileged EXEC mode:

Device(config)# exit
Device# 


Step 8

Write the running configuration to the startup configuration file.


Device# copy running-config startup-config     


Step 9

Confirm that manual boot mode is enabled.


Device# show boot
 
 BOOT variable = flash:packages.conf;
 Manual Boot = yes
 Enable Break = yes


Step 10

Reload the device.


Device# reload


Step 11

Set the SWITCH_IGNORE_STARTUP_CFG parameter to 0.


Device(config)# no system ignore startupconfig switch all
Device(config)# end
Device# write memory


Step 12

Boot the device with the packages.conf file from flash.


Device: boot flash:packages.conf


Step 13

After the device boots up, disable manual boot on the device.


Device(config)# no boot manual



Procedure with Password Recovery Disabled

If the password-recovery mechanism is disabled, this message appears:


The password-recovery mechanism has been triggered, but
is currently disabled.  Access to the boot loader prompt
through the password-recovery mechanism is disallowed at
this point.  However, if you agree to let the system be
reset back to the default system configuration, access
to the boot loader prompt can still be allowed.

Would you like to reset the system back to the default configuration (y/n)?



Caution

Returning the device to the default configuration results in the loss of all existing configurations. We recommend that you contact your system administrator to verify if there are backup device and VLAN configuration files.


  • If you enter y (yes), the configuration file in flash memory and the VLAN database file are deleted. When the default configuration loads, you can reset the password.

Procedure

Step 1

Choose to continue with password recovery and delete the existing configuration:


Would you like to reset the system back to the default configuration (y/n)? Y 


Step 2

Display the contents of flash memory:

Device: dir flash:



The device file system appears.


Directory of flash:/
.
.
.i'
15494  drwx        4096   Jan 1 2000 00:20:20 +00:00  kirch
15508  -rw-   258065648   Sep 4 2013 14:19:03 +00:00  cat9k_caa-universalk9.SSA.03.12.02.EZP.150-12.02.EZP.150-12.02.EZP.bin
162196684
Step 3

Boot up the system:

Device: boot


You are prompted to start the setup program. To continue with password recovery, enter N at the prompt:


Continue with the configuration dialog? [yes/no]: N


Step 4

At the device prompt, enter privileged EXEC mode:

Device> enable


Step 5

Enter global configuration mode:

Device# configure terminal


Step 6

Change the password:

Device(config)# enable secret password


The secret password can be from 1 to 25 alphanumeric characters, can start with a number, is case sensitive, and allows spaces but ignores leading spaces.

Step 7

Return to privileged EXEC mode:

Device(config)# exit
Device# 


Step 8

Write the running configuration to the startup configuration file:


Device# copy running-config startup-config


The new password is now in the startup configuration.

Step 9

You must now reconfigure the device. If the system administrator has the backup device and VLAN configuration files available, you should use those.


Preventing Autonegotiation Mismatches

The IEEE 802.3ab autonegotiation protocol manages the device settings for speed (10 Mb/s, 100 Mb/s, and 1000 Mb/s, excluding SFP module ports) and duplex (half or full). There are situations when this protocol can incorrectly align these settings, reducing performance. A mismatch occurs under these circumstances:

  • A manually set speed or duplex parameter is different from the manually set speed or duplex parameter on the connected port.

  • A port is set to autonegotiate, and the connected port is set to full duplex with no autonegotiation.

To maximize the device performance and ensure a link, follow one of these guidelines when changing the settings for duplex and speed:

  • Let both ports autonegotiate both speed and duplex.

  • Manually set the speed and duplex parameters for the ports on both ends of the connection.


Note

If a remote device does not autonegotiate, configure the duplex settings on the two ports to match. The speed parameter can adjust itself even if the connected port does not autonegotiate.


Troubleshooting SFP Module Security and Identification

Cisco small form-factor pluggable (SFP) modules have a serial EEPROM that contains the module serial number, the vendor name and ID, a unique security code, and cyclic redundancy check (CRC). When an SFP module is inserted in the device, the device software reads the EEPROM to verify the serial number, vendor name and vendor ID, and recompute the security code and CRC. If the serial number, the vendor name or vendor ID, the security code, or CRC is invalid, the software generates a security error message and places the interface in an error-disabled state.


Note

The security error message references the GBIC_SECURITY facility. The device supports SFP modules and does not support GBIC modules. Although the error message text refers to GBIC interfaces and modules, the security messages actually refer to the SFP modules and module interfaces.


If you are using a non-Cisco SFP module, remove the SFP module from the device, and replace it with a Cisco module. After inserting a Cisco SFP module, use the errdisable recovery cause gbic-invalid global configuration command to verify the port status, and enter a time interval for recovering from the error-disabled state. After the elapsed interval, the device brings the interface out of the error-disabled state and retries the operation. For more information about the errdisable recovery command, see the command reference for this release.

If the module is identified as a Cisco SFP module, but the system is unable to read vendor-data information to verify its accuracy, an SFP module error message is generated. In this case, you should remove and reinsert the SFP module. If it continues to fail, the SFP module might be defective.

Executing Ping

If you attempt to ping a host in a different IP subnetwork, you must define a static route to the network or have IP routing configured to route between those subnets.

IP routing is disabled by default on all devices.


Note

Though other protocol keywords are available with the ping command, they are not supported in this release.


Use this command to ping another device on the network from the device:

Command

Purpose

ping ip host | address


Device# ping 172.20.52.3


Pings a remote host through IP or by supplying the hostname or network address.

Monitoring Temperature

The Device monitors the temperature conditions and uses the temperature information to control the fans.

Use the show env temperature status privileged EXEC command to display the temperature value, state, and thresholds. The temperature value is the temperature in the Device(not the external temperature).You can configure only the yellow threshold level (in Celsius) by using the system env temperature threshold yellow value global configuration command to set the difference between the yellow and red thresholds. You cannot configure the green or red thresholds. For more information, see the command reference for this release.

Monitoring the Physical Path

You can monitor the physical path that a packet takes from a source device to a destination device by using one of these privileged EXEC commands:

Table 1. Monitoring the Physical Path
Command Purpose

tracetroute mac [interface interface-id] {source-mac-address} [interface interface-id] {destination-mac-address} [vlan vlan-id] [detail]

Displays the Layer 2 path taken by the packets from the specified source MAC address to the specified destination MAC address.

tracetroute mac ip {source-ip-address | source-hostname}{destination-ip-address | destination-hostname} [detail]

Displays the Layer 2 path taken by the packets from the specified source IP address or hostname to the specified destination IP address or hostname.

Executing IP Traceroute


Note

Though other protocol keywords are available with the traceroute privileged EXEC command, they are not supported in this release.


Command

Purpose

traceroute ip host

Device# traceroute ip 192.51.100.1


Traces the path that packets take through the network.

Redirecting Debug and Error Message Output

By default, the network server sends the output from debug commands and system error messages to the console. If you use this default, you can use a virtual terminal connection to monitor debug output instead of connecting to the console port or the Ethernet management port.

Possible destinations include the console, virtual terminals, internal buffer, and UNIX hosts running a syslog server. The syslog format is compatible with 4.3 Berkeley Standard Distribution (BSD) UNIX and its derivatives.


Note

Be aware that the debugging destination you use affects system overhead. When you log messages to the console, very high overhead occurs. When you log messages to a virtual terminal, less overhead occurs. Logging messages to a syslog server produces even less, and logging to an internal buffer produces the least overhead of any method.

For more information about system message logging, see Configuring System Message Logging.


Using the show platform forward Command

The output from the show platform forward privileged EXEC command provides some useful information about the forwarding results if a packet entering an interface is sent through the system. Depending upon the parameters entered about the packet, the output provides lookup table results and port maps used to calculate forwarding destinations, bitmaps, and egress information.

Most of the information in the output from the command is useful mainly for technical support personnel, who have access to detailed information about the device application-specific integrated circuits (ASICs). However, packet forwarding information can also be helpful in troubleshooting.

Using the show debug command

The show debug command is entered in privileged EXEC mode. This command displays all debug options available on the switch.

To view all conditional debug options run the command show debug condition The commands can be listed by selecting either a condition identifier <1-1000> or all conditions.

To disable debugging, use the no debug all command.


Caution

Because debugging output is assigned high priority in the CPU process, it can render the system unusable. For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions with Cisco technical support staff. Moreover, it is best to use debug commands during periods of lower network traffic and fewer users. Debugging during these periods decreases the likelihood that increased debug command processing overhead will affect system use.


Configuring OBFL


Caution

We recommend that you do not disable OBFL and that you do not remove the data stored in the flash memory.


  • To enable OBFL, use the hw-switch switch [switch-number] logging onboard [message level level] global configuration command. On switches, the range for switch-number is from 1 to 9. Use the message level level parameter to specify the severity of the hardware-related messages that the switch generates and stores in the flash memory.

    The following applies to the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches. To enable OBFL, use the hw-switch switch [module-number] logging onboard {application-name } global configuration command.

  • To copy the OBFL data to the local network or a specific file system, use the copy onboard switch switch-number url url-destination privileged EXEC command.

    Note

    This does not apply to the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches.


  • To disable OBFL, use the no hw-switch switch [switch-number] logging onboard [message level] global configuration command.

    The following applies to the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches. To disable OBFL, use the no hw-module slot [module-number] logging onboard {application-name } global configuration command.

  • To clear all the OBFL data in the flash memory except for the uptime and CLI command information, use the clear onboard switch switch-number privileged EXEC command.

    The following applies to the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches. To disable OBFL, use the no hw-module slot [module-number] logging onboard {application-name } global configuration command.

    To clear all the OBFL data in the flash memory except for the uptime, use the clear logging onboard RP active {application } privileged EXEC command.

  • The following does not apply to the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches. To disable OBFL, use the no hw-module slot [module-number] logging onboard {application-name } global configuration command.

    You can enable or disable OBFL on a member switch from the active switch.

For more information about the commands in this section, see the command reference for this release.

Verifying Troubleshooting of the Software Configuration

Displaying OBFL Information

Table 2. Commands for Displaying OBFL Information - Cisco Catalyst 9500 Series Switches - High Performance

Command

Purpose

show logging onboard RP active clilog [ continuous | detail | summary ]

Device# show logging onboard RP active clilog


Displays the OBFL CLI commands that were entered on a module.

show logging onboard RP active environment [ continuous | detail | summary ]

Device# show logging onboard RP active environmentt


Displays the UDI information for a module and for all the connected FRU devices: the PID, the VID, and the serial number.

show logging onboard RP active message [ continuous | detail | summary ]

Device# show logging onboard RP active message


Displays the hardware-related messages generated by a module.

show logging onboard RP active counter [ continuous | detail | summary ]

Device# show logging onboard RP active counter


Displays the counter information on a module.

show logging onboard RP active temperature [ continuous | detail | summary ]

Device# show logging onboard RP active temperature


Displays the temperature information of a module.

show logging onboard RP active uptime [ continuous | detail | summary ]

Device# show logging onboard RP active uptime


Displays the time when a module start, the reason the module restart, and the length of time that the module have been running since they last restarted.

show logging onboard RP active voltage [ continuous | detail | summary ]

Device# show logging onboard RP active voltage


Displays the system voltages of a module.

show logging onboard RP active status [ continuous | detail | summary ]

Device# show logging onboard RP active status


Displays the status of each OBFL application of a module.

Table 3. Commands for Displaying OBFL Information

Command

Purpose

show onboard switch switch-number clilog

Device# show onboard switch 1 clilog


Displays the OBFL CLI commands that were entered on a standalone switch or the specified stack members.

show onboard switch switch-number environment

Device# show onboard switch 1 environment


Displays the UDI information for a standalone switch or the specified stack members and for all the connected FRU devices: the PID, the VID, and the serial number.

show onboard switch switch-number message

Device# show onboard switch 1 message


Displays the hardware-related messages generated by a standalone switch or the specified stack members.

show onboard switch switch-number counter

Device# show onboard switch 1 counter


Displays the counter information on a standalone switch or the specified stack members.

show onboard switch switch-number temperature

Device# show onboard switch 1 temperature


Displays the temperature of a standalone switch or the specified switch stack members.

show onboard switch switch-number uptime

Device# show onboard switch 1 uptime


Displays the time when a standalone switch or the specified stack members start, the reason the standalone switch or specified stack members restart, and the length of time that the standalone switch or specified stack members have been running since they last restarted.

show onboard switch switch-number voltage

Device# show onboard switch 1 voltage


Displays the system voltages of a standalone switch or the specified stack members.

show onboard switch switch-number status

Device# show onboard switch 1 status

Displays the status of a standalone switch or the specified stack members.

Example: Verifying the Problem and Cause for High CPU Utilization

To determine if high CPU utilization is a problem, enter the show processes cpu sorted privileged EXEC command. Note the underlined information in the first line of the output example.


Device# show processes cpu sorted
CPU utilization for five seconds: 8%/0%; one minute: 7%; five minutes: 8%
PID Runtime(ms) Invoked uSecs 5Sec 1Min 5Min TTY Process 
309 42289103 752750 56180 1.75% 1.20% 1.22% 0 RIP Timers 
140 8820183 4942081 1784 0.63% 0.37% 0.30% 0 HRPC qos request 
100 3427318 16150534 212 0.47% 0.14% 0.11% 0 HRPC pm-counters 
192 3093252 14081112 219 0.31% 0.14% 0.11% 0 Spanning Tree 
143 8 37 216 0.15% 0.01% 0.00% 0 Exec 
...
<output truncated>


This example shows normal CPU utilization. The output shows that utilization for the last 5 seconds is 8%/0%, which has this meaning:

  • The total CPU utilization is 8 percent, including both time running Cisco IOS processes and time spent handling interrupts.

  • The time spent handling interrupts is zero percent.

Table 4. Troubleshooting CPU Utilization Problems

Type of Problem

Cause

Corrective Action

Interrupt percentage value is almost as high as total CPU utilization value.

The CPU is receiving too many packets from the network.

Determine the source of the network packet. Stop the flow, or change the switch configuration. See the section on “Analyzing Network Traffic.”

Total CPU utilization is greater than 50% with minimal time spent on interrupts.

One or more Cisco IOS process is consuming too much CPU time. This is usually triggered by an event that activated the process.

Identify the unusual event, and troubleshoot the root cause. See the section on “Debugging Active Processes.”

Scenarios for Troubleshooting the Software Configuration

Scenarios to Troubleshoot Power over Ethernet (PoE)

Table 5. Power over Ethernet Troubleshooting Scenarios

Symptom or Problem

Possible Cause and Solution

Only one port does not have PoE.

Trouble is on only one switch port. PoE and non-PoE devices do not work on this port, but do on other ports.

Verify that the powered device works on another PoE port.

Use the show run , or show interface status user EXEC commands to verify that the port is not shut down or error-disabled.

Note 

Most switches turn off port power when the port is shut down, even though the IEEE specifications make this optional.

Verify that power inline never is not configured on that interface or port.

Verify that the Ethernet cable from the powered device to the switch port is good: Connect a known good non-PoE Ethernet device to the Ethernet cable, and make sure that the powered device establishes a link and exchanges traffic with another host.

Note 

Cisco powered device works only with straight cable and not with crossover one.

Verify that the total cable length from the switch front panel to the powered device is not more than 100 meters.

Disconnect the Ethernet cable from the switch port. Use a short Ethernet cable to connect a known good Ethernet device directly to this port on the switch front panel (not on a patch panel). Verify that it can establish an Ethernet link and exchange traffic with another host, or ping the port VLAN SVI. Next, connect a powered device to this port, and verify that it powers on.

If a powered device does not power on when connected with a patch cord to the switch port, compare the total number of connected powered devices to the switch power budget (available PoE). Use the show power inline command to verify the amount of available power.

No PoE on all ports or a group of ports.

Trouble is on all switch ports. Nonpowered Ethernet devices cannot establish an Ethernet link on any port, and PoE devices do not power on.

If there is a continuous, intermittent, or reoccurring alarm related to power, replace the power supply if possible it is a field-replaceable unit. Otherwise, replace the switch.

If the problem is on a consecutive group of ports but not all ports, the power supply is probably not defective, and the problem could be related to PoE regulators in the switch.

Use the show log privileged EXEC command to review alarms or system messages that previously reported PoE conditions or status changes.

If there are no alarms, use the show interface status command to verify that the ports are not shut down or error-disabled. If ports are error-disabled, use the shut and no shut interface configuration commands to reenable the ports.

Use the show env power and show power inline privileged EXEC commands to review the PoE status and power budget (available PoE).

Review the running configuration to verify that power inline never is not configured on the ports.

Connect a nonpowered Ethernet device directly to a switch port. Use only a short patch cord. Do not use the existing distribution cables. Enter the shut and no shut interface configuration commands, and verify that an Ethernet link is established. If this connection is good, use a short patch cord to connect a powered device to this port and verify that it powers on. If the device powers on, verify that all intermediate patch panels are correctly connected.

Disconnect all but one of the Ethernet cables from switch ports. Using a short patch cord, connect a powered device to only one PoE port. Verify the powered device does not require more power than can be delivered by the switch port.

Use the show power inline privileged EXEC command to verify that the powered device can receive power when the port is not shut down. Alternatively, watch the powered device to verify that it powers on.

If a powered device can power on when only one powered device is connected to the switch, enter the shut and no shut interface configuration commands on the remaining ports, and then reconnect the Ethernet cables one at a time to the switch PoE ports. Use the show interface status and show power inline privileged EXEC commands to monitor inline power statistics and port status.

If there is still no PoE at any port, a fuse might be open in the PoE section of the power supply. This normally produces an alarm. Check the log again for alarms reported earlier by system messages.

Cisco pre-standard powered device disconnects or resets.

After working normally, a Cisco phone intermittently reloads or disconnects from PoE.

Verify all electrical connections from the switch to the powered device. Any unreliable connection results in power interruptions and irregular powered device functioning such as erratic powered device disconnects and reloads.

Verify that the cable length is not more than 100 meters from the switch port to the powered device.

Notice what changes in the electrical environment at the switch location or what happens at the powered device when the disconnect occurs.

Notice whether any error messages appear at the same time a disconnect occurs. Use the show log privileged EXEC command to review error messages.

Verify that an IP phone is not losing access to the Call Manager immediately before the reload occurs. (It might be a network problem and not a PoE problem.)

Replace the powered device with a non-PoE device, and verify that the device works correctly. If a non-PoE device has link problems or a high error rate, the problem might be an unreliable cable connection between the switch port and the powered device.

IEEE 802.3af-compliant or IEEE 802.3at-compliant powered devices do not work on Cisco PoE switch.

A non-Cisco powered device is connected to a Cisco PoE switch, but never powers on or powers on and then quickly powers off. Non-PoE devices work normally.

Use the show power inline command to verify that the switch power budget (available PoE) is not depleted before or after the powered device is connected. Verify that sufficient power is available for the powered device type before you connect it.

Use the show interface status command to verify that the switch detects the connected powered device.

Use the show log command to review system messages that reported an overcurrent condition on the port. Identify the symptom precisely: Does the powered device initially power on, but then disconnect? If so, the problem might be an initial surge-in (or inrush) current that exceeds a current-limit threshold for the port.

Configuration Examples for Troubleshooting Software

Example: Pinging an IP Host

This example shows how to ping an IP host:


Device# ping 172.20.52.3

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echoes to 172.20.52.3, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 1/2/4 ms
Device#

Table 6. Ping Output Display Characters

Character

Description

!

Each exclamation point means receipt of a reply.

.

Each period means the network server timed out while waiting for a reply.

U

A destination unreachable error PDU was received.

C

A congestion experienced packet was received.

I

User interrupted test.

?

Unknown packet type.

&

Packet lifetime exceeded.

To end a ping session, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and release the Ctrl, Shift, and 6 keys and then press the X key.

Example: Performing a Traceroute to an IP Host

This example shows how to perform a traceroute to an IP host:


Device# traceroute ip 192.0.2.10

Type escape sequence to abort.
Tracing the route to 192.0.2.10

  1 192.0.2.1 0 msec 0 msec 4 msec
  2 192.0.2.203 12 msec 8 msec 0 msec
  3 192.0.2.100 4 msec 0 msec 0 msec
  4 192.0.2.10 0 msec 4 msec 0 msec
   


The display shows the hop count, the IP address of the router, and the round-trip time in milliseconds for each of the three probes that are sent.

Table 7. Traceroute Output Display Characters

Character

Description

*

The probe timed out.

?

Unknown packet type.

A

Administratively unreachable. Usually, this output means that an access list is blocking traffic.

H

Host unreachable.

N

Network unreachable.

P

Protocol unreachable.

Q

Source quench.

U

Port unreachable.

To end a trace in progress, enter the escape sequence (Ctrl-^ X by default). Simultaneously press and release the Ctrl, Shift, and 6 keys and then press the X key.

Additional References for Troubleshooting Software Configuration

Related Documents

Related Topic Document Title

For complete syntax and usage information for the commands used in this chapter.

Command Reference (Catalyst 9500 Series Switches)

Feature History for Troubleshooting Software Configuration

This table provides release and related information for features explained in this module.

These features are available on all releases subsequent to the one they were introduced in, unless noted otherwise.

Release

Feature

Feature Information

Cisco IOS XE Everest 16.5.1a

Troubleshooting Software Configuration

Troubleshooting software configuration describes how to identify and resolve software problems related to the Cisco IOS software on the switch.

Support for this feature was introduced only on the C9500-12Q, C9500-16X, C9500-24Q, C9500-40X models of the Cisco Catalyst 9500 Series Switches.

Cisco IOS XE Fuji 16.8.1a

Troubleshooting Software Configuration

Support for this feature was introduced only on the C9500-32C, C9500-32QC, C9500-48Y4C, and C9500-24Y4C models of the Cisco Catalyst 9500 Series Switches.

Cisco IOS XE Amsterdam 17.3.1

System-Report Files

The hostname is prepended to the system-report files. This makes the system-report files uniquely identifiable.

Use Cisco Feature Navigator to find information about platform and software image support. To access Cisco Feature Navigator, go to http://www.cisco.com/go/cfn.