IP 403 Keeps Rebooting 2

[Quadnet]

My Ipoffice 403 was working fine on 2.1 27 till someone advised upgrading to 2.1 51.

Since, I have had to deal with a re-booting switch, and have subsequently had to reset the sytem to factory and reinstall the config. But it still re-boots..

I have now been advised to do a AT-X command on the thing!.. and then re-configure the whole thing (and not to import the config).. :

Connect via DTE port
"AT - X" to wipe box
Load 2.1.27 default configuration
Upgrade to 3.0 (999)
Load back to 2.1.51

But why goto 3.0(999) ?? this part i do not understand..

Would this be the way forward..

What other commands would I need to run apart from AT-X to wipe the box?

Will it reset the unit back to a 1.3 and will i have to do a upgarde to 1.99 again? and then to 2.1 27?

Thanks for your time..

Anj

 

[Wally1775]

I know it sounds weird, but you DO need to go to 3.0(999) for that. Otherwise there is not enough room for the new binary.

 

[big70]

I wouldt go to 2.1(62)

http://support.avaya.com/japple/css...ucketID=108025&temp.releaseID=162487&x=9&y=17

Greets Peter

 

[Quadnet]

which version was the most stable?

and where do i get the 3.0 (999) from ?

Anj

 

[bwilch]

The 3.0 (99) will be on the admin CD you download. After you install manager you will notice a folder called (something like) 403v3099 That is where the 3.0 (99) bin will be stored.

 

[l33byt1]

Post up your monitor read offs. Do a search for "contact lost" some one may be able to point you into right direction of the reboots.

Can the reboots be pinpointed to when some thing is done. Eg. Call pickups, When a hunt group is busy, when putting system in night service bla bla bla.

 

[Quadnet]

so if i download the 2.1.62 admin files it will have the 3.0(999) in there as well..?

then :
"AT - X" to wipe box
Load 2.1.2x default configuration
Upgrade to 3.0 (999)
Load back to 2.1.51

this ok..

Anj

 

[spridge]

Excellent Technical Bulletin PDF available on same screen where download files presented

Explains exact upgrade procedure

Basically any upgrade after 2.1 (31) requires the interim 3.0 (999) upgrade to provide more flash memory to hold the latest versions

2.1 (51) and above

3.1 any version

Carried this upgrade out dozens of times with no problems

Good luck

 

[Quadnet]

Great I'm piecing together all the info.. Did not know that after v31 it needed more flash memory!! Thanks for that Spridge..

could someone please confirm that only the one command AT-X needs to be run from the console? and not any more..

Anj

 

[NuggiFirst]

If you have a system that starts up fine, then i wouldn't do anything in the console!

Just upgrade to 3.0(999) with UpgradeWiz, and then the software you want to use.

One possible reboot cause (In 3.0(59) and maybe 2.1(51)):
Example:
HG200 overflows to HG201
HG201 overflows to HG200

If both HG's are busy (so that they follow their overflow destination), and a call arrives to one of them, then the IPO will have a nice red LED

 

[Quadnet]

NuggiFirst,

I have done the upgarde using the ZIx and reloaded the config, and the peoblem persisted!

Hence the reason for going through the console to flash the memory and get it back up again with a fresh re-build..

Anyone else think this is OTT

 

[Quadnet]

If downgrading a Box from 2.1.51 using the DTE port and running the AT-X command..

what version will it leave the box in..

will I have a box set back to v 1.3? or 2. something..?

 

[PHins711]

Isn't 3.0(999) only needed if you aren't doing a validated upgrade? If that box is checked then you shouldn't need to use 3.0(999). I just upgraded two 406V2s to the newest release with no problem. They were shipped with 2.1.27 and I took them straight to 3.1.56.

 

[Quadnet]

Last night it i tried the procedure - surgical gloves, scalpal..and an IP office Laptop..

At first my serial connector would not let me get a conection, then it would not work when the escape key was pressed, stating a signal failure.. where as it was because I did not have a correct Boottp Entry. Once corrected I was able to continue.

I ran the AT-X command but it would not erase the config on the box..tried it several times with differnet bin files as well.. but in the end decided to go the full hog and reset the box..

AT-X2..3..4.. then AT-X was run.

The config was erased, and the system was re-booted with the 2.1.24 bin file on my machine.

I then did an upgrade to 2.999 or something (not 3.0 (999) as this number did not exist in the upgrade options even on the latest downloaded admin cd from avaya)

The system was then downgraded to 2.1.51 and a config file copied into it and saved and closed.

All systems seem to be working but will only find out if it has worked when the phones do not cut out any more.

My customer was having the same problem and I will be doing his one in 15 mins! fingers crossed it all goes well.

Thanks for all your help especially NuggiFirst, for idetifying the overflow issue.

Anj

 

[Quadnet]

My system's still re-booting!

Done:
1. AT-X2..3..4.. then AT-X was run..

2. Upgrade to 2.999 (3.0 (999) does not exist in the upgrade options) - and did not do a 1.99 either

3. Downgraded to 2.1.51

I STILL HAVE A REBOOTING SWITCH !!

How do i get the sytem back to 2.1.27 and no later and keep it there.. ?

Do I run AT-X2..3..4. AT-X and re-boot only with 2.1.27 (will this work as it has gone up to 2.1.51 will there still be a problem?)

 

[bigjohn8210]

you just need to install 2.1 (27) if you have 2.1 51 running and then downgrade which the syatem calls and upgrade. then factory reset the box then add the old config back on.

 

[Quadnet]

I have just had a chat with a techi in MTV telecom..

He advised do the at-X commands and start with the 1.3 bin files and start upgrading from there.