Lab 8-1 CUCM First Run & Shutdown


This lab will give you the opportunity to explore the user interface of Cisco Unified Communications Manager (CUCM) and learn how to shut it down cleanly.

Starting Point

You should already have a working CUCM install within a virtual machine with a supporting network and services, as described in lab A-1.



You'll know that you're finished when the VM console window closes on its own after displaying shutdown logging messages from the CUCM server.

Exam Objectives

None. Shutting down phone systems is something best left to prototyping labs, where it is incredibly valuable. It is only rarely done in the wild and is not part of the knowledge Cisco expects from their CCNA candidates. On the other hand, familiarity with the menu structure of Cisco's appliance software, like CUCM, is important.


CUCM is running in a Virtual Machine (VM) running on an inexpensive PC. CUCM will behave as if it was installed directly on the hardware of a Cisco appliance.

Underlying Network Configurations and Services

Our router on a stick provides a DHCP server, both in our data VLAN and in the voice VLAN. CUCM has a static address within its virtual machine, while the real machine underlying that VM receives some unimportant address in the data VLAN from DHCP.

Table 1. Important Addresses and Logins
CUCM AddressCUCM Admin Login / PasswordCUCM OS Admin Login / Password / ciscoclass
(Used for almost everything)
cucmroot / ciscoclass
(Used for the OS Admin interface and the console login)

Our CUCM server will be configured with a static address of This is in the data VLAN because CUCM generally deals with signaling traffic rather than the actual audio that requires QoS expediting. The physical computer that hosts the Virtual Machine (VM) containing the CUCM server will automatically receive some unimportant address in the same subnet from the DHCP server.

Lab Walkthrough (Screenshots are clickable)