SOE stuck in "offline mode"

[KatzEye1]

hi folks i've got a weird one here hope you can help:

an SOE ip401ng unit, we upgraded to 4.2.20, monitor says:
PRN: Offline Mode
even in manager when we go to open the conf, in the "select ip office" window the unit shows up in the list but under the "type" column it is named "Offline IP 401 NG" !!

the upgrade process went fine, the upgrade app said all the right words (preparing, uploading, upgrading, rebooting etc), didnt crash and gave the "completed" window...

we've upgraded other SOEs to 4.2.20 before no probs...

i know these units go into offline mode when upgrading, and its poss that this one is stuck in that mode,

how in the world do i bring it back "online"?

many thx...

 

[KatzEye1]

PS I already went through the manual DTE erase processes...

first i erased config:
AT
AT-X2
AT-X3

that did solve it, then i erased it all with:
AT
AT-X

unit rebooted, tftp downloaded ip401ng.bin, but after its last reboot it showed offline mode again...

 

[tlpeter]

Offline mode means it is a mode without a working software.
It will come back in a certain amount of time but I forgot how long.

You need a bootloader when you are not already on release 4.
The software is too big to do an online upgrade.


Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[KatzEye1]

i can actually load the config file in manager software, everything else seems ok but of course since its in offline mode non of the services on it work (phone etc)..

i've left it on for hours, didnt come back online...

 

[tlpeter]

When you do an offline upgrade then it is actually an AT-X with holding the config.
You must be sure that you have the bootp entry and that the tftp server works.

You could try this:

at-debug
upgrade

this will do an offline upgrade too.

Homo sapiens non urinat in ventum

honey, i fried the IP Office !!!

Sarcasm, it's only one of the services I offer.

 

[mattKnight]

>You need a bootloader when you are not already on release 4.
>The software is too big to do an online upgrade.
^^
This!

Are you very sure that youhave upgraded to 3.2.999

If you have the slightest doubt that you haven't done so, then upgrade to 3.2.999 first



Take Care

Matt
I have always wished that my computer would be as easy to use as my telephone.
My wish has come true. I no longer know how to use my telephone.

 

[KatzEye1]

I'm pretty sure i did go thru 3.2.999 but just to make sure I went back to 3.2.57 then to 3.2.999.

The 3.2.57 stage went well and unit came online and was stable.

upgrade to 3.2.999 file transfer went well but unit then went into a restart loop...

monitor shows this before each reboot:

********** Warning: TEXT Logging to File STOPPED on 26/9/2010 21:57:25 **********

12768mS PRN: Monitor Started IP=192.168.42.100 IP 401 NG 3.2(999) 00E007017C83
(IP Office: Supports Unicode, System Locale is enu)
12769mS PRN: LAW=U PRI=0, BRI=0, ALOG=2, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=0)
12779mS LIST2: IFACE(4) "LAN1","LAN2","DialIn","RemoteManager"
13261mS RES: Sun 26/9/2010 21:57:25 FreeMem=3705336(2) CMMsg=1 (1) Buff=100 612 500 1470 5 Links=5119
13770mS PRN: Sorting User List...
13770mS PRN: User List Sorted
13772mS PRN: Sorting Hunt Group List...
13772mS PRN: Hunt Group List Sorted
13774mS PRN: Sorting Directory List...
13774mS PRN: Sorted Directory List.
13776mS PRN: Config Write Completed
15769mS PRN: +++ START OF ALARM LOG DUMP +++
15769mS PRN: ALARM: 26/09/2010 21:46:19 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c 00000000 ff87cfbc ff8888cc ff8889b4 ff7f8444
15770mS PRN: ALARM: 26/09/2010 21:46:45 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c 00000000 ff87cfbc ff8888cc ff8889b4 ff7f8444
15771mS PRN: ALARM: 26/09/2010 21:47:09 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c ffe48ab8 ff87cfbc ff8888cc ff8889b4 ff7f8444
15771mS PRN: ALARM: 26/09/2010 21:47:35 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444
15772mS PRN: ALARM: 26/09/2010 21:48:00 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444
15773mS PRN: ALARM: 26/09/2010 21:48:25 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444
15773mS PRN: ALARM: 26/09/2010 21:49:42 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444
15774mS PRN: ALARM: 26/09/2010 21:50:10 IP 401 NG 3.2(999) <TLB Data > CRIT RAISED addr=000000b4 d=5 pc=ff61e59c ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444
15774mS PRN: +++ END OF ALARM LOG DUMP +++
17736mS PRN: Alarm log cyclic wrap
17736mS PRN: Begin Stack Trace
17736mS PRN: pc=ff61e59c
17736mS PRN: lr=ff87cfbc
17736mS PRN: findfunc ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444 ff7fa814 ff7fab24 ff7f8b98 ff7d3b20 ff7d3fc8
17736mS PRN: findfunc ff7d40d4 ff7d417c ff599d48 ff599d0c 00000000 00000000 00000000 00000000 00000000 00000000
17736mS PRN: End Stack Trace
17736mS PRN: .FATAL TLB Data address=000000b4 d=5 pc=ff61e59c ff5a86f0 ff87cfbc ff8888cc ff8889b4 ff7f8444 IP 401 NG 3.2(999)



hrrmmmm, any ideas? The SOE is brand new i opened the seal myself!!

 

[kwing112000]

Dont all the SOE's have a VCM in them? It shows as 0 up above.

Kevin Wing
ACSS Small and Medium Enterprise (SME) Communications
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[KatzEye1]

Good point, i didnt keep record of the monitor report when it was on 3.2.57, i just assumed it shows 0 when 3.2.999 is installed since 3.2.999 is not a "complete" firmware?