3Com S7906E Configuration Manual page 2407

To do...
Add a new user to an SNMP
agent group
Configure the maximum size of
an SNMP packet that can be
received or sent by an SNMP
agent
Follow these steps to configure SNMPv1 and SNMPv2c:
To do...
Enter system view
Enable the SNMP agent
Configure SNMP agent system
information
Configure a local engine ID for
an SNMP entity
Create or update MIB view
content for an SNMP agent
Configur
e
directly
Configur
e SNMP
NMS
access
Configur
right
e
indirectl
y
Use the command...
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 ]
snmp-agent packet max-size
byte-count
Use the command...
system-view
snmp-agent
snmp-agent sys-info
{ contact sys-contact |
location sys-location | version
{ { v1 | v2c | v3 }* | all } }
snmp-agent local-engineid
engineid
snmp-agent mib-view
{ excluded | included }
view-name oid-tree [ mask
mask-value ]
Create snmp-agent community
an { read | write }
SNMP community-name [ acl
commun acl-number | mib-view
ity view-name ]*
snmp-agent group { v1 | v2c }
Configur
group-name [ read-view
e an
read-view ] [ write-view
SNMP
write-view ] [ notify-view
group
notify-view ] [ acl acl-number ]
Add a
user to snmp-agent usm-user { v1 |
an v2c } user-name group-name
SNMP [ acl acl-number ]
group
1-4
Remarks
Required
If the cipher keyword is
specified, the arguments
auth-password and
priv-password are considered
as cipher text passwords.
Optional
1,500 bytes by default.
Remarks
—
Optional
Disabled by default
You can enable the SNMP
agent through this command or
any commands that begin with
snmp-agent.
Required
The defaults are as follows:
3Com Corporation. for contact;
Marlborough, MA 01752 USA
for location, and SNMP v3 for
the version.
Optional
Company ID and device ID by
default.
Optional
The MIB view name is
ViewDefault and OID is 1 by
default.
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
agent.