LEGRAND Server Technology PRO3X User Manual page 248

• Select the 'Custom subject' checkbox, and enter the text you prefer as this email's subject. •
• • Select the 'Use custom log message' checkbox, and then create a custom message up to 1024
characters in the provided field.
• To automatically insert message placeholders, open the Custom Log Message Help section. Search •
for placeholders and click to include them in your message.
8) Click Create.
Send an SNMP Notification
This option sends an SNMP notification to one or multiple SNMP destinations.
▶
Operation:
1) Choose Device Settings > Event Rules >
2) Select 'Send SNMP notification' from the Action list.
3) Select the type of SNMP notification. See either procedure below according to your selection.
▶
To send SNMP v2c notifications:
1) In the 'Notification type' field, select 'SNMPv2c trap' or 'SNMPv2c inform.'
2) For SNMP INFORM communications, leave the resend settings at their default or do the following:
a. In the Timeout field, specify the interval of time, in seconds, after which a new inform a.
communication is resent if the first is not received. For example, resend a new inform
communication once every 3 seconds.
b. In the 'Number of retries' field, specify the number of times you want to re‑send the inform b.
communication if it fails. For example, inform communications are re‑sent up to 5 times when
the initial communication fails.
3) In the Host fields, enter the IP address of the device(s) you want to access. This is the address to
which notifications are sent by the SNMP system agent.
4) In the Port fields, enter the port number used to access the device(s).
5) In the Community fields, enter the SNMP community string to access the device(s). The community
is the group representing the PRO3X and all SNMP management stations.
Tip: An SNMP v2c notification action permits only a maximum of three SNMP destinations. To assign
more than three SNMP destinations to a specific rule, first create several SNMP v2c notification actions,
each of which contains completely different SNMP destinations, and then add all of these SNMP v2c
notification actions to the same rule.
248
.