Cisco Unified Communications Manager CallManager 8.6.2.10000-14 ENG--ISO.torrent 50
Elpidio Heart
hey Aziz,
I have downloaded the ccm 5.1.1 and am now downloading 6.0.1. i had problem adding the cisco IP communicator to call manager, as it said license file required, will i have the same problem in ccum 6.0.1. please advice if i need to buy it
Cisco Unified Communications Manager CallManager 8.6.2.10000-14 ENG--ISO.torrent 50
Download https://vlyyg.com/2yXeky
- If we want to set up a home lab or to practice our collaboration studies we might want to set up as we did in our previous video, a VMware ESXi sized server. And then we can have multiple virtual machines running on that ESXi platform. And in this video we want to take a look at how to set up a Cisco's Cloud Services Router or a CSR 1000 V. This is a fully functional virtual router that we can get for free, and we can install that on top of VMware ESXi, but that's not the only platform we could install it on top of Microsoft Hyper-V, we can install it on Amazon Web Services, and it's going to be running a specific flavor of Cisco iOS. It's going to be running Cisco iOS XE, and this is great for our home lab use. I know some CCA candidates, since it's a free download from Cisco they set up multiple instances of the CSR 1000 Vs all running within a virtual machine, like an ESXi server, and they can have very, very elaborate topologies. And I mentioned that Cisco is going to allow us to download this for free. It's an evaluation version of the CSR 1000 V. It's not something you would want to run in production because Cisco throttles the throughput but for use in a home lab, it's a great solution. Here's how we can download the software for free. Now the specific version we're going to be downloading is 3.11.2S ED. We can download this, even if we do not have a SmartNet Maintenance Contract. Here's the URL that I want you to go to. You're going to go to bit.ly/csr1000v, that's a little shortcut link that I set up for you. And that's going to take you to a page like we see on screen. Now, maybe you've already logged in with your Cisco account, because you do have to log in you don't have to have special permission on your account. Like you don't have to have a maintenance contract, but you're got to be logged in. And I want you to download this ISO image, notice we've got different versions of the image on screen. We've got an OVA, we've got a BIN, we've got an ISO file, personally I recommend downloading the ISO file. I've had some issues with compatibility when it comes to the OVA, so that's, what's worked for me. And the way you're going to download that is you're going to click that little download button next to the shopping cart for that ISO file. And if you click that download button, and you've not yet logged in, you'll be prompted to login then. Now let's take a look at this topology that we're going to be building throughout this course. We're going to start off with our Lab Network. And in my case my Lab Network has a network of 172.16.0.0 and it's a 16 bit subnet mask. And that ESXi router that was set up in the previous video, it connects into my lab network using a virtual switch that comes by default inside of the ESXi server. And this virtual switch is connecting out to my lab network using the first network interface card on that server, that physical server, that HPE ProLaint that I was telling you about in the last video it has four different NIC cards, and it's going to use NIC0 to connect out to our network. That's what we're plugged into right now. What we're going to be doing in this video is we're going to be creating a virtualized router that's going to connect into this default virtual switch that we have. We're going to create a router called HQ on the interface facing out to the lab network. It's going to have an IP address of 172.16.20.1 with a 16 bit subnet mask. But then this HQ router it's going to have another interface point to our collaboration typology. You see, I don't want to mix my collaboration network with my lab network because we're going to be setting up things like a DHCP, I don't want to mix those two. So off of this HQ router, we want to have another switch, and that's what we're going to do in this video. We're going to create a switch a virtualized switch named HQ-SW1 and it's going to be in the IP address base of 10.3.3.0/24 and that router interface, it's going to have an IP address of 10.3.3.100 . And when we're setting up these virtual switches into which we can connect our virtual machines you're going to see that we don't connect a VM directly to a switch we connect the VM to a port group. Think of that as a group of virtual ports that live in the virtual switch, and we have a default port group it's called VM Network. So when we create this HQ router one of the interfaces is going to be pointing to the VM network port group, but we're creating this other virtualized switch for the collaboration typology we need a port group for it. So we're going to create a port group called PG-HQ-SW1 and that's what we're going to build in this video. But just to give you a vision of what's coming up later on we can start connecting our collaboration servers into this HQ switch 1. For example in an upcoming video we're going to see how to install a Cisco unified communications manager server. It's going to be called HQ-CUCM-PUB because it's going to be our publisher server. Now at this point I've already gone to the URL that I showed you and I've downloaded the CSR 1000 V ISO file. So let's go out to our VMware interface that we saw in our previous video, and let's number one, set up a virtual switch, let's then create a port group that is associated with that virtual switch. Then let's install our CSR 1000 V router. It's going to be the HQ router. We'll do a basic configuration on that router that makes sure we have connectivity to the outside world, and again in future videos we're going to be installing different collaboration servers that will virtually connect into HQ-SW1. So let's jump over to that ESXi interface now. All right we're sitting in our ESXi interface that we set up in our previous video, and the first thing we want to do is to create a virtual switch that HQ switch 1, and to do that we're going to go under networking, and we'll see that we've already got a vSwitch0, that's there by default, and I'm going to go under virtual switches. And in addition to vSwitch0 I want to add a standard virtual switch. And I'm going to call this HQ-SW1. Now, what is the uplink? I mentioned that my physical server, that HP ProLiant, it has four network interface cards. Why am I only seeing three here? Because vmnic0 is already in use by vSwitch0. So which of these uplinks should I choose? Well, if you recall our topology did you switch one connect out to the outside world? Did it connect out to my lab network in any way? No. It was all part of a network that lived entirely inside of this VM-ware Server. Well, I don't really want any uplink so I'm going to click this X to get rid of any uplinks. And I'm going to say Add. So we've now created a virtual switch, but remember when we create a virtual machine like our CSR 1000 V or our communications manager server, when we set up that virtual machine we don't say connect me to this virtual switch, instead we say connect me to this port group, which is associated with the virtual switch. So I'm going to go under a port groups and let's create a new port group. I going to call this port group PG-HQ-SW1, to remind them to me that this is a port group for the switch named HQ-SW1. I'm not going to worry about VLANs or anything like that. And it's asking what virtual switch do you want to be associated with? I want to be associated with HQ switch 1 that we just created. I'll select that, and I'll say add. Now when I set up my CSR 1000 V I'll be able to say, connect this into PG-HQ-SW1. Now let's upload that ISO file that we had downloaded from Cisco. To do that we go under storage, and I've only got one datastore on my server, and I'll click on datastore1, and I'll say I want to go into the data store browser. And notice that we don't have any files that I've uploaded yet ? So let's go to upload. And now I'm just looking on the hard drive of my computer, and here's where I've put that ISO file. I'll select the ISO file, say open, and it's going to take a few seconds to get uploaded into this data store. And then when we go to install the virtual machine, we can say boot up, not off of a CD but boot up for this ISO file that lives in the data store. It should finish up here in just a couple of seconds. All right there it is, let's close out of this and now we're ready to install our CSR 1000 V. And even though it's not a traditional server it is a virtual machine. So I'm going to go under Virtual Machines and we don't have any right now, but I'm going to say Create/Register VM. And I want to create a new virtual machine. Again, you may be thinking didn't Cisco give us an OVA file. They did personally on my hardware with my version of ESXi I've had an issue with the OVA file, so I've experimented around a little bit, and I'm going to show you what I've found works for me. Now, this is not the only way to install it you might try something else, it might work for you, but I going to install the ISO file. So I'll say create a new virtual machine and I'll say next let's give this a name. It's going to be the HQ router. I'll simply call it HQ. And again for you it might be fine to leave the compatibility at the default. After some experimentation though I'm going to use ESXi 5.0 virtual machine as the compatibility. For the guest operating system it's going to be a flavor of Linux, and again this is not the only flavor of Linux that will work, but what I've had good luck with is Other2.4 Linux (64-bit). Let's click on next. And there's only one data store to store the virtual machine image. So I'll click on next again. How many CPU's do we have? How many cores? I'm fine with just one. For memory I need a 2.5 gigabytes of memory so I'll change the unit of measure from megabytes to gigabytes. And I'll say 2.5. 8 gig is fine for the hard drive size, it's not going to be taking up much storage, and notice that I've got one network adapter that's connecting to the port group that I created. But remember this router is going to have one interface that points to my lab network and it's going to have another interface that points to our collaboration topology. Now this Network Adapter 1 it's pointing to my PG-HQ switch 1 that we just created, but I need to have another network adapter that's going to point to my lab network. So let's say Add network adapter, and notice right now they're both pointing to PG-HQ-SW1. So for the second adapter, I'll choose our other port group the one we have had by default that's named VM Network and that's associated with vSwitch0 that we have by default. So now I've got my two network adapters, each pointing to different port groups. And for the CD, I don't want to use a CD on the host device, I want to boot up off this data store ISO file that we just uploaded. So let's select data store ISO. I'm going to select my CSR 1000 V, we'll say Select and I'll say next, this just reviews our configuration it's a summary for us. I'm happy with this configuration so I'm going to say finish. And here in a moment, we're going to see this pop up under virtual machines. There it is. I'm going to go to HQ and I'm going to power it on. And just to see it a bit better, I'm going to click on this terminal thumbnail and under actions, I want to say let's open this up in a new tab. And this installation does not require any interaction, I don't have to press enter or answer any questions until it comes up with that traditional router message where it says, do you want to go through the system configuration dialog wizard? And I'm not going to do that. But it's going to take several minutes to do this, so I'm going to pause the video here and then we'll resume after this installation has completed. We're sitting at our configuration dialog prompt, and I'm going to say, no, I don't want to go through that configuration dialogue wizard. So we give it a few moments to finish coming back up here. And we're sitting at a router prompt. Let's do some basic configuration after all the messages you stop scrolling. Let's go into privilege mode by saying enable. Let's go into global configuration mode with a conf t for configure terminal. And one thing I like to do is to go into the console port which we're virtually connected to here and set things up such that when a message pops up on the screen like we've seen scroll by. If I'm in the middle of topping something, I really don't want those messages to interrupt what I'm typing. So what I can do to prevent that from happening is to go into my console zero line and I'm going to say logging synchronous. Also I like to in a lab environment, not for production but in a lab environment, I'd like to not be automatically timed out. So I'm going to say my exec-timeout 0 0. That means it will never time out. And if I want to go out to the rest of the world I need to point to a DNS server. So I'll say my IP name-server is the very commonly used 8.8.8.8 that Google maintains for us and we'll press enter. And one of the challenges that we have here is to know what interface points to my lab network and what interface points to my collaboration topology that we're going to be building. In other words, what interface points to that HQ-Switch 1 that we created. Let's take a look at the interfaces we have, I'll say, show IP interface brief I've got two interfaces gig 1 and gig 2. Let's go back to our ESXi screen, and we can see very clearly when we look at the virtual machine which interface is connecting to which virtual switch via a port group. So really briefly, I'm going to close this console. Let me put this back to its original size. And we can see that network adapter one is connected to the port group of VM network. So this is pointing to that default virtual port group, that's associated with our default virtual switch which is getting out to the rest of the world including my lab network via NIC0. Here's the one that we created. PG-HQ-SW1 it's connected to adapter two. So in our case, it looks like gig 1 goes to my lab network and gig 2 goes to my collaboration topology that we're going to be building. So let's go set up gig one to begin with. I'll go back into my terminal. Then I'll say let's open this in another tab. I'll make it a bit bigger force. Lets go into global configuration mode. And I'll say for interface gig 1 this points to the lab network and all of that topology that I showed you that had an IP address of 172.16.20.1 with a 16 bit subnet mask. So I'll say IP address 172.16.20.1 We'll give it a 16 subnet mask. I'll say no shot to administratively bring it up. Let's go into interface gigabit 2 this points to my collaboration typology that we're going to be building. It's got an IP address based on our topology of 10.3.3.100 with a 24 bit subnet mask. Again, let's do a no shutdown to bring it up administratively. And I need to have a default route, If I want to get out to the rest of the world, I want to point to the default router for my lab network which has an IP address of 172.16.1.1 . So let's set up that default route. To do that we say IP route 0.0.0.0.0.0.0.0 and then we say the next hop address for this default route is 172.16.1.1 And we are done let's exit and let's do a copy run star to write our running config to our startup config. And let's test this. Can I get to cisco.com for example? Can I ping cisco.com? Yes I can. That was successful. Oh, and one of the things we want to do here let's set the host name. Let's go back into global configuration mode. I'm going to say host name HQ, because this is our HQ router I'll exit. And again, do a copy run star. And now our CSR 1000 V is configured. So taking a look at what we've built, we've created a virtual switch named HQ-SW1. It doesn't connect to a physical NIC in my server because this virtual switch is going to be self-contained within the collaboration topology, and I associated a port group with that switch, and the port group was named at PG-HQ-SW1. We installed our CSR 1000 V connecting one interface to the lab network via vSwitch0 and the other interface to our collaboration network via HQ-SW1. And in upcoming videos, we're going to be installing servers that will virtually connect into HQ switch 1. So in this video and the previous video we've seen how to go out, assuming you have some server hardware to run it on. We've seen how to go out and get a free license to copy of VMware ESXi. And we saw how to go out and get a free copy of Cisco's CSR 1000 V virtual router. Admittedly, it's not a version you would want to use in production. It's throughput is throttled but it's great for a lab environment. Well let's say that you don't want to set up a home network. The great news is Cisco DevNet has a sandbox that allows us to reserve topologies for free, and go out and use those topologies. Now that sandbox is continually changing in terms of what devices and what labs are available to us. By at the time of this recording there is a topology that's geared towards a Cisco Unified Communications Manager Server version 12.5 which is what we're going to be running, and what I want you to be familiar with for the exam. So in our next video, we're going to take a look at how we can go out and access that virtualized topology out of Cisco's dev net site.
aa06259810