Okay dude, for those who already familiar with vcbMC-1.0.6 beta, here another new release (vcbMC-1.0.7-Lite) from me. Frankly, I lost vcbMC-1.0.6 Beta source code and here I am start from the scratch again for vcbMC Lite. Though perhaps vSphere didn’t need VCB anymore, I believe most of you out there still relying on vcb to backup your virtual machines. BTW, this tool only do manual backup for your ESX 3.5 virtual machines. It’s really easy to use though no manual, but you can always press “help” button for guidence.

• Tool : vcbMC-1.0.7 Lite
• Description : vcb GUI for ESX virtual machine manual backup operation
• Tested : Win2k3 32 Bit / WinXP (old .ocx may need to be replaced during installation)
• Download : here

 

p/s: Still working on another version which can do schedule backup job like vcbMC-1.0.6.

No comments

After long waiting for my first experience with ESX 4/vSphere, finally today is the day for me to know more & get familiar with vSphere. Once my collegue finished with vSphere installation, we concluded that with :

• Hardware Blade BL460c G6, SAS drive & 6GB HDD
• Installation time duration = 25-30 minutes

Then I created a VM acting as nfs server, vmkernel and mount ESX 4 to that nfs server and within a minute I got nfs datastore mounted on my ESX 4. Ohh yea, I noticed without enable nfs client, ESX 4 still can mount to nfs server. . What else, one more, vSphere Client installation take approximately 20-30 minutes to be finished and I suspect it’s all down to .NET Framework 3.x. Last but not least, wow VMware replaced their license file (.lic) format with license key.

ariyossss

No comments

This post is password protected. To view it please enter your password below:

Password:

Enter your password to view comments

For my record :

Task : Change Service Console IP addresss for ESX02 / sp-vm02

Server info:

• SC ip = 168.xxx.1.12
• Netmask = 255.255.255.0
• Gateway = 168.xxx.1.3
• fqdn = bla bla bla

Virtual Switch

• vSwitch0 = vmnic4, vmnic0, vm network & service console
• vSwitch1 = vmnic2, vmnic1, NetworkA
• vSwitch2 = vmnic5, vmnic3, NetworkB
• vSwitch3 = isolated network

$esxcfg-vswif -i 168.180.1.13 -n 255.255.255.0 vswif0

edit /etc/hosts (no need for esx 3.5 cause it’s auto correct)

edit /etc/sysconfig/network to change gateway & hostname

$service network restart

$esxcfg-vswitch -L

$esxcfg-vswitch –unlink=vmnic4 vswitch0

$esxcfg-vswitch –link=vmnic5 vswitch0

Problem solved!

No comments

Last week downtime on MSA2000i (controller device error) caused all my customer VMs running on ESX build 64607 down & disconnected and from MSA logs, we found that 2 errors which is PSU under voltage & FRU device error and MSA did tried to reboot the system but failed. We also found that the controller totally not functional, no light indicate it’s running on the LED. HP simply want us to update to the latest patch J210P012 which we schedule to do it this morning. Hopefully the problem will run away with this patch otherwise high I/O could cause iSCSI connection interruption as what rumors said will haunt me back! Read more

No comments

At last, I able to make my firefox 2.0.0 on Linpus linux working with virtual machines console on ESX webaccess. It’s quite frustrating actually when I failed to make it work on Slackware & Ubuntu previously. However, this time it’s really working after I managed to resolved the dependency on this Linpus running on Acer Aspire One.

First problem is to install firefox’s plug-in called “vmware-mks-xpi”. Firefox unabled to install it
automatically when you click the “install” button. I need to donwload the file directly from ESX server by using “wget” command as below :

$wget https://192.168.1.20/ui/plugin/mozilla/linux/vmware-mks.xpi –no-check-certificate

Once finished, rename the file to “vmware-mks.zip” and then, unzip the file to “./mozilla/firefox/plugins” folder.

Second problem was Firefox complaint something about “remote MKS” after you reload your firefox. That wasn’t difficult actually to find why. Just go to “.mozilla/firefox/plugins/” then run “./viewer” and you’ll get an error message “error while loading shared libraries: libexpat.so.0: cannot open shared object file: No such file or directory”

Just install “compat-epxat1″ with this command :
$sudo yum install compat-expat1

Now you should be able to use your virtual machine console via ESX webaccess without problem.

p/s : somehow I failed to install compat-expat1 via proxy but no problem with direct connection to internet.

ariyossss
athlon_crazy 03062009

No comments