levans01's Posts

Joerg, SIOC is not enabled on these datastores in any throughout the environment. 
1.0 Background: [Setup] I have a problem I hope someone here can help me with.  I have a large vSphere 6.0 with a few hundred hosts. These hosts are distributed between 4-5 vCenter environme... See more...
1.0 Background: [Setup] I have a problem I hope someone here can help me with.  I have a large vSphere 6.0 with a few hundred hosts. These hosts are distributed between 4-5 vCenter environments. I have several HPE Nimble storage arrays organized into groups and they present various LUNs to the various vCenter environments. The vCenter environments are organized into two groups. A couple are for Hosting servers as guests and the others are for VDI. The storage arrays are arranged in a similar fashion so that one array cluster only presents LUNs to vCenters that have servers as guests and the other array presents LUNs to the vCenters used for VDI. The exception to this are two volumes.  We have  one volume that is used to present template and ISO images located in the SAN used to present LUNs to the VDI environment that is also made available to the vCenters for Servers.  And another volume that is hosted on the SAN for Servers and is presented to all  environments for temporary storage and the movement of data between the various vCenters.  This LUN is generally empty and is not used for heart-beating etc. All volumes are mounted using ISCSI software Adapter. 2.0  The Problem: In troubleshooting an unrelated issue with the storage vendor we noted these lightly used volumes were showing up really high on the IOPS and Network throughput list higher than many of our production LUNs some of which contain 200-300 VMs. IOPS and and throughput for these volumes were way out of line for their use.  We were able to determine this IO activity was not related to any actual workloads so it must be coming from the hosts or is VMware/ESXi related in some way. 3.0 What has been Done: We opened a ticket with VMware support.  They ran through all of the storage related performance checks and did not find anything out of order.  We disabled ATS on the hosts to see if it would change anything it did not.  We were able to determine the scope to be as follows of the 5 vCenters the two volumes are mounted to ,the problem only shows up on three of the 5 vCenters  1 vCenter for servers and 2 VDI vCenters. Our largest vCenter which contains 4 clusters the problem only shows up in two of the clusters. We know that if we unmount the volume the problem appears to go away.  We see corresponding drops in IOPs and throughput. We’ve taken packet traces and checked the ESXI hosts logs and we found something interesting but have not been able to get anything to line up.  We can see the high-IOPS/throughput when  Setting a performance chart  Performance > Datastore > Realtime > (datastores) > Read Rate.   In places where this problem does not exists, the throughput is  < 20 KBps  but in places were we are seeing the problem we see 3000-8000KBps.  Most of the errors we are seeing in the vmkernel.log on the hosts are MISCOMPARE ON VERIFY Please let me know if additional information is needed. Thank you.
1. Forward and Reverse lookup names are working from the Jump Box where the installer is running for the VCSA FQDN. 2. All machines are in the same port group on the VDS.  They are all pointing ... See more...
1. Forward and Reverse lookup names are working from the Jump Box where the installer is running for the VCSA FQDN. 2. All machines are in the same port group on the VDS.  They are all pointing to the same DNS servers. 3. I move all machines into the host same host.   (Source Appliance, Destination Appliance, Windows VUM machine and Jumpbox.) 4. Started Stage 2 of the installation  - Failed at the same point. (It failed)  #2 made it to 100% before generating an error. Image 1.1 Final error.
Johnathon,  I will try that to see if it solves my problem.   I will post and update on my steps and the outcomes. Thanks!
Johnathan, Thanks for the quick answer and the TIP.   Here's the SR 20099508402 Thank you.
Good Afternoon, 1. For a couple of weeks now I have been working on completing what should be a fairly straight forward task of upgrading a fully integrated 6.0 VCSA to 6.7 VCSA. 2.  Stage 1:... See more...
Good Afternoon, 1. For a couple of weeks now I have been working on completing what should be a fairly straight forward task of upgrading a fully integrated 6.0 VCSA to 6.7 VCSA. 2.  Stage 1: Deploy vCenter Server Appliance with an Embedded Platform  Services Controller completes without issue. Image 1.1. Upgrade Stage 2: Data transfer and appliance setup is in progress  3. Stage 2 completes two of the three tasks and then complains that the source vCenter has been powered off.   This seems like a problem with the workflow.  I've tried powering the old vCenter back on and retrying the operation but it simply fails again in error.  Image 1.2 VCSA 6.7 Upgrade Failure Error: 4. The new appliance has an error which indicates the IMPORT failed.  It still has the old IP address on the console.  When I reboot the target appliance it switches to the new Appliance FQDN and IP address but the appliance is clearly broken.  The console still shows Upgrade Import error: Image 1.3 VCSA 6.7 VCSA appliance      5. When I logon to the VCSA 6.7 at https://FQDN.TLD/:5480  I see the following error message: Image 1.4 VCSA 6.7 Appliance Broken message. I think I am doing everything correctly.  I don't know if there is another way to go forward.  I want to say that several years back there was talk of being able to stand up a new appliance. (Standalone) and them manually import the configuration?  If anyone has seen this problem and have a solution I am all ears. PS.  I have a ticket open with VMware support and I have provided them with the logs but I have not received any actionable responses from them yet.  Other than try powering on the previous appliance to complete the final step. Thank you.
LucD, In our troubleshooting, we disabled the policy.  It did not change the results for our script.  And to be clear,  your script was able to grab several results over multiple runs against... See more...
LucD, In our troubleshooting, we disabled the policy.  It did not change the results for our script.  And to be clear,  your script was able to grab several results over multiple runs against the same servers and only sporadically missed two.  We are running our test script that attempts to get 10 sets of 12345 from the server.  In one of our test runs, your script missed on 4th attempt out of 10 with the error previously noted against the same server.  And in another instance, on the 10th attempt. Subsequent runs were without error.
LucD, Thanks for all of your help.  I was able to work with a team member to get your script to run inside of Powershell on my machine.  I can report that is pretty much works flawlessly.  My... See more...
LucD, Thanks for all of your help.  I was able to work with a team member to get your script to run inside of Powershell on my machine.  I can report that is pretty much works flawlessly.  My PowerCLI script has a much higher failure rate when getting results from non-domain controllers. Your script failed a couple of times when running iterations against member servers.  The error returned was File : <Path.PS1> cannot be loaded.  The file <FileName> is not digitally signed.  You cannot run this script on the current system.  For more information about running scripts and settings execution policy, see about_Execution-Policies at http://go.microsoft.com/fwlink/?LinkID=135170.  - This only happened twice during multiple attempts.  Have you ever seen this before?  I do not think the problem is a script error but something in the guest perhaps.  I have screenshots.
Understood.  Thanks for the feedback.  I can try different versions in my test environment provided I can reproduce the the problem with the older versions that is, the ones I am using in my prod... See more...
Understood.  Thanks for the feedback.  I can try different versions in my test environment provided I can reproduce the the problem with the older versions that is, the ones I am using in my production.  How can I use Invoke-VMScriptPlus​?  What do have to do to use it on my system? Thanks! 
I manage a very large environment and have change controls in place.  If we think upgrading to the latest version of PowerCLI and and Powershell will permit an defined system function to work cor... See more...
I manage a very large environment and have change controls in place.  If we think upgrading to the latest version of PowerCLI and and Powershell will permit an defined system function to work correctly it is worth a shot.  However, that would suggest to me that there is a bug in the software.  I have situations when I run the commands against a domain controllers and it works flawlessly.  But when I run the commands against domain joined machines the results get sporadic. (The problem appears to be particularly specific).
Good Morning, My PowerCLI Version is: PowerCLI 6.5 Release 1 build 4624819   the output of $PsVersionTable on the target VMs is: PSVersion 4.0 WSManStackVersion 3.0 SerializationVersio... See more...
Good Morning, My PowerCLI Version is: PowerCLI 6.5 Release 1 build 4624819   the output of $PsVersionTable on the target VMs is: PSVersion 4.0 WSManStackVersion 3.0 SerializationVersion 1.1.0.1 CLRVersion 4.0.30319.42000 BuildVersion 6.3.9600.19170 PSCapatibleVersion {1.0, 2.0, 3.0, 4.0} RSremotingProtocolVersion 2.2
Issue Details:  1. We use PowerCLI to get values from VMs.  There are instances where the values fail to return.  It is our belief that this worked flawlessly before and we can show that it s... See more...
Issue Details:  1. We use PowerCLI to get values from VMs.  There are instances where the values fail to return.  It is our belief that this worked flawlessly before and we can show that it still does in some instances.  We developed a test script to reproduce the problem as well as show instances where things appear to work correctly.  This script connects to a machine we chose.  We provide administrative credentials and the script returns the value 12345.  It does ten iterations of this task.  We expect 10/10.  $creds = Get-Credential $successes = 0; while ($true) { $output = Invoke-VMScript -VM "MyVM" -ScriptText "return '12345'" -GuestCredential $creds $output if ($output.ScriptOutput) {$successes++} if ($successes -eq 10) {break} } When we run this script against some servers it works flawlessly.  That is the return is 10/10.  When we look at the VM > Tasks & Events > Events  we see the following successive events which are normal. (1) Guest operation Create Temporary File performed. (2) Guest operation Start program performed. (3) Guest operation List processes Performed. (4) Guest operation List processes Performed. (5) Guest operation Initiate File Transfer from Guest Perform. (6) Guest operations Delete File performed. The system repeats these events for each successful iteration. 2.  Our test script will make as many iterations as possible to get 10 successful results.   Ideally, it would only have to make 10 attempts to get 10 results.  But when there are failures, we have to make more than 10 attempts to get the desired results. I have seen it take as many as 19 attempts to get 10 successes. 3. As an additional data point, When running this script against the domain controller in an environment it works flawlessly.  However, when running against a domain joined machine in the domain, the problem happens. If I watch the creation of the Powershell## file in the temp directory on the system.  The ones that copy with 0 bytes are the ones that fail.  Any ideas? Thanks!