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

Vom 11.08.2017 bis zum 12.08.2017 wurden 24 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Volume Purchasing Program (VPP) FAQ – General Information

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Licensing section is missing in Web Client with Windows vCenter Server

Am 11.08.2017 vom Typ: Patch, Troubleshooting
Titel: PSOD on ESXi while vMotion: PF Exception 14 in world xxxxxxx :vmotionRecvH

Am 11.08.2017 vom Typ: Troubleshooting
Titel: VMware ESXi 5.x and 6.0 host stops sending syslogs to remote server

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Stopping, starting, or restarting services in vCenter Server Appliance 6.5

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Storing ESXi coredump and scratch partitions in vSAN

Am 11.08.2017 vom Typ: Troubleshooting
Titel: VMware vSphere Web Client 6.0 reports the error: Unable to load recent tasks from one or more vCenter Server systems: No matching LinkedVcGroup Found

Am 11.08.2017 vom Typ: Troubleshooting
Titel: ESXi host version requirements in a vSAN cluster

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Build numbers and versions of VMware NSX for vSphere

Am 11.08.2017 vom Typ: How to
Titel: Using VMware vSphere On-disk Metadata Analyzer to re-create missing partition tables on VMware ESXi

Am 11.08.2017 vom Typ: Patch, Troubleshooting
Titel: Errors occur when running the background jobs

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Unable to install Mirage Management Server because Secondary Logon Service is disabled

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Advanced setting „ScratchConfig.ConfiguredScratchLocation“ for persistent scratch location is reverted to the default value after ESXi 6.5 U1 host reboot

Am 11.08.2017 vom Typ: Troubleshooting
Titel: When using ESXi 6.0 and vCenter Server 6.5, adding an instant-clone desktop pool fails with the error: The resource “ is in use.

Am 11.08.2017 vom Typ: Informational
Titel: Build numbers and versions of VMware vSAN

Am 11.08.2017 vom Typ: Troubleshooting
Titel: How to view the Subscription Service Detail Page in My VMware

Am 11.08.2017 vom Typ: Troubleshooting
Titel: VIO Not all the volumes attached to an instance are correctly shown up inside a Linux guest OS.

Am 11.08.2017 vom Typ: Troubleshooting
Titel: ScratchConfig.CurrentScratchLocation is set to /scratch after upgrading to ESXi 6.x

Am 11.08.2017 vom Typ: Informational
Titel: NSX 6.3.3 does not support ESXi versions earlier than 6.0 Update 2 or 5.5 Update 1

Am 11.08.2017 vom Typ: Troubleshooting
Titel: Error „SSL Certificate add failed, Error: 183“ while installing vRA

Am 11.08.2017 vom Typ: Informational, Troubleshooting
Titel: VIO meta-data of vmware:hw_version on flavor or vmware_hw_version on images fails with „A component of the virtual machine is not accessible on the host“

Am 11.08.2017 vom Typ: Informational
Titel: Setting up active-passive dual pathing with vSAN and vSphere

Am 11.08.2017 vom Typ: Troubleshooting
Titel: OVF deployment fails after upgrading to vCenter Server Appliance 6.5 U1

Am 11.08.2017 vom Typ: Troubleshooting
Titel: 2400 second timeout error during VM deployment when Storage DRS is enabled

Ausführliche Auflistung:

Titel: Volume Purchasing Program (VPP) FAQ – General Information

Knowledgebase Nr: 1024540

Aktualisiert: 11.08.2017

Link zum Artikel: 1024540

Beschreibung:
What is the VMware Volume Purchasing Program (VPP)? VMware’s Volume Purchasing Program (VPP) is an end customer purchasing program that rewards our customers, and helps maximize their investment in VMware software. By enrolling and purchasing under VPP, customers can lower their total cost of VMware software ownership over a rolling two-year period. VPP rewards customers for prior purchases, enables consistent savings for customers and their authorized affiliates, and provides online tools to…
… Für weitere Details den Link zum Artikel anklicken

Titel: Licensing section is missing in Web Client with Windows vCenter Server

Knowledgebase Nr: 2151025

Aktualisiert: 11.08.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2151025

Beschreibung:
You are using VMware vCenter Server 6.0 installed on Windows Server. When you log in to vSphere Web Client, Licensing section is missing under Administration section. There is no selection for Licenses or Reports, you see a blank page. You see this issue for all users including administrator@vsphere.local.
… Für weitere Details den Link zum Artikel anklicken

Titel: PSOD on ESXi while vMotion: PF Exception 14 in world xxxxxxx :vmotionRecvH

Knowledgebase Nr: 2147271

Kategorie: Patch, Troubleshooting

Aktualisiert: 11.08.2017

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

Link zum Artikel: 2147271

Beschreibung:
The ESXi host fail with a purple diagnostic screen.The purple diagnostic screen contains entries similar to: cpu14:2999181)0x4392dc69bd30:[0x41800a865fb1]MCSLockWithFlagsWork@vmkernel#nover+0x1 stack: 0x4304c17b24d0, 0x0, cpu14:2999181)0x4392dc69bd60:[0x41800b4924c0]DVFilterCheckpointGetSize@com.vmware.vmkapi#v2_3_0_0+0x78 stack: 0xb cpu14:2999181)0x4392dc69bdc0:[0x41800bc73a8a]VMotionRecv_GetDVFilterState@esx#nover+0x26 stack: 0x4306172d24c0, 0 …
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware ESXi 5.x and 6.0 host stops sending syslogs to remote server

Knowledgebase Nr: 2003127

Kategorie: Troubleshooting

Aktualisiert: 11.08.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: 2003127

Beschreibung:
You have configured an ESXi 5.x host’s syslog service to route system log streams to a remote syslog server using any of the methods described in Configuring syslog on ESXi 5.x (2003322). An ESXi 5.x and 6.0 host stops sending logs to a remote syslog server. You see the event message:esx.problem.vmsyslogd.remote.failure In the /var/log/vodb.log file, you see entries similar to:[UserLevelCorrelator] nnnnnnnnus: [vob.user.vmsyslogd.remote.failure] The host „10.11.12.13:514“ has become…
… Für weitere Details den Link zum Artikel anklicken

Titel: Stopping, starting, or restarting services in vCenter Server Appliance 6.5

Knowledgebase Nr: 2147152

Aktualisiert: 11.08.2017

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

Link zum Artikel: 2147152

Beschreibung:
This article provides information on how to manage vCenter server appliance using the service-control command. This can be accessed through the Appliance Shell or BASH Shell.
… Für weitere Details den Link zum Artikel anklicken

Titel: Storing ESXi coredump and scratch partitions in vSAN

Knowledgebase Nr: 2074026

Aktualisiert: 11.08.2017

Für Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2074026

Beschreibung:
vSAN provides the following storage solutions for ESXi coredump and scratch partitions: Assign one disk for each host. When you install vSAN on a local disk, a disk is automatically assigned to the host. Use this approach for hosts with more than 512GB of memory. Use a USB or SD card and do not set scratch partitions as non-persistent. vSAN tracefiles take up space in a coredump, so a 4GB SD or USB card is sufficient to support coredumps for hosts with up to 512GB of memory rather than 1TB…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSphere Web Client 6.0 reports the error: Unable to load recent tasks from one or more vCenter Server systems: No matching LinkedVcGroup Found

Knowledgebase Nr: 2116062

Kategorie: Troubleshooting

Aktualisiert: 11.08.2017

Für Produkte: VMware vCenter Server 6.0.x

Link zum Artikel: 2116062

Beschreibung:
After a sequential upgrade of vCenter Single Sign-On and vCenter Server in Multisite mode from 5.1.x to 6.0, you experience these symptoms: VMware vSphere Web Client displays an empty inventory In the vSphere Web Client, you see the error:No matching LinkedVcGroup Found
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host version requirements in a vSAN cluster

Knowledgebase Nr: 2148493

Aktualisiert: 11.08.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: 2148493

Beschreibung:
The compatibility between host ESXi software versions and vSAN on-disk format versions can vary, depending on the software version numbers. Upgrading the on-disk format in a vSAN cluster can affect the compatibility of each host’s ESXi version.
… Für weitere Details den Link zum Artikel anklicken

Titel: Build numbers and versions of VMware NSX for vSphere

Knowledgebase Nr: 2143854

Aktualisiert: 11.08.2017

Link zum Artikel: 2143854

Beschreibung:
This table lists the NSX for vSphere build numbers and versions of release dates:VersionRelease DateBuild NumberInstaller Build NumberVMware NSX for vSphere 6.3.32017-08-106276725N/A

VMware NSX for vSphere 6.3.2 Using VMware vSphere On-disk Metadata Analyzer to re-create missing partition tables on VMware ESXiKnowledgebase Nr: 2103078Kategorie: How toAktualisiert: 11.08.2017Für Produkte: VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.xLink zum Artikel: 2103078Beschreibung: This article explains steps to use the vSphere On-disk Metadata Analyzer (VOMA) to assist in the resolution of missing partition tables on devices which contain VMFS filesystems.Note: The VOMA functionality detailed here is added to ESXi 5.5 in patch 04. For more information on VMware ESXi 5.5 patch 04, see VMware ESXi 5.5, Patch Release ESXi550-201501001 (2099265). … Für weitere Details den Link zum Artikel anklickenTitel: Errors occur when running the background jobsKnowledgebase Nr: 2150417Kategorie: Patch, TroubleshootingAktualisiert: 11.08.2017Für Produkte: VMware App Volumes 2.12.xLink zum Artikel: 2150417Beschreibung: When running background jobs you see errors similar to: uninitialized constant Cvo::Ldap::Repository, uninitialized constant Cvo::Hypervisor::VcenterAdapter::VcenterStorage The errors could be self recover but the failure causes few issue … Für weitere Details den Link zum Artikel anklickenTitel: Unable to install Mirage Management Server because Secondary Logon Service is disabledKnowledgebase Nr: 2150372Kategorie: TroubleshootingAktualisiert: 11.08.2017Für Produkte: VMware Mirage 5.xLink zum Artikel: 2150372Beschreibung: Mirage management server fails to install at Setting default VMware Mirage Server Policies: default minimal set stage.You see the message:Quiet exec failed: Failed running process … Für weitere Details den Link zum Artikel anklickenTitel: Advanced setting „ScratchConfig.ConfiguredScratchLocation“ for persistent scratch location is reverted to the default value after ESXi 6.5 U1 host rebootKnowledgebase Nr: 2151270Aktualisiert: 11.08.2017Für Produkte: VMware ESXi 6.5.xLink zum Artikel: 2151270Beschreibung: Advanced setting ScratchConfig.ConfiguredScratchLocation for persistent scratch location is reverted to the default value after ESXi 6.5 U1 host reboot.Note: Scratch space is configured automatically during installation or first boot of an ESXi host, and is not required to be manually configured. ESXi Installable creates a 4 GB Fat16 partition on the target device during installation if there is sufficient space, and if the device is considered Local. The default value…… Für weitere Details den Link zum Artikel anklickenTitel: When using ESXi 6.0 and vCenter Server 6.5, adding an instant-clone desktop pool fails with the error: The resource “ is in use.Knowledgebase Nr: 2150925Aktualisiert: 11.08.2017Für Produkte: VMware ESXi 6.0.x, VMware Horizon 7 version 7.0.x, VMware Horizon 7 version 7.1.x, VMware Horizon 7 version 7.2.x, VMware vCenter Server 6.5.xLink zum Artikel: 2150925Beschreibung: Symptoms:Adding instant-clone desktop fails.On vCenter Server the VitualMachine.createForkChild.label task fails with the error: The resource ‚<number>‘ is in use.Cause:This issue occurs because of an internal design incompatibility in port binding between ESXi 6.0 and vCenter Server 6.5 when instant clone deployment is used. Currently, instant clone works when the versions of ESXi and vCenter Server are the same. (i.e. ESXi 6.0 with vCenter Server 6.0 or ESXi 6.5 with vCenter Server 6.5…… Für weitere Details den Link zum Artikel anklickenTitel: Build numbers and versions of VMware vSANKnowledgebase Nr: 2150753Kategorie: InformationalAktualisiert: 11.08.2017Link zum Artikel: 2150753Beschreibung: This table lists the vSAN build numbers and versions: vSAN version ESXi version ReleaseDate BuildNumber vSAN on-disk format version vSAN 6.6.1 ESXi 6.5 Update 1 2017-07-27 5969303 5 vSAN 6.6 ESXi 6.5.0d 2017-04-18 5310538 5 vSAN 6.5 Express Patch 1a ESXi 6.5 Express Patch 1a 2017-03-28 5224529 3 vSAN 6.5 Patch 01 ESXi 6.5 Patch 01 2017-03-09 5146846 3 vSAN 6.5.0a ESXi 6.5.0a 2017-02-02 4887370 3 vSAN 6.5 ESXi 6.5 GA 2016-11-15 4564106 3 vSAN 6.2…… Für weitere Details den Link zum Artikel anklickenTitel: How to view the Subscription Service Detail Page in My VMwareKnowledgebase Nr: 2151125Aktualisiert: 11.08.2017Link zum Artikel: 2151125Beschreibung: To view your Subscription Service details: Log in to My VMware. Select the Manage Services navigation tile in the upper right corner of the page. In the next page, click the Service Name of the Subscription service you want to view. In the Subscription Service Detail page, you can: View your account details such as: Status Service ID Start Date Offering Partner Bill Day Payment Method Fund Name Fund Expiration Usage Spend Notification Service Owner Support Level Expand the Manage…… Für weitere Details den Link zum Artikel anklickenTitel: VIO Not all the volumes attached to an instance are correctly shown up inside a Linux guest OS.Knowledgebase Nr: 2151093Aktualisiert: 11.08.2017Link zum Artikel: 2151093Beschreibung: After attaching some volumes to a Linux instance, not all of them, are correctly displayed inside the guest OS.For i.e.1) On Horizon VIO, have been attached seven volumes to the instance. 2) Inside Linux guest OS, only two of them are correctly displayed:[root@Linuxtest]# lsblkNAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTsda 8:0 0 12G 0 disk├─sda1 8:1 0 1M 0 part├─sda2 8:2 0 200M 0 part /boot└─sda3 8:3 0 4.8G 0 part└─VolGroup00-LogVol00 253:0 0 4.6G 0 lvm /sdb 8:16 0 10G 0 disksr0 11:0 1 548K 0…… Für weitere Details den Link zum Artikel anklickenTitel: ScratchConfig.CurrentScratchLocation is set to /scratch after upgrading to ESXi 6.xKnowledgebase Nr: 2151209Aktualisiert: 11.08.2017Für Produkte: VMware ESXi 6.5.xLink zum Artikel: 2151209Beschreibung: After upgrading an ESXi host using a custom image, you experience these symptoms.The ScratchConfig.CurrentScratchLocation is set to /scratch.You see these warnings:System logs on host [] are stored on non-persistent storage.AndNo scratch partition has been configured. Recommended scratch partition size is {} MiB.“ (Syslog.global.logdir = /scratch/log).Changing the ScratchConfig.CurrentScratchLocation does not persist between reboots. … Für weitere Details den Link zum Artikel anklickenTitel: NSX 6.3.3 does not support ESXi versions earlier than 6.0 Update 2 or 5.5 Update 1Knowledgebase Nr: 2151267Kategorie: InformationalAktualisiert: 11.08.2017Für Produkte: VMware ESXi 5.5.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x, VMware NSX for vSphere 6.3.xLink zum Artikel: 2151267Beschreibung: The minimum supported ESXi 5.5 and 6.0 versions has changed between NSX-v 6.3.3 and earlier versions of NSX. … Für weitere Details den Link zum Artikel anklickenTitel: Error „SSL Certificate add failed, Error: 183“ while installing vRAKnowledgebase Nr: 2150521Kategorie: TroubleshootingAktualisiert: 11.08.2017Für Produkte: VMware vRealize Automation 7.0.x, VMware vRealize Automation 7.1.x, VMware vRealize Automation 7.2.x, VMware vRealize Automation 7.3.xLink zum Artikel: 2150521Beschreibung: vRealize Automation (vRA) installation fails on Manager Service. Installation was performed with the same components previously and had to be reverted. Re-installation on the manager service server fails with the following error:SSL Certificate add failed, Error: 183Cannot create a file when that file already exists … Für weitere Details den Link zum Artikel anklickenTitel: VIO meta-data of vmware:hw_version on flavor or vmware_hw_version on images fails with „A component of the virtual machine is not accessible on the host“Knowledgebase Nr: 2150711Kategorie: Informational, TroubleshootingAktualisiert: 11.08.2017Link zum Artikel: 2150711Beschreibung: Specifying the hardware version in either the flavor with vmware:hw_version or in the image with vmware_hw_version succeeds but the resulting instance deployment fails.The meta-data of vmware:hw_version on flavor or vmware_hw_version on images fails with „A component of the virtual machine is not accessible on the host“e.g.glance image-create –name cirroshw10 –disk-format=vmdk –container-format=bare –property vmware_hw_version=10 < ./cirros.rawWhen trying to create the instance it fails…… Für weitere Details den Link zum Artikel anklickenTitel: Setting up active-passive dual pathing with vSAN and vSphereKnowledgebase Nr: 2151225Kategorie: InformationalAktualisiert: 11.08.2017Link zum Artikel: 2151225Beschreibung: Some enclosures permit more than one path from a node to the drives in use. These are usually dual port SAS drives. A typical arrangement would look similar to: Single Node

Schreibe einen Kommentar

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