Presentation is loading. Please wait.

Presentation is loading. Please wait.

1 Semester 2 Module 5 Managing Cisco IOS Software Yu da college of business James Chen

Similar presentations


Presentation on theme: "1 Semester 2 Module 5 Managing Cisco IOS Software Yu da college of business James Chen"— Presentation transcript:

1 1 Semester 2 Module 5 Managing Cisco IOS Software Yu da college of business James Chen ydjames@ydu.edu.tw

2 2 Outline Router Boot Sequence and Verification Managing the Cisco File System

3 3 Stages of the router power-on boot sequence The startup routines must do the following: Test the router hardware. Find and load the Cisco IOS software. Find and apply configuration statements, including protocol functions and interface addresses.

4 4

5 5 How a Cisco device locates and loads IOS The default source for Cisco IOS software depends on the hardware platform, but most commonly the router looks to the boot system commands saved in NVRAM. Cisco IOS software allows several alternatives to be used.

6 6 The settings in the configuration register enable the following alternatives: Global configuration mode boot system commands can be specified to enter fallback sources for the router to use in sequence. If NVRAM lacks boot system commands that the router can use, the system by default uses the Cisco IOS software in flash memory. If flash memory is empty, the router then attempts to use TFTP to load an IOS image from the network.

7 7

8 8 Using the boot system command The following examples show the use of multiple boot system commands to specify the fallback sequence for booting Cisco IOS software. Flash memory – A system image from flash memory can be loaded. Network server – In case flash memory becomes corrupted, a system image can be loaded from a TFTP server. ROM – If flash memory is corrupted and the network server fails to load the image, booting from ROM is the final bootstrap option in software.

9 9

10 10

11 11

12 12 Configuration register The order in which the router looks for system bootstrap information depends on the boot field setting in the configuration register. The default configuration register setting can be changed with the global configuration mode command config-register.

13 13 The configuration register is a 16-bit register in NVRAM. The lowest four bits of the configuration register form the boot field. To ensure that the upper 12 bits are not changed, first retrieve the current values of the configuration register using the show version command. Then use the config-register command, changing only the value of the last hexadecimal digit.

14 14 To change the boot field in the configuration register, follow these guidelines: To enter the ROM monitor mode, set the configuration register value to 0xnnn0, where nnn represents the previous value of the non-boot field digits. To configure the system to boot automatically from ROM, set the configuration register to 0xnnn1, where nnn represents the previous value of the non-boot field digits. To configure the system to use the boot system commands in NVRAM, set the configuration register to any value from 0xnnn2 to 0xnnnF, where nnn represents the previous value of the non-boot field digits.

15 15

16 16 Troubleshooting IOS boot failure In the event that the router does not boot properly, there are several things that could be wrong: Configuration file has missing or incorrect boot system statement Incorrect configuration register value Corrupted flash image Hardware failure

17 17 This boot system statement can force the router to boot from another image instead of the IOS in flash. To identify the boot image source, type the show version command and look for the line that identifies the image boot source.

18 18 An incorrect configuration register setting will prevent the IOS from loading from flash. The value in the configuration register tells the router where to get the IOS. This can be confirmed by using the show version command and looking at the last line for the configuration register.

19 19 If there is still a problem, the router may have a corrupted flash image file. If this is the case, an error message should be displayed during boot. That message may take one of several forms. Some examples are: open: read error...requested 0x4 bytes, got 0x0 trouble reading device magic number boot: cannot open "flash:" boot: cannot determine first file name on device "flash:"ú If the flash image is corrupt, a new IOS should be uploaded into the router.

20 20 If none of the above appears to be the problem, the router could have a hardware failure. If this is the case, the Cisco Technical Assistance (TAC) center should be contacted. Although hardware failures are rare, they do occur.

21 21 Outline Router Boot Sequence and Verification Managing the Cisco File System

22 22 IOS file system overview Routers and switches depend on software for their operation. The two types of software required are operating systems and configuration. Each of the software components is stored in memory as a separate file. These files are also stored in different types of memory.

23 23

24 24 Beginning with version 12 of the IOS, a single interface to all the file systems that a router uses is provided. This is referred to as the Cisco IOS File System (IFS). The IFS provides a single method to perform all the file system management that a router uses. This would include the flash memory file systems, the network file systems (TFTP, rcp, and FTP), and reading or writing data (such as NVRAM, the running configuration, ROM). The IFS uses a common set of prefixes to specify file system devices.

25 25

26 26 The IFS uses the URL convention to specify files on network devices and the network. The URL convention identifies the location of the configuration files following the colon as [[[//location]/directory]/filename]. The IFS also supports FTP file transfer.

27 27

28 28 IOS naming conventions To identify the different versions, Cisco has a naming convention for IOS files. This IOS naming convention uses different fields in the name. Among the fields are the hardware platform identification, the feature set identification, and the numerical release.

29 29 The first part of the Cisco IOS file name identifies the hardware platform for which this image is designed.

30 30 The second part of the IOS file name identifies the various features that this file contains. Each feature set contains a specific subset of Cisco IOS features. Examples of feature-set categories are: Basic – A basic feature set for the hardware platform, for example IP and IP/FW Plus – A basic feature set plus additional features such as IP Plus, IP/FW Plus, and Enterprise Plus Encryption – The addition of the 56-bit data encryption feature sets, such as Plus 56, to either a basic or plus feature set.

31 31 The third part of the file name indicates the file format. It specifies if the IOS is stored in flash in a compressed format and whether the IOS is relocatable. If the flash image is compressed, the IOS must be expanded during boot as it is copied to RAM. A relocatable image is copied from flash into RAM to run. A non-relocatable image is run directly from flash.

32 32 The fourth part of the file name identifies the release of the IOS. As Cisco develops newer versions of the IOS, the numerical version number increases.

33 33

34 34 Managing configuration files using TFTP In a Cisco router or switch, the active configuration is in RAM and the default location for the startup configuration is NVRAM. One of these backup copies of the configuration can be stored on a TFTP server. The copy running-config tftp command can be used to do this.

35 35 The steps for this process are listed below: Enter the command copy running-config tftp. At the prompt, enter the IP address of the TFTP server to store the configuration file. Enter the name to assign to the configuration file or accept the default name. Confirm the choices by typing yes each time.

36 36

37 37 Loading the backup configuration file from a TFTP server can restore the router configuration. The steps below outline this process: Enter the command copy tftp running-config. At the prompt, select a host or network configuration file. At the system prompt, enter the IP address of the TFTP server where the configuration file is located. At the system prompt, enter the name of the configuration file or accept the default name. Confirm the configuration filename and the server address that the system supplies.

38 38

39 39 Managing configuration files using copy and paste Another way to create a backup copy of the configuration is to capture the output of the show running-config command. This can be done from the terminal session by copying the output, pasting to a text file, then saving the text file.

40 40 Perform the following to capture the configuration using the text displayed on the HyperTerminal screen to a text file: 1. Select Transfer 2. Select Capture Text 3. Specify the name for the text file to capture the configuration 4. Select Start to start capturing text 5. Display the configuration to the screen by entering show running-config 6. Press the space bar when each "-More -" prompt appears 7. When the complete configuration has been displayed, stop the capture by: 8. Select Transfer 9. Select Capture Text 10. Select Stop

41 41

42 42 After the capture is complete, the configuration file needs to be edited to remove extra text. The lines that need to be deleted contain: show running-config Building configuration... Current configuration: - More - Any lines that appear after the word "End" At the end of each of the interface sections add the no shutdown command.

43 43 HyperTerminal can be used to restore a configuration. The clean backup of the configuration can be copied into the router. Enter router global configuration mode. From HyperTerminal, click on Transfer > Send Text File. Select the name of the file for the saved backup configuration. The lines of the file will be entered into the router as if they were being typed. Observe any errors. After the configuration is entered, press Ctrl-Z key to exit global configuration mode. Restore the startup configuration with copy running-config startup-config.

44 44

45 45 Managing IOS images using TFTP When a router first arrives, the IOS should be backed up. The IOS backup can be initiated from the privileged EXEC mode with the copy flash tftp command. The router will prompt the user to enter the IP address of the TFTP server.

46 46 When prompted for the filename of the IOS image on the server, the router may then prompt to erase flash. As the image is erased from flash, a series of “e’s” will appear to show the erase process. As each datagram of the IOS image file is downloaded, an “!” will be displayed.

47 47

48 48 Managing IOS images using Xmodem If the IOS image in flash has been erased or corrupted, the IOS may need to be restored from the ROM monitor mode (ROMmon). In many of the Cisco hardware architectures, the ROMmon mode is identified from the rommon 1 > prompt. The flash should be examined with the dir flash: command.

49 49 If an image is located that appears to be valid, an attempt should be made to boot from that image. This is done using boot flash: command. For example if the image name was “c2600- is-mz.121-5”, the command would be: rommon 1>boot flash:c2600-is-mz.121-5

50 50 If the router will not properly boot from the image or there is no IOS image, a new IOS will need to be downloaded. The IOS file may be recovered using either Xmodem to restore the image through the console, or downloading the image using TFTP from the ROMmon mode.

51 51 The IOS can be restored using the default console speed of 9600 bps. The baud rate can be changed to 115200 bps to speed up the download. The console speed can be changed from ROMmon mode using the confreg command. After entering the confreg command, the router will prompt for the various parameters that can be changed.

52 52

53 53 The Xmodem command can be used from the ROMmon mode to restore the IOS software image from the PC. The format of the command is xmodem -c image_file_name. For example, to restore an IOS image file with the name “c2600- is-mz.122-10a.bin”, type the command: xmodem -c c2600-is-mz.122-10a.bin The -c instructs the Xmodem process to use Cyclic Redundancy Check (CRC) for error checking during the download.

54 54

55 55 In HyperTerminal, select Transfer > Send File. Then in the Send File popup specify the image name/location, select Xmodem as the protocol, and start the transfer. Before restarting the router, the console speed needs to be set back to 9600 and the config register back to 0x2102. Enter the command config-register 0x2102 at the privileged EXEC prompt.

56 56

57 57 Environment variables The IOS can also be restored from a TFTP session. Downloading the image using TFTP from ROMmon is the fastest way to restore an IOS image to the router. This is done by setting environmental variables and then using the tftpdnld command.

58 58 The environmental variables provide a minimal configuration to allow for the TFTP of the IOS. The ROMmon TFTP transfer works only on the first LAN port so a simple set of IP parameters are set for this interface. To set a ROMmon environment variable, the variable name is typed, then the equal sign (=), and the value for the variable (VARIABLE_NAME=value). For example, to set the IP address to 10.0.0.1, type IP_ADDRESS=10.0.0.1 at the ROMmon prompt. Note: All variable names are case sensitive.

59 59 The minimum variables required to use tftpdnld are: IP_ADDRESS – The IP address on the LAN interface IP_SUBNET_MASK – The subnet mask for the LAN interface DEFAULT_GATEWAY – The default gateway for the LAN interface TFTP_SERVER – The IP address of the TFTP server TFTP_FILE – The IOS filename on the server

60 60

61 61

62 62 File system verification The show version command can be used to check the current image and the total amount of flash. The show flash command can also be used to verify the file system.


Download ppt "1 Semester 2 Module 5 Managing Cisco IOS Software Yu da college of business James Chen"

Similar presentations


Ads by Google