Trap Settings; Notification Recipients - Cisco SX350 Series Administration Manual

21
STEP 4

Trap Settings

STEP 1
STEP 2
STEP 3
STEP 4

Notification Recipients

371
Read Write—Management access is read-write. Changes can be made to the device
configuration, but not to the community.
SNMP Admin—User has access to all device configuration options, as well as
permissions to modify the community. SNMP Admin is equivalent to Read Write
for all MIBs except for the SNMP MIBs. SNMP Admin is required for access to the
SNMP MIBs.
- View Name—Select an SNMP view (a collection of MIB subtrees to which access
is granted).
• (Community Type) Advanced—Select this type for a selected community.
- Group Name—Select an SNMP group that determines the access rights.
Click Apply. The SNMP Community is defined, and the Running Configuration is updated.
The Trap Settings page enables configuring whether SNMP notifications are sent from the
device, and for which cases. The recipients of the SNMP notifications can be configured in the
SNMPv1.2 Notification Recipients
To define trap settings:
Click SNMP > Trap Settings.
Select Enable for SNMP Notifications to specify that the device can send SNMP
notifications.
Select Enable for Authentication Notifications to enable SNMP authentication failure
notification.
Click Apply. The SNMP Trap settings are written to the Running Configuration file.
Trap messages are generated to report system events, as defined in RFC 1215. The system can
generate traps defined in the MIB that it supports.
Cisco Sx350, SG350X, SG350XG, Sx550X & SG550XG Series Managed Switches, Firmware Release 2.2.5.x
page, or the SNMPv3 Notification Recipients
SNMP
Trap Settings
page.