-
Migrate on-premises NetScaler ADM to Citrix Cloud
-
FAQs
-
-
-
-
View recommendations and manage your ADCs and applications efficiently
-
-
Use ADM log messages for managing and monitoring your infrastructure
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!
FAQs
ADM service
Is ADM service agent optional similar to on-premises NetScaler agent?
No. ADM service agent is mandatory for ADM service and all communications between instances and ADM service happen through the ADM service agent. On-premises ADM agent is optional; however, you can configure the on-premises agent only for saving bandwidth consumption.
Why ADM service?
ADM service through Citrix Cloud provides the following benefits, without the need for new periodic builds:
-
Cloud-based SaaS offering with easier onboarding and lesser cost of ownership than the on-premises NetScaler ADM.
-
Faster releases, approximately every two weeks with latest feature updates.
-
Machine-learning based analytics for application security, performance, and usage.
-
Various other features that are currently supported only in ADM service, such as peak and lean period analytics, machine-learning based application security analytics for WAF and bot, application CPU analytics, and many more.
What happens after migration if on-premises NetScaler ADM is an HA pair?
All configurations are moved to Citrix Cloud. Configuring a disaster recovery node is not required.
What happens if the agent goes down for any reason?
You can expect a potential data loss until the agent is up and running. However, you can also configure ADM agents for multisite deployments to ensure continuity if there is an agent failover. For more information, see Configure ADM agents for multisite deployment.
Is instance backup also migrated?
Backup is not included in migration.
Is historical data also migrated?
Historical data is not migrated. You can export the data from the on-premises ADM.
Are on-premises licenses also migrated?
No. The on-premises license file cannot be used for ADM service. You must obtain licenses for ADM service. For more information, see Licensing. If you are using pooled licenses in on-premises ADM, you must obtain pooled licenses for ADM service and then allocate licenses to instances.
What is not migrated from on-premises NetScaler ADM?
The following features cannot be migrated to ADM service:
-
RBAC – In ADM service, the user access is based on the invite from the administrator. ADM service users must have an account in Citrix Cloud. As a result, the on-premises ADM users are not migrated.
-
Export schedules – Export schedules include details such as drill-down and schedules from various pages. All these detailed export schedules are not migrated.
-
SSL Certificates/Keys/CSRs – ADM service can only display the ADC SSL certificates/Keys/CSRs. As a result, SSL certs/keys uploaded to on-premises NetScaler ADM won’t be migrated to ADM service.
On-premises NetScaler ADM is integrated with Citrix Director. What happens to the integration?
Director integration with ADM is currently supported only in on-premises ADM.
After migration, is it again required to license the instance or to enable analytics?
You must ensure that the licenses in ADM service are more than or equal to the on-premises VIP licenses. If the licenses are already more than the on-premises NetScaler ADM VIP, the virtual servers are automatically licensed. If not, the licenses are assigned randomly.
Migration tool
After running the migration script, error messages are displayed. What can be the issue?
A log file with failure reasons is displayed. You can take appropriate corrective actions and run the migration script again. In general, before you run the migration script, ensure to:
-
Configure the ADM service agent
-
Obtain the ADM service licenses
-
Copy the correct path where you have stored the client and secure CSV file
The ADC instances have lower versions than the mentioned limitation for pooled licensing. What happens if the option ‘Y’ is selected to change the license server?
Change of license server happens only for the supported NetScaler MPX, VPX, and SDX versions.
What happens if the migration script has failed configuration regarding ADC instances?
The ADC instances continue to work on the on-premises ADM setup. You can take necessary action from the suggested failed reason and run the migration script again.
What happens if a few of the ADC instances fail to move to ADM service. Will rerunning the migration script help?
Yes. After you rerun the script, only the failed instances are migrated. Let’s assume that two out of five instances have failed to move. After you have taken corrective actions and rerun the migration script, three instances that were moved successfully earlier show the “Device already exists” message. And the other two instances that failed earlier are migrated successfully.
Is there a log file to check the migration status?
Yes, a log file is generated in the /var/mps/log/ directory. ADM with python3.7 has the log file as servicemigrationtool.py.log and ADM with python 2.7 has the log file as servicemigrationtool_27.py.log.
What happens if the session gets terminated while running the migration script?
You can rerun the migration script. In the new session, the already added instances from the last session display as “Device already exists”, and the migration continues further.
What happens if ADM service has lesser licenses than the on-premises NetScaler ADM and the migration script is initiated?
After the migration script is run, a suggestion appears, mentioning about the licenses are lesser and prompts to continue or stop. If you want to continue with lesser licenses, the virtual servers are licensed randomly from the available licenses.
What happens when on-premises NetScaler ADM is migrated to the ADM service Express Account?
The ADM service Express Account has only two virtual server licenses, two StyleBook configuration packs, and two configuration jobs. If your on-premises ADM has more than these configurations and you initiate the migration with Express Account, the script can migrate only the mentioned configurations applicable for Express Account (two virtual server licenses, two StyleBook configuration packs, and two configuration jobs)
What happens if a Citrix Cloud invited user (other than Admin User who created Citrix Cloud account) tries to migrate on-premises ADM setup?
It is recommended that the administrator to run the migration script. An invited user does not have admin privileges (adminExceptSystem_group). As a result, groups, roles, and policies migration fail and the message “User doesn’t have permission” is displayed.
As a solution, the administrator (who created the Citrix Cloud account) can change the group associated with invited user as “admin_group”.
Rollback script
What happens if rollback script is used in on-premises ADM HA pair?
The on-premises ADM HA pair is restored with all configurations that were available before migration.
What happens to Disaster Recovery node after using the rollback script?
Disaster recovery node is also restored with all configurations before migration.
Share
Share
In this article
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.