Configuring Usm And Vacm Security - Motorola BSR 2000 Configuration And Management Manual

BSR 2000 Configuration and Management Guide
2. Use the no snmp-server community command to remove the specified
Caution: Using only a community name to establish SNMP access levels is
not a completely secure access control method.
included in every packet transmitted between an SNMP client and server
but is not encrypted, which
accessible to any packet capture software. Access to SNMP Get/Set
operations could provide the following:
Note: If you do not specify a view, the system sets a default to the dod MIB
group (that is, 1.3.6). If you do not specify an administrative permission
(read-only or read-write), the system uses the default of read-only.
Example
MOT

Configuring USM and VACM Security

You can define security levels for each SNMP Server by establishing a USM with
defined access levels. Set permissions to a specified set of MIB objects with the
VACM. These security methods encrypt transmissions between an SNMP client and
server and allow the SNMP Server to authenticate each user requesting access. They
also let you specify various protection levels (unsecured, authenticated, and
authenticated with encryption) that are common to SNMPv3. USM specifies
authentication and encryption functions. VACM specifies how access-control rules
are handled. Configuring USM and VACM security for an SNMP Server involves the
following tasks:
4-28
community string.
A blueprint of a network topology and configuration
Control of a device configured for remote SNMP management
(config)#snmp-server community public
Configuring a Group Model
Configuring a MIB View
Associating Groups to MIB Views
Configuring an SNMP Context
makes SNMP Get/Set operations potentially
MGBI
Release 1.0
The community string is
526360-001-00 Rev. B