cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
330
Views
0
Helpful
2
Replies

Degraded expressway node in cluster, how to stop its call processing

iverson.justin
Level 1
Level 1

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

1 Accepted Solution

Accepted Solutions

iverson.justin
Level 1
Level 1

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 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd65321

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc25546

View solution in original post

2 Replies 2

Refer Remove a Dead Peer From a Cluster (Permanently) and Remove a Live Peer From a Cluster (Permanently)

 

https://www.cisco.com/c/dam/en/us/td/docs/voice_ip_comm/expressway/config_guide/X12-5/Cisco-Expressway-Cluster-Creation-and-Maintenance-Deployment-Guide-X12-5.pdf



Response Signature


iverson.justin
Level 1
Level 1

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 

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwd65321

https://bst.cloudapps.cisco.com/bugsearch/bug/CSCwc25546