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

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

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

Vom 06.02.2017 bis zum 07.02.2017 wurden 35 Knowledgebase Artikel veröffentlicht.

Liste der veröffentlichten Knowledgebase Artikel von VMware:

Am 06.02.2017 vom Typ: Informational
Titel: How to view Support Contract history in My VMware

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Location of VMware View log files

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Upgrading vCenter Server from 5.5 to 6.0 fails with authentication error during pre-upgrade check

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Error „Fatal Error: Out of resources“ while installing ESXi 5.5.x, 6.0.x and 6.5.x

Am 06.02.2017 vom Typ: How to
Titel: Enabling root access for SSH and SCP in VMware vCenter Support Assistant

Am 06.02.2017 vom Typ: How to
Titel: Creating a local user and assigning permissions on an ESXi host

Am 06.02.2017 vom Typ: Best Practices
Titel: Accessing or creating a VMFS datastore larger than 16TB fails when using EqualLogic

Am 06.02.2017 vom Typ: Troubleshooting
Titel: PowerCLI Set-CDDrive cmdlet fails with the error: „Device ‚ide1:0‘ already exists.“

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Deleting a Tenant in VMware vRealize Automation 6.0.x fails

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Error „Logon failure: the user has not been granted the requested logon type at this computer“

Am 06.02.2017 vom Typ: Best Practices, Informational
Titel: vSphere Data Protection (VDP) performance test requirements

Am 06.02.2017 vom Typ: Troubleshooting
Titel: „No host data available“ error in the Hardware Status tab after upgrading to vCenter Server 6.5

Am 06.02.2017 vom Typ: Troubleshooting
Titel: After replacing the vCenter Server certificates in VMware vSphere 6.0, the ESX Agent Manager solution user fails to log in

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Reclaiming space on vPostgres databases within the VMware vCenter Server Appliance fails with the error: domain socket „/tmp/.s.PGSQL.5432“

Am 06.02.2017 vom Typ: Troubleshooting
Titel: VM network is disconnected in ESXi 5.5 when re-configuring two vNICs simultaneously

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Upgrading to vCenter Server 6.x fails with the error: „Internal error occurred during vCenter Server Database pre-upgrade checks“

Am 06.02.2017 vom Typ: Troubleshooting
Titel: OSPF stops sending Hello packets when IGMP snooping is enabled

Am 06.02.2017 vom Typ: Informational, Troubleshooting
Titel: HP Gen 8/9 lose access to device backing boot filesystem

Am 06.02.2017 vom Typ: Informational, Troubleshooting
Titel: Backing up a VM using VDDK 6.0 fails while attempting to open a disk on the Windows Proxy

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Changing an ATS-only volume to public in ESXi

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Creating or upgrading the NSX 6.x Edges fails after adding an IPv6 address under NSX Management interface

Am 06.02.2017 vom Typ: Patch, Troubleshooting
Titel: ESXi host fails with a PSOD #PF Exception 14 after NVIDIA spinlock allocation failure

Am 06.02.2017 vom Typ: How to
Titel: After importing the REST configuration into VMware vRealize Orchestrator you see the error: Error in Plug-in

Am 06.02.2017 vom Typ: Informational
Titel: Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Downloading logs from multiple NSX Controllers simultaneously in VMware NSX for vSphere fails with the error: 404 Not Found

Am 06.02.2017 vom Typ: Informational
Titel: Limited Support for End Of Life Product — vCloud Networking and Security 5.5.x (vCNS)

Am 06.02.2017 vom Typ: Troubleshooting
Titel: NSX is unavailable from the vSphere Web Client Plug-in

Am 06.02.2017 vom Typ: Troubleshooting
Titel: VM fails to add in Dynamic Security Groups

Am 06.02.2017 vom Typ: Troubleshooting
Titel: NSX Edge uplink interface does not process any traffic after it is disabled and re-enabled

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Changing the Storage Policy of a VM fails with error: „The scheduling parameter change failed“

Am 06.02.2017 vom Typ: Troubleshooting
Titel: NSX Plug-in does not appear in Web Client when ESXTOP plug-in installed

Am 06.02.2017 vom Typ: How to, Troubleshooting
Titel: VIO Volume snapshot creation with the force option is reporting „State Error“

Am 06.02.2017 vom Typ: Troubleshooting
Titel: NSX Manager disk becomes full with IDFW data

Am 06.02.2017 vom Typ: Troubleshooting
Titel: VMware Tools 10.0.x fails to run on Ubuntu 16.10 guest operating system

Am 06.02.2017 vom Typ: Troubleshooting
Titel: Management pack for storage devices fails to register Fabric CIM Server in vRealize Operations Manager

Ausführliche Auflistung:

Titel: How to view Support Contract history in My VMware

Knowledgebase Nr: 2006981

Kategorie: Informational

Aktualisiert: 06.02.2017

Link zum Artikel: 2006981

Beschreibung:
The Support Contract History page is available to the Super User, Procurement Contact, Administrator, and users with View Orders & Contracts permissions. To view your Support Contract History, log in to My VMware and go to Support > Support Contracts. On this page, you can view the: Contract ID number Status of the support contract Products with which the support contract is associated Support level (Basic, Production, or Mixed support) Contract end date You can use the filter…
… Für weitere Details den Link zum Artikel anklicken

Titel: Location of VMware View log files

Knowledgebase Nr: 1027744

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware Horizon View 5.0.x, VMware Horizon View 5.1.x, VMware Horizon View 5.2.x, VMware Horizon View 5.3.x, VMware View 6.0.x, VMware View Manager 4.5.x, VMware View Manager 4.6.x

Link zum Artikel: 1027744

Beschreibung:
This article provides the locations of VMware View Manager log files.
… Für weitere Details den Link zum Artikel anklicken

Titel: Upgrading vCenter Server from 5.5 to 6.0 fails with authentication error during pre-upgrade check

Knowledgebase Nr: 2140225

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2140225

Beschreibung:
Upgrade from vCenter 5.5 to vCenter 6.0 fails during pre-upgrade check with the following error: Error: There is a problem authenticating into the legacy vCenter Server using the credentials provided by the user. Resolution: Check if vCenter Server is up and running.Double check provided vCenter Server credentials In the C:ProgramDataVMwarevCenterServerlogsvmware-vpxdvpxd.log file, you see entries similar to: [02828 info ‚commonvpxLro‘ opID=500f1eb7] [VpxLRO] — BEGIN…
… Für weitere Details den Link zum Artikel anklicken

Titel: Error „Fatal Error: Out of resources“ while installing ESXi 5.5.x, 6.0.x and 6.5.x

Knowledgebase Nr: 2076105

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2076105

Beschreibung:
ESXi 5.5.x, ESXi 6.0.x or ESXi 6.5.x installation might fail with Fatal Error: Out of resources error when there are a number of adapters that require Memory-mapped I/O space. Depending upon the number of adapters and the system configuration there may not be enough 32 bit memory (below 4GB) available to allocate to the adapters.
… Für weitere Details den Link zum Artikel anklicken

Titel: Enabling root access for SSH and SCP in VMware vCenter Support Assistant

Knowledgebase Nr: 2076086

Kategorie: How to

Aktualisiert: 06.02.2017

Für Produkte: VMware vCenter Support Assistant 5.1.x, VMware vCenter Support Assistant 5.5.x, VMware vCenter Support Assistant 6.0.x, VMware vCenter Support Assistant 6.5.x

Link zum Artikel: 2076086

Beschreibung:
This article provides steps to enable the root account for SSH and SCP in vCenter Support Assistant. Enabling the root account for SSH and SCPhelps in log collection when troubleshooting vCenter Support Assistant 5.x and later Note: By default, the root account for SSH is disabled and there are no options in Virtual Appliance Management Interface (VAMI) to enable the account.
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating a local user and assigning permissions on an ESXi host

Knowledgebase Nr: 2082641

Kategorie: How to

Aktualisiert: 06.02.2017

Für Produkte: VMware ESXi 5.0.x

Link zum Artikel: 2082641

Beschreibung:
This article provides steps to create a local user and assign permissions on an ESXi host. You can create a local user and assign permissions on the ESXi host using the vSphere Client or PowerCLI.
… Für weitere Details den Link zum Artikel anklicken

Titel: Accessing or creating a VMFS datastore larger than 16TB fails when using EqualLogic

Knowledgebase Nr: 2079071

Kategorie: Best Practices

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2079071

Beschreibung:
Cannot access or create a VMFS datastore larger than 16 TB in ESXi 5.5 Accessing or creating a VMFS datastore larger than 16 TB in ESXi 5.5 fails EqualLogic Group Manager reports device is created with 4K bytes per sector, not default 512 bytes Equallogic Group Manager displays an Experimental Flag for this setting Creating a VMFS datastore on a very large device stops at disk geometry section of the Add Storage UI wizard Previously created VMFs on a very large device suddenly becomes…
… Für weitere Details den Link zum Artikel anklicken

Titel: PowerCLI Set-CDDrive cmdlet fails with the error: „Device ‚ide1:0‘ already exists.“

Knowledgebase Nr: 2092716

Aktualisiert: 06.02.2017

Für Produkte: VMware vSphere PowerCLI 5.5

Link zum Artikel: 2092716

Beschreibung:
When using vSphere PowerCLI 5.1 or 5.5 against vCenter Server 5.5, you experience these symptoms: When you run these commands to remove media from virtual machines, you see the error:Get-CDDrive -VM $vm | Set-CDDrive -NoMedia -Confirm:$false In the vCenter Server tasks, you see an error similar to:“Device ‚ide1:0‘ already exists.“ CD ROM gets unmounted from the virtual machine.
… Für weitere Details den Link zum Artikel anklicken

Titel: Deleting a Tenant in VMware vRealize Automation 6.0.x fails

Knowledgebase Nr: 2076082

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware vCloud Automation Center for Desktop 6.0.x, VMware vCloud Automation Center for Server 6.0.x

Link zum Artikel: 2076082

Beschreibung:
Cannot delete a Tenant in VMware vRealize Automation 6.0 (formerly known as VMware vCloud Automation Center 6.0) Deleting a vRealize Automation Tenant fails. When logging into the Tenant, you cannot see any Business Groups in the Infrastructure tab.
… Für weitere Details den Link zum Artikel anklicken

Titel: Error „Logon failure: the user has not been granted the requested logon type at this computer“

Knowledgebase Nr: 2148054

Aktualisiert: 06.02.2017

Für Produkte: VMware vCenter Server 6.5.x

Link zum Artikel: 2148054

Beschreibung:
vCenter Server 6.5 Windows services under VMware Service life cycle Manager (vmon) fails to start. Running the Service-control –start –all command times out. In the vMon logs, you see this entry indicating the service start failure:Logon failure: the user has not been granted the requested logon type at this computer. In the Security Event Viewer, you see an entry for audit failure for the respective users and below properties:Logon failure: the user has not been granted the requested…
… Für weitere Details den Link zum Artikel anklicken

Titel: vSphere Data Protection (VDP) performance test requirements

Knowledgebase Nr: 2074293

Kategorie: Best Practices, Informational

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2074293

Beschreibung:
When configure the VMware vSphere Data Protection (VDP) appliance and running the performance test, it reports varying results depending on the size of the appliance being deployed.
… Für weitere Details den Link zum Artikel anklicken

Titel: „No host data available“ error in the Hardware Status tab after upgrading to vCenter Server 6.5

Knowledgebase Nr: 2148520

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2148520

Beschreibung:
After upgrading to vCenter Server 6.5, the vSphere Web Client displays this error when selecting the Hardware Status tab:No host data availableIn the vpxd.log file, there are entries similar to:2016-12-21T20:34:13.439Z verbose vpxd[7F7629716700] [Originator@6876 sub=HTTP server] Sent NotFound response for GET /hwh/gwtcim?host=host-92&op=getHostData2016-12-21T20:34:31.903Z verbose vpxd[7F760BD7A700] [Originator@6876 sub=HTTP server] Sent NotFound response for GET…
… Für weitere Details den Link zum Artikel anklicken

Titel: After replacing the vCenter Server certificates in VMware vSphere 6.0, the ESX Agent Manager solution user fails to log in

Knowledgebase Nr: 2112577

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2112577

Beschreibung:
After replacing certificates on vCenter Server, you experience these symptoms: ESX Agent Manager solution user fails to log in. In the /var/log/vmware/eam/eam.log file or the C:ProgramDataVMwarevCenterServerlogseameam.log file for the ESX Agent Manager (EAM), you see entries similar to: YYYY-MM-DDTHH:MM:SS.MSZ | INFO | eam-0 | VcConnection.java | 167 | Connecting to vCenter as com.vmware.vim.eam extensionYYYY-MM-DDTHH:MM:SS.MSZ | INFO | eam-0 | VcConnection.java | 603 | Connecting to…
… Für weitere Details den Link zum Artikel anklicken

Titel: Reclaiming space on vPostgres databases within the VMware vCenter Server Appliance fails with the error: domain socket „/tmp/.s.PGSQL.5432“

Knowledgebase Nr: 2111236

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2111236

Beschreibung:
Reclaiming space on vPostgres database with in the VMware vCenter Server Appliance fails When you run the vacuumdb script # sudo -u postgres /opt/vmware/vpostgres/1.0/bin/vacuumdb -a -e -v -f -U postgres > /tmp/vacuumdb.log, you see the error:vacuumdb: could not connect to database postgres: could not connect to server: No such file or directoryIs the server running locally and accepting connections on Unix domain socket „/tmp/.s.PGSQL.5432“? In the /storage/db/vpostgres/serverlog file, you…
… Für weitere Details den Link zum Artikel anklicken

Titel: VM network is disconnected in ESXi 5.5 when re-configuring two vNICs simultaneously

Knowledgebase Nr: 2114609

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware vSphere Web Services SDK 5.5

Link zum Artikel: 2114609

Beschreibung:
Virtual machine network is disconnected in ESXi 5.5 when re-configuring two vNICs using ExtraConfig property simultaneously by invoking reconfigVM_Task() API. Cannot reconfigure two vNICs simultaneously by invoking reconfigVM_Task() API. This issue is observed 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: Upgrading to vCenter Server 6.x fails with the error: „Internal error occurred during vCenter Server Database pre-upgrade checks“

Knowledgebase Nr: 2113819

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2113819

Beschreibung:
When you run the upgrade installer for vCenter Server 6.0, you see the error: Error: Internal error occurs duing VMWARE vCenter Server Database pre-upgrade checks.Resolution: send upgrade logs files to GSS for further assistance. In the CollectRequirements_com.vmware.vcdb_YYYY-MM-DD.log file, you see entries similar to: <YYYY-MM-DD>T<TIME> ERROR __main__ Upgrade Phase ‚vcdb:CollectRequirements‘ failed. Exception: need more than 1 value to unpack Traceback (most recent call…
… Für weitere Details den Link zum Artikel anklicken

Titel: OSPF stops sending Hello packets when IGMP snooping is enabled

Knowledgebase Nr: 2147922

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2147922

Beschreibung:
OSPF neighbor adjacency goes down after an undefined period of time (varies between minutes up to hour).Note: For additional symptoms and log entries, see the Additional Information section.
… Für weitere Details den Link zum Artikel anklicken

Titel: HP Gen 8/9 lose access to device backing boot filesystem

Knowledgebase Nr: 2144283

Kategorie: Informational, Troubleshooting

Aktualisiert: 06.02.2017

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

Link zum Artikel: 2144283

Beschreibung:
HP Gen 8/9 servers might fail to boot from an SD card. ESXi host stops responding or runs in a stateless condition after losing access to device backing boot filesystem:Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem /vmfs/devices/disks/mpx.vmhba:32:C0:T0:L0. As a result, host configuration changes will not be saved to persistent storage.
… Für weitere Details den Link zum Artikel anklicken

Titel: Backing up a VM using VDDK 6.0 fails while attempting to open a disk on the Windows Proxy

Knowledgebase Nr: 2125497

Kategorie: Informational, Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: Virtual Disk Development Kit 6.0

Link zum Artikel: 2125497

Beschreibung:
Backing up a virtual machine using Virtual Disk Development Kit (VDDK) 6.0 fails while attempting to open a disk on the Windows Proxy The backup proxy has IPv6 enabled on one or more network interfaces used for the backup.
… Für weitere Details den Link zum Artikel anklicken

Titel: Changing an ATS-only volume to public in ESXi

Knowledgebase Nr: 2147260

Aktualisiert: 06.02.2017

Link zum Artikel: 2147260

Beschreibung:
This article provides steps to change an ATS-only volume to be accessible using SCSI. It must be unmounted and remounted to apply the change and initialize the new locking mechanism.
… Für weitere Details den Link zum Artikel anklicken

Titel: Creating or upgrading the NSX 6.x Edges fails after adding an IPv6 address under NSX Management interface

Knowledgebase Nr: 2127561

Kategorie: Troubleshooting

Aktualisiert: 06.02.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: 2127561

Beschreibung:
After adding an IPv6 address under NSX Management interface, you experience these symptoms: Creating or upgrading an Edge fails on VMware NSX for vSphere 6.x In the /home/secureall/secureall/logs/vsm.log file of the NSX Manager, you see entries similar to:2015-07-24 15:27:06.636 MDT ERROR TaskFrameworkExecutor-6 AbstractEdgeApplianceManager:185 – Timed out waiting for Edge vm {}. Vm took too long to boot and respond2015-07-24 15:51:50.513 MDT ERROR TaskFrameworkExecutor-8…
… Für weitere Details den Link zum Artikel anklicken

Titel: ESXi host fails with a PSOD #PF Exception 14 after NVIDIA spinlock allocation failure

Knowledgebase Nr: 2145707

Kategorie: Patch, Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2145707

Beschreibung:
ESXi host fails with a PSOD #PF Exception 14 after NVIDIA spinlock allocation failure. ESXi host runs a NVIDIATesla M60 or GRID K1 cards. In the purple diagnostic screen, you see the backtraces similar to :@BlueScreen: #PF Exception 14 in world 37407:vmx-vthread- IP 0x41802c482b0d addr 0x18PTEs:0x7f6be9027;0xa0005d027;0x0;Code start: 0x41802c400000 VMK uptime: 0:00:22:36.6910x439190f9bb98:[0x41802c482b0d]SPLockWork@vmkernel#nover+0x19 stack:…
… Für weitere Details den Link zum Artikel anklicken

Titel: After importing the REST configuration into VMware vRealize Orchestrator you see the error: Error in Plug-in

Knowledgebase Nr: 2133883

Kategorie: How to

Aktualisiert: 06.02.2017

Für Produkte: VMware vCenter Orchestrator Appliance 5.5.x, VMware vRealize Orchestrator 6.0.x

Link zum Artikel: 2133883

Beschreibung:
After installing a new VMware vRealize Orchestrator appliance, you experience these symptoms: When you import an existing configuration from another vRealize Orchestrator deployment, the HTTP-REST plugin displays the status:Error in plug-in In the Orchestrator client, under HTTP-REST on the Inventory tab, you see the exception: Exception: Unable to execute ‚fetchRelation‘ for type: RootFinder : java.lang.IllegalArgumentException: The validated string is empty In the /etc/var/server.log file,…
… Für weitere Details den Link zum Artikel anklicken

Titel: Minimum recommended version for NSX for vSphere with GID, ESXi, and vCenter Server

Knowledgebase Nr: 2144295

Kategorie: Informational

Aktualisiert: 06.02.2017

Für Produkte: VMware ESXi 6.0.x, VMware NSX for vSphere 6.2.x, VMware vCenter Server 5.5.x, VMware vCenter Server 6.0.x, VMware vCenter Server Appliance 5.5.x, VMware vCenter Server Appliance 6.0.x

Link zum Artikel: 2144295

Beschreibung:
This article provides information on the recommended minimum version for VMware NSX for vSphere 6.2.x, ESXi, vCenter Server and Guest Introspection Driver (GID).
… Für weitere Details den Link zum Artikel anklicken

Titel: Downloading logs from multiple NSX Controllers simultaneously in VMware NSX for vSphere fails with the error: 404 Not Found

Knowledgebase Nr: 2135653

Aktualisiert: 06.02.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: 2135653

Beschreibung:
Downloading logs from multiple NSX Controller simultaneously in VMware NSX for vSphere 6.x failsYou see the error:404 Not FoundFor more information, see Collecting diagnostic information for VMware NSX for vSphere 6.x (2074678).
… Für weitere Details den Link zum Artikel anklicken

Titel: Limited Support for End Of Life Product — vCloud Networking and Security 5.5.x (vCNS)

Knowledgebase Nr: 2148907

Kategorie: Informational

Aktualisiert: 06.02.2017

Für Produkte: VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x, VMware vCloud Networking and Security 5.5.x

Link zum Artikel: 2148907

Beschreibung:
As of September 19th, 2016, vCloud Networking and Security (vCNS) is End of Life and no longer supported by VMware. Customers still using the product are encouraged to upgrade to the NSX solution. However, VMware still provides troubleshooting support for a customer using vCNS under below-mentioned criteria:The customer has agreed with VMware for extended support till upgrade to NSX solution.The customer has a valid NSX license in hand but has yet to upgrade.Note: All customers who are using…
… Für weitere Details den Link zum Artikel anklicken

Titel: NSX is unavailable from the vSphere Web Client Plug-in

Knowledgebase Nr: 2142263

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x

Link zum Artikel: 2142263

Beschreibung:
NSX is unavailable from the vSphere Web Client plug-in after taking a backup of NSX Manager with quiesced snapshot. The NSX plug-in User Interface (UI) is reachable but the pages do not display content. In the vmware.log file of the NSX Manager VM, you see entries similar to:2016-02-25T15:00:48.586Z| vmx| I120: SnapshotVMXTakeSnapshotComplete: Snapshot 0 failed: Failed to quiesce the virtual machine (31).Note: The preceding log excerpts are only examples. Date, time, and environmental…
… Für weitere Details den Link zum Artikel anklicken

Titel: VM fails to add in Dynamic Security Groups

Knowledgebase Nr: 2146757

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x

Link zum Artikel: 2146757

Beschreibung:
When multiple VMs are created or migrated to a different host about the same time, some of the VMs may not get added to NSX dynamic security groups defined in Service Composer even though they match the defined criteria. In the NSX Manager vsm.log file, you see entries similar to: ERROR DCNPool-7 AbstractFlushingEventListener:324 – Could not synchronize database state with session org.hibernate.StaleObjectStateException: Row was updated or deleted by another transaction (or unsaved-value…
… Für weitere Details den Link zum Artikel anklicken

Titel: NSX Edge uplink interface does not process any traffic after it is disabled and re-enabled

Knowledgebase Nr: 2145468

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x

Link zum Artikel: 2145468

Beschreibung:
OSPF and BGP traffic no longer passes Attempting to statically add the correct MAC address in the ARP table of the Edge Services Gateway (ESG) fails You see the error:SIOCSARP: Network is unreachable The NSX Edge logs contains entries similar to:2015-06-01T14:49:55+00:00 itcldfxnsxesg1-0 zebra[889]: [daemon.err] ERROR: Cannot get device settings for interface: VDR strerror: Operation not supported ## get_e100X_status @ e1000_tool.c:2632015-06-01T14:49:55+00:00 corpnsxesg1-0 zebra[889]:…
… Für weitere Details den Link zum Artikel anklicken

Titel: Changing the Storage Policy of a VM fails with error: „The scheduling parameter change failed“

Knowledgebase Nr: 2148490

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware ESXi 6.0.x

Link zum Artikel: 2148490

Beschreibung:
In the vSphere Web Client, Changing the Storage Policy of a virtual machine fails. You see an error similar to:The scheduling parameter change failed In the /var/log/vpxa.log file, you see the entries similar to:–> (vmodl.LocalizableMessage) {–> key = „msg.disk.sched.fail“,–> message = „The scheduling parameter change failed.“,–> }–> ],–> reason = „The scheduling parameter change failed.“,–> msg = „The scheduling parameter change failed.“–> }–> Args: In the…
… Für weitere Details den Link zum Artikel anklicken

Titel: NSX Plug-in does not appear in Web Client when ESXTOP plug-in installed

Knowledgebase Nr: 2145808

Kategorie: Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware NSX for vSphere 6.1.x, VMware NSX for vSphere 6.2.x, VMware NSX for vSphere 6.3.x

Link zum Artikel: 2145808

Beschreibung:
After deployment of NSX and successful registration with vCenter Server, NSX plug-in does not appear in the vSphere Web Client.
… Für weitere Details den Link zum Artikel anklicken

Titel: VIO Volume snapshot creation with the force option is reporting „State Error“

Knowledgebase Nr: 2148564

Kategorie: How to, Troubleshooting

Aktualisiert: 06.02.2017

Für Produkte: VMware Integrated OpenStack 2.0.x, VMware Integrated OpenStack 2.5.x, VMware Integrated OpenStack 3.0.x

Link zum Artikel: 2148564

Beschreibung:
The creation of a volume snapshot when the volume is attached to an instance is in error status when using the force option: openstack snapshot create –name my_snapshot –force fc973c04-5222-4f28-b7da-d187d868d418This command line is not returning an error:+

2017-02-07T09:07:43+00:00Februar 7th, 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