Default Reasoning

Construction of sensible guesses when some useful information is lacking and no contradictory evidence is present…

  • Subscribe

  • Disclaimer

    This blog is personal. The views and opinions expressed here represent my own and not those of the people, institutions or organizations that I may or may not be related with unless stated explicitly. All blog post, white papers and manuals were written during the projects, mostly at a customer site and are scenario specific. Use at your own risk.
  • Meta

Archive for the ‘ESX 4’ Category

Monitor VMkernel activity with the tail command.

Posted by Marek.Z on 18 June 2010

The tail command displays last 10 lines of a file and with the –f (follow) parameter you can see the data appended to it. So, if you want to see what is going on in the vmkernel of your ESX host:

  1. Login to you ESX host
  2. Type: #tail –f /var/log/vmkernel
  3. Watch for new events to appear
  4. If you want to terminate the process,  press CTRL + C

Nice & simple :)

Cheers!

- Marek.Z

Posted in ESX 3.5, ESX 4, Uncategorized, VMware | Leave a Comment »

Configure Jumbo Frames on Hardware iSCSI HBA in ESX 4.

Posted by Marek.Z on 24 March 2010

Before you begin, check the names of the vmhba adapters on your ESX server. From the vSphere Client go to Configuration tab and click on Storage Adapters. Now, to set Jumbo Frame support (MTU 9000) on your hardware iSCSI HBA, follow these steps: 

  1. Login as Root user on your ESX server.
  2. Type: #esxcfg-hwiscsi –j enable <vmhba#>
  3. If successful, you should get the “MTU size successfully set to : 9000” message.
  4. To verify the change type: #esxcfg-hwiscsi –l  <vmhba#>

All done! 

 Cheers! 

- Marek.Z

Posted in ESX 4, VMware, vSphere | 1 Comment »

Kill an unresponsive VM on an ESX server.

Posted by Marek.Z on 11 February 2010

If you want to kill an unresponsive VM on an ESX server and it cannot be turned off with the vmware-cmd stop hard command then try the following: 

  1. Logon the ESX server as Root and type: #vm-support –x to find the VMID of the unresponsive VM.
  2. Next, type: #vm-support –X <VMID> to kill the VM. Answer the questions as desired and wait until the ESX server finishes the job. 

Cheers! 

- Marek.Z

Posted in ESX 3.5, ESX 4, VMware | 1 Comment »

Configure software iSCSI networking from the CLI.

Posted by Marek.Z on 25 November 2009

Follow these steps to configure software iSCSI networking on an ESX server. In this case I’ll be creating a new vSwitch, new Port Group on the new vSwitch and I’ll add the VMkernel port to the vSwitch. This setup will support the Jumbo Frames (MTU 9000). After that I’ll add an iSCSI target to the iSCSI software adapter and rescan the adapter for new targets. 

  1. Login as Root user on your ESX server.
  2. List the vSwitches with #esxcfg-vswitch -l and check the next available switch name. In this case I’ll be using vSwitch2.
  3. Create a new vSwitch: #esxcfg-vswitch -a vSwitch2
  4. Set the MTU to 9000: #esxcfg-vswitch vSwitch2 -m 9000
  5. List available NIC’s that can be used with the new vSwitch: #esxcfg-nics -l. In this case I’ll use vmnic4 and vmnic5.
  6. Add the vmnic4 to the new vSwitch: #esxcfg-vswitch vSwitch2 -L vmnic4
  7. Add the vmnic5 to the new vSwitch: #esxcfg-vswitch vSwitch2 -L vmnic5
  8. Add a Port Group to the new vSwitch: #esxcfg-vswitch vSwitch2 -A “VMkernel iSCSI”
  9. Add the VMkernel port to the new Port Group: #esxcfg-vmknic -a -i <IP address>-n <Network Mask> -m 9000 “VMkernel iSCSI”
  10. Enable the software iSCSI adapter: #esxcfg-swiscsi -e
  11. Add the iSCSI target to the software iSCSI adapter: #vmkiscsi-tool -D -a <IP address> <vmhba#> . Repeat this step if you have more iSCSI targets.
  12. Rescan the vmhba adapter with: #esxcfg-rescan <vmhba#>
  13. When the targets are discovered, you can view them with: #vmkiscsi-tool -T -l <vmhba#>
  14. Restart your server if necessary.

All done :)

Tested on ESX 4.0.0, Build 164009. Should also work on ESX 3.x.x.

Cheers!

- Marek.Z

Posted in ESX 4, VMware | 1 Comment »

503 Service Unavailable when logging in on ESX server through Web Access.

Posted by Marek.Z on 24 September 2009

I have encountered this error after a clean installation of ESX 4 server on a new HP DL 380 G6. When you access your ESX server through web interface and you try to log in by clicking on the “Log in to Web Access” link, you get the “503 Service Unavailable” error in your web browser. Here is how I solved this issue: 

  1. Log in to the console of the affected ESX server (or through puTTY) and check the status of the vmware-webAccess service by typing: #service vmware-webAccess status
  2. If the service is not running, start it with: #service vmwware-webAccess start
  3. If you want to start this service automatically when your ESX server starts, type: #chkconfig – - level 3 vmware-webAccess on
  4. Now, try again to log in to the Web Access of you ESX server and the issue schould be solved.

Cheers! :)

- Marek

Posted in ESX 3.5, ESX 4, VMware | 4 Comments »

 
Follow

Get every new post delivered to your Inbox.

Join 423 other followers