snmp-agent community write adminnms2 mib-view allexthgmp acl 2001
#
snmp-agent sys-info contact call Operator at 010-12345678
snmp-agent sys-info version v2c v3
snmp-agent target-host inform address udp-domain 1.1.1.2 params securityname
1.1.2.1
#
snmp-agent mib-view excluded allexthgmp hwCluster
#
snmp-agent inform timeout 5
snmp-agent inform resend-times 6
snmp-agent inform pending 7
#
return
3.5.3 Example for Configuring a Device to Communicate with an
NM Station by Using SNMPv3
This section provides an example to describe how to configure a device to communicate with
an NM station by using SNMPv3 and how to specify the MIB objects that can be managed by
the NM station.
Networking Requirements
CAUTION
On a single NE5000E, an interface is numbered in the format of slot number/card number/
interface number. In the multi-chassis scenario, an interface is numbered in the format of chassis
ID/slot number/card number/interface number. This requires the chassis ID to be specified along
with the slot number.
, two NM stations (NMS1 and NMS2) and the router are connected
across a public network. According to the network planning, NMS2 can manage every MIB
object except HGMP on the router, and NMS1 does not manage the router.
On the router, only the modules that are enabled by default are allowed to send alarms to NMS2.
This prevents an excess of unwanted alarms from being sent to NMS2. Excessive alarms can
make fault location difficult.
The data transmitted between NMS2 and the router needs to be encrypted and the NMS
administrator needs to be authenticated because the data has to travel across the public network.
Contact information of the equipment administrator needs to be configured on the router. This
helps the NMS administrator to contact the equipment administrator if a fault occurs.
HUAWEI NetEngine5000E Core Router
Configuration Guide - System Management
3 SNMP Configuration
Issue 01 (2011-10-15)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
93