> Source: [sk170779](https://support.checkpoint.com/results/sk/sk170779)

# sk170779 - AES-NI commands no longer work in R80.40 and R81

| Property | Value |
|----------|-------|
| Solution ID | sk170779 |
| Date Created | 2020-12-01 |
| Last Modified | 2022-03-15 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81 (EOS) |

## Symptoms

- * The command **"dmesg \| grep AES-NI"** returns no output in R80.40 and R81.

* When running the command **"sim -i 0 enable_aesni"** you get the output:  

  *sim_aesni_enable: Failed to enable AES-NI. RC=-1*

## Cause

In R80.40, if AES-NI (Intel Advanced Encryption Standard New Instructions) is supported and enabled and configured automatically, there is no longer any user configuration for AES-NI to enable or disable it.

Starting from R80.40, AES-NI related debug messages are no longer sent to `dmesg`, and consequently cannot be found with `dmesg | grep 'AES-NI'`  

For R80.30 and below, use this command on the Security gateway: `# dmesg | grep 'AES-NI'`  

The expected output which indicates that AES-NI is enabled should be as follows:  
`[fw4_0];VPN-1: AES-NI is allowed on this machine. Testing hardware support`  
`[fw4_0];VPN-1: AES-NI is supported on this hardware`

## Solution

This problem was fixed. The fix is included in:

* [Check Point R81.10](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk170416)
* [Jumbo Hotfix Accumulator for R81](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk170114) starting from Take 13
* [Jumbo Hotfix Accumulator for R80.40](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk165456) starting from Take 100

The fix gives ability to check if AES-NI is enabled on the Security Gateway. To do so, run the command:   
`#fw ctl get int AESNI_is_supported`  
If the result is*1* then AES-NI is enabled.  
If the result is *0* then AES-NI is disabled.  

If you choose not to upgrade, Check Point can supply a **Hotfix** . [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.  
A Support Engineer will make sure the Hotfix is compatible with your environment before providing the Hotfix.  
For faster resolution and verification, please collect [CPinfo files](http://supportcontent.checkpoint.com/solutions?id=sk92739) from the Security Management Server and Security Gateways involved in the case.

**Hotfix installation instructions:**   
Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

<br />

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content