Small Office Reboots Every 7 Minutes 3

[bixtool]

Todays Issue: We upgraded our 412 to 4.2.20 this past weekend, everything went well except one issue. One of our remote sites has a Small Office Edition connected via SCN which is also at 4.2.20. Anyway, the Small Office keeps rebooting every 7 minutes almost to the second. We replaced it with a spare Small Office, changed the power supply, tried a different oulet etc. Rebooting issue still there. When we unplug the ethernet from LAN 1 the issue goes away. Don't know if the upgrade we did on the 412 has any relation to the small office issues or not. Could something on the network be sending some sort of updates every 7 minutes? Or could the 412 be trying to send something? Just wondered if anyone out there has seen this?
Thanks

 

[tlpeter]

Sounds like an ip conflict.



ACSS - SME (IP Office)
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!

 

[bixtool]

The IP conflict is being explored. Any ideas on the seven minute deal? And as far as I know we didn't have any network changes around the time of this issue cropping up, could it be some sort of network loopback? I would think if that was the case it would crash it all together along with other network issues.

 

[tlpeter]

Post a trace with everything from reboot to reboot.



ACSS - SME (IP Office)
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!

 

[kwing112000]

I saw one like this one time. it turned out to be that the remote site had a codec set on the IP trunk that was not supported anymore in 5.0. I would check all my IP trunk settings and make sure your sites are set up properly according to the 4.2 docs. They should be hub and spoke.

Kevin Wing
ACS- Implement IP Office
ACA- Implement IP Office
Carousel Industries

 

[bixtool]

I will check into that, also try to post a trace. Thanks for the help!

 

[Chedzz]

Had the same issue. SCN of 15 IP Offices, once we upgraded to 4.2 the two SoE's in the SCN rebooted at approx same interval as you state above. If we rolled them back to 4.1 they were fine. Not sure of the reason but it seemed that the SoE's weren't up to the task as far as the SCN was concerned. If we took them off the SCN then they would run without issue after being upgraded to 4.2.

I don't see why it would be an IP conflict as none of the IP's have changed and an IP conflict is an IP conflict whether you are on 4.1 or 4.2 so why wasn't it an issue before upgrade?

IMHO it is a memory issue, 4.2 is a larger config than 4.1 and the SoE's simply can't cope with the extra config size and the amount of information that is exchanged between units in an SCN.

We never resolved the issue as the client is planning to upgrade all sites to IP500's soon anyway and in the meantime SCN works fine with a couple of units running S/W one release lower.

 

[tlpeter]

You could be right although sometimes with an upgrade there are more changes in the network because it must go down anyway.
Then the IT guys does his changes too.

I agree with the memory, it is just not big enough.




ACSS - SME (IP Office)
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!

 

[intrigrant]

Small Office's have memory problems in 4.2, Avaya advises to replce them for a 406V2 if 4.2 if needed or keep them on 4.1.

 

[bixtool]

We replaced the SOE with a 406 Friday and everything seems to be fine, memory seems to be the culprit! Thanks again for everyones help.