Sometimes we have the need to change the MAC address in a virtual machine, usually when we want to keep the MAC that we had on a physical computer or for reasons of applications that control it (license servers..). In this document we will see how to force a MAC address on a VM since VMware will allow us only the next range: 00:50:56:00:00:00 – 00:50:56:3F:FF:FF.
In this document, we'll look at the VMware virtual appliance called VMware Management Assistance (VMware vMA), is based on a CentOS distribution 5.2 with vCLI, CIM, Java JRE, vSphere SDK for Perl and vSphere SDK for Java, is a script-based management appliance for our virtual environment.. VMware vMA is a great utility to replace the Service Console and be able to manage our ESXi or vCenter hosts more easily and centrally through scripts/tasks, We can configure it as a log server, Backup, ESX distribution via PXE…
One of the new features brought by the new version of VMware vSphere 4.1 is that we will be able to validate against a domain when authenticating against an ESX or ESXi host with Active Directory accounts, We can put in’ in domain to hosts to control access or permissions. It is very simple to set up as well as recommended,
An essential feature that we should always leave configured when working with gigabit networks is to modify the MTU value (Maximum Transfer Unit – Maximum Transfer Unit) What is the size (in bytes) of the largest data unit you can send with IP, by default, LAN networks use an MTU of 1500 bytes. On VMware and all devices that make up the gigabit ethernet network (typically the iSCSI storage network) its value must be raised to 9000 bytes, We should enable it in the storage cabin, on the switch (Some switches have it enabled by default), on VMware ESX hosts / VMware ESXi (vSwitch & Port Group) and at the NIC level on equipment that is directly connected. All this in order to take advantage of the gigabit network and be able to send larger packets.
In this post we are going to fingerprint between esxi servers 4.1 to build trust between them and not rely on a validation request. With all this we can make ssh connections between them without being stopped asking for credentials.
This upgrade process will be the most used among those of us who have VMware vSphere environments with ESX hosts 4.0 and we want to upgrade them to ESX 4.1, since we will do it in an orderly and managed way through Update Manager, This document shows the steps we will need to update our hosts to the latest version.
Algo típico de estos días es ir actualizando nuestros entornos virtuales a la versión 4.1 los que tengan VMware ESXi 4.0 y quieran migrarlos a VMware ESXi 4.1, en este documento vemos cómo actualizar los host que tengamos descentralizados de una forma rápida pero manual, lo realizaremos mediante VMware vSphere CLI (Command-Line Interface) y bajándonos el fichero a que nos permitirá dicha actualización.
If we intend to upgrade our VMware ESX hosts 4.0 or VMware ESXi 4.0 to the new version of vSphere 4.1 manually, This is, without using VMware Update Manager we can do it in a simple way. We will only have to download a couple of files, copy them to the host and apply them to update the computer, Previously we will have shut down all the virtual machines that the host runs or we have moved them to other computers and put the computer in maintenance mode.
ghettoVCB.sh is one of the few good scripts I know that can help us make copies of our VMware environment for free, This is, we will be able to make backups on both ESX and ESXi servers without a license! We can say that it behaves the same as the traditional VCB, Takes a snapshot of the virtual machine to be copied, It copies the virtual machine's files to a directory and then deletes the snapshot. ghettoVCB is a script that must be run on the VMware ESX server itself(i), we can schedule it to run using 'Cron’ or as in my case I will run it from a remote computer using the utility plink.exe. In addition, ghettoVCB stores backups in an ESX datastore(i), In this document we will see at the end how to make the backup in a Windows folder that we have thanks to NFS.
From the version 4.1 VMware vSphere, In both VMware ESX and ESXi there is a way to enable the host access mode called Tech Support Mode, We can enable access to the local console from the host itself (Local Tech Support) or enable remote access with SSH (Remote Tech Support), In addition, the good thing is that we can enable SSH access remotely from the VMware client itself.
Do Tailor-made training
Windows Server – VMware vSphere – Citrix Virtual Apps & Desktops – Centreon
|
We are a consulting firm that cares and pampers
|
 |
|
With quality and added value
|
 |
|
¡Let's work together!
|
 |
