IP 406 upgrade to V5.0.18 Network stops responding after couple hours

[Yaze]

I had an SCN of 3 ip 406 on 4.2.20 we added a 4th site with an IP 500 so we ugraded the 3 other sites to latest 5.0.18...

Everything works fine for a couple of hours then the Main central site (IP406 v2)stops responding, we can make and receive calls, but voicemail and scn stops(main site is on same subnet/switch as vm server), the ipo doesn't even respond to pings... It seems that the whole network side of the IPO stops responding.

I'm about to downgrade back to 4.2 untill avaya resolve a ticket i will open tomorrow...

If anyone can think of anything causing this issue please be free to fill in.

Thanks.

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[Yaze]

BTW rebooting only the main IPO resolve the issue... but only for a while.

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[tlpeter]

Can you try 5.0.8 or 5.0.15 ?
I have seen a case where a 406 stops responding at all!


ACSS IP Office
APSS IP Office
APSS UC
ACA - Implement IP Telephony -- ACA - Design IP Telephony
ACA - Voice Services Management


______________
Women and cats can do as they please and men and dogs should relax and get used to the idea!

 

[Yaze]

Well right now i've enabled LAN2 on port 8 reconfigured lan2 to same ip as lan1, changed lan1 ip, changed system ip routes to lan2 and plug the voicemail into the switch instead of the ipo office, 5 hours and 10 minutes later both lans are still pinging...

Waiting for it to crash...

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[Bas1234]

Downgrade like tlpeter mentioned;

CQ40222

SCN audio loss appears to be related to frequent ARP updates

5.0.18

SP_RELEASE_3Q10_5.0


1-Not Required

Or try to reduce the ARP requests.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Bas1234]

Spanning tree on the switches could cause it, so first try to turn that off.

___________________________________________
It works! Now if only I could remember what I did...

Dain Bramaged
___________________________________________

 

[Yaze]

8 hours still running...

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[Yaze]

Well after 18 hours without crashing the changes i made to the config might be enough...

I'm still at 5.0.18, buffers look normal, both lans still ping, hopes are high !!

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[rogier97]

Till running today? Yaze?

 

[Yaze]

Yes, but i had to finally downgrade to 5.0.15, opened the ticket with avaya and sent traces got to tier 4 they came back saying they needed more detailed wireshark traces, by then i had downgraded to 5.0.15 and the system was stable, client receives about 2500 calls a day there's no way i am upgrading back to 5.0.18 to wait for it to crash and have the right traces...

Yaze.
Chaos, Panic and Disorder, my work here is done.

 

[hairlessupportmonkey]

you know - avaya asking for wireshark traces make it all sound so easy!

That does my head in

Avaya should build in some more packet monitoring on their OWN fecking LAN ports - i mean its called an IP office ffs!

In my eyes, asking for wireshark traces is a total cop out by avaya, as they know full well hardly anyone has the time or customer downtime while you fart around on their switch taking 2500 calls a day.....

 

[CIDCrane]

I agree, everytime I have an IP issue they ask for more wireshark traces and when I confront them on what the traces I am seeing coming from the IPO mean they never have a good answer for me, the definitely need to have some better built in tools for these things