Download Print this page

Advertisement

Step
7.
(Optional.) Configure a remote
engine ID.
8.
(Optional.) Create or update a
MIB view.
9.
Create an SNMPv3 group.
10.
(Optional.) Convert a plaintext
key to an encrypted key.
Command
snmp-agent remote { ip-address |
ipv6 ipv6-address } [ vpn-instance
vpn-instance-name ] engineid
engineid
snmp-agent mib-view { excluded |
included } view-name oid-tree
[ mask mask-value ]
In non-FIPS mode:
snmp-agent group v3
group-name [ authentication |
privacy ] [ read-view
view-name ] [ write-view
view-name ] [ notify-view
view-name ] [ acl acl-number |
acl ipv6 ipv6-acl-number ] *
In FIPS mode:
snmp-agent group v3
group-name { authentication |
privacy } [ read-view
read-view ] [ write-view
write-view ] [ notify-view
notify-view ] [ acl acl-number |
acl ipv6 ipv6-acl-number ] *
In non-FIPS mode:
snmp-agent calculate-password
plain-password mode {md5 |
sha } { local-engineid |
specified-engineid engineid }
In FIPS mode:
snmp-agent calculate-password
plain-password mode sha
{ local-engineid |
specified-engineid engineid }
99
Remarks
By default, no remote engine ID is
configured.
To send informs to an SNMPv3
NMS, you must configure the
SNMP engine ID of the NMS.
By default, the MIB view
ViewDefault is predefined. In this
view, all the MIB objects in the iso
subtree but the snmpUsmMIB,
snmpVacmMIB, and
snmpModules.18 subtrees are
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.
By default, no SNMP group
exists.
N/A

Advertisement

This manual also for:

5900

Comments to this Manuals

Symbols: 0
Latest comments: