Day: Apr 21, 2015

What is Processor Queue Length?

Posted on Updated on


A collection of one or more threads that is ready but not able to run on the processor due to another active thread that is currently running is called the processor queue. The clearest symptom of a processor bottleneck is a sustained or recurring queue of more than two threads. Although queues are most likely to develop when the processor is very busy, they can develop when utilization is well below 90 percent. This can happen if requests for processor time arrive randomly and if threads demand irregular amounts of time from the processor.

If queue occur frequently, You need to investigate the processes that are running when threads collect in the queue.

To determine this:

  • Identify the processes that are consuming processor time. Determine whether a single process or multiple processes are active during a bottleneck. Running processes appear in the Instance box when you select the Process\% Processor Time counter. For more information, see “Processes in a Bottleneck” later in this chapter.
  • Scrutinize the processor-intensive processes. Determine how many threads run in the process and watch the patterns of thread activity during a bottleneck.
  • Evaluate the priorities at which the process and its threads run. You might be able to eliminate a bottleneck merely by adjusting the base priority of the process or the current priorities of its threads. However, Microsoft does not recommend this as a long-term solution. Use Task Manager to find the base priority of the process.

Different guidelines apply for queue lengths on multiprocessor systems. For busy systems (those having processor utilization in the 80 to 90 percent range) that use thread scheduling, the queue length should range from one to three threads per processor. For example, on a four-processor system, the expected range of processor queue length on a system with high CPU activity is 4 to 12.

On systems with lower CPU utilization, the processor queue length is typically 0 or 1.

There are other objects that track processor queue length. The Server Work Queues\Queue Length counter reports the number of requests in the queue for the processor on the selected server.

This entry was posted in Windows and tagged .

Syslog Server storage logs size calculation

Posted on Updated on


Syslog Server storage calculation:
I want to modify the settings so that my logs size is upped from 2mb to 10mb and we rotate after 40 logs not 20.Here we need to do some planning to see if we have enough free space.

Count hosts: 100
Current size log max: 2
Current rotation count: 20
Total possible MB used: 100x2x20 = 4,000MB  (4gb)

Count hosts: 100
Desired size log max: 10
Desired  rotation count: 40
Total possible MB used: 100x10x40=40,000MB (40GB)

So the drive where your logs are stored would need 40gbfree in the above example to be able to service future demands.
How to modify the VMware Syslog Collector configuration after it is installed:

  1. Make a backup of the file:vCenter Server 5.5 and lower: %PROGRAMDATA%\VMware\VMware Syslog Collector\vmconfig-syslog.xml
    vCenter Server 6.0: %PROGRAMDATA%\VMware\vCenterServer\cfg\vmsyslogcollector\config.xml
  2. Open the copied file using a text editor.
  3. Under <defaultValues>, change any of the options to the required values.For example, to increase the log file size to 10 MB and to decrease the number of files retained to 20, modify the attributes:<defaultValues>
<port>514</port>
<protocol>TCP,UDP</protocol>
<maxSize>10</maxSize>
<rotate>20</rotate>
<sslPort>1514</sslPort>

</defaultValues>Note: This configuration in vCenter Server overrides the ESXi host configuration file.

  1. Save and close the file.
  2. Stop the VMware Syslog Collector service.
  3. Remove the file:

    vCenter Server 5.5 and lower    : %PROGRAMDATA%\VMware\VMware Syslog Collector\vmconfig-syslog.xml
    vCenter Server 6.0: %PROGRAMDATA%\VMware\vCenterServer\cfg\vmsyslogcollector\config.xml
  4. Rename the copy of the modified file to:vCenter Server 5.5 and lower: %PROGRAMDATA%\VMware\VMware Syslog Collector\vmconfig-syslog.xml
    vCenter Server 6.0: %PROGRAMDATA%\VMware\vCenterServer\cfg\vmsyslogcollector\config.xml
  5. Start the VMware Syslog Collector service. It may be required to restart the syslog service on the ESXi host if logs are no longer updating on the Syslog Server. To restart the syslog service, see VMware ESXi 5.x host stops sending syslogs to remote server (2003127).

 

The maximum supported number of hosts for use with each vSphere Syslog Collector instance is 30, however depending on the load generated by your environment, you may encounter issues below this number.

To work around this issue, you can deploy multiple instances of vSphere Syslog Collector on separate Windows machine which allows you to distribute the load.

If the customer wishes to continue using vSphere Syslog Collector with more than 30 hosts (current maximum for syslog collector). There are no plans to increase the supported number of hosts. The windows event log error does not apply to the appliance, in some instances we receive no error message but the service simply stops responding or collecting logs.
Alternatively, investigate a more scalable solution such a VMware vRealize Log Insight.

This entry was posted in VMware, Windows and tagged .

How to restart Management agents on ESXi host

Posted on Updated on


Restarting the Management agents on ESXi

To restart the management agents on ESXi:

From the Direct Console User Interface (DCUI):

  1. Connect to the console of your ESXi host.
  2. PressF2 to customize the system.
  3. Log in asroot.
  4. Use theUp/Down arrows to navigate to Restart Management Agents.

    Note: In ESXi 4.1 and ESXi 5.0, 5.1, 5.5 and 6.0 this option is available under Troubleshooting Options.

  5. PressEnter.
  6. PressF11 to restart the services.
  7. When the service has been restarted, pressEnter.
  8. PressEsc to log out of the system.

From the Local Console or SSH:

  1. Log in to SSH or Local console as root.
  2. Run these commands:

    /etc/init.d/hostd restart
    /etc/init.d/vpxa restart

    Note: In ESXi 4.x, run this command to restart thevpxa agent:

    service vmware-vpxa restart

    Alternatively:

  • To reset the management network on a specific VMkernel interface, by default vmk0, run the command:

    esxcli network ip interface set -e false -i vmk0; esxcli network ip interface set -e true -i vmk0

    Note: Using a semicolon (;) between the two commands ensures the VMkernel interface is disabled and then re-enabled in succession. If the management interface is not running on vmk0, change the above command according to the VMkernel interface used.

  • To restart all management agents on the host, run the command:

    services.sh restart

    Caution:

  • Check if LACP is enabled on DVS for version 5.x and above. For more information, see vSphere 5.0 Networking Guide

If LACP is not configured, the services.sh script can be safely executed.

This entry was posted in VMware and tagged .

How to get Serial number and System information of ESXi host remotely using putty

Posted on Updated on


Get hardware serial number using this command from putty

esxcfg-info | grep “Serial N”

Type the following command from the command line on the service console and you will get some Vendor details and serial number information.

/usr/sbin/dmidecode |grep -A4 “System Information”

This entry was posted in VMware and tagged .