Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

System randomly reboots during merge config

Status
Not open for further replies.

milestoned

Vendor
Feb 27, 2003
154
US
Two things that I'm noticing.

1) the status message when pulling configs "aking 2, 3,..."
2) Merge config status ticks off slow and sometime fails at differnt % intervals.

If the merge config fails most times it will reboot the switch.

IP 406V2 3.1 (65)
VM Pro 3.1 (21)
CCC 5.0 (33)
60 5410 Phones connected

The config size is normal so I'm not seeing the normal corruption issues. The network that this rides on seems to be very slow. Does any one think it's possible that the IP Office is getting hammered with broadcast packets and is making it fail?
 
Only time I have had issues with merges causing reboots has been corruption. Rewrite of DB cured problems.


Jamie Green

Fooball is not a matter of life and death-It is far more important!!!!
 
Do you have any problems if you connect your Manager computer directly on the IPO, if not it's probably network related.
Either to much traffic or bad cables.

If you have this problem you may end up with a messed up configuration if your unlucky because of unit not receiving complete config and rebooting.
 
You could Save your current configuration. Default IP Office using Manager, not DTE. Recieve the default config. Test for any problems using the default config. IF you still have problems you may have to reinstall Manager next or it may be in IP Office unit assuming your connections are good.
Just a thought.

"A politician is a fellow who will lay down your life for his country.
 
The server was and is directly connected to the IP Office and was during these issues. I have defaulted the switch thru the DTE and reinstalled the Admin suite and I'm not having any problems yet. I tried to make it happen by pulling config and then meging over and over again and couldn't. Avaya wants a trace but I can't seem to make it happen anymore.

Who knows,

Thanks
 
Make sure all your user names do not have any funky characters, spaces, or any starting with a number. Had the same problem with reboots and renamed some users with some luck on the reboots.

To Us and Those Like Us, Damn Few Left
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top