Sample notification configuration – ADC CUDA 3 User Manual

Page 203

Advertising
background image

Cuda 12000 IP Access Switch CLI-based Administration Guide

Sample SNMP Configurations

201

Sample Notification Configuration

The following sample commands configure the Cuda 12000 to send
SNMPv1 traps to a host (201.1.1.20):

cli:192.168.208.3:root# snmp-server view allaccess 1.3.6.1 included

cli:192.168.208.3:root# snmp-server group trapcommunity v1 notify allaccess

cli:192.168.208.3:root# snmp-server group trapcommunity v2 notify allaccess

cli:192.168.208.3:root# snmp-server community trapcommunity trapcommunity

cli:192.168.208.3:root# snmp-server host 201.1.1.20 trapcommunity traps version 1

In this example, the SNMP agent on the Cuda 12000 sends SNMPv1 traps
(on the default UDP port of 162) to a host with an IP address of 201.1.1.20.
Because the administrator does not specify any notification types, all types
are sent.

The administrator creates two group entries for community-based
SNMPv1/v2c access. Each group entry is assigned a notify view of “allaccess”
that allows notifications access to the entire MIB (this community has no
read or write access). The community inserted into outgoing traps will be
“trapcommunity.”

To send SNMPv2 traps instead of SNMPv1 traps, the administrator would
issue the same commands except for a slightly different version of the
snmp-server host command:

cli:192.168.208.3:root# snmp-server host 201.1.1.20 trapcommunity traps version 2c

To send inform messages instead of traps, another form of the snmp-server
host
command would be used:

cli:192.168.208.3:root# snmp-server host 201.1.1.20 trapcommunity informs version 2c

This command sends inform messages with the default timeout and retries
values set. To change the defaults to 20 (for timeout) and 5 (for retries), the
administrator would issue the following command:

cli:192.168.208.3:root# snmp-server host 201.1.1.20 trapcommunity informs timeout 20

retries 5 version 2c

Advertising