Most Basic of IP Office Questions; Can't PING

[nsi12000]

Have a used but supposedly defaulted IP403 sent to us by a client to pre-configure. We are new to this IP System, but have done loads of Avaya analog systems. following the directions, we seem to not be able to establish a valid connection with the switch. link lights OK, Green flashing when trying to ping or interrogate but no ping return on either the 42 or 43 default lans. How best to proceed?

thanks
JEB@NSI

 

[mforrence]

Default it again...

 

[IPGuru]

Defaulting via the DTE port is the easiest option, but if you are just curious then you could monitor the dte port as the system boots, it will output its IP address in amongst all the other diagnostic output.


Computers are like Air conditioners:-
Both stop working when you open Windows

 

[nsi12000]

Thanks Guys,

Got into the DTE did an eraseconfig and a erasenvconfig.
Was able to ping 192.169.42.1 However can not Discover/select an IP-office when asked to open configuration from IP Office, no device is displayed. System monitor will read the system. Displaying the
following about once a minute.

********** SysMonitor v5.2 (69) **********

********** contact made with 192.168.42.1 at 12:52:58 28/11/2011 **********

********** System (192.168.42.1) has been up and running for 2mins and 23secs(143762mS) **********


********** Warning: TEXT File Logging selected **********


0mS PRN: Monitor Started IP=192.168.42.203 IP 403 DS 2.0(16) 00E0070075BC
0mS PRN: LAW=A PRI=1, BRI=0, ALOG=0, ADSL=0 VCOMP=0, MDM=0, WAN=0, MODU=0 LANM=0 CkSRC=0 VMAIL=0(VER=0 TYP=1) CALLS=0(TOT=0)
327mS RES: Mon 28/11/2011 12:52:58 FreeMem=6482428(5) CMMsg=2 (2) Buff=100 656 500 1425 Links=10424
3005mS PRN: +++ START OF ALARM LOG DUMP +++
3005mS PRN: ALARM: 28/11/2011 12:40:43 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=01010018 d=5 pc=ff5dfb34 ff5dfb00 ff5c69d4 ff5c6620 ff5c6728 ff5c3ac8
3005mS PRN: ALARM: 28/11/2011 12:44:50 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=01010018 d=5 pc=ff5dfb34 ff5dfb00 ff5c69d4 ff5c6620 ff5c6728 ff5c3ac8
3006mS PRN: ALARM: 28/11/2011 12:47:04 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=01010018 d=5 pc=ff5dfb34 ff5dfb00 ff5c69d4 ff5c6620 ff5c6728 ff5c3ac8
3006mS PRN: ALARM: 28/11/2011 12:48:14 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=01010018 d=5 pc=ff5dfb34 ff5dfb00 ff5c69d4 ff5c6620 ff5c6728 ff5c3ac8
3006mS PRN: ALARM: 28/11/2011 12:50:25 IP 403 DS 2.0(16) <TLB Data Error> CRIT RAISED addr=01010018 d=5 pc=ff5dfb34 ff5dfb00 ff5c69d4 ff5c6620 ff5c6728 ff5c3ac8
3006mS PRN: +++ END OF ALARM LOG DUMP +++
15329mS RES: Mon 28/11/2011 12:53:14 FreeMem=6476940(5) CMMsg=2 (2) Buff=100 656 500 1425 Links=10421
30332mS RES: Mon 28/11/2011 12:53:29 FreeMem=6482428(5) CMMsg=2 (2) Buff=100 656 500 1425 Links=10424
36262mS PRN: .FATAL TLB Data Error address=01010018 d=5 pc=ff5dfb34 ff5dfb00 ff5c69d4 ff5c6620 ff5c6728 ff5c3ac8 IP 403 DS 2.0(16)

********** contact lost with 192.168.42.1 at 12:53:49 28/11/2011 - reselect = 1 **********
*****************************************************************


So, seem to be talking but, seem unable to send a config to the system.

What are we (or the system) missing?

Thanks, JEB@NSI

 

[tlpeter]

It is an old machine so it could be just broken.
Sometimes they run for years and after a reboot it just dies.


BAZINGA!

I'm not insane, my mother had me tested!

 

[CarGoSki]

All of those TLB alarms are from today.

If you have any daughter cards attached then I would remove them and try again.

 

[Telecomboy]

If it is an old machine, turn the firewall off on the pc trying to connect to it. It could be blocking the communication. Also, set a static IP address to the machine trying to connect to it. Also, make sure the version on Manager you are using is compatible with it.

 

[nsi12000]

Thanks fro your comments Guys,

Have removed the analog trunk card, re-defaulted the system,
checked that we are using 5.2 manager on this 3.2 IP403, set the
management computer to static 192.168.42.203 255.255.255.0 with no
gateway. Can Ping 192.168.42.1 ... have created a new config in manager offline but still unable to find the IP Office when trying to send the config to the device. Also still throwing TLB alarms in
monitor for about a minute before the system throws a reboot. About ready to give up on this one, unless anyone has any ideas.

Thanks Again, JEB@NSI

 

[bdelmar]

the IPO is on 2.0.16, your sys mon is version 5.2.69. Im assuming you manager is the same version as your Sys Mon. Im not sure if it was backwards compatible that far back to 2.0.

Anyone remember?

 

[tlpeter]

2.1 and up.
2.0 is not supported for using to program.
There is still a PRI card in the system.
Remove that one too and try again.
Also the 403 is running 2.0.16!!!

BAZINGA!

I'm not insane, my mother had me tested!

 

[bdelmar]

As I thought, you're going to have to find a lower version of manager.

 

[jamie77]

You can use the new manager to upgrade that system.

Get hold of the tech bulletins from support.avaya.com and make sure you go through all the builds needed.

Jamie Green

Football is not a matter of life and death-It is far more important!!!!

 

[hairlessupportmonkey]

might be better to also just "upgrade" to 3.2 - assuming the info is actually correct in the trace and this is a DS and not a DT with DS software on it.... ;-)

ACSS - SME
General Geek