Don’t get stuck in the IT past

Watch what happens when you try to buy a cloud solution from the wrong company.

Microsoft pokes fun at VMware with “VMlimited man“.

Enable SSH on ESXi 5 via vSphere Client

In the first post I wrote how you can enable SSH on the ESXi 5.0 host. In this post I show you how you can enable or activate SSH on the ESXi 5.0 hosts via the vSphere Client.

  1. First start the vSphere Client
  2. Select the ESXi host in the configurations tab
  3. Select Security Profile
    Enable SSH on ESXi 5.0 vis vSphere Client
  4. Click on Properties in the upper right corner and you will get the a popup with all the services on this ESXi 5.0 hosts. Select the SSH service and press the Options button.
    Enable SSH on ESXi 5.0 vis vSphere Client
  5. Now you can start the services and set the startup options
    Enable SSH on ESXi 5.0 vis vSphere Client
  6. press okay and you are done..

Activate SSH on VMware ESXi 5.0

As in VMware ESXi 4.1 you can enable or activate SSH on VMware ESXi 5.0 very simple. VMware ESXi 5.0 is also known as VMware vSphere Hypervisor.

  1. On the start screen press F2 for “Customize System”
    VMware ESXi 5.0 enable SSH
  2. Login with the local password
    VMware ESXi 5.0 enable SSH
  3. Select and enter Troubleshooting Options
    VMware ESXi 5.0 enable SSH
  4. Click on Enable SSH to activate SSH on your VMware ESXi 5.0 host
    VMware ESXi 5.0 enable SSH
  5. After you have pressed the ENTER key you will now see that SSH is enabled
    VMware ESXi 5.0 activate SSH

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

Activate SSH on ESXi 4.1 via vSphere Client

Some months ago I wrote a post about how to activate SSH on a ESXi 4.1 via console. But you can also activate SSH with the vSphere Client.

  1. Login to the vSphere Client
  2. Click on the configuration tab
    VMware vSphere Client ESXi
  3. Click on Security profile
  4. VMware vSphere Client ESXi Click on Properties
    VMware vSphere Client ESXi
  5. Click on Remote Tech Support (SSH)
    VMware vSphere Client ESXi
  6. Click on Options and choose the startup policy and click start
    VMware vSphere Client ESXi
  7. Now you can verify that the daemon shows as running in the Services Properties window