[cisco-voip] Expressway version X8.11.x

[Dana Tong]

This is after the TAC did a factory reset and rebuilt the cluster. It was perfectly happy before it shat itself again. It's a cluster f@&$.

The edge cluster is stable. Only the core.

On 25 Oct 2018, at 4:05 am, Matt Jacobson <m4ttjacobson at gmail.com<mailto:m4ttjacobson at gmail.com>> wrote:

You have some alerts, I would check what they say. We have several clusters on x8.11.x all running fine, never seen anything like this as well. Possibly look through the event or configuration logs for any cluster related changes or events on that specific node.

And then to “fix” this... take a full backup, read up on how to rejoin a node to a cluster after a factory reset in cluster maintenance doc, and I’d open a tac case before doing so.

On Wed, Oct 24, 2018 at 10:50 Dana Tong <dana.tong at yellit.com.au<mailto:dana.tong at yellit.com.au>> wrote:
What is it with new Expressway code?

I have a cluster that was working happily and no one touched the config but all of a sudden it says that it is going to factory reset itself.

Is there any way to avoid this?

<image001.png>
_______________________________________________
cisco-voip mailing list
cisco-voip at puck.nether.net<mailto:cisco-voip at puck.nether.net>
https://puck.nether.net/mailman/listinfo/cisco-voip
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181024/95f4c90e/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 43803 bytes
Desc: image001.png
URL: <https://puck.nether.net/pipermail/cisco-voip/attachments/20181024/95f4c90e/attachment.png>