This section
provides guidance for configuring Collaboration Edge OTT in the Service
Provider Cisco HCS data center. Use this information with, but not as a
replacement for, the Cisco Expressway documentation.
Two more VLANs are required to accommodate ASA contexts, global DMZ inside and outside. The customer inside and outside VLANs
are also required. Configuration is required in the Nexus 7000, vSphere Distributed Switch (VDS) (and in the Nexus 5000, if deployed), UCS Manager, and ASA. The global DMZ inside VLAN (after Firewall) and the customer
outside VLAN extend into the DC. These VLANs are used on the virtualized Cisco Expressway-E.
Expressway in OTT
DeploymentsExpressway-E hosts the public IP address. The client accesses
this address by way of the public Internet. Expressway-E typically sits in the
DMZ of the enterprise network. In the HCS DC, Expressway-E runs on UCS behind
the ASA. Expressway-C sits in the same IP address space as
Cisco Unified
Communications Manager.
Communication between Expressway-C and Expressway-E is through the ASA, which
provides the NAT and firewall functions.
Shared Expressway for
Business-to-Business Dialing: Expressway-E hosts the public IP address. The
non-HCS businesses access this address by way of the public Internet.
Expressway-E typically sits in the DMZ of the shared network, between the
common outside and shared inside firewall contexts on ASA, to create a DMZ. The
Expressway-E is connected to the Expressway-C through the shared internal
firewall context. Communication between Expressway-C and Expressway-E is
through the ASA, which provides the NAT and firewall functions. The
Expressway-C is peered with the session border controller (as a neighbor). For
more information, see the
Cisco Hosted Collaboration Solution Solution Reference Network Design Guide.