69
6.
the local engine ID.
snmp-agent local-engineid
engineid
By default, the local engine ID is
the company ID plus the device
ID.
7.
update a MIB view.
snmp-agent mib-view
{
excluded
|
included
} view-name oid-tree [
mask
mask-value ]
ViewDefault
is predefined. In this
view, all the MIB objects in the
iso
subtree but the
snmpUsmMIB
,
snmpVacmMIB
snmpModules.18
accessible.
Each view-name oid-tree pair
represents a view record. If you
specify the same record with
different MIB sub-
tree masks
multiple times, the most recent
configuration takes effect. Except
for the four sub-trees in the default
MIB view, you can create up to 16
unique MIB view records.
8.
access right.
•
(Method 1.) Create an SNMP
community:
In VACM mode:
snmp-agent community { read |
write } [ simple | cipher ]
community-name [ mib-view
view-name ] [ acl acl-number | acl
ipv6 ipv6-acl-number ] *
In RBAC mode:
snmp-agent community [ simple |
cipher ] community-name
user-role role-name [ acl
acl-number | acl ipv6
ipv6-acl-number ] *
• (Method 2.) Create an SNMPv1/v2c
group, and add users to the group:
a. snmp-agent group { v1 | v2c }
group-name [ read-view
view-name ] [ write-view
view-name ] [ notify-view
view-name ] [ acl acl-number |
acl ipv6 ipv6-acl-number ] *
b. snmp-agent usm-user { v1 |
v2c } user-name group-name
[ acl acl-number | acl ipv6
ipv6-acl-number ] *
By default, no SNMP group or
SNMP community exists.
The username in method 2 has
the same purpose as the
community name in method 1.
Whichever method you use, make
sure the configured name is the
same as the community name on
the NMS.
9.
SNMP context.
snmp-agent context
context-name
By default, no SNMP context is
configured on the device.
10.
(Optional.) Map an
SNMP community to
an SNMP context.
snmp-agent community-map
community-name
context
context-name
By default, no mapping between
an SNMP community and an
SNMP context exists on the
device.
To Next Page
Loading...
Need help?
General