[cisco-voip] 7832 Real-time Device Status

[Anthony Holloway]

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 <G.J.Parker at lboro.ac.uk> wrote:

>
>
> > On 11 Jul 2018, at 23:20, Anthony Holloway <
> avholloway+cisco-voip at gmail.com> 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20180712/ee4f5d76/attachment.html>