Mobility Experts Team: XenMobile AppController and HA Clustering -
1. Overview of this document
The purpose of this document is to provide a step by configuration step of XenMobile AppController high availability (HA) clustering. When and HA Clustering is configured, Cluster Head used as database support and service nodes communicate to Head for Cluster database information
Prerequisites for HA :.
- Two virtual machines AppController and they should be of the same construction.
- Three free internal IP addresses. One for primary APPC, APPC for second and third secondary virtual IP is used to access these HA paired APPC
Prerequisites for Clustering :.
- must have multiple APPC virtual machine with separate IP address assigned to each service node of the virtual machine. APPC virtual machines must have the same construction.
- A VServer load balancer and Content Switching Vserver should be created to load balance traffic to these service nodes.
2. HA configuration between two AppControllers
Before continuing, the AppController virtual image must be downloaded from the website Citrix Web. (Www.citrix.com)
- To install AppController on the XenServer platform, the VM file .xva extension must be downloaded
- AppController To install the VMware platform, the virtual machine file with .ova extension must be downloaded
Note: After downloading successfully AppController virtual image, download the same platform XenServer / VMWare and make another copy of the VM HA and 2 to 3 copies for clustering (ie service nodes).
login prompt for AppController will be displayed once the import process is complete.
Log for CLI AppController
Username: administration
Password: password
main menu is displayed, Enter 0 to express Setup
Enter 1 to configure the IP address, subnet mask
AppController configured with the following:
IP address:
Subnet Mask: 255.255.255.0
Enter 2 to configure the default gateway
Enter the default gateway address
Enter 5 to confirm the changes
Enter Y to restart AppController
Repeat the previous steps on all other virtual machines AppController. By doing this, IP address assignment for virtual machines will be done.
After successfully assigned IP addresses, select the two virtual machines AppController to configure HA. Connect to the AppController primary CLI and select option 1.
Select option 1 for role Preference.
Select Option 1. By selecting option 1, it means that this virtual machine is your primary machine.
Select option 2 to assign virtual IP and Peer IP.
Virtual IP is the common IP address used to access AppController active / primary.
Peer IP is the IP address of another configuration of the AppController virtual machine for HA.
shared key could be an alpha numeric value that must be entered in the secondary service.
Provide the information below and click "y" to confirm the changes.
Select option 3 and press "y" to enable HA.
Log in to the CLI secondary AppController and select option 1 to set HA.
Select 1 to assign the role of preference.
Select option 2, which is secondary. Now it will be your secondary device.
Select option 2 to enter IP peer and shared key primary AppController.
in Peer ID address, enter the IP address of the primary AppController and provide the shared key that was entered in the steps above.
Select 3 to turn HA and hit "y" to confirm.
If you select option 4, you can see the current status of HA.
3. AppController initial configuration for HA pair
Enter the following URL in the browser by providing the correct IP address Virtrual which was awarded in the above section
https :. // : 4443 / ControlPoint /
Log in using the following credentials:
Username: administrator
Password password: password
You will be presented with the following screen. First we are going to run through the wizard Configure network.
You will be prompted to change the administrator password. Type
Current Password: password
New Password:
Click Next
Enter the following parameters for system settings
hostname:
IP address:
subnet mask:
default gateway:
Note :. DNS A record must be created for AppController FQDN in DNS
Enter the following parameters for the Active Directory configuration [
server: (this is the IP address of your domain controller)
domain
service account:
DN base: the point at the user DN
Password:
Note: Select Use secure connection if your domain controller only accepts secure connections
(ie port 636).
Enter the following parameters for the Configuration of the NTP server
NTP: (general best practice is to use the DC as time server)
time Zone: US / Eastern
Enter the following parameters for the DNS configuration
DNS suffixes
primary and secondary IP Address:
Enter following information for your Flux Email Settings
mail server:
Port: 25
Email: (the sending account for workflow)
A summary of all the settings is displayed. Click Save and click Yes to restart the AppController
Note:.? How to check HA works well
Power Off the AppController active virtual machine and open a Web browser and enter the virtual IP address / hostname that resolves to this IP address. If you are able to authenticate and view applications in Web Receiver, it means that your HA works well .
4. Cluster Configuration AppController
Log in to the CLI and primary AppController 2. Select
Among the options aviliable select 3 Create Cluster and provide a shared key that will be used when configuring service nodes
Note :. This virtual machine will be your Cluster Head. Provide IP AppController Vitrual your head cluster IP address in the service nodes
Note :. Before preparing the AppController department heads, please make sure that you assign IP addresses to the Head AppController service follwing steps in section 2 of this document.
Log on to the CLI anyone to AppController that has been assigned an IP address (ie Service Nodes AppControllers), using the following credentials.
Username: admin
Password: password ..
Select option 2 for Clustering
Select option 4, to join the Cluster
Provide HA virtual IP address that your environment Cluster Head IP address and enter the shared key that was provided in step 2 of this section and enter "y" to restart the AppController.
Log in to the rest of AppControllers Service node and repeat the above steps
Note :. After the configuration on the node AppControllers individual service, you can directly access any service Node AppController using their IP address
. 5. NetScaler Configuration for Clustering AppController.
Below, the section helps you configure content switching NetScaler strategies to manage the AppController reunion.
Log in to NetScaler administration console.
develop traffic management and expand Load Balancing and click Services.
In the right panel. Click Add, provide the name of the service as Cluster Head and provide details of the IP address Cluster Head server, select HTTP and define the port 80.
Under the tab advanced, go to the option Cache Redirection set the cache type to the regular server
Provide cluster head of the ID of the server as the server ID and click Create
Note: .. ID server can be found when configuring AppController Clustering (ie Article 4 of this document)
again Click Add to create another service, providing the service name as service node and provide the IP address of the cluster node server, select HTTP and set the port as 80.
on the Advanced tab, go to Cache forwarding option, define the cache-type to regular server.
provide the server ID as ID server service node and click Create.
Note: .. If you have more than one cluster node please repeat the above step for each node
now, click on virtual servers in load balancing
Click Add, specify the virtual server name, from the Service select all nodes in the cluster tab ( in this case, I have only one cluster node) and uncheck the checkbox directly addressable, click Yes to Clear & Disable pop up.
in the same window, click the Method tab and persistence in the Persistence section, select the type Persistence Rule drop-down list. Please copy and paste the article below and answer the rule mentioned below
Rule :.
HTTP.REQ.HEADER ( "cookie") VALUE (0) .TYPECAST_NVLIST_T ( '=', ';') VALUE ( "ACNODEID")
Response rule: .. HTTP.RES.HEADER ( "Set-cookie") VALUE (0) .TYPECAST_NVLIST_T ( '=', ';') VALUE ( "ACNODEID".)
once you enter the above rule and the rule of answer, click Create.
again Click Add, specify the virtual server name, from the Service select cluster heads tab and all nodes (in this case, I have only one cluster node) and uncheck the checkbox directly addressable, click Yes in Clear & Disable pop up.
in same window, click the method tab and persistence in the persistence section, select the type CUSTOMSERVERID persistence in the dropdown list. please copy and paste the following rule to the rule text box
Rule:. URLQUERY CONTAINS sid =
Once you enter the above rule. Click Create.
Ensure both LB servers you created in the above should be in Up state.
Develop traffic management, content switching Expand and click Policies.
In the panel Right Hand Side, Click Add. Provide the name of the policy and add the following expression under the table expression
Expression: .. HTTP.REQ.HEADER ( "Cookie") CONTAINS ( "ACNODEID")
again Click Add. Provide the name of the policy and add the following expression under the table expression
Expression :. HTTP.REQ.URL.CONTAINS ( "SID =")
Now click on Virtual Servers in content switching.
Click Add, specify the virtual server name, provide the IP address, select the SSL protocol and set the Port to 443.
Under Policies tab using the option of integration policy insert the policies that you created in the previous steps with URL policy with the next highest priority policy Cookie and also insert the default policy. Also select the target accordingly, Set Cookie LB target as the default policy
On the Settings tab Add SSL certificate issued to the FQDN and APPC click Create.
Note: You must have a proper DNS entry for the virtual IP address to resolve FQDN APPC
Check the status of the virtual server you created
[
You can also visit the URL below for more information:
/ blogs / 2014/03/14 / Control-xenmobile-ha- cluster-for-the big business powered by NetScaler /
your Virtualization infrastructure can be a bit intimidating, especially if you are a small or medium sized business or a small site in a large company. I saw some pretty impressive large deployments scale VDI support 40,000 virtual machines (desktops) and a lot of literature and reference architectures refer to these impressive deployments. 
Sometimes many of us in the IT forget that technology is here to help companies move on, not get into a side business of acquiring IT architects or consultants and create new roles requiring specialized dedicated system administrators! Sometimes the simplest solutions are the best and really bring a smile to your face ... .. just like my furry friend Elvis!