-
-
Migrate Citrix ADM single-server deployment to a high availability deployment
-
-
-
-
Importing and synchronizing StyleBooks from GitHub repository
-
Simplified migration of Citrix ADC application configuration using StyleBooks
-
-
Use ADM log messages for managing and monitoring your infrastructure
-
-
Citrix ADC automation using Citrix ADM in Cisco ACI hybrid mode
-
Citrix ADC device package in Cisco ACI's cloud orchestrator mode
-
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Migrate Citrix ADM single-server deployment to a high availability deployment
You can upgrade your Citrix ADM single server to a high availability deployment of two Citrix ADM servers. A high availability pair of Citrix ADM servers is in active-passive mode, and both the servers have the same configuration. In this type of active-passive deployment, one Citrix ADM server is configured as the primary node and the other as the secondary node. If for any reason, the primary node goes down, the secondary node takes over.
To migrate a Citrix ADM single server to a high availability pair, you need to provision a new Citrix ADM server node, configure it as the second Citrix ADM single server, and deploy both the Citrix ADM servers as a high availability pair.
Migrating a Citrix ADM single server to a high availability mode involves the following steps:
-
Modifying the existing server node
-
Provisioning the second server node
-
Deploying the two nodes in HA mode
-
Configuring the high availability pair
Modify the existing Citrix ADM server node
To migrate the Citrix ADM from single server to high availability mode, you have to change the initial deployment type of the server node to high availability mode.
-
On a workstation or laptop, open the console of the existing Citrix ADM server node. For example, consider that you have deployed a Citrix ADM with IP address as 10.106.171.17 as a standalone server.
-
Log on to Citrix ADM. The default credentials are
nsroot
andnsroot
. -
In the shell prompt, type
/mps/deployment_type.py
, and press Enter. -
Select the deployment type as Citrix ADM server. If you do not select any option, by default, it is deployed as a server.
-
The deployment console prompts you to select the server deployment (as standalone). Type No to confirm the deployment as high availability pair.
-
The console prompts you to select the (first server node). Enter Yes to confirm the node as the first server node.
-
The console prompts you to restart the server.
-
Type Yes to restart.
Provision the second server node
You have to provision the second server on your hypervisor. Use the same image file that you used to install the first server, or obtain an image file of the same version from the Citrix download site.
-
Import the image file to your hypervisor, and then from the Console tab configure the initial network configuration options as explained on the following screen:
-
After specifying the required IP addresses, in the shell prompt, type /mps/deployment_type.py, and press enter.
-
Select the deployment type as Citrix ADM server.
-
The deployment console prompts you to select the server deployment (as standalone). Type No to confirm the deployment as high availability pair.
-
The console then prompts you to select the (first server node). Type No to confirm the node as the second server node.
-
Enter the first server’s IP address and password.
-
Enter the floating IP address of the first node.
-
The console prompts you to restart the system. Enter Yes to restart.
Deploy the two servers in a high availability mode
To complete the installation process of the two server nodes as a high availability pair, you have to deploy these nodes from the GUI of the previously existing Citrix ADM server node. Internal communication between the two servers starts when you deploy the two server nodes.
Important
Before deploying high-availability nodes, ensure to change the default password.
-
In a web browser, type the IP address of the previously existing Citrix ADM server node.
-
In the User Name and Password fields, enter the administrator credentials.
-
On the System tab, navigate to Deployment and click Deploy.
-
A confirmation message appears. Click Yes.
Note
After you deploy Citrix ADM in high availability, you can either access the primary node or the floating IP address. You cannot access the secondary node from 12.1 release onwards.
-
Though you have entered the floating IP while configuring the second server node, you have an option to update the FIP on the Systems page. Click HA Settings > Configure Floating IP Address for High Availability Mode. You can view the floating IP address you configured earlier. You can enter a new IP address and click OK.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.