Trap Configuration; Configuration Prerequisites; Configuration Procedure - H3C S9500 Series Operation Manual

Operation Manual – SNMP
H3C S9500 Series Routing Switches
Configure the engine ID
for a local SNMP agent
Create or update MIB
view content for an SNMP
agent
Caution:
The validity of a USM user depends on the engine ID of the SNMP agent. If the engine
ID used for USM user creation is not identical to the current engine ID, the USM user is
invalid.

1.3 Trap Configuration

SNMP Agent sends Trap messages to NMS to alert the latter of critical and important
events (such as restart of the managed device).

1.3.1 Configuration Prerequisites

Basic SNMP configurations have been completed.

1.3.2 Configuration Procedure

I. Enabling Trap message transmission
Follow these steps to enable Trap packet transmission:
Enter system view
Set to enable the device
to send Trap packets
globally
To do...
snmp-agent
local-engineid engineid
snmp-agent mib-view
{ included | excluded }
view-name oid-tree
[ mask mask-value ]
To do...
system-view
snmp-agent trap enable
[ bgp | configuration |
flash | mpls | ospf
[ process-id ]
[ ospf-trap-list ] | standard
[ authentication |
coldstart | linkdown |
linkup | warmstart ]* |
system | vrrp
[ authfailure |
newmaster ] ]
Use the command...
Use the command...
1-5
Chapter 1 SNMP Configuration
Remarks
Optional
Company ID and device
ID by default
Optional
ViewDefault by default
Remarks
—
Optional
All types of Trap packets
are allowed by default.