• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Yellow Bricks

by Duncan Epping

  • Home
  • Unexplored Territory Podcast
  • HA Deepdive
  • ESXTOP
  • Stickers/Shirts
  • Privacy Policy
  • About
  • Show Search
Hide Search

VirtualCenter

VirtualCenter 2.5 Update 3 and HA networks

Duncan Epping · Oct 4, 2008 ·

I wrote about a new patch for ESX(i) 3.5 yesterday and the fact that VirtualCenter 3.5 Update 3 was mentioned. Well today VirtualCenter 2.5 Update 3 has been released! You can pick it up here.

I think the most important fixes are the ones for HA. With Update 2 VM started checking the subnets of the heartbeat network for HA. If these weren’t compatible than HA bailed out. With Update 3 a new advanced option has been introduced ,”das.bypassNetworkVerification”. When this setting is set to “true” the Network compatibility check isn’t done and thus it’s possible to have an incompatible but routable HA heartbeat network.

Another important one is that as of U3 it’s possible again to delete HA advanced options, this problem was introduced in U2 and has been fixed.

An error that was also much talked about on the VMTN forum was the fact that VM’s weren’t vmotioned when maintenance mode was entered even if the admision control was disabled. This error has also been fixed.

These are three most important fixes in U3 in my opinion. Be sure to update and read the release notes for more info and fixes. Please not that the plugins for Update Manager and Converter has also been updated.

Update: Quick Migration

Duncan Epping · Oct 3, 2008 ·

A couple of days ago I wrote about the Quick Migration script that Mike D wrote with Powershell. Like I said, it should be possible to integrate the script with VC. Well this has been done by Dennis of Icomasoft. Icomasoft recently released the Powershell Plugin for VirtualCenter. And with this plugin you can easily integrate your scripts into VirtualCenter which makes it even more easy to run your scripts. You can find the altered script here, it includes a nice progress bar…

Thanks Thomas, for pointing me out! And great work by Dennis!

Bluebear’s Kodiak, what’s all the fuss about…

Duncan Epping · Sep 30, 2008 ·

Kodiak is a cross platform application(Windows, Linux, Mac) with which you can manage your virtual environment. Why would one want to use this instead of the VIC? Well you can run it from your Linux box without having to run a VM. What do you need? Well I tested it with Ubuntu and Windows and you should start with installing Adobe Air. For Windows it’s pretty straighton, but I couldn’t even find a download link for Ubuntu. After a couple of seconds on Google I found this Howto. It gave me a link and provided me with the info needed to install, although chmod and running the executable is pretty straight forward.

After the installation there was still the AIR package left to install that Bluebear provided. So I started Adobe Air, pointed towards the air package and that’s about it. It installed within a few minutes and I was ready to go.

So I wanted to do some extensive testing with Bluebear’s Kodiak and started out with Windows. Well after a couple of minutes all the “certificate” related messages started to irritate me so I quit with the Windows version and went straight on to Ubuntu. Luckily Ubuntu gave me the option to select “Always” when the same certificate message was dropped. (There’s a workaround for the certificate problem by the way, check this article)

So the next screen was sort of an inventory, the ESX host with it’s vSwitch and the VM attached to it. Reminds me a lot of the VMware maps functionality. But the cool thing about the map is that you can drag, drop and rotate in 3D. So as you can see in the screen below there’s a VM running…

So now what, what can we do with Kodiak? Well to be honest, not that much at this moment. Power Off and Power On a VM works fine, but that’s about it for now. I can’t edit any config settings, I can’t do vmotion, I can’t add or remove a VM, I can open a console to the VM but there’s no response or whatsoever. The interface looks cool, but like Carlo said in his article, what will it look like when you’ve got over a dozen VM’s. The arcs around the VM represent the current CPU / MEM resource usage by the way. I opened up a couple more windows and this is what it looked like:

Is this tool worth checking out? I do think so, there’s not much you can do with it at this point but it’s got a nice “look and feel” that seems to be promissing for the future. Let’s hope these guys can incorporate some new functionality a.s.a.p. I think it will be really useful for the SMB’s out there that do not have a VirtualCenter server but do have more than 1 ESX(i) host. And the Linux/Mac users, although with the new VMware Workstation it’s possible to run the VirtualCenter client as a seamless app.

So for the bluebear people reading this, I would like to be able to edit VM config’s for starters and a couple of power on / power off / restart buttons at the top of the console would be handy.

Release notes:
Manual Installation for Windows
Download and install Adobe Air for Windows if you don’t already have it on your computer
Download the Kodiak Air Package
Locate the downloaded Air file and run it, the Air installer should automatically begin
Release Notes
Kodiak Beta 0.0.1 Release Notes:

Thanks for downloading Kodiak! Kodiak is beta software, and no functionality is guaranteed, and is all subject to change.

We’ve really only validated functionality on Mac platforms. Our testing on Windows & Linux has been limited, but we haven’t encountered any problems. Your mileage may vary.

We’re completely interested in your feedback.

Here’s a quick idea of Kodiak usage, subject to change.

By default, Kodiak will open to a login screen. Enter your server address, your username/password, and off you go.

Kodiak will come up to a network map display, with a small server tab on the left-hand side of the screen. Double-clicking this tab will expand it into a list where you can view your VMs/Virtual switches/Resource Pools/Datastores, and for VMs, you’ll be able to power a VM on/off, and get to a console.

We added (today) a console dock on the right hand side where you can dock your consoles.

Kodiak’s map (in the background) is completely interactive, and will display resource usage information that’s updated on the fly. Click it, drag it, select it, poke it, launch consoles from it!

To use the map: Left click will select an individual VM. Left click + drag selects a group of VMs/hosts/networks Right Click + drag will pan the map around. Right Click + shift + drag will rotate the map in 3D.

To connect to a new server with kodiak, click the top-level “Connections” button that you see up in the upper-left hand corner, then click the “new” button you see there.

This will bring you to a new login screen. (FYI, Kodiak will keep track of your server names so you don’t have to type them in all the time.) Log in, and Kodiak will return your server into a new tab.

Currently, Kodiak WILL connect to a Virtual Center server, but we cannot guarantee that it will find all available hosts/VMs/resources.

If anyone wants an invite to the beta program than just drop your email here, or send me your email on duncan[@]yellow-bricks.com and I will hook you up. It’s still limited so be quick!

I’m all out. So you guys should help each other… over 60 invites within 24 hours. Bluebear is hot!

Bluebear’s Kodiak!

Duncan Epping · Sep 30, 2008 ·

I just received my beta invite for Bluebear’s Kodiak and will be testing it today. I am downloading a brand new Ubuntu 8.0.4 virtual appliance and will keep you guys up to date on this multi platform VirtualCenter management client.

If anyone wants an invite to the beta program than just drop your email here, or send me your email on duncan[@]yellow-bricks.com and I will hook you up. It’s still limited so be quick!

I’m all out. So you guys should help each other… over 60 invites within 24 hours. Bluebear is hot!

Storage VMotion fails after Service Console IP change

Duncan Epping · Sep 29, 2008 ·

As some of you know I spend a lot of time on the VMTN forums, helping people out and learning from other experts. Today someone posted about Storage VMotion not working after a Service Console IP change. It reminded me of a problem I faced a while ago. The solution wasn’t obvious but fairly easy, because the problem was solved with a slightly different approach I wrote it down:

Disconnect the ESX host from VirtualCenter
Stop the VMware VirtualCenter Server service
Remove the /etc/opt/vmware/vpxa/vpxa.cfg file from the ESX host that’s affected
Run this script on the database:
———–
UPDATE [VCDB].[dbo].[VPX_HOST]
SET [IP_ADDRESS] = ‘w.x.y.z’
WHERE [DNS_NAME] = ‘name of esx host as it is listed in the table’
———–
“w.x.y.z” above is the new ip address
Start the VMware VirtualCenter Server service
Add the host to the cluster again

Thanks goes out to BigRolTide for pointing me out to this solution. (In my case updating the database wasn’t necessarry)

Update: http://kb.vmware.com/kb/1006768

  • « Go to Previous Page
  • Page 1
  • Interim pages omitted …
  • Page 5
  • Page 6
  • Page 7
  • Page 8
  • Page 9
  • Interim pages omitted …
  • Page 16
  • Go to Next Page »

Primary Sidebar

About the Author

Duncan Epping is a Chief Technologist and Distinguished Engineering Architect at Broadcom. Besides writing on Yellow-Bricks, Duncan is the co-author of the vSAN Deep Dive and the vSphere Clustering Deep Dive book series. Duncan is also the host of the Unexplored Territory Podcast.

Follow Us

  • X
  • Spotify
  • RSS Feed
  • LinkedIn

Recommended Book(s)

Advertisements




Copyright Yellow-Bricks.com © 2025 · Log in