Tuesday, June 2, 2009

Installing Perl Modules on W2K3 Server x64 without Internet access

Installing Perl Modules on W2K3 Server x64 without Internet access
 
ActiveState have a 64-bit build of perl - so I would think the first thing for you to do is to download and install it (if you haven't already) - http://downloads.activestate.com/ActivePerl/Windows/5.8/ActivePerl-5.8.8.822-MSWin32-x64-280952.zip. (Just run the 'Installer.bat' that's part of that download - or there's also an MSI version you can grab, if you prefer.) Then install (from Microsoft) "Microsoft Platform SDK for Windows Server 2003 R2". That should hopefully give you the compiler and nmake to work with that 64-bit build of perl. (It all works fine for me on my AMD64 box with Vista Business 64). To set up the environment to use that compiler just run C:\your_path_to\Platform_SDK\SetEnv.cmd /XP64 /RETAIL You should then be able to build most modules from CPAN source in the usual way.





Windows Live™: Keep your life in sync. Check it out!

Friday, May 22, 2009

VMware ESX Server 3 VirtualCenter Server & Update Manager

VirtualCenter Server & Update Manager
 
vpxd
This is the process name of the Windows service that is the core service running on the VirtualCenter management server.
If there are problems with the VirtualCenter service starting and then stopping almost immediately or a few seconds later, then check your ODBC database string and then the health of the the database server. We have seen this when the database runs out of disk space; check if the log space is full on the DB server, many clients forget about regular backup of this database. When troubleshooting the VirtualCenter service you can try VirtualCenter in stand-alone mode. This is done by invoking the following command at the Windows command line
vpxd -s
You will get interactive logging of the start-up activity helping you to pinpoint where the problem is.
If all else fails, you can always re-initialize the VirtualCenter database, however we would not recommend this. By re-initializing the VirtualCenter database you are wiping out all VC data!! If you do want this, then use the -b command switch to vpxd.
 
vpxd.cfg
This is the VirtualCenter management server configuration file. (Ok, so we are extending this command line guide to cover the VirtualCenter server now as well as the ESX host!)
There are a number of configuration changes to VirtualCenter we can make in this file, but as of VC 2.5, one such change you may wish to make is the disabling of "Guided Consolidation". This feature, shown just as a consolidation button in the VI client, is intended to help small customers select which physical Windows hosts are suitable for consolidation and then guide them to perform the physical to virtual migration.
If you have already been through the consolidation process, then you don't need this feature. It makes sense to disable the feature if you are not using it as this should improve VC performance. To disable Guided Consolidation, simply edit the vpxd.cfg file on the VC management server and make the following change:
config.vcp2v.dontStartConsolidation = true
 
vum-proxyAuthCfg.exe
The Update Manager component of Virtual Infrastructure is new to version 2.5. This component allows the patch management of Windows & Linux guests as well as ESX hosts. When installing the Update Manager component, the Windows installer package prompts the operator if they wish to use a proxy server to connect to the Internet, the only options are proxy IP address and port. If your proxy server requires authentication, then this tool must be run to supply the proxy server credentials.
 
vci-integrity.xml
This is the primary configuration file for the Update Manager.
One of the main reasons you may want to edit this file is if you wish to change the directory that patches are downloaded into, i.e. the patchstore.
 
vmware-umds.exe
This is the VMware Update Manager Download Service. If you don't want the server where Update Manager is installed on to actually connect to the Internet and do the patch downloading, then UMDS is for you. Maybe you don't want the load of update downloads on the UM server or maybe the UM server is on a subnet that can't reach the Internet. Anyway, the UMDS installs on a Windows server (that is not the same server as UM) and doesn't create a start menu program group.
To start a download, simply enter the command
vmware-umds --download
Once the updates are downloaded, we can export them. This means we copy the patches from the download directory to another path. The intended purpose of exporting is to copy all or a subset of the downloaded patches to a location that will then be made available to the Update Manager server.
vmware-umds -E e:\exportedupdates
At this time UMDS does not support NFS/CIFS shares for the export operation. This is related to a permissions issue
 
vmware-updateDownloadCli.exe
This tool is run on the Update Manager server to import the patches made available from the UMDS export. So if you had a DVD burned which had all the updates that was inserted to the UM server and available as drive Z:



Invite your mail contacts to join your friends list with Windows Live Spaces. It's easy! Try it!

VMware ESX Server 3 VMware HA

VMware HA
 
AAM
AAM is the Automated Availability Manager that runs in the service console when you create a VMware High Availability (VMware HA) cluster. The VMware HA feature was previously known as DAS (Distributed Availability Services) but we don't mention that anymore.
This software maintains an in-memory database on active nodes in the cluster and uses heartbeats to co-ordinate the active and passive nodes. It is suggested that you configure service console with 2 Ethernet interfaces to remove any single point of failure.
This is a piece of licensed Legato software which itself has been renamed to EMC AutoStart.
This component has a very high dependency upon fully functional host name resolution. So before you enable VMware HA, check the following files
/etc/hosts
/etc/FT_HOSTS
/etc/resolv.conf
/etc/vmware/esx.conf
to ensure accuracy. One thing you can do to check the name resolution functionality before enabling HA is run
hostname -s
to return the short name of the service console. If this fails, then the HA configuration WILL fail.
The log file for VMware HA in ESX 3.0.x can be found in the service console in the directory
/opt/LGTOaam512/
and for ESX 3.5 can be found in
/opt/VMware/
To avoid split brain scenarios, an ESX server can determine if it has become isolated from other servers and we can configure that servers' isolation response. If the AAM component loses contact with the other nodes in the HA cluster, it attempts to contact the configured default gateway for service console using ICMP echo request (PING). If this fails, then the ESX host is isolated. If your default gateway suppresses ICMP echo requests, then we can configure an alternate IP address called the das.isolationaddress. From ESX 3.5, you can configure multiple isolation addresses so that you can configure a host with more that one address to attempt contact with before declaring itself isolated.
 
/opt/LGTOaam512/bin/ftcli
This utility allows you to view the active nodes in an HA cluster and the managed IP addresses. This utility will help you determine whether the HA agent is in a running state and which IP addresses are visible between those managed hosts.
 
/etc/FT_HOSTS
This file is created when HA is enabled and is a copy of /etc/hosts. If you have problems with name resolution and configuring HA, you can safely delete this file and reconfigure that cluster node for HA again. FT_HOSTS will be re-created.


See all the ways you can stay connected to friends and family