UCS Network Configuration for Unified CCE

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Network Requirements for UCS C Series Servers: Major update to address field issues with old design - new design added along with new diagrams)
Line 17: Line 17:
== Setting up the Cisco UCS Fabric and the Ethernet Network ==
== 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:
+
Figure 1 below shows the cable connections between the following UCS Fabric components with redundant configuration for a Unified CCE on UCS B-series deployment:
* Two Cisco MDS multilayer fabric switches
* Two Cisco MDS multilayer fabric switches
Line 26: Line 26:
Please note that the B200 blade is configured with the Cisco UCS M71KR-Q QLogic network adapter that provides 10 Gigabit Ethernet and Fibre Channel connectivity for the server. However, when deploying Clustering Over the WAN with B-Series hardware, the Cisco UCS M81KR Virtual Interface Card is used instead of the Cisco UCS M71KR-Q.  
Please note that the B200 blade is configured with the Cisco UCS M71KR-Q QLogic network adapter that provides 10 Gigabit Ethernet and Fibre Channel connectivity for the server. However, when deploying Clustering Over the WAN with B-Series hardware, the Cisco UCS M81KR Virtual Interface Card is used instead of the Cisco UCS M71KR-Q.  
-
=== UCS B-Series General Network Configuration for UCCE Deployment ===
+
=== UCS B-Series General Network Configuration for Unified CCE Deployment ===
-
Figure 1 illustrates UCS B-Series network configuration for UCCE deployment.
+
Figure 1 illustrates UCS B-Series network configuration for Unified CCE deployment.
UCS Fabric Ethernet switching mode must be set to '''End-Host Mode'''. Switching Mode is not supported.
UCS Fabric Ethernet switching mode must be set to '''End-Host Mode'''. Switching Mode is not supported.
Line 38: Line 38:
[[Image:PhysicalNetworkConnection.JPG]]
[[Image:PhysicalNetworkConnection.JPG]]
-
=== UCCE Public and Private Network Configuration (for deployments other than Clustering Over the WAN) ===  
+
=== Unified CCE Public and Private Network Configuration (for deployments other than Clustering Over the WAN) ===  
-
Figure 2 illustrates the UCCE Public and Private network connections set up in the UCS B-Series system.   
+
Figure 2 illustrates the Unified CCE Public and Private network connections set up in the UCS B-Series system.   
'''Figure 2'''
'''Figure 2'''
Line 46: Line 46:
[[Image:LogicalNetworkConnection.JPG]]
[[Image:LogicalNetworkConnection.JPG]]
-
=== UCCE Public and Private Network Configuration for Clustering Over the WAN ===  
+
=== Unified CCE Public and Private Network Configuration for Clustering Over the WAN ===  
-
Figure 3 illustrates UCCE Public and Private network connections set up in the UCS B-Series system with split fabric (i.e., a deployment containing redundant interfaces for each network alternating Fabric side (A/B)) and Clustering Over the WAN deployments.
+
Figure 3 illustrates Unified CCE Public and Private network connections set up in the UCS B-Series system with split fabric (i.e., a deployment containing redundant interfaces for each network alternating Fabric side (A/B)) and Clustering Over the WAN deployments.
'''Figure 3'''
'''Figure 3'''
Line 62: Line 62:
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.
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. However, it provides the necessary information to configure a service profile for UCCE.
+
This page does not provide a step by step guide on how to use UCS manager. However, it provides the necessary information to configure a service profile for Unified CCE.
-
== VLAN Configuration for UCCE Public and Private Traffic ==
+
== VLAN Configuration for Unified CCE Public and Private Traffic ==
-
The service profile '''must have the complete and correct VLANs configured for UCCE Public and Private traffic'''.  
+
The service profile '''must have the complete and correct VLANs configured for Unified CCE Public and Private traffic'''.  
-
The following shows an example of the VLANs needed for a UCCE deployment.  
+
The following shows an example of the VLANs needed for a Unified CCE deployment.  
* One VLAN is needed for the Public Ethernet traffic
* One VLAN is needed for the Public Ethernet traffic
Line 75: Line 75:
=== Public and Private Traffic Deployment ===
=== Public and Private Traffic Deployment ===
-
The following figure illustrates the VLANs needed on the SideA blade for most UCCE deployments. In these deployments, a similar VLAN configuration would be needed on the SideB blade.
+
The following figure illustrates the VLANs needed on the SideA blade for most Unified CCE deployments. In these deployments, a similar VLAN configuration would be needed on the SideB blade.
'''Figure 4'''
'''Figure 4'''
Line 97: Line 97:
== vSAN ==
== vSAN ==
-
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.
+
The service profile '''must have a vSAN configured for Unified CCE'''. 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.
'''Figure 6'''
'''Figure 6'''
Line 119: Line 119:
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.
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 [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND)].
+
As with all previous Unified CCE deployments, there must be dedicated public and private links between routers following supported models as defined in the [http://www.cisco.com/en/US/docs/voice_ip_comm/cust_contact/contact_center/ipcc_enterprise/ipccenterprise8_0_1/design/guide/uccesrnd80.pdf Cisco Unified Contact Center Enterprise Solution Reference Network Design (SRND)].
== Configuring the Virtual Switch and vmnic Adapters ==
== Configuring the Virtual Switch and vmnic Adapters ==
-
For deploying Cisco UCCE on UCS B-Series servers, configure the vSwitches and vmnic adapters as follows:
+
For deploying Cisco Unified CCE on UCS B-Series servers, configure the vSwitches and vmnic adapters as follows:
=== vSwitch and vmnic Adapter Configuration  ===
=== vSwitch and vmnic Adapter Configuration  ===
Line 145: Line 145:
[[Image:PaloVswitchConfig.JPG]]
[[Image:PaloVswitchConfig.JPG]]
 +
= Unified CCE on UCS C-Series Network Configuration =
-
= UCCE on UCS C-Series Network Configuration =
+
The following section provides instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (Unified CCE) on UCS C-Series servers.
-
The following section provides instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (UCCE) on UCS C-Series servers.
+
== Network Requirements for UCS C Series Servers ==
-
== Network Requirements for C-210 Servers ==
+
The below design is the default and recommended for all Unified CCE deployments on UCS C series servers. Exampled in Figures 10 and 11 are two possible network side implementations of the same vSphere Hypervisor vSwitch design. This design calls for using the VMware NIC Teaming (without load balancing) of vmnic interfaces in an Active/Standby configuration through alternate and redundant hardware paths to the network, thereby preventing any single point of failure from affecting the Visible or Private network communications.
-
*When you install ESXi 4.0, connect the VMKernel port for the ESX Management Network to the virtual switch that is connected to the public network.  
+
The network side implementation does not have to exactly match either of those illustrated below, but it must allow for redundancy and not allow for single points of failure affecting both Visible and Private network communications. There are more possible ways that this could be implemented in a supportable design than can be covered here.  
-
*During the ESXi 4.0 installation, be sure to enable the second Network Interface Card so you can use it to connect to the private network.
+
Requirements:
 +
* Ethernet interfaces must be Gigabit speed, and connected to Gigabit Ethernet switches. 10/100 Ethernet is not supported.
 +
* No single point of failure is allowed for visible and private networks.
 +
* Network switch infrastructure cannot use Cisco Stacking technology to combine all switches the UCS C series server is connected to into a single virtual switch.
 +
* Network switches must be configured properly for connection to VMware Hypervisor. Please refer to the below for details on ensuring proper switch configuration to prevent STP delay in failover/fallback scenarios.
 +
** http://kb.vmware.com/selfservice/search.do?cmd=displayKC&externalId=1003804
-
* You are required to configure the UCCE/ICM public and private networks for the ICM components on the C-210 servers the same as on the MCS servers.
+
<br>
-
* To configure the network for the VMs using the vSphere client, do the following:
+
'''Figure 9'''
-
** Create a virtual switch connected to a 1GB physical port on the server.
+
-
** Connect this physical port to the public network, and associate the virtual machine's network adapter to this virtual switch.  See [http://docwiki-dev.cisco.com/wiki/UCS_Network_Configuration_for_UCCE#Configuring_the_ESXi_Host_Network_for_the_Virtual_Machines Configuring the ESXi Host Network for the Virtual Machines] for instructions.
+
-
:You need to do the same for the private network as required by certain ICM components, such as the Router, Logger, and PGs.
+
Figure 9 illustrates how to configure the vSwitches and vmnic adapters on a C-Series server using the redundant Active/Standby vSwitch NIC Teaming design.  
-
* All the VMs on the ESXi host are connected to the public virtual switch, and to the private virtual switch as required by the ICM component.  In other words, all the VMs are sharing the same 1 GB physical Ethernet ports: one connected to the public network, and one connected to the private network.
+
Note: vmnic numbers in figure 9 do not match those illustrated in figures 10 and 11 below.  
-
Figure 9 illustrates how to configure the vSwitches and vmnic adapters on a C-Series server. Figure 10 illustrates a sample UCS C-Series server network configuration for UCCE components that require both Public and Private network connections.
+
[[Image:PaloVswitchConfig.JPG]]
-
'''Figure 9'''
+
<br>
 +
'''Figure 10 '''
-
[[Image:C-Series_Vswitch_Vnic_network.JPG]]
+
Figure 10 illustrates a sample UCS C-Series server network configuration for UCCE components that require both Public and Private network connections, and how that can work using the Active/Standby design with two network switches.  
-
'''Figure 10 '''
+
<br>
 +
 
 +
[[Image:UCS-C-3vSW-5L-2SW.jpg]]
 +
 
 +
<br>
 +
'''Figure 11 '''
 +
 
 +
Figure 11 illustrates a sample UCS C-Series server network configuration for UCCE components that require both Public and Private network connections, and how that can be deployed using the Active/Standby design with three network switches.
 +
 
 +
[[Image:UCS-C-3vSW-5L-3SW.jpg]]
 +
 
 +
<br>
-
[[Image:NetworkConfig C-Series.jpg]]
+
Note: The Management VLAN and design is not fully illustrated as we do not have specific requirements for it to be deployed in any specific manner other than separate from the Visible and Private vSwitch & network interfaces. Please refer to VMware for best practices in deploying vSphere VMKernel/management interfaces to network.
= Configuring the ESXi Host Network for the Virtual Machines =
= Configuring the ESXi Host Network for the Virtual Machines =
Line 198: Line 214:
-----
-----
-
Go to: [[Virtualization for Unified CCE]]
+
Back to [http://docwiki-dev.cisco.com/wiki/Unified_Contact_Center_Enterprise Unified Contact Center Enterprise main page]

Revision as of 21:33, 10 February 2012

Contents

UCCE on UCS B-Series Network Configuration

The following sections provide instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (UCCE) on UCS B-Series servers.

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 Unified CCE 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 will be connected to redundant Network Routers.

Please note that the B200 blade is configured with the Cisco UCS M71KR-Q QLogic network adapter that provides 10 Gigabit Ethernet and Fibre Channel connectivity for the server. However, when deploying Clustering Over the WAN with B-Series hardware, the Cisco UCS M81KR Virtual Interface Card is used instead of the Cisco UCS M71KR-Q.

UCS B-Series General Network Configuration for Unified CCE Deployment

Figure 1 illustrates UCS B-Series network configuration for Unified CCE deployment.

UCS Fabric Ethernet switching mode must be set to End-Host Mode. Switching Mode is not supported.

Redundant chassis is not required, but recommended.

Figure 1

PhysicalNetworkConnection.JPG

Unified CCE Public and Private Network Configuration (for deployments other than Clustering Over the WAN)

Figure 2 illustrates the Unified CCE Public and Private network connections set up in the UCS B-Series system.

Figure 2

LogicalNetworkConnection.JPG

Unified CCE Public and Private Network Configuration for Clustering Over the WAN

Figure 3 illustrates Unified CCE Public and Private network connections set up in the UCS B-Series system with split fabric (i.e., a deployment containing redundant interfaces for each network alternating Fabric side (A/B)) and Clustering Over the WAN deployments.

Figure 3

NetworkConfig B-Series.JPG

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.

http://www.cisco.com/en/US/products/ps10281/products_configuration_example09186a0080af7515.shtml

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. However, it provides the necessary information to configure a service profile for Unified CCE.

VLAN Configuration for Unified CCE Public and Private Traffic

The service profile must have the complete and correct VLANs configured for Unified CCE Public and Private traffic.

The following shows an example of the VLANs needed for a Unified CCE deployment.

  • One VLAN is needed for the Public Ethernet traffic
  • One VLAN is needed for the Private Ethernet traffic.

Public and Private Traffic Deployment

The following figure illustrates the VLANs needed on the SideA blade for most Unified CCE deployments. In these deployments, a similar VLAN configuration would be needed on the SideB blade.

Figure 4

VLANConfig.JPG

Public and Private Traffic for Split Fabric and Clustering Over the WAN Deployment

For split fabric and Clustering Over the WAN deployments, the Public and Private networks must be configured to use their own redundant interfaces, with redundant interfaces for each network alternating Fabric side (A/B). It is also best practice to configure separate redundant interfaces for the management networks. These interfaces will be used in configuration of the vSwitches for networks in the HyperVisor.

Note MAC addresses in UCS Manager for all vNICs, as the vNIC numbers do not map to same number vmnic in the HyperVisor.

Note that in order to provision more than two interfaces per blade, the M81KR “Palo” Cisco Converged Network Adapter (CNA) must be used. The M71KR is only capable of provisioning two interfaces and is limited to the configuration shown in Figure 4.

The figure below illustrates redundant interfaces for Public, Private and management networks (where two pairs of Public interfaces are shown due to the example configuration having the management network on the same VLAN).

Figure 5

VnicUCSConfig.JPG

vSAN

The service profile must have a vSAN configured for Unified CCE. 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.

Figure 6

VSANConfig.JPG

Configuring the VLAN on the Network Router

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 Unified CCE 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 Virtual Switch and vmnic Adapters

For deploying Cisco Unified CCE on UCS B-Series servers, configure the vSwitches and vmnic adapters as follows:

vSwitch and vmnic Adapter Configuration

In most deployments, you create one ESXi virtual switch and connect both VM virtual Ethernet adapters to the virtual switch, as shown in the following figure. See Configuring the ESXi Host Network for the Virtual Machines for instructions.

NOTE: The Nexus 1000 virtual switch is not supported as a VMware switch.

Figure 7

EXSiHostNetwork.JPG

vSwitch and vmnic Adapter Configuration for Split Fabric and Clustering Over the WAN Deployment

For split fabric and UCS Clustering Over the WAN deployments that use the M81KR Virtual Interface Card, create ESXi virtual switches and connect VM virtual Ethernet adapters as shown in the following figure.

Assign physical adapters (vmnics) to vSwitches by MAC address to ensure that the correct interfaces created by the UCS profile are being assigned. Make sure that the Public and Private networks use alternate Fabrics (A/B) on their Active vmnic.

Figure 8

PaloVswitchConfig.JPG

Unified CCE on UCS C-Series Network Configuration

The following section provides instructions on performing the network configuration needed to deploy Cisco Unified Contact Center Enterprise (Unified CCE) on UCS C-Series servers.

Network Requirements for UCS C Series Servers

The below design is the default and recommended for all Unified CCE deployments on UCS C series servers. Exampled in Figures 10 and 11 are two possible network side implementations of the same vSphere Hypervisor vSwitch design. This design calls for using the VMware NIC Teaming (without load balancing) of vmnic interfaces in an Active/Standby configuration through alternate and redundant hardware paths to the network, thereby preventing any single point of failure from affecting the Visible or Private network communications.

The network side implementation does not have to exactly match either of those illustrated below, but it must allow for redundancy and not allow for single points of failure affecting both Visible and Private network communications. There are more possible ways that this could be implemented in a supportable design than can be covered here.

Requirements:

  • Ethernet interfaces must be Gigabit speed, and connected to Gigabit Ethernet switches. 10/100 Ethernet is not supported.
  • No single point of failure is allowed for visible and private networks.
  • Network switch infrastructure cannot use Cisco Stacking technology to combine all switches the UCS C series server is connected to into a single virtual switch.
  • Network switches must be configured properly for connection to VMware Hypervisor. Please refer to the below for details on ensuring proper switch configuration to prevent STP delay in failover/fallback scenarios.


Figure 9

Figure 9 illustrates how to configure the vSwitches and vmnic adapters on a C-Series server using the redundant Active/Standby vSwitch NIC Teaming design.

Note: vmnic numbers in figure 9 do not match those illustrated in figures 10 and 11 below.

PaloVswitchConfig.JPG


Figure 10

Figure 10 illustrates a sample UCS C-Series server network configuration for UCCE components that require both Public and Private network connections, and how that can work using the Active/Standby design with two network switches.


UCS-C-3vSW-5L-2SW.jpg


Figure 11

Figure 11 illustrates a sample UCS C-Series server network configuration for UCCE components that require both Public and Private network connections, and how that can be deployed using the Active/Standby design with three network switches.

UCS-C-3vSW-5L-3SW.jpg


Note: The Management VLAN and design is not fully illustrated as we do not have specific requirements for it to be deployed in any specific manner other than separate from the Visible and Private vSwitch & network interfaces. Please refer to VMware for best practices in deploying vSphere VMKernel/management interfaces to network.

Configuring the ESXi Host Network for the Virtual Machines

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

  1. Login to the ESXi host using VMware Infrastructure Client
  2. Select the ESXi host
  3. Click on the Configuration tab
  4. Click on Hardware/Networking
  5. Click on Add Networking...
  6. Select Connection Types: Virtual Machine. Click Next.
  7. Select "Create a virtual switch" and select an associated VM NIC.
  8. Enter Port Group Properties/Network label: VM Network n, where n is an integer.(Example: "VM Network 1")
  9. Click on Finish.

To Associate a VM Network Adapter to Network Connection

  1. Edit virtual machine settings.
  2. Select the Network Adapter.
  3. Select a virtual switch from the Network Connection/network label. (Example: "VM Network 1")
  4. Click OK.

Back to Unified Contact Center Enterprise main page

Rating: 5.0/5 (11 votes cast)

Personal tools