this is an ip office which randomly reboots and we can't see why. config has been checked and reloaded, psu has been changed, ip office has been changed, ip office is now on a ups, environment is air conned [cool] and no interference nearby [eg copier, large screen vdus etc] : any ideas?
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 SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
reboots on its own
- Thread starter 430s
- Start date
When running the monitor application using the correct tick box's for system reboot you should be able to search the txt file for either cause codes (BT errors other than 16/17 normally 127/79/65/38 ) or search for contact lost. These will show you when the system reboot, one classic is the customers LAN , if they run SNMP queries (The lan administrator has set up all the monitoring tools on the network).
TRy to get the customer to run a sniffer at the same time this would normally show details as well, to assist you in finding the problem, check the amount of network traffic on the LAn as well.
Therer is not just one reason why this happens but one reason from a list, sorry its over to you.
![[lightsaber]](/data/assets/smilies/lightsaber.gif "[lightsaber] [lightsaber]")
P.S.
Make sure none of the users/groups have any spaces of characters other than 0-9 and A-Z in them as well
TRy to get the customer to run a sniffer at the same time this would normally show details as well, to assist you in finding the problem, check the amount of network traffic on the LAn as well.
Therer is not just one reason why this happens but one reason from a list, sorry its over to you.
P.S.
Make sure none of the users/groups have any spaces of characters other than 0-9 and A-Z in them as well
Don't know if you have resolved this issue but one possible cause is if you have a large paging group defined for the switch. We discovered that the reboots were occurring at the time of messages being paged. We had one install where this was an issue and Avaya provided a patch specifically to deal with this problem. No problems with reboots since.
I have an IPO 406 Doing the same thing. Ive replaced 1 30 port module and also the IPO 406 module itself. System is located in a rack in an air conditioned environment. Isolated power with Isolated ground.
Im starting to get use reboots with this system.
What a nightmare!!!
Im starting to get use reboots with this system.
What a nightmare!!!
From my experience the majority of system reboots are caused by either incorrect programming of the switch or a particular set of circumstances that highlight a bit of buggy code.
IPOJedi is right to suggest that the monitor application is the way to go forward, particularly looking for contact lost sections in it which are followed by contact made and a very short uptime in ms.
It would also be worth leaving a laptop connected to the serial port, saving all output to file as this may catch something useful that doesn't get output to the monitor file.
I would be happy to look at any saved monitor file for you to help get your problems resolved.
IPOJedi is right to suggest that the monitor application is the way to go forward, particularly looking for contact lost sections in it which are followed by contact made and a very short uptime in ms.
It would also be worth leaving a laptop connected to the serial port, saving all output to file as this may catch something useful that doesn't get output to the monitor file.
I would be happy to look at any saved monitor file for you to help get your problems resolved.
TheBoyWonder
Technical User
There is currently and issue with Phone30 modules rebooting. A patch is due out shortly to rectify the problem. A monitor trace will indicate whether the IPO is rebooting or whether calls a dropping ie. due to a module rebooting.
- Status
Similar threads
