Hi, Even the factory reset might not work, because the factory-reset image is not in the OVA and you need to upload it and add also a file with the release key somewhere in /mnt/.../factoryxxx/rk I was recently into this nightmare when I tried to change one of the hostnames, without following the documented procedure.
Regards, John On Wed, Oct 24, 2018 at 11:03 PM Dana Tong <[email protected]> wrote: > 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 <[email protected]> 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 <[email protected]> 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 >> [email protected] >> https://puck.nether.net/mailman/listinfo/cisco-voip >> > _______________________________________________ > cisco-voip mailing list > [email protected] > https://puck.nether.net/mailman/listinfo/cisco-voip >
_______________________________________________ cisco-voip mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-voip
