Agents Administration - Tests
 

Configuration of CpVsxCPUUtilTest

The Check Point Smart-1 appliance helps administrators to configure multiple virtual systems in their environment, where each virtual system works as a Security Gateway protecting a specified network. This test monitors the current CPU utilization of each virtual system configured in the Check Point Smart-1 appliance and reports the number of cores in the virtual system CPU. If the CPU resources are found to be consumed excessively, then, this test will help administrators to determine when exactly did the CPU utilization peak - during the last 1 sec? or 1 minute? This revelation helps administrators troubleshoot the CPU spikes better.

The default parameters associated with this test are:

  • The TEST PERIOD list box helps the user to decide how often this test needs to be executed.

  • In the HOST text box, specify the IP address of the host.

  • Specify the port at which the Check Point Smart-1 appliance exposes its SNMP MIB in the SNMPPORT text box, the default is 161.

  • 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 DATA OVER TCP flag to Yes. By default, this flag is set to No.

  • Specify the maximum duration (in seconds) for which the test will wait for a response from the server in the TIMEOUT text box. The default Timeout period is 10 seconds

  • 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.

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

  • The eG agent should connect to the MIB using the credentials of a user with access permissions to be MIB when v3 is selected as the SNMPversion. Specify the name of such a user in the USERNAME textbox.

  • 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. When v3 is selected as the SNMPversion, specify the context name of the Username in the CONTEXT text box.

  • If v3 is selected as the SNMPversion, Specify the password that corresponds to the above-mentioned Username in the AUTHPASS textbox.

  • Confirm the Password by retyping it in the CONFIRM PASSWORD text box.

  • If v3 is selected as the SNMPversion, 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, from the AUTHTYPElist box. You can choose between the following options:

    • MD5-Message Digest Algorithm

    • SHA-Secure Hash Algorithm

  • If v3 is selected as the SNMPversion,to ensure that SNMP requests sent by the eG agent are encrypted set ENCRYPTFLAG to Yes, By default, this FLAG is set to No.

  • If this Encryptflag is set to Yes then you will have to mention the encryption type supported by SNMP v3 version by selecting an option from the ENCRYPTTYPE list. You can choose between the following:

    • DES-Data Encryption Standard

    • AES-Advanced Encryption Standard

  • Specify the encryption password in the ENCRYPTPASSWORD text box.

  • Confirm the Password by retyping it in the CONFIRM PASSWORD text box.

  • If v3 is selected as the SNMPversion, sometimes, the test may not report metrics when AES192 or AES256 is chosen as the Encryption type. To ensure that the test report metrics consistently, administrators need to set ENGINEID flag to Yes, By default, this FLAG is set to No.

  • To make diagnosis more efficient and accurate, eG embeds an optional detailed diagnostic capability. With this capability, the eG agents can be configured to run detailed, more elaborate tests as and when specific problems are detected. To enable the detailed diagnosis capability of this test, by default, for a particular server, choose the On option against DETAILED DIAGNOSIS. To disable the capability, click on the Off option.

    The option to selectively enable/disable the detailed diagnosis capability will be available only if the following conditions are fulfilled:

    • The eG manager license should allow the detailed diagnosis capability.

    • Both the bad and normal frequencies configured for the detailed diagnosis measures should not be 0.

  • If multiple components of the same component type are awaiting configuration, then an APPLY TO OTHER COMPONENTS button will appear in this page. Clicking on this button will allow you to apply the configuration to all/selected components of that type.

  • Once the necessary values have been provided, clicking on the UPDATE button will register the changes made.

When changing the configuration for specific servers, a “*” beside the text box corresponding to the parameter signifies that these values have to be manually configured by the user. The parameter values that require to be configured will typically be prefixed with a “$” or contain a series of “*”. A value of “none” in the parameter value indicates that the corresponding parameter value can be changed if required.