Troubleshooting

This section contains the following:

Troubleshooting

This section describes the troubleshooting scenarios.

Before troubleshooting a software problem, you must connect a PC to the router via the console port. With a connected PC, you can view status messages from the router and enter commands to troubleshoot a problem.

You can also remotely access the interface by using Telnet. The Telnet option assumes that the interface is up and running.

Understanding Diagnostic Mode

The router boots up or accesses diagnostic mode in the following scenarios:

  • The IOS process or processes fail, in some scenarios. In other scenarios, the system resets when the IOS process or processes fail.

  • A user-configured access policy was configured using the transport-map command that directs the user into the diagnostic mode.

  • A send break signal (Ctrl-C or Ctrl-Shift-6) was entered while accessing the router, and the router was configured to enter diagnostic mode when a break signal was sent.

In the diagnostic mode, a subset of the commands that are available in user EXEC mode are made available to the users. Among other things, these commands can be used to:

  • Inspect various states on the router, including the IOS state.

  • Replace or roll back the configuration.

  • Provide methods of restarting the IOS or other processes.

  • Reboot hardware, such as the entire router, a module, or possibly other hardware components.

  • Transfer files into or off of the router using remote access methods such as FTP, TFTP, and SCP.

The diagnostic mode provides a more comprehensive user interface for troubleshooting than previous routers, which relied on limited access methods during failures, such as ROMMON, to diagnose and troubleshoot Cisco IOS problems. The diagnostic mode commands can work when the Cisco IOS process is not working properly. These commands are also available in privileged EXEC mode on the router when the router is working normally.

Before Contacting Cisco or Your Reseller

If you cannot locate the source of a problem, contact your local reseller for advice. Before you call, you should have the following information ready:

  • Chassis type and serial number

  • Maintenance agreement or warranty information

  • Type of software and version number

  • Date you received the hardware

  • Brief description of the problem

  • Brief description of the steps you have taken to isolate the problem

show interfaces Troubleshooting Command

Use the show interfaces command to display the status of all physical ports and logical interfaces on the router. Describe messages in the command output.

The IR1800 supports the following interfaces:

GigabitEthernet 0/0/0

GigabitEthernet 0/1/0 to 0/1/3

Cellular 0/4/0, 0/4/1, 0/5/0, and 0/5/1

Async 0/2/0 and 0/2/1

usbflash0:

msata

Alarm input alarm contact 0

Software Upgrade Methods

Several methods are available for upgrading software on the Cisco IR1800 Routers, including:

  • Copy the new software image to flash memory over LAN or WAN when the existing Cisco IOS software image is in use.

  • Copy the new software image to flash memory over the LAN while the boot image (ROM monitor) is operating.

  • Copy the new software image over the console port while in ROM monitor mode.

  • From ROM monitor mode, boot the router from a software image that is loaded on a TFTP server. To use this method, the TFTP server must be on the same LAN as the router.

Change the Configuration Register

To change a configuration register, follow these steps:

Procedure

Step 1

Connect a PC to the CONSOLE port on the router.

Step 2

At the privileged EXEC prompt (router_name #), enter the show version command to display the existing configuration register value (shown in bold at the bottom of this output example):

Example:


Router# show version
Cisco IOS XE Software, Version 17.06.01prd23
Cisco IOS Software [Bengaluru], ISR Software (ARMV8EL_LINUX_IOSD-UNIVERSALK9_IOT-M), Version 17.6.1prd23, RELEASE SOFTWARE (fc1)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2021 by Cisco Systems, Inc.
Compiled Tue 20-Jul-21 02:28 by mcpre


Cisco IOS-XE software, Copyright (c) 2005-2021 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.


ROM: 3.9(REL)

IR1833 uptime is 13 hours, 6 minutes
Uptime for this control processor is 13 hours, 9 minutes
System returned to ROM by Firmware Upgrade
System image file is "bootflash:ir1800-universalk9.17.06.01prd23.SPA.bin"
Last reload reason: Reload Command



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.


Technology Package License Information:

-----------------------------------------------------------------
Technology Type Technology-package Technology-package
Current Next Reboot
-----------------------------------------------------------------
Smart License Perpetual network-advantage network-advantage
Smart License Subscription None None

The current throughput level is 50000 kbps


Smart Licensing Status: Registration Not Applicable/Not Applicable

cisco IR1833-K9 (1RU) processor with 470123K/6147K bytes of memory.
Processor board ID FCW2447P0EB
Router operating mode: Autonomous
MCU bootloader version: 0x22
MCU application version: 0x4d
1 Virtual Ethernet interface
6 Gigabit Ethernet interfaces
2 Serial interfaces
1 terminal line
4 Cellular interfaces
32768K bytes of non-volatile configuration memory.
3988088K bytes of physical memory.
7475198K bytes of Bootflash at bootflash:.

Configuration register is 0x2102

Router#

Step 3

Record the setting of the configuration register.

Step 4

To enable the break setting (indicated by the value of bit 8 in the configuration register), enter the config-register <value> command from privileged EXEC mode.

  • Break enabled—Bit 8 is set to 0.

  • Break disabled (default setting)—Bit 8 is set to 1.

Configuring the Configuration Register for Autoboot


Note
Altering the configuration register is only for advanced troubleshooting and should only be done with guidance from Cisco support.

The configuration register can be used to change router behavior. This includes controlling how the router boots. Set the configuration register to 0x0 to boot into ROM, by using one of the following commands:

  • In Cisco IOS configuration mode, use the config-reg 0x0 command.

  • From the ROMMON prompt, use the confreg 0x0 command.


Note
Setting the configuration register to 0x2102 will set the router to autoboot the Cisco IOS XE software.

Reset the Router

To reset the router, follow these steps:

Procedure

Step 1

If break is disabled, turn the router off (O), wait 5 seconds, and turn it on (|) again. Within 60 seconds, press the Break key. The terminal displays the ROM monitor prompt.

Note

 
Some terminal keyboards have a key labeled Break . If your keyboard does not have a Break key, see the documentation that came with the terminal for instructions on how to send a break.

Step 2

Press break. The terminal displays the following prompt:

Example:


rommon 2>

Step 3

Enter confreg 0x2142 to reset the configuration register:

Example:


rommon 2> confreg 0x142

Step 4

Sync the configuration changes with sync command.

Example:


rommon 2>sync

Step 5

Initialize the router by entering the reload command:

Example:


rommon 2>reload

The router cycles its power, and the configuration register is set to 0x2142. The router uses the boot ROM system image, indicated by the system configuration dialog:

Example:


--- System Configuration Dialog ---

Step 6

Enter no in response to the prompts until the following message is displayed:

Example:


Press RETURN to get started!

Step 7

Press Return . The following prompt appears:

Example:


Router>

Step 8

Enter the enable command to enter enable mode. Configuration changes can be made only in enable mode:

Example:


Router> enable

The prompt changes to the privileged EXEC prompt:

Example:


Router#

Step 9

Enter the show startup-config command to display an enable password in the configuration file:

Example:


Router# show startup-config

What to do next

If you are recovering an enable password, do not perform the steps in the Reset the Password and Save Your Changes section. Instead, complete the password recovery process by performing the steps in the Reset the Configuration Register Value section.

If you are recovering an enable secret password, it is not displayed in the show startup-config command output. Complete the password recovery process by performing the steps in the Reset the Password and Save Your Changes section.

Recovering a Lost Password

To recover a lost enable or lost enable-secret password, refer to the following sections:

  1. Change the Configuration Register

  2. Reset the Router

  3. Reset the Password and Save your Changes (for lost enable secret passwords only)

  4. Reset the Configuration Register Value.

    5. If you have performed a write erase, or used the reset button, you will need to add the license. 

    IR1800#config term
IR1800#license smart reservation

Note
Any vlan interfaces will have to be recreated, and it is possible you may need to re-generate certs.

Note
Recovering a lost password is only possible when you are connected to the router through the console port. These procedures cannot be performed through a Telnet session.

Tip
See the “Hot Tips” section on Cisco.com for additional information on replacing enable secret passwords.

Reset the Password and Save Your Changes

To reset your password and save the changes, follow these steps:

Procedure

Step 1

Enter the configure terminal command to enter global configuration mode:

Example:


Router# configure terminal

Step 2

Enter the enable secret command to reset the enable secret password in the router:

Example:


Router(config)# enable secret 
password

Step 3

Enter exit to exit global configuration mode:

Example:


Router(config)# exit

Step 4

Save your configuration changes:

Example:


Router# copy running-config startup-config

Reset the Configuration Register Value

To reset the configuration register value after you have recovered or reconfigured a password, follow these steps:

Procedure

Step 1

Enter the configure terminal command to enter global configuration mode:

Example:


Router# configure terminal

Step 2

Enter the configure register command and the original configuration register value that you recorded.

Example:


Router(config)# config-reg 
value

Step 3

Enter exit to exit configuration mode:

Example:


Router(config)# exit

Note

 
To return to the configuration being used before you recovered the lost enable password, do not save the configuration changes before rebooting the router.

Step 4

Reboot the router, and enter the recovered password.

Configuring a Console Port Transport Map

This task describes how to configure a transport map for a console port interface on the router.

Procedure

  Command or Action Purpose

Step 1

enable

Example:


Router> enable

Enables privileged EXEC mode.

Enter your password if prompted.

Step 2

configure terminal

Example:


Router# configure terminal

Enters global configuration mode.

Step 3

transport-map type console transport-map-name

Example:


Router(config)# transport-map type console consolehandler

Creates and names a transport map for handling console connections, and enters transport map configuration mode.

Step 4

connection wait [allow [interruptible] | none [disconnect]]

Example:


Router(config-tmap)# connection wait none

Specifies how a console connection will be handled using this transport map.

  • allow interruptible—The console connection waits for a Cisco IOS VTY line to become available, and also allows users to enter diagnostic mode by interrupting a console connection that is waiting for a Cisco IOS VTY line to become available. This is the default setting.

    Note

     
    Users can interrupt a waiting connection by entering Ctrl-C or Ctrl-Shift-6.

  • none—The console connection immediately enters diagnostic mode.

Step 5

(Optional) banner [diagnostic | wait] banner-message

Example:


Router(config-tmap)# banner diagnostic X
Enter TEXT message. End with the character 'X'.
--Welcome to Diagnostic Mode--
X
Router(config-tmap)#

(Optional) Creates a banner message that will be seen by users entering diagnostic mode or waiting for the Cisco IOS VTY line because of the console transport map configuration.

  • diagnostic—Creates a banner message seen by users directed to diagnostic mode because of the console transport map configuration.

    Note

     
    Users can interrupt a waiting connection by entering Ctrl-C or Ctrl-Shift-6.

  • wait—Creates a banner message seen by users waiting for Cisco IOS VTY to become available.

  • banner-message—Banner message, which begins and ends with the same delimiting character.

Step 6

exit

Example:


Router(config-tmap)# exit

Exits transport map configuration mode to re-enter global configuration mode.

Step 7

transport type console console-line-number input transport-map-name

Example:


Router(config)# transport type console 0 input consolehandler

Applies the settings defined in the transport map to the console interface.

The transport-map-name for this command must match the transport-map-name defined in the transport-map type console command.

Examples

The following example shows how to create a transport map to set console port access policies and attach to console port 0: 

Router(config)# transport-map type console consolehandler
Router(config-tmap)# connection wait allow interruptible
Router(config-tmap)# banner diagnostic X
Enter TEXT message. End with the character 'X'.
--Welcome to diagnostic mode--
X
Router(config-tmap)# banner wait X
Enter TEXT message. End with the character 'X'.
Waiting for IOS vty line
X
Router(config-tmap)# exit
Router(config)# transport type console 0 input consolehandler

Viewing Console Port, SSH, and Telnet Handling Configurations

Use the following commands to view console port, SSH, and Telnet handling configurations:

  • show transport-map

  • show platform software configuration access policy

Use the show transport-map command to view transport map configurations.

show transport-map [all | name transport-map-name | type [console ]]

This command can be used either in user EXEC mode or privileged EXEC mode.

Example

The following example shows transport maps that are configured on the router: console port (consolehandler): 

Router# show transport-map all 
Transport Map:
Name: consolehandler Type: Console Transport

Connection:
Wait option: Wait Allow Interruptable Wait banner:

Waiting for the IOS CLI bshell banner:
Welcome to Diagnostic Mode


 
Router# show transport-map type console 
Transport Map:
Name: consolehandler
 

REVIEW DRAFT - CISCO CONFIDENTIAL

Type: Console Transport

Connection:
Wait option: Wait Allow Interruptable Wait banner:

Waiting for the IOS CLI Bshell banner:
Welcome to Diagnostic Mode

 
 
Router# show transport-map type persistent ssh 
Transport Map:
Name: consolehandler Type: Console Transport

Connection:
Wait option: Wait Allow Interruptable Wait banner:

Waiting for the IOS CLI Bshell banner:
Welcome to Diagnostic Mode

Use the show platform software configuration access policy command to view the current configurations for handling the incoming console port, SSH, and Telnet connections. The output of this command provides the current wait policy for each type of connection (Telnet, SSH, and console), as well as information on the currently configured banners.

Unlike the show transport-map command, the show platform software configuration access policy command is available in diagnostic mode so that it can be entered in scenarios where you need transport map configuration information, but cannot access the Cisco IOS CLI.

Example

The following example shows the show platform software configuration access policy command. 

Router# show platform software configuration access policy
The current access-policies

Method : telnet
Rule : wait with interrupt Shell banner:
Welcome to Diagnostic Mode

Wait banner :
Waiting for IOS Process

Method : ssh Rule : wait Shell banner: Wait banner :

Method : console
Rule : wait with interrupt Shell banner:
Wait banner :

Using the factory reset Commands

The factory reset commands are used to remove all the customer specific data on a router/switch that has been added. The data can be configuration, log files, boot variables, core files, and so on.

The factory-reset all command erases the bootflash, nvram, rommon variables, licenses, and logs.


Caution
Use of the factory reset command should not be done lightly. All customer configurations will be ddeleted and the platform will boot up as if new from the factory.

Note
factory-reset all does not work if IOS-XE is running in controller mode. Please refer to SDWAN configuration information. 
Router#factory-reset all 
The factory reset operation is irreversible for all operations. Are you sure? [confirm] *Enter*

*May 12 09:55:45.831: %SYS-5-RELOAD: Reload requested by Exec. Reload Reason: Factory Reset.

***Return to ROMMON Prompt

Boot Sequence after Factory Reset

Booting the image:

  • The bootloader attempts to boot “golden.bin” from the bootflash: partition

  • If no “golden.bin” is present, then boot the first image.

Loading the configuration:

  • IOS looks for “golden.cfg” file on nvram: partition and applies it upon booting.

  • If no “golden.cfg” is present on nvram: then IOS looks for “golden.cfg” file on bootflash: partition and applies it upon booting.

  • If no “golden.cfg” is present on bootflash: then configurations are erased and Software Configuration dialog is used.