Netonix Forums

I'm just curious about how many people restart their system?? from time to times.
and how often you to do if your doing?

would also like to hear if you don't it and why ??

Not sure what you mean by system?

Routers - Cisco 2951, maybe once a year
AP's - airMAX M5/M2 Rockets, once or twice a year - they "sometimes" act up
Client radios, airMAX M5/M2, when ever needed, not very often that we do, customers sometimes do it themselves
Switches - WS-24-400A, when ever I put new firmware on

sirhc wrote:Not sure what you mean by system?
...
Switches - WS-24-400A, when ever I put new firmware on

If/when I take a service window and I know what I am about to do will cause a disruption, I often do a reboot prior to flashing JIC the unit is limping. Flashing is always less risky on a fresh boot.

After a while you get a feel for which systems can run on forever and which ones need more TLC. At the mill we had some systems that were powered off every year on our scheduled yearly power outage, and other systems we dared not shut down and so kept going with generators. Every year there was a percentage of units that would not come back up after the outage.

We don't reboot anything on purpose regularly. Only when/if it needs it.
I do a reboot before I do a firmware upgrade as others have mentioned.

Just the other day a Mikrotik router died on me after being powered up for 190 days.... The question is, if I had rebooted it monthly, would it still have died? Would it have died earlier? who knows...

The WS is forcing us to think of how we design our network. While it will always stay routed, customer traffic that used to be inside VPLS tunnels may move to VLAN's between towers. Taking the pressure off of the tower router. *shrug* still chewing on it.

thanks for your response, because I ask is that is that I think of putting my towers to restart one by one each month, just to empty the buffer and see and it gives some effect

We never reboot unless upgrading and then, like others, reboot before hand. Rebooting "bandaids" issues, it doesn't fix them. I prefer to find the issue rather than just sweeping it away. I have servers up for 2 years, Cisco switches up for 2 years, Ubiquiti gear up for 300 days.... it just runs.

Never reboot really either. Everything is normally only rebooted because of a firmware upgrade. My previous company that I worked for was using moto gear and that was rebooted once a month. I never really was sure why as I was not making the decisions.

I only reboot routers or switches for firmware updates typically. I still have a few rb493 units that need a reboot to straighten them up but i've depreciated those in favor of the rb850Gx2 which has been flawless so far.

Same with radios, only reboot for firmware updates. Every now and then reboot an AP, but I try to stay on 'stable' firmwares to avoid that need. Client radios are on a ping watchdog and so will reboot on their own typically. Customers might reboot if they think there is an issue but it's typically their home router.

I have a testing site on airCRM and seem to be rebooting devices 10x more often for updates or issues. I've had to do some scripting on radios to overcome some long standing bugs and avoid reboots. That's 'beta' though so to some degree expected.

Rebooting equipment means interruption at some customers. Especially if you're a business customer running VPN tunnels to different departments, having the ISP to reboot is equipment now and then is annoying.

I personally only reboot if it's required. I'm glad if stuff is running days after days after da....
Just had a look at a customer radio. It has been running for 240 days. In other words it has been running since it was installed

If you need to reboot, better use some time to find out why reboot is needed.

Before Chris came with the WISP switch I had to reboot my TOUGHswitches as they slowed down performance. So rebooting is often a required in a broken system, not a working system in my opinion...