XenMobile 10 Cluster installation Here is the task that would be completed in order to implement a XenMobile 10 Cluster. For this example, running on my lab, I am using XenServer 6.5 SP1 as hypervisor and SQL 2014 installed on a Windows 2012 R2 as DB server. After the virtual appliance has been imported, power it on. Logon with default username which is admin. You will be prompted to change the password during the initial configuration. Enter the following network information for the virtual appliance: IP Address Subnet Mask Gateway Primary DNS Secondary DNS (optional) Confirm the settings to continue
Type Y and press Enter Here I will chose N and press Enter For the Database connection, remote is required in order to complete the cluster installation.
I am using a remote SQL Server on my lab so, enter mi and press Enter. Enter the following information to connect to the remote SQL Server: SSL Use Server Port Username Password Database Name Type Y and press Enter to commit settings Note: XenMobile 10 has to create the database so the credentials to connect to remote SQL Server need dbcreator role according to the product documentation (but also sysadmin role to avoid error messages) For Cluster, type Y
Provide the Xenmobile Server FQDN (external name) Type Y and Enter to commit the settings.
Change if required the default communication ports or let it like proposed and type Y and press Enter to commit the settings. Prefer to use the same password for all the certificates, type Y and press Enter Provide password twice, type Y and press Enter to commit the settings.
Use the default username or enter a new one, enter twice a password, type Y and press Enter to commit the settings For Upgrade, type N and press Enter
Wait for the configuration app and main app to restart Shutdown the XenMobile virtual appliance in the Main Menu, go to System Menu, and choose Shutdown Server option. Once the XenMobile virtual Appliance is shutdown, make a copy or a clone. When the copy or clone process is completed, power on the new virtual appliance. Log on the Appliance
Type 0 and press Enter to go in the Configuration Menu Type 1 and press Enter to go in the Network Menu Type Y and press Enter to proceed
Change the IP address, type Y and press Enter to reboot When the restart process is finished launch and web browser and point to https://xms_ip_address:8443. Note: The IP address can be either of the cluster members. Logon using the credentials entered earlier during the initial system configuration Click on Start
For licensing, select Configure License, Remote, provide the IP address of the license server and click Test Connection On the connection is verified, the available licenses appear. If you have more than 1, select the 1 you want and activate it. Click Next Enable the Notification Expiration, provide an email and click Next
Click Import and provide the following information: Keystore PKCS#12 APNs Your_cert.pfx Password Click Import
A pop-up appear, click OK Click Import and provide the following information: Keystore PKCS#12 Server Your_cert.pfx Password
Click Import Click Next and provide the NetScaler Gateway information
Click Next and provide the information to connect to LDAP/Active Directory Click Next Provide Notification Server settings and click Test Configuration
Provide an email and click Send Click OK Optionally you could modify if requested the Advanced Settings. Click Next
Verify settings and click Finish Click Start Managing Apps and Devices You need to reboot each XenMobile server cluster Nodes one at a time Reboot each XenMobile virtual appliance in the cluster one at a time. After the reboots are completed, log back onto the web console by browsing to https://ip address:8443. The IP address can be either of the cluster members. After logging back onto the XenMobile web console, click the tool/wrench icon next to the username.
Click Cluster Information under Advanced. Verify the Cluster Members and review the Messages. Review the Tasks and verify the Hazelcast Cluster Information. The next article will be on Configure Load Balancing of XMS Cluster in Netscaler. Stay tuned ;)