Call Manager 12.0 Restart HAProxy service impact

[stuart.pannell]

Hi all,

Is there anyone out there that knows the impact if any of restarting the HAproxy services on Cisco  Call Manager?

We have hit a bug and TAC are going to come in and fix it but they need to reconfigure and restart the haproxy service but no one can tell me if there will be any impact to the customer. 

Cheers

Stuart

[Nithin Eluvathingal · Accepted solution]

Asper the below, Haproxy restart is done deactivating and  activating the TFTP services. There won’t be much impact on user if it’s just HAproxy. 

HAProxy is designed to use both Tomcat certificate on port 6972 and callmanager certificate on 6971. So regenerating / updating tomcat/callmanager certificate requires HAProxy service to be restarted. HAProxy can be restarted by deactivating and activating TFTP Service. From CUCM 11.0 , HTTPS support for TFTP is provided using HAProxy.

[Vaijanath Sonvane]

This is an old thread but today I came across one issue and it was related to Cisco HAProxy service and wanted to share the information:

Cisco HAProxy is a fast and reliable solution that offers high availability, load balancing, and proxy capabilities for HTTP-based applications. CiscoHA Proxy frontends all the incoming web traffic into Unified Communication Manager and IM and Presence Service.

Restarting Cisco HAProxy service does not affect existing connections but it will affect new HTTP/HTTPs connections that are trying to connect while service is restarting.

You can restart Cisco HA Proxy service in two ways:

1. Restart of the Cisco Tomcat service will internally restart the HAProxy service.
2. You can issue CUCM command utils service restart Cisco HAProxy