Upgrade of VG224 IOS didn't seem to work

Unanswered Question
Mar 16th, 2010
User Badges:

Hello all, I have attempted to upgrade the IOS of my VG224 -12.4.(15)T5 - several times to no apparent avail, using the vg224-i6s-mz.124-25c.bin and vg224-i6s-mz.150-1.M2.bin images.  I am having a problem with Polycom conference phones (have to enter numbers very rapidly to join a conference clal) I'd really like to solve.

I have TFTP'd the new IOS images both to slot1 and flash, then utilized these commands at config terminal to load the new IOS:

no boot system
boot system slot1:[file name]

I then ran show run | include boot to verify the "boot system" entry was pointing to the right place.  I then wrote to memory and reloaded the router.  Unfortunately, when it came up it showed the same old IOS.  It still shows what should be the correct boot system location, so I'm not sure what's wrong here.  Doesn't seem to work either from flash or slot1.

Can anyone provide any insight?

Thanks in advance.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (4 ratings)
Aaron Harrison Wed, 03/17/2010 - 02:36
User Badges:
  • Super Bronze, 10000 points or more
  • Community Spotlight Award,

    Member's Choice, May 2015

Hmmm... maybe try:

Verify slot1:filename

To see if the MD5 is what is was supposed to be...?


Dan Lynch Thu, 03/24/2016 - 02:04
User Badges:

Sorry for asking this on an old post. I made a mistake and did not name the file for slot0 anyone know how to remove an unnamed file in slot0?

r.babb Tue, 11/30/2010 - 08:58
User Badges:

I am having the same issue.

Do you have access to the console to see an error message during startup.  I'm wondering if there is something kicking that image out. Do we need to upgrade the bootstrap as well?

Felipe Garrido Tue, 11/30/2010 - 09:02
User Badges:
  • Cisco Employee,

I would definitely check that the VG224 also has sufficient memory to boot the image. Connecting via console port and monitoring the boot sequence events would also be helpful. Make sure to save the output and post it.

j.burwell Fri, 01/27/2012 - 07:58
User Badges:

Even though this post is old, I figured I would post with the resolution I was given for the exact same problem I was having when attempting to upgrade a VG224 just in case anyone else hits this problem and sees this post as I did when searching for a solution.

The problem for my VG224 ended up being the config-register was not set to 0x2102. It was set to another value ( I have no idea why) and the VG224 was ignoring the boot statement when booting and booting with the first .bin image file on flash which was the old image. Chaning the config-register value to 0x2102 resolved the problem.

Bushra Kabir Mon, 09/10/2012 - 18:06
User Badges:

Brilliant. That exactly what my problem was as well. It's all fixed now.



JOSE RIVERA Mon, 02/09/2015 - 12:00
User Badges:

Changing the config register also fixed my issue.





This Discussion