14.12.2016 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

//14.12.2016 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

14.12.2016 – #Mightycare News: Neue #VMware #KnowledgeBase Artikel veröffentlicht

Vom 13.12.2016 bis zum 14.12.2016 wurden 54 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Moving Disk Groups to a new vSAN cluster

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Creating or editing a virtual machine Storage Policy to correct a missing vSAN VASA provider fails

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – Network Health – Hosts disconnected from vCenter Server

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – vSAN HCL Health – vSAN HCL DB up-to-date

Am 14.12.2016 vom Typ: Troubleshooting
Titel: EVO:RAIL vSAN VLAN Troubleshooting

Am 14.12.2016 vom Typ: Troubleshooting
Titel: MySQL DB installation in vRealize Orchestrator 7.2 fails

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Configuring certificates for PSC for High Availability in vSphere 6.5

Am 14.12.2016 vom Typ: Troubleshooting
Titel: View Storage Accelerator not working and causing poor vSAN performance

Am 14.12.2016 vom Typ: Troubleshooting
Titel: VMware ESXi 6.0, Patch ESXi600-201605401-BG: Updates esx-base, vsanhealth, vsan VIBs

Am 13.12.2016 vom Typ: How to, Troubleshooting, Video
Titel: Upgrading vSAN On-Disk format to 3.0 may fail in small vSAN clusters or ROBO/stretched clusters

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Unable to release the acquired trigger and/or clone task stuck in queued state in VMware Horizon DaaS

Am 13.12.2016 vom Typ: How to
Titel: Adding more than 16 hosts to a vSAN cluster

Am 13.12.2016 vom Typ: Video
Titel: vSAN 6.2 on disk upgrade fails at 10%

Am 13.12.2016 vom Typ: Best Practices, How to, Informational
Titel: Horizon View 5.3.1 on VMware vSAN – Quick Start Guide

Am 13.12.2016 vom Typ: Troubleshooting
Titel: USB device splitting rules do not work after a reset port action on the agent machine

Am 13.12.2016 vom Typ: How to, Informational, Troubleshooting
Titel: When attempting to deploy linked clones using VMware vSAN fails with the error: Unable to connect to PBM sub system PB may be down

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Schema Validation errors when upgrading vCenter Server with PostgreSQL

Am 13.12.2016 vom Typ: Informational, Troubleshooting
Titel: Update Manager takes virtual machine snapshot when updating VMware Tools

Am 13.12.2016 vom Typ: How to, Informational
Titel: Recommended settings for RAID0 logical volumes on certain 6G LSI based RAID vSAN

Am 13.12.2016 vom Typ: Troubleshooting
Titel: ESXi host or virtual machine hangs after approximately 85 days

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Dealing with vSAN VIB issues in ESXi 6.0 Update 2 and later releases

Am 13.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – Physical Disk Health – Metadata Health

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Windows 7 virtual machines running on VMware ESXi 6.0 hosts restart unexpectedly

Am 13.12.2016 vom Typ: Troubleshooting
Titel: „Host cannot communicate with all other nodes in virtual SAN enabled cluster“ error

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Preparing Local SSD for use with all-flash vSAN Cluster

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Troubleshooting vSAN SSD congestion on vSphere 5.5

Am 13.12.2016 vom Typ: Troubleshooting
Titel: “Unexpected status code: 503” error in vSAN health check plug-in

Am 13.12.2016 vom Typ: Best Practices
Titel: Best practices when using vSAN and non-vSAN disks with the same storage controller

Am 13.12.2016 vom Typ: Troubleshooting
Titel: vSAN handling of devices detected as snapshots

Am 13.12.2016 vom Typ: Informational
Titel: vSAN 6.1/5.5 Update 3 Disk Groups show as Unmounted in the vSphere Web Client (DDH)

Am 13.12.2016 vom Typ: Troubleshooting
Titel: vSAN 6.2 hybrid disk group performance degradation

Am 13.12.2016 vom Typ: How to, Troubleshooting, Video
Titel: vSAN Providers display the status as disconnected in the vSphere Web Client

Am 13.12.2016 vom Typ: Informational
Titel: Understanding vSAN on-disk format versions

Am 13.12.2016 vom Typ: Best Practices
Titel: VMware vSAN Network Health Check for MTU check fails in a Stretched Cluster

Am 13.12.2016 vom Typ: Alerts, Informational
Titel: Recompose/reprovision of multiple desktops on a pool changes VC health status to RED

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Build numbers and versions of VMware vCenter Server

Am 13.12.2016 vom Typ: Troubleshooting
Titel: VMware ESXi 6.0, Patch ESXi600-201608401-BG: Updates esx-base, vsanhealth, vsan VIBs

Am 13.12.2016 vom Typ: Troubleshooting
Titel: VMware vSAN 6.2 on disk upgrade fails due to CBT enabled virtual disks

Am 13.12.2016 vom Typ: Troubleshooting
Titel: „Failed to clean up VKS binaries, Error: 2“ error when installing vCenter Server 6.5

Am 13.12.2016 vom Typ: Informational, Troubleshooting
Titel: The vpxd service fails to start if the service uses an account with hostnameusername format

Am 13.12.2016 vom Typ: Troubleshooting
Titel: „Internal error occurs during execution of upgrade process“ error when upgrading to vCenter Server Appliance 6.5

Am 13.12.2016 vom Typ: Troubleshooting
Titel: “Encountered login error. Subsequent connection attempt failed: 28000” error in vCenter Server 6.0

Am 13.12.2016 vom Typ: Troubleshooting
Titel: „Exception: Failed to configure identity manager“ error when upgrading to vCenter Server 6.5

Am 13.12.2016 vom Typ: How to
Titel: Windows 10 support fo App Volumes 2.12

Am 13.12.2016 vom Typ: Troubleshooting
Titel: vSAN Performance service is not enabled after upgrading the VMware Virtual SAN to 6.2.x

Am 13.12.2016 vom Typ: Troubleshooting
Titel: vRealize Operations for Horizon Broker Agent Configuration Utility Will Not Start

Am 13.12.2016 vom Typ: Troubleshooting
Titel: [Internal] VIO 3.0 – Horizon shows ’no data available‘ in Resources Usage Overview

Am 13.12.2016 vom Typ: Troubleshooting
Titel: „Replace a process level token‘ privilege“ error during Pre-Check when migrating to vCenter Server 6.5

Am 13.12.2016 vom Typ: Troubleshooting
Titel: „Migration process failed halfway“ error in vRealize Business for Cloud 7.01

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Data Collection fails for vRealize Automation Adapter Instance in vRealize Operations Manager 6.x

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Interacting with the VMware Update Manager 6.5 embedded vPostgres Database

Am 13.12.2016 vom Typ: How to
Titel: How to generate range of monthly reports from vCloud Usage Meter CLI

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Configuring certificates for Windows Platform Services Controller for High Availability in vSphere 6.55

Am 13.12.2016 vom Typ: Troubleshooting
Titel: Interacting with the vCenter Server Appliance 6.5 embedded vPostgres Database

Ausführliche Auflistung:

Titel: Moving Disk Groups to a new vSAN cluster

Knowledgebase Nr: 2073931

Aktualisiert: 14.12.2016

Für Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2073931

Beschreibung:
Moving a vSAN (formerly known as Virtual SAN) disk group from an existing vSAN cluster to a newly created vSAN cluster without decommissioning the disk group, automatically adds the original disk groups to the new cluster. This capability works on HBAs, passthrough controllers, and RAID controllers with write-back cache mode disabled. You cannot use disks that are already moved to a new cluster for creating a new disk group.Note that, vSAN has the capability to read metadata from the disks and…
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating or editing a virtual machine Storage Policy to correct a missing vSAN VASA provider fails

Knowledgebase Nr: 2075838

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2075838

Beschreibung:
The vSAN VASA provider is not listed in VMware vSAN 5.5. You cannot create a Storage Policy due to the unlisted vSAN VASA. You cannot edit existing Storage Policies on the virtual machine.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – Network Health – Hosts disconnected from vCenter Server

Knowledgebase Nr: 2108004

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.0.x

Link zum Artikel: 2108004

Beschreibung:
This article explains the Network Health – Hosts disconnected from vCenter check in the vSAN (formerly known as Virtual SAN) Health Service and provides details on why it might report an error.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – vSAN HCL Health – vSAN HCL DB up-to-date

Knowledgebase Nr: 2109870

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.0.x, VMware vSAN 6.1.x, VMware vSAN 6.2.x

Link zum Artikel: 2109870

Beschreibung:
This article explains the vSAN HCL Health – vSAN HCL DB up-to-date check in the vSAN Health Service and provides details on why it might report an error.Adherence to the VMware Compatibility Guide (VCG)/Hardware Compatibility Guide (HCL) is critically important to the stability of vSAN environments. Experience has shown that failing to observe the VCG often leads to production outages over time. It is, therefore, very important to monitor the health checks in the HCL checker category. For more…
… Für weitere Details den Link zum Artikel anklicken

Titel: EVO:RAIL vSAN VLAN Troubleshooting

Knowledgebase Nr: 2118997

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Link zum Artikel: 2118997

Beschreibung:
EVO:RAIL requires a vSAN VLAN on your switch that is configured with IPv4 multicasting. When it is not working properly, you experience these symptoms: EVO:RAIL Management displays the total disk size for the MARVIN-Virtual-SAN-Datastorexxxx to be 3.35 TB of space. A single EVO:RAIL appliance should show 13.1 TB of space for the MARVIN-Virtual-SAN-Datastorexxxx. vSphere Web Client displays this error in the Network Status field for Virtual SAN:Misconfiguration Detected
… Für weitere Details den Link zum Artikel anklicken

Titel: MySQL DB installation in vRealize Orchestrator 7.2 fails

Knowledgebase Nr: 2148277

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vRealize Orchestrator 7.2.x

Link zum Artikel: 2148277

Beschreibung:
Issuing workflow to add new MySQL DB in vRealize Orchestrator 7.2 release with error:item: ‚Add a database/item2‘, state: ‚failed‘, business state: ’null‘, exception: ‚java.lang.IllegalArgumentException: The driver ‚com.mysql.jdbc.Driver‘ for ‚MySQL‘ database cannot be found! (Dynamic Script Module name : addDatabase#8)’workflow: ‚Add a database‘ (18541090831854109083178946495518541090830101010101010101010101010)| ‚attribute‘: name=errorCode type=string…
… Für weitere Details den Link zum Artikel anklicken

Titel: Configuring certificates for PSC for High Availability in vSphere 6.5

Knowledgebase Nr: 2147627

Aktualisiert: 14.12.2016

Für Produkte: VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2147627

Beschreibung:
This article provides information on creating certificates to use in configuring Platform Service Controller High Availability.
… Für weitere Details den Link zum Artikel anklicken

Titel: View Storage Accelerator not working and causing poor vSAN performance

Knowledgebase Nr: 2115001

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware Horizon 6 version 6.1.x, VMware Horizon View 5.3.x, VMware View 6.0.x

Link zum Artikel: 2115001

Beschreibung:
There are circumstances when you enable View Storage Accelerator (VSA) using View Administrator and encounter no error. VSA should in turn enable the Content Based Read Cache (CBRC) feature on ESXi hosts. However, CBRC is not enabled, as evidenced by the absence of digest files for the desktop VMs. With CBRC disabled, vSAN performance will be poor because of slower disk access. This problem can occur in the following cases: 1. The desktop VMs are not powered off when you enable VSA. 2. When…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware ESXi 6.0, Patch ESXi600-201605401-BG: Updates esx-base, vsanhealth, vsan VIBs

Knowledgebase Nr: 2144685

Aktualisiert: 14.12.2016

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2144685

Beschreibung:
Release date: May 12, 2016 Patch Category Bugfix Patch Severity Critical Build For build information, see KB 2136186. Host Reboot Required Yes Virtual Machine Migration or Shutdown Required Yes Affected Hardware N/A Affected Software N/A VIBs Included VMware:esx-base:6.0.0-2.37.3825889 VMware:vsanhealth:6.0.0-3000000.3.0.2.37.3825892 VMware:vsan:6.0.0-2.37.3825891 PRs Fixed 1611463, 1616775, 1626050, 1626789, 1626948, 1636418, 1632784 Related CVE numbers NA
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading vSAN On-Disk format to 3.0 may fail in small vSAN clusters or ROBO/stretched clusters

Knowledgebase Nr: 2144944

Kategorie: How to, Troubleshooting, Video

Aktualisiert: 13.12.2016

Link zum Artikel: 2144944

Beschreibung:
Attempting an on-disk upgrade in certain vSAN configurations may result in failure. Configurations that can cause these errors are: The stretched vSAN Cluster consists of two ESXi Hosts and the Witness Node (ROBO configuration) Each Host in the Stretched Cluster contains a single vSAN Disk Group A vSAN cluster consists of three normal nodes, with one disk group per node A vSAN cluster is very full, preventing the „full data migration“ disk-group decommission mode On-disk upgrade failures…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to release the acquired trigger and/or clone task stuck in queued state in VMware Horizon DaaS

Knowledgebase Nr: 2100111

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Link zum Artikel: 2100111

Beschreibung:
Cannot release acquired trigger and/or clone task stuck in queued state. In the VMware Horizon DaaS tenant log, you see entries similar to: 2011-04-26 06:50:52,488 ERROR [org.quartz.core.ErrorLogger]-[dtScheduler_QuartzSchedulerThread] An error occured while releasing trigger ‚DEFAULT.queuedTaskSchedulerSimpleTrigger’org.quartz.JobPersistenceException: Couldn’t release acquired trigger: ERROR: could not read block 2 of relation 1663/16386/16859: read only 0 of 8192 bytes [See nested…
… Für weitere Details den Link zum Artikel anklicken

Titel: Adding more than 16 hosts to a vSAN cluster

Knowledgebase Nr: 2073930

Kategorie: How to

Aktualisiert: 13.12.2016

Für
Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2073930

Beschreibung:
You can create a new vSAN cluster with 16 or more hosts.
… Für weitere Details den Link zum Artikel anklicken

Titel:
vSAN 6.2 on disk upgrade fails at 10%

Knowledgebase Nr: 2144881

Kategorie: Video

Aktualisiert: 13.12.2016

Für
Produkte: VMware vSAN 6.2.x

Link zum Artikel: 2144881

Beschreibung:
When upgrading VMware vSAN to version 6.2, the vSAN Disk Format Conversion task fails at 10%. In the vSphere Web Client, you see an error similar to:A general system error occurred: Failed to realign following Virtual
SAN objects: <uuid list>, due to being locked or lack of vmdk descriptor file which requires manual fix The Convert disk format for vSAN task fails with a General Virtual SAN error status. Note: For additional symptoms and log entries, see the Additional Information…

Für weitere Details den Link zum Artikel anklicken

Titel: Horizon View 5.3.1 on VMware vSAN – Quick Start Guide

Knowledgebase Nr: 2073795

Kategorie: Best Practices, How to, Informational

Aktualisiert: 13.12.2016

Für Produkte: VMware Horizon View 5.3.x

Link zum Artikel: 2073795

Beschreibung:
Overview VMware vSAN is a software-defined storage technology that is available with vSphere 5.5 Update 1 (or later). vSAN is a core component of vSphere that aggregates local
server-attached storage (local storage on a vSphere host/server) and provides a datastore that is visible to all hosts within a vSphere cluster. VMware vSAN is optimized for use with Horizon
View 5.3.1 and provides the following benefits: High-performance storage with automatic caching Storage policy based management,…
… Für weitere Details den Link zum Artikel anklicken

Titel: USB device splitting rules do not work after a reset port action on the agent machine

Knowledgebase Nr: 2148239

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Link
zum Artikel: 2148239

Beschreibung:
You can configure USB policies for both the remote desktop or application (Horizon Agent) and Horizon Client. These policies specify whether the client device should split composite USB devices into separate components for redirection. You can split devices to restrict the types of USB devices that the
client
makes available for redirection, and to make Horizon Agent prevent certain USB devices from being forwarded from a client computer. If you configure a USB…
… Für weitere Details den Link zum Artikel anklicken

Titel: When attempting to deploy linked clones using VMware vSAN fails with the error: Unable to connect to PBM sub system PB may be down

Knowledgebase Nr: 2094412

Kategorie: How to, Informational, Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware View 6.0.x

Link zum Artikel: 2094412

Beschreibung:
Attempting to deploy linked clones using vSAN (formerly known as Virtual
SAN) fails You see the error:Unable to connect
to PBM subsystem PB may be down Alternatively, you may see this or a similar View Administrator error at the pool level:Error during provisioning: Unable to automatically reconnect to PBM subsystem. The VC might be possibly down.
… Für weitere Details den Link zum Artikel anklicken

Titel: Schema Validation errors when upgrading vCenter Server with PostgreSQL

Knowledgebase Nr: 2147952

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2147952

Beschreibung:
Upgrading vCenter Server with a PostgreSQL database fails with the error:Source vCenter Server schema validation found an issue. Resolution:
Read the vcdb_req.err log
file and address the issues found“ In the VMware-VCS-logs-timestamp_number/vcsUpgrade/vcdb_req.err log file is empty. In the VMware-VCS-logs-timestamp_number/vcsUpgrade/UpgradeRunner.log file, you see entries similar to:ERROR vcdb.const Error while validating source vCenter Server database: Error while executing…
… Für weitere Details den Link zum Artikel anklicken

Titel: Update Manager takes virtual machine snapshot when updating VMware Tools

Knowledgebase Nr: 2146592

Kategorie: Informational, Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Update Manager 6.0.x

Link zum Artikel: 2146592

Beschreibung:
When using
Update Manager to schedule a VMware Tools update on next Virtual Machine power cycle, a snapshot is taken of the Virtual Machines being configured, immediately after
the Wizard has exited.Snapshots were being taken when they shouldn’t be.This issue is only seen when using the Update Manager plugin in the Web Client.
… Für weitere Details den Link zum Artikel anklicken

Titel: Recommended settings for RAID0 logical volumes on certain 6G LSI based RAID vSAN

Knowledgebase Nr: 2111266

Kategorie: How to, Informational

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 5.5.x, VMware vSAN 6.0.x, VMware vSAN 6.1.x, VMware vSAN 6.2.x

Link zum Artikel: 2111266

Beschreibung:
This article outlines recommendations for creating RAID0 logical volumes on vSAN compatible controllers. VMware recommends specific settings
when creating RAID0 logical volumes on these controllers: MegaRAID SAS 9271-8i UCS-RAID9271CV-8I MegaRAID SAS 9265-8i MegaRAID SAS 9266-8i MegaRAID SAS 9267-8i MegaRAID SAS 9266-4i MegaRAID SAS 9270-8i MegaRAID SAS 9272-8i MegaRAID SAS 9270CV-8i MegaRAID SAS 9271-8iCC MegaRAID SAS 9271-4i SMC2208 PERC H710 mini Adapter PERC H710P Adapter …
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host or virtual machine hangs after approximately 85 days

Knowledgebase Nr: 2147739

Aktualisiert: 13.12.2016

Für Produkte: VMware ESXi 5.5.x,
VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 2147739

Beschreibung:
ESXi 5.5 and 6.x hosts hang after running for 85 days. In the /var/log/vmkernel log file, you see entries similar to:YYYY-MM-DDTHH:MM:SS.833Z cpu58:34255)qlnativefc: vmhba2(5:0.0): Recieved a PUREX
IOCB woh ooYYYY-MM-DDTHH:MM:SS.833Z cpu58:34255)qlnativefc: vmhba2(5:0.0): Recieved the PUREX IOCB.YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674)qlnativefc: vmhba2(5:0.0): sizeof(struct rdp_rsp_payload) = 0x88YYYY-MM-DDTHH:MM:SS.833Z cpu58:33674qlnativefc: vmhba2(5:0.0): transceiver_codes[0] =…
… Für weitere Details den Link zum Artikel anklicken

Titel: Dealing with vSAN VIB issues in ESXi 6.0 Update 2 and later releases

Knowledgebase Nr: 2144595

Aktualisiert: 13.12.2016

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2144595

Beschreibung:
With the introduction of vSAN (formerly known as Virtual SAN) 6.2 along with ESXi 6.0 Update 2 release, a new VIB called vsan.vib is shipped.The new vsan VIB has a close dependency with the esx-base and the vsanhealth VIBs. As a result of this, a tight coupling is being introduced between the esx-base, the vsan and the vsanhealth VIBs to maintain them in lock-step from ESXi 6.0 Update 2 release onwards.Due to this new lock-step being introduced between these VIBS, there are some expected…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – Physical Disk Health – Metadata Health

Knowledgebase Nr: 2108690

Kategorie: Informational, Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 6.0.x

Link zum Artikel: 2108690

Beschreibung:
This article explains the Physical Disk Health – Metadata Health check in the vSAN Health Service, and provides details on why it might report an error.
… Für weitere Details den Link zum Artikel anklicken

Titel: Windows 7 virtual machines running on VMware ESXi 6.0 hosts restart unexpectedly

Knowledgebase Nr: 2117244

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2117244

Beschreibung:
Windows 7 virtual machine restarts unexpectedly when running on ESXi 6.0 hosts. In the /var/log/vmkwarning.log, you see entries similar to: <YYYY-MM-DD>T<TIME> cpu3:255920)WARNING: World: vm 255903: 12276: vmm0:VDI-STD-005:vmk:vcpu-0:p2m update buffer full <YYYY-MM-DD>T<TIME> cpu3:255920)WARNING: VmMemPf: vm 255903: 652: COW copy failed: pgNum=0x3d108, mpn=0x3fffffffff <YYYY-MM-DD>T<TIME> cpu3:255920)WARNING: VmMemPf: vm 255903: 2626: PhysPageFault…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Host cannot communicate with all other nodes in virtual SAN enabled cluster“ error

Knowledgebase Nr: 2143214

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 6.1.x

Link zum Artikel: 2143214

Beschreibung:
When a host in the vSAN cluster running on vSphere 6.0 Update 1b is down for maintenance, the ESXi hosts in the cluster report the error:Host cannot communicate with all other nodes in virtual SAN enabled cluster After the node(s) reboots and rejoins the cluster, the message does not clear automatically. This message appears in the Summary tab in the vSphere Web Client and the ESXi host shows a notification triangle, though no alarms are triggered.Note: For additional symptoms and log entries,…
… Für weitere Details den Link zum Artikel anklicken

Titel: Preparing Local SSD for use with all-flash vSAN Cluster

Knowledgebase Nr: 2120252

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 6.0.x

Link zum Artikel: 2120252

Beschreibung:
Unable to see SSD as „eligible disks“ for use with all-flash vSAN environment when 2 or more SSD are present. Trying to configure all-flash based vSAN cluster. Unable to create disk groups exclusively with local SSD drives in an vSphere 6 environment.
… Für weitere Details den Link zum Artikel anklicken

Titel: Troubleshooting vSAN SSD congestion on vSphere 5.5

Knowledgebase Nr: 2119043

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2119043

Beschreibung:
A vSAN cluster experiences write congestion that cannot be readily explained by the workload size/write intensiveness. This congestion can manifest as latency alarms, virtual machines unavailability/inaccessibility and hosts disconnecting from vCenter Server. In the var/log/clomd.log file or var/log/vmkernel.log file, you see entries similar to: <YYYY-MM-DD>t<tTME>Z cpu37:32519726)LSOM: LSOM_ThrowCongestionVOB:2064: VSAN Node: 532dcc8c-b0ee-de82-64b8-38eaa7104cf0 Maximum SSD…
… Für weitere Details den Link zum Artikel anklicken

Titel: “Unexpected status code: 503” error in vSAN health check plug-in

Knowledgebase Nr: 2128353

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server Appliance 6.0.x, VMware vSAN 6.0.x

Link zum Artikel: 2128353

Beschreibung:
When replacing vCenter Server with the SSL certificate Automation tool, you experience these symptoms: If the VMware vSAN (formerly known as Virtual SAN) Health Check plug-in is deployed and working correctly, you see these symptoms: The vSphere Web Client screen for the vSAN Health Check plug-in displays an error similar to:Unexpected status code: 503 org.apache.http.client.ClientProtocolException In the /storage/log/vmware/vsan-health/vmware-vsan-health-service.log file, you see an entry…
… Für weitere Details den Link zum Artikel anklicken

Titel: Best practices when using vSAN and non-vSAN disks with the same storage controller

Knowledgebase Nr: 2129050

Kategorie: Best Practices

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 5.5.x, VMware vSAN 6.0.x, VMware vSAN 6.1.x, VMware vSAN 6.2.x, VMware vSAN 6.5.x

Link zum Artikel: 2129050

Beschreibung:
This article provides best practices when both VMware vSAN (formerly known as Virtual SAN) and non-vSAN disks are attached to the same storage controller. Notes: The physical storage aspects such as vSAN disks managing IO, retries, and fault declaration are managed differently when the same elements are handled by non-vSAN workloads. This applies only in circumstances where the non-vSAN disks are attached to the same storage controller as the vSAN disks.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN handling of devices detected as snapshots

Knowledgebase Nr: 2129058

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 5.5.x, VMware vSAN 6.0.x

Link zum Artikel: 2129058

Beschreibung:
One or more disks used by vSAN (SSD or HDD) is detected as a snapshot. In the vmkernel.log file, you see entries similar to: 2015-08-05T04:15:18.251Z cpu76:34712 opID=ec55b0cc)LVM: 8389: Device naa.600508b1001cb554d9ac87eb1c070895:2 detected to be a snapshot: The disk or disk group is present in the vSphere Web Client, but all components or objects on those disks are in an ABSENT state. The overall capacity of the vSAN Datastore is smaller than expected, despite all disks appearing as…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN 6.1/5.5 Update 3 Disk Groups show as Unmounted in the vSphere Web Client (DDH)

Knowledgebase Nr: 2132079

Kategorie: Informational

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 5.5.x, VMware vSAN 6.1.x

Link zum Artikel: 2132079

Beschreibung:
When running VMware vSAN (formerly known as Virtual SAN ) versions 6.1/5.5 Update 3, you experience one or more of these symptoms: In the vSphere Web Client, under Disk Management for the vSAN Cluster, vSAN Disk Groups or disk group members show unmounted and are greyed-out. Virtual machines and objects stored in the vSAN cluster become unavailable. When you run esxcli vsan storage list from the ESXi shell, disks may report: In CMMDS: false In the /var/log/vmkernel.log file on the ESXi…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN 6.2 hybrid disk group performance degradation

Knowledgebase Nr: 2146267

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 6.2.x

Link zum Artikel: 2146267

Beschreibung:
After upgrading a vSAN (Formerly known as Virtual SAN) environment with Hybrid disk groups to version 6.2, some virtual machines resident on vSAN datastores may exhibit poor disk IO performance compared to previous versions of vSAN.For example, Virtual Machine Read and/or Write IOs may have poor response time than on vSAN 6.1 or vSAN 6.0. A significantly lower than expected read cache hit ratio is observed on vSAN caching tier. A higher percentage of IOPS may be observed on capacity tier…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Providers display the status as disconnected in the vSphere Web Client

Knowledgebase Nr: 2126810

Kategorie: How to, Troubleshooting, Video

Aktualisiert: 13.12.2016

Für Produkte: VMware ESXi 6.0.x, VMware vCenter Server 6.0.x, VMware vCenter Server Appliance 6.0.x

Link zum Artikel: 2126810

Beschreibung:
vSAN Providers display status as disconnected (To see this in the vSphere Web Client, navigate to vCenter Server > Manage > Storage Providers.). A resynchronization operation fails to refresh the connection status. In the /var/log/vsanvpd.log file, you see entries similar to:vsanvpd.log: 2015-04-27T00:39:42Z vsanSoapServer: ssl_verify_cert:759:ssl_verify_cert: client certificate not presentedvsanvpd.log: error:14094416:SSL routines:SSL3_READ_BYTES:sslv3 alert certificate…
… Für weitere Details den Link zum Artikel anklicken

Titel: Understanding vSAN on-disk format versions

Knowledgebase Nr: 2145267

Kategorie: Informational

Aktualisiert: 13.12.2016

Link zum Artikel: 2145267

Beschreibung:
This article outlines all vSAN on-disk format versions, their purposes, and alternate version numbers where applicable. vSAN has several different on-disk format versions available depending on the version and upgrade history of the cluster. Some on-disk format versions are transient while some are intended for long-term production. Important: There can be some deviation between the on-disk format version displayed in the vSphere Web Client and the version displayed during command-line…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN Network Health Check for MTU check fails in a Stretched Cluster

Knowledgebase Nr: 2141733

Kategorie: Best Practices

Aktualisiert: 13.12.2016

Link zum Artikel: 2141733

Beschreibung:
When you have a VMware vSAN Stretched Cluster setup where vSAN Data nodes have MTU of 9000 and the Witness host/appliance is placed across the WAN which has a MTU limit of 1500, you experience these symptoms: vSAN Network Health Check for MTU check in a Stretched Cluster fails vSAN Network Health status shows that the Hosts large ping test (MTU check) has failed
… Für weitere Details den Link zum Artikel anklicken

Titel: Recompose/reprovision of multiple desktops on a pool changes VC health status to RED

Knowledgebase Nr: 2147660

Kategorie: Alerts, Informational

Aktualisiert: 13.12.2016

Für Produkte: VMware Horizon 7 version 7.0.x

Link zum Artikel: 2147660

Beschreibung:
In view admin page the vCenter Server service status turns to Red.You see errors similar to:service is not working properly OR For self-signed certificate, click ‚Verify‘. If the vCenter Server certificate can be validated, make sure that the trusted store on the Connection Server system has the correct Certification Authorities.In DriveLetter:ProgramDataVMwareVDMlogs, You see entries similar to: <VCHealthUpdate> [CertMatchingTrustManager] invalid certificate (as expected) for…
… Für weitere Details den Link zum Artikel anklicken

Titel: Build numbers and versions of VMware vCenter Server

Knowledgebase Nr: 2143838

Aktualisiert: 13.12.2016

Link zum Artikel: 2143838

Beschreibung:
This table lists the vCenter Server build numbers and versions: Version Release Date Build Number Installer Build Number vCenter Server 6.5 GA 2016-11-15 4602587 N/A vCenter Server 6.0 Update 2a 2016-11-22 4541947 4637290 vCenter Server 6.0 Update 2 2016-03-16 3634793 3634788 vCenter Server 6.0 Update 1b 2016-01-07 3339083 3343019 vCenter Server 6.0 Update 1 2015-09-10 3018524 3040890 vCenter Server 6.0.0b 2015-07-07 2776511 2800571 vCenter Server 6.0.0a 2015-04-16 2656760 2656757…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware ESXi 6.0, Patch ESXi600-201608401-BG: Updates esx-base, vsanhealth, vsan VIBs

Knowledgebase Nr: 2145664

Aktualisiert: 13.12.2016

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2145664

Beschreibung:
Release date: Aug 4, 2016 Patch Category Bugfix Patch Severity Critical Build For build information, see KB 2145663. Host Reboot Required Yes Virtual Machine Migration or Shutdown Required Yes Affected Hardware N/A Affected Software N/A VIBs Included VMware:esx-base:6.0.0-2.43.4192238 VMware:vsanhealth:6.0.0-3000000.3.0.2.43.4064824 VMware:vsan:6.0.0-2.43.4097166 PRs Fixed 912743, 1390800, 1464308, 1464736, 1492308, 1503784, 1509011, 1569235, 1570739, 1584180, 1584677,…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN 6.2 on disk upgrade fails due to CBT enabled virtual disks

Knowledgebase Nr: 2144882

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 6.0.x, VMware vSAN 6.1.x, VMware vSAN 6.2.x

Link zum Artikel: 2144882

Beschreibung:
Attempting to upgrade vSAN to version 6.2 fails during the on disk upgrade process with errors relating to Changed Block Tracking (CBT) enabled virtual machine disks. The vSAN Disk Format Conversion task fails at 10%. The Convert disk format for vSAN task fails with a General Virtual SAN error. status. Note: For additional symptoms and log entries, see the Additional Information section.
… Für weitere Details den Link zum Artikel anklicken

Titel: „Failed to clean up VKS binaries, Error: 2“ error when installing vCenter Server 6.5

Knowledgebase Nr: 2148056

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2148056

Beschreibung:
Installing vCenter Server 6.5 fails with the error:An error occurred while starting service ‚VMwareDNSService’Failed to clean up VKS binaries, Error: 2Installation of component VCSServiceManager failed with error code 1603In the vmafd-firstboot.py_PID_stderr.log file. you see:“An error occurred while starting service ‚VMwareDNSService'“,Note: The vmafd-firstboot.py_PID_stderr.log file is located at the VMware-VCS-logs Date_TIME.zip file created on vCenter Server after the upgrade failure.There…
… Für weitere Details den Link zum Artikel anklicken

Titel: The vpxd service fails to start if the service uses an account with hostnameusername format

Knowledgebase Nr: 2147960

Kategorie: Informational, Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2147960

Beschreibung:
When upgrading or installing vCenter Server with a local user account in the HostnameUsername format, you experience these symptoms:In the %TEMP%vminst.log file, there are entries similar to:2016-11-16 11:08:04.709+09:00| vcsInstUtil-4602587| I: ParseStatusFile: curr error msg: „The installation of vCenter Server failed due to an internal error.“2016-11-16 11:08:04.709+09:00| vcsInstUtil-4602587| E: ParseStatusFile: Displaying error message for „VMware vCenter Server“: „The installation of…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Internal error occurs during execution of upgrade process“ error when upgrading to vCenter Server Appliance 6.5

Knowledgebase Nr: 2147933

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2147933

Beschreibung:
vCenter Server upgrade fails with the error:ErrorInternal error occurs during execution of upgrade process.ResolutionSend upgrade log files to VMware technical support team for further assistance.In the /var/log/vmware/upgrade/bootstrap.log file on the destination vCenter Server Appliance, there are entries similar to:2016-11-17T22:32:48.457Z INFO ssh_utils Local directory /usr/lib/vmware/cis_upgrade_runner has been successfully uploaded to…
… Für weitere Details den Link zum Artikel anklicken

Titel: “Encountered login error. Subsequent connection attempt failed: 28000” error in vCenter Server 6.0

Knowledgebase Nr: 2147904

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2147904

Beschreibung:
Unable to login to the vCenter Server service after updating the SQL user. In the C:ProgramDataVMwareVMware VirtualCenterLogsvpxd.log file, you see entries similar to:YYYY-MM-DD T TIME.228-05:00 warning vpxd[04532] [Originator@6876 sub=VpxProfiler] ServerApp::Init [TotalTime] took 10104 msYYYY-MM-DD T TIME.228-05:00 error vpxd[04532] [Originator@6876 sub=Default] Failed to intialize VMware VirtualCenter. Shutting down…YYYY-MM-DD T TIME.228-05:00 info vpxd[04532] [Originator@6876…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Exception: Failed to configure identity manager“ error when upgrading to vCenter Server 6.5

Knowledgebase Nr: 2148200

Aktualisiert: 13.12.2016

Für Produkte:
VMware vCenter Server 6.5.x

Link zum Artikel: 2148200

Beschreibung:
Upgrading to vCenter Server 6.5 fails with this error:Encountered an internal error.  Traceback (most recent call last):   File „D:Program FilesVMwarevCenter Serverfirstbootvmidentity-firstboot.py“, line
2018, in main     vmidentityFB.boot()   File „D:Program FilesVMwarevCenter Serverfirstbootvmidentity-firstboot.py“, line 347, in boot     self.configureIdentityManager(self.__idmRetryCount, self.__idmRetryInterval)   File „D:Program FilesVMwarevCenter Serverfirstbootvmidentity-firstboot.p „,…
… Für weitere Details den Link zum Artikel anklicken

Titel: Windows 10 support fo App Volumes 2.12

Knowledgebase Nr: 2148177

Kategorie: How to

Aktualisiert: 13.12.2016

Für
Produkte: VMware App Volumes 2.12.x

Link zum Artikel: 2148177

Beschreibung:
This article describes how to use App Volumes 2.12 in combination with Windows 10 Anniversary Update in a non-persistent VDI environment. This article is specifically targeted at non-persistent VDI environments
running Windows 10 and contains tuning tips for optimizing the performance and user experience. App Volumes
2.12 is only supported on the below or higher build version of Windows 10:    November 8, 2016 (OS Build 14393.447)   For more information, see: The Microsoft Knowledge Base…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Performance service is not enabled after upgrading the VMware Virtual SAN to 6.2.x

Knowledgebase Nr: 2145179

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vSAN 6.2.x

Link zum Artikel: 2145179

Beschreibung:
After upgrading to VMware vSAN (formerly known as Virtual SAN) 6.2.x, you experience these symptoms: In the vSAN health Check plugin, you see the warning:Warning on ‚Stats DB object‘

Für weitere Details den Link zum Artikel anklicken

Titel: vRealize Operations for Horizon Broker Agent Configuration Utility Will Not Start

Knowledgebase Nr: 2147533

Aktualisiert: 13.12.2016

Link
zum Artikel: 2147533

Beschreibung:
vRealize Operations for Horizon Broker Agent Configuration Utility fails to launch.In the Broker Agent logs, you see the entries similar to:VMware vRealize Operations for Horizon Broker Agent failed to initialize. @OnLoadException details : Index was outside the bounds of the array.   at ViewBrokerAgentConfigUtil.BrokerConfigurationManager.Init()
… Für weitere Details den Link zum Artikel anklicken

Titel: [Internal] VIO 3.0 – Horizon shows ’no data available‘ in Resources Usage Overview

Knowledgebase Nr: 2148027

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware Integrated OpenStack 3.0.x

Link zum Artikel: 2148027

Beschreibung:
Horizon shows no data available error in Resources Usage Overview
… Für weitere Details den Link zum Artikel anklicken

Titel: „Replace a process level token‘ privilege“ error during Pre-Check when migrating to vCenter Server 6.5

Knowledgebase Nr: 2148010

Kategorie: Troubleshooting

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server 6.5.x, VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2148010

Beschreibung:
When migrating a vCenter Server 6.0 installed on Windows to the vCenter Server Appliance 6.5, pre-check fails with the error:User running the upgrade does not have ‚Replace a process level token‘ privilegeIn the runner.log file, you see entries similar to:“requirementMismatchSpecs“: [{ „text“: { „id“: „common.error.windows.missing_privilege.text“, „localized“: „User running the upgrade does not have ‚Replace a process level token‘ privilege.“, „translatable“: „User running
the upgrade does…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Migration process failed halfway“ error in vRealize Business for Cloud 7.01

Knowledgebase Nr: 2145404

Aktualisiert: 13.12.2016

Für Produkte: VMware
vRealize Business for Cloud Advanced
7.x, VMware vRealize Business for Cloud Standard 7.x

Link zum Artikel: 2145404

Beschreibung:
When you have deployed a new vRealize Business for Cloud 7.01 Standard appliance and connected to VAMI appliance, you experience these symptoms:From
Migrator tab, migrating the data from old vRealize Business for Cloud appliance to the new vRealize Business for Cloud 7.01 fails.You see the error:“Migration process failed halfway. Please revert the snapshot of vRB and try again“
… Für weitere Details den Link zum Artikel anklicken

Titel: Data Collection fails for vRealize Automation Adapter Instance in vRealize Operations Manager 6.x

Knowledgebase Nr: 2147537

Kategorie: Troubleshooting

Aktualisiert:
13.12.2016

Für Produkte: VMware vRealize Operations Manager 6.1.x, VMware vRealize Operations Manager 6.2.x, VMware vRealize Operations Manager 6.3.x

Link zum Artikel: 2147537

Beschreibung:
Data Collection
fails for vRealize Automation Adapter Instance in vRealize Operations Manager, you see the error:Collection
succeeded, but with some errors. Please check logs for detailsIn the /storage/log/vcops/log/adapters/VCACAdapter/VCACAdapter.log file, you see the entries similar to:ERROR [pool-4039-thread-1] (12036) com.vmware.adapter3.vcac.util.WAPIWorkItem.call – Error collecting for VirtualMachine index 0: 42000 : is not a valid value for Int32.In the C:Program Files…
… Für weitere Details den Link zum Artikel anklicken

Titel: Interacting with the VMware Update Manager 6.5 embedded vPostgres Database

Knowledgebase Nr: 2147300

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2147300

Beschreibung:
This article explains how to connect to the embedded VMware Update Manager vPostgres Database of a vCenter Server Appliance 6.5. Caution: Ensure you have working backups and/or snapshots of the vCenter Server Appliance 6.5 before interacting with the embedded VMware Update Manager 6.5 Database.
… Für weitere Details den Link zum Artikel anklicken

Titel: How to generate range of monthly reports from vCloud Usage Meter CLI

Knowledgebase Nr: 2145490

Kategorie: How to

Aktualisiert: 13.12.2016

Für Produkte: VMware vCloud Usage Meter 3.3.x

Link zum Artikel: 2145490

Beschreibung:
This article provides steps to generate a report with more than one month of data or a specific date range in VMware vCloud Usage Meter.
… Für weitere Details den Link zum Artikel anklicken

Titel: Configuring certificates for Windows Platform Services Controller for High Availability in vSphere 6.55

Knowledgebase Nr: 2147626

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2147626

Beschreibung:
This article contains information on creating certificates to use in configuring Platform Service Controller High Availability.
… Für weitere Details den Link zum Artikel anklicken

Titel: Interacting with the vCenter Server Appliance 6.5 embedded vPostgres Database

Knowledgebase Nr: 2147285

Aktualisiert: 13.12.2016

Für Produkte: VMware vCenter Server Appliance 6.5.x

Link zum Artikel: 2147285

Beschreibung:
The article provide steps to connect to the embedded vPostgres Database of a vCenter Server Appliance 6.5. Caution: Ensure you have working backups and/or snapshots of the vCenter Server Appliance 6.5 before interacting with the vCenter Server Appliance 6.5 Database.
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2016-12-14T11:32:58+00:00Dezember 14th, 2016|Knowledgebase|
Um unsere Webseite für Sie optimal zu gestalten und fortlaufend verbessern zu können, verwenden wir Cookies. Durch die weitere Nutzung der Webseite stimmen Sie der Verwendung von Cookies zu. Weitere Informationen zu Cookies erhalten Sie in unserer Datenschutzerklärung. Sie können die Erfassung Ihrer Daten durch Google Analytics verhindern, indem Sie auf folgenden Link klicken. Es wird ein Opt-Out-Cookie gesetzt, der die Erfassung Ihrer Daten bei zukünftigen Besuchen dieser Website verhindert. Weitere Einstellungen Ok

Google Analytics deaktivieren

Verbiete Google Analytics, mich zu verfolgen