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 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.
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.
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
Use the show interfaces command to display the status of all physical ports and logical interfaces on the router. describes messages in the command output.
The IR8340 supports the following interfaces:
GigabitEthernet 0/0/0 and 0/0/1
Cellular 0/4/0, Cellular 0/4/1, Cellular 0/5/0, and Cellular 0/5/1
msata
Several methods are available for upgrading software on the Cisco IR1840H Routers, including:
Copy the new software image to flash memory over the WAN interface when the existing Cisco IOS software image is in use.
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 boot the image from the TFTP server, the TFTP server must be on the same network as the router.
To change a configuration register, follow these steps:
|
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: |
|
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.
|
 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. |
To reset the router, follow these steps:
|
Step 1 |
If the break is disabled, turn off the router, wait for 5 seconds and turn the router back on. Within 60 seconds push the Reset button. The terminal displays the Rommon prompt. Example: |
|
Step 2 |
Enter confreg 0x2142 to ignore the running config. Example: |
|
Step 3 |
Sync the configuration changes with the sync command. Example: |
|
Step 4 |
Reset the router to apply confreg. The router will reload with the reset. Example: |
|
Step 5 |
Verify that the correct confreg 0x2142 was applied, and entern when asked if you want to change the configuration. Example: |
|
Step 6 |
Boot the image with the confreg 0x2142. Example: |
To recover a lost password, follow these steps. Refer to Reset the Router for details.
Reset the router.
Change the confreg to 0x2142.
Boot the router with confreg 0x2142 from Rommon.
If you used the reset button, add the license:
Router#config term
Router#license smart reservationNote |
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. |
To reset the configuration register value after you have recovered or reconfigured a password, follow these steps:
|
Step 1 |
Enter the configure terminal command to enter global configuration mode: Example: |
||
|
Step 2 |
Enter the configure register command and the original configuration register value that you recorded. Example: |
||
|
Step 3 |
Enter exit to exit configuration mode: Example:
|
||
|
Step 4 |
Reboot the router, and enter the recovered password. |
This task describes how to configure a transport map for a console port interface on the router.
| Command or Action | Purpose | |||
|---|---|---|---|---|
|
Step 1 |
enable Example: |
Enables privileged EXEC mode. Enter your password if prompted. |
||
|
Step 2 |
configure terminal Example: |
Enters global configuration mode. |
||
|
Step 3 |
transport-map type console transport-map-name Example: |
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: |
Specifies how a console connection will be handled using this transport map.
|
||
|
Step 5 |
(Optional) banner [diagnostic | wait] banner-message Example: |
(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.
|
||
|
Step 6 |
exit Example: |
Exits transport map configuration mode to re-enter global configuration mode. |
||
|
Step 7 |
transport type console console-line-number input transport-map-name Example: |
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. |
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 consolehandlerUse 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.
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.
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 :
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
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.
Feedback