Cisco Packaged Contact Center Enterprise Installation and Upgrade Guide, Release 10.5(1)
Network Design Considerations
Downloads: This chapterpdf (PDF - 1.86MB) The complete bookPDF (PDF - 4.67MB) | The complete bookePub (ePub - 1.09MB) | Feedback

Network Design Considerations

Network Design Considerations

This chapter provides guidance on performing the network configuration needed to deploy Packaged CCE on UCS servers. It includes information on fault tolerance and redundancy.

Network Requirements for Cisco UCS C-Series Servers

The illustration below shows the reference design for all Packaged CCE deployments on UCS C-series servers and the network implementation of the vSphere vSwitch design.

This design calls for using the VMware NIC Teaming (without load balancing) of virtual machine network interface controller (vmnic) interfaces in an Active/Standby configuration through alternate and redundant hardware paths to the network.

The network side implementation does not have to exactly match this illustration, but it must allow for redundancy and must not allow for single points of failure affecting both Visible and Private network communications.


Note


The customer also has the option, at their discretion, to configure VMware NIC Teaming on the Management vSwitch on the same or separate switch infrastructure in the data center.


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 to which the UCS C-Series server is connected into a single virtual switch.
  • Network switches must be configured properly for connection to VMware. Refer to the VMware Knowledge Base for details on ensuring proper switch configuration to prevent Spanning Tree Protocol (STP) delay in failover/fallback scenarios.

VMware vSwitch Design for Cisco UCS C-Series Servers

This figure illustrates a configuration for the vSwitches and vmnic adapters on a UCS C-Series server using the redundant Active/Standby vSwitch NIC Teaming design. The configuration is the same for the Side A server and the Side B server.

Data Center Switch Configuration for UCS C-Series Server Ethernet Uplinks

Reference and required design for UCS C-Series server Packaged CCE Visible and Private networks Ethernet uplinks uses the VMware default of IEEE 802.1Q (dot1q) trunking, which is referred to as the Virtual Switch VLAN Tagging (VST) mode. This design requires that specific settings be used on the uplink data center switch, as described in the example below.

Improper configuration of up-link ports can directly and negatively impact system performance, operation, and fault handling.


Note


All VLAN settings are given for example purposes. Customer VLANs may vary according to their specific network requirements.


Example: Virtual Switch VLAN Tagging

    C3750-A1

    interface GigabitEthernet1/0/1
      description PCCE_Visible_A_Active
      switchport trunk encapsulation dot1q
      switchport trunk allowed vlan 10
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk

    interface GigabitEthernet1/0/2
      description PCCE_Private_A_Standby
      switchport trunk encapsulation dot1q
       switchport trunk allowed vlan 100
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk

    C3750-A2

    interface GigabitEthernet1/0/1
      description PCCE_Visible_A_Standby
      switchport trunk encapsulation dot1q
      switchport trunk allowed vlan 10
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk

    interface GigabitEthernet1/0/2
      description PCCE_Private_A_Active
      switchport trunk encapsulation dot1q
       switchport trunk allowed vlan 100
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk


    C3750-B1

    interface GigabitEthernet1/0/1
      description PCCE_Visible_B_Active
      switchport trunk encapsulation dot1q
      switchport trunk allowed vlan 20
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk

    interface GigabitEthernet1/0/2
      description PCCE_Private_A_Standby
      switchport trunk encapsulation dot1q
       switchport trunk allowed vlan 200
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk

    C3750-B2

    interface GigabitEthernet1/0/1
      description PCCE_Visible_B_Standby
      switchport trunk encapsulation dot1q
      switchport trunk allowed vlan 20
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk

    interface GigabitEthernet1/0/2
      description PCCE_Private_B_Active
      switchport trunk encapsulation dot1q
       switchport trunk allowed vlan 200
      switchport mode trunk
      switchport nonegotiate
      spanning-tree portfast trunk 

Note


  • ESXi supports dotlq only.
  • DTP is not supported.

Network Requirements for Cisco UCS B-Series Servers

The illustration below shows the virtual to physical Packaged CCE communications path from application local OS NICs to the data center network switching infrastructure.

The reference design depicted uses a single virtual switch with two vmnics in Active/Active mode, with Visible and Private network path diversity aligned through the Fabric Interconnects using the Port Group vmnic override mechanism of the VMware vSwitch.



Alternate designs are allowed, such as those resembling that of UCS C-Series servers where each Port Group (VLAN) has its own vSwitch with two vmnics in Active/Stanby configuration. In all designs, path diversity of the Visible and Private networks must be maintained so that both networks do not fail in the event of a single path loss through the Fabric Interconnects.

VMware vSwitch Design for Cisco UCS B-Series Servers

The figures in this topic illustrate the two vmnic interfaces with Port Group override for the VMware vSwitch on a UCS B-Series server using an Active/Active vmnic teaming design. The configuration is the same for the Side A and Side B servers.

The following figure shows the Public network alignment (preferred path via override) to the vmnic0 interface.



The following figure shows the Private networks alignment to the vmnic1 interface.



When using Active/Active vmnic interfaces, Active/Stanby can be set per Port Group (VLAN) in the vSwitch Properties dialog in the vSphere Web Client, as shown:



Ensure that the Packaged CCE Visible and Private networks Active and Standby vmnics are alternated through Fabric Interconnects so that no single path failure will result in a failover of both network communication paths at one time. In order to check this, you may need to compare the MAC addresses of the vmnics in vSphere to the MAC addresses assigned to the blade in UCS Manager to determine the Fabric Interconnect to which each vmnic is aligned.

UCS B-Series servers may also be designed to have 6 or more vmnic interfaces with separate vSwitch Active/Standby pairs similar to the design used for UCS C-Series servers. This design still requires that active path for Visible and Private networks be alternated between the two Fabric Interconnects

Data Center Switch Configurations for Cisco UCS B-Series Fabric Interconnect Ethernet Uplink

This topic provides examples of data center switch uplink port configurations for connecting to UCS B-series Fabric Interconnects.

There are several supported designs for configuring Ethernet uplinks from UCS B-Series Fabric Interconnects to the data center switches for Packaged CCE. Virtual Switch VLAN Tagging is required, with EtherChannel / Link Aggregation Control Protocol (LACP) and Virtual PortChannel (vPC) being options depending on data center switch capabilities.

The required and reference design for Packaged CCE Visible and Private network uplinks from UCS Fabric Interconnects uses a Common-L2 design, where both Packaged CCE VLANs are trunked to a pair of data center switches. Customer also may choose to trunk other management (including VMware) and enterprise networks on these same links, or use a Disjoint-L2 model to separate these networks from Packaged CCE. Both designs are supported, though only the Common-L2 model is used here.


Note


All VLAN, vPC and PortChannel IDs and configuration settings are given for example purposes. Customer VLANs, IDs and any vPC timing and priority settings may vary according to their specific network requirements.


Improper configuration of up-link ports can directly and negatively impact system performance, operation, and fault handling.

Example 1: vPC Uplinks

In this example, UCS Fabric Interconnect Ethernet uplinks to a pair of Cisco Nexus 5500 series switches using LACP and vPC. UCS Fabric Interconnects require LACP where PortChannel uplinks are used, regardless of whether they are vPC.


Note


Cisco Catalyst 10G switches with VSS also may be used in a similar uplink topology with VSS (MEC) uplinks to the Fabric Interconnects. That IOS configuration is not described here, and differs from the configuration of NX-OS.




    N5KA

    cfs ipv4 distribute
    cfs eth distribute
    feature lacp
    feature vpc
    feature lldp

    vlan 1-10,100

    vpc domain 1
      role priority 1000
      system-priority 4000
      peer-keepalive destination 10.0.0.2
      delay restore 180
      peer-gateway
      auto-recovery

    interface port-channel1
      description vPC_to_FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk
      vpc 1

    interface port-channel2
      description vPC_to_FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk
      vpc 2

    interface port-channel100
      description vPC_Peer_Link
      switchport mode trunk
      spanning-tree port type network
      vpc peer-link

    interface Ethernet1/1
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 1 mode active

    interface Ethernet1/2
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 2 mode active

    interface Ethernet1/5
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface Ethernet1/6
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface mgmt0
      ip address 10.0.0.1/24

    no ip igmp snooping mrouter vpc-peer-link
    vpc bind-vrf default vlan 4048

    N5KB

    cfs ipv4 distribute
    cfs eth distribute
    feature lacp
    feature vpc
    feature lldp

    vlan 1-10,100

    vpc domain 1
      role priority 2000
      system-priority 4000
      peer-keepalive destination 10.0.0.1
      delay restore 180
      peer-gateway
      auto-recovery

    interface port-channel1
      description vPC_to_FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk
      vpc 1

    interface port-channel2
      description vPC_to_FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk
      vpc 2

    interface port-channel100
      description vPC_Peer_Link
      switchport mode trunk
      spanning-tree port type network
      vpc peer-link

    interface Ethernet1/1
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 1 mode active

    interface Ethernet1/2
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 2 mode active

    interface Ethernet1/5
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface Ethernet1/6
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface mgmt0
      ip address 10.0.0.2/24

    no ip igmp snooping mrouter vpc-peer-link
    vpc bind-vrf default vlan 4048

Note


Additional interfaces can be added to the vPCs (channel-groups) to increase the aggregate uplink bandwidth. These interfaces must be added symetrically on both Nexus 5500 switches.


Example 2: Standard Uplinks

In this example, a pair of Cisco Nexus 5500 series switches uplinked to the UCS Fabric Interconnects without PortChannels or vPC (the Nexus 5500 pair may still be vPC enabled).


Note


Cisco Catalyst switches capable of 10G Ethernet also may use a similar uplink topology. That IOS configuration is not described here, and may differ from NX-OS configuration.




    N5KA
    cfs ipv4 distribute
    cfs eth distribute
    feature lldp

    vlan 1-10,100

    interface port-channel100
      description L2-Interswitch-Trunk
      switchport mode trunk
      spanning-tree port type network

    interface Ethernet1/1
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface Ethernet1/2
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface Ethernet1/5
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface Ethernet1/6
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    N5KB
    cfs ipv4 distribute
    cfs eth distribute
    feature lldp

    vlan 1-10,100

    interface port-channel100
      description L2-Interswitch-Trunk
      switchport mode trunk
      spanning-tree port type network

    interface Ethernet1/1
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface Ethernet1/2
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface Ethernet1/5
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface Ethernet1/6
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

Example 3: EtherChannel Uplinks

In this example, a Nexus 5500 pair with non-vPC PortChannel (EtherChannel with LACP) uplinks to the UCS Fabric Interconnects.


Note


Cisco Catalyst switches capable of 10G Ethernet also may use a similar uplink topology. That IOS configuration is not described here, and may differ from NX-OS configuration.




    N5KA

    cfs ipv4 distribute
    cfs eth distribute
    feature lacp
    feature lldp

    vlan 1-10,100

    interface port-channel1
      description PC_to_FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface port-channel2
      description PC_to_FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface port-channel100
      description Interswitch_Peer_Link
      switchport mode trunk
      spanning-tree port type network

    interface Ethernet1/1
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 1 mode active

    interface Ethernet1/2
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 1 mode active

    interface Ethernet1/3
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 2 mode active

    interface Ethernet1/4
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 2 mode active

    interface Ethernet1/5
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface Ethernet1/6
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    N5KB

    cfs ipv4 distribute
    cfs eth distribute
    feature lacp
    feature lldp

    vlan 1-10,100

    interface port-channel1
      description PC_to_FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface port-channel2
      description vPC_to_FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      spanning-tree port type edge trunk

    interface port-channel100
      description PC_Peer_Link
      switchport mode trunk
      spanning-tree port type network

    interface Ethernet1/1
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 1 mode active

    interface Ethernet1/2
      description Uplink-To-FabricA
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 1 mode active

    interface Ethernet1/3
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 2 mode active

    interface Ethernet1/4
      description Uplink-To-FabricB
      switchport mode trunk
      switchport trunk allowed vlan 1-10,100
      channel-group 2 mode active

    interface Ethernet1/5
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

    interface Ethernet1/6
      description Interswitch_Link
      switchport mode trunk
      channel-group 100

Bandwidth Provisioning and Network QoS Considerations

Your Wide Area Network must support QoS. For details, refer to the Bandwidth Provisioning and QoS considerations section in the Cisco Unified Contact Center Enterprise Design Guide: http:/​/​www.cisco.com/​en/​US/​partner/​products/​sw/​custcosw/​ps1844/​products_​implementation_​design_​guides_​list.html.