Monthly Archives: February 2016

Location of VMware vCenter Server 6.0 log files

Purpose

This article provides the default location of the VMware vCenter Server logs.

Resolution

The VMware vCenter Server 6.0 logs are located in the %ALLUSERSPROFILE%\VMWare\vCenterServer\logs folder.
The VMware vCenter Server Appliance 6.0 logs are located in the /var/log/vmware/ folder.
vCenter Server logs are grouped by component and purpose in these sub-directories:
vCenter Server
vCenter Server Appliance
Description
vmware-vpx\vpxd.log
vpxd/vpxd.log
The main vCenter Serverlog
vmware-vpx\vpxd-profiler.log
vpxd/vpxd-profiler.log
Profile metrics for operations performed in vCenter Server
vmware-vpx\vpxd-alert.log
vpxd/vpxd-alert.log
Non-fatal information logged about the vpxd process
perfcharts\stats.log
perfcharts/stats.log
VMware Performance Charts
eam\eam.log
eam/eam.log
VMware ESX Agent Manager
invsvc
invsvc
VMware Inventory Service
netdump
netdumper
VMware vSphere ESXi Dump Collector
vapi vapi VMware vAPI Endpoint
vmdird
vmdird
VMware Directory Service daemon
vmsyslogcollector
syslog
vSphere Syslog Collector
vmware-sps\sps.log
vmware-sps/sps.log
VMware vSphere Profile-Driven Storage Service
vpostgres
vpostgres
vFabric Postgres database service
vsphere-client
vsphere-client
VMware vSphere Web Client
vws
vws
VMware System and Hardware Health Manager
workflow
workflow
VMware vCenter Workflow Manger
SSO SSO VMware Single Sign-On

For more information, please read VMware KB (2110014)




Important Updates to NSX for vSphere KB Articles

Here is a list of currently trending KB articles for NSX for vSphere.

NSX Distributed Firewall unfiltered rules may be deleted during the firewall rule publish operation in VMware NSX for vSphere 6.x (2141155)
Symptoms:

  • In Distributed Firewall Apply Filter mode in VMware NSX for vSphere 6.x, when filtered rules belonging to only one firewall section is modified and published by either Publish Section or Publish Changes or filtered rules belonging to multiple firewall sections are modified, you experienced these symptoms:
  • The publish operation may publish only the filtered rules
  • All the unfiltered rules within that section may be removed

VMware NSX for vSphere 6.2.1 supportability with vRealize Log Insight Reporting (2143058)
Symptoms:

  • NSX for vSphere Log Insight Content Pack (both 1.0, and 2.0) does not work with NSX for vSphere 6.2 infrastructure release

The netcpa agent on an ESXi host fails to communicate with NSX controller(s) in VMware NSX for vSphere 6.x (2137011)
Symptoms:

  • Routes from dynamic routing protocols may not be present in VMware NSX for vSphere 6.x Edge Services Gateway (ESG) or Distributed Logical Router (DLR) when the Control VM is running on affected ESXi host
  • Virtual machines on the affected ESXi host fails to communicate with other virtual machines running on other ESXi hosts
  • Running the esxcli network vswitch dvs vmware vxlan network list –vds-name=Name_VDS command on the ESXi host displays the VNIs as down

NSX User Interface (UI) is grayed out for several seconds and exhibits slow performance on NSX for vSphere 6.2.0 (2141919)
Symptoms:

  • Selecting an item on the vSphere Web client for NSX appears to be slow. Specifically, the screen turns grey and pauses for roughly 10 seconds before a corresponding request from the Web client reaches NSX Manager and is captured in the NSX Manager logs (vsm.log)
  • After this initial slowness, performance works as expected
  • The NSX Manager logs display a roughly five-second lag to complete login and successful authentication between NSX Manager and Virtual Center

NSX is unavailable from the vSphere Web Client Plugin after backup of NSX Manager with quiesced snapshot (2142263)
Symptoms:

  • NSX is unavailable from the vSphere Web Client plug-in.
  • The NSX plug-in User Interface (UI) is reachable but the pages do not display content
  • A restart of the NSX Manager is required to recover from this situation

The post Important Updates to NSX for vSphere KB Articles appeared first on Support Insider.

Source: VMware Blogs