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.
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.
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.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.