Tagged: vmware

ESX ports

Well as most exams like you to memorise numbers I thought I’d put together this list of ports that are used within ESX, all of the ports here can be found in the firewall config in the Security Profile Configuration page on the host/virtual center.

Incoming connections

CIM Secure Server 5989 TCP

Outgoing

Licence Server 27000 27010 TCP

CIM SLP 427 UDP TCP Incoming and outgoing

AAM 2050-2250,8042-8045 Incoming and outgoing

Virtual Center Agent 902 UDP

Iscsi Client 3260 TCP

NTP Client 123 UDP

SSH 22 TCP Incoming and outgoing

VCB 443,902 TCP

Alot of these ports I’m sure you’ve all seen before its just really the vmware specific ports that you need to concerntrate on as I’m sure like most other exams I’ve taken they will want to test you on them.

VMware DPS

Right so im back from my course and I must say it was very worth while. One of the things that really perked my interest was DPS (Distributed Power Service). Which basically means that once you have Distributed Resource Scheduing configured correctly you can enable DPS and it will VMotion machines around based on load and put un-needed hosts into standby.

They Showed us this video to demonstrate it and its fantastic. Not only can you save all those pennies turning off all your old tin when you virtualize the OS but you can also save mony during non peak load times too.

Vmware plans

So i laid in bed last night thinking about how to visualize Esx and came up with a rough idea of what i might try. First the spare serves i have will get windows xp Mo it. After that i will install Vmware server Mo it and try sticking Esx on that also with openfiler for Iscsi access. Hopefully that will give of something to work with and them i can stick virtual center on a laptop or similar. If that gets of anywhere then ilk do a big blog on it.

Virtualizing linux boxes

I’m going to talk briefly about virtualizing live linux servers. At work i’ve just virtualized my first red hat box. Was it painless? No. Was it informative? Yes.
l was given the task of p2v’ing the box after a disk in its mirror failed. So with a good bit of googling i came upon this tutorial on how to virtualize the box. It was not quite complete for me and I had to figure out various error messages I encountered along the way but I eventually managed it and with shaking hands clicked the vm’s power on button.

I must admit I was expecting a good number of errors when it started (and would not have been surprised by a kernal panic), but it booted into kudzu hardware manager uninstalling all the old bits and installing the new and too my relief completed its boot without any further issues.

Some of the issues that I came across along the way is doing the conversion in this way creates a VM for you and it firstly mounts a VM convertor helper ISO into the VM. This helper VM requires an IP address etc so you need to either let it DHCP for an address or Statically assign one during the convetor wizard screen.

Also as it needs to be contactable on the network you need to ensure that the VM is set up so that the network card(s) are on your production network. So if any of you normally put the cards into an isolated lan then this wont work. Also I’m not sure if this is to do with our setup or convertor “feature” I found I had to have the machine running the convertor client connecting to the convertor server on the linux box in the same subnet.

Trouble is now I’ve done one I expect I’ll be labelled with the “Linux Virtualization Expert” badge at work and will be given lots of other jobs that wont be quite so smooth! Ah well its all about the learning curve isnt it.