This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos XG 125 Huge memory Usage

Hello, I have a sophos XG 125 with last release 18.5.1 configured in HA (active-standby). The memory consumption is always between 85%-92% even after a restart without traffic and load. Yesterday it rebooted after reached 100% of swap usage. I started to encounter this issue of memory usage after the migration from release 17 to 18 few months ago. With release 17 memory has never gone more than 85%.

Below, some images with my situation. Snort is consuming the RAM.

Can someone help me to troubleshoot the issue?

Thank you,

Alessandro



This thread was automatically locked due to age.
Parents Reply Children
  • I disabled IPS on almost the rules. It remains active on few rules without traffic. I don't know which component is consuming so much swap memory.

  • Hello Alessandro,

    Thank you for the Case ID. I can see the engineer has reach out to GES to see if  there is a way to increase the SWAP memory.

    I can see you opened the Case on Oct 8 and the day before your appliance generated a core dump for the Awarrenhttp 

    -rw------- 1 root 0 7.0M Oct 7 15:45 core.awarrenhttp

    How many users are making use of the Web Filter/ DPI?

    The XG 125 without using IPS, Web Filter, it is designed to handle no more than 50 users.

    Most likely your device is undersized for this traffic, I would recommend you to check with your Sales Engineer to confirm.

    18.5.1 is more resource intense, than 17.5 so from my point of view that would explain the increase in memory. 

    Regards,


     
    Emmanuel (EmmoSophos)
    Technical Team Lead, Global Community Support
    Sophos Support VideosProduct Documentation  |  @SophosSupport  | Sign up for SMS Alerts
    If a post solves your question use the 'Verify Answer' link.
  • Good morning Emmanuel,

    Behind the XG125 there are more or less 50 users, someday less someday more. The strange things is that now the 100% of swap is reached also in the weekend, without users connected. So, to answer at your question, Web Filter /DPI is active for more or less 50 users.

    Thank you for your support,

    Alessandro

  • Snort is not IPS. 

    Snort is one of the backbone modules, used for most technologies in SFOS. Therefore, if there is an issue with Snort, it does not matter, if you unload or load pattern in Firewall rules. 

    Could you check the console first? 

    console> show ips-settings
    -------------IPS Settings-------------
    stream on
    lowmem off
    maxsesbytes 0
    maxpkts 8
    enable_appsignatures on
    http_response_scan_limit 65535
    search_method hyperscan
    sip_preproc enabled
    sip_ignore_call_channel enabled
    inspect all-content

    -------------IPS Instances------------
    IPS is running on all cores

    __________________________________________________________________________________________________________________

  • console> show ips-settings
    -------------IPS Settings-------------
    stream on
    lowmem off
    maxsesbytes 10
    maxpkts 8
    enable_appsignatures on
    http_response_scan_limit 65535
    search_method ac-q
    sip_preproc enabled
    sip_ignore_call_channel enabled
    inspect untrusted-content

    -------------IPS Instances------------
    IPS CPU
    1 0
    2 1

    I changed, yesterday, only maxsesbytes value as suggested by a Sophos Engineer.

  • Is this a old installation? 

    Because i assumed, hyperscan should be enabled by most customers. But not if you use a old backup. 

    Change search_method to hyperscan. 

    __________________________________________________________________________________________________________________

  • Yes, It is an old installation.

    After I change that setting snort process is using half of the RAM, at the moment. Could be the issue related to this setting?

    Thank you,

    Alessandro

  • New installations always use hyperscan to optimize the load of the pattern. You can read about it here: https://www.intel.com/content/www/us/en/developer/articles/technical/introduction-to-hyperscan.html

    But likely it will resolve your issue. You could restart the appliance now to flush the mem and it should be better. 

    __________________________________________________________________________________________________________________

  • I will organize a reboot in a non work hours. I really appreciated your help! I'll let you know in these days the behaviour.

    BR,

    Alessandro

  • nice job,that you figured this out! I think this is Alessandro's solution.

    from SNORT Man

    Queued match search methods - Matches arequeued until the fast pattern matcher is finished withthe payload, then evaluated. This was found to gen-erally increase performance through fewer cachemisses (evaluating each rule would generally blowaway the fast pattern matcher state in the cache).

    ac and ac-q - Aho-Corasick Full (high memory, best performance).