SXL Statistics Test

Secure XL (SXL) is the security performance architecture of Check Point VPN-1/FireWall-1 and Nokia security appliances. When the SXL feature is enabled for the Nokia IPSO firewall, the architecture offloads multiple CPU intensive security operations to optimize Nokia IPSO code running on Intel x86 hardware or on network processor hardware. The optimized IPSO code reduces the overhead involved in performing the security operations. As a result of the reduced overhead, SXL accelerates firewall performance, throughput and connection rate by remembering certain attributes of packets and packet flows that have already been validated by the firewall. If the SXL is disabled abruptly due to any abnormal reason, the firewall may not be able to handle the traffic faster as the firewall needs to validate the connection details everytime. Therefore, it is important for administrators to continuously monitor the current status of the SXL and the traffic handled by the SXL at regular intervals. This can be easily achieved using the SXL Statistics test!

Using this test, administrators can instantly find out whether/not the Secure XL feature is enabled for the target firewall. In the process, this test also reveals the count of connections that are added to the firewall/deleted, by the SXL.

Target of the test : Nokia IPSO Firewall

Agent deploying the test : An external agent

Outputs of the test : One set of results for the target firewall that is to be monitored.

Configurable parameters for the test
Parameter Description

Test Period

How often should the test be executed.


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


Refers to the port at which the specified host listens to.


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.

Measurements made by the test
Measurement Description Measurement Unit Interpretation

SXL Status

Indicates whether the Secure XL is enabled or not.


The values reported by this measure and its numeric equivalents are mentioned in the table below:

Measure value Numeric Value
Enabled 1
Disabled 0


By default, this measure reports the Measure Values listed in the table above to indicate the current state of the Secure XL. The graph of this measure however is represented using the numeric equivalents only i.e., 0 to 1.

Existing connections

Indicates the number of connections that have already been validated by the Secure XL.


A low value of this measure may indicate that the count of connections validated by the SXL is less. Therefore, the firewall needs to natively verify the connection details everytime. This approach may increase the processing overheads and time required to establish the connections through the target firewall.

Accepted connections

Indicates the number of connections that are added to the firewall by the Secure XL.



Deleted connections

Indicates the number of connections that are deleted by the Secure XL.