Fast Track IT Solution

Archive for December, 2013

truth v/s hype “Still Vmware don’t have any solution for ensure 100% up time for any enterprise application”

Unfortunately still don’t have any solution for ensure 100 % up time for mission critical application.I

Ideally two are the basic solution, which we can purpose in Vmware environment, we can configure HA for VMs, if primary host(where Currently VMs are resided) goes down, all Vms will migrate to another host (If another host have enough reserve resource)

and will restart all Vms on this host.

It will consider Minimum 5 mins Downtime (Fail to server 100 Up time)

Second option is FT, we can purpose to FT solution, FT facility are supporting to limited only Processor, if your processor are supported then you can assign single processor CPU for virtual machine.

“If you have enterprise application and you expecting 1000 concurrent session then you can face performance issues”

This solution are not probably 100 good.

Third solution is “Vmware Vcenter Site recovery Manager” this also good solution but it also consider few mins downtime and little bit expansive solution for mid size organization.

Little bit frustrate “When typing into a remote console, you see unintended repeated keystrokes “

Details

When typing into a remote console, you see unintended repeated keystrokes.

Solution

If you are using a wide-area or low-bandwidth connection, the time delay over the network may be long enough to cause the virtual machine to start auto-repeat.

To reduce these effects, increase the time threshold necessary for auto-repeat in the remote console.

  1. Power off the virtual machine.
  2. Add a line, similar to this, at the end of your virtual machine’s configuration (.vmx) file:

    keyboard.typematicMinDelay = "2000000"

    The delay is specified in micro-seconds, so the line in the example above increases the repeat time to 2 seconds. This should ensure that you never get auto-repeat unless you intend it.

  3. Power on the virtual machine.

To make the changes using the vSphere Client:

  • Power off the virtual machine
  • Right click virtual machine select Edit Settings
  • Click Options > General  > Configuration Parameters
  • Click Add Row
  • Under Name enter keyboard.typematicMinDelay  In the Value field  2000000
  • Click OK
  • Power on the virtual machine

Error “The VMware VirtualCenter Server Service on Local Computer started then stopped”

One Silly issues has spoil 2 hours for solution….coincidentally we had installed PRTG Monitoring tool and V Center in same system.

Issue

VirtualCenter Server service fails starting on vCenter Server 5 with an error: The VMware VirtualCenter Server Service on Local Computer started then stopped . Some services stop automatically if they have no work to do, for example the Performance logs and Alerts service.

Solution

There is a conflict with TCP/IP port 8085 that is used by PRTG Network Monitor software and also by VirtualCenter Server.
Please refer to the following VMware KB article for a list of TCP and UDP ports required to access vCenter Server:

 

VMware vSphere FT Configuration

1. Network configuration.

2. Turning on FT.

3. 54% through setting up FT.

4. FT setup complete.

5. vLockstep Interval and Log Bandwidth information are now updated.

6. Primary VM is located on 10.10.10.146.

7. Secondary VM is running on the Secondary Host- 10.10.10.145.

8. Testing FT using the built in Test Failover command.

9. Failover test completes. Notice that 10.10.10.146 has become the secondary location.

10. After the Failover Test, the primary host server is now 10.10.10.145 and the primary VM is running on it.

11. Furthermore, after the Failover Test, the secondary VM runs on the secondary host server, 10.10.10.146.

12. Failover test completion will result in showing the primary VM on the new primary host server and the new secondary host server with the accompanying vLockstep Interval and Log Bandwidth.

13. Finally, VMware vSphere FT is ready to provide continuous protection to your VMs