MTA Admin Thread Test

This test measures the health of the GroupWise Message Transfer Agent's (MTA) admin thread.

Target of the test : A GWMTA application

Agent deploying the test : A remote agent

Outputs of the test : One set of results for every MTA application.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


The IP address of the host for which this test is to be configured.


The port at which the server listens.


The port at which the monitored target exposes its SNMP MIB; The default value is 161.


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.


The SNMP community name that the test uses to communicate with the firewall. This parameter is specific to SNMP v1 and v2 only. Therefore, if the SNMPVersion chosen is v3, then this parameter will not appear.


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 this parameter. 


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.


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.


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


This flag appears only when v3 is selected as the SNMPversion. By default, the eG agent does not encrypt SNMP requests. Accordingly, the this flag is set to No by default. To ensure that SNMP requests sent by the eG agent are encrypted, select the Yes option. 


If this 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


Specify the encryption password here.

Confirm Password

Confirm the encryption password by retyping it here.


Specify the duration (in seconds) within which the SNMP query executed by this test should time out in this text box. 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 monitored target over TCP (and not UDP). For this, set this flag to Yes. By default, this flag is set to No.


The name of the domain on which the MTA has been installed. Refer to Determining Domain Name of MTA to know how to find out the domain name of MTA.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

Thread status

Indicates the status of the admin thread.


If the value is 1, it indicates that the thread is running. If the value is 0, it indicates that the thread is not running. Therefore, start the thread. If the value is –1, it indicates that the status is "unknown". In such a case, restart the MTA.

Message processing rate

Indicates the rate at which admin messages were processed by this MTA during the last measurement period.


A high value may be indicative of an excessive load on the admin thread.

Error messages

Indicates the rate at which admin message errors were detected by this MTA during the last measurement period.


If this value is high, check the domain DB status.

Messages in queue

Indicates the number of admin messages waiting to be processed.


If this value is high, check the admin thread status and Msgs_processing_rate, and then, act accordingly. 

Database status

Indicates the status of the domain database.


The status indicators are:

  • 1  - Normal
  • 0  - Database error
  • -1 - Unknown

0 indicates a critical database error. The domain database cannot be recovered. Rebuild the domain database using ConsoleOne. The MTA admin thread will not process any more administrative messages until the database status has returned to Normal. If the value is –1, restart the MTA.

Database recoveries

Indicates the number of DB recoveries performed during the last measurement period.


If the frequency of db_recovery is more, it may be indicative of a critical database error.