« previous next »
Pages: [1]   Go Down

Author Topic: Best Practices for Scheduled Reboots  (Read 896 times)

Offline griam01

  • Contributer
  • *
  • Posts: 27
  • Country: us
  • Karma: +0/-0
    • View Profile
Best Practices for Scheduled Reboots
« on: September 18, 2019, 08:56:06 AM »
Looking to see what everyone else does for reboot schedules for their virtual systems.  Have been running into instances of the system completely locking up (cannot putty to it, cannot load web gui, cannot console to it, but can ping the IP).  A hard reboot resolves the issue.  In troubleshooting with Mitel, they said that the uptimes were over 1 year and that caused the issue.  So what is everyone's best practice for a multi tenant virtual system with resiliency, 3300, MBG, MiCollab, MiCC and Call Recording.  Thanks in advance for your time. 
Logged

Offline VinceWhirlwind

  • Hero Member
  • *****
  • Posts: 899
  • Country: au
  • Karma: +31/-0
    • View Profile
Re: Best Practices for Scheduled Reboots
« Reply #1 on: September 19, 2019, 01:15:52 AM »
Just going through a bunch of controllers on a cluster, uptime is:
116, 23, 506, 190, 8, 86, 170, 145, 222, 51.
Most of the controller reboots were probably recent upgrades or local power outages.
The MiCollab uptime is <24 hours, cos it locked up yesterday.
Logged

Pages: [1]   Go Up
« previous next »
 

Sitemap 1 2 3 4 5 6 7 8 9 10