Contents
Last updated: April 3, 2019

This guide describes how to access all the features of our Collaboration lab racks. Specifically, it describes how to establish a VPN connection between your location and our Collaboration lab rack, and how to access each of the devices and servers described below within the lab rack from your location.

Important note concerning on-demand rack sessions: When one of our COv2 racks is not in use, all of the physical and virtual devices are powered off. When you schedule a rack session to start immediatly all the devices are simply powered on. The physical devices (SW1, R1 and R2) take 6 to 7 minutes to fully boot and may have the proper config on them or the Cisco factory configuration on them. Since the switch also does the majority of the routing for the devices in the rack you will not be able to ping anything until the switch is booted and has the proper configuration which you may need to apply by pasting in the config from the Default Collaboration Config (see Initial Configurations). The Cisco Collaboration servers can also take as long as 30 minutes for all of them to be fully booted. To avoid this, schedule your rack session at least 45 minutes ahead of time so our automation can have the rack ready for you to use.

See the next topic in this section for detailed Collaboration lab rack hardware spefications.

Your lab rack consists of:

  • Two 2911 routers
  • One 3560E-PD switch
  • Two 8845 Cisco IP telephones
  • Four Cisco Unified Communications Manager (CUCM) Publisher servers
  • One Cisco Unified Communications Manager (CUCM) Publisher server SME version
  • One Cisco Unified Communications Manager (CUCM) Subscriber server
  • One Cisco Unity Connection (CUC or UC) servers
  • One Cisco Unified Contact Center (CUCCX or UCCX) server
  • Three Cisco IM and Presence (IMP) servers
  • Two Expressway C (CES) servers
  • One Expressway E (CES) server
  • One Cisco Meeting (CMS) server
  • One Cisco Unity Express (CUE) server
  • Four Windows 10 machines running Jabber, Wireshark and other tools
  • Two Microsoft Active Directory server (labeled “hq-dns” and "ext-dns" in the lab rack diagram)
  • One access server (not shown in the diagram) for console port access to routers and switches
  • Additional infrastructure not visible to you, nor configurable by you, to connect your rack to servers and the VPN

The Lab Rack Diagram in the third section shows how all these components, except the access server and infrastructure elements, fit together.

Router and Ethernet Port Tables contains the summary tables of VLANs, IP subnets, router and switch port connections.

Device Connectivity is a quick reference for rack access information.

The lab topology is broken into 5 sites:

  • HQ
  • SB
  • SC
  • PSTN
  • EXT
^ back to top