I have definitely encountered this. It was a new install, not yet in production, and I think I even figured it out was the vmware being corrupt but couldn't get it fixed and just reinstalled.
Crazy! Matthew Loraditch Sr. Network Engineer p: 443.541.1518 w: www.heliontechnologies.com | e: mloradi...@heliontechnologies.com From: cisco-voip <cisco-voip-boun...@puck.nether.net> On Behalf Of Pawlowski, Adam Sent: Friday, April 26, 2019 1:30 PM To: 'cisco-voip@puck.nether.net' <cisco-voip@puck.nether.net> Subject: Re: [cisco-voip] looks like we're back to rebooting the cluster Maybe you won't be rebooting it if you don't patch out for this one https://www.cisco.com/c/en/us/support/docs/field-notices/703/fn70379.html
_______________________________________________ cisco-voip mailing list cisco-voip@puck.nether.net https://puck.nether.net/mailman/listinfo/cisco-voip
