cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
4168
Views
0
Helpful
13
Replies

Upgrade ISSU Core 4506 error

cnogueral
Level 1
Level 1

Attempt to update two 4056e cores in HA, by the issu process.

In the first part when entering the load command ..., the following error occurs:
CI_CORE#issu loadversion 11 bootflash:cat4500es8-universalk9.SPA.03.08.06.E.152-4.E6.bin 1 slavebootflash:cat4500es8-universalk9.SPA.$
% Active config-register doesn't have 0x0002 as the low order nibble

An attempt was made to change the registry configuration and it was retested, showing the following result:

BOOT = bootflash:cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin,1;
Configuration register = 0x2101 (will be 0x2102 at next reload)

CI_CORE#$at4500es8-universalk9.SPA.03.08.06.E.152-4.E6.bin 1 slavebootflash:cat4500es8-universalk9.SPA.03.08.06.E.152-4.E6.bin
% Active Boot variable is invalid

The output of the show redndancy, show ver, show issu state commands is attached

Please, indicate how I should proceed, according to the configuration, if do I have to change the registry and reload the devices, so that they can make the change on register, and retry realizing the process by issu

2 Accepted Solutions

Accepted Solutions

Hello,

 

I don't think there is a recommended one since you will only be on it for a little while while you do the next upgrade. I would probably go to 3.8.4.

 

The output from show ver and the output from show boot have to match in order for ISSU to work

System image file is "bootflash:/cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin"

BOOT = bootflash:cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin,1;

 

I am wondering if that "/" is messing you up. Can you try the following?

 

conf t

no boot sys

boot sys bootflash:/cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin

wr

show bootvar

 

Does show boot have the "/" at the beginning now? 

 

Hope that helps!

 

 

 

-Bradley Selzer
CCIE# 60833

View solution in original post

Ok, now that ISSU doesn't work try the "old fashion way":
1. Copy the IOS into the primary supervisor card;
2. Copy the IOS into the secondary supervisor card;
OPTIONAL: Check the MD5 hash value of the IOS against the MD5 hash value found in the Cisco website.
3. Change the boot variable string;
NOTE: Delete ALL the previous boot variable string, add a new boot variable string point to the NEW IOS, add another boot variable string pointing to the OLD IOS.
4. Check to make sure the config-registry value is 0x2102;
5. Save the config; and
OPTIONAL: Export the config to a remote client.
6. Reboot.

View solution in original post

13 Replies 13

brselzer
Cisco Employee
Cisco Employee

Hello,

 

For starters, you can not do an ISSU between 3.8.1 and 3.8.6:

 

http://docwiki.cisco.com/wiki/Catalyst_4500/4900_series_ISSU_compatibility_matrix

 

You will need to go to a version in between first. However, that should not cause this error. Can you post the output of the following two commands:

 

attach module 1

show version

 

Hope that helps!

 

 

-Bradley Selzer
CCIE# 60833

Hello,

 

There is the commands output:

 

CI_CORE#
CI_CORE#attach module 1
Connecting to standby virtual console
Type "exit" or "quit" to end this session


CI_CORE-standby-console#
CI_CORE-standby-console#show vers
CI_CORE-standby-console#show version
Cisco IOS Software, IOS-XE Software, Catalyst 4500 L3 Switch Software (cat4500es8-UNIVERSALK9-M), Version 03.08.01.E RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2016 by Cisco Systems, Inc.
Compiled Thu 28-Jan-16 18:46 by prod_rel_team

 

Cisco IOS-XE software, Copyright (c) 2005-2015 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.
(http://www.gnu.org/licenses/gpl-2.0.html) 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: 15.1(1r)SG6
CI_CORE uptime is 3 weeks, 3 days, 5 hours, 8 minutes
Uptime for this control processor is 3 weeks, 3 days, 5 hours, 8 minutes
System returned to ROM by reload
System restarted at 08:44:57 COL Fri Oct 5 2018
System image file is "bootflash:/cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin"
Jawa Revision 4, RadTrooper Revision 0x0.0x41, Conan Revision 0x378D


Last reload reason: Critical software exception

 

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.


License Information for 'WS-X45-SUP8L-E'
License Level: ipbase Type: Permanent
Next reboot license Level: ipbase

cisco WS-C4506-E (P5040) processor (revision 2) with 4194304K bytes of physical memory.
Processor board ID SPE202100F0
P5040 CPU at 1.8GHz, Supervisor 8L-E
Last reset from Reload
40 Virtual Ethernet interfaces
168 Gigabit Ethernet interfaces
8 Ten Gigabit Ethernet interfaces
511K bytes of non-volatile configuration memory.

Configuration register is 0x2101

CI_CORE-standby-console#exit
CI_CORE#exit

 

What is the recommended first version between 3.8.1 and 3.8.6 to make the issu process?

 

Thank you

 

 

Hello,

 

I don't think there is a recommended one since you will only be on it for a little while while you do the next upgrade. I would probably go to 3.8.4.

 

The output from show ver and the output from show boot have to match in order for ISSU to work

System image file is "bootflash:/cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin"

BOOT = bootflash:cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin,1;

 

I am wondering if that "/" is messing you up. Can you try the following?

 

conf t

no boot sys

boot sys bootflash:/cat4500es8-universalk9.SPA.03.08.01.E.152-4.E1.bin

wr

show bootvar

 

Does show boot have the "/" at the beginning now? 

 

Hope that helps!

 

 

 

-Bradley Selzer
CCIE# 60833

Your configuration register is 0x2101

it needs to be 0x2102.

 

HTH

Hello,

 

When i make the change of registry, I must restart the device to be able to do the process of update by issu? or can i do it without reload the device

 

Thank you,

Ok, now that ISSU doesn't work try the "old fashion way":
1. Copy the IOS into the primary supervisor card;
2. Copy the IOS into the secondary supervisor card;
OPTIONAL: Check the MD5 hash value of the IOS against the MD5 hash value found in the Cisco website.
3. Change the boot variable string;
NOTE: Delete ALL the previous boot variable string, add a new boot variable string point to the NEW IOS, add another boot variable string pointing to the OLD IOS.
4. Check to make sure the config-registry value is 0x2102;
5. Save the config; and
OPTIONAL: Export the config to a remote client.
6. Reboot.

Sorry, maybe you do not explain well before.
The new attempt to make the process by issu has not yet been made
What I would like to know is if after changing the register to 0x2102, do I must reload the two C4506 so that the change is taken by them, or if I only have to change the registry and try again to update by issu?

Thank you,

Sorry, maybe I do not explain well before.
The new attempt to make the process by issu has not yet been made
What I would like to know is if after changing the register to 0x2102, do I must reload the two C4506 so that the change is taken by them, or if I only have to change the registry and try again to update by issu?

Yes, the chassis will need to be rebooted or else the new config register won't get applied.

Correct. As Leo also said, in order for the config change to take effect, you have to reboot the chassis.

HTH

hello. 

 

In case that issu doesn´t work, i will do as said "old fashion", for this can i do it from version 3.8.1 to 3.8.6 or i have to make a previous version between them.

 

Thank you,

With "old fashion" way, you can straight to 3.8.6.

Most of the time ISSU is more headache then helpful. So, if you have a maintenance window to reboot the chassis, you should be fine.

 

HTH 

Read the Release Notes. There are cases before upgrading you will need to upgrade the ROMmon first.
Review Cisco Networking for a $25 gift card