Software: PuTTY b0.61 is released
2011-07-12 PuTTY 0.61 is released:
PuTTY 0.61 is out, after over four years (sorry!), with new features, bug fixes, and compatibility updates for Windows 7 and various SSH server software.

Download: PuTTY
2011-07-12 PuTTY 0.61 is released:
PuTTY 0.61 is out, after over four years (sorry!), with new features, bug fixes, and compatibility updates for Windows 7 and various SSH server software.

Download: PuTTY
Oke.. I didn’t know this feature, last week a colleague consultant shows me a little menu to (re-)configure the ESX service console. With the command “console-setup” you can add or delete some vSwitches, create a new SC and view current configurations.
If you never worked with ESX CLI then will this a nice feature to setup/troubleshoot the SC.

The option “Console-setup” is available since ESX 4.0 update 2
Menu structure:
When you console-setup as root from the service console, you are presented with this menu:
1. Show Current Service Consoles
2. Show Network Adapters
3. Show vSwitch/vDS Information
4. Delete Service Console
4.1 Select the interface to delete, defaults to vswif0
5. Configure Service Console
5.1 vswif ID, default to vswif0
5.2 Name of service console port group: default to “Service Console”
5.3 vSwitch for service console, default to vSwitch0
5.4 IP Address:
5.5 Subnet mask:
5.6 Default gateway:
5.7 VLAN ID: default to 0
5.8 vmnic to use for the service console
5.9 Save Changes
5.10 Return to Menu
6. Exit
Use:
- Options 1,2 and 3 for display current information
- Option 4 to remove an existing service console interface (vswif). You may also do this, if you want to recreate it.
- Option 5 to change the configuration of an existing vswif interface, or for creating a new one.
More information: VMware
You can monitor/check your ESX performance with esxtop, by generating a share to your vCenter Server and view the results with Perfmon you can follow this article.
Create Credentials:
1. I created a new share on my vCenter 2003 on E:\Logging\
2. I created a new user with username: Logging and password: Logging
3. On the new created folder I add the Logging account with full permissions to the security rights:
After upgrading from VMware ESX 3.x to ESX 4.0 you can cleanup the bootloader from the older ESX 3.5 installation. You can do this from the console of by connection the host with ssh, give the command “cleanup-esx3”
Little note: You can run the cleanup-esx command as long as everything works for you in 4. If you use the -f flag, the software prompts you to confirm that you want to disable the ability to roll back to the ESX 3.x.x.
Thanks xchello from Dutch VMug for the tip!
Het is daarstraks niet gelukt om te upgraden van HP Management Agent versie 8.1 naar versie 8.2, had voorheen ook mijn oude installatie bestanden verwijdert.
Om de HP Management Agents te deinstalleren opnieuw de oude “hpmgmt-8.1.0-vmware3x.tgz” gedownload en uitgepakt met tar -zxvf hpmgmt-8.2.0-vmware3x.tgz
Uit de map: /var/tmp/update/hpmgmt/810/ het volgende commando uitgevoerd:
./installvm810.sh –uninstall
De agents worden nu juist gedeinsatlleerd:
De nieuwe installatie kan worden uitgevoerd.
Download: hpmgmt-8.2.0-vmware3x.tgz
Download URL: http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&cc=US&swItem=MTX-f7e5291b6fe84bdd95f996a7b1
Release notes:
Important:
./installvm820.sh –silent –inputfile hpmgmt.conf