How to add new XenMobile nodes in environments with Rolling Patches installed
book
Article ID: CTX331520
calendar_today
Updated On:
Description
Step by step on how to add new XenMobile nodes when the the environment already has Rolling Patches installed
Instructions
Prerequisites:
Same MSSQL Database server:
FQDN/IP
Service Account
Same database name
Valid PKI passphrase
The easiest way to check if you have a valid SQL service account/password as well as a valid PKI passphrase is as follows:
Login to one of your existing XenMobile nodes Command Line interface
Select [ 2 ] System on the Main Menu
Select [ 12 ] Advanced Settingsnext
Select [ 9 ] Cloud Migration Credential Check next
Check your SQL service account password and PKI passphrase next, make sure the check passes, the message Passed should appear on the screen:
Instructions:
Take snapshots of your existing nodes
Take backups of your XenMobile database
Create a new virtual machine using the base release of XenMobile as template
In this case go to Citrix Downloads and download the 10.13 file for your respective hypervisor
Boot the virtual machine
Configure basic networking and CLI user accounts
Configure the database, this is key:
Point the same database server IP or name as the other nodes in the cluster
Use the same database service account as the other nodes
Use the same exact database name
If the above steps are correct then the XenMobile CLI should say that the "Database already exists":
As you can see the new node (10.13 base release) is joining a 10.13 Rolling Patch 4 environment because the schema version of the database only cares about the base release 10.13000
The next step is to enter your PKI passphrase
Once that's completed the server will continue with the boot process
Once the boot process completes make sure to make the necessary changes in the CLI, for example modifying the XenMobile internal firewall to enable SSH and other, environment specific, changes
Login to the XenMobile web console navigating directly to the new node IP address (https://ipaddress:4443)
Once logged in, navigate to Release Management and upload the appropriate Rolling Patch binary to match the rest of the environment
The server will reboot and process the upgrade .bin file
Once completed your new node is a full member of your cluster
Never leave the new node without a rolling patch that matches the rest of the nodes, the above steps need to be perform on the same activity.