H3C SR6600-X Configuration Manual page 174

Hide thumbs Also See for SR6600-X:
Table of Contents

Advertisement

Step
2.
(Optional.) Enable
the SNMP agent.
3.
(Optional.)
Configure the system
contact.
4.
(Optional.)
Configure the system
location.
5.
Enable SNMPv3.
6.
(Optional.) Change
the local engine ID.
7.
(Optional.)
Configure a remote
engine ID.
8.
(Optional.) Create or
update a MIB view.
Command
snmp-agent
snmp-agent sys-info contact sys-contact
snmp-agent sys-info location sys-location
snmp-agent sys-info version v3
snmp-agent local-engineid engineid
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 ]
160
Remarks
By default, the SNMP agent is
disabled.
The SNMP agent is enabled
when you use any command
that begins with snmp-agent
except for the snmp-agent
calculate-password command.
The default system contact is
Hangzhou H3C Tech. Co., Ltd..
The default system location is
Hangzhou, China.
By default, SNMPv3 is
enabled.
By default, the local engine ID is
the company ID plus the device
ID.
IMPORTANT:
After you change the local
engine ID, the existing SNMPv3
users and encrypted keys
become invalid, and you must
reconfigure them.
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.

Advertisement

Table of Contents
loading

This manual is also suitable for:

R6600

Table of Contents