
Configuring for Network Management Applications
Using SNMP Tools To Manage the Switch
[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.
For 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 restricted
(Access to all MIB objects (read-only)
except the CONFIG MIB.)
ProCurve(config)# snmp-server community red-team
manager unrestricted
ProCurve(config)# snmp-server community blue-team
operator restricted
To eliminate a previously configured community named "gold-team":
ProCurve(config) # no snmp-server community gold-team
SNMPv3 Notification and Traps
The switches covered by this manual support the SNMPv3 notification
process. They also support version 1 or version 2c traps. For more information
on version 1 or version2c traps, see “SNMPv1 and SNMPv2c Trap Features”
on page 15-19. The SNMPv3 notification process allows for the messages
passed to be authenticated and encrypted if you choose. To set up a SNMPv3
notification there are three steps:
1. Establish a Notification with the snmpv3 notify command
2. Point the notification to an Address with the snmpv3 targetaddress com-
mand.
3. Establish a parameter record for the target address with the snmpv3
params command.
15-16
Comentários a estes Manuais