Tag: Bladecenter

Distinguished Judges for the UCS Power Scripting Contest

Cisco UCS PowerShell Scripting Contest

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.

Distinguished Judges for the UCS Power Scripting Contest

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 UCS Hyper-V Cluster – Configure Hyper-V Networks – Part 5

This How-To shows you how you configure the (Virtual) Network Adapters of the Hyper-V Servers. This is not really heavy, but to complete the UCS Hyper-V Guide I post this. If you use Microsoft System Center Virtual Machine Manager 2008 R2 you will find later a post about doing this in SCVMM 2008 R2.

  1. Connect to the Hyper-V Server with the Hyper-V Manager Console
    Hyper-V Manager
  2. Now you can configure the Networks under Virtual Network Manager on each Hyper-V Host.
    Hyper-V Virtual Network ManagerWhat we did is, we added 7 (Virtual) Network adapters to the UCS Bladenodes in the UCS Manager. We added the same on Configuration on the Blades which are using VMware ESXi and on the Blades with Microsoft Hyper-V and thats why we have a Network called vMotion on the Hyper-V Servers. We use the vMotion network adpater for the private Failover Cluster Heartbeat.

Basically we have the following Networks:

UCS Blade Server Networks

  • 1. Network adapter is the Hyper-V Management Network dedicated to the Hyper-V Node
  • 2. Network adpater for Hyper-V Cluster Live Migration
  • 3. Network adapter for private Failover Cluster Heartbeat
  • 4. Network adapter External Network, is used for our main external Network
  • 5. Network adapter Internal Network, is used for our internal Management Network for Servers
  • 6. and 7. Network adapters are used for VLAN Trunks

To get the best performance we don’t share any Network Adapter with the Hyper-V Host and a Virtual Network.



Cisco UCS and Microsoft Hyper-V R2

Last week we run our first tests with the Cisco UCS Bladecenter, VMware ESXi and Microsoft Hyper-V R2.

I am really excited about the performance and the easy management of the Cisco Bladecenter. Maybe I get some more information about Hyper-V and the UCS out there for next week.

There is also a Microsoft TechNet event next Tuesday:

Cisco Unified Computing System + Microsoft Hyper-V/System Center = die Komplettlösung für Virtual IT und Private Cloud