CCIE Voice Lab 1.2 – Initial Cisco Unified Communications Manager Configuration

Lab 1.2 will explore the initial Cisco Unified Communications Manager (CUCM) configuration and setup. I’ve built two CUCM virtual machines on a VMware ESX 3.5 server. CUCM 7.x release includes a “starter license”, which provided 150 DLUs and a 3 node license. Follow the instructions in the Unity Connection-CUCME Lab 3 – Unity Connection Installation on VMware ESX 3.5 post for the process of building CUCM on VMware ESX 3.5.

CCIE Voice Lab 1.2 Tasks
1. Activate all appropriate and necessary Network and Feature Services.

2. Ensure that the call processing cluster does not need to rely on DNS for any services.

3. Ensure that the interdigit timeout does not exceed 5 seconds.

4. Quickly provision the phones in New York and Los Angeles.

CCIE Voice Lab 1.2 Solutions
1. First step is to log into the publisher, UCMPUB01. From there, navigate to System > Servers. If your servers are listed by their hostname, click each one and change to their IP Address.




2. Next stop, visit the Cisco Unified Serviceability interface. From there, Tools > Control Center – Network Services and verify everything in functioning correctly.

3. Next, the Tools > Control Center – Feature Services in the Cisco Unified Serviceability interface shows that by default, these services are deactivated. By going to Tools > Service Activation, we can select each server and then activate accordingly. To understand which service to activate, go to the Help > This Page and review the information in Table 11-1.

After activating the appropriate services for the Publisher and Subscriber, you can verify status by navigating to Tools > Control Center – Feature Services in the Cisco Unified Serviceability.

4. Returning to Cisco Unified CM Administration, go to System > Enterprise Parameters. Modify the Phone URL Parameters that reference UCMPUB01 to 10.1.10.20.

5. To modify the interdigit timeout, go to System > Service Parameters. Select the Publisher (10.1.10.20) in the Server drop down, followed by Cisco CallManager (Active) in the Service drop down. Look for the T302 Timer, and modify from the default 15000ms to 5000ms.

6. The easiest way to quickly provision phones is to enable auto registration. To accomplish this task, navigate to System > Cisco Unified CM and select the Publisher server. Use a phantom number range, such as 7000 to 7099, and uncheck the “Auto-registration Disabled on this Cisco Unified Communications Manager” box.

7. After a few minutes, the phones should register with UCMPUB01.

Pics of my Lab & Gear

CCIE Voice Lab 1.1 Solutions

Rather than dissect each sub-task individually, I will review each device, and then circle back around on verifying connectivity. One thing to keep in mind with the CCIE LAB, you needn’t necessarily configure everything in the order presented in the lab guide.

1. Below is the configuration for the frame relay switch. Also note, I’ve configured this router to synchronize with an NTP server on the Internet. This router will then act as the NTP server for the lab devices.

ISP#
!
clock timezone EST -5
clock summer-time EDT recurring
!
frame-relay switching
!
!
interface Serial0/0/0
description frame-relay link to London
no ip address
encapsulation frame-relay
no fair-queue
clock rate 128000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 301 interface Serial0/0/1 103
!
interface Serial0/0/1
description frame-relay to New York
no ip address
encapsulation frame-relay
clock rate 128000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 102 interface Serial0/1/0 201
frame-relay route 103 interface Serial0/0/0 301
!
interface Serial0/1/0
description frame-relay link to Los Angeles
no ip address
encapsulation frame-relay
clock rate 128000
frame-relay lmi-type cisco
frame-relay intf-type dce
frame-relay route 201 interface Serial0/0/1 102
!
ntp source FastEthernet0/0
ntp update-calendar
ntp server 198.82.1.201


2. Next, we’ll take a look at the New York router. First, the basic configuration parameters for the IP addressing, including the WAN (frame relay) and LANs/VLANs.

newyork#
!
interface FastEthernet0/0.1
description link to Internet
encapsulation dot1Q 1 native
ip address 10.1.1.101 255.255.255.0
!
interface FastEthernet0/0.10
description New York Server VLAN
encapsulation dot1Q 10
ip address 10.1.10.1 255.255.255.0
!
interface FastEthernet0/0.11
description New York Data VLAN
encapsulation dot1Q 11
ip address 10.1.11.1 255.255.255.0
!
interface FastEthernet0/0.12
description New York Voice VLAN
encapsulation dot1Q 12
ip address 10.1.12.1 255.255.255.0
!
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
frame-relay lmi-type cisco
!
interface Serial0/2/0.102 point-to-point
description frame relay link to Los Angeles
ip address 172.16.1.1 255.255.255.252
ip ospf network point-to-point
frame-relay interface-dlci 102
!
interface Serial0/2/0.103 point-to-point
description frame relay link to London
ip address 172.16.1.5 255.255.255.252
ip ospf network point-to-point
frame-relay interface-dlci 103
!


Next, the routing, including a default route to the Internet:

!
router ospf 1
router-id 1.1.1.1
log-adjacency-changes
network 1.1.1.0 0.0.0.255 area 1
network 10.1.10.0 0.0.0.255 area 1
network 10.1.11.0 0.0.0.255 area 1
network 10.1.12.0 0.0.0.255 area 1
network 172.16.1.0 0.0.0.255 area 0
!
ip route 0.0.0.0 0.0.0.0 10.1.1.3


Finally, some of the key “IP services” configuration in the router, including the DHCP scopes:

!
service timestamps debug datetime msec localtime show-timezone year
service timestamps log datetime msec localtime show-timezone year
!
clock timezone EST -5
clock summer-time EDT recurring
!
ip dhcp excluded-address 10.1.11.1 10.1.11.15
ip dhcp excluded-address 10.1.12.1 10.1.12.15
!
ip dhcp pool newyork-data
network 10.1.11.0 255.255.255.0
update dns both
default-router 10.1.11.1
domain-name ballplayersllc.com
dns-server 10.1.10.11 4.2.2.1
!
ip dhcp pool newyork-voice
network 10.1.12.0 255.255.255.0
update dns both
default-router 10.1.12.1
domain-name ballplayersllc.com
option 150 ip 10.1.10.20
dns-server 10.1.10.11 4.2.2.1
!
!
ip domain name ballplayersllc.com
!
ntp source FastEthernet0/0.1
ntp update-calendar
ntp server 10.1.1.4


3. Below is are the pertinent pieces of the configuration for the 3750 switch for the New York LAN/VLANs.

s1-newyork#
!
interface FastEthernet1/0/2
description to NewYork
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,10-12
switchport mode trunk
spanning-tree portfast trunk
!
!
interface FastEthernet1/0/8
description newyork phones
switchport access vlan 11
switchport voice vlan 12
spanning-tree portfast
!
interface FastEthernet1/0/9
description newyork phones
switchport access vlan 11
switchport voice vlan 12
spanning-tree portfast
!
interface FastEthernet1/0/10
description newyork phones
switchport access vlan 11
switchport voice vlan 12
spanning-tree portfast
!
!
interface Vlan1
ip address 10.1.1.3 255.255.255.0
!
interface Vlan10
description newyork-management
ip address 10.1.10.2 255.255.255.0
!
interface Vlan11
description newyork-data
ip address 10.1.11.2 255.255.255.0
!
interface Vlan12
description newyork-voice
ip address 10.1.12.2 255.255.255.0
!


4. Next stop is Los Angeles. The configuration here is very similar to New York. Note, this router uses a 4-port Ethernet Switch HWIC module.

losangeles#sh start
!
clock timezone PST -8
clock summer-time PST recurring
!
!
ip dhcp excluded-address 10.1.21.1 10.1.21.15
ip dhcp excluded-address 10.1.22.1 10.1.22.15
!
ip dhcp pool losangeles-data
network 10.1.21.0 255.255.255.0
update dns both
default-router 10.1.21.1
dns-server 10.1.10.11 4.2.2.1
domain-name ballplayersllc.com
!
ip dhcp pool losangeles-voice
network 10.1.22.0 255.255.255.0
update dns both
default-router 10.1.22.1
dns-server 10.1.10.11 4.2.2.1
domain-name ballplayersllc.com
option 150 ip 10.1.10.20
!
!
ip domain name ballplayersllc.com
!
!
interface Loopback0
ip address 2.2.2.2 255.255.255.0
ip ospf network point-to-point
!
interface FastEthernet0/0
description link to Internet
ip address 10.1.1.102 255.255.255.0
duplex auto
speed auto
!
!
interface FastEthernet0/3/0
description losangeles ip phones
switchport access vlan 21
switchport voice vlan 22
!
interface FastEthernet0/3/1
description losangeles ip phones
switchport access vlan 21
switchport voice vlan 22
!
interface FastEthernet0/3/2
description losangeles ip phones
switchport access vlan 21
switchport voice vlan 22
!
interface FastEthernet0/3/3
description losangeles ip phones
switchport access vlan 21
switchport voice vlan 22
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
frame-relay lmi-type cisco
!
interface Serial0/2/0.201 point-to-point
description frame relay to New York
ip address 172.16.1.2 255.255.255.252
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 201
!
!
interface Vlan20
description Los Angeles Server VLAN
ip address 10.1.20.1 255.255.255.0
!
interface Vlan21
description Los Angeles Data VLAN
ip address 10.1.21.1 255.255.255.0
!
interface Vlan22
description Los Angeles Voice VLAN
ip address 10.1.22.1 255.255.255.0
!
router ospf 1
router-id 2.2.2.2
log-adjacency-changes
network 2.2.2.0 0.0.0.255 area 2
network 10.1.20.0 0.0.0.255 area 2
network 10.1.21.0 0.0.0.255 area 2
network 10.1.22.0 0.0.0.255 area 2
network 172.16.1.0 0.0.0.255 area 0
!
ip route 0.0.0.0 0.0.0.0 10.1.1.3
!
ntp source FastEthernet0/0
ntp update-calendar
ntp server 10.1.1.4


5. London’s configuration is very similar to the other locations, with a few exceptions. First, the option 150 command for the voice DHCP scope points to the router, since this is will be a CUCME location. Also, London’s router has an NME-16ES-1G-P, which from the perspective of the router, looks like an independent switch.

london#sh start
!
clock timezone GMT 0
clock summer-time BST recurring
!
ip dhcp excluded-address 10.1.31.1 10.1.31.15
ip dhcp excluded-address 10.1.32.1 10.1.32.15
!
ip dhcp pool london-data
network 10.1.31.0 255.255.255.0
update dns both
default-router 10.1.31.1
dns-server 10.1.10.11 4.2.2.1
domain-name ballplayersllc.com
!
ip dhcp pool london-voice
network 10.1.32.0 255.255.255.0
update dns both
default-router 10.1.32.1
domain-name ballplayersllc.com
dns-server 10.1.10.11 4.2.2.1
option 150 ip 10.1.30.1
!
!
ip domain name ballplayersllc.com
!
!
interface Loopback0
ip address 3.3.3.3 255.255.255.0
ip ospf network point-to-point
!
interface FastEthernet0/0
description link to Internet
ip address 10.1.1.103 255.255.255.0
duplex auto
speed auto
!
!
!
interface Serial0/2/0
no ip address
encapsulation frame-relay
frame-relay lmi-type cisco
!
interface Serial0/2/0.301 point-to-point
description frame relay to New York
ip address 172.16.1.6 255.255.255.0
ip ospf network point-to-point
snmp trap link-status
frame-relay interface-dlci 301
!
!
interface GigabitEthernet1/0
no ip address
!
interface GigabitEthernet1/0.30
description London Server VLAN
encapsulation dot1Q 30 native
ip address 10.1.30.1 255.255.255.0
!
interface GigabitEthernet1/0.31
description London Data VLAN
encapsulation dot1Q 31
ip address 10.1.31.1 255.255.255.0
!
interface GigabitEthernet1/0.32
description London Voice VLAN
encapsulation dot1Q 32
ip address 10.1.32.1 255.255.255.0
!
router ospf 1
router-id 3.3.3.3
log-adjacency-changes
network 3.3.3.0 0.0.0.255 area 3
network 10.1.30.0 0.0.0.255 area 3
network 10.1.31.0 0.0.0.255 area 3
network 10.1.32.0 0.0.0.255 area 3
network 172.16.1.0 0.0.0.255 area 0
!
ip route 0.0.0.0 0.0.0.0 10.1.1.3
!
ntp source FastEthernet0/0
ntp update-calendar
ntp server 10.1.1.4


6. As mentioned above, I am leveraging a NME-16ES-1G-P Ethernet Switch Module to function as a “3750” in London. For all intents and purposes, the router “views” this module as a separate device. See here for a detailed explanation and here for an example of how I previous configured this module. Below is the pertinent configuration.

london-s1#
!
clock timezone GMT 0
clock summer-time BST recurring
!
!
interface FastEthernet1/0/1
description london ip phones
switchport access vlan 31
switchport voice vlan 32
spanning-tree portfast
!
interface FastEthernet1/0/2
description london ip phones
switchport access vlan 31
switchport voice vlan 32
spanning-tree portfast
!
!etc…!
!
!
interface Vlan1
no ip address
shutdown
!
interface Vlan30
description London Server Vlan
ip address 10.1.30.2 255.255.255.0
!
interface Vlan31
description London Data Vlan
ip address 10.1.31.2 255.255.255.0
!
interface Vlan32
description London Voice Vlan
ip address 10.1.32.2 255.255.255.0
!
ip route 0.0.0.0 0.0.0.0 10.1.30.1
!


7. Finally, some quick ping tests verify connectivity.

newyork#ping 172.16.1.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/28/32 ms

newyork#ping 172.16.1.6

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 172.16.1.6, timeout is 2 seconds:
!!!!!

newyork#ping 10.1.21.1

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.21.1, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/29/32 ms

newyork#ping 10.1.31.2

Type escape sequence to abort.
Sending 5, 100-byte ICMP Echos to 10.1.31.2, timeout is 2 seconds:
!!!!!
Success rate is 100 percent (5/5), round-trip min/avg/max = 28/32/40 ms
newyork#

CCIE Voice Lab 1.1 – LAN, WAN, and IP Services

The purpose of CCIE Voice Lab 1.1 is to configure the LAN, WAN and IP Services that will provide the foundation for the entire series of labs. Refer to the CCIE Voice Lab 1 Scenario Background post for a diagram and IP addressing information.

CCIE Voice Lab 1.1 Tasks
Perform the following tasks for CCIE Voice Lab 1.1:

1. Configure LAN and WAN based on the information provided in CCIE Voice Lab 1 Scenario Background.

2. Configure the WAN / Frame Relay as point to point links. On the WAN router, set the clockrate to 128000.

3. Configure OSPF as the routing protocol. The WAN should be area 0; New York LAN subnets area 1; Los Angeles LAN subnets area 2; London LAN subnets area 3.

4. Configure the Frame Relay router as an NTP server and synchronize each router with it. Set the time zones as appropriate.

5. Set up DHCP services for the Voice and Data VLANs. The TFTP server for New York and Los Angeles should point to the UC Manager server in NY. The TFTP server address for London should point to itself using the Voice VLAN IP address (VLAN 32). Exclude the first /28 block from each DHCP scope.

6. Configure switch ports for IP phones.

CCIE Voice Lab 1

CCIE Voice Lab 1 Scenario Background

Ballplayers, Inc. is a sports marketing firm headquartered in New York City, NY and branch offices in Los Angeles, CA and London, England. The firm represents both current and retired athletes and their associated marketing ventures. The firm had previous piloted Cisco Unified Communications Manager Express and Cisco Unity Connection. Ballplayers, LLC is now interested in deploying an enterprise Cisco Unified Communications solution that includes Cisco Unified Communications Manager, Cisco Unity Connection, Cisco Unified Contact Center Express, and Cisco Unified Presence. Finally, they may also pilot Cisco MeetingPlace Express in conjunction with this solution.***

***Note: I will proceed with MPE only as time permits and for personal learning. MPE is not on the CCIE Voice Lab Blueprint.

Below is a high-level design of the Cisco Unity Connection Pilot.

The following are the VLANs, IP Subnetting, Server Addressing, PSTN E.164 Address, and User/Phone information for this lab. Please note and realize, I may change and/or tweak this as I progress.

The first lab will discuss the basic IP setup requirements for New York, Los Angeles, and London.

Unity Connection-CUCME Labs: Wrap Up

After some thoughtful consideration, I am going to end any further development of the Unity Connection-CUCME Labs. When I initially launched my study CCIE Voice study efforts in July of 2008, my intention was to drill deep on each component of the lab. However, I've reached the conclusion that while this approach was worthwhile, it was also a tedious and time-consuming process. At the rate I am moving and studying, around normal work responsibilities and daily life, I would be sitting for the lab sometime in 2011! LOL

Instead, I am going to plow ahead with developing more “comprehensive” lab incorporating all technologies. The upside is I hope to accelerate the study process and aim to sit for the lab sometime in late spring / early summer 2010. The possible downside would be failing to delve deep enough to anticipate everything that could be thrown at me.

Look for a new series of postings shortly!