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

Vom 12.06.2017 bis zum 13.06.2017 wurden 24 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 12.06.2017 vom Typ: Troubleshooting
Titel: ESXi 6.x vSAN host experiences a purple diagnostic screen at bora/modules/vmkernel/lsomcommon/ssdlog/ssdopslog.c:199

Am 12.06.2017 vom Typ: How to, Troubleshooting
Titel: ESXi 6.5 does not recognize Datastores that were recognized before with ESXi 5.x or 6.0

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Domain joining on a new desktop in VMware Horizion DaaS fails with the error: empty configured hostname

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Configuring a Windows Server 2008 R2 as a Desktop

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Single Sign-On support in VMware Horizon Cloud with Hosted Infrastructure and VMware Horizon DaaS

Am 12.06.2017 vom Typ: Troubleshooting
Titel: To track a user back to a session and a desktop

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Creating a pool in VMware Horizon Cloud with Hosted Infrastructure or Horizon DaaS fails with the error: DaaSAgent message – Bad domain info returned

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Increasing the amount of memory assigned to a virtual machine

Am 12.06.2017 vom Typ: Troubleshooting
Titel: LUNs are missing after upgrading the hosts to ESXi 6.5

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Configuring SAN certificates for vRA instances where the IaaS server domain names differ from the load balancer domain

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Unable to reconfigure two vNICs simultaneously by invoking reconfigVM_Task() API

Am 12.06.2017 vom Typ: How to
Titel: How to switch pDRS providers in vRealize Operations Manager 6.4

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

Am 12.06.2017 vom Typ: Troubleshooting
Titel: Cannot enable secure boot on ESXi 6.5 host that was upgraded

Am 12.06.2017 vom Typ: Troubleshooting
Titel: vCenter Server Database Health Alarm causes vCenter Server to shut down

Am 12.06.2017 vom Typ: Troubleshooting
Titel: vSAN Health Service – vSAN iSCSI target service – Home object

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

Am 12.06.2017 vom Typ: Troubleshooting
Titel: vSAN Health Service – vSAN iSCSI target service – Network configuration

Am 12.06.2017 vom Typ: Troubleshooting
Titel: VMware Identity Manager Cloud Hosted IP Addresses Change

Am 12.06.2017 vom Typ: Troubleshooting
Titel: VMware Identity Manager – „404 Page Not Found“ errors after configuring a clustered envrionment.

Am 12.06.2017 vom Typ: Patch
Titel: VMware Identity Manager – Messaging Connection failure in a clustered environment

Am 12.06.2017 vom Typ: Troubleshooting
Titel: ESXi 6.5, earlier versions might not enable all VFs of PCI SR-IOV device

Am 12.06.2017 vom Typ: Informational, Troubleshooting
Titel: Database in read-only mode under System Diagnostic Dashboard

Am 12.06.2017 vom Typ: Troubleshooting
Titel: NVIDIA Tesla card shows Active Mode as Basic and Memory as 0.00 B in vSphere Web Client.

Ausführliche Auflistung:

Titel: ESXi 6.x vSAN host experiences a purple diagnostic screen at bora/modules/vmkernel/lsomcommon/ssdlog/ssdopslog.c:199

Knowledgebase Nr: 2146345

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

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

Link zum Artikel: 2146345

Beschreibung:
A vSAN 6.x host fails with a purple diagnostic screen. The purple diagnostic screen contains entries similar to:PanicvPanicInt@vmkernel#nover+0x36b stack: 0x417ff6af0980, 0x41803682015-04-20T16:27:38.399Z cpu7:1000015002)0x439124d1a780:[0x4180368ad6b7]Panic_vPanic@vmkernel#nover+0x23 stack: 0x46a, 0x4180368d7bc1, 0x43a2015-04-20T16:27:38.411Z cpu7:1000015002)0x439124d1a7a0:[0x4180368d7bc1]vmk_PanicWithModuleID@vmkernel#nover+0x41 stack: 0x439124d1a800, 0x42015-04-20T16:27:38.423Z…
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi 6.5 does not recognize Datastores that were recognized before with ESXi 5.x or 6.0

Knowledgebase Nr: 2148265

Kategorie: How to, Troubleshooting

Aktualisiert: 12.06.2017

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

Link zum Artikel: 2148265

Beschreibung:
VMFS datastores may be absent after upgrading to ESXi 6.5 despite path availability.After upgrading an ESXi host version 6.5, one or more datastores may be absent.The vmkernel log reports an error around UUIDs and device-registration failures:2017-06-02T17:12:54.076Z cpu23:65974)ScsiUid: 403: Existing device naa.6001f931059e80000113000200000000 already has uid vml.02000400006001f931059e800001130002000000004953453234302017-06-02T17:12:54.076Z cpu23:65974)ScsiDevice: 4163: Failing registration of…
… Für weitere Details den Link zum Artikel anklicken

Titel: Domain joining on a new desktop in VMware Horizion DaaS fails with the error: empty configured hostname

Knowledgebase Nr: 2100344

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Link zum Artikel: 2100344

Beschreibung:
Domain join on new desktop fails.In the DaaS agent log, you see the error:empty configured hostname returned by element
… Für weitere Details den Link zum Artikel anklicken

Titel: Configuring a Windows Server 2008 R2 as a Desktop

Knowledgebase Nr: 2100073

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Link zum Artikel: 2100073

Beschreibung:
This article provides information about configuring a Windows Server 2008 R2 as a Desktop.Note: This article is applicable to the following products: VMware Horizon DaaS Bundle (VDI/RDSH Edition)VMware Horizon Cloud with Hosted Infrastructure (formerly known as VMware Horizon Air Cloud-Hosted)VMware Horizon DaaS On Premise Platform
… Für weitere Details den Link zum Artikel anklicken

Titel: Single Sign-On support in VMware Horizon Cloud with Hosted Infrastructure and VMware Horizon DaaS

Knowledgebase Nr: 2100106

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Link zum Artikel: 2100106

Beschreibung:
This article provides information about Single Sign-On support in VMware Horizon Cloud with Hosted Infrastructure (formerly known as VMware Horizon Air Cloud-Hosted) and VMware Horizon DaaS.
… Für weitere Details den Link zum Artikel anklicken

Titel: To track a user back to a session and a desktop

Knowledgebase Nr: 2100265

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Link zum Artikel: 2100265

Beschreibung:
This article provides steps to track a user back to a session and a desktop. Note: This article is applicable to the following products:VMware Horizon DaaS Bundle (VDI/RDSH Edition)VMware Horizon Cloud with Hosted Infrastructure (formerly known as VMware Horizon Air Cloud-Hosted)VMware Horizon DaaS On Premise Platform
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating a pool in VMware Horizon Cloud with Hosted Infrastructure or Horizon DaaS fails with the error: DaaSAgent message – Bad domain info returned

Knowledgebase Nr: 2100287

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Link zum Artikel: 2100287

Beschreibung:
Creating a pool in VMware Horizon Cloud with Hosted Infrastructure (formerly known as VMware Horizon Air Cloud-Hosted) or Horizon DaaS fails.You see the error:DaaSAgent – Bad domain info returned. Required field/s in domain information is/are empty
… Für weitere Details den Link zum Artikel anklicken

Titel: Increasing the amount of memory assigned to a virtual machine

Knowledgebase Nr: 1004059

Aktualisiert: 12.06.2017

Link zum Artikel: 1004059

Beschreibung:
This article describes how to increase the amount of memory assigned to a virtual machine. Increasing the amount of memory assigned to a virtual machine may be required if the memory requirements have changed since the time of its creation. The article addresses problems encountered with the virtual machine’s operating system as a result of having insufficient memory. Insufficient memory problems result in slow operating system performance, slow application performance, and the…
… Für weitere Details den Link zum Artikel anklicken

Titel: LUNs are missing after upgrading the hosts to ESXi 6.5

Knowledgebase Nr: 2150253

Kategorie: Troubleshooting

Aktualisiert: 12.06.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 entries 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: Configuring SAN certificates for vRA instances where the IaaS server domain names differ from the load balancer domain

Knowledgebase Nr: 2150346

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Für Produkte: VMware vRealize Automation 7.3.x

Link zum Artikel: 2150346

Beschreibung:
In some configurations the domain portion of the IaaS server’s individual FQDNs differ from the load balancing FQDN. In such case, when generating the certificate for the web server role, the certificate should contain both the load balancing FQDN and the server’s FQDNs as Subject Alternative Names. On some occasions, a SAN certificate cannot be generated and a wildcard certificate representing only the domain of the load balancing FQDN must be used.For Example:vRealize Automation Appliance…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to reconfigure two vNICs simultaneously by invoking reconfigVM_Task() API

Knowledgebase Nr: 2114609

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Für Produkte: VMware vSphere Web Services SDK 5.5

Link zum Artikel: 2114609

Beschreibung:
Reconfiguring two vNICs using ExtraConfig property simultaneously by invoking reconfigVM_Task()API fails. This issue is seen to occur while using, but is not restricted to, Trend Micro’s Deep Security software.
… Für weitere Details den Link zum Artikel anklicken

Titel: How to switch pDRS providers in vRealize Operations Manager 6.4

Knowledgebase Nr: 2147716

Kategorie: How to

Aktualisiert: 12.06.2017

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

Link zum Artikel: 2147716

Beschreibung:
This article provides steps to change the pDRS provider of a vSphere 6.5 or higher instance. Changing the pDRS provider of a vSphere 6.5 or higher instance results in a complete changeover of pDRS data. For example: If vRealize Operations Manager instance A is the pDRS provider for a vSphere 6.5 or higher instance and has 60 days worth of vSphere data, and the pDRS provider is switched to vRealize Operations Manager instance B that only has 20 days worth of vSphere data, the results in…
… Für weitere Details den Link zum Artikel anklicken

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

Knowledgebase Nr: 2147627

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

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: Cannot enable secure boot on ESXi 6.5 host that was upgraded

Knowledgebase Nr: 2147606

Aktualisiert: 12.06.2017

Für Produkte: VMware ESXi 6.5.x

Link zum Artikel: 2147606

Beschreibung:
If you upgrade an ESXi host from ESXi 5.5 or ESXi 6.0 to ESXi 6.5, and you attempt to enable secure boot on that host, an error results.If the error indicates that this problem is caused by the lsu-lsi-mptsas-plugin VIB, you can remove that VIB without complications. CAVEATS: If you performed the upgrade by using ESXCLI instead of using the ISO, you cannot resolve the problem by removing the VIB. If the error indicates that other VIBs prevent enabling secure boot, you are responsible for…
… Für weitere Details den Link zum Artikel anklicken

Titel: vCenter Server Database Health Alarm causes vCenter Server to shut down

Knowledgebase Nr: 2147618

Aktualisiert: 12.06.2017

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2147618

Beschreibung:
This KB article describes the predefined vCenter Server Database Health Alarm, which operates at the vCenter Server level. Every 15 minutes, vCenter Server checks how much free space a database has and triggers an alarm in accordance with preconfigured thresholds. A warning is issued when the database is 80% full. vCenter Server shuts down when the database is 95% full. You can determine whether a shut down was caused by the lack of free space through one of the following methods: Check…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – vSAN iSCSI target service – Home object

Knowledgebase Nr: 2147601

Aktualisiert: 12.06.2017

Link zum Artikel: 2147601

Beschreibung:
This article explains the vSAN iSCSI target service – Home object check in the vSAN Health Service and provides details about why it might report an error.
… 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: 12.06.2017

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: vSAN Health Service – vSAN iSCSI target service – Network configuration

Knowledgebase Nr: 2147602

Aktualisiert: 12.06.2017

Link zum Artikel: 2147602

Beschreibung:
This article explains the vSAN iSCSI target service – Network configuration check in the vSAN Health Service and provides details about why it might report an error.
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware Identity Manager Cloud Hosted IP Addresses Change

Knowledgebase Nr: 2149884

Aktualisiert: 12.06.2017

Link zum Artikel: 2149884

Beschreibung:
Note: June 12, 2017 – Americas Region The IP addresses for Access Gateway User/Admin Portal and Android SSO Certificate Authentication Proxy mentioned in this KB article for changes to be made on May 15, 2017 are not accurate and should not be used. These IP addresses were reassigned before the migration of the VMware Identity Manager US data center gateway services. VMware Identity Manger…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware Identity Manager – „404 Page Not Found“ errors after configuring a clustered envrionment.

Knowledgebase Nr: 2149675

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Für Produkte: VMware Identity Manager 2.x

Link zum Artikel: 2149675

Beschreibung:
Service does not start up or takes very long to start. Messaging (RabbitMQ) is done correctly.On the browser, you see error similar to:404 Page Not Found
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware Identity Manager – Messaging Connection failure in a clustered environment

Knowledgebase Nr: 2149719

Kategorie: Patch

Aktualisiert: 12.06.2017

Für Produkte: VMware Identity Manager 2.x

Link zum Artikel: 2149719

Beschreibung:
If System Information and Health shows the health is Red because of error: Messaging Connection failures. In the horizon.log, you see entries similar to: „connection or channel shutdown by RabbitMQ: connection error; protocol method“ or additional RabbiTMQ errors. Running the below commands shows the consumer health down: a) . /usr/local/horizon/scripts/hzn-bin.incb) curl -ks https://localhost/SAAS/jersey/manager/api/messaging/health/stats | python -mjson.tool If output displays: …
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi 6.5, earlier versions might not enable all VFs of PCI SR-IOV device

Knowledgebase Nr: 2147604

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

Für Produkte: VMware ESXi 6.5.x

Link zum Artikel: 2147604

Beschreibung:
On some platforms, ESXi might fail to enable all virtual functions (VFs) of a PCI SR-IOV device as requested by the device’s physical function (PF) driver. This failure results in hardware resources being unused or wasted.This problem occurs on platforms where the BIOS or UEFI firmware programs the PF’s base address registers (BARs) so that gaps of unassigned physical address space are left within the parent PCI-PCI bridge’s memory apertures. For example, non-prefetchable and prefetchable base…
… Für weitere Details den Link zum Artikel anklicken

Titel: Database in read-only mode under System Diagnostic Dashboard

Knowledgebase Nr: 2146543

Kategorie: Informational, Troubleshooting

Aktualisiert: 12.06.2017

Für Produkte: VMware Identity Manager 2.x

Link zum Artikel: 2146543

Beschreibung:
Database shows read only mode even though we can make changes to vIDM configurations:Change entitlementAdd/Remove Users /Groups/application etc.Under SaaS Database Properties „Database Read-Only“ is set to FalseIn horizon.log, you see entries similar to: ERROR (main) [;;] com.vmware.horizon.datastore.impl.DbConnectionCheckServiceImpl – Error connecting the databasecom.microsoft.sqlserver.jdbc.SQLServerException: There is already an object named ‚id_pkey‘ in the database. at…
… Für weitere Details den Link zum Artikel anklicken

Titel: NVIDIA Tesla card shows Active Mode as Basic and Memory as 0.00 B in vSphere Web Client.

Knowledgebase Nr: 2150436

Kategorie: Troubleshooting

Aktualisiert: 12.06.2017

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

Link zum Artikel: 2150436

Beschreibung:
After installing an NVIDIA M6, M10, or M60 graphics card in your ESXi host and loading the corresponding VIB, you are unable to assign VMs to the graphics card.In Host -> Configure -> Hardware -> Graphics -> Graphics Devices, the Configured Type might be set to Shared or Shared Direct, and yet Active Type will show Basic. The Memory field will show 0.00 B.From an SSH session, running the command cat /var/log/Xorg.log | grep -E „GPU|nv“ will show no results.
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

Schreibe einen Kommentar

Deine E-Mail-Adresse wird nicht veröffentlicht. Erforderliche Felder sind mit * markiert.