Creating A Basic Snmp Trap Configuration; Basic Snmp Trap Configuration - Enterasys SecureStack B3 Configuration Manual

Creating a Basic SNMP Trap Configuration

Parameters
profile
targetparam
targetparam
Defaults
None.
Mode
Switch command, read‐write.
Example
This example shows how to delete SNMP notify profile "area51":
B3(su)->clear snmp notifyprofile area51 targetparam v3ExampleParams
Creating a Basic SNMP Trap Configuration
Traps are notification messages sent by an SNMPv1 or v2 agent to a network management station,
a console, or a terminal to indicate the occurrence of a significant event, such as when a port or
device goes up or down, when there are authentication failures, and when power supply errors
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 B3 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 6‐11 shows the commands used to complete an SNMPv2 trap configuration on a
SecureStack B3 device.
Table 6-11 Basic SNMP Trap Configuration
To do this...
Create a community name.
6-36 SNMP Configuration
Specifies an SNMP filter notify name to delete.
Specifies an associated entry in the snmpTargetParamsTable.
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