How to Configure LHC to use Custom Port

Follow below steps to configure Citrix Broker and Citrix High Availability services to use custom port.

• Modify the default storefront port of Citrix Broker service via cmd or PowerShell by using below command

User-added image
• Modify the storefront port of High Availability service to be same as that of Broker service. Although SF port for this gets updated automatically but still change it explicitly by using below command.

User-added image
• Launching Citrix studio will prompt you for “Automatic Site Upgrade” and continuing with the upgrade should update the broker service port changes returning with 1 successful task.

User-added image

• Follow the above steps on all the delivery controllers and complete automatic site upgrade via Citrix studio.

• Run netsh http show urlacl on all the DDCs and ensure you see Reserved URLs of all the broker WCF endpoints for CitrixHighAvailabilityService and they are in ‘Listening’ state.

Example:


• Modify the Storefront GUI port via SF console to match with the Storefront port configured for Citrix Broker and Citrix HA services.

User-added image
• Validate and confirm, you are able to enumerate and launch applications successfully.

• Switch to LHC outage mode and monitor the events on DDC to confirm secondary broker service has taken over to serve user requests.

• Validate and confirm, you are able to enumerate and launch applications successfully in LHC outage mode.

LHC Outage Mode:

During the period directly after the database connection is lost, resource (Application/Desktop) enumerations in StoreFront and Session launches may fail. In practice it takes ~2 minutes before the site starts working (Resources enumerating and session launching). The site will not be fully functional until all the machines have re-registered which may take up to 10 minutes (You can decrease this interval via registry) . Recovery from the outage follows a similar flow.

Step Timeline Description
1 0 seconds DDCs lose connectivity to the Site Database.
2 0 – 60 seconds Services are unable to contact site database and report errors in the event log.
3 120 seconds Broker Service hands over the XML communication to the High Availability Service (Secondary Broker).
4 120 seconds StoreFront is no longer able to communicate with the Secondary DDCs. All Enumerations are going to the Primary DDC.
5 120 – 600 seconds VDAs begin to register with the Secondary Broker on the Primary DDC.
6 120 – 600 seconds Site is ready.

The process of exiting outage

Step Timeline Description
1 0 seconds DDCs gain connectivity to the Site Database.
2 0 – 60 seconds Services connect to the Site Database and report connection in the event log.
3 120 seconds High Availability Service (Secondary Broker) hands over the XML communication to the Broker Service.
4 120 seconds StoreFront is able to communicate with all the DDCs
5 120-600 seconds VDAs begin to register with the Broker Service a DDC in their List of DDCs.
6 120-600 seconds Site is ready.

Related:

Leave a Reply