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

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

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

Vom 08.05.2017 bis zum 09.05.2017 wurden 17 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 08.05.2017 vom Typ: Informational
Titel: FAQ: Log Insight for vCenter Server

Am 08.05.2017 vom Typ: Informational, Troubleshooting
Titel: vSAN host may encounter a purple diagnostic screen during resync operations if resync is paused

Am 08.05.2017 vom Typ: Troubleshooting
Titel: Connecting to the VMware vSphere Data Protection Appliance fails with the error: The most recent request has been rejected by the server

Am 08.05.2017 vom Typ: Troubleshooting
Titel: vCenter Single Sign-On and Platform Services Controller High Availability Compatibility Matrix

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

Am 08.05.2017 vom Typ: Troubleshooting
Titel: vSAN APD message that can be safely ignored: Unable to register file system for APD timeout notifications: Inappropriate ioctl for device

Am 08.05.2017 vom Typ: Troubleshooting
Titel: „Virtual SAN Disk Balance“ warning alarm during vSAN health check

Am 08.05.2017 vom Typ: How to
Titel: Adding existing vSAN hosts to a new vSAN cluster after rebuilding vCenter Server

Am 08.05.2017 vom Typ: Staff Picks, Troubleshooting
Titel: Troubleshooting a slow network connection in Windows Virtual machines on VMware Fusion

Am 08.05.2017 vom Typ: Informational, Troubleshooting
Titel: vSAN Health check warning for controller driver version containing string patterns with „-1OEM“ or “VMW”

Am 08.05.2017 vom Typ: Troubleshooting
Titel: „Hard disk x‘ ExternalDiskID:“xx“vm: ‚xx-dvsa ‚ does not have or lost its storage” error vRealize Automation

Am 08.05.2017 vom Typ: Troubleshooting
Titel: Managing NSX Ege from vCloud Director fails after upgrading vCNS 5.5.3 to NSX for vSphere 6.2.x

Am 08.05.2017 vom Typ: Troubleshooting
Titel: Veeam backup and replication with vSAN datastores

Am 08.05.2017 vom Typ: Troubleshooting
Titel: vRA HA environment upgrade from 7.1 to 7.2 fails in Post-install scripts with exit code 256

Am 08.05.2017 vom Typ: Troubleshooting
Titel: Windows 10 upgrade requirements for Horizon Client for Windows

Am 08.05.2017 vom Typ: How to
Titel: Changing internal configuration options in VMware vRealize Log Insight

Am 08.05.2017 vom Typ: Troubleshooting
Titel: „snmpd start failed with status: 1“ error in syslog on ESXi 5.0

Ausführliche Auflistung:

Titel: FAQ: Log Insight for vCenter Server

Knowledgebase Nr: 2144909

Kategorie: Informational

Aktualisiert: 08.05.2017

Link zum Artikel: 2144909

Beschreibung:
VMware has announced that all users with a supported vCenter Server license are entitled to a 25-OSI pack of vRealize Log Insight for vCenter Server, at no charge. vRealize Log Insight 3.3.2 and above will accept the vCenter Server 5.x or 6.x license key you already have. Refer to the VMware Product Interoperability Matrices for confirmation of which versions are compatible.For more information, see the VMware Accelerates the Shift to Digitization and Hybrid Cloud With the Introduction of…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN host may encounter a purple diagnostic screen during resync operations if resync is paused

Knowledgebase Nr: 2149130

Kategorie: Informational, Troubleshooting

Aktualisiert: 08.05.2017

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

Link zum Artikel: 2149130

Beschreibung:
A vSAN 6.2 host fails with a purple diagnostic screen (PSOD). The panic screen returns a stack trace, similar to:2016-10-05T15:47:05.649Z cpu4:23591339)@BlueScreen: 4316f557-6c93-3818-902e-246e960e1b18 stuck during cleanup (1) 2016-10-05T15:47:05.649Z cpu4:23591339)Code start: 0x418036800000 VMK uptime: 76:05:26:53.582 2016-10-05T15:47:05.649Z cpu4:23591339)0x43954d59b6e8:[0x418036877afa]PanicvPanicInt@vmkernel#nover+0x37e stack: 0x43954d59b7a0 2016-10-05T15:47:05.649Z…
… Für weitere Details den Link zum Artikel anklicken

Titel: Connecting to the VMware vSphere Data Protection Appliance fails with the error: The most recent request has been rejected by the server

Knowledgebase Nr: 2040078

Kategorie: Troubleshooting

Aktualisiert: 08.05.2017

Für Produkte: VMware vSphere Data Protection 5.1.x, VMware vSphere Data Protection 5.5.x

Link zum Artikel: 2040078

Beschreibung:
Connecting to the VMware vSphere Data Protection (VDP) appliance from the Web Client fails. You see the error:The most recent request has been rejected by the server. The most common cause for this error is that the times on the VDP appliance and your SSO server are not in sync. This issue occurs when your vCenter Server and ESXi hosts are configured for NTP and are syncing from the same NTP.Note: For more information, see the NTP Configuration section in the VMware vSphere Data…
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter Single Sign-On and Platform Services Controller High Availability Compatibility Matrix

Knowledgebase Nr: 2112736

Aktualisiert: 08.05.2017

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

Link zum Artikel: 2112736

Beschreibung:
This article provides information on vCenter Single Sign-On and the Platform Services Controller compatibility regarding the use of qualified load balancers that supply high availability as well as their requirements between versions of vSphere. Only local load balancers (often times referred to as LTM, or Local Traffic Manager) are supported for PSC HA. Note: VMware does not support the configuration or setup of the load balancer used to provide high availability within a vSphere…
… 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: 08.05.2017

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: vSAN APD message that can be safely ignored: Unable to register file system for APD timeout notifications: Inappropriate ioctl for device

Knowledgebase Nr: 2145444

Kategorie: Troubleshooting

Aktualisiert: 08.05.2017

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

Link zum Artikel: 2145444

Beschreibung:
You see entries in the /var/log/vmkernel.log file, similar to:2016-05-11T23:11:30.437Z cpu34:35283 opID=d6b83ffe)Vol3: 956: Unable to register file system 21bc3357-bed6-7e9a-a4a9-3464a990bfac for APD timeout notifications: Inappropriate ioctl for device2016-05-11T23:12:35.974Z cpu22:998827)Vol3: 956: Unable to register file system 21bc3357-bed6-7e9a-a4a9-3464a990bfac for APD timeout notifications: Inappropriate ioctl for device2016-05-11T23:13:39.196Z cpu20:999104)Vol3: 956: Unable to register…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Virtual SAN Disk Balance“ warning alarm during vSAN health check

Knowledgebase Nr: 2148484

Aktualisiert: 08.05.2017

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

Link zum Artikel: 2148484

Beschreibung:
The vSAN health check reports the warning:“Virtual SAN Disk Balance“Note: This warning occurs only in the VSAN stretched cluster configuration.
… Für weitere Details den Link zum Artikel anklicken

Titel: Adding existing vSAN hosts to a new vSAN cluster after rebuilding vCenter Server

Knowledgebase Nr: 2059194

Kategorie: How to

Aktualisiert: 08.05.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: 2059194

Beschreibung:
This article provides steps to add existing vSAN hosts to a new vSAN cluster after rebuilding vCenter Server.Note: vSphere 5.5 includes vSAN as an experimental feature. You can perform testing with vSAN, but it is not supported for use in a production environment.
… Für weitere Details den Link zum Artikel anklicken

Titel: Troubleshooting a slow network connection in Windows Virtual machines on VMware Fusion

Knowledgebase Nr: 1027976

Kategorie: Staff Picks, Troubleshooting

Aktualisiert: 08.05.2017

Für Produkte: VMware Fusion 2.x, VMware Fusion 3.x, VMware Fusion 4.x, VMware Fusion 5.x, VMware Fusion 6.x, VMware Fusion 7.x, VMware Fusion 8.x, VMware Fusion Pro 8.x

Link zum Artikel: 1027976

Beschreibung:
This article provides the general steps to follow when your windows virtual machine’s network connection is significantly slower than expected. Note: When your virtual machine’s network connection is not working, see Troubleshooting networking and internet connection issues in VMware Fusion (1016466).
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health check warning for controller driver version containing string patterns with „-1OEM“ or “VMW”

Knowledgebase Nr: 2148615

Kategorie: Informational, Troubleshooting

Aktualisiert: 08.05.2017

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

Link zum Artikel: 2148615

Beschreibung:
The vSAN Health Service shows a warning for controller driver versions containing string patterns with -1OEM or VMW even though the driver is compatible as per the vSAN HCL entry for the device. For example, this issue occurs when using the megaraid_sas driver version 6.608.16.00-1OEM with an LSI / Symbios Logic MegaRAID SAS Invader controller or Cisco 12G SAS Modular Raid Controller for vSAN or Intel NVME controller with driver version 1.2.0.27-4vmw.550.0.0.1331820. For more information about…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Hard disk x‘ ExternalDiskID:“xx“vm: ‚xx-dvsa ‚ does not have or lost its storage” error vRealize Automation

Knowledgebase Nr: 2101169

Kategorie: Troubleshooting

Aktualisiert: 08.05.2017

Für Produkte: VMware vCloud Automation Center for Server 6.0.x, VMware vCloud Automation Center for Server 6.1.x, VMware vRealize Automation 6.2.x, VMware vRealize Automation 7.0.x, VMware vRealize Automation 7.1.x

Link zum Artikel: 2101169

Beschreibung:
vRealize Automation Center (formerly known as vCloud Automation Center) reports an error similar to:Hard disk 3′ ExternalDiskID:“xx“vm: ‚xx-dvsa ‚ does not have or lost its storage” Either the virtual machine was deleted, but vRealize Automation Center still sees it as missing or the virtual machines are in the local data store and are not managed by vRealize Automation Center. In the Install DirServerLogsAll.log file, you see entries similar to:[UTC:yyyy-mm-dd 21:06:44
Local:2014-10-29…
… Für weitere Details den Link zum Artikel anklicken

Titel: Managing NSX Ege from vCloud Director fails after upgrading vCNS 5.5.3 to NSX for vSphere 6.2.x

Knowledgebase Nr: 2150069

Kategorie: Troubleshooting

Aktualisiert: 08.05.2017

Für Produkte: VMware NSX for vSphere 6.2.x, VMware vCloud Director 5.5.x

Link zum Artikel: 2150069

Beschreibung:
After upgrading vCNS 5.5.x to NSX for vSphere 6.2.x in a vCloud Director environment, you experience these symptoms:Managing the NSX Edge failsDeleting a network
in vCloud Director failsYou see the error on the NSX Edge similar to:[ 5504a62f-b3bc-4bdd-ade6-98c2c2aae77c ] Cannot deploy organization VDC network (5c7f9d6b-0f09-4d67-9dbe-ac72dbff5270)Failed to connect interface of edge gateway edge_ccs9764 to organization VDC network testjava.util.concurrent.ExecutionException:…
… Für weitere Details den Link zum Artikel anklicken

Titel: Veeam backup and replication with vSAN datastores

Knowledgebase Nr: 2149874

Aktualisiert: 08.05.2017

Link zum Artikel: 2149874

Beschreibung:
This article provides information about Veeam Backup & Replication 9.5.Disclaimer: The partner solution referenced in this article is a solution developed and supported by a partner. Use of this product is also governed by the end user license agreement of the partner. You must obtain the application, support, and licensing for using this product from the partner. For more information, see https://www.veeam.com/support.html.Use Cases To backup virtual machines or virtual disk data residing…
… Für weitere Details den Link zum Artikel anklicken

Titel: vRA HA environment upgrade from 7.1 to 7.2 fails in Post-install scripts with exit code 256

Knowledgebase Nr: 2149966

Kategorie: Troubleshooting

Aktualisiert: 08.05.2017

Für Produkte: VMware vRealize Automation 7.1.x, VMware vRealize Automation 7.2.x

Link zum Artikel: 2149966

Beschreibung:
After upgrading a vRealize Automation HA environment from 7.1 to 7.2 and the appliance fails with exit code 256 . In the /opt/vmware/var/log/vami/updatecli.log file, you see error message similar to:+ echo ‚Script /etc/bootstrap/postupdate.d/995-upgrade-replicas failed, error status 1‘ In the /var/log/bootstrap/postupdate.log file, you see entries similar to:Traceback (most recent call last): File „/etc/bootstrap/postupdate.d/995-upgrade-replicas“, line 148, in <module> …
… Für weitere Details den Link zum Artikel anklicken

Titel: Windows 10 upgrade requirements for Horizon Client for Windows

Knowledgebase Nr: 2148201

Aktualisiert: 08.05.2017

Für Produkte: VMware Horizon Client for Windows 4.3.x, VMware Horizon Client for Windows 4.4.x

Link zum Artikel: 2148201

Beschreibung:
Horizon Client 4.3 and Horizon Client 4.4 for Windows support the following Windows 10 servicing branches and versions:Current Branch (CB) version 1607Current Business Branch (CBB) version 1607Long-Term Servicing Branch (LTSB) version 1607
… Für weitere Details den Link zum Artikel anklicken

Titel: Changing internal configuration options in VMware vRealize Log Insight

Knowledgebase Nr: 2123058

Kategorie: How to

Aktualisiert: 08.05.2017

Link zum Artikel: 2123058

Beschreibung:
The VMware vRealize Log Insight administration user interface exposes common configuration options. Additional advanced configuration options exist which affect the behavior of various components. This article provides steps to review and set new advanced configuration options.VMware recommends that you set these configuration options under the direction of VMware Technical Support or a VMware Knowledge base article.Caution: Option values modified using one of these methods are not checked for…
… Für weitere Details den Link zum Artikel anklicken

Titel: „snmpd start failed with status: 1“ error in syslog on ESXi 5.0

Knowledgebase Nr: 2150037

Kategorie: Troubleshooting

Aktualisiert: 08.05.2017

Für Produkte: VMware ESXi 5.0.x

Link zum Artikel: 2150037

Beschreibung:
In the ESXi host syslog, you will see entries similar to:2016-08-23T16:35:53Z jumpstart[66636]: executing start plugin: snmpd2016-08-23T16:35:54Z root: Starting snmpd2016-08-23T16:35:54Z root: snmpd has not been enabled.2016-08-23T16:35:54Z jumpstart[66636]: Jumpstart failed to start: snmpd reason: Execution of command: /etc/init.d/snmpd start failed with status: 1
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2017-05-09T08:06:08+00:00Mai 9th, 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