Raj2796's Blog

October 10, 2012

Windows 2008 R2 64 clearing all event logs via powershell

Filed under: MS — raj2796 @ 11:34 am

Quick post – some of my virtual servers amassed massive event logs that were using up valuable space, a quick way to clear all event logs on the server from  powershell is to use the command:

wevtutil el | foreach { wevtutil cl $_ }


March 14, 2012

Vmware vSphere 5 dead LUN and pathing issues and resultant SCSI errors

Filed under: san,vmware — raj2796 @ 3:13 pm

Recently we had a hardware issues with a san, somehow it appears to have presented multiple fake LUN’s to vmware before crashing and leaving vmware with a large amount of dead LUN’s it could not connect to. Cue a rescan all … and everthing started crashing !

Our primary cluster of 6 servers started to abend, half the ESX servers decided to vmotion of every vm and shutdown, the other 3 ESX servers were left running 6 servers worth of vm’s, DRS decided to keep moving vm’s of the highest utilised ESX server resulting in another esx server becoming highest utilised which then decided to migrate all vm’s of and so on in a never-ending loop

As a result the ESX servers were:

  • unresponsive
  • showing powered of machines as being on
  • unable to vmotion vm’s of
  • intermittently lost connection to VC
  • lost vm’s that were vmotioned i.e. the vms became orphaned

Here’s what i did to fix the issue.

1 – get NAA ID of the lun to be removed

 See error messages on server

Or see properties of Datastore in vc (assuming vc isn’t crashed)

Or from command line :

#esxcli storage vmfs extent list

Alternatively you could use #esxclu storage filesystem list however that wouldn’t work in this case since there were no filesystems on the failed luns

e.g. output

Volume Name VMFS UUID                           Extent Number Device Name                           Partition
———– ———————————– ————- ————————————  ———
datastore1  4de4cb24-4cff750f-85f5-0019b9f1ecf6             0  naa.6001c230d8abfe000ff76c198ddbc13e        3
Storage2    4c5fbff6-f4069088-af4f-0019b9f1ecf4             0  naa.6001c230d8abfe000ff76c2e7384fc9a        1
Storage4    4c5fc023-ea0d4203-8517-0019b9f1ecf4             0  naa.6001c230d8abfe000ff76c51486715db        1
LUN01       4e414917-a8d75514-6bae-0019b9f1ecf4             0 naa.60a98000572d54724a34655733506751        1

Look at the 3rd column, it’s the naa id of the luns, the 4th one is for a volume that’s labelled LUN01 – dodgy since they would have a recognisable label such as FASSHOME1 or FASSWEB6 etc if they were production servers, or even test servers

  • 2 – remove bad luns


If vc is working – in our case it wasn’t – goto configuration / device / look at the identifier’s and match the naa – e.g. random screenshot below to show where to look ( screenshot removed since it shows too much work information)

Right click the naa under identifier and select detach – confirm

Now rescan the fc hba

In our case vc wasn’t an option since the hosts were unresponsive and vc couldn’t communicate, also the luns were allready detached since they were never used, so :

list permanently detached devices:

# esxcli storage core device detached list

look at output at state off luns e.g.

Device UID                            State

————————————  —–

naa.50060160c46036df50060160c46036df  off

naa.6006016094602800c8e3e1c5d3c8e011  off

next permanently remove the device configuration information from the system:

# esxcli storage core device detached remove -d <NAA ID>


# esxcli storage core device detached remove  -d naa.50060160c46036df50060160c46036df




To detach a device/LUN, run this command:

# esxcli storage core device set –state=off -d <NAA ID>

To verify that the device is offline, run this command:

# esxcli storage core device list -d <NAA ID>

The output, which shows that the status of the disk is off, is similar to:


   Display Name: NETAPP Fibre Channel Disk (naa.60a98000572d54724a34655733506751)

   Has Settable Display Name: true

   Size: 1048593

   Device Type: Direct-Access

   Multipath Plugin: NMP

   Devfs Path: /vmfs/devices/disks/naa.60a98000572d54724a34655733506751

   Vendor: NETAPP

   Model: LUN

   Revision: 7330

   SCSI Level: 4

   Is Pseudo: false

   Status: off

   Is RDM Capable: true

   Is Local: false

   Is Removable: false

   Is SSD: false

   Is Offline: false

   Is Perennially Reserved: false

   Thin Provisioning Status: yes

   Attached Filters:

   VAAI Status: unknown

   Other UIDs: vml.020000000060a98000572d54724a346557335067514c554e202020

Running the partedUtil getptbl command on the device shows that the device is not found.

For example:

# partedUtil getptbl /vmfs/devices/disks/naa.60a98000572d54724a34655733506751


Error: Could not stat device /vmfs/devices/disks/naa.60a98000572d54724a34655733506751- No such file or directory.

Unable to get device /vmfs/devices/disks/naa.60a98000572d54724a34655733506751



In our case we’re vmotioning the servers of then powering down/up the servers since they have issues and we want to force all references to be updated from a fresh network discovery which is the safest option

You can rescan through VC under normal operations – the scan all can cause errors however and its better to selectively scan adapaters to avoid stressing the system

Alternately theres the command line command which needs to be run on all affect servers:

# esxcli storage core adapter rescan [ -A vmhba# | –all ]

Othere usefull info

  • Where existing datastores have issues and need unmounting and vc not working

# esxcli storage filesystem list

(see above for example output)

Unmount the datastore by running the command:

# esxcli storage filesystem unmount [-u <UUID> | -l <label> | -p <path> ]

For example, use one of these commands to unmount the LUN01 datastore:

# esxcli storage filesystem unmount -l LUN01

# esxcli storage filesystem unmount -u 4e414917-a8d75514-6bae-0019b9f1ecf4

# esxcli storage filesystem unmount -p /vmfs/volumes/4e414917-a8d75514-6bae-0019b9f1ecf4

verify its unmounted by again running # esxcli storage filesystem list and confirming its removed from list

The above are the actions I found useful in my environment – to read the original Vmware TID i gained the majority of the information from go here

September 30, 2011

Novell Application Launcher (NAL) – diagnosing freezing, slow starting and other problems.

Filed under: edir,Netware — raj2796 @ 2:58 pm

This post is a collated note to myself of useful links and information from goggling these issues when I encountered them in the past.  We encountered an issue in the recent past where nal failed to load at random.

Whilst it turned out to be edir corruption of our user container its reoccurred, my moneys on corruption again!

You can however, investigate in detail by enabling nal debugging and tracing what happens. With debugging enabled to the level you need logs will be generated which should hopefully give you a clue what’s wrong. You have two options

  •  manually hack in the relevant reg settings
Enabling Debug Logging for the Novell Application Launcher
Debug logging for the Novell® Application LauncherTM is enabled in the Windows registry or using the diagnostic tool, naldiag.exe. This section focuses on using the registry to enable debug logging.
NOTE:  The keys in this table are the same as those that are set by nialdiag.exe.
The table below specifies the information you need to edit registry of the workstation where the Application Launcher agent is running:
Registry Key and Hive Location Value Name Value Type Data Notes
HKLM\Software\NetWare\NAL\1.0\Debug Level DWORD 0 (Off) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
1 (Informational messages only)
2 (Warning messages only)
3 (Informational and Warning messages only)
4 (Critical messages only)
5 (Informational and Critical messages only)
6 (Warning and Critical messages only)
F (All messages)
HKLM\Software\NetWare\NAL\1.0\Debug LogFileLocation STRING location_and_filename_of_output_file Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Browser DWORD 0 (Off) Destination: Browser log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Explorer DWORD 0 (Off) Destination: Application Explorer log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug IPC DWORD 0 (Off) Destination: IPC log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Library DWORD 0 (Off) Destination: Library log file specified


1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug MUP DWORD 0 (Off) Destination: MUP log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Reporting DWORD 0 (Off) Destination: Reporting log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Service DWORD 0 (Off) Destination: NT Services log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Start DWORD 0 (Off) Destination: Startup log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug Workstation DWORD 0 (Off) Destination: Workstation log file as specified
1 (On) Location: program files\novell\zenworks\
zfdnal.csv (default location if none is specified)
HKLM\Software\NetWare\NAL\1.0\Debug MSI DWORD 0 (Off) Location: program files\novell\zenworks\
1 (On) Alternatively, zappmsi.log is in the path listed in the LogFileLocation string value, if specified
  • OR use the naldiag.exe tool,  it will create the registry keys for logging for you, You should fine it located under

c:\Program Files\Novell\ZENworks\NalDiag.exe


a.k.a where I got the information from

The importance of launcher configuration

Enable debug logging in ZDM

Slow Nal start-up or refresh

September 28, 2011

Windows Symbolic links, Hard links, Junctions and problem accessing remotely

Filed under: MS — raj2796 @ 11:03 am

Microsoft has once again implemented more features from rival os’s, which can only be a good thing since in this case it’s Linux. Symbolic links, hard links and junctions can now be created in windows via the mklink command, older OS’s e.g. XP need to download the resource pack and grab linkd


Mklink – vista/windows 7/ windows 2008 / windows 8

There are 3 options for mklink

  • Symbolic links – selected via the /D flag – these are like short cuts – a symbolic link to a directory is created, the default is a file symbolic link . For those of us from Linux think softlink
  • Hard link – selected via the /H flag – only for files – if you delete the hard link you delete the actual file as opposed to symbolic links where you just delete the link to the file
  • Junction – selected via the /J flag – created a directory junction i.e. hard link to a directory
For example, if you want to create a symbolic link from your appv content directory e.g. c:\AppV\content to a dev directory e.g. c:\AppV\dev you would type:
mklink /D c:\Appv\content\dev c:\Appv\dev
as shown in the below image
Linkd - only on older machines such as XP, mklink is far better

LINKD Link [/D] Target


I suggest using a junction, they work remotely by default, however if you need to access a symbolic link remotely you can by editing the symbolic link evaluation. MS explain this on technet here – the relevant part being:

Evaluations. A user can enable or disable any of the four evaluations that are available in symbolic links. The available evaluations are:

  • Local-to-local describes a computer accessing a local symbolic link that points to a local file or folder.
  • Local-to-remote is a computer accessing a local symbolic link that points to a Universal Naming Convention (UNC) path using the server message block (SMB) protocol.
  • Remote-to-local is a computer accessing a remote symbolic link that points to a local file or folder using SMB.
  • Remote-to-remote describes a computer accessing a remote symbolic link that points to a remote UNC path using SMB.
to allow all use the command :
fsutil behavior set SymlinkEvaluation L2L:1 R2R:1 L2R:1 R2L:1

February 1, 2011

Deploying VM template including McAfee

Filed under: vmware — raj2796 @ 4:32 pm

I found this useful post on the mcafee forums

Cloning images containing the McAfee Agent can cause problems for ePO. Duplicate GUIDs and MAC addresses cause the problems.

Once the image is deployed, VirusScan Enterprise protects agains changes, so the batch file below needs to have these protections disabled prior to attempting changing the GUIDs and MAC addresses.

Do this before closing the image so that when the newly deployed image is first started new values will populate automatically with virtually no likely of duplicates. (Well, the MAC address needs to be considered in your environment.)

In order to make either registry change, you will have to temporarily change the default settings within VSE to allow the changes to occur.

From the VirusScan Console

  • Access Protection > Properties
  • Uncheck (unblock) ‘Prevent McAfee services from being stopped’
  • Common Standard Protection
  • Uncheck ‘Prevent modification of McAfee files and settings’
  • Uncheck ‘Prevent modification of McAfee Common Management Agent’

Then run the batch file below, or manually make the changes.


@echo off
title McAfee AgentGUID and MacAddress Removal Tool – by Ron Metzger
echo The McAfee Agent communicates with ePO, Protection Pilot, or McAfee’s
echo update services, using registry values of AgentGUID and MacAddress, to
echo uniquely identify each system. Imaging or duplicating a system breaks
echo these unique identifiers. Clearing these values, followed by a reboot or
echo services restart, repopulates these values with new and unique entries.
echo Prior to duplication, clear these registry entries and create the image
echo before restarting services or rebooting.
echo Otherwise,
echo After duplication, clear these values, then reboot or restart the services.
echo VSE v8.7i (or above) by default, self-protects against certain changes.
echo In order to make either registry change, temporarily disable the
echo self-protection settings within VSE v8.7i (or above).
echo From the VirusScan Console:
echo Access Protection > Properties
echo Uncheck ‘Prevent McAfee services from being stopped’
echo Common Standard Protection
echo Uncheck (un)Block ‘Prevent modification of McAfee files and settings’
echo Uncheck (un)Block ‘Prevent modification of McAfee Common Management Agent’
Choice.exe /C:YN /N ” Press Y to continue, N to skip . . . ?”
if ErrorLevel 2 goto Exit

echo Stopping services . . .
net stop McAfeeFramework /yes
net stop McShield /yes
net stop McTaskManager /yes
echo Stopping services, done.

echo Deleting registry entries . . .
REG delete “HKLM\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent” /v AgentGUID /F
REG delete “HKLM\SOFTWARE\Network Associates\ePolicy Orchestrator\Agent” /v MacAddress /F
REG delete “HKLM\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Agent” /v AgentGUID /f
REG delete “HKLM\SOFTWARE\Wow6432Node\Network Associates\ePolicy Orchestrator\Agent” /v MacAddress /f
echo Deleting registry entries, done.

echo Please re-enable the self-protection settings within
echo VSE v8.7i (or above) to there original values.
echo From the VirusScan Console:
echo Access Protection > Properties
echo Check ‘Prevent McAfee services from being stopped’
echo Common Standard Protection
echo Check Block ‘Prevent modification of McAfee files and settings’
echo Check Block ‘Prevent modification of McAfee Common Management Agent’
Choice.exe /C:YN /N ” Press YN to continue . . . ?”
echo About to restart McAfee services.
echo This will repopulate AgentGUID and MacAddress values.
echo Please do Not start these services if Imaging this system Now. (Choose Skip.)
Choice.exe /c:YN /T:N,15 /N ” Restart Services? Y to continue, N [or wait 15 seconds] to skip . . .
if ErrorLevel 2 goto Exit

echo Starting services . . .
net start McAfeeFramework /yes
net start McShield /yes
net start McTaskManager /yes
echo Starting services, done.

Choice /c:YN /T:Y,15 /N ” Press YN [or wait 15 seconds] to continue . . .

This batch file can be used to prep and image or to simply change the values after the image has been issued.Hope this helps. Post back with more questions.


Ron Metzger

originally posted here

January 25, 2011

VMware Template renames network adaptor when deploying windows 7 or windows 2008 R2

Filed under: MS,vmware — raj2796 @ 10:40 am

This caught me out for a while and I originally thought i had made a mistake in creating my templates, however it appears this is a known issue with VMware, from the VMware knowledge base :

Deploying Windows 2008 R2 and Windows 7 templates with vmxnet3 renames the NIC as #2

When deploying virtual machines from a Windows 2008 R2 or Windows 7 template configured with the vmxnet3 Ethernet device, the resulting virtual machine’s guest operating system shows the Ethernet adapter as:

VMXNET Device #2 in Device Manager
Local Area connection #2 in Network Properties

This issue occurs when virtual adapter VMXNET3 is used.
To workaround this issue, try one of these options:

  • Use E1000 virtual network cards in Windows 2008 R2 and Windows 7 templates.
  • Apply the Microsoft hotfix for this issue. For more information, see the Microsoft Knowledge Base article 2344941.

This hotfix may resolve issues with duplicate MACs when deploying Windows 2008 R2 from template using an E1000 driver.

Note: The preceding link was correct as of January 12, 2011. If you find the link is broken, provide feedback and a VMware employee will update the link.

From :

January 14, 2011

DNS query of multi-label SRV records cause the KMS auto-detection feature not to work

Filed under: MS — raj2796 @ 4:25 pm

From technet (basically you install a hotfix)

When you try to activate Windows 7 or Windows Server 2008 R2, you may receive an error message that resembles the following:
Windows could not be activated. Key management services (KMS) host could not be located in domain name system (DNS), please have your system administrator verify that a KMS is published correctly in DNS. Error: 0x80092328 Description: DNS name does not exist.
Alternatively, you may receive error code 0x800705b4:
This operation returned because the timeout period expired.
This hotfix changes the behavior in which a Domain Name System (DNS) client queries DNS for Key Management Service (KMS). This hotfix applies to DNS clients that are running Windows 7 or Windows Server 2008 R2.
Important The most common causes for this error are described in the following Microsoft Knowledge Base article:
929826 Error message when you try to activate Windows Vista Enterprise, Windows Vista Business, Windows 7, or Windows Server 2008: “Code 0x8007232b”
We recommend that you try the methods that are documented in this article before you install this hotfix.

To query DNS, a DNS client that is running Windows 7 or Windows Server 2008 first queries without appending DNS suffixes. If the first query fails, the DNS client then queries again by appending DNS suffixes.

However, this behavior may cause the KMS auto-detection feature not to work. The KMS auto-detection feature relies on the Service Location (SRV) resource record, that is returned by a DNS query, to specify the location of a KMS host. Because of customer’s DNS configuration, the SRV record may be a multi-label name. In this case, the DNS client cannot locate a multi-label SRV record in the first DNS query. If the first query times out, the DNS client will not run another query by appending suffixes. Instead of a followed suffix query, a failed initial multi-label query is submitted to the upstream DNS host servers that are outside the domain. Therefore, the KMS auto-detection feature does not work and a KMS host cannot be located.


December 16, 2010

SSSU and You!

Filed under: eva — raj2796 @ 11:53 am

Now, in a previous posting, I mentioned that I would talk more about SSSU, especially in talking about how to export the information and then put it into a human readable format. SSSU can output xml format, but that requires some type of xml parsing tool. I did mention that Microsoft’s Log Parser tool could be used, but really I’m lazy, and it’s a bit cumbersome. And truth be told, I never got it to work just right.
So last night I sat down and did some old fashioned thinking about how I can get the information I need, but easier and with less effort. I started toying with powershell as it’s a good friend in the VMware space. I have to confess though that I have a Mac. Yes, I enjoy monotasking. Nothing wrong with that I then realized (as I sometimes forget) that I had a whole delicious CLI on my mac. This includes great tools like grep and diff! Well and a lot more, but I’ll stick to those for now. (Note that you can get grep and diff for Windows, via either the Windows versions of those tools, or using Cygwin). Fear not win32 folks, you are covered!
Let me take a step back and cover the premise for wanting to gather information from SSSU. As we know, Command View is a web-based interface for communicating with the EVAs. While it does provide lots of information, it is troublesome to navigate around and get that information easily. One off kinds of things, certainly. But pulling in lots of info easily, I think not. One big flaw, in my mind, is that CV talks to the EVAs via the SAN, and not via IP. Why is this a flaw? Well, for instance, SSSU can’t talk directly to the EVAs themselves. Rather, it has to talk to the CV server (which is why it prompts you when you fire it up for a “manager”). This also means you can’t use SSSU to do anything if your CV server has bit the dust. But I digress.
From the arrays, I want to gather information on my vdisks, my controllers, snapshots, disks, and my disk groups. I want to gather some information once, some monthly, and some on a more regular basis.
For the vdisks, I run (via SSSU) this command: LS VDISK FULL > vdisk.txt (This will output the information into a text file in the directory where the sssu.exe is located) Then, I fire up my command line, and grep that sucker for some info:
grep “familyname\|allocatedcapacity\|redundancy\|diskgroupname” textfile > date_vdisk.txt
This output will give me a file with the date that has the information I am specifically looking for


As stated before, I am quite lazy and so I could use (or you could use) awk (another great command line text processor) to generate the output in a better format. But instead, I keep it like this. Note that allocatedcapacity is the vdisk size in GB. Now, since I’m generating these files monthly, I can use the diff command to compare two months and see what has changed (disk grows, adds, deletes, etc).
diff -y date_vdisk1.txt date_vdisk2.txt | grep “familyname\|allocatedcapacity”


Note the | in there. The older date is on the left, and the newer date is on the right. So it’s easy to see which has changed and by how much. Arguably you could make this even easier, but again, lazy. And this works for me, so your mileage may vary.
Since these are simple text files, it’s easy and pain free to keep them around. Overall, I use this information for vdisks to track growth, easy at a glance for what vdisk is what size/raid level, and you can also pull out info to find out what controller has what disks.
This leads me into talking about what information I grab from my controllers. Now, one thing to note: The EVA4400 series only has one listed Controller (in this case Controller 1). This is because of how it is designed: both controllers are in the same housing, sharing a back plane. We have three 8100 series, each having two physically separate controllers, listed as Controller 1 and Controller 2.
First, to find out ALL the info on your controllers, do LS CONTROLLER FULL in SSSU. The output will be big and full of interesting details. One other thing to note: SSSU denotes them as Controllers 1 and 2. Command View denotes them as Controllers A and B. Lame! For what I need, I don’t need to keep controller info like I do vdisk info. I will do an initial grab after an XCS code update to keep handy.
One pretty handy way to find out what snapshots you have on any given EVA for a point in time is to use LS SNAPSHOT. You can also do an LS SNAPSHOT FULL if you want the full info per snapshot (like the vdisk info). The key difference between a snapshot and a normal vdisk is the line item sharingrelationship. A normal vdisk will have none, but a snapshot will say snapshot


When it comes to gathering information on disks, I use this primarily to check firmware levels. If you are an EVA owner, you know that as part of the care and feeding of an EVA comes making sure all drives are at the most current level of firmware. Updates are also usually done and bundled with XCS updates. One thing to be aware is that with drive failures, replacements may not always come with the latest firmware. They should, but I have not always seen that. Thankfully firmware updates are non-invasive (for the most part). I will cover an XCS code upgrade in a future blog post (our EVA4400 is due).
So, if you do LS DISK FULL from SSSU, you will get all the info from each disk. You can then just grep for fun and profit!
grep “diskname\|firmware” disks.txt


So you are saying hey that’s great, but I have multiple kinds of disks in my EVA. So, you need to know what model of drive so you can keep things sorted as to what firmware is for what drive. Easy way is to just sort by disk group. Since you built your EVA correctly, you know only to put drives of the same type and speed into the same group right?
grep “diskname\|diskgroupname\|firmware” disks.txt


You can also grab the model number for the drives by tossing in modelnumber to the grep.
And finally, since you all are probably bored to tears now, I grab the size of the disk group to know what kind of overall growth or change occurs on each group. I can also use this information to plan out new server storage requests, and manage to 90% capacity. Easier to give management a shiny graph saying “Look, almost out of disk. Checkbook time!”
Okay, so that about wraps up what I use SSSU for. If I think about anything else neat that I do, I’ll be sure to blog about it. The next blog topic will be about WEBES, its use, the install, and the fact that it actually works pretty good.

From h t t p://www.virtualizetips.com/2010/09/ (virtualizetips is currently hosting malawareso i can’t link direct to them as google/antivirus filters will block my site- 14 oct 2011)

December 15, 2010

Configuring VMware High Availability fails with the error: Cannot complete the configuration of the HA agent on the host

Filed under: ha,vmware — raj2796 @ 4:40 pm

Configuring VMware High Availability (HA) fails
The vSphere Client may show one service console, however running the esxcfg-vswif -l command while logged into the ESX service console, reveals additional service consoles
You see the messages:
Cannot complete the configuration of the HA agent on the host. See the task details for additional information.
Misconfiguration in the host network setup
This issue occurs if all the hosts in the cluster do not share the same service console or management network configurations. Some hosts may have service consoles using a different name or may have more service consoles than other hosts.

Address the network configuration differences between the hosts if you are going to use the Shut Down or Power Off isolation responses because these options trigger a VMware HA isolation in the event of Service Console or Management Network failures.

If you are using the Leave VM Powered on isolation response, the option to ignore these messages is available in VMware VirtualCenter 2.5 Update 3.

To configure VirtualCenter to ignore these messages, set the advanced option das.bypassNetCompatCheck to true:

Note: When using the das.bypassNetCompatCheck option, the heartbeat mechanism during configuration used in VirtualCenter 2.5 only pairs symmetric IP addresses within subnets across nodes. For example, in a two node cluster, if host A has vSwif0 “Service Console” 10.10.1.x and vSwif1 “Service Console 2” 10.10.5.x and host B has vSwif0 “Service Console” 10.10.2.x and vSwif1 “Service Console 2” 10.10.5.x, the heartbeats only happen on vSwif1. Starting in vCenter Server 4.0, they can be paired across subnets if pings are allowed across the subnets. However, VMware recommends having them within subnets.
Right-click the cluster, then click Edit Settings.
Deselect Turn on VMware HA.
Wait for all the hosts in the cluster to unconfigure HA.
Right-click the cluster, and choose Edit Settings.
Select Turn on Vmware HA, then select VMware HA from the left pane.
Select Advanced options.
Add the option das.bypassNetCompatCheck with the value True.
Click OK on the Advanced Options screen, then click OK again to accept the cluster setting changes.
Wait for all the ESX hosts in the cluster to reconfigure for HA.

From http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1019200

October 19, 2010

Windows 2008 Vmware Vsphere additional disk issue

Filed under: MS,vmware — raj2796 @ 1:28 pm

All virtual machine disk files (VMDKs) are presented to VMs as SAN disks and Windows 2008 changed how SAN disks were handled, in effect they are offline until you set them online. You will see the “Disk is Offline because policy was set by an administrator” message.

First you need to change how Windows 2008 sees the SAN devices, then you need to clear a readonly flag, then you are good to go. Using ‘diskpart’ enter the following commands


Now you can use your normal mechanisms to add, format, etc. the disk into the system.


Next Page »

Create a free website or blog at WordPress.com.