12-07-2022 11:57 AM
Question, we currently have a Expressway C and E cluster, 2 & 2. One of the Expressway Es is degraded, can't access web interface, can't get xstatus/xconfiguration. TAC is suggesting we reset the node in CLI using tsh. However our Express C and E still see the as SIP active and the degraded node is taking calls. Without access to the GUI not sure how to put this node into maintenance mode and stop it from taking calls. I guess we could remove it from Express C zones and block Express E on FW from external clients? The degraded node is also the Configuration primary so once it does get restored I am sure we'll run into Cluster database delays.
Thanks
Solved! Go to Solution.
12-11-2022 11:02 AM
TAC and us were finally able to resolve. Looks like two pretty big bugs when you restart a express node. We had to upgrade to 14.2
12-08-2022 12:34 AM - edited 12-08-2022 12:35 AM
Refer Remove a Dead Peer From a Cluster (Permanently) and Remove a Live Peer From a Cluster (Permanently)
12-11-2022 11:02 AM
TAC and us were finally able to resolve. Looks like two pretty big bugs when you restart a express node. We had to upgrade to 14.2
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide