This blog helps you configure XenMobile Server in cluster mode and load it with NetScaler (NS) compensates. XMS is a single server, the integration between XDM and AppC, so it would take two LoadBalance VIPs (LB VIP) that must be configured on NetScaler level. In the earlier versions of XME we had XDM configured as a cluster and AppC as HA pair cluster. Now, configured in the unified console of XMS, only cluster is
There are two LB VIPs required which are as :.
MDM LB VIP - MDM LB VIPs is required to configure XDM cluster in SSL-bridge mode. These LB VIPs are created at 443 and 8443 ports
MAM LB VIP -. MAM LB VIP is required to speak for Access Gateway to XMS. The LB VIP is created on 8443 port. In the XMS, all traffic from Access Gateway on LB VIP routed to 8443 Port
This can be configured manually or using wizards in the NetScaler
Pre-requirements: ..
- It is assumed that you have the appropriate XMS knots fully configured.
- Two free IP addresses for LB VIPs
- server certificate / s
- AG VIP already set
Visit the URL below, FAQs on XenMobile 10 and NetScaler 10.5 Integration and the steps the XenMobile 10 run Deployment Wizard in NetScaler:
http: //support.citrix. com / article / CTX0430
1. Install the cluster nodes
Based is required on the number of nodes, you must create new VMs and they to same DB [1945004Punkt] and the provision of same PKI certificate passwords . You should also "allow cluster 'to' y 'in CLI guarantee, while configuring the first node.
to the following steps, a new VM to join the cluster.
. 1 Open the console of the new VM and enter a new password for the admin account
2. Enter the network configuration details as below
3. If you want to use the default password for data protection, you can 'y' here otherwise enter 'n' and enter a new password
4. Configure the database so that you can refer to the same DB as that of the previous fully configured VM. the message "database already exists"
5 to see. Give was given for the certificates here, as for the first VM, the same passwords.
6. After entering the password, will complete the initial configuration to the second node.
7. Once the configuration is complete, start the XMS and you are the login prompt
receive 
Note : the login prompt name here would be the same in all the nodes that is the host name of the XMS. This is defined as a control point that both the VMs on the same DB server show / service. They
8. Visit using the UI of the XMS server FQDN. The landing page is the upper right, a tool icon (red in the picture circled below) to find. Click on the.
9. It opens a support program side up. In this page, under Advanced, click on Cluster Information
10. This page will give you all information about the cluster, including cluster member, device connection information, tasks, etc.
11. This is how a new node made member of the cluster. You can add another node using the same method.
1.1. Finding XMS node server IDs
For service IDs of the nodes, perform, see the following steps:
FROM CLI:
1. Login to the CLI of XMS, you want to
2 find the node ID
. Enter choice than 1 in order in clustering navigation 
3. You can download the node ID to see, as shown
Note : same steps Repeat node IDs of all the cluster members in the XMS cluster [zufinden
FROM GUI:
[1945001Registration] 1. Admin console to XMS 
2. In the Support page, click cluster information under Advanced
3. They are the node IDs, see how below
2 shown. Configuring Load Balancing of XMS cluster in NetScaler
Once the required nodes will now be added as members of XMS cluster, you must access this Load Balancing cluster. Since it is a single XMS server console, you must configure SSL bridge on MDM component and MAM component. You also need the DNS address record (NetScaler> Traffic Management> DNS Records> address entries) to refer to configure the XMS FQDN MAM LB VIP. The information required in this blog.
2.1 explained. SSL BRIDGE - MDM LB VIP
In this section we will look at the configuration of SSL Bridge see the wizard in NetScaler with
1 .. Log into NetScaler Gateway
2. In the configuration tab, click XenMobile
3. click Configure (Device Manager Load balancing)
4. Enter the LB VIP
5. Click Next
6. at this VIP add the XMS nodes
7. Enter the XMS server IP
8. Click Add
9. In the same way, add the second node of XMS
10. Click Next and then Finish.
This is the MDM LB VIP create
2.2. SSL offload - by following the steps below
1 MAM LB VIP
, you must configure SSL offload for MAM component on 8443 port. Navigate to Configurations -> Traffic Management -> Load Balancing -> Virtual Server
2. Click "Add"
3. Enter the MAM LB VIP Server Info here
4. protocol should SSL and port should be 8443
. 5 Click 6. After you create a VIP Next
, you have the persistence value
add. 7 Select Persistence as CustomServerID
8. Enter the following value as an expression of
HTTP.REQ.COOKIE.VALUE ( "ACNODEID")
9. Click Save, and you will see this screen with saved settings
10th Since this is on SSL certificate, you need to bind the server certificate. From Advanced on the left side, select Certificates
11. Select the > book brand certificate (see below)
12. It is on server cert key take page, click bind
13. Select the SSL certificate and click Paste
14. Click Next
15. Click Finish
2.3. create Service group
createservice groups by the steps given here following:
Service Group for MDM on port 443
1. Navigate to NetScaler> Traffic management> Load balancing> service groups
2. Add Click
3. Select protocol 4 as SSL_BRIDGE
Click Next
5. Click Done service group
6 to create. In the same manner, create another service group for MDM on port 8443
done 7. Once with MDM, you need for MAM on port 8443
Note to create a service group : you can follow the same steps as described above. Make sure that the protocol selected as SSL
2.4. Creating members for service groups
createmembers for service groups through the steps given here following
1. Open the LB service groups, and click the first (or someone) to add members
2. here I have selected MDM service group on port 443
. 3 4. Click the + next to members
> Click on service members
add. 5 Add Click
6. Enter the IP address of the node
7. Make sure that the port number matches.
8. Repeat steps for other nodes in the cluster
9. Once done, click Close
10. Click Finish
11. Repeat steps for MDM service group on port 8443
Note : Since groups and members are assigned, you would see the status of UP
12. now open the MAM-service group
13. Run have done the same steps as for MDM, and you must add the server IDs, as shown here.
14. You should see all the VIPs in Activated and UP mode
2.5. Binding LB VIPs to service groups
you need to bind the service groups with the LB VIPs. You can do this by performing the steps of
1. Open the MDM-LB (or someone you love)
. 2 on the right side, click on service groups
3. click the> mark in the service group
4. Click 5. bind
Select to bind the same port group
6. Click Save
7. Click Finish to
8. you see that LB VIP as activated shows and to
9. Repeat steps for other VIPs LB
10. you should all LBs in uP and status Enabled
to 2.6 see. point AG VIP LB VIP
After LB VIP Configure AG LB VIP point. You can do this by using the following steps below:
1. Open the AG VIP configuration page (NS Configuration -> XenMobile)
2. Click Edit
3. Click 4. Edit next XenMobile settings
Add the App controller FQDN (XMS FQDN) with : 8443
5. After appending, you would see the port as under
. 6 Click Done
2.7. point XMS host MAM LB VIP
You have changes in NS directions make all the traffic from AG to MAM LB VIP. To achieve this, we need a DNS entry in NS add as 1 under
Navigate to NetScaler> Traffic Management> DNS> Records> Address Records
2. Add click
3. Enter the host name and AG VIP IP address and click the plus sign the IP
4 add. 5. Click on Create
They are the DNS entry in the list
IMPORTANT: .. The MAM LB VIP FQDN, MDM LB VIP FQDN and the XMS FQDN should be equal to
This includes the blog.
0 Komentar