You are on page 1of 5

Resumen Procedimiento de actualizacin

plataforma cisco 7600


The Purpose of the Configuration Register
The configuration register can be used to change router behavior in several ways, such as:
how the router boots (into ROMmon, NetBoot)
options while booting (ignore configuration, disable boot messages)
console speed (baud rate for a terminal emulation session)
Note: If the baud rate is set different than the default rate, odd characters are seen on CLI. Check table1 to set
baud rates for different Confreg values.
The configuration register can be set from configuration mode using the config-register command. From
ROMmon, use the confreg command. Issue the show version command to view the current setting of the
configuration register:
Router#show version
Cisco Internetwork Operating System Software
IOS (tm) 2500 Software (C2500-JS-L), Version 12.1(5), RELEASE SOFTWARE (fc1)
Copyright (c) 1986-2000 by cisco Systems, Inc.
Compiled Wed 25-Oct-00 05:18 by cmong
Image text-base: 0x03071DB0, data-base: 0x00001000
ROM: System Bootstrap, Version 5.2(8a), RELEASE SOFTWARE
BOOTFLASH: 3000 Bootstrap Software (IGS-RXBOOT), Version 10.2(8a), RELEASE SOFTWARE
(fc1)
Router uptime is 7 minutes
System returned to ROM by reload
System image file is "flash:c2500-js-l_121-5.bin"
cisco 2500 (68030) processor (revision D) with 16384K/2048K bytes of memory.
Processor board ID 03867477, with hardware revision 00000000
Bridging software.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
TN3270 Emulation software.
1 Token Ring/IEEE 802.5 interface(s)
2 Serial network interface(s)
32K bytes of non-volatile configuration memory.
16384K bytes of processor board System flash (Read ONLY)
Configuration register is 0x2102

The factory-default setting for the configuration register is 0x2102. This indicates that the router should attempt
to load a Cisco IOS software image from Flash memory and load the startup configuration with a console
speed of 9600 baud.

En la ejecucion
Removing Previous Boot Statements
To remove the commands, enter into configuration terminal mode. From the configuration mode, you can
negate any command by typing "no" in front of each boot statement. The following example illustrates the
removal of an existing boot statement:
7500#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
7500(config)#no boot system flash slot0:rsp-jsv-mz.121-13.bin
7500(config)#^Z
7500#

Setting New Boot Statements


Now set the router to boot the new image. Issue the following command to set the boot system parameter:
boot system flash slot0:{imagename} (imagename = name of the new IOS image)
7500#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
7500(config)#boot system flash slot0:rsp-jsv-mz.122-6.bin
7500(config)#^Z
7500#write mem
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0
Building configuration...
7500#

On platforms equipped with ATA PCMCIA Flash disks, the command syntax would be:
boot system [device]:{imagename}

For example:
7500(config)#boot system disk0:rsp-jsv-mz.122-6.bin

Be sure to verify that you are using config-register 0x2102 by issuing the show bootvar or show version
command. If it is set up differently, you can change it by issuing the following command in configuration mode:
7500#configure terminal
Enter configuration commands, one per line.
7500(config)#config-register 0x2102
7500(config)#^Z
7500#write mem

End with CNTL/Z.

Verify the boot parameters by issuing the show bootvar command:


7500#show bootvar
BOOT variable = slot0:rsp-jsv-mz.122-6.bin,12;
CONFIG_FILE variable =
BOOTLDR variable does not exist

Configuration register is 0x102 (will be 0x2102 at next reload)


7500#

After changing the config-register, the change takes place at the next reload, as shown above.

Step1: Reboot the router to load new image


For the router to run the new Cisco IOS software image, you need to reload the router. Make sure you have
saved the configuration by issuing the copy run start or write mem command.
7500#write mem
3d01h: %SYS-5-CONFIG_I: Configured from console by vty0 (127.0.0.11)
Building configuration...
7500#reload

Step 2: Verify the Upgrade


After the router comes up, make sure you are currently running the new version of code, by issuing the show
version command:
7500#show version
Cisco Internetwork Operating System Software
IOS (tm) RSP Software (RSP-JSV-M), Version 12.2(6), RELEASE SOFTWARE (fc3)
Copyright (c) 1986-2002 by cisco Systems, Inc.
Compiled Wed 30-Jan-02 19:58 by kellythw
Image text-base: 0x60010958, data-base: 0x6148A000
ROM: System Bootstrap, Version 11.1(8)CA1, EARLY DEPLOYMENT RELEASE SOFTWARE (fc1)
BOOTLDR: RSP Software (RSP-BOOT-M), Version 12.2(6), RELEASE SOFTWARE (fc2)
7500-A uptime is 0 minutes
System returned to ROM by reload at 00:05:37 PST Sat Jan 1 2000
System image file is "slot0:rsp-jsv-mz.122-6.bin"
!-- you have booted the correct image
cisco RSP4 (R5000) processor with 131072K/2072K bytes of memory.
R5000 CPU at 200Mhz, Implementation 35, Rev 2.1, 512KB L2 Cache
Last reset from power-on
G.703/E1 software, Version 1.0.
G.703/JT2 software, Version 1.0.
Channelized E1, Version 1.0.
X.25 software, Version 3.0.0.
SuperLAT software (copyright 1990 by Meridian Technology Corp).
Bridging software.
TN3270 Emulation software.
Primary Rate ISDN software, Version 1.1.
Chassis Interface.
1 EIP controller (6 Ethernet).
1 AIP controller (1 ATM).
2 TRIP controllers (8 Token Ring).
2 MIP controllers (2 T1) (2 E1).
6 Ethernet/IEEE 802.3 interface(s)
8 Token Ring/IEEE 802.5 interface(s)
48 Serial network interface(s)
1 ATM network interface(s)
2 Channelized E1/PRI port(s)
2 Channelized T1/PRI port(s)
123K bytes of non-volatile configuration memory.

20480K bytes of Flash PCMCIA card at slot 0 (Sector size 128K).


16384K bytes of Flash PCMCIA card at slot 1 (Sector size 128K).
8192K bytes of Flash internal SIMM (Sector size 256K).
No slave installed in slot 6.
Configuration register is 0x2102

ANEXOS:
DORTEZAL2# dir sup-bootdisk: donde esta almacenado nueva imagen IOS
Directory of sup-bootdisk:/

1 -rw121933380
mz.122-33.SRC1.bin
2

c7600rsp72043-adventerprisek9-

33554432

Apr 30 2008 14:43:00 -05:00

sea_log.dat

3 -rw121746980
mz.122-33.SRC.bin

Apr 30 2008 17:20:46 -05:00

c7600rsp72043-adventerprisek9-

Apr 30 2008 17:23:56 -05:00

c7600-fpd-pkg.122-33.SRC.pkg

-rw-

Aug 1 2008 15:58:14 -05:00

-rw-

27872768

5 -rw168943172 Jun 18 2013 22:57:20 -05:00


mz.151-3.S4.bin ---- Nueva imagen

c7600rsp72043-adventerprisek9-

512090112 bytes total (38027264 bytes free)

Actualmente

configuracin de inicio

DORTEZAL2#show bootvar
BOOT variable = sup-bootdisk:c7600rsp72043-adventerprisek9-mz.122-33.SRC1.bin,1;
CONFIG_FILE variable =
BOOTLDR variable =
Configuration register is 0x2102

Standby BOOT variable = sup-bootdisk:c7600rsp72043-adventerprisek9-mz.12233.SRC1.bin,1;


Standby CONFIG_FILE variable =
Standby BOOTLDR variable =
Standby Configuration register is 0x2102

5 -rw168943172
mz.151-3.S4.bin

Jun 18 2013 22:57:20 -05:00

512090112 bytes total (38027264 bytes free)

c7600rsp72043-adventerprisek9-

Durante la ventana se debe cambiar el Boot con la nueva imagen de acuerdo


al manual, primero retirar la anterior ( no boot system sup-bootdisk:c7600rsp72043adventerprisek9-mz.122-33.SRC1.bin) y luego colocar la nueva ( boot system supbootdisk:c7600rsp72043-adventerprisek9-mz.151-3.S4.bin)), luego guardar los cambios
(wr) aislar troncales del equipo, el personal de apoyo a travs de la consola
reiniciara el equipo con el comando indicado en el manual.