Converting Service Profiles from UCSM/Central to Server Profiles in Intersight

Perform the following steps to start with the IMM transition:

1. Click Add IMM Transition.

2. Enter a name for the Transition.

3. Select a Transition Type.

   (a) Select Generate Readiness Report if you only want to view the compatibility/readiness summary of the UCS Manager hardware and configuration or the compatibility of the UCS Central configuration.

   (b) Select Generate Readiness Report + Push Config to Intersight if you want to view the readiness report and push the converted configuration to Intersight.

   (c) Select In-Place UCS Domain Migration if you want to migrate a UCS Manager device from UCSM mode to Intersight Managed mode. For the detailed procedure, see Adding an IMM Transition for an Automated In-Place Migration of UCS Manager Device.

   (c) Select Clone Intersight if you want to migrate from one Intersight account to another by cloning the configurations. For the detailed procedure, see Adding an IMM Transition for Cloning.

   (d) Select Upload Configuration + Push to Intersight if you want to directly upload a JSON configuration file and push it to Intersight. For the detailed procedure, see Adding an IMM Transition to Push the Uploaded Configuration.

   In IMM Transition Tool, Release 5.0.1 and later, a guided tour containing the summary of the selected transition type appears. This helps you to understand all the steps involved in the selected transition. You can check Do not show this page again check box if you don't want to get this information again.

   Currently, this overview summary is available only for the following transitions:

   • Generate Readiness Report

   • Generate Readiness Report + Push Config to Intersight

   • In-Place UCS Domain Migration

4. Click Next.

5. Select the Source UCS Device - UCS Manager or UCS Central.

6. Enter the selected device details.

   (a) Choose the Select Existing UCS Manager/ Select Existing UCS Central option if you want to migrate the configuration of an existing device.

   (b) Choose the Add New UCS Manager/Add New UCS Central option if you want to add a new UCS Manager/UCS Central configuration.

   Enter the Domain IP/FQDN, Username, and Password for the device. If required, enable the proxy for the newly added device by turning on the Use Proxy toggle button. Add proxy settings details in the Proxy Settings interface. To know about the procedure to enable Proxy Settings, see Proxy Settings.

7. Click Refresh to retrieve the latest configuration and inventory details from the UCS Manager/Central device.

   If the selected source device is UCS Central, then you can choose the UCS Central instance from the Choose UCS Central drop-down list.

   You can download the Configuration JSON file and Inventory JSON file for the current device using the Download link.

   Configuration JSON file contains the detailed information of the software configuration present in the existing UCS Manager/UCS Central device.

   Inventory JSON file contains the detailed information of the hardware inventory present in the UCS Manager domain or in all the UCS domains of the UCS Central instance.

   These files can be shared with the technical support team for troubleshooting purpose.

   Note

   While adding a transition, the configuration/inventory fetched from a live device is represented by , and the configuration/inventory fetched from a file (manually uploaded by user) is denoted by on the Select Source UCS/Intersight Device page. For more details, see Uploading Custom Device File. In case an error occurs, you can enable the Force Fetch toggle button to allow the tool to ignore the failed objects and proceed to fetch the configurations of the remaining devices.

8. Click Next.

9. Select the destination Intersight Account.

   (a) Select Choose from existing account option if you want to migrate the configuration to an existing Intersight account. Go to Step 12.

   (b) Select Add new account option if you want to migrate the configuration to a new Intersight SaaS or a new Intersight Appliance VM account. Go to Step 10.

   Note	From release 4.0.1 onwards, If you select Intersight SaaS account, you can also select the region to which the account belongs: US or EU.

   (c) Select Proceed without Intersight device option if you want to generate the conversion readiness report without adding the details of the destination Intersight account. Go to Step 12.

10. Perform the following steps to generate an API Key ID from Intersight.

    1. Log into the Intersight application.

    2. On the top-right corner, click on the Gear icon and select Settings.

    3. Under the API section, click API Keys.

    4. On the top-right of the page, click Generate API Keys.

    5. Enter a name in the Description field and select API Key for OpenAPI Schema Version 2 or Version 3.

       Note	OpenAPI schema version 2 is not supported till IMM Transition Tool, Release 3.0.1. The support for API Keys with V2 and V3 schema is available from IMM Transition Tool, Release 3.0.2 onwards.

    6. Click Generate.

    The API Key ID and Secret Key get generated. Use the Copy to Clipboard blue icon to copy these values to the clipboard. Go back to the IMM Transition Tool application.

11. Complete the following fields:

    • API Key ID: Enter the API Key Id generated in the previous step.

    • Secret Key: Enter the Secret Key generated in the Intersight.

    Also, enter the FQDN if you have selected Intersight Appliance VM.

12. Click Next.

13. Configure the settings that you want for the transition.

    • For details on each of the Transition Settings field, see B.Transition Settings for Conversion in Default Settings.

    • For defining a default set of configurations for every new transition that you create, see A. Default Transition Settings for Conversions in Default Settings.

14. Click Next.

15. Select the Service Profiles/Templates that need to be converted.

    Next to the profile name, profile state, and association details with the physical server can be viewed.

    You can search for a specific service profile/template using the search bar located on the top.

    You can apply a filter to view the All or Templates in the Show drop-down list, located beside the search bar.

    Note	The system displays a warning for profiles in states such as pending reboot, configuration failure, or other invalid conditions, which could lead to a misconfigured setup.

16. Click Next.

17. Configure the mapping of converted objects from UCSM to Intersight from Organization Mapping page. You can choose either Advanced Mapping or Default Mapping.

    The Advanced Mapping option helps in mapping a single UCS organization or multiple UCS organizations to an Intersight organization. Whereas, the Default Mapping option maps each UCS organization to an Intersight organization with the same name in Intersight.

    • Proceed with the below steps, if you select Advanced Mapping:

      1. To add a new Destination Intersight Org, click Add New.

      2. From the list of UCS Orgs, select one or more UCS Orgs and map it to a Destination Org in Intersight.

      3. To configure a Destination Org as a Shared Org, select the Share with Other Organizations checkbox, and then click Share.

         In this case, the UCS Orgs mapped to the Shared Intersight Destination Org will share the same Resources.

         Note	To maintain a similar resource inheritance as in Cisco UCSM/Central, you need to map the Root and Parent Orgs with a Shared Intersight Destination Org, and then map the Sub-orgs to the non shared Intersight Destination Orgs.

         Note

         We can not have the same inheritance as in UCSM/Central because Intersight does not support transitive sharing. Consider the scenario in UCSM with orgs: root, root/Org1, root/Org1/Org2. In UCSM, Org2 can inherit resources from both Org1 and root, while Org1 inherits resources from root. However, replicating the same inheritance structure in Intersight is not feasible due to the absence of transitive sharing. In Intersight, sharing root with Org1 creates a constraint—Org1 cannot be a shared org. This is because, in Intersight, a sub-org (an Org to which a parent org is shared) cannot itself be a shared org. This distinction necessitates a thoughtful approach when translating UCSM inheritance structures to Intersight.

    • Proceed with the below steps, if you select Default Mapping:

      1. To manually enter the name of the Destination Intersight Org, enter a Root Org name.

         Note

         When using the default mapping, ensure that the Root Org name on this page and the Target Org Name for Fabric Policies on the Transition Settings page are different. If these values are the same, a Mapping Confirmation dialog box will appear. Click Cancel and modify the Root Org name. When the selected Target Org Name for Fabric Policies on the Transition Settings page exists and is shared in the destination Intersight account, a Mapping Confirmation dialog box will appear on the Organization Mapping page. To avoid conflicts during the transition, click Cancel and enter a different Target Org Name for Fabric Policies.

         Unlike the same name mapping behavior, customized mapping avoids creating multiple Intersight Orgs for an account.

      2. To retain the Source UCS Org name in the Destination Intersight Org, turn on Keep source Org path in Intersight Org name.

         Note	If Keep source Org path in Intersight Org name is disabled, "root/PROD/WINDOWS" and "root/NONPROD/WINDOWS" would get converted to the same "WINDOWS" organization in Intersight. This could cause conflicts if policies/pools/profiles/templates objects are named the same in both source UCS orgs.

      3. To configure all Sub-orgs to share resources with the Root Org, turn on the Share Root with Sub-orgs option.

         If this option is disabled, the resources present in the Root Org that are used by profiles or templates in sub-orgs will be cloned to each corresponding converted Org.

      4. Go to step 19.

18. Click Map Now.

    When the Source Org and Destination Org mapping is complete, a Mapped tag is displayed next to the Destination Intersight Org. You can also review the mapped Source Orgs in the Mapping section present at the bottom of the Organization Mapping page.

    You can use the Un-Map All option to unmap the existing Source Org to Destination Org mapping within a selected Intersight account. Also, you can unmap a single mapped entity by going to the mapping section, selecting the mapped entity, clicking the three-dot menu against it, and selecting the unmap option.

19. Click Next.

    If Advanced Mapping is selected, the Next button will appear enabled only when the all the source UCS orgs have been selected and mapped to the respective destination Intersight org.

    A readiness report gets generated. This process may take several minutes as the selected config attributes are fetched from UCS Manager/UCS Central, converted to IMM, and the resultant report is generated.

    Note	Depending on the size of UCS Manager/Central Configurations and number of servers connected, some operations may take a significant amount of time to complete (more than an hour).

20. Click View Report to view the report or download the report in PDF format using the Download option.

    For details on interpreting the report, see Interpreting Transition Readiness Report.

    Report generation for any selected config is a one-time activity and cannot be regenerated. This ensures that the history of transitions is maintained and can be referred anytime. If you want to edit the config and generate the report, you can clone the transition. For more details, see Transition Management.

21. Click Next.

    Push converted configuration to Intersight page appears.

    Note	In case an error occurs, you can enable the Force Push toggle button to allow the tool to ignore the failed objects and proceed to push the configurations to Intersight.

    In IMM Transition Tool, Release 1.0.2 and above, you can download the available configuration file, manually edit it, and then upload the same using Advanced Options.

22. Click Advanced Options, browse to the edited file, and click Upload.

    The uploaded file is used for pushing the configuration to Intersight.

23. Click Next.

    A connection with Intersight is established, the converted config attributes get pushed to Intersight.

    Note

    When a transition is being pushed to Intersight using an Intersight device or is fetching a config/inventory from a UCS Manager/UCS Central device, then the same device cannot be used by other transitions until the previous task on the device completes. Reset the default password for the converted polices if those have been pushed to Intersight.

24. Click View Push Summary to view the push status of each of the converted object.

    This summary lets you know the push status for each of the object. Clicking the three-dot menu (...) next to each object status displays the detailed commits performed by the IMM Transition Tool in order to push the object to Intersight. The status can be any one of the following:

    • Success - The converted object has been pushed successfully to Intersight.

    • Skipped - The converted object already exists in the destination Intersight account and has been skipped in the push operation.

    • Failed - The converted object could not be pushed to Intersight.

      Click the three-dot menu present next to the object status to know the reason for push failure.

25. Click Next to proceed to the Push Equipment Configuration (Optional) page.

26. [Optional] On the Push Equipment Configuration (Optional) page, choose one of the following actions:

    • To push the equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions) to your destination Intersight account, click Next.

    • To skip this step if this configuration is not required, click Skip.

    • To download the equipment configuration, click Download.

      Note

      The IMM Transition Tool, Release 5.1.3 and later, supports this optional step. Ensure equipment is properly claimed and discovered in your destination Intersight account before pushing equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions). You can skip this step if the configuration is not required. This step will be automatically skipped if there are no equipment-specific configurations to push.

27. Click View Equipment Push Summary to view the push status of each equipment configuration (if applicable).

IMM Transition Tool, release 5.0.1 allows you to migrate a UCS Manager device from UCSM mode to Intersight Managed mode. Perform the following steps to add a transition for an automated in-place migration of a UCS Manager device:

1. Click Add IMM Transition.

2. Enter a name for the Transition.

3. Select In-Place UCS Domain Migration and click Next.

   A guided tour containing the Summary of In-Place UCS Domain Migration appears. This helps you to understand all the steps involved in this transition. You can check Do not show this page again check box if you don't want to get this information again.

4. Click Start.

5. On the Select Source UCS device page, select the source UCS Manager device.

   Note	If the UCS Manager device is managed by UCS Central, UCS Central must be converted separately.

6. Enter the selected device details.

   (a). Choose the Select Existing UCS Manager option, if you want to migrate the configuration of an existing device.

   (b). Choose the Add New UCS Manager option, if you want to add a new UCS Manager configuration.

7. Enter the Domain IP/FQDN, Username, Password, and User Label for the device, in case you are adding a new UCS Manager device.

   Note

   While adding a transition, the configuration/inventory fetched from a live device is represented by , and the configuration/inventory fetched from a file (manually uploaded by user) is denoted by on the Select Source UCS/Intersight Device page. For more details, see Uploading Custom Device File. In case an error occurs, you can enable the Force Fetch toggle button to allow the tool to ignore the failed objects and proceed to fetch the configurations of the remaining devices.

8. Click Next.

9. Select the destination Intersight Account.

   (a). Select Choose from existing account option, in case you want to deploy the configuration to an existing Intersight account and then go to step 12.

   (b). Select Add new account option, in case you want to deploy the configuration to a new Intersight SaaS or a new Intersight Appliance VM account.

10. Perform the following steps to generate an API Key ID from Intersight.

    1. Log into the Intersight application.

    2. On the top-right corner, click on the Gear icon and select Settings.

    3. Under the API section, click API Keys.

    4. On the top-right of the page, click Generate API Keys.

    5. Enter a name in the Description field and select API Key for OpenAPI Schema Version 2 or Version 3.

       Note	OpenAPI schema version 2 is not supported till IMM Transition Tool, Release 3.0.1. The support for API Keys with V2 and V3 schema is available from IMM Transition Tool, Release 3.0.2 onwards.

    6. Click Generate.

    The API Key ID and Secret Key get generated. Use the Copy to Clipboard blue icon to copy these values to the clipboard. Go back to the IMM Transition Tool application.

11. Complete the following fields:

    • API Key ID: Enter the API Key Id generated in the previous step.

    • Secret Key: Enter the Secret Key generated in the Intersight.

    • User Label: Enter the User Label for the device for easy identification.

    • Intersight Appliance VM FQDN: Enter the FQDN if you have selected Intersight Appliance VM.

    If required, enable the proxy for the newly added device by turning on the Use Proxy toggle button. Add proxy settings details in the Proxy Settings interface. To know about the procedure to enable Proxy Settings, see Proxy Settings.

12. Click Next.

13. On the Transition Settings page, configure the settings that you want for the transition. For more information, see Default Settings.

14. Click Next.

15. On the Select Service Profiles/Templates page, select the profiles or templates that need to be converted. By default, all profiles on this page are selected.

    Next to the profile name, profile state, and association details with the physical server can be viewed.

    You can apply a filter to view the All or Templates in the Show drop-down list, located beside the search bar.

    Note	The system displays a warning for profiles in states such as pending reboot, configuration failure, or other invalid conditions, which could lead to a misconfigured setup. The system displays a warning when you attempt to push more than 100 service profiles.

16. Click Next.

17. On Organization Mapping page, configure the mapping of converted objects from UCSM to Intersight. You can choose either Advanced Mapping or Default Mapping.

    The Advanced Mapping option helps in mapping a single UCS organization or multiple UCS organizations to an Intersight organization. Whereas, the Default Mapping option maps each UCS organization to an Intersight organization with the same name in Intersight.

    • Proceed with the below steps, if you select Advanced Mapping:

      1. To add a new Destination Intersight Org, click Add New.

      2. From the list of UCS Orgs, select one or more UCS Orgs and map it to a Destination Org in Intersight.

      3. To configure a Destination Org as a Shared Org, select the Share with Other Organizations checkbox, and then click Share.

         In this case, the UCS Orgs mapped to the Shared Intersight Destination Org will share the same Resources.

         Note	To maintain a similar resource inheritance as in Cisco UCSM/Central, you need to map the Root and Parent Orgs with a Shared Intersight Destination Org, and then map the Sub-orgs to the non shared Intersight Destination Orgs.

         Note

         We can not have the same inheritance as in UCSM/Central because Intersight does not support transitive sharing. Consider the scenario in UCSM with orgs: root, root/Org1, root/Org1/Org2. In UCSM, Org2 can inherit resources from both Org1 and root, while Org1 inherits resources from root. However, replicating the same inheritance structure in Intersight is not feasible due to the absence of transitive sharing. In Intersight, sharing root with Org1 creates a constraint—Org1 cannot be a shared org. This is because, in Intersight, a sub-org (an Org to which a parent org is shared) cannot itself be a shared org. This distinction necessitates a thoughtful approach when translating UCSM inheritance structures to Intersight.

    • Proceed with the below steps, if you select Default Mapping:

      1. To manually enter the name of the Destination Intersight Org, enter a Root Org name.

         Note

         When using the default mapping, ensure that the Root Org name on this page and the Target Org Name for Fabric Policies on the Transition Settings page are different. If these values are the same, a Mapping Confirmation dialog box will appear. Click Cancel and modify the Root Org name. When the selected Target Org Name for Fabric Policies on the Transition Settings page exists and is shared in the destination Intersight account, a Mapping Confirmation dialog box will appear on the Organization Mapping page. To avoid conflicts during the transition, click Cancel and enter a different Target Org Name for Fabric Policies.

         Unlike the same name mapping behavior, customized mapping avoids creating multiple Intersight Orgs for an account.

      2. To retain the Source UCS Org name in the Destination Intersight Org, turn on Keep source Org path in Intersight Org name.

         Note	If Keep source Org path in Intersight Org name is disabled, "root/PROD/WINDOWS" and "root/NONPROD/WINDOWS" would get converted to the same "WINDOWS" organization in Intersight. This could cause conflicts if policies/pools/profiles/templates objects are named the same in both source UCS orgs.

      3. To configure all Sub-orgs to share resources with the Root Org, turn on the Share Root with Sub-orgs option.

         If this option is disabled, the resources present in the Root Org that are used by profiles or templates in sub-orgs will be cloned to each corresponding converted Org.

      4. Go to step 19.

18. Click Map Now.

    When the Source Org and Destination Org mapping is complete, a Mapped tag is displayed next to the Destination Intersight Org. You can also review the mapped Source Orgs in the Mapping section present at the bottom of the Organization Mapping page.

    You can use the Un-Map All option to unmap the existing Source Org to Destination Org mapping within a selected Intersight account. Also, you can unmap a single mapped entity by going to the mapping section, selecting the mapped entity, clicking the three-dot menu against it, and selecting the unmap option.

19. Click Next.

    If Advanced Mapping is selected, the Next button will appear enabled only when the all the source UCS orgs have been selected and mapped to the respective destination Intersight org.

    A readiness report gets generated. This process may take several minutes as the selected config attributes are fetched from UCS Manager, converted to IMM, and the resultant report is generated.

    Note	Depending on the size of UCS Manager Configurations and number of servers connected, some operations may take a significant amount of time to complete (more than an hour).

20. Click View Report to view the report or download the report in PDF format using the Download option.

    Note	The Errors and Warnings Overview section displays issues related to the transition process. You cannot proceed if there are errors in this section. Resolve the errors manually, then attempt the transition again.

    For details on interpreting the report, see Interpreting Transition Readiness Report.

    Report generation for any selected config is a one-time activity and cannot be regenerated. This ensures that the history of transitions is maintained and can be referred anytime. If you want to edit the config and generate the report, you can clone the transition. For more details, see Transition Management.

21. Click Next.

    If you are proceeding with warnings on the readiness report, a Readiness Report Confirmation dialog box appears.

22. Check I Acknowledge check box and click OK.

    Push converted configuration to Intersight page appears.

    Note	In case an error occurs, you can enable the Force Push toggle button to allow the tool to ignore the failed objects and proceed to push the configurations to Intersight.

    In IMM Transition Tool, Release 1.0.2 and above, you can download the available configuration file, manually edit it, and then upload the same using Advanced Options.

23. Click Advanced Options, browse to the edited file, and click Upload.

    The uploaded file is used for pushing the configuration to Intersight.

24. Click Next.

    A connection with Intersight is established, the converted config attributes get pushed to Intersight.

    Note

    When a transition is being pushed to Intersight using an Intersight device or is fetching a config/inventory from a UCS Manager device, then the same device cannot be used by other transitions until the previous task on the device completes. Reset the default password for the converted polices if those have been pushed to Intersight.

25. Click View Push Summary to view the push status of each of the converted object.

    This summary lets you know the push status for each of the object. Clicking the three-dot menu (...) next to each object status displays the detailed commits performed by the IMM Transition Tool in order to push the object to Intersight. The status can be any one of the following:

    • Success - The converted object has been pushed successfully to Intersight.

    • Skipped - The converted object already exists in the destination Intersight account and has been skipped in the push operation.

    • Failed - The converted object could not be pushed to Intersight.

      Click the three-dot menu present next to the object status to know the reason for push failure.

26. Click Next. If any errors occur in the push summary, the system will display a Push Summary Confirmation pop-up window. Click OK to proceed.

27. The Backup page appears.

    A full-state backup of the UCSM setup will be taken before proceeding to ensure that a rollback is possible if needed. For more information on how to perform a rollback, see Cisco UCS Manager Administration Management Guide 4.3 - Backup and Restore [Cisco UCS Manager] - Cisco.

    Note	Cisco UCS Manager release 4.2(3d) and later do not allow you to create backup configuration files or import backup configuration files without setting the Password Encryption Key. For more information, see Cisco UCS Manager Administration Management Guide, 4.3.

28. Click Download if you wish to download the backup configuration file or click Next.

29. On the Erase Configuration page, select one of the following options:

    • Erase Configuration - Fabric Interconnects are reset to factory defaults and then reconfigured in Intersight mode. Initial Setup can be performed automatically via DHCP or manually using the Console ports on the devices.

    • Change Mode - Fabric Interconnects are automatically switched to Intersight Managed mode without requiring an Initial Setup. This option removes the requirement for a DHCP server, or for performing any manual operation.

    Note	To use the Change Mode option, the devices running in UCSM mode must have firmware version 4.3(5c) or later in the Fabric Interconnects. Change Mode is only available starting with IMM Transition Tool 5.0.3.

    On the Erase Configuration page, mandatory validation will be performed before erasing the existing configuration or change mode operation. After validation is complete and no errors are found, the Erase Configuration or Change Mode button, depending on your selection, will be enabled. If there are errors, you can retry the validation check by clicking Retry button.

    Note

    The following checks are performed on your existing UCS environment: Ensure all servers are in a Powered off state before continuing with the migration. This ensures they are in a clean state before reconfiguring the domain in IMM. If any server is not powered off, shut it down cleanly and retry the validations. The existing UCS Manager domain should not be claimed by the destination Intersight account, as this prevents the pre-assignment of Server Profiles to the server serial numbers from working properly. To proceed, unclaim your UCS Manager domain from Intersight first. Both HTTPS and SSH access must be open between the IMM Transition Tool and the IPs of both Fabric Interconnects in your UCS domain. These protocols are necessary for performing the erase, setup, and claim steps.

30. Click Erase Configurationor Change Mode.

    • If you choose the Erase Configuration, enter the device password in the Erase Confirmation dialog box to confirm the erasure of all configurations, then click Continue. This action will delete all configurations and domain information from your device.

      Alternatively, click Skip to manually erase the configuration if the automated operation fails.

      Note	If you click Skip to manually erase the configuration, you cannot make any changes to the erase configuration step. To proceed, you must manually erase the configurations.

    • If you choose the Change Mode, both Fabric Interconnects (FIs) will automatically switch to Intersight Managed Mode on reboot. This operation can take up to 30 minutes. The Next button will be enabled once change mode operation is complete. Click Next and proceed to step 34 for further instructions.

      Note	Selecting Skip for the Change Mode option bypasses the initial setup, requiring you to manually complete the change-mode operation.

31. Click Next. The Initial Setup page appears.

32. Choose one of the following options:

    • If you have DHCP servers, click Yes and enter the IP details for both Fabric Interconnect A and Fabric Interconnect B. The Transition Tool will then automatically complete the initial setup.

    • If you do not have a DHCP server, click No. The Transition Tool will display all necessary values on your screen. Connect a console cable to each of your Fabric Interconnects and complete the initial setup manually. For more information, see Setting Up Fabric Interconnects.

    Note	Make sure to enter the UCSM Device's admin password in the required field. A DHCP server is the server on the network to which your Fabric Interconnects' management interfaces are connected.

33. Click Next.

    Note	If a DHCP server was not available in the previous step, the Manual Initial Setup in IMM Mode Confirmation dialog box will appear. After completing the manual initial setup, click OK.

    The Claim To Intersight page appears.

34. Turn on the Configure Proxy toggle button to configure the Fabric Interconnects Device Connector to use a proxy to connect to Intersight.

    1. Enter the Proxy Hostname or IP.

    2. Enter the Proxy Port number.

    3. If your proxy settings require authentication, toggle Authentication to turn it on, else go to step e.

    4. Enter the Username and the Password.

    5. Click Save.

    Alternatively, click Skip to proceed and manually perform the claim operation if the automated process fails.

35. Click Next.

36. Verify the details on the Assign and Deploy - Domain Profile page, then click Next to start assigning and deploying the domain profile to the Fabric Interconnects. Once the deployment is complete, click OK.

    Note

    IMM Transition Tool, Release 5.0.1, does not support cloning of In-place domain migration transition. From Release 5.0.3 onward, the IMM Transition Tool allows for the cloning of in-place domain migration transitions. This operation is only possible if the transition is not complete, and the Erase Configuration operation has not yet been performed.

37. Click Next to proceed to the Push Equipment Configuration (Optional) page.

38. [Optional] On the Push Equipment Configuration (Optional) page, choose one of the following actions:

    • To push the equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions) to your destination Intersight account, click Next.

    • To skip this step if this configuration is not required, click Skip.

    • To download the equipment configuration, click Download.

      Note

      The IMM Transition Tool, Release 5.1.3 and later, supports this optional step. Ensure equipment is properly claimed and discovered in your destination Intersight account before pushing equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions). You can skip this step if the configuration is not required. This step will be automatically skipped if there are no equipment-specific configurations to push.

39. Click View Equipment Push Summary to view the push status of each equipment configuration (if applicable).

Perform the following steps to start with the cloning of an Intersight account:

1. Click Add IMM Transition.

2. Enter a name for the Transition.

3. Select a Transition Type.

   Select Clone Intersight if you want to migrate from one Intersight account to other by cloning the configurations. This option can be used for migrating the configuration policies between two SaaS Intersight accounts, two Virtual Appliance accounts, from a Virtual Appliance Intersight account to a cloud Intersight account and vice-versa. For details on the supported features for cloning, refer Supported Features for Cloning.

4. Click Next.

5. Select the source Intersight account.

   (a) Select Choose from existing account option, in case you want to migrate the configuration of an existing Intersight account.

   (b) Select Add new account option, in case you want to migrate the configuration of a new Intersight SaaS or a new Intersight Appliance VM account. Refer step 9 and 10 for API Key ID and Secret key details and then go to step 7. Enable Proxy Settings, if required. To know about the procedure to enable Proxy Settings, refer Proxy Settings.

   Note

   While adding a transition, the configuration/inventory fetched from a live device is represented by , and the configuration/inventory fetched from a file (manually uploaded by user) is denoted by on the Select Source UCS/Intersight Device page. For more details, see Uploading Custom Device File. In case an error occurs, you can enable the Force Fetch toggle button to allow the tool to ignore the failed objects and proceed to fetch the configurations of the remaining devices.

6. Click Refresh to retrieve the latest configuration from the existing Intersight account and then go to step 11.

   You can download the Configuration JSON file using the Download link.

   Configuration JSON file contains the detailed information of the software configuration present in the existing Intersight account.

   This file can be shared with the technical support team for troubleshooting purpose.

7. Click Next.

8. Select the destination Intersight Account.

   (a) Select Choose from existing account option, in case you want to migrate the configuration to an existing Intersight account and then go to step 11.

   (b) Select Add new account option, in case you want to migrate the configuration to a new Intersight SaaS or a new Intersight Appliance VM account. Enable Proxy Settings, if required. To know about the procedure to enable Proxy Settings, refer Proxy Settings.

   Note	From release 4.0.1 onwards, If you select Intersight SaaS account, you can also select the region to which the account belongs: US or EU.

9. Perform the following steps to generate an API Key ID from Intersight.

   1. Log into the Intersight application.

   2. On the top-right corner, click on the Gear icon and select Settings.

   3. Under the API section, click API Keys.

   4. On the top-right of the page, click Generate API Keys.

   5. Enter a name in the Description field and select API Key for OpenAPI Schema Version 2 or Version 3.

   6. Click Generate.

   The API Key ID and Secret Key get generated. Use the Copy to Clipboard blue icon to copy these values to the clipboard. Go back to the IMM Transition Tool application.

10. Complete the following fields:

    • API Key ID: Enter the API Key Id generated in the previous step.

    • Secret Key: Enter the Secret Key generated in the Intersight.

    Also, enter the FQDN if you have selected Intersight Appliance VM.

11. Click Next.

12. Configure the settings that you want for the transition.

    • From IMM Transition Tool, 3.1.1 onwards, you can preserve the assigned IDs on all the UCS server profiles while cloning an account. For more details, refer the C. Transition Settings for Cloning section in Default Settings.

13. Click Next.

14. You can choose either Selective Cloning or Full Cloning from this page.

    • Select Selective Cloning to choose the Organizations, Server Profiles/Templates, Chassis Profiles/Templates, or Domain Profiles/Templates that need to be cloned.

      - Next to the profile name, profile state, and association details with the physical server can be viewed.

      - You can search for a specific Profile/Template using the search bar located on the top.

      - You can apply a filter to only view the Templates, or Org, Profile, and Template in the Show drop-down list, located beside the search bar.

    • Select Full Cloning to clone all Organizations, Server Profiles/Templates, Chassis Profiles/Templates, or Domain Profiles/Templates and their associated policies.

    Note

    With IMM Transition Tool, Release 4.0.1 you can select the specific Server Profiles that need to be cloned. With IMM Transition Tool, Release 4.1.1, you can select the specific Server, Chassis, and Domain Profiles that need to be cloned. The associated policies and templates will also get cloned automatically. The system displays a warning for profiles in states such as pending reboot, configuration failure, or other invalid conditions, which could lead to a misconfigured setup.

15. Click Next.

16. Configure the mapping of cloned organization from source Intersight account to destination Intersight account from Organization Mapping page. You can choose either Advanced Mapping or Default Mapping.

    The Advanced Mapping option helps in mapping a single source Intersight organization or multiple source Intersight organizations to a destination Intersight organization.

    1. Proceed with the below steps, if you select Advanced Mapping:

       1. To add a new Destination Intersight Org, click Add New.

       2. From the list of source Intersight Orgs, select one or more source Intersight Orgs and map it to a Destination Org in Intersight and click Map Now. Repeat this step until all the mapping is complete.

       3. To configure a Destination Org as a Shared Org, click on ellipse (…) next to the Destination Org name and select the Share with other orgs option.

          In this case, the source Intersight Orgs mapped to the Shared Intersight Destination Org will share the same Resources.

       Note

       For Advanced Mapping: The Next button becomes active only after you select and map all source Intersight organizations to their respective destination Intersight organizations. In IMM Transition Tool, Release 5.1.3 and later, if multiple policies from different source organizations have the same name and mapped to a single destination organization, a pop-up message appears once you proceed to the next step. This message provides an option to enable the Rename Policies toggle button. Enable Rename Policies: If you enable this toggle, the tool automatically renames all conflicting policies by appending the source organization name to their original name. Do Not Enable Rename Policies: If you do not enable the toggle, the tool converts only the first policy encountered with a conflicting name and skips all other policies with that same name during the cloning configuration. The IMM Transition Tool, Release 5.1.1 and later, supports Organization Mapping for Clone Intersight transition. If the selected source Intersight organization does not comply with the organization sharing rules, the tool will blur or disable access to that organization to prevent the mapping. Organization Sharing Rules A shared org cannot be mapped concurrently with orgs that contain profiles. A shared source org cannot be mapped to a destination org that is already a recipient of another shared org, and vice versa — An Intersight org that is already a recipient of a shared destination org cannot be mapped with a shared source org. If the total resource groups from all mapped source organizations exceed the limit of 10 per organization, the mapping operation fails with an error message. A shared organization cannot be mapped to a destination organization that already contains associated resource groups. To allow this, enable the delete_existing_resource_group_memberships_for_intersight_shared_orgs setting. A source organization that has resource groups cannot be mapped to a shared destination organization — resource groups are not supported in shared organizations.

       When the Source Org and Destination Org mapping is complete, a Mapped tag is displayed next to the Destination Intersight Org. You can also review the mapped Source Orgs in the Mapping section present at the bottom of the Organization Mapping page, by choosing Destination Intersight Organization Name.

       You can use the Un-Map All option to unmap the existing Source Org to Destination Org mapping within a selected Intersight account. Alternatively, to unmap a single entity, navigate to the mapping section, select the specific mapped entity, click the three-dot menu next to it, and choose the Un-map option.

    2. Select Default Mapping option to map each source Intersight organization to a destination Intersight organization with the same name in Intersight.

17. Click Next.

    If Advanced Mapping is selected in the previous step, the Next button will be enabled only when the all the source Intersight orgs have been selected and mapped to the respective destination Intersight org.

18. Click Next.

    Push cloned configuration to Intersight page appears.

    Note

    With IMM Transition Tool, Release 5.0.1, you can push the converted SPAN configurations by enabling the Push Equipment toggle button.However, it requires all the inventory to be fully discovered and all profiles to be assigned and deployed. With IMM Transition Tool Release 5.0.3, you can enable the Push Equipment Configuration toggle to choose between two options: Push Config + Equipment: Push configuration along with the equipment-related configuration elements such as User Labels, Tags and SPAN sessions. Push Equipment Only: Push only the equipment-related configuration elements (SPAN sessions, User Labels & Tags assigned to hardware). However, it requires all the inventory to be fully discovered and all profiles to be assigned and deployed. With IMM Transition Tool Release 5.1.3, you can push equipment-specific configuration items to Intersight as an optional step after you claim and discover devices in the destination Intersight account. For more information, go to step 23. In case an error occurs, you can enable the Force Push toggle button to allow the tool to ignore the failed objects and proceed to push the configurations to Intersight. In IMM Transition Tool, Release 1.0.2 and above, you can download the available configuration file, manually edit it, and then upload the same using Advanced Options.

19. Click Advanced Options, browse to the edited file, and click Upload.

    The uploaded file is used for pushing the configuration to Intersight.

20. Click Next.

    A connection with Intersight is established, the converted config attributes get pushed to Intersight.

21. Click View Push Summary to view the push status of each of the converted object.

    This summary lets you know the push status for each of the object. Clicking on the three dots (...) next to each object status displays the detailed commits performed by the IMM Transition Tool in order to push the object to Intersight. The status can be any one of the following:

    • Success - The converted object has been pushed successfully to Intersight.

    • Skipped - The converted object already exists in the destination Intersight account and has been skipped in the push operation.

    • Failed - The converted object could not be pushed to Intersight.

      Click the three-dot menu present next to the object status to know the reason for push failure.

22. Click Next to proceed to the Push Equipment Configuration (Optional) page.

23. [Optional] On the Push Equipment Configuration (Optional) page, choose one of the following actions:

    • To push the equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions) to your destination Intersight account, click Next.

    • To skip this step if this configuration is not required, click Skip.

    • To download the equipment configuration, click Download.

      Note

      The IMM Transition Tool, Release 5.1.3 and later, supports this optional step. Ensure equipment is properly claimed and discovered in your destination Intersight account before pushing equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions). You can skip this step if the configuration is not required. This step will be automatically skipped if there are no equipment-specific configurations to push.

24. Click View Equipment Push Summary to view the push status of each equipment configuration (if applicable).

Perform the following steps to directly upload the JSON configuration file and push it to Intersight account:

1. Click Add IMM Transition.

2. Enter a name for the Transition.

3. Select Upload Configuration + Push to Intersight to upload a JSON configuration file and push it to Intersight.

4. Click Next.

5. Select the destination Intersight Account.

   (a) Select Choose from existing account option, in case you want to upload the configuration to an existing Intersight account and then go to step 8.

   (b) Select Add new account option, in case you want to upload the configuration to a new Intersight SaaS or a new Intersight Appliance VM account.

6. Perform the following steps to generate an API Key ID from Intersight.

   1. Log into the Intersight application.

   2. On the top-right corner, click on the Gear icon and select Settings.

   3. Under the API section, click API Keys.

   4. On the top-right of the page, click Generate API Keys.

   5. Enter a name in the Description field and select API Key for OpenAPI Schema Version 2 or Version 3.

   6. Click Generate.

   The API Key ID and Secret Key get generated. Use the Copy to Clipboard blue icon to copy these values to the clipboard. Go back to the IMM Transition Tool application.

7. Complete the following fields:

   • API Key ID: Enter the API Key Id generated in the previous step.

   • Secret Key: Enter the Secret Key generated in the Intersight.

   Also, enter the FQDN if you have selected Intersight Appliance VM.

8. Click Next.

   Push configuration to Intersight page appears.

   Note

   With IMM Transition Tool, Release 5.0.1, you can push the converted SPAN configurations by enabling the Push Equipment toggle button.However, it requires all the inventory to be fully discovered and all profiles to be assigned and deployed. With IMM Transition Tool Release 5.0.3, you can enable the Push Equipment Configuration toggle to choose between two options: Push Config + Equipment: Push configuration along with the equipment-related configuration elements such as User Labels, Tags and SPAN sessions. Push Equipment Only: Push only the equipment-related configuration elements (SPAN sessions, User Labels & Tags assigned to hardware). However, it requires all the inventory to be fully discovered and all profiles to be assigned and deployed. With IMM Transition Tool Release 5.1.3, you can push equipment-specific configuration items to Intersight as an optional step after you claim and discover devices in the destination Intersight account. For more information, go to step 14. In case an error occurs, you can enable the Force Push toggle button to allow the tool to ignore the failed objects and proceed to push the configurations to Intersight.

9. Click Browse to select the JSON configuration file.

10. Click Upload.

    The uploaded file is used for pushing the configuration to Intersight.

11. Click Next.

    A connection with Intersight is established, the uploaded config attributes get pushed to Intersight.

12. Click View Push Summary to view the push status of each of the converted object.

    This summary lets you know the push status for each of the object. Clicking on the three-dot menu (...) next to each object status displays the detailed commits performed by the IMM Transition Tool in order to push the object to Intersight. The status can be any one of the following:

    • Success - The converted object has been pushed successfully to Intersight.

    • Skipped - The converted object already exists in the destination Intersight account and has been skipped in the push operation.

    • Failed - The converted object could not be pushed to Intersight.

      Click on the three dots present next to the object status to know the reason for push failure.

13. Click Next to proceed to the Push Equipment Configuration (Optional) page.

14. [Optional] On the Push Equipment Configuration (Optional) page, choose one of the following actions:

    • To push the equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions) to your destination Intersight account, click Next.

    • To skip this step if this configuration is not required, click Skip.

    • To download the equipment configuration, click Download.

      Note

      The IMM Transition Tool, Release 5.1.3 and later, supports this optional step. Ensure equipment is properly claimed and discovered in your destination Intersight account before pushing equipment configuration (User Labels & Tags for chassis/servers, SPAN sessions). You can skip this step if the configuration is not required. This step will be automatically skipped if there are no equipment-specific configurations to push.

15. Click View Equipment Push Summary to view the push status of each equipment configuration (if applicable).

Click ... located against each transition record to perform the required action.

• Click Report to view the readiness report for the transition.

  This option is not available for cancelled and failed transitions.

• Click Edit to change the transition name.

• Click Delete to delete the transition.

  You can select multiple transitions and click the trash button located on upper-left of the list view to delete the selected transitions in bulk.

• Click Clone to copy the existing transition config.

  (a) Provide a name for the transition. It appears in the listing page with status as Incomplete.

  (b) Click Transition name to edit the config, generate the readiness report, and push the modified config to Intersight.

  Note	Clone option is not available for transitions with type as Clone Intersight.

• Click Download Logs to download the conversion logs to a file.