How Is The Front Bumper Put On A 645

Despiste 10: Cambiar la IP de la Service Console

recently asked me to change an ESX 3.5 host our production VLAN to another VLAN. This change implies a change of IP addresses portgroups Service Console and the vmkernel. Initially, this task could be viewed as a simple task, to log into the ESX host and change the IP physically, but this change is more hidden implications that could lead to serious problems such as losing the HA or VMotion capabilities in the affected host.

Change Service Console IP is quite simple and the procedure looks like (based on the information based on this great post ):

List the port
1. actuales groups of service console: esxcfg-vswitch
-l This command will return it Configuración current vSwitch, something like:

Switch Name	a Ports Used Ports		Configured Ports MTU		Uplinks
vSwitch0		64 13 64		1500	vmnic0, vmnic2
	PortGroup Name VLAN ID Used Ports Uplinks VM Network 0 8 vmnic0,vmnic2 Service Console 0 1 vmnic0,vmnic2

Switch Name	Num Ports	Used Ports	Configured Ports	MTU	Uplinks
vSwitch0	64	13	64	1500	vmnic1,vmnic3
	VLAN ID Used Ports PortGroup Name uplinks VMkernel 0 1 vmnic1, vmnic3

so you can find the name of port group in your Service Console, in our example the one in bold. We seek
2. interfazvirtual port associated with that group, you have to have a name like vswif where n is the number of the interface virtual, and will be returned by the command esxcfg-vswif -l, plus all the IP settings associated with each virtual interface:

Name		Port Group IP Address		Netmask Broadcast Enabled		DHCP
vswif0	Service Console		xxx.xxx.xxx.xxx nnn.nnn.nnn.nnn	bbb.bbb.bbb.bbb		true false

3. Once we have located the virtual interface associated with our Service Console, the only way to change the IP settings is to delete the virtual interface and create a new interface virtual target range. The steps to perform the procedure are:
   
   
   
   1. Clear virtual interface: esxcfg-vswif -d vswif0
   2. Create a new virtual interface associates with our port of the service group called console Service console: esxcfg-vswif
      -a-p "Service Console" -i  <new IP Address>  -n  <netmask>  vswif0
4. También deberíamos modificar la puerta de enlace por defecto asociada con la interfaz virtual modificando  /etc/sysconfig/network-scripts/ifcfg-vswif0  y añadiendo GATEWAY=ggg.ggg.ggg.ggg  en el fichero.
5. Este paso es bastante importante si quieres ahorrarte un montón de dolores de cabeza. Modifica la entrada correspondiente en el fichero  /etc/hosts
6. At this point you have two options, reboot the ESX host and enable or disable vswif l interface. If you choose to disable and enable the interface vswif should do the following:
   
   
   
   • To disable the interface vswif: esxcfg-vswif -s vswif0
   • To enable vswif interface: esxcfg-vswif -e vswif0
   
   
   Once you have completed all these steps, just look for the ESX affected in VirtualCenter, Disconnect them and reconnect. This process will uninstall the agent vpxa isntalado the ESX host and reinstalled during the reconnection process .
   
   
   If after this you still tienendo connection problems / VMotion / HA checks the ESX host entry in the VirtualCenter database. Duncan Epping has a great post on Yellow-Bricks that record should be checked and changed http://www.yellow-bricks.com/2008/09/29/storage-vmotion-fails-after-service-console -ip-change /
   
   
   is time to change the IP address of the VMkernel. This change can be conducted via vClient, or can be made directly from the Service Console. Changing the IP address of the VMkernel through vClient is quite easy, so I will focus on how to make this change manually.
   
   
   As we saw with the method for changing the IP of the Service Console, this procedure depends on vmknic hit delete and create a new one.
   
   

1. Again, the recommended first step is to list all available vmknics your ESX host. This can be done using the command esxcfg-vmknic -l will produce output similar to this:

Interface	Port Group	IP Address	Netmask	Broadcast	MAC Address	MTU	TSO MSS	Enabled
vmk0	VMkernel	xxx.xxx.xxx.xxx	nnn.nnn.nnn.nnn	bbb.bbb.bbb.bbb	00:50:56:aa:bb:cc		1500 40960	true

2. Then let's clear the affected vmknic (which is bold in our example). We also need the associated port group: esxcfg-
vmknic-d-p VMkernel vmk0
3. Finally, we construct the desired configuration vmknic and associate with the correct port group. Remember that this procedure will generate a new MAC address:
esxcfg-vmknic VMkernel-a-p-i-n mmm.mmm.mmm.mmm vmk0 yyy.yyy.yyy.yyy

Note that these proceedings are valid only for Standard vSwitch, and the need for a slight modification to suit the Distributed vSwitch available on ESX 4. But that's another story.

I have based this post on my personal experience and information gathered from:

• http://vmwaretips.com/wp/2008/09/12/changing-service-console-ip-address-in-esx -35 /
• http://www.yellow-bricks.com/2008/09/29/storage-vmotion-fails-after-service-console-ip-change/
• http://www .yellow-bricks.com/2008/06/04/changing-the-ip-address-of-an-esx-host-and-ha /

I hope this post can help someone.

Fashionable Pharmacutical

Misleading 10: Changing Service Console IP address

Recently I've been asked for changing an ESX 3.5 host from one of our production VLAN to another VLAN. This change involve a change of IP addresses for Service Console and vmKernel portgroup. Initially, this task could be viewed as a simple task, just login in ESX host physically and change the IP, but this change has more hidden implications that could move on serious problems like losing HA o vMotion capabilities for the affected host.

Changing Service Console IP is quite simple and the procedure looks something like (based on information found in this great post ):

1. List current Service Console port groups:
esxcfg-vswitch -l this command will retrieve current vSwitches configuration, something like:

Switch Name	Num Ports	Used Ports	Configured Ports	MTU	Uplinks
vSwitch0	64	13	64	1500	vmnic0,vmnic2
	PortGroup Name VLAN ID Used Ports Uplinks VM Network 0 8 vmnic0,vmnic2 Service Console 0 1 vmnic0,vmnic2

Switch Name	Num Ports	Used Ports	Configured Ports	MTU	Uplinks
vSwitch0	64	13	64	1500	vmnic1,vmnic3
	PortGroup Name VLAN ID Used Ports Uplinks VMkernel 0 1 vmnic1,vmnic3

so you can look for your Service Console port group's name, in our example the bold one.
2. We are looking for the virtual interface associated with that PortGroup, witch will be named something like vswif<n> , where n is the instance number of virtual interface, and will be retrieved by the esxcfg-vswif -l , aside all IP configuration associated with each virtual interface:
   

Name	Port Group	IP Address	Netmask	Broadcast	Enabled	DHCP
vswif0	Service Console	xxx.xxx.xxx.xxx	nnn.nnn.nnn.nnn	bbb.bbb.bbb.bbb	true	false

3. Once we've located our Service Console's associated virtual interface the only way for changing IP configuration is delete that virtual interface and create a new virtual interface with the new desired parameters. Steps to perform that procedure are:
   
   
   
   1. Delete virtual interface with esxcfg-vswif -d vswif0
      
   2. Create new virtual interface and associate it with our service console port group called Service Console :
      esxcfg-vswif -a -p "Service Console" -i <new IP Address> -n <netmask>  vswif0
      
4. We also should modify the default gateway associated with the virtual interface modifying /etc/sysconfig/network-scripts/ifcfg-vswif0 and adding GATEWAY=ggg.ggg.ggg.ggg in the file.
   
5. This step it's quite important if you want to save a lot of headaches. Modify the corresponding in the /etc/hosts file
   
6. At this point you have two options, reboot the ESX host or disable and enable the vswif interface. If your choice was disabling and enabling the vswif interface you should perform the following procedure:
   
   
   
   • To disable a vswif interface: esxcfg-vswif -s vswif0
     
   • To enable a vswif interface: esxcfg-vswif -e vswif0
     
   
   

Once you have done all these steps, just find your affected ESX in your VirtualCenter, Disconnect it and Reconnect . This process will uninstall the vpxa agent installed on the ESX host and will reinstall it during the reconecting process .

If after all you still have connections/vMotion/HA problems check ESX host's entry in the VirtualCenter database. Duncan has a great post at Yellow-Bricks that explains what registry should be checked and modified:  http://www.yellow-bricks.com/2008/09/29/storage-vmotion-fails-after-service-console-ip-change/

Now it's time to change VMkernel IP address. This change can be done via vClient, or can be done directly from Service Console. Changing VMkernel IP address through vClient it's quite simple, so I'll focus on making this change manually.

As we saw with the method for change the Service Console IP, this procedure depends on deleting the affected vmknic and creating a new one.

1. Again, the first recommended step it's to list all vmknics available on your ESX host. That could be done using the esxcfg-vmknic -l command that will produce an output like this:
   

Interface	Port Group	IP Address	Netmask	Broadcast	MAC Address	MTU	TSO MSS	Enabled
vmk0	VMkernel	xxx.xxx.xxx.xxx	nnn.nnn.nnn.nnn	bbb.bbb.bbb.bbb	00:50:56:aa:bb:cc	1500	40960	true

2. Next, we are going to delete the affected vmknic (the bold one in our example). We'll also need the associated port group:
   
esxcfg-vmknic -d -p VMkernel vmk0
3. Finally, we create a new vmknic with the desired configuration and we associate it with the correct port group. Remember that this procedure will generate a new MAC Address:
   
esxcfg-vmknic -a -p VMkernel -i yyy.yyy.yyy.yyy -n mmm.mmm.mmm.mmm vmk0

Keep in mind that these procedures are valid only for Standard vSwitches, and it's necesary slight modification to adapt it to Distributed vSwitches availables in ESX 4. But that's another history.

I based this post in my personal experience and the information recollected from:

• http://vmwaretips.com/wp/2008/09/12/changing-service-console-ip-address-in-esx-35/
• http://www.yellow-bricks.com/2008/09/29/storage-vmotion-fails-after-service-console-ip-change/
• http://www.yellow-bricks.com/2008/06/04/changing-the-ip-address-of-an-esx-host-and-ha/

I hope this post could help somebody

Can Anybody Recommend A Good Camping Pillow

Winds of change

It's been a while since the last time I updated the blog, and after much thought about the topic I've decided the moment for the change has arrived. Two obvious options arise to me: abandon the blog or keep writing.

If I'm writing this post is because I've decided to bet on the blog once again, but I think that it needs a change of approach.  So I would like to start  with a  new line of work, making a real change of approach . First of those measures I'll take to achieve my purpose is write all my post in Both languages, Inglés and English. I'll translate all entries slowly Already posted. So I apologize for my must-Inglés, remove'm sure That it will make someone cry.