Example; Basic Snmp Trap Configuration - Enterasys SECURESTACK C3 Configuration Manual

Creating a Basic SNMP Trap Configuration
occur. The following configuration example shows how to use CLI commands to associate SNMP
notification parameters with security and authorization criteria (target parameters), and map the
parameters to a management target address.
Complete an SNMPv2 trap configuration on a SecureStack C3 device as follows:
1. Create a community name that will act as an SNMP user password.
2. Create an SNMP target parameters entry to associate security and authorization criteria to the
users in the community created in Step 1.
3. Verify if any applicable SNMP notification entries exist, or create a new one. You will use this
entry to send SNMP notification messages to the appropriate management targets created in
Step 2.
4. Create a target address entry to bind a management IP address to:
–
–
Table 8‐11 shows the commands used to complete an SNMPv2 trap configuration on a
SecureStack C3 device.
Table 8-11 Basic SNMP Trap Configuration
To do this...
Create a community name.
Create an SNMP target parameters entry.
Verify if any applicable SNMP notification
entries exist.
Create a new notification entry.
Create a target address entry.

Example

This example shows how to:
• Create an SNMP community called mgmt.
• Configure a trap notification called TrapSink.
This trap notification will be sent with the community name mgmt to the workstation
192.168.190.80 (which is target address tr). It will use security and authorization criteria contained
in a target parameters entry called v2cExampleParams.
C3(su)->set snmp community mgmt
C3(su)->set snmp targetparams v2cExampleParams user mgmt
security-model v2c message-processing v2c
C3(su)->set snmp notify entry1 tag TrapSink
C3(su)->set snmp targetaddr tr 192.168.190.80 param v2cExampleParams taglist
TrapSink
8-38 SNMP Configuration
Note: This example illustrates how to configure an SNMPv2 trap notification. Creating an
SNMPv1 or v3 Trap, or an SNMPv3 Inform notification would require using the same commands
with different parameters, where appropriate. Always ensure that v1/v2 communities or v3 users
used for generating traps or informs are pre-configured with enough privileges to access
corresponding MIBs.
The notification entry and tag name created in Step 3 and
The target parameters entry created in Step 2.
Use these commands...
set snmp community
set snmp targetparams
show snmp notify
set snmp notify
set snmp targetaddr