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

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

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

Vom 17.02.2017 bis zum 18.02.2017 wurden 37 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 17.02.2017 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 17.02.2017 vom Typ: How to, Informational, Staff Picks, Video
Titel: How to file a Support Request in My VMware

Am 17.02.2017 vom Typ: Best Practices, Staff Picks, Video
Titel: Understanding VM snapshots in ESXi / ESX

Am 17.02.2017 vom Typ: Informational, Troubleshooting
Titel: No agent configuration found on host when deploying an NSX Service Deployment

Am 17.02.2017 vom Typ: Troubleshooting
Titel: After unmapping a LUN, ESXi host fails with a Purple Diagnostic Screen and reports FRAME DROP events

Am 17.02.2017 vom Typ: Troubleshooting
Titel: VMs are reported as managed by Site Recovery Manager

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Warnings in the Hardware Status tab of an ESXi host fail to clear

Am 17.02.2017 vom Typ: Troubleshooting
Titel: The vpxd process becomes unresponsive after upgrading to vCenter Server 5.5/6.0

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

Am 17.02.2017 vom Typ: Informational
Titel: Supported drivers‘ firmware versions for I/O devices

Am 17.02.2017 vom Typ: Informational
Titel: Data recovery services for data not recoverable by VMware Technical Support

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Using small magnetic disks for vSAN might result in virtual machine failures

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Cannot view or add vSAN Storage Providers in the vSphere Web Client

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Configuring VMware vSphere Replication (VR) server connection in VMware Site Recovery Manager (SRM) reports the error:’Managed Object ‚HmsServiceInstance‘ thrown

Am 17.02.2017 vom Typ: Troubleshooting
Titel: vCenter Server indicates that the Distributed Resource Scheduler usage load is imbalanced

Am 17.02.2017 vom Typ: Troubleshooting
Titel: „TypeError: Cannot read property „optionDef“ from null“ in vCenter Server plug-in 6.0.0

Am 17.02.2017 vom Typ: How to, Informational, Troubleshooting
Titel: Enabling COM3 and COM4 in a Windows virtual machine

Am 17.02.2017 vom Typ: Troubleshooting
Titel: ESXi host in a vSAN cluster reports a warning alarm: Host vendor provider registration

Am 17.02.2017 vom Typ: Best Practices, How to, Troubleshooting
Titel: VIO does not show the available Clusters in other data center

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

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Connecting vCenter Server Appliance 5.1, 5.5, or 6.0 to an Active Directory domain with a large number of trusts fails with the error: Idm client exception: Error trying to join AD, error code [40705]

Am 17.02.2017 vom Typ: Troubleshooting
Titel: VixDiskLib_Init() call fails after installing Virtual Disk Deployment Kit 6.0 and vCenter Server 6.0 on same machine

Am 17.02.2017 vom Typ: Alerts, Informational
Titel: Trending support issues in VMware NSX for vSphere 6.x

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Horizon portal fail on some operations „Danger An error occurred. please retry later“

Am 17.02.2017 vom Typ: Troubleshooting
Titel: vCO plug-in error in vCO Inventory Edge

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

Am 17.02.2017 vom Typ: How to
Titel: „VMware Depot Not Available“ error after upgrading from VMware Cloud Foundation 2.0.0 to 2.1.0

Am 17.02.2017 vom Typ: Best Practices, How to
Titel: VIO deployment with „_“ character fail to update glance data stores

Am 17.02.2017 vom Typ: Troubleshooting
Titel: vSphere 6.0 or later displays Cluster Requirements Compliance Error for Fault Tolerance

Am 17.02.2017 vom Typ: Informational, Troubleshooting
Titel: „There is no more space for virtual disk .vmdk“ error when starting vSAN VM

Am 17.02.2017 vom Typ: Troubleshooting
Titel: vSAN Storage Providers do not appear in the vSphere Web Client

Am 17.02.2017 vom Typ: How to
Titel: Verbose logging and information for the software iSCSI initiator in VMware ESX 4.x and ESXi 4.x / 5.x

Am 17.02.2017 vom Typ: Informational, Troubleshooting
Titel: ESXi 6.0 host disconnects from vCenter due to a localcli process locking /etc/vmware/lunTimestamps.log

Am 17.02.2017 vom Typ: Troubleshooting
Titel: Installing vCenter Server on Windows fails with the error „Error 1402. Could not open key“

Am 17.02.2017 vom Typ: Troubleshooting
Titel: ESXi host that uses Intel Corporation Ethernet Controller X710 for 10GbE SFP+ NIC fails with PSOD

Am 17.02.2017 vom Typ: Troubleshooting
Titel: vCloud Air Disaster Recovery Service Performance Metrics

Am 17.02.2017 vom Typ: Troubleshooting
Titel: „Memory exceeds hard limit“ error on ESXi 5.5 P09 and P10

Ausführliche Auflistung:

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: 17.02.2017

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

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: How to file a Support Request in My VMware

Knowledgebase Nr: 2006985

Kategorie: How to, Informational, Staff Picks, Video

Aktualisiert: 17.02.2017

Link zum Artikel: 2006985

Beschreibung:
Ways to file a Support RequestFile a Support Request online – Filing a Support Request online is the fastest way to file a Support Request. When filing a Support Request online, you can choose from one of these categories: Technical – Choose from this dropdown if you are facing an issue related to product usage or installation. For more information, see Filing a Technical Support Request in this article. Product Licensing or Account – Choose from this dropdown if you are facing an issue…
… Für weitere Details den Link zum Artikel anklicken

Titel: Understanding VM snapshots in ESXi / ESX

Knowledgebase Nr: 1015180

Kategorie: Best Practices, Staff Picks, Video

Aktualisiert: 17.02.2017

Für Produkte: VMware ESX 2.5.x, VMware ESX 3.0.x, VMware ESX 3.5.x, VMware ESX 4.0.x, VMware ESX 4.1.x, VMware ESXi 3.5.x Embedded, VMware ESXi 3.5.x Installable, VMware ESXi 4.0.x Embedded, VMware ESXi 4.0.x Installable, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 1015180

Beschreibung:
This article may be helpful when you encounter these issues: Virtual machines are not responding or cannot start due to broken parent and child virtual disk dependencies. Virtual machines are not responding or do not start due to redo logs residing on datastores that do not have free space. Snapshot creation takes too long when specifying the memory snapshot option. Snapshot delete or remove operations result in the vSphere or VMware Infrastructure (VI) Client timing out. Backups fail…
… Für weitere Details den Link zum Artikel anklicken

Titel: No agent configuration found on host when deploying an NSX Service Deployment

Knowledgebase Nr: 2147520

Kategorie: Informational, Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware NSX for vSphere 6.0.x, VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x

Link zum Artikel: 2147520

Beschreibung:
When deploying an NSX Service deployment, you see errors similar to:No agent network configuration found on host or No agent data store configuration found on the host. In the NSX Manager vsm.log file, you see entries similar to: 2016-10-26 15:50:43.845 GMT+00:00 INFO DCNPool-8 EamListener:273 – using vsmagent VSMAgent [serviceStatus=UNKNOWN, powerState=UNKNOWN, fabricState=ENABLED, healthState=FAILED, vsmAgentState=null, moid=93de685b-8f13-491e-a41b-4775ab902ecd, hostid=host-661,…
… Für weitere Details den Link zum Artikel
anklicken

Titel: After unmapping a LUN, ESXi host fails with a Purple Diagnostic Screen and reports FRAME DROP events

Knowledgebase Nr: 2142317

Kategorie: Troubleshooting

Aktualisiert:
17.02.2017

Für Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2142317

Beschreibung:
After unmapping a LUN in ESXi 5.5, you experience these symptoms:ESXi host fails with a purple
diagnostic screen.In the
purple diagnostic screen, you see backtrace similar to:2016-01-23T00:10:50.992Z cpu62:33922)WARNING: iodm: vmk_IodmEvent:193: vmhba2: FRAME DROP event has been observed 6 times in the last one minute. This suggests a problem with Fibre Channel link/switch!.2016-01-23T00:10:50.997Z cpu37:33222)WARNING: iodm: vmk_IodmEvent:193: vmhba1: FRAME DROP event has been observed 6 times…
… Für
weitere Details den Link zum Artikel anklicken

Titel: VMs are reported as managed by Site Recovery Manager

Knowledgebase Nr: 2032366

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware vCenter Site Recovery Manager 5.0.x, VMware vCenter Site Recovery Manager 5.1.x, VMware vCenter Site Recovery Manager 5.5.x, VMware vCenter Site Recovery Manager 5.8.x, VMware vCenter Site Recovery Manager 6.0.x

Link zum Artikel: 2032366

Beschreibung:
After a failover and failback done previously, virtual machines in Production Site/Real virtual machines are reported as managed by VMware vCenter Site Recovery Manager (SRM) in the Summary tab. When you click the virtual machine, you see this alert:This entity is managed by solution VMware vCenter Site Recovery
Manager Extension. It is not recommended to modify it directly. Instead use the management console for the solution if you want
to make changes.
… Für weitere Details den Link zum Artikel anklicken

Titel: Warnings in the Hardware Status tab of an ESXi host fail to clear

Knowledgebase Nr: 2061093

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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

Link
zum Artikel: 2061093

Beschreibung:
Hardware Status tab of an ESXi host reports warnings that do not clear even after the hardware issue
is resolved. You see the alert:Status on the battery, storage and system logsThe battery on array status Unknown
… Für weitere Details den Link zum Artikel anklicken

Titel: The vpxd process becomes unresponsive after upgrading to vCenter Server 5.5/6.0

Knowledgebase Nr: 2065630

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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

Link zum Artikel: 2065630

Beschreibung:
The vpxd.exe process continually fails. You are unable to log in to vCenter Server. Windows Service Manager and service.msc show VMware VirtualCenter
Server service as Starting. In Windows Task Manager, the vpxd process continually recycles. A 0 or 1 byte vpxd.dmp file is generated in the vCenter Server log directory, located at C:ProgramDataVMwareVMware VirtualCenterLogs. In the C:ProgramDataVMwareVMware VirtualCentervpxd.log file, you see entries similar…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN on disk upgrade
fails at 10%

Knowledgebase Nr: 2144881

Kategorie: Video

Aktualisiert: 17.02.2017

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

Link zum Artikel: 2144881

Beschreibung:
When upgrading vSAN, the On 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 section.
… Für weitere Details den Link zum Artikel anklicken

Titel: Supported drivers‘ firmware versions for I/O devices

Knowledgebase Nr: 2030818

Kategorie: Informational

Aktualisiert: 17.02.2017

Für Produkte: VMware ESX 4.0.x, VMware ESX 4.1.x, VMware ESXi 4.0.x Embedded, VMware ESXi 4.0.x Installable, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x,
VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x

Link zum Artikel: 2030818

Beschreibung:
This article contains links to resources that provide information about support for I/O card firmware versions corresponding to certified drivers.   VMware recommends using the latest firmware versions listed at these links provided that they are paired with certified drivers.Note: The content contained in this Knowledge Base article does NOT apply to supported controller, firmware and driver version combinations in a vSAN environment.
Consult the VMware Compatibility Guide for certified vSAN…
… Für weitere Details den Link zum Artikel anklicken

Titel: Data recovery services for data not recoverable
by VMware Technical Support

Knowledgebase Nr: 1015413

Kategorie: Informational

Aktualisiert: 17.02.2017

Für Produkte: VMware ESX 2.0.x, VMware ESX 2.1.x, VMware ESX 2.5.x, VMware ESX 3.0.x, VMware ESX 3.5.x, VMware ESX 4.0.x, VMware ESX 4.1.x, VMware ESXi 3.5.x Embedded, VMware ESXi 3.5.x Installable, VMware ESXi 4.0.x Embedded, VMware ESXi 4.0.x Installable, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x

Link
zum Artikel: 1015413

Beschreibung:
VMware does not offer data recovery services. This article provides contact information for data recovery service providers.Note: VMware does not endorse or recommend any particular third-party utility, nor is this list meant to be exhaustive.
… Für weitere Details den Link zum Artikel anklicken

Titel: Using small magnetic disks for vSAN might result in virtual machine failures

Knowledgebase Nr: 2080503

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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: 2080503

Beschreibung:
When the physical magnetic disks used for vSAN are smaller than 255 GB, virtual machines that run on vSAN datastores
might experience disk space issues. You see entry similar to:There is no more space for virtual disk XX. You might be able to continue this session by freeing disk space on the relevant volume and clicking retry.Note: When vSAN stores virtual machine objects, it creates components whose default size does not exceed 255 GB. However, when you use magnetic disks that are smaller…
… Für weitere Details den Link zum
Artikel anklicken

Titel: Cannot view or add vSAN Storage Providers in the vSphere Web Client

Knowledgebase Nr: 2078070

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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: 2078070

Beschreibung:
Cannot view or manually add VMware vSAN (formerly known as Virtual SAN) Storage Providers in the vSphere Web Client.
You see the error:The Register new storage provider operation failed for the entity with the following error message. A Problem was encountered while registering the providerNote: For specific symptoms and log entries, see the Additional Information section.
… Für weitere Details den Link zum Artikel anklicken

Titel:
Configuring VMware vSphere Replication (VR) server connection in VMware Site Recovery Manager (SRM) reports the error:’Managed Object ‚HmsServiceInstance‘ thrown

Knowledgebase Nr: 2079214

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware vCenter Site Recovery Manager 5.5.x, VMware vSphere Replication 5.5.x

Link zum Artikel: 2079214

Beschreibung:
When configuring
the VMware vSphere Replication (VR) server connection in vCenter Site Recovery Manager (SRM), you see this error in the VR configuration page:Configuring
VR connection failedConnect or disconnect VRM server operation failedDetailsVRM Server Generic error. Please check the documentation for any troubleshooting information. The detailed exception is ‚Managed Object ‚HmsServiceInstance‘ thrown unexpected exception
‚java.net.UnknownHostException‘ with message…
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter Server indicates that the Distributed Resource Scheduler usage load is imbalanced

Knowledgebase Nr: 2087250

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Link
zum Artikel: 2087250

Beschreibung:
DRS usage load is not evenly balanced across hosts. Some hosts within a DRS Cluster show significantly higher CPU and/or memory usage compared to other hosts in the cluster. DRS resource distribution charts indicate that load is not distributed evenly across the hosts in the cluster.
… Für weitere
Details den Link zum Artikel anklicken

Titel: „TypeError: Cannot read property „optionDef“ from null“ in vCenter Server plug-in 6.0.0

Knowledgebase Nr: 2101118

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware vRealize Orchestrator 6.0.x

Link zum Artikel: 2101118

Beschreibung:
If you use the vCenter Server plug-in for vRealize Orchestrator 6.0.0 to manage vCenter Server 5.5 Update 2 or earlier instances, errors might occur when running some of the workflows.
Any workflow that contains specific data type might fail with the error:TypeError: Cannot read property „optionDef“ from null. This error occurs in operations which interact with HostConfigInfo, HostInternetScsiHba, HostInternetScsiHbaSendTarget, HostInternetScsiHbaStaticTarget, and OptionManager data types or…
… Für weitere Details den Link zum Artikel anklicken

Titel: Enabling COM3 and COM4 in a Windows virtual machine

Knowledgebase Nr: 1002463

Kategorie: How to, Informational, Troubleshooting

Aktualisiert: 17.02.2017

Link
zum Artikel: 1002463

Beschreibung:
VMware documentation indicates that it is possible to use COM3 and COM4 in a virtual machine, however these ports do not appear in the operating system This article discusses enabling COM3 and COM4 in a Windows virtual machine
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host in a vSAN cluster reports a warning alarm: Host vendor provider registration

Knowledgebase Nr: 2105018

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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: 2105018

Beschreibung:
ESXi host in a vSAN cluster reports a warning alarm: Host vendor provider registration
The same ESXi host is displaying
as unknown in the vCenter Server Storage Provider tab. In the /var/log/vsanvpd.log file in the ESXi host, you see entries similar to:<YYYY-MM-DD>T<TIME> Z vsanSoapServer: run:127:SSL Connection error 30: SSL_ERROR_SSL error:1408F119:SSL routines:SSL3_GET_RECORD:decryption failed or bad record mac In the /var/log/vmware/vpx/sps/sps.log located in the vCenter…
… Für weitere Details den Link zum Artikel
anklicken

Titel: VIO does not show the available Clusters in other data center

Knowledgebase Nr: 2148659

Kategorie: Best Practices, How to, Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware Integrated OpenStack 2.0.x, VMware Integrated OpenStack 2.5.x, VMware Integrated OpenStack 3.0.x

Link zum Artikel: 2148659

Beschreibung:
When deploying VMware Integrated OpenStack (VIO) or when adding a new compute to and existing VIO deployment:
Only cluster available in the data center where the management is deployed are visible.  Cluster which are located in different data center under the same VC are unavailable.
… 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: 17.02.2017

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: Connecting vCenter Server Appliance 5.1, 5.5, or 6.0 to an Active Directory domain with a large number of trusts fails with the error: Idm client exception: Error trying to join AD, error code [40705]

Knowledgebase Nr: 2117709

Aktualisiert: 17.02.2017

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

Link zum Artikel: 2117709

Beschreibung:
When attempting to connect a vCenter Server Appliance to an Active Directory domain which has a large number of trusts, you experience these symptoms: The vSphere Web Client displays the error:Idm client exception: Error trying to join AD, error code [40705] Joining the vCenter Server Appliance from an SSH sessions fails with the error:ERROR:Undocumented exception [code 0x00009f01]An undocumented exception has occurred. Please contact Likewise technical support and use the error code to…
… Für weitere Details den Link zum Artikel anklicken

Titel: VixDiskLib_Init() call fails after installing Virtual Disk Deployment Kit 6.0 and vCenter Server 6.0 on same machine

Knowledgebase Nr: 2120818

Aktualisiert: 17.02.2017

Für Produkte: VMware vCenter Server 6.0.x, Virtual Disk Development Kit 6.0

Link zum Artikel: 2120818

Beschreibung:
When VDDK 6.0 and vCenter server 6.0 are installed on same machine, library related issues are observed. This issue does not appear when they are installed on separate machines.
… Für weitere Details den Link zum Artikel anklicken

Titel: Trending support issues in VMware NSX for vSphere 6.x

Knowledgebase Nr: 2131154

Kategorie: Alerts, Informational

Aktualisiert: 17.02.2017

Für Produkte: VMware NSX for vSphere 6.0.x, VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x

Link zum Artikel: 2131154

Beschreibung:
This article provides information regarding trending issues and important Knowledge Base articles regarding VMware NSX for vSphere 6.x.
… Für weitere Details den Link zum Artikel anklicken

Titel: Horizon portal fail on some operations „Danger An error occurred. please retry later“

Knowledgebase Nr: 2148820

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware Integrated OpenStack 2.0.x, VMware Integrated OpenStack 2.5.x, VMware Integrated OpenStack 3.0.x

Link zum Artikel: 2148820

Beschreibung:
Some operation fail on Horizon dashboard with the error:Danger An error occurred. please retry later No specific logs are generated
… Für weitere Details den Link zum Artikel anklicken

Titel: vCO plug-in error in vCO Inventory Edge

Knowledgebase Nr: 2148554

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware vRealize Orchestrator 7.2.x

Link zum Artikel: 2148554

Beschreibung:
Unable to see vCO Inventory Edge on vRO client. In the Server.log file on vRO server, you see entries similar to: 2017-01-10 12:23:39.396+0530 [serverHealthMonitorScheduler-1] WARN {} [AbstractClient] ******* WARNING ****** WARNING ****** WARNING ******* 2017-01-10 12:23:39.396+0530 [serverHealthMonitorScheduler-1] WARN {} [AbstractClient] Possible remote API mismatch detected. Operation will continue, but errors are l ikely. 2017-01-10 12:23:39.396+0530 [serverHealthMonitorScheduler-1] WARN…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN 6.2 hybrid disk group performance degradation

Knowledgebase Nr: 2146267

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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: „VMware Depot Not Available“ error after upgrading from VMware Cloud Foundation 2.0.0 to 2.1.0

Knowledgebase Nr: 2148926

Kategorie: How to

Aktualisiert: 17.02.2017

Für Produkte: VMware SDDC Manager 2.0.x

Link zum Artikel: 2148926

Beschreibung:
After upgrading VMware Cloud Foundation from version 2.0.0 to version 2.1.0, the Lifecycle Management page in the SDDC Manager UI displays the error:VMware Depot Not Available
… Für weitere Details den Link zum Artikel anklicken

Titel: VIO deployment with „_“ character fail to update glance data stores

Knowledgebase Nr: 2148666

Kategorie: Best Practices, How to

Aktualisiert: 17.02.2017

Für Produkte: VMware Integrated OpenStack 2.0.x

Link zum Artikel: 2148666

Beschreibung:
Deploying VMware Integrated Open stack fails. When deleting a nova Datastore in plug-in, you see this message:Cannot delete the Nova datastore. Invalid value: node VM name=NAME_2-ComputeDriver-0.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSphere 6.0 or later displays Cluster Requirements Compliance Error for Fault Tolerance

Knowledgebase Nr: 2149112

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware vSphere Client 6.5.x

Link zum Artikel: 2149112

Beschreibung:
When you check Cluster Requirements Compliance in vSphere 6.0 or later under Cluster->Monitor->Profile Compliance->Cluster Requirements Compliance, you might see the following error displayed:FtSupported: „Fault Tolerance is not supported on this host. Reason: incompatibleCpuThis error message applies only to Legacy FT, as Legacy FT is not supported on Intel Broadwell generation or later processors. You can safely ignore this message for SMP-FT virtual machines.
… Für weitere Details den Link zum Artikel anklicken

Titel: „There is no more space for virtual disk .vmdk“ error when starting vSAN VM

Knowledgebase Nr: 2146613

Kategorie: Informational, Troubleshooting

Aktualisiert: 17.02.2017

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

Link zum Artikel: 2146613

Beschreibung:
You are unable to start up a vSAN virtual machine and you experience these symptoms The vSAN datastore reports sufficient total free space to provision the virtual machine. The Capacity Tier disks in use by the vSAN cluster ESXi hosts are greater than 255 GB in size. You see an error in the vSphere Web client, similar to:There is no more space for virtual disk <VM name>.vmdk. You might be able to continue this session by freeing disk space on the relevant volume and clicking retry.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Storage Providers do not appear in the vSphere Web Client

Knowledgebase Nr: 2144125

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

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: 2144125

Beschreibung:
You cannot see or manually add VMware vSAN Storage Providers in the VMware vSphere Web Client.Manually adding a Storage Provider for vSAN in the vSphere Web client fails.Note: For specific symptoms and log entries, see the Additional Information section.
… Für weitere Details den Link zum Artikel anklicken

Titel: Verbose logging and information for the software iSCSI initiator in VMware ESX 4.x and ESXi 4.x / 5.x

Knowledgebase Nr: 1013283

Kategorie: How to

Aktualisiert: 17.02.2017

Für Produkte: VMware ESX 4.0.x, VMware ESX 4.1.x, VMware ESXi 4.0.x Embedded, VMware ESXi 4.0.x Installable, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x

Link zum Artikel: 1013283

Beschreibung:
This article describes how to enable and disable verbose logging of the VMware software initiator.
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi 6.0 host disconnects from vCenter due to a localcli process locking /etc/vmware/lunTimestamps.log

Knowledgebase Nr: 2146548

Kategorie: Informational, Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2146548

Beschreibung:
ESXi hosts appear as Not Responding in vCenter Server.The issue persists after completing the work around in ESXi 6.0 host is disconnected from vCenter Server (2145106).In the /var/run/log/hostd.log file, there are entries similar to:YYYY-MM-DD T10:09:00.493Z error hostd[39A80B70] [Originator@6876 sub=Hostsvc] Failed to fetch LUN data from VmkCtl: Error interacting with configuration file /etc/vmware/lunTimestamps.log: Timout while waiting for lock, /etc/vmware/lunTimestamps.log.LOCK, to be…
… Für weitere Details den Link zum Artikel anklicken

Titel: Installing vCenter Server on Windows fails with the error „Error 1402. Could not open key“

Knowledgebase Nr: 1029282

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware vCenter Server 4.1.x, VMware vCenter Server 5.0.x, VMware vCenter Server 5.1.x, VMware vCenter Server 5.5.x, VMware vCenter Server 6.0.x

Link zum Artikel: 1029282

Beschreibung:
Installing vCenter Server 4.1 on Windows server fails You see the error: Error 1402. Could not open key: UNKNOWN Note: This issue may also occur with other VMware products, such as VMware Workstation.
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host that uses Intel Corporation Ethernet Controller X710 for 10GbE SFP+ NIC fails with PSOD

Knowledgebase Nr: 2126909

Aktualisiert: 17.02.2017

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

Link zum Artikel: 2126909

Beschreibung:
ESXi host that uses Intel Corporation Ethernet Controller X710 for 10GbE SFP+ NIC fails with a purple diagnostic screen. Multiple driver/firmware combinations are affected. The purple diagnostic screen contains entries similar to:@BlueScreen: #PF Exception 14 in world wwww:WorldName IP 0xnnnnnnnnnn addr 0x0 PTEs:0x0;0xnnnnnnnnnnnn [0xnnnnnnnnnnnn] i40e_lan_xmit_frame@<None>#<None>+0x3a40xnnnnnnnnnnnn:[0xnnnnnnnnnnnn] DevStartTxImmediate@com.vmware.driverAPI#9.2+0x137…
… Für weitere Details den Link zum Artikel anklicken

Titel: vCloud Air Disaster Recovery Service Performance Metrics

Knowledgebase Nr: 2148043

Aktualisiert: 17.02.2017

Link zum Artikel: 2148043

Beschreibung:
This article describes the maximum limits while using vCloud Air’s multi-tenant Disaster Recovery service available as of January, 2016.
… Für weitere Details den Link zum Artikel anklicken

Titel: „Memory exceeds hard limit“ error on ESXi 5.5 P09 and P10

Knowledgebase Nr: 2148979

Kategorie: Troubleshooting

Aktualisiert: 17.02.2017

Für Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2148979

Beschreibung:
The ESXi host is running 5.5 P09 (build 4345813) or P10 (build 4722766) In the /var/log/hostd.log file, there are entries similar to:2017-02-01T16:34:39.613Z [29340B70
error ‚UW Memory checker‘] Current value 780292 exceeds hard limit 780185. Shutting down process.2017-02-01T16:34:39.613Z [29340B70 panic ‚Default‘]–>–> Panic: Memory exceeds hard limit. Panic–> Backtrace:And[…]Failed to read advanced option subtree UserVars.HostClient.SessionTimeout:…
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2017-02-18T09:12:51+00:00Februar 18th, 2017|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