11月 11, 2010

iLO “Remote Console is unavailable. It is already in use by a different client”

 When you  try to access the ILO Remote Console on some servers you sometimes get the message “Remote Console is unavailable. It is already in use by a different client”. But there is no other client connected to the ILO on that server. How can you “reset” the Remote Console connection (from remote) to access the server through the ILO again?

 Solve the problem by simply going to “Administration -> Settings -> Network -> Apply” (no changes to settings and just applying the current configuration)

 It disconnect all connections, you may able to connect the remote console now.

 Source: http://billyf2010.blog.com/2009/10/03/ilo-remote-console/ — this is a pretty good blog for WinTel system admins.

 Another solution:
 When using the integrated remote console on a HP Blade Server and you get disconnected for whatever reason you get the error message “The Integrated Remote Console is unavailable; it is already in use by a different client.”.

 This is a common problem and is apparently working as intended, though it can be annoying. To fix this you need to turn on “Remote console acquire” within the iLO of the system.

 Log into iLO and select Remote Console / Settings

There you will see settings that allow you to enable:

- Remote Console Acquire

Acquire allows you to terminate the current remote console session to attach a new one. The current user is notified.

 You can also click on Remote Console Share but you will need to purchase another license key for the functionality of having multiple users using the remote console at the same time.

 Source: http://waynestorey.com/blog/tag/remote-console/

 For Blade: http://egementanirer.blogspot.com/2009/03/integrated-remote-console-is.html

 Another solution:
 If you’re using HP ILO (Integrated lights out) and get this message it is because another use is either using the ILO or somehow it’s locked up.

 One way to get around this is to reset it under the web settings for the ILO if you have access to it. Under the System Status tab, you can go into diagnostics and there is a button to reset iLO2.

 Note that will kick off anyone currently using it, but who cares as long as it helps you right?

 Source: http://www.ashbaughonline.com/2007/12/08/unavailable-already-in-use-by-a-different-client/

 New ESX 4.0 host HA issue

add node failed HA configuration: Internal AAM Error – agent could not start.: Unknown HA error

 Solve the problem by: disable HA and DRS. then enable ONLY HA by itself, it should go through without a problem, then enable DRS on its own after HA is on.

 Strange issue with the warning message on the console screen:

LVM: 1234: One or more devices not found (file system [MY-VOL1, 48204a32-92515189-d2e2-0017a44742e7])

 and at the VIC this datastore has capacity for 1.2TB and used 1TB, but if add all the LUNs presided to the cluster, it only has 1TB, short 200GB and the free space is 200GB. That is very scary!!!

 This KB has the solution: http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1005204

We are the unlucky one. Here is the support engineer’s respond:

 All the ESX server in the cluster are complaining that part of the VMFS MY-Vol1 is missing an extent.  When we examined the VMFS header we found that volume was spanned across 8 devices,  but for at least the last 100 days, we only see 7 devices.

 We know the device is around 200GB,  but it was impossible to find out with where this device went nor can we repair this type of error.

 The only way to fix this issue is to create a New VMFS volume on new disk then storage vmotion all vms from the damaged  then remove/reformat the datastore.

 In support we recommend that you ovoid extents all together as they make VMFS volume recovery harder and are prone to human error (like this case)