100% found this document useful (2 votes)

720 views177 pages

U2000 SNMP NBI User Guide (V200R015C60)

U2000 SNMP NBI User Guide ( V200R015C60 )

Uploaded by

Michał Buźniak

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

100% found this document useful (2 votes)

720 views177 pages

U2000 SNMP NBI User Guide (V200R015C60)

U2000 SNMP NBI User Guide ( V200R015C60 )

Uploaded by

Michał Buźniak

We take content rights seriously. If you suspect this is your content, claim it here.

Available Formats

Download as PDF, TXT or read online on Scribd

You are on page 1/ 177

iManager U2000 Unified Network Management

System
V200R015C60

SNMP NBI User Guide

Issue 01
Date 2016-01-15

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.

Trademarks and Permissions

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.

Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China

Website: http://www.huawei.com
Email: support@huawei.com

Issue 01 (2016-01-15) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide About This Document

About This Document

Related Versions
The following table lists the product versions related to this document.

Product Name Version

iManager U2000 V200R015C60

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.

This document is intended for:

l Network Planning Engineer

l Application Developer
l Installation and Commissioning Engineer
l Data Configuration Engineer
l System Maintenance Engineer

Symbol Conventions
The symbols that may be found in this document are defined as follows.

Symbol Description

Indicates an imminently hazardous situation

which, if not avoided, will result in death or
serious injury.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential ii

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide About This Document

Symbol Description

Indicates a potentially hazardous situation

which, if not avoided, could result in death
or serious injury.

Indicates a potentially hazardous situation

which, if not avoided, may result in minor
or moderate injury.

Indicates a potentially hazardous situation

which, if not avoided, could result in
equipment damage, data loss, performance
deterioration, or unanticipated results.
NOTICE is used to address practices not
related to personal injury.

Calls attention to important information,

best practices and tips.
NOTE is used to address information not
related to personal injury, equipment
damage, and environment deterioration.

Command Conventions
The command conventions that may be found in this document are defined as follows.

Convention Description

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.

[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.

{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential iii

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide About This Document

GUI Conventions
The GUI conventions that may be found in this document are defined as follows.

Convention Description

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.

> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.

Change History
Updates between document issues are cumulative. Therefore, the latest document issue
contains all updates made in previous issues.

Changes in Issue 01 (2016-01-15) Based on Product Version V200R015C60

Initial release.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential iv

Contents

About This Document.....................................................................................................................ii

1 Preview............................................................................................................................................ 1
1.1 Overview........................................................................................................................................................................ 2
1.2 Reading Guide................................................................................................................................................................ 2

2 Overview......................................................................................................................................... 4
2.1 Introduction.................................................................................................................................................................... 5
2.2 Network Position............................................................................................................................................................ 5
2.3 Function.......................................................................................................................................................................... 6
2.3.1 U2000 MIB..................................................................................................................................................................6
2.3.2 U2000-T MIB.............................................................................................................................................................. 8
2.4 Security Mechanism....................................................................................................................................................... 9
2.5 Standard Compliance....................................................................................................................................................11
2.6 Performance Indicators.................................................................................................................................................12

3 Introduction to the SNMP NBI................................................................................................. 13

3.1 Overview...................................................................................................................................................................... 14
3.2 Network Management Framework............................................................................................................................... 14
3.3 SNMP Message Structure.............................................................................................................................................15
3.4 MIB...............................................................................................................................................................................16
3.5 SNMP Packet Operation Process................................................................................................................................. 17
3.6 Version Evolution......................................................................................................................................................... 18

4 Preparing for a Deployment...................................................................................................... 20

4.1 Important Notes............................................................................................................................................................ 21
4.2 Collecting Integration Parameters................................................................................................................................ 22

5 Deploying and Configuring the SNMP NBI......................................................................... 25

5.1 Overview...................................................................................................................................................................... 26
5.2 Configuration Requirements.........................................................................................................................................27
5.3 Flow of Deploying the SNMP NBI.............................................................................................................................. 27
5.4 Checking the License....................................................................................................................................................28
5.5 Logging in to NBI Config Tools...................................................................................................................................29
5.6 Configuring the SNMP NBI......................................................................................................................................... 31
5.7 Testing the SNMP NBI.................................................................................................................................................39

Issue 01 (2016-01-15) Huawei Proprietary and Confidential v

5.7.1 U2000 MIB................................................................................................................................................................39

5.7.2 U2000-T MIB............................................................................................................................................................ 40
5.8 Configuration Sample...................................................................................................................................................40
5.8.1 Deploying the SNMPv1 NBI.....................................................................................................................................40
5.8.2 Deploying the SNMPv3 NBI.....................................................................................................................................43

6 Configuring the SNMP NBI on the OSS................................................................................ 47

6.1 Configuring the SNMPv1 or SNMPv2c NBI............................................................................................................... 48
6.2 Configuring the SNMPv3 NBI..................................................................................................................................... 49

7 Calling the SNMP NBI............................................................................................................... 52

7.1 U2000 MIB Subinterfaces............................................................................................................................................ 53
7.1.1 Reporting Real-Time Alarms.....................................................................................................................................53
7.1.2 Changing Filter Criteria.............................................................................................................................................53
7.1.3 Synchronizing Alarms............................................................................................................................................... 56
7.1.4 Acknowledging Alarms............................................................................................................................................. 59
7.1.5 Unacknowledging Alarms......................................................................................................................................... 62
7.1.6 Clearing Alarms.........................................................................................................................................................64
7.1.7 Reporting Alarm Acknowledging Status...................................................................................................................66
7.1.8 Reporting Alarm Clearing Status.............................................................................................................................. 67
7.2 U2000-T MIB Subinterfaces........................................................................................................................................ 68
7.2.1 Reporting Real-Time Alarms.....................................................................................................................................68
7.2.2 Synchronizing Alarms............................................................................................................................................... 68

8 Maintaining the SNMP NBI......................................................................................................72

8.1 Maintenance Description.............................................................................................................................................. 73
8.2 Deleting and Disabling an SNMP Interface................................................................................................................. 73
8.2.1 Logging In to the System Monitor Client..................................................................................................................73
8.2.2 Stopping the SNMP NBI........................................................................................................................................... 74
8.2.3 Disabling the SNMP NBI.......................................................................................................................................... 75
8.2.4 Restarting the SNMP NBI......................................................................................................................................... 77
8.3 Faults and Solutions......................................................................................................................................................78
8.3.1 SNMP Service Process Is Not Displayed.................................................................................................................. 79
8.3.2 SNMP Service Process Fails to Be Started............................................................................................................... 79
8.3.3 NMS User Cannot Connect to the SNMP NBI......................................................................................................... 80
8.3.4 The OSS Cannot Receive Heartbeat Information......................................................................................................81
8.3.5 OSS Cannot Receive Real-Time Alarms...................................................................................................................82
8.3.6 Acknowledge or Un-acknowledge or Clear Alarms Fails.........................................................................................82
8.3.7 How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive................................................83
8.3.8 How to configure T2000Support item..................................................................................................................... 84
8.3.9 How to report the event alarm................................................................................................................................... 84
8.3.10 How to Disable Password Complexity Checks for Read and Write Communities................................................. 85
8.3.11 How to Configure SupportOldGroupID for MxUs.............................................................................................. 85

9 Replacing the Certificate of the NBI Config Tools...............................................................87

Issue 01 (2016-01-15) Huawei Proprietary and Confidential vi

10 Revoking the Certificate of the NBI Config Tools............................................................. 90

A Relations Between License and SNMP Interface.................................................................92
B Configuration Parameters......................................................................................................... 95
B.1 General Parameters...................................................................................................................................................... 96
B.2 Advanced Configuration.............................................................................................................................................. 98
B.3 Third-Party NMS....................................................................................................................................................... 109

C U2000 MIB.................................................................................................................................. 113

C.1 MIB Description.........................................................................................................................................................114
C.2 Alarm Fields Reported By the U2000 MIB............................................................................................................... 114
C.3 U2000 MIB Trap........................................................................................................................................................123
C.3.1 Active Alarm Notification Trap.............................................................................................................................. 123
C.3.2 Active Alarm Synchronization Start Trap...............................................................................................................127
C.3.3 Active Alarm Report Trap...................................................................................................................................... 128
C.3.4 Active Alarm Synchronization End Trap................................................................................................................132
C.3.5 KeepAlive Info (Heartbeat) Trap............................................................................................................................ 134
C.4 U2000 MIB Trap Sample...........................................................................................................................................135
C.4.1 Active Alarm Trap.................................................................................................................................................. 135
C.4.2 Active Alarm Synchronization Start Trap...............................................................................................................138
C.4.3 Active Alarm Synchronization Result Trap............................................................................................................138
C.4.4 Active Alarm Synchronization End Trap................................................................................................................139
C.4.5 Heartbeat................................................................................................................................................................. 140

D U2000-T MIB............................................................................................................................. 142

D.1 MIB Description........................................................................................................................................................ 143
D.2 Reported Alarm Field by U2000-T MIB................................................................................................................... 143
D.3 U2000-T MIB Trap....................................................................................................................................................146
D.3.1 Active Alarm Notification Trap..............................................................................................................................147
D.3.2 Active Alarm Synchronization Start Trap.............................................................................................................. 150
D.3.3 Active Alarm Report Trap...................................................................................................................................... 151
D.3.4 Active Alarm Synchronization End Trap............................................................................................................... 154
D.4 U2000-T MIB Trap Sample.......................................................................................................................................155
D.4.1 Active Alarm Trap.................................................................................................................................................. 155
D.4.2 Active Alarm Synchronization Start Trap.............................................................................................................. 157
D.4.3 Active Alarm Synchronization Result Trap............................................................................................................157
D.4.4 Active Alarm Synchronization End Trap............................................................................................................... 158

E Service Ports Description........................................................................................................ 160

E.1 Notes and Precautions................................................................................................................................................ 161
E.2 Port Used Between the U2000 Server and the OSS...................................................................................................161

F Setting an Alarm or Event Northbound Filtering Rule..................................................... 162

G Equipment Supported............................................................................................................. 165

Issue 01 (2016-01-15) Huawei Proprietary and Confidential vii

H Acronyms and Abbreviations................................................................................................ 167

Issue 01 (2016-01-15) Huawei Proprietary and Confidential viii

1 Preview

About This Chapter

The preview describes main contents of each chapter and provides recommended chapters for
different readers.

1.1 Overview
The overview describes main contents of each chapter.
1.2 Reading Guide
This reading guide provides recommended chapters for different readers.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 1

1.1 Overview
The overview describes main contents of each chapter.

Chapter Description

2 Overview This chapter describes the network position, functions,

security mechanism, and standard compliance of the
U2000 SNMP NBI.

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.

5 Deploying and This chapter describes the methods for deploying and
Configuring the SNMP NBI configuring the SNMP NBI.

6 Configuring the SNMP This chapter describes how the OSS connects to the
NBI on the OSS U2000 through the SNMP NBI when different protocol
versions are used.

7 Calling the SNMP NBI This chapter describes how the OSS manages alarms on
the U2000 through the SNMP NBI.

8 Maintaining the SNMP This chapter describes the routine maintenance and FAQs
NBI of the SNMP NBI.

A Relations Between This appendix describes license control items of the

License and SNMP SNMP NBI.
Interface

B Configuration Parameters This appendix describes parameters and their meanings

for configuring the SNMP NBI.

C U2000 MIB This appendix describes U2000 MIB details, including

U2000 MIB node descriptions, alarm fields, traps, and
trap examples.

A Relations Between This appendix describes U2000-T MIB details, including

License and SNMP U2000-T MIB node descriptions, alarm fields, traps, and
Interface trap examples.

E Service Ports Description This appendix describes service ports used by the SNMP
NBI.

H Acronyms and This appendix describes terms, acronyms and

Abbreviations abbreviations used in the document.

1.2 Reading Guide

This reading guide provides recommended chapters for different readers.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 2

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 and complies with SMIv1, which
supports upgrades of original transport NMSs and can manage only transport devices.

Intended Purpose Recommended Chapter

Audience

Network Design, plan, and optimize 2 Overview, 3 Introduction to the

Planning networks. They need to know SNMP NBI, A Relations Between
Engineer working principles, network License and SNMP Interface, B
positions, and interface parameters Configuration Parameters, and E
(such as IP address and ports) of the Service Ports Description
SNMP NBI.

Application Develop the OSS and programs for 2 Overview, 3 Introduction to the
Developer interconnecting with the SNMP SNMP NBI, 5 Deploying and
NBI. They need to know basic Configuring the SNMP NBI, 6
principles, functions, MIB Configuring the SNMP NBI on
structures, and parameter definitions the OSS, 7 Calling the SNMP
of the SNMP NBI. NBI, B 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 Chapters 5, 6, and 7, and 6, and
and its connection with the OSS. They appendixes B and D
Commissioni do not need to know basic concepts Focus on 5 Deploying and
ng Engineer or principles of the SNMP NBI. Configuring the SNMP NBI.
Data Complete SNMP NBI deployment
Configuratio and configuration by referring to
n Engineer the flowchart and procedures.
5 Deploying and Configuring the
SNMP NBI, 6 Configuring the
SNMP NBI on the OSS, 7 Calling
the SNMP NBI, B Configuration
Parameters, andE Service Ports
Description

System Maintain the SNMP NBI and 2 Overview, 3 Introduction to the

Maintenance diagnose SNMP NBI faults. They SNMP NBI, 8 Maintaining the
Engineer need to know working principles SNMP NBI, B Configuration
and parameters of the SNMP NBI. Parameters, B Configuration
Parameters, andE Service Ports
Description

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 3

2 Overview

About This Chapter

iManager U2000 unified network management system (hereinafter referred to as U2000)

provide the SNMP NBI to the NMS/OSS to manage the alarms.

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.2 Network Position
The SNMP NBI is deployed between the OSS and the U2000; it establishes transmission
channels for alarm information between these two systems.
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.
2.4 Security Mechanism
The security mechanism used by the SNMP NBI is also the security mechanism of the SNMP
protocol. Any access to the SNMP NBI must be authenticated by the security mechanism of
the specific SNMP version (SNMPv1, SNMPv2c, and SNMPv3).
2.5 Standard Compliance
The SNMP NBI was developed based on the SNMP protocol.
2.6 Performance Indicators
The OSS manages alarms on the U2000 through the SNMP NBI. Performance indicators for
the SNMP NBI include maximum number of concurrent NMS connections, alarm forwarding
efficiency, alarm forwarding delay, and SNMP request response delay.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 4

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.

2.2 Network Position

The SNMP NBI is deployed between the OSS and the U2000; it establishes transmission
channels for alarm information between these two systems.
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.
Figure 2-1 shows the position of the SNMP NBI in a network.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 5

Figure 2-1 Position of the SNMP NBI in a network

OSS

Get/Set SNMP Trap

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.

U2000: iManager U2000 unified network management system, is the equipment

management system developed by Huawei. It is also a major future-
oriented network management solution that provides powerful element
management and network management functions.

NE: Network Element

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.

2.3.1 U2000 MIB

The U2000 MIB is used to manage transport, access, and datacom NEs or manage multi-
domain NEs. When loaded with the U2000 MIB, the SNMP NBI supports automatic alarm
reporting, synchronizing, clearing, acknowledging, and unacknowledging. Alarm

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 6

synchronizing is to query active alarms and report alarm acknowledgement and clearance
status.

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.

For details on trap messages, see C.3 U2000 MIB Trap.

Function Description

Subscribi Subscribes alarms by alarm severity and alarm category. You can set the
ng alarms severity and category when deploying the SNMP NBI.
Sets the alarm field or variable binding (VB).

Reporting Reports alarms from NEs or the U2000.

alarms

Reporting Reports heartbeat and sets the heartbeat period.

heartbeat

Reporting Reports the alarm acknowledgement status.

alarm
acknowle
dgement
status

Reporting Reports the alarm clearance status.

alarm
clearance
status

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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 7

l Clearing alarms

NOTE

Ensure that the OSS is connected to the SNMP NBI properly before the query function is enabled.

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 7.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
criteria are 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.

Acknowledging/ Acknowledges or unacknowledges current alarms on the U2000

Unacknowledging based on alarm serial numbers (SNs).
alarms

Clearing alarms Clears alarms on the U2000 based on alarm SNs.

2.3.2 U2000-T MIB

The U2000-T MIB is used to be compatible with upgrades of transport NMSs. It is used to
manage only transport NEs. When the U2000-T MIB is loaded, the SNMP NBI supports
automatic alarm reporting and synchronizing. Synchronizing alarms is to query active alarms.

U2000
At the U2000 side, the primary function is automatic alarm reporting.

NOTE

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 8

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.

Function Description

Subscribi Subscribes alarms by alarm severity and alarm category. You can set the
ng alarms severity and category when deploying the SNMP NBI.

Reporting Reports alarms from NEs or the U2000.

alarms

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.

For details on alarm synchronization, see 7.2.2 Synchronizing Alarms.

For details on traps, see D.3 U2000-T MIB Trap.

Function Description

Querying Reports all alarms by default. You can stop alarm synchronization using the
all Set operation.
current
alarms

Querying Reports alarms by alarm severity and category. The filter criteria are specified
alarms by during alarm subscription.
criteria

2.4 Security Mechanism

The security mechanism used by the SNMP NBI is also the security mechanism of the SNMP
protocol. Any access to the SNMP NBI must be authenticated by the security mechanism of
the specific SNMP version (SNMPv1, SNMPv2c, and SNMPv3).

Figure 2-2 shows that SNMPv1 and SNMPv2c use the community-based security
mechanism, while SNMPv3 uses the user-based security mechanism.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 9

Figure 2-2 Security mechanism

NMS

v1/v2c use v3 uses user

community name based security
based security mechanism
mechanism

SNMP alarm northbound interface

SNMPv1 and SNMPv2

The security mechanism of SNMPv1 and SNMPv2c is community-based: the NMS
authenticates NEs based on the community name list and the agent does not check the validity
of the community name. SNMP packets are transferred without encryption. Therefore,
authentication security and confidentiality are not well guaranteed.

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

SNMPv1 does not support the inform mode.

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:

l Data integrity check

The data cannot be modified in an unauthorized manner. Any changes in the data
sequence are limited to the allowed extent.
l Data origin authentication
SNMPv3 authenticates users from whom received packets are sent rather than
applications that generate these packets.
l Data confidentiality check
When the NMS or agent receives a packet, it checks when the packet was generated. If
the interval between the creation time and the system time exceeds the preset time range,
this packet will be discarded. This check prevents packets from being maliciously
modified and malicious packets from being received.

In access control, the NMS performs security checks on managed objects (MOs) based on
SNMPv3.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 10

Security Level
Table 2-1 shows security levels supported by the SNMP versions.

Table 2-1 Security Level

Version Security Level Authenticatio Data Description

n Encryption

v1 Without Community None Uses only

authentication community
and encryption names for
access
authentication.

v2c Without Community None Uses only

authentication community
and encryption names for
access
authentication.

v3 Without User name None Uses only user

authentication names for
and encryption access
authentication.

v3 With MD5 or SHA None Uses MD5 or

authentication SHA
and without algorithms for
encryption authentication.

v3 With MD5 or SHA AES or DES Uses MD5 or

authentication SHA
and encryption algorithms for
authentication;
AES or DES
algorithms for
data encryption.

NOTE

The following rules are applicable to SNMPv3:

l You can set a different user name, authentication password, and encryption password from others.
l You can select any of the listed security levels, authentication algorithms, and encryption algorithms.

2.5 Standard Compliance

The SNMP NBI was developed based on the SNMP protocol.

Currently, the SNMP NBI complies with the following three SNMP protocol versions:

l SNMPv1: the first release version. For details, see RFC1157.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 11

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.

2.6 Performance Indicators

The OSS manages alarms on the U2000 through the SNMP NBI. Performance indicators for
the SNMP NBI include maximum number of concurrent NMS connections, alarm forwarding
efficiency, alarm forwarding delay, and SNMP request response delay.
Table 2-2 lists the performance indicators for the SNMP NBI.

Table 2-2 Performance Indicators for the SNMP NBI

Indicator Description

Maximum number of concurrent NMS 10

connections

Alarm forwarding efficiency No less than 60 alarms per second (for three
NMS connections)

Alarm forwarding delay Less than 10 seconds (three NMS

connections)

SNMP request response delay Less than 5 seconds (CPU usage is less than
50%)

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 12

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

3 Introduction to the SNMP NBI

About This Chapter

This topic describes the working principles of the SNMP NBI. For details on the SNMP
protocol, see the relevant protocol documents.

3.1 Overview
SNMP is one of the widely applied NMS protocols in the TCP/IP network.
3.2 Network Management Framework
The Simple Network Management Protocol (SNMP) is a set of protocols and standards. It
provides channels for the OSS to collect network management data from network equipment
and for network equipment to report problems and errors to the OSS.
3.3 SNMP Message Structure
The SNMP message structure also refers to protocol data units (PDUs) or SNMP packet
types.
3.4 MIB
MIB is a key part of the SNMP network management framework.
3.5 SNMP Packet Operation Process
This topic uses the SNMPv1 as an example to introduce the operation process of SNMP
packet.
3.6 Version Evolution
Currently there are three SNMP versions: SNMPv1, SNMPv2c, and SNMPv3, all of which
are supported by the SNMP NBI.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 13

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

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:
l To transmit the management information between two nodes.
l To help the manager to search and modify the information, and locate faults at any node
in the network.
l To help the manager to diagnose the faults, configure the capacity, and generate reports.
The features of the SNMP are as follows:
l Uses the polling mechanism and provides a basic function set.
l Fits small, fast and cost effective network.

3.2 Network Management Framework

The Simple Network Management Protocol (SNMP) is a set of protocols and standards. It
provides channels for the OSS to collect network management data from network equipment
and for network equipment to report problems and errors to the OSS.
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.

Figure 3-1 Network management framework

SNMP MIB
NMS Agent

Module1 Module2 Module3

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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 14

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

Processes that run on NEs.

The SNMP agent performs the following operations:
Receive, parse, and authenticate query packets from the NMS.
Search the MIB tree, call other modules for operation, and obtain responses.
Construct response packets and send them to the NMS.
Send traps to the NMS if urgent.
l MIB
A type of database that stores NE management information and responds to management
requests, such as the query and setting requests, issued from the NMS through the SNMP
agent.
The agent queries the MIB for required operations.
l SNMP
An application-layer protocol carried over UDP in the TCP/IP structure.
Exchanges management information between the NMS and agents.
Figure 3-2 shows the position of SNMP in the TCP/IP family.

Figure 3-2 Position of SNMP

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.

3.3 SNMP Message Structure

The SNMP message structure also refers to protocol data units (PDUs) or SNMP packet
types.
PDUs are used for communication between the NMS and agents. Figure 3-3 shows five
PDUs.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 15

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

Figure 3-3 SNMP PDUs

GetNextRequest
GetRequest
NMS SetRequest Agent

GetResponse
Trap

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 16

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

Figure 3-4 MIB tree

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.

3.5 SNMP Packet Operation Process

This topic uses the SNMPv1 as an example to introduce the operation process of SNMP
packet.
The agent on the managed node receives a request packet from the NMS through UDP port.
U2000 use 9812 by default.
The agent treats the received packet as follows:
1. Decoding the packet based on basic encoding rules of ASN.1 and representing it in an
internal data structure
The agent discards the packet if some errors cause the decoding failure.
2. Checking the SNMP version number contained in the packet
The agent fetches the version number from the packet and compares it with the version
that it supports. If they are inconsistent, the agent discards the packet.
3. Checking the community name contained in the packet
The community name is inserted by the NMS. If the community name is not the
supported one, the agent discards the packet. A trap packet is returned to the NMS at the
same time. SNMPv1 provides weak security measures, which are enhanced in SNMPv3.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 17

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

4. Fetching the PDU from the authenticated ASN.1 object

If the operation fails, the agent discards the packet.
5. Handling the PDU
The agent handles the PDU according to its type. It searches the MIB to find the MO
matching the variable, and then obtains the value of the variable from the module. After
that, the agent generates the response packet, encodes it and returns it to the NMS.
6. The NMS performs the same operations as the agent, and displays the final result.

3.6 Version Evolution

Currently there are three SNMP versions: SNMPv1, SNMPv2c, and SNMPv3, all of which
are supported by the SNMP NBI.

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 18

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 3 Introduction to the SNMP NBI

SNMPv3
SNMPv3 inherits all functions in SNMPv2 and provides the following new features:
l User-based security model
l SNMPv3 supports all security levels as follows:
Without authentication and encryption
With authentication and without encryption
With authentication and encryption
The authentication supports MD5 and SHA algorithms and the encryption supports DES
and AES algorithms.
NOTE

The OSS must get the SNMPv3 information from the U2000 administrator, including security levels,
user names, authentication passwords, and encryption passwords.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 19

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 4 Preparing for a Deployment

4 Preparing for a Deployment

About This Chapter

Before deploying the SNMP NBI, you need to collect related configuration data. Modifying
some configuration items may require the restart of the U2000. Therefore, to prevent service
interruption, you need to apply for modifications in advance.

4.1 Important Notes

This topic describes the important notes for deploying and configuring the SNMP NBI.
4.2 Collecting Integration Parameters
Integration parameters must be collected from OSS O&M engineers and confirmed before the
SNMP NBI is deployed to ensure that the input parameters are correct; otherwise, the OSS
cannot receive alarms from or connects to the U2000.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 20

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 4 Preparing for a Deployment

4.1 Important Notes

This topic describes the important notes for deploying and configuring the SNMP NBI.
Deploying and configuring the SNMP NBI may affect the OSS and other components of the
U2000. Modifying configuration items may also depend on the U2000 components.
Therefore, confirm whether the configuration items to be modified will bring such kind of
impact and submit a request to the customer for approval before deploying and configuring
the SNMP NBI.

Item Impact on U2000 Description

Alarm Field The number of alarm field You need check the number
will be changed if you have of alarm field with OSS,
modified this configuration then set this item.
item. The OSS maybe can
not parse the alarm
correctly.

Encoding Format The encoding format of You must check the

alarm reported by the SNMP character set of the OSS,
NBI will be changed if you then set the correct value.
have modified this Current version support two
configuration item. The OSS character set, such as UTF-8
maybe can not parse the and GBK. The character set
alarm correctly. of SNMP and OSS must be
the same. If the character set
of SNMP is different from
the OSS, the OSS maybe
can not parse the
information from SNMP.

MIB Frame The OSS maybe can not U2000-T MIB and U2000
parse the alarm correctly if MIB are both supported.
you have modified this You need to check the MIB
configuration item. type that the OSS used. If it
is T2000-
NETMANAGEMENT-
MIB.mib, you must set to
U2000-T MIB. If it is HW-
IMAPV1NORTHBOUND-
TRAP-MIB.mib or HW-
IMAPV2NORTHBOUND-
TRAP-MIB.mib, you must
set toU2000 MIB.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 21

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 4 Preparing for a Deployment

4.2 Collecting Integration Parameters

Integration parameters must be collected from OSS O&M engineers and confirmed before the
SNMP NBI is deployed to ensure that the input parameters are correct; otherwise, the OSS
cannot receive alarms from or connects to the U2000.

Table 4-1 and Table 4-2 show the collected information.

For parameter definitions, see B Configuration Parameters.

NOTICE
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 Advanced
Configuration.
l Using SNMPv3 is recommended because of its higher security than SNMPv1 and
SNMPv2c.

Table 4-1 General parameters

Item Sample Description

U2000 server IP address 10.71.227.2 Indicates the IP address of the U2000

03 server. Set this parameter when
configuring the SNMP agent.

Port to send 6666 Indicates the U2000 server port that

trap 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 9812 Indicates the U2000 server port that

the request receives request packets form the OSS.

Up-layer IP address 10.70.71.97 Indicates the IP address of the OSS

NMS server server. Set this parameter when setting
third-party NMS parameters.
Ensure the OSS can communicate with
the U2000 by this IP.

Port to receive 6666 Indicates the OSS server port that

trap receives traps from the U2000.

SNMPv1/v2c Read Changeme_ Indicates the community-based security

Community 123 mechanism.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 22

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 4 Preparing for a Deployment

Item Sample Description

Write Changeme_
Community 123

SNMPv3 Security Model USM Model Indicates the security model, security
level, authentication protocol and data
Security Level With encryption protocol for SNMPv3.
authenticati
on and For details, see B.1 General
encryption Parameters.

Authentication HMACSHA

Data AES
Encryption

user name admin Indicates the security mechanisms that

use the user name, authentication
Password Changeme_ password, and encryption password.
Authentication 123
For details, see B.3 Third-Party NMS.
Password for Changeme_
Privacy 123

Alarm Filter Alarm Level Critical Indicates the level of alarms that are
Major reported to the OSS.

Alarm Fault Alarm Indicates the category of alarms that are

Category reported to the OSS.

Table 4-2 Advanced parameter

Item Sample Description

Heartbeat Need heartbeat Specifies whether to send the heartbeat

Heartbeat Period: information to the OSS and the
60 s heartbeat period.

Alarm Field N/A Indicates the alarm information to be

reported to the OSS.
For details, see B.2 Advanced
Configuration.

Notificatio Reporting Trap Indicates the notification mode, such as

n Mode trap and inform. The trap and inform
mode are supported.
Do not use the inform mode unless it is
required.

Support X.733 No Indicates the notification format

Alarms support X.733 standards.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 23

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 4 Preparing for a Deployment

Item Sample Description

Trap Transmit 40ms Indicates the interval for sending

Interval information in trap mode.

Inform Delay 5s Indicates the interval between two

attempts of sending information. The
second attempt is performed when the
OSS does not respond.

Inform Failure 3 Indicates attempts to retransmit

Retry information when the OSS does not
respond in inform mode.

Time 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 Advanced
Configuration.

Encoding Format UTF-8 Indicates the code format for reported

alarms. The UTF-8 and GBK are
supported.
For details, see B.2 Advanced
Configuration.

Alarm Correlation All Specifies whether to report correlation

alarms. By default, the SNMP NBI
report all alarms.
For details, see B.2 Advanced
Configuration.

Engineering Alarm Disable Specifies whether to report engineering

alarms. By default, the SNMP NBI
report all alarms.
For details, see B.2 Advanced
Configuration.

MIB Frame U2000 MIB Specifies whether to load the U2000-T

MIB or U2000 MIB.
For details, see B.2 Advanced
Configuration.

Other Record Log Disable Specifies whether to record log.

Real-time 10000 Indicates the cache size for reported

Alarm Cache alarms. Each OSS user is assigned an
Size independent cache.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 24

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

5 Deploying and Configuring the SNMP NBI

About This Chapter

This chapter describes how to deploy and configure the U2000 SNMP NBI. It includes the
following information:

5.1 Overview
This topic describes the background information and the terms involved in the process of
configuring the northbound interface.
5.2 Configuration Requirements
U2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any
additional configuration is not required. However, to enable the SNMP NBI, you must
purchase the license for the corresponding functions.
5.3 Flow of Deploying the SNMP NBI
After installed U2000, you can configure the SNMP NBI to interconnection with the NMS/
OSS.
5.4 Checking the License
The U2000 controls the functions and available resources of the SNMP NBI by the license.
Before using the SNMP NBI , ensure that you have obtained its license and ensure that the
SNMP NBI configurations in the license meet requirements.
5.5 Logging in to NBI Config Tools
The NBI Config Tools is a graphical maintenance tool developed for the northbound
interfaces (NBIs) of iManager U2000. The MSuite is used to configure the NBIs.
5.6 Configuring the SNMP NBI
By default, the SNMP NBI is installed during the installation of the U2000. But to enable the
SNMP NBI, you need to configure the SNMP NBI parameters by referring to the network
management system (NMS) planning guide.
5.7 Testing the SNMP NBI
This topic describes how to check whether the SNMP NBI functions properly and whether it
is successfully interconnected with the OSS.
5.8 Configuration Sample
This section introduce how to configure the SNMP NBi by configuration sample.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 25

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

5.1 Overview
This topic describes the background information and the terms involved in the process of
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 The northbound interface system has been added automatically during the installation of
U2000. But you need to configure the parameters manually to enable the functions.

NOTICE
l After the U2000 is installed, you need to start the NBI-related process. Then, you can
configure the parameters.
l After initializing the database of the U2000, you need to configure the northbound
interface again.
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 NBI Config Tools server and
clients, log in the NBI Config Tools client that installed on the U2000 server. Otherwise,
the operation may be failed.
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.

NBI Config Tools

Through the GUI of the NBI Config Tools, you can conveniently deploy the northbound
interface.

The NBI Config Tools is a graphical maintenance tool developed for the northbound interface
of Huawei iManager U2000, a type of Huawei network product. The MSuite is used to
configure the northbound interface.

MSuite
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.

For U2000 northbound interface, MSuite is used to update the security certificates.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 26

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Refer to the MSuite part of the iManager U2000 Administrator Guide for the details about the
MSuite.

5.2 Configuration Requirements

U2000 SNMP NBI and the U2000 server run on the same PC or Sun workstation, any
additional configuration is not required. However, to enable the SNMP NBI, you must
purchase the license for the corresponding functions.

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.
For details of hardware requirements of U2000 Server, refer to section Configuration
Requirements in the iManager U2000 Software Installation Guide.

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.
For details of software requirements U2000 Server, refer to section Configuration
Requirements in the iManager U2000 Software Installation Guide.

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.

5.3 Flow of Deploying the SNMP NBI

After installed U2000, you can configure the SNMP NBI to interconnection with the NMS/
OSS.

Context
l Through NBI Config Tools, you can conveniently configure SNMP NBIs.
l SNMP NBI is an optional component of the U2000. A license is required for using this
function.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 27

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

l By default, the SNMP NBI is installed during the installation of U2000. But you need to
configure the parameters of SNMP NBI to enable the function of it.
l After initializing the database of the U2000, you need to configure the SNMP NBI again.

Flowchart of Configuring the SNMP NBI

Figure 5-1 shows the flowchart of configuring the SNMP NBI.

Figure 5-1 Flowchart of configuring the SNMP NBI

Start

No
Is SNMP NBI licensed

Yes

Configure the SNMP NBI

Verify the SNMP NBI

End

5.4 Checking the License

The U2000 controls the functions and available resources of the SNMP NBI by the license.
Before using the SNMP NBI , ensure that you have obtained its license and ensure that the
SNMP NBI configurations in the license meet requirements.

Prerequisites
l The U2000 has been installed.
l The U2000 license has been loaded.
l The U2000 has NE management licenses and functions properly.

Context
NOTE

In U2000 capacity expansion, NBI licenses need to be expanded.

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 ossuser user.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 28

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

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 5-1.
NOTE

l On the Windows OS, the license file is %IMAP_ROOT%\etc\conf\license\LIC_ONxxxxxxx.dat.

l On the Solaris or Linux OS, the license file is $IMAP_ROOT/etc/conf/license/
LIC_ONxxxxxxx.dat.

Table 5-1 Description for License Item

License Control Item Abbreviation Value

Per Equivalent NE License LNSDPENES01 0-500000

for NBI-SNMP Alarm-
Transmission Network

Per Equivalent NE License LNSDPENES02 0-500000

for NBI-SNMP Alarm -IP

Per Narrowband Port LNSDPENEC21 0~8000000

License for NBI-SNMP
Alarm-Access Network

Per Broadband Port License LNSDPENEC25 0~8000000

for NBI-SNMP Alarm-
Access Network

Per PON Terminal Resource LNSDNELCR84 0~8000000

License for NBI-SNMP
Alarm-Access Network

Compatible License for LNSDNELCR75 0~8000000

SNMP Alarm NBI-Access
Network

Per CMC NE Resource LNSDPENEC48 0~8000000

License for NBI-SNMP
Alarm-Access Network

NBI-SNMP Management LNSDNSMFC01 0~8000000

Function Component For
Non-Port Service-Access
Network

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

5.5 Logging in to NBI Config Tools

The NBI Config Tools is a graphical maintenance tool developed for the northbound
interfaces (NBIs) of iManager U2000. The MSuite is used to configure the NBIs.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 29

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Prerequisites
l The nbi_configtools and is_server processes are running.
l The desired NBI process is running.
NBI Type Process

CORBA NBI l Naming_Service

l Notify_Service
l Agent_CORBA

XML NBI l xmlagent

l ActiveMQ

SNMP NBI snmpagent

Performance text NBI textagent

NOTICE
If you do not want to use the default SSL certificate provided by the NBI Config Tools, apply
for a secure certificate and replace the original certificate with the new one. For details, see
Replacing the Certificate of the NBI Config Tools.

Context
Browser requirement:

Browser Requirements

Internet l Version: Internet Explorer 8.0, Internet Explorer 9.0, Internet

Explorer Explorer 10.0
l Security level: Medium or Low.
l Internet Explorer must use a more secure TLS protocol (such as TLS
1.1 and TLS 1.2) and disables the SSL protocol (such as SSL 2.0 and
SSL 3.0) and TLS 1.0.
1. In the Internet Explorer, choose Tools > Internet Options from
the main menu. The Internet Options window is displayed.
2. Select the Advance tab, in the Settings area, select Use TLS 1.1,
Use TLS 1.2 and clear Use SSL 2.0, Use SSL 3.0 and Use TLS
1.0.

Procedure
Step 1 Open Internet Explorer, enter the address of the NBI Config Tools server in the address bar,
and press Enter. The NBI Config Tools Login dialog box is displayed.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 30

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

NOTE

Enter the address of the server, for example, https://IP:13231. The IP is the IP address of the local server
computer in a centralized system or the IS server computer in a distributed system. 13231 is the port ID.

Step 2 Enter the user name, password, and verification code, and click Login.
NOTE

In a centralized system, the NBI Config Tools can be logged in to as the user of the U2000. That is, the
default user name is admin, and the default password is Changeme_123.
In a distributed system, the NBI Config Tools can be logged in to as the user of the U2000 administrator.
That is, the default user name is ssoadmin, and the default password is Changeme_123.

----End

5.6 Configuring the SNMP NBI

By default, the SNMP NBI is installed during the installation of the U2000. But to enable the
SNMP NBI, you need to configure the SNMP NBI parameters by referring to the network
management system (NMS) planning guide.

Prerequisites
l NBI Config Tools running normally.
l After the U2000 is installed, the SNMP NBI process is not running by default. You have
started the snmpagent process manually.
l The U2000 License include SNMP NBI function.

NOTICE
l Set the MIB toU2000 MIB when loading the U2000 MIB.
l Set the MIB to U2000-T MIB when loading the U2000-T MIB.
When the U2000-T MIB is loaded, the following advanced parameters are not supported:
l Heartbeat Settings
l Alarm Field Settings
l Report Date Format Settings

Process of Configuring the SNMP NBI

Figure 5-2 is a flowchart for configuring the SNMP NBI. Setting alarm filter criteria and
advanced parameters are optional. Select desired parameters based on customized
requirements.

Generally, advanced parameters are optional (default values are recommended). Advanced
parameters are independent of each other and no configuration order is required.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 31

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Figure 5-2 Process of configuring the SNMP NBI

Optional Start

Set send trap and receive

request IP/port on U2000

Choose SNMP version

Set receive trap IP/port

Add NMS/OSS
of NMS/OSS

Yes
Whether Set the v3 security level,
SNMPv3 is used? authentication and encrption

No
Set read/write Set v3 user name,
password for authentication
community
and encryption

Set alarm filter criteria

Yes
Multiple NMS?

No
Set Advanced
parameters

End

NOTICE
For a distributed U2000 system, configure the SNMP NBI on the NM server. You do not need
to configure the SNMP NBI on the NBI gateway or EM server.

Context
This topic uses a single-server system as an example. In an HA system, you only need to set
the IP addresses of the primary and secondary sites additionally. Other settings are the same
as those of the single-server system. The specific setting method is as follows.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 32

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

In an HA system, you only need to log in to the NBI Config Tools on the active server to set
the SNMP Agent parameters, without the need to log in to the standby server for repetitive
setting.
l Active server: Select an IP address that is interconnected with the OSS from the drop-
down list.
l Standby server: Enter an IP address that is interconnected with the OSS.

NOTE
If the active and standby servers have multiple network adapters, select (or enter) a correct IP address
that is interconnected with the OSS.

Procedure
Step 1 Log in to NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP > General Config from the navigation tree on the left.

Step 3 Set parameters in the General area.

For details on the SNMP agent, see B.1 General Parameters.

1. Set the trap sending address/port and request receiving address/port.

By default, the trap sending port is 6666 and the request receiving port is 9812.

NOTICE
The trap sending address and request receiving 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.

By default, the SNMP version is v3.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 33

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

NOTICE
When SNMPv3 is used, it is recommended that the OSS use the securer SHA and AES
algorithms.

Step 4 Set parameters for the OSS in the Third-Party NMS area.

For parameter definitions, see B.3 Third-Party NMS.

1. The Receiving/Sending Address is the IP address of the OSS server.
NOTE

The Receiving/Sending Address is not the IP address of the U2000 server but the IP address of a
third-party NMS of the upper layer. If the third-party NMS uses two servers to receive traps and
send requests, the IP addresses for these two servers must be configured respectively.
Currently a maximum of 10 third-party NMSs are supported. The following table lists the
configuration requirements for third-party NMSs.

MIB SNMP Configuration Requirements

Type Version

U2000 v1/v2c You are advised to set different read and write community names
MIB for third-party NMSs. If multiple third-party NMSs (for example,
NMS 1 and NMS 2) use the same read and write community
names, ensure that the SNMP protocol versions used by the NMSs
are the same.

v3 You are advised to set different user names for third-party NMSs.
If multiple third-party NMSs (for example, NMS 1 and NMS 2)
use the same user name, the same authentication password or
encryption password must be set for all the NMSs.

U2000-T v1/v2c You are advised to set different read and write community names
MIB for third-party NMSs.

v3 You are advised to set different user names for third-party NMSs.

2. Set SNMP security parameters.

The following are the default security parameters. Modifying these parameters and using
SNMPv3 protocol is recommended for security concern.
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.
If the SNMP version is set to v3, configure V3 User Name, V3 Authentication
Password, and V3 Privacy Password for SNMPv3 users. By default, the user
name is admin and the two passwords are Changeme_123.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 34

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

NOTICE
In the case of SNMPv3, 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, remember to change the default passwords of
U2000 and update the passwords regularly, passwords must be complex enough.
The password must meet the following requirements to safeguard your user account.
1. Contain 8 to 30 characters.
2. Contains at least four types of the following combinations:
n Uppercase letter
n Lowercase letter
n Digit
n Special characters ~!@#$^&*()-_=+|[{}];:' ",<.>/?
3. Cannot contain more than two consecutive identical characters.

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 7.1.2 Changing Filter Criteria.
Fault: Specifies whether to report alarm generation and alarm clearance. After this check box is
selected, 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 NBI Config Tools.
But you can enable this function by following methods.
You can enable event alarm function manually. For details, see 8.3.9 How to report the event
alarm.
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: Repeat the preceding substeps to add, modify, or delete the third-party NMS.
Step 5 Optional: Set advanced parameters in the Advanced area.
1. Specify whether to set the heartbeat, and set the heartbeat period.
NOTE

The U2000-T MIB does not support this function.

Parameters Value Description

Heartbeat Default: 60 Specifies the heartbeat period of the

Interval 3s-300s third-party NMS.

Heartbeat Default: Enable Specifies whether send the heartbeat

Reporting Enable, Disable information to the third-party NMS.

2. Set the alarm fields to be reported. For details, see B.2 Advanced Configuration.
3. Set the reporting mode and other relevant parameters.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 35

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Parameter Description Value

Reporting Default: Trap Specifies the mode used by the SNMP

Mode Trap, Inform agent for sending alarms to the OSS.

Support X.733 Default: No Specifies whether traps use the event

Alarms Yes, No types 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.

Trap Transmit Default: 0 Specifies the time interval for sending

Interval 0 ms-1000 ms messages in Trap mode.

Inform Delay Default: 5 Indicates the interval between two

5 s - 120 s attempts to send information in inform
mode. The second attempt is performed
if the OSS does not respond.

Max. Inform Default: 3 Indicates attempts to resend information

Transmit 2 times-6 times when the OSS does not respond in
Retries inform mode.

4. Set the date format for reported alarms.

Paramete Value Description
rs

Alarm Default: UTC Indicates the format of the alarm time.

Time Time UTC Time
Format UTC Time, The format is as YYYY/MM/DD - hh:mm:ssZ.
Local Time
(without Time Example: 2009/12/23 - 11:30:30Z
Zone), Local Local Time (without Time Zone)
Time (with The format is as YYYY/MM/DD - hh:mm:ss.
Time Zone)
Example: 2009/12/23 - 19:30:30
Local Time (with Time Zone)
The format is as YYYY/MM/DD -
hh:mm:ss,hh:mmTZ[DST], where TZ stands for
timezone information.
Example:
2009/12/23 - 19:30:30,+08:00[0] (if the date is not
in DST).
2009/12/23 - 19:30:30 +08:00[3600] (if the date is
in DST of 1 hr). The DST value is in seconds.

5. Set the code format for traps.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 36

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Parameters Value Description

Alarm Default: UTF-8 There are two types of alarm

Encoding UTF-8, GBK coding as follows: UTF-8, GBK.
Format

6. Specify whether to report the correlative alarms.

Parameter Value Description
s

Alarm Default: All All: Queries and reports all alarms including the root
Correlation Root alarm and correlative alarms.
Root: Queries and reports only the root alarm and
common alarms.

7. Specify whether to report the engineering alarms.

Parameters Value Description

Filter Out Default: Disable Specifies whether to report the

Engineering Enable, Disable engineering alarms. You must
Alarms restart the server if you have
changed the configuration of
engineering alarm.
Disable: specifies that all
alarms are queried and
reported.
Enable: specifies that all
alarms except for engineering
alarms are queried and
reported.

8. Set the MIB structure and resource information for alarms.

NOTICE
Select an appropriate MIB structure based on integration scenarios. For details, see B.2
Advanced Configuration.

9. Specify whether to log alarms, and set the cache size for alarms.
Parameters Value Description

Logging Default: Specifies whether alarms are recorded in logs.

Disable
Enable,
Disable

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 37

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Parameters Value Description

Active-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.

Step 6 Click Save, the dialog box displayed prompt restart the NBI processes for the updates to take
effect. Click OK, the dialog box displayed prompt successfully saved. Click OK to complete
the configuration.

NOTICE
If you click Cancel in the dialog box displayed prompting you to restart the NBI processes for
the updates to take effect, the user configurations are saved only on the configuration page but
not applied to the configuration file. In this case, the configurations will not take effect even
after the related NBI process is restarted.

NOTE

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.

CAUTION
Restart the U2000 when you first deploy NBIs. After NBIs are deployed, restart the U2000
only when Alarm Correlation and Engineering Alarm are modified.

Step 7 Check the status of the SNMP service process. If the process is running, the SNMP NBI has
been enabled successfully.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 38

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

----End

5.7 Testing the SNMP NBI

This topic describes how to check whether the SNMP NBI functions properly and whether it
is successfully interconnected with the OSS.

5.7.1 U2000 MIB

This topic describes how to verify the running status of the SNMP NBI after the U2000 MIB
is loaded. The U2000 MIB includes HW-IMAPV1NORTHBOUND-TRAP-MIB.mib and
HW-IMAPV2NORTHBOUND-TRAP-MIB.mib.

Prerequisites
l The SNMP NBI is correctly deployed and configured.
l Set SNMP heartbeat information.
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 found, see the 8.3.1 SNMP Service Process Is Not
Displayed for troubleshooting.
l If the SNMP NBI process fails to be started, see the 8.3.2 SNMP Service Process Fails
to Be Started for troubleshooting.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 39

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Step 2 Check whether heartbeat messages are received on the related OSS port. If no heartbeat
message is received, see the 8.3.4 The OSS Cannot Receive Heartbeat Information for
troubleshooting.

----End

5.7.2 U2000-T MIB

This topic describes how to verify the running status of the SNMP NBI after the U2000-T
MIB is loaded. The U2000-T MIB includes T2000-NETMANAGEMENT-MIB.mib.

Prerequisites
The SNMP NBI is correctly deployed and configured.

----End

5.8 Configuration Sample

This section introduce how to configure the SNMP NBi by configuration sample.

5.8.1 Deploying the SNMPv1 NBI

This topic describes how to use SNMPv1 to deploy the SNMP NBI. The deployment of the
SNMPv2c NBI is similar to that of the SNMPv1 NBI.

Prerequisites
NBI Config Tools running normally.

Network Planning
The MIB file HW-IMAPV1NORTHBOUND-TRAP-MIB.mib is loaded to the OSS, as
shown in Figure 5-3. The OSS manages and monitors alarms from Huawei network
equipment using the SNMPv1 NBI. Table 5-2 and Table 5-3 list detailed parameters.

You are advised to use default values for other relevant parameters. For more details, see B
Configuration Parameters.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 40

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Table 5-2 Server parameters for the SNMPv1 NBI

Server Parameters Value

Upper-layer IP address 10.70.71.97

NMS
Receiving/Sending Address 6666

MIB HW-IMAPV1NORTHBOUND-
TRAP-MIB.mib

U2000 IP address 10.167.239.92

Trap Sending Port 6666

Request Receiving Port 9812

Table 5-3 Communication parameters for the SNMPv1 NBI

Parameters Value

SNMP Version SNMPv1

Old Community Changeme_123

Read Community Changeme_1234

Write Community Changeme_1234

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 41

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Figure 5-3 Network planning parameters for the SNMPv1 NBI

OSS IP: 10.70.71.97

Received Trap Port: 6666
MIB: HW-IMAPV1NORTHBOUND-TRAP-MIB.mib

set/get Inform Read Community: Changeme_1234

SNMPv1 Write Community: Changeme_1234

IP: 10.167.239.92
U2000 Received Request Port: 9812
Send Trap Port: 6666

Device Network

Procedure
Step 1 Log in to NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP > General Config from the navigation tree on the left.

Step 3 Set the parameters in the General area.

General configuration parameters are U2000 server parameters.
l Address for Sending Trap: 10.167.239.92 Port: 6666
l Address for Receiving NMS Request: 10.167.239.92 Port: 9812

Step 4 Set parameters for third-party NMSs in the Third-Party NMS area.
Third-party NMS parameters are OSS parameters. Set the parameters according to the data
plan.
l Receiving/Sending Address: 10.70.71.97

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 42

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

l Port: 6666
l SNMP Version: v1
l Old Community: Changeme_123
l Read Community: Changeme_1234
l Write Community: Changeme_1234

NOTE

Parameter for SNMPv3 (such as user name/password, authentication password, and encryption
password) are invalid if v3 is not selected.

Step 5 In the Advanced area, select U2000 MIB from the MIB Frame drop-down list.

----End

5.8.2 Deploying the SNMPv3 NBI

This topic describes how to use SNMPv3 to deploy the SNMP NBI. The SNMPv3 NBI
provides a higher security level than SNMPv1 and SNMPv2c NBIs.

Prerequisites
NBI Config Tools running normally.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 43

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Network Planning
The MIB file T2000-NETMANAGEMENT-MIB.mib is loaded to the OSS, as shown in
Figure 5-4. The OSS manages and monitors alarms from Huawei network equipment using
the SNMPv1 NBI. Table 5-4 and Table 5-5 list detailed parameters.
You are advised to use default values for other relevant parameters. For more details, see B
Configuration Parameters.

Table 5-4 Server parameters for the SNMPv3 NBI

Server Parameters Value

Upper-layer IP address 10.70.71.97

NMS
Receiving/Sending Address 9833

MIB T2000-NETMANAGEMENT-
MIB.mib

U2000 IP address 10.167.239.92

Trap Sending Port 9831

Request Receiving Port 9832

Table 5-5 Communication Parameters for the SNMPv3 NBI

Parameters Value

SNMP Version v3

Security Level With authentication and encryption

v3 User Name admin

Old Password You must enter the old password to set the
password. The default password is
Changeme_123.

v3 Authentication Password Changeme_1234

v3 Encryption Password Changeme_1234

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 44

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Figure 5-4 Network planning parameters for the SNMPv3 NBI

OSS IP: 10.70.71.97

Received Trap Port: 9833
MIB: T2000-NETMANAGEMENT-MIB.mib

v3 User: admin
set/get Inform Authentication password: Changme_1234
SNMPv3 Encryption password: Changme_1234

IP: 10.167.239.92
U2000 Received Request Port: 9832
Send Trap Port: 9831

Device Network

Procedure
Step 1 Log in to NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP > General Config from the navigation tree on the left.

Step 3 Set the parameters in the General area.

General configuration parameters are U2000 server parameters.

l Trap Sending Address: 10.167.239.92 Port: 9831

l Request Receiving Address: 10.167.239.92 Port: 9832
l Security Model: USM
l Security Level: With authentication and encryption
l Authentication: HMACSHA
l Data Encryption: AES

Step 4 Set parameters for third-party NMSs in the Third-Party NMS area.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 45

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 5 Deploying and Configuring the SNMP NBI

Third-party NMS parameters are OSS parameters. Set the parameters according to the data
plan.
l Receiving/Sending Address: 10.70.71.97
l Port: 9833
l SNMP Version: v3
l v3 User Name: admin
l Old Password: Changeme_123
l v3 Authentication Password: Changeme_1234
l v3 Encryption Password: Changeme_1234

Step 5 In the Advanced area, select U2000-T MIB from the MIB Frame drop-down list.

----End

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 46

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 6 Configuring the SNMP NBI on the OSS

6 Configuring the SNMP NBI on the OSS

About This Chapter

After the SNMP NBI was deployed properly, the OSS can receive real-time alarms. To
connect to the U2000 and enable operations on reported alarms (such as synchronize,
acknowledge, unacknowledge, and clear alarms), you need also load the appropriate MIB file
to the OSS and set relevant parameters. A maximum of ten OSSs can be connected
concurrently to the U2000. For the NMS connection, SNMPv1, SNMPv2c, and SNMPv3 can
be used.

6.1 Configuring the SNMPv1 or SNMPv2c NBI

The OSS connects to the U2000 through SNMPv1 and SNMPv2c NBIs by using communities
for access authentication. Configurations are similar for SNMPv1 and SNMPv2c NBIs.
Parameters include the request receive IP address/port on the U2000, SNMP version, and
read/write communities.
6.2 Configuring the SNMPv3 NBI
Compared to SNMPv1 and SNMPv2c, the SNMPv3 NBI is characterized by higher security
due to its user-based security mechanism. In this mechanism, user names and passwords are
used for access authentication and packet data is encrypted. Parameters include the request
receive IP address/port on the U2000, SNMP version, security level, authentication/
encryption protocol, and authentication/encryption password.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 47

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 6 Configuring the SNMP NBI on the OSS

6.1 Configuring the SNMPv1 or SNMPv2c NBI

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 NBI Config Tools.
2. Choose Configure SNMP > General Config from the navigation tree on the left. View
parameters as follows.
Para Description Default Navigation Path
meter Value
s

IP Indicates the 9812 In the General area, view Address for

addres request receive IP This value can Receiving NMS Request and Port.
s and address/port on the be modified
port of U2000. based on
U2000 system
conditions.

SNMP Indicates the v3 In the Third-Party NMS area, view

Versio SNMP version for SNMP version.
n the SNMP NBI.

Read/ Indicates the Read Learn the values of Read Community

Write access Community: and Write Community from the
Comm authentication for Changeme_123 administrator.
unity the OSS to connect Write
to the U2000 Community:
through the SNMP Changeme_123
NBI.

Step 2 Configure the OSS based on the previous parameters set on the U2000.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 48

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 6 Configuring the SNMP NBI on the OSS

NOTICE
Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the
connection may fail.

----End

6.2 Configuring the SNMPv3 NBI

Compared to SNMPv1 and SNMPv2c, the SNMPv3 NBI is characterized by higher security
due to its user-based security mechanism. In this mechanism, user names and passwords are
used for access authentication and packet data is encrypted. Parameters include the request
receive IP address/port on the U2000, SNMP version, security level, authentication/
encryption protocol, and authentication/encryption password.

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.

IP address Indicates the 9812 In the General area, view Address

and port of request receive IP This value can for Receiving NMS Request and
U2000 address/port on be modified Port.
the U2000. based on
system
conditions.

SNMP Indicates the v3 In the Third-Party NMS area, view

Version SNMP version Change the SNMP version.
for the SNMP value to v3 if
NBI. SNMPv3 is
used.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 49

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 6 Configuring the SNMP NBI on the OSS

Parameters Description Default Navigation Path

Value

Security For SNMPv3, USM model In the General area, view Security
Model you can set the Mode.
security model.
The USM model
is support for
current version.

Security Indicates the With In the General area, view Security

Level security level, authentication Level.
including without and
authentication encryption
and encryption,
with
authentication
and without
encryption, and
with
authentication
and encryption.

Authenticati Indicates the HMACSHA In the General area, view

on Protocol authentication Authentication Protocol.
algorithm,
including NONE,
HMACMD5, and
HMACSHA.

Data Including the AES In the General area, view Data

Encryption encryption Encryption.
Protocol algorithm,
including NONE,
DES, and AES.

User Name Indicates the user admin In the Third-Party NMS area, view
name for v3 User Name.
authentication.

Authenticati Indicates the Changeme_1 Learn v3 Authentication Password

on Password authentication 23. from the administrator.
password.

Data Indicates the data Changeme_1 Learn v3 Privacy Password from

Encryption encryption 23. the administrator.
Password password.

Step 2 Configure the OSS based on the previous parameters set on the U2000.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 50

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 6 Configuring the SNMP NBI on the OSS

NOTICE
Confirm with the U2000 administrator if you need to modify a parameter; otherwise, the
connection may fail.

----End

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 51

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

7 Calling the SNMP NBI

About This Chapter

The OSS calls SNMP subinterfaces to perform operations such as alarm synchronization on
the U2000. Available interfaces vary with the loaded MIB (U2000-T MIB or U2000 MIB).

NOTE

Ensure that the OSS has connected to the U2000 through the SNMP NBI and the desired operations
have been licensed for use.

7.1 U2000 MIB Subinterfaces

When the OSS is loaded with the U2000 MIB, the SNMP NBI provides subinterfaces to
enable the following functions: reporting alarms automatically, and synchronizing, clearing,
confirming, acknowledging, unacknowledging, and filtering alarms.
7.2 U2000-T MIB Subinterfaces
When the OSS is loaded with the U2000-T MIB, the SNMP NBI provides subinterfaces to
enable the following functions: reporting alarms automatically and synchronizing alarms.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 52

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

7.1 U2000 MIB Subinterfaces

NOTICE
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.

7.1.1 Reporting Real-Time Alarms

You do not need to set any parameters for the OSS to receive alarm packets from the U2000
through the SNMP NBI. After the SNMP NBI is properly deployed on the U2000, alarms will
be reported to the OSS in real time.
The SNMP NBI 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 5 Deploying and
Configuring the SNMP NBI.

NOTICE
The SNMP NBI in distributed U2000 cannot report events.

7.1.2 Changing Filter Criteria

The SNMP NBI allows the OSS dynamically to change filter criteria during its running so
only required alarms are reported.

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.
The full path is

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 53

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFau
lt(3).thirdNMSFaultFilter(5)

Object Type Max Access Description

thirdNMSFaultFilter Octet string read-write Indicates that alarm

filter criteria are
changed
dynamically.

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

NOTICE
l The thirdNMSFaultFilter node only supports the set operation, that is, only the write
attribute is enabled. Therefore, you need to use the U2000 MSuite to query the setting
results of the thirdNMSFaultFilter node.
l When you set the OID of MIB node, you must add .0 to the end of the OID of MIB node.

Table 7-1 Format description - changing filter criteria

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.

AlarmFilterLe Indicates the severity of an alarm.

vel Four binary digits are used to represent critical, major, minor, or warning
in 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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 54

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Field Description

AlarmCategor Indicates the category of an alarm.

yFilter Six binary digits are used to represent event, fault, recover, acknowledge,
unacknowledge or change alarm in descending order.
l 1: indicates that the alarms of the corresponding category are filtered
out and the OSS cannot receive alarms with the category.
l 0: indicates that the alarms of the corresponding category are reported
and the OSS can receive alarms with the category.

NOTICE
The SNMP NBI in distributed U2000 cannot report events.

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

To change the filter criteria as follows: alarm severity (critical or major) and alarm category
(fault or clear).

Table 7-2 shows the parameters of this sample.

Table 7-2 Sample parameters - changing filter criteria

Parameter Value MIB Object

The IP of upper-layer NMS 10.70.73.97 10.70.73.97

Receive Trap Port 6666 6666

Alarm Severity to be Critical, Major 0011

Reported

Alarm Category to be Fault Alarm, recover 100111

Reported

Procedure

1. The OSS sets the OID of thirdNMSFaultFilter node to

1.3.6.1.4.1.2011.2.15.1.3.5.0.
2. The OSS sets thirdNMSFaultFilter to 10.70.73.97:6666:0011:100111.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 55

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

The OSS receives responses from the U2000, indicating that the filter criteria are changed
successfully. The OSS will then receive the required alarms only.

7.1.3 Synchronizing Alarms

The SNMP NBI allows the OSS to initiate the synchronization operation to ensure that the
alarm information on the OSS and the U2000 is consistent.

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.

Figure 7-1 shows the alarm synchronization process.

Figure 7-1 Alarm synchronization process

NMS/OSS SNMP NBI

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

Synchronize alarms 1. The OSS synchronizes alarms.

2. The U2000 sends traps through the SNMP NBI to inform the
OSS of the start of alarm synchronization.
3. The U2000 sends traps through the SNMP NBI to report the
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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 56

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Operation Description

Stop the alarm 1. The OSS stops the alarm synchronization.

synchronization 2. The U2000 sends traps through the SNMP NBI to inform the
OSS of the stop of alarm synchronization.

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.

The OIDs are 1.3.6.1.4.1.2011.2.15.1.7.7.4 and

1.3.6.1.4.1.2011.2.15.1.7.7.5.

The full paths are

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmNor
thboundEvent(7).hwNmNorthboundEventSynchronization(7).hwNmNort
hboundEventSynchronizationCommandStart(4)

Object Syntax Max Access Description

hwNmNorthboundE Octet string read-write Indicates that the

ventSynchroniza- alarm
tionCommandStart synchronization is
started.

hwNmNorthboundE Octet string read-write Indicates that the

ventSynchroniza- alarm
tionCommandStop synchronization is
stopped.

Setting Method
Start alarm synchronization.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 57

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

The OSS can set the value of the MIB node to start alarm synchronization within a specified
time. The format is as follows:
IP:port:start time:end time
Stop alarm synchronization.
The OSS can set the value of the MIB node to stop alarm synchronization. The format is as
follows:
IP:port

NOTE

l When you set the OID of MIB node, you must add .0 to the end of the OID of MIB node.
l You do not need to set the start and end time to stop the alarm synchronization.

Table 7-3 Format description - synchronizing alarms

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.

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.
l MM: Two-digit month. The range of values is 01-12.
l DD: Two-digit date. The range of values is 01-31.
l hh: Two-digit hour. The range of value is 00-23.
l mm: Two-digit minutes. The range of values is 00-59.
l ss: Two-digit seconds. The range of values is 00-59.

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 58

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

l The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.

Purpose

To synchronize alarms that are generated between 2011-03-01 00:00:00 and 2011-03-15
00:00:00.

Table 7-4 shows the parameters of this sample.

Table 7-4 Sample parameters - synchronizing alarms

Parameter Value MIB Object

The IP of the upper-layer 10.70.73.97 10.70.73.97

NMS

Receive Trap Port 6666 6666

Start time 2011-03-01 00:00:00 20110301000000

End Time 2011-03-15 00:00:00 20110315000000

Procedure
1. The OSS sets the OID of hwNmNorthboundEventSynchronizationCommandStart
node to:
1.3.6.1.4.1.2011.2.15.1.7.7.4.0
2. The OSS sets hwNmNorthboundEventSynchronizationCommandStart to:
10.70.73.97:6666:20110301000000:20110315000000
The OSS receives traps from the U2000, indicating that the synchronization is
started.
The U2000 reports alarms saved in the database that are generated during the preset
time period.
3. Optional:
To stop the synchronization, the OSS sets
hwNmNorthboundEventSynchronizationCommandStop to 10.70.73.97:6666.
4. After the synchronization is completed or stopped, the U2000 sends traps through the
SNMP NBI to inform the OSS that the synchronization is ended.

7.1.4 Acknowledging Alarms

The SNMP NBI allows the OSS to acknowledge alarms on the U2000 by alarm serial number.
An acknowledged alarm is an alarm that has been handled.

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 59

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

NOTICE
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.

The full path is

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFau
lt(3).hwNmAcknowledgeAlarms(7)

Object Type Max Access Description

hwNmAcknowledge Octet string read-write Indicates that alarms

Alarms are acknowledged
based on serial
numbers.

NOTE

The GET operation is not supported on this MIB node.

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,...

Table 7-5 Format description - acknowledging alarms

Parameter Description

Serial alarm serial number

Number,Se Integer, separated by a comma.
rial
Number,..
.

Table 7-6 shows the status changes when alarms are acknowledged.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 60

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Table 7-6 Alarm states - acknowledging alarms

Sl.No Alarm Status Status Change SET Response Failed List

1 Unacknowledge Acknowledge Success Empty

and Unclear and Unclear

2 Unacknowledge Acknowledge Success Empty

and Clear and Clear

3 Acknowledge Acknowledge Success Empty

and Unclear and Unclear

4 Acknowledge NA Success serial number

and Clear

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.
When you set the OID of MIB node, you must add .0 to the end of the OID of MIB node.

Sample
Prerequisite

The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.

Purpose

To acknowledge the alarm with the serial number 20,30,10005,18000.

Table 7-7 shows sample parameters.

Table 7-7 Sample parameters - acknowledging alarms

Parameter Value MIB Object

Alarm serial number 20,30,10005,18000 20,30,10005,18000

Procedure

1. The OSS sets the OID of hwNmAcknowledgeAlarms node to

1.3.6.1.4.1.2011.2.15.1.3.7.0.
2. The OSS sets hwNmAcknowledgeAlarms to 20,30,10005,18000.

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 61

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

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.

7.1.5 Unacknowledging Alarms

The SNMP NBI allows the OSS to unacknowledge alarms on the U2000 by alarm serial
number. This function allows you to unacknowledge an acknowledged alarm if necessary.

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.

NOTICE
The Acknowledgement User parameter is SNMP Agent User on the U2000 client after an
alarm is unacknowledged by the OSS through the SNMP NBI.
Alarms with invalid or nonexistent serial numbers and historical alarm cannot be
unacknowledged 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.8.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFau
lt(3).hwNmUnAcknowledgeAlarms(8)

Object Type Max Access Description

hwNmUnAcknowle Octet string read-write Indicates that alarms

dgeAlarms are unacknowledged
based on serial
numbers.

NOTE

The GET operation is not supported on this MIB node.

Setting Method
The OSS can set the value of the MIB node to unacknowledge the active alarm on U2000.
The format is as follows:

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 62

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Serial Number,Serial Number,...

Table 7-8 Format description - unacknowledging alarms

Parameter Description

Serial alarm serial number

Number,Se Integer, separated by a comma.
rial
Number,..
.

Table 7-9 shows the state change when alarms are unacknowledged.

Table 7-9 Alarm states - unacknowledging alarms

Sl.No Alarm Status Status SET Response Failed List

Change

1 Unacknowledge Unacknowledge Success Empty

and Unclear and Unclear

2 Unacknowledge Unacknowledge Success Empty

and Clear and Clear

3 Acknowledge Unacknowledge Success Empty

and Unclear and Unclear

4 Acknowledge NA Success serial number

and Clear

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.
When you set the OID of MIB node, you must add .0 to the end of the OID of MIB node.

Sample
Prerequisite

The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.

Purpose

To unacknowledge the alarm with the serial number 20,30,10005,18000.

Table 7-10 shows the parameters of this sample.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 63

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Table 7-10 Sample parameters - unacknowledging alarms

Parameter Value MIB Object

Alarm serial number 20,30,10005,18000 20,30,10005,18000

Step
1. The OSS sets the OID of hwNmUnAcknowledgeAlarms node to
1.3.6.1.4.1.2011.2.15.1.3.8.0.
2. The OSS sets hwNmUnAcknowledgeAlarms to 20,30,10005,18000.

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.

7.1.6 Clearing Alarms

The SNMP NBI allows the OSS to clear alarms on the U2000 by alarm serial number.
Manually clear the alarm if the U2000 cannot automatically clear the alarm or this alarm does
not exist on an NE.

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.

NOTICE
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.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).hwNetManagement(15).hwNmAgent(1).hwNmFau
lt(3).hwNmClearAlarms(6)

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 64

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Object Type Max Access Description

hwNmClearAlarms Octet string read-write Indicates that alarms

are cleared based on
serial numbers.

NOTE

The GET operation is not supported on this MIB node.

Setting Method
The OSS can set the value of the MIB node to clear the active alarm on U2000. The format is
as follows:
Serial Number,Serial Number,...

Table 7-11 Format description - clearing alarms

Parameter Description

Serial alarm serial number

Number,Se Integer, separated by a comma.
rial
Number,..
.

Table 7-12 shows the change in state when alarms are cleared.

Table 7-12 Alarm status - clearing alarms

Sl.No Alarm Status Status SET Response Failed List
Change

1 Unacknowledge Unacknowledge Success Empty

and Unclear and Clear

2 Unacknowledge Unacknowledge Success Empty

and Clear and Clear

3 Acknowledge Acknowledge Success Empty

and Unclear and Clear

4 Acknowledge NA Success serial number

and Clear

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 65

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

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.
When you set the OID of MIB node, you must add .0 to the end of the OID of MIB node.

Sample
Prerequisite
The OSS connects to the SNMP NBI and can receive heartbeat or real-time alarms.
Purpose
To clear the alarm with the serial number 20,30,10005,18000.

Table 7-13 shows the parameters of this sample.

Table 7-13 Sample parameters - clearing alarms

Parameter Value MIB Object

Alarm serial number 20,30,10005,18000 20,30,10005,18000

Procedure
1. The OSS sets the OID of hwNmClearAlarms node to:
1.3.6.1.4.1.2011.2.15.1.3.6.0
2. The OSS sets hwNmClearAlarms to:
20,30,10005,18000

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 a cleared alarm is also an acknowledged one, it becomes a historical alarm.

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.

7.1.7 Reporting Alarm Acknowledging Status

The SNMP NBI reports the alarm acknowledging status.

Description
When a user configures the reporting alarm acknowledging status function of the SNMP NBI
on the U2000, the OSS receives alarm acknowledging status in real-time.

MIB Node Definition

The OID of this object is 1.3.6.1.4.1.2011.2.15.1.7.1.33.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 66

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

The complete path is:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).netManagement(15).nmAgent(1).nmNorthboun
dEvent(7).hwNmNorthboundEventInfo(1).hwNmNorthboundConfirmStat
us(33)

Node Data Type Max Access Description

hwNmNorthboundC Integer32 read-write l 1: acknowledged

onfirmStatus l 2:
unacknowledged

NOTE

The MIB node does not support Get and Set operations.

Setting Method
For details, see Configuring the SNMP NBI.

7.1.8 Reporting Alarm Clearing Status

The SNMP NBI reports the alarm clearing status.

Description
When a user configures the reporting alarm clearing status function of the SNMP NBI on the
U2000, the OSS receives alarm clearing status in real-time.

MIB Node Definition

The OID of this object is 1.3.6.1.4.1.2011.2.15.1.7.1.34.

The complete path is:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).netManagement(15).nmAgent(1).nmNorthboun
dEvent(7).hwNmNorthboundEventInfo(1).hwNmNorthboundRestoreStat
us(34)

Node Data Type Max Access Description

hwNmNorthboundR Integer32 read-write l 1: cleared

estoreStatus l 2: not cleared

NOTE

The MIB node does not support Get and Set operations.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 67

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

Setting Method
For details, see Configuring the SNMP NBI.

7.2 U2000-T MIB Subinterfaces

When the OSS is loaded with the U2000-T MIB, the SNMP NBI provides subinterfaces to
enable the following functions: reporting alarms automatically and synchronizing alarms.

NOTICE
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.

7.2.1 Reporting Real-Time Alarms

The SNMP NBI 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 5 Deploying and
Configuring the SNMP NBI.

NOTICE
l 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.
l The SNMP NBI in distributed U2000 cannot report events.

7.2.2 Synchronizing Alarms

The SNMP NBI allows the OSS to initiate the synchronization operation to ensure that alarms
on the OSS and the U2000 are consistent.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 68

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

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.
Figure 7-2 shows the alarm synchronization process.

Figure 7-2 Alarm synchronization process

NMS/OSS SNMP NBI

Set alarm
synchronization start node
Report alarm
synchronization stop trap

Operation Description

Synchronize alarms 1. The OSS synchronizes alarms.

2. The U2000 sends traps through the SNMP NBI to inform the
OSS of the start of alarm 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.

Stop alarm 1. The OSS stops the alarm synchronization.

synchronization 2. The U2000 sends traps through the SNMP NBI to inform the
OSS of the stop 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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 69

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

MIB Definition
The OID is 1.3.6.1.4.1.2011.2.15.1.7.4.1.
The full path is
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).netManagement(15).nmAgent(1).nmNorthboun
dEvent(7).northboundSynchAlarm(4).northBoundSynchAlarmCommand(
1)

Object Type Max Access Description

northBoundSynchA- Integer read-write Indicates that the

larmCommand alarm
synchronization is
started or stopped.

Setting Method
The OSS can set the value of the MIB node to start or stop the synchronization. The format is
as follows:
number

Table 7-14 Format description - synchronizing alarms

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
To start or end the alarm synchronization.
Step
1. The OSS sets the OID of northBoundSynchAlarmCommand node to
1.3.6.1.4.1.2011.2.15.1.7.4.1.0.
2. The OSS sets the northBoundSynchAlarmCommand node to 1.
The OSS receives traps from the U2000, indicating that the synchronization is
started.
The U2000 reports alarms saved in the database that are generated during the set
time period.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 70

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 7 Calling the SNMP NBI

3. Optional:
To stop the synchronization, set the northBoundSynchAlarmCommand node to 0.
4. After the synchronization is completed or stopped, the U2000 sends traps through the
SNMP NBI to inform the OSS that the synchronization is ended.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 71

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

8 Maintaining the SNMP NBI

About This Chapter

This chapter introduces how to maintain the SNMP NBI.

8.1 Maintenance Description

This section describes the basic requirement of maintenance SNMP NBI.
8.2 Deleting and Disabling an SNMP Interface
This topic describes how to disable or delete an SNMP interface when the U2000 temporarily
need not provide this interface to an external network.
8.3 Faults and Solutions
This section introduces the faults of the SNMP NBI and the related solutions.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 72

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

8.1 Maintenance Description

This section describes the basic requirement of maintenance SNMP NBI.
To ensure that the SNMP NBI works well, there are some requirements as follows:
1. The maintenance personnel must be familiar with:
Windows or the Sun workstation - Solaris 8 or Solaris 10, and Linux
The SNMP protocol
Basic concepts of the Telecommunication Management Network (TMN)
2. The U2000 Server runs normally.
3. The License support SNMP NBI function.
4. The parameter is correct when you deploy the SNMP NBI by NBI Config Tools.

8.2 Deleting and Disabling an SNMP Interface

This topic describes how to disable or delete an SNMP interface when the U2000 temporarily
need not provide this interface to an external network.

8.2.1 Logging In to the System Monitor Client

The U2000 System Monitor Client uses the client/server model. To perform an operation, you
need to log in to the server through the U2000 client.

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 of U2000 System Monitor on the desktop to start the system
monitor client.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 73

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

NOTE

In the Solaris and Linux OS , login to the OS of the server as the ossuser user. Run the following
command to start the system monitor client.
$ cd /opt/oss/client
$ ./startup_sysmonitor_global.sh
/opt/oss 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

If the list does not contain a server, do as follows:

1. Click on the right of the Server drop-down list.

2. In the Server List dialog box, click Add.
3. In the Add Server Information dialog box, specify Name and Server Name(or IP Address), and
then select a login mode. Click OK.
4. In the Server List dialog box, click OK.

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.

Step 4 Click Login.

NOTE

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

8.2.2 Stopping the SNMP NBI

If you need not use the SNMP NBI, you can stop the service of the SNMP NBI by using the
System Monitor client.

Prerequisites
l Log in to the Solaris or Linux OS as user ossuser.
l Log in to the Windows OS as user Administrator.
l The U2000 must be operating.
l The SnmpAgent service are in the Running state.

Context
NOTE

The default start mode is Automatic. The SNMP interface process is started with the U2000.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 74

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

Procedure
Step 1 Log in to the System Monitor.
Step 2 On the System Monitor, enter the Service Monitor tab.

Step 3 Select SnmpAgent service, right-click and choose Stop the Service.
Step 4 The prompt dialog box displayed, click Yes.
Step 5 On the System Monitor client, if Status of the related service of the SNMP NBI is Stopped, it
indicates that the operation is successful.

----End

8.2.3 Disabling the SNMP NBI

By disabling the SNMP NBI, the SNMP interface service will not start with the U2000 when
you start the U2000 next time.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 75

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

Prerequisites
l Log in to the Solaris or Linux OS as user ossuser.
l Log in to the Windows OS as user Administrator.
l The U2000 must be operating.
l The SnmpAgent Service is in the Stopped state.

Procedure
Step 1 Log in to the System Monitor.

Step 2 On the System Monitor, enter the Service Monitor tab.

Step 3 Select the SnmpAgent service, right-click, and choose Startup Mode > Disable to disable
the process.
Step 4 On the System Monitor client, if Startup Mode of the related service of the SNMP NBI is
Disabled, it indicates that the operation is successful.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 76

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

----End

8.2.4 Restarting the SNMP NBI

When the SNMP interface service is in the stopped state, you can restart the service in the
System monitor client.

Prerequisites
l Log in to the Solaris or Linux OS as user ossuser.
l Log in to the Windows OS as user Administrator.
l The U2000 must be operating.
l The SnmpAgent Service is in the Stopped state.

Procedure
Step 1 Log in to the System Monitor.

Step 2 On the System Monitor, enter the Service Monitor tab.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 77

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

Step 3 Select the SnmpAgent service, right-click, and then choose Start the Service from the
shortcut menu.
Step 4 In the System Monitor client, when Status of the relevant SNMP service, namely SNMP
Service are Running, the operation is successful.

----End

8.3 Faults and Solutions

This section introduces the faults of the SNMP NBI and the related solutions.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 78

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

8.3.1 SNMP Service Process Is Not Displayed

Symptom
After the SNMP NBI is deployed, the SNMP Service process is not displayed on the System
Monitor client.

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 5.4 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

8.3.2 SNMP Service Process Fails to Be Started

Symptom
After the SNMP NBI is configured, the SNMP service process fails to be started.

Possible Causes
Port 9812 for configuring the SNMP NBI is occupied by other processes.
The V3 User is blank when use the SNMP v3.

NOTICE
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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 79

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

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.

Table 8-1 Service ports of an SNMP NBI

Service Name Serving Port/ Direction (with Description

Protocol Type the Server as the
Reference Object)

SnmpAgent 6666/UDP OUT SNMP trap sending

SnmpAgent 9812/UDP IN SNMP trap

receiving

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 Choose Configure SNMP > General Config from the navigation tree on the left.

Step 4 View Third-party NMS in the General area. Check whether the V3 user is blank. If it is
blank, input the correct value, then deploy the SNMP NBI.

----End

8.3.3 NMS User Cannot Connect to the SNMP NBI

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.

Version Communication Parameters

SNMPv1 and l Receive Request from NMS address/port

SNMPv2 l SNMP version
l Read community
l Write community

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 80

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

Version Communication Parameters

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 firewall blocks the communication between the request transmit port on the OSS
and the request receive port on the U2000.

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, see8.3.1 SNMP Service Process Is Not
Displayed.
l If the SNMP Service process cannot be started, see 8.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

8.3.4 The OSS Cannot Receive Heartbeat Information

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 NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP > General Config from the navigation tree on the left.

Step 3 Check whether the loaded MIB meets the requirements:

In the Advanced area and check whether MIB Frame is set to U2000 MIB. If no, change it
to U2000 MIB and then reconfigure the SNMP NBI.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 81

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

Step 4 Check whether the heartbeat function is disabled:

In the Advanced area and check whether Report Heartbeat Info is set to Yes. If no, change
it to Yes and then reconfigure the SNMP NBI.

----End

8.3.5 OSS Cannot Receive Real-Time Alarms

Symptom
The OSS cannot receive real-time alarms.

Possible Causes
l The following parameters are incorrect when the SNMP NBI is deployed.
Send Trap address/port in SNMP Agent
NMS receive Trap address/port in Third-part NMS
l The request transmit port on the OSS and the request receive port on the U2000 are
disabled on the firewall, so they cannot communicate with other.
The request transmit port on the OSS is 6666 by default.
The request receive port on the U2000 is 6666 by default.

Procedure
Step 1 After confirming the previous parameters with OSS engineers, log in to the NBI Config Tools
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

8.3.6 Acknowledge or Un-acknowledge or Clear Alarms Fails

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 82

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

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 NBI Config Tools.
2. Choose Configure SNMP > General Config from the navigation tree on the left.
3. In Advanced area, view whether the MIB Frame 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

8.3.7 How to configure the heartbeat notification trap to

hwNmNorthboundKeepAlive

Question
By default, the heartbeat notification trap reports the hwNMAgent field. You can make
modifications for the trap to report the hwNmNorthboundKeepAlive field. How to configure
the heartbeat notification trap to hwNmNorthboundKeepAlive?

Answer
Step 1 Log in to NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP NBI > Custom Configuration from the navigation tree on the
left.

Step 3 Select KeepAliveVBOID from the Configuration Item Name drop-down list, set
Configuration Item Value to 1.3.6.1.4.1.2011.2.15.1.7.2.1. To report the default field
hwNmAgent, set Configuration Item Value to 1.3.6.1.4.1.2011.2.15.1.

Step 4 Restart the SNMP NBI by system monitor client.

----End

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 83

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

8.3.8 How to configure T2000Support item

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
Step 1 Log in to NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP NBI > Custom Configuration from the navigation tree on the
left.

Step 3 Select T2000Support from the Configuration Item Name drop-down list, and set
Configuration Item Value. Select 1 when managing transport optical NEs. Select 0 when
managing cross-domain NEs. The default value is 1.

Step 4 Restart the SNMP NBI by system monitor client.

----End

8.3.9 How to report the event alarm

Question
By default, the SNMP NBI cannot report the event alarm. How to enable the event alarm
report function?

NOTICE
The SNMP NBI in distributed U2000 cannot report events.

Answer
The OSS can change the filter criteria in real time. For details, see 7.1.2 Changing Filter
Criteria.

Step 1 Log in to NBI Config Tools. For details, see 5.5 Logging in to NBI Config Tools.

Step 2 Choose Configure SNMP NBI > Custom Configuration from the navigation tree on the
left.

Step 3 Select event.* from the Configuration Item Name drop-down list, where * indicates the
sequence number (1-10) of the OSS. Set Configuration Item Value to 1, which indicates that
the SNMP NBI will report event alarms to the OSS. The default value is 0.

Step 4 Restart the SNMP NBI by system monitor client.

----End

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 84

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

8.3.10 How to Disable Password Complexity Checks for Read and

Write Communities

Question
The passwords of the SNMP read and write communities must meet certain complexity
requirements. If you want to use simple passwords, you can disable the password complexity
check function in the configuration file.

NOTICE
To ensure the security of your system, passwords must be complex enough. Exercise
cautiously when you want to disable the password complexity check function.

Answer
Step 1 Change the value of the enableComplexityChecking configuration item in the
$IMAP_ROOT/etc/oss_cfg/nbi/snmp/tools.cfg file to FALSE.
1. Run the following command to open the editor. $ vi /opt/oss/server/etc/
oss_cfg/nbi/snmp/tools.cfg
2. Edit the server/nbi/snmp/bin/tools.cfg file. Move the cursor in the editor by typing the
key, h for left, l for right, k for up, j for down. Move until you find
enableComplexityChecking. Then change its value to FALSE.
3. Type key : to enter the command mode, and then type two keys wq to save and exit the
editor.

Step 2 Re-open the SNMP NBI deployment window.

----End

8.3.11 How to Configure SupportOldGroupID for MxUs

Question
The GroupID of MxUs can be represented in two modes. How can I modify the representation
mode of the GroupID?

Answer
Step 1 Log in to the OS of the U2000 server.

Step 2 Modify the configuration file $IMAP_ROOT/etc/nbi/snmp/snmpagent.xml.

The default value is 0, which indicates that the new GroupID representation mode is used. Set
the value of the SupportOldGroupID configuration item to 1, which indicates that the old
GroupID representation mode is used. The following uses the MA5616 as an example to
show the two representation modes.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 85

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 8 Maintaining the SNMP NBI

NE Type New Mode Old Mode

MA5616 59 71

<param name="SupportOldGroupID">0</param>

Step 3 Restart the SNMP NBI by system monitor client.

----End

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 86

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 9 Replacing the Certificate of the NBI Config Tools

9 Replacing the Certificate of the NBI Config

Tools

U2000 provides a default security certificate for encryption and authentication. It is

recommended that customers replace the default certificate with their security certificate.
Specifically, apply for a security certificate from a trusted CA and then use the certificate to
replace the original SSL certificate of the NBI Config Tools.

Windows OS
1. Log in to the server where the NBI Config Tools resides.
2. Back up the original certificate keystore.jks on the server. For example, copy the
keystore.jks file and rename it as keystore.jks_bak.
3. Copy the new certificate to the original certificate path to replace the keystore.jks
certificate. The name of the new certificate must be changed to keystore.jks.
4. Go to the encryption tool directory, and run the GenerateNBPass.bat -e command to
encrypt the certificate password.
After the following information is displayed, enter N:
check complexity of password or not(Y/N,default is 'Y',need check and suggest
this. if enter 'N', then will not check.):

Enter the initial password to be encrypted for two consecutive times.

$ enter password:
$ re-enter password:

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 87

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 9 Replacing the Certificate of the NBI Config Tools

NOTICE
To ensure the security of the U2000, remember to change the default passwords of
U2000 and update the passwords regularly, passwords must be complex enough.
The password must meet the following requirements to safeguard your user account.
1. It is a character string consisting of 8 to 18 characters.
2. Not be the same as or the reverse of the user name.
3. It contains at least three types of the following characters:
l Lowercase letter: a-z
l Uppercase letter: A-Z
l Digit: 0-9
l Special character: =~@#^*-_+[{}]:./;?.
4. On UNIX or Linux OS, if a pound key (#) is used as the first character of the
password, you need to add a slash (\) before the pound key.

The ciphertext after encryption is returned:

Encrypt password result: b273290137C725168F52F3D7E1EA8670

5. Add the encrypted password to the KeyStorePassword configuration item.

The configuration file path is server\etc\oss_cfg\nbi\configtool\conf
\config.properties.
The configuration item name is KeyStorePassword.
6. Restart the NBI Config Tools process nbi_configtools on the System Monitor client.

Linux/Solaris OS
1. Log in to the server where the NBI Config Tools resides as the ossuser user.
2. Run the following commands to back up the original certificate keystore.jks on the
server:
$ cd $OSS_ROOT/server/etc/ssl/nbi/configtool/certificate
$ cp keystore.jks keystore.jks_bak

3. Copy the new certificate to the original certificate path to replace the keystore.jks
certificate. The name of the new certificate must be changed to keystore.jks.
4. Go to the encryption tool directory, and run the following commands to encrypt the
certificate password:
$ cd $OSS_ROOT/server/nbi/tools/encrypt
$ ./GenerateNBPass -e

After the following information is displayed, enter N:

check complexity of password or not(Y/N,default is 'Y',need check and suggest
this. if enter 'N', then will not check.):

Enter the initial password to be encrypted for two consecutive times.

$ enter password:
$ re-enter password:

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 88

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 9 Replacing the Certificate of the NBI Config Tools

The ciphertext after encryption is returned:

Encrypt password result: b273290137C725168F52F3D7E1EA8670

5. Add the encrypted password to the KeyStorePassword configuration item.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 89

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 10 Revoking the Certificate of the NBI Config Tools

10 Revoking the Certificate of the NBI

Config Tools

This topic describes how to revoke the SSL certificate of the U2000 NBI Config Tools.

Windows OS
1. Log in to the server where the NBI Config Tools resides.
2. Modify the server/etc/oss_cfg/nbi/configtool/conf/config.properties file by adding the
path and name of the certificate to be revoked to the CRLFile configuration item. By
default, the CRLFile configuration item is left blank. To revoke a certificate, enter the
correct path and name of the certificate to be revoked.

3. Copy the CRL file huaweiossCA.crl to the server/etc/ssl/nbi/configtool/certificate

directory.
4. Restart the NBI Config Tools process nbi_configtools on the System Monitor client.

Linux/Solaris OS
1. Log in to the server where the NBI Config Tools resides as the ossuser user.
2. Use the vi editor to modify the server/etc/oss_cfg/nbi/configtool/conf/
config.properties file by adding the path and name of the certificate to be revoked to the
CRLFile configuration item. By default, the CRLFile configuration item is left blank.
To revoke a certificate, enter the correct path and name of the certificate to be revoked.

3. Use FTP as the ossuser user to upload the CRL file huaweiossCA.crl to the
$OSS_ROOT/server/etc/ssl/nbi/configtool/certificate directory.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 90

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide 10 Revoking the Certificate of the NBI Config Tools

4. Change the permission of the certificate to be revoked to 600.

$ cd $OSS_ROOT/server/etc/ssl/nbi/configtool/certificate
$ chmod 600 huaweiossCA.crl
5. Restart the NBI Config Tools process nbi_configtools on the System Monitor client.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 91

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide A Relations Between License and SNMP Interface

A Relations Between License and SNMP

Interface

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.
For details of Dimension, refer to Figure A-1 and Table A-1.

Figure A-1 Main dimensions

y
ci t
a pa
tC
technical domain

m en
ge
ana
M

Interface Function

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 92

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide A Relations Between License and SNMP Interface

Table A-1 Description for Dimension

Dimension Meaning

Interface function Alarm

Technical domain l Transmission Network

l IP
l Access Network

Management capacity Controls NEs. The unit is number of equivalent NEs.

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.

Table A-2 Description for License Item

License Control Item Abbreviation Value

Per Equivalent NE License LNSDPENES01 0-500000

for NBI-SNMP Alarm-
Transmission Network

Per Equivalent NE License LNSDPENES02 0-500000

for NBI-SNMP Alarm -IP

Per Narrowband Port LNSDPENEC21 0~8000000

License for NBI-SNMP
Alarm-Access Network

Per Broadband Port License LNSDPENEC25 0~8000000

for NBI-SNMP Alarm-
Access Network

Per PON Terminal Resource LNSDNELCR84 0~8000000

License for NBI-SNMP
Alarm-Access Network

Compatible License for LNSDNELCR75 0~8000000

SNMP Alarm NBI-Access
Network

Per CMC NE Resource LNSDPENEC48 0~8000000

License for NBI-SNMP
Alarm-Access Network

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 93

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide A Relations Between License and SNMP Interface

License Control Item Abbreviation Value

NBI-SNMP Management LNSDNSMFC01 0~8000000

Function Component For
Non-Port Service-Access
Network

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 94

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

B Configuration Parameters

The U2000 can connect to the NMS/OSS after you correctly set general parameters by using
the NBI Config Tools. You can also set advanced parameters to customize the messages
queried or reported through the SNMP NBI.

B.1 General Parameters

The SNMP NBI runs on the U2000. It receives requests from the OSS, performs required
operations on the U2000, and reports alarms to the OSS in real time. General parameters for
the SNMP BNI include the trap-transmitting IP address or port, request-receiving IP address
or port, and SNMP version.
B.2 Advanced Configuration
You can set the advanced parameters for the SNMP NBI through NBI Config Tools.
B.3 Third-Party NMS
The third-party NMS refers to the NMS (also called SNMP manager) in the SNMP protocol.
For the SNMP NBI, the third-party NMS functions as the OSS. The third-party NMS sends
requests to the SNMP agent, receives responses or traps from the SNMP agent, parses these
packets, and displays the result.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 95

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

B.1 General Parameters

Navigation Path
Choose Configure SNMP > General Config from the navigation tree on the left.

Parameters

NOTICE
The trap sending address and request receiving 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.

Parameter Value Description

SNMP Agent

Address for Sending IP addresses except 127.0.0.1 Specifies the IP address on the
Trap Default: IP address of the SNMP agent for sending traps
U2000 server to 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 1 to 65535 Specifies the port for sending

Default: 6666 traps.
Recommended value: 1025 to
32767

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 96

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Parameter Value Description

Address for IP addresses except 127.0.0.1 Specifies the IP address for

Receiving NMS Default: IP address of the receiving requests from the
Request U2000 server OSS.
On the U2000 with multiple
NICs, set an IP address for
successful communication
between the U2000 and the
OSS.

Port 1 to 65535 Specifies the port for receiving

Default: 9812 requests from the OSS.
Recommended value: 1025 to
32767

SNMPv3 Parameters

Security Model USM model Specifies the security model of

the SNMPv3 protocol.
USM: User-based Security
Mechanism

Security Level Without authentication and Specifies the security level of

encryption, With authentication, the SNMPv3 protocol.
Without encryption, With
authentication and encryption
Default: With authentication
and encryption

Authentication HMACMD5, HMACSHA Specifies the authentication

Default: HMACSHA protocol in SNMPv3. The value
of this parameter must be
consistent with that on the OSS.
The options are as follows:
l MD5: Message Digest
(Version 5)
l SHA: Secure Hash
Algorithm
NOTICE
It is recommended that the OSS
use the securer SHA algorithm.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 97

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Parameter Value Description

Data Encryption DES, AES Specifies the data encryption

Default: AES protocol in SNMPv3. The value
of this parameter must be
consistent with that on the OSS.
The options are as follows:
l DES: Data Encryption
Standard
l AES: Advanced Encryption
Standard
NOTICE
It is recommended that the OSS
use the securer AES algorithm.

B.2 Advanced Configuration

You can set the advanced parameters for the SNMP NBI through NBI Config Tools.

Navigation Path
Choose Configure SNMP > General Config from the navigation tree on the left.

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.

NOTE

There is no heartbeat information for the U2000-T MIB.

Parameters Value Description

Heartbeat Interval Default: 60s Specifies the heartbeat period of the third-
3s-300s party NMS.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 98

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Parameters Value Description

Heartbeat Default: Enable Specifies whether send the heartbeat

Reporting Enable, Disable information to the third-party NMS.

Time Format
The data format for reported alarm information can be set on the OSS. Currently the universal
time coordinated (UTC) format and local time format are supported.

Parameter Value Description

Alarm Default: UTC Indicates the format of the alarm time.

Time Time UTC Time
Format UTC Time, The format is as YYYY/MM/DD - hh:mm:ssZ.
Local Time
(without Time Example: 2009/12/23 - 11:30:30Z
Zone), Local Local Time (without Time Zone)
Time (with Time The format is as YYYY/MM/DD - hh:mm:ss.
Zone)
Example: 2009/12/23 - 19:30:30
Local Time (with Time Zone)
The format is as YYYY/MM/DD -
hh:mm:ss,hh:mmTZ[DST], where TZ stands for
timezone information.
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.

Alarm Correlation
Cause analysis indicates that some alarms are triggered by the root alarm. Report all alarms or
only the root alarm as required.

Parameter Value Description

Alarm Default: All All: Queries and reports all alarms including the root alarm
Correlation Root and correlative alarms.
Root: Queries and reports only the root alarm and common
alarms.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 99

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Engineering Alarm
During engineering commissioning or service cutover, a large number of alarms are generated
on NEs. If you set the NEs in engineering maintenance state, generated alarms are displayed
as engineering alarms. You can specify whether to report the engineering alarms. You must
restart the server if you have changed the configuration of engineering alarm.

Parameters Value Description

Filter Out Default: Disable Specifies whether to report the

Engineering Enable, Disable engineering alarms. You must
Alarms restart the server if you have
changed the configuration of
engineering alarm.
l Disable: specifies that all alarms
are queried and reported.
l Enable: specifies that all alarms
except for engineering alarms
are queried and reported.

Encoding Format
The NMS/OSS can set the encoding format of the reported alarms according to requirement.
The SNMP NBI support UTF-8 and GBK currently.

Parameters Value Description

Alarm Default: UTF-8 There are two types of alarm

Encoding UTF-8, GBK coding as follows: UTF-8, GBK.
Format

Log and Cache

Parameters Value Description

Logging Default: Specifies whether alarms are recorded in logs.

Disable
Enable,
Disable

Active-Alarm Cache Default: Specifies the cache for real-time alarms. Each
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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 100

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Notification
You can set the reported mode and the relevant parameters.

CAUTION
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.

Parameter Description Value

Reporting Mode Default: Trap Specifies the mode used by the SNMP
Trap, Inform agent for sending alarms to the OSS.

Support X.733 Default: No Specifies whether traps use the event types
Alarms 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.

Trap Sending Default: 0 Specifies the time interval for sending

Interval 0 ms-1000 ms messages in Trap mode.

Inform Delay Default: 5 Indicates the interval between two attempts

5 s - 120 s to send information in inform mode. The
second attempt is performed if the OSS
does not respond.

Max. Inform Default: 3 Indicates attempts to resend information

Retries 2 times-6 times when the OSS does not respond in inform
mode.

MIB Frame
The correct MIB frame must be set when the SNMP NBI is deployed. This ensures that the
OSS connects to the U2000 for alarm management.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 101

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

NOTICE
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.

Three MIB files are supported:

l T2000-NETMANAGEMENT-MIB.mib (U2000-T MIB)
l HW-IMAPV1NORTHBOUND-TRAP-MIB.mib and HW-IMAPV2NORTHBOUND-
TRAP-MIB.mib (U2000 MIB)
Parameter Value Description
s

MIB U2000 MIB, U2000 MIB: If the MIB file HW-

U2000-T IMAPV1NORTHBOUND-TRAP-MIB.mib or HW-
MIB IMAPV2NORTHBOUND-TRAP-MIB.mib is loaded on
the OSS, select U2000 MIB.
l For details of the alarm fields (VB) of U2000 MIB, see
C.2 Alarm Fields Reported By the U2000 MIB.
l It is recommended if the U2000 manages multi-domain
equipment.
U2000-T MIB: If the MIB file T2000-
NETMANAGEMENT-MIB.mib is loaded on the OSS,
select U2000-T MIB.
l For details of the alarm fields (VB) of U2000-T MIB,
see D.2 Reported Alarm Field by U2000-T MIB.
l Only transport NEs are supported. The U2000-T MIB is
used for upgrades at some sites.

Alarm Field
The reported alarm field, also called bound variable (VB), specifies the alarm information to
be reported through the SNMP NBI.

NOTICE
This parameter is applicable to the U2000 MIB only.
This parameter is applicable to all third-party NMSs connected to the SNMP NBI.
The U2000 automatically fills the alarm field and the alarm field is not support manual
setting.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 102

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Table B-1 T2000Support=0

Name Name in the Description Value Parse
MIB Supporte
d

NE hwNmNorthb Indicates the name of the NE where Octet No

Name oundNENam an alarm is generated. string
e l For alarms generated on an NE,
the NE name is reported.
l For alarms generated due to NE
disconnection, the NE name is
reported. For example, if alarms
are generated due to NE login
failures or NE disconnection,
the NE name is reported.
l If alarms are generated on a
WDM NE that is mounted to an
optical NE, the name of the
optical NE is reported.
l For other NMS alarms, the
NMS name is reported. By
default, OSS is reported. If the
NMS name is changed, the
name of the changed NMS is
reported.

NE Type hwNmNorthb Indicates the type of the NE on Octet No

oundNEType which alarms are generated. For string
NMS alarms, the NMS name is
reported.

Object hwNmNorthb Indicates location information. For Octet No

instance oundObjectIn details, see Table C-3. string
stance

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 103

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Name Name in the Description Value Parse

MIB Supporte
d

Event hwNmNorthb Indicates the alarm type. For non- Octet Yes. See
Type oundEventTy X.733-compliant alarms, options string the
pe are as follows: enumerate
l Environment d value.
l Equipment
l Communication
l Service
l Process
l Security
For X.733-compliant alarms,
options are as follows:
l EnvironmentalAlarm
l EquipmentAlarm
l CommunicationsAlarm
l QualityofServiceAlarm
l ProcessingErrorAlarm
l SecurityAlarm

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 104

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Name Name in the Description Value Parse

MIB Supporte
d

Alarm hwNmNorthb Indicates the time at which an Octet Yes. See

Occurren oundEventTi alarm is generated, cleared, string the time
ce Time me acknowledged, unacknowledged, format.
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.
l If an alarm is unacknowledged,
this parameter indicates the time
at which the alarm is
unacknowledged.
l If an alarm is changed, this
parameter indicates the time at
which the alarm is changed.
The options can be in either of the
following formats:
l UTC Time. The format is as
YYYY/MM/DD - hh:mm:ssZ.
Example: 2009/12/23 -
11:30:30Z
l Local Time without timezone
information. The format is as
YYYY/MM/DD - hh:mm:ss.
Example: 2009/12/23 -
19:30:30
l Local Time with timezone
information. The format is as
YYYY/MM/DD - hh:mm:ss,
hh:mmTZ[DST], where TZ
stands for timezone
information. Example:
2009/12/23 - 19:30:30,
+08:00[0]. (If the date is not
in DST.)
2009/12/23 - 19:30:30
+08:00[3600]. (If the date is
in DST of one hour. The

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 105

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Name Name in the Description Value Parse

MIB Supporte
d

DST value is represented in

seconds.)

Alarm hwNmNorthb Indicates possible causes for an Octet No

Cause oundProbable alarm. string
Cause Format: ID:[Alarm
ID],DeviceType:[DeviceType
ID],Alarm Cause

Alarm hwNmNorthb Indicates alarm severity. Octet Yes. See

Severity oundSeverity l Critical string the
enumerate
l Major d value.
l Minor
l Warning
l Cleared: This option is
supported for X.733-compliant
alarms.

Alarm hwNmNorthb Indicates the ID, device type, and Octet No

Details oundEventDe details of an alarm. string
tail Format: ID:
[AlarmID],DeviceType:
[DeviceType ID],Alarm Details

Alarm hwNmNorthb Indicates the specific location of Octet No

Location oundAddition the equipment where an alarm is string
alInfo generated.

Type hwNmNorthb Indicates the alarm type. Options Octet Yes. See
Flag oundFaultFla are as follows: string the
g l Event: indicates that an event is enumerate
generated. d value.
l Fault: indicates that an alarm is
generated.
l Recovery: indicates that the trap
is alarm recovery.
l Acknowledge: indicates that the
alarm is acknowledged.
l Unacknowledge: indicates that
the alarm is unacknowledged.
l Change: indicates that the alarm
is changed.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 106

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Name Name in the Description Value Parse

MIB Supporte
d

Alarm hwNmNorthb Indicates the alarm type based on Octet Yes. See
Function oundFaultFun functions, as same as string the
Category ction hwNmNorthboundEventType. enumerate
d value.

Managed hwNmNorthb Indicates the IP address of the IP address No

Equipme oundDeviceI equipment.
nt P l For transport NEs,
Address
It is the IP address of the NE
for GNEs.
It is 0.0.0.0 for non-GNEs.
l For other NEs, it is the IP
address of the NE.
l For NMS alarms, it is the IP
address of the NMS.

Alarm hwNmNorthb Indicates the serial number of an Integer No

Serial oundSerialNo alarm.
Number

Alarm hwNmNorthb Indicates advice for alarm recovery. Octet No

Recover oundProbable Format: ID: string
y Advice Repair [AlarmID],DeviceType:
[DeviceType ID],Alarm Recovery
Advice

Resource hwNmNorthb Indicates the ID of the resource Octet No

ID oundResourc where an alarm is generated. string
eIDs

Event hwNmNorthb Indicates the name of an alarm. Octet No

Name oundEventNa Format: ID: string
me [AlarmID],DeviceType:
[DeviceType ID],Event Name

Alarm hwNmNorthb Indicates the alarm ID. Integer No

Cause ID oundReasonI
D

Alarm hwNmNorthb Indicates the fault ID. Integer No

ID oundFaultID

Managed hwNmNorthb Indicates the managed equipment Octet No

Equipme oundDeviceT type. string
nt Type ype

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 107

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Name Name in the Description Value Parse

MIB Supporte
d

Trail hwNmNorthb Indicates the name of the trail Octet No

Name oundTrailNa affected by an alarm. If alarm A string
me affects a trail, a new changed alarm
B will generate. Its serial number is
as same as alarm A. The severity of
alarm B is Change. Trail Name in
alarm B indicates the affected trail.
However, for alarm A, Trail Name
is blank.
l It is applicable for transport and
IP NEs.
l It is always blank for access
NEs.

Root hwNmNorthb Specifies whether the alarm is a Integer Yes. See

Alarm oundRootAla root alarm or not. Options are as the
rm follows: enumerate
l 0: Non-root alarm d value.
l 1: Root alarm

Group hwNmNorthb Indicates the ID of the alarm group. Integer No

ID oundGroupID l For transport and IP NEs, the
alarm group ID and the alarm
ID uniquely identify a static
alarm.
l For access NEs, the alarm group
ID, alarm ID, and the alarm
cause ID uniquely identify a
static alarm.

Engineer hwNmNorthb Specifies whether this alarm is Integer Yes. See

ing oundMaintain generated by the NE in the the
Alarm Status engineering maintenance state. enumerate
Status Maintenance engineers can focus d value.
on engineering alarms selectively.
l 0: Non-engineering alarms
l 1: Engineering alarms
NOTE
NEs during engineering
commissioning or service cutover
generate a large number of alarms, and
you can set the NEs in engineering
maintenance state. Therefore, the
alarms generated by this kind of NE
are engineering alarms.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 108

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Name Name in the Description Value Parse

MIB Supporte
d

Root hwNmNorthb Indicates the log serial number of Octet No

Alarm oundRootAla root alarm. string
Serial rmSerialNo
Number

Alarm hwNmNorthb Indicates the alarm Integer Yes. See

Acknowl oundConfirm acknowledgement status. the
edgemen Status l 1: acknowledged enumerate
t Status d value.
l 2: unacknowledged

Alarm hwNmNorthb Indicates the alarm clearance Integer Yes. See

Clearanc oundRestoreS status. the
e Status tatus l 1: cleared enumerate
d value.
l 2: uncleared

B.3 Third-Party NMS

The third-party NMS refers to the NMS (also called SNMP manager) in the SNMP protocol.
For the SNMP NBI, the third-party NMS functions as the OSS. The third-party NMS sends
requests to the SNMP agent, receives responses or traps from the SNMP agent, parses these
packets, and displays the result.

Parameters
NOTE

The Receiving/Sending Address is not the IP address of the U2000 server but the IP address of a third-
party NMS of the upper layer. If the third-party NMS uses two servers to receive traps and send
requests, the IP addresses for these two servers must be configured respectively.
Currently a maximum of 10 third-party NMSs are supported. The following table lists the configuration
requirements for third-party NMSs.

MIB SNMP Configuration Requirements

Type Version

U2000 v1/v2c You are advised to set different read and write community names for
MIB third-party NMSs. If multiple third-party NMSs (for example, NMS 1
and NMS 2) use the same read and write community names, ensure
that the SNMP protocol versions used by the NMSs are the same.

v3 You are advised to set different user names for third-party NMSs. If
multiple third-party NMSs (for example, NMS 1 and NMS 2) use the
same user name, the same authentication password or encryption
password must be set for all the NMSs.

U2000-T v1/v2c You are advised to set different read and write community names for
MIB third-party NMSs.

v3 You are advised to set different user names for third-party NMSs.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 109

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

NOTICE
To ensure the security of the U2000, remember to change the default passwords of U2000 and
update the passwords regularly, passwords must be complex enough.
The password must meet the following requirements to safeguard your user account.
1. It is a character string consisting of 8 to 16 characters.
2. It contains at least four types of the following characters:
l Lowercase letter: a-z
l Uppercase letter: A-Z
l Digit: 09
l Special character: ` ~ ! @ # $ % ^ & * ( ) - _ = + \ | [ { } ] ; : ' " , < . > / ? or space.

Parameters Value Description

Receiving/ IP address Indicates the IP address of the third-party NMS

Sending or the IP address for the OSS to communicate
Address with the U2000 server.

Port Default: 6666 Specifies the port of the third-party NMS for
1 to 65535 receiving traps.
NOTE
l When the U2000 is interconnected with the OSS,
enter the port provided by the upper layer NMS
that receives traps or sends requests.
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.

SNMP version v1, v2c, v3 The SNMP NBIU2000 support three SNMP
Default: v3 protocol versions: SNMPv1, SNMPv2c, and
SNMPv3.

Read Default When the third-party NMS uses the SNMPv1 or

Community l Read Community: SNMPv2c protocol, the authentication control
Changeme_123 between the SNMP agent and the OSS is
implemented through community information.
l Write Community:
Changeme_123 The SNMP agent responds to operations
(including querying, acknowledging,
unacknowledging, and clearing alarms) only
when the read and write communities are the
same as those on the OSS; otherwise, operation
requests are ignored.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 110

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Parameters Value Description

Write Default When the third-party NMS uses the SNMPv1 or

Community l Write Community: SNMPv2c protocol, the authentication control
Changeme_123 between the SNMP agent and the OSS is
implemented through community information.
You can also enter any
character string The SNMP agent responds to operations
consisting of 255 (including querying, acknowledging,
characters at most. unacknowledging, and clearing alarms) only
when the read and write communities are the
same as those on the OSS; otherwise, operation
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.

v3 The default password Indicates the password for authenticating the

Authentication is Changeme_123. OSS when the OSS visits the SNMP agent.
Password If the security level is set to With
authentication, without encryption or With
authentication and encryption, set encryption
policy of the password.

v3 Privacy The default password Indicates the password for encrypting data when
Password is Changeme_123. the OSS visits the SNMP agent.
If the security level is set to With
authentication and encryption, set encryption
policy of the password.

Alarm Default: All Specifies the severity of reported alarms.

Severity Critical, Major, Minor,
Warning

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 111

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide B Configuration Parameters

Parameters Value Description

Alarm Default: Fault Specifies the category of reported alarms.

Category Fault, Acknowledge, l Fault: Specifies whether to report alarm
Unacknowledged, generation and alarm clearance. After this
Changed check box is selected, 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.
l Acknowledge/Unacknowledged: Indicates
the SNMP NBI will report the alarm if its
acknowledge status is changed.
l Changed: Indicates the SNMP NBI will
report changed information of the alarm,
include severity, affected trail and root
alarm.
NOTE
Event alarm reporting is disabled by default and
cannot be configured by using the NBI Config Tools.
But you can enable this function by following
methods.
l You can enable event alarm function manually.
For details, see 8.3.9 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.
For details about the thirdNMSFaultFilter
subinterface, see 7.1.2 Changing Filter
Criteria.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 112

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.
The U2000 MIB has two versions: HW-IMAPV1NORTHBOUND-TRAP-MIB and HW-
IMAPV2NORTHBOUND-TRAP-MIB. The OSS selects a version based on its supported
SMI version.
This document uses HW-IMAPV1NORTHBOUND-TRAP-MIB as an example.

SMI Version MIB

SMI-V1 HW-IMAPV1NORTHBOUND-TRAP-MIB.mib

SMI-V2 HW-IMAPV2NORTHBOUND-TRAP-MIB.mib

C.1 MIB Description

C.2 Alarm Fields Reported By the U2000 MIB
U2000 MIB supports 21 alarm fields. You can customize the alarm fields as required.
C.3 U2000 MIB Trap
C.4 U2000 MIB Trap Sample
There are five traps supported by U2000 MIB: active alarm trap, active alarm synchronization
start trap, active alarm synchronization result trap, active alarm synchronization stop trap, and
heartbeat trap. The samples in this topic use SNMPv1 as an example. SNMPv2c and SNMPv3
are similar to SNMPv1.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 113

C.1 MIB Description

The complete HW-IMAPV1NORTHBOUND-TRAP-MIB MIB node information is:
iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).hwNetManagement(15).hwNmAgent(1)

The MIB tree showed as follows:

--- huawei(2011)
|--- products(2)
|--- hwNetManagement(15)
|--- hwNmAgent(1)
|---- hwNmFault(3)

hwNmFault defines the SNMP NBI.

For the function interface of U2000 MIB, see 7.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.

C.2 Alarm Fields Reported By the U2000 MIB

U2000 MIB supports 21 alarm fields. You can customize the alarm fields as required.
When the MIB frame is set to U2000 MIB, the SNMP NBI reports the following alarm fields.
You can customize them as required.

T2000Support=0
Table C-1 shows the reported details of the SNMP NBI if T2000Support is 0.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 114

Table C-1 T2000Support=0

Name Name in the Description Value Parse
MIB Supporte
d

NE hwNmNorthb Indicates the name of the NE where Octet No

NE Type hwNmNorthb Indicates the type of the NE on Octet No

oundNEType which alarms are generated. For string
NMS alarms, the NMS name is
reported.

Object hwNmNorthb Indicates location information. For Octet No

instance oundObjectIn details, see Table C-3. string
stance

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 115

Name Name in the Description Value Parse

MIB Supporte
d

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 116

Name Name in the Description Value Parse

MIB Supporte
d

Alarm hwNmNorthb Indicates the time at which an Octet Yes. See

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 117

Name Name in the Description Value Parse

MIB Supporte
d

DST value is represented in

seconds.)

Alarm hwNmNorthb Indicates possible causes for an Octet No

Cause oundProbable alarm. string
Cause Format: ID:[Alarm
ID],DeviceType:[DeviceType
ID],Alarm Cause

Alarm hwNmNorthb Indicates alarm severity. Octet Yes. See

Severity oundSeverity l Critical string the
enumerate
l Major d value.
l Minor
l Warning
l Cleared: This option is
supported for X.733-compliant
alarms.

Alarm hwNmNorthb Indicates the ID, device type, and Octet No

Details oundEventDe details of an alarm. string
tail Format: ID:
[AlarmID],DeviceType:
[DeviceType ID],Alarm Details

Alarm hwNmNorthb Indicates the specific location of Octet No

Location oundAddition the equipment where an alarm is string
alInfo generated.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 118

Name Name in the Description Value Parse

MIB Supporte
d

Alarm hwNmNorthb Indicates the alarm type based on Octet Yes. See
Function oundFaultFun functions, as same as string the
Category ction hwNmNorthboundEventType. enumerate
d value.

Managed hwNmNorthb Indicates the IP address of the IP address No

Alarm hwNmNorthb Indicates the serial number of an Integer No

Serial oundSerialNo alarm.
Number

Alarm hwNmNorthb Indicates advice for alarm recovery. Octet No

Recover oundProbable Format: ID: string
y Advice Repair [AlarmID],DeviceType:
[DeviceType ID],Alarm Recovery
Advice

Resource hwNmNorthb Indicates the ID of the resource Octet No

ID oundResourc where an alarm is generated. string
eIDs

Event hwNmNorthb Indicates the name of an alarm. Octet No

Name oundEventNa Format: ID: string
me [AlarmID],DeviceType:
[DeviceType ID],Event Name

Alarm hwNmNorthb Indicates the alarm ID. Integer No

Cause ID oundReasonI
D

Alarm hwNmNorthb Indicates the fault ID. Integer No

ID oundFaultID

Managed hwNmNorthb Indicates the managed equipment Octet No

Equipme oundDeviceT type. string
nt Type ype

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 119

Name Name in the Description Value Parse

MIB Supporte
d

Trail hwNmNorthb Indicates the name of the trail Octet No

Root hwNmNorthb Specifies whether the alarm is a Integer Yes. See

Alarm oundRootAla root alarm or not. Options are as the
rm follows: enumerate
l 0: Non-root alarm d value.
l 1: Root alarm

Group hwNmNorthb Indicates the ID of the alarm group. Integer No

Engineer hwNmNorthb Specifies whether this alarm is Integer Yes. See

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 120

Name Name in the Description Value Parse

MIB Supporte
d

Root hwNmNorthb Indicates the log serial number of Octet No

Alarm oundRootAla root alarm. string
Serial rmSerialNo
Number

Alarm hwNmNorthb Indicates the alarm Integer Yes. See

Acknowl oundConfirm acknowledgement status. the
edgemen Status l 1: acknowledged enumerate
t Status d value.
l 2: unacknowledged

Alarm hwNmNorthb Indicates the alarm clearance Integer Yes. See

Clearanc oundRestoreS status. the
e Status tatus l 1: cleared enumerate
d value.
l 2: uncleared

T2000Support=1
If T2000Support is 1. the Table C-2 shows the reported details of the SNMP NBI

Table C-2 T2000Support=1

Name Name in the MIB Description

Object hwNmNorthboundO Format: source=[NE Name] location=[location

instance bjectInstance information]
source indicates the alarm source, and location
indicates the location information.
The above rule is supported for transport, access
and IP NEs.
Example: source=CE1-test-1 location=User
Name=VTY User IP=10.78.224.206 User
Channel=VTY4 Serial Number:649018

Alarm hwNmNorthboundPr The alarm ID and NE ID are not reported, and only
Cause obableCause the alarm cause is contained.
Example: The user logs out or fails to log in.

Alarm hwNmNorthboundE The alarm ID and NE ID are not reported, and only
Details ventDetail the alarm details are contained.
Example: NE NE(9-8886) not login

Alarm hwNmNorthboundPr The alarm ID and NE ID are not reported, and only
Recovery obableRepair the alarm recovery advice is contained.
Advice Example: None

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 121

Name Name in the MIB Description

Event Name hwNmNorthboundE The alarm ID and NE ID are not reported, and only
ventName the event name is contained.
Example: NE_NOT_LOGIN

Location Information Format

For NE alarms, the location information is different based on the NE domain.

Table C-3 Location Information Format

Domain Location Information Format Description

Transport NE Format: Frame=[Frame ID] When a WDM NE is mounted to

(SDH, OSN, Slot=[Slot ID] Port=[Port an optical NE, Frame ID is the
MSTP, WDM, Number] TTP_TYPE=[Function WDM NE ID. For PTN NEs,
PTN, RTN, and Block ID] [Location Information] Frame ID is the NE ID.
so on) l Frame: indicates the subrack l The subrack ID is displayed,
ID. It is the NE ID by default. This field is reported only for
l Slot: indicates the slot ID. NEs with subracks. For
example, for SDH NEs that do
l Port: indicates the logical or not have subracks, the subrack
physical port on which the ID is not reported.
alarm is generated.
l For port alarms, the slot and
l TTP_TYPE: indicates the port IDs are reported.
function module ID. It is
internal information. l For board alarms, the
following situations may
l Location Information: You occur: Only the slot ID is
cannot parse it. reported; the slot and port IDs
are reported, but the port ID is
fixed to 65535.
l For NE alarms or NMS alarms,
the slot or port ID is not
reported.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 122

Domain Location Information Format Description

Access NE Format: Frame=[Frame ID] Indicates the location information

Slot=[Slot ID] Subslot=[subslot reported by NEs. ONUs include
ID] Port=[Port Number] MDUs and ONTs.
ONUID=[ONU ID] [Non-
Physical Location Information]
l Frame: indicates the NE ID
l Slot: indicates the slot ID.
l Subslot: indicates the subslot
ID.
l Port: indicates the logical or
physical port on which the
alarm is generated.
l ONUID: indicates the ONU
ID.
l Non-Physical Location
Information: indicates the
alarm object name, type, and
alias.

IP NE (Router, Format: [Location Information] Indicates the alarm information of

Switch, [Additional Information] IP NEs.
Security)

C.3 U2000 MIB Trap

The SNMP NBI support the following traps when load U2000 MIB.

C.3.1 Active Alarm Notification Trap

The active alarm notification trap, hwNmNorthboundEventNotify, indicates that the U2000
generates new alarms or alarm information changes.

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 123

Definition
Name Enterprise Type Description

hwNmNorthboundE hwNmNorthboundE Trap/Inform Indicates that real-

ventNotify ventInfo time alarms are
reported.

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.

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the name of a network

NEName 15.1.7.1.1 string element (NE).

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the device type of a

NEType 15.1.7.1.2 string NE.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm location. The

ObjectInstance 15.1.7.1.3 string options are as follows:
l Rack
l Frame
l Slot
l Subslot
l Port

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the type of events.

EventType 15.1.7.1.4 string l Communication
l Environment
l Equipment
l Service
l Process
l Security

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 124

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates time when the alarm

EventTime 15.1.7.1.5 string was generated. The options are
as follows:
l Local Time
(YYYY/MM/DD-hh:mm:ss)
l UTC Time (YYYY/MM/DD-
hh:mm:ssZ)
l Local with Time Zone
(YYYY/MM/
DD:hh:mm:ss:hh:mmTZ)

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the probable cause of

ProbableCause 15.1.7.1.6 string the alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm severity. The

Severity 15.1.7.1.7 string options are as follows:
l Critical
l Major
l Minor
l Warning
l Indeterminate

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm ID and

EventDetail 15.1.7.1.8 string detailed information.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the additional

AdditionalInfo 15.1.7.1.9 string information of an NE.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the flag bit for an

FaultFlag 15.1.7.1.10 string alarm. The options are as
follows:
l Event: indicates that an event
is generated.
l Fault: indicates that an alarm
is generated.
l Recovery: indicates that the
trap is alarm recovery.
l Acknowledge: Indicates the
alarm is acknowledged.
l Unacknowledge: Indicates
the alarm is unacknowledged.
l Change: Indicates alarm is
changed.
l UNKNOWN_EVENT_TYPE
: Unknown event type

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 125

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the function type of an

FaultFunction 15.1.7.1.11 string alarm. The options are as
follows:
l Power
l Environment
l Signal
l Relay
l Hardware
l Software
l Run
l Communication
l Service
l Processerror
l UNKNOWN_FU NC_TYPE

hwNmNorthbound 1.3.6.1.4.1.2011.2. IP address Indicates the IP address of a

DeviceIP 15.1.7.1.12 device.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the serial number of an

SerialNo 15.1.7.1.13 alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm

ProbableRepair 15.1.7.1.14 string troubleshooting suggestions.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the ID of a resource.

ResourceIDs 15.1.7.1.15 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB1 15.1.7.1.16 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB2 15.1.7.1.17 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB3 15.1.7.1.18 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB4 15.1.7.1.19 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB5 15.1.7.1.20 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB6 15.1.7.1.21 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB7 15.1.7.1.22 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB8 15.1.7.1.23 string

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 126

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the name of an event.

EventName 15.1.7.1.24 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the ID of an alarm.

ReasonID 15.1.7.1.25

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the fault ID of an

FaultID 15.1.7.1.26 alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the device type ID of

DeviceType 15.1.7.1.27 string an alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the name of the trail

TrailName 15.1.7.1.28 string affected by an alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Specifies whether the alarm is

RootAlarm 15.1.7.1.29 root alarm or not.
l 0: Non-root alarm
l 1: Root alarm

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the group ID the alarm

GroupID 15.1.7.1.30 belongs to.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the engineering alarm

MaintainStatus 15.1.7.1.31 status.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the log serial number of

RootAlarmSerial- 15.1.7.1.32 string root alarm.
No

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the alarm

ConfirmStatus 15.1.7.1.33 acknowledgement status.
l 1: acknowledged
l 2: unacknowledged

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the alarm clearance

RestoreStatus 15.1.7.1.34 status.
l 1: cleared
l 2: uncleared

C.3.2 Active Alarm Synchronization Start Trap

The active alarm synchronization start trap,
hwNmNorthboundEventSynchronizationCommandStart is used to notify the OSS of
starting to synchronize alarms.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 127

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 7.1.3 Synchronizing Alarms.

The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStart

in the following format:

NMS IP:port:start time:end time

NOTE

l NMS IP:Port indicates the IP address and port of the OSS.

l The format for start and end time is YYYYMMDDhhmmss.

Definition
Name Enterprise Type Description

hwNmNorthboundE hwNmNorthboundE Trap/Inform Indicates that the

ventSynchroniza- ventSynchroniza- alarm
tionStartNotify tionStart synchronization is
started.

VB List
N/A

C.3.3 Active Alarm Report Trap

The active alarm report trap, hwNmNorthboundEventSynchronizationQueryResult,
indicates the information about alarms in the U2000.

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 7.1.3 Synchronizing Alarms.

The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStart

in the following format:

NMS IP:port:start time:end time

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 128

NOTE

l NMS IP:Port indicates the IP address and port of the OSS.

l The format for start and end time is YYYYMMDDhhmmss.

Definition
Name Enterprise Type Description

hwNmNorthboundE hwNmNorthboundE Trap/Inform Indicates the

ventSynchroniza- ventSynchroniza- synchronization
tionQueryResultNo- tionQueryResult result or required
tify alarms.

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

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the name of a network

NEName 15.1.7.1.1 string element (NE).

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the device type of a

NEType 15.1.7.1.2 string NE.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm location. The

ObjectInstance 15.1.7.1.3 string options are as follows:
l Rack
l Frame
l Slot
l Subslot
l Port

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the type of events.

EventType 15.1.7.1.4 string l Communication
l Environment
l Equipment
l Service
l Process
l Security

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 129

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates time when the alarm

EventTime 15.1.7.1.5 string was generated. The options are
as follows:
l Local Time
(YYYY/MM/DD-hh:mm:ss)
l UTC Time (YYYY/MM/DD-
hh:mm:ssZ)
l Local with Time Zone
(YYYY/MM/
DD:hh:mm:ss:hh:mmTZ)

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the probable cause of

ProbableCause 15.1.7.1.6 string the alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm severity. The

Severity 15.1.7.1.7 string options are as follows:
l Critical
l Major
l Minor
l Warning
l Indeterminate

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm ID and

EventDetail 15.1.7.1.8 string detailed information.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the additional

AdditionalInfo 15.1.7.1.9 string information of an NE.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the flag bit for an

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 130

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the function type of an

FaultFunction 15.1.7.1.11 string alarm. The options are as
follows:
l Power
l Environment
l Signal
l Relay
l Hardware
l Software
l Run
l Communication
l Service
l Processerror
l UNKNOWN_FU NC_TYPE

hwNmNorthbound 1.3.6.1.4.1.2011.2. IP address Indicates the IP address of a

DeviceIP 15.1.7.1.12 device.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the serial number of an

SerialNo 15.1.7.1.13 alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the alarm

ProbableRepair 15.1.7.1.14 string troubleshooting suggestions.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the ID of a resource.

ResourceIDs 15.1.7.1.15 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB1 15.1.7.1.16 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB2 15.1.7.1.17 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB3 15.1.7.1.18 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB4 15.1.7.1.19 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB5 15.1.7.1.20 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB6 15.1.7.1.21 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB7 15.1.7.1.22 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Reserved field.

sAdditionalVB8 15.1.7.1.23 string

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 131

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the name of an event.

EventName 15.1.7.1.24 string

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the ID of an alarm.

ReasonID 15.1.7.1.25

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the fault ID of an

FaultID 15.1.7.1.26 alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the device type ID of

DeviceType 15.1.7.1.27 string an alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the name of the trail

TrailName 15.1.7.1.28 string affected by an alarm.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Specifies whether the alarm is

RootAlarm 15.1.7.1.29 root alarm or not.
l 0: Non-root alarm
l 1: Root alarm

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the group ID the alarm

GroupID 15.1.7.1.30 belongs to.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the engineering alarm

MaintainStatus 15.1.7.1.31 status.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indicates the log serial number of

RootAlarmSerial- 15.1.7.1.32 string root alarm.
No

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the alarm

ConfirmStatus 15.1.7.1.33 acknowledgement status.
l 1: acknowledged
l 2: unacknowledged

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the alarm clearance

RestoreStatus 15.1.7.1.34 status.
l 1: cleared
l 2: uncleared

C.3.4 Active Alarm Synchronization End Trap

The active alarm synchronization end trap,
hwNmNorthboundEventSynchronizationCommandStop, is used to notify the OSS of
ending alarm synchronization.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 132

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 7.1.3 Synchronizing
Alarms.
The OSS performs the operation hwNmNorthboundEventSynchronizationCommandStop
on the designated U2000 in the following format:
NMS IP:port

NOTE

NMS IP:port refers to the IP address and port of the OSS server.

Definition
Name Enterprise Type Description

hwNmNorthboundE hwNmNorthboundE Trap/Inform Indicates that the

ventSynchronizatio- ventSynchronizatio- alarm
nEndNotify nEnd synchronization
completes.

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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 133

VB OID Data Description

Type

hwNmNorthbound 1.3.6.1.4.1.2011.2. Integer Indicates the synchronization

EventSynchroniza- 15.1.7.7.3.1 result. The options are as
tionEndStatus follows:
1: normalEnd(1): Indicates that
the synchronization was
complete.
2: stopped(2): Indicates that the
OSS stopped the
synchronization.
3: error(3): Indicates that
exceptions occurred during the
synchronization.

hwNmNorthbound 1.3.6.1.4.1.2011.2. Octet Indications the details about the

EventSynchroniza- 15.1.7.7.3.2 string synchronization result.
tionEndStatusDe-
tail

C.3.5 KeepAlive Info (Heartbeat) Trap

The heartbeat notification trap, hwNmNorthboundEventKeepAliveInfo, identifies that the
OSS communicates properly with the U2000.

Description
U2000 sends the KeepAlive info (heartbeat) to the NMS/OSS regularly each period. If the
NMS receives the trap, the connection between the NMS/OSS and the U2000 works. If the
NMS/OSS 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 Advanced Configuration.

Condition
The U2000 sends the keepAlive info (heartbeat) trap to the NMS/OSS regularly in the preset
period.

Trap Definition
Name ENTERPRISE Type Description

hwNmNorthboundE hwNmNorthboundE Trap/Inform Notification for the

ventKeepAlive ventKeepAliveInfo Keep Alive traps.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 134

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.

Name OID Data Type Descriptio

hwNmAgent 1.3.6.1.4.1.2011.2.15.1 OCTET STRING By default,

this field is
reported.

hwNmNorthboundK 1.3.6.1.4.1.2011.2.15.1.7.2.1 OCTET STRING You can

eepAlive make
configuratio
ns for the
heartbeat
notification
trap to
report this
field.

NOTICE
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
8.3.7 How to configure the heartbeat notification trap to hwNmNorthboundKeepAlive.

C.4 U2000 MIB Trap Sample

There are five traps supported by U2000 MIB: active alarm trap, active alarm synchronization
start trap, active alarm synchronization result trap, active alarm synchronization stop trap, and
heartbeat trap. The samples in this topic use SNMPv1 as an example. SNMPv2c and SNMPv3
are similar to SNMPv1.

C.4.1 Active Alarm Trap

Two formats are available for alarm notifications when the U2000 MIB is used. They are used
to manage multi-domain devices and optical devices of the transport domain.

Description of the T2000support configuration item

The default value of the T2000support configuration item is 1. Check and change the value
before an upgrade for ensure compatibility. You must configure the item manually. For
details, see8.3.8 How to configure T2000Support item.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 135

Table C-4 Configuration file path

Version File Path

Versions earlier than U2000 V100R002C00 server/conf/snmpagent.cfg

U2000 V100R002C00 and later versions server/etc/nbi/snmp/snmpagent.xml

Table C-5 Description of the T2000support configuration item

Scenario T2000supp Example Value of Description
ort hwNmNorthboundO
Configurat bjectInstance
ion Item

Managing <param hwNmNorthboundOb- l This mode is fit for the multi-

multiple- name="T20 jectInstance.0 *** domain equipment scene.
domain NEs 00Support" (octets) Slot=4 Port=1 l Alarm field: The reported
>0</param> TTP_TYPE=1 4- alarm identification
N1SL16-1(SDH-1)-SPI: information contains only the
1 alarm ID.
l When optical NEs exist in the
management domain, this
mode is not recommended.

Managing <param hwNmNorthboundOb- l Alarm field: The redundancy

optical NEs name="T20 jectInstance.0 *** information, such as the alarm
of the 00Support" (octets) source=NE ID and equipment type, is
transport >1</param> (9-3500) location=4- deleted from the reported
domain N1SL16-1(SDH-1)-SPI: alarm information.
1 l In this mode, the SNMP NBI
can report the information of
optical NE.

<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 (24)
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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 136

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
Binding #19: hwNmNorthboundDeviceType.0 *** (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
Binding #24: hwNmNorthboundRootAlarmSerialNo.0 *** (octets) (zero-
length)

<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 (24)
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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 137

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 #18: hwNmNorthboundFaultID.0 *** (int32) 1
Binding #19: hwNmNorthboundDeviceType.0 *** (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
Binding #24: hwNmNorthboundRootAlarmSerialNo.0 *** (octets) (zero-
length)

C.4.2 Active Alarm Synchronization Start Trap

After the NMS/OSS send alarm synchronization request to the U2000, the SNMP NBI will
return the start notification of alarm synchronization.
18: Specific trap
hwNmNorthboundEventSynchronizationStart::hwNmNorthboundEventSynchronizati
onStartNotify #9 trap(v1) received from: 10.71.88.151 at 2010-11-24
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.

C.4.3 Active Alarm Synchronization Result Trap

After the NMS/OSS send alarm synchronization request to the U2000, the SNMP NBI will
report the active alarm with the filter criteria to the NMS/OSS.
101: Specific trap
hwNmNorthboundEventSynchronizationQueryResult::hwNmNorthboundEventSynchro
nizationQueryResultNotify #10 trap(v1) received from: 10.71.88.151 at
2011-12-24 15:56:49
Time stamp: 0 days 00h:06m:28s.55th
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: hwNmNorthboundEventSynchronizationQueryResult
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventSynchronizationQueryResultNotify, Module:
HW-IMAPV1NORTHBOUND-TRAP-MIB, Enterprise:

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 138

hwNmNorthboundEventSynchronizationQueryResult
Bindings (24)
Binding #1: hwNmNorthboundNEName.0 *** (octets) NE(9-1954)
Binding #2: hwNmNorthboundNEType.0 *** (octets) OptiX PTN 3900
Binding #3: hwNmNorthboundObjectInstance.0 *** (octets) TUNNEL:
(463,1.1.19.55,54.74.57.54)
Binding #4: hwNmNorthboundEventType.0 *** (octets) Communication
Binding #5: hwNmNorthboundEventTime.0 *** (octets) 2010/10/31 -
17:09:46
Binding #6: hwNmNorthboundProbableCause.0 *** (octets) ID:
12814,DeviceType:128450560,\1. The physical link fails.\2. The network
is severely congested.\3. The opposite equipment is faulty.
Binding #7: hwNmNorthboundSeverity.0 *** (octets) Critical
Binding #8: hwNmNorthboundEventDetail.0 *** (octets) ID:
12814,DeviceType:128450560,Loss of Connectivity Verification defect
Binding #9: hwNmNorthboundAdditionalInfo.0 *** (octets)
Alarm Parameter II(hex) 0x0f
Binding #10: hwNmNorthboundFaultFlag.0 *** (octets) Fault
Binding #11: hwNmNorthboundFaultFunction.0 *** (octets) Communication
Binding #12: hwNmNorthboundDeviceIP.0 *** (octets) 10.78.217.248
Binding #13: hwNmNorthboundSerialNo.0 *** (int32) 60229
Binding #14: hwNmNorthboundProbableRepair.0 *** (octets) ID:
12814,DeviceType:128450560,
Binding #15: hwNmNorthboundResourceIDs.0 *** (octets)
3145793.-1.-1.-1.-1.-1.-1.-1
Binding #16: hwNmNorthboundEventName.0 *** (octets) ID:
12814,DeviceType:128450560,MPLS_TUNNEL_LOCV
Binding #17: hwNmNorthboundReasonID.0 *** (int32) 12814
Binding #18: hwNmNorthboundFaultID.0 *** (int32) 0
Binding #19: hwNmNorthboundDeviceType.0 *** (octets) 128450560
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
Binding #24: hwNmNorthboundRootAlarmSerialNo.0 *** (octets) (zero-
length)

C.4.4 Active Alarm Synchronization End Trap

Active alarm synchronization end traps are triggered when all required alarms have been
reported to the OSS or the OSS automatically stops the synchronization.

Synchronization Stopped After Alarm Reporting Was Complete

After all required alarms are reported to the OSS, the U2000 sends traps through the SNMP
NBI to inform the OSS that the alarm reporting is complete.
1335: Specific trap
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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 139

Bindings (2)
Binding #1: hwNmNorthboundEventSynchronizationEndStatus.0 ***
(int32) normalEnd(1)
Binding #2: hwNmNorthboundEventSynchronizationEndStatusDetail.0 ***
(octets) Sync End: Successfully queried all alarms!

Synchronization Was Stopped by the OSS

During the synchronization, the OSS automatically interrupts the process. The U2000 then
reports traps to inform the OSS that the synchronization is stopped as a response to the
request.
2420: Specific trap
hwNmNorthboundEventSynchronizationEnd::hwNmNorthboundEventSynchronization
EndNotify #11 trap(v1) received from: 10.71.88.151 at 2010-11-24 16:04:01
Time stamp: 0 days 00h:13m:40s.35th
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) stopped(2)
Binding #2: hwNmNorthboundEventSynchronizationEndStatusDetail.0 ***
(octets) Sync Stopped: The synchronization is stopped by the NMS's
command!

Synchronization Was Stopped by Abnormal Event

403: Specific trap
hwNmNorthboundEventSynchronizationEnd::hwNmNorthboundEventSynchronization
EndNotify #11 trap(v1) received from: 10.71.224.13 at 2011-4-27 16:44:56
Time stamp: 0 days 00h:03m:31s.64th
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: hwNmNorthboundEventSynchronizationEnd
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventSynchronizationEndNotify, Module: HW-
IMAPV1NORTHBOUND-TRAP-MIB, Enterprise:
hwNmNorthboundEventSynchronizationEnd
Bindings (2)
Binding #1: hwNmNorthboundEventSynchronizationEndStatus.0 ***
(int32) error(3)
Binding #2: hwNmNorthboundEventSynchronizationEndStatusDetail.0 ***
(octets) Sync 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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 140

NOTE

Two OIDs are supported. For their configurations, see 8.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
Specific Trap MIB Lookup Results
Name: hwNmNorthboundEventKeepAlive, Module: HW-IMAPV1NORTHBOUND-TRAP-
MIB, Enterprise: hwNmNorthboundEventKeepAliveInfo
Bindings (1)
Binding #1: hwNmNorthboundKeepAlive *** (octets) SNMP Agent

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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 141

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

D U2000-T MIB

The U2000-T MIB (T2000-NETMANAGEMENT-MIB) is used mainly in the management of

a transport network or upgrades of the T2000.

D.1 MIB Description

D.2 Reported Alarm Field by U2000-T MIB
U2000-T MIB support 19 alarm fields, you cannot customize the alarm fields.
D.3 U2000-T MIB Trap
D.4 U2000-T MIB Trap Sample
There are four traps supported by U2000-T MIB: active alarm trap, active alarm
synchronization start trap, active alarm synchronization result trap, and active alarm
synchronization stop trap. The samples in this topic use SNMPv1 as an example. SNMPv2c
and SNMPv3 are similar to SNMPv1.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 142

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

D.1 MIB Description

The complete T2000-NETMANAGEMENT-MIB MIB node information is:

iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).hua
wei(2011).products(2).netManagement(15).nmAgent(1)

The MIB tree showed as follows:

--- huawei(2011)
|--- products(2)
|--- netManagement(15)
|--- nmAgent(1)
|---- nmNorthboundEvent(7)

nmNorthboundEvent defines the SNMP NBI.

For the function interface of U2000-T MIB, see 7.2 U2000-T MIB Subinterfaces.

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.

D.2 Reported Alarm Field by U2000-T MIB

U2000-T MIB support 19 alarm fields, you cannot customize the alarm fields.

When the MIB frame set to U2000-T MIB, the SNMP NBI will report the following alarm
fields, you can customize the alarm fields.

Name Name in the MIB Description Value

EMS Name northboundRepor- EMS name. Octet string

tAlarmEmsName The value is always Huawei/
U2000.

Equipment northboundRepor- Type of the equipment where Octet string

Type tAlarmManagedOb- an alarm is generated
jectClass For example, OptiX 2500+.

Equipment northboundRepor- Name of the equipment where Octet string

Name tAlarmManagedOb- an alarm is generated
jectInstance For example, NE350.

NE Name northboundRepor- Name of the NE where an Octet string

tAlarmNEName alarm is generated. The NE
name is the same as the
equipment name.
For example, NE350.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 143

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Name Name in the MIB Description Value

Rack Name northboundRepor- Name of the rack where an Octet string

tAlarmRackName alarm is generated
The value is always 1.

Subrack northboundRepor- Name of the subrack where an Octet string

Name tAlarmShelfName alarm is generated.
In the WDM or OTN domain,
an NE name is the name of an
optical NE and a subrack name
is the name of the subrack that
belongs to the optical NE.
In the SDH or other domains,
an NE presents a subrack. That
is, an NE name is a subrack
name.
For example, NE350.

Physical northboundRepor- Physical location of the Octet string

Location of tAlarmDevLocation equipment where an alarm is
Equipment generated.
This parameter is always left
blank.

Board Name northboundRepor- Name of the board where an Octet string

tAlarmBoardName alarm is generated.
For example, PQ1.

Port Type northboundRepor- Port type. Octet string

tAlarmPortType For example, SDH_TU.

Port Number northboundRepor- Port number. Integer

tAlarmPortNumber For example, 1.

Location of northboundRepor- Specific location of an alarm. Octet string

an Alarm tAlarmLocation For example, ne=590174/
Object rack=1/shelf=1/slot=5/
domain=sdh/port=1/
highPath=1/lowPath=0/layer=5
The rules for assembling alarm
location information for a PTN
NE may be slightly different.
For example,
ne=3145796/rack=1/shelf=1/
slot=4/domain=ptn/
type=physical/port=1/
location1=260/layer=15

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 144

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Name Name in the MIB Description Value

Alarm Type northboundRepor- Alarm type. Octet string

tAlarmEventType Options are as follows:
l communicationsAlarm
l qualityofServiceAlarm
l equipmentAlarm
l processingErrorAlarm
l environmentalAlarm

Alarm Rising northboundRepor- Time at which an alarm is Octet string

Time tAlarmEventTime generated. The option is always
the local time.
For example,
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

Possible northboundRepor- Possible alarm cause. Octet string

Alarm Cause tAlarmProbableCau For example, RAI.
se

Alarm Cause northboundRepor- Alarm cause. Octet string

tAlarmSpecificPro- For example, NE
blems communication was lost

Affect northboundRepor- Whether an alarm affects Integer

Service tAlarmOperationAf services or not.
fected Options are as follows:
l 0: The alarm does not affect
services.
l 1: The alarm affects
services.

Alarm ID northboundRepor- Alarm ID. Integer

tAlarmID For example, 93.

Alarm Name northboundRepor- Alarm name. Octet string

tAlarmName For example, LP_RDI.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 145

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Name Name in the MIB Description Value

Advice on northboundRepor- Alarm recovery suggestion. Octet string

Fixing an tAlarmProposedRe- This parameter is always left
Alarm pairActions blank.

IP Address northboundRepor- IP address of the equipment IP address

of the Object tAlarmIPAddress where an alarm is generated.
for Alarm This parameter is always left
Rising blank.

Serial northboundRepor- Serial number of an alarm. Integer

Number of tAlarmNotificatio- For example, 109.
an Alarm nIdentifier

ID of the northboundRepor- ID of the resource where an Integer

Resource for tAlarmResourceID alarm is generated.
Alarm Rising This parameter is always left
blank.

Additional northboundRepor- Additional information. Octet string

Information tAlarmAdditional- For example, Alarm Parameter
Text II(hex) 0x02

Clear Alarm northboundRepor- Whether to clear an alarm. Integer

tAlarmCleared Options are as follows:
l 0: Do not clear the alarm.
l 1: Clear the alarm.

Serial northboundRepor- Serial number of the alarm to Integer

Number of tAlarmCorrelated- be cleared.
the Alarm to Notifications The value of this parameter is
Be Cleared the same as that of the Serial
Number of an Alarm
parameter.

Additional northboundRepor- Additional information of an Octet string

Alarm tAlarmAdditionalV alarm.
Information B The value of this parameter is
(10 Fields) the same as that of the Alarm
Rising Time parameter.

D.3 U2000-T MIB Trap

The SNMP NBI support the following traps when load U2000-T MIB.

l Active alarm trap: northBoundReportAlarm

l Active alarm synchronization start trap: northBoundSynchAlarm
l Active alarm synchronization stop trap: northBoundSynchAlarmStart

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 146

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

l Active alarm synchronization result trap: northBoundSynchAlarmEnd

D.3.1 Active Alarm Notification Trap

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

northBoundRepor- northboundNotifica- Trap Indicates that real-

tAlarm tionType time alarms are
reported.

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.

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the type of the equipment

larmManagedObject 2011.2.15. string where an alarm is generated, for
Class 1.7.3.1 example, OptiX 2500+.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the equipment

larmManagedObjec- 2011.2.15. string where an alarm is generated, for
tInstance 1.7.3.2 example, NE350.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm type.

larmEventType 2011.2.15. string The options are as follows:
1.7.3.3
l communicationsAlarm
l qualityofServiceAlarm
l equipmentAlarm
l processingErrorAlarm
l environmentalAlarm

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 147

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the time when an alarm is

larmEventTime 2011.2.15. string generated. The value is always set to
1.7.3.4 the local time, for example,
2005-10-14,17:41:04.0.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the probable alarm cause, for

larmProbableCause 2011.2.15. string example, RAI.
1.7.3.5

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm cause, for example,

larmSpecificPro- 2011.2.15. string NE communication was lost.
blems 1.7.3.6

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm severity.

larmPerceivedSever- 2011.2.15. string Options are as follows:
ity 1.7.3.7
l Critical
l Major
l Minor
l Warning
l Cleared
l Indeterminate

northboundReportA- 1.3.6.1.4.1. Integer Indicates the serial number of an alarm,

larmNotificationI- 2011.2.15. for example, 109.
dentifier 1.7.3.8

northboundReportA- 1.3.6.1.4.1. Integer Indicates the serial number of an alarm

larmCorrelatedNoti- 2011.2.15. to be cleared.
fications 1.7.3.9 The value of this parameter is the same
as that of the serial number of an alarm.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm troubleshooting

larmProposedRepair 2011.2.15. string suggestions.
Actions 1.7.3.10 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the additional information, for

larmAdditionalText 2011.2.15. string example, Alarm Parameter II(hex)
1.7.3.11 0x02.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the EMS name.

larmEmsName 2011.2.15. string The value is always Huawei/U2000.
1.7.3.12

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the NE where an

larmNEName 2011.2.15. string alarm is generated. The NE name is the
1.7.3.13 same as the equipment name, for
example, NE350.
For example, NE350.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 148

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the physical location of the

larmDevLocation 2011.2.15. string equipment where an alarm is generated.
1.7.3.14 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the rack where an

larmRackName 2011.2.15. string alarm is generated.
1.7.3.15 The value is always 1.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the subrack

larmShelfName 2011.2.15. string where 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 Indicates the name of the board where

larmBoardName 2011.2.15. string an alarm is generated, for example,
1.7.3.17 PQ1.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the port type, for example,

larmPortType 2011.2.15. string SDH_TU.
1.7.3.18

northboundReportA- 1.3.6.1.4.1. Integer Indicates the port number, for example,

larmPortNumber 2011.2.15. 1.
1.7.3.19

northboundReportA- 1.3.6.1.4.1. Octet Indicates the specific location of an

larmLocation 2011.2.15. string 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.

northboundReportA- 1.3.6.1.4.1. Octet Specifies whether an alarm affects

larmOperationAffec- 2011.2.15. string services.
ted 1.7.3.21 The options are as follows:
0: The alarm does not affect services.
1: The alarm affects services.

northboundReportA- 1.3.6.1.4.1. Integer Indicates the alarm ID, for example, 93.
larmID 2011.2.15.
1.7.3.22

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 149

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm name, for example,

larmName 2011.2.15. string LP_RDI.
1.7.3.23

northboundReportA- 1.3.6.1.4.1. IP address Indicates the IP address of the

larmIPAddress 2011.2.15. equipment where an alarm is generated.
1.7.3.24 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Integer Indicates the ID of the resource where

larmResourceID 2011.2.15. an alarm is generated.
1.7.3.25 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Integer Specifies whether to clear an alarm.

larmCleared 2011.2.15. The options are as follows:
1.7.3.26
0: Do not clear the alarm.
1: Clear the alarm.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the additional information

larmAdditionalVB1- 2011.2.15. string about an alarm.
VB10 1.7.3.27 The value of this parameter is the same
as that of northboundReportAlarmE-
ventTime.

D.3.2 Active Alarm Synchronization Start Trap

Function
After the OSS sends query requests, the U2000 sends this kind of traps to inform the OSS that
the synchronization is started.

Trigger Condition
The OSS triggers the synchronization. For details, see 7.2.2 Synchronizing Alarms.
The OSS sets northBoundSynchAlarmCommand to 1.

NOTE

l 1: starts the alarm synchronization.

l 0: ends the alarm synchronization.

Definition
Name Enterprise Type Description

northBoundSynchA- northboundNotifica- Trap Indicates the alarm

larmStart tionType synchronization is
started.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 150

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB List
N/A

D.3.3 Active Alarm Report Trap

Function
After the OSS performs the alarm synchronization, the U2000 sends this kind of traps to
report required alarms in the U2000 database.

Trigger Condition
The OSS triggers the synchronization. For details, see 7.2.2 Synchronizing Alarms.

The OSS sets northBoundSynchAlarmCommand to 1.

NOTE

l 0: starts the alarm synchronization.

l 1: ends the alarm synchronization.

Definition
Name Enterprise Type Description

northBoundSynchA- northboundNotifica- Trap/Inform Indicates the alarm

larm tionType synchronization is
started.

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

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the type of the equipment

larmManagedObject 2011.2.15. string where an alarm is generated, for
Class 1.7.3.1 example, OptiX 2500+.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the equipment

larmManagedObjec- 2011.2.15. string where an alarm is generated, for
tInstance 1.7.3.2 example, NE350.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 151

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm type.

larmEventType 2011.2.15. string The options are as follows:
1.7.3.3
l communicationsAlarm
l qualityofServiceAlarm
l equipmentAlarm
l processingErrorAlarm
l environmentalAlarm

northboundReportA- 1.3.6.1.4.1. Octet Indicates the time when an alarm is

larmEventTime 2011.2.15. string generated. The value is always set to
1.7.3.4 the local time, for example,
2005-10-14,17:41:04.0.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the probable alarm cause, for

larmProbableCause 2011.2.15. string example, RAI.
1.7.3.5

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm cause, for example,

larmSpecificPro- 2011.2.15. string NE communication was lost.
blems 1.7.3.6

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm severity.

larmPerceivedSever- 2011.2.15. string Options are as follows:
ity 1.7.3.7
l Critical
l Major
l Minor
l Warning
l Cleared
l Indeterminate

northboundReportA- 1.3.6.1.4.1. Integer Indicates the serial number of an alarm,

larmNotificationI- 2011.2.15. for example, 109.
dentifier 1.7.3.8

northboundReportA- 1.3.6.1.4.1. Integer Indicates the serial number of an alarm

larmCorrelatedNoti- 2011.2.15. to be cleared.
fications 1.7.3.9 The value of this parameter is the same
as that of the serial number of an alarm.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the alarm troubleshooting

larmProposedRepair 2011.2.15. string suggestions.
Actions 1.7.3.10 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the additional information, for

larmAdditionalText 2011.2.15. string example, Alarm Parameter II(hex)
1.7.3.11 0x02.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 152

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Indicates the EMS name.

larmEmsName 2011.2.15. string The value is always Huawei/U2000.
1.7.3.12

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the NE where an

larmNEName 2011.2.15. string alarm is generated. The NE name is the
1.7.3.13 same as the equipment name, for
example, NE350.
For example, NE350.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the physical location of the

larmDevLocation 2011.2.15. string equipment where an alarm is generated.
1.7.3.14 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the rack where an

larmRackName 2011.2.15. string alarm is generated.
1.7.3.15 The value is always 1.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the subrack

northboundReportA- 1.3.6.1.4.1. Octet Indicates the name of the board where

larmBoardName 2011.2.15. string an alarm is generated, for example,
1.7.3.17 PQ1.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the port type, for example,

larmPortType 2011.2.15. string SDH_TU.
1.7.3.18

northboundReportA- 1.3.6.1.4.1. Integer Indicates the port number, for example,

larmPortNumber 2011.2.15. 1.
1.7.3.19

northboundReportA- 1.3.6.1.4.1. Octet Indicates the specific location of an

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 153

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

VB OID Type Description

northboundReportA- 1.3.6.1.4.1. Octet Specifies whether an alarm affects

larmOperationAffec- 2011.2.15. string services.
ted 1.7.3.21 The options are as follows:
0: The alarm does not affect services.
1: The alarm affects services.

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 Indicates the alarm name, for example,

larmName 2011.2.15. string LP_RDI.
1.7.3.23

northboundReportA- 1.3.6.1.4.1. IP address Indicates the IP address of the

larmIPAddress 2011.2.15. equipment where an alarm is generated.
1.7.3.24 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Integer Indicates the ID of the resource where

larmResourceID 2011.2.15. an alarm is generated.
1.7.3.25 This parameter is always left blank.

northboundReportA- 1.3.6.1.4.1. Integer Specifies whether to clear an alarm.

larmCleared 2011.2.15. The options are as follows:
1.7.3.26
0: Do not clear the alarm.
1: Clear the alarm.

northboundReportA- 1.3.6.1.4.1. Octet Indicates the additional information

larmAdditionalVB1- 2011.2.15. string about an alarm.
VB10 1.7.3.27 The value of this parameter is the same
as that of northboundReportAlarmE-
ventTime.

D.3.4 Active Alarm Synchronization End Trap

Function
The U2000 sends this kind of traps to inform the OSS that the alarm synchronization is ended.

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 triggers the termination of synchronization. For details, see 7.2.2 Synchronizing
Alarms.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 154

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

The OSS sets northBoundSynchAlarmCommand to 1.

NOTE

l 0: starts the alarm synchronization.

l 1: ends the alarm synchronization.

Definition
Name Enterprise Type Description

northBoundSynchA- northboundNotifica- Trap/Inform Indicates that the

larmEnd tionType alarm
synchronization is
ended.

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.

VB OID Data Description

Type

northBoundSynch 1.3.6.1.4.1.2011.2. Integer Indicates the alarm

AlarmEndStatus 15.1.7.4.3 synchronization result.
0: indicates that the
synchronization was complete.
1: indicates that the OSS stopped
the synchronization.

D.4 U2000-T MIB Trap Sample

There are four traps supported by U2000-T MIB: active alarm trap, active alarm
synchronization start trap, active alarm synchronization result trap, and active alarm
synchronization stop trap. The samples in this topic use SNMPv1 as an example. SNMPv2c
and SNMPv3 are similar to SNMPv1.

NOTE

U2000-T MIB does not support heartbeat traps.

D.4.1 Active Alarm Trap

When the alarm generated in equipment or U2000, the SNMP NBI will report the alarm to the
NMS/OSS. U2000-T MIB support 36 VBs and you cannot customized it.
4: Specific trap northboundNotificationType::northBoundSynchAlarm #2
trap(v1) received from: 10.71.226.158 at 2011-3-10 10:52:50
Time stamp: 0 days 00h:05m:24s.43th

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 155

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Agent address: 10.71.226.158 Port: 982 Transport: IP/UDP Protocol:

SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: qq
SNMPv1 agent address: 10.71.226.158
Enterprise: northboundNotificationType
Specific Trap MIB Lookup Results
Name: northBoundSynchAlarm, Module: T2000-NETMANAGEMENT-MIB,
Enterprise: northboundNotificationType
Bindings (36)
Binding #1: northboundReportAlarmManagedObjectClass.0 *** (octets)
(zero-length)
Binding #2: northboundReportAlarmManagedObjectInstance.0 ***
(octets) Huawei/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) Huawei/U2000
Binding #13: northboundReportAlarmNEName.0 *** (octets) Huawei/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

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 156

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Binding #30: northboundReportAlarmAdditionalVB4.0 *** (octets)

2010-11-29,23:31:54.0
Binding #31: northboundReportAlarmAdditionalVB5.0 *** (octets)
2010-11-29,23:31:54.0
Binding #32: northboundReportAlarmAdditionalVB6.0 *** (octets)
2010-11-29,23:31:54.0
Binding #33: northboundReportAlarmAdditionalVB7.0 *** (octets)
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

D.4.2 Active Alarm Synchronization Start Trap

After the NMS/OSS send alarm synchronization request to the U2000, the SNMP NBI will
return the start notification of alarm synchronization.
54: Specific trap northboundNotificationType::northBoundSynchAlarmStart
#3 trap(v1) received from: 10.71.226.158 at 2011-3-10 10:53:04
Time stamp: 0 days 00h:05m:38s.06th
Agent address: 10.71.226.158 Port: 982 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: qq
SNMPv1 agent address: 10.71.226.158
Enterprise: northboundNotificationType
Specific Trap MIB Lookup Results
Name: northBoundSynchAlarmStart, Module: T2000-NETMANAGEMENT-MIB,
Enterprise: northboundNotificationType
Bindings (1)
Binding #1: northboundNotificationType.0.4 *** (int32) 0

D.4.3 Active Alarm Synchronization Result Trap

After the NMS/OSS send alarm synchronization request to the U2000, the SNMP NBI will
report the active alarm with the filter criteria to the NMS/OSS.
55: Specific trap northboundNotificationType::northBoundSynchAlarm #2
trap(v1) received from: 10.71.226.158 at 2011-3-10 10:53:04
Time stamp: 0 days 00h:05m:38s.25th
Agent address: 10.71.226.158 Port: 982 Transport: IP/UDP Protocol:
SNMPv1 Trap
Manager address: 10.70.71.97 Port: 6666 Transport: IP/UDP
Community: qq
SNMPv1 agent address: 10.71.226.158
Enterprise: northboundNotificationType
Specific Trap MIB Lookup Results
Name: northBoundSynchAlarm, Module: T2000-NETMANAGEMENT-MIB,
Enterprise: northboundNotificationType
Bindings (36)
Binding #1: northboundReportAlarmManagedObjectClass.0 *** (octets)
(zero-length)
Binding #2: northboundReportAlarmManagedObjectInstance.0 ***
(octets) Huawei/U2000
Binding #3: northboundReportAlarmEventType.0 *** (octets)
processingErrorAlarm
Binding #4: northboundReportAlarmEventTime.0 *** (octets)
2008-09-21,15:29:56.0

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 157

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Binding #5: northboundReportAlarmProbableCause.0 *** (octets) SFTP

server fault
Binding #6: northboundReportAlarmSpecificProblems.0 *** (octets)
SFTP server fault
Binding #7: northboundReportAlarmPerceivedSeverity.0 *** (octets)
Major
Binding #8: northboundReportAlarmNotificationIdentifier.0 ***
(int32) 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) Huawei/U2000
Binding #13: northboundReportAlarmNEName.0 *** (octets) Huawei/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

D.4.4 Active Alarm Synchronization End Trap

Active alarm synchronization end traps are triggered when all required alarms have been
reported to the OSS or the OSS automatically stops the synchronization.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 158

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide D U2000-T MIB

Synchronization Stopped After Alarm Reporting Was Complete

After all required alarms are reported to the OSS, the U2000 sends traps through the SNMP
NBI to inform the OSS that the alarm reporting is complete.
101: Specific trap northboundNotificationType::northBoundSynchAlarmEnd
#4 trap(v1) received from: 10.71.226.158 at 2011-3-10 10:53:08
Time stamp: 0 days 00h:05m:42s.27th
Agent address: 10.71.226.158 Port: 982 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.226.158
Enterprise: northboundNotificationType
Specific Trap MIB Lookup Results
Name: northBoundSynchAlarmEnd, Module: T2000-NETMANAGEMENT-MIB,
Enterprise: northboundNotificationType
Bindings (1)
Binding #1: northboundNotificationType.0.4 *** (int32) 1

Synchronization Was Stopped by the OSS

During the synchronization, the OSS automatically interrupts the process. The U2000 then
reports traps to inform the OSS that the synchronization is stopped as a response to the
request.
101: Specific trap northboundNotificationType::northBoundSynchAlarmEnd
#4 trap(v1) received from: 10.71.226.158 at 2011-3-10 10:53:08
Time stamp: 0 days 00h:05m:42s.27th
Agent address: 10.71.226.158 Port: 982 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.226.158
Enterprise: northboundNotificationType
Specific Trap MIB Lookup Results
Name: northBoundSynchAlarmEnd, Module: T2000-NETMANAGEMENT-MIB,
Enterprise: northboundNotificationType
Bindings (1)
Binding #1: northboundNotificationType.0.4 *** (int32) 0

Synchronization Was Stopped by Abnormal Event

58: Specific trap northboundNotificationType::northBoundSynchAlarmEnd #4
trap(v1) received from: 10.71.224.13 at 2011-4-27 17:15:52
Time stamp: 0 days 00h:22m:37s.33th
Agent address: 10.71.224.13 Port: 982 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: northboundNotificationType
Specific Trap MIB Lookup Results
Name: northBoundSynchAlarmEnd, Module: T2000-NETMANAGEMENT-MIB,
Enterprise: northboundNotificationType
Bindings (1)
Binding #1: northboundNotificationType.0.4 *** (int32) 2

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 159

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide E Service Ports Description

E Service Ports Description

This appendix describes service ports of the Northbound Interface and how to query the
service ports.

E.1 Notes and Precautions

E.2 Port Used Between the U2000 Server and the OSS
This topic describes the port used between the U2000 server and the OSS.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 160

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide E Service Ports Description

E.1 Notes and Precautions

In the practical communication process, the source (the server) and the sink (the client) use
relevant ports. Usually you only need to specify the source port, and the sink port is
dynamically created.
Note the following during the project implementation:
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.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 161

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide F Setting an Alarm or Event Northbound Filtering Rule

F Setting an Alarm or Event Northbound

Filtering Rule

On the live network, the NMS receives a large number of alarms or events. This causes
overload on the NMS, resulting in network congestion and breakdown. In addition, users
cannot quickly locate their concerned alarms or events. After an alarm or event northbound
filtering rule is set, the iMAP can report or not report only alarms or events that match the rule
to the NMS. The reported alarms or events are more accurate and users can focus on
concerned alarms or events.

Context
l If you do not set the northbound filtering rules, all alarms or events are reported by
default.
l Alarm or event northbound filtering rules apply only to alarms or events that are
generated after the rules are set. Alarm or event northbound filtering rules take effect for
multiple NMSs.
l If you select reporting alarms that meet the rule to the northbound interface, the alarms,
corresponding acknowledged alarms, unacknowledged alarms, and clear alarms that
meet the northbound filtering rule are reported to the northbound interface (although the
rule is deleted, modified, or not used). If you select do not reporting alarms that meet the
rule to the northbound interface, the alarms, corresponding acknowledged alarms,
unacknowledged alarms, and clear alarms that meet the northbound filtering rule are not
reported to the northbound interface (although the rule is deleted, modified, or not used).
l This tag is customized for section xxx for the M2000.
l Only users in the Administrators group can import alarm or event northbound filtering
rules in batches.
l The OSS supports creation of only one alarm northbound filtering rule and one event
northbound filtering rule.

Procedure
Step 1 Choose Fault > Alarm Settings > Northbound Filtering Rules from the main menu
(traditional style); alternatively, double-click Fault Management in Application Center and
choose Alarm Settings > Northbound Filtering Rules from the main menu (application
style).

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 162

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide F Setting an Alarm or Event Northbound Filtering Rule

Step 2 In the Northbound Filtering Rules window, set an alarm or event northbound filtering rule.

Setting Northbound Operations

Filtering Rule
Adding an alarm or event 1. Click Add, and choose Alarm Northbound Filtering
northbound filtering rule Rule or Event Northbound Filtering Rule.
2. In the Add Alarm Northbound Filtering Rule or Add
Event Northbound Filtering Rule dialog box, set the
filter criteria, and click Next.
3. Set remarks and select Enable.
4. Select an execution mode.
5. Click Finish.

Modifying an alarm or event 1. Select a rule, and then click Properties.

northbound filtering rule
2. In the Properties dialog box, modify the parameters
settings.
NOTE
You can also select a rule, and click or double-click a field
to modify the parameters settings.

The fields displayed in can be modified. The

fields displayed in cannot be modified. The fields
displayed in are already modified but are not used.
Click Apply to save the modifications. The Apply button is
available after a field is modified regarding whether a
record is selected.
3. Click OK.

Deleting an alarm or event 1. Select a rule and click Delete.

northbound filtering rule
NOTE
You can select more than one record by holding down Shift or
Ctrl.
2. In the Confirm dialog box, click Yes.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 163

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide F Setting an Alarm or Event Northbound Filtering Rule

Setting Northbound Operations

Filtering Rule

Exporting alarm or event 1. Select one or more rules and click Export.
northbound filtering rules 2. Select a save path in the Export dialog box.
3. Click Save.
NOTE
When alarm or event rules are exported, corresponding NE
information is not exported.

Importing alarm or event 1. Click Import.

northbound filtering rules 2. In the Import dialog box, select one or more rules that
are stored on the local computer.
NOTE
The OSS supports creating or importing a maximum of one
alarm northbound filtering rule and one event northbound
filtering rule.
3. Click Open. If you select more than one rule, the rules
are directly imported. If you select one rule, the Add
Alarm Northbound Filtering Rule or Add Event
Northbound Filtering Rule dialog box is displayed.
Modify parameters of the rule and click Next until
Finish.
NOTE
When alarm or event rules are imported, corresponding NE
information is not imported.

----End

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 164

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide G Equipment Supported

G Equipment Supported

Transport Equipment

Table G-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 ne
MST RTN RTN
P (TD
M
Featu
re)

Alarm

NOTE

l Submarine and North American equipment is not supported.

l For restrictions on specific parameters, see SNMP NBI User Guide.

Router Equipment

Table G-2 Router equipment supported by the SNMP NBI

Feature NE CX Huawei BRAS ATN Security
Series Series Switch

Alarm

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 165

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide G Equipment Supported

NOTE

The following devices are supported:

l NE series: (NE40/40E/40E-4/40E-X3/40E-X8/40E-X16, NE80/80E, NE5000E, NE5000E-Multi).
l CX series: CX600/600-4/600-8/600-16/600-X1/600-X2/600-X3/600-X4/600-X8/600-X16.
l Switches: Quid way S2300/3300/5300/9300
l BRAS: ME60/60-X3/-X8/60-X16
l ATN VRP series: ATN910/950/990
l Endemon series
l eLog series
l vCPE devices (NEs, boards, ports and services)

Access Equipment

Table G-3 Access equipment supported by the SNMP NBI

Feature MSAN/DSLAM FTTx

Narrowband Broadband FTTH FTTB/FTTC

Port Port

Alarm

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 166

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide H Acronyms and Abbreviations

H Acronyms and Abbreviations

This part list the acronyms and abbreviations in this document.

E
EMS Element Management System

I
IP Internet Protocol

M
MC Monitor Center
MIB Management Information Base

N
NBI Northbound Interface
NE Network Element
NMC Network Management Center
NMS Network Management Station, namely the NMS/OSS.

P
PDU Protocol Data Unit

S
SMI Structure of Management Information
SNMP Simple Network Management Protocol

T
TCP Transmission Control Protocol
TMN Telecommunication Management Network

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 167

Copyright Huawei Technologies Co., Ltd.
iManager U2000 Unified Network Management System
SNMP NBI User Guide H Acronyms and Abbreviations

VB Variable Bindings, namely the alarm field to be reported.

Issue 01 (2016-01-15) Huawei Proprietary and Confidential 168

GPON Huawei OLT Basic Troubleshooting Commands
No ratings yet
GPON Huawei OLT Basic Troubleshooting Commands
23 pages
Nas-Ic-82424301-01 Rev H
No ratings yet
Nas-Ic-82424301-01 Rev H
72 pages
MA5600T Commissioning and Configuration Guide (V800R007C01 - 02, GPON) PDF
100% (2)
MA5600T Commissioning and Configuration Guide (V800R007C01 - 02, GPON) PDF
508 pages
ZENIC ONE R20 EMS Common Operations
No ratings yet
ZENIC ONE R20 EMS Common Operations
28 pages
3JL03001BTAAPCZZA01 - V1 - 5529 IDM Release 9.7 Installation Administration and User Guide
No ratings yet
3JL03001BTAAPCZZA01 - V1 - 5529 IDM Release 9.7 Installation Administration and User Guide
136 pages
Imanager U2000 Unified Network Management System
100% (3)
Imanager U2000 Unified Network Management System
1,187 pages
IManager U2000 V200R017C60 Administrator Guide 02 (PDF) - C
80% (5)
IManager U2000 V200R017C60 Administrator Guide 02 (PDF) - C
1,571 pages
TOGAF 9 Artifact Templates v1
No ratings yet
TOGAF 9 Artifact Templates v1
19 pages
Imanager U2000 Northbound XML Interface User Guide - (V100R002C01 - 05)
50% (2)
Imanager U2000 Northbound XML Interface User Guide - (V100R002C01 - 05)
120 pages
Huawei Transport Network Maintenance Reference-RTN Microwave 03
No ratings yet
Huawei Transport Network Maintenance Reference-RTN Microwave 03
86 pages
ATN 905 V200R002C01 Configuration Guide 03 (CLI)
100% (1)
ATN 905 V200R002C01 Configuration Guide 03 (CLI)
134 pages
I Manager Huawei
No ratings yet
I Manager Huawei
289 pages
OG For MA5600T or MA5603T NE Management - (V100R002C01 - 03)
No ratings yet
OG For MA5600T or MA5603T NE Management - (V100R002C01 - 03)
505 pages
3hh13842ffaatczza01 - v1 - r6.5 Cli Commands For 7362 Isam DFSF
No ratings yet
3hh13842ffaatczza01 - v1 - r6.5 Cli Commands For 7362 Isam DFSF
4,580 pages
3HH-08082-DEAA-TCZZA-02-CLI TL1 Alarm Mapping Document - R4 4 X
No ratings yet
3HH-08082-DEAA-TCZZA-02-CLI TL1 Alarm Mapping Document - R4 4 X
160 pages
Imanager U2000 V200R016C60 Administrator Guide 14 (PDF) - C PDF
No ratings yet
Imanager U2000 V200R016C60 Administrator Guide 14 (PDF) - C PDF
1,524 pages
RTN 980
No ratings yet
RTN 980
2 pages
BTS3012AE Base Station Cabinet Installation Manual
No ratings yet
BTS3012AE Base Station Cabinet Installation Manual
155 pages
IManager U2000 Unified Network Managemen
No ratings yet
IManager U2000 Unified Network Managemen
260 pages
Baza Cisco RK2
No ratings yet
Baza Cisco RK2
178 pages
U2000 SNMP Nbi User Guide v100r006c0205
No ratings yet
U2000 SNMP Nbi User Guide v100r006c0205
175 pages
Huawei Imanager U2000 Northbound CORBA Interface Developer Guide (Configuration)
100% (1)
Huawei Imanager U2000 Northbound CORBA Interface Developer Guide (Configuration)
344 pages
U2000 Fundamental Configuratin Guide
No ratings yet
U2000 Fundamental Configuratin Guide
60 pages
Huawei Series Ethernet Switches Alarm Handling S2750&5700&6700 PDF
No ratings yet
Huawei Series Ethernet Switches Alarm Handling S2750&5700&6700 PDF
946 pages
Huawei OPTIX RTN 600 TRAINING210 Presentation Basics OPTIX RTN 605 610 620
0% (1)
Huawei OPTIX RTN 600 TRAINING210 Presentation Basics OPTIX RTN 605 610 620
74 pages
U2000 SNMP Nbi User Guide - (v100r006c02 - 05)
No ratings yet
U2000 SNMP Nbi User Guide - (v100r006c02 - 05)
175 pages
Huawei Guide - Basic Configuration
No ratings yet
Huawei Guide - Basic Configuration
233 pages
Imanager U2000 V200R016C50 XML NBI Developer Guide Alarm PDF
No ratings yet
Imanager U2000 V200R016C50 XML NBI Developer Guide Alarm PDF
123 pages
Smart Devices
No ratings yet
Smart Devices
16 pages
Installation and Commissioning The RTN 900 V1R2 Hybrid Microwave-20091220-A
No ratings yet
Installation and Commissioning The RTN 900 V1R2 Hybrid Microwave-20091220-A
42 pages
3hh13800daaatqzza20 - v1 - r6.5 System Description For 7362 Isam DFSF
No ratings yet
3hh13800daaatqzza20 - v1 - r6.5 System Description For 7362 Isam DFSF
270 pages
03.developer Guide (Performance)
No ratings yet
03.developer Guide (Performance)
106 pages
U2000 V200R015C60 SNMP NBI User Guide 05
No ratings yet
U2000 V200R015C60 SNMP NBI User Guide 05
162 pages
MX Component Ver.4 - Programming Manual SH (NA) - 081085-G (04.15)
No ratings yet
MX Component Ver.4 - Programming Manual SH (NA) - 081085-G (04.15)
586 pages
02 MA5600T Basic Operation ISSUE1 00
No ratings yet
02 MA5600T Basic Operation ISSUE1 00
95 pages
MA5600&MA5603 V300R003C05 Configuration Guide 09
No ratings yet
MA5600&MA5603 V300R003C05 Configuration Guide 09
384 pages
HUAWEI MSAN Pre-Sales Specialist Training
100% (1)
HUAWEI MSAN Pre-Sales Specialist Training
40 pages
Reliance Wi-Fi Router Manual
No ratings yet
Reliance Wi-Fi Router Manual
33 pages
List of TCP and UDP Port Numbers
No ratings yet
List of TCP and UDP Port Numbers
30 pages
MNET Protocol Manual
No ratings yet
MNET Protocol Manual
78 pages
RAS Configuration
No ratings yet
RAS Configuration
108 pages
Huawei MA5616 Service Configuration Document
50% (2)
Huawei MA5616 Service Configuration Document
11 pages
MA5603T Product Description (GPON)
100% (3)
MA5603T Product Description (GPON)
90 pages
Slides From TCP/IP - Forouzan: - Process-to-Process Communication - User Datagram - Checksum - Use of UDP - UDP Design
No ratings yet
Slides From TCP/IP - Forouzan: - Process-to-Process Communication - User Datagram - Checksum - Use of UDP - UDP Design
7 pages
Communication System Characteristics: Daniel E. Nordell, PE
No ratings yet
Communication System Characteristics: Daniel E. Nordell, PE
175 pages
แนวข้อสอบ CCNA
No ratings yet
แนวข้อสอบ CCNA
20 pages
Unit I Computer Networks 16SCCCS6
No ratings yet
Unit I Computer Networks 16SCCCS6
69 pages
Nokia Datacom FMC Training
100% (1)
Nokia Datacom FMC Training
34 pages
How To Quickly Configure The OLT Huawei MA5608T With ONT Huawei
100% (2)
How To Quickly Configure The OLT Huawei MA5608T With ONT Huawei
5 pages
Commandes Navigator 7
No ratings yet
Commandes Navigator 7
281 pages
Wireshark Tutorial For Intermediate Beginners
No ratings yet
Wireshark Tutorial For Intermediate Beginners
8 pages
OSI Model
No ratings yet
OSI Model
15 pages
04 HCIP-Datacom-NCE Northbound Openness Lab Guide
No ratings yet
04 HCIP-Datacom-NCE Northbound Openness Lab Guide
57 pages
OSI Model and TCP/IP Protocol Suite)
No ratings yet
OSI Model and TCP/IP Protocol Suite)
40 pages
Si Entro Inst en Acces Card
No ratings yet
Si Entro Inst en Acces Card
132 pages
Historical Antecedent
No ratings yet
Historical Antecedent
11 pages
Huawei E9000 Product
100% (1)
Huawei E9000 Product
16 pages
6.FTTx GPON System Troubleshooting
No ratings yet
6.FTTx GPON System Troubleshooting
33 pages
Module 2-Basics of Wireless Networks
No ratings yet
Module 2-Basics of Wireless Networks
52 pages
Guide To Obtaining BSC6900 Information
No ratings yet
Guide To Obtaining BSC6900 Information
49 pages
EA5800-X7 Datasheet: Quick Spec
No ratings yet
EA5800-X7 Datasheet: Quick Spec
5 pages
PTN 6110 Packet Transport Product Hardware Introduction
100% (1)
PTN 6110 Packet Transport Product Hardware Introduction
35 pages
Re HK Reliance Jio
No ratings yet
Re HK Reliance Jio
4 pages
H. DBS Commissioning Guide
No ratings yet
H. DBS Commissioning Guide
19 pages
TCP Ip Model
No ratings yet
TCP Ip Model
5 pages
zxv10 b866v2f
No ratings yet
zxv10 b866v2f
20 pages
Huawei SmartAX MA5600T Series OLT Brochure PDF
No ratings yet
Huawei SmartAX MA5600T Series OLT Brochure PDF
4 pages
OLT Basic Configuration
No ratings yet
OLT Basic Configuration
5 pages
Radio Ceragon CLI
No ratings yet
Radio Ceragon CLI
13 pages
SIEMENS - BS241 Installation Guide
No ratings yet
SIEMENS - BS241 Installation Guide
18 pages
RTN 380 Brochure PDF
100% (1)
RTN 380 Brochure PDF
4 pages
CORBA 20120627154709-010 NetNumen U31 R22 (V12.12.20) Unified Network Management System Northbound Interface User Guide (Data Products)
No ratings yet
CORBA 20120627154709-010 NetNumen U31 R22 (V12.12.20) Unified Network Management System Northbound Interface User Guide (Data Products)
351 pages
GPRS Tutorial
No ratings yet
GPRS Tutorial
25 pages
Lte CV Engineer PDF
No ratings yet
Lte CV Engineer PDF
4 pages
MA5616 Configuration Script
No ratings yet
MA5616 Configuration Script
5 pages
EG8145X6-10 Datasheet
No ratings yet
EG8145X6-10 Datasheet
4 pages
Work Technology-2024
No ratings yet
Work Technology-2024
89 pages
Dea 5TT2
No ratings yet
Dea 5TT2
3 pages
Usefull Info Networking
No ratings yet
Usefull Info Networking
33 pages
Presentation On Internet Technologies PDF
No ratings yet
Presentation On Internet Technologies PDF
13 pages
RPSC Programmer Paper 2012
No ratings yet
RPSC Programmer Paper 2012
26 pages
P3APS17003EN Ethernet - IP Configuration Instructions
No ratings yet
P3APS17003EN Ethernet - IP Configuration Instructions
24 pages
Unit 1 MCQ
No ratings yet
Unit 1 MCQ
27 pages
01 VESDAnet TCPIP Connectivity Application Note
No ratings yet
01 VESDAnet TCPIP Connectivity Application Note
9 pages
DCA2201 Unit-01 Merged
No ratings yet
DCA2201 Unit-01 Merged
236 pages
IP Multimedia Subsystem IMS A Complete Guide
From Everand
IP Multimedia Subsystem IMS A Complete Guide
Gerardus Blokdyk
No ratings yet
Voice over LTE Standard Requirements
From Everand
Voice over LTE Standard Requirements
Gerardus Blokdyk
3/5 (1)
Drive testing The Ultimate Step-By-Step Guide
From Everand
Drive testing The Ultimate Step-By-Step Guide
Gerardus Blokdyk
No ratings yet
Alcatel-Lucent Network Routing Specialist II (NRS II) Self-Study Guide: Preparing for the NRS II Certification Exams
From Everand
Alcatel-Lucent Network Routing Specialist II (NRS II) Self-Study Guide: Preparing for the NRS II Certification Exams
Glenn Warnock
No ratings yet
Backhaul Deployment Report
From Everand
Backhaul Deployment Report
Wade Sarver
No ratings yet

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.