--- title: "Configure an SNMP Forwarder" slug: "configure-an-snmp-forwarder-2" tags: ["Product Usage", "IPS 11.1.x"] updated: 2026-11-19T12:28:23Z published: 2026-11-19T12:28:23Z canonical: "docs.trellix.com/configure-an-snmp-forwarder-2" --- > ## 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. # Configure an SNMP Forwarder **Steps:** 1. To add an SNMP server, go to the **SNMP** tab and click the ![GUID-E7BA235E-C8E9-494B-A481-32F301FEAAB8-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-a265d0b5-4039-16f5-7bb1-cb4512697e13(8).png?sv=2026-02-06&spr=https&st=2026-11-20T13%3A19%3A01Z&se=2026-11-20T14%3A19%3A01Z&sr=c&sp=r&sig=jKmVtPq0AArEWQXoPPHV%2BgL366UZ0gxeK%2F2%2FEBR4V1s%3D) icon at the bottom-left corner of the page. The **SNMP Forwarder Configuration Details** panel opens to the right of the page. ![GUID-4E8FE5C5-797E-4436-91DF-77DFD85DE1C3-low.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-d8ae7ce9-c891-539e-ff2c-1d21d7275486(7).png?sv=2026-02-06&spr=https&st=2026-11-20T13%3A19%3A01Z&se=2026-11-20T14%3A19%3A01Z&sr=c&sp=r&sig=jKmVtPq0AArEWQXoPPHV%2BgL366UZ0gxeK%2F2%2FEBR4V1s%3D) 2. Specify your options in the appropriate fields. | Field | Description | | --- | --- | | **Profile Name** | Specify a profile name for the server addition. This name will be used while configuring the SNMP notification profile. > [!NOTE] > Note > > It is recommended to specify the Server Profile Name as **_** to avoid confusing with child domains names. | | **IP Address** | IP address of the target SNMP server. This can be an IPv4 or IPv6 address. | | **Target Port** | SNMP listening port of the target server | | **SNMP Version** | The version of SNMP running on your target SNMP server. Version options are **1**, **2c**, **Both 1 and 2c**, and **3**. | | **Community String** | Enter an SNMP community string to protect your Trellix IPS data. SNMP community strings authenticate access to Management Information Base (MIB) objects and functions as embedded passwords. | | The following fields appear only when **SNMP Version** 3 is selected. | | **Username** | Username for authentication | | **Authoritative Engine ID (Hex Values)** | The authoritative (security) engine ID used for SNMP version 3 REQUEST messages by primary Manager. The length of the hex value of the Authoritative Engine ID should be between 10 and 50 hexadecimal characters. | | **Authoritative Peer Engine ID (Hex Values):** > [!NOTE] > Note > > The **Authoritative Peer Engine ID** field is available while configuring SNMP version 3 only after successful creation of an MDR pair. | The authoritative (security) engine ID used for SNMP version 3 REQUEST messages by secondary Manager. > [!NOTE] > Note > > The Authoritative (security) engine ID for any Manager is unique. At any point of time, the **Authoritative Engine ID** of the Manager is static irrespective of Manager status in case of an MDR pair. That is, when MDR switchover occurs, the authoritative engine ID of the Manager will not change with the status of the Manager. Hence, the alerts generated from the Primary and Secondary Manager will have their respective authoritative engine IDs. > [!NOTE] > Note > > After successful deletion of an MDR pair, the Authoritative Engine IDs are retained by the respective Managers. | | **Authentication Level** | This specifies the authentication level and has the following categories: - **No Authorization, No Privileges** — Uses Username match for authentication - **Authorization, No Privileges** — Provides authentication based on the MD5 or SHA algorithms - **Authorization and Privileges** — Provides authentication based on the MD5 or SHA algorithms. It also provides encryption in addition to authentication based on the DES or AES standards. | | **Customize Community** | Enter an SNMP community string to protect your Trellix IPS data. SNMP community strings authenticate access to Management Information Base (MIB) objects and functions as embedded passwords. | | The following fields appear only when **Authorization, No Privileges** is selected as **Authentication Level**: | | **Authentication Type** | The authentication protocol (MD5, SHA, or SHA256) used for authenticating SNMP version 3 messages | | **Authentication Password** | The authentication pass phrase used for authenticating SNMP version 3 messages | | The following fields appear only when **Authorization and Privileges** is selected as **Authentication Level**: | | **Authentication Type** | The authentication protocol (MD5, SHA, or SHA256) used for authenticating SNMP version 3 messages | | **Authentication Password** | The authentication pass phrase used for authenticating SNMP version 3 messages | | **Encryption Type** | The privacy protocol (DES, AES, or AES256) used for encrypting SNMP version 3 messages > [!NOTE] > Note > > **AES256** appears in the drop-down menu only when you choose **SHA256** as the **Authentication Type**. | | **Privacy Password** | The privacy pass phrase used for encrypting SNMP version 3 messages | 3. Click **Save**. The SNMP server is added under the **SNMP** tab. > [!NOTE] > Note > > Do not use a broadcast IP address (that is, 255.255.255.255) as the target SNMP server for forwarding alerts. 4. If you want to modify an existing entry, double-click the specific SNMP entry. The **SNMP Forwarder Configuration Details** panel opens where you can update the required fields and save the changes. 5. In case you want to delete an existing server, select the specific entry and click ![GUID-C5DB3A60-0A1C-4C8F-83A6-37EAFFF00433-low.jpg](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-2ebd8f05-a000-f22e-5dff-257981fc8b48(14).jpg?sv=2026-02-06&spr=https&st=2026-11-20T13%3A19%3A01Z&se=2026-11-20T14%3A19%3A01Z&sr=c&sp=r&sig=jKmVtPq0AArEWQXoPPHV%2BgL366UZ0gxeK%2F2%2FEBR4V1s%3D). You can delete only one server entry at a time.