Yesterday I posted about Cisco UCS supporting RDMA (SMB Direct) with firmware version 2.2(4b)B. Walter Dey, former Cisco Distinguished Engineer at Cisco informed me not only about the RDMA feature he also showed me that Cisco UCS now supports Consistent Device Naming which was introduced with Windows Server 2012. Consistent Device Naming (CDN) allows Ethernet interfaces to be named in a consistent manner. This makes Ethernet interface names more persistent when adapter or other configuration changes are made. To use CDN in Cisco UCS you need to run firmware version 2.2(4b)B. This will help to make it a lot easier to identify network interfaces used with Windows Server 2012 R2 and Hyper-V.
Tag: Cisco UCS
As you may know we use SMB as the storage protocol for several Hyper-V deployments using Scale-Out File Server and Storage Spaces which adds a lot value to your Hyper-V deployments. To boost performance Microsoft is using RDMA or SMB Direct to accelerate Storage network performance.
RDMA over Converged Ethernet (RoCE) allows direct memory access over an Ethernet network. RoCE is a link layer protocol, and hence, it allows communication between any two hosts in the same Ethernet broadcast domain. RoCE delivers superior performance compared to traditional network socket implementations because of lower latency, lower CPU utilization and higher utilization of network bandwidth. Windows Server 2012 and later versions use RDMA for accelerating and improving the performance of SMB file sharing traffic and Live Migration. If you need to know more about RDMA or SMB Direct checkout my blog post: Hyper-V over SMB: SMB Direct
With Cisco UCS Manager Release 2.2(4), Cisco finally supports RoCE for SMB Direct. It sends additional configuration information to the adapter while creating or modifying an Ethernet adapter policy.
Guidelines and Limitations for SMB Direct with RoCE
- SMB Direct with RoCE is supported only on Windows Server 2012 R2.
- SMB Direct with RoCE is supported only with Cisco UCS VIC 1340 and 1380 adapters.
- Cisco UCS Manager does not support more than 4 RoCE-enabled vNICs per adapter.
- Cisco UCS Manager does not support RoCE with NVGRE, VXLAN, NetFlow, VMQ, or usNIC.
- You can not use Windows Server NIC Teaming together with RMDA enabled adapters in Windows Server 2012 and Windows Server 2012 R2 or you will lose RDMA feature on these adapters.
- Maximum number of queue pairs per adapter is 8192.
- Maximum number of memory regions per adapter is 524288.
- If you do not disable RoCE before downgrading Cisco UCS Manager from Release 2.2(4), downgrade will fail.
Checkout my post about Hyper-V over SMB:
As I already mentioned I did several Hyper-V and Microsoft Windows Server projects with Cisco UCS. With Cisco UCS you can now configure stateless offloads for NVGRE traffic which is needed for Hyper-V Network Virtualization.
Cisco UCS Manager supports stateless offloads with NVGRE only with Cisco UCS VIC 1340 and/or Cisco UCS VIC 1380 adapters that are installed on servers running Windows Server 2012 R2 operating systems.
To use this you have to create Ethernet Adapter Policy, and set the Configuring an Ethernet Adapter Policy to Enable Stateless Offloads with NVGREin the Resources area:
- Transmit Queues = 1
- Receive Queues = n (up to 8)
- Completion Queues = # of Transmit Queues + # of Receive Queues
- Interrupts = # Completion Queues + 2
And in the Option area set the following settings:
- Network Virtualization using Generic Routing Encapsulation = Enabled
- Interrupt Mode = Msi-X
Make also sure you have installed eNIC driver Version 184.108.40.206 or later.
At the Worldwide Partner Conference 2014 Cisco and Microsoft announced a multi-year sales and go-to-market agreement designed to modernize data centers through the delivery and acceleration of integrated solutions. This will focus on bringing a deeper integration between the datacenter technologies of both companies. This includes Cisco UCS and Nexus products as well as Microsoft’s CloudOS solutions based Windows Server, Hyper-V, System Center, SQL Server and Microsoft Azure.
- Cisco and Microsoft agree to a three-year go-to-market plan focused on transforming data centers through the delivery of integrated solutions for enterprise customers and service providers.
- In year one, the companies will focus on six countries — the United States, Canada, UK, Germany, France, and Australia — with expansion to additional countries in the following years.
- Cisco and Microsoft will align partner incentive programs to accelerate solutions selling via mutual channel partners.
- Cisco and Microsoft sales teams will work together on cloud and data center opportunities, including an initial program focused on the migration of Windows 2003 customers to Windows 2012 R2 on the Cisco UCS platform.
- Integrated solutions will focus on private cloud, server migration, service provider, and SQL Server 2014
- Cisco technologies to include Cisco UCS, Cisco Nexus switching, Cisco UCS Manager with System Center integration modules, and Cisco PowerTool.
- Cisco-based integrated infrastructure solutions will include FlexPod with NetApp and Cisco Solutions for EMC VXPEX.
- Microsoft technology includes Windows Server 2012 R2, System Center 2012 R2, PowerShell, Microsoft Azure and SQL Server 2014
- Cisco Application Centric Infrastructure and Cisco InterCloud Fabric to be integrated in the solutions in future releases
Source and More information: www.streetinsider.com
As you may know I am a Microsoft MVP and a Cisco Champion and I really like doing project with Cisco Hardware since they do a lot of integration with the Microsoft Stack especially System Center and PowerShell. In my opinion this could be a strong partnership and will make life of a lot of people a lot easier.
I feel honored to be awarded by Cisco with the Cisco Champion title. Cisco does a lot of great products and I focused on the datacenter solutions which Cisco offers with their Cisco UCS platform and the Microsoft solutions, such as the System Center Integration and the Cisco UCS PowerShell Module.
Passionate Experts, Global Champions for Change
What makes a Cisco Champion? Passion, plus a desire to share their perspectives with the community. There are Cisco Champions all over the world. They represent a variety of segments across the IT industry. And they offer their time to help others learn about Cisco and connect with Cisco in unique ways.
In addition to sharing their insights and expertise, Cisco Champions make a difference by:
- Supporting their peers in social communities, forums, and networks
- Sharing their relevant experiences and thoughts on Cisco blogs
- Providing valuable feedback directly to Cisco
- And more
Cisco Champions have a unique opportunity to contribute to and enhance the way people use the latest technologies. They also receive:
- Recognition for their contributions
- Invitations to exclusive events
- Opportunities to directly communicate with Cisco employees
In the Microsoft world PowerShell is the tool to automate everything especially in your datacenter. I already mentioned that Cisco offers some great enhancements for the Microsoft Datacenter stack. If you are using a Cisco UCS solution you can integrate System Center Virtual Machine Manager, Orchestrator and others. But Cisco does also offer a PowerShell module for the UCS called Cisco UCS PowerTool. The UCS PowerTool allows you to automate management and deployment tasks very easily via Windows PowerShell. By the way, one of the coolest features in the Cisco UCS PowerTool is the ConvertTo-UCScmdlet.
Cisco announced the UCS Power Scripting Contest
Everyone is invited to share their scripts and possibly win some prizes by entering the UCS Power Scripting Contest on the Cisco Communities. The contest will run until May 11th. A distinguished panel of judges (Jeffery Snover, Rob Willis, Don Jones, Hal Rottenberg and Thomas Maurer) along with other members of the community will select the grand prize winner from a set of five finalists.
I am proud to be one of the Distinguished Judges for the UCS Power Scripting Contest and I hope we will see some great solutions. To get more information about the contest check out the Cisco Blog from Bill Shields and the UCS Power Scripting Contest website.
Cisco does a really great job on supporting different management software for their blade center. For example Cisco offers a System Center Virtual Machine Manager Add-in to manage your Cisco fabric directly from the SCVMM console, a System Center Orchestrator Integration Pack for automation and a System Center Operations Manager Management Pack for monitoring. But another great thing they offer is the PowerShell module for the Cisco UCS called Cisco UCS PowerTools, which allows you to manage and automate your Cisco Blade Center via Windows PowerShell. The Cisco PowerShell module offers round 1400 PowerShell cmdlets which allows you basically to do every task from the console.
To connect to your Cisco UCS system you can use the following cmdlet:
Connect-Ucs <ip or hostname>
and you can use other cmdlets to manage your Blades, VLANs or Service Profiles.
Get-Ucsblade Get-UcsServiceProfile Connect-UcsServiceProfile -ServiceProfile ServiceProfileName -Blade ServerID
You can get the Cisco UCS PowerTools from the Cisco Website.
Some days ago I posted an article how you can manage your Cisco UCS Blade Center directly from System Center Virtual machine Manager. Cisco also offers an Integration Pack for System Center Orchestrator which allows you to automate your Cisco UCS via Orchestrator Integration Packs, which is great if you are building your own Private Cloud based on Cisco hardware.
First step you have to download the Cisco UCS PowerTool (PowerShell Module) and the Cisco UCS Microsoft System Center Orchestrator Integration Pack.
After you have installed the Cisco UCS PowerTool on your System Center Orchestrator Runbook servers you now an import the Integration Pack via the System Center Orchestrator Deployment Manager. With a right click on Integration Packs you can Register the Cisco UCS IP.
After that you also have to deploy the IP to the Orchestrator Runbook servers.
You can start to create new Orchestrator Run Books with the Runbook Designer. First open the SCO Runbook Designer and in the Options menu select Cisco UCS to added the Path to the Cisco UCS PowerTool module (PowerShell module). The default path the Cisco UCS PowerTools are installed is: “C:\Program Files (x86)\Cisco\Cisco UCS PowerTool\Modules\CiscoUcsPS\CiscoUcsPS.psd1”
You can now start to automate your Cisco UCS with System Center Orchestrator.
If you are interested in how you monitor your Cisco UCS system with System Center Operations Manager Stefan Roth blogged about that.
Maybe you already know about the Cisco UCS Blade Center about I already blogged a lot especially about Microsoft Hyper-V and System Center integration. Today I had the change to integrate the Cisco UCS in many different System Center products such as Virtual Machine Manager, Operations Manager and Orchestrator. The Cisco UCS Manager Add-in for Microsoft System Center Virtual Machine Manager allows administrators to manage the physical and virtual infrastructure on a single pane of glass right from the Virtual Machine Manager console.
Key Features of Cisco UCSM Add-in 1.0.1:
- Mapping of the hypervisor host with UCS Manager managed server on which it is installed
- UCS domain registration and grouping
- Summary of both blades and rack servers in the UCS domain, including the firmware details.
- Fault Summary
- View of service profiles and service profile templates in the domain
- Associate and disassociate of service profiles.
- Modify power state
- Launch KVM console
- Clone a service profile or service profile template.
- Create service profile from template
The Cisco UCS Add-in for Virtual Machine Manager supports System Center 2012 SP1 and System Center 2012 R2.
How to install:
- First you have to download the Add-in from the Cisco Homepage.
- Open the Virtual Machine Manager console and navigate to settings and click on “Import Console Add-in”
Select the .ZIP file, the wizard will show a waring because the add-in is not signed by a trusted authority.
After that the Cisco UCS Manager logo will show up in the SCVMM console and you can now connect your UCS Domains.
And you can now start to manage your Cisco UCS blades directly from the System Center Virtual Machine Manager console.
And of course you have also KVM console support directly from the SCVMM console.
I already did a post how you can add the Cisco UCS drivers to a Windows Server 2008 R2 Hyper-V Image using dism and imagex. With Windows Server 2012 you cannot use the command line tool imagex anymore but you have a new Windows PowerShell module for dism which allows you basically the same with. In this tutorial I will add the Cisco UCS drivers to a Windows Server 2012 ISO image or a Microsoft Hyper-V Server Image.
First I created three new folders:
- Drivers – which includes all the extracted drivers for Windows Server 2012 (I removed all the drivers which are not related to Windows Server 2012)
- ISO – This includes the extracted Windows Server 2012 ISO image
- Mount – This is a empty folder which will be used to mount the WIM files
First we have to check in which Windows edition we want to add drivers. We can do this by using the Get-WindowsImage cmdlet:
Get-WindowsImage -ImagePath .\ISO\sources\install.wim
This will show you all the Images which are included in this WIM file.
After we have seen the Index numbers we can now mount the Windows Image our Mount folder. In my example I use Image Index 3 which is the Windows Server 2012 Datacenter Core Edition
Mount-WindowsImage -Path .\Mount -ImagePath .\ISO\sources\install.wim -Index 3
After the image is mounted we can now add the drivers from the Drivers folder.
Add-WindowsDriver -Path .\Mount -Driver .\Drivers -Recurse
When all drivers are added to the Image you can dismount the image and save it.
Dismount-WindowsImage -Path .\Mount -Save
We have now added the drivers to the Install image, you should also added the drivers to your boot image. To do this just do the same steps to the .\ISO\sources\boot.wim.
After that you can create a ISO file
oscdimg -n -m -bc:\temp\ISO\boot\etfsboot.com C:\temp\ISO C:\temp\mynew.iso