--- title: "Mapping event types using the CLI" slug: "mapping-event-types-using-the-cli" tags: ["Product Usage", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "Network Security"] updated: 2026-09-12T20:42:23Z published: 2026-09-12T20:42:23Z canonical: "docs.trellix.com/mapping-event-types-using-the-cli" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Mapping event types using the CLI Use the CLI commands in this topic to configure event notifications. ### Prerequisites - Admin or Operator access to the Network Security appliance. ### Configuring event notifications **To configure event notifications using the CLI:** 1. Enable the CLI configuration mode. ``` hostname > enable hostname # configure terminal ``` 2. Check which notification methods and event types are already enabled for notifications: ``` hostname (config) # show fenotify alerts FireEye Notification Enabled: yes FireEye Alerts:                          email  http    rsyslog snmp                              --------------------------------                  Global  yes    no      yes     no                                ----   ----    ----    ----     domain-match        yes  |yes    yes     yes     yes     infection-match     yes  |yes    yes     yes     yes     ips-event           yes  |no     no      yes     no       lnec-alert          no   |no     no      yes     no       malware-callback    yes  |yes    yes     yes     yes     malware-object      yes  |yes    yes     yes     yes     riskware-callback   yes  |no     yes     yes     yes     riskware-object     no   |no     yes     yes     yes     web-infection       yes  |no     yes     yes     yes        Digest notification:                 Time    : 12:00                 Enabled : yes ``` 3. Enable notifications using the `fenotify enable` command. By default, notifications are enabled. This command only enables notifications for enabled protocols. ``` hostname (config) # fenotify enable ``` 4. Enable or disable the desired notification methods: ``` hostname (config) # fenotify enable ``` or ``` hostname (config) # no fenotify enable ``` For example, to enable `SMTP` notifications: ``` hostname (config) # fenotify smtp enable ``` 5. Enable or disable the desired event types globally: ``` hostname (config) # fenotify alerts enable ``` or ``` hostname (config) # no fenotify alerts enable ``` For example, to enable the event type `lnec-alert` globally: ``` hostname (config) # fenotify alert lnec-alert enable ``` 6. Map the desired event types to specific notification methods: ``` hostname (config) # fenotify alert enable ``` or ``` hostname (config) # no fenotify alert enable ``` For example, to enable the `lnec-alert` event type to use the `rsyslog` notification method: ``` hostname (config) # fenotify rsyslog alert lnec-alert enable ``` 7. Send a test message to all enabled recipients: ``` hostname (config) # fenotify send-test ``` For example, to send a test notification using email: ``` hostname (config) # fenotify email send-test ``` > [!NOTE] > Note > > - Before you can test notifications, you need to add one or more recipients. To add an email recipient, see [Adding email (SMTP) recipients using the CLI](/network-and-platform/docs/adding-email-smtp-recipients-using-the-cli). > - Test messages generated for event notifications appear on the **Alerts** tab for five minutes. 8. Save the configuration: ``` hostname (config) # write memory ```