H3C S5810 Series, Руководство по эксплуатации

Страница: 672 / 820

1-4
To do… Use the command… Remarks
Add a new user to an SNMP
agent group
snmp-agent usm-user v3
user-name group-name
[ [ cipher ]
authentication-mode { md5 |
sha } auth-password
[ privacy-mode { 3des |
aes128 | des56 }
priv-password ] ] [ acl
acl-number ]
Required
If the cipher keyword is
specified, the arguments
auth-password and
priv-password are considered
as cipher text passwords.
Configure the maximum size of
an SNMP packet that can be
received or sent by an SNMP
agent
snmp-agent packet max-size
byte - count
Optional
1,500 bytes by default.
Follow these steps to configure SNMPv1 and SNMPv2c:
To do… Use the command… Remarks
Enter system view system-view —
Enable the SNMP agent snmp-agent
Optional
Disabled by default
You can enable the SNMP
agent through this command or
any commands that begin with
snmp-agent .
Configure SNMP agent system
information
snmp-agent sys-info
{ contact sys-contact |
location sys-location | version
{ { v1 | v2c | v3 }* | all } }
Required
The defaults are as follows:
Hangzhou H3C Technologies
Co., Ltd. for contact; Hangzhou
China for location and SNMPv1
SNMPv2c SNMPv3 for the
version.
Configure a local engine ID for
an SNMP entity snmp-agent local-engineid
engineid
Optional
Company ID and device ID by
default.
Create or update MIB view
content for an SNMP agent
snmp-agent mib-view
{ excluded | included }
view - name oid - tree [ mask
mask-value ]
Optional
The MIB view name is
ViewDefault and OID is 1 by
default.
Configur
e
directly
Create
an
SNMP
commun
ity snmp-agent community
{ read | write }
community - name [ acl
acl-number | mib-view
view-name ]*
Configur
e SNMP
NMS
access
right
Configur
e
indirectl
y
Configur
e an
SNMP
group
snmp-agent group { v1 | v2c }
group-name [ read-view
read-view ] [ write-view
write-view ] [ notify-view
notify-view ] [ acl acl-number ]
Use either approach.
Both commands can be used to
configure SNMP NMS access
rights. The second command
was introduced to be
compatible with SNMPv3.
The community name
configured on the NMS should
be consistent with the
username configured on the