Trap Configuration; Configuration Prerequisites; Configuration Procedure - 3Com MSR 50 Series Configuration Manual

2088 C 113: SNMP C
HAPTER

Trap Configuration

Configuration
Prerequisites

Configuration Procedure

ONFIGURATION
To do...
Configure SNMP Agent system
information
Configur Configure
e SNMP directly
NMS
access
right
Configure
indirectly
Configure the maximum size of an
SNMP packet that can be received or
sent by an SNMP agent
Configure the switch fabric ID for a
local SNMP agent
Create or update MIB view content for
an SNMP agent
c
CAUTION: The validity of a USM user depends on the switch fabric ID of the
SNMP agent. If the switch fabric ID used for USM user creation is not identical to
the current switch fabric ID, the USM user is invalid.
SNMP Agent sends Trap messages to NMS to alert the latter of critical and
important events (such as restart of the managed device).
Basic SNMP configurations have been completed. These configurations include
version configuration: community name is needed when SNMPv1 and v2c are
adopted; username and MIB view are needed if SNMPv3 is adopted.
Enabling Trap message transmission
Follow these steps to enable Trap packet transmission:
To do...
Enter system view
Use the command...
snmp-agent sys-info
{ contact sys-contact |
location sys-location |
version { { v1 | v2c | v3 }*
| all } }
Configure a snmp-agent community
community { read | write }
name community-name [ acl
acl-number | mib-view
view-name ]*
Configure an snmp-agent group { v1 |
SNMP group v2c } group-name
[ read-view read-view ]
[ write-view write-view ]
[ notify-view notify-view ]
[ acl acl-number ]
Add a new snmp-agent usm-user
user to an { v1 | v2c } user-name
SNMP group group-name [ acl
acl-number ]
snmp-agent packet
max-size byte-count
snmp-agent local-switch
fabricid switch fabricid
snmp-agent mib-view
{ excluded | included }
view-name oid-tree [ mask
mask-value ]
Use the command...
system-view
Remarks
Required
The defaults are as
follows:
Hangzhou H3C
Technology Co.,Ltd. for
contact,
Hangzhou China for
location, and SNMP v3
for the version.
Use any command.
All of these three
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 NMS
should be consistent
with the username
configured on the
Agent.
Optional
15,00 bytes by default
Optional
Company ID and device
ID by default
Optional
ViewDefault by default
Remarks
-