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

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

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

Vom 23.05.2017 bis zum 24.05.2017 wurden 19 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 23.05.2017 vom Typ: Best Practices, How to
Titel: How to unmount a LUN or detach a datastore device from ESXi hosts

Am 23.05.2017 vom Typ: Troubleshooting
Titel: „Issue of delete blocks failed“ error is displayed in vmkernel.log file

Am 23.05.2017 vom Typ: Troubleshooting
Titel: vCenter Appliance root Partition 100% full due to Audit.log files not being rotated

Am 23.05.2017 vom Typ: How to
Titel: Installing and configuring the NVIDIA VIB on ESXi

Am 23.05.2017 vom Typ: Troubleshooting
Titel: ESXi 6.0 host is disconnected from vCenter Server

Am 23.05.2017 vom Typ: Troubleshooting
Titel: vRealize Orchestrator 6.0.4 appliance is unable to connect to SQL Server via SSL

Am 23.05.2017 vom Typ: Troubleshooting
Titel: vSAN node fails to enter the maintenance mode in current state

Am 23.05.2017 vom Typ: Troubleshooting
Titel: Folder redirection configured by UEM does not show the redirected location

Am 23.05.2017 vom Typ: Troubleshooting
Titel: After upgrading hosts to ESXi 6.5 LUNs are missing

Am 23.05.2017 vom Typ: Alerts, Informational, Troubleshooting
Titel: ESXi host fails with intermittent NMI purple diagnostic screen on HP Gen8 servers

Am 23.05.2017 vom Typ: Troubleshooting
Titel: Domain users having authentication issues in SRM 6.1 with Federated SSO / PSC

Am 23.05.2017 vom Typ: Troubleshooting
Titel: vRealize Operations Manager 6.3 fails to appear online with Waiting for Analytics status for Cluster nodes in Admin UI

Am 23.05.2017 vom Typ: Troubleshooting
Titel: Deploying VMware vSphere Replication fails at registration with the error: Error applying startup configuration: com.vmware.vr-UUID

Am 23.05.2017 vom Typ: Troubleshooting
Titel: Workaround for Apache Struts CVE-2017-5638 for vCenter Server 6.0

Am 23.05.2017 vom Typ: Troubleshooting
Titel: DPI synchronization problems with Windows Server 2012 RDS desktops and applications

Am 23.05.2017 vom Typ: Troubleshooting
Titel: Virtual machine power off during snapshot consolidation

Am 23.05.2017 vom Typ: Troubleshooting
Titel: Updating vCenter Server 6.0 to a later release fails on VCSServiceManager with error code ‚1603‘

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

Am 23.05.2017 vom Typ: Informational, Troubleshooting
Titel: Using Non-PCI storage adapters in VMware vSphere 6.0 results in heap exhaustion

Ausführliche Auflistung:

Titel: How to unmount a LUN or detach a datastore device from ESXi hosts

Knowledgebase Nr: 2004605

Kategorie: Best Practices, How to

Aktualisiert: 23.05.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: 2004605

Beschreibung:
This article provides steps to unmount a LUN from an ESXi 5.x/6.x host, which includes unmounting the file system and detaching the datastore/storage device. These steps must be performed for each ESXi host.Note: The documented method using the vSphere Client is limited to detaching the device on a per-host basis. To detach a storage device from multiple hosts at the same time, see Automating detaching datastores using PowerCLI and the vSphere SDK for Perl in the Resolution section in this…
… Für weitere Details den Link zum Artikel anklicken

Titel: „Issue of delete blocks failed“ error is displayed in vmkernel.log file

Knowledgebase Nr: 2146505

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2146505

Beschreibung:
In the /var/log/vmkernel.log file, you see entries similar to:FSDisk: 260: Issue of delete blocks failed [sync:0] numDescs 1 Address is not aligned on required boundary0x439dc0c5cb40 hostd process gets crashed. Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter Appliance root Partition 100% full due to Audit.log files not being rotated

Knowledgebase Nr: 2149278

Aktualisiert: 23.05.2017

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

Link zum Artikel: 2149278

Beschreibung:
100% capacity used for /dev/sda3. Size of audit.log file is very large and /var/log/audit folder consumes majority of the space. Saved logs from log rotate policy reference a date that is not in line with the policy. Unable to connect to the vCenter Server as services are not started. Running /etc/cron.daily/logrotate manually rotates logs as expected.
… Für weitere Details den Link zum Artikel anklicken

Titel: Installing and configuring the NVIDIA VIB on ESXi

Knowledgebase Nr: 2033434

Kategorie: How to

Aktualisiert: 23.05.2017

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

Link zum Artikel: 2033434

Beschreibung:
Before using the hardware-based (GPU) virtual Shared Graphics Acceleration (vSGA) and vGPU feature in vSphere, you must install and configure the NVIDIA GPU VIB (vSphere Installation Bundle) on ESXi.This feature is supported in Horizon View 5.2 and later releases.Note: This vSphere 5.1 feature is not supported in Horizon View 5.1 or earlier.
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi 6.0 host is disconnected from vCenter Server

Knowledgebase Nr: 2145106

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2145106

Beschreibung:
ESXi hosts appear as Not Responding in vCenter Server. Running esxcli commands on the ESXi host fail with the error:Error interacting with configuration file /etc/vmware/lunTimestamps.log: Timeout while waiting for lock, /etc/vmware/lunTimestamps.log.LOCK, to be released. Another process has kept this file locked for more than 30 seconds. The process currently holding the lock is smartd(PID). This is likely a temporary condition. Please try your operation again.Note: PID is the process ID for…
… Für weitere Details den Link zum Artikel anklicken

Titel: vRealize Orchestrator 6.0.4 appliance is unable to connect to SQL Server via SSL

Knowledgebase Nr: 2150247

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware vRealize Orchestrator 6.0.x

Link zum Artikel: 2150247

Beschreibung:
vRealize Orchestrator 6.0.4 appliance unable to connect to SQL Database over SSL. In the /var/lib/vco/configuration/catalina.out log, you see the entries similar to:2658263 [Validation : Database] ERROR ch.dunes.vso.configuration.web.commons.database.DB_SQLServer – Error while testing connectionch.dunes.vso.db.DatabaseException: Cannot connect with jdbc:jtds:sqlserver://sql_server_Name_FQDN:49758/SD_VAUTOP2Orchestrator_VCO2;domain=FQDN;instance=sql_server_name;useNTLMv2=true;ssl=authenticate -…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN node fails to enter the maintenance mode in current state

Knowledgebase Nr: 2150271

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

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

Link zum Artikel: 2150271

Beschreibung:
vSAN node fails to enter the maintenance mode. You will see the error similar to: „host can not enter the maintenance mode in current state.“ cmmds-tool find -t NODE_DECOM_STATE -f json displays the entries for the affected host similar to:“uuid“: „xx_id“,“owner“: „xx_id“,“health“: „Healthy“,“revision“: „146“,“type“: „NODE_DECOM_STATE“,“flag“: „2“,“minHostVersion“: „0“,md5sum“: „12157ef595dabe28b6f8b50501f4d8c1″,“valueLen“: „128“,“content“: {„decomState“: 4, „decomJobType“: 2,…
… Für weitere Details den Link zum Artikel anklicken

Titel: Folder redirection configured by UEM does not show the redirected location

Knowledgebase Nr: 2150264

Aktualisiert: 23.05.2017

Link zum Artikel: 2150264

Beschreibung:
When a user logs in to a session to open the My Documents or other redirected folders, the location points to C:UsersusernameDocuments and not to the redirected network location.Example:If user wants to open the My Documents folder under the This PC section in the Explorer, the location points to C:UsersusernameDocuments and not to the redirected network location. The My Documents folder under Quick access might still point to the correct redirected network location. Note: This behavior…
… Für weitere Details den Link zum Artikel anklicken

Titel: After upgrading hosts to ESXi 6.5 LUNs are missing

Knowledgebase Nr: 2150253

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware ESXi 6.5.x

Link zum Artikel: 2150253

Beschreibung:
Upgrading ESXi hosts to 6.5 causes LUN not to be seen.In the vmkernel.log you see messages similar to:2017-03-09T20:38:56.567Z cpu5:65786)ScsiUid: 403: Existing device naa.60060e80101b7280058bb6f80000000f already has uid vml.020001000060060e80101b7280058bb6f80000000f4446363030462017-03-09T20:38:56.567Z cpu5:65786)ScsiDevice: 4163: Failing registration of device ’naa.60060e80101b7280058bb6f80000000f’2017-03-09T20:38:56.567Z cpu5:65786)ScsiDevice: 4165: Failed to add legacy uid…
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host fails with intermittent NMI purple diagnostic screen on HP Gen8 servers

Knowledgebase Nr: 2085921

Kategorie: Alerts, Informational, Troubleshooting

Aktualisiert: 23.05.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: 2085921

Beschreibung:
When ESXi host runs on HP Gen8 servers, you experience these symptoms: ESXi host experiences Intermittent Non-Maskable interrupt purple diagnostic screen. You see a backtrace similar to: BlueScreen: LINT1/NMI (motherboard nonmaskable interrupt), undiagnosed. This may be a hardware problem; please contact your hardware vendor. Code start: 0x418021400000 VMK uptime: 40:20:33:47.842 PanicvPanicInt@vmkernel#nover+0x575 stack: 0x412400000008 Panic_NoSave@vmkernel#nover+0x49 stack:…
… Für weitere Details den Link zum Artikel anklicken

Titel: Domain users having authentication issues in SRM 6.1 with Federated SSO / PSC

Knowledgebase Nr: 2147524

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Link zum Artikel: 2147524

Beschreibung:
When clicking on sites in the SRM plug-in, domain user reports an error:Cannot complete login due to an incorrect user name or password In the srm logs on the protected site, you see entries similar to:2016-01-04T12:36:16.854-06:00 [60552 trivia ‚SsoClient‘] Result: true2016-01-04T12:36:16.854-06:00 [60552 trivia
‚SsoClient‘] opId=52b998da-fb9b-ee50-04af-28beded04e17 END operation SecurityTokenServiceImpl::ValidateSubject2016-01-04T12:36:16.854-06:00 [60552 verbose ‚SessionManager‘]…
… Für weitere Details den Link zum Artikel anklicken

Titel: vRealize Operations Manager 6.3 fails to appear online with Waiting for Analytics status for Cluster nodes in Admin UI

Knowledgebase Nr: 2149785

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

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

Link zum Artikel: 2149785

Beschreibung:
vRealize Operations Manager fails to appear online after Cluster restart Upgrading of vRealize Operations Manager 6.3 to either 6.4 or 6.4 appears to hang at stage 3 or 4 of 9Cluster Status for nodes in Admin UI shows Waiting for Analytics. In the vRealize Operations Manager node analytics-UUID_of_Master_Node.log file, you see the entries similar to: INFO [pool-9-thread-1 ] com.vmware.statsplatform.persistence.sqldb.SQLDBMasterStatusChecker.run – spring service not ready, skip checking In…
… Für weitere Details den Link zum Artikel anklicken

Titel: Deploying VMware vSphere Replication fails at registration with the error: Error applying startup configuration: com.vmware.vr-UUID

Knowledgebase Nr: 2120154

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware vSphere Replication 6.0.x, VMware vSphere Replication 6.1.x

Link zum Artikel: 2120154

Beschreibung:
vSphere Replication was previously deployed and removed from the VMware vCenter Server The vSphere Replication appliance virtual appliance management interface displays this error when you click Save and Restart: Error applying startup configuration: com.vmware.vr-UUID The /opt/vmware/hms/hms-configtool.log file shows errors similar to:<YYYY-MM-DD>T<Time> vsphere.local 2d8652df-8b87-466f-89b6-22f3307575a0 ERROR] [IdentityManager] Failed to delete principalName…
… Für weitere Details den Link zum Artikel anklicken

Titel: Workaround for Apache Struts CVE-2017-5638 for vCenter Server 6.0

Knowledgebase Nr: 2149434

Aktualisiert: 23.05.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2149434

Beschreibung:
There is a catastrophic vulnerability tracked by CVE-2017-5638. This vulnerability affects the vCenter Server Appliance and vCenter Server on Windows. This article provides a workaround for the security issue CVE-2017-5638 by disabling the performance charts service. Before applying the workaround see VMSA-2017-0004 for up to date information on this vulnerability. The following versions of the vCenter Server Appliance and vCenter Server are impacted with the CVE-2017-5638 issue: VMware…
… Für weitere Details den Link zum Artikel anklicken

Titel: DPI synchronization problems with Windows Server 2012 RDS desktops and applications

Knowledgebase Nr: 2149334

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware Horizon Client for Android 4.5.x, VMware Horizon Client for Windows 4.5.x, VMware Horizon Client for iOS 4.5.x

Link zum Artikel: 2149334

Beschreibung:
If you enable DPI synchronization in Horizon Client and launch a Windows Server 2012 RDS desktop or application, black blocks appear on the screen. This problem occurs when a low resolution is combined with a high DPI value. It occurs most frequently with Horizon Client for Android.The DPI synchronization feature is supported in Horizon Client for Windows 4.2 and later, Horizon Client for Android 4.5 and later, and Horizon Client for iOS 4.5 and later. In Horizon Client for Android, the DPI…
… Für weitere Details den Link zum Artikel anklicken

Titel: Virtual machine power off during snapshot consolidation

Knowledgebase Nr: 2144095

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

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

Link zum Artikel: 2144095

Beschreibung:
When Changed Block Tracking (CBT) is enabled and ESXi hosts in the environment are running ESXi 5.1 or later, you experience these symptoms: When attempting a snapshot consolidation, virtual machines running on block storage power off. Virtual machines state that an error occurred during the quiesce process. The vmware.log file for the virtual machine in question reports entries similar to:2016-01-27T13:53:31.687Z| vcpu-0| I120:…
… Für weitere Details den Link zum Artikel anklicken

Titel: Updating vCenter Server 6.0 to a later release fails on VCSServiceManager with error code ‚1603‘

Knowledgebase Nr: 2148327

Kategorie: Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2148327

Beschreibung:
Upgrading vCenter Server to 6.0 fails on VCSServiceManager with this error: Installation of component VCSServiceManager failed with error code ‚1603‘. Check the logs for more details Inventory service fails to start. In the firstbootrun-updateboot-scripts.log file, you see entries similar to:Error waiting for service invsvc start. Exit code: 1066 Current State: 1ERROR:root:Unable to start service invsvc The upgrade rolls back. In the %ALLUSERSPROFILE%VMWarevCenterServerlogsinvsvc.log file,…
… 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: 23.05.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: Using Non-PCI storage adapters in VMware vSphere 6.0 results in heap exhaustion

Knowledgebase Nr: 2137341

Kategorie: Informational, Troubleshooting

Aktualisiert: 23.05.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2137341

Beschreibung:
During regular operations on VMware vSphere 6.0 host with EMC ScaleIO (or similar non-PCI) storage adapters, you see these events: The host becomes unresponsive. Virtual machines on the host stop running. The storage heap of the host gets exhausted. In the /var/log/vmkernel.log file, you see errors similar to::2015-10-09T12:42:59.212Z cpu19:34059)WARNING: ScsiSched: 1338: SCSISchedQAllocByType: could not allocate scheduler queue for world 02015-10-09T12:42:59.213Z cpu3:1724704)WARNING:…
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2017-05-24T08:04:19+00:00Mai 24th, 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