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

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

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

Vom 28.12.2016 bis zum 29.12.2016 wurden 16 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 28.12.2016 vom Typ: How to
Titel: Disabling the VAAI functionality in ESXi/ESX

Am 28.12.2016 vom Typ: Troubleshooting
Titel: Unmounting an inactive datastore fails with the error: Cannot remove datastore ‚datastore_name‘ because Storage I/O Control is enabled on it

Am 28.12.2016 vom Typ: Troubleshooting
Titel: Inconsistent datastore labels in cluster

Am 28.12.2016 vom Typ: Troubleshooting
Titel: Cannot remount a datastore after an unplanned permanent device loss (PDL)

Am 28.12.2016 vom Typ: How to, Informational, Troubleshooting
Titel: Synchronizing VMware Horizon View Pool in Workspace portal fails with error: Failed to complete View sync due to a problem with the View Connection Server

Am 28.12.2016 vom Typ: How to
Titel: Stopping, starting, or restarting VMware vCenter Server Appliance 6.x services

Am 28.12.2016 vom Typ: Informational
Titel: VSS Quiescing Support with vSphere Replication

Am 28.12.2016 vom Typ: How to, Troubleshooting
Titel: Using hardware NMI facilities to troubleshoot unresponsive hosts

Am 28.12.2016 vom Typ: Troubleshooting
Titel: Slow VMs after upgrading VMware Tools in NSX and vCloud Networking and Security

Am 28.12.2016 vom Typ: Best Practices, Informational
Titel: All guest OS memory reserved when disabling VM swap file

Am 28.12.2016 vom Typ: How to
Titel: Configuring and troubleshooting Load Balancing as a Service in Integrated Openstack 3.0

Am 28.12.2016 vom Typ: Troubleshooting
Titel: Logging in to vCloud Director using LDAP with Kerberos fails

Am 28.12.2016 vom Typ: How to, Informational
Titel: Applying vSphere host configuration changes after an unclean shutdown

Am 28.12.2016 vom Typ: How to
Titel: Removing a solution from VMware vRealize Operations Manager 6.x

Am 28.12.2016 vom Typ: Troubleshooting
Titel: Detect and Update Duplicate Names of Distributed Virtual Switches and Distributed Virtual Portgroups before Upgrading vCenter Server

Am 28.12.2016 vom Typ: How to, Informational, Troubleshooting
Titel: Changing the VIO – FQDN after initial deployment

Ausführliche Auflistung:

Titel: Disabling the VAAI functionality in ESXi/ESX

Knowledgebase Nr: 1033665

Kategorie: How to

Aktualisiert: 28.12.2016

Für Produkte: VMware ESX 4.1.x, 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: 1033665

Beschreibung:
This article provides steps to disable the vStorage APIs for Array Integration (VAAI) functionality in ESXi/ESX. You may want to disable VAAI if the storage array devices in the environment do not support the hardware acceleration functionality or are not responding correctly to VAAI primitives.For information on VAAI support in a given storage array or required firmware levels, contact the storage array vendor.
… Für weitere Details den Link zum Artikel anklicken

Titel: Unmounting an inactive datastore fails with the error: Cannot remove datastore ‚datastore_name‘ because Storage I/O Control is enabled on it

Knowledgebase Nr: 2011220

Kategorie: Troubleshooting

Aktualisiert: 28.12.2016

Für Produkte: VMware ESX 4.1.x, VMware ESXi 4.1.x Embedded, VMware ESXi 4.1.x Installable, VMware ESXi 5.0.x, VMware ESXi 5.1.x, VMware vCenter Server 5.0.x, VMware vCenter Server 5.1.x

Link zum Artikel: 2011220

Beschreibung:
Cannot unmount an inactive datastore. Unmounting an unavailable datastore fails. Cannot delete the inactive datastore. You see the error:The resource “ is in use.Cannot remove datastore ‚datastore_name‘ because Storage I/O Control is enabled on it. Correct it and re-try the operation. The datastore LUN is not available and, therefore, cannot be re-added. The Storage Adapter indicates the Operational State of the device as Lost Communication. All Paths to the device are marked as Dead. …
… Für weitere Details den Link zum Artikel anklicken

Titel: Inconsistent datastore labels in cluster

Knowledgebase Nr: 1002681

Kategorie: Troubleshooting

Aktualisiert: 28.12.2016

Für Produkte: VMware ESX 3.5.x, VMware ESXi 3.5.x Embedded, VMware ESXi 3.5.x Installable, VMware ESXi 6.0.x, VMware VirtualCenter 2.5.x

Link zum Artikel: 1002681

Beschreibung:
The datastore names appear with extra parenthesis in some ESX hosts sharing the same storage. For example, if datastore-volume is the datastore name, in hosts with this issue the name appears as datastore-volume(1) The storage appears same when viewed through the Virtual Infrastructure Client, either when connecting directly to host or through VirtualCenter. This issue is only seen in the Service Console, the performance of the virtual machines are not affected and the paths are consistent…
… Für weitere Details den Link zum Artikel anklicken

Titel: Cannot remount a datastore after an unplanned permanent device loss (PDL)

Knowledgebase Nr: 2014155

Kategorie: Troubleshooting

Aktualisiert: 28.12.2016

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

Beschreibung:
After a storage device has unexpectedly unpresented from the storage array, you are unable to mount it again. This issue occurs when there was a running virtual machine when the storage device went offline. An ESXi 5.x host cannot mount the storage after the LUN is online again. In the vmkernel.log file, you see entries similar to:cpu36:5590)Vol3: 1665: Error refreshing FD resMeta: Device is permanently unavailablecpu34:5590)VC: 1449: Device rescan time 165 msec (total number of devices…
… Für weitere Details den Link zum Artikel anklicken

Titel: Synchronizing VMware Horizon View Pool in Workspace portal fails with error: Failed to complete View sync due to a problem with the View Connection Server

Knowledgebase Nr: 2091744

Kategorie: How to, Informational, Troubleshooting

Aktualisiert: 28.12.2016

Für Produkte: VMware Horizon Workspace 1.x, VMware Identity Manager 2.x, VMware Workspace Portal 2.x

Link zum Artikel: 2091744

Beschreibung:
Synchronizing VMware Horizon View Pools in Workspace portal fails with one of these errors: Failed to complete view sync due to a problem with the View Connection Server: Unable authenticate to View broker, problem with directory Failed to complete View sync due to a problem with the View Connection Server: Unable to query any broker in the pod for pool and entitlement information. Check connectivity with the View pod Failed to complete View sync due to a problem with the View Connection…
… Für weitere Details den Link zum Artikel anklicken

Titel: Stopping, starting, or restarting VMware vCenter Server Appliance 6.x services

Knowledgebase Nr: 2109887

Kategorie: How to

Aktualisiert: 28.12.2016

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

Link zum Artikel: 2109887

Beschreibung:
This article provides step to stop, start, or restart vCenter Server Appliance services. For troubleshooting and maintenance purposes, it may be necessary to change the status of VMware vCenter Server Appliance services, such as VMware Virtual Center Server, VMware vSphere Web Client, or VMware Directory Service.
… Für weitere Details den Link zum Artikel anklicken

Titel: VSS Quiescing Support with vSphere Replication

Knowledgebase Nr: 2041909

Kategorie: Informational

Aktualisiert: 28.12.2016

Für Produkte: VMware vSphere Replication 5.1.x, VMware vSphere Replication 5.5.x, VMware vSphere Replication 5.6.x, VMware vSphere Replication 5.8.x, VMware vSphere Replication 6.0.x

Link zum Artikel: 2041909

Beschreibung:
Microsoft Volume Shadow Copy Service (VSS) quiescing is supported for virtual machines running Windows Server 2003, XP, or later. vSphere Replication does not support quiescing for Linux and for earlier versions of Windows such as Windows 2000. The quiescing option is unavailable for unsupported operating systems.
… Für weitere Details den Link zum Artikel anklicken

Titel: Using hardware NMI facilities to troubleshoot unresponsive hosts

Knowledgebase Nr: 1014767

Kategorie: How to, Troubleshooting

Aktualisiert: 28.12.2016

Für Produkte: 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: 1014767

Beschreibung:
This article provides information about using Non-Maskable Interrupt (NMI) facilities to troubleshoot unresponsive VMware ESXi or ESX hosts. This process should be followed if an ESXi/ESX host does not respond to interaction at the console or through the network and all hosted virtual machines do not respond to remote communication. For more information on these scenarios, see Determining why an ESX/ESXi host does not respond to user interaction at the console (1017135). If an ESXi/ESX host is…
… Für weitere Details den Link zum Artikel anklicken

Titel: Slow VMs after upgrading VMware Tools in NSX and vCloud Networking and Security

Knowledgebase Nr: 2144236

Kategorie: Troubleshooting

Aktualisiert: 28.12.2016

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 vCloud Networking and Security 5.5.x

Link zum Artikel: 2144236

Beschreibung:
The guest operating system in the virtual machine is slow and unresponsive in an NSX 6.x and VMware vCloud Networking and Security 5.5.x environment where VMware Tools were recently upgraded to version 10.0.x. Note: For additional symptoms, see the Additional Information section.
… Für weitere Details den Link zum Artikel anklicken

Titel: All guest OS memory reserved when disabling VM swap file

Knowledgebase Nr: 2146618

Kategorie: Best Practices, Informational

Aktualisiert: 28.12.2016

Link zum Artikel: 2146618

Beschreibung:
Virtual machines running on an ESXi host uses a swap file (vswap) for any memory that is not reserved. This swap file is used when the virtual machine is unable to allocate physical memory from the ESXi host. In larger environments this can increase the storage usage to provide multiple virtual machines with vswap space.
… Für weitere Details den Link zum Artikel anklicken

Titel: Configuring and troubleshooting Load Balancing as a Service in Integrated Openstack 3.0

Knowledgebase Nr: 2147657

Kategorie: How to

Aktualisiert: 28.12.2016

Für Produkte: VMware Integrated OpenStack 3.0.x

Link zum Artikel: 2147657

Beschreibung:
This article provides steps to configure and troubleshoot Load Balancing as a Service (LBaaSv2) in VMware Integrated Openstack (VIO) 3.0. Note: This process only applies to VMware Integrated OpenStack deployments where NSX for vSphere (NSX-V) networking is in use.
… Für weitere Details den Link zum Artikel anklicken

Titel: Logging in to vCloud Director using LDAP with Kerberos fails

Knowledgebase Nr: 2147599

Kategorie: Troubleshooting

Aktualisiert: 28.12.2016

Für Produkte: VMware vCloud Director for Service Provider 8.10.x

Link zum Artikel: 2147599

Beschreibung:
You use LDAP with Kerberos to log in to vCloud Director You see the error:String cannot be cast to java.util.Vector Upgrading to vCloud Director for Service Provider 8.10 breaks LDAP functionality
… Für weitere Details den Link zum Artikel anklicken

Titel: Applying vSphere host configuration changes after an unclean shutdown

Knowledgebase Nr: 2001780

Kategorie: How to, Informational

Aktualisiert: 28.12.2016

Für Produkte: 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: 2001780

Beschreibung:
This article explains how ESX and ESXi persist configuration information across reboots, and the ramifications of an unclean shutdown or reboot. Troubleshooting the cause of the unclean shutdown or restart is outside the scope of this article, but should be investigated separately.
… Für weitere Details den Link zum Artikel anklicken

Titel: Removing a solution from VMware vRealize Operations Manager 6.x

Knowledgebase Nr: 2114441

Kategorie: How to

Aktualisiert: 28.12.2016

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

Link zum Artikel: 2114441

Beschreibung:
Data migration fails due to an incompatible solution. You are able to install the solution or management pack in VMware vRealize Operations Manager UI. There is no way to uninstall the solution or management pack from VMware vRealize Operations Manager UI.
… Für weitere Details den Link zum Artikel anklicken

Titel: Detect and Update Duplicate Names of Distributed Virtual Switches and Distributed Virtual Portgroups before Upgrading vCenter Server

Knowledgebase Nr: 2147547

Aktualisiert: 28.12.2016

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

Link zum Artikel: 2147547

Beschreibung:
vSphere 6.5 allows only unique names across all Distributed Virtual Switches and Distributed Virtual Portgroups in the same network folder. Earlier versions of vSphere allowed a Distributed Virtual Switch and a Distributed Virtual Portgroup to have the same name. If you attempt to upgrade from a version that allows duplicate names, the upgrade fails. When upgrading a vSphere environment that does not have a unique name, you experience these symptoms: Upgrading the vCenter Server fail with the…
… Für weitere Details den Link zum Artikel anklicken

Titel: Changing the VIO – FQDN after initial deployment

Knowledgebase Nr: 2147624

Kategorie: How to, Informational, Troubleshooting

Aktualisiert: 28.12.2016

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

Link zum Artikel: 2147624

Beschreibung:
This article provides steps to change the initially configured FQDN to a new FQDN. During initial deployment, the hostname of the appliance is used instead of the desired FQDN for public consumption.
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2016-12-29T09:08:34+00:00Dezember 29th, 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