Configuring snmpv3 basic parameters – H3C Technologies H3C S6300 Series Switches User Manual

Page 105

Advertising
background image

92

Step

Command

Remarks

8.

Configure the SNMP
access right.

(Method 1) Create an SNMP
community:

snmp-agent community { read |

write } [ simple | cipher ]
community-name [ mib-view

view-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 ] *

Use either method.
By default, no SNMP group or
SNMP community exists.
The username configured by using
method 1 is the same as that

configured by using method 2.
Usernames created by either

method must be the same as the

community name configured on the

NMS.

9.

(Optional.) Create an
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.

11.

(Optional.) Configure
the maximum SNMP

packet size (in bytes)

that the SNMP agent
can handle.

snmp-agent packet max-size byte-count

By default, the maximum SNMP
packet size that the SNMP agent

can handle is 1500 bytes.

12.

Specify the UDP port
for receiving SNMP

packets.

snmp-agent port port-number

By default, the device uses UDP
port 161 for receiving SNMP

packets.

Configuring SNMPv3 basic parameters

SNMPv3 users are managed in groups. All SNMPv3 users in a group share the same security model, but

can use different authentication and privacy key settings. To implement a security model for a user and

avoid SNMP communication failures, make sure the security model configuration for the group and the
security key settings for the user are compliant with

Table 16

and match the settings on the NMS.

Advertising