-
-
Migrate Citrix ADM single-server deployment to a high availability deployment
-
Migrate Command Center configurations to Citrix ADM
-
Integrate Citrix ADM with Citrix Citrix Virtual Desktop Director
-
-
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 Command Center configurations to Citrix ADM
You can now migrate your Command Center configurations to the Citrix Application Delivery Management (ADM) without losing the existing configuration, settings, or data of your Command Center deployment and Citrix ADM deployment. You can view the migrated Command Center configurations in Citrix ADM after the migration process is completed.
Points to note
-
Migrating Command Center configurations to Citrix ADM is supported on the following deployments:
-
Command Center standalone to Citrix ADM standalone deployment or Citrix ADM high availability deployment.
-
Command Center high availability to Citrix ADM standalone deployment or Citrix ADM high availability deployment.
Note
You must use only the primary node IP address of Command Center and Citrix ADM high availability deployment while migrating the Command Center standalone or high availability deployment to Citrix ADM standalone or high availability deployment.
-
-
You can run the Command Center tool multiple times on same or different Citrix ADM deployments:
-
Whenever you run the Command Center tool beyond the first time for the same Citrix ADM, the logs will be shown as failed for the configurations that have already been migrated and exist in Citrix ADM.
-
If any new configuration has been added in Command Center from the time the tool was run earlier to now for the same Citrix ADM, all such configuration except the new Custom tasks will be migrated to Citrix ADM.
-
-
Migrating Command Center configurations to Citrix ADM is supported for Citrix ADC, Citrix ADC SDX, and Citrix SD-WAN WO devices.
-
All communication between Command Center and Citrix ADM is on an HTTPS connection.
-
Backing up of existing data of Citrix ADM before migrating the Command Center configurations is highly recommended.
-
After the Command Center migration is completed, the Admin Partitions of Citrix ADC are auto-discovered in the Citrix ADM.
Limitations
The following Command Center configurations are not migrated from the Command Center appliance to the Citrix ADM:
-
Device backup configuration files
-
Timeout details in SD-WAN WO device profiles
-
The following details under event and alarm triggers are not migrated:
-
Abort details for run command action
-
Run task details
-
Triggers with all empty parameters (severity/category/instances/failure objects) are not migrated
-
Triggers having instances with the state as HA cluster, primary, and secondary are not migrated if all the three states of the instances are selected
-
-
Custom tasks without description are not migrated
-
Event severities settings
-
Event rule schedule details
-
Syslog suppress filters
-
Configuration task details
-
Audit templates
-
Audit policies without devices
-
Audit policy schedule details
-
Groups RBAC authorized scope settings
-
Database monitor and management settings
-
Performance custom reports
-
Performance thresholds
-
Custom views of fault/syslog/reports/Entity Monitoring
-
AppFirewall and NS gateway reports and its schedule details
-
SD-WAN WO auto configuration details
-
High Availability settings
-
Scheduled system backup settings
-
Database retry settings
-
Syslog purge schedule time
-
All statistic data like syslog, events, and audit logs of all modules.
Prerequisites
Before migrating the Command Center configurations to Citrix ADM, ensure that the following prerequisites are met:
-
You are running Command Center version 5.2 build 48.2 or later.
-
You have installed and configured Citrix ADM version 12.0 build 51.24 or later.
-
Only the Admin user will run the Command Center configuration migration.
-
For successful migration of custom tasks, the description field is mandatory in Command Center.
-
Communication between the Command Center and Citrix ADM is NITRO based. You must configure and open the necessary SSL (Secure Socket Layer) and TLS (Transport Layer Security) protocol settings on Command Center and Citrix ADM for NITRO communication.
Note
If you are using a Command Center version earlier than 5.2 build 48.2, you must upgrade the Command Center version to 5.2 build 48.2 and then migrate the Command Center configurations to Citrix ADM. For detailed information about upgrading the Command Center appliance, see Upgrading Command Center.
Migrate the configurations
To migrate a Command Center configuration to Citrix ADM, you need the Command Center appliance IP address and administrator credentials.
To migrate Command Center Configurations to Citrix ADM:
-
In a web browser, type the IP address of the Command Center appliance.
-
In the User Name and Password fields, type the administrator credentials and log in.
-
After successful login, on the screen that appears, select the Administration tab and do one of the following:
-
In the right pane, under Citrix ADM Migration, select Migrate Configuration, as shown in the following figure.
-
In the left pane, select Citrix ADM Migration, and then click Migrate Configuration, as shown in the following figure.
-
-
In the Command Center to MAS Migration dialog box, enter the IP address of the Citrix ADM server, and the administrator credentials, and then click OK.
Note
In case of Citrix ADM high availability deployment, enter the primary node IP address.
-
At the confirmation prompt, click Yes.
The screen reports the progress of the migration tasks.
The Migrate Configuration operation takes the details of the Citrix ADM deployment and its admin credentials as input. The Migrate Configuration operation then migrates the configuration of Command Center deployment to Citrix ADM deployment.
When the tasks are completed, you can verify the migrated Command Center configuration from Command Center migration logs and Citrix ADM data.
To use the Command Center migration logs to verify the migration
-
In the Command Center GUI, on the Administration tab, do one of the following:
-
In the right pane, under Citrix ADM Migration, click Migration Log.
-
In the left pane, select Citrix ADM Migration, and then click Migration Log.
-
-
Review the list of migration logs.
-
To display more detail, select Module Name, or to display details for a particular module, select that module, and then click Details.
-
The following example shows the log details for a selected module.
To use the Citrix ADM to verify the migration
During the migration process, the Command Center configurations are migrated to Citrix ADM and are shown as Citrix ADM configurations in the Citrix ADM GUI.
After the migration process is completed, the Citrix ADM server reboots and there might be a momentary downtime. When the Citrix ADM server is up and running, access the Citrix ADM GUI by typing the IP address of the Citrix ADM server in the address bar of your browser.
The following table shows how the Citrix ADM terminology for the migrated configurations corresponds to the terminology used in Command Center.
Command Center Terminology | Citrix ADM Terminology |
---|---|
Device profiles | Instance profiles |
Devices and its state (like managed/unmanaged) | Instances and its state (like managed/unmanaged) |
Device annotations | Instance annotations |
Device groups | Instance groups |
Maps | Instance groups |
Event and alarm triggers | Event rules |
Built-In and custom task commands | Configuration templates under create Job editor |
Scheduled audit policies | Audit templates |
Password policy | Password policy |
Users (local users only) | System users |
Groups* | System groups |
Authentication profiles and authentication settings | Authentication profiles and authentication configuration |
Email settings | Email server/Email distribution list |
Syslog server | Syslog server |
SSL settings | SSL settings |
SNMP agent configuration | SNMP manager |
Trap forward settings | Trap settings |
Event purge settings | Events prune settings |
Inventory settings | Instance backup settings |
Syslog purge settings | Syslog prune settings |
Appliance network settings like DNS, NTP, and time zone | Citrix ADM network settings like DNS, NTP, and time zone |
*Groups with all permissions in Command Center are migrated as groups with an “admin” role in Citrix ADM. All other Command Center groups are migrated as groups with a “read-only” role in Citrix ADM.
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.