Collaboration Applications in Business Edition 6K/7K server with NFVIS hypervisor

Good morning, good afternoon, and good evening to everybody. Thank you so much for joining us today for this community live session. We are excited to have you as part of.00:11Of our team for a little bit here and today our session is CUCM cluster migration to business edition 6K7K server with NFVIS for UC hypervisor. My name is Brooke Hammer. I'm the English community manager for community.cisco.com and will be your host for today.00:20We also have two amazing speakers, Mario and Jorge, and they are from the collaboration tech team, and i'll tell you a little bit more about them.00:40Mario is a tech engineer for the Cisco unified Communications manager team, joined TAC in 2019 as part of the unified communications applications team. He's experienced in CUCM and IM and presence deployments, upgrades and migrations and he specialized in Webex app integrations and single sign on solutions.00:50Hey Marcus is also a tech engineer for the same team. He joined Cisco tech in 2023 as part of the CUCM support team. He's experienced with Cisco business edition platforms, BE six K and Be seven K and specializes in troubleshooting CUCM database and platform related issues.01:10Today we will be having a few poll questions pretty earlier on in our presentation, so you can go ahead and join here. I will also push them live throughout so you will see a poll going up on the side of your screen. So if you don't wanna join from another device, I will be putting them in. Your participation is voluntary, but we love.01:32Up to have some interaction between all of our distinguished guests today. And with that, I'm going to pass it over. If you do have any questions actually, please do put them in the Q and A panel. We do have question managers here to answer anything that you have or you can wait till the end during our Q and A session.01:52Towards the end of our presentation. Now with that, I'm gonna hand it over and thank you so much for being here.02:13Thank you very much Brooke and welcome everyone. So, well, there's something I want to talk about about NFVIS. So let's review the agenda before entering into the material. 1st we will introduce NFVIS for UC and explain when to use it.02:21Next we will install NFVIS on B6K and B7K platforms and then we will review the basic configuration needed to prepare the environment. Finally, we are going to explain how to install and migrate CUCM to NFVIS, so let's get started.02:40Well, I like to start by getting into the basics about NFVIS for UC. This software is the Cisco's answer to the need for a simplified virtualization infrastructure. We're not talking about a generic hypervisor that requires additional layers of management, but a platform designed specifically.02:59For the Cisco collaboration ecosystem on B6K and B7K hardware.03:18So let's start by defining what is a hypervisor and explain where it fits. So a hypervisor allows one physical server to run several virtual machines or Vmiss as we're going to call them, and it shows resources like CPU, memory, and storage. So each virtual machine.03:24Can run independently. The hypervisor connects the physical server with the virtual machines. In simple terms NFVIS works just like VMware ESXi does. It hosts hosts them and manages the Vmiss on the server.03:43So, let's define what is NFVIS for unified Communications. NFVIS stands for Network Function Virtualization Infrastructure software. Think of it as a Cisco Designed hypervisor. It is designed for Cisco collaboration applications specifically such as call manager, IM presence, unity connection, Cisco.03:58As a responder and expressway, all the applications from the UC street that you usually use. These applications runs run as virtual network functions or bnfs on B6K and B7K servers. And if the ES manages the CPU and the memory efficiently. This helps the voice and video applications to run with low latency. It supports the.04:18Deployments from 200 to 5000 users.04:38Now, let's see where NFVIS fits into the Cisco unified communications architecture. NFVIS sits between the business edition six K and seven K server and the Cisco collaboration applications are the ones that I have mentioned. Call manager, I am in presence uni, emergency responder, expressway, and contact center. Its job is mainly to provide the virtualization layer.04:44That allows these applications to run efficiently on the hardware. It is also important to know that starting with the version of call manager 15 SU four business edition six K and seven K servers will support only NFVIS. Okay, that's important. Esxi and Itanics will NO longer be supported on these business edition platforms.05:04Is with the software version.05:24Now, let's compare NFVIS with other hypervisors. So let's start with the 1st point. The 1st one is going to be the network optimization. NFVIS is built with technologies like SRIOV and DPDK, which improve the network performance. But why is this important? Invoicing video applications such as.05:28Call manager and expressway. The low latency is critical. On ESXi or Nutanix you usually need extra configuration to achieve the best performance. So with NFVIS, these optimizations are built in.05:47So they are native, allowing the networking traffic to reach the virtual machines faster with lower latency and less jitter. 2nd one is the licensing cost. So NFAS is planned to be a lower cost option for business edition servers. The number three is integration with the Cisco solutions. NFAS is designed to work seamlessly with the Cisco ecosystem.05:59During Cisco SD one, e.g., Cisco DNA center. So that makes the deployment much easier. With other hypervisors hypervisors, you may need additional software or manual configuration. The number four is the lower resource overhead.06:19So every hypervisor uses some CPU and memory just to run itself. So this is what we call the overhead. Because NFVIS is based on a lightweight Linux KBM platform, it uses fewer system resources. So, it means that it's going to run smoothly.06:34And better. The number five is the automation and the APIs. So NFVIS supports standard APIs, including netconf. This allows the administrators to automate deployments and manage multiple servers using the scripts, making operations faster and easier. Since it uses open standards, it also integrates well with.06:50With the net dev OPs tools and workflows. And then number six is going to be the unified unified technical support. With NFAIS, Cisco tech provides the support for both the collaboration applications and the virtualization platform. If you use a 3rd party hypervisor troubleshooting may involve working with multiple vendors at the same time. With NFVIS, you have a single point of con.07:10That which is stacked and that simplifies and speed up the problem resolution.07:30So Brooke, is going to help us with the 1st question. Perfect yes, so let's take it back. What does NMVIS stand for? A network framework which virtualized infrastructure service B, network function virtualization infrastructure software or suit C.07:37Get new feature virtualization integration system and that poll should be up on your side and we can see what's happening.07:57Okay, I've got, oh, we're between A and B right now. Nobody's falling for C Okay we'll give it another minute. Let's get your votes in there. Okay, ok, we've got about 40 % for A and about 58 % for B oh, 67 % for B.08:06And I think it's time, one more vote. Okay, and the correct answer is B, network function Virtualization Infrastructure software. Okay, thank you very much, Brick.08:26So, well, let's continue and let's let's discuss about why should I choose NFAS. 1st, because that is easier to manage. Since the hardware, the hypervisor and Cisco collaboration applications are designed to work together, the deployment and management are easier reducing the change of configuration errors. 2nd.08:44It's very important as well because it helps to control the budget. NFVAS is planned to be included with Cisco Business edition servers, so you don't need to purchase separate 3rd party hypervisor licenses. You keep your solutions on premises. Finally, in simplified support because the hardware, the hypervisor and the application all come from Cisco.09:04Cisco Cisco tech.09:24So we cisco tech, have, we have the end to end visibility of the entire solution from the firmware to the application. This means that you have a single point of contact avoiding the need to coordinate the troubleshooting with multiple vendors at the same time. A common question is whether different hypervisors can be mixed and the answer is absolutely NO.09:27For notes in the same cluster, we cannot do that. All servers in a cluster should use the same application version and the same hypervisor. Let's put an example, call manager cluster. If the publisher is running on NFVIS, then all the subscribers must run on NFVIS two. You should not have publisher on NFVIS, e.g., and the subscribers on ESXi.09:47Because this can cause database replication issues. The main exception is the enhanced obability node ESM in dedicated instance, but that is only an exception. And if you have separate independent clusters such as expressway C and expressway e pair, you have more flexibility in that case because they do not share the same database.10:07The the the thing the thing here is that, any node or any closer cluster that replace rep replicates the data, the database between the publisher and the subscribers, they should always have the same hypervisor and the same version.10:27To use NFVIS, your deployment must be running call manager 15 SU four as I mentioned before or later, ok? 15 SU four from from call manager. Since this is the 1st version that supports NFVIS, you can verify compatibility for each Cisco collaboration application in installation guide under the virtualization requirements section, and you can.10:44Also check the release notes. But the installation guide is usually the quickest and easiest place to confirm which hypervisors are supported. So here is the compatibility section of the virtualization guide, and now my colleague Jorgeo will help us answer a question, which hypervisor should I choose? So please.11:04Ahead. Thank you. Oh, but the 1st time we have the 1st question about what is one of the main advantages of using any presentation, if you can help us Brooke with that question.11:24So our options are A, it allows multiple hypervisor vendors to be used on the same hardware. B, it requires purchasing 3rd party virtualization licenses or C, it provides a single vendor Cisco for the hardware, hypervisor and applications simplifying management.11:40Okay, we have a bunch of votes and everybody seems to be going for option C, but let's give it another minute, get a few more in here. Oh, that just jumped up. Fantastic. Okay, I think everybody knows the answer to this. I don't think you challenged them enough here with this very difficult question because they all got it.11:59Right? It is C It provides a single vendor for the hardware.12:19Hard questions are coming later, NO worries. There you go. We're really gonna test you, take some notes. We got you so yeah we will be answering the question that someone on the chat just pop out. I just read it that cluster size on on this one.12:26Okay, so which hypervisor should you choose? The answer depends on what you want to run on your server. NFVIS for unified communications, was created for customers who only need to run voice applications. Unlike other virtualization platforms, NFVIS is made.12:42Mainly for voice workloads and is optimized for unified communications. One of its biggest benefits is simplicity, and if it's a complete Cisco solution so you don't need to work with other vendors as mentioned this make support and troubleshooting and.13:03Management issue.13:23Also, any of the agency is a good choice for organization with about 200 to 5000 users. It is also a good option for customers who want to keep their voice system separate in a secure and real reliable environment. In short NAP agency is a great choice if you want to virtualize.13:24Voice applications with how the extra cost and complexity of traditional virtualization platforms. On the other hand, and Nutanix are also good option for voice applications. However, they are built for a wider range of users.13:44The best choice depends on your IT strategy and business needs. These platforms work in large data centers where voice applications run together with other business applications. E.g., they can host worklogs on Microsoft Windows server, Ubuntu server, another operator.14:02In systems. Another benefit is hardware flexibility unlike NFBHS, these platforms can run on servers for many different vendors.14:22They also offer advanced features like high available live migration and centralized management because of this they are good fit for large and complex environments to summarize. Choose NVHS if you want a simple and dedicated platform.14:32For applications and we need to choose being or Nutanix if you need to run different types of workloads and wants advanced data center features.14:52So, now that we have reviewed the hypervisor options and where they fit best, we need to compare how they work during the deployment and daily operations. A key, a key point in NFVIS for UC is that it uses the.15:06The same over falls as being world.15:25This is a big advantage for customers moving from because the immigration process is easier and does not require a new deployment method. Nutanix is different. It requires a specific image file for Cisco unified communications applications because of this extra preparation and the.15:28Deployment steps maybe needed. Another important benefit of any just for UC is that the drivers needed for voice applications are already included and supported. So with being where and Nutanix administrators might need to find and install and maintain.15:48In some drivers themselves with specific cases. This can require more time and and effort.16:08And there is also a difference in management tools, being where may require guest agents for some virtual machine management features and for UC and Nutanix do not need extra guest agents. This makes administration simpler and reduces management maintenance.16:15Tasks. Overall NFVHS for UC offers a simple experience for unified communications and worklogs. EDCC deployment built in driver support and lower management effort on making it an a strong choice for organizations that want to do.16:36Complexity while keeping a stable and reliable voice environment.16:56So with that said we have already discussed that why NFBHS for GC was created and when is the best choice to to choose it. And now let's move from theory to practice. In the next sec section, we will go through the installation process for NFHS for GC.17:05On business edition six K and business edition and seven K platforms. Also, we will review the main steps and important points to help make the deployment process smooth and successful. To begin the 1st step is to download the NFBHHS for.17:25You see, ISO image. You can download it from the Cisco software download center at software at.cisco.com.17:45One of the main benefits of NFVHS for UC is that it already includes all the drivers and software software needed for voice applications because everything is included in the ISO image. There is NO need to download or install extra drivers.17:55This makes the installation process easier and faster. After any of these for UC is installed, you can deploy unified communications applications using the same use it in being environments. This is a big advantage for administrators who already work with.18:14Because the process is very similar and easy tooler. Before starting the installation, Cisco recommends reviewing the NFPHS release notes. The release notes provide important information including supported hardware platforms, supported NFPHS versions and required.18:34For CMC versions.18:54Checking these details before, installation helps avoid problems and supports smooth deployment. By completing these preparation steps, you can reduce installation issues and build a solid foundation for your C environment. So let's move to the install.18:58Process on the next slide. So now that we have seen working on load the software, we need to 1st check the prerequisites there.19:17Prerequisites and for you see supported on business edition and six K and business edition and seven K platforms including M5M6 and M seven server models as well as the CEB 1400 B platform. We also need access to.19:29So Cisco integrated management controller or CMC because and we will use it to mount the installation image and control the server put process. Another requirement is the NFBGS for.eighteen.X ISO image. So before starting, make sure there are.19:49You know all virtual drives mounted. This helps avoid issues during the installation.20:09So once everything is ready, we can begin the installation. 1st, we need to mount the nfv's nfvs ISO image through CMC and perform a one reboot of the server during a startup, open the boot menu and select the mounted ISO image as the boot device. After that.20:16At the NFV S installation runs automatically and requires very little user input.20:36When the installation is finished, we move to the initial configuration, we log in using the default administration, the administrator account and the username is admin and the password is admin 123 pound. So for security reasons change.20:43Is the default password immediately. Next, we need to configure the physical network interfaces or your network design, assign them to the LAN or one site as needed and then configure the basic network settings including IP routes, DNS servers. So.21:03At this point, the system is ready for deployment of unified communications applications. So as you can see, the installation and initial setup process is simple and follows an appliance style deployment model with just a few steps and if you just for UC is ready to host your unified communication.21:23Applications applications. Now let's look at the application deployment process.21:431st, the 1st step is we need to open up web browser and enter the service management IP address. We need to log in to the Cisco integrated management controller or CMC using your credentials. After logging in, we need to open the KBM consoles.21:51You can use either the HTML five version or the Java version. I recommend the HTML five console because it is it runs directly in the browser and usually provides a very better experience. In the console, we need to go to virtual media.22:09Enable CDS/and then select the image that you downloaded earlier. Next we need to restart the server using the power cycle option during the startup, we need to press F six to open the the boot menu, then select the mounted ISO.22:28Much as the boot device. In the boot menu, we need to select Cisco NFPHS install. The installation starts automatically and begins installing NFPHS on the server. During the installation, the system asks for confirmation before deleting any existing data and creating a new.22:48Partition. This is a really important steps. So before continue, make sure any required data has been backed up and that the server is ready for a fresh installation. When the installation is complete, we need to access the NFAS console and log in using the default credenti.23:09Said before, username admin password admin 123 pound. So just remember for security reasons change the default password immediately after the 1st login. Once NFS is installed the next step is to complete the initial system configuration and prepare.23:29At the platform.23:48For unified communications applications, with like with that, I would like to hand it over to my colleague Mario, who will show us a quick demonstration of the NFV IS installation process. So Mario over to you. Thank you very much Jorge. So, well, if.23:50You're going to choose to pay attention to an important part is this one, ok? So let's do, let's go with the demo. To begin installation process of Cisco NFVIS, we need to enter to the Cisco integrated management controller or CAMC as mentioned in the slides and move to the storage storage section, ok? In the storage section.24:10Is where the ESXi put is, and let's go to the virtual drive info.24:30And let's locate the virtual drive number zero, ok? This is the one that contains the esxi boot, so now we need to delete this virtual drive. Yeah, it will prompt you to confirm that you'd like to delete the virtual drive number zero, so we click on ok, then it will process the request and we'll delete this one, ok? That's gone.24:34This is a required step because we need to create a new virtual drive boot specifically for NFVIS. Then we go back to the controller info and create a new virtual drive with the physical drives that are now available to install NFVIS. So select the available physical drives, move them to the device group site and give it a.24:54Descriptive name like I don't know NFA is dashboard or something like that, e.g..25:14Further options here will depend on each business edition characteristics. The request will be, will be processed and then we will be able to see the virtual drive info when, once we have created the virtual drive. So that's going to process a request again.25:20And we will be able to see the new virtual drive boot for NFBIS, ok? We can see now that in the screen with optimal status and good health, as you can see there. Okay, we can also visualize that it has a right level of one. Again, that.25:37It's just to due to the business additional characteristics of the lab.25:57The server that we have, using the ok. Through the CMC, we need to go to the virtual KVM as Jorge mentioned in the slides as in the virtual KBM we're going to mount the ISO image to install NFVIS. So we're prompted to confirm the operation, we confirm and then we proceed to reset the system after we have mounted the, the, the.26:01The file. We need to wait a few seconds for it to start so we can enter to the boot menu accessing.26:21With the F six key constantly, but for now we will see several options and and and and they are the images that we have mounted previously, ok? They can be like via CMC or e.g. the one that we need in in this case, that is the one that we have.26:28Map from the virtual KBM, so we choose that one. Okay, so now we are going to enter to the boot menu, pressing the F six key constantly.26:49Now there are all the options that we have for the iso file. We are going to choose the one that we have mounted in the CIMC before, and we choose this one that is the BDBD.27:08Two.zero ok so the installation process is going to begin and then we see some checks in green. This is the way that we know that it's going to stay.27:26So here's something important I want to tell you. This process can take quite some time.27:47Actually, there is NO need to be alarm here because in our case it took more than 1 h, so that is normal for the NFVIS installation. So well for practical purposes here in the webinar, we'll run the clock into the future and get to the point where NFVIS has finished installation. So let's do some magic and there you go. Okay, once NFAS.27:53This has been installed, we entered to the CLI.28:13And we need to enter the default password and user that Jorge mentioned twice before, which are, do you remember? Admin and admin 123 pound. Then we're going to be prompted to do the 1st configuration immediately that is going to change the password as Jorge mentioned. So attack.28:15See here. It is recommended to have a password previously password previously designed and ready once you have started the process to configure it as soon as it starts the NFVIS, because you will be asked to confirm a new password for security reasons, ok? So once that you have created the password, you type it, then you.28:35We're going to be prompted to type it again.28:55And then you have finished your 1st configuration. Now, we are now inside the CLI of the of the new installed NFVIS. So let's let's explore the basic commands, e.g., the show version, show version will show us the NFVIS system version which in this case is for the.28:58At 18.29:18We can have other basic commands like e.g. show platform. This will show all the hardware details, show platform. There you go, you have all the hardware details there. You can see.29:22Another version of this command which is a show platform detail. It is going to provide us with that detailed report of the platform.29:41Yeah. If you want to know, e.g., in which mode this NFVIA is, you can type the command show NFVIA NFV modes.29:49And this will, provide you the information of the mode of NFVIS. E.g., if you want to know, how long it's been up or who, who has been logged in, you can choose.30:04Show system uptime that will show us the time that the system has been up and show system setting brief that will give us a small summary of show system and who has been locked in at the same time. So.30:21Yeah. So here the goal is not to be afraid to use your new friendly or fresh NFVIS. You have to explore the hypervisor you you can enter the basic commands that we're going to share in the next slides that.30:36Let's go to the next slide because there there we have a list of the commands that you can enter for later reference. You will have access to those and the next slide as well has a list of commands for the basic configuration or the health check for NFVIS, ok? So, well hopefully the the.30:57More has been good for you. So let's go with the next question with Brooke.31:17Awesome. What is the minimum C U C M version supported with NFVIS? I'm sorry I realized I didn't make the question available for UC, sorry. There we go. Is it A 14 SU 5B15 SU four or C.31:2515 SU one and the question should be up there so we're just waiting for some votes.31:44There we go, we got some in, ok. We're a little bit between most people are going with the F 15 SU four, but we have a couple strugglers maybe doing that ANC answer. Let's get a couple more votes in here.31:50Okay. All right. Majority is going B 15 SU four, which is the correct answer. So thank you so much for participating. Thank you very much for the question Brooke. So guys before we go in the next slide, let's let's have this piece of data clear. This is.32:0615 SU four because that's the 1st version that's going to support NFVIS and remember what I said before, if we have this version and B6K and B7K, we are only going to support NFVIS, NO Nutanix, NO ESXi, so it is important that you check the requirements in the 15.32:25Okay, that is a good question. So let's move on to the basic NFVIS for UC configuration. Yeah, the slides are going to be available available later. So well I'm going to introduce you to the basic configuration of NFVIS for UC. The configuration starts with the management interface.32:46Which is simple and easy to use. We'll also see the three ways to manage NFVIS, but for now, just remember that this is where you configure the VLANs, the trunks, the network ports, which NFVIS refers to as bridges. Another important setting is the resource reservation, ok? Also called the holdback. Cisco resource.33:05Automatically 122 physical CPU cores and up to 13 gb of RAM for the physic for the hypervisor itself to run, ok? For a storage only hardware right one or write five is supported and the software right is not recommended because it cannot provide this performance required for applications like call manager, which is the important one for us. Finally, the.33:25Should always use the thick provisioning instead of the thin provisioning, ok? With theme provisioning, the storage space is allocated only when it is needed. This can introduce delays while the hypervisor allocates the new disk blocks and reducing the the disk performance. This is something that we don't want to to experience. Since UCM relies strongly on.33:46On the SQL database, these delays can affect services and even cause database replication issues. The thick provisioning that is the one that we are going to use reserves required storage from the beginning, providing more consistent performance and making it the recommended option for NFVIS deployments.34:05Now, it is important to keep your virtual machines backed up once they are installed, so we recommend using using DRS for backups. Other backup methods are not supported or recommended. You should also separate the network traffic using VLANs. Use one VLAN for management and.34:24Another for voice traffic. This helps isolate management traffic from voice traffic, reducing the congestion and protecting the call quality. And finally.34:43But not least, do do not overlook the security. Cisco recommends using tech explores or radius for user authentication and access control. These solutions provide centralized authentication and auditing. If we rely on local accounts, you might lose the ability to centrally track and audit audit administrative access, ok?34:52So well.35:12Once NFVIS is installed and running, the next step is to create the virtual machines, configure the network breaches and manage the hypervisor before installing and or restarting the call manager. As I mentioned before, there are three ways to manage NFVIS. The 1st one is going to be the NFV NFVIS portal, and it's the one that we are seeing there in the screen.35:13The NFAST portal is a web based interface that provides an easy and visual way to manage the platform. When you log in, you'll see an overview of the servers current health, including the system information, a clear system status indicator, resources usage, network interface interface status, deployment details, and system alerts or notifications that we need.35:33To know at the moment that we enter the NFVIS. That's the screen that you are seeing there in the slide. And this makes easy to monitor the server and quickly identify any issue from a single dashboard, ok? So NFVIS portal is the 1st option. 2nd option to manage NFVIS is the NFVIS CLI. That one provides a command line interface.35:53For managing the platform. It offers flexibility through commands as we saw in the in the demo. This is a good choice for administrators who prefer working from from the command line interface or that maybe have experience with Linux environment. The 3rd option is the NFAS API, which allows.36:13Allows you to automate and integrate management task with internal tools and scripts. So with a, with APIs exactly. If you like to learn more about the official API documentation, that is available in the link shown in the, in the screen, ok?36:33Now I'm going to give you a tactive and that's something important. Always use the areas backup only on Cisco collaboration virtual machines. Why? Because some other methods like e.g. snapshots that are not supported, create delta these files and that can reduce the performance over time.36:49Since applications like call manager, unity, IMM presence depends strongly on the database performance. The snapshots can lead to database corruption, replication problems and service issues. We don't want that. Instead, we should always use the Cisco disaster recovery system DRS to back up the collaboration servers.37:08DRS is the only Cisco supported and recommended backup method for CUCM, Unity, IMM presence, and the other collaboration applications. Ensuring reliable backups and safe restores. So now my colleague Jorge is going to help us with the deployment, installation and migration of call manager in NFBIS, and then the.37:28There will be another demo, so go ahead for you.37:48Thank you Mario. So as Mario said with NFES for UC installed and configure, we are ready for the next step deploying call manager. So let's see how the process works. So, let's talk about migrating COCM from being where sxi to NFBS for.37:53The goal is to move an existing COCM deployment from a environment to a new NFHS for UC platform. 1st, it is important to understand that this is not a live migration scenario.38:14Instead, this is a planet migration that follows Cisco best practices to move CUCM from UC. Before starting, we need to create and verify a complete DRS backup. This is the most important requirement because the backup will be used.38:27To restore the COCM configuration and data on the new NFPAS platform without a valid backup, the immigration should not continue. Another important requirement is to schedule a maintenance window because there is NO live migration capability between the COCM virtual machine.38:47Been on sxi must be shut down before the restoration begins on NFVIS. This means there will be some service downtime during the immigration, so proper planning is important.39:07So on now that we have reviewed the immigration requirements, let's look at the main steps for migrating CUCM@twelve.five of layer from being where sxi to see, so let's move on to onto the immigration workflow.39:19On this slide I will explain the main steps for twelve.five or a higher version. 1st we review the network platform and software requirements to make sure the environment is ready. Second, and we perform the data export from the existing system using the command shown on the screen.39:39There, we complete a clean installation on the new platform. This process replaces the existing virtual machines. 4th, we verify the integrity of the exported data. If there is any issue with the base PID, we we need to contact Cisco tech for assistance immediately and we can help you.39:59To change that PID. So 5th, we upload the NFEIS image and the required profile for CUCM 15 SU four. Finally we deploy and create the virtual machine.40:18After these steps are completed, the immigration is ready for validation and testing. So on this slide, the main difference is on step two, as you can see, instead of using a.export, we use a DRS backup. This is the recommended method for customers.40:33It's already running COCM 15 as you four. The backup allows to restore the COCM configuration and that down the new NFVIS for you see platform. Other than that the immigration process is largely the same. In summary, if you're running a COCM 15 as you four, simple.40:53We replace the data explore step with backup and follow the rest of the immigration workflow as, as usual.41:13So, now that we are ready to deploy COCM on NFVIS, at this point we have completed the infrastructure step in and running COCM in the NFAS environment. 1st we need to upload the COCM ISO image and.41:21And then the overf file to the NFVS repository. Next we need to register the image in the NFVS so they are available for deployment.41:41Then we create a virtual machine profile, and this profile defines the resources for the virtual machine such as bcpus, memory and storage on Cisco's recommendations. Once the profile is ready, we deploy the UCM virtual machine using the NPI.41:53Yes portal or the rest API. Next, we need to connect the virtual network interfaces to the correct network cards such as the management LAN and the voice VLAN networks, and this ensures proper connectivity for the application. Finally, we need to.42:12To open the virtual machine console and verify that the operating system and CUCM services start correctly. As you can see, the deployment process is simple and very similar to what many administrators already know from other virtualization platforms with the virtual machine and running and the network comp.42:32Here. COCM is ready for the next stages of setup and operation. So.42:53I will hand it over to one question with Brooke that if you pay attention, you will note it. Okay, apparently this is gonna be the test here, guys. You have to pay attention for this one. So which protocols are used for centralized management through the NFVISEAPI? Is it A S.43:00NMP and SSH, B netconf, with restcom.43:20For C HTTP and FTP. Okay, we've got some people coming in and they are hot on answer B alright we've got to switch over to maybe possibly C let's give another minute to see if anybody else has any.43:25Amazing answers here. I think we're going strong with our answer as B And I think we can not keep them waiting. They did good. They paid attention and correct. You guys got it. Congratulations. We're really proud of you. It was answer B.43:45Thank you brooke. Ok, let's review another another tech tip and this one is about the OVAs and ISO files. We need we need to use always OVAs and ISO files downloaded directly from cisco.com or provided through a Cisco tech case, ok? Files from other sources may contain virus.44:05Or have harmful code and that may also cause installation problems or system failures. So if you contact tech, the 1st thing that we're going to do is to confirm that you're using a file from an official site or provided by us tech, ok? So never never never go to other repositories or those.44:25Storage places where they have images from legacy? No, only Cisco.com files, ok? So, well, let's go to create the virtual machine for a call manager and 15 four again in an FBIS for UC. So we are now in the NFVIS manage.44:45Management portal that you can see here. We start by logging into the NFVIS for UC web portal, and that's the 1st tool for management that I talk about before. This is where we are going to do the whole process of creating and deploying the virtual machines.45:05Once inside, we are going to navigate to the image repository. Now, there in the repository, there is where NFVIS manages all the images that we will later use to deploy the applications.45:22Here we upload the necessary files for CUCM 15 issue four and the bootable ISO ISO file is loaded as an image, ok? The bootable ISO file is loaded as an image while the OVA is converted into a profile, which defines the base configuration of the virtual machine. This is a bit.45:39It's important because it clearly separates the system image from the VM profile.45:59Once we have the image and profile created, we navigate to the configuration and deploy. From here, we can create a virtual virtual machine connected to the corresponding virtual network and assign the image and profile. Finally, we hit the deploy button.46:05To start a virtual machine.46:24Once the virtual machine is booting, we access the console or terminal, and from here we monitor the call manager installation wizard and validate that system starts installing correctly, ok? This is the last checkpoint. So we have done that. Before we continue with the task of installation of call manager.46:27We can continue monitoring it there.46:46So, I'm going to talk about this slide and the next one that is going to show us the complete process of deploying and installing and migrating the call manager of NFVIS ones that we have created the virtual machine, and it has been divided into seven main steps. The 1st ones, the 1st one is to prepare the files. The.46:49Follow the 15 the the call manager 15 SU four ISO and OVA file and decide how many notes and collaboration applications you need. Decide how many notes of call manager, decide if you're going to use call manager with call call manager with unity. There is where you plan everything. Then you are going to.47:09To Define the Vmiss in 2nd step and you're going to assign the CPU, the memory, the disk space and follow the official CUCM guides and OVA requirements to prevent performance problems, ok? This is a very important step. The number three is to.47:29Make the deployment. You need to create a virtual machines as we have seen there in an FBIS, add the ISO files and the OVA files and OVA files and configure the management and voice networks. The number four is to install, start installation wizard, configure the NTP, the DNS, the certificates, the security settings, every.47:43Thing that we need to for this to work. The installation process is similar to the standard standard UCM installation, so there is NO difference. The only difference is that this time is running on an FBIS.48:03The step number five is the integrations. Here we connect call manager with external services that already exist in the environment. E.g., integrations with LDAP, integrations with SSO, SIP trunks, gateways, and in some cases SRST or MGCP configuration, e.g.. The number six and.48:16Very important as well is the high availability. Here we set up the call processing groups at TFTP redundancy and database replication between the nodes.48:36The last one and the number seven is testing. This is I believe the the most important part of the process because we validate the endpoint logging, internal and external calls and testing scenarios such as SRST or failover. This test confirmed that the environment was correctly deployed and functioning as expected.48:45Tested.49:05Now remember, when installing or restoring call manager, there are only two supported migration methods and the 1st one is DRS backup and restore, and 2nd one is fresh installed with data import. It will depend only on the version that you are using. E.g., if you are.49:08In a version of call manager 14. If we're migrating from from call manager 14, we need to use the fresh install with data import. If we are already running call manager 15 SU four, we need to use the DRS backup and restore. Why? Because the version that we are going to use within FBIS is 15 SU four.49:26We cannot do a DRS backup in different versions. So this is why if we are in the version 14 or twelve.five or something like that, we need to go with a fresh install with data import. Only if we are using the same version which is 15 issue four, we can go with the DRS backup. Before starting the migration process, follow the same.49:46Best practices that you would do for any call manager upgrade. Once, one of the most important steps is running the pre upgrade call file, which checks the system for potential issues that could affect the migration.50:06Once everything is ready, the next step is to create a virtual machine in an FBIS, following the Cisco virtualization requirements for call manager 15 issue four, and now comes the data migration, which is one of the most important parts of the process.50:19As I mentioned before during ideas restore, call manager rebuilds the database. So that's also why it's important. The target cluster should have the same CPU memory and storage resources as the source source cluster at least for these kind of scenarios. This helps prevent services from failing to start because of.50:34Insufficient resources, e.g.. After complete verify and adjust any required configuration such as gateways or patterns, partitions, other network settings depending on your, on your current deployment.50:53Once all the Cisco unified communication notes have been installed and restored, the final step is to verify that everything is working correctly. Next next slide please. So that's going to start by running the post upgrade call file.51:06And this helps identify any remaining issues or configuration problems after the migration. If the results are clean, you can move onto the functional testing. And what are we going to do in the functional testing? Well, we should, include, e.g., placing test calls, checking the voice quality and latency.51:22Assuming that the IP phones registered correctly and successfully verified the database replication that.51:42That is very important the database replication because sometimes database replication has issues after this process. So it is important we keep keep in mind that if all of those tests are successful and they post upgrade reports, NO issues, you can consider the cluster is healthy.51:48And the migration is complete. Now, my colleague Jorge will give you a tag tip and and the final demo about all these configurations, so please go ahead Jorge. So thank you Mario, before any migration or deployment, it is always a good idea to check the health of the environment, make sure to run.52:05The appropriate and post upgrade to identify any potential issues. Also verify that NTP and DDS are configured correctly and working properly. In addition confirm that the server has enough CPU, memory and storage resources available for the deployment.52:25These simple checks can help prevent problems caused by configuration issues or lack of resources from our experience in tech in many deployment and integration issues could have been avoided with a few basic validation steps before starting spending a few minutes on preparations can save hours of.52:45Shooting in later.53:05So we will head with the demo. So this is the main NFPAS, which Mario introduced it earlier. For this webinar, we will focus on the settings section where you can view and manage all the deployed virtual machines. Here you can see the topology that.53:06Dashboard which provides a visual representation of all the deployed virtual machines and their network connections. At the top left of the screen, you will find a dropdown menu that contains the virtual machines currently available for deployments such as call manager, IM and presence, unity connection, emergency responder, expressway.53:26Any applications not listed in this menu are not currently supported.53:47For this example, we will select call manager once selected, the virtual machine note appears on the dashboard. You can then drag it in into the workspace where four connection points will be displayed. These connection points are used later to connect the virtual machine to the appropriate network bridge. On the right side we can configure the the.53:52Deployment details including the virtual machine name and the bootable image, the virtual machine profile, the sizing option, small, medium or large, data store these settings determine how virtual machine will be deployed. So once done that we will connect the.54:12The line that is our physical representation of the physical cable. So once everything is configured, we need to click on deploy to start the virtual machine deployment.54:32To monitor the process, we will go to virtual machine and then manage where all the deployed virtual machines are displaying on a list and we will see it right there. Next, you can see at the right that we have all the options that can be performed with this.54:45Virtual machine. So one of them is will will be the console option that will be opening on a few minutes. And this one is showing on a darker color indicating that it is still being deployed. As you can see that one is the one that.55:04This is still being deployed, we will switch to the adjacent CUCM virtual machine which is already prompting for installation on on a few and you can see on that one that is showing a blue screen that is prompting for installation. From this console, we can monitor the installation processing and re.55:24All time. So the available option also include power on and power off, start and short down the virtual machine. The next one is reboot and restarts the virtual machine, and then we have the Mount ISO.55:44And this is where we attach an ISO image to the virtual machine. This is commonly used to recovery disk if Cisco requested during our troubleshooting sessions. So as you can see we have the tools that allows administration to manage and troubleshoot their virtual machines.56:00On the bridges section and that we will go back, we can create a new bridges. So we need to simply click on the plus icon and select the desired physical interface. As you can see it will prompt you to fill on the required.56:20Data on that one and then in the network section we can manage the villains, where it is configuring an in access trunk or an access mode or trunk mode. Adding a new VLAN is also as simple as selecting a network and entering the required parameter.56:41Such as if I say before if the network will be on access or drink mode. So we will go on now with the image and profile section and the image section contains the available deployment profiles, including if we have a small medium, and large alert.57:01With their associated CPU memory and storage specifications as you can see on the screen, to upload a new.57:20OBA file, we need to image of OVA file, we need to select upload and choose the data store and and you can see we are selecting the bootable files right there. We select the desired destination of the storage that we want to use and all the default values are.57:29Fill that by default, as you can see calling and virtual machine type, yeah.57:49Call manager. To upload the OVA file is a really similar process and we need to open up and select upload buildable file and on there you can see a menu that says checkbox metadata oVA/star. From there you will need to click on select file.57:54File or OBA and from that window if we click it, we will see an OVA file, we need to select the corresponding COCM OBA file.58:14And, click on open. Once I've done that, we just simply need to click on upload file and select the desired data store destination that we want to upload that one. One cool tip is that.58:25You can go to diagnostics and click on that button that says download, that info is really helpful for us as that since it will contain all the configuration that you have established on that one and it will prompt that the have been downloaded and you can upload it that to a tech case.58:40Also one on the other tip is CPU utilization. From here you can see.59:01If a virtual machine is showing a typical CPU behavior and also open attack case in case you need it. So we will go ahead with the Mario with the the last summary points.59:07Thank you for here. So, well, let's go now with the key takeaways of the information theory and demos that we have provided to you. So, well.59:27Let's start with important things to do before implementing NFVIS. The 1st one is that we must make sure that the version of call manager that we're going to install is version 15 four for NFVIS. Plan if we will be using the RS backups or import, all that depends on the version as I mentioned before. So.59:41So just keep in mind that the version that the the the final version is going to be 15 as you four. It is extremely important to use the pre upgrade call file on UC servers and apps.01:00:00Also plan and execute the NFVIS installation by removing the esxi boot as we did in the 1st demo. Do you remember that we deleted the virtual drive and created a new one for the NFVIS? Follow the installation steps and configure the network settings as you would do for any kind of installation, ok?01:00:14Now regarding the best practices, remember remember that we are going to use the default username and password. Do you remember them? They were admin and admin 123 pounds to enter any VIS for the 1st time and after finishing the installation and remember that you need to change the password to one that you have.01:00:32Previously deviced prior installation, ok?01:00:52Always use the OVA and ISO images downloaded directly from Cisco.com. That was also attacked. There is NO other image or place where we can do that. We need to always use the cisco.com images and OVA files, ok?01:00:57After the setup, know the three types of interface for the management of NFAIS. Do you remember them they were the NFAS portal, the NFA CLI, and the NFAS API, ok?01:01:14Verify that the network configurations are accurate such as VLANs and breaches. Remember that part of the separated VLANs for management and for voice, ok? Always use the DRS backup or data import neighbor any kind of unsupported methods. Remember that tip about not using snap.01:01:28Options because that create data delta files and corruption, everything that we want to avoid. And finally use the post upgrade code file for use servers and apps in order to have everything clear clarified and established, now remember to do the functional testing. So, well.01:01:47Next slides are going to be, about useful links. My colleague Jorge is going to provide them. So that's going to be all the theory on my part. So I I hopefully I hope that you have enjoyed and find these useful, so thank you very much for your attention. Go ahead Jorge.01:02:07Oh, thank you Mario. So here we have the virtualization guide where you can see which versions of sxi and AVAS for UC and Nutanix if you want to use it for your business edition server, here we have more about the system.01:02:23Going to be adjust the.01:02:43If you want to learn more about it, and finally we have finally virtualization docs for 15 issue four where you can follow up. We will share it later this presentation so you can have it handy and now comes the good part if you have some questions and answers.01:02:46You can open the mic or put, in the chat your questions if you have them. Let's see if we got, you know you guys are answering them quick, but I'm just going back and seeing if there's anything that has not been answered yet.01:03:07Let's see supported. Yeah, I mean these are all great questions. Do we have anything else?01:03:28Do you guys see anything on there that you'd like to delve in more? Oh, well, yeah, circle mentioned that he would like to see more details on the management. We can help you on on a tech case if you need help with that. We do it quickly since it was a webinar and we need to do a quick demo but.01:03:49We can help you to attack case if you have more questions and we can show you on detail.01:04:08Those things I'm having some issue that's not working as expected, so.01:04:14Again, you know, if there's, you know, real life situations that you guys are having to, please do raise a tag case. Can you let them know how they do that and then we can keep going? Oh yeah, I, I already, well, I already know the answer of that one and they.01:04:29In A case with that and we asked internally with our developer team and they said that they do that since they need to allocate CPU resources for the the host of the virtual machine, we can help you on on on a tag case since I have that.01:04:49Chat conversation and we can reply that and to explain you more on detail what is happening, so you can open up that case gladly and we will help you with that.01:05:09Perfect, thank you. Any other questions? Go ahead and put it right into the chat. I'll give another minute and if not, the recording and the slides will all be available by the end of the week. So.01:05:20Let's see, but like I said, yeah, like Jorge and Mario once again, thank you so much for this fantastic presentation and taking.01:05:36Us through all of this great content. Like I said, the recording and slides will be available in the community. I put the community link, but you can just find it in the collaboration video space. That is where it will be. Again, my name is Brookehammer. I'm the English community manager. Please join us on the community. If you have more questions after the session, that is a great.01:05:56Great place to go ahead and ask them as we will, you know, be monitoring a little closer into those chats and we have some fantastic VIPs that handle a lot of questions that you have and we could work through real time if you don't want to open a tech case, so we do have that. You can go to the next slide.01:06:16We'd love for you to follow us on all of our social channels. It's Cisco community on LinkedIn and X, Instagram, YouTube Facebook and Blue Sky. We have all the sessions that are coming through, that, you know, we will bring bringing to you throughout the year. We do a lot of that on social, so if you are ever questioning or you can come to the.01:06:35Community to get that.01:06:55We did have a question that just came in. Is there any plan for Cisco not supporting VMware soon? So I don't want that to go not answered. Yeah, about that yeah there's a plan of not supporting being soon. That's why we reope any just for UC and also.01:06:57So we are planning to on new servers, a good really good server, Nutanix.01:07:17So yeah, I believe the last supported that we free up is SXR sxi eight and on that one we only have documentation, but yeah, on the future we are not planning to support on Pingberg.01:07:23Yeah, that's correct. Thank you. Well, once again, thank you everybody for joining us today on this community live session. As I said, the slides and the recording will be available on community.cisco.com under the collaboration video board. And thank you again. There will be a short survey at the end that.01:07:40It helps us, you know, bring you more sessions and and follow up with other sessions that you may need in the future. So please do take a moment to do that. It's super valuable. Thank you. Thank you to our presenters. Thank you for our question managers and thank you all for being here. Have a wonderful day.01:08:00Thank you, everyone. Thank you. Have a good one. Thank you for coming.01:08:19