Configuring SNMP
Notification Recipients
Cisco 500 Series Stackable Managed Switch Administration Guide
421
22
•
IP Version
—Select either IPv4 or IPv6.
•
IPv6 Address Type
—Select the IPv6 address type (if IPv6 is used). The
options are:
-
Link Local
—The IPv6 address uniquely identifies hosts on a single
network link. A link local address has a prefix of
FE80
, is not routable, and
can be used for communication only on the local network. Only one link
local address is supported. If a link local address exists on the interface,
this entry replaces the address in the configuration.
-
Global
—The IPv6 address is a global Unicast IPV6 type that is visible and
reachable from other networks.
•
Link Local Interface
—Select the link local interface (if IPv6 Address Type
Link Local is selected) from the pull-down list.
•
Recipient IP Address
—Enter the IP address of where the traps are sent.
•
UDP Port
—Enter the UDP port used to for notifications on the recipient
device.
•
Notification Type
—Select whether to send traps or informs. If both are
required, two recipients must be created.
•
Timeout—Enter the amount of time (seconds) the device waits before re-
sending informs/traps. Timeout: Range 1-300, default 15
•
Retries—Enter the number of times that the device resends an inform
request. Retries: Range 1-255, default 3
•
User Name—Select from the drop-down list the user to whom SNMP
notifications are sent. In order to receive notifications, this user must be
defined on the SNMP User page, and its engine ID must be remote.
•
Security Level—Select how much authentication is applied to the packet.
NOTE
The Security Level here will depend on which User Name was
selected. If this User Name was configured as No Authentication, the
Security Level will be No Authentication only. However, if this User Name
has assigned Authentication and Privacy on the User page, the security
level on this screen can be either No Authentication, or Authentication
Only, or Authentication and Privacy.
The options are:
-
No Authentication
—Indicates the packet is neither authenticated nor
encrypted.