-
Migrate NetScaler Console on-prem to Citrix Cloud
-
Troubleshooting
-
-
-
Minimum and maximum capacity for Flexed and Pooled licensing
-
Scenarios for Flexed or Pooled license expiry and connectivity issues behavior
-
Configure NetScaler Console on-prem as the Flexed or Pooled license server
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!
Troubleshooting
When you run the migration script for the first time, it checks for the prerequisites and proceeds with the migration. If all prerequisites are met, the migration completes without any errors. If any prerequisite fails, the script displays error messages with reasons. After fixing the errors, you must rerun the script again.
Note
If you see an error message that displays “already exists”, it means that:
You might have run the migration script for more than one time and some configurations are already migrated to NetScaler Console service.
You might have manually created the same configuration in NetScaler Console service, before running the migration script.
Refer to some of the following error messages:
Manual profile added to NetScaler Console service
Workaround: If you have created admin profiles in NetScaler Console service before running the migration script, ensure to delete those profiles and rerun the migration script.
NetScaler device added to NetScaler Console service
Workaround: In NetScaler Console, ensure the instance status and see if you can access the instance without any issues. If any issue persists, fix the issue, and rerun the migration script.
StyleBook custom templates import to NetScaler Console service
Workaround: This error message is an example for the already migrated StyleBook. You can also see this error if you have manually created a StyleBook with the same name, version, and namespace, in NetScaler Console service before running the migration script.
Configuration Jobs added to NetScaler Console service
Workaround: This error occurs if you have subscribed to Express Account and have more than two configuration jobs. You must obtain a valid subscription to have all your configuration jobs to be migrated.
IP blocks added to NetScaler Console service
Workaround: Delete the IP block that is manually created in NetScaler Console service and rerun the migration script.
Network dashboard report addition status
Workaround: Delete the dashboard that is manually created in NetScaler Console service and rerun the migration script.
Share
Share
In this article
- Manual profile added to NetScaler Console service
- NetScaler device added to NetScaler Console service
- StyleBook custom templates import to NetScaler Console service
- Configuration Jobs added to NetScaler Console service
- IP blocks added to NetScaler Console service
- Network dashboard report addition status
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.