Professional Documents
Culture Documents
U2000 SNMP Nbi User Guide v100r006c0205 PDF
U2000 SNMP Nbi User Guide v100r006c0205 PDF
Issue 05
Date 2013-05-17
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 1/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://www.huawei.com
Email: support@huawei.com
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 2/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Related Versions
The following table lists the product versions related to this document.
Intended Audience
This document describes the basic concept and principles of the SNMP NBI (northbound
interface). And it is also describes how to deploying and maintaining the SNMP NBI. This
document also provides the relationship between the SNMP NBI and license, description of
alarms reported by the SNMP NBI, the glossary, and the acronyms and abbreviations.
This document guides the user to understand basic operations of the SNMP NBI.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 3/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Symbol Description
Command Conventions
The command conventions that may be found in this document are defined as follows.
Convention Description
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Convention Description
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 4/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Convention Description
Change History
Updates between document issues are cumulative. Therefore, the latest document issue contains
all updates made in previous issues.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 5/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Contents
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 6/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 7/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
C U2000 MIB..................................................................................................................................118
C.1 MIB Description........................................................................................................................................................119
C.2 Reported Alarm Field by U2000 MIB.......................................................................................................................119
C.3 U2000 MIB Trap........................................................................................................................................................124
C.3.1 Active Alarm Notification Trap..............................................................................................................................124
C.3.2 Active Alarm Synchronization Start Trap..............................................................................................................128
D U2000-T MIB.............................................................................................................................143
D.1 MIB Description........................................................................................................................................................144
D.2 Reported Alarm Field by U2000-T MIB...................................................................................................................144
D.3 U2000-T MIB Trap....................................................................................................................................................147
D.3.1 Active Alarm Notification Trap..............................................................................................................................148
D.3.2 Active Alarm Synchronization Start Trap..............................................................................................................151
D.3.3 Active Alarm Report Trap......................................................................................................................................152
D.3.4 Active Alarm Synchronization End Trap...............................................................................................................155
D.4 U2000-T MIB Trap Sample.......................................................................................................................................156
D.4.1 Active Alarm Trap..................................................................................................................................................156
D.4.2 Active Alarm Synchronization Start Trap..............................................................................................................158
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 8/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
F Equipment Supported..............................................................................................................163
G Acronyms and Abbreviations................................................................................................165
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 9/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
1 Preview
1.1 Overview
The overview describes main contents of each chapter.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 10/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
1.1 Overview
The overview describes main contents of each chapter.
Chapter Description
3 Introduction to the SNMP This chapter describes the basic principles of the SNMP
NBI protocol, including its system architectures, message types,
and protocol versions.
4 Deploying and Configuring This chapter describes the methods for deploying and
6 Calling the SNMP NBI This chapter describes how the OSS manages alarms on the
U2000 through the SNMP NBI.
7 Maintaining the SNMP This chapter describes the routine maintenance and FAQs
NBI of the SNMP NBI.
A Relations Between License This appendix describes license control items of the SNMP
A Relations Between License This appendix describes U2000-T MIB details, including
and SNMP Interface U2000-T MIB node descriptions, alarm fields, traps, and
trap examples.
E Service Ports Description This appendix describes service ports used by the SNMP
NBI.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 11/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
The SNMP NBI supports two formats of management information bases (MIBs): U2000 MIB and U2000-T
MIB.
l Both HW-IMAPV1NORTHBOUND-TRAP-MIB.mib and HW-IMAPV2NORTHBOUND-TRAP-
MIB.mib refer to the U2000 MIB, which is used to manage transport, access, and datacom devices, or cross-
domain devices. V1 and V2 indicate the SMI (Structure of Management Information) versions of the HW-
IMAPV1NORTHBOUND-TRAP-MIB.mib and HW-IMAPV2NORTHBOUND-TRAP-MIB.mib
respectively. The OSS selects a version based on its supported SMI version. SMI versions differ in syntax.
For details, see RFC 1155 and RFC 1902.
l T2000-NETMANAGEMENT-MIB.mib refers to the U2000-T MIB, which supports upgrades of original
transport NMSs and can manage only transport devices.
Application Develop the OSS and programs for 2 Overview, 3 Introduction to the
Developer interconnecting with the SNMP NBI. SNMP NBI, 4 Deploying and
They need to know basic principles, Configuring SNMP, 5 Configuring
functions, MIB structures, and the SNMP NBI on the OSS , 6
parameter definitions of the SNMP Calling the SNMP NBI, B
NBI. Configuration Parameters, C
U2000 MIB, andD U2000-T MIB
Focus on C U2000 MIB and D
U2000-T MIB.
Installation Deploy the SNMP NBI and verify its Chapters 5, 6, and 7, and 6, and
and connection with the OSS. They do appendixes B and D
Commissioni not need to know basic concepts or Focus on 4 Deploying and
ng Engineer principles of the SNMP NBI. Configuring SNMP. Complete
Data SNMP NBI deployment and
Configuratio configuration by referring to the
n Engineer flowchart and procedures.
4 Deploying and Configuring
SNMP, 5 Configuring the SNMP
NBI on the OSS, 6 Calling the
SNMP NBI, B Configuration
Parameters, andE Service Ports
Description
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 12/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
2 Overview
2.1 Introduction
The Simple Network Management Protocol (SNMP) northbound interface (NBI) is one of the
NBIs provided by the U2000. The operational support systems (OSSs) can access U2000 by the
SNMP NBI to monitor and manage alarms in Huawei equipment networks.
2.3 Function
The SNMP NBI supports two types of management information bases (MIBs) for different
functions. Telecommunication carriers can select an appropriate MIB to interconnect managed
devices with the OSS for network operation and maintenance (O&M) based on the following
principles.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 13/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
2.1 Introduction
The Simple Network Management Protocol (SNMP) northbound interface (NBI) is one of the
NBIs provided by the U2000. The operational support systems (OSSs) can access U2000 by the
SNMP NBI to monitor and manage alarms in Huawei equipment networks.
The SNMP protocol consists of a set of standards for network management and is the most
widely used protocol in TCP/IP networks. TCP is short for Transmission Control Protocol and
IP is short for Internet Protocol.
Huawei developed the SNMP NBI for the U2000 in compliance with industry standards. With
this NBI, OSSs can interconnect with the U2000 quickly and manage alarms on the network.
NOTE
OSSs are computer systems used by telecommunications carriers to manage performance, inventories,
services, and faults of network equipment efficiently. By function, OSSs can be classified into the service
assurance OSS, the service provisioning OSS, and the inventory management OSS.
In this document, OSSs cover upper-layer NMSs and third-party NMSs (NMS is short for network
management system). Currently, the SNMP NBI supports alarm management only and the OSS is usually
a service assurance OSS.
After an alarm is generated on the equipment, the alarm is reported to the U2000 for processing.
The U2000 then reports the processed alarm to the OSS through the SNMP NBI in real time.
The OSS queries, acknowledges, unacknowledges, or clears alarms on the U2000 through the
SNMP NBI.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 14/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
OSS
Northbound SNMP
Interface
U2000
Device Network
NEn
NE1
NE2
OSS: The SNMP NBI can support alarm management only. Generally, the OSS
indicates the service assurance OSS.
2.3 Function
The SNMP NBI supports two types of management information bases (MIBs) for different
functions. Telecommunication carriers can select an appropriate MIB to interconnect managed
devices with the OSS for network operation and maintenance (O&M) based on the following
principles.
The U2000
NEs. WhenMIB is used
loaded with to
themanage
U2000transport,
MIB, theaccess,
SNMP and
NBIdatacom
supportsNEs or manage
automatic multi-domain
alarm reporting,
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 15/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
U2000
At the U2000 side, the primary functions are:
l Reporting alarms
l Reporting heartbeat
NOTE
To enable this function, set third-party NMS parameters only on the U2000 when deploying the SNMP
NBI instead of configuring the OSS. Alarm information will be received at the preset port of the OSS
server.
After receiving alarms from the equipment or the U2000, the SNMP NBI reports these alarms
to the OSS by means of standard SNMP trap messages.
The SNMP NBI periodically reports heartbeat to the OSS. Based on the heartbeat, the OSS
determines whether the connection with the SNMP NBI is proper.
Function Description
Subscribi Subscribes alarms by alarm severity and alarm category. You can set the severity
ng alarms and category when deploying the SNMP NBI.
Sets the alarm field or variable binding (VB).
OSS
At the OSS side, the primary functions are:
l Synchronizing alarms (querying current alarms)
l
Changing filter criteria in real time
l Acknowledging/Unacknowledging alarms
l Clearing alarms
NOTE
Ensure that the OSS is connected to the SNMP NBI properly before the query function is enabled.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 16/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Function Description
Synchronizing Queries current alarms (uncleared alarms) on the U2000 in the Set
alarms (querying operation.
current alarms)
To query current alarms on the U2000, the OSS issues the query begin
command (value: 1) in the Set operation. After receiving the
command, the SNMP agent queries current alarms from the U2000
and reports the result to the OSS. If there are too many alarms and
the query needs to be stopped, the OSS issues the query end command
(value: 0) in the Set operation. After receiving the command, the
SNMP agent stops querying and does not report the result to the OSS.
For details on alarm synchronization, see 6.1.3 Synchronizing
Alarms.
For details on trap messages, see C.3 U2000 MIB Trap.
Querying alarms by Reports alarms by alarm severity and category. The filter criteria are
criteria specified during alarm subscription.
You can change filter criteria in real time when loading the U2000
MIB.
Changing filter Changes filter criteria using the Set operation when the SNMP NBI
criteria in real time is running.
The change will take effect without restarting the SNMP NBI.
U2000
At the U2000 side, the primary function is automatic alarm reporting.
NOTE
To enable this function, set third-party NMS parameters only on the U2000 when deploying the SNMP
NBI instead of configuring the OSS. Alarm information will be received at the preset port of the OSS
server.
After receiving alarms from the equipment or the U2000, the SNMP NBI reports these alarms
to the OSS using standard SNMP traps. For details, see D.3 U2000-T MIB Trap.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 17/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Function Description
Subscribi Subscribes alarms by alarm severity and alarm category. You can set the severity
ng alarms and category when deploying the SNMP NBI.
OSS
At the OSS side, the primary function is querying current alarms on the U2000 (current alarms
are uncleared alarms). The OSS uses the Set operation to query these alarms.
NOTE
Ensure that the OSS is connected to the SNMP NBI properly before the query function is enabled.
To query current alarms on the U2000, the OSS issues the query begin command (value: 1) in
the Set operation. After receiving the command, the SNMP agent queries current alarms from
the U2000 and reports the result to the OSS. If there are too many alarms and the query needs
to be stopped, the OSS issues the query end command (value: 0) in the Set operation. After
receiving the command, the SNMP agent stops querying and does not report the result to the
OSS.
Function Description
Querying Reports all alarms by default. You can stop alarm synchronization using the Set
all current operation.
alarms
Querying Reports alarms by alarm severity and category. The filter criteria are specified
alarms by during alarm subscription.
criteria
Figure 2-2 shows that SNMPv1 and SNMPv2c use the community-based security mechanism,
while SNMPv3 uses the user-based security mechanism.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 18/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NMS
l Before the Get, Get Next, or Set operation, the NMS must know the read and write
community names configured for the agent.
l For trap and inform packets, the community name is the read community name configured
for the agent.
NOTE
SNMPv3
The security mechanism of SNMPv3 is user-based. In terms of security, SNMPv3 emphasizes
data security and access control and therefore offers a higher level of security than SNMPv1 and
SNMPv2c.
In data security, SNMPv3 provides protection for SNMP packets in the following ways:
In access control, the NMS performs security checks on managed objects (MOs) based on
SNMPv3.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 19/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Security Level
Table 2-1 shows security levels supported by the SNMP versions.
NOTE
Currently, the SNMP NBI complies with the following three SNMP protocol versions:
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 20/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l SNMPv2c: the second release version. Some data types and protocol applications are added.
For details, see RFC1902.
l SNMPv3: the latest release version. The security mechanism is reinforced. For details, see
RFC2571, RFC2572, RFC2573, RFC2574, and RFC2575.
Indicator Description
Alarm forwarding efficiency No less than 60 alarms per second (for three
NMS connections)
SNMP request response delay Less than 5 seconds (CPU usage is less than
50%)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 21/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
3.1 Overview
SNMP is one of the widely applied NMS protocols in the TCP/IP network.
3.4 MIB
MIB is a key part of the SNMP network management framework.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 22/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
3.1 Overview
SNMP is one of the widely applied NMS protocols in the TCP/IP network.
As a widely applied industry standard for the NMS protocols, the SNMP aims:
The SNMP network management framework consists of the network management system
(NMS), agent, management information base (MIB), and SNMP protocols. Figure 3-1 illustrates
relationships between them.
NOTE
In SNMPv3, both the NMS and the agent are called an entity.
SNMP MIB
NMS Agent
l NMS
An independent system that runs network management applications.
The NMS performs the following operations:
– Send query packets to NEs.
– Receive responses or traps from NEs.
l SNMP agent
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 23/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
SNMP
UDP
IP
Link Layer
Physical Layer
NOTE
For the SNMP NBI, the agent is running on the U2000 and the NMS refers to the OSS. Currently two MIBs
are supported: U2000-T MIB andU2000 MIB. For details, see C U2000 MIB and D U2000-T MIB.
PDUs are used for communication between the NMS and agents. Figure 3-3 shows five PDUs.
GetNextRequest
GetRequest
NMS SetRequest Agent
GetResponse
Trap
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 24/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l GetRequest: The PDU that the NMS uses to visit the agent and obtains one or several
parameter values.
l GetNextRequest: The PDU that the NMS uses to visit the agent and obtains the next
parameter value.
l SetRequest: The PDU that the NMS uses to visit the agent and sets one or more parameter
values.
l GetResponse: The PDU that the agent uses to return one or more parameter values to the
NMS as responses to GetRequest, GetNextRequest, and SetRequest packets.
l Trap: The PDU that the agent uses to send traps to inform the NMS of important events or
state changes that occurred in NEs.
GetRequest, GetNextRequest, and SetRequest packets are sent from the NMS to agents while
GetResponse and trap packets are sent from agents to the NMS.
3.4 MIB
MIB is a key part of the SNMP network management framework.
NOTE
For U2000, the MIB defines managed objects that are used by the function interfaces of the SNMP NBI. These
definitions are extremely important for the U2000 in that they determine what operations the OSS can perform
and what network management information the OSS can obtain.
The MIB covers all managed objects (MOs) and refers to a group of SNMP-based entities. The
MIB structure resembles a tree, so it is also called a MIB tree. Each MO is mapped to a leaf
node, also called an object or object identifier (OID). The MIB tree is static in that after the agent
is started and the MIB is initialized, the NMS queries or modifies MOs based on the current
MIB. The NMS manages the MIB in read and write mode.
All MOs in a network are displayed as a leaf node in the MIB tree. An MO is identified by OID,
a unique path that originates from the root node to the leaf node.
An OID consists of a set of integers greater than or equal to 0 and is used to identify an MO in
the MIB tree. The structure of management information (SMI) ensures that an MO is mapped
to a unique OID.
Once the MIB file is released, OIDs are bound to related MOs and this binding cannot be
modified. A MO in the MIB cannot be deleted, but can be set to obsolete indicating that this
MO is not no longer used.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 25/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Figure 3-4 gives an OID example: In the MIB tree, the MO mgmt is marked { iso(1) org
(3) dod(6) internet(1) mgmt(2) } or simply 1.3.6.1.2.
The agent on the managed node receives a request packet from the NMS through UDP port.
U2000 use 9812 by default.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 26/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
SNMPv1
l Mutual access to management information between the NMS (also called SNMP manager)
and SNMP agent.
l Operations include:
– Get
– Set
– Trap
l Protocol data units (PDU) are:
– GetRequest
– GetNextRequest
– GetResponse
– SetRequest
– Trap
l Community-based security model
NOTE
The OSS must get the community information from the U2000 administrator.
SNMPv2c
SNMPv2 inherits all functions in SNMPv1 and provides the following new features:
l Mutual access to management information between SNMP managers.
l Operations include:
– GetBulk
– Inform
– Report
l The format of traps is modified to the same as that of the Get and Set packets.
l SNMPv2 provides fractionalized error codes.
NOTE
The OSS must get the community information from the U2000 administrator.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 27/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
SNMPv3
SNMPv3 inherits all functions in SNMPv2 and provides the following new features:
The OSS must get the SNMPv3 information from the U2000 administrator, including security levels, user
names, authentication passwords, and encryption passwords.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 28/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
4.1 Overview
This topic describes the background information and the terms involved in the process of
deploying and configuring the northbound interface.
The SNMP
NBI NBI you
by default, is one of the
need components
to add the SNMPofNBI
the U2000. If you have not installed the SNMP
component.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 29/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 30/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
4.1 Overview
This topic describes the background information and the terms involved in the process of
deploying and configuring the northbound interface.
Attention Item
l Northbound interface is an optional component of the U2000. A license is required for
using this function.
l If you do not install the northbound interface component during the installation of the
U2000, you need to add it manually.
l The northbound interface is a System single-instance deployment package. Therefore, only
one instance can be deployed.
CAUTION
l After the northbound interface component is installed or added, you need to add a
corresponding instance and configure parameters. Then, the U2000 can start the NBI-related
process.
l After initializing the database of the U2000, you need to configure the northbound interface
instance again.
l After the northbound interface instance is configured, you need to restart all the NMS
services.
l You can configure only one IP address for one network interface. It is not allowed to set
multiple IP addresses for the same network interface. It is suggested that configure multiple
network interface for multiple IP address.
l If the NAT is used to transform addresses between the Msuite server and clients, deploy the
NBI on the Msuite client that installed on the U2000 server. Otherwise, the NBI may be
failure to deploy.
l The U2000 server and the OSS must can communicate with each other. Otherwise, the OSS
cannot interconnect with the NBI of the U2000. Therefore, if the U2000 server is configured
with multiple network interface cards (NICs) and the NICs are in different network segments,
set the IP address for connecting to the OSS as the IP address of the U2000 server.
l You must configure the northbound interface again after the IP of NMS changed.
Terms
The following explains certain confusable terms:
l Component: It is the software functional unit that you can choose to install. Each component
can include multiple deployment packages.
l Deployment package: It is the software unit deployed on a computer. In distributed mode,
the deployment packages of one component may be deployed on different computers.
Accordinginto
packages to the
thequantity of types:
following the instances supported, you can classify the deployment
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 31/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l Instance names are irrelevant with process names queried on the System Monitor. You can change
instance names by using the Msuite.
l The type of northbound interface deployment package is System single-instance.
Msuite
Through the GUI of the Msuite, you can conveniently deploy the northbound interface.
The Msuite is a graphical maintenance tool developed for the Huawei iManager U2000, a type
of Huawei network product. The Msuite is used to debug, maintain, and redeploy the U2000.
Refer to the Msuite part of the iManager U2000 Administrator Guide for the details about the
Msuite.
NOTE
For different operating system, the configuration requirements of U2000 is different, refer to the
corresponding Software Installation Guide for more information.
Hardware Configuration
In practice, the U2000 SNMP interface and the U2000 server run on the same PC or SUN
workstation. The hardware should be well configured enough to ensure the proper installation
and running of the U2000 server. Any additional hardware configuration is not required the
U2000 SNMP interface.
Software Configuration
The function of U2000 SNMP interface is implemented based on the ORB technology of the
SNMP. Since the the SNMP is integrated into the U2000 installation software, no additional
software configuration is required for the installation of the U2000SNMP interface.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 32/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
License
The U2000 controls the functions and available resources of the SNMP NBI through a license.
If you want to enable the SNMP interface, you need to purchase the U2000 license. Ensure the
license support SNMP interface function before deploying the SNMP NBI.
For details, see A Relations Between License and SNMP Interface . If the license does not
support the functions or resources needed, contact Huawei engineers to apply for the license.
For the license introduction and information on how to apply for a license, see section Applying
for and Updating the U2000 License in the iManager U2000 Administrator Guide .
Context l Through the GUI of the Msuite, you can conveniently deploy SNMP NBIs.
l SNMP NBI is an optional component of the U2000. A license is required for using this
function.
l If you do not install the SNMP interface component during the installation of the U2000,
you need to manually add it.
l The SNMP interface component is a single-instance system. Therefore, only one instance
can be deployed.
l After the northbound interface (SNMP) server component is installed or added, you need
to add a corresponding instance and configure parameters. Then, the U2000 can start the
SNMP-related process.
l After initializing the database of the U2000, you need to configure the SNMP NBI instance
again.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 33/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Start
Collect Connection
Parameters
No
Check the License
Yes
Deploy for No
the first time?
Yes
Add the Northbound
Interface Component
Test the
Norhtbound Interface
End
CAUTION
l Collect general parameters only and use default values for advanced parameters.
l For U2000 upgrades, select the MIB structure carefully by referring to B.2.9 MIB Frame.
l Using SNMPv3 is recommended because of its higher security than SNMPv1 and SNMPv2c.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 34/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Port to send trap 6666 Indicates the U2000 server port that sends
traps to the OSS.
The default port is 6666. You can not use
the port 161. For more details about port,
see the chapter "U2000 Port List" in
iManager U2000 Administrator Guide.
Port to receive 6666 Indicates the OSS server port that receives
trap traps from the U2000.
Write Changeme_
Community 123
SNMPv3 user name admin Indicates the security mechanisms that use
the user name, authentication password,
Password U2k_snmpv and encryption password.
Authentication 3
For details, see B.1.2 Third-Party NMS.
Password for u2000_SN
Privacy MP
Alarm Filter Alarm Level Critical Indicates the level of alarms that are
Major reported to the OSS.
Alarm Category Fault Alarm Indicates the category of alarms that are
reported to the OSS.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 35/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Alarm Date Format UTC Indicates the time format for reported
alarms. The UTC time, local time
(without time zone) and local time (with
time zone) are supported.
For details, see B.2.4 Time Format.
Real-time Alarm Cache Size 10000 Indicates the cache size for reported
alarms. Each OSS user is assigned an
independent cache.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 36/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Prerequisites
l The U2000 has been installed.
l The U2000 license has been loaded.
Context
NOTE
Procedure
Step 1 Log in U2000 server.
l On the Windows OS, log in the U2000 server as the Administrator user.
l
On the Solaris or Linux OS, log in U2000 server as the nmsuser user.
Step 2 Open the directory that contain License. Use the text viewer to view the contents of the License
file. For the relations between the control items in the U2000 license file and the SNMP NBI
functional items, see Table 4-3.
NOTE
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 37/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 3 If the license does not support the function needed, contact Huawei engineers to apply for the
license. For the license introduction and information on how to apply for a license, see section
Applying for and Updating the License in the iManager U2000 Administrator Guide.
----End
For details of Msuite, refer to appendix "Msuite" in the iManager U2000 Administrator
Guide.
Context
Generally, the process of the MSuite server server is started with the OS startup. If the process
is not started, perform the following operations to start it.
NOTE
If the server is a Netra 240, V240, or V440 workstation, the process of the MSuite server is not started with
the OS startup.
Procedure
l In Windows OS, check whether the msdaemon.exe and msserver.exe processes are started
in the Task Manager window. If you can find the two processes in the process list, the
MSuite server is running. If the two processes do not exist in the process list, the MSuite
server is not running. In this case, perform the following operations to start the MSuite
server:
----End
Prerequisites
The MSuite server must be started.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 38/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Context
If you consecutively enters incorrect passwords three times, the IP address of the PC on which
the MSuite client is installed will be locked by the U2000. The U2000 will unlock this IP address
5 minutes later.
Procedure
Step 1 On a computer where the MSuite client is installed, double-click the U2000 NMS Maintenance
Suite shortcut icon on the desktop and then wait about one minute. The Login dialog box is
displayed.
NOTE
l In Solaris/SUSE Linux OS, log in to the Java desktop system as user nmsuser. Otherwise, the U2000
NMS Maintenance Suite shortcut icon is not displayed on the desktop. To start the MSuite client by
running commands, run the following commands as user nmsuser. If you have logged in as the root
user, you cannot run the su - nmsuser command to switch to the nmsuser user to run the following
command:
$ cd /opt/U2000/engineering
$ ./startclient.sh
l If a dialog box showing The client and server versions are different. Upgrade the client using the
CAU. is displayed, the method of upgrading the U2000 client by using the CAU is as follow:
1. Install the U2000 client software in network mode: Enter https://server_IP_address:10443/cau
(more secure) or http://server_IP_address:8080/cau in the address box of the Internet Explorer,
and press Enter to access the Web installation page. For details, see Installing the U2000 Client
in Network Mode in the U2000 Client Software Installation Guide .
2. If you upgrade the U2000 client software using the CAU, the MSuite client is also upgraded. For
details, see Upgrading a Standalone U2000 Client in In-Service CAU Mode in the U2000 Client
Upgrade Guide.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 39/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
l When you log in to the MSuite client, a progress bar is displayed showing the progress of querying
components and instances. Wait until the operation is complete.
l The MSuite works in single-user mode. Specifically, only one MSuite client can log in to the MSuite at one
time.
l Change the initial password upon your first login to ensure U2000 system security and remember the new
password. For details, see 4.6.3 Changing the Password of the MSuite.
----End
Exception Handling
If a dialog box is displayed during the login, indicating that network configuration information
is inconsistent and re-synchronization is required after login, read through the message to learn
the server that needs to be synchronized. Then, update the network configuration, for details,
see iManager U2000 Administrator Guide .
Context
In the high availability system, you only need to log in to the MSuite server on the primary site
and change the password of the MSuite. The password of the MSuite on the secondary site is
then automatically changed.
Procedure
Step 1 Log in to the MSuite client. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the MSuite client, choose System > Change Password from the main menu. The Change
Password dialog box is displayed.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 40/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
----End
Prerequisites
l The Msuite client communicates with the Msuite server in the normal state.
l Ensure that all Msuite servers are started.
l Ensure that the database is running.
Deploy Environment
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
l In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Context
The SNMPinNBI
integrated is one ofofthe
the process components
installing of U2000.
the U2000 The
server. installation
There are twoofcases
the SNMP NBI is
of the installation.
l If the SNMP NBI is not installed during the installation of the U2000 server, to enable the
interface, you need to add the component first and then add the instance. For details, see
4.8 Adding SNMP NBI Component.
l If the SNMP NBI is installed during the installation of the U2000 server, to enable the
interface, you need to configure the instance. For details, see 4.9 Configuring the SNMP
NBI.
The details for how to install the U2000 Server, refer to iManager U2000 Software Installation
Guide. If you want to install SNMP NBI, ensure you have select Northbound SNMP Interface
component during the installation of the U2000 server.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 Click Instance tab, check whether the AgentSNMP exist in the instance list.
l If the AgentSNMP instance exist, refer the steps in 4.9 Configuring the SNMP NBI to
enable the SNMP NBI.
l If the AgentSNMP instance not exist, you need to check whether the SNMP NBI
deployment package exist according to the Step 3.
Click Deployment
Step 3 package list. Package tabs, check whether the SNMP NBI exist in the deployment
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 41/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l If the SNMP NBI deployment package exist, refer the steps in 4.9 Configuring the SNMP
NBI to enable the SNMP NBI.
l If the SNMP NBI deployment package not exist, refer the steps in 4.8 Adding SNMP NBI
Component to enable the SNMP NBI.
----End
Prerequisites
l The Msuite client communicates with the Msuite server in the normal state.
l Ensure that all Msuite servers are started.
l Ensure that the database is running.
l Ensure the installation directory has enough available space. In the Solaris or Linux OS,
you can run the df -hk /opt command to view the remaining space of the /opt directory.
Deploy Environment
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
l In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the Msuite client, choose Deploy > Add Component. The Add Component dialog box is
displayed.
CAUTION
l In the distributed system, the SNMP NBI could be deployed in master server only.
l You can add one SNMP NBI component only.
Step 3 Choose the North-Bound SNMP Interface component and click OK , the progress bar is
displayed.
Step 4 Wait until the message the component is successfully added is displayed. Click OK , completed
the operation
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 42/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 5 View the deployment package list in the Deployment Package tab, the North-Bound SNMP
Interface deployment package exist indicate that the operation is successful.
----End
Follow-up Procedure
After the component is added, you need to configure the SNMP NBI instance , then you can
enable the SNMP interface.
Prerequisites
l The Msuite client communicates with the Msuite server in the normal state.
l Ensure that all Msuite servers are started.
l Ensure that the database is running.
l Ensure the installation directory has enough available space. In the Solaris or Linux OS,
you can run the df -hk /opt command to view the remaining space of the /opt directory.
l Ensure that the component for the instance to be added is installed. If the component is not
installed, install it first. For details, see adding SNMP NBI component .
CAUTION
Deploy Environment
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
l
In a high
of the availability
primary site to system,
performyou
thisonly need to log in to the NMS maintenance tool server
operation.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 43/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Setting alarm filter criteria and advanced parameters are optional. Select desired parameters
based on customized requirements.
Optional Start
Yes
Whether Set the v3 security level,
SNMPv3 is used? authentication and encrption
No
Yes
Multiple NMS?
No
Set Advanced
parameters
End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 44/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
l After filter criteria for correlative alarms and engineering alarms are set, restart the U2000
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 45/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
The trap-transmitting IP address and request-receiving IP address are both the U2000 server
IP address. Ensure that this IP address can be used for successful communication between
the U2000 and the OSS.
Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the
iManager U2000 Planning Guide before you configure ports for the SNMP NBI. Before
configuring these ports, ensure that the specified ports are idle.
Do not use the default ports of the SNMP protocol (port 161 and port 162) to deploy the
SNMP NBI, because they are occupied by other processes.
2. Select the SNMP version. You also need to set the security level, authentication protocol,
and data encryption protocol if the version is set to v3.
1. Set the trap receive IP address/port. The trap receive IP address is the IP address of the OSS
server. The port is 6666 by default.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 46/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
The Receive Trap Address is not the IP address of the U2000 server.
Currently a maximum of 10 third-party NMSs are supported.
The same SNMPv3 user configured for different third-party NMSs, for example, NMS 1 and NMS
2, must use the same authentication and encryption passwords
When the U2000-T MIB is used, the SNMP NBI identifies OSSs by read or write community.
l If multiple OSSs use the same read or write community, only the first OSS gets the synchronized
results when any of the OSSs tries to synchronize data.
l It is recommended that each OSS uses a unique read or write community so that the OSS can get
correct synchronized results.
CAUTION
In a Linux-based HA system, if the floating IP address function is enabled during NMS
installation, set Send Trap address and Receive Request from NMS address to floating
IP addresses.
2. Set SNMP security parameters. For security concern, input parameters are encrypted. For
example, to set Read Community, click next to Read Community and set parameters
in the Set Password dialog box.
The following are the default security parameters. Modifying these parameters is
recommended for security concern.
l If the SNMP version is set to v1 or v2c, configure the read and write communities. By
default, the read community is Changeme_123 and the write community is
Changeme_123.
l If the SNMP version is set to v3, configure the V3 User Name, V3 Authentication
Password, and V3 Privacy Password for SNMPv3 users.
l By default, the user name is admin and the two passwords are blank.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 47/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
In the case of SNMPv3, the V3 User Name is required. If no user name is entered, the
SNMP service process cannot start after deployment.
To ensure the security of the U2000, passwords must be complex enough. For example, a
password must contain eight or more characters of two types. The allowed characters are
digits, letters, and special characters. Remember to change passwords regularly.
The password must meet the following requirements to safeguard your user account.
l Consists more than 8 characters.
l The password cannot be the user name or its reverse spelling.
l The password must consist of three of the following types of characters at least:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ?
and space
3. Set the alarm filter criteria, including Alarm Level and Alarm Category.
NOTE
Alarms are reported to the OSS based on the defined alarm severity and category.
The OSS can change the filter criteria in real time. For details, see 6.1.2 Changing Filter Criteria.
Fault: Indicates that the SNMP NBI will report alarm generation and alarm clearance. That is, the second
and third places of the value of AlarmCategoryFilter in binary mode are set to 0 when the
thirdNMSFaultFilter subinterface is invoked.
Event alarm reporting is disabled by default and cannot be configured by using the Msuite. But you can
enable this function by following methods.
l You can enable event alarm function manually. For details, see 7.3.10 How to report the event
alarm.
l To configure event alarm reporting, you can invoke the thirdNMSFaultFilter subinterface and set
the first place of the value of AlarmCategoryFilter in binary mode to 0.
4. Optional: Click New Tab Item. To add more third-party NMSs, repeat the preceding
substeps.
Heartbeat Period Default: 60s Specifies the heartbeat period of the third-
3s~300s party NMS.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 48/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
2. Click Alarm Field and set the alarm information to be reported. For details, see B.2.2
Alarm Field.
3. Click notification and set the reporting mode and other relevant parameters.
Reporting Default: Trap Mode Specifies the mode used by the SNMP
Mode Trap Mode, Inform agent for sending alarms to the OSS.
Mode
Support X733 Default: No Specifies whether traps use the event types
Alarm Yes, No and levels defined in X.733.
Yes indicates that the X.733 format is
used.
No indicates that the X.733 format is not
used.
4. Click Time Format and set the date format for reported alarms.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 49/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
5. Click Encoding Format and set the code format for traps.
6. Click Alarm Relativity Config and specify whether to report the correlative alarms.
Alarm Default: All All alarms: Queries and reports all alarms including the
Relativity alarms root alarm and correlative alarms.
Config All alarms, Root Alarm: Queries and reports only the root alarm and
Root Alarm common alarms.
7. Click Engineering Alarm and specify whether to report the engineering alarms.
8. Click Other Settings, specify whether to log alarms, and set the cache size for alarms.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 50/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Real-time Alarm Default: Specifies the cache for real-time alarms. Each
Cache Size 10000 NMS/OSS user is assigned with an independent
0-50000 cache.
When the alarm generate rate is more than the
alarm reporting rate, the SNMP NBI will buffer the
alarm data in the cache.
9. Click MIB Frame and set the MIB structure and resource information for alarms.
CAUTION
Select an appropriate MIB structure based on integration scenarios. For details, see B.2.9
MIB Frame.
In a Linux-based HA system, floating IP addresses can be used to deploy SNMP NBIs. Specifically, the
active and standby servers use the same floating IP address. In a non-Linux-based HA system, perform the
following operations to complete the configuration.
Step 7 Optional: For an HA system with multiple network interface cards (NICs), if you use the IP
address of the primary site to deploy the SNMP NBI and this IP address is not displayed in the
required drop-down list, the Address for Standby Server dialog box will be displayed.
1. Set the IP address of the secondary site for the SNMP NBI.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 51/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.
WARNING
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 52/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Prerequisites
l The SNMP NBI is correctly deployed and configured.
l The Heartbeat parameter on the Advanced tab is configured.
Heartbeat Period: 60s
Report Heartbeat Info: yes
Procedure
Step 1 On the System Monitor client, check the status of the SNMP service. If Status is Running, the
SNMP NBI is enabled.
l If no SNMP NBI process is f ound, see the 7.3.1 SNMP Service Process Is Not Displayed
for troubleshooting.
l If the SNMP NBI process fails to be started, see the 7.3.2 SNMP Service Process Fails to
Be Started for troubleshooting.
Step 2 Check whether heartbeat messages are received on the related OSS port. If no heartbeat message
is received, see the 7.3.4 The OSS Cannot Receive Heartbeat Information for
troubleshooting.
----End
Prerequisites
The SNMP NBI is correctly deployed and configured.
Procedure
Step 1 On the System Monitor client, check the status of the SNMP service. If Status is Running, the
SNMP NBI is enabled.
l
If
forno SNMP NBI process is found, see the 7.3.1 SNMP Service Process Is Not Displayed
troubleshooting.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 53/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l If the SNMP NBI process fails to be started, see the 7.3.2 SNMP Service Process Fails to
Be Started for troubleshooting.
----End
Network Planning
The MIB file HW-IMAPV1NORTHBOUND-TRAP-MIB.mib is loaded to the OSS, as shown
in Figure 4-3. The OSS manages and monitors alarms from Huawei network equipment using
the SNMPv1 NBI. Table 4-4 and Table 4-5 list detailed parameters.
You are advised to use default values for other relevant parameters. For more details, see B
Configuration Parameters.
MIB HW-IMAPV1NORTHBOUND-
TRAP-MIB.mib
Parameters Value
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 54/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters Value
IP: 10.71.226.158
U2000 Received Port: 9812
Send Port: 9832
Device Network
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 3 Click the General tab and choose SNMP Agent from the navigation tree to set parameters for
the SNMP agent.
SNMP agent parameters are U2000 server parameters.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 55/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 4 In the right pane, set the SNMP version (in this example, v1 is selected).
NOTE
Step 5 Choose Third-Party NMS from the navigation tree to set parameters for third-party NMSs in
the right pane.
Third-party NMS parameters are OSS parameters. Set the parameters according to the data plan.
NOTE
Parameter for SNMPv3 (such as user name/password, authentication password, and encryption password)
are invalid if v3 is not selected.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 56/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 6 Click the Advanced tab and choose MIB Frame from the navigation tree. In the right pane,
select U2000 MIB from the MIB drop-down list.
Step 7 Click OK . The U2000 starts to redeploy the SNMP NBI.
Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 57/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
WARNING
----End
Prerequisites
l The Msuite has been started.
l The SNMP NBI component has been installed.
Network Planning
The MIB file T2000-NETMANAGEMENT-MIB.mib is loaded to the OSS, as shown in
Figure 4-4. The OSS manages and monitors alarms from Huawei network equipment using the
SNMPv1 NBI. Table 4-6 and Table 4-7 list detailed parameters.
You are advised to use default values for other relevant parameters. For more details, see B
Configuration Parameters.
MIB T2000-NETMANAGEMENT-
MIB.mib
Parameters Value
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 58/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters Value
User: admin
set/get Inform Authentication password: U2ksnmp_v3
SNMPv3 Encryption password: u2000_SNMP
IP: 10.71.226.158
U2000 Received Port: 9832
Send Port: 9831
Device Network
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 3 Click the General tab and choose SNMP Agent from the navigation tree to set parameters for
the SNMP agent.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 59/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 4 In the right pane, set the SNMP version (in this example, v3 is selected).
l Security Model: USM
l Security Level: With authentication and encryption
l Authentication: HMACMD5
l Data Encryption: DES
Step 5 Click the General tab and choose Third-Party NMS from the navigation tree to set parameters
for third-party NMSs.
Third-party NMS parameters are OSS parameters. Set the parameters according to the data plan.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 60/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 6 Click the Advanced tab and choose MIB Frame Setting from the navigation tree. In the right
pane, select T2000-MIB from the MIB drop-down list.
Step 7 Click OK . The U2000 starts to redeploy the SNMP NBI.
Step 8 Wait until a dialog box is displayed prompting to restart all NMS processes.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 61/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
WARNING
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 62/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 63/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Prerequisites
l For SNMP NBI deployment, the SNMP version has been set to SNMPv1 or SNMPv2c,
and write and read communities have been configured.
l For SNMP NBI deployment, third-party NMS parameters have been set properly and the
OSS can receive real-time alarms or heartbeat from the U2000.
Procedure
Step 1 Confirm SNMP NBI parameters with the U2000 administrator.
1. Log in to the Msuite client.
2. On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the
main menu. View parameters as follows.
Step 2 Configure the OSS based on the previous parameters set on the U2000.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 64/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the
connection may fail.
----End
Prerequisites
l For SNMP NBI deployment, the SNMP version has been set to SNMPv3, and related
security parameters have been set.
l For SNMP NBI deployment, third-party NMS parameters have been set properly and the
OSS can receive real-time alarms or heartbeat from the U2000.
Procedure
Step 1 Confirm SNMP NBI parameters with the U2000 administrator.
1. Log in to the Msuite client.
2. On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the
main menu. View parameters as follows.
system
conditions.
Security USM model USM model l Specifies the security model of the
Model SNMPv3 protocol.
l USM: User-based Security
Mechanism
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 65/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
User Name Indicates the user admin On the General tab, choose Third-
name for Party NMS from the navigation. In
authentication. the right pane, click the tab for
configured OSSs and view V3 User
Name.
Data
Encryption Indicates
encryptionthe data The
valuedefault
is left On
Party General
theNMS tab,
from thechoose Third-
navigation. In
Password password. blank. the right pane, click the tab for
configured OSSs and view V3
Privacy Password.
Step 2 Configure the OSS based on the previous parameters set on the U2000.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 66/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 67/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Ensure that the OSS has connected to the U2000 through the SNMP NBI and the desired operations have
been licensed for use.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 68/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
Ensure that the U2000 MIB has been loaded to the OSS. To load the U2000 MIB, set the MIB
type to U2000 MIB when deploying the SNMP NBI.
Context
The SNMP NBI component has been installed and the SNMP NBI instance has been configured
on the U2000.
After the trap-receiving IP address or port and SNMP version have been set for the OSS on the
U2000, the OSS can receive real-time alarms.
You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected
to the U2000 and the related ports are permitted by the firewall.
For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring
SNMP.
Function
The OSS can call the alarm filter interface to change alarm filter criteria dynamically when the
SNMP NBI is working.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.5.
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).thirdNMSFaultFilter(5)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 69/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Setting Method
The OSS can set the value of the MIB node to change the alarm filter criteria. The format is as
follows:
IPAddress:Port:AlarmFilterLevel:AlarmCategoryFilter
Field Description
IPAddress Indicates the IP address used by the OSS. This IP address is the trap-
receiving IP address preset for third-party NMSs when the SNMP NBI is
deployed.
Port Indicates the port used by the OSS. This port is the trap-receiving port preset
for third-party NMSs when the SNMP NBI is deployed.
descending order.
A binary digit is 0 or 1.
l 1: indicates that the alarms of the corresponding alarm severity are
filtered out and the OSS cannot receive alarms with the level.
l 0: indicates that the alarms of the corresponding alarm severity are
reported and the OSS can receive alarms with the level.
Sample
Prerequisite
l The IP address of the OSS is set to 10.70.73.97 and the port for receiving alarms 6666.
l The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 70/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
To change the filter criteria as follows: alarm severity (critical or major) and alarm category
(fault or clear).
Procedure
The OSS receives responses from the U2000, indicating that the filter criteria are changed
successfully. The OSS will then receive the required alarms only.
Function
The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and
some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data
consistency and can also stop synchronization.
After the synchronization starts, the U2000 sends traps through the SNMP NBI to inform the
OSS that the alarm synchronization is started.
When the synchronization is complete or stopped, the U2000 will send traps through the SNMP
NBI to inform the OSS that the alarm synchronization is ended.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 71/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Set alarm
synchronization start node
Report alarm
synchronization start trap
Report alarm
. . All
synchronization result trap
. . Alarms
. . are
. Report the alarm . reported
synchronization stop trap
Set alarm
synchronization start node
Report alarm
synchronization stop trap
Operation Description
NOTE
For details of the alarm synchronization start trap, see C.3.2 Active Alarm Synchronization Start
Trap.
For details of the alarm synchronization result trap, see C.3.3 Active Alarm Report Trap.
For details of the alarm synchronization stop trap, see C.3.4 Active Alarm Synchronization End Trap.
MIB Definition
There are two MIB nodes for alarm synchronization:
hwNmNorthboundEventSynchronizationCommandStart and
hwNmNorthboundEventSynchronizationCommandStop. The former indicates start alarm
synchronization, while the latter indicates stop alarm synchronization.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 72/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization
(7).hwNmNorthboundEventSynchronizationCommandStart(4)
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmNorthboundEvent(7).hwNmNorthboundEventSynchronization
(7).hwNmNorthboundEventSynchronizationCommandStop(5)
Setting Method
Start alarm synchronization.
The OSS can set the value of the MIB node to start alarm synchronization within a specified
time. The format is as follows:
The OSS can set the value of the MIB node to stop alarm synchronization. The format is as
follows:
IP:port
NOTE
You do not need to set the start and end time to stop the alarm synchronization.
Parameter Description
IP Indicates the IP address used by the OSS. This IP address is the trap-
receiving IP address set for third-party NMSs when the SNMP NBI is
deployed.
port Indicates the port used by the OSS. This port is the trap-receiving port set
for third-party NMSs when the SNMP NBI is deployed.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 73/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameter Description
start Indicates the start and end time for alarm synchronization.
time:endtime The U2000 reports alarms that are generated during the preset time period.
NOTE
l If the end time is not set, the current system time of the U2000 is used as the end
time.
l If the start and end time are not set, all the active alarms are synchronized.
l If the end time is set, the start time is mandatory.
l Both the start and end time indicate the time period when alarms are generated on
the equipment rather than reported to the U2000.
l The timekeeping standard is universal time coordinated (UTC).
The syntax for start time and end time is:YYYYMMDDhhmmss.
l YYYY: Four-digit year. The range of values is 1970 onwards.
Sample
Prerequisite
l The IP address of the upper-layer OSS is set to 10.70.73.97 and the port for receiving alarms
is set to 6666.
l The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 74/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Procedure
1. The OSS sets hwNmNorthboundEventSynchronizationCommandStart to:
10.70.73.97:6666:20110301000000:20110315000000
l The OSS receives traps from the U2000, indicating that the synchronization is started.
l The U2000 reports alarms saved in the database that are generated during the preset
time period.
2. Optional:
To stop the synchronization, the OSS sets
hwNmNorthboundEventSynchronizationCommandStop to 10.70.73.97:6666.
3. After the synchronization is completed or stopped, the U2000 sends traps through the
SNMP NBI to inform the OSS that the synchronization is ended.
Function
The OSS can acknowledge U2000 alarms based on the alarm serial numbers.
The alarm status will change after the alarm is acknowledged. If acknowledged alarms are
specified as the filter criteria, the OSS will receive the information about state changes along
with the alarms.
CAUTION
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an
alarm is acknowledged by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be acknowledged
and the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.7.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 75/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Setting Method
The OSS can set the value of the MIB node to acknowledge the active alarm on U2000. The
format is as follows:
Serial Number,Serial Number,...
Parameter Description
Serial alarm serial number
Number,Se Integer, separated by a comma.
rial
Number,..
.
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical
alarms, no data will be returned after you acknowledge these alarms. The life cycle specifies the period in
which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 76/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Procedure
Query the alarm status on the OSS or U2000. The state for the alarm
20,30,10005,18000 is Acknowledge, indicating the alarm is acknowledged successfully.
The Acknowledgement User parameter is SNMP Agent User on the U2000 client.
NOTE
If acknowledged alarms are specified as the filter criteria, the OSS will receive the information about state
changes along with the alarms. The alarm time is when the alarm is acknowledged.
Function
The OSS can unacknowledge alarms based on alarm serial numbers.
The alarm status will change after the alarm is unacknowledged. If unacknowledged alarms are
specified as the filter criteria, the OSS will receive the information about state changes along
with the alarms.
CAUTION
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.8.
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).hwNmUnAcknowledgeAlarms(8)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 77/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Setting Method
The OSS can set the value of the MIB node to unacknowledge the active alarm on U2000. The
format is as follows:
Serial Number,Serial Number,...
Parameter Description
Serial alarm serial number
Number,Se Integer, separated by a comma.
rial
Number,..
.
2 Unacknowledge
and Clear Unacknowledge
and Clear Success Empty
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 78/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical
alarms, no data will be returned after you unacknowledge these alarms. The life cycle specifies the period
in which these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
Step
Query the alarm state on the OSS or U2000. The state for the alarm 20,30,10005,18000
is Unacknowledge, indicating the alarm is unacknowledged successfully. The
Acknowledgement User parameter is SNMP Agent User on the U2000 client.
NOTE
If unacknowledged alarms are specified as the filter criteria, the OSS will receive the information about
status changes along with the alarms. The alarm time is when the alarm is generated.
Function
The OSS can clear alarms based on the alarm serial numbers.
The alarm status will change after the alarm is cleared. If cleared alarms are specified as the
filter criteria, the OSS will receive the information about status changes along with the alarms.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 79/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
The Clearance User parameter is SNMP Agent User on the U2000 client after an alarm is
cleared by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be cleared and
the serial numbers will be returned to the OSS.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.3.6.
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).hwNetManagement(15).hwNmAgent
(1).hwNmFault(3).hwNmClearAlarms(6)
NOTE
Setting Method
The OSS can set the value of the MIB node to clear the active alarm on U2000. The format is
as follows:
Parameter Description
Serial alarm serial number
Number,Se Integer, separated by a comma.
rial
Number,..
.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 80/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
If you set the life cycle for acknowledged and cleared alarms and these alarms are not converted to historical
alarms, no data will be returned after you clear these alarms. The life cycle specifies the period in which
these alarms are saved in the current-alarm database.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
Procedure
Query the alarm state on the OSS or U2000. The state for the alarm 20,30,10005,18000
is Clear, indicating the alarm is cleared successfully. The Clearance User parameter is SNMP
Agent User on the U2000 client.
NOTE
If cleared alarms are specified as the filter criteria, the OSS will receive the information about status changes
along with the alarms. The alarm time is when the alarm is cleared.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 81/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
Ensure that the U2000-T MIB has been loaded to the OSS. To load the U2000-T MIB, set the
MIB type to U2000-T MIB when deploying the SNMP NBI.
Context
The SNMP NBI component has been installed and the SNMP NBI instance has been configured
on the U2000.
After the trap-receiving IP address or port and SNMP version have been set for the OSS on the
U2000, the OSS can receive alarms in real time.
You do not need to set related parameters on the OSS. Ensure that the OSS is properly connected
to the U2000 and the related ports are permitted by the firewall.
For details on how to deploy and configure the SNMP NBI, see 4 Deploying and Configuring
SNMP.
CAUTION
The reported alarm field for the U2000-T MIB consists of 36 bound variables (VBs). For details,
see D.2 Reported Alarm Field by U2000-T MIB.
Function
The UDP-based SNMP protocol cannot guarantee that all alarms are reported to the OSS and
some alarm packets may be lost. Therefore, the OSS synchronizes alarms to ensure alarm data
consistency and can also stop the synchronization.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 82/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
When the synchronization is complete or stopped, the U2000 will send traps through the SNMP
NBI to inform the OSS that the alarm synchronization is ended.
Set alarm
synchronization start node
Report alarm
synchronization start trap
Report alarm
. . All
synchronization result trap
. . Alarms
. . are
. Report the alarm . reported
synchronization stop trap
Set alarm
synchronization start node
Report alarm
synchronization stop trap
Operation Description
2. of
The U2000
the sends
start of traps
alarm through the SNMP NBI to inform the OSS
synchronization.
3. The U2000 sends traps through the SNMP NBI to report required
alarms saved in the database.
4. After the alarms are reported, the U2000 sends traps through the
SNMP NBI to inform the OSS of the end of alarm synchronization.
NOTE
For details of the alarm synchronization start trap, see D.3.2 Active Alarm Synchronization Start
Trap.
For details of the alarm synchronization result trap, see D.3.3 Active Alarm Report Trap.
For details of the alarm synchronization stop trap, see D.3.4 Active Alarm Synchronization End Trap.
MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.7.4.1.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 83/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
iso(1).org(3).dod(6).internet(1).private(4).enterprises
(1).huawei(2011).products(2).netManagement(15).nmAgent
(1).nmNorthboundEvent(7).northboundSynchAlarm
(4).northBoundSynchAlarmCommand(1)
Setting Method
The OSS can set the value of the MIB node to start or stop the synchronization. The format is
as follows:
number
Parameter Description
number 0, 1
l 0: indicates the stop of alarm synchronization.
l 1: indicates the start of alarm synchronization.
Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
Step
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 84/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 85/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
To ensure that the SNMP NBI works well, there are some requirements as follows:
Prerequisites
Before login, ensure that the U2000 client and server are connected properly and that the server
works correctly.
Context
l The default port number of the server is 31030. Do not change it in normal conditions.
Otherwise, you cannot log in to the U2000 server.
l The login modes include the SSL mode and common mode. In SSL mode, the data is
encrypted when being transmitted between the client and the server. In common mode, the
data is not encrypted during transmission. To ensure the security of data transmission, you
are recommended to use the Security (SSL) mode.
l The port used for login in common mode is different from that in SSL mode. The port
number is 31030 in common mode, and 31080 in security (SSL) mode.
l After last login, if you do not log in again during the preset period, your account hibernates
or the U2000 deletes the account.
l If you never use a new user account for login, the U2000 does not invalidate or delete the
account.
Procedure
Step 1 Double-click the shortcut icon on the desktop to start the system monitor client.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 86/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
In the Solaris and Linux OS , login to the OS of the server as the nmsuser user. Run the following command
to start the system monitor client.
$ cd /opt/U2000/client
$ ./startup_sysmonitor_global.sh
/opt/U2000 is the default installation path for the U2000. You can change it as required.
Step 2 In the Login dialog box, select a server by selecting an IP address or host name from the
Server drop-down list.
NOTE
3. In theselect
then Add aServer Information
login mode. dialog
Click OK . box, specify Name and Server Name(or IP Address), and
Step 3 In the Login dialog box, enter the user name and password.
The user name and password are the same as those used on the U2000 client.
l If the user name and the password are correct, the Loading dialog box is displayed, showing the loading
progress.
l If the user name or password is incorrect, the Information dialog box is displayed, prompting that you
cannot log in.
l If the password will expire in the specified days, a dialog box is displayed, prompting you to change
the password before the expiration date.
----End
Prerequisites
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l The U2000 must be operating.
l The SNMP Service processes are in the Running state.
Context
NOTE
After the SNMP interface instance is added through the Msuite, the default start mode is Automatic. The
SNMP interface process is started with the U2000.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 87/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Procedure
Step 1 Log in to the System Monitor.
Step 3 Select SNMP Service process, right-click and choose Stop the Process.
Step 5 On the System Monitor client, if Status of the related processes of the SNMP NBI is
Stopped, it indicates that the operation is successful.
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 88/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Prerequisites
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l The U2000 must be operating.
l The SNMP Service processes is in the Stopped state.
Procedure
Step 3 Select the SNMP Service process, right-click, and choose Startup Mode > Disable to disable
the process.
Step 4 On the System Monitor client, if Startup Mode of the related processes of the SNMP NBI is
Disabled, it indicates that the operation is successful.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 89/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
----End
Prerequisites
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l The U2000 must be operating.
l The SNMP Service processes is in the Stopped state.
Procedure
Step 1 Log in to the System Monitor.
Step 2 On the System Monitor, enter the Process Monitor tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 90/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 3 Select the SNMP Service process, right-click, and then choose Start the Process from the
shortcut menu.
Step 4 In the System Monitor client, when Status of the relevant SNMP processes, namely SNMP
Service are Running, the operation is successful.
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 91/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Prerequisites
l The Msuite client communicates with the Msuite server in the normal state.
l Ensure that all Msuite servers are started.
l
Ensure that the database is running.
l It is recommended that you stop the SNMP NBI before delete the instance.
Deploy Environment
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
l In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 Click the Instance tab. Select the AgentSNMP instance from the instance list, right-click, and
choose Delete Instance
Step 3 Click OK . After the confirmation, the Msuite begins deleting the AgentSNMP instance.
Step 4 Click the Deployment Package tab, if the Instance Count of the SNMP NBI deployment
package is zero, that means the deletion success.
Step 5 Required: Log in to the System Monitor. Restart all processes of the U2000.
----End
Result
NOTE
After the AgentSNMP instance is deleted, the Sysmonitor does not display the information about the
AgentSNMP process. If you need to re-enable the SNMP interface, refer to 4.9 Configuring the SNMP
NBI.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 92/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Prerequisites
l The Msuite client communicates with the Msuite server in the normal state.
l Ensure that all Msuite servers are started.
l
Ensure the NMS processes are ended.
l Ensure you have deleted the SNMP NBI instance.
Deploy Environment
l Log in to the Solaris or Linux OS as user nmsuser.
l Log in to the Windows OS as user Administrator.
l In a distributed system, you only need to log in to the NMS maintenance tool server of the
master server to perform this operation.
l In a high availability system, you only need to log in to the NMS maintenance tool server
of the primary site to perform this operation.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the Msuite client, click Deployment Package tab, check whether the instance count of SNMP
NBI deployment package is zero.
l If Instance Count is not zero, you need to deleted the SNMP NBI instance first.
l If Instance Count is zero, choose Deploy > Remove Component from the Main Menu.
The dialog box is displayed.
You cannot delete the components which are basic or have not installed. You cannot select them in the left
window.
Step 4 Click OK in the displayed dialog. The deleting of the component is started.
Step 5 Wait until the message the component is successfully removed is displayed. Click OK .
Step 6 View the deployment package list in the Deployment Package tab, the North-Bound SNMP
Interface deployment package not exist indicate that the operation is successful.
----End
Symptom
After theclient.
Monitor SNMP NBI is deployed, the SNMP Service process is not displayed on the System
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 93/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Possible Causes
The SNMP NBI is not licensed.
Procedure
Step 1 Check whether the license for the SNMP NBI has been obtained. If not, the SNMP service
process is not displayed on the System Monitor client. For details, see 4.5 Checking the
License.
Step 2 If there is a license for the SNMP NBI, redeploy the NBI or restart the U2000. Then check for
the SNMP Service process.
Step 3 If the SNMP Service process is not running, contact your Huawei engineers.
----End
Possible Causes
Port 9812 for configuring the SNMP NBI is occupied by other processes.
CAUTION
Do not use the default ports of the SNMP protocol (port 161 and port 162) to configure the
SNMP NBI, because these they are occupied by other processes.
Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the
iManager U2000 Planning Guide before you configure ports for the SNMP NBI.
Procedure
Step 1 Check whether other processes are using the port of the SNMP service.
Run the netstat -an command to view the service ports opened by the system.
l On the Solaris or Linux OS, run the netstat -an | grep port_number command to view the
status of a specified port.
For example, run the netstat -an | grep 6666 command to view the status of port 6666.
l In the Windows OS, run the netstat -an | find "port_number" command to view the status
of a specified port.
For example, run the netstat -an | find "6666" command to view the status of port 6666.
NOTE
If any router or firewall is located on the network between the U2000 and the OSS, you must check the
ports used by the U2000 and the OSS and ensure that these ports can be opened for normal communication.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 94/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Step 2 If the port is occupied by other processes, negotiate with OSS engineers to modify the port for
the SNMP NBI, or end the processes if they are not needed.
Step 3 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
Step 4 Select Third-party NMS in the General tab. Check whether the V3 user is blank. If it is blank,
input the correct value, then deploy the SNMP NBI.
----End
Symptom
The NMS user cannot connect to the SNMP NBI.
Possible Causes
l The SNMP service process is not started.
l As the following tables shows, the communication parameters of the OSS do not match
with those of the U2000.
l Write community
SNMPv3 l Receive Request from NMS address/port
l SNMP version
l User name
l Authentication password and encryption password
l Security model
l Authentication protocol and encryption protocol
l
The firewallreceive
the request blocksport
the communication
on the U2000. between the request transmit port on the OSS and
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 95/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Procedure
Step 1 Log in the client of U2000 System Monitor and check whether the SNMP Service process is
started.
l
If there is no SNMP Service process, see7.3.1 SNMP Service Process Is Not
Displayed.
l If the SNMP Service process cannot be started, see 7.3.2 SNMP Service Process Fails to
Be Started.
Step 2 If the SNMP Service process has been started, determine the communication parameters with
OSS engineers and redeploy the SNMP NBI.
Step 3 Ensure the communication between the request transmit port on the OSS and the request receive
port on the U2000 is not blocked by the firewall; otherwise they cannot communicate with each
other.
----End
Symptom
The OSS can receive alarms but cannot receive heartbeat information from the U2000.
Possible Causes
l The OSS is loaded with the U2000-T MIB that does not support heartbeat transmission.
l The heartbeat function is disabled when the SNMP NBI is deployed.
Procedure
Step 1 Log in to the client of the Msuite. For details, see 4.6.2 Logging In to the MSuite Client .
Step 2 On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.
----End
Symptom
The OSS cannot receive real-time alarms.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 96/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Possible Causes
l The following parameters are incorrect when the SNMP NBI is deployed.
– Send Trap address/port in SNMP Agent
Procedure
Step 1 After confirming the previous parameters with OSS engineers, log in to the Msuite MSuite client
and reconfigure the SNMP NBI based on the confirmation.
Step 2 Check whether the request transmit port on the OSS and the request receive port on the
U2000 are enabled on the firewall; otherwise they cannot communicate with each other.
----End
Symptom
The NMS/OSS can receive heartbeat and alarms, but active alarms cannot be acknowledged or
unacknowledged or cleared.
Possible Causes
l The alarm have converted to the history alarm.
l The dependent services are down, such as log service and fault service.
l Version mismatch of the MIB file.
– The U2000-T MIB cannot acknowledged or unacknowledged or cleared alarms.
– The MIB file that the NMS/OSS loaded is mismatch with the U2000.
Procedure
Step 1 Log in the client of U2000, browse the history alarms. View the serial number is exist. If the
serial number is exist, the alarm is converted to history alarm, then you cannot acknowledge,
unacknowledge and clear history alarms.
Step 2 Log in the client of U2000 System Monitor, view whether the log service and fault service are
running normally. If not started, please restart the processes.
Step 3 View whether the MIB file the U2000 loaded is correct.
1. Log in the client of Msuite.
2. On themenu.
main NMS MSuite client, choose NBI > Configure SNMP interface instance from the
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 97/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
3. Click Advanced, select MIB Frame. View whether the MIB is set to U2000 MIB. If the
MIB is set to U2000-T MIB, please modify to U2000 MIB. Then deploy the SNMP NBI
again.
Step 4 View whether the MIB file the NMS/OSS loaded is correct.
l If the MIB file is T2000-NETMANAGEMENT-MIB.mib, acknowledged or
unacknowledged or cleared alarms is not supported.
l If the MIB file is HW-IMAPV1NORTHBOUND-TRAP-MIB.mib or HW-
IMAPV2NORTHBOUND-TRAP-MIB.mib, please get the U2000 version
documentation iManager U2000 Northbound SNMP Interface MIB file from Huawei
technology engineer. This documentation is published in Huawei support website.
----End
Answer
The following operations are for Solaris. The operations in Linux or Windows are similar. The
environment variable for Windows is %IMAP_ROOT%.
CAUTION
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 98/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Step 7 Optional: Perform the following operations for the heartbeat notification trap to report
hwNmAgent instead of hwNmNorthboundKeepAlive:
1. Delete the KeepAliveVBOID configuration item from the $IMAP_ROOT/etc/conf/
snmp_agent_svc.xml and $IMAP_ROOT/nbi/snmp/engineering/server/etc/conf/
snmp_agent_svc.xml configuration files.
2. Delete the configuration item in the database and reload it.
# SettingTool -cmd delparam -path /imap/snmpagent/notify/transfer/
KeepAliveVBOID
# svc_adm -cmd reload
----End
Answer
The following operations are for Solaris. The operations in Linux or Windows are similar. The
environment variable for Windows is %IMAP_ROOT%.
CAUTION
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 99/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l For Solaris or Linux, log in to the OS of the U2000 server as the nmsuser user.
l For windows, log in to the OS of the U2000 server as the Administrator user.
<param name="VB22">GroupID</param>
<param name="VB23">MaintainAlmStatus</param>
<param name="AdditionalVB1">0</param>
<param name="AdditionalVB2">1</param>
<param name="AdditionalVB3">2</param>
<param name="AdditionalVB4">3</param>
<param name="AdditionalVB5">4</param>
<param name="AdditionalVB6">5</param>
<param name="AdditionalVB7">6</param>
<param name="AdditionalVB8">7</param>
</Mib1>
Step 7 Optional: Perform the following operations if the additional VBs are not needed.
1. Delete the AdditionalVB1 to AdditionalVB8 configuration item from the
$IMAP_ROOT/etc/conf/snmp_agent_svc.xml and $IMAP_ROOT/nbi/snmp/
engineering/server/etc/conf/snmp_agent_svc.xml configuration files.
2. Delete the configuration item in the database and reload it.
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB1
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB2
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB3
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB4
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB5
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB6
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB7
$ SettingTool -cmd delparam -path /imap/snmpagent/notify/transVB/Mib1/
AdditionalVB8
$ svc_adm -cmd reload
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 100/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Question
By default, the configuration item T2000Support is 1, then the SNMP NBI can report the
information of optical NE. C.4.1 Active Alarm Trap shows the sample of enable and disable
this item. How to configure the T2000Support item?
Answer
The following operations are for Solaris. The operations in Linux or Windows are similar. The
environment variable for Windows is %IMAP_ROOT%.
CAUTION
<param name="T2000Support">0</param>
----End
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 101/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Answer
The OSS can change the filter criteria in real time. For details, see 6.1.2 Changing Filter
Criteria.
Modify the first binary digital of filtercategory to 0. 0 indicates the SNMP NBI will report event
alarm, 1 indicates not. The default value is 1. For the following example, the SNMP NBI can
report event alarm, fault alarm and clear alarm, but cannot report acknowledge alarm,
unacknowledge alarm and change alarm.
<param name="filtercategory">000111</param>
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 102/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
This part introduces the relations between license and SNMP interface.
The U2000 license controls the software of SNMP interface in the following three dimensions:
l Interface function
l Technical domain
l Management capacity
The three dimensions depend on each other. The U2000 divides the license according to the
dimensions to dynamically control the SNMP software.
i t y
te a p a c
C
c
h
m e n t
n e
ic
n a g
a
l M a
d
om
a
in
Interface Function
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 103/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Dimension Meaning
On Solaris or Linux, view the license as user root. Use the text viewer to view the contents of
the $IMAP_ROOT/etc/conf/license/LIC_ONxxxxxxx.dat file.
On Windows, view the license as user administrator. Use the text viewer to view the contents
of the %IMAP_ROOT%\etc\conf\license\LIC_ONxxxxxxx.dat file.
Here each "X" represents an integer ranging from 0 to 9. Refer to Table A-2 for the details of
license control items.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 104/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
B Configuration Parameters
The U2000 can connect to the NMS/OSS after you correctly set general parameters by using the
Msuite. You can also set advanced parameters to customize the messages queried or reported
through the SNMP NBI.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 105/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. In the dialog box that is displayed, click SNMP Agent on the General tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 106/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
CAUTION
The trap-transmitting IP address and request-receiving IP address are both the U2000 server IP
address. Ensure that this IP address can be used for successful communication between the
U2000 and the OSS.
Refer to chapter "U2000 Port List" in the iManager U2000 Administrator Guide and the
iManager U2000 Planning Guide before you configure ports for the SNMP NBI. Before
configuring these ports, ensure that the specified ports are idle.
Do not use the default ports of the SNMP protocol (port 161 and port 162) to deploy the SNMP
NBI, because they are occupied by other processes.
Send Trap address IP addresses except 127.0.0.1 Specifies the IP address on the
Default: IP address of the SNMP agent for sending traps to
U2000 server the OSS.
On the U2000 with multiple
network interface cards (NICs),
set an IP address for successful
communication between the
U2000 and the OSS.
Port 1025~32767 Specifies the port for sending
Default: 6666 traps.
Recommended value:
1025~32767
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 107/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Security Level Without authentication and Specifies the security level of the
encryption, With authentication, SNMPv3 protocol.
Without encryption, With
authentication and encryption
Default: Without authentication
and encryption
Standard
l AES: Advanced Encryption
Standard
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Third-Party NMS in General tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 108/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
NOTE
The Receive Trap Address is not the IP address of the U2000 server.
Currently a maximum of 10 third-party NMSs are supported.
The same
use the SNMPv3
same user configured
authentication for different
and encryption third-party NMSs, for example, NMS 1 and NMS 2, must
passwords
When the U2000-T MIB is used, the SNMP NBI identifies OSSs by read or write community.
l If multiple OSSs use the same read or write community, only the first OSS gets the synchronized
results when any of the OSSs tries to synchronize data.
l It is recommended that each OSS uses a unique read or write community so that the OSS can get
correct synchronized results.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 109/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
CAUTION
To ensure the security of the U2000, passwords must be complex enough. For example, a
password must contain eight or more characters of two types. The allowed characters are digits,
letters, and special characters. Remember to change passwords regularly.
The password must meet the following requirements to safeguard your user account.
l Consists more than 8 characters.
l The password cannot be the user name or its reverse spelling.
l The password must consist of three of the following types of characters at least:
l Lower-case letters
l Upper-case letters
l Digits
l Special characters including ~ ! @ # $ % ^ & * ( ) - _ = + \ |[ { } ] ; : ' " , < . > / ? and
space
Port Default: 6666 Specifies the port of the third-party NMS for
1025~32767 receiving traps.
NOTE
l When the U2000 is interconnected with the OSS,
enter the port ID that is provided by the OSS.
l When the U2000 is not interconnected with the
OSS, the port ID cannot be left blank. In this case,
use the default port ID 6666.
Read/Write Default When the third-party NMS uses the SNMPv1 or
Community SNMPv2c protocol, the authentication control
l Read Community:
between the SNMP agent and the OSS is
Changeme_123
implemented through community information.
l Write Community:
The SNMP agent responds to operations
Changeme_123
(including querying, acknowledging,
You can also enter any unacknowledging, and clearing alarms) only
character string when the read and write communities are the same
consisting of 255 as those on the OSS; otherwise, operation
characters at most. requests are ignored.
V3 User Name Default: admin Specifies the user name used by the OSS to
Character string (20) communicate with the SNMP agent through the
SNMPv3 protocol.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 110/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
V3 The default password Indicates the password for authenticating the OSS
Authentication is left blank. when the OSS visits the SNMP agent.
Password
If the security level is set to With authentication,
Without encryption or Authentication and
Privacy, set encryption policy of the password.
V3 Privacy The default password Indicates the password for encrypting data when
Password is left blank. the OSS visits the SNMP agent.
If the security level is set to Authentication and
Privacy, set encryption policy of the password.
first place
binary modeof the
to 0value
. of AlarmCategoryFilter in
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 111/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
B.2.1 Heartbeat
The U2000 can periodically send heartbeat information to the OSS through the SNMP NBI.
Based on the heartbeat information, the OSS determines whether the communication is
successful. The heartbeat settings are applicable to the U2000 MIB only.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose Heartbeat on the Advanced tab.
Parameters
NOTE
Heartbeat Period Default: 60s Specifies the heartbeat period of the third-
3s~300s party NMS.
The reported
reported alarm
through thefield,
SNMP alsoNBI.
called bound variable (VB), specifies the alarm information to be
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 112/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose Alarm Field on the Advanced tab.
Parameters
CAUTION
NE Name hwNmNorthbou Indicates the name of the NE where an Octet string
ndNEName alarm is generated.
NE Type hwNmNorthbou Indicates the type of the NE where an alarm Octet string
ndNEType is generated.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 113/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Event Type hwNmNorthbou Indicates alarm type. For non-X.733- Octet string
ndEventType compliant alarms, options are as follows:
l Communication
l Environment
l Equipment
l Service
l Processing
l Unknown
For X.733-compliant alarms, options are as
follows:
l communicationsAlarm
l environmentalAlarm
l equipmentAlarm
l qualityofServiceAlarm
l processingErrorAlarm
l Unknown_EventType
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 114/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Alarm time hwNmNorthbou Indicates the time at which an alarm is Octet string
ndEventTime generated, cleared, acknowledged,
unacknowledged, or changed.
l If an alarm is generated, this parameter
indicates the time at which the alarm is
generated.
l If an alarm is cleared, this parameter
indicates the time at which the alarm is
cleared.
l If an alarm is acknowledged, this
parameter indicates the time at which
the alarm is acknowledged.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 115/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Alarm hwNmNorthbou Indicates ID, device type, and details of an Octet string
Details ndEventDetail alarm.
Type Flag hwNmNorthbou Indicates alarm type. Options are as Octet string
ndFaultFlag follows:
l Event: Indicates the event is generated.
l Fault: Indicates the alarm is generated.
l Recovery: Indicates the trap is alarm
recovery.
l Acknowledge: Indicates the alarm is
acknowledged.
l Unacknowledged: Indicates the alarm
is unacknowledged.
l Change: Indicates alarm is changed.
l UNKNOWN_EVENT_TYPE:
Unknown event type
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 116/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Trail Name hwNmNorthbou Indicates the name of the trail affected by Octet string
ndTrailName an alarm.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 117/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
maintenance
generated by state, therefore,
this kind of NEsthe
arealarms
engineering
alarms.
B.2.3 Notification
You can set the reported mode and the relevant parameters.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Notification in Advanced tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 118/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
WARNING
l Trap mode: A received alarm is reported immediately regardless of whether the OSS returns
a response to the previous alarm reporting.
l Inform mode: A received alarm is reported immediately after the OSS returns a response to
the previous alarm reporting or the retried times is excessed. In this mode, if the parameters
configured for the OSS are incorrect, the SNMP agent tries connecting to the OSS for many
times. This will occupy a large number of resources. As a result, the efficiency of the SNMP
agent is reduced. Therefore, exercise caution when you set this parameter to Inform.
l The SNMPv1 supports the Trap mode only.
Reporting Mode Default: Trap Mode Specifies the mode used by the SNMP agent
Trap Mode, Inform Mode for sending alarms to the OSS.
Support X733 Default: No Specifies whether traps use the event types
Alarm Yes, No and levels defined in X.733.
Yes indicates that the X.733 format is used.
No indicates that the X.733 format is not
used.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose Time Format on the Advanced tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 119/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
Parameter Value Description
s
Example:
l 2009/12/23 - 19:30:30,+08:00[0] (if the date is not in
DST).
l 2009/12/23 - 19:30:30 +08:00[3600] (if the date is in
DST of 1 hr). The DST value is in seconds.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 120/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Encoding Format in Advanced tab.
Parameters
Parameters Value Description
Alarm Default: UTF-8 There are two types of alarm coding
Character UTF-8, GBK as follows: UTF-8, GBK.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.On the Advanced tab, click Alarm Relativity Config.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 121/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
Parameter Value Description
s
Alarm Default: All All alarms: Queries and reports all alarms including the root
Relativity
Config alarms alarm and correlative alarms.
All alarms, Root Alarm: Queries and reports only the root alarm and
Root Alarm common alarms.
NOTE
The following two correlative alarms are involved by the location relationships between correlative alarms
and root alarms:
l NE-level correlative alarms: Correlative alarms and root alarms are generated on the same NE.
l Trail-based correlative alarms: Correlative alarms and root alarms are generated on different upstream
and downstream NEs connected by services.
After alarm correlation rules are enabled on the U2000, the NBIs report correlative alarms based on the
alarm correlation analysis results on the U2000 and different NBIs have different rules for reporting
correlative alarms. The SNMP NBI supports only trail-based correlative alarms.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 122/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu.On the Advanced tab, click Engineering Alarm.
Parameters
Parameters Value Description
Engineering Default: All alarms Specifies whether to report the
Alarm All alarms, Engineering Alarm engineering alarms.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Select Other Settings in Advanced tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 123/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
Parameters Value Description
Real-time Alarm Default: Specifies the cache for real-time alarms. Each NMS/
Cache Size 10000 OSS user is assigned with an independent cache.
0-50000 When the alarm generate rate is more than the alarm
reporting rate, the SNMP NBI will buffer the alarm
data in the cache.
Navigation Path
On the NMS MSuite client, choose NBI > Configure SNMP interface instance from the main
menu. Choose MIB Frame on the Advanced tab.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 124/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Parameters
CAUTION
This setting has a direct impact on the successful communication between the U2000 and the
OSS for alarm management. Confirm the MIB frame with the MIB frame on the OSS.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 125/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 126/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
C U2000 MIB
The U2000 MIB is used mainly in the management of a multi-domain network or upgrades of
network management systems (NMSs) such as the N2000 DMS and N2000 BMS.
HW-IMAPV2NORTHBOUND-TRAP-MIB.mib SMI-V2
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 127/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
For the function interface of U2000 MIB, see 6.1 U2000 MIB Subinterfaces.
For the structure and details of U2000 MIB, see iManager U2000 SNMP NBI MIB File.
NOTE
The iManager U2000 SNMP NBI MIB File is available on the Huawei technical support website. To obtain
this document, contact the local technical support engineers.
When the MIB frame set to U2000 MIB, the SNMP NBI will report the following alarm fields,
you can customize the alarm fields.
NE Name hwNmNorthbou Indicates the name of the NE where an Octet string
ndNEName alarm is generated.
NE Type hwNmNorthbou Indicates the type of the NE where an alarm Octet string
ndNEType is generated.
Object
instance hwNmNorthbou
ndObjectInstanc Indicates location information. Octet string
For example, Slot = 20. Port = 2 20-EFG2-2
e (PORT2)-MAC:1
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 128/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Event Type hwNmNorthbou Indicates alarm type. For non-X.733- Octet string
ndEventType compliant alarms, options are as follows:
l Communication
l Environment
l Equipment
l Service
l Processing
l Unknown
For X.733-compliant alarms, options are as
follows:
l communicationsAlarm
l environmentalAlarm
l equipmentAlarm
l qualityofServiceAlarm
l processingErrorAlarm
l Unknown_EventType
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 129/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Alarm time hwNmNorthbou Indicates the time at which an alarm is Octet string
ndEventTime generated, cleared, acknowledged,
unacknowledged, or changed.
l If an alarm is generated, this parameter
indicates the time at which the alarm is
generated.
l If an alarm is cleared, this parameter
indicates the time at which the alarm is
cleared.
l If an alarm is acknowledged, this
parameter indicates the time at which
the alarm is acknowledged.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 130/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Alarm hwNmNorthbou Indicates ID, device type, and details of an Octet string
Details ndEventDetail alarm.
Type Flag hwNmNorthbou Indicates alarm type. Options are as Octet string
ndFaultFlag follows:
l Event: Indicates the event is generated.
l Fault: Indicates the alarm is generated.
l Recovery: Indicates the trap is alarm
recovery.
l Acknowledge: Indicates the alarm is
acknowledged.
l Unacknowledged: Indicates the alarm
is unacknowledged.
l Change: Indicates alarm is changed.
l UNKNOWN_EVENT_TYPE:
Unknown event type
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 131/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Trail Name hwNmNorthbou Indicates the name of the trail affected by Octet string
ndTrailName an alarm.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 132/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
maintenance
generated by state, therefore,
this kind of NEsthe
arealarms
engineering
alarms.
Function
When alarms are generated on NEs or the U2000, the U2000 automatically sends this type of
traps to notify the OSS of real-time alarms through the SNMP NBI.
Trigger Condition
Alarms generated on NEs or the U2000 trigger the sending of active alarm notification traps
through the SNMP NBI.
Definition
Name Enterprise Type Description
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 133/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
l Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm
notification traps are automatically sent by the U2000 while active alarm report traps are responses to
the query of active alarms from the OSS.
l Additional VBs range from hwNmNorthboundsAdditionalVB1 to
hwNmNorthboundsAdditionalVB8. By default, the Additional VBs are not reported and you can not
use them. But the SNMP can report the additional VBs also. For detail, see 7.3.8 How to report
additional VBs alarm trap.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 134/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 135/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 136/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Function
After the OSS sends alarm query requests, the U2000 sends this type of traps to inform the OSS
that the synchronization starts.
Trigger Condition
The OSS triggers the alarm synchronization. For details, see 6.1.3 Synchronizing Alarms.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 137/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Definition
Name Enterprise Type Description
VB List
N/A
Function
After the OSS initiates the alarm synchronization, the U2000 sends this type of traps to report
required alarms on the U2000 to the OSS.
Trigger Condition
The OSS triggers the synchronization. For details, see 6.1.3 Synchronizing Alarms.
NOTE
Definition
Name Enterprise Type Description
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 138/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
l Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm
notification traps are automatically sent by the U2000 while active alarm report traps are responses to
the query of active alarms from the OSS.
l Additional VBs range from hwNmNorthboundsAdditionalVB1 to
hwNmNorthboundsAdditionalVB8. By default, the Additional VBs are not reported and you can not
use them. But the SNMP can report the additional VBs also. For detail, see 7.3.8 How to report
additional VBs alarm trap.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 139/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 140/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 141/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Function
The U2000 sends this type of traps to inform the OSS that the alarm synchronization completes.
Trigger Condition
Active alarm synchronization end traps are triggered when:
l All required alarms have been reported to the OSS in trap packets.
l The OSS stops the synchronization.
The OSS triggers the termination of synchronization. For details, see 6.1.3 Synchronizing
Alarms.
The OSS
on the performsU2000
designated the operation hwNmNorthboundEventSynchronizationCommandStop
in the following format:
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 142/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NMS IP:port
NOTE
Definition
Name Enterprise Type Description
VB List
In the following table, listed data types for interconnection using the SNMPv1 protocol. Most
of these data types are applicable to the SNMPv2c and SNMPv3 protocols. For any differences,
details will be described in brackets.
tail
Description
U2000
receivessends the KeepAlive
the trap, infobetween
the connection (heartbeat)
theto the NMS/OSS
NMS/OSS regularly
and the each period.
U2000 works. If the If the NMS
NMS/OSS
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 143/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
does not receive the trap in this period and the heartbeat is enabled, it indicates that the NMS/
OSS disconnects with the U2000.
NOTE
You can configure the heartbeat, for details, see B.2.1 Heartbeat.
Condition
The U2000 sends the keepAlive info (heartbeat) trap to the NMS/OSS regularly in the preset
period.
Trap Definition
Name ENTERPRISE Type Description
Field List
In the following table, by default, the field types are those used for the connection with SNMPv1.
For SNMPv2c or SNMPv3, the same data types will not be introduced again. Different data
types are remarked in brackets.
CAUTION
By default, the heartbeat notification trap reports the hwNMAgent field. You can make
modifications for the trap to report the hwNmNorthboundKeepAlive field. For details, see 7.3.7
How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive .
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 144/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 145/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
<param name="T2000Support">0</param>
13: Specific trap hwNmNorthboundEventInfo::hwNmNorthboundEventNotify #1
trap(v1) received from: 10.71.224.13 at 2011-12-27 16:19:58
Time stamp: 0 days 00h:05m:29s.09th
Agent address: 10.71.224.13 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.224.13
Enterprise: hwNmNorthboundEventInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventNotify, Module: HW-IMAPV1NORTHBOUND-TRAP-
MIB, Enterprise: hwNmNorthboundEventInfo
Bindings (19)
Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-3500)
Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX OSN 3500
Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) Slot=4 Port=1
TTP_TYPE=1 4-N1SL16-1(SDH-1)-SPI:1
Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication
Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2011/04/27 -
16:11:30
Binding #6: hwNmNorthboundProbableCause.0 *** (octets) ID:
1,DeviceType:0,\(1)The fiber jumper is not connected at the optical
interface of the board;\(2)The laser of the board on the opposite station
is shutdown;\(3)A fiber break occurs in the transm ...
Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical
Binding #8: hwNmNorthboundEventDetail.0 *** (octets) ID:1,DeviceType:
0,Loss of signal
Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)
Alarm Parameter(hex) 0x01 0x00 0x01 0x01 0x01
Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault
Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication
Binding #12: hwNmNorthboundDeviceIP.0 *** (ipaddr) 10.70.71.97
Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 85415
Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) ID:
1,DeviceType:0,
Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)
3145893.-1.4.1.1.1.-1.-1
Binding #16: hwNmNorthboundEventName.0 *** (octets) ID:1,DeviceType:
0,R_LOS
Binding #17: hwNmNorthboundReasonID.0 *** (int32) 1
Binding #18: hwNmNorthboundFaultID.0 *** (int32) 1
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 146/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
<param name="T2000Support">1</param>
21: Specific trap hwNmNorthboundEventInfo::hwNmNorthboundEventNotify #1
trap(v1) received from: 10.71.224.13 at 2011-4-27 16:25:24
Time stamp: 0 days 00h:02m:02s.27th
Agent address: 10.71.224.13 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.224.13
Enterprise: hwNmNorthboundEventInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventNotify, Module: HW-IMAPV1NORTHBOUND-TRAP-
MIB, Enterprise: hwNmNorthboundEventInfo
Bindings (19)
Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-3500)
Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX OSN 3500
Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) source=NE
(9-3500) location=4-N1SL16-1(SDH-1)-SPI:1
Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication
Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2011/04/27 -
16:11:30
Binding #6: hwNmNorthboundProbableCause.0 *** (octets) \(1)The fiber
jumper is not connected at the optical interface of the board;\(2)The
laser of the board on the opposite station is shutdown;\(3)A fiber break
occurs in the transmission line;\(4) T ...
Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical
Binding #8: hwNmNorthboundEventDetail.0 *** (octets) Loss of signal
Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)
Alarm Parameter(hex) 0x01 0x00 0x01 0x01 0x01
Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault
Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication
Binding #12: hwNmNorthboundDeviceIP.0 *** (ipaddr) 10.70.71.97
Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 85417
Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) (zero-
length)
Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)
3145893.-1.4.1.1.1.-1.-1
Binding #16: hwNmNorthboundEventName.0 *** (octets) R_LOS
Binding #17: hwNmNorthboundReasonID.0 *** (int32) 1
Binding
Binding #18:
#19: hwNmNorthboundFaultID.0 ******
hwNmNorthboundDeviceType.0 (int32) 1
(octets) 0
Binding #20: hwNmNorthboundTrailName.0 *** (octets) PWE3:2
Binding #21: hwNmNorthboundRootAlarm.0 *** (int32) 0
Binding #22: hwNmNorthboundGroupID.0 *** (int32) 268374017
Binding #23: hwNmNorthboundMaintainStatus.0 *** (int32) 0
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 147/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
15:56:45
Time stamp: 0 days 00h:06m:24s.69th
Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.88.151
Enterprise: hwNmNorthboundEventSynchronizationStart
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventSynchronizationStartNotify, Module: HW-
IMAPV1NORTHBOUND-TRAP-MIB, Enterprise:
hwNmNorthboundEventSynchronizationStart
Bindings (0)
None.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 148/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
hwNmNorthboundEventSynchronizationEnd::hwNmNorthboundEventSynchronization
EndNotify #11 trap(v1) received from: 10.71.88.151 at 2010-11-24 15:57:45
Time stamp: 0 days 00h:07m:25s.16th
Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.88.151
Enterprise: hwNmNorthboundEventSynchronizationEnd
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventSynchronizationEndNotify, Module: HW-
IMAPV1NORTHBOUND-TRAP-MIB, Enterprise:
hwNmNorthboundEventSynchronizationEnd
Bindings (2)
Binding #1: hwNmNorthboundEventSynchronizationEndStatus.0 *** (int32)
normalEnd(1)
Binding #2: hwNmNorthboundEventSynchronizationEndStatusDetail.0 ***
(octets) Sync End: Successfully queried all alarms!
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 149/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Binding
(octets) #2:
Sync hwNmNorthboundEventSynchronizationEndStatusDetail.0
Error: Query failed as Agent shutting down! ***
C.4.5 Heartbeat
The SNMP NBI sends the heartbeat trap to the NMS/OSS periodically. The NMS/OSS can check
the connection status by the heartbeat.
NOTE
Two OIDs are supported. For their configurations, see 7.3.7 How to configure the heartbeat notification trap
to hwNmNorthboundKeepAlive.
hwNmAgent (default)
795: Specific trap
hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap
(v1) received from: 10.71.88.151 at 2010-11-24 15:57:20
Time stamp: 0 days 00h:07m:00s.12th
Agent address: 10.71.88.151 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.73.96 Port: 8888 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.71.88.151
Enterprise: hwNmNorthboundEventKeepAliveInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventKeepAlive, Module: HW-IMAPV1NORTHBOUND-TRAP-
MIB, Enterprise: hwNmNorthboundEventKeepAliveInfo
Bindings (1)
Binding #1: hwNmAgent *** (octets) SNMP Agent
hwNmNorthboundKeepAlive (configurable-1.3.6.1.4.1.2011.2.15.1.7.2.1)
8: Specific trap
hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap
(v1) received from: 10.67.192.220 at 2012/6/26 11:19:13
Time stamp: 0 days 00h:00m:15s.04th
Agent address: 10.67.192.220 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.66.102.169 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.67.192.220
Enterprise: hwNmNorthboundEventKeepAliveInfo
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 150/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
hwNmNorthboundKeepAlive (configurable-1.3.6.1.4.1.2011.2.15.1.7.2.1.0)
3: Specific trap
hwNmNorthboundEventKeepAliveInfo::hwNmNorthboundEventKeepAlive #2 trap
(v1) received from: 10.78.219.70 at 2012/7/26 19:11:29
Time stamp: 0 days 00h:01m:45s.11th
Agent address: 10.78.219.70 Port: 6666 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.66.103.78 Port: 6666 Transport: IP/UDP
Community: Changeme_123
SNMPv1 agent address: 10.78.219.70
Enterprise: hwNmNorthboundEventKeepAliveInfo
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventKeepAlive, Module: HW-IMAPV1NORTHBOUND-TRAP-
MIB, Enterprise: hwNmNorthboundEventKeepAliveInfo
Bindings (1)
Binding #1: hwNmNorthboundKeepAlive.0 *** (octets) SNMP Agent
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 151/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
D U2000-T MIB
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 152/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
--- huawei(2011)
|--- products(2)
|--- netManagement(15)
|--- nmAgent(1)
|---- nmNorthboundEvent(7)
For the structure and details of U2000-T MIB, see iManager U2000 SNMP NBI MIB File .
NOTE
The iManager U2000 SNMP NBI MIB File is available on the Huawei technical support website. To obtain
this document, contact the local technical support engineers.
When the MIB frame set to U2000-T MIB, the SNMP NBI will report the following alarm
fields, you can customize the alarm fields.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 153/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 154/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
2005-10-14,17:41:04.0.
Alarm northboundRepor- Alarm severity. Octet string
Severity tAlarmPerceivedSe- Options are as follows:
verity
l Critical
l Major
l Minor
l Warning
l Cleared
l Indeterminate
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 155/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 156/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Function
When alarms are generated on NEs or the U2000, the U2000 sends this kind of traps to notify
the OSS of real-time alarms automatically through the SNMP NBI.
Trigger Condition
When alarms are generated on NEs or the U2000, active alarm report traps are triggered.
Definition
Name Enterprise Type Description
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm notification
traps are automatically sent by the U2000 while active alarm report traps are used as responses to OSS
queries.
l environmentalAlarm
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 157/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the probable alarm cause, for
larmProbableCause 2011.2.15. example, RAI.
1.7.3.5
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the alarm cause, for example,
larmSpecificPro- 2011.2.15. NE communication was lost.
blems 1.7.3.6
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 158/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the name of the subrack where
larmShelfName 2011.2.15. an alarm is generated.
1.7.3.16 (1)In the WDM or OTN domain, the NE
name is the name of an optical NE and
the subrack name is the name of the
subrack that belongs to the optical NE.
(2)In the SDH or other domains, the NE
name is the subrack name, for example,
NE350.
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the name of the board where an
larmBoardName 2011.2.15. alarm is generated, for example, PQ1.
1.7.3.17
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the port type, for example,
larmPortType 2011.2.15. SDH_TU.
1.7.3.18
northboundReportA-
larmPortNumber 1.3.6.1.4.1.
2011.2.15. Integer Indicates
1. the port number, for example,
1.7.3.19
northboundReportA- 1.3.6.1.4.1. Integer Indicates the alarm ID, for example, 93.
larmID 2011.2.15.
1.7.3.22
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 159/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the alarm name, for example,
larmName 2011.2.15. LP_RDI.
1.7.3.23
Trigger Condition
The OSS triggers the synchronization. For details, see 6.2.2 Synchronizing Alarms.
NOTE
Definition
Name Enterprise Type Description
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 160/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
VB List
N/A
Trigger Condition
The OSS triggers the synchronization. For details, see 6.2.2 Synchronizing Alarms.
Definition
Name Enterprise Type Description
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
Bound variables (VBs) are the same for active alarm notification and report traps. Active alarm notification
traps are automatically sent by the U2000 while active alarm report traps are used as responses to OSS
queries.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 161/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the probable alarm cause, for
larmProbableCause 2011.2.15. example, RAI.
1.7.3.5
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the alarm cause, for example,
larmSpecificPro- 2011.2.15. NE communication was lost.
blems 1.7.3.6
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 162/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the name of the rack where an
larmRackName 2011.2.15. alarm is generated.
1.7.3.15 The value is always 1.
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the name of the subrack where
larmShelfName 2011.2.15. an alarm is generated.
1.7.3.16 (1)In the WDM or OTN domain, the NE
name is the name of an optical NE and
the subrack name is the name of the
subrack that belongs to the optical NE.
(2)In the SDH or other domains, the NE
name is the subrack name, for example,
NE350.
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the name of the board where an
larmBoardName 2011.2.15. alarm is generated, for example, PQ1.
1.7.3.17
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the port type, for example,
larmPortType 2011.2.15. SDH_TU.
1.7.3.18
1.7.3.19
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the specific location of an
larmLocation 2011.2.15. alarm, for example, ne=590174/rack=1/
1.7.3.20 shelf=1/slot=5/domain=sdh/port=1/
highPath=1/lowPath=0/layer=5.
The value format for a PTN NE is a little
different, for example, ne=3145796/
rack=1/shelf=1/slot=4/domain=ptn/
type=physical/port=1/location1=260/
layer=15.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 163/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
northboundReportA- 1.3.6.1.4.1. Integer Indicates the alarm ID, for example, 93.
larmID 2011.2.15.
1.7.3.22
northboundReportA- 1.3.6.1.4.1. Octet string Indicates the alarm name, for example,
larmName 2011.2.15. LP_RDI.
1.7.3.23
Trigger Condition
Active alarm synchronization end traps are triggered when:
l All required alarms have been reported to the OSS in trap mode.
l The OSS stops the synchronization.
The OSS
Alarms. triggers the termination of synchronization. For details, see 6.2.2 Synchronizing
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 164/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Definition
Name Enterprise Type Description
VB List
In the following table, listed data types are for SNMPv1. Most of these data types are applicable
to SNMPv2c or SNMPv3. For any differences, details will be described in brackets.
NOTE
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 165/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
Bindings
Binding(36)
#1: northboundReportAlarmManagedObjectClass.0 *** (octets)
(zero-length)
Binding #2: northboundReportAlarmManagedObjectInstance.0 *** (octets)
iManager U2000
Binding #3: northboundReportAlarmEventType.0 *** (octets)
processingErrorAlarm
Binding #4: northboundReportAlarmEventTime.0 *** (octets)
2010-11-29,23:31:54.0
Binding #5: northboundReportAlarmProbableCause.0 *** (octets) When the
database usage is larger than the threshold for the critical severity, the
NMS generates this alarm. When the database usage is smaller than the
threshold for the critical severit ...
Binding #6: northboundReportAlarmSpecificProblems.0 *** (octets)
(zero-length)
Binding #7: northboundReportAlarmPerceivedSeverity.0 *** (octets)
Critical
Binding #8: northboundReportAlarmNotificationIdentifier.0 *** (int32)
20
Binding #9: northboundReportAlarmCorrelatedNotifications.0 ***
(int32) 20
Binding #10: northboundReportAlarmProposedRepairActions.0 ***
(octets) (zero-length)
Binding #11: northboundReportAlarmAdditionalText.0 *** (octets) (zero-
length)
Binding #12: northboundReportAlarmEmsName.0 *** (octets) iManager
U2000
Binding #13: northboundReportAlarmNEName.0 *** (octets) iManager
U2000
Binding #14: northboundReportAlarmDevLocation.0 *** (octets) (zero-
length)
Binding #15: northboundReportAlarmRackName.0 *** (octets) 1
Binding #16: northboundReportAlarmShelfName.0 *** (octets) (zero-
length)
Binding #17: northboundReportAlarmBoardName.0 *** (octets) (zero-
length)
Binding #18: northboundReportAlarmPortType.0 *** (octets) (zero-
length)
Binding #19: northboundReportAlarmPortNumber.0 *** (int32) 0
Binding #20: northboundReportAlarmLocation.0 *** (octets) EMS System
Binding #21: northboundReportAlarmOperationAffected.0 *** (int32) 0
Binding #22: northboundReportAlarmID.0 *** (int32) 103
Binding #23: northboundReportAlarmName.0 *** (octets) The Database
Usage Is Too High (Critical)
Binding #24: northboundReportAlarmIPAddress.0 *** (octets) (zero-
length)
Binding #25: northboundReportAlarmResourceID.0 *** (octets) (zero-
length)
Binding #26: northboundReportAlarmCleared.0 *** (int32) 0
Binding #27: northboundReportAlarmAdditionalVB1.0 *** (octets)
2010-11-29,23:31:54.0
Binding #28: northboundReportAlarmAdditionalVB2.0 *** (octets)
2010-11-29,23:31:54.0
Binding #29: northboundReportAlarmAdditionalVB3.0 *** (octets)
2010-11-29,23:31:54.0
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 166/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
2010-11-29,23:31:54.0
Binding #34: northboundReportAlarmAdditionalVB8.0 *** (octets)
2010-11-29,23:31:54.0
Binding #35: northboundReportAlarmAdditionalVB9.0 *** (octets)
2010-11-29,23:31:54.0
Binding #36: northboundReportAlarmAdditionalVB10.0 *** (octets)
2010-11-29,23:31:54.0
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 167/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
2
Binding #9: northboundReportAlarmCorrelatedNotifications.0 ***
(int32) 2
Binding #10: northboundReportAlarmProposedRepairActions.0 ***
(octets) (zero-length)
Binding #11: northboundReportAlarmAdditionalText.0 *** (octets) (zero-
length)
Binding #12: northboundReportAlarmEmsName.0 *** (octets) iManager
U2000
Binding #13: northboundReportAlarmNEName.0 *** (octets) iManager
U2000
Binding #14: northboundReportAlarmDevLocation.0 *** (octets) (zero-
length)
Binding #15: northboundReportAlarmRackName.0 *** (octets) 1
Binding #16: northboundReportAlarmShelfName.0 *** (octets) (zero-
length)
Binding #17: northboundReportAlarmBoardName.0 *** (octets) (zero-
length)
Binding #18: northboundReportAlarmPortType.0 *** (octets) (zero-
length)
Binding #19: northboundReportAlarmPortNumber.0 *** (int32) 0
Binding #20: northboundReportAlarmLocation.0 *** (octets) EMS System
Binding #21: northboundReportAlarmOperationAffected.0 *** (int32) 0
Binding #22: northboundReportAlarmID.0 *** (int32) 60002
Binding #23: northboundReportAlarmName.0 *** (octets) SFTP server
fault
Binding #24: northboundReportAlarmIPAddress.0 *** (octets) (zero-
length)
Binding #25: northboundReportAlarmResourceID.0 *** (octets) (zero-
length)
Binding #26: northboundReportAlarmCleared.0 *** (int32) 0
Binding #27: northboundReportAlarmAdditionalVB1.0 *** (octets)
2008-09-21,15:29:56.0
Binding #28: northboundReportAlarmAdditionalVB2.0 *** (octets)
2008-09-21,15:29:56.0
Binding #29: northboundReportAlarmAdditionalVB3.0 *** (octets)
2008-09-21,15:29:56.0
Binding #30: northboundReportAlarmAdditionalVB4.0 *** (octets)
2008-09-21,15:29:56.0
Binding #31: northboundReportAlarmAdditionalVB5.0 *** (octets)
2008-09-21,15:29:56.0
Binding #32: northboundReportAlarmAdditionalVB6.0 *** (octets)
2008-09-21,15:29:56.0
Binding #33: northboundReportAlarmAdditionalVB7.0 *** (octets)
2008-09-21,15:29:56.0
Binding #34: northboundReportAlarmAdditionalVB8.0 *** (octets)
2008-09-21,15:29:56.0
Binding #35: northboundReportAlarmAdditionalVB9.0 *** (octets)
2008-09-21,15:29:56.0
Binding #36: northboundReportAlarmAdditionalVB10.0 *** (octets)
2008-09-21,15:29:56.0
Active
to alarm
the OSS orsynchronization end traps
the OSS automatically are triggered
stops when all required alarms have been reported
the synchronization.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 168/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 169/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
This appendix describes service ports of the Northbound Interface and how to query the service
ports.
E.2 Port Used Between the U2000 Server and the OSS
This topic describes the port used between the U2000 server and the OSS.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 170/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
l The service ports used by the NMS should not be closed. Run the following command to
view the system service ports:
netstat -an
l If there are routers or firewalls between the source and the sink, check all ports used by the
source and the sink. Make sure that these ports can be normally turned up to support the
communication between the source and sink.
E.2 Port Used Between the U2000 Server and the OSS
This topic describes the port used between the U2000 server and the OSS.
If a firewall is deployed between the U2000 server and the OSS, ensure that any port on the OSS
can set up connections with ports on the U2000 through the firewall. For ports used by the U2000,
see U2000 Communication Port Matrix.
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 171/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
F Equipment Supported
Transport Equipment
Table F-1 Transport equipment supported by the SNMP NBI
Featu MST Hybri WD OTN Hybri TDM Packe PTN Mari
re P d M d RTN t RTN ne
MST RTN
P (TD
M
Featu
re)
Alarm √ √ √ √ √ √ √ √ ×
NOTE
Router Equipment
Alarm √ √ √ √ √ √
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 172/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
NOTE
Access Equipment
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 173/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
E
EMS Element Management System
I
IP Internet Protocol
M
MC Monitor Center
N
NBI Northbound Interface
NE Network Element
NMC Network Management Center
NMS Network Management Station, namely the NMS/OSS.
T
TCP Transmission Control Protocol
TMN Telecommunication Management Network
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 174/175
7/21/2019 u2000 Snmp Nbi User Guide-(v100r006c02_05)
http://slidepdf.com/reader/full/u2000-snmp-nbi-user-guide-v100r006c0205 175/175