En el caso de necesitar instalar una actualización del aplicativo de gestión Dell Open Manage Server Administrator en un servidor VMware ESXi seguir el procedimiento descrotp en la siguiente web:
http://www.cogenesis.com.au/blog/installing-the-esxi-vib-dell-for-vsphere-client
Mostrando entradas con la etiqueta ESXI. Mostrar todas las entradas
Mostrando entradas con la etiqueta ESXI. Mostrar todas las entradas
lunes, 7 de marzo de 2016
jueves, 29 de noviembre de 2012
Como: Instalar Owncloud en Ubuntu 12 LTS desde 0
# Una vez instalado ubuntu en vmware.
# Apagar Ubuntu
sudo shutdown -h now
# Instalar vmware tools
# Quitar easy install mediante los siguientes comandos
# Restore the /etc/issue file:
sudo mv /etc/issue.backup /etc/issue
# Restore the /etc/rc.local file:
sudo mv /etc/rc.local.backup /etc/rc.local
##################################################
# Boton derecho sobre el server "Install VMware tools"
# Comprobar si ha cargado correctamente el cd
ls /mnt/cdrom
tar xzvf /mnt/cdrom/vmaretools-5.5.3.tar.gz -C /tmp/
cd /tmp/vmware-tools-distrib/
sudo ./vmware-install.pl -d
##################################################a
# Configurar el teclado en castellano
dpkg-reconfigure keyboard-configuration
##################################################a
# Instalar nano
sudo apt-get install nano
##################################################
# Asignar una IP fija
sudo nano /etc/network/interfaces
# Por la configuración TCP/IP que queramos. Por ejemplo:
auto eth0
iface eth0 inet static
address 192.168.1.100
netmask 255.255.255.0
network 192.168.1.0
broadcast 192.168.1.255
gateway 192.168.1.1
dns-nameservers 80.58.61.250
dns-nameservers 80.58.61.254
# Grabamos los cambios y finalmente solo queda reiniciar el interfaz de red.
sudo ifdown eth0 && sudo ifup eth0
##################################################
# Activar ssh
sudo apt-get install openssh-server
##################################################
# Actualizar Ubuntu
apt-get update
apt-get upgrade
# Descargar apps necesarias para su funcionamiento
apt-get install apache2 php5 php5-json php5-gd php5-sqlite curl libcurl3 libcurl3-dev php5-curl php5-common php-xml-parser
apt-get install sqlite
# Descargar owncloud y descomprimir
wget http://mirrors.owncloud.org/releases/owncloud-4.5.3.tar.bz2
tar -xjf owncloud-4.5.3.tar.bz2
sudo cp -r owncloud /var/www
# Añadir permisos al usuario por defecto de apache en www
chown -R www-data:www-data /var/www
service apache2 restart
# Acceder mediante navegador a la IP fija
http://192.168.1.100/owncloud
##################################################
Como : Apagar una VM ESXi mediante comandos
1. Paso : Conexion al host mediante ssh
2. Paso : Listar las maquinas instladas en el mismo y recordar el numero
de la que queremos encender/apagar.
~ # vim-cmd /vmsvc/getallvms
3. Paso : Encender la maquina con VMnumber n
# vim-cmd /vmsvc/power.on 32
4. Paso : Apagar la maquina con VMnumber n
# vim-cmd /vmsvc/power.shutdown VMnumber
5. Paso : En caso de no poder apagar correctamente la maquina mediante el anterio comando
podemos usar el siguiente
# vim-cmd /vmsvc/power.off VMnumber
2. Paso : Listar las maquinas instladas en el mismo y recordar el numero
de la que queremos encender/apagar.
~ # vim-cmd /vmsvc/getallvms
3. Paso : Encender la maquina con VMnumber n
# vim-cmd /vmsvc/power.on 32
4. Paso : Apagar la maquina con VMnumber n
# vim-cmd /vmsvc/power.shutdown VMnumber
5. Paso : En caso de no poder apagar correctamente la maquina mediante el anterio comando
podemos usar el siguiente
# vim-cmd /vmsvc/power.off VMnumber
lunes, 8 de octubre de 2012
Como renombrar disco virtual mediante comandos
1. Paso : Acceder mediante ssh
2. Paso : Cambiarte al directorio en cuestion:
cd /vmfs/volumes/datastore
Cuando nos movamos a la carpeta en cuestión esta queda sustituida por un churro.
cd virtualmachinedirectory
3. Paso : Ejecutar el siguiente comando.
vmkfstools -E NombreAntiguo.vmdk NombreNuevo.vmdk
2. Paso : Cambiarte al directorio en cuestion:
cd /vmfs/volumes/datastore
cd virtualmachinedirectory
3. Paso : Ejecutar el siguiente comando.
vmkfstools -E NombreAntiguo.vmdk NombreNuevo.vmdk
viernes, 28 de septiembre de 2012
Como actualizar ESXi 5.0 Update 1 mediante vib
El update 1 de ESXi 5.0 conlleva una limitacion en el autoarranque de las maquinas virtuales , para ello deberemos de aplicar el siguente parche.
1. Paso : Iniciar sesion en http://www.vmware.com
2. Paso : Ir a la url https://www.vmware.com/support/pubs/sdk_pubs.html
3. Paso : Descarga de vSphere 5.0 Update 1 SDK
for Perl y descagar el parche en formato vib
4. Paso : Instalar el mismo en una maquina cliente
5. Paso : Activar en el ESXi acceso a shell remoto desde Service
properties - remote access
6. Paso : Parar las
vm
7. Paso : Poner el server en modo
mantenimiento.
8. Paso : En el equipo cliente lanzar una consola de MSDOS
9. Paso : Cambiar de directorio a C:\Program Files
(x86)\VMware\VMware vSphere CLI\bin\
10. Paso : Copiar el archivo vib a un directorio temporal (por ejemplo "parches").
11. Paso : Listar disponibles.
esxcli --server=IPdestino --username=root software sources vib list --depot=/vmfs/volumes/Datastore/Parches/ESXi500-201207001.zip | more
10. Paso : Instalar desde el zip.
esxcli --server=IPdestino --username=root software vib update
--depot=/vmfs/volumes/Datastore/Parches/ESXi500-201207001.zip
11. Paso : Reiniciar la maquina y arrancar las vm.
domingo, 26 de agosto de 2012
Como mover maquinas virtuales de un ESXi a otro ESXI
Basicamente tenemos que tener los dos Esxi en el mismo rango , tener paradas las maquinas virtuales en el origen y utilizar el cliente "VMware vsphere client " para realizar el proceso sin tener que pagar una licencia de vmotion.
This process will require that, at least temporary, the “source” ESXi server has access to some storage that will be used by the “destination” ESXi server. In my case, I use a NFS shared Datastore that is visible from both ESXi ; I expect a VMFS on FC or iSCSI to work as well.
As seen previously, you can’t migrate a “living” Virtual Machine ; it has to be paused or shutdown before it can be moved. This is quite expectable as there would be no reasons to pay for vMotion if it could be done by some other way…
What has to be know while dealing with ESXi migration is that, although we’re using virtual hardware, a running Virtual Machine has some kind of adherence to the physical CPU it is running on. In my case, I moved the VMs from a physical ESXi to a virtual one and the paused Virtual Machines couldn’t be restarted in their paused state. You can probably face the same problem if migrating between ESXi that have not the exact same CPU (and CPU features). The error I got was “Your virtual machine did not resume because of a correctable error”. I choose the “Delete” option and the VM started as if I had been savagely powered down. So my advice is to properly shutdown the Virtual Machine before migrating it from one ESXi server to another.
The migration process is then really simple ; at least as simple as seen in the previous section. We’ll assume that the Virtual Machine is already located in some shared space.:
– Connect to the “source” ESXi server using the vSphere client ;
– Execute “Shut Down Guest” on the Virtual Machine to be moved ;
– Right-click on the Virtual Machine object and select “Remove from Inventory” ;
– Connect to the “destination” ESXi server using the vSphere client ;
– Open the shared Datastore browser ;
– Browse to the location where the VM files are and select the VMX file ;
– Right-click the object and select the “Add to Inventory” action ;
– Follow the wizard to attach the Virtual Machine to the “destination” ESXi server ;
You can now start the Virtual Machine.
As seen previously, you’ll get a warning message telling you that “The Virtual Machine might have been moved or copied”.
If you’re a lucky Administrator, the Virtual Machine should now be up and running from the “destination” ESXi server. Note that it only takes a few seconds to migrate a Virtual Machine from one ESXi to another (since the VMs is powerred off).
This process will require that, at least temporary, the “source” ESXi server has access to some storage that will be used by the “destination” ESXi server. In my case, I use a NFS shared Datastore that is visible from both ESXi ; I expect a VMFS on FC or iSCSI to work as well.
As seen previously, you can’t migrate a “living” Virtual Machine ; it has to be paused or shutdown before it can be moved. This is quite expectable as there would be no reasons to pay for vMotion if it could be done by some other way…
What has to be know while dealing with ESXi migration is that, although we’re using virtual hardware, a running Virtual Machine has some kind of adherence to the physical CPU it is running on. In my case, I moved the VMs from a physical ESXi to a virtual one and the paused Virtual Machines couldn’t be restarted in their paused state. You can probably face the same problem if migrating between ESXi that have not the exact same CPU (and CPU features). The error I got was “Your virtual machine did not resume because of a correctable error”. I choose the “Delete” option and the VM started as if I had been savagely powered down. So my advice is to properly shutdown the Virtual Machine before migrating it from one ESXi server to another.
The migration process is then really simple ; at least as simple as seen in the previous section. We’ll assume that the Virtual Machine is already located in some shared space.:
– Connect to the “source” ESXi server using the vSphere client ;
– Execute “Shut Down Guest” on the Virtual Machine to be moved ;
– Right-click on the Virtual Machine object and select “Remove from Inventory” ;
– Connect to the “destination” ESXi server using the vSphere client ;
– Open the shared Datastore browser ;
– Browse to the location where the VM files are and select the VMX file ;
– Right-click the object and select the “Add to Inventory” action ;
– Follow the wizard to attach the Virtual Machine to the “destination” ESXi server ;
You can now start the Virtual Machine.
As seen previously, you’ll get a warning message telling you that “The Virtual Machine might have been moved or copied”.
If you’re a lucky Administrator, the Virtual Machine should now be up and running from the “destination” ESXi server. Note that it only takes a few seconds to migrate a Virtual Machine from one ESXi to another (since the VMs is powerred off).
miércoles, 15 de agosto de 2012
Como redimensionar particiones en ESXI
Excelente articulo de como realizar una redimension de discos en VMware y su aplicacion practica en entornos windows.
URL : http://www.petenetlive.com/KB/Article/0000381.htm
URL : http://www.petenetlive.com/KB/Article/0000381.htm
Suscribirse a:
Entradas (Atom)


