09-21-2023 01:28 AM
the manual is great for new clients/accounts - but I don't find any information how to handle existing accounts, especially how to move from US to EMEA.
I'll assume, "almost any" account by european clients will be transferred sooner or later.
Question:
Solved! Go to Solution.
10-27-2023 03:13 AM
Hello,
First of all, I would like to thank you for bringing up this question. The migration process for Intersight from US to EU is rather simple. But before that it will be better if we investigate the impact of each type of migration:
1. IMM - Intersight Managed Mode
• Fully Disruptive - Requires UCS Domain downtime
• Data (configuration) needs to be cloned or recreated
• Loss of power statistics
2. UMM – UCS Manager Mode
• No disruption
• No data loss
3. Standalone C-series
• No disruption – but a reboot might be required
• No data loss
4. Hyperflex
• No disruption
• Statistics loss (affects Capacity Planning)
• Functionalities are limited to Imported Cluster
5. Connected Appliance
• No disruption
• No data loss
Note: For Hyperflex, “Functionalities are limited to Imported Cluster” means the feature of “Redeploy Node” will not be available after the migration.
After estimating the impact, we would need to ensure appropriate connectivity. Intersight Regions and endpoints are mentioned as follows:
To claim a target, access to the North American (us-east-1) endpoints is required.
If the target is claimed by an EU account, access to the EU (eu-central–1) URLs is also required.
The migration is disruptive for IMM as all the management is done from Intersight itself. The migration process for IMM is as follows:
Note: Cloning of Account configuration can be done by the IMM transition tool.
We need to choose the option of “Clone Intersight”
Then we would need to follow through the steps:
Note: If you get an error, try redoing the process
Next, you would need to unclaim the IMM domain from the old account and claim it in the new account. This process could take some time to complete.
After that, you would need to assign the appropriate profiles to the devices. (Domain profiles to Fis and server profiles to servers and so on)
The migration process for other types of deployment is as follows:
5. Unclaim the deployment from the US account and claim it to the EU Account.
That would be an overview of the migration of existing customers from Intersight US to EU. If you have any further questions or queries, do reach out to us.
If you find my reply solved your question or issue, kindly click the 'Accept as Solution' button and vote it as helpful.
You can also learn more about Intersight through our live Ask the Experts (ATXs) session. Check out the ATXs Resources [https://community.cisco.com/t5/data-center-and-cloud-knowledge/cisco-aci-ask-the-experts-resources/ta-p/4394491] to view the latest schedule for upcoming sessions, as well as the useful references, e.g. online guides, FAQs.
10-27-2023 03:13 AM
Hello,
First of all, I would like to thank you for bringing up this question. The migration process for Intersight from US to EU is rather simple. But before that it will be better if we investigate the impact of each type of migration:
1. IMM - Intersight Managed Mode
• Fully Disruptive - Requires UCS Domain downtime
• Data (configuration) needs to be cloned or recreated
• Loss of power statistics
2. UMM – UCS Manager Mode
• No disruption
• No data loss
3. Standalone C-series
• No disruption – but a reboot might be required
• No data loss
4. Hyperflex
• No disruption
• Statistics loss (affects Capacity Planning)
• Functionalities are limited to Imported Cluster
5. Connected Appliance
• No disruption
• No data loss
Note: For Hyperflex, “Functionalities are limited to Imported Cluster” means the feature of “Redeploy Node” will not be available after the migration.
After estimating the impact, we would need to ensure appropriate connectivity. Intersight Regions and endpoints are mentioned as follows:
To claim a target, access to the North American (us-east-1) endpoints is required.
If the target is claimed by an EU account, access to the EU (eu-central–1) URLs is also required.
The migration is disruptive for IMM as all the management is done from Intersight itself. The migration process for IMM is as follows:
Note: Cloning of Account configuration can be done by the IMM transition tool.
We need to choose the option of “Clone Intersight”
Then we would need to follow through the steps:
Note: If you get an error, try redoing the process
Next, you would need to unclaim the IMM domain from the old account and claim it in the new account. This process could take some time to complete.
After that, you would need to assign the appropriate profiles to the devices. (Domain profiles to Fis and server profiles to servers and so on)
The migration process for other types of deployment is as follows:
5. Unclaim the deployment from the US account and claim it to the EU Account.
That would be an overview of the migration of existing customers from Intersight US to EU. If you have any further questions or queries, do reach out to us.
If you find my reply solved your question or issue, kindly click the 'Accept as Solution' button and vote it as helpful.
You can also learn more about Intersight through our live Ask the Experts (ATXs) session. Check out the ATXs Resources [https://community.cisco.com/t5/data-center-and-cloud-knowledge/cisco-aci-ask-the-experts-resources/ta-p/4394491] to view the latest schedule for upcoming sessions, as well as the useful references, e.g. online guides, FAQs.
10-27-2023 03:17 AM - edited 10-27-2023 03:46 AM
_
06-05-2024 03:41 AM
Hi
Interesting thread. Appreciate if you could clarify the below.
- What is the process to migrating an existing Intersight (SaaS) to > Intersight Private Virtual Appliances
- What do you mean by 'Fully Disruptive' what is the exact impact?
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide