UCS Network Configuration for UCCE
Design Considerations for High Availability
The High Availability (HA) deployment provides redundancy from a component failure in the Unified Computing System (UCS) architecture.
For deploying Cisco Unified Contact Center Enterprise (UCCE) on UCS B-Series servers, it is mandatory that HA must be used. Please follow the best practices and guidelines described in the Cisco white paper Design Consideration for High Availability and Scalability in Blade Server Environment for guidelines on implementing HA. Pay particular attention to the following information in this white paper:
- The guidelines described in the section “Server I/O High Availability Architecture” with redundant infrastructure and paths.
- The diagrams of HA design shown in Figure 2, Figure 4, and Figure 6 in the above white paper. For an additional example of Cisco UCS 6100 Series Fabric Interconnects HA, refer to Figure 5 in this document.
This HA design requires redundant Cisco UCS 6100 Series Fabric Interconnects on a Cisco UCS and redundant Cisco UCS 2104XP Fabric Extenders.
For an introduction to UCS architecture, see the Cisco white paper http://www.cisco.com/en/US/prod/collateral/ps10265/ps10281/solution_overview_c22-522771.pdf.
Setting up the Cisco UCS Fabric and the Ethernet Network
Figure 1 below shows the cable connections between the following UCS Fabric components with redundant configuration for a UCCE on UCS B-series deployment:
- Two Cisco MDS multilayer fabric switches
- Two Cisco UCS 6100 Series Fabric Interconnects
- Two Cisco UCS 2104 Series Fabric Extenders
- Dual redundant Ethernet Uplinks that eventually be connected to redundant Network Routers.
Please note that the B200 M1 blade is configured with the Cisco UCS M71KR-Q QLogic network adapter that provides 10 Gigabit Ethernet and Fibre Channel connectivity for the server.
Redundant chassis is not required, but recommended.
Creating the UCS Profile
Understanding the service profile is key to understanding the blade management in the UCS. The service profile represents a logical view of a single blade server, without needing to know exactly which blade you are talking about. The profile object contains the server personality (identity and network information). The profile can then be associated with a single blade at a time. The following link provides a step by step guide on how to provision service profiles.
Every server that is provisioned in the Cisco UCS is specified by a service profile. A service profile is a software definition of a server and its LAN and SAN network connectivity. In other words, a service profile defines a single server and its storage and networking characteristics. The UCS Manager software is embedded in the Cisco UCS 6100 Series Fabric Interconnects, which is also where the service profiles are stored. When a service profile is deployed to a server, UCS Manager automatically configures the server, adapters, fabric extenders, and fabric interconnects to match the configuration specified in the service profile. Automating the device configuration reduces the number of manual steps required to configure servers, network interface cards (NICs), host bus adapters (HBAs), and LAN and SAN switches.
This page does not provide a step by step guide on how to use UCS manager (it is assumed that a UCS Data Center certified engineer will perform this task.) However, it provides the necessary information to configure a service profile for UCCE.
VLANs for UCCE Public and Private Traffic
The service profile must have the complete and correct VLANs configured for UCCE Public and Private traffic. The following shows an example of the VLANs needed for a UCCE deployment. One VLAN is needed for the Public Ethernet traffic and one VLAN is needed for the Private Ethernet traffic.
The service profile must have a vSAN configured for UCCE. The following shows an example of the vSAN needed for a UCCE deployment. The vSAN network ID must match the vSAN ID configured on the SAN devices for connectivity.
Configuring the VLAN Trunking on the Network Routers
The following is an example of the port configuration for the network router. For redundancy there must be at least two TenGigabitEthernet ports configured per UCS 6100 Series Fabric Interconnect.
interface TenGigabitEthernet2/1 description Fabric-Connect-A switchport switchport trunk encapsulation dot1q switchport trunk allowed vlan 1,10,11 switchport mode trunk no ip address mls qos trust cos spanning-tree portfast trunk
Where VLAN trunking is used to uplink to VMware, it is essential that the network configuration be implemented correctly. Testing has shown that improper configuration of VLAN trunking directly and negatively impacts performance of the system.
As with all previous UCCE deployments, there must be dedicated public and private links between routers following supported models as defined in the Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND).
Configuring the ESXi Host Network for the Virtual Machines
For deploying Cisco UCCE on UCS B-Series servers, configure the vSwitches and vmnic adapters as follows:
Create one ESXi virtual switch and connect both VM virtual Ethernet adapters to the virtual switch.
NOTE: The Nexus 1000 virtual switch is not supported as a VMware switch.
To configure the network for VMs, you create a virtual switch connected to an Ethernet port on the server, and then associate the virtual machine's network adapter to this virtual switch.
To Add a vSwitch
- Login to the ESXi host using VMware Infrastructure Client
- Select the ESXi host
- Click on the Configuration tab
- Click on Hardware/Networking
- Click on Add Networking...
- Select Connection Types: Virtual Machine. Click Next.
- Select "Create a virtual switch" and select an associated VM NIC.
- Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: "VM Network 1")
- Click on Finish.
To Associate a VM Network Adapter to Network Connection
- Edit virtual machine settings.
- Select the Network Adapter.
- Select a virtual switch from the Network Connection/network label. (Example: "VM Network 1")
- Click OK.