412 Upgrade 3.2(57) to 5.0.22

[ShikePoke]

Ip office 412 at 3.2.57 having issues with 5.0.22 manager seeing the bin files for 3.2.999, 4.2, any others.

This should be a step upgrade process, but the only .bin files manager recognizes is the ones in the default directory for 5.0.22.

Thanks,
Shike

 

[hairlessupportmonkey]

make sure both directory paths are the same in your Working Directory.

 

[ShikePoke]

This is the directory for both:

C:\Program Files\Avaya\IP Office\Manager\V3_2_999

Still nothing on the upgrade wizard.

 

[amriddle01]

There is no bin file in 3.2.999 for the 412 itself, that is purely for Dig v2 expansion modules, that's why it doesn't see anything as it does not exist, it should see 4.2 bin files but then it needs to be just the Manager folder obviously

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[hairlessupportmonkey]

Andy is right. just take the 412 to r5 and only step the modules. (i figured that was what you were trying to so anyway.) Its only 3.1-3.2 where the IPO needed to be stepped.

 

[ShikePoke]

I tried to go straight to 5.0.22, it failed immediately. I'm now downloading 4.2 manager to see if it will recognize those .bin files.

 

[amriddle01]

Failing immediately usually means wrong password, which is "password" not the same one as used for logging in with Manager or SSA etc

ACSS (SME)
APSS (SME)

http://www.ipoffice.tel

"I'm just off to Hartlepool to buy some exploding trousers

 

[ShikePoke]

Yes, tried "password", still fails immediately. Just downloaded latest 4.2, fully installed manager, will let you know.

thanks,
Shike

 

[ShikePoke]

I loaded manager, and used DTE maintenance for this procedure(I'm moving forward finally!):

Procedure: Erasing the Core Software via Debug
1. Run Manager. In the BOOTP entries, check that there is an entry that matches the MAC
Address, IP Address and .bin file used by the system (the first two details can be found in the
Module settings in the system's configuration file).
2. If an entry is not present, create a new entry. Then close and restart Manager.
3. Under File | Preferences ensure that Manager is set to 255.255.255.255. Also check that
Enable BootP Server is checked.
4. Select View | TFTPLog.
5. Check that the required .bin file is present in Manager's working directory.
6. Attach the serial cable between the PC and the DTE port on the IP Office control unit.
7. Start the terminal program on your PC. Ensure that it has been setup as listed in DTE Port
Settings. Within a HyperTerminal session, the current settings are summarized across the base
of the screen.
8. Arrange the program windows so that the Terminal program and Manager TFTP Log are visible
at the same time.
9. Enter AT (note upper case). The control unit should respond OK.
10. Enter AT-DEBUG. The control unit should response with the time and date and then Hello> to
show it is ready to accept commands.
11. To erase the current configuration in RAM memory enter upgrade.
12. The IP Office will erase its current software and then send out a BootP request on the network for
new software. Manager will respond and start transferring the software using TFTP.

 

[ShikePoke]

Now can I load the .cfg file that I have at 3.2.57? Or must I downgrade, load the .cfg, then upgrade?

 

[ShikePoke]

OK, took it back to 3.2.57, loaded config, then upgraded striaght to 5.0.22. All resolved, thanks all.

Shike