[operator | manager]
Optionally assigns an access level.
• At the operator level, the community can access all MIB objects
except the CONFIG MIB.
• At the manager level, the community can access all MIB objects.
[restricted |
unrestricted]
Optionally assigns MIB access type.
• Assigning the restricted type allows the community to read MIB
variables, but not to set them.
• Assigning the unrestricted type allows the community to read and
set MIB variables.
Example:
To add the following communities:
Community Access Level Type of Access
red-team manager (Access to all MIB
objects.)
unrestricted (read/write)
blue-team operator (Access to all MIB
objects except the CONFIG MIB.)
restricted (read-only)
switch(config)# snmp-server community red-team
manager unrestricted
switch(config)# snmp-server community blue-team
operator restricted
To eliminate a previously configured community named "gold-team":
switch(config) # no snmp-server community gold-team
SNMP notifications
The switches:
• Default Traps: A switch automatically sends default traps to trap receivers using the configured community
name. You have to configure and supply the community name to use in the trap-receiver config, there is no
default. Use the snmp-server host <IP_ADDRESS> community "<COMMUNITY_NAME>" command to
configure a community name and the snmp-server host <IP_ADDRESS> community
"<COMMUNITY_NAME>" trap-level [all | critical | not-info | debug | none] command
to set the level of traps to send to the community.
• SNMPv2c informs
• SNMP v3 notification process, including traps
This section describes how to configure a switch to send network security and link-change notifications to
configured trap receivers.
154 Aruba 2530 Management and Configuration Guide for
ArubaOS-Switch 16.05