Initially you would require the ISO image of the CUCM. The process is rather simple, to install CUCM the required hardware is:

Ram: 2GB, Harddisk: 80GB, CPU:1. Click on the image below, as it would open photobucket and the other stream of pics can be seen from there.

Figure 1: Start screen

To have a functioning CUCM VM, you should choose Workstation 6.5-7.x, as CUCM will work with ESX 4.x only. I ran with all sort of problems with ESX5 only (workstation 8).

Figure 2: Workstation 6-7.x

Before finalizing the Setup, select Customize Hardware.

Figure 3: Customize Hardware

At this point, choose the network that you have connected the GNS3 with. In my case i have setup VMnet 8, as seen in figure 4.

Figure 4: Choosing the correct network

The ISO which was downloaded will run Unity Server too, the only difference between the two components are the hardware requirements.

Unity will require: RAM: 4GB, Harddisk: 160GB, CPU: 1. The rest of steps would be the same.

This conclude the setup steps to configure the Virtual Machine. Once that is done, we would proceed with the installation of CUCM.

1- ISO image of CUCM, it can be found at www.cisco.com

2- VMware workstation, as it is the compatible virtualization tool.

3- GNS3 with a router IOS.

For the setup of CUCM there are few components that are required, there is the essential part that without it CUCM will not install. It is NTP. We would use GNS3, to connect the CUCM to Router with NTP configurations on it. Figure one shows the essential configurations, and the connectivity.

Figure 1: GNS3

The Cloud would be configured with port that is connecting to the VMware network. Alternately, a Windows Server can be installed in VMware, configured as Domain Controller, DNS server, and NTP server.

Second component that might require is DNS. While configuring CUCM there is the option of installing DNS client, if you isntall it. then the hostname of CUCM should be resolvable. For this tutorial i have not done that. Although, for a real practice it is best to configure the Windows Server. As other operations can be practiced as well. Such as user authentications, and user related activities.

In part two, We would look into how to create the VMware machine, as that is the second step. Mistakes in creating the VM is equal to many hours wasted in trial and error solution.

MQC Frame-Relay Traffic shaping

In here, we see the efforts put into introducing the MQC style for traffic shaping. but with this method, you nest the MQC into a map-class. Yes, it doesn’t look pretty, and seems slightly confusing. But let’s have an example, and this will ease our understanding of the topic.

policy-map CBWFQ
class VOICE
priority 64
class class-default
fair-queue
!
policy-map SHAPE
class class-default
shape average 256000 2560 0
shape adaptive 128000
service-policy CBWFQ
!
map-class frame-relay TEST_DLCI
service-policy output SHAPE
!
interface Serial 0/0.1
frame-relay interface-dlci 101
class TEST_DLCI

This example lengthy as it seems, but it is still straight forward. we have defined shaping in MCQ style, then impliemented that into map-class. lastly, this map-class was configured inside the interface-dlci.

Class Based Generic Traffic Shaping

This is the last method out of the four methods that can be used for FRTS. It is similar to the legacy GTS. In this, you have the advantage to match the class based of frame-relay dlci. Lets see an example and that should show us the details.

class-map DLCI
match fr-dlci 123
!
policy-map SHAPE_123
class DLCI
shape average 256000
!
interface s0/1
service-policy output SHAPE_123

One of the main issues of this method is that adaptive shaping can’t be used, nor voice-adaptive fragmentation.

all of the four methods have their advantage and disadvantage to them. from the simplest, to more complicated ones. The situations/requirment will be the deciding factor on which method use for FRTS.