Server Virtualization (aka hardware virtualization) is the most common application being used for Hardware’s virtualization where hypervisor software enables creating a virtual machine (VM) that emulates a physical computer by creating different OS environment that is logically separated from the hosting system. A single physical system/hardware can be used to create several VMs that can run different OSs independently and at the same time.
Cisco’s Hardware for Data center systems virtualization (Unified Computing system UCS ) can provide a very scalable, simplified and manageable functionalities with market biggest memory support with Cisco Extended Memory Technology.
Although Cisco UCS is a scalable, manageable and simplifying operations rather than make it harder such as adding or moving servers, installing new VMs ..etc within minutes only, but the actual Design of Cisco UCS system requires some knowledge/expertise in different areas such as systems virtualization using VMware, Storage (SAN) and L2 and L3 Networking. This article will focus on the networking part from high level point of view describing methods and mechanisms to setup and design of the virtualized network connectivity with the physical network world and compare different approaches and methodologies using Cisco UCS and Nexus 1000v Switch. In this article there will be no deep dive in any of the discussed areas, but a link of each discussed concept will be provided that can be referred to for more details and technical understanding which will help to direct the designer to the right direction first before going deep into the details.
Designing and building a virtual switching LAN within the virtualized environment such as VMware has some similarities to the physical switching but there are some technical differences in the operations and the used terminologies:
By using independent vswitch per ESXi host VMs connected to the same vSwitch that reside in the same ESXi host does not need a physical switch to forward the traffic between them however because communications between two vswitch not supported a physical switch is required to forward the traffic between VMs on different vSwtich even if they are on the same ESXi host by using external physical switch, also a physical NIC is required to be defined as a uplink to that vswitch and used for sending traffic out to the physical switch to other vswitchs or for inter-VLAN routing for example.
Now the question that arise what are the technical differences between the vSwitch and the physical switch :
With VMWare virtual distributed switch the switching fabric reside virtually across multiple VMware ESXi hosts , and this feature enable VMs to migrate smoothly from one VMware Vsphere server to other, also the vDS provide centralized management via its integration with VMware Vcenter.
Cisco has developed the first third party vDS switch that works with VMWare virtual infrastructure. The Cisco Nexus 1000v series switch to some extent provides same features, managment and functionalities to network Admins they used to have with physical switches but the switch now delivered as a software rather than hardware
There is a new Cisco Nexus 1010v delivered in appliance, but the actual vSwitch concept is still the same software and the hardware just for offloading the control plane processing form the VI servers
Nexus 1000v (aka N1K) has several features that are currently only supported by N1Kv such as:
As mentioned earlier there will be no deep dive in any specific topic but only high level discussion of the concepts. Understanding the architecture of Nexus 1000v is crucial in the design of virtualized network environment with Cisco UCS and VMware, now what are the component of Nexus 1000v ? and how the overall architecture of this software looks like in a virtualized environment ?
To answer these questions we need first to understand what are the components of the N1K:
VSM: Virtual Supervisor Module
Just like a blade switch supervisor module such as Cisco 6500 where the supervisor module is the brain of the switch doing control plane, management functions and integration with VMware Vcenter
VEM: Virtual Ethernet Module
And this is like the Ethernet module of the physical switch but the difference here is in each ESXi host there will be a VEM that communicate and controlled by the VSM , VEM replaces the ESXi Vswitch, provide each VM with a dedicated port
With physical switch there is a backplane cross bar normally used for communications between the modules within this virtualized switching there is no backplane crossbar but it uses same backplane protocol in N7K and MDS switches called AIPC which is used for communications between the VEM and VSM these communications can be done either in:
The most commonly used approach is the L2 connectivity where three type of VLANs have to be created Management, Control and data VLANs:
Earlier in this document several concepts and methodologies of virtualized switching and networking have been described with more focus on Cisco Nexus 1000v vDS switch. Before we discuss how this virtual network world can connect to the physical Data center Network world we need to understand in a high level what Cisco unified computing system UCS can offer to this virtualized environment from networking point of view as this document focus on the network part only.
Cisco UCS offer many features, functions and capabilities that boost the virtualized infrastructures deployments and make it more scalable and manageable from the physical layer ( power and cabling with the unified I/O ) up to the application layer UCSM and Layer 8 user experience
For more information about Cisco UCS please refer to the bellow link:
In a high level cisco UCS component are as shown below:
For more details see the bellow link
The bellow figure shows a typical Physical connectivity of Cisco UCS platform:
Although this physical connectivity look standard but based on the NIC card used in the UCS platform the vNetwrking logical connectivity will be different in conjunction with Cisco N1K vDS as a virtualized switch . Cisco UCS offer different type of NIC that can be used and each has different capabilities which can be selected based on the network design requirements:
Optimized for virtualization, up to 58 dynamic, programmable Ethernet and Fibre Channel interfaces, Hardware- and/or software-enabled Cisco VN-Link capability
How the M81KR virtualized adapter integrates with rest of the UCS system and what are its benefits
Total of 4 fixed interfaces 2 Ethernet and 2 Fibre Channel, Software-enabled Cisco VN-Link capability
Ideal for efficient, high-performance Ethernet, Total of 2 fixed Ethernet interfaces, Software-enabled Cisco VN-Link capability
The bellow figure shows the logical architecture of the cisco virtualized interface VIC:
as mentioned above using different NIC can lead to different vNetorking approach in general there are two main approaches forwarding/siwthcing in hardware or in software where the hardware one must utilize the Cisco VIC to provide virtual NICs (vNICs) per VM
the bellow figure is taken from Cisco Live 2011 ( end to end Data Center virtulization ) which describe and summarise the whole concept:
As shown in the figure above the VN-link in hardware can provide better performance and management as the management will be via the UCSM and vCenter as the VSM will not be part of the solution and that mean any aggregation or NIC teaming has to managed and aligned between VMware Vcenter and UCSM
While the software vn-link is just uses the entire concpets of VSM with VEM described earler in this document and al of the Networking configurations and Admin is done via N1K VMS CLI including the pining and links aggregation.
For more details please see the bellow links:
Best Practices in Deploying Cisco Nexus 1000V Series Switches on Cisco UCS B and C Series Cisco UCS Manager Servers
Cisco Nexus 1000V Series Switches Deployment Guide
As described above if the N1K going to be used with VSM for vNetwokring ( vNetwiorking in software ) the all of the configurations of the uplinks, link aggregation and pining have to be done using VSM CLI. Just like any physical access switch the design and configurations are dependant on the aggregation layer switchs and how these switches have been designed such as aggregated/clustered with some sort of virtualizations concepts such as vPC or VSS as this will affect the way of designing N1K uplinks
There are different way that N1K VEM can connect to the upstream switches:
by using mac-pining with links sub-groups VMs can be pined automatically on the VM boot up to a formed subgroup if link failure occur repining and failover to the other Woking links will happen automatically this approach is useful when the upstream switches are not clustered using vPC or VSS for example
Static pining provide the ability to select specific VMs/traffic type to use Specific uplinks selectively, for example vMotion can be enforced to use a specific uplink and this design still preserve the concept of active/standby during failover situations
LACP is control mechanism of port-channelling that used in link aggregations and it provide the ability of bundling and utilization more than uplink for more traffic and high availability and better failover/convergence time this method is recommended when the upstream switches are aggregated/clustered using vPC or VSS
LACP is a control plane protocol that runs on the supervisor of a switch ( VSM in N1K )
In the case VSM is disconnected or down the VEM will be operating in a headless mode without the ability to utilise the control plane LACP function
LACP Offload solved this problem by offloading the operation of the LACP protocol from the VSM to the VEMs
Cisco Nexus1000V Release Notes, Release 4.2(1) SV1(4):
With the modern and converged networks and Data centers that carry many real time sensitive data such as voice and video in conjunction with some business critical applications that require some bandwidth grantee QoS become a very important component that need to be considered when designing any networking solution not to mention cisco UCS uses fiber channel over Ethernet which require the FCoE to be prioritized and lossless and using Cisoc Unified communications on UCS ( aka UC on UCS ) make QoS more important and deterministic element in the Data Center Design.
Cisco UCS uses Data Center Ethernet (DCE) to handle all traffic inside a Cisco UCS system. System classes determine how the DCE bandwidth in these virtual lanes is allocated within UCS. Cisco UCS uses only L2 COS and these values range from 0 to 7 (where 0 is the lowest value and 6 is highest value). COS 7 is reserved for internal traffic
QoS in UCS can be differ in the way that it can be designed with regard to the network design approach and NIC used in the UCS system ( QoS requirements has to be aligned with the above section of Network connectivity )
For example using the virtualized NIC vNIC has several benefits such as ability to have multiple virtual interfaces and each interface assigned to different QoS policy that being allocated a COS value and treated differently within the UCS system based on the QoS requirements, so we can have up 8 queues in theory but normally there is one queue/COS reserved for FCoE ( by default COS 3 ) and other one used for management, and the reset can be allocated as per the design requirements.
However this design approach is not always the best, for example UC on UCS better work with the use of Nexus 1000v QoS capabilities to mark the traffic on the VM port for L3 DSCP value mapping to L2 COS value as the UCS dose not map L3 DSCP to L2 COS and Cisco UC applications mark the traffic ( signalling and media with DSCP only ), cisco N1K here will be working just like any L2 access switch and can perform the L3 DSCP mapping to L2 COS and UCS can priorities traffic based on this COS value and pre-configured policies
QoS Design Considerations for Virtual UC with UCS
Best Practices in Deploying Cisco Nexus 1000V Series Switches on Cisco UCS B and C Series Cisco UCS Manager Servers
Cisco Live 2011, Deployment of VN-Link with the Nexus 1000v.
Cisco Live 2011, End-to-End Data Centre Virtualisation.
Lowe S., Mastering VMware vSphere 4 Sep 2009.
Thanks and Regards,