Table Of Contents
Recuperar Imagen (XMODEM) de Switch Catalyst 2960Download Image: https://drive.google.com/file/d/13iaYLGaGRtr1G3OuLTiKl7HaxLpiElzJ/view?usp=sharing. Xmodem: —Obtain the file from a network machine by using the Xmodem protocol. We recommend using the archive download-sw and archive upload-sw privileged EXEC commands to download and upload software image. Describes how to archive (download and upload) software image files, which contain the system software, the Cisco IOS code. A simple and sweet video showing the IOS Image Recovery procedure via xMODEM.To view the full 800x600 resolution video please visit;http://www.freeccnaworkbo. Xmodem x/ymodem image download rommon 2 xmodem usage: xmodem -cyrx -c CRC-16 -y ymodem-batch protocol -r copy image to dram for launch -x do not launch on download completion. Cisco 2620 (MPC860) processor.
ROM Monitor
The ROM monitor firmware runs when the router is powered up or reset. The firmware helps to initialize the processor hardware and boot the operating system software. You can use the ROM monitor to perform certain configuration tasks, such as recovering a lost password or downloading software over the console port. If there is no Cisco IOS software image loaded on the router, the ROM monitor runs the router.
This appendix contains the following sections:
•Entering the ROM Monitor
•ROM Monitor Commands
•Command Descriptions
•Disaster Recovery with TFTP Download
•Configuration Register
•Console Download
•Debug Commands
•Exiting the ROM Monitor
Entering the ROM Monitor
To use the ROM monitor, you must be using a terminal or PC that is connected to the router over the console port.
Perform these steps to configure the router to boot up in ROM monitor mode the next time it is rebooted.
Purpose | ||
---|---|---|
Step 1 | enable | Enters privileged EXEC mode. Enter your password if prompted. |
Step 2 | configure terminal | Enters global configuration mode. |
Step 3 | config-reg 0x0 | Resets the configuration register. |
Step 4 | exit | Exits global configuration mode. |
Step 5 | reload | Reboots the router with the new configuration register value. The router remains in ROM monitor and does not boot the Cisco IOS software. As long as the configuration value is 0x0, you must manually boot the operating system from the console. See the boot command in the 'Command Descriptions' section in this appendix. After the router reboots, it is in ROM monitor mode. The number in the prompt increments with each new line. Note In ROM monitor mode, only the Fast Ethernet LAN interface FE0 is enabled and is available for communication, while the other three Fast Ethernet LAN interfaces (FE1, FE2, and FE3) are disabled. After the IOS software boots up, all of the four Fast Ethernet LAN interfaces are enabled. This feature is available if the ROM monitor version that is installed on your router is 12.3(8r)YI6 or later. |
Timesaver Break (system interrupt) is always enabled for 60 seconds after the router reboots, regardless of whether it is set to on or off in the configuration register. During this 60-second window, you can break to the ROM monitor prompt by pressing the Break key.
![Cisco xmodem download mac Cisco xmodem download mac](https://content.spiceworksstatic.com/service.community/p/how_to_step_attachments/0000127930/5ba55a6f/attached_file/d9169477c0a1f71d2581e218d9eabefb1ecc1f6302855fcaea1af871a9025535_GetImage.png)
ROM Monitor Commands
Enter ? or help at the ROM monitor prompt to display a list of available commands and options, as follows:
Commands are case sensitive. You can halt any command by pressing the Break key on a terminal. If you are using a PC, most terminal emulation programs halt a command when you press the Ctrl and the Break keys at the same time. If you are using another type of terminal emulator or terminal emulation software, see the documentation for that product for information on how to send a Break command.
Command Descriptions
Table C-1 describes the most commonly used ROM monitor commands.
Description | |
---|---|
help or ? | Displays a summary of all available ROM monitor commands. |
-? | Displays information about command syntax; for example: The output for this command is slightly different for the xmodem download command: |
reset or i | Resets and initializes the router, similar to a power up. |
dirdevice: | Lists the files on the named device;for example, flash memory files: |
For more information about the ROM monitor boot commands, see the . | |
b | Boots the first image in flash memory. |
bflash:[filename] | Attempts to boot the image directly from the first partition of flash memory. If you do not enter a filename, this command will boot this first image in flash memory. |
Disaster Recovery with TFTP Download
The standard way to load new software on your router is to use the copy tftp flash privileged EXEC command from the Cisco IOS software command-line interface (CLI). However, if the router is unable to boot Cisco IOS software, you can load new software while in ROM monitor mode.
This section describes how to load a Cisco IOS software image from a remote TFTP server to the router flash memory. Use the tftpdnld command only for disaster recovery, because it erases all existing data in flash memory before downloading a new software image to the router.
TFTP Download Command Variables
This section describes the system variables that can be set in ROM monitor mode and that are used during the TFTP download process. There are both required variables and optional variables.
Note The commands described in this section are case sensitive and must be entered exactly as shown.
Required Variables
These variables must be set with these commands before you use the tftpdnld command:
Command | |
IP address of the router. | IP_ADDRESS= ip_address |
Subnet mask of the router. | IP_SUBNET_MASK=ip_address |
IP address of the default gateway of the router. | DEFAULT_GATEWAY=ip_address |
IP address of the TFTP server from which the software will be downloaded. | TFTP_SERVER=ip_address |
Name of the file that will be downloaded to the router. | TFTP_FILE=filename |
Optional Variables
These variables can be set with these commands before using the tftpdnld command:
Command | |
Configures how the router displays file download progress. 0—No progress is displayed. 1—Exclamation points (!!!) are displayed to indicate file download progress. This is the default setting. 2—Detailed progress is displayed during the file download process; for example: •Initializing interface. •Interface link state up. •ARPing for 1.4.0.1 •ARP reply for 1.4.0.1 received. MAC address 00:00:0c:07:ac:01 | TFTP_VERBOSE=setting |
Number of times the router attempts ARP and TFTP download. The default is 7. | TFTP_RETRY_COUNT=retry_times |
Length of time, in seconds, before the download process times out. The default is 2,400 seconds (40 minutes). | TFTP_TIMEOUT=time |
Whether or not the router performs a checksum test on the downloaded image: 1—Checksum test is performed. 0—No checksum test is performed. | TFTP_CHECKSUM=setting |
Using the TFTP Download Command
Perform these steps in ROM monitor mode to download a file through TFTP.
Step 1 Use the appropriate commands to enter all the required variables and any optional variables described in preceding sections.
Step 2 Enter the tftpdnld command as follows:
Note The -r variable is optional. Entering this variable downloads and boots the new software but does not save the software to flash memory. You can then use the image that is in flash memory the next time you enter the reload command.
You will see output similar to the following:
Step 3 If you are sure that you want to continue, enter y in response to the question in the output:
The router begins to download the new file.
If you mistakenly entered yes, you can enter Ctrl-C or Break to stop the transfer before the flash memory is erased.
Configuration Register
The virtual configuration register is in nonvolatile RAM (NVRAM) and has the same functionality as other Cisco routers. You can view or modify the virtual configuration register from either the ROM monitor or the operating system software. Within the ROM monitor, you can change the configuration register by entering the register value in hexadecimal format, or by allowing the ROM monitor to prompt you for the setting of each bit.
Changing the Configuration Register Manually
To change the virtual configuration register from the ROM monitor manually, enter the confreg command followed by the new value of the register in hexadecimal format, as shown in the following example:
The value is always interpreted as hexadecimal. The new virtual configuration register value is written into NVRAM but does not take effect until you reset or reboot the router.
Changing the Configuration Register Using Prompts
Entering the confreg command without an argument displays the contents of the virtual configuration register and a prompt to alter the contents by describing the meaning of each bit.
In either case, the new virtual configuration register value is written into NVRAM but does not take effect until you reset or reboot the router.
The following display shows an example of entering the confreg command:
Console Download
You can use console download, a ROM monitor function, to download either a software image or a configuration file over the router console port. After download, the file is either saved to the mini-flash memory module or to main memory for execution (image files only).
Use console download when you do not have access to a TFTP server.
Note If you want to download a software image or a configuration file to the router over the console port, you must use the ROM monitor dnld command.
Note If you are using a PC to download a Cisco IOS image over the router console port at 115,200 bps, ensure that the PC serial port is using a 16550 universal asynchronous transmitter/receiver (UART). If the PC serial port is not using a 16550 UART, we recommend using a speed of 38,400 bps or less when downloading a Cisco IOS image over the console port.
Command Description
Download game pc motogp 2017. The following are the syntax and descriptions for the xmodem console download command:
xmodem [-cyrx]destination_file_name
c | Optional. Performs the download using 16-bit cyclic redundancy check (CRC-16) error checking to validate packets. Default is 8-bit CRC. |
y | Optional. Sets the router to perform the download using Ymodem protocol. The default is Xmodem protocol. The protocols differ as follows: •Xmodem supports a 128-block transfer size. Ymodem supports a 1024-block transfer size. •Ymodem uses CRC-16 error checking to validate each packet. Depending on the device that the software is being downloaded from, this function might not be supported by Xmodem. |
r | Optional. Image is loaded into DRAM for execution. The default is to load the image into flash memory. |
x | Optional. Image is loaded into DRAM without being executed. |
destination_file_name | Name of the system image file or the system configuration file. In order for the router to recognize it, the name of the configuration file must be router_confg. |
Follow these steps to run Xmodem:
Step 1 Move the image file to the local drive where Xmodem will execute.
Step 2 Enter the xmodem command.
Error Reporting
Because the ROM monitor console download uses the console to perform the data transfer, when an error occurs during a data transfer, error messages are only displayed on the console once the data transfer is terminated.
If you have changed the baud rate from the default rate, the error message is followed by a message telling you to restore the terminal to the baud rate specified in the configuration register.
Debug Commands
Most ROM monitor debugging commands are functional only when Cisco IOS software has crashed or is halted. If you enter a debugging command and Cisco IOS crash information is not available, you see the following error message:
The following are ROM monitor debugging commands:
•stack or k—Produces a stack trace; for example:
Cisco Xmodem Download
•context—Displays processor context; for example:
•frame—Displays an individual stack frame.
•sysret—Displays return information from the last booted system image. This information includes the reason for terminating the image, a stack dump of up to eight frames, and, if an exception is involved, the address where the exception occurred; for example:
•meminfo—Displays size in bytes, starting address, available range of main memory, the starting point and size of packet memory, and size of NVRAM; for example:
Exiting the ROM Monitor
You must set the configuration register to a value from 0x2 to 0xF for the router to boot a Cisco IOS image from flash memory upon startup or reloading.
The following example shows how to reset the configuration register and cause the router to boot a Cisco IOS image stored in flash memory:
You must reset or power cycle for new config to take effect:
The router will boot the Cisco IOS image in flash memory. The configuration register will change to 0x2101 the next time the router is reset or power cycled.
Last week at work now, so been rushing to get things sorted out. I have still been doing a bit of study and planing some more ROUTE posts, but with a broken down car and house sale looking like its falling through haven’t had time to do any actually real posting.
However I came across something today, that I have known about for a while but never really used much. One of the things every one seems to love about CISCO is the fact you can simple copy and past configurations in to the terminal emulator window. And this is indeed great. set up one interface, copy the config to notepad, update it as you wish and past it back in… A real time saver and why we all love CISCO more than Microsoft ;).
In the past this is also how I have always copied backed up configurations on to a new switch/router. Simply open the saved config in notepad. Ctrl-A to select it all, copy and paste to the device. However I was doing this today and hit an issues. With really large configuration files (500+ lines of configuration), I was watching the console windows and could see it was skipping some of the configuration when doing this connected through the serial port. I could see that while things like VLAN’s where being created and the device was pausing, the following lines would some times get lost or corrupted. Now while if you only have a small size configuration file this is not an issue as it is quite easy to check, hundreds of lines become very hard to validate.
I found the best way around this problem was to set up the device with an IP address, put it on a limited access network that has a TFTP sever and copy over the configuration file, either to the startup-config or running-config. This works fine but it is a bit of a hassle going to all that trouble and it means you have to connect the switch to the network, so you have to be very careful with things like VTP and spanning tree. What I really wanted was a way to send the configuration file through the console port.
This made me think of how to recover a corrupted IOS image (which you can fine in the tips and tricks link above). Where boot the device in to ROMmon mode, and then copy the IOS over using the xmodem protocol. Almost all the mainstream terminual emulators have this built in, and while for recovering the IOS you need to increase the baud speed of the console port to speed up the copying process, as the configuration file is only 20-30kb max for most people, the standard speed will move that across in a few seconds.
So then it is just a case of knowing the command to achieve the goal, and I was happy to see it is as simple as it should be. On the device simple type the following from the enable prompt.
router#copy xmodem: startup-config
That’s it, no file names or anything, the device will now wait to receive the file(if you do not start the transfer within a few minutes the device will time out waiting). Then in your terminal emulation program start the transfer. In teraterm it is under the file menu, while secure CRT has a whole menu structure dedicated to various methods to transfer files. Simple chose the xmodem protocol (I found selecting the 1K option was more reliable), and browse to the configuration file, and away it goes. A few moments later the configuration will be on the device (#show Flash: to confirm), and a reboot will have it all up and running.
To me this is a far more reliable way of copying large configurations across, and allows you to easily set up the device from any client, this can be very useful if you are out on site and don’t have access to a limited access network, or the TFTP server to use to copy the files via TFTP or FTP using the network.
DevilWAH.
Cisco Xmodem Download Mac
PS. Some older routers don’t seem to like you copying from xmodem to nvram, or require you to give a source file name. But you can still achieve the same by copying the file to Flash: .
PPS. Although I prefer the xmodem method, you can improve the reliability of the copy/paste method by increasing the line/character delay in you terminal emulation program. A 5msec delay per character seems to help, although with a 1000+ lines of configuration you may get from a complex configuration, you may find the paste takes a little time, and you may still get errors.