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

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

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

Vom 14.12.2016 bis zum 15.12.2016 wurden 53 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 14.12.2016 vom Typ: How to, Troubleshooting, Video
Titel: Upgrading vSAN On-Disk format to 3.0 may fail in small vSAN clusters or ROBO/stretched clusters

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: Network interfaces used for vSAN are not ready

Am 14.12.2016 vom Typ: How to
Titel: Enabling or disabling a vSAN cluster

Am 14.12.2016 vom Typ: How to, Informational
Titel: vSAN clustering has been disabled on an ESXi host

Am 14.12.2016 vom Typ: Troubleshooting
Titel: vSphere High Availability (HA) fails to restart a virtual machine when VMware vSAN network is partitioned

Am 14.12.2016 vom Typ: How to
Titel: vSphere 5.5 vSAN requirements

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: Automatic disk claiming does not work as expected if license is applied after enabling VMware vSAN

Am 14.12.2016 vom Typ: Informational
Titel: vSAN node reached threshold of opened components

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Moving Disk Groups to a new vSAN cluster

Am 14.12.2016 vom Typ: How to, Troubleshooting
Titel: Collecting diagnostic information for VMware products

Am 14.12.2016 vom Typ: Troubleshooting
Titel: vSAN disk components are marked ABSENT after enabling CBT

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Creating or editing a virtual machine Storage Policy to correct a missing vSAN VASA provider fails

Am 14.12.2016 vom Typ: Troubleshooting
Titel: A hard disk/magnetic disk in a VMware vSAN disk group fails

Am 14.12.2016 vom Typ: Informational
Titel: Storage Controllers previously supported for vSAN 5.5 that are no longer supported

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Cannot view or add vSAN Storage Providers in vSphere Web Client

Am 14.12.2016 vom Typ: Informational
Titel: Hot unplug and plug of disks on HPE Gen8 and Gen9 IO controllers

Am 14.12.2016 vom Typ: How to, Informational
Titel: Updating the vSAN HCL database manually

Am 14.12.2016 vom Typ: How to, Informational
Titel: Redirecting vSAN trace-level messages to a syslog server

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Potential ESXi host failures when hot unplugging SSD disks backed by LSI controllers

Am 14.12.2016 vom Typ: How to
Titel: Adding alarms to vCenter Server for vSAN 5.5 monitoring

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Configuring Windows PSC for High Availability in vSphere 6.5

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Storage providers fail to auto-register for certain vSAN hosts

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

Am 14.12.2016 vom Typ: Alerts, Informational, Troubleshooting
Titel: Upgrading from VMware vSphere 5.5 EP06 or 5.5 P04 to vSphere 6.0 GA can cause VMware vSAN Data Unavailability

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – Network Health – Hosts disconnected from vCenter Server

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – vSAN HCL Health – vSAN HCL DB up-to-date

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Check Information

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers

Am 14.12.2016 vom Typ: Troubleshooting
Titel: EVO:RAIL vSAN VLAN Troubleshooting

Am 14.12.2016 vom Typ: Troubleshooting
Titel: MySQL DB installation in vRealize Orchestrator 7.2 fails

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

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Unable to upload, copy or create files in a VMware vSAN-backed datastore

Am 14.12.2016 vom Typ: Informational
Titel: VMware vSAN 6.0 Health Check Plug-in does not function as expected

Am 14.12.2016 vom Typ: Informational
Titel: Required vSAN and ESXi configuration for controllers based on the LSI 3108 chipset

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Unable to apply storage policies to virtual machines residing on a VMware vSAN cluster with SSLv3 disabled

Am 14.12.2016 vom Typ: Troubleshooting
Titel: View Storage Accelerator not working and causing poor vSAN performance

Am 14.12.2016 vom Typ: Troubleshooting
Titel: VMware ESXi 6.0, Patch ESXi600-201605401-BG: Updates esx-base, vsanhealth, vsan VIBs

Am 14.12.2016 vom Typ: Troubleshooting
Titel: VMware vSAN storage provider fails during resyncwith the error: com.vmware.vim.binding.sms.fault.ServiceNotInitialized

Am 14.12.2016 vom Typ: Troubleshooting
Titel: VMware vSAN 6.1 health plugin reports the error: Unexpected status code: 503

Am 14.12.2016 vom Typ: Best Practices, Security
Titel: Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – Witness host not found

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Display protocol error when connecting to View Machine using Blast

Am 14.12.2016 vom Typ: Informational
Titel: VMware vSAN 6.2 fulfillment

Am 14.12.2016 vom Typ: Troubleshooting
Titel: VMware vSAN 6.1 fulfillment

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN Health Service – Witness host within vCenter cluster

Am 14.12.2016 vom Typ: Informational
Titel: Support for Server SAN Suite

Am 14.12.2016 vom Typ: Troubleshooting
Titel: SSD log buildup can cause poor performance in a VMware vSAN Cluster

Am 14.12.2016 vom Typ: Troubleshooting
Titel: vSAN Performance service is not enabled after upgrading the VMware vSAN to 6.2.x

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

Am 14.12.2016 vom Typ: Alerts, Informational, Troubleshooting
Titel: Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x

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

Am 14.12.2016 vom Typ: Troubleshooting
Titel: Date format is discarded for cost model upload in vRealize Business Advanced and Enterprise 8.0.0

Am 14.12.2016 vom Typ: Informational, Troubleshooting
Titel: vSAN network redundancy has been reduced

Ausführliche Auflistung:

Titel: Upgrading vSAN On-Disk format to 3.0 may fail in small vSAN clusters or ROBO/stretched clusters

Knowledgebase Nr: 2144944

Kategorie: How to, Troubleshooting, Video

Aktualisiert: 14.12.2016

Link zum Artikel: 2144944

Beschreibung:
Attempting an on-disk upgrade in certain vSAN configurations may result in failure. Configurations that can cause these errors are: The stretched vSAN Cluster consists of two ESXi Hosts and the Witness Node (ROBO configuration) Each Host in the Stretched Cluster contains a single vSAN Disk Group A vSAN cluster consists of three normal nodes, with one disk group per node A vSAN cluster is very full, preventing the „full data migration“ disk-group decommission mode On-disk upgrade failures…
… Für weitere Details den Link zum Artikel anklicken

Titel: Network interfaces used for vSAN are not ready

Knowledgebase Nr: 2058521

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Beschreibung:
When the VMkernel adapter that your ESXi host uses for vSAN is not ready, you receive an event with the description: vmknic vmkX that is currently configured to be used with VSAN doesn’t have an IP address yet. There are no other active network configuration and therefore the VSAN node doesn’t have network connectivity. For example, this event might occur when the VMkernel adapter does not have a proper IP address. Impact The ESXi host might not be able to join an existing vSAN cluster or form…
… Für weitere Details den Link zum Artikel anklicken

Titel: Enabling or disabling a vSAN cluster

Knowledgebase Nr: 2058322

Kategorie: How to

Aktualisiert: 14.12.2016

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

Beschreibung:
This article provides steps to enable or disable vSAN (formerly known as Virtual SAN) on a cluster.For more information, see the vSphere documentation. The documentation contains definitive information. If there is a discrepancy between the documentation and this article, assume that the documentation is correct.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN clustering has been disabled on an ESXi host

Knowledgebase Nr: 2058794

Kategorie: How to, Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2058794

Beschreibung:
When vSAN clustering is disabled on an ESXi host, the following error message displays: VSAN clustering and directory services have been disabled thus will be no longer available. This event might occur when you move the host out of the vSAN cluster. Impact The host is no longer a part of the vSAN cluster. Its storage disks cannot contribute to the vSAN datastore.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSphere High Availability (HA) fails to restart a virtual machine when VMware vSAN network is partitioned

Knowledgebase Nr: 2073949

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2073949

Beschreibung:
When a VMware vSAN network is partitioned, you may experience these symptoms: vSphere High Availability (HA) fails to restart virtual machines protected by HA vSphere High Availability (HA) cannot restart virtual machines protected by HA Virtual machines do not power on as expected
… Für weitere Details den Link zum Artikel anklicken

Titel: vSphere 5.5 vSAN requirements

Knowledgebase Nr: 2058424

Kategorie: How to

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2058424

Beschreibung:
This article provides information on the minimum requirements to create a vSAN cluster in vSphere 5.5.For more information, see the vSphere 5.5 documentation. The documentation contains definitive information. If there is a discrepancy between the documentation and this article, assume that the documentation is correct.
… Für weitere Details den Link zum Artikel anklicken

Titel: Automatic disk claiming does not work as expected if license is applied after enabling VMware vSAN

Knowledgebase Nr: 2073948

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2073948

Beschreibung:
When you are running VMware vSAN configured to claim storage automatically, after applying a license for vSAN you experience these symptoms: Storage devices are not claimed automatically. Disk groups are not created automatically. vSAN fails to claim the disks.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN node reached threshold of opened components

Knowledgebase Nr: 2071379

Kategorie: Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2071379

Beschreibung:
SummaryYou receive this message when the limit for the number of components your vSAN node can handle is approaching.Once this limit is reached, creation of additional components will fail. As a consequence high level operations such as cloning a virtual machine or vSphere replication might fail. ExampleA given vSAN node currently has a default component limit of 3000, and the user has 2399 components in this node. The user creates another VM which causes the number of components to raise to…
… Für weitere Details den Link zum Artikel anklicken

Titel: Moving Disk Groups to a new vSAN cluster

Knowledgebase Nr: 2073931

Aktualisiert: 14.12.2016

Für Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2073931

Beschreibung:
Moving a vSAN (formerly known as Virtual SAN) disk group from an existing vSAN cluster to a newly created vSAN cluster without decommissioning the disk group, automatically adds the original disk groups to the new cluster. This capability works on HBAs, passthrough controllers, and RAID controllers with write-back cache mode disabled. You cannot use disks that are already moved to a new cluster for creating a new disk group.Note that, vSAN has the capability to read metadata from the disks and…
… Für weitere Details den Link zum Artikel anklicken

Titel: Collecting diagnostic information for VMware products

Knowledgebase Nr: 1008524

Kategorie: How to, Troubleshooting

Aktualisiert: 14.12.2016

Link zum Artikel: 1008524

Beschreibung:
VMware Technical Support routinely requests diagnostic information from you when a support request is handled. This diagnostic information contains product specific logs, configuration files, and data appropriate to the situation. The information is gathered using a specific script or tool for each product and can include a host support bundle from the ESXi host and vCenter Server support bundle. Data collected in a host support bundle may be considered sensitive. Additionally, as of vSphere…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN disk components are marked ABSENT after enabling CBT

Knowledgebase Nr: 2077611

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2077611

Beschreibung:
vSAN disk components are marked ABSENT after enabling CBT (Changed Block Tracking) on a virtual machine that has existing snapshots vSphere Web Client reports these errors: An error was received from the ESX host while powering on Virtual Machine Failed to start the virtual machine Module DiskEarly power on failed Cannot open the disk disk path or one of the snapshot disks it depends on Input/output error In the var/log/vmkernel log file, you see entries similar to:CBT: 2214: Created device…
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating or editing a virtual machine Storage Policy to correct a missing vSAN VASA provider fails

Knowledgebase Nr: 2075838

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2075838

Beschreibung:
The vSAN VASA provider is not listed in VMware vSAN 5.5. You cannot create a Storage Policy due to the unlisted vSAN VASA. You cannot edit existing Storage Policies on the virtual machine.
… Für weitere Details den Link zum Artikel anklicken

Titel: A hard disk/magnetic disk in a VMware vSAN disk group fails

Knowledgebase Nr: 2077185

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2077185

Beschreibung:
A hard disk/magnetic disk in a VMware vSAN (formerly Known as Virtual SAN) disk group fails. When a hard disk or magnetic disk in a vSAN disk group is physically removed the host does not reboot.
… Für weitere Details den Link zum Artikel anklicken

Titel: Storage Controllers previously supported for vSAN 5.5 that are no longer supported

Knowledgebase Nr: 2081431

Kategorie: Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2081431

Beschreibung:
Effective July 1, 2014, some previously supported storage controllers are no longer supported with vSAN 5.5.This article provides information on the list of controllers that are no longer supported with vSAN 5.5.
… Für weitere Details den Link zum Artikel anklicken

Titel: Cannot view or add vSAN Storage Providers in vSphere Web Client

Knowledgebase Nr: 2078070

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vCenter Server 5.5.x, VMware vSAN 5.5.x

Link zum Artikel: 2078070

Beschreibung:
Cannot view or manually add VMware vSAN (formerly known as Virtual SAN) Storage Providers in the vSphere Web Client. You see the error: The Register new storage provider operation failed for the entity with the following error message.A Problem was encountered while registering the provider
… Für weitere Details den Link zum Artikel anklicken

Titel: Hot unplug and plug of disks on HPE Gen8 and Gen9 IO controllers

Knowledgebase Nr: 2077426

Kategorie: Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware ESXi 5.5.x

Link zum Artikel: 2077426

Beschreibung:
Symptoms: Upon drive removal, you may notice the device continuing to be listed in the web UI or console. You may also notice kernel log messages (/var/log/vmkernel.log) indicating IO failures on the device that was removed. When you check the status of the logical volume using the hpssacli tool, you may notice that the logical volume indicates a failure but it is still online. Upon drive insertion, you may notice that IO errors continue to be logged. This is because the old volume is being…
… Für weitere Details den Link zum Artikel anklicken

Titel: Updating the vSAN HCL database manually

Knowledgebase Nr: 2145116

Kategorie: How to, Informational

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2145116

Beschreibung:
To update the vSAN HCL database manually: Log in to vCenter server using vSphere Web Client with administrator credentials. Go to vSAN cluster and click the Manage tab. In the management tab, click health under vSAN section in the left pane. If the vCenter server can communicate with internet, click Get latest version online. If the vCenter server does not have proxy and unable to communicate with internet: Log in to a workstation where you have internet access. Open the below link in…
… Für weitere Details den Link zum Artikel anklicken

Titel: Redirecting vSAN trace-level messages to a syslog server

Knowledgebase Nr: 2145556

Kategorie: How to, Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.2.x

Link zum Artikel: 2145556

Beschreibung:
For vSAN 6.2, some of the trace-level logging created by vSAN can be forwarded to a syslog server. The total volume of traces is too great for syslog handling, but the urgent traces (provides details on most potentially-significant problems) can be forwarded to an external syslog collector. The use of syslog redirection for the urgent traces is a useful troubleshooting tool, as it can permit the evaluation of trace data even if the traces are lost.
… Für weitere Details den Link zum Artikel anklicken

Titel: Potential ESXi host failures when hot unplugging SSD disks backed by LSI controllers

Knowledgebase Nr: 2092959

Aktualisiert: 14.12.2016

Für Produkte: VMware ESXi 5.5.x, VMware vCenter Server 5.5.x, VMware vSAN 5.5.x

Link zum Artikel: 2092959

Beschreibung:
When you manually hot unplug SSD disks, vSAN hosts that are using the disks might fail with a PSOD. This failure might happen when you use the following LSI drivers: mpt2sas version 19.00.00.00.1vmw mpt2sas version 18.00.00.00.1vmw mpt2sas version 15.10.06.00.1vmw mpt3sas version 6.00.00.00.1vmw megaraid_sas version 6.603.55.00.1vmw
… Für weitere Details den Link zum Artikel anklicken

Titel: Adding alarms to vCenter Server for vSAN 5.5 monitoring

Knowledgebase Nr: 2091347

Kategorie: How to

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2091347

Beschreibung:
This article outlines how to define alarms for these vSAN state changes: Disk removal/loss Disk failure Congestion affecting performance Cluster is approaching component maximums Note: vCenter Server does not have default alarms for certain vSAN host, cluster or disk state-changes.
… Für weitere Details den Link zum Artikel anklicken

Titel: Configuring Windows PSC for High Availability in vSphere 6.5

Knowledgebase Nr: 2147527

Aktualisiert: 14.12.2016

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2147527

Beschreibung:
This article provides the procedure to configure Windows installed Platform Services Controller (PSC) Appliance 6.5 High Availability.
… Für weitere Details den Link zum Artikel anklicken

Titel: Storage providers fail to auto-register for certain vSAN hosts

Knowledgebase Nr: 2109894

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2109894

Beschreibung:
When you move a vSAN (formerly known as Virtual SAN) host to a vSAN cluster on another vCenter Server, you see this message: The Virtual SAN host cannot be moved to the destination cluster: Virtual SAN cluster UUD MisMatch: (Host: <UUID>, destination: <UUID>)
… 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: 14.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: Upgrading from VMware vSphere 5.5 EP06 or 5.5 P04 to vSphere 6.0 GA can cause VMware vSAN Data Unavailability

Knowledgebase Nr: 2113024

Kategorie: Alerts, Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2113024

Beschreibung:
Virtual machines become inaccessible or disappear from VMware vCenter Server inventory. Your environment includes a vSAN (formerly known as Virtual SAN) Cluster with 3 or more VMware ESXi hosts running either: ESXi 5.5 EP06 (Build 2456374) ESXi 5.5 P04 (Build 2403361) One of the hosts within the vSAN cluster has been upgraded to ESXi 6.0. One or more virtual machines have been migrated using vMotion to the upgraded host.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – Network Health – Hosts disconnected from vCenter Server

Knowledgebase Nr: 2108004

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.0.x

Link zum Artikel: 2108004

Beschreibung:
This article explains the Network Health – Hosts disconnected from vCenter check in the vSAN (formerly known as Virtual SAN) Health Service and provides details on why it might report an error.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – vSAN HCL Health – vSAN HCL DB up-to-date

Knowledgebase Nr: 2109870

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2109870

Beschreibung:
This article explains the vSAN HCL Health – vSAN HCL DB up-to-date check in the vSAN Health Service and provides details on why it might report an error.Adherence to the VMware Compatibility Guide (VCG)/Hardware Compatibility Guide (HCL) is critically important to the stability of vSAN environments. Experience has shown that failing to observe the VCG often leads to production outages over time. It is, therefore, very important to monitor the health checks in the HCL checker category. For more…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Check Information

Knowledgebase Nr: 2114803

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2114803

Beschreibung:
This article provides an overview and serves as a homepage for the VMware vSAN health check Knowledge Base articles.
… Für weitere Details den Link zum Artikel anklicken

Titel: Best practices for vSAN implementations using Dell PERC H730 or FD332-PERC storage controllers

Knowledgebase Nr: 2109665

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2109665

Beschreibung:
This article provides the best practices for implementing VMware vSAN (formerly known as Virtual SAN) using Dell PERC H730 or FD332-PERC storage controllers.
… Für weitere Details den Link zum Artikel anklicken

Titel: EVO:RAIL vSAN VLAN Troubleshooting

Knowledgebase Nr: 2118997

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Link zum Artikel: 2118997

Beschreibung:
EVO:RAIL requires a vSAN VLAN on your switch that is configured with IPv4 multicasting. When it is not working properly, you experience these symptoms: EVO:RAIL Management displays the total disk size for the MARVIN-Virtual-SAN-Datastorexxxx to be 3.35 TB of space. A single EVO:RAIL appliance should show 13.1 TB of space for the MARVIN-Virtual-SAN-Datastorexxxx. vSphere Web Client displays this error in the Network Status field for Virtual SAN:Misconfiguration Detected
… Für weitere Details den Link zum Artikel anklicken

Titel: MySQL DB installation in vRealize Orchestrator 7.2 fails

Knowledgebase Nr: 2148277

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vRealize Orchestrator 7.2.x

Link zum Artikel: 2148277

Beschreibung:
Issuing workflow to add new MySQL DB in vRealize Orchestrator 7.2 release with error:item: ‚Add a database/item2‘, state: ‚failed‘, business state: ’null‘, exception: ‚java.lang.IllegalArgumentException: The driver ‚com.mysql.jdbc.Driver‘ for ‚MySQL‘ database cannot be found! (Dynamic Script Module name : addDatabase#8)’workflow: ‚Add a database‘ (18541090831854109083178946495518541090830101010101010101010101010)| ‚attribute‘: name=errorCode type=string…
… Für weitere Details den Link zum Artikel anklicken

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

Knowledgebase Nr: 2147627

Aktualisiert: 14.12.2016

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: Unable to upload, copy or create files in a VMware vSAN-backed datastore

Knowledgebase Nr: 2119776

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2119776

Beschreibung:
Attempting to upload files to the root directory of a vSAN (formerly known as Virtual SAN) datastore using the VSphere Client or VSphere Web Client fail with error messages. Attempting to upload files to the root directory of a vSAN datastore using ssh tools such as winSCP, FileZilla or puTTY fail. Attempting to create or copy files to the root directory of a vSAN datastore using the touch, cp, mkdir or mv commands from the ESXi console fail.
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN 6.0 Health Check Plug-in does not function as expected

Knowledgebase Nr: 2117769

Kategorie: Informational

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2117769

Beschreibung:
VMware vSAN 6.0 Health Check Plug-in does not function as expectedHighlighting an ESXi host that is part of the vSAN (formerly known as Virtual SAN) cluster displays an empty panel
… Für weitere Details den Link zum Artikel anklicken

Titel: Required vSAN and ESXi configuration for controllers based on the LSI 3108 chipset

Knowledgebase Nr: 2144936

Kategorie: Informational

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2144936

Beschreibung:
When a VMware vSAN (formerly known as Virtual SAN) cluster is using LSI 3108-based controllers, some configurations can result in instability and errors such as: Drives and/or disk groups are marked as failed or unhealthy in the vSAN User Interface: In the /var/log/vmkernel.log file of the ESXi host, you see entries similar to:WARNING: lsi_mr3: fusionReset:2565: megaraid_sas: Hardware critical error, returning FAILED.megasas_hotplug_work[0]: event code 0x010bmegasas_hotplug_work[0]: event…
… Für weitere Details den Link zum Artikel anklicken

Titel: Unable to apply storage policies to virtual machines residing on a VMware vSAN cluster with SSLv3 disabled

Knowledgebase Nr: 2128391

Aktualisiert: 14.12.2016

Link zum Artikel: 2128391

Beschreibung:
Disabling SSLv3 in vpxd.cfg causes the application of vSAN storage policies to fail. Cannot apply a storage profile to a vSAN object.In the %ALLUSERSPROFILE%Application DataVMwareInfrastructureProfile-Driven StorageLogssps.log file, you see entries similar to:2015-04-29T06:13:12.152-06:00 [05584 info ‚commonvpxLro‘ opID=DECA7CE8-00000420-6f-5a-18] [VpxLRO] — BEGIN task-internal-1965 — — VsanUpdateVasaProviderLRO — 2015-04-29T06:13:12.154-06:00 [05220 warning ‚ProxySvc‘] SSL Handshake…
… Für weitere Details den Link zum Artikel anklicken

Titel: View Storage Accelerator not working and causing poor vSAN performance

Knowledgebase Nr: 2115001

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware Horizon 6 version 6.1.x, VMware Horizon View 5.3.x, VMware View 6.0.x

Link zum Artikel: 2115001

Beschreibung:
There are circumstances when you enable View Storage Accelerator (VSA) using View Administrator and encounter no error. VSA should in turn enable the Content Based Read Cache (CBRC) feature on ESXi hosts. However, CBRC is not enabled, as evidenced by the absence of digest files for the desktop VMs. With CBRC disabled, vSAN performance will be poor because of slower disk access. This problem can occur in the following cases: 1. The desktop VMs are not powered off when you enable VSA. 2. When…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware ESXi 6.0, Patch ESXi600-201605401-BG: Updates esx-base, vsanhealth, vsan VIBs

Knowledgebase Nr: 2144685

Aktualisiert: 14.12.2016

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2144685

Beschreibung:
Release date: May 12, 2016 Patch Category Bugfix Patch Severity Critical Build For build information, see KB 2136186. Host Reboot Required Yes Virtual Machine Migration or Shutdown Required Yes Affected Hardware N/A Affected Software N/A VIBs Included VMware:esx-base:6.0.0-2.37.3825889 VMware:vsanhealth:6.0.0-3000000.3.0.2.37.3825892 VMware:vsan:6.0.0-2.37.3825891 PRs Fixed 1611463, 1616775, 1626050, 1626789, 1626948, 1636418, 1632784 Related CVE numbers NA
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN storage provider fails during resyncwith the error: com.vmware.vim.binding.sms.fault.ServiceNotInitialized

Knowledgebase Nr: 2129032

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2129032

Beschreibung:
The vSAN (formerly known as Virtual SAN) provider is no longer available on all ESXI hosts in the vCenter Server inventory.After performing a resync, you see the error:The last operation failed for the entity with the following error message.com.vmware.vim.binding.sms.fault.ServiceNotInitialized:inherited from com.vmware.vim.binding.sms.fault.ServiceNotInitializedIn the C:ProgramDataVMwareInfrastructureProfile-Driven StorageLogs. sps.log you see entries similar to:2015-08-10 15:31:34,529…
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN 6.1 health plugin reports the error: Unexpected status code: 503

Knowledgebase Nr: 2138475

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.1.x

Link zum Artikel: 2138475

Beschreibung:
The VMware vSAN health plugin reports the error:异常状态代码: 404 (Unexpected status code: 404) The VMware vSphere Web Client reports the error:Unexpected status code: 503 In the vmware-vsan-health-service.log file, you see entries similar to:2015-11-06T07:05:37.151Z WARNING vsan-health[MainThread] [VsanPyVmomiProfiler::InvokeAccessor] Invoke: mo=alarm-159, info=info2015-11-06T07:05:37.249Z CRITICAL vsan-health[MainThread] [VsanHealthServer::UncaughtExcpetionHandler] Traceback (most recent call…
… Für weitere Details den Link zum Artikel anklicken

Titel: Status of TLSv1.1/1.2 Enablement and TLSv1.0 Disablement across VMware products

Knowledgebase Nr: 2145796

Kategorie: Best Practices, Security

Aktualisiert: 14.12.2016

Für Produkte: VMware App Volumes 3.0.x, VMware ESXi 6.0.x, VMware ESXi 6.5.x, VMware Horizon 7 version 7.0.x, VMware Identity Manager 2.x, VMware Mirage 5.x, VMware NSX for vSphere 6.2.x, VMware vCenter Converter Standalone 6.0.x, VMware vCenter Infrastructure Navigator 5.8.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, VMware vCenter Site Recovery Manager 5.8.x, VMware vCenter Site Recovery Manager 6.0.x, VMware vCenter Update Manager 6.5.x, VMware vCloud Connector 2.7.x, VMware vFabric Postgres Standard Edition 9.3.x, VMware vRealize Automation 6.2.x, VMware vRealize Automation 7.0.x, VMware vRealize Configuration Manager 5.x, VMware vRealize Infrastructure Navigator 5.8.x, VMware vRealize Log Insight 3.0.x, VMware vRealize Log Insight 3.3.x, VMware vRealize Log Insight 3.6.x, VMware vRealize Log Insight 4.0.x, VMware vRealize Operations Manager 6.2.x, VMware vSAN 6.2.x, VMware vSphere PowerCLI 6.0, VMware vSphere Update Manager 6.0.x, VMware vSphere Update Manager 6.5.x

Link zum Artikel: 2145796

Beschreibung:
Due to security concerns in the TLSv1.0 protocol, both Payment Card Industry (PCI) and BSI organizations have suggested to implement and enable TLSv1.1 or TLSv1.2, and move away from the use of TLSv1.0 as soon as possible. In this article we are providing the current status of that implementation across applicable VMware products. Disclaimer: Some products or older release versions of some products may not be listed here because either there are no plans for implementing the newer TLS…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – Witness host not found

Knowledgebase Nr: 2130585

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2130585

Beschreibung:
The Witness host not found check in the vSAN Health Service verifies that the witness host is configured and that it can be reached over the network. If this health check is not green (OK), the vSAN stretched cluster has configuration errors that affect its operation.
… Für weitere Details den Link zum Artikel anklicken

Titel: Display protocol error when connecting to View Machine using Blast

Knowledgebase Nr: 2148267

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Link zum Artikel: 2148267

Beschreibung:
Connecting a View virtual machine using View Blast fails with an error:The display protocol for this desktop is currently not available
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN 6.2 fulfillment

Knowledgebase Nr: 2143726

Kategorie: Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware Horizon 6 version 6.1.x, VMware Horizon 6 version 6.2.x, VMware vSAN 6.2.x

Link zum Artikel: 2143726

Beschreibung:
This article provides information on the fulfillment of VMware vSAN (formerly known as Virtual SAN) for existing VMware vSAN and VMware Horizon 6.x customers.
… Für weitere Details den Link zum Artikel anklicken

Titel: VMware vSAN 6.1 fulfillment

Knowledgebase Nr: 2127302

Aktualisiert: 14.12.2016

Link zum Artikel: 2127302

Beschreibung:
This article provides information on the fulfillment of VMware vSAN for existing VMware vSAN (formerly known as Virtual SAN) and VMware Horizon 6 Advanced and Enterprise Edition customers.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – Witness host within vCenter cluster

Knowledgebase Nr: 2130587

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2130587

Beschreibung:
The Witness host within vCenter cluster check in the vSAN Health Service verifies that the witness host is a standalone host, and not part of the vSAN-enabled cluster. If this health check is not green (OK), the stretched cluster has configuration issues that affect its operation.If the witness host resides within a vSAN-enabled cluster, it causes problems with vSphere DRS, HA, and EVC. The witness host must not be a member of any vSAN-enabled vCenter cluster.
… Für weitere Details den Link zum Artikel anklicken

Titel: Support for Server SAN Suite

Knowledgebase Nr: 2142261

Kategorie: Informational

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.1.x

Link zum Artikel: 2142261

Beschreibung:
This article provides information on activating and getting support for the products included in Server SAN Suite.Server SAN Suite entitles you to VMware vSAN or EMC ScaleIO. These redemption and download instructions apply only if you purchased the Server SAN Suite from VMware, not EMC.
… Für weitere Details den Link zum Artikel anklicken

Titel: SSD log buildup can cause poor performance in a VMware vSAN Cluster

Knowledgebase Nr: 2141386

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x, VMware vSAN 6.0.x, VMware vSAN 6.1.x

Link zum Artikel: 2141386

Beschreibung:
Under certain rare circumstances, vSAN (formerly known as Virtual SAN) can exhibit a behavior where the SSD/cache-tier logging space is filled. When this occurs, it leads to performance impact in the cluster as the SSD is unable to buffer inbound IO in a timely manner. If this issue is encountered, you experience one or more of these symptoms: Hosts periodically enter in to a not responding state in vCenter Server Some virtual machines resident on vSAN exhibit extremely poor performance Some…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Performance service is not enabled after upgrading the VMware vSAN to 6.2.x

Knowledgebase Nr: 2145179

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 6.2.x

Link zum Artikel: 2145179

Beschreibung:
After upgrading to VMware vSAN (formerly known as Virtual SAN) 6.2.x, you experience these symptoms: In the vSAN health Check plugin, you see the warning:Warning on ‚Stats DB object‘
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN Health Service – vSAN iSCSI target service – Network configuration

Knowledgebase Nr: 2147602

Aktualisiert: 14.12.2016

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: Certification of Dell PERC H730 and FD332-PERC Controllers with vSAN 6.x

Knowledgebase Nr: 2144614

Kategorie: Alerts, Informational, Troubleshooting

Aktualisiert: 14.12.2016

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

Link zum Artikel: 2144614

Beschreibung:
The Dell PERC H730 and FD332 based storage controllers have been certified on VMware vSAN 6.2. These storage controllers were impacted and are now certified: Dell PERC H730 (VCG entry) Dell PERC H730P (VCG entry) Dell PERC H730 mini (VCG entries: 34859 and 34860) Dell PERC H730P mini (VCG entries: 34857 and 34858) Dell FD332-PERC – Single ROC (VCG entry) Dell FD332-PERC – Dual ROC (VCG entry) Note: Any Ready Nodes that are utilizing the above controllers are certified as of 04/28/2016….
… 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: 14.12.2016

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: Date format is discarded for cost model upload in vRealize Business Advanced and Enterprise 8.0.0

Knowledgebase Nr: 2073169

Kategorie: Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware IT Business Management Advanced 8.x, VMware IT Business Management Enterprise 8.x

Link zum Artikel: 2073169

Beschreibung:
Cost model discards date format for uploaded cost data and allocation data. When viewing data on the Upload Details page of an expense source or a cost group’s allocation, the date format is forced to dd-mm-yy format and the date format which is specified in the source adaptor is discarded.
… Für weitere Details den Link zum Artikel anklicken

Titel: vSAN network redundancy has been reduced

Knowledgebase Nr: 2058530

Kategorie: Informational, Troubleshooting

Aktualisiert: 14.12.2016

Für Produkte: VMware vSAN 5.5.x

Link zum Artikel: 2058530

Beschreibung:
When you use multiple network interfaces for your vSAN network and remove some of them, you receive events with the following descriptions: VSAN network configuration redundancy has reduced. This may be a problem if further network configuration is removed. and VSAN network configuration doesn’t have any redundancy. This may be a problem if further network configuration is removed. These events warn you that if you continue removing vSAN interfaces, you might entirely lose network redundancy….
… Für weitere Details den Link zum Artikel anklicken

Zurück nach oben

2016-12-15T09:40:21+00:00Dezember 15th, 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