Host Processors Test
This test monitors the CPU usage of every processor on a server.
Target of the test : A server that supports the HOST-RESOURCES MIB
Agent deploying the test : A remote agent
Outputs of the test : One set of results for every processor on the server being monitored
Configurable parameters for the test
- TEST PERIOD - How often should the test be executed
- HOST - The host for which the test is to be configured
- snmpport - The port used to poll for SNMP statistics (default 161)
- SNMPVERSION – By default, the eG agent supports SNMP version 1. Accordingly, the default selection in the snmpversion list is v1. However, if a different SNMP framework is in use in your environment, say SNMP v2 or v3, then select the corresponding option from this list.
- SNMPCommunity – The SNMP community name that the test uses to communicate with the target host. This parameter is specific to SNMP v1 and v2 only. Therefore, if the snmpversion chosen is v3, then this parameter will not appear.
- username – This parameter appears only when v3 is selected as the snmpversion. SNMP version 3 (SNMPv3) is an extensible SNMP Framework which supplements the SNMPv2 Framework, by additionally supporting message security, access control, and remote SNMP configuration capabilities. To extract performance statistics from the MIB using the highly secure SNMP v3 protocol, the eG agent has to be configured with the required access privileges – in other words, the eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB. Therefore, specify the name of such a user against the username parameter.
- CONTEXT – This parameter appears only when v3 is selected as the SNMPVERSION. An SNMP context is a collection of management information accessible by an SNMP entity. An item of management information may exist in more than one context and an SNMP entity potentially has access to many contexts. A context is identified by the SNMPEngineID value of the entity hosting the management information (also called a contextEngineID) and a context name that identifies the specific context (also called a contextName). If the USERNAME provided is associated with a context name, then the eG agent will be able to poll the MIB and collect metrics only if it is configured with the context name as well. In such cases therefore, specify the context name of the USERNAME in the CONTEXT text box. By default, this parameter is set to none.
- authpass – Specify the password that corresponds to the above-mentioned username. This parameter once again appears only if the snmpversion selected is v3.
- confirm password – Confirm the authpass by retyping it here.
authtype – This parameter too appears only if v3 is selected as the snmpversion. From the authtype list box, choose the authentication algorithm using which SNMP v3 converts the specified username and password into a 32-bit format to ensure security of SNMP transactions. You can choose between the following options:
- md5 – Message Digest Algorithm
- sha – Secure Hash Algorithm
- encryptflag – This flag appears only when v3 is selected as the snmpversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the encryptflag is set to no by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the yes option.
encrypttype – If the encryptflag is set to yes, then you will have to mention the encryption type by selecting an option from the encrypttype list. SNMP v3 supports the following encryption types:
- des – Data Encryption Standard
- AES – Advanced Encryption Standard
- encryptpassword – Specify the encryption password here.
- confirm password – Confirm the encryption password by retyping it here.
- TIMEOUT – Specify the duration (in seconds) beyond which the SNMP query executed by this test should time out. The default is 10 seconds.
DATA OVER TCP - By default, in an IT environment, all data transmission occurs over UDP. Some environments however, may be specifically configured to offload a fraction of the data traffic - for instance, certain types of data traffic or traffic pertaining to specific components - to other protocols like TCP, so as to prevent UDP overloads. In such environments, you can instruct the eG agent to conduct the SNMP data traffic related to the server over TCP (and not UDP). For this, set the DATA OVER TCP flag to Yes. By default, this flag is set to No.
Measurements made by the test
The average, over the last minute, of the percentage of time that a processor was not idle.
A consistently high value of this measure indicates that there could be a CPU bottleneck on the server.
In addition to the above, the Operating System layer of an Oracle server can also be configured to run the following tests: VarAdmMessages test, UnixTables test, BufferCache test, ProcessState test, IOWaits test, InodeCache test, Paging test, ad Swap test. These tests have been dealt with extensively in the Monitoring Unix and Windows Servers document.