Rebooting S87xx servers once a year?

[S8700Girl]

Hi,

I was informed by Avaya that the S87xx servers should be rebooted at least once a year. They say that they are like computers and that they will run better and longer. I was wondering if anyone makes a habit of rebooting these servers on a regular basis? Thanks.

 

[phoneguy55]

nope. I would let them run forever. A reboot wouldn't hurt but I haven't read anything that says a reboot is necessary.

 

[MasterRacker]

I've been told that about my S8300 also, but I can't find a written reference.

I reboot my Intuity LX every 90 days per Avaya. We had some wierd voice mail issues and that was one of the first things the Avaya tech wanted me to do. Cleared it right up. That system will also actually throw a warning when it's been over 90 days since the last reboot. It's also Linux based.

_____
Jeff
[small][purple]It's never too early to begin preparing for [/purple]International Talk Like a Pirate Day
"The software I buy sucks, The software I write sucks. It's time to give up and have a beer..." - Me[/small]

 

[big70]

like phoneguy55 say,s let them run forever..

It can run for ever, but if you reboot it then you never now what happens.

moved one S8720/v5.0 this weekend and the second server never went active again. When i did the interchange to remove the first one no problem then shutdown poefff.

Greets Peter

 

[Mitch672]

These servers are running Linux. Linux is NOT perfect, and an occasional reboot could not hurt anything. I would of course make a FULL backup before a powerdown/reboot, in case it doesn't come back up, and you need to get it replaced.

The danger in not rebooting these S-Series servers is, you will eventually have a powerfailure, if your Linux boot record is corrupted, or any other # of problems occur, your system may not reboot. If you plan the reboot, and make a full backup on an external device/machine, via FTP or SCP or SFTP, then you will be prepared, in case it doesn't come back, rather than be in a panic after a power failure or catastrophic failure of the S-Series server to come back up.

AVAYA has recomendations for the IALX to be rebooted every 180 days, it used to be every 90 days (was easy to say do it with every new season). Of course they have a "242" day bug, if your audix has been running for longer than 242 days, it will no longer answer calls and must be rebooted. This was their solution to the issue

I should say I work for a Business Partner, and we usually end up powercycling a machine at least twice a year, due to scheduled building power downs, for the most part.

Mitch


AVAYA Certified Specialist

 

[phonebiz]

This is old information for long time Linux users, but relevant to those running Communication Manager versions 1.x and 2.x. These CM releases use Linux kernel version 2.4.20. The 2.4.x kernel suffers from an uptime rollover bug. At 497 days of uptime, the uptime counter rolls back to zero and starts over.

If you allow your CM 1.x or 2.x system to reach 497 days, you will be forced to reboot. If it is a duplicated system, you will have to reboot BOTH servers at the same time. Avaya has 3 different field loads that solve this issue, but assuming you will be upgrading your dinosaur soon, a simple reboot prior to the 497 days will solve your problem (for another 497 days).

Run the command "uptime" from the shell to see how long your Linux server has been up.

An affected system shows "Time Sync Err". Duplicated systems have repeating duplication alarms and filesync errors.

See Avaya PSN# 252U for additional details.