https://www.zdnet.com/article/a-lesson-for-the-cloud-100-percent-uptime-achieved-for-16-years/
--- Lelio Fulgenzi, B.A. | Senior Analyst Computing and Communications Services | University of Guelph Room 037 Animal Science & Nutrition Bldg | 50 Stone Rd E | Guelph, ON | N1G 2W1 519-824-4120 Ext. 56354 | [email protected]<mailto:[email protected]> www.uoguelph.ca/ccs<http://www.uoguelph.ca/ccs> | @UofGCCS on Instagram, Twitter and Facebook [University of Guelph Cornerstone with Improve Life tagline] From: cisco-voip <[email protected]> On Behalf Of Anthony Holloway Sent: Thursday, July 12, 2018 12:19 PM To: Gary Parker <[email protected]> Cc: cisco-voip voyp list <[email protected]> Subject: Re: [cisco-voip] 7832 Real-time Device Status To all the people who say: "What is this, a Windows server that I have to reboot?", yes, sometimes you have to reboot these things. It may not be the direct fault of the OS, but at the same time, you are not given the full access/knowledge necessary to restart specific problematic processes Cisco has created, and as such, a reboot can clear those issues. And since I'm on my soap box: Your system should be rebooted regularly when you apply your patches/updates/upgrades anyway, so you should never see uptime that's 1,000+ days. Though, I still see egregious uptimes out in the field ranging from 1 year to 5 years. On Thu, Jul 12, 2018 at 3:09 AM Gary Parker <[email protected]<mailto:[email protected]>> wrote: > On 11 Jul 2018, at 23:20, Anthony Holloway > <[email protected]<mailto:avholloway%[email protected]>> > wrote: > > Put a piece of black tape on your monitor where the IP should be; that's what > my dad did to fix the check engine light. Well, we happened to have a complete shutdown of our datacenter last night, which meant the whole cluster was rebooted, and it’s working properly today. ¯\_(ツ)_/¯ Gary
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
