Top vSAN articles for November 2017

  1. Component metadata health check fails with invalid state error
  2. vSAN Build Recommendation Engine Health fails
  3. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  4. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  5. Deployment guidelines for running VMware vSAN and VMware vSphere VMFS datastores on a Dell H730 controller with the lsi_mr3 driver
  6. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  7. vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider
  8. vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
  9. Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
  10. Cannot view or add vSAN Storage Providers in the vSphere Web Client
  11. “Failed to create directory” error when running vSAN 5.5/6.x
  12. VMware vSAN 6.1 fulfillment
  13. “Unexpected status code: 503” error in vSAN health check plug-in
  14. vSAN Multicast performance test fails
  15. SSD log buildup can cause poor performance in a VMware vSAN Cluster
  16. vSAN on disk upgrade fails at 10%
  17. vSAN Health Service – Cluster – Disk format version
  18. vSAN 6.2 hybrid disk group performance degradation

The post Top vSAN articles for November 2017 appeared first on Support Insider.

Posted in Knowledge Base, Top 20 | Comments

Top vSAN articles for November 2017

  1. Component metadata health check fails with invalid state error
  2. vSAN Build Recommendation Engine Health fails
  3. Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers
  4. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  5. Deployment guidelines for running VMware vSAN and VMware vSphere VMFS datastores on a Dell H730 controller with the lsi_mr3 driver
  6. “Host cannot communicate with all other nodes in vSAN enabled cluster” error
  7. vCenter Server 6.0 Update 2 displays on non-vSAN enabled ESXi hosts displays the message: Retrieve a ticket to register the vSAN VASA Provider
  8. vSAN performance diagnostics reports: “vSAN is experiencing congestion in one or more disk group(s)”
  9. Virtual Machine with more than 64GB memory fails to Storage vMotion to vSAN cluster
  10. Cannot view or add vSAN Storage Providers in the vSphere Web Client
  11. “Failed to create directory” error when running vSAN 5.5/6.x
  12. VMware vSAN 6.1 fulfillment
  13. “Unexpected status code: 503” error in vSAN health check plug-in
  14. vSAN Multicast performance test fails
  15. SSD log buildup can cause poor performance in a VMware vSAN Cluster
  16. vSAN on disk upgrade fails at 10%
  17. vSAN Health Service – Cluster – Disk format version
  18. vSAN 6.2 hybrid disk group performance degradation

The post Top vSAN articles for November 2017 appeared first on Support Insider.

Posted in Knowledge Base, Top 20 | Comments

Top NSX articles for November 2017

  1. Troubleshooting vShield Endpoint / NSX Guest Introspection
  2. Guest Introspection memory usage spikes to 90+% or you see the error: “Lost communication with ESX module” in NSX-V 6.3
  3. ESXi 5.5 and 6.0 hosts fail with a PSOD: VMCIEventDelayedDispatchCB@com
  4. Modifying the interface configuration for an already deployed DLR/ESG fails with a blank error message
  5. vCenter Server access is blocked after creating a Deny All rule in DFW
  6. Logging in to the NSX Manager Command Line Interface (CLI) as admin fails after upgrade
  7. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  8. “Not Ready” Installation Status in NSX
  9. Virtual machine in ESXi is unresponsive with a non-paged pool memory leak
  10. Network connectivity issues after upgrade in NSX/VCNS environment
  11. EAM fails with OutOfMemoryErrors
  12. Guest Introspection status reports “Warning: Guest Introspection service not ready”
  13. Backing up the NSX Manager to OpenSSH 7.x or later fails
  14. Upgrade,redeploy and deleting an NSX Edge fails
  15. Virtual machines are stuck at 0% or 35% when powering on
  16. NSX Edge upgrade to 6.3.3 fails when configured with IPv6 default gateway
  17. At times certain controller APIs could fail due to cleanup of API server reference files
  18. Upgrading from NSX-v 6.2.0, 6.2.1 and 6.2.2 to NSX-v 6.3.5 fails
  19. “No NSX Managers available” error in the vSphere Web Client

The post Top NSX articles for November 2017 appeared first on Support Insider.

Posted in Knowledge Base, Top 20 | Comments

Top NSX articles for November 2017

  1. Troubleshooting vShield Endpoint / NSX Guest Introspection
  2. Guest Introspection memory usage spikes to 90+% or you see the error: “Lost communication with ESX module” in NSX-V 6.3
  3. ESXi 5.5 and 6.0 hosts fail with a PSOD: VMCIEventDelayedDispatchCB@com
  4. Modifying the interface configuration for an already deployed DLR/ESG fails with a blank error message
  5. vCenter Server access is blocked after creating a Deny All rule in DFW
  6. Logging in to the NSX Manager Command Line Interface (CLI) as admin fails after upgrade
  7. Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products
  8. “Not Ready” Installation Status in NSX
  9. Virtual machine in ESXi is unresponsive with a non-paged pool memory leak
  10. Network connectivity issues after upgrade in NSX/VCNS environment
  11. EAM fails with OutOfMemoryErrors
  12. Guest Introspection status reports “Warning: Guest Introspection service not ready”
  13. Backing up the NSX Manager to OpenSSH 7.x or later fails
  14. Upgrade,redeploy and deleting an NSX Edge fails
  15. Virtual machines are stuck at 0% or 35% when powering on
  16. NSX Edge upgrade to 6.3.3 fails when configured with IPv6 default gateway
  17. At times certain controller APIs could fail due to cleanup of API server reference files
  18. Upgrading from NSX-v 6.2.0, 6.2.1 and 6.2.2 to NSX-v 6.3.5 fails
  19. “No NSX Managers available” error in the vSphere Web Client

The post Top NSX articles for November 2017 appeared first on Support Insider.

Posted in Knowledge Base, Top 20 | Comments

Top 20 vSphere articles for November 2017

  1. vCenter Appliance root Partition 100% full due to Audit.log files not being rotated
  2. “invalid credentials LDAP Error 49” error when starting Inventory Services in vCenter Server 6.x
  3. Important information before upgrading to vSphere 6.5
  4. Unable to log in to the root account of vCenter Server Appliance
  5. Large Java dump files created in the location /storage/log/vmware/perfcharts
  6. How to reset the lost or forgotten root password in vCenter Server Appliance 6.5
  7. ESXi host disconnects intermittently from vCenter Server
  8. Windows 8 and Windows 2012 Server or later virtual machines fail upon reboot
  9. How to repoint vCenter Server 6.x between External PSC within a site
  10. “fsck failed” error when starting vCenter Server Appliance
  11. Error “Logon failure: the user has not been granted the requested logon type at this computer”
  12. The vpxd process becomes unresponsive after upgrading to vCenter Server 5.5/6.0
  13. Cannot change the vCenter Server or Platform Service Controller 6.x hostname
  14. vmware-dataservice-sca and vsphere-client status change from green to yellow
  15. Best practices for upgrading to vCenter Server 6.5
  16. How to unlock and reset SSO password in vSphere 6.x
  17. “No host data available” reported in Hardware status tab
  18. “Failed to verify the SSL certificate for one or more vCenter Server Systems” error in the vSphere Web Client
  19. ESX Agent Manager solution user fails to log in after replacing the vCenter Server certificates in vSphere 6.0
  20. “back-end property provider” error while adding new datastore in vSphere Web Client

The post Top 20 vSphere articles for November 2017 appeared first on Support Insider.

Posted in Knowledge Base, Top 20 | Comments

Powerpoint for Mac switching resolution?

Advertise here with BSA


I’ve had this issue for a long time. Whenever I would open PowerPoint and present using a projector all my diagrams and screenshot would show up fuzzy. Even if I would set up the screen configuration to be optimized for the projector it still would not look great. The funny thing is that I always have my screen setup in “mirror” mode, and this week I noticed that when I switched between my regular screen to Presenter Mode on PowerPoint that the resolution would change.

Apparently when you use presenter mode with PowerPoint on a Mac it sets the screens in “extended mode” automatically. By default it then seems to optimize for the Mac screen automatically, which usually does not work well for the projector considering most are low resolution devices. I disabled the Presenter Mode option next, and when I turned off presenter mode in PowerPoint it worked fine. You can switch it off in Preferences under Slide Show:

I normally don’t blog about this kind of stuff, but as I hardly was able to find anything useful about it anywhere I figured I would share it with the world.

"Powerpoint for Mac switching resolution?" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.

Posted in mac, powerpoint, resolution, Various | Comments

Powerpoint for Mac switching resolution?

Advertise here with BSA


I’ve had this issue for a long time. Whenever I would open PowerPoint and present using a projector all my diagrams and screenshot would show up fuzzy. Even if I would set up the screen configuration to be optimized for the projector it still would not look great. The funny thing is that I always have my screen setup in “mirror” mode, and this week I noticed that when I switched between my regular screen to Presenter Mode on PowerPoint that the resolution would change.

Apparently when you use presenter mode with PowerPoint on a Mac it sets the screens in “extended mode” automatically. By default it then seems to optimize for the Mac screen automatically, which usually does not work well for the projector considering most are low resolution devices. I disabled the Presenter Mode option next, and when I turned off presenter mode in PowerPoint it worked fine. You can switch it off in Preferences under Slide Show:

I normally don’t blog about this kind of stuff, but as I hardly was able to find anything useful about it anywhere I figured I would share it with the world.

"Powerpoint for Mac switching resolution?" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.

Posted in mac, powerpoint, resolution, Various | Comments

Insufficient configured resources to satisfy the desired vSphere HA failover level

Advertise here with BSA


I was going over some of the VMTN threads and I noticed an issue brought up with Admission Control a while ago. Completely forgot about it until it was brought up again internally. With vSphere 6.5 and vSphere HA there seems to be a problem with some Admission Control Policies. When you for instance have selected the Percentage Based Admission Control Policy and you have a low number of hosts, you could receive the following error

Insufficient configured resources to satisfy the desired vSphere HA failover level on the cluster …

I managed to reproduce this in my lab, and this is what it looks like in the UI:

It seems to happen when there’s a minor difference in resources between the host, but I am not 100% certain about it. I am trying to figure out internally if it is a known issue or not, and will come back to this when I know in which patch it will be solved and/or if it is indeed a known issue.

 

"Insufficient configured resources to satisfy the desired vSphere HA failover level" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.

Posted in 6.5, ha, Storage, Various, vSphere, vsphere ha | Comments

Insufficient configured resources to satisfy the desired vSphere HA failover level

Advertise here with BSA


I was going over some of the VMTN threads and I noticed an issue brought up with Admission Control a while ago. Completely forgot about it until it was brought up again internally. With vSphere 6.5 and vSphere HA there seems to be a problem with some Admission Control Policies. When you for instance have selected the Percentage Based Admission Control Policy and you have a low number of hosts, you could receive the following error

Insufficient configured resources to satisfy the desired vSphere HA failover level on the cluster …

I managed to reproduce this in my lab, and this is what it looks like in the UI:

It seems to happen when there’s a minor difference in resources between the host, but I am not 100% certain about it. I am trying to figure out internally if it is a known issue or not, and will come back to this when I know in which patch it will be solved and/or if it is indeed a known issue.

 

"Insufficient configured resources to satisfy the desired vSphere HA failover level" originally appeared on Yellow-Bricks.com. Follow me on twitter - @DuncanYB.

Posted in 6.5, ha, Storage, Various, vSphere, vsphere ha | Comments

vCD Extender – Warm Migration Demonstration

This post originally appeared on Clouds, etc. by Daniel Paluszek.

 

Continuation of vCD Extender Setup – Part 1 and Part 2

 

Now you’re ready for your first migration. Going back to my high-level diagram, I will be migrating WebApp2 to the Provider vCD environment and ensuring connectivity is available over the VPN tunnel.

 

Before we start, we can see WebApp1 can ping WebApp2:

 

 

Let’s go to Migrations – Warm Migration:

 

Let’s select WebApp2 – remember, it must be running for a warm migration:

 

 

Selecting the defaults – I only have one network here, so it defaulted to our L2VPN network of “company-network”

 

 

Changing the Target RPO to 5 minutes (this is the fastest RPO currently) and naming the migration job “WebApp2-Migration” – this will start immediately.

 

 

Okay, now we see the job running! Depending on your network connectivity, this will take some time to replicate over the WAN.

So let’s see what happens behind the scenes.

On my provider side, I see my cloud replication instance accepting the incoming replication:

 

 

We can also see on the provider vCenter, a shell VM is substantiated and then removed from inventory. I also see some kind of SSL update to one of the hosts (I presume this is to allow direct replication):

 

 

On the tenant side, I can also see a task in here to enable and start replication of WebApp2:

 

 

While the On-Prem replication instance shows an outbound replication ID:

 

 

OK, initial replication is complete! We are now ready to cut WebApp2 over.

 

 

Back to Workloads subtab -> hit the Start Cutover button

 

 

It will prompt you for the target and you can also choose to power it on after cutover. This is handy if you had multiple VM’s that were ready for cutover, but perhaps not ready to cut them over at the same time.

 

 

Hitting the start button, you are asked one last time if you’re ready to cut over…

 

 

Alright, we are cutting over…

 

 

We can see the pings stop…

 

 

We can see WebApp2 was shut down –

 

 

I start seeing some new tasks on the provider vCenter side…

 

 

Now we also see WebApp2 pop up in vCD –

 

 

Looks like we have power on!

 

 

 

And now waiting a few moments for the VM to fully boot…and we have connectivity! Note that I am double nested here, so this duplicate packet behavior is something I’ve seen with VPN tunnels.

 

 

WebApp1 can see WebApp2, let’s see if it’s the reverse! Yes, we do.

 

 

By my count, this took about 4 minutes from me pushing the button, final synchronization and having network connectivity between my two WebApp servers.

 

I hope to have a demo video next – enjoy setting up vCD Extender and migrating your customers to your vCD Cloud! #longlivevCD

 

Stay tuned to the VMware Cloud Provider Blog for future updates, and be sure to follow @VMwareCloudPrvdon Twitter and ‘like’ us on Facebook.

The post vCD Extender – Warm Migration Demonstration appeared first on VMware Cloud Provider Blog.

Posted in VMware Cloud Provider | Comments