Hello, everyone. Today we will explore the transition from the traditional UCS managed mode to Intersight managed mode abbreviated as IMM. By the end of this session, you will have a clear understanding of IMM.00:05How it differs from what you are used to, and most importantly, how you can transition smoothly and confidently to Intersight managed mode using a practical guided path. So we're gonna dive right in and start by explaining what inter site managed mode actually is for clarity.00:19At its core, it represents a completely new and purpose built software stack that is designed specifically for Fabric Interconnect devices. Think of it as a modern alternative to UCS Manager and to UCS managed mode. For many years now, a lot of us have relied on UCS managed mode.00:36So this mode lets you configure and manage your entire UCS infrastructure and you do it through the inter site platform. What is really nice is that it is built on the standards based on the foundation using the redfish model. So it is designed to be more open and truly future friendly.00:54Also, it provides you with a single highly centralized place to manage your standalone servers and your fabric interconnect attached systems in the single pane of glass. Now let's really take a careful look and compare the two sides, one to the other. If you have previously.01:13You worked with or UCS management mode, you already know the basic building blocks, the guiding policies, the various profiles, and the templates that encode the setups. The good news is that IMM also uses exactly the same concepts, so your existing knowledge carries over to IMM as well.01:33The difference here lies in how they're organized. IMM takes those familiar pieces and arranges them in a more modular, flexible way that is centrally managed in the cloud or it could also be in your environment if using an appliance. So you're not learning everything from scratch. You are merely applying what you already know in a more scalable.01:51Robust and flexible structure for everyday use. Now let's move on to see how this important transition will happen. So the transition occurs via the IMM transition tool. This is where things become truly practical.02:11Moving from one mode to another might sound like a lot of manual work, but this very tool is designed to solve that issue. It automates the migration for you right away. For each server, you can see the examples in this diagram here as well.02:30The server name, the identities, information like the UUID, Mac, WWN, the boot configuration, the LAN and sand settings, even the firmware details, all of it gets carried over to Intersight. It also takes your existing identity pools and maps them to new ID.02:46Identity pools in IMM and it converts your service profile templates into server profile templates on Intersight. Bottom line, this tool saves you a lot of time and drastically reduces the chances of human error during the migration process.03:06Alright, that's enough talk now. Let me show you exactly how this works in practice today. I'm going to walk you through the IMM transition tool right now. We will begin by connecting our source UCS domain.03:27Then select the profiles, templates, and we will bring them over to Intersight. And before we commit anything, the tool also gives you a chance to review what is going to be migrated so that there are NO surprises. Now we will see how we can migrate from a UCS manager managed environment to an Intersight managed environment.03:38So the tool that will help us to do that will be IMM transition tool. How do you get that?03:58Is to go to UCS tools.cloudapps.cisco.com. Under that you will get to see the IMM transition tool and you can download it for a new installation or you can also download the up up upgrade package. So once you download and deploy this tool, it will look something like this here.04:04This is how the transitions will look like. You have device management where you can claim the targets from where you want to transition and the target to which you want to transition. So the user's manager and the inter site. Likewise, you may use a software repository. You can keep your OS files here and also move them to Intersight if it's needed.04:23This is the UCS environment we'll use for the plan transition. It has four UCSCC servers.04:43And this is the inner site account we'll move it to. Currently, the fis are claimed on Intersight, including this particular inter site account, so therefore our immediate 1st step is to remove that claim. If it is claimed on any inter site account, we must unclaim it there.04:50That is what we are doing now. After that, we can go to UCS manager and verify in device center that it is unclaimed and then we'll be good to go. Here is one more important detail we should verify. If we want our passwords to stay intact when they are added to the policy settings in intersight, we must ensure that the password encryption key is con.05:08Figured and ready for use. To set up the password encryption key, you will need to provide the key here. You simply have to remember this key because it will be used to securely and easily retrieve the passwords whenever you access intersight.05:28Let's proceed with the transition. We will use the in place UCS domain migration. This new feature supports substantial automation for the transition itself. The initial step is to add the user's manager. If already added, refresh the configuration in inventory once so the latest data is available to the tool.05:45A couple minutes the video is sped up.06:06You can observe the progress on the right hand side of your screen as the information retrieval process continues to advance. When it finishes completely, you can close it and then add your inter site account. We have already done this before. This is the place where you select the exact transition settings. If you need to modify any tags or options, you may.06:13Edit them here now.06:33You need to change the profiles and the fabric policies. Everything is possible here on this tab. Then you select which profiles and templates you want to migrate. Here we have four service profiles, so that is what we will migrate. Then we also need to map the organization of UCS Manager to the organization of Intersight.06:35We map the UCS manager route to the default inter site account. Then it will generate a readiness report that details what the transition would look like if we proceed with it. If there are warnings or errors here, please review them closely.06:55And address them before we proceed with the transition. In our lab environment, we will ignore the warnings, but we should explicitly acknowledge that we are ignoring them for the record. When you have completed that, we can continue to the next step. This is where you push the configurations from your UCS manager to intersight.07:13Now this may take a few more minutes. You can monitor the progress on the right side of your screen. The duration depends on the size of your transition. After the configuration push is complete, you can close this window and proceed to the next section, which will be backing up your UCS manager. Before we go ahead and erase the config.07:33Configuration from your fis of the UCS manager settings, it is always recommended to take a backup. So this is also integrated within the tool itself.07:53You can take a backup using the tool. So once again, this will take a couple of minutes of the time depending on how big the backup is. Once the backup has finished, you may also download it from the download button that you can clearly see here.08:02Alright, the backup is now finished. We can close this and download the backup so that you have it readily available right away in case something goes wrong during the transition. After the download completes, we now proceed to the erase configuration step.08:19Before configuring ADS, it will verify that the servers are powered on, registered in Intersight, and that reachability is working well. So in our case, the servers are still on, so we'll shut them off fast.08:36It will guarantee that all of them are turned off.08:56Then we return to the tool and retry now. Then all checks pass, then we erase the configuration. It will quickly erase the fis configuration and leave it ready for intersite managed operation.09:05Now set up inter site managed mode on fis. Please ensure console access to fis. Here you can see the console access to the fis and the fis are rebooting. After they reboot, we will.09:21Proceed with configuring them.09:37So this tool will provide the configurations you need. If you have a DHCP server, you can do it automatically there.09:52If not, you can do it manually here, which we will do right here. We display all inputs that are visible on the screen.09:59The password is something you must provide yourself. We carefully determine which fabric interconnected is. We provide and set up the management IP address, the subnet, the gateway, and the DNS IP address. These are the configurations we have completed.10:05We want to ensure that everything looks good, and then we apply it to be sure So this will take just a couple minutes to finish. Then on the next FI, once we select the con.10:23It will fetch the configuration from the FI if you just enter the password.10:44Now you can see all the configurations that have been fetched. You just need its management IP address. After you do that, apply config. It will again start applying the config it got from the other FI.10:48The configurations are about to be completed soon. This will again record.11:15By a couple of minutes. We go back to tool. Once the configuration is done and both the fis are set, we go ahead with claiming it to inter site.11:25Once we claim it, the system will immediately begin generating the domain profile and then proceed to deploy it as well.11:51So now at the moment it's deploying the domain profile to the fis with all the configurations. On intersight, you can also observe that the domain profiles are being deployed on their fis.12:02You can see that their fis have already been claimed on intersight, and the servers are likewise present and appear once the domain profile is deployed. It will perform the discovery of the servers, and afterwards you can also see the servers. Now the servers are beginning to populate as you can clearly verify.12:20As the discovery has started. Now that the discovery is complete, the IM transition tool will stop there now. If you wish to proceed forward, you will need to perform the next step manually. Specifically, you must assign the server profiles to the servers that are currently on inter site. That is something you will have to.12:38Performed manually.12:58So the discovery is continuing now at this moment Okay, so the discovery is now complete. Now you simply deploy the server profiles on the servers, and then the servers will now be ready.13:00Can fully transition from your UCS manager mode to the inside managed mode.13:20So this is what the entire demonstration of the time and transition tool entails. I hope you found it quite useful indeed.13:34
