Logging in vSphere 5.0 has been significantly enhanced. You now have fine-grained control over system logs, the location where logs are sent, and, for each log, default size and rotation policy. You can set up logging with the vSphere Client or with the esxcli system syslog command and the PowerCLI VMHostSysLogServer Commandlets. You can also set up logging behaviour for a host by using the Host Profiles interface in the vSphere Client and can then import that host profile into other hosts.
VMware vSphere ESXi 5.0 hosts run a syslog service (vmsyslogd) which provides a standard mechanism for logging messages from the VMkernel and other system components. By default in ESXi, these logs are placed on a local scratch volume or a ram disk. To preserve the logs further, ESXi can be configured to place these logs to an alternate storage location on disk, and to send the logs across the network to a syslog server.
You have to install the vSphere Syslog Collector to enable ESXi system logs to be directed to a server on the network, rather than to a local disk. It’s possible install the Syslog Collector on the same machine as the associated vCenter Server, or on a different machine that has network connection to the vCenter Server. The Syslog Collector service binds to an IPv4 address for communication with vCenter Server, and does not support IPv6. The vCenter Server can be on a host machine in an IPv4-only, IPv4/IPv6 mixed-mode, or IPv6-only network environment, but the machine that connects to the vCenter Server through the vSphere Client must have an IPv4 address for the Syslog Collector service to work.
In the ESXi Software panel there's an Advanced Setting called Syslog.global.LogHost, the value of this setting presents the remote host to which syslog messages are forwarded and port on which the remote host receives syslog messages. You can include the protocol and the port, for example, ssl://hostName1:514. UDP (default), TCP, and SSL are supported. The remote host must have syslog installed and correctly configured to receive the forwarded syslog messages. Checkout the video how the syslog service is installed on the vCenter host.
You can also set up ESXi Syslog from the Host Profiles Interface. Hosts provisioned with Auto Deploy usually do not have sufficient local storage to save system logs. You can specify a remote syslog server for those hosts by setting up a reference host, saving the host profile, and applying that host profile to other hosts as needed. Best practice is to set up the syslog server on the reference host with the vSphere Client or the esxcli system syslog command and save the host profile. In some situations, setting up syslog from the Host Profiles interface is an alternative.
The card is available under a Creative Commons license, so feel free to copy and distribute this in paper or electronic format. Just check back frequently to www.vReference.com for updates, or subscribe to the RSS feed to be the first to know.
Forbes Guthrie: At long last, the vSphere 5.0 vReference Card is ready. Go and grab it over here. This time I’ve split it up into both an A4 version and a separate Letter size one. This should hopefully make the printing experience more consistent regardless of which side of the pond you try.New with this release is a full page version. This is the same information as the card, but I’ve increased the font to a less eye-ball screamingly small font. This should make it make much more conducive to reading as a study guide, or if you want to bone-up on a particular area.
VMware supports in-place upgrades on 64-bit systems from vCenter Server 4.x to vCenter Server 5.0. You can upgrade VirtualCenter 2.5 Update 6 or later and vCenter Server 4.0.x to vCenter Server 5.0 by installing vCenter Server 5.0 on a new machine and migrating the existing database.
This upgrade method makes it possible to upgrade from a 32-bit system to a 64-bit system. Alternatively, if the VirtualCenter or vCenter Server database is on a remote machine, you can upgrade the database. vCenter Server 5.0 can manage ESX 3.5.x/ESXi 3.5.x hosts in the same cluster with ESX 4.x/ESXi 4.x hosts.
You cannot upgrade a vCenter Server 4.x instance that is running on Windows XP Professional x64 Edition to vCenter Server 5.0, because vCenter Server 5.0 does not support Windows XP Professional x64. This article provides information about upgrading to vCenter Server 5.0.
The host-X-hb (where X is the host’s MOID) is Located on each heartbeat datastore, this file is used to check for slave liveness through the heartbeat datastore. This file is checked by the master host if the master loses network heartbeats from the slave.
For VMFS datastores, the vSphere HA agent locks this file with an exclusive lock and relies on the VMkernel heartbeat to indicate liveness. For NFS datastores, vSphere HA periodically updates the time stamp to this file to indicate liveness.
The host-X-poweron (where X is the host’s MOID) is a per-host file that contains the list of all virtual machines that are powered on. This file is used as a communication channel if a management network outage occurs. Isolated slaves use this file to tell the master that it is isolated as well as to tell the master which virtual machines it has powered off.
The master host must determine whether the slave host:
• Actually crashed • Is not responding because of a network failure • The HA agent is in an unreachable state
The absence of both a network and datastore heartbeat indicates full host failure. Datastores are used as a backup communication channel to detect virtual machine and host heartbeats. Datastore heartbeats are used to make the distinction between a failed, an isolated or a partitioned host.
vCenter Chargeback Manager is an end-to-end cost reporting solution for virtual environments that are using VMware vSphere. vCenter Chargeback Manager provides functionality to define unit costs and calculate the overall costs based on the actual usage or reservation of computing resources. This Web-based application interacts with the vCenter Server Database to retrieve usage information, calculates the cost by using the defined chargeback formulas, and generates cost and usage reports.
vCenter Chargeback Manager runs on an Apache Tomcat server instance. Users interact with vCenter Chargeback Manager through a load balancer (Apache HTTP Server). vCenter Chargeback Manager connects to the vCenter Chargeback Manager database that stores application-specific information, such as the defined chargeback hierarchies, cost models, users, roles, and so on. The application interacts with the vCenter Server using VIM APIs and with the vCenter Server database through a data collector. The data collector communicates with the vCenter Server Database using JDBC.
The card is available under a Creative Commons license, so feel free to copy and distribute this in paper or electronic format. Just check back frequently to www.vReference.com for updates, or subscribe to the RSS feed to be the first to know.
Forbes Guthrie: At long last, the vSphere 5.0 vReference Card is ready. Go and grab it over here. This time I’ve split it up into both an A4 version and a separate Letter size one. This should hopefully make the printing experience more consistent regardless of which side of the pond you try.New with this release is a full page version. This is the same information as the card, but I’ve increased the font to a less eye-ball screamingly small font. This should make it make much more conducive to reading as a study guide, or if you want to bone-up on a particular area.
(Page 5 of 14, totaling 68 entries)
