Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

How do I create or edit an SNMP Notification Contact on the SMS?

    • Updated:
    • 7 Dec 2017
    • Product/Version:
    • TippingPoint SMS All
    • TippingPoint Virtual SMS
    • Platform:
Configure notification contacts to send messages to a recipient (either human or machine) in response to a traffic-related event that occurs on the device. The traffic-related event can be the result of triggering a filter configured with an action set that specifies a notification contact.

How To: Create/Edit a SNMP Notification Contact

  1. Log in to the SMS from a client.
  2. From the top navigation pane, click Profiles. The Profiles screen displays.
  3. From the navigation pane on the left, click the + sign next to the IPS Profiles to expand the category and select Shared Settings.
  4. Select the Notification Contacts tab.
  5. From the SNMP area, do one of the following to create a new contact:
    • Click New.
    • Right-click an entry and click New.
  6. Select an SNMP notification contact and do one of the following to edit an existing contact:
    • Click Edit.
    • Right-click an entry and click Details.
  7. The Add SNMP Contacts or Edit SNMP Contacts dialog box displays.
    • Enter or modify the Name for the contact.
    • Enter or modify the SNMP Host Address and SNMP Port (generally 162) for the contact.
    • Enter of modify the amount of Aggregation in minutes.
  8. Click OK.


Note 1: SNMP notification contacts require SNMPv2, and will not work when SNMPv2 is disabled.

Note 2: Alert notification is controlled by the aggregation period that you configure when you Email or SNMP Notification. The aggregation period is the amount of time that the device will accrue alerts before it sends a notification. The first time a particular filter is triggered, a notification is sent to the alert contact target. At the same time, the aggregation timer starts ticking down the aggregation period. During the aggregation period, further packet triggers are counted, but no notification is sent. At the end of the aggregation period, a second notification, including the packet count, is sent. The timer and the counter are reset, and will continue to cycle as long as the filter in question is active.


CAUTION: Short aggregation periods can significantly affect system performance. The shorter the aggregation period, the higher the system load. In the event of a flood attack, a short aggregation period can lead to system performance problems.


Reference: User Guide

Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.